-
Notifications
You must be signed in to change notification settings - Fork 37
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
Backtrace from API query; post 81600 has no username #277
Comments
I managed to pare it down to a simpler test case which triggers on post 81600.
I was speculating that the API filter expression in Halflife was causing this, but I get the traceback even without the filter. |
Seems like MS is complaining about Line 7 of names: post.flag_logs.select { |f| f.success && f.is_auto }.map { |f| f.user.username }, So it looks like |
bug buggity bug. Dunno why that doesn't have a user attached. |
Another instance with the same symptom.
|
Using the repro script above, I isolated the offending sample: 62559 I don't really care about the user names so I suppose I could perhaps tweak the API query filter to not request this information as a workaround. |
E.g. /flagging/users/2/logs returns a backtrace, too; I guess there are user IDs which used to exist but which are now deleted? |
There certainly are some of those. Depending on what traceback you're getting, it may just be a 404. |
I have a code path from Halflife which crashes every time.
The traceback is a humongous pile of HTML which I am attaching here.
The request is
The beef of the error message seems to be in
The text was updated successfully, but these errors were encountered: