00:00:55 <moneroedu[m]> Hi, whats the easiest way to use monero anonymously
00:01:12 <moneroedu[m]> is it possible to do everything on my phone?
00:03:37 <MajesticBank> wrong channel, try #monero
00:04:11 <merope> <ryit[m]> "I'm using a remote daemon for..." <- https://github.com/ryn0/csharp-monero-rpc-client/blob/master/src/Tests/MoneroClient.IntegrationTests/Utilities/ProcessUtils.cs#L36
00:06:08 <merope> Perhaps the individual test tries to connect to the wallet-rpc that's running on localhost from `TestingConstants.DefaultHost`, while the full integration test is binding to a different address by default, for whatever reason?
00:08:22 <merope> Hmmm, but then all tests would have to fail the same way
00:10:01 <ryit[m]> I don't think it's binding any differently, it starts the wallet RPC and that process stays running until all tests are done and then it stops the process. I have only know this issue to be related to the test that fails with wallet creation. The other test that failed was an unlocked balance, that has nothing to do with this issue. 
00:11:26 <ryit[m]> I think pretty much every RPC call is ok to run how I want except for the wallet creation one (which only runs correctly if I run only that test).
00:12:24 <NorrinRadd> ryit[m] i have a faint memory of hearing that was the case before 
00:13:24 <merope> Gotta figure out what's blocking the socket, and/or where it's trying to connect
00:15:34 <ryit[m]> I have tried closing, disposing, saving everything with the wallet I can in the test prior so it'd work but nothing seems to have an impact. 
00:19:34 * ryit[m] uploaded an image: (64KiB) < https://libera.ems.host/_matrix/media/v3/download/matrix.org/vUpnygVNfhxtuYuPRzAqEcVk/image.png >
00:19:35 <ryit[m]> What I just did that worked... but this is of course a bad idea... is force the wallet creation test first. 
17:06:32 <ryit[m]> Actually, I see the "The I/O operation has been aborted because of either a thread exit or an application request." exception thrown in other tests too, not just the wallet creation one. Not sure how I would know what's blocking the socket or what exactly is going on. 
17:12:32 <ryit[m]> It seems like, as soon as this happens, all downstream tests have the same issue.