docker-compose build is failing. I want to see what docker-compose build is doing so I can reproduce it step by step and drill down into the problem. What I'm interested in is a process for finding out what's wrong, not a solution to my current problem. Setting --log-level DEBUG doesn't seem to help at all.
Related
I was running tests just fine a few days ago. But, from some point onward, the Run button is greyed out and IntelliJ no longer makes configuration for Run. There seems to be no way to run the test. How can I address this problem?
Run button being greyed out
While I was searching online, I found this advice on adding proper Project compiler output and Output path and Test output path via Project Structure (as shown in screenshot below). But this did not fix my problem. Any tips on addressing this issue?
Project Structure - Output path and Test output path
By the way, when I tried to add Run configuration, it was giving me this message saying "Test Class is not specified". As shown in the image below, it didn't enable me to add the Test Class.
attempt to create a Run configuration failed
Also, I manually marked both src - main - scala as Sources Root and src - test - scala as Test Sources Root, but still didn't work. Then, I deleted .idea directory and re-imported the entire project. But then, I saw this message "[info] shutting down sbt server".
now shutting down sbt server
Any help will be greatly appreciated!
Edit:
Summary, I tried to follow only the steps listed in the below two links as applies to windows:
https://github.com/mapbox/mapbox-gl-js/blob/master/CONTRIBUTING.md
https://github.com/stackgl/headless-gl#windows
Here I have reattached the screenshot of the commands that I had problems with:
https://imgur.com/RCQCNU5
One more step I took that I should mention is I also did not find the headless gl when I downloaded the repository, when the install headless gl command did not work I manually copied the file and put it in my local copy under the nodemodules directory thinking it would work but it didnt solve anything. I do think this is related to access issues but I dont know what else I should try to get it working?
First, let's clarify your problem: you want a version of mapbox-gl.js which contains a recently fixed bug.
Your best option is to just wait a couple of weeks for a release.
Failing that, you should build your own, from master. You don't need to set up a debug server for that. You can skip straight to the "Creating a Standalone Build" section.
If the steps for building on Windows don't work for some reason, you could set up a local virtual machine running Ubuntu and use that.
But honestly, just wait a couple of weeks. :)
Just in case some one else need to run this on local server.
After clone
Run npm install
npm run start-debug
It will start listening on port 9966.
Test the debug html files entering to
localhost:9966/debug/FILE_NAME_TO_TEST.html
Validation of ServiceMetadataDerivedType failed: not found
I tried running without deploying the application. I tried to run a pipeline in Jdev but it is throwing this error in test console. Tried restarting my machine also, but no luck. Please help.
I have edited the question, do not know how to go about. Last time somebody has deleted my answer. So here is the answer: When I first deploy it on WebLogic, and then run the pipeline, it ran successfully.
So, I was given the task to upgrade our yocto based system from fido to morty. I have very little experience with yocto, I have been struggling with it and trying to understand it for almost a week now. I have managed to fix some issues, but now I'm facing a problem when trying to build the image:
ERROR: basic-image-1.0-r0 do_rootfs: The following packages could not be configured offline and rootfs is read-only: ['component']
ERROR: basic-image-1.0-r0 do_rootfs: Function failed: do_rootfs
If I disable the compoents the basic-image builds just fine, and both of them build just fine on their own, i.e bb component
I don't even know where to start looking for a solution. So if you have any idea what might be causing this or where to start looking for a solution, it would be greatly appreciated.
Ofcourse I have been browsing the yocto manuals, but there is so much stuff that I'm just overwhelmed by all of it.
Well, the "problem" stems from the fact that you have the following in your image:
IMAGE_FEATURES += "read-only-rootfs"
That implies that nothing can modify the rootfs during runtime, everything has to be done off-line, i.e. when constructing the rootfs in question.
Your package component (adcl and cfgmgr in your original question), all have a post-installation script including the following snippet:
pkg_postinst_${PN} () {
if test "x$D" != "x" then
# Need to run on first boot
exit 1
fi
}
(Something similar at least, which exit 1).
The conditional in my example checks if the pkg_postinst script is being run during rootfs creation, if so, it exits with 1 as exit status. That means that the pkg_postinst has to be run live on the target system. However, as the target system is read-only, this will be impossible, and the build fails.
You'll have to check for pkg_postinst scripts, and rewrite them, such that they're able to be run during rootfs creation.
I have been trying to get my front-end working on docker for the past day and I have narrowed down some irregular behaviour to eslint-watch and docker. I have recreated a minimal working repo of the bug I am experiencing.
It seems that linting is somehow staggered when using docker-compose (docker-compose up specifically, docker-compose run seems to work fine). Rather the last console log statements are staggered. I am not sure what it is, but from my reading the best interpretation I can give is that the log messages that should be printed out for the linting are for some reason not flushed out of the node message queue.
I have narrowed down the message printing to the eslint watcher file. If I add in more console logs at the end of this method it prints out the linting fine, but it staggers my logs (i.e. the last logs in execution). Funny thing is, if I save again it flushes the rest of the message queue i.e. the previous logs print out.
To replicate, download my repo, run docker-compose up and edit the test.js file and save. Watch the logs in your terminal for the linting. You will see what I mean.
I hope this is descriptive enough, it's a really strange bug and difficult to explain in a question.
Any ideas how I can actually figure this out?
Finally figured this out. iterm of all things was the culprit. Really weird.
Anyway I was using iTerm2 3.0.9. It seems in iTerm2 3.0.12 (OS 10.8+) this bug is fixed.
https://github.com/rizowski/eslint-watch/issues/94#issuecomment-261287265