Authorization Error with AZCopy

Which service(blob, file, queue, table) does this issue concern?
blob
Which version of the Azurite was used?
v3.28.0
Where do you get Azurite? (npm, DockerHub, NuGet, Visual Studio Code Extension)
npm
What's the Node.js version?
v18.14.0
What problem was encountered?
Error:
C:\Windows\System32>azcopy sync "D:\Dev\Data" "http://server5:10000/devstoreaccount1/data/?se=2023-12-12T02%3A24%3A20Z&sig=pw0GRd4oaURPwQ9choUoWnXxjYEsimipq64yu1otAVE%3D&sp=rwl&spr=https%2Chttp&srt=co&ss=b&st=2023-12-12T01%3A24%3A20Z&sv=2021-12-02" --from-to=LocalBlob

INFO: NOTE: HTTP is in use for one or more location(s). The use of HTTP is not recommended due to security concerns.
INFO: Any empty folders will not be processed, because source and/or destination doesn't have full folder support

Job a8778dc3-07d2-9244-42a6-d3194b6097e7 has started
Log file is located at: C:\Users\Work\.azcopy\a8778dc3-07d2-9244-42a6-d3194b6097e7.log

Cannot perform sync due to error: cannot list files due to reason GET http://server5:10000/devstoreaccount1
--------------------------------------------------------------------------------
RESPONSE 403: 403 This request is not authorized to perform this operation using this resource type.
ERROR CODE: AuthorizationResourceTypeMismatch
--------------------------------------------------------------------------------
<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<Error>
  AuthorizationResourceTypeMismatch
  <Message>This request is not authorized to perform this operation using this resource type.
RequestId:9a9321a7-29b3-4f04-9cfb-6fc18da290bd
Time:2023-12-12T01:24:37.583Z</Message>
</Error>
--------------------------------------------------------------------------------

Steps to reproduce the issue?

Place some files in D:\Dev\Data
Create a blob named data
Run the above command.

If possible, please provide the debug log using the -d parameter, replacing <pathtodebuglog> with an appropriate path for your OS, or review the instructions for docker containers:
2023/12/12 01:24:37 AzcopyVersion  10.22.0
2023/12/12 01:24:37 OS-Environment  windows
2023/12/12 01:24:37 OS-Architecture  amd64
2023/12/12 01:24:37 Log times are in UTC. Local time is 11 Dec 2023 16:24:37
2023/12/12 01:24:37 ==> REQUEST/RESPONSE (Try=1/2.7092ms, OpTime=10.0106ms) -- RESPONSE STATUS CODE ERROR
   HEAD http://server5:10000/devstoreaccount1/data?se=2023-12-12T02%3A24%3A20Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=co&ss=b&st=2023-12-12T01%3A24%3A20Z&sv=2021-12-02
   Accept: application/xml
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: 35e01dbd-2194-41eb-5f5f-57b207f922c6
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 400 Bad Request
   Connection: keep-alive
   Date: Tue, 12 Dec 2023 01:24:37 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/12 01:24:37 ==> REQUEST/RESPONSE (Try=1/2.5326ms, OpTime=3.0599ms) -- RESPONSE STATUS CODE ERROR
   GET http://server5:10000/devstoreaccount1?comp=list&delimiter=%2F&include=metadata&prefix=data%2F&restype=container&se=2023-12-12T02%3A24%3A20Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=co&ss=b&st=2023-12-12T01%3A24%3A20Z&sv=2021-12-02
   Accept: application/xml
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: c2c00001-3607-4fea-62d9-dc314d942bd9
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 403 This request is not authorized to perform this operation using this resource type.
   Connection: keep-alive
   Content-Type: application/xml
   Date: Tue, 12 Dec 2023 01:24:37 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
   X-Ms-Error-Code: AuthorizationResourceTypeMismatch
   X-Ms-Request-Id: 9a9321a7-29b3-4f04-9cfb-6fc18da290bd
Response Details: <?xml version="1.0" encoding="UTF-8" standalone="yes"?> <Error>   AuthorizationResourceTypeMismatch   <Message>This request is not authorized to perform this operation using this resource type. </Message>

2023/12/12 01:24:37 Closing Log

Please be sure to remove any PII or sensitive information before sharing!
The debug log will log raw request headers and bodies, so that we can replay these against Azurite using REST and create tests to validate resolution.
Have you found a mitigation/solution?
I have not. I was advised to open an issue here for further investigation.

Hi @InteXX ,
For the operation here:    GET http://server5:10000/devstoreaccount1?comp=list&delimiter=%2F&include=metadata&prefix=data%2F&restype=container&se=2023-12-12T02%3A24%3A20Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=co&ss=b&st=2023-12-12T01%3A24%3A20Z&sv=2021-12-02 , the operation is recognized as listing container against an account which requires service resource type, while the SAS token only allows container and object resource type.
From your AzCopy command, seems you want to copy a local folder to an Azurite container, in the copy operation, AzCopy should not send request to list an account.  I think the issue here is because: URL http://server5:10000/devstoreaccount1/data should indicating a container, but AzCopy think the container is http://server5:10000/devstoreaccount1.
Maybe you can open an issue to AzCopy team here  to ask for investigation?
Thanks
Emma

When I include Service in the SAS, I get a memory error:
panic: runtime error: invalid memory address or nil pointer dereference
[signal 0xc0000005 code=0x0 addr=0x18 pc=0x174bd12]

goroutine 114 [running]:
github.com/Azure/azure-storage-azcopy/v10/cmd.(*blobTraverser).parallelList.func1({0x1811d00?, 0xc000160570}, 0xc00067c000, 0xc00067e000)
        D:/a/1/s/cmd/zc_traverser_blob.go:332 +0x2b2
github.com/Azure/azure-storage-azcopy/v10/common/parallel.(*crawler).processOneDirectory(0xc00013e840, {0x1c1b990, 0xc000113dc0}, 0xf)
        D:/a/1/s/common/parallel/TreeCrawler.go:177 +0x338
github.com/Azure/azure-storage-azcopy/v10/common/parallel.(*crawler).workerLoop(0xc00013e840, {0x1c1b990, 0xc000113dc0}, 0x0?, 0x0?)
        D:/a/1/s/common/parallel/TreeCrawler.go:104 +0xb1
created by github.com/Azure/azure-storage-azcopy/v10/common/parallel.(*crawler).runWorkersToCompletion
        D:/a/1/s/common/parallel/TreeCrawler.go:93 +0x50

Maybe you can open an issue to AzCopy team

As you can see from my three-hour session (linked in original report) with them yesterday, we didn't make any progress. In fact, they've sent me to you.

AzCopy should not send request to list an account

In order to perform a sync operation, AzCopy needs a list of what's already in the container.

AzCopy think the container is http://server5:10000/devstoreaccount1

Isn't devstoreaccount1 the account to use for connecting to Azurite on the command line with a SAS?
https://learn.microsoft.com/en-us/azure/storage/common/storage-use-azurite?tabs=visual-studio%2Cblob-storage#well-known-storage-account-and-key

FYI I'm running Azurite like this:
azurite-blob.cmd --silent --blobHost <IP_ADDRESS> --location D:\Azurite -

How does one stop Azurite? I tried killing the Node process, but Azurite continued to respond.

