-
Updated
Apr 3, 2022 - Python
sqs
Here are 684 public repositories matching this topic...
-
Updated
Aug 3, 2021 - Go
-
Updated
Mar 29, 2022 - TypeScript
-
Updated
Mar 31, 2022 - TypeScript
-
Updated
Apr 3, 2022 - Go
-
Updated
Mar 29, 2022 - JavaScript
-
Updated
Aug 25, 2021 - Python
-
Updated
Mar 19, 2022 - C#
In what area(s)?
/area components (kafka pub/sub)
Describe the feature
The current kafka pub/sub component targets just the minimum interfaces to publish and subscribe. We need an enhancement to the kafka component to support "ResetOffets". This means, we need to be able to invoke an API call to the dapr sidecar to "reset" the current offset to a previous value so that messages can b
-
Updated
Mar 30, 2022 - PHP
-
Updated
Feb 3, 2021 - Dockerfile
-
Updated
Nov 7, 2021 - Perl
Describe the bug
Remove the warning moving await from mocha.opts.
DeprecationWarning: Configuration via mocha.opts is DEPRECATED and will be removed from a future version of Mocha. Use RC files or package.json instead.
-
Updated
Apr 1, 2022 - TypeScript
-
Updated
Feb 1, 2022 - Java
We have often see developer telling us the problems going on with WPA and then the first way to debug the issue is by going through WPA kubernetes logs for the queue to find what is going on. We should logs events for all the important thing that goes on with the WPA object.
Reasons:
- Easy to debug.
- Developer who does have access to wpa logs but has access to their WPA object can tro
-
Updated
Aug 6, 2020 - Python
-
Updated
Nov 26, 2021 - Ruby
-
Updated
Jan 12, 2022 - Ruby
-
Updated
Mar 9, 2022 - Java
-
Updated
Jan 2, 2022 - CSS
-
Updated
Jan 18, 2021 - Python
Improve this page
Add a description, image, and links to the sqs topic page so that developers can more easily learn about it.
Add this topic to your repo
To associate your repository with the sqs topic, visit your repo's landing page and select "manage topics."
Is your feature request related to a problem? Please describe.
From the end of May, .NET 5.0 goes out of support, which forms a good trigger for us to move the samples to .NET 6.0.
https://devblogs.microsoft.com/dotnet/dotnet-5-end-of-support-update/
Describe the solution you'd like
The simplest solution here is to just target .NET 6.0 and rebuild. We don't want to bring over .NET