-
Notifications
You must be signed in to change notification settings - Fork 853
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
[azservicebus] Validate that credits are within limits (not over or under) #19992
[azservicebus] Validate that credits are within limits (not over or under) #19992
Conversation
- <= 0 is bad since it can hang and we never intend to subtract credit. - Don't allow asking for more than the actual credit ceiling of the link, which is set, statically, when the link is created.
…hims of the go-scheduler and the speed of our test.
/azp run go - azservicebus |
Azure Pipelines successfully started running 1 pipeline(s). |
Also, sanity check that we do pass in the proper Credit value.
/azp run go - azservicebus |
Azure Pipelines successfully started running 1 pipeline(s). |
/azp run go - azservicebus |
Azure Pipelines successfully started running 1 pipeline(s). |
…rable) to be able to get logs multiple times, siphoning off whatever is in the channel at that point. This also eliminates another silly problem I have sometimes where the channel is closed early (because I extract logs) but the receiver or sender is still doing some background work which generates log information.
/azp run go - azservicebus |
Azure Pipelines successfully started running 1 pipeline(s). |
Once we get the underlying issue in |
Yeah, infinite credits and infinite sinks will be a nice touch. :) |
Fixing issues where we could over-request credit (#19965) or allow for negative/zero credits (#19743), both of which could cause issues with go-amqp..
Fixes #19965
Fixes #19743