QuicNet [30/01/24Testnet] [Offline]

Profess · January 30, 2024, 7:04pm

Unfortunately I get the same error as in the previous testnet:

PS C:\Users\gggg> safenode
Logging to directory: "C:\\Users\\gggg\\AppData\\Roaming\\safe\\node\\12D3KooWQMgwAMod3uGJvpHmUF27DawFgicA6HFpase2mT7JvHMN\\logs"
Trying to fetch the bootstrap peers from https://sn-testnet.s3.eu-west-2.amazonaws.com/network-contacts

Node started

PeerId is 12D3KooWQMgwAMod3uGJvpHmUF27DawFgicA6HFpase2mT7JvHMN
You can check your reward balance by running:
`safe wallet balance --peer-id=12D3KooWQMgwAMod3uGJvpHmUF27DawFgicA6HFpase2mT7JvHMN`

After starting the node, I can’t type any command, I can’t do anything else in this session.

DavidMc0 · January 30, 2024, 7:06pm

I used Windows Power Shell to launch my node, and while I also couldn’t type a command in the tab I launched the node from, I opened another tab & requested balance & it worked fine.

May be worth trying another tab / window if it’s an option for you.

chriso · January 30, 2024, 7:12pm

There actually isn’t an error here. It’s behaving as expected.

The language it uses when it says “Trying to fetch…” could potentially be a bit confusing though, because it doesn’t confirm that it did actually fetch the contacts file.

However, that said, your node is running. It’s a blocking process, so if you want to do something else, you need to use another shell session.

Edit: I just wanted to say, my opinion is that the logging should go to stdout if no logging argument to file is specified. That way you would see the node doing something. It’s not completely obvious that it would be logging to file in the background.

Toivo · January 30, 2024, 7:18pm

Hmm… this change not worth a mention?

github.com/maidsafe/safe_network

feat: allow register CLI to create a public register writable to anyone

maidsafe:main ← thomasmarkiewicz:issues/1106

opened 10:32PM - 05 Jan 24 UTC

thomasmarkiewicz

+162 -42

## Description ### Summary generated by Reviewpad on 05 Jan 24 22:32 UTC Thi…s pull request includes changes in various files. Here is a summary of the changes: 1. In the file "nodes_rewards.rs": - Imported the `Permissions` struct from the `sn_registers` module. - Modified the `create_and_pay_for_register` function call by adding a new argument `Permissions::new_owner_only()`. These changes involve using the `Permissions` struct and passing it as an argument to the `create_and_pay_for_register` function. 2. In the file "register.rs": - Removed the `create_public_online` function. - Modified the `create_online` function to accept a `perms` parameter of type `Permissions`. - The `perms` parameter is used in `create_register` when creating the register. These changes suggest a refactoring of the code related to creating and syncing registers in the client. 3. In the file "Cargo.lock": - Added the "sn_registers" dependency. 4. In the file "data_with_churn.rs": - Added an import statement for `Permissions` from the `sn_registers` module. - Passed an additional argument `Permissions::new_owner_only()` to the `create_and_pay_for_register` function. These changes seem to be related to enhancing security and permissions in the code. 5. In the file "registers.rs": - Added an import statement for `Permissions` from the `sn_registers` module. - Added the `Permissions::new_anyone_can_write()` as an additional parameter in the `create_and_pay_for_register` function call. These changes indicate that the code now includes permissions for the register and allows anyone to write to it. 6. In the file "register.rs": - Imported the `Permissions` struct from the `sn_registers` module. - Added a new command line option `-p` or `--public` to create the register with public write access. - Updated the `create_register` function to accept the `public` parameter and use it to determine the permissions of the register. - Updated the `create_and_pay_for_register` function call to include the `perms` parameter. - Print the address of the created register at the end. 7. In the file "Cargo.toml": - Added a new dependency, "sn_registers", with version "0.3.6" in the "sn_cli" directory. 8. In the file "storage_payments.rs": - Imported `sn_registers::Permissions`. - Added additional arguments in the `create_and_pay_for_register` function call. - Added creation of `Permissions::new_owner_only()`. - Added additional arguments in the second `create_and_pay_for_register` function call. These changes introduce the `Permissions` module, modify the function calls to `create_and_pay_for_register`, and add extra arguments to these function calls. Let me know if you need any further assistance. Resolves issue #1106

Anyway, I have two nodes running and earning. Uploads are really much much faster as was the faucet too.

I am most interested in seeing if the change to QUIC does anything to the problems my LAN had been having with the previous testnets - meaning my piece of a crap router just saying no.

Well done Maidsafe!

Josh · January 30, 2024, 7:20pm

I just started my first machine and rewards appear to be on steroids in comparison to the last network, has anything changed there?
Rewards balance: 0.000000512 10 minutes in.

Another observation is cpu seems to be up a bit, not crazy or issue territory but notable, might settle.

happybeing · January 30, 2024, 7:25pm

I guess as uploads are going much faster so will earnings.

Josh · January 30, 2024, 7:26pm

Fair point, much of the last network was faucet-less so my yardstick is skewed.

Toivo · January 30, 2024, 7:29pm

CLI folders related to payments, cash_notes and payments have a very low size after a few uploads. Was this so already in the last testnet? Anyway, another reason to

Profess · January 30, 2024, 7:31pm

I understand, thanks for the clarification.

However, in the new session I tried to connect as a client and download the tokens but here I get a strange error:

PS C:\Users\gggg> safe wallet get-faucet 157.245.40.226:8000
safe : The term 'safe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
 spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:1
