Some tests are skipped due to duplicate names

Test names must be unique per scope otherwise the second test overrides the first one with the same name.
For example if you had a test file that does:
def test_a():
    pass

def test_a():
    pass

Then only the second test_a will be ran. More details here.
These are the tests that are overriding previously defined tests due to this problem:
https://github.com/fastlmm/FaST-LMM/blob/d1fdad820ebb80329b39cedf8e599ef33230487e/fastlmm/association/tests/test_snp_set.py#L145
I found this issue automatically, see other issues here

Thanks. Will fix.


Replace bold with headings in breaking changes pages

Keep the linter happy at all costs

Also reduced heading level to make the breaking changes appear in the right-hand contents pane, do we like?

The right-hand pane is pretty much unusable with this

I thought it was useful to have the list, but can info they part of it seems bad.

Perhaps just group them by impact?

I'll give it a go.

Done, looks pretty nice IMHO


docstring updates for mkdocs

docstring replacement for mkdocs

@justinjeffery-ipf created a new workflow, made it so docs build CI only runs when changes occur to docs repo. mkdocs.yml, or build_docs.yml


Ability to hide users below a given power level in the membership list

We almost get this for free on LL; just need to spec a threshold below which clients should politely not show joins/parts or even membership of given users in a room.  Aka auditorium mode. (Do we really not have a bug for this already?)

Related: https://github.com/matrix-org/matrix-doc/issues/951
Related: https://github.com/vector-im/riot-web/issues/6417
Related: https://github.com/matrix-org/matrix-doc/issues/759 (loosely)


Embedded compression(LZ4)

Compression and serialization are inseparable relationships.
By including LZ4 support in the API, we try more efficient compression.
For that, I need to implement LZ4 myself (lz4.net is not a good choice).

Just out of curiosity, why is lz4.net not a good choice? FYI, I am currently taking a dependency on it in Easy.Compression.

latest LZ4 implementation is improved https://github.com/lz4/lz4 but lz4.net is not ported yet.
RavenDB has own LZ4 implemantation https://github.com/ayende/ravendb/tree/v4.0/src/Sparrow/Compression and it is so good.

I see, RavenDB's implementation is indeed quite interesting, can you not use that? I wonder what the license is.

Well, RavenDB is proprietary software, I think it is difficult.

The license is AGPL, can be found here: https://ravendb.net/terms (you have to select the tab 'Open Source License EULA'). Dammit.

Stupid question: what if someone ends up writing code quite similar on his own, without even knowing someone published the same code with a license that doesn't allow copying it? Who can say it was copied?

@snalesso if you can prove that you wrote that code 100% on your own, everything is fine. I don't think that ravendb will instantly sue you if they noticed, but coping or changing the code from them is strictly forbidden.

Thank you @Alkalinee. Anyway, I'm pretty confused since, potentially, someone can end up writing the exact same code as yours. With much more probability, just the same code structure. How can he prove he didn't copy since the "copied" code is open source?
Lawyers paradise.
P.S. Obviously I'm talking about few LOC

@neuecc would this work? https://github.com/MiloszKrajewski/K4os.Compression.LZ4
I am considering using this on top of ZeroFormatter. Or will MessagePack+LZ4 outperform ZeroFormatter + K4os.Compression.LZ4?


Write a C++ program to convert seconds to hours

Description
Write a C++ program to convert seconds to hours
1 hour = 60 minutes = 3600 seconds
Input  : 18000
Output : 5

How to contribute

Save the solution in program/ConvertSecondsToHours.cpp file
Add ConvertSecondsToHours.cpp file in convert-seconds-to-hours folder

!assign

Hey @astitva0011,
This issue has been assigned to you for more than 15 days.
We are unassigning you from this issue.
If you are still interested in contributing to this issue, please get auto-assigned on the issue by commenting !assign again.
Thanks for your contributions :)

!assign


Division of two integer types to return float result

The code is aimed at changing the default behaviour of the __truediv__ operator for tensors when both arguments are integers, so that a float type is returned instead of an integer - resolves #3133.
Before:
from tinygrad import Tensor
(Tensor([1]) / Tensor([2])).numpy()
# array([0], dtype=int32)
import torch
out = torch.tensor([1]) / torch.tensor([2])
print(out, out.dtype)
# tensor([0.5000]) torch.float32
After:
from tinygrad import Tensor
(Tensor([1]) / Tensor([2])).numpy()
# array([0.5], dtype=float32)
import torch
out = torch.tensor([1]) / torch.tensor([2])
print(out, out.dtype)
# tensor([0.5000]) torch.float32
The new result is more intuitive and more aligned with torch when using normal division. It makes more sense for a additional __floordiv__ operator to explicitly return an integer type after division when needed.

I'm fine with this if it matches torch. How's it coming?

No update in a few days, feel free to reopen.


Option to have Path Resolver Forget parameter based on config option

Description
It's better to enable/disable $route->forgetParameter(static::$tenantParameterName); in Path Resolver via a config option so that in some projects we can keep the parameter in the url for better identification and also to use this parameter in controllers for other needs.
https://github.com/archtechx/tenancy/blob/22dcb8b0693cfb0dbbf91a3e515ad9a9e2d5e95b/src/Resolvers/PathTenantResolver.php#L30C21-L30C36
Why this should be added
we can enable / disable this based on projects. Also this forgetParameter() is not documented.

You can use tenant().


Signal listener called based on the signal event that it expects

registerSignalListener(IModel.EVENT_LISTENER_ADDED, new ISignalReceiver<ModelEvent<TileModel>>() {
	@Override public void signalReceived(ModelEvent<TileModel> event) {
	}
});

The above would only be called if the event is a ModelEvent from TileModel

Will not fix until there is a valid reason for it


Update for Scala 2.13 with implicit WrappedArray

This has compiled, tested, and published without error on Windows, Linux, and Intel and M1 Macs.  I will try to use it with a few projects that depend on it to see if they still run.

@thebrenthaines, I'd be interested to know whether this works for you.

@thebrenthaines, I'd be interested to know whether this works for you.

Hi @kwalcock, I'll give it a try today and let you know. Thanks!

@thebrenthaines, any luck?  I almost have a version for Scala 3 working.

@thebrenthaines, any luck? I almost have a version for Scala 3 working.

Hi @kwalcock, sorry about that. I was wrapped up in other fun work (wrapping javacv in a reasonably well-typed scala package) and neglected to test in a timely way. Your gentle nudge did the trick though. I was able build and incorporate your branch seamlessly. No changes. It was sort of anticlimactic, really. I had to triple check that I was pulling in the right library.
Anyway, it looks good to me. Thanks for putting it together!

@MihaiSurdeanu, this is seeming to work and it's up to date with the current master branch.  There are lots and lots of changes, but they are mostly touching up old syntax.  Notable are the Scala version specific directories that you might want to be aware of.  The ThreadUtils was a pre-existing issue.  The DependencyMap and GraphMap needed to be pulled out of scala to account for changes in Scala 2.13, but are otherwise little changed.  package.scala is used to rename some types.  The Wrapper classes are empty for Scala 2.11 and 2.12 which means that functionality should not be affected at all.  In the Scala 2.13 version, some implicit trickery is used to override the copy that would otherwise be performed whenever an Array is converted into a Seq.  The Arrays get wrapped similarly to how it is done in 2.12 and 2.11: somewhat unsafely.
Presently, all three Scala versions (2.11, 2.12, and 2.13) will be tested by Jenkins.  If this turns out to be a problem because of the wait or because people find it difficult to write syntax compatible with all three versions, the the 2.13 can be removed and I will make any needed touch ups before publication.
I think this is ready to go.

Yay! Thank you @kwalcock !
Ok to merge, as far as I'm concerned.


Create losrios.edu

Official Link:
https://www.scc.losrios.edu/cis/

@drainu This domain is blacklisted because the school allows to register an email address there even if you are not a student of the college. If you are the student of this college, please apply with official document ("OFFICIAL DOCUMENT" tab at https://www.jetbrains.com/shop/eform/students).


fixes https://github.com/fabric8io/fabric8/issues/4296 and add apiman into iPaaS

fixes https://github.com/fabric8io/fabric8/issues/4296 and add apiman into iPaaS

Refer to this link for build results (access rights to CI server needed):
https://fabric8-ci.fusesource.com/job/fabric8-quickstarts-master-pullreq/586/
Test PASSed.


SQL error when trying to enter data types with timestamps

Laravel Version: 5.3.30
Voyager Version: 0.10.10
PHP Version: 5.6.24
Database Driver & Version:
mysql

Description:
following tutorials on youtube. created a products data type with timestamps. but when I try to enter a new product. I leave the created update fields blank since I do not get a pop type bootstrap calendar and I assume that the timestamps will be saves automatically but getting SQL error:
SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '' for column 'created_at' at row 1 (SQL: insert into products (name, description, created_at, updated_at) values (Laravel Book, A book about Laravel development, , ))
if we have to enter a date for data types then I would assume a jquery calendar or some date formatting hints.  But I then try to enter a data as such:  02/02/2017 and get an error of:
Unexpected data found.
Unexpected data found.
Data missing
Steps To Reproduce:
following tutorials on youtube. created a products data type with timestamps. but when I try to enter a new product. I leave the created update fields blank since I do not get a pop type bootstrap calendar and I assume that the timestamps will be saves automatically but getting SQL error:
BTW. in the database tool. the timestamps options are marked YES for NULL.

So today more research. So when I have the created and updated fields marked as Date fields in the BREAD editor I do get a calendar view but of course in the DB it is marked as Timestamps so this does not work. I can leave the fields as Textboxes but I have to make sure that the time is formatted correctly as such:  2017-02-24 00:00:00	If I leave them blank, I get the SQL error. The field is not formatted correctly I get SQL error.
So I would assume that if I chose the Created and Update fields in my datatype, I would not need to enter anything in the fields and upon submit, it would just save the item in the DB. As of right now, you have to enter a Timestamp formatted correctly or you will get an error.
Thanks!

Can you please share a screenshot of the database table products structure, the BREAD options for products and the error that happens.

screenshots below:

I have same issue. Resolve it with adding this code to my Model.
public function save(array $options = [])     {         if(!isset($this->created_at)) {         	$this->created_at = date("Y-m-d H:i:s");         }         $this->updated_at = date("Y-m-d H:i:s");         parent::save();     }
It's a little bit hacky but works.

Indeed a hacky solution. But however a temporary fix.

I looked a little bit closer to this issue.
When I disable timestamps show in Create it works fine and in database there is right dates of create_at and update_at. Then on Edit we need to disable only update_at if we want be able to change created_at and generate new date for update_at.
Everthing is going about overrides.
If it's lame just ignore it but i hope it will help someone.

Well, this is not a bug to me, when you're not using timestamps you have indeed to disable them in your models.
And also $cast the dates besides the normal ones created_at, updated_at, deleted_at, or you're gonna face another error like this one.
Simply add public $timestamps = false; to your models.

I believe the problem lies in src/Http/Controllers/Controller.php where for timestamps it is not checked whether the input actually contains a value. I have prepared a pull request that fixes this.
For me, this fixes the error ...
QueryException in Connection.php line 770:
SQLSTATE[22007]: Invalid datetime format: 1292 Incorrect datetime value: '1970-01-01 00:00:00' for column 'created_at' at row 1 (SQL: update `users` set `password` = XXX, `created_at` = 1970-01-01 00:00:00, `updated_at` = 2017-02-13 18:28:24, `avatar` = users/February2017/C1DXaKqmbgRtjLsBKs3T.jpg where `id` = 1)

... which I got when updating my avatar.


Initial serialized member name mapping

This is the prototype implementation for serialized member name mappings we discussed. The other commits will be squashed out if/when merged into master.

(+@AhsonKhan if he has time for a sanity check)

Follow up to the above comment https://github.com/Azure/azure-sdk-for-net/pull/13527#discussion_r456734973
The following code snippet won't work when the stream starts with a UTF-8 BOM.
https://github.com/Azure/azure-sdk-for-net/blob/61241787da85546516933d4321f1c9a963e63658/sdk/core/Azure.Core.Experimental/src/Serialization/JsonObjectSerializer.cs#L52-L54
The synchronous, JsonSerializer.Deserialize method that accepts a ReadOnlySpan<byte> expects only valid JSON data (without any trivia or artifacts). The BOM is considered invalid JSON and will fail.
The async, stream accepting API explicitly skips the BOM for you (to support things like file stream). For this workaround, you would have to explicitly skip the BOM yourself.
https://github.com/dotnet/runtime/blob/e87fbd1030b472b4bc44c375434da65611aa4df0/src/libraries/System.Text.Json/src/System/Text/Json/Serialization/JsonSerializer.Read.Stream.cs#L159-L164
var utf8 = new byte[5] {0xEF, 0xBB, 0xBF, (byte)'{', (byte)'}'};
object obj = JsonSerializer.Deserialize<object>(utf8);

/*
Unhandled exception. System.Text.Json.JsonException: '0xEF' is an invalid start of a value. Path: $ | LineNumber: 0 | BytePositionInLine: 0.
 ---> System.Text.Json.JsonReaderException: '0xEF' is an invalid start of a value. LineNumber: 0 | BytePositionInLine: 0.
   at System.Text.Json.ThrowHelper.ThrowJsonReaderException(Utf8JsonReader& json, ExceptionResource resource, Byte nextByte, ReadOnlySpan`1 bytes)
*/

This is why I asked if accepting input streams that could contain a BOM is important to support here.
There is an existing request to add the sync stream-accepting APIs to S.T.J, but until then, you'd need to address it yourself as a workaround:
https://github.com/dotnet/runtime/issues/1574

@ahsonkhan please open a separate bug. That code was not touched nor is it in scope for this PR.

ObjectSerializer and friends are being moved to Azure.Core in PR #13619 and this interface isn't yet board-approved. Will need to retarget/rebase once approved.

This might need to be updated to include the new package: https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/core/ci.yml#L38

This might need to be updated to include the new package: https://github.com/Azure/azure-sdk-for-net/blob/master/sdk/core/ci.yml#L38

Are we planning on shipping it just yet? I didn't expect so. If not, I'll open an issue to track releasing it.


Reduce size of PNG files

This is the result of running https://pnggauntlet.com/
It should not impact the quality of the images, just the size.

By the way, thanks for creating and managing this repo, it's an extremely helpful resource!


Automated cherry pick of #7917

Cherry pick of #7917 on cloud.
/cc  @BenCookie95

/release-note-none

Will try to auto merge this PR once all tests and checks are passing. This might take up to an hour.

Trying to auto merge this PR.

Pull Request successfully merged
SHA: c6290ad485464769dfe9611358f44a7223492622


Betterize tests and update resolve action

The resolve action was using socket.gethostbyname_ex, which does not support IPv6 resolution.
This PR updates the resolve action to use socket.getaddrinfo, pins dependencies to Python 2.7 compatible versions, and improves the test assertions a bit.
I bumped the pack version to 0.6.0, since the changes made to the resolve action were slightly more than just fixing a bug.

Should we have CODEOWNERS for StackStorm Exchange packs? Manually having to set the required reviewers is quite a pain.

I assume someone who's maintaining the repositories are already subscribed to github dev activity, including PRs.
But sure why not, adding additional layer of notifications/awareness with the Github CODEOWNERS is a good idea!
Want to create PRs for the packs you're maintaining as a pilot experiment example?
cc @StackStorm-Exchange/tsc

Sure happy to do that, if you want to enforce review by CODEOWNERS then there's a repo setting to be turned for for branch protection.
A example CODEOWNERS for my packs would be:
* @jjm @StackStorm-Exchange/tsc
.circleci/** @StackStorm-Exchange/tsc


[azservicebus] Receiving messages with lock expiration delay

I'm having a weird issue where my service is receiving messages with delay. The delay corresponds (probably not a coincidence, might be related) to the message lock expiration.
My application logs if it fails to complete/defer/abandon a message, but I don't see any logs executing any of these operations, so I'm not receiving the events before.
My guess is that somewhere on the azservicebus lib the message is being lost and not being sent as output of the ReceiveMessages method.
I'm using version 0.4.0 of github.com/Azure/azure-sdk-for-go/sdk/messaging/azservicebus lib.
I can't reproduce this issue consistently, but it's happening multiple times a day (27 times on the last 7 days).
Unfortunately, I don't have any SDK logs active but I can activate if you find it necessary. There are no logs when messages are received though.
azservicebus_logs.pdf
The message lock duration is configured to 5 minutes.
@richardpark-msft

Hi @SpaWn2KiLl,
Some questions for you:

Are you using sessions?
How often do you receive messages and ask for more than you get back? Ie, if you have Receiver.ReceiveMessages(ctx, 10) do you typically get 10 messages? Or does it tend to fall short?
What max message count do you pass to ReceiveMessages()?
Do you have a time limit or deadline set on the context you pass to ReceiveMessages()? Does it get exceeded often?

Let's start here. I'll try to repro this on our internal testing as well.

Hello @richardpark-msft, thanks for your availability!

Are you using sessions?

No

How often do you receive messages and ask for more than you get back? Ie, if you have Receiver.ReceiveMessages(ctx, 10) do you typically get 10 messages? Or does it tend to fall short?

I'm receiving messages on a for loop without sleep. As soon as it processes all messages it requests for more. I'm having about 15~20 events per minute so it definitely tends to fall short

What max message count do you pass to ReceiveMessages()?

30

Do you have a time limit or deadline set on the context you pass to ReceiveMessages()? Does it get exceeded often?

No, I don't have deadline defined. The context stays active until explicit canceled, which is not happening.

@richardpark-msft Thanks for looking into this issue.
@SpaWn2KiLl I am removing the CXP Attention label from this tagging the Service Team.

Hello @richardpark-msft
Did you manage to reproduce the issue? do you have any news regarding to this issue? is there anything else I can do to help you find the issue?

Hi @richardpark-msft
Quick update about this issue
I have been running an affected service for 24 hours with the library v1 and so far I didn't have any problems.
I also activated the debug logs and I noticed this:
[azsb.Receiver] Fetching messages, issuing 30 credits
[azsb.Receiver] Context has been cancelled
[azsb.Receiver] Draining to clear 29 credits
[azsb.Receiver] Received 1/30 messages
[azsb.Receiver] Fetching messages, issuing 30 credits

Specifically, if you cancelled the context passed to receiver.ReceiveMessages() it would also cancel reading any messages that were stored internally to the AMQP receiver itself.

From what I understand, the context is being cancelled not by me but by the library itself based on defaultTimeAfterFirstMessage here
The issue was probably because the library was canceling the context based on that timer. Since you have now fixed the issue where messages are lost when the context is canceled, then this whole issue is probably fixed already. Anyway, I'll keep this service running for some more time

I had the message consumption delay again, not sure if it is the same error since it wasn't a 5 minutes delay (the message lock duration)

Logs
2022-05-20T16:27:34.296223660Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:27:34.296259462Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:27:34.299476050Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:27:34.432995566Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:27:35.349262131Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:27:35.349307135Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:27:35.351852131Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:27:35.427112737Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:27:49.637695594Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:27:49.637740598Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:27:49.639250411Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:27:49.679141599Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:28:00.877362616Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:28:00.877380818Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:28:00.878925727Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:28:00.909943317Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:28:03.956860481Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:28:03.956889683Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:28:03.958505102Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:28:04.012048753Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:28:07.048729833Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:28:07.048770236Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:28:08.049456478Z [azsb.Receiver] Closing link due to cancellation
2022-05-20T16:28:08.050772875Z [azsb.Receiver] Response router has shut down
2022-05-20T16:28:08.056247379Z [azsb.Receiver] Drain didn't complete in 1s, link was recreated
2022-05-20T16:28:08.056303383Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:28:08.056315184Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:28:08.056323385Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:43:08Z
2022-05-20T16:28:08.057193149Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:28:08.058780466Z [azsb.Auth] Response router has shut down
2022-05-20T16:28:08.060669905Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:28:08.060685606Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:43:08Z
2022-05-20T16:28:08.060690507Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.994594301s
2022-05-20T16:28:08.062679654Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:28:08.064264671Z [azsb.Auth] Response router has shut down
2022-05-20T16:28:08.066223015Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.994484793s
2022-05-20T16:28:08.083940222Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:28:13.141968904Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:28:13.142000606Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:28:13.173257242Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:28:13.249130440Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:28:24.362318264Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:28:24.362348666Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:28:24.369928792Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:28:24.484644053Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:28:40.652088210Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:28:40.652126012Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:28:40.653532612Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:28:40.717363837Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:28:42.724053801Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:28:42.724076402Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:28:43.724353617Z [azsb.Receiver] Closing link due to cancellation
2022-05-20T16:28:43.725744415Z [azsb.Receiver] Response router has shut down
2022-05-20T16:28:43.727406633Z [azsb.Receiver] Drain didn't complete in 1s, link was recreated
2022-05-20T16:28:43.727423234Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:28:43.728324198Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:28:43.728344400Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:43:43Z
2022-05-20T16:28:43.730201131Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:28:43.731570528Z [azsb.Auth] Response router has shut down
2022-05-20T16:28:43.733097437Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:28:43.733131839Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.995245063s
2022-05-20T16:28:43.733138040Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:43:43Z
2022-05-20T16:28:43.735177084Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:28:43.736532080Z [azsb.Auth] Response router has shut down
2022-05-20T16:28:43.738919449Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.994253592s
2022-05-20T16:28:43.990290307Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:28:49.507257205Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:28:49.507295508Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:28:49.508791609Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:28:49.538034492Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:28:51.320702161Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:28:51.320920577Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:28:51.358539589Z [azsb.Receiver] Flushed 1 messages from receiver's internal cache
2022-05-20T16:28:51.358575191Z [azsb.Receiver] Received 2/30 messages
2022-05-20T16:28:51.472848828Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:29:02.624263108Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:29:02.624318712Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:29:02.627783151Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:29:02.656327817Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:29:04.682364839Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:29:04.682396842Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:29:04.683868343Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:29:04.725372701Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:29:10.837630038Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:29:10.837660340Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:29:10.838987430Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:29:10.943655426Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:29:11.956193671Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:29:11.956229974Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:29:11.958287013Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:29:12.076867453Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:29:12.982330239Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:29:12.982359141Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:29:12.983424213Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:29:13.004456439Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:29:17.057079647Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:29:17.057109449Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:29:17.058937978Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:29:17.120839846Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:29:18.174884223Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:29:18.174910625Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:29:18.176431333Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:29:18.273457779Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:29:26.247625491Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:29:26.247657993Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:29:26.249140487Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:29:26.308489961Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:29:29.370392706Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:29:29.370416608Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:29:29.371899712Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:29:29.446674962Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:29:30.427702239Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:29:30.427718640Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:29:30.428940726Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:29:30.513356053Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:29:34.483062730Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:29:34.483100433Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:29:34.485972534Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:29:34.530131027Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:29:36.604891451Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:29:36.604921353Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:29:36.632084656Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:29:36.705786118Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:29:52.911385131Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:29:52.911410333Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:29:52.917688964Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:29:52.975636539Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:29:57.076660425Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:29:57.076693328Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:29:57.086821722Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:29:57.126376735Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:30:08.374543124Z [azsb.Receiver] Closing link/connection (potentially) for error link detached, reason: *Error(nil)
2022-05-20T16:30:08.378878919Z [azsb.Receiver] Response router has shut down
2022-05-20T16:30:08.383679847Z [azsb.Receiver] Non-fatal error occurred and no messages were received. Will recover on next call: link detached, reason: *Error(nil)
2022-05-20T16:30:08.383702248Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:30:08.383753252Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:45:08Z
2022-05-20T16:30:08.385269855Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:30:08.456962942Z [azsb.Auth] Response router has shut down
2022-05-20T16:30:08.500213991Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:30:08.500250093Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:45:08Z
2022-05-20T16:30:08.500343800Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.883466655s
2022-05-20T16:30:08.504626992Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:30:08.505796971Z [azsb.Auth] Response router has shut down
2022-05-20T16:30:08.507861812Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.992365979s
2022-05-20T16:30:28.755206694Z [azsb.Receiver] (receiveMessages.getlinks) Retry attempt 0 returned retryable error: *Error{Condition: amqp:internal-error, Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:4b305fedcd8f418a9ac9f54d51278106_G2, SystemTracker:gateway7, Timestamp:2022-05-20T16:30:28, Info: map[]}
2022-05-20T16:30:28.793276433Z [azsb.Receiver] (receiveMessages.getlinks) Retry attempt 1 sleeping for 5.081018176s
2022-05-20T16:30:33.840450298Z [azsb.Conn] Recovering link for error *Error{Condition: amqp:internal-error, Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:4b305fedcd8f418a9ac9f54d51278106_G2, SystemTracker:gateway7, Timestamp:2022-05-20T16:30:28, Info: map[]}
2022-05-20T16:30:33.840489601Z [azsb.Conn] Recovering connection (and links)
2022-05-20T16:30:33.840495801Z [azsb.Conn] Skipping connection recovery, already recovered: 2 vs 0
2022-05-20T16:30:33.840500902Z [azsb.Conn] Recovered connection and links
2022-05-20T16:30:33.840505902Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:30:33.840522803Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:45:33Z
2022-05-20T16:30:33.896416578Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:30:33.907367737Z [azsb.Auth] Response router has shut down
2022-05-20T16:30:33.918908437Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:30:33.918945839Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.921634968s
2022-05-20T16:30:33.918949640Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:45:33Z
2022-05-20T16:30:33.921911745Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:30:33.924379616Z [azsb.Auth] Response router has shut down
2022-05-20T16:30:33.926624272Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.992290566s
2022-05-20T16:30:49.312182177Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:30:49.312216680Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:45:49Z
2022-05-20T16:30:49.314630849Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{another topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:30:49.316004445Z [azsb.Auth] Response router has shut down
2022-05-20T16:30:49.316788400Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:30:49.316805401Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:45:49Z
2022-05-20T16:30:49.317679662Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.994488115s
2022-05-20T16:30:49.319396582Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{another topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:30:49.320674871Z [azsb.Auth] Response router has shut down
2022-05-20T16:30:49.334922168Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.981938637s
2022-05-20T16:30:54.004373570Z [azsb.Receiver] (receiveMessages.getlinks) Retry attempt 1 returned retryable error: *Error{Condition: amqp:internal-error, Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:4b305fedcd8f418a9ac9f54d51278106_G2, SystemTracker:gateway7, Timestamp:2022-05-20T16:30:53, Info: map[]}
2022-05-20T16:30:54.004406773Z [azsb.Receiver] (receiveMessages.getlinks) Retry attempt 2 sleeping for 13.587360319s
2022-05-20T16:31:07.592477907Z [azsb.Conn] Recovering link for error *Error{Condition: amqp:internal-error, Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:4b305fedcd8f418a9ac9f54d51278106_G2, SystemTracker:gateway7, Timestamp:2022-05-20T16:30:53, Info: map[]}
2022-05-20T16:31:07.592509209Z [azsb.Conn] Recovering connection (and links)
2022-05-20T16:31:07.592516609Z [azsb.Conn] Skipping connection recovery, already recovered: 2 vs 0
2022-05-20T16:31:07.592525010Z [azsb.Conn] Recovered connection and links
2022-05-20T16:31:07.592528710Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:31:07.592541611Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:46:07Z
2022-05-20T16:31:07.594788567Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:31:07.598969658Z [azsb.Auth] Response router has shut down
2022-05-20T16:31:07.600798685Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:31:07.600821186Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:46:07Z
2022-05-20T16:31:07.600883291Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.991674021s
2022-05-20T16:31:07.602679115Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:31:07.603886899Z [azsb.Auth] Response router has shut down
2022-05-20T16:31:07.606111254Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.994726434s
2022-05-20T16:31:07.677149290Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:31:07.706307116Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:31:07.706339919Z [azsb.Receiver] Draining to clear 24 credits
2022-05-20T16:31:07.710891735Z [azsb.Receiver] Received 6/30 messages
2022-05-20T16:31:08.223174960Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:31:08.274781050Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:31:08.274810352Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:31:08.276530082Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:31:08.347383623Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:31:17.425462925Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:31:17.425522831Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:31:17.426953081Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:31:17.538772800Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:31:20.538673296Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:31:20.538709699Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:31:20.551620009Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:31:20.815686932Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:31:21.715477787Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:31:21.715507789Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:31:21.719980904Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:31:21.765234596Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:31:22.758504843Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:31:22.758524745Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:31:22.761536957Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:31:22.876416859Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:31:23.810481031Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:31:23.810540135Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:31:24.810971783Z [azsb.Receiver] Closing link due to cancellation
2022-05-20T16:31:24.814737152Z [azsb.Receiver] Drain didn't complete in 1s, link was recreated
2022-05-20T16:31:24.814769254Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:31:24.815749124Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:31:24.815763525Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:46:24Z
2022-05-20T16:31:24.821133708Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:31:24.822218186Z [azsb.Auth] Response router has shut down
2022-05-20T16:31:24.824012514Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:31:24.824033915Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.991788614s
2022-05-20T16:31:24.824039316Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:46:24Z
2022-05-20T16:31:24.825827243Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:31:24.827196341Z [azsb.Auth] Response router has shut down
2022-05-20T16:31:24.828763053Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.995260162s
2022-05-20T16:31:24.856871559Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:31:29.974358538Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:31:29.974393440Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:31:29.979559509Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:31:30.012536363Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:31:41.240122012Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:31:41.240145713Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:31:41.241858210Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:31:41.343912457Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:32:00.685894752Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:32:00.685927655Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:32:00.687638776Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:32:00.813565366Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:32:06.768544707Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:32:06.768564908Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:32:06.770236708Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:32:06.844852777Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:32:14.957466129Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:32:14.957503931Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:32:14.968874327Z [azsb.Receiver] Flushed 1 messages from receiver's internal cache
2022-05-20T16:32:14.968905629Z [azsb.Receiver] Received 2/30 messages
2022-05-20T16:32:15.049881097Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:32:26.195410679Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:32:26.195453082Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:32:26.197414719Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:32:26.296748343Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:32:27.263835055Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:32:27.263866557Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:32:27.265044439Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:32:27.287657415Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:32:31.417139794Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:32:31.417168696Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:32:31.484953115Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:32:31.610448653Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:32:36.639260375Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:32:36.639282776Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:32:36.652252407Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:32:36.707363916Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:32:44.889767215Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:32:44.889792917Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:32:45.889860131Z [azsb.Receiver] Closing link due to cancellation
2022-05-20T16:32:46.270350260Z [azsb.Receiver] Response router has shut down
2022-05-20T16:32:46.382805353Z [azsb.Receiver] Drain didn't complete in 1s, link was recreated
2022-05-20T16:32:46.382825954Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:32:46.384377560Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:32:46.384393661Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:47:46Z
2022-05-20T16:32:46.459629208Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:32:46.541991142Z [azsb.Auth] Response router has shut down
2022-05-20T16:32:46.573665509Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:32:46.573698011Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:47:46Z
2022-05-20T16:32:46.573723013Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.810692949s
2022-05-20T16:32:46.592338787Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:32:46.599038245Z [azsb.Auth] Response router has shut down
2022-05-20T16:32:46.612451862Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.961277651s
2022-05-20T16:32:46.646307179Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:32:55.916017087Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:32:55.916040288Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:32:56.050534295Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:32:56.097998644Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:33:03.984940957Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:33:03.984972459Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:33:03.986516158Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:33:04.016533672Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:34:05.962694113Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:34:05.962720314Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:34:05.964172808Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:34:05.989208320Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:34:12.118607123Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:34:12.118648825Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:34:12.120244528Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:34:12.192328969Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:34:19.311672943Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:34:19.311706845Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:34:19.313284950Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:34:19.398314517Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:34:19.424733477Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:34:19.424749478Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:34:19.425905755Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:34:19.532887484Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:34:21.431020757Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:34:21.431044159Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:34:21.432884076Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:34:21.545479079Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:34:31.579946856Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:34:31.579980158Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:34:31.581740774Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:34:31.659412860Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:34:34.699983183Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:34:34.700027786Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:34:34.756164662Z [azsb.Receiver] Flushed 1 messages from receiver's internal cache
2022-05-20T16:34:34.756204664Z [azsb.Receiver] Received 2/30 messages
2022-05-20T16:34:34.871665626Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:34:49.748897208Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:34:49.748930110Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:34:49.751758888Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:34:49.771385120Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:34:50.901421180Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:34:50.901458982Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:34:51.167688791Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:34:51.343577972Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:34:55.545398066Z [azsb.Receiver] Closing link/connection (potentially) for error link detached, reason: *Error(nil)
2022-05-20T16:34:55.548966799Z [azsb.Receiver] Response router has shut down
2022-05-20T16:34:55.556359581Z [azsb.Receiver] Non-fatal error occurred and no messages were received. Will recover on next call: link detached, reason: *Error(nil)
2022-05-20T16:34:55.556402684Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:34:55.556411285Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:49:55Z
2022-05-20T16:34:55.559512487Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:34:55.560748768Z [azsb.Auth] Response router has shut down
2022-05-20T16:34:55.562287968Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:34:55.562312870Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:49:55Z
2022-05-20T16:34:55.562348172Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.993962806s
2022-05-20T16:34:55.566072215Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:34:55.574987996Z [azsb.Auth] Response router has shut down
2022-05-20T16:34:55.590938437Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.971439137s
2022-05-20T16:35:15.880101837Z [azsb.Receiver] (receiveMessages.getlinks) Retry attempt 0 returned retryable error: *Error{Condition: amqp:internal-error, Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:4b305fedcd8f418a9ac9f54d51278106_G2, SystemTracker:gateway7, Timestamp:2022-05-20T16:35:15, Info: map[]}
2022-05-20T16:35:15.880135139Z [azsb.Receiver] (receiveMessages.getlinks) Retry attempt 1 sleeping for 4.075428374s
2022-05-20T16:35:19.956004345Z [azsb.Conn] Recovering link for error *Error{Condition: amqp:internal-error, Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:4b305fedcd8f418a9ac9f54d51278106_G2, SystemTracker:gateway7, Timestamp:2022-05-20T16:35:15, Info: map[]}
2022-05-20T16:35:19.956051348Z [azsb.Conn] Recovering connection (and links)
2022-05-20T16:35:19.956064049Z [azsb.Conn] Skipping connection recovery, already recovered: 2 vs 0
2022-05-20T16:35:19.956068949Z [azsb.Conn] Recovered connection and links
2022-05-20T16:35:19.956072649Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:35:19.956076850Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:50:19Z
2022-05-20T16:35:19.958801919Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:35:19.960200705Z [azsb.Auth] Response router has shut down
2022-05-20T16:35:19.962085622Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:35:19.962099123Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:50:19Z
2022-05-20T16:35:19.962117224Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.993882721s
2022-05-20T16:35:19.968646129Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:35:19.968673330Z [azsb.Auth] Response router has shut down
2022-05-20T16:35:19.968679631Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.994891583s
2022-05-20T16:35:26.493797183Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:35:26.742956550Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:35:26.742993453Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:35:26.763829096Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:35:26.948939133Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:35:35.968483487Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:35:35.968515489Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:35:36.968759870Z [azsb.Receiver] Closing link due to cancellation
2022-05-20T16:35:36.973285562Z [azsb.Receiver] Drain didn't complete in 1s, link was recreated
2022-05-20T16:35:36.973314864Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:35:36.974255124Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:35:36.974275726Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:50:36Z
2022-05-20T16:35:36.976994001Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:35:36.978635807Z [azsb.Auth] Response router has shut down
2022-05-20T16:35:36.980138504Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:35:36.980158305Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:50:36Z
2022-05-20T16:35:36.980193107Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.99409562s
2022-05-20T16:35:36.982568060Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:35:36.983810240Z [azsb.Auth] Response router has shut down
2022-05-20T16:35:36.985804869Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.99441154s
2022-05-20T16:35:37.019573346Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:35:47.171030486Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:35:47.171061288Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:35:47.172547084Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:35:47.197271375Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:35:49.312981382Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:35:49.313009884Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:50:49Z
2022-05-20T16:35:49.315096018Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{another topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:35:49.316261993Z [azsb.Auth] Response router has shut down
2022-05-20T16:35:49.317307360Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:35:49.317322361Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:50:49Z
2022-05-20T16:35:49.317680984Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.9953253s
2022-05-20T16:35:49.319226683Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{another topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:35:49.320528567Z [azsb.Auth] Response router has shut down
2022-05-20T16:35:49.321813049Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.995525313s
2022-05-20T16:35:57.375140780Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:35:57.375180283Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:35:57.376690377Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:35:57.491524759Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:36:16.759686524Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:36:16.759720526Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:36:17.759895193Z [azsb.Receiver] Closing link due to cancellation
2022-05-20T16:36:17.761479583Z [azsb.Receiver] Response router has shut down
2022-05-20T16:36:17.763060873Z [azsb.Receiver] Drain didn't complete in 1s, link was recreated
2022-05-20T16:36:17.763073974Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:36:17.764193238Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:36:17.764213239Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:51:17Z
2022-05-20T16:36:17.765984140Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:36:17.767186308Z [azsb.Auth] Response router has shut down
2022-05-20T16:36:17.768805700Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:36:17.768820201Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.995402238s
2022-05-20T16:36:17.768825701Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:51:17Z
2022-05-20T16:36:17.770511597Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:36:17.772340102Z [azsb.Auth] Response router has shut down
2022-05-20T16:36:17.773562071Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.995316233s
2022-05-20T16:36:17.875614384Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:36:25.911793373Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:36:25.911826875Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:36:25.914001813Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:36:26.034728178Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:36:28.998686026Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:36:28.998714028Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:36:29.000553944Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:36:29.027295036Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:36:49.481466218Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:36:49.481490519Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:36:49.482914506Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:36:49.523311368Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:36:51.527210002Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:36:51.527230503Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:36:51.529192223Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:36:51.624704044Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:37:02.718387293Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:37:02.718432295Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:37:02.722885671Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:37:02.828108082Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:37:35.285217229Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:37:35.285245231Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:37:35.286845031Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:37:35.396327472Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:37:42.365041410Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:37:42.365072512Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:37:42.366793717Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:37:42.421759573Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:37:43.400844458Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:37:43.400880560Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:37:43.402396353Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:37:43.490108309Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:37:50.547857783Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:37:50.547897086Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:37:50.549562790Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:37:50.652021470Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:37:53.631670531Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:37:53.631690532Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:37:53.670426345Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:37:53.805746572Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:37:55.670435797Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:37:55.670463799Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:37:55.672338516Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:37:55.738792654Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:37:57.726336453Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:37:57.726364654Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:37:57.728575191Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:37:57.756426213Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:38:19.136081655Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:38:19.136117557Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:38:19.137502836Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:38:19.317775619Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:38:21.225886441Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:38:21.225913243Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:38:21.227210048Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:38:21.335367754Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:38:27.361677298Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:38:27.361710601Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:38:27.363336034Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:38:27.448639689Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:38:28.409843110Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:38:28.409868012Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:38:28.411662924Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:38:28.461168205Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:38:40.682083437Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:38:40.682138740Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:38:40.683643244Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:38:40.747534129Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:38:56.919468532Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:38:56.919502234Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:38:56.920705011Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:38:56.994272133Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:39:02.030894402Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:39:02.030928404Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:39:02.032728810Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:39:02.053123614Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:39:06.104713312Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:39:06.104750814Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:39:06.106090294Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:39:06.230827755Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:39:15.282312977Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:39:15.282356180Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:39:15.283779268Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:39:15.383150611Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:39:18.381732332Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:39:18.381751133Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:39:18.383390034Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:39:18.438975663Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:40:01.956162679Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:40:01.956208581Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:40:01.958245206Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:40:01.999328613Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:40:08.057457897Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:40:08.057491599Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:40:08.060130549Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:40:08.076763195Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:40:12.714129680Z [azsb.Receiver] Closing link/connection (potentially) for error link detached, reason: *Error(nil)
2022-05-20T16:40:12.744225350Z [azsb.Receiver] Response router has shut down
2022-05-20T16:40:12.785397008Z [azsb.Receiver] Non-fatal error occurred and no messages were received. Will recover on next call: link detached, reason: *Error(nil)
2022-05-20T16:40:12.785427710Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:40:12.785435710Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:55:12Z
2022-05-20T16:40:12.803054705Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:40:12.819189707Z [azsb.Auth] Response router has shut down
2022-05-20T16:40:12.845334832Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:40:12.845364134Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:55:12Z
2022-05-20T16:40:12.845404736Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.940010973s
2022-05-20T16:40:12.850722967Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:40:12.863616468Z [azsb.Auth] Response router has shut down
2022-05-20T16:40:12.879756470Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.965645165s
2022-05-20T16:40:33.145244313Z [azsb.Receiver] (receiveMessages.getlinks) Retry attempt 0 returned retryable error: *Error{Condition: amqp:internal-error, Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:4b305fedcd8f418a9ac9f54d51278106_G2, SystemTracker:gateway7, Timestamp:2022-05-20T16:40:32, Info: map[]}
2022-05-20T16:40:33.145260914Z [azsb.Receiver] (receiveMessages.getlinks) Retry attempt 1 sleeping for 4.049274994s
2022-05-20T16:40:37.195187488Z [azsb.Conn] Recovering link for error *Error{Condition: amqp:internal-error, Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:4b305fedcd8f418a9ac9f54d51278106_G2, SystemTracker:gateway7, Timestamp:2022-05-20T16:40:32, Info: map[]}
2022-05-20T16:40:37.195230490Z [azsb.Conn] Recovering connection (and links)
2022-05-20T16:40:37.195249191Z [azsb.Conn] Skipping connection recovery, already recovered: 2 vs 0
2022-05-20T16:40:37.195255092Z [azsb.Conn] Recovered connection and links
2022-05-20T16:40:37.195260092Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:40:37.195266192Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:55:37Z
2022-05-20T16:40:37.197659738Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:40:37.198991919Z [azsb.Auth] Response router has shut down
2022-05-20T16:40:37.200748925Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:40:37.200776927Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.994527667s
2022-05-20T16:40:37.200781327Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:55:37Z
2022-05-20T16:40:37.203356784Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:40:37.204627061Z [azsb.Auth] Response router has shut down
2022-05-20T16:40:37.206648184Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.994176747s
2022-05-20T16:40:49.314065269Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:40:49.314093271Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:55:49Z
2022-05-20T16:40:49.316385110Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{another topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:40:49.317633886Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:40:49.317646687Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:55:49Z
2022-05-20T16:40:49.317728692Z [azsb.Auth] Response router has shut down
2022-05-20T16:40:49.319725113Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.994340156s
2022-05-20T16:40:49.321260006Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{another topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:40:49.322549085Z [azsb.Auth] Response router has shut down
2022-05-20T16:40:49.324198985Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.993468203s
2022-05-20T16:40:55.749098593Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:40:58.285728096Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:40:58.285754998Z [azsb.Receiver] Draining to clear 27 credits
2022-05-20T16:40:58.324387945Z [azsb.Receiver] Flushed 4 messages from receiver's internal cache
2022-05-20T16:40:58.324417947Z [azsb.Receiver] Received 7/30 messages
2022-05-20T16:40:58.918003508Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:40:58.940845796Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:40:58.940912100Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:40:58.943393650Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:40:59.001512681Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:40:59.379198726Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:40:59.379233128Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:40:59.380885629Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:40:59.427552264Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:41:01.557107441Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:41:01.557136043Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:41:01.568940860Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:41:01.641574673Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:41:04.771942563Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:41:04.771971765Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:41:04.773305246Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:41:04.806059136Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:41:14.909040152Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:41:14.909075454Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:41:14.911403696Z [azsb.Receiver] Received 1/30 messages
2022-05-20T16:41:14.944248392Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:41:18.992904605Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:41:18.992927906Z [azsb.Receiver] Draining to clear 29 credits
2022-05-20T16:41:18.995188544Z [azsb.Receiver] Received 1/30 messages

Suspicious logs
2022-05-20T16:28:08.056247379Z [azsb.Receiver] Drain didn't complete in 1s, link was recreated

2022-05-20T16:28:43.727406633Z [azsb.Receiver] Drain didn't complete in 1s, link was recreated

2022-05-20T16:29:57.126376735Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:30:08.374543124Z [azsb.Receiver] Closing link/connection (potentially) for error link detached, reason: *Error(nil)
2022-05-20T16:30:08.378878919Z [azsb.Receiver] Response router has shut down
2022-05-20T16:30:08.383679847Z [azsb.Receiver] Non-fatal error occurred and no messages were received. Will recover on next call: link detached, reason: *Error(nil)
2022-05-20T16:30:08.383702248Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:30:08.383753252Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:45:08Z
2022-05-20T16:30:08.385269855Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:30:08.456962942Z [azsb.Auth] Response router has shut down
2022-05-20T16:30:08.500213991Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:30:08.500250093Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:45:08Z
2022-05-20T16:30:08.500343800Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.883466655s
2022-05-20T16:30:08.504626992Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:30:08.505796971Z [azsb.Auth] Response router has shut down
2022-05-20T16:30:08.507861812Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.992365979s
2022-05-20T16:30:28.755206694Z [azsb.Receiver] (receiveMessages.getlinks) Retry attempt 0 returned retryable error: *Error{Condition: amqp:internal-error, Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:4b305fedcd8f418a9ac9f54d51278106_G2, SystemTracker:gateway7, Timestamp:2022-05-20T16:30:28, Info: map[]}
2022-05-20T16:30:28.793276433Z [azsb.Receiver] (receiveMessages.getlinks) Retry attempt 1 sleeping for 5.081018176s
2022-05-20T16:30:33.840450298Z [azsb.Conn] Recovering link for error *Error{Condition: amqp:internal-error, Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:4b305fedcd8f418a9ac9f54d51278106_G2, SystemTracker:gateway7, Timestamp:2022-05-20T16:30:28, Info: map[]}
2022-05-20T16:30:33.840489601Z [azsb.Conn] Recovering connection (and links)
2022-05-20T16:30:33.840495801Z [azsb.Conn] Skipping connection recovery, already recovered: 2 vs 0
2022-05-20T16:30:33.840500902Z [azsb.Conn] Recovered connection and links
2022-05-20T16:30:33.840505902Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:30:33.840522803Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:45:33Z
2022-05-20T16:30:33.896416578Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:30:33.907367737Z [azsb.Auth] Response router has shut down
2022-05-20T16:30:33.918908437Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:30:33.918945839Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.921634968s
2022-05-20T16:30:33.918949640Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:45:33Z
2022-05-20T16:30:33.921911745Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:30:33.924379616Z [azsb.Auth] Response router has shut down
2022-05-20T16:30:33.926624272Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.992290566s
2022-05-20T16:30:49.312182177Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:30:49.312216680Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:45:49Z
2022-05-20T16:30:49.314630849Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{another topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:30:49.316004445Z [azsb.Auth] Response router has shut down
2022-05-20T16:30:49.316788400Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:30:49.316805401Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:45:49Z
2022-05-20T16:30:49.317679662Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.994488115s
2022-05-20T16:30:49.319396582Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{another topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:30:49.320674871Z [azsb.Auth] Response router has shut down
2022-05-20T16:30:49.334922168Z [azsb.Auth] ({another topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.981938637s
2022-05-20T16:30:54.004373570Z [azsb.Receiver] (receiveMessages.getlinks) Retry attempt 1 returned retryable error: *Error{Condition: amqp:internal-error, Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:4b305fedcd8f418a9ac9f54d51278106_G2, SystemTracker:gateway7, Timestamp:2022-05-20T16:30:53, Info: map[]}
2022-05-20T16:30:54.004406773Z [azsb.Receiver] (receiveMessages.getlinks) Retry attempt 2 sleeping for 13.587360319s
2022-05-20T16:31:07.592477907Z [azsb.Conn] Recovering link for error *Error{Condition: amqp:internal-error, Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:4b305fedcd8f418a9ac9f54d51278106_G2, SystemTracker:gateway7, Timestamp:2022-05-20T16:30:53, Info: map[]}
2022-05-20T16:31:07.592509209Z [azsb.Conn] Recovering connection (and links)
2022-05-20T16:31:07.592516609Z [azsb.Conn] Skipping connection recovery, already recovered: 2 vs 0
2022-05-20T16:31:07.592525010Z [azsb.Conn] Recovered connection and links
2022-05-20T16:31:07.592528710Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) refreshing claim
2022-05-20T16:31:07.592541611Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) negotiate claim, token expires on 2022-05-20T16:46:07Z
2022-05-20T16:31:07.594788567Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription} with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:31:07.598969658Z [azsb.Auth] Response router has shut down
2022-05-20T16:31:07.600798685Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) refreshing claim
2022-05-20T16:31:07.600821186Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) negotiate claim, token expires on 2022-05-20T16:46:07Z
2022-05-20T16:31:07.600883291Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}) next refresh in 4m59.991674021s
2022-05-20T16:31:07.602679115Z [azsb.Auth] negotiating claim for audience amqps://{service bus namespace}.servicebus.windows.net/{affected-topic}/Subscriptions/{service bus subscription}/$management with token type servicebus.windows.net:sastoken and expiry of<PHONE_NUMBER>
2022-05-20T16:31:07.603886899Z [azsb.Auth] Response router has shut down
2022-05-20T16:31:07.606111254Z [azsb.Auth] ({affected-topic}/Subscriptions/{service bus subscription}/$management) next refresh in 4m59.994726434s
2022-05-20T16:31:07.677149290Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:31:07.706307116Z [azsb.Receiver] Context has been cancelled
2022-05-20T16:31:07.706339919Z [azsb.Receiver] Draining to clear 24 credits
2022-05-20T16:31:07.710891735Z [azsb.Receiver] Received 6/30 messages

This application is consuming from two different topics using the same client. It uses a subscription (with the same name) on those two topics.
I was supposed to receive a message at around 16:28:42 but I only received it at 16:31:07 instead.
@richardpark-msft

Hi @SpaWn2KiLl,
This is a great log, and I appreciate your patience on this. :)
It looks like we have a sequence of events that might explain part of this delay. From what I can see the issue boils down to some network/connection trouble. The azservicebus package handles recovering from these failures, transparently, but it can add additional delays as a result.
Here's where it appears to start:

2022-05-20T16:29:57.126376735Z [azsb.Receiver] Fetching messages, issuing 30 credits
2022-05-20T16:30:08.374543124Z [azsb.Receiver] Closing link/connection (potentially) for error link detached, reason: *Error(nil)

The second line indicates that we were disconnected from Service Bus. This'll cause us to have to recreate the connection and link. It looks like we continued to have trouble:

2022-05-20T16:30:28.755206694Z [azsb.Receiver] (receiveMessages.getlinks) Retry attempt 0 returned retryable error: *Error{Condition: amqp:internal-error, Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:4b305fedcd8f418a9ac9f54d51278106_G2, SystemTracker:gateway7, Timestamp:2022-05-20T16:30:28, Info: map[]}

This happens a few more times:

2022-05-20T16:30:54.004373570Z [azsb.Receiver] (receiveMessages.getlinks) Retry attempt 1 returned retryable error: *Error{Condition: amqp:internal-error, Description: The service was unable to process the request; please retry the operation. For more information on exception types and proper exception handling, please refer to http://go.microsoft.com/fwlink/?LinkId=761101 TrackingId:4b305fedcd8f418a9ac9f54d51278106_G2, SystemTracker:gateway7, Timestamp:2022-05-20T16:30:53, Info: map[]}

It looks like there was a network/connection issue that lasted a few minutes - from what I can see azservicebus is handling this correctly. It's also possible that it was intermittent, but the intervals where it failed happened to be when we were attempting to do a retry.
It might be interesting to adjust would be the retry options for your application. We use fairly conservative retry options by default, which can lead to retry times as long as 13 seconds (it's exponential). If you want, you can adjust these - we have an example of doing that here:
https://github.com/Azure/azure-sdk-for-go/blob/a9d9b56a8ee885da9f94ed5e35ff001ca325fe84/sdk/messaging/azservicebus/example_client_test.go#L76


Fix a bug where a protocol violation is not handled by ServerErrorHandler

Motivation:
CorsServerErrorHandler was added as the first error handler by #5632 CorsServerErrorHandler does not handle an exception but delegates it to the default one or user-defined handler and injects CORS headers.
CorsServerErrorHandler overrode onServiceException to delegate but omitted to override onProtocolViolation. As a result, a user-defined onProtocolViolation wasn't invoked.
Modifications:

Override onProtocolViolation() and delegate to serverErrorHandler

Result:
A protocol violation is now correctly handled by ServerErrorHandler.onProtocolViolation()

I prefer keeping it default because most users may not be interested in protocol-level errors.


landing page styled

I have styled the logo WELCOME to WILDGUARD and also added a catchy tagline under it that will serve as a introductory catchline

no theme match Please see the conflicts . Resolve the conflicts . Ensure you pull all the latest changes before pushing your feature/bug fixes to the main branch. After resolving the conflicts, please open a new PR for review.
Thank you!


[Bug]: Return value must be of type string, null returned

Bug type
Installation
Commenter Version
2.0.9
Database
mysql
Description
LakM\Comments\Models\Comment::ownerName(): Return value must be of type string, null returned
I'm using DevDojo Auth package for authentication

@
Steps To Reproduce
No response
Reproduce URL
No response

If you're using a different column for the username, the package assumes it is name by default. Simply specify the correct column name in the commenter configuration file.  https://github.com/Lakshan-Madushanka/laravel-comments/blob/cf7445abd2d920ee0976a721f803e65aa88e0578/config/comments.php#L40

If you're using a different column for the username, the package assumes it is name by default. Simply specify the correct column name in the commenter configuration file.
https://github.com/Lakshan-Madushanka/laravel-comments/blob/cf7445abd2d920ee0976a721f803e65aa88e0578/config/comments.php#L40

users table has default column => name. I'm using Jetstream and Devdojo Auth packages for authentication.

If you're using a different column for the username, the package assumes it is name by default. Simply specify the correct column name in the commenter configuration file.
https://github.com/Lakshan-Madushanka/laravel-comments/blob/cf7445abd2d920ee0976a721f803e65aa88e0578/config/comments.php#L40

users table has default column => name. I'm using Jetstream and Devdojo Auth packages for authentication.

To Reproduce install a fresh laravel app with jetstream starter kit and set devdojo auth
Devdojo Auth

Please create a sample repo and share the link. I am prefer if I have write access. Then I can directly work on it with exact your dependencies.

Make sure users table doesn't have name column with a null value

Make sure users's table doesn't have a null value for the name column.


Improve type inference

The original Doodle model was that you start by fixing the Algebra operations you want to use , and then write everything to that fixed Algebra. In practice this doesn't work so well when combining different systems and we can be much more flexible. This will avoid a lot of type inference issues, particularly when writing cross-backend code, at the cost of more work for implementors of algebras (i.e. me). This is a reasonable trade-off.
The essential thing is that operations should accept some Alg and return Alg with TheStuffINeed.

Closed in bb84364

Closed in bb84364


Allow trade and hold a coin

Describe the solution you'd like
Allow a config per coin to I set how many units that I wanna hold of this coin, that config will allow e.g.: I wanna hold 50 units of ADA, but keep the bot running for this coin, buying and selling US$ 20 per trade
Describe alternatives you've considered
Remove the trading for the coins that I wanna hold, or transfer to another wallet.

What a coincidence! I just made the same issue for the very same feature!
https://github.com/chrisleekr/binance-trading-bot/issues/181

@elvishp2006 another good suggestion.
I will put it in the TODO list later.

Yes, it would be a good feature cause I can't trade some coins with this script that I've bought to hold them in a mid-long term.


Stackdriver example should subscribe to view

In our Stackdriver example we don't show subscribing to any views. This means that no stats will be collected.

We should also probably show explicitly recording a measure.

Hi @ramonza is this still needed? Seems like it was covered by your latest ergonomics PR.
I'm looking to contribute to the examples in the repo, but maybe I'll make one for the zipkin exporter instead.

yup, closing