-
Notifications
You must be signed in to change notification settings - Fork 9
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
MaxListenersExceededWarning #771
Comments
hmm, It seems like beforestart hook is not handling the timeout value defined in configs. I'm going to take a look at that. |
hey @kaaax0815, upgrade corde's version to 4.1.1 😊 |
@lucasgmagalhaes after updating corde throws this error: |
Fixed in |
Log in
|
Can you try to delete node_modes and reinstall it? |
As I said I already did that |
Ok, Sorry |
Dont have to say sorry Do you maybe know why this happens or is it maybe me bot architectur |
@kaaax0815, corde was expecting the property |
The
|
@kaaax0815 looks like that the problem is in yours commands.
|
Thats also possible because you didnt send every env var. because if i run my bot without corde the command works fine |
This is the log from Github Actions (it has more infos, but is weirdly censored)
|
Describe the bug
I get an error when running my tests
To Reproduce
Steps to reproduce the behavior:
Expected behavior
every test case should succeed
Desktop (please complete the following information):
Additional context
Log: ```
(node:1584) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 12 unhandledRejection listeners added to [process]. Use emitter.setMaxListeners()
to increase limit
(Use
node --trace-warnings ...
to show where the warning was created)Test Files: 1 failed. 1 total
Tests: 18 failed. 18 total
Time: 22.75s
The text was updated successfully, but these errors were encountered: