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: Support for retrying to deliver SQS message #304

Merged
merged 4 commits into from
Aug 29, 2024

Conversation

fredrjoh
Copy link
Contributor

@fredrjoh fredrjoh commented Aug 23, 2024

@fredrjoh fredrjoh changed the title INVO-636: feat: Support for retrying to deliver SQS message feat: Support for retrying to deliver SQS message Aug 23, 2024
@fredrjoh
Copy link
Contributor Author

@naile @danhemma feel free to have a look at this one, I will also add some unit tests to verify that it calls the correct functions at certain scenarios

@fredrjoh fredrjoh force-pushed the support-for-keeping-or-deleting-message branch 3 times, most recently from d98c89f to 64a3b50 Compare August 26, 2024 10:53
@fredrjoh fredrjoh marked this pull request as ready for review August 26, 2024 10:57
@fredrjoh fredrjoh requested a review from a team as a code owner August 26, 2024 10:57
@fredrjoh fredrjoh force-pushed the support-for-keeping-or-deleting-message branch 2 times, most recently from 16c6a5d to a3b40a3 Compare August 26, 2024 13:03
Copy link
Contributor

@naile naile left a comment

Choose a reason for hiding this comment

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

Looks good. Suggestion: make the retry policy a function instead returning visibility timeout. That way a consumer can have their own backoff logic by changing that function. Ie if someone wants to do less or more aggressive backoff like linear or exponential. The function can also take exception as parameter allowing the consumer to change the logic depending on the error.

src/queue/QueueSubjectListener.ts Outdated Show resolved Hide resolved
@fredrjoh fredrjoh force-pushed the support-for-keeping-or-deleting-message branch from a3b40a3 to 909c3e6 Compare August 28, 2024 12:46
@fredrjoh fredrjoh force-pushed the support-for-keeping-or-deleting-message branch from 909c3e6 to 5a4bbb0 Compare August 28, 2024 13:07
@fredrjoh fredrjoh requested a review from naile August 29, 2024 08:46
@fredrjoh fredrjoh merged commit 08bd12a into master Aug 29, 2024
1 check passed
@fredrjoh fredrjoh deleted the support-for-keeping-or-deleting-message branch August 29, 2024 11:18
tibbercom-builduser pushed a commit that referenced this pull request Aug 29, 2024
# [6.2.0](v6.1.4...v6.2.0) (2024-08-29)

### Features

* Support for retrying to deliver SQS message ([#304](#304)) ([08bd12a](08bd12a))
@tibbercom-builduser
Copy link

🎉 This PR is included in version 6.2.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

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.

5 participants