Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Failed plugin github:gh: string indices must be integers! #6

Open
mvidner opened this issue Apr 15, 2013 · 3 comments
Open

Failed plugin github:gh: string indices must be integers! #6

mvidner opened this issue Apr 15, 2013 · 3 comments

Comments

@mvidner
Copy link
Contributor

mvidner commented Apr 15, 2013

I got this message ... until I commented on an issue here :) Now I have "-1 issues commented".

I think it would be easier to debug the problem myself if exception backtraces were enabled.
@mvidner
Copy link
Contributor Author

mvidner commented Apr 15, 2013

Hmm, after fixing the time frame to look in the past, it again errors out, not considering any of the commits and pull requests I touched during Hackweek in https://github.com/yast/ycp-killer/

@mvidner mvidner mentioned this issue Apr 15, 2013
Closed
aspiers pushed a commit to aspiers/rapport that referenced this issue May 20, 2013
provide more information when a plugin barfs an exception
33c2386 
This is still not very useful because the stack trace is in the
context of the re-raise by futures.Future, not within the thread
where it was originally raised.  I'm not sure whether it's possible
to fix this without using a different thread handling mechanism.

See also issue saschpe#6.
@aspiers aspiers mentioned this issue May 21, 2013
Closed
@aspiers
Copy link

aspiers commented May 21, 2013

I also see this, and I tried to enable backtraces (see #20) but I'm not sure there is an easy way to provide helpful debug. Filed as #23.

@aspiers
Copy link

aspiers commented Jun 18, 2014

The github plugin changed quite a bit since this was reported, so I'm not sure it's an issue any longer. Can we resolve it? If we see it again, we can reopen, this time with useful debug since #23 is now resolved.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@aspiers @mvidner