- Notifications
You must be signed in to change notification settings - Fork 1.2k
fix python 3.x str.decode exception #877
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
Conversation
Since this is a community submitted pull request, a Jenkins build has not been kicked off automatically. Can an Elastic organization member please verify the contents of this patch and then kick off a build manually? |
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.
Can you put the try
inside the if
statement?
if body: try: body = body.decode('utf-8', 'ignore') except AttributeError: pass
This way we avoid the try statement if no body.
Thanks for the patch
Also could you please sign the CLA? I can't merge until that's signed. Thanks |
Moving the change inside the if statement sounds good. Also, I signed the CLA. Thank You, |
I will push the requested change in the morning. Mike |
Change has been pushed |
jenkins test this please |
@mmarshallgh when you signed the CLA did you sign it using an email address associated to your GH account? The CLA check is still failing. |
@fxdgear I have now signed it using the private github issued email. That didn't work, so i uncheck "keep email address private" and signed it again. Please check to see if it took. Thank You, |
@mmarshallgh still not showing up. I'll look into the CLA checker in a bit, have to run some errands now. But if you look at the "PR status" at the bottom of this page where it shows the "Clients-ci" green check box and the build has finished. You'll see a red x where the CLA check is. Maybe something is going on with the CLA checker and I'll investigate. |
Where do we stand on troubleshooting the CLA? I have multiple signed copies in my email box matching the email used on the github account. |
@mmarshallgh I'm not sure how this is not working, but I don't see any signatures related to your GH username. If you want I can look up by email? see what email addresses you've signed with? when you signed the form did you add your GH username as well? |
please lookup michael_marshall@neimanmarcus.com Thank you, Mike |
@mmarshallgh ahh hah I found you. the problem is the GH username in our system is Could you please re-sign using the correct GH name |
Hello Michael, sorry for the troubles with the CLA. The reason why the CLA checker doesn't want to approve the commits seems to be an incorrect e-mail address used in the Git commit — have a look at the raw patch, it has To fix the commit, just set your email address for Git, and then update the commit:
and force push the branch here so it's getting processed. |
I just spoke to the author of the CLA checker and he said that the email that you use for your If you look at the patch being applied to the repo, you can see that your email is:
But when you signed the CLA your email is There is a transposition of the If your email truly is ALSO I would recommend updating your git config to have the correct email address to avoid situations like this in the future. |
…py into fixbasedecode Amend author email address
Hi @mmarshallgh, we have found your signature in our records, but it seems like you have signed with a different e-mail than the one used in yout Git commit. Can you please add both of these e-mails into your Github profile (they can be hidden), so we can match your e-mails to your Github profile? |
What is the next step to get the change merged? |
all done! :) Thanks for your patience and the patch! |
Python 3.x doesn't support str.decode() causing code to fail with AttributeError exception. This code change allows the python module to continue to work with older 2.x python while being 3.x friendly as well. Any alternate suggestions?