Mahmoud Al-Qudsi

Running under ASAN doesn't report any memory corruption our out-of-bound reads/writes until something (tokio, I think) tries to access an invalid address: ``` AddressSanitizer:DEADLYSIGNAL ================================================================= ==19006==ERROR: AddressSanitizer: SEGV on unknown...

Unfortunately easier said than done. It's an interactive application that requires user input and performs non-repeatable work. The crashes *generally* don't happen right away (though that has occurred); I'll probably...

I don't think it's a compiler regression; I've managed to reproduce it with the nightly-2022-09-01 toolchain. It reproduces under ASAN but not under valgrind (so probably timing dependent) but neither...

I was able to compile the same binary on the same machine and run it against the same workload but as a Windows executable rather than as a Linux one...

Out of curiosity, can you install the rust client and try it? Cargo install ssclient

Oh, ok. What about trying the .NET client on Linux? `dotnet tool install --global SecureStore.Client`

I've moved this to the securestore-rs repo, as it seems the bug is in the rust version of the client (unless @Myvryn-LF reproduces it with the dotnet one, too).

If you have a legacy version of the store and are using a modern version of ssclient or securestore.client, the client will attempt to upgrade the store before exit. I'm...

> I created the store files with the current version of SecureStore they are not legacy stores and, therefore, shouldn't require a file write to upgrade I'm sorry, I completely...

I recommend using a different target directory for RA, that should solve all your lock file and incremental rebuild issues.