Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Cloud scheduler for Cloud Functions timezone is not set correctly #3425

Closed
saurabhshah23 opened this issue May 28, 2021 · 6 comments
Closed

Cloud scheduler for Cloud Functions timezone is not set correctly #3425

saurabhshah23 opened this issue May 28, 2021 · 6 comments
Assignees
@inlined @joehan

Comments

@saurabhshah23
Copy link

Cloud functions pubsub set with .timezone("America/New_York") not working since firebase-tools latest update.
.pubsub
.schedule('0 12 * * *')
.timeZone("America/New_York")
CI pipeline successful but the timezone for cloud-scheduler was always set to default ("Los Angelos") without any errors.

It worked only after reverting the firebase-tools version back to 9.6.1 in CI.

npm install -g firebase-tools@9.6.1
@astefer
Copy link

astefer commented May 31, 2021

Same issue. This crashed my production environment without any warning

@mikan3rd
Copy link

I had the same problem with "firebase-tools": "9.12.0"
Downgrading to "firebase-tools": "9.11.0" brought it back.

@astefer
Copy link

astefer commented May 31, 2021

I think 33ff495 broke something.

@ashking
Copy link

ashking commented Jun 1, 2021

I caused a loss of close to $1000 transactions due to this issue (~70k thousand INR) on production
I regret upgrading to this version and deploying on a Friday night.

@samtstern
Copy link
Contributor

samtstern commented Jun 1, 2021 •
edited
Loading

@saurabhshah23 @mikan3rd @astefer thank you for reporting this and we are really sorry about the timing of this bug. Googlers in the US were on holiday for Friday and Monday and because this was a CLI issue rather than a backend issue it didn't page the on-call team.

We'll get a fix out ASAP. In the meantime the workaround is to downgrade to 9.11.0 and redeploy.

@ashking or anyone else who experienced a loss due to this issue please write in to Firebase support and mention this bug, we'll see what we can do.

@inlined
Copy link
Member

inlined commented Jun 1, 2021

Fixed in #3434 and released to npm

@inlined inlined closed this as completed Jun 1, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@inlined inlined

@joehan joehan

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
7 participants
@inlined @ashking @saurabhshah23 @joehan @samtstern @mikan3rd @astefer
pFad - Phonifier reborn

Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


Alternative Proxies:

Alternative Proxy

pFad Proxy

pFad v3 Proxy

pFad v4 Proxy