-
Notifications
You must be signed in to change notification settings - Fork 26
Sporadic datetime parse error #160
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
are you using the latest release? #149 |
Oh, does 0.1.2 fix this issue? |
Not sure it's fixed, but checking.... The issue you linked is for firestore, but my error is in pubsub function. |
From examining the firebase-functions-python code and commits, it doesn't seem fixed but maybe I'm missing something. Is your understanding that the issue is also fixed for pubsub functions? |
I don't know, but I'd assume though that datetime parsing is not in many places. I only saw the issue and fix passing by here on github earlier, I don't know anything else. |
@jacobg Could you confirm on the status of this? If not fixed by 0.1.2, then please let me know and I can investigate further |
Hi @exaby73 I have not seen the error since bumping to 0.1.2, but I'm not sure that's a proof because it only happened once to me in the old version. I think it occurred when the event timestamp was exactly 0 milliseconds and so the formatted string left off the sub-second part. |
Could you give me an example of a error timestamp you observed to be causing this error? Even if this is fixed, we can add tests for this |
I'm still getting this issue. It seems to happen before it gets to any of the logic in the function itself. It persists between retries. I'm on the latest version
|
I saw this across 3 of my cloud functions this morning.
Each of them Python Firebase Cloud Functions triggered via pub sub with these dependencies
|
Saw this again this morning. Here is a more complete stack trace. Appears to error before the function ever starts
|
This issue also affects Firebase Realtime DB functions such as db_fn.on_value_created (the issue is present in the db_fn _db_endpoint_handler method) |
In order to protect from this insanity I've created the following function wrapper which I apply on all my cloud functions
|
The following error occurred once on my pubsub function. It's otherwise run fine hundreds of times without any issue.
Why would that occur?
The text was updated successfully, but these errors were encountered: