Does this also mean that when the upload is being “verified” at the end, it’s only verifying that each chunk was paid for? Or is verification checking to see if the chunk actually exists on the network?
Because I’ve had chunks that presumably uploaded -were removed from the chunk to-do folder; but then later after verification, the chunks weren’t found (or weren’t paid for), so it added them back to the to-do list.
the verification checks whether chunk exists on the network.
So it can sometimes happen then that a chunk get’s uploaded and paid for, but then it does not get replicated for some reason and so later can’t be found during verification. OR, some other weird thing is happening.
Just so we understand each other 
There are currently files in C:\Users\gggg\AppData\Roaming\safe
safe.exe
safenode.exe
safeup.exe
while previously there was a problem with Windows deleting the safe.exe file and recognizing it as a virus:
On the other hand, I reinstalled the client yesterdey evenign and it turns out that Windows no longer removes it (although nothing has changed in my Win or in the safeup client file at this time):
I will try.
The directories the binaries get stored in should be different from the directory where data for the client is stored. You shouldn’t be seeing binaries in AppData\Roaming\safe.
I will have a look at this later on a VM, just to verify exactly which directories are used.
Hmmm… strange things are happening here…
However, before trying to delete the folder, I tried to reinstall the node (encouraged by the fact that I managed to install the client without being blocked by Win) and it turns out that everything works…
PS C:\Users\gggg> rm -r C:\Users\gggg\AppData\Roaming\safe
PS C:\Users\gggg> safeup node --version 0.103.25
**************************************
* *
* Installing safenode *
* *
**************************************
Installing safenode.exe for x86_64-pc-windows-msvc at C:\Users\gggg\safe...
[########################################] 6.21 MiB/6.21 MiB safenode.exe 0.103.25 is now available at C:\Users\gggg\safe\safenode.exe
PS C:\Users\gggg> safenode
Logging to directory: "C:\\Users\\gggg\\AppData\\Roaming\\safe\\node\\12D3KooWMruETNkE7mZmb4j6mzVqvkZLXgxq9aV6vbSjrkoT1K9v\\logs"
Trying to fetch the bootstrap peers from https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
Node started
PeerId is 12D3KooWMruETNkE7mZmb4j6mzVqvkZLXgxq9aV6vbSjrkoT1K9v
You can check your reward balance by running:
`safe wallet balance --peer-id=12D3KooWMruETNkE7mZmb4j6mzVqvkZLXgxq9aV6vbSjrkoT1K9v`
In the new session
PS C:\Users\gggg> safe wallet balance --peer-id=12D3KooWMruETNkE7mZmb4j6mzVqvkZLXgxq9aV6vbSjrkoT1K9v
Logging to directory: "C:\\Users\\gggg\\AppData\\Roaming\\safe\\client\\logs\\log_2024-02-01_13-39-24"
Built with git version: a15b141 / main / a15b141
Node's rewards wallet balance (PeerId: 12D3KooWMruETNkE7mZmb4j6mzVqvkZLXgxq9aV6vbSjrkoT1K9v): 0.000000000
PS C:\Users\gggg> safe wallet get-faucet 157.245.40.226:8000
Logging to directory: "C:\\Users\\gggg\\AppData\\Roaming\\safe\\client\\logs\\log_2024-02-01_13-41-06"
Built with git version: a15b141 / main / a15b141
Instantiating a SAFE client...
Trying to fetch the bootstrap peers from https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts
Connecting to the network with 43 peers
🔗 Connected to the Network
Requesting token for wallet address: b73c14faf20b55807fc81c23aecf2822ec5cb0edd0d8c5722e5d6f1ace2377f95c06da3a45dd5b2edfa2a371adbcd6e7
Successfully parsed transfer.
Verifying transfer with the Network...
Successfully verified transfer.
Successfully stored cash_note to wallet dir.
Old balance: 0.000000000
New balance: 100.000000000
Successfully got tokens from faucet.
As for the files in AppData\Roaming\safe, they are visible:
OK, glad you got it working.
The output there actually confirms the client data directory:
However, safeup does not put binaries in that directory. It puts them at %USERPROFILE%\safe. Annoyingly, Windows doesn’t have the equivalent of something like /usr/local/bin on Linux, that is, some directory that’s guaranteed to be on the PATH. Pretty much the only directory guaranteed to be on PATH is C:\Windows\system32, but it doesn’t make sense to put our binaries in there.
IMHO these bugs are repeated in every testnet and I report them but I think they went unnoticed because the team and most of the testers are probably using Linux, meanwhile many users may have tried to participate in testing but when bugs like mine appeared they stopped testing and didn’t post on the forum - it’s just discouraging.
I think that if we want to have more testers, these seemingly trivial problems with Windows should be solved so that everyone can at least try to upload a file or make a payment.
Correct me if I am wrong. 
Is it really that bad? I could reboot to Windows and try, but don’t really want to 
We are definitely committed to supporting users on all platforms, and I certainly welcome more testing and usage on Windows and macOS. I honestly just had not come across the anti-virus issue until now. That’s the only new issue I think I’m seeing here. I think you’ve had some unfortunate difficulty with the use of Powershell to clear out some directories, but that’s not really an issue with any of our applications.
I will do if you do it 
I don’t think it’s that bad, but the number of testers who use Windows is probably in the minority (and assuming their skills are at a lower level than the pros), which might be why they don’t report problems they can’t get through.
I have no doubt that the team is fully committed to helping users, but at this rate of testing, minor issues may go unnoticed. If I have over-interpreted anything, I am very sorry.
Don’t worry, it’s not a problem. Happy to keep helping where I can. I am definitely going to have a more detailed look at the anti-virus issue.
I know, I always feel kinda dirty if I do.
And not in a good way.
I am taking one for the team. @chriso I already feel like a novice.
PS C:\Users\kyte7> safeup client --version 0.89.29
**************************************
* *
* Installing safe *
* *
**************************************
Installing safe.exe for x86_64-pc-windows-msvc at C:\Users\kyte7\safe...
Installing safe version 0.89.29...
[00:00:06] [########################################] 7.53 MiB/7.53 MiB (0s)safe.exe 0.89.29 is now available at C:\Users\kyte7\safe\safe.exe
PS C:\Users\kyte7> safeup node --version 0.103.25
**************************************
* *
* Installing safenode *
* *
**************************************
Installing safenode.exe for x86_64-pc-windows-msvc at C:\Users\kyte7\safe...
Installing safenode version 0.103.25...
[00:00:03] [########################################] 6.21 MiB/6.21 MiB (0s)safenode.exe 0.103.25 is now available at C:\Users\kyte7\safe\safenode.exe
PS C:\Users\kyte7> safe wallet get-faucet 157.245.40.226:8000
error: Found argument 'get-faucet' which wasn't expected, or isn't valid in this context
USAGE:
safe.exe wallet [OPTIONS] <SUBCOMMAND>
For more information try --helpThis is interesting, looking at my nodes memory there is a clear divide where some split into memory hungry chaos and a rollercoaster ride to eventual doom.
But it seems from this graph it all happened at about the same time and no more set off on that journey again.
See the black void/wedge at the bottom going back toward yesterday, most stayed flat but 18 took a different path, why then and why did no more join the memory party after that?
The get-faucet command is not found?! 
Honestly thought I would 
get further than that
Can you just actually confirm that you do in fact have version 0.89.29 of safe.exe?
I do, but I also had a forgotten .safe with a historic cli. 
Back in action. 
