-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Add error handling to composer GCF trigger sample #732
Conversation
}; | ||
} | ||
|
||
test.cb.serial(`Does nothing for deleted files`, (t) => { |
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 we remove serial
?
const sample = getSample(); | ||
sample.mocks.bodyJson.error = expectedMsg; | ||
|
||
sample.program.triggerDag(event, (err, message) => { |
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.
Should we switch to promises at some point? (In a separate PR, of course.)
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.
I didn't realize we could return promises with GCF. Yeah, that'd be ideal.
Thanks for making this. I think we should consider doing retry on failure in the future as well (maybe someone else can PR that?) We've had issues with execution_date timestamp collisions. |
Addressed feedback from bug 111401746.
Please review @TrevorEdwards