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

Pull development into main ahead of tagged release #62

Merged
merged 48 commits into from
Mar 14, 2023
Merged

Conversation

nmassey001
Copy link
Contributor

No description provided.

nmassey001 and others added 30 commits January 25, 2023 14:42
This is done so as to allow a general/default retry delays tuple to be
specified.
The callback wrapper now implements the transaction-level retries made
possible by the refactoring of Retries outside of the PathDetails
object. Some things to note:
 - All messages that fail in the accepted number of ways denoted in the
   try-catch block in teh callback wrapper will be retried. We may in
   the future want to expand this to all Exceptions and expand what
   throws errors within the callback so it is applied more widely.
 - Only the final reason is stored alonside the FailedFile record in the
   monitoring database, which can be either a File-level Retry Reason or
   a Transaction-level Retry Reason. We may in the future want to store
   more than one reason if they exist but this will do for now.
 - All retries are reset upon successful completion of a callback, both
   FRs and TRs
@nmassey001 nmassey001 merged commit 88b8618 into main Mar 14, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants