I have an Android Studio project connected to GitHub Actions, but my GitHub actions started to fail and I don't know the reason. For example, the log of working actions was:
Fetching gem metadata from https://rubygems.org/.
31
Following files may not be writable, so sudo is needed:
32
/var/lib/gems/3.0.0
33
/var/lib/gems/3.0.0/build_info
34
/var/lib/gems/3.0.0/cache
35
/var/lib/gems/3.0.0/doc
36
/var/lib/gems/3.0.0/extensions
37
/var/lib/gems/3.0.0/gems
38
/var/lib/gems/3.0.0/plugins
39
/var/lib/gems/3.0.0/specifications
40
Fetching bundler 2.2.29
41
Installing bundler 2.2.29
But now for some reason I'm seeing this and builds fail:
Fetching bundler 2.2.29
32
Retrying download gem from https://rubygems.org/ due to error (2/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.0.0/cache/bundler-2.2.29.gem`. It is likely that you need to grant write permissions for that path.
33
34
Retrying download gem from https://rubygems.org/ due to error (3/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.0.0/cache/bundler-2.2.29.gem`. It is likely that you need to grant write permissions for that path.
35
36
Retrying download gem from https://rubygems.org/ due to error (4/4): Bundler::PermissionError There was an error while trying to write to `/var/lib/gems/3.0.0/cache/bundler-2.2.29.gem`. It is likely that you need to grant write permissions for that path.
Telling me that I need to grant permission. Any help would be much appreciated.
Related
I am getting the following error while running my Ruby on rails 6 app on locale (Ubuntu 18.04 using chrome):
Uncaught (CardanoSerializationLib.ts:15 in promise) CompileError: WebAssembly.instantiate(): expected magic word 00 61 73 6d, found 3c 21 44 4f #+0
and
GET http://localhost:3000/wasm/csl-v10.0.4.wasm 404 (Not Found)
and
`WebAssembly.instantiateStreaming` failed because your server does not serve wasm with `application/wasm` MIME type. Falling back to `WebAssembly.instantiate` which is slower. Original error:
TypeError: Failed to execute 'compile' on 'WebAssembly': HTTP status code is not ok
Seems like it is affecting webpacker, and cannot render my pages.
Looks like disabling Eternl wallet extension might be a temp fix while the team looks into it:
https://github.com/ccwalletio/tracker/issues/119
I’m having this weird error when deploying to nexus.
npm i
npm ERR! code E403
npm ERR! 403 Forbidden: express#^4.16.3
Where the artifact at the end it changes from time to time (I mean, is not always express#^4.16.3)
Things I have checked so far.
I can login to Nexus through browser using the user and password that is defined on the upload.
I can login to Nexus repo through shell using the user and password defined on the upload.
I can upload the package using a local shell and using the same credentials.
During the execution, I did a curl -v repo-url and I get a correct response (so I assume I got network connectivity).
I have checked if was a proxy, and there was.
I deleted the proxy configuration
I changed to another proxy
I added a no proxy variable so I can except the FQDN of the Nexus URL Repo
I also checked if the package (in this case express#^4.16.3) exists on Nexus, and it does.
But in all cases I’m still getting the 403 error at the end.
To give a bit more of context.
This is using Jenkins.
And targetting a new nexus that I'm deploying.
If I use the old nexus I don’t have this issues. It only happens to the new version
And, I migrate all the data, so the same user that exists in the old nexus is in the new one and you can login with those credentials.
I have checked nexus.log, request.log and Jenkins logs but didn't find any errors.
Jenkins and "old nexus" are installed in docker form in the same server
"New nexus" is installed in another server, also as a container.
From the servers I have network connectivity between them (can ping them, check port, and curl to the URLs.
I have given nx-admin role to the user that is configured.
Still the same error.
While the Jenkins job was running, I left the Nexus Log Viewer open
There was no error or sign in the Nexus Log Viewer.
BUT, I managed to find the following log in Jenkins: JENKINS_HOME/.npm/_logs/timestamp-debug.log
Where I have the ERR 403, and got the following
jenkins#hostname:~/.npm/_logs$ cat timestamp-debug.log
0 info it worked if it ends with ok
1 verbose cli [ '/var/jenkins_home/tools /jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/bin/node',
1 verbose cli '/var/jenkins_home/tools /jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/bin/npm',
1 verbose cli 'i' ]
2 info using npm#5.6.0
3 info using node#v8.9.4
4 verbose npm-session 609c979f77769373
5 silly install runPreinstallTopLevelLifecycles
6 silly preinstall api-docs#1.0.0
7 info lifecycle api-docs#1.0.0~preinstall: api-docs#1.0.0
8 silly install loadCurrentTree
9 silly install readLocalPackageData
10 silly install loadIdealTree
11 silly install cloneCurrentTreeToIdealTree
12 silly install loadShrinkwrap
13 silly install loadAllDepsIntoIdealTree
14 http fetch GET 403 http://nexus-url/repository/my-repo-npm/express 2096ms
15 silly fetchPackageMetaData error for express#^4.16.3 403 Forbidden: express#^4.16.3
16 http fetch GET 403 http://nexus-url/repository/my-repo-npm/http-server 2094ms
17 http fetch GET 403 http://nexus-url/repository/my-repo-npm/swagger-ui-express 2092ms
18 silly fetchPackageMetaData error for http-server#^0.11.1 403 Forbidden: http-server#^0.11.1
19 silly fetchPackageMetaData error for swagger-ui-express#^4.0.1 403 Forbidden: swagger-ui-express#^4.0.1
20 http fetch GET 403 http://nexus-url/repository/my-repo-npm/multi-file-swagger 2095ms
21 silly fetchPackageMetaData error for multi-file-swagger#2.2.0 403 Forbidden: multi-file-swagger#2.2.0
22 http fetch GET 403 http://nexus-url/repository/my-repo-npm/express 45ms
23 silly fetchPackageMetaData error for express#^4.16.3 403 Forbidden: express#^4.16.3
24 http fetch GET 403 http://nexus-url/repository/my-repo-npm/http-server 46ms
25 silly fetchPackageMetaData error for http-server#^0.11.1 403 Forbidden: http-server#^0.11.1
26 http fetch GET 403 http://nexus-url/repository/my-repo-npm/multi-file-swagger 48ms
27 silly fetchPackageMetaData error for multi-file-swagger#2.2.0 403 Forbidden: multi-file-swagger#2.2.0
28 http fetch GET 403 http://nexus-url/repository/my-repo-npm/swagger-ui-express 49ms
29 silly fetchPackageMetaData error for swagger-ui-express#^4.0.1 403 Forbidden: swagger-ui-express#^4.0.1
30 silly saveTree api-docs#1.0.0
31 verbose stack Error: 403 Forbidden: express#^4.16.3
31 verbose stack at fetch.then.res (/var/jenkins_home/tools /jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/pacote/lib/fetchers/registry/fetch.js:42:19)
31 verbose stack at tryCatcher (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/util.js:16:23)
31 verbose stack at Promise._settlePromiseFromHandler (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:512:31)
31 verbose stack at Promise._settlePromise (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:569:18)
31 verbose stack at Promise._settlePromise0 (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:614:10)
31 verbose stack at Promise._settlePromises (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/promise.js:693:18)
31 verbose stack at Async._drainQueue (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:133:16)
31 verbose stack at Async._drainQueues (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:143:10)
31 verbose stack at Immediate.Async.drainQueues (/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/lib/node_modules/npm/node_modules/bluebird/js/release/async.js:17:14)
31 verbose stack at runCallback (timers.js:789:20)
31 verbose stack at tryOnImmediate (timers.js:751:5)
31 verbose stack at processImmediate [as _immediateCallback] (timers.js:722:5)
32 verbose cwd /var/jenkins_home/jobs/CUSTOM/workspace
33 verbose Linux 4.4.21-69-default
34 verbose argv "/var/jenkins_home/tools /jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/bin/node" "/var/jenkins_home/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/Node_8.9.4/bin/npm" "i"
35 verbose node v8.9.4
36 verbose npm v5.6.0
37 error code E403
38 error 403 Forbidden: express#^4.16.3
39 verbose exit [ 1, true ]
I looked for this packages on my Nexus Repo
express#^4.16.3
http-server#^0.11.1
swagger-ui-express#^4.0.1
multi-file-swagger#2.2.0
And found that I did not got some of those, so I downloaded them and uploaded to the repo.
I have also rerun the job, but still got the same error.
Even configuring the proxy at server and container level didn't worked.
I'd found out that Jenkins has a proxy configuration at the application level.
So I went into Jenkins, Administration section and configured the proxy properly. After that was done, it all started to work.
I am a broken man, my builds have been working for years, and since iOS did its latest build, i have issues. I cannot for life get this to work.
MAC is catilina, i cannot believe all of this was working and then a simple version update and i cannot get it to build. I use command line for android (it still works and build successfully). I used the gui for iOS but am now getting a vsTAC issue immediately, so changed to use TACO-cli and was able to connect to mac and start the build process. It fails with this error, my build is all there as id expect except the platform folder where id navigate to open the xcode as normal. But i assume this is because my build is failing. I have updated the mac to be on the exact versions windows is on, i have give all the files the correct permissions. I am totally at a loss. I have been on higher versions before and had it working in past, i wasnt able to update to cordova 9 as one of those plugins didnt support 9 yet.
Currently running:
npm 6.7.0
node 11.15.0
cordova 8.1.2
cordova-android 9.0.0
cordova-ios 6.1.0
23 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-android-permissions
24 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-app-version
25 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-bluetoothclassic-serial
26 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-device
27 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-dialogs
28 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-file
29 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-file-opener2
30 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-file-transfer
31 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-geolocation
32 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-inappbrowser
33 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-navigationbar
34 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-network-information
35 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-screen-orientation
36 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-statusbar
37 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-whitelist
38 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-wkwebview-engine
39 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-wkwebview-file-xhr
40 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-sqlite-storage
41 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/es6-promise-plugin
42 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/ionic-plugin-keyboard
43 warn checkPermissions Missing write access to /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/uk.co.workingedge.cordova.plugin.sqliteporter
44 timing stage:rollbackFailedOptional Completed in 1ms
45 timing stage:runTopLevelLifecycles Completed in 1869ms
46 warn VetIMPRESS#3.0.0 No repository field.
47 verbose stack Error: ENOENT: no such file or directory, access '/Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-android-permissions'
48 verbose cwd /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp
49 verbose Darwin 19.6.0
50 verbose argv "/usr/local/bin/node" "/usr/local/bin/npm" "install" "cordova-plugin-vs-taco-support" "--production" "--no-save"
51 verbose node v11.15.0
52 verbose npm v6.14.6
53 error code ENOENT
54 error syscall access
55 error path /Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-android-permissions
56 error errno -2
57 error enoent ENOENT: no such file or directory, access '/Users/AppleDev/.taco_home/remote-builds/taco-remote/builds/3456/cordovaApp/node_modules/cordova-plugin-android-permissions'
58 error enoent This is related to npm not being able to find a file.
59 verbose exit [ -2, true ]
I have a Dart with AngluarDart in local.
Ubuntu 16.04.2
DartSdk v1.23.0
"pub serve" seems work fine
$ pub serve
Loading source assets...
Loading angular2, dart_to_js_script_rewriter and dart_sass_transformer
transformers... (3.4s)
Serving xxx web on http://localhost:8080
Build completed successfully
But when I try to load the web into my browser I get this error:
[web] GET Served 3 cached assets.
[Info from Dart2JS]:
Compiling xxx|web/main.dart...
[Error from Dart2JS]:
web/main.dart:
The compiler crashed when compiling this element.
The compiler is broken.
When compiling the above element, the compiler crashed.
It is not possible to tell if this is caused by a problem in your program or not.
Regardless, the compiler should not crash.
The Dart team would greatly appreciate if you would take a moment to
report this problem at http://dartbug.com/new.
Please include the following information:
* the name and version of your operating system,
* the Dart SDK build number (build number could not be determined), and
* the entire message you see here (including the full stack trace
below as well as the source location above).
Build error:
Transform Dart2JS on xxx|web/main.dart threw error: The getter 'uses'
was called on null.
Receiver: null
Tried calling: uses
dart:core
Object.noSuchMethod
package:compiler_unsupported/src/dump_info.dart 576
DumpInfoTask.dumpInfoJson
package:compiler_unsupported/src/dump_info.dart 536
DumpInfoTask.dumpInfo.<fn>
package:compiler_unsupported/src/common/tasks.dart 63
CompilerTask.measure
package:compiler_unsupported/src/dump_info.dart 533
DumpInfoTask.dumpInfo
package:compiler_unsupported/src/compiler.dart 703
Compiler.compileLoadedLibraries.<fn>
package:compiler_unsupported/src/common/tasks.dart 176
CompilerTask.measureSubtask
package:compiler_unsupported/src/compiler.dart 582
Compiler.compileLoadedLibraries
package:compiler_unsupported/src/compiler.dart 471
Compiler.runInternal
===== asynchronous gap ===========================
package:compiler_unsupported/src/compiler.dart 310 Compiler.run.
<fn>.<fn>
dart:async
Future.Future.sync
package:compiler_unsupported/src/compiler.dart 310 Compiler.run.
<fn>
package:compiler_unsupported/src/common/tasks.dart 176
CompilerTask.measureSubtask
package:compiler_unsupported/src/compiler.dart 307 Compiler.run
package:compiler_unsupported/src/apiimpl.dart 245 CompilerImpl.run.<fn>.<fn>
Build completed with 2 errors.
[web] GET main.dart.js → Could not find asset xxx|web/main.dart.js.
[web] GET favicon.ico → (cached) xxx|web/favicon.ico
I tried to get DartSDK again, revised the PATH...
What can be the problem?
I solved the problem downgrading Dart SDK version.
From 1.23.0 to 1.21.1
Now the complilator do his job without problems.
I am using Dockerflow to run parallel tasks through the Google Pipelines API on Google Cloud Platform. I started a single-step task running 1389 VMs in parallel and found that 233 of the VMs were apparently doing nothing and hanging indefinitely.
I did a spot check of the serial console output and repeatedly saw the VMs running into "Getting controller config failed" errors.
When I tried logging into the VMs I received the error: "Connection Failed. We are unable to connect to the VM on port 22".
I am wondering why my VM instances are hanging, and if there is something I can do to avoid running into these issues.
I've included a snippet of the serial console output below
startupscript: +++ readlink -f /usr/share/google-genomics/startup.sh
startupscript: ++ dirname /usr/share/google-genomics/startup.sh
startupscript: + cd /usr/share/google-genomics
startupscript: + ./controller --operation_id <id> --validation_token <token> --base_path https://genomics.googleapis.com
create controller[2905]: Getting controller config
create controller[2905]: Getting controller config failed, will retry: Get <link>: Get <service_account_token_link>: net/http: timeout awaiting response headers
create controller[2905]: Getting controller config failed, will retry: Get <link>: dial tcp 74.125.26.95:443: i/o timeout
collectd[2342]: write_gcm: Asking metadata server for auth token
collectd[2342]: write_gcm: curl_easy_perform() failed: Couldn't connect to server
collectd[2342]: write_gcm: Error -1 from wg_curl_get_or_post
collectd[2342]: write_gcm: wg_transmit_unique_segment failed.
collectd[2342]: write_gcm: wg_transmit_unique_segments failed. Flushing.
there was a temporary networking issue in us-east1-b. All 3 above VMs were in us-east1-b. These minor incidents do not appear in https://status.cloud.google.com/
Serial console output for a successful run looks like:
A Feb 21 19:05:06 ggp-5629907348021283130 startupscript: + ./controller --operation_id --validation_token --base_path https://autopush-genomics.sandbox.googleapis.com
A Feb 21 19:05:06 ggp-5629907348021283130 create controller[2689]: Getting controller config
A Feb 21 19:05:36 ggp-5629907348021283130 create controller[2689]: Getting controller config failed, will retry: Get https://genomics.googleapis.com/v1alpha2/pipelines:getControllerConfig?alt=json&operationId=&validationToken=: dial tcp 173.194.212.81:443: i/o timeout
A Feb 21 19:05:43 ggp-5629907348021283130 controller[2689]: Switching to status: pulling-image
A Feb 21 19:05:43 ggp-5629907348021283130 controller[2689]: Calling SetOperationStatus(pulling-image)
A Feb 21 19:05:44 ggp-5629907348021283130 controller[2689]: SetOperationStatus(pulling-image) succeeded
The "Getting controller config failed, will retry" is fine. It succeeded upon retry. The "SetOperationStatus(pulling-image) succeeded" indicates networking is working.
In theory, you can submit any number of jobs to Pipelines API and the API will take care of queueing.
If these temporary networking hiccups become common, we may consider changing Pipelines API to somehow detect and retry.
there may have been a temporary networking issue. Can you give me some failed operation ids (or failed VM names)?
Have you tried again since then; can you reproduce the problem?