The first step in the TC build process is to run "yarn install" in the directory: D:\TeamCity\Agent\work\MyApp
this is successfull up until: [4/4] Rebuilding all packages...
at which point this error is thrown:
```[Step 1/5] error An unexpected error occurred: "D:\\TeamCity\\Agent\\work\\MyApp\\node_modules\\#babel\\runtime-corejs2\\node_modules\\core-js: UNKNOWN: unknown error, open 'D:\\TeamCity\\Agent\\temp\\buildTmp\\yarn--1592234614361-0.5350564069819825\\yarn'"```
From what I can tell here, its trying to open the temp folder, but cant? or cant find it?
This does not happen consistently. It seems to be random, or whenever there is an extended time between builds. We cannot determine a common pattern. To fix it, we just re-run the build.
We have tried 'yarn install --verbose' and 'yarn install --force' the former showed nothing usefull on output, and --force was a guess at best.
I'm hoping someone can give a bit more context as to exactly what that error might mean.
Screenshot of the error
Related
Context:
I am attempting to run the demo from Wundergraph on a work computer. When I get to installing Wundergraph with Yarn, it fails. The Wundergraph error is.
Internal Error: Error when performing the request
at ClientRequest.<Anonymous> (C:Users\{user name here}\AppData\Roaming\npm\node_modules\corepack\dist\corepack.js :3927:20)
at ClientRequest.emit (noe:events:390:28)
at TLSSocket.socketErrorListener (node:_http_client:447:9)
at TLSSocket.emit (node:events:390:20)
at emitErrorNT (node:internal/streams/destroy:157:8)
at emitErrorCloseNT (node:internal/streams/destroy:122:3)
at processTicksAndRejections (node:internal/process/task_queues:83:21)
With the socket issue, I am guessing there is a proxy or some other security issue on the client computer. I have successfully run the following on a separate, personal computer:
yarn global add #wundergraph/wunderctl#latest
No variation of yarn commands work on the work, computer (fails with any of the following):
yarn
yarn global add #wundergraph/wunderctl#latest
To eliminate possibilities:
On my local machine, yarn will not properly add path to wunderctl, which means searcing out the .exe to get the samples installed. This is a minor oversight in the demo, as the demo now works.
Does not matter if the command prompt is run as me or as administrator. It fails either way.
Fails on VPN and off, so VPN not the issue.
I can get things installed with NPM, but that appears to successfully install the .js files from Wundergraph and not the .exe. I am thinking this might be a clue.
I am going to work with others who say they have it installed and see how they did it, but that won't happen until next week. As I am contract and they are employees, it could end up being additional restrictions.
As this does it with yarn, as well as yarn {install command here}, I am guessing it is some check yarn does every time, or permissions on the yarn files themselves.
I know this is a long shot, but hoping someone encountered this and has found a way down the Rabbit Hole and then back out of wonderland. My fear is having to go full manual, edit the sample files heavily to eradicate yarn (for npm, most likely), have to wait until Wundergraph goes open source and grab the bits, work strictly from command line, or all of the above.
I have done a lot of searching for an answer before coming here.
I had the same problem with another package, with exactly the same error call stack.
First I updated NodeJS to the latest stable version 16.13.1 (I had 14.16.0). After that yarn showed signs of life:
yarn install v1.21.1
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
But then it failed with
RequestError: connect ETIMEDOUT {ip address}:443
at ClientRequest.<anonymous> (node_modules\got\source\request-as-event-emitter.js:178:14)
at Object.onceWrapper (node:events:510:26)
at ClientRequest.emit (node:events:402:35)
at ClientRequest.origin.emit (node_modules\got\node_modules\#szmarczak\http-timer\source\index.js:37:11)
at TLSSocket.socketErrorListener (node:_http_client:447:9)
at TLSSocket.emit (node:events:390:28)
That ip address was indeed unreachable due to a routing problem, after I fixed that all went well.
I tried the steps for quick setup of firefox debugger at http://firefox-dev.tools/debugger/#quick-setup a few times but had the same problem.
I have pasted all my commands and warning (including error) messages in a gist at the bottom.
I suspect two things may cause the failure of the setting up.
when running curl -o- -L https://yarnpkg.com/install.sh | bash -s, I got warning message saying it is advised to not mix npm with yarn. However, I have not yet found out a way to separate them.
when running yarn, I got a lot of warning message saying the versions of packages are not matching, a lot of error messages for failing to run commands which I suspect to be the result of unmet packages but I can be wrong about it.
or what do you think the problem is?
could you give me some guidance on how to resolve this setting up problem? Thanks
please see the warning and error messages here in the gist.
https://gist.github.com/EmbraceLife/f84993112c5b4a894c30b0a4ba4bb4fc
it is advised to not mix npm with yarn
...in a single project. If you follow the instructions of cloning a clean repository and running yarn install inside, you should be fine.
I got a lot of warning message saying the versions of packages are not matching
I get these too, so I don't think anything is wrong on your end.
warning " > react-redux#5.0.7" has unmet peer dependency "redux#^2.0.0 || ^3.0.0 || ^4.0.0-0".
warning "devtools-launchpad > svg-inline-react#3.0.0" has incorrect peer dependency "react#^0.14.0 || ^15.0.0".
warning "devtools-launchpad > url-loader#0.5.9" has unmet peer dependency "file-loader#*".
warning " > eslint-plugin-mozilla#1.2.1" has unmet peer dependency "eslint-plugin-no-unsanitized#^3.0.0".
warning "devtools-reps > devtools-components > #storybook/react#3.4.8" has unmet peer dependency "babel-core#^6.26.0 || ^7.0.0-0".
warning "devtools-reps > devtools-components > #storybook/react#3.4.8" has unmet peer dependency "babel-runtime#>=6.0.0".
warning " > babel-jest#23.6.0" has unmet peer dependency "babel-core#^6.0.0 || ^7.0.0-0".
node-pre-gyp WARN Pre-built binaries not found for fsevents#1.2.4 and node#12.9.1 (node-v72 ABI, unknown) (falling back to source compile with node-gyp)
followed by a large number of build errors, ending with:
30 warnings and 14 errors generated.
make: *** [Release/obj.target/fse/fsevents.o] Error 1
gyp ERR! build error
...looks like a problem with your running node12 (the CI seems to be running with node10) but I'm not even sure lack of fsevents is fatal...
Listening for WS on localhost:8116, all traffic is proxied to localhost:6080
TCP connection failed: Error: connect ECONNREFUSED 127.0.0.1:6080
These messages in your output are expected - you're supposed to run a controlled instance of the browser that listens on port 6080, until you do the "launcher" page tries to connect and fails repeatedly.
Apart from the console messages, is there a problem or does the debugger work?
i get this error mesage when I try to deploy my project and I really do not understand why:error log
shub is unable to build the Python egg of your project. This could be related to a misconfigured setup.py. Try running the 'build egg' command yourself so you can take a look at the error message: python setup.py clean -a bdist_egg -d temp_directory (run it in your project directory).
If you don't have any custom/important code in your setup.py, you can try deleting it, and shub will auto-generate a vanilla one on the next deploy.
I have been running on some problems since the last update (6.38.1). docpad seems to be broken on macosx the command "docpad run" or "docpad watch" returns the error (on the browser)
Error 15 (net::ERR_SOCKET_NOT_CONNECTED): Error unknown
when i try to access
http://localhost:9778
but "docpad server" works without problems, so maybe the error is the liverload module or other module for development... i'm not able to isolate this problem.
does anyone has the same problem and maybe a solution to share? i'm about to leave docpad because of this error :(
I get the following error in Jenkins. I'm using Maven 3.0.4. Running on a Linux slave. Anyone have any solutions?
Error: Could not find or load main class org.jvnet.hudson.maven3.agent.Maven3Main
ERROR: Failed to launch Maven. Exit code = 1
The solution was not even related to the error message I was seeing. But nonetheless, I had a step where I install custom tools using the custom tools plugin. I never used the tools, but just installed them. And this gave me the above error.