-
Notifications
You must be signed in to change notification settings - Fork 49
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
UnicodeDecodeError when producing query cursors on dev_appserver #47
Comments
What worked for me was manually building a wheel for protobuf and forcing the C compilation: brew install protobuf
python3.7 -m pip wheel --wheel-dir=wheels --no-binary=protobuf --global-option="--cpp_implementation" protobuf==3.19.0 And then adding this into requirements.txt (can point at GCS with some index file):
By default protobuf falls back to a pure-python implementation which causes that error/warning. Compiled binary works fine. This workaround won't be needed once correct wheels are published for protobuf. |
Thanks for the note on your fix @sadovnychyi, I killed a lot of time trying to figure out what was corrupted in my datastore before seeing this. |
I'm getting a similar error except instead of an exception from the Python implementation I'm getting an error from libprotobuf:
The query seems to work though so maybe it's less an error than a warning? I don't really know where it's coming from because it's somewhere quite deep and a couple hours of debugging hasn't revealed anything obvious. |
Hmm, after upgrading protobuf the error message goes away, but the error in the descriptor for |
Expected Behavior
No exception is thrown.
Actual Behavior
Steps to Reproduce the Problem
Specifications
This used to produce just some log warnings on non-ARM platform – not sure yet whether it's due to ARM or just some dependency being newer due to a new system (all python deps are fixed and are the same, maybe they still depend on system wide protobuf and that one got bumped?)
golang/appengine#136 -- maybe related?
The text was updated successfully, but these errors were encountered: