-
Notifications
You must be signed in to change notification settings - Fork 66
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Credo agent failing to start #888
Comments
I believe that the Credo agent is actually starting, however it is taking longer to start in some instances than the 30 second timer we have set waiting to get a status. This is manifesting now because we no longer run tests if we don't get a status on an agent. In the past it would carry on and we wouldn't notice. I think we need to extend the checking of status to 60 seconds. |
I may be mistaken and the credo agent is actually not starting. I am getting a Require ESM error when building locally now. A bad library version update maybe. |
Any luck resolving this? When I run it locally, no logs are written, so I can't see anything to debug. AFAIK, the build works fine. |
Not yet. I'm working through the package.json trying to pin modules to previous versions but not luck. This is the error.
So something has changed in Tsed/common or logger. |
After working with the main Ts.ED maintainers, they have fixed a v6 peer dependancy and a v7 peer dependancy. This has fixed our immediate problem. However, I am still working with them to move the credo backchannel to Ts.ED v7 permanently so this will be less likely to happen again. So if we can get to a working v7 I will still do a PR for that. I'll only spend a few more hours on that and if we can't sort it will revert to v6 as is. |
Awesome stuff — well done!! |
In the most recent test runs, the Credo agent is failing to start, resulting in all tests failing.
The text was updated successfully, but these errors were encountered: