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

Check for cancellation after triggering function #852

Merged
merged 2 commits into from
Aug 22, 2023

Conversation

MikeNicholls
Copy link
Contributor

Fixes #851 by throwing an exception if cancellation is requested, preventing automatic checkpointing from occurring.

Copy link
Member

@ealsur ealsur left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please add tests for the scenario if possible

@MikeNicholls
Copy link
Contributor Author

@microsoft-github-policy-service agree company="Smudge"

@MikeNicholls
Copy link
Contributor Author

@ealsur I've added an end-to-end test which covers this scenario.

@ealsur
Copy link
Member

ealsur commented Aug 22, 2023

@brettsam Do you know how can we get the CI tests to run for external contributors that have no write permissions?

@ealsur
Copy link
Member

ealsur commented Aug 22, 2023

CI in this repo is not working for external forks, we'll try to test the fork manually

@ealsur
Copy link
Member

ealsur commented Aug 22, 2023

Manually running the test in the fork passes:

image

@ealsur ealsur merged commit b12d0c9 into Azure:dev Aug 22, 2023
3 of 7 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Cosmos DB triggered function advances checkpoint after cancellation
3 participants