[Core] Fix overriding of next resync status when cancelled due to scheduled resync #1035
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
What - Fix overriding of next resync status when cancelled due to scheduled resync
Why - When setting up a low resync interval and the resync still runs, the new resync sends an abort signal to the existing integration causing it to stop, which then the integration updates the integration as completed, while the integration is actually running a resync, this causes incorrect status in the UI. In the case of having kafka configured it can also cause the integration to detect new resync.
How - Handled
asyncio.CancelledError
and skips updating the resync status.Type of change
Please leave one option from the following and delete the rest:
All tests should be run against the port production environment(using a testing org).
Core testing checklist
Integration testing checklist
examples
folder in the integration directory.Preflight checklist
Screenshots
Include screenshots from your environment showing how the resources of the integration will look.
API Documentation
Provide links to the API documentation used for this integration.