-
Notifications
You must be signed in to change notification settings - Fork 184
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
Maximum Call stack size reached on Shim-Array #241
Comments
same here. I rolled back to v5.0.0 |
Seeing same thing here for me:
I could not get it to work fixed a version 5.0.0 either. Had to stop using it altogether as it interferred badly with Apollo GraphQL API. This looks to be using Monkey patching which is asking for trouble. |
Committed a tentative fix on master, please try it and let me know if it fixes it. |
Just wanted to use collections for the first time. The algorithms implemented looked decent, but to be honest, I am quite disappointed that importing e.g. In general I find shimming of global objects like overwriting I do not see a need for SortedMap for example to shim anything. As shimming seems to be deeply embedded, the risk of it breaking existing code at a fundamental and global level is just too high. |
We've just hit this too on Note: We aren't using EDIT: @marchant For the sake of this issue and your request, I tried your fix on |
Dears, 5.1.12 is installed but doesn't contain the the error is on the |
@marchant - Is it possible to get this fix pushed out as a release ? In the homebridge community we have had numerous users of our packages impacted by this issue due to the usage of mqtt. |
this fix doesn't fix the issue :( i've tried it |
@NebzHB - When I was testing, I applied the fix to all the plugins leveraging collections and that appeared to resolve the issue. Did you try that |
not to all of them, i'll try |
well... homebridge-camera-ffmpeg seems to still use it (^4.2.8) but doesn't crash here... so with only changing homebridge-alexa, it doesn't solve. but push to release anyway, we'll see ;) |
I tried to reproduce the issue using minimal code. When I import (emulation code) version 5.1.12 once, it works fine. However, I import version 5.1.12 twice, then infinity recursive call happens. If import order is 5.1.12 -> master, then it works fine. If import order is master -> 5.1.12, then infinity recursive call happens. If import master twice, then it works fine. NOTE: master is 85f00f8 So in order to fix the issue, all of collections library need to update. After the current master including 85f00f8 fix would be released, and then all collections.js users would update the library, I guess that the issue would be fixed. |
I just published the latest master as version 5.1.13. |
Main project has dependent on collections/shim-array and one of its npm package also depends upon collections/shim-array.
And whenever in the code we imported(required) both packages, node js returning Maximum call stack size.
Same scenario is not happening with any other such inter dependency packs like mongoose, geolib, etc.
The text was updated successfully, but these errors were encountered: