When I tried to write the integration test for the Kafka container I get this error after trying to build the project. I have no idea what is going wrong.
22:46:01.464 [Thread-4] WARN o.t.utility.ResourceReaper - Unable to delete image testcontainers/byvren8fgzpzaxgy
com.github.dockerjava.api.exception.NotFoundException: Status 404: {"message":"No such image: testcontainers/byvren8fgzpzaxgy:latest"}
I am using the version 1.15.1 org.testcontainers maven dependency. Is there any suggestion on what is going wrong?
The above issue happens when you had a couple of integration tests running locally and each test requires a separate test container.
Having all of the tests conducted locally with the help of a single test container solves the issue.
Related
I recently updated my Azerothcore docker version, but I am encountering an error: "azerothcore-wotlk-ac-worldserver-1 | MMAP:loadMap: 5303231.mmtile was built with generator v15, expected v16". I have tried deleting AC and installing from scratch following the guide on the Azerothcore website, but when I run "./acore.sh docker client-data", it is still downloading client data files for v15 instead of the latest version v16. I have followed the Docker Setup and Azerothcore Bash Dashboard setup, but I am still having issues. Does anyone know how I can fix this problem?
Thanks in advance for any help.
Best regards.
This sounds to me like a PR is required to fix the setup process of docker. If a manual swap of the client data isn't sufficient, only an adjustment of the docker script can solve this.
You should create an issue about it in the respective repo you've cloned, azerothcore-wotlk or acore-docker.
Edit: Please update and try again due to https://github.com/azerothcore/azerothcore-wotlk/pull/14527
I have Jest tests that are running against the dockerized Neo4j Database, and sometimes they fail on CircleCI. The error message for all 25+ of them is :
thrown: "Exceeded timeout of 5000 ms for a hook.
#*******api: Use jest.setTimeout(newTimeout) to increase the timeout value, if this is a long-running test."
Since they fail sometimes, like once in 25 runs, I am wondering if jest.setTimeout will solve the issue. I was able to fail them locally by setting jest.setTimeout(10), but I am not sure how to debug this even more, or whether something else could be an issue here aside from a small timeout (default 5000). I would understand if 1/25 or a few fails, or if all other suits fail, but only a single file with all tests within that file is failing. And it is always the same file, never some other file for this reason ever.
Additional information, locally, that single file runs in less than a 1000ms connected to the staging database which is huge compared to the dockerized that has only a few files at the time of running
For anyone who sees this, I was able to solve this by adding the --maxWorkers=2 flag to the test command in my CircleCI config. See here for details: https://support.circleci.com/hc/en-us/articles/360005442714-Your-test-tools-are-smart-and-that-s-a-problem-Learn-about-when-optimization-goes-wrong-
Naman's answer is perfect! I couldn't believe it but it really solved my problem. Just to be extra clear on how to do it:
I change the test script from my package.json from jest to jest --maxWorkers=2. Then I pushed and it did solve my error.
I am currently following a GraphQL Tutorial and am on the "Add a Database" section explaining how to set up Prisma with GraphQL.
I finished adding the information in the prisma.yml file, installed prisma, ran prisma deploy and followed the steps, but every time I run prisma info, prisma token, or prisma deploy again, I keep getting the same error:
TypeError: url_1.URL is not a constructor
I have been trying to look up solutions to the error. I tried updating node and npm, downloading docker but nothing seems to be making any difference.
Help would be greatly appreciated.
You are running into this issue.
Basically, this is a known issue with node 6.x.
Please update the node version to fix this issue and track the progress of above issue in case you want to continue to use node 6.x.
I am trying to get CircleCI to work with my electron app but I can't understand how to stop the timeout error.
You can look at the app here: https://github.com/sauravyash/OutFlux
It fails on the npm test stage of the build with:
> outflux#1.0.0 test /home/ubuntu/OutFlux
> electron .
Xlib: extension "RANDR" missing on display ":99".
Xlib: extension "RANDR" missing on display ":99".
command ((npm :test)) took more than 10 minutes since last output
I'm new to the whole idea of CI so bear with me if the answer is obvious.
In case anyone sees this, you must understand that running electron by itself isnt testing anything, which is the point of CI. You should use something like Spectron to test if your app is successful in headless testing (testing without a real display).
https://github.com/electron/spectron
I'm following the getting started steps to setup fabric environment on my mac, from the steps mentioned here :
When I'm trying to start my network using the ./network_setup.sh up script, I'm getting the following grpc timeout error (as shown in the images attached
anyone has any idea what am I missing ?
So I got it working. The issue was something might have updated the .proto files. I had to run the following command from the fabric directory to generate/update the respective pb.go files.
make protos