Skip to content

Issues: Particular/NServiceBus.AmazonSQS

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.

Sign up for GitHub

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

20 Open 183 Closed
20 Open 183 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Amazon SQS transport doesn't support binary serialization Bug
#2630 opened Nov 19, 2024 by lailabougria
Add support for “desired state” deployment styles (e.g., AWS CDK or Terraform) candidate-for-next-release Feature
#2597 opened Oct 24, 2024 by mauroservienti
DoNotWrapOutgoingMessages set to true cannot be used with NServiceBus.Metrics.ServiceControl Bug Triaged
#2520 opened Jul 15, 2024 by tmasternak
1
2
Enable Cloudflare R2 as a storage alternative compatible with S3 API candidate-for-next-release Improvement
#2498 opened May 13, 2024 by NChaganlal
Transport test to verify that the transport can be restarted fails on the build server Improvement
#2425 opened Feb 21, 2024 by andreasohlund
1
Cross-account communication in SQS transport
#2365 opened Nov 27, 2023 by mauroservienti
Preserve native message attributes when message is retried via ServiceControl Improvement
#2356 opened Nov 14, 2023 by SzymonPobiega
1
Allow dispatcher to batch multiple isolated dispatches per destination Improvement
#2248 opened Aug 9, 2023 by danielmarbach
Consider using "ApproximateReceiveCount" attribute to compute number of immediate processing failures for ErrorContext candidate-for-next-release
#2163 opened May 10, 2023 by jdaigle
"Unrestricted delayed delivery" should be optional candidate-for-next-release Improvement
#2161 opened May 10, 2023 by jdaigle
1
Propagate NServiceBus headers to SQS message attribute candidate-for-next-release
#1922 opened Feb 8, 2023 by jpalac
3
Simplify getting logs into AWS CloudWatch candidate-for-next-release Improvement
#1699 opened Nov 4, 2022 by WilliamBZA
2
Enable turning on CloudWatch message delivery failures via TransportConfiguration api candidate-for-next-release Improvement
#1676 opened Oct 24, 2022 by tmasternak
The built-in delayed delivery mechanism (based on FIFO queues) might impact costs candidate-for-next-release Improvement
#1207 opened Jan 12, 2022 by mauroservienti
Generate the list of required CLI commands to deploy the infrastructure at build time candidate-for-next-release
#1176 opened Dec 14, 2021 by mauroservienti
3
Evaluate if is it worth automatically extending the message visibility timeout (as an opt-in setting) candidate-for-next-release
#1003 opened Sep 16, 2021 by mauroservienti
1
Evaluate if is it worth exposing the message visibility timeout setting candidate-for-next-release
#1002 opened Sep 16, 2021 by mauroservienti
3
Use CloudWatch Events to manage delayed messages
#244 opened Sep 27, 2018 by mauroservienti
4
FIFO queues support candidate-for-next-release
#240 opened Aug 16, 2018 by VladimirMakaev
6
Should transport block TTBR from sending if there are other delivery constraints defined?
#211 opened Mar 23, 2018 by SeanFeldman
ProTip! Mix and match filters to narrow down what you’re looking for.