02:01 < luke-jr> it looks like Xcode is no longer gratis to download.. :/

02:01 < luke-jr> do we actually need the latest version, or can we revert back to the last gratis one?

02:24 < achow101> luke-jr: I'm still able to download it for free

02:24 < achow101> the link in the docs don't work because apple broke them with redirects

02:24 < achow101> but you can still get it manaully

02:26 < achow101> you have to sign in to developer.apple.com, go to the downloads page, click "More", and then scroll through the gigantic list to find the right xcode version

02:34 < luke-jr> I can get to the downloads page, but they all say unauthorised :/

02:34 < achow101> do you have an apple account?

02:34 < luke-jr> yes

02:34 < luke-jr> even gave them my phone number :/

02:36 < achow101> where does it say unauthorised?

02:38 < luke-jr> when I click on the actual download link for anything

02:39 < achow101> weird, I don't have any problems

02:40 < achow101> and I don't pay them

02:42 < achow101> do you have something that deletes cookies and maybe the auth cookie is lost when you try to download?

02:48 < luke-jr> ooh, could be - I have cookies on a whitelist basis

02:48 < luke-jr> bingo

02:49 < luke-jr> > [Xcode_11.3.1](https://download.developer.apple.com/Developer_Tools/Xcode_12.1/Xcode_12.1.xip)

02:49 < luke-jr> eh

02:49 < luke-jr> (FWIW, I had to whitelist https://download.developer.apple.com/ for cookies)

02:51 < achow101> Glad that's resolved

08:29 < gazza> hi all

08:30 < gazza> ive just downloaded the whole network (putting in my 2cents to feel apart of it) just wanted to know if theres anything else that needs doing?

10:47 < michaelfolkson> gazza: As the topic of the channel says this channel is for development discussion. #bitcoin for general usage

13:31 < Guest4> Hi

18:45 < bitcoin-git> [bitcoin] theStack opened pull request #22423: test: wallet_listtransactions improvements (speedup, cleanup, logging) (master...202106-test-improve-wallet_listtransactions_test) https://github.com/bitcoin/bitcoin/pull/22423

23:23 < brcolow> I am confused by something. If you look at this line of code: https://github.com/bitcoin/bitcoin/blob/master/src/crypto/sha256_avx2.cpp#L63 it is writing a 32-bit (4byte) integer. In the case of -1996298034 that is, in big endian, 8902 e8ce - then it's converted to little endian which is CEE8 0289 - however what's strange is that WriteLE32 function writes CEE8289 - it skips the

23:23 < brcolow> starting zero of the second chunk. How is that not a bug? It changes the length of bytes written, and changes the resulting hash by skipping a zero.

23:39 < sipa> that makes no sense :)

23:39 < sipa> it writes 4 bytes, always

23:39 < sipa> CEE8289 doesn't even exist; it's 3.5 bytes

23:55 < brcolow> Yeah, that was my bad. I was printing it incorrectly. I'm sorry.