I have some weird issue.
When I write compose code, sometimes the app is killed.
There is no error message or firebase report.
So when the error is occured, I'm so confused about what's wrong.
is there any one who experienced this?
here is my environment.
Compose 1.3.0-beta02
Kotlin 1.7.10
AGP 7.3.0
Gradle 7.4
Related
I'm running docker for mac with the following version
Docker has recently started failing with the following error message
invalid character 's' looking for beginning of value
I was also recently shown this dialog when trying to shut down docker after receiving the above error message:
I've tried reducing the size of the disk to fully wipe it through the preferences dialog, but that didn't eliminate the issue:
What does this error message mean and how can I resolve it?
Turns out it was because I upgraded to the latest version of Docker for Mac. I downgraded to 4.12.0 and haven't seen the problem since.
I am trying to build ORO Platform js assets, using a non-docker environment, it works like a charm, but in Docker (either during Docker Build, or container execution) the building process stop and hangs with 100% CPU.
67% [0] building 1416/1470 modules 54 active ... ndles/orotask/sidebar_widgets/assigned_tasks/css/styles.scss
The building process does not necessarily hang on the exact same file. And also, the build seems to succeed on some occasion.
I've try to reduce to a minimum the process by removing Happy, tested with --max-old-space-size=4096, but no luck.
Sources : https://github.com/oroinc/platform/tree/master/build
How would you recommend debugging this ?
Thanks
There is a known issue when a NodeJs process hangs while you run it from the root user. As I know, there is no workaround for now. Consider using another user to build the assets.
If it's not the case, please review the Troubleshooting section in OroAssetBundle, that might help.
Since yesterday I am trying to start the Azure Cloud shell but every time I am getting the following error:
Sorry, something went wrong: Unknown Error
See attached image.
To troubleshoot I tried to delete the Cloud Shell Resource Group (cloud-shell-storage-westeurope) and its storage account.
After restarting the Cloud Shell I was asked to create the RG and storage account for the Cloud Shell again. But the problem was still there.
Apologies for that experience - we've recently been resolving this issue as it is a bug on our end. We've released a few hotfixes that will hopefully fix this issue, if you still hit it please try simply exiting the shell and launching it again. If at this point you still repeatedly receive this error, please open a support ticket with us here.
Thanks for your patience and for being a Cloud Shell user!
I recently set up concourse CI using the following docker-compose: https://concourse-ci.org/docker-repository.html and then tried the flight school training here: https://concourse-ci.org/flight-school.html and then, when that failed showing "no workers", I attempted the hello-world here: https://concourse-ci.org/hello-world.html.
I keep seeing an error saying "no workers". If I had to guess, this is because of a simple configuration issue on my end, but I am having trouble tracking it down.
Can someone please help me figure out how to debug this, I do not see errors in the docker startup logs. Searching for the problem is showing seemingly unrelated errors.
I talked with the team and it appears it was a race condition in v3.1 that I was running. Updating to v3.2 fixed the issues and everything is running smoothly.
We have Jenkins installed and running on a WebSphere Application Server. We recently upgraded the server to version 8.5.5 and switched the profile to use JDK version 1.7. Doing this Jenkins Crashes the WebSphere Application Server and we cannot tell why. Any hints or suggestions on things to look at? Switching the server back to JDK 1.6 seems to work just fine, can Jenkins not run on JDK 1.7 or is it something else?
I'll assume that by crash the websphere application server you mean either a fatal error at startup or a java process crash. Those can have many causes.
Just to give some ideas, it may be related to the fact that you had somewhat customized your JDK install and forgot to re-apply those customization to your new JDK. Or that switching SDK requires you to switch command line options, or that you indeed hit an incompatible class in the stack, or that your process crash because of bad luck, etc.
So please find more information in the logs, either the corresponding stack traces in your WAS server logs or the javacores crash files.
Please also report your jenkins version.
As for JDK 7 compatibility, latest jenkins itself should be compatible, yet some plugins are not
You may also want to read this: https://stackoverflow.com/questions/17411717/jenkins-on-websphere-reports-java-lang-noclassdeffounderror-jenkins-model-jenki. Maybe you have the same issue.
If you indeed find out an incompatibility, please report an issue in jenkins issue tracker and consider updating the Jenkins Websphere wiki.