-
Notifications
You must be signed in to change notification settings - Fork 46
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
Prevent GSSError/_display_status() infinite recursion #112
Prevent GSSError/_display_status() infinite recursion #112
Conversation
(Pulled some of the prep commits out of #109) |
I'm not a fan of assert() for flow control. Some flags (e.g. |
Christian Heimes <notifications@github.com> writes:
I'm not a fan of assert() for flow control. Some flags (e.g. ```-O```)
remove assert statements.
Understood. Do you have a recommendation instead? My original thought
was to raise an exception manually, and I only switched to
assert() because the assertion failure exception looked closest to the
kind of problem that was occurring.
|
Any other exception will do. I like |
4dc66ab
to
2068ffe
Compare
Switched to |
2068ffe
to
08efae8
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
small change, but otherwise looks good
gssapi/raw/misc.pyx
Outdated
# but obviates infinite recursion into stack exhaustion. The | ||
# exception raised here is handled by get_all_statuses(), which prints | ||
# the code. | ||
raise ValueError("gss_display_status call returned failure.") |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
please attach the error codes from gss_display_status
into this message
I was unable to reproduce the problem, but this should prevent the issue. Resolves: pythongssapi#111
08efae8
to
b7e6c6c
Compare
Updated to include |
I was unable to reproduce the problem, but this should prevent the issue (which is #111).