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.

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

feat: add a stack_trace field to the Error messages specifying where the error occured feat: add call_log_level field to Execution messages doc: clarify requirement to escape strings within JSON arguments #220

Merged
merged 2 commits into from Nov 15, 2021

Conversation

gcf-owl-bot[bot]
Copy link
Contributor

@gcf-owl-bot gcf-owl-bot bot commented Nov 5, 2021

  • Regenerate this pull request now.

Update the Execution proto with stack_trace field which is populated on output if an error occurs, and the call_log_level field can be specified on input to request that function calls and/or errors for the given execution be logged to Cloud Logging.

PiperOrigin-RevId: 407842136

Source-Link: googleapis/googleapis@cd48c16

Source-Link: https://github.com/googleapis/googleapis-gen/commit/eefbcd70342adee1df52e4c595243da751e5b6a9
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiZWVmYmNkNzAzNDJhZGVlMWRmNTJlNGM1OTUyNDNkYTc1MWU1YjZhOSJ9

…the error occured feat: add call_log_level field to Execution messages doc: clarify requirement to escape strings within JSON arguments

Update the Execution proto with stack_trace field which is populated on output if an error occurs, and the call_log_level field can be specified on input to request that function calls and/or errors for the given execution be logged to Cloud Logging.

PiperOrigin-RevId: 407842136

Source-Link: googleapis/googleapis@cd48c16

Source-Link: https://github.com/googleapis/googleapis-gen/commit/eefbcd70342adee1df52e4c595243da751e5b6a9
Copy-Tag: eyJwIjoiLmdpdGh1Yi8uT3dsQm90LnlhbWwiLCJoIjoiZWVmYmNkNzAzNDJhZGVlMWRmNTJlNGM1OTUyNDNkYTc1MWU1YjZhOSJ9
@gcf-owl-bot gcf-owl-bot bot requested a review from as a code owner Nov 5, 2021
@google-cla google-cla bot added the cla: yes label Nov 5, 2021
@trusted-contributions-gcf trusted-contributions-gcf bot added kokoro:force-run owlbot:run labels Nov 5, 2021
@product-auto-label product-auto-label bot added the api: workflowexecutions label Nov 5, 2021
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run label Nov 5, 2021
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run label Nov 5, 2021
@trusted-contributions-gcf trusted-contributions-gcf bot added kokoro:force-run owlbot:run labels Nov 5, 2021
@gcf-owl-bot gcf-owl-bot bot removed the owlbot:run label Nov 5, 2021
@yoshi-kokoro yoshi-kokoro removed the kokoro:force-run label Nov 5, 2021
@lesv lesv added the automerge label Nov 6, 2021
@gcf-merge-on-green
Copy link

@gcf-merge-on-green gcf-merge-on-green bot commented Nov 6, 2021

Merge-on-green attempted to merge your PR for 6 hours, but it was not mergeable because either one of your required status checks failed, one of your required reviews was not approved, or there is a do not merge label. Learn more about your required status checks here: https://help.github.com/en/github/administering-a-repository/enabling-required-status-checks. You can remove and reapply the label to re-run the bot.

@gcf-merge-on-green gcf-merge-on-green bot removed the automerge label Nov 6, 2021
@chanseokoh chanseokoh added the automerge label Nov 15, 2021
@gcf-merge-on-green gcf-merge-on-green bot merged commit 8b4e352 into main Nov 15, 2021
18 checks passed
@gcf-merge-on-green gcf-merge-on-green bot deleted the owl-bot-0e7921dd-9418-4e20-b819-77cb4c6d5f9d branch Nov 15, 2021
@gcf-merge-on-green gcf-merge-on-green bot removed the automerge label Nov 15, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
api: workflowexecutions cla: yes owl-bot-copy
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants