-
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
NoMethodError (undefined method `find' for #<String:0x00000001198ffa60>) #20
Comments
Thanks for the report. This error is a mistery for me, since Exception#backtrace_locations is supposed to return an array. I need to understand why the original backtrace is a string. Could you provide me the type of the original exception please ? Is it possible that the method |
I honestly wish I knew what the original exception was! I throw a lot of ActiveResource::ClientError and ActiveResource::ServerError, but that's just a statistic. I was also doing work on my local machine and was connected to my production DB and that connection is always flaky, so I get a lot of ActiveRecord connection errors. But those are just guesses. I did try to get a breakpoint into your code to debug it but wasn't successful. I did see that that method sometimes returns |
I have added a fallback to the old way in this case and some logging. Can you try to reproduce with the following version in your Gemfile please ? gem "rorvswild", git: "https://github.com/BaseSecrete/rorvswild.git", ref: "42b66153ad0db9d7ab849e073604cec660f4d191" If the error happens again, something should be printed by the following command |
Alright. I'm a bit apprehensive about running special versions of the code but for a little while I'll try it. I was able to reproduce the error twice in a row but then it stopped happening... |
Do you have more details about the origin exception where backtrace_locations returns a string ? |
@alexisbernard I do not and I do not know if I ever will again. If and when I do, I will surely let you know |
The text was updated successfully, but these errors were encountered: