-
Notifications
You must be signed in to change notification settings - Fork 79
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
bug: stack level too deep (with repro) #91
Comments
thank you! I'll take a look next week. |
argh I still can't repro :(
Can you try it with I also don't get the |
Hmm it looks like my reproduction repo was not complete; I didn't check it by deleting and re-cloning it, and I should have. Sorry. :/ I have done that now, and I am successfully getting the error.
|
argh, still doesn't repro for me (though I can't use you git gems, I need to rebundle) :( If you're willing to get your hands dirty, there is some more debugging we can do:
|
I have done as you suggested above. It has been running for a few minutes now and I am kind of worried that my computer will explode. The logfile is already several gigabytes. I'll post here when it completes or with the remnants if it refuses to complete. |
|
@xaviershay the top 90001 lines of the 3.9Gb file that it created before I killed the process are up at https://www.dropbox.com/s/r3vl9ndoo63hcq5/short_log.log?dl=0 Please let me know if you need more of it and how you prefer that I send it. :) |
Can I get the bottom of the file instead? Once it starts overflowing - that will be the interesting part. Thank you! |
|
Here is the rest https://www.dropbox.com/s/woxmpwznm5sntqn/tail_short_log.log?dl=0 |
I don't know what the problem was but we changed a whole bunch of things and now the problem no longer happens. |
I finally made a redacted version of the code that is showing this error. It is at https://github.com/compwron/stacklevel_cane_fail
This issue was previously in #90
The text was updated successfully, but these errors were encountered: