Ecosyste.ms: Issues
An open API service for providing issue and pull request metadata for open source projects.
GitHub / rebus-org/rebus.azureservicebus issues and pull requests
#49 - Deferring a message onto another input queue using azure service bus
Issue -
State: closed - Opened by mclausen about 5 years ago
- 3 comments
#49 - Deferring a message onto another input queue using azure service bus
Issue -
State: closed - Opened by mclausen about 5 years ago
- 3 comments
#48 - Avoid potential async deadlock in GetTopicClient
Pull Request -
State: closed - Opened by jr01 about 5 years ago
- 2 comments
#48 - Avoid potential async deadlock in GetTopicClient
Pull Request -
State: closed - Opened by jr01 about 5 years ago
- 2 comments
#47 - Error counter
Issue -
State: closed - Opened by MarcoGix about 5 years ago
- 1 comment
#47 - Error counter
Issue -
State: closed - Opened by MarcoGix about 5 years ago
- 1 comment
#46 - Make sure "renewal peek lock" task is stopped at the right time.
Pull Request -
State: closed - Opened by jr01 about 5 years ago
- 1 comment
#46 - Make sure "renewal peek lock" task is stopped at the right time.
Pull Request -
State: closed - Opened by jr01 about 5 years ago
- 1 comment
#45 - EnsureQueue/Topic/Subscription exist exception handling can be improved
Issue -
State: closed - Opened by dariogriffo about 5 years ago
- 3 comments
Labels: question
#45 - EnsureQueue/Topic/Subscription exist exception handling can be improved
Issue -
State: closed - Opened by dariogriffo about 5 years ago
- 3 comments
Labels: question
#44 - EnsureTopicExists and GetOrCreateSubscription implementation could be improved
Issue -
State: closed - Opened by sabbadino about 5 years ago
- 1 comment
#44 - EnsureTopicExists and GetOrCreateSubscription implementation could be improved
Issue -
State: closed - Opened by sabbadino about 5 years ago
- 1 comment
#43 - Configure max delivery count of queues
Issue -
State: closed - Opened by mookid8000 over 5 years ago
- 1 comment
Labels: bug
#43 - Configure max delivery count of queues
Issue -
State: closed - Opened by mookid8000 over 5 years ago
- 1 comment
Labels: bug
#42 - The "renewal peek lock" task stops before actually terminating the handler, causing another thread to process the message again in another thread and "invalid lock toke / message already removed" errors in the original one.
Issue -
State: closed - Opened by Rzpeg over 5 years ago
- 1 comment
#42 - The "renewal peek lock" task stops before actually terminating the handler, causing another thread to process the message again in another thread and "invalid lock toke / message already removed" errors in the original one.
Issue -
State: closed - Opened by Rzpeg over 5 years ago
- 1 comment
#41 - Add support for Session queues
Issue -
State: closed - Opened by tinlong over 5 years ago
- 2 comments
Labels: idea
#41 - Add support for Session queues
Issue -
State: closed - Opened by tinlong over 5 years ago
- 2 comments
Labels: idea
#40 - Stop the RenewPeekLock task after `Could not renew lock` message
Issue -
State: closed - Opened by jr01 over 5 years ago
- 5 comments
Labels: bug
#40 - Stop the RenewPeekLock task after `Could not renew lock` message
Issue -
State: closed - Opened by jr01 over 5 years ago
- 5 comments
Labels: bug
#39 - Topic and subscription naming standard
Issue -
State: closed - Opened by sabbadino over 5 years ago
- 8 comments
#39 - Topic and subscription naming standard
Issue -
State: closed - Opened by sabbadino over 5 years ago
- 8 comments
#38 - messages moved from azure subscription to azure queue before being dispatched to code ?
Issue -
State: closed - Opened by sabbadino over 5 years ago
- 5 comments
#38 - messages moved from azure subscription to azure queue before being dispatched to code ?
Issue -
State: closed - Opened by sabbadino over 5 years ago
- 5 comments
#37 - Support managed identities
Issue -
State: closed - Opened by mookid8000 over 5 years ago
- 5 comments
Labels: enhancement, help wanted
#37 - Support managed identities
Issue -
State: closed - Opened by mookid8000 over 5 years ago
- 5 comments
Labels: enhancement, help wanted
#36 - Topics are only created upon subscriptions
Issue -
State: closed - Opened by mikanyg almost 6 years ago
- 11 comments
Labels: enhancement
#36 - Topics are only created upon subscriptions
Issue -
State: closed - Opened by mikanyg almost 6 years ago
- 11 comments
Labels: enhancement
#35 - Error header exceeding 65K
Issue -
State: closed - Opened by jr01 almost 6 years ago
- 4 comments
#35 - Error header exceeding 65K
Issue -
State: closed - Opened by jr01 almost 6 years ago
- 4 comments
#34 - Added transport setting for overriding the Receive OperationTimeout
Pull Request -
State: closed - Opened by jr01 almost 6 years ago
- 1 comment
#34 - Added transport setting for overriding the Receive OperationTimeout
Pull Request -
State: closed - Opened by jr01 almost 6 years ago
- 1 comment
#33 - OperationTimeout is not parsed from connectionstring by the new Microsoft.Azure.ServiceBus
Issue -
State: closed - Opened by jr01 almost 6 years ago
- 1 comment
#33 - OperationTimeout is not parsed from connectionstring by the new Microsoft.Azure.ServiceBus
Issue -
State: closed - Opened by jr01 almost 6 years ago
- 1 comment
#32 - Topic not found exception is swallowed
Issue -
State: closed - Opened by thecontrarycat almost 6 years ago
- 9 comments
Labels: question
#32 - Topic not found exception is swallowed
Issue -
State: closed - Opened by thecontrarycat almost 6 years ago
- 9 comments
Labels: question
#31 - This resolves #30, shared access policy with manage permission is always required
Pull Request -
State: closed - Opened by ehabelgindy almost 6 years ago
- 9 comments
#31 - This resolves #30, shared access policy with manage permission is always required
Pull Request -
State: closed - Opened by ehabelgindy almost 6 years ago
- 9 comments
#30 - A manage permission is required send/receive messages using existing queues
Issue -
State: closed - Opened by ehabelgindy almost 6 years ago
#30 - A manage permission is required send/receive messages using existing queues
Issue -
State: closed - Opened by ehabelgindy almost 6 years ago
#29 - Pluggable queue/topic/subscription name formatting
Pull Request -
State: closed - Opened by jr01 almost 6 years ago
- 4 comments
#29 - Pluggable queue/topic/subscription name formatting
Pull Request -
State: closed - Opened by jr01 almost 6 years ago
- 4 comments
#28 - Add '/' back as a valid topicname character in v6
Issue -
State: closed - Opened by jr01 almost 6 years ago
- 7 comments
#28 - Add '/' back as a valid topicname character in v6
Issue -
State: closed - Opened by jr01 almost 6 years ago
- 7 comments
#27 - Empty list of published message causes NullRefException in MS.Azure.SB
Issue -
State: closed - Opened by mikanyg almost 6 years ago
- 9 comments
#27 - Empty list of published message causes NullRefException in MS.Azure.SB
Issue -
State: closed - Opened by mikanyg almost 6 years ago
- 9 comments
#26 - v7 Naming Breaking change format
Issue -
State: closed - Opened by Meyce about 6 years ago
- 2 comments
#26 - v7 Naming Breaking change format
Issue -
State: closed - Opened by Meyce about 6 years ago
- 2 comments
#25 - / in topic name
Issue -
State: closed - Opened by Meyce about 6 years ago
- 1 comment
#25 - / in topic name
Issue -
State: closed - Opened by Meyce about 6 years ago
- 1 comment
#24 - Update referenced version of Microsoft.Azure.AzureServiceBus
Issue -
State: closed - Opened by Meyce about 6 years ago
- 1 comment
#23 - Possible problem with subscribers in the same IoC container
Issue -
State: closed - Opened by Jeern about 6 years ago
- 2 comments
Labels: question
#22 - Some types of event not handled in Azure Service Bus after upgrade of Rebus.AzureServiceBus
Issue -
State: closed - Opened by Jeern about 6 years ago
- 5 comments
#21 - Please provide a compat for V7 Naming Breaking change
Issue -
State: closed - Opened by Rzpeg about 6 years ago
- 7 comments
Labels: enhancement
#20 - V6: The lock supplied is invalid. Either the lock expired, or the message has already been removed from the queue
Issue -
State: closed - Opened by Rzpeg about 6 years ago
- 9 comments
#19 - Error registering event subscriptions when running multiple instances
Issue -
State: closed - Opened by MortenChristiansen about 6 years ago
- 3 comments
Labels: bug
#18 - Normalizing dashes to underscores.
Issue -
State: closed - Opened by codyrehm over 6 years ago
- 8 comments
#17 - Using path in connection string no longer works
Issue -
State: closed - Opened by vegar over 6 years ago
- 5 comments
Labels: bug
#16 - Published release version depends on pre-release version
Issue -
State: closed - Opened by vladimir-kovalyuk over 6 years ago
- 3 comments
#15 - Message entity could not be found
Issue -
State: closed - Opened by MortenChristiansen over 6 years ago
- 13 comments
#14 - Using Shared access signature is not working
Issue -
State: closed - Opened by runes83 over 6 years ago
- 3 comments
#13 - Lock Expiration
Issue -
State: closed - Opened by mpaul31 over 6 years ago
- 2 comments
#12 - Suddenly alot of lock exceptions is heading my way
Issue -
State: closed - Opened by KennethJakobsen almost 7 years ago
- 8 comments
#11 - Create an extensibility point to name topics
Issue -
State: closed - Opened by heberop almost 7 years ago
- 4 comments
#10 - Too Many Incoming Requests
Issue -
State: closed - Opened by samuelya almost 7 years ago
- 1 comment
Labels: question
#9 - Native dead letter queue support
Issue -
State: closed - Opened by sbochoa almost 7 years ago
- 5 comments
#8 - Add ConfigureAwait to fix deadlock issues.
Pull Request -
State: closed - Opened by lezzi almost 7 years ago
- 7 comments
#7 - .Net Core assembly does not support System.Configuration.ConfigurationManager
Issue -
State: closed - Opened by KennethJakobsen about 7 years ago
- 6 comments
#6 - Compatibility with netstandard/net core
Issue -
State: closed - Opened by mollyporph over 7 years ago
- 61 comments
Labels: enhancement
#5 - Conflicting subscription names when using '/' in queue names
Issue -
State: closed - Opened by jmenziessmith over 7 years ago
- 7 comments
Labels: bug
#4 - Add ability to change the way topic names are created
Issue -
State: closed - Opened by ChristopherHaws over 7 years ago
- 7 comments
Labels: enhancement, help wanted
#3 - Why are pre-fetching and retry features in client not used?
Issue -
State: closed - Opened by trreeves over 7 years ago
- 2 comments
#2 - Add Transport configuration options to support MS guidance for high message throughput
Issue -
State: closed - Opened by trreeves over 7 years ago
- 3 comments
#1 - support "/" in topic path
Pull Request -
State: closed - Opened by Meyce about 8 years ago
- 10 comments