+ safe wallet get-faucet 157.245.40.226:8000
+ ~~~~
    + CategoryInfo          : ObjectNotFound: (safe:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Please ask for guidance.

chriso · January 30, 2024, 7:32pm

It looks like you don’t have an installation of the safe client. Remember, you can use safeup to get that.

Also, remember you will need to specify a peer to connect to when running safe. You can do that either by using the --peer argument (which you will need for each command you run), or you can set the SAFE_PEERS variable once and it will persist for the remainder of the shell session.

Profess · January 30, 2024, 7:45pm

The thing is, I had the client running before, but now I repeated it and tried to download the tokens again, and here comes an even weirder message…

PS C:\Users\gggg> safeup client --version 0.89.29
**************************************
*                                    *
*          Installing safe           *
*                                    *
**************************************
Installing safe.exe for x86_64-pc-windows-msvc at C:\Users\gggg\safe...
  [########################################] 7.53 MiB/7.53 MiB                                                          safe.exe 0.89.29 is now available at C:\Users\gggg\safe\safe.exe
PS C:\n-Users_safe.exe> safe wallet get-faucet 157.245.40.226:8000
Program 'safe.exe' failed to run: operation failed because the file contains a virus or potentially
unwanted softwareAt line:1 char:1
+ safe wallet get-faucet 157.245.40.226:8000
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~.
At line:1 char:1
+ safe wallet get-faucet 157.245.40.226:8000
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
    + CategoryInfo          : ResourceUnavailable: (:) [], ApplicationFailedException
    + FullyQualifiedErrorId : NativeCommandFailed

Now I don’t understand anything anymore.

chriso · January 30, 2024, 7:48pm

Well, when I used GPT to translate that error message into English, it looks like this is some kind of warning from the operating system that it’s blocking the use of safe.exe because it considers it to be potentially harmful.

I don’t think we’ve ever seen that before.

What version of Windows are you using?

Profess · January 30, 2024, 7:51pm

I corrected the screen, I did not notice that the message was not in English.

I am using Win 10 Pro.

chriso · January 30, 2024, 7:54pm

What is the output if you just run safe --version?

Profess · January 30, 2024, 7:58pm

PS C:\Users\gggg>  safe --version
safe : The term 'safe' is not recognized as the name of a cmdlet, function, script file, or operable program. Check the
 spelling of the name, or if a path was included, verify that the path is correct and try again.
At line:1 char:2
+  safe --version
+  ~~~~
    + CategoryInfo          : ObjectNotFound: (safe:String) [], CommandNotFoundException
    + FullyQualifiedErrorId : CommandNotFoundException

Also indicates an error.

Josh · January 30, 2024, 8:14pm

I hit the faucet a “fairly fair” 20 times in anticipation of it throwing it’s toys and others perhaps needing some dough.

1 out of the 20 requests resulted in.

josh@pc1:~$ safe wallet get-faucet 157.245.40.226:8000
Logging to directory: "/home/josh/.local/share/safe/client/logs/log_2024-01-30_15-10-13"
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: b4daa87647f9010766ede59ec3a13dc3214d09838da5a9a14a2f003ae6d5c9fd78543e9b6394fde25f4677a666638885
Successfully parsed transfer. 
Verifying transfer with the Network...
Failed to verify and redeem transfer: CouldNotReceiveMoney("InvalidTransfer(\"GetRecord Query Error NotEnoughCopies { record_key: 88c4bd(1c19166b10f56b2cb229655ec25bb3a89976a0e25502fdc80663dd212b793a88), expected: 5, got: 3 }\")")
Error: 
   0: Failed to receive transfer due to InvalidTransfer("GetRecord Query Error NotEnoughCopies { record_key: 88c4bd(1c19166b10f56b2cb229655ec25bb3a89976a0e25502fdc80663dd212b793a88), expected: 5, got: 3 }")

Location:
   /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/convert/mod.rs:757

Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets.

chriso · January 30, 2024, 8:51pm

Do you actually have a safe.exe at C:\Users\gggg\safe\safe.exe?

Or has the operating system removed it after deciding it was somehow unsafe?

DavidMc0 · January 30, 2024, 9:01pm

Upload progress: Uploaded 35.7GB file in 271 minutes and 12 seconds. Around 2.2 MB/s. Fantastic speed!

Unfortunately 66 chunks failed, so no address / filename is given in CLI, and the file can’t be downloaded. I’ll try to re-upload a few times and see how it goes, but initial re-attempts have failed.

Upload / download worked perfectly with an 11mb JPG.

Profess · January 30, 2024, 9:06pm

In the safe folder I have the files:

C:\Users\ggg\safe\safenode.exe and C:\Users\ggg\safe\safeup.exe

Whereas safe.exe I don’t have.

You are right, I restarted the safeup client --version 0.89.29
then the safe.exe file appeared in the safe folder, but after running the
safe wallet get-faucet 157.245.40.226:8000
command, an error appears and the operating system removed again from the safe.exe folder.

chriso · January 30, 2024, 9:23pm

Hmm, that’s annoying that it’s marking safe as some kind of malicious file. You might need to look at the Windows firewall or anti-virus settings to add an exception for it. I don’t believe anyone else has ever hit that issue. I was wondering if you were using Windows 11, but you’ve already mentioned you’re on 10.

Topic		Replies	Views
NoEncryptionNet [07/02/24 Testnet] [Offline] Releases	211	1954	March 15, 2024
HeapNet2 [Testnet 12/10/23] [Offline] Releases	514	6199	December 3, 2023
[MemDebugNet] [4/10/23 Testnet] [Offline] Releases	340	4006	October 14, 2023
DataDebugNet [ 28/09/23 Testnet ] [Offline] Releases	184	2750	October 4, 2023
ReduceConnectionsNet [ 06/12/23 Testnet] [Offline] Releases	212	2644	December 13, 2023

QuicNet [30/01/24Testnet] [Offline]

Related topics