I did consider the possibility of corrupted memory on my dev box, but running the same command directly on SERVER5 results in the same error.

Hi @InteXX ,
For the 403 issue, you are trying to copy a local folder to a container in Azurite.
From logic I don't think AzCopy intent to send request to list an account. The issue should because: AzCopy tried to send a request to list a container, but it mistreated the URL to the account http://server5:10000/devstoreaccount1 as a URL to the container. AzCopy didn't parse the account and container from the URL you input (http://server5:10000/devstoreaccount1/data/).
As a workaround, can you try to use a host name with the account name in the beginning, like devstoreaccount1.server5 ?  The command to copy the folder to container should look like: azcopy sync "folderpath" "http://devstoreaccount1.server5:10000/<containername>/
Thanks
Emma

you are trying to copy a local folder to a container in Azurite

Pardon my repetition, but I'm trying to sync a local folder with a container. There's a big difference. A sync can't happen until azcopy has lists of the files and their timestamps that exist on both sides, after which it will send only the latest files to the container.
I tried the workaround you suggested:
azcopy sync "D:\Dev\Data" "http://devstoreaccount1.server5:10000/data/" --from-to=LocalBlob

But I encountered this error:

INFO: Autologin not specified.
Cannot perform sync due to error: Login Credentials missing. No SAS token or OAuth token is present and the resource is not public

You'd still need to provide a SAS with the URL to Azurite.
azcopy sync "D:\Dev\Data" "http://devstoreaccount1.server5:10000/data/?<SASToken>" --from-to=LocalBlob

That produces a network timeout:

tcp: lookup devstoreaccount1.server5: no such host

Frankly, I should have caught that earlier. There is no hostname on my network devstoreaccount1.server5 (nor should there be).

To change host name,  you'd need to change your hosts file accordingly...

I'm disappointed to learn that I'll have to adjust my DNS just to get my build scripts to work, but if there's no other way I guess I'll just have to.
I'm now able to connect, but Azurite is returning a 500 Internal Server Error:
2023/12/13 06:20:50 AzcopyVersion  10.22.0
2023/12/13 06:20:50 OS-Environment  windows
2023/12/13 06:20:50 OS-Architecture  amd64
2023/12/13 06:20:50 Log times are in UTC. Local time is 12 Dec 2023 21:20:50
2023/12/13 06:20:50 ISO 8601 START TIME: to copy files that changed before or after this job started, use the parameter --include-before=2023-12-13T06:20:45Z or --include-after=2023-12-13T06:20:45Z
2023/12/13 06:20:50 Any empty folders will not be processed, because source and/or destination doesn't have full folder support
2023/12/13 06:20:50 Job-Command sync D:\Dev\Data http://devstoreaccount1.server5:10000/data/?se=2023-12-13t07%3A03%3A16z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13t06%3A03%3A16z&sv=2021-12-02 --from-to LocalBlob
2023/12/13 06:20:50 Number of CPUs: 20
2023/12/13 06:20:50 Max file buffer RAM 10.000 GB
2023/12/13 06:20:50 Max concurrent network operations: 300 (Based on number of CPUs. Set AZCOPY_CONCURRENCY_VALUE environment variable to override)
2023/12/13 06:20:50 Check CPU usage when dynamically tuning concurrency: true (Based on hard-coded default. Set AZCOPY_TUNE_TO_CPU environment variable to true or false override)
2023/12/13 06:20:50 Max concurrent transfer initiation routines: 64 (Based on hard-coded default. Set AZCOPY_CONCURRENT_FILES environment variable to override)
2023/12/13 06:20:50 Max enumeration routines: 16 (Based on hard-coded default. Set AZCOPY_CONCURRENT_SCAN environment variable to override)
2023/12/13 06:20:50 Parallelize getting file properties (file.Stat): false (Based on AZCOPY_PARALLEL_STAT_FILES environment variable)
2023/12/13 06:20:50 Max open files when downloading:<PHONE_NUMBER> (auto-computed)
2023/12/13 06:20:50 Final job part has been created
2023/12/13 06:20:50 Final job part has been scheduled
2023/12/13 06:20:50 INFO: [P#0-T#1] Starting transfer: Source "\\\\?\\D:\\Dev\\Data\\_Blogging.sdf" Destination "http://devstoreaccount1.server5:10000/data/_Blogging.sdf". Specified chunk size 8388608
2023/12/13 06:20:50 INFO: [P#0-T#0] Starting transfer: Source "\\\\?\\D:\\Dev\\Data\\Blogging.sdf" Destination "http://devstoreaccount1.server5:10000/data/Blogging.sdf". Specified chunk size 8388608
2023/12/13 06:20:50 INFO: [P#0-T#2] Starting transfer: Source "\\\\?\\D:\\Dev\\Data\\__Blogging.sdf" Destination "http://devstoreaccount1.server5:10000/data/__Blogging.sdf".  States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:20:52 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 2.6102
2023/12/13 06:20:54 ==> REQUEST/RESPONSE (Try=1/10.3017ms, OpTime=11.0626ms) -- RESPONSE STATUS CODE ERROR
   PUT http://devstoreaccount1.server5:10000/data/__Blogging.sdf?se=2023-12-13T07%3A03%3A16Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13T06%3A03%3A16Z&sv=2021-12-02
   Accept: application/xml
   Content-Length: 131072
   Content-Type: application/octet-stream
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: d456358d-7ec4-4c07-4e77-d62faa7e5f2b
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-type: BlockBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 500 Internal Server Error
   Connection: keep-alive
   Content-Length: 0
   Date: Wed, 13 Dec 2023 06:20:54 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/13 06:20:54 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:20:54 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0.5208
2023/12/13 06:20:55 ==> REQUEST/RESPONSE (Try=1/42.9886ms, OpTime=44.7658ms) -- RESPONSE STATUS CODE ERROR
   PUT http://devstoreaccount1.server5:10000/data/_Blogging.sdf?se=2023-12-13T07%3A03%3A16Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13T06%3A03%3A16Z&sv=2021-12-02
   Accept: application/xml
   Content-Length: 131072
   Content-Type: application/octet-stream
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: 375f3474-86e6-490a-6659-873ec72e151f
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-type: BlockBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 500 Internal Server Error
   Connection: keep-alive
   Content-Length: 0
   Date: Wed, 13 Dec 2023 06:20:55 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/13 06:20:56 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:20:56 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0.5234
2023/12/13 06:20:58 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:20:58 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0
2023/12/13 06:21:00 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:00 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0
2023/12/13 06:21:01 ==> REQUEST/RESPONSE (Try=1/13.534ms, OpTime=17.5224ms) -- RESPONSE STATUS CODE ERROR
   PUT http://devstoreaccount1.server5:10000/data/__Blogging.sdf?se=2023-12-13T07%3A03%3A16Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13T06%3A03%3A16Z&sv=2021-12-02
   Accept: application/xml
   Content-Length: 131072
   Content-Type: application/octet-stream
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: d456358d-7ec4-4c07-4e77-d62faa7e5f2b
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-type: BlockBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 500 Internal Server Error
   Connection: keep-alive
   Content-Length: 0
   Date: Wed, 13 Dec 2023 06:21:00 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/13 06:21:02 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:02 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0.524
2023/12/13 06:21:03 ==> REQUEST/RESPONSE (Try=1/11.6509ms, OpTime=12.4368ms) -- RESPONSE STATUS CODE ERROR
   PUT http://devstoreaccount1.server5:10000/data/_Blogging.sdf?se=2023-12-13T07%3A03%3A16Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13T06%3A03%3A16Z&sv=2021-12-02
   Accept: application/xml
   Content-Length: 131072
   Content-Type: application/octet-stream
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: 375f3474-86e6-490a-6659-873ec72e151f
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-type: BlockBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 500 Internal Server Error
   Connection: keep-alive
   Content-Length: 0
   Date: Wed, 13 Dec 2023 06:21:03 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/13 06:21:04 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:04 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0.5237
2023/12/13 06:21:06 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:06 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0
2023/12/13 06:21:08 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:08 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0
2023/12/13 06:21:10 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:10 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0
2023/12/13 06:21:12 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:12 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0
2023/12/13 06:21:14 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:14 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0
2023/12/13 06:21:15 ==> REQUEST/RESPONSE (Try=1/10.9187ms, OpTime=14.6506ms) -- RESPONSE STATUS CODE ERROR
   PUT http://devstoreaccount1.server5:10000/data/__Blogging.sdf?se=2023-12-13T07%3A03%3A16Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13T06%3A03%3A16Z&sv=2021-12-02
   Accept: application/xml
   Content-Length: 131072
   Content-Type: application/octet-stream
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: d456358d-7ec4-4c07-4e77-d62faa7e5f2b
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-type: BlockBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 500 Internal Server Error
   Connection: keep-alive
   Content-Length: 0
   Date: Wed, 13 Dec 2023 06:21:15 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/13 06:21:16 ==> REQUEST/RESPONSE (Try=1/123.0334ms, OpTime=124.9326ms) -- RESPONSE STATUS CODE ERROR
   PUT http://devstoreaccount1.server5:10000/data/_Blogging.sdf?se=2023-12-13T07%3A03%3A16Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13T06%3A03%3A16Z&sv=2021-12-02
   Accept: application/xml
   Content-Length: 131072
   Content-Type: application/octet-stream
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: 375f3474-86e6-490a-6659-873ec72e151f
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-type: BlockBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 500 Internal Server Error
   Connection: keep-alive
   Content-Length: 0
   Date: Wed, 13 Dec 2023 06:21:16 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/13 06:21:16 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:16 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 1.0469
2023/12/13 06:21:18 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:18 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0
2023/12/13 06:21:20 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:20 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:22 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:22 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:24 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:24 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:26 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:26 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:28 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:28 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:30 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:30 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:32 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:32 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:34 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:34 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:36 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:36 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:38 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:38 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:40 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:40 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:41 ==> REQUEST/RESPONSE (Try=1/16.7865ms, OpTime=23.5965ms) -- RESPONSE STATUS CODE ERROR
   PUT http://devstoreaccount1.server5:10000/data/__Blogging.sdf?se=2023-12-13T07%3A03%3A16Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13T06%3A03%3A16Z&sv=2021-12-02
   Accept: application/xml
   Content-Length: 131072
   Content-Type: application/octet-stream
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: d456358d-7ec4-4c07-4e77-d62faa7e5f2b
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-type: BlockBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 500 Internal Server Error
   Connection: keep-alive
   Content-Length: 0
   Date: Wed, 13 Dec 2023 06:21:41 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/13 06:21:42 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:42 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0.5228 (Disk may be limiting speed)
2023/12/13 06:21:44 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:44 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:45 ==> REQUEST/RESPONSE (Try=1/19.7081ms, OpTime=20.7046ms) -- RESPONSE STATUS CODE ERROR
   PUT http://devstoreaccount1.server5:10000/data/_Blogging.sdf?se=2023-12-13T07%3A03%3A16Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13T06%3A03%3A16Z&sv=2021-12-02
   Accept: application/xml
   Content-Length: 131072
   Content-Type: application/octet-stream
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: 375f3474-86e6-490a-6659-873ec72e151f
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-type: BlockBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 500 Internal Server Error
   Connection: keep-alive
   Content-Length: 0
   Date: Wed, 13 Dec 2023 06:21:45 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/13 06:21:46 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:46 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0.5238 (Disk may be limiting speed)
2023/12/13 06:21:48 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:48 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:50 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:50 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:52 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:52 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:54 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:54 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:56 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:56 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:21:58 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:21:58 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:00 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:00 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:02 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:02 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:04 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:04 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:06 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:06 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:08 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:08 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:10 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:10 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:12 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:12 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:14 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:14 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:16 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:16 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:18 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:18 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:20 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:20 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:22 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:22 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:24 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:24 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:26 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:26 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:29 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:29 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:31 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:31 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:33 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:33 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:35 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:35 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:37 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:37 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:39 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:39 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:41 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:41 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:41 ==> REQUEST/RESPONSE (Try=1/8.2503ms, OpTime=15.621ms) -- RESPONSE STATUS CODE ERROR
   PUT http://devstoreaccount1.server5:10000/data/__Blogging.sdf?se=2023-12-13T07%3A03%3A16Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13T06%3A03%3A16Z&sv=2021-12-02
   Accept: application/xml
   Content-Length: 131072
   Content-Type: application/octet-stream
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: d456358d-7ec4-4c07-4e77-d62faa7e5f2b
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-type: BlockBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 500 Internal Server Error
   Connection: keep-alive
   Content-Length: 0
   Date: Wed, 13 Dec 2023 06:22:41 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/13 06:22:43 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:43 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0.5236 (Disk may be limiting speed)
2023/12/13 06:22:45 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:45 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:45 ==> REQUEST/RESPONSE (Try=1/19.3777ms, OpTime=20.9447ms) -- RESPONSE STATUS CODE ERROR
   PUT http://devstoreaccount1.server5:10000/data/_Blogging.sdf?se=2023-12-13T07%3A03%3A16Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13T06%3A03%3A16Z&sv=2021-12-02
   Accept: application/xml
   Content-Length: 131072
   Content-Type: application/octet-stream
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: 375f3474-86e6-490a-6659-873ec72e151f
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-type: BlockBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 500 Internal Server Error
   Connection: keep-alive
   Content-Length: 0
   Date: Wed, 13 Dec 2023 06:22:45 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/13 06:22:47 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:47 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0.5225 (Disk may be limiting speed)
2023/12/13 06:22:49 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:49 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:51 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:51 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:53 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:53 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:55 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:55 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:57 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:57 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:22:59 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:22:59 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:01 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:01 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:03 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:03 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:05 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:05 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:07 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:07 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:09 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:09 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:11 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:11 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:13 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:13 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:15 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:15 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:17 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:17 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:19 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:19 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:21 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:21 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:23 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:23 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:25 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:25 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:27 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:27 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:29 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:29 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:31 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:31 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:33 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:33 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:35 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:35 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:37 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:37 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:39 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:39 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:41 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:41 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:41 ==> REQUEST/RESPONSE (Try=1/13.1082ms, OpTime=19.6657ms) -- RESPONSE STATUS CODE ERROR
   PUT http://devstoreaccount1.server5:10000/data/__Blogging.sdf?se=2023-12-13T07%3A03%3A16Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13T06%3A03%3A16Z&sv=2021-12-02
   Accept: application/xml
   Content-Length: 131072
   Content-Type: application/octet-stream
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: d456358d-7ec4-4c07-4e77-d62faa7e5f2b
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-type: BlockBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 500 Internal Server Error
   Connection: keep-alive
   Content-Length: 0
   Date: Wed, 13 Dec 2023 06:23:41 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/13 06:23:43 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:43 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0.5221 (Disk may be limiting speed)
2023/12/13 06:23:45 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:45 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:45 ==> REQUEST/RESPONSE (Try=1/16.2187ms, OpTime=16.2187ms) -- RESPONSE STATUS CODE ERROR
   PUT http://devstoreaccount1.server5:10000/data/_Blogging.sdf?se=2023-12-13T07%3A03%3A16Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13T06%3A03%3A16Z&sv=2021-12-02
   Accept: application/xml
   Content-Length: 131072
   Content-Type: application/octet-stream
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: 375f3474-86e6-490a-6659-873ec72e151f
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-type: BlockBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 500 Internal Server Error
   Connection: keep-alive
   Content-Length: 0
   Date: Wed, 13 Dec 2023 06:23:45 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/13 06:23:47 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:47 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0.5221 (Disk may be limiting speed)
2023/12/13 06:23:49 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:49 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:51 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:51 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:53 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:53 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:55 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:55 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:57 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:57 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:23:59 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:23:59 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:01 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:01 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:03 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:03 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:05 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:05 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:07 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:07 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:09 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:09 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:11 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:11 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:13 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:13 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:15 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:15 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:17 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:17 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:19 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:19 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:21 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:21 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:23 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:23 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:25 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:25 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:27 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:27 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:29 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:29 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:31 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:31 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:33 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:33 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:35 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:35 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:37 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:37 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:39 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:39 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:41 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:41 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:41 ==> REQUEST/RESPONSE (Try=1/19.0894ms, OpTime=25.3359ms) -- RESPONSE STATUS CODE ERROR
   PUT http://devstoreaccount1.server5:10000/data/__Blogging.sdf?se=2023-12-13T07%3A03%3A16Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13T06%3A03%3A16Z&sv=2021-12-02
   Accept: application/xml
   Content-Length: 131072
   Content-Type: application/octet-stream
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: d456358d-7ec4-4c07-4e77-d62faa7e5f2b
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-type: BlockBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 500 Internal Server Error
   Connection: keep-alive
   Content-Length: 0
   Date: Wed, 13 Dec 2023 06:24:41 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/13 06:24:43 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:43 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0.5233 (Disk may be limiting speed)
2023/12/13 06:24:45 ==> REQUEST/RESPONSE (Try=1/14.5308ms, OpTime=14.5308ms) -- RESPONSE STATUS CODE ERROR
   PUT http://devstoreaccount1.server5:10000/data/_Blogging.sdf?se=2023-12-13T07%3A03%3A16Z&sig=-REDACTED-&sp=rwl&spr=https%2Chttp&srt=sco&ss=b&st=2023-12-13T06%3A03%3A16Z&sv=2021-12-02
   Accept: application/xml
   Content-Length: 131072
   Content-Type: application/octet-stream
   User-Agent: AzCopy/10.22.0 azsdk-go-service.Client/v1.2.0 (go1.19.12; Windows_NT)
   X-Ms-Client-Request-Id: 375f3474-86e6-490a-6659-873ec72e151f
   x-ms-blob-content-type: application/octet-stream
   x-ms-blob-type: BlockBlob
   x-ms-version: 2023-08-03
   --------------------------------------------------------------------------------
   RESPONSE Status: 500 Internal Server Error
   Connection: keep-alive
   Content-Length: 0
   Date: Wed, 13 Dec 2023 06:24:45 GMT
   Keep-Alive: timeout=5
   Server: Azurite-Blob/3.28.0
Response Details:

2023/12/13 06:24:45 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:45 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0.5221 (Disk may be limiting speed)
2023/12/13 06:24:47 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:47 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:49 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:49 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:51 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:51 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:53 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:53 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:55 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:55 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:57 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:57 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:24:59 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:24:59 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:01 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:01 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:03 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:03 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:05 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:05 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:07 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:07 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:09 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:09 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:11 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:11 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:13 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:13 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:15 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:15 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:17 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:17 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:19 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:19 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:21 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:21 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:23 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:23 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:25 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:25 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:27 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:27 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:29 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:29 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)
2023/12/13 06:25:31 PERF: primary performance constraint is Disk. States: X:  0, O:  0, M:  0, L:  0, R:  0, D:  2, W:  0, F:  0, B:  0, E:  0, T:  2, GRs: 300
2023/12/13 06:25:31 33.3 %, 1 Done, 0 Failed, 2 Pending, 3 Total, 2-sec Throughput (Mb/s): 0 (Disk may be limiting speed)

Hi @InteXX ,
It should AzCopy's issue, which cannot parse the URL you provided correctly. We just help to provide a work around.
For the 500 error,  the log you shared is from AzCopy? Could you share Azurite's debug log to help us on investigation?
Thanks
Emma

@EmmaZhu
@gapra-msft
May I say that I'm fast growing weary of being bounced around between various Microsoft teams, each blaming the other for a problem that should be debugged and fixed internally.
How do I get Azurite's debug log?

Totally understand.
For Azurite's debug log, you can get it with the -d <logpath> when starting Azurite. https://github.com/azure/azurite#debug-log-configuration

Oh. My. Gosh.
I have no idea how or why, but suddenly it started working. I added the --debug switch, and for some odd reason that seems to have fixed everything. My azcopy sync command is now working correctly and reliably.
I should note that the debug log is only written to at Azurite startup, with these four lines:
2023-12-13T13:36:27.418Z 	 info: Azurite Blob service is starting on <IP_ADDRESS>:10000
2023-12-13T13:36:27.419Z 	 info: AccountDataStore:init() Refresh accounts from environment variable AZURITE_ACCOUNTS with value undefined
2023-12-13T13:36:27.419Z 	 info: AccountDataStore:init() Fallback to default emulator account devstoreaccount1.
2023-12-13T13:36:27.461Z 	 info: BlobGCManager:start() Starting BlobGCManager. Set status to Initializing.

Other activities, e.g. uploads, downloads, etc. using Storage Explorer don't make it to the log.
Here's my Azurite startup command:
PowerShell -command "Start-Process azurite-blob.cmd -PassThru -ArgumentList '--silent --skipApiVersionCheck --blobHost <IP_ADDRESS> --location D:\Azurite --debug D:\Logs\Azurite\Debug.log'"

I encountered the same issue and it did not fix itself when enabling azurite's debug logs. Here is -- as far as I can tell -- the relevant part:
2024-01-09T08:50:36.318Z 11a841a4-55c5-449f-b3ef-0bc9c1aa2f34 debug: BlobSASAuthenticator:validate() Retrieved signature from URL parameter sig: 4bePhs+oVRC+ZhCr/WwhIIAU37jRSJ2V45rfAuBf4tE=
2024-01-09T08:50:36.318Z 11a841a4-55c5-449f-b3ef-0bc9c1aa2f34 debug: BlobSASAuthenticator:validate() Signed resource type is c.
2024-01-09T08:50:36.318Z 11a841a4-55c5-449f-b3ef-0bc9c1aa2f34 debug: BlobSASAuthenticator:validate() Successfully got valid blob service SAS values from request. {"version":"2023-11-03","expiryTime":"2024-01-10T08:50:35Z","permissions":"rwl","containerNam
e":"amulet","blobName":"projects/test_project/amlt-code/14128e8d0fc8a888ca51c65656c12c93/not_ignored_folder/valid.txt","signedResource":"c"}
2024-01-09T08:50:36.318Z 11a841a4-55c5-449f-b3ef-0bc9c1aa2f34 info: BlobSASAuthenticator:validate() Validate signature based account key1.
2024-01-09T08:50:36.318Z 11a841a4-55c5-449f-b3ef-0bc9c1aa2f34 debug: BlobSASAuthenticator:validate() String to sign is: "rwl\n\n2024-01-10T08:50:35Z\n/blob/devstoreaccount1/amulet\n\n\n\n2023-11-03\nc\n\n\n\n\n\n"
2024-01-09T08:50:36.318Z 11a841a4-55c5-449f-b3ef-0bc9c1aa2f34 debug: BlobSASAuthenticator:validate() Calculated signature is: ZXhOqB6YJipo7kddfBZuf9j+c/vYYYdTqItnk2R45fA=
2024-01-09T08:50:36.318Z 11a841a4-55c5-449f-b3ef-0bc9c1aa2f34 info: BlobSASAuthenticator:validate() Signature based on key1 validation failed.
2024-01-09T08:50:36.319Z 11a841a4-55c5-449f-b3ef-0bc9c1aa2f34 error: ErrorMiddleware: Received a MiddlewareError, fill error information to HTTP response
2024-01-09T08:50:36.319Z 11a841a4-55c5-449f-b3ef-0bc9c1aa2f34 error: ErrorMiddleware: ErrorName=StorageError ErrorMessage=Server failed to authenticate the request.

The error started to appear after upgrading azurite to the newest version.

Hi @temporaer ,
Can you open a new one to track your issue?
Can you also share more details about your issue:

Azurite version
Node.JS version
OS version
Whole debug log
Error you got. A small repro would be perfect if possible.

Thanks
Emma


Changes in Django do not trigger a rebuild until now dev is restarted manually

Using the python-django example https://github.com/zeit/now-examples/tree/master/python-django, any changes in the project files require now dev to be stopped and restarted before it is rebuilt.

related to https://github.com/zeit/now-builders/issues/413
since only the app.py file is watched for update
{"src":"app.py","use":"@now/python","config":{"maxLambdaSize":"15mb"}}


Convert Calendar tests to Minitest

This effectively reverts https://github.com/alphagov/calendars/pull/852 and converts all the tests for the calendars pages from RSpec back to Minitest (sorry @barrucadu).
The reason for doing this is because currently this application has both Minitest and RSpec which is confusing for developers. It can also cause problems where CI only runs half of the tests: https://github.com/alphagov/frontend/pull/2472
Once this and #2477 are merged we can remove RSpec from this repo.

@barrucadu Thanks, I think your comments should be resolved now!


[MRG] [Feat] Fix #3 workflow patch

🎉 New feature for workflow patch
You can run this simple script
import augly.text as textaugs

from dataci.plugins.decorators import stage

@stage
def text_augmentation(df):
    aug_function = textaugs.OneOf([
        textaugs.ReplaceSimilarUnicodeChars(),
        textaugs.SimulateTypos(),
    ])
    df['text'] = aug_function(df['text'].tolist())

    return df

if __name__ == '__main__':
    from dataci.models import Dataset
    from example.text_process.text_process_ci import text_process_ci_pipeline

    print('Prepare the input streaming dataset...')
    yelp_review_dataset = Dataset('yelp_review', dataset_files=[
        {'date': '2020-10-05 00:44:08', 'review_id': 'HWRpzNHPqjA4pxN5863QUA', 'stars': 5.0,
         'text': "I called Anytime on Friday afternoon about the number pad lock on my front door. After several questions, the gentleman asked me if I had changed the battery.", },
        {'date': '2020-10-15 04:34:49', 'review_id': '01plHaNGM92IT0LLcHjovQ', 'stars': 5.0,
         'text': "Friend took me for lunch.  Ordered the Chicken Pecan Tart although it was like a piece quiche, was absolutely delicious!", },
        {'date': '2020-10-17 06:58:09', 'review_id': '7CDDSuzoxTr4H5N4lOi9zw', 'stars': 4.0,
         'text': "I love coming here for my fruit and vegetables. It is always fresh and a great variety. The bags of already diced veggies are a huge time saver.", },
    ]).publish(version_tag='2020-10')
    print(yelp_review_dataset)

    print('Patch the pipeline with new version of `text_augmentation`...')
    print('Before patch:', text_process_ci_pipeline, 'fingerprint:', text_process_ci_pipeline.fingerprint)
    text_process_ci_pipeline.patch(text_augmentation=text_augmentation)
    print('Before patch:', text_process_ci_pipeline, 'fingerprint:', text_process_ci_pipeline.fingerprint)
    print('Test the new pipeline locally...')
    text_process_ci_pipeline.test()

log:

At the red arrow, it opens a pager for the user to inspect the auto-applied changes

    print('Patch the pipeline with new version of `text_augmentation`...')
    print('Before patch:', text_process_ci_pipeline, 'fingerprint:', text_process_ci_pipeline.fingerprint)
    text_process_ci_pipeline.patch(text_augmentation=text_augmentation)
    ### after patch?
    print('Before patch:', text_process_ci_pipeline, 'fingerprint:', text_process_ci_pipeline.fingerprint)
    print('Test the new pipeline locally...')
    text_process_ci_pipeline.test()

    print('Patch the pipeline with new version of `text_augmentation`...')

    print('Before patch:', text_process_ci_pipeline, 'fingerprint:', text_process_ci_pipeline.fingerprint)

    text_process_ci_pipeline.patch(text_augmentation=text_augmentation)

    ### after patch?

    print('Before patch:', text_process_ci_pipeline, 'fingerprint:', text_process_ci_pipeline.fingerprint)

    print('Test the new pipeline locally...')

    text_process_ci_pipeline.test()

Yes after patch, see the updated example code at the PR description. The typo blames to my Copilot.


ARROW-12955:  [C++] Add additional type support for if_else kernel

This PR adds fixed and variable binary type support

@pitrou @lidavidm I made some changes to the code. As Antoine pointed out previously, the null values in the output string array would have non-empty slots in the data buffer. I think it requires a small fix. I'll add that here as well. But I'd like to get your feedback on the code flow.

N.B. it looks like this segfaults in the tests on Windows MSVC 2019 (https://github.com/apache/arrow/pull/10538/checks?check_run_id=2966481230#step:8:339) and there are various errors on Clang, MSVC, and MinGW (mostly related to implicit casts or needing to explicitly parameterize std::max).

Looks like this also needs to be rebased now. But once that's done and the nits above are addressed I think this can be merged.


Support for vanilla js

Are there any plans in the future support for vanilla js?

Sorry, but this this is not planned feature. Strongly typed languages are priority.

Thanks for the reply


Will a small batchsize reduce the accuracy?

I only have one GPU, so batchsize is set to 1. Does this have a serious impact on the result?

according to my experiments, large batchsize will improve the accuracy and the training process will be much easier. 1 batchsize will be very hard to train.


The description for how to make flux dust is incredibly unclear.

It needs to be more clear. I was only able to figure out what I was supposed to do after I spent a while googling, and the only helpful place happened to be one of the closed issues on here.

There is a link named 'here' to github page on curseforge which contains how to get flux, and I will add a more detailed info in JEI


Configuring Eureka-Client for Cloudfoundry

In many examples (even on http://cloud.spring.io/spring-cloud-netflix/1.0.x/) I found
eureka.instance.hostname: ${vcap.application.uris[0]}
Isn't this working against Ribbon?
In my understanding the address of the cf-loadbalancer is set as the hostname.
So Ribbon would have multiple instances with the same address (which is actually a server-side loadbalancer in a client-side loadbalancing context).
Wouldn´t it make more sense to use
eureka.instance.hostname: ${vcap.application.instance.hostname}:${vcap.application.port}
I was also searching for an equivalent for CF_INSTANCE_ADDR (https://docs.run.pivotal.io/devguide/deploy-apps/environment-variable.html#CF-INSTANCE-ADDR), but I didn't find any.

@elgohr in the early days of Spring Cloud, direct addressing of CF instances wasn't possible. The cf route was the only way, and yes that is redundant. Now, with the right version of CF and the right settings, you can address the instances directly. I'm not CF guru, someone else would have to help there.

@spencergibb, @elgohr, just to add a little more information based on my understanding - if two app instances are on the same diego cell in CF, they cannot reach other directly using the ip/port. If they happen to be on different diego cell's then this will work. That is the reason why the direct call is discouraged in CF/PCF and instead the call is routed via the go routers. @scottfrederick will have a better answer based on his experience with Spring Cloud Services.
This likely will be mitigated when Container networking is implemented in CF/PCF

Thanks @bijukunjummen
This:

This likely will be mitigated when Container networking is implemented in CF/PCF

is what I meant when I said

with the right version of CF and the right settings, you can address the instances directly. I'm not CF guru

Thank you very much, sounds promising.
By the way, is there any overview of the ${vcap.* - variables? I tried to guess some from the documented cf-variables.
I was a bit confused because the instance ID is configured as hostname by default.

Thank you very much, sounds promising.
By the way, is there any overview of the ${vcap.* - variables? I tried to guess some from the documented cf-variables.
I was a bit confused because the instance ID is configured as hostname by default.

I'm sure there is, but I'm not sure where to find it.


Skip logic cannot be specified for non-input elements

Skip logic cannot be specified for non-input elements, but is this reasonable? I'm using the survey tool to simply walk people through all of the Azores OUS heatmaps without soliciting input from them. If they select "Flores Island", I want to show them a bunch of maps, one after the other, showing activities around Flores Island. Then, I want to direct them to the "submit" page. However, there's no way for me to do that because there are other forms that follow (and I'd like to skip).

See https://next.seasket.ch/blueazores/admin/surveys/157
I realize this is a bit of an unintended use of the Survey Tool, but doesn't it make sense that we should be able to skip from any question to the next? Let's discuss.

Give that change a try. I haven't tested the actual performance of the skip logic yet when running through a survey but it should be functional now.


Fix ON/OFF switch jump in new merge datasets modal

Fixes #4215

Frontend tests were OK :+1: (details)

Frontend tests were OK :+1: (details)

@xavijam :eyes:

:point_up: :eyes: @javierarce

:+1:


fix changelog ordering

fixes  #559

@moerketh. Does this issue fully resolves #559? :)

Looks good to me. What do you think @madkoo?

@Alexander-Hjelm it does, but I did not test this with Jira Cloud (only with Jira Server 8). However, I do not expect issues because of the API versioning. Jira Cloud specific things should be on the v3 not the v2 REST API.

@Alexander-Hjelm it does, but I did not test this with Jira Cloud (only with Jira Server 8). However, I do not expect issues because of the API versioning. Jira Cloud specific things should be on the v3 not the v2 REST API.

I'll run some tests against our jira cloud instance once we merge this into a new feature branch in the base repo. That should give us enough confidence to merge.


docs: Expand on filesystem /var

Let's talk about the /var trap more.

Test failure is caused by two reasons:

testing farm can't deploy nested ARM machine to run test since Saturday. QE CI failed lots of tests this weekend with the same issue.
quay.io/fedora/fedora:40 image changed. Package sudo has not be installed (log: http://artifacts.osci.redhat.com/testing-farm/a7409509-aaaf-4632-b1cc-6459b2e9ce43/). I filed a bug https://bugzilla.redhat.com/show_bug.cgi?id=2269960 and mark it as testBlocker. The sudo should be installed from https://pagure.io/fedora-kickstarts/blob/f40/f/fedora-container-base.ks#_12. I don't know what happened in the new Fedora 40 image. But I have a PR https://github.com/containers/bootc/pull/396 to remove sudo to workaround this issue.


Inline display: contents is very common

Many elements on Web use display: 'contents'. I wonder if this should be put it a class name instead of going inline as a style attribute?

Fixed in 51d233da9b4bb979008202db522788cfa21cae64 beta.211


Decoding B2-Four presets

From #64 we have a download of a preset, which shows that the format is slightly different. The preset includes a PRM2 (instead of PPRM) block and a NAME block.
Changes pushed for decode_preset.py so they can be parsed, but the output doesn't make sense. Volume of '0' is probably wrong.
None

    name = u'DamnTime20' (total 10)
    ids = ListContainer:
        33554560 => 0x2000080
        67108960 => 0x4000060
        83886112 => 0x5000020
        0
        0
        469762064 => 0x1C000010

So are those the IDs of the FX per slot?

So are those the IDs of the FX per slot?

Yes, full decode here...
patch_64.dump.txt

Yes, full decode here...
patch_64.dump.txt

There is a new section NAME which stores a "long name". You may want to extract that too.


Suggestion: Create web and node versions separately

In an attempt to keep unnecessary package creep from happening, it would be very nice if there were two versions or a plugin architecture where we could depend on a version that included or did not included web/browser based rendering.
Some of the dependencies (22 packages in total once flattened; including pretty-error) are not at all needed in a server only environment.

Hmm, I actually made pretty-error only for node, but yes, the dependencies could have browser-specific code.
Taking a look at the dependencies, through RenderKid, we get to htmlparser2 and css-select. The first one parses XML which is one of the inputs that RenderKid accepts. The second one is a simple utility to parse and apply css selectors. Since RenderKid creates XML documents and styles them with CSS, I don't see how we can skip either of these dependencies.

@AriaMinaei wow, ok, I admit I didn't look at the code but I never suspected you'd be using XML of all things to make it work. I guess that makes sense.


IE, Edge - selection of year in datepickers work incorrectly in Snapshots and Activity log

Description
In IE and Edge browsers if you set the russian language in settings and go to selection of a year in datepicker in Snapshots or in Activity log you will get the wrong display and behavior of datepicker
Steps to reproduce

Log in and set the russian language in the Settings
Go to Activity log/Snapshots
Open the datepicker
Click to year
Click to any year in the list

Actual result

1. When you open the years list in datepicker:

the symbols "г." are displayed next to every year like "1994 г."
the list is displayed from the beginning
the current year isn't highlighted: font size and color are the same as for all years

2. When you click to any year the selected year isn't saved and the empty calendar is displayed
Expected result

(!) Expected result shouldn't depend on environment or language in the system
1. When you open the years list in datepicker:

the year is displayed without any letters, just numbers of the year like "1994"
the part of the list in which the current year is located is displayed: current year in the middle of displayed list, a few years before and a few years after the current year
the current year is highlighted: font size is larger than the others, color is blue

2. When you click to any year the selected year is saved and the calendar is displayed with highlighted selected current date
Environment

Browser:
- [ ] IE version XX
- [ ] Edge version XX

Connected feature ID
volsnapshot_list_datepicker
activitylog_datepicker_display
activitylog_datepicker_change
settings_language_change
Screenshots

Actual result:

Expected result:

To test:
volsnapshot_list_datepicker
activitylog_datepicker_display
activitylog_datepicker_change
settings_language_change

Tested on 1311


Better widget for ManyToMany fields

The current M2M widget is all right for a small number of items, but it would be nice to have an autosuggest field instead.

Covered by #231

I opened a separate ticket because that seemed like it dealt explicitly with many-to-many throughs and wasn't considering simple M2Ms. But seeing as you're the one who actually knows what's going on I will defer to your knowledge. :-)

Hi @melinath, we appreciate the feedback. :) It looks like @gasman is referring to this comment where "a better UI widget" is mentioned. It would be valuable to make note of including a search feature, which I agree would be an improvement.
I'm guessing that isn't possible yet, though, until #231 is covered.
Thanks! Please let us know if you have any more ideas.

django-ajax-select is a beautiful implementation of an auto-suggest field.
I was able to make it work in Wagtail admin with a simple :
       FieldPanel('people', widget=AutoCompleteSelectMultipleWidget('people')),
... then I was bitten by issue #231...

@dperetti do you have any sample app done with Wagtail and django-ajax-selects? I'm using it to select an m2m value but for some reason it doesn't get saved to the db.


Version issues

Hi, this doesn't work when following the installation.
The package downloaded from npm contains an old version of CheckBox.js without the newest PR to fix proptypes.
Workaround:
npm install git+https://github.com/ismayilmalik/react-native-checkbox-heaven.git --save

@hegelstad Is there a more permanent solution than this? I have to re-run this command each time I use react-native link.

I have updated npm repo, thanks!


[FIX] Compile error involving a missing include

The plugin would not compile on our 5.1 config because of the unrecognized identifier FAppStyle.
This was fixed by adding a missing include in NYEngineVersionHelpers.h.

Thx but github is just a mirror, not the place to raise PRs.
https://gitlab.com/NotYetGames/DlgSystem


fix(#28): implement 64-bit stable memory support

This change implements 64 bit stable memory API.
ic0.stable64_size : () -> (page_count : i64);                               // *
ic0.stable64_grow : (new_pages : i64) -> (old_page_count : i64);            // *
ic0.stable64_write : (offset : i64, src : i64, size : i64) -> ();           // *
ic0.stable64_read : (dst : i64, offset : i64, size : i64) -> ();            // *

NOTE: We mostly need this API for spec compliance, I didn't dare to
allocate real 5GiB Haskell arrays on my machine. We need a more
efficient, sparse Memory implementation to test this properly.
Fixes #28.

The code uses exactly the same implementation for 32 and for 64 bit APIs.

I thought the spec says that the 32 bit variants will always trap (even if they could do something useful otherwise) if the stable memory is larger than 2^32 bytes. These checks probably need to be added to the system api implementation. At that point duplicating the four functions in src/IC/Canister/Imp.hs  might be cleaner than overloading, this way the code stays closer to the pseudo-code in the spec.

Looks good! I might have used mutable vectors instead of ptr stuff.
Kudos for writing a unit test suite!


Update scdoc runtime files

Disable conceal by default
Don't highlight indent for list continuation as an error
Add upstream link to file headers
Highlight errors in malformed tables

I'll include it, thanks.


Routing to Existing Page

Currently, clicking a link to the page you're on does nothing. In my app, I would like it to "reload" the page. For example, clicking a menu item in most websites will reload the page (get you back to a known state).

Closing this issue because it's related to an old router version. Please update to the latest @riotjs/route version if you can.


What are the functions of these two APIs：GET  /serverinfo/statusoverrides and PUT /{version}/asg/{asgName}/status?

<IP_ADDRESS>:18080


removed translation and locale middleware

removed translation and locale middleware

Pull Request Test Coverage Report for Build 1024

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage increased (+1.2%) to 67.797%

Files with Coverage Reduction
New Missed Lines
%

libraries/botframework-config/src/botConfiguration.ts
2
87.39%

Totals

Change from base Build 1014:
1.2%

Covered Lines:
2049

Relevant Lines:
2849

💛  - Coveralls

Added branch https://github.com/Microsoft/botbuilder-js/tree/johtaylo/translation-sample with these file on it.


Raise an error if perticular environment variables referenced with import.meta.env.VITE_VAR are undefined

Clear and concise description of the problem
Vite doesn't complain when building an app with environment variables missing, they simply become undefined at runtime. It would be nice if Vite could notify users of missing environment variables which are referenced with import.meta.env.VITE_VAR.
Also the docs on IntelliSense for TypeScript suggest the following:
/// <reference types="vite/client" />

interface ImportMetaEnv {
  readonly VITE_APP_TITLE: string
  // more env variables...
}

interface ImportMeta {
  readonly env: ImportMetaEnv
}

but it is esentially lying as the value could be undefined.
Suggested solution
A config option that when enabled would raise an error if an environment variable was missing. This could be for all environment variables or just a subset.
Alternative
Type it like this readonly VITE_APP_TITLE: string | undefined and do a runtime check to see if the value is undefined or not.
Additional context
No response
Validations

[X] Follow our Code of Conduct
[X] Read the Contributing Guidelines.
[X] Read the docs.
[X] Check that there isn't already an issue that request the same feature to avoid creating a duplicate.

While I think this can be easily achieved in dev via a Proxy for import.meta.env, on the other hand you should be in charge of the variables and type them accordingly. Implementing this could cause false positives too if someone intentionally wants it undefined and there's no way to disable it. I'd be open to hear what other think about this though.


Chang bable-eslint to fixed error.

Fixed error modulesTypeError: Cannot read property 'visitClass' of undefined

@tinhanchanachai Thanks!


Support for zarr datasets, in particular zspy (ZARR Hyperspy) in the GUI

It seems that Zarr is replacing HDF5 in HyperSpy, in particular for large data.
LiberTEM does support that for scripting through the HyperSpy lazy loader and Dask array integration. However, in the GUI it is not available. That would be useful to preview and process such files.
This could be implemented natively similar to HDF5, or through the HyperSpy reader and Dask array interface. Zarr support seems to be quite similar to HDF5, including paying attention to align partitions and processing with the chunking scheme.

See also #997


ci(TypeScript): Added dangerfile.ts to the excluded files

The danger script should not be used by the awesome-typescript-loader so we need to add the file to excluded files in the tsconfig.json

Fails

:no_entry_sign:
This pull request needs an assignee!

Messages

:book:
:pencil: Changed Files:
- dangerfile.ts
- tsconfig.json

:book:

:heavy_check_mark: Pull request is ready to merge!

  Generated by :no_entry_sign: dangerJS against 4c5ab75c40a421fec0aa3aecb499d969d9aa1441


localCI: make the logs generated in each stage accesible

in order to make the logs generated in each testing stage
this patch change the mode of the log directory to 0755 and
the mode of the log files to 0664
fixes #197
Signed-off-by: Julio Montes<EMAIL_ADDRESS>

lgtm


Regarding version issues

Hello, thank you for disclosing your research findings
I have a question to as

When I use torch=1.9.0 and torch vision=0.10.1, it displays the following error

The problem doesn't seem to be caused by DOConv, you should probably look at the rest of the code:)


[ADDON] - Falco

Add support for cloud-native runtime security with Falco via an add-on.

Closing the issue as the addon is implemented.


The build issue that occurs after updating the MongoCSharpDriver

Describe the bug
An error occurred when updating from mongocharpdriver-2.27 to 2.28 as below;
CS0012	The type 'ObjectId' is defined in an assembly that is not referenced. You must add a reference to assembly 'MongoDB.Bson, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'
To Reproduce
Steps to reproduce the behavior:

Go to 'Nuget Update'
Click on 'MongoCSharpDriver 2.28.0'

Expected behavior
As before, we expect it to work in concert without any problems.
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

.Net Core version: [.Net Core 8.0]
Package Version: [8.3.3]

Same issue. Just discovered this.

hi there, next versions has fixed this issue:
v8.3.5
v9.0.0
@SteAmeR  v9.0.0 supports Net8, so I advice you to upgrade to this version directly instead of 8.3.5


idea: split seed into smaller crates

Currently seed has "all batteries included" that is great for a lot of use-cases but in some cases I just want to use some core functionalities.
Can we split up seed at least into two crates? e.g.

seed-core - basic vdom and event handling
seed-batteries - fetch, routing, storage, markdown etc.

The default seed crate would remain as a all-in crate.

How did you get this idea? Do you want to use custom libs? Strip WASM size? ..

This batteries-included approach was deliberate, with the intent of maximizing ease-of-use. If there are concrete benefits to splitting that outweigh this, like the ones Martin suggested, we'll consider.

How did you get this idea? Do you want to use custom libs? Strip WASM size? ..

There are actually two reasons:

because I consider to use reqwest
because I think that the overall architecture improves if we are forced to build clean interfaces.

But for now there are probably more important things to do, so I'm totally fine to close this issue.

You should be able to use reqwest without the builtin, web_sys-based fetch module interfering, once it fully supports wasm. Worth giving it a shot, now, or once they improve WASM functionality.

because I consider to use reqwest

Just some info if you haven't seen it yet: https://github.com/David-OConnor/seed/issues/226.

because I think that the overall architecture improves if we are forced to build clean interfaces.

actix -web is a good example.
But I think it would slow down us now. I have bad experience from the world of microservices - if you try to split monolith into parts (i.e. define clean interfaces) before you see boundaries clearly, it turns into a mess and versioning / administration hell.
So I suggest to wait until Seed is battle-tested enough or/and adding new libraries (reqwest, gloo libs, ..) becomes too painful. And maybe it would be nice to implement this idea together with https://github.com/David-OConnor/seed/issues/246.

So I suggest to wait until Seed is battle-tested enough or/and adding new libraries (reqwest, gloo libs, ..) becomes too painful. And maybe it would be nice to implement this idea together with #246.

I agree! So I'll close this issue for now.


Use reshape to re-implement squeeze

@huningxin, @ibelem, PTAL, thanks!

@huningxin, thanks for your comments, PTAL again.


[SYSTEMML-1491] Add different ReLU variants ELU

Added ELU activation
Added Reference Paper
Added forward test
Added backward test

@niketanpansare @dusenberrymw could you please review this?.

@niketanpansare, @dusenberrymw thank for your feedback. Will make the necessary changes shortly.

@niketanpansare @dusenberrymw have implemented the gradient checks for ELU now and will tackle PReLU in a separate PR.
The functions and the gradients were compared against pytorch here.

Refer to this link for build results (access rights to CI server needed):
https://sparktc.ibmcloud.com/jenkins/job/SystemML-PullRequestBuilder/2272/

LGTM wrt my comments :+1:  ... @dusenberrymw, unless you object, I will merge this next week.

@krishnakalyan3 Thanks for adding tests.  The forward function test compared against PyTorch looks great.  However, can you please add a random automated gradient test in the nn/test/gradcheck.dml in the style of those tests?  The overall idea is that the forward functions can be compared to another implementation for correctness, and then the gradient tests can be automated for random values to ensure that the backward functions are correct w.r.t. their corresponding forward functions.

Add gradient tests in nn/test/gradcheck.dml. The ReLU test can be copied and adapted for the ELU function, and the affine layer test could be copied and adapted for the PReLU. These will ensure that the backward functions are computing the correct derivatives.

@dusenberrymw added gradient checks.

Refer to this link for build results (access rights to CI server needed):
https://sparktc.ibmcloud.com/jenkins/job/SystemML-PullRequestBuilder/2274/

@krishnakalyan3 Sorry for the delay on this.  One last thing and this can be merged (pending passing tests): please enable the tests in the nn/test/run_tests.dml script by adding one line to call the grad check test in the grad check section, and one line to call the other test in the other test section.  Both sections are in alphabetical order.
Given that, you should be able to run ../bin/systemml nn/test/run_tests.dml from the scripts folder and look for any failures via ERROR... messages.  (Side note: the print statements from these tests used to be in order, but a somewhat recent change caused that to no longer be the case -> cc @mboehm7 as a reminder).  The tests will also be run automatically from Java via the NNTest.java test case once the above 2 lines are added to run_tests.dml.

@dusenberrymw well I thought I fixed it immediately after the 1.0 release by always sorting prints within a DAG according to their line numbers. Anyway, now I know what you mean: after function inlining and merge of DAGs, we end up sorting the prints according to their own line numbers not the line numbers of the original function calls. I'll take care of it.

gentle ping @dusenberrymw. Thank you for the reviews so far :).

Refer to this link for build results (access rights to CI server needed):
https://sparktc.ibmcloud.com/jenkins/job/SystemML-PullRequestBuilder/2306/


bumpversion installation

Should bumpversion be installed at the start of the documentation at http://sdss-python-template.readthedocs.io/en/latest/ in the same way  that invoke is installed? Later in the documentation bumpversion is referred to (in a similar way that invoke is), but bumpversion may not be installed.

I think this is probably a good idea. Arguably the template only needs cookiecutter to be installed (and people may not want to use bumpversion or invoke). In that case maybe the pip install invoke should be moved to the section in which we explain how to use invoke.
Thought? In principle I lean towards doing what Andy suggests.

If we're planning on keeping the template lean, then I lean towards including the bumpversion in the install instructions.  If we start adding more functionality, then this will get large, in which case I'd rather move each pip install into their respective sections.
Other cookiecutter templates provide a bunch of functionality but don't explicitly include the pip installs in their installation instructions.  There merely mention you get this functionality and link to individual package pages.

Sounds good. I have added it to the install instructions.


Upgrade built in mono to 5.18

Mono 5.18 fixes https://github.com/mono/mono/issues/11214, which causes https://github.com/OmniSharp/omnisharp-vscode/issues/2604 in OmniSharp.

@DustinCampbell any interest in taking this on?

This was done as part of #1444 and released