-
Notifications
You must be signed in to change notification settings - Fork 28
Event Time parse issue in firestore_fn.py #95
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
Comments
Same issue for me, just I started with the sample
versions: I did a short research and the class implements the generic CloudEvent. Current version from the spec is v1.0.2 says the Timestamp format is RFC 3339 - it should match with |
Is there a workaround for this right now? I can't run test my firestore cloud functions at all without running into this error. |
Same problem here. Yesterday it worked, when I deployed my python function for the first time on functions emulator. After that I keep getting this error. |
We are having the same issue in a live environment when the milliseconds happen to be 0. It looks like on line 65 of cloudevents.http.event.py it is trying to add the time attribute to the event using isoformat which is dropping off the milliseconds. Then in firebase_functions.pubsub_fn.py on line 108 it is trying to parse that time assuming that there are milliseconds and it is throwing the same error everyone else is seeing.
|
Release exist with this fix? I'm still have this issue sometimes |
I'm following the start guide at: https://firebase.google.com/docs/functions/get-started?gen=2nd
At step 7, when testing the functions using the emulator, the
addmessage
function works fine, and triggers themakeuppercase
function appropriately, but themakeuppercase
call fails with an error related to event datetime:FWIW, I was able to hack around it locally by modifying firestore_fn.py to use dateutil.parser instead and changing line 114:
Line 114:
Not sure if this would be the most appropriate fix for the repo, or if there's some other underlying root cause that should be addressed.
The text was updated successfully, but these errors were encountered: