joshuef
January 17, 2024, 2:54pm
5433
I wonder if we can proactively try and pinpoint this failure in future… Maybe run a. balance check every 15 mins and if we hit this we know we’ve an issue in that time frame?
3 Likes
Can’t hurt
@Josh has added time stamps to his NTracking so I think we will have a record of balance every 20 min so with NTracking we can pinpoint it to a 20 min window for next testnet run.
3 Likes
looking at NTracking we can already get a time frame.
joshuef
January 17, 2024, 3:33pm
5436
I’d check the logs for wallet write’s around then and see if any errors were cropping up.
My logs don’t go that far back I’m storing 10 uncompressed log files which I believe is about 24hrs worth
But will be on it next time
2 Likes
joshuef
January 17, 2024, 4:05pm
5438
next time logs will be more relaxed too (by default at least)
4 Likes
There’s a PR being worked on by Gabriel to implement safe folders commands to create folders on the network using registers and upload/download directory trees.
Here’s the underlying folders API:
maidsafe:main ← bochaco:feat-folders-api
opened 08:48PM - 31 Jan 24 UTC
## Description
### Summary generated by Reviewpad on 31 Jan 24 20:48 UTC
Thi… s pull request includes the following changes across multiple files:
- In the `subcommands/mod.rs` file, a new module `folders` has been added, along with the necessary command handling for the `SubCmd::Folders` variant.
- In the `subcommands/mod.rs` file, the `FoldersApi` trait has been imported.
- In the `subcommands/folders.rs` file, the implementation of the `FoldersApi` struct has been added. The struct provides APIs for interacting with folders and includes methods such as `new`, `wallet`, and `upload`.
- In the `folders.rs` file, the implementation of the `FoldersCmds` enum has been added, which includes variants for `Upload` and `Download` operations.
- In the `folders.rs` file, helper functions `upload_folder` and `download_folder` have been implemented to handle the actual upload and download operations.
- In the `api.rs` file, a blank line has been added at line 62, and there is an additional comment for instantiating a new client.
Please review the changes in the diff for any potential issues or improvements.
Here’s the safe folders CLI command implementation:
maidsafe:main ← bochaco:feat-folders-api
opened 08:48PM - 31 Jan 24 UTC
## Description
### Summary generated by Reviewpad on 31 Jan 24 20:48 UTC
Thi… s pull request includes the following changes across multiple files:
- In the `subcommands/mod.rs` file, a new module `folders` has been added, along with the necessary command handling for the `SubCmd::Folders` variant.
- In the `subcommands/mod.rs` file, the `FoldersApi` trait has been imported.
- In the `subcommands/folders.rs` file, the implementation of the `FoldersApi` struct has been added. The struct provides APIs for interacting with folders and includes methods such as `new`, `wallet`, and `upload`.
- In the `folders.rs` file, the implementation of the `FoldersCmds` enum has been added, which includes variants for `Upload` and `Download` operations.
- In the `folders.rs` file, helper functions `upload_folder` and `download_folder` have been implemented to handle the actual upload and download operations.
- In the `api.rs` file, a blank line has been added at line 62, and there is an additional comment for instantiating a new client.
Please review the changes in the diff for any potential issues or improvements.
And here’s the draft PR to track:
maidsafe:main ← bochaco:feat-folders-api
opened 08:48PM - 31 Jan 24 UTC
## Description
### Summary generated by Reviewpad on 31 Jan 24 20:48 UTC
Thi… s pull request includes the following changes across multiple files:
- In the `subcommands/mod.rs` file, a new module `folders` has been added, along with the necessary command handling for the `SubCmd::Folders` variant.
- In the `subcommands/mod.rs` file, the `FoldersApi` trait has been imported.
- In the `subcommands/folders.rs` file, the implementation of the `FoldersApi` struct has been added. The struct provides APIs for interacting with folders and includes methods such as `new`, `wallet`, and `upload`.
- In the `folders.rs` file, the implementation of the `FoldersCmds` enum has been added, which includes variants for `Upload` and `Download` operations.
- In the `folders.rs` file, helper functions `upload_folder` and `download_folder` have been implemented to handle the actual upload and download operations.
- In the `api.rs` file, a blank line has been added at line 62, and there is an additional comment for instantiating a new client.
Please review the changes in the diff for any potential issues or improvements.
14 Likes
And we have a new toy to play with: feat(client): adding Folders API and CLI cmds by bochaco · Pull Request #1251 · maidsafe/safe_network · GitHub
Folders
The folders storage capability can be demonstrated by uploading folders to the local network, then retrieving them.
Upload a directory:
cargo run --bin safe --features local-discovery -- folders upload <dir-path>
After it finishes uploading the complete directory, with files and sub-directories, it will show the address where the main directory can be pulled from.
Now download the folders, optionally providing a target directory name:
cargo run --bin safe --features local-discovery -- folders download <address> [dir name]
13 Likes
libp2p AutoNATv2 looks close:
umgefahren:transport-redesign ← umgefahren:implement-autonat-v2
opened 04:08PM - 07 Nov 23 UTC
## Description
This is a WIP implementation of AutoNATv2.
I would appreci… ate feedback by @mxinden and @thomaseizinger. You don't have to go into any specifics, I just wanted to check up if the direction is correct. A complete and formal PR will follow once everything is done.
- 🚧 Client - ConnectionHandler (~80% done)
- 🚧 Client - Behavior (~10% done)
- 🌰 Server - ConnectionHandler
- 🌰 Server - Behavior
I'm sorry it took me so long to give a sign of life. I sunk a lot of hours into doing it with request-response just to discover I need to do it without it. Additionally I couldn't work on it for the last week since I had to study for a midterm.
<!--
Please write a summary of your changes and why you made them.
This section will appear as the commit message after merging.
Please craft it accordingly.
For a quick primer on good commit mesages, check out this blog post: https://cbea.ms/git-commit/
Please include any relevant issues in here, for example:
Related https://github.com/libp2p/rust-libp2p/issues/ABCD.
Fixes https://github.com/libp2p/rust-libp2p/issues/XYZ.
-->
## Notes & open questions
<!--
Any notes, remarks or open questions you have to make about the PR which don't need to go into the final commit message.
-->
## Change checklist
- [ ] I have performed a self-review of my own code
- [ ] I have made corresponding changes to the documentation
- [ ] I have added tests that prove my fix is effective or that my feature works
- [ ] A changelog entry has been made in the appropriate crates
15 Likes
Think this one is in your honour @Southside
maidsafe:main ← maqi:restart_node_on_HDD_error
opened 02:42PM - 19 Feb 24 UTC
## Description
reviewpad:summary
11 Likes
Anyone for some alpha.0 ?
8 Likes
joshuef
February 21, 2024, 11:27am
5444
This is me testing out some release process updates. Laying the ground work to be able to have longer running testnets of varying stability…
17 Likes
@JimCollinson announcement about an announcement has me clutching at straws for clues lol
15 Likes
Drums fingers.
Taps watch.
Looks around.
Pretty lonely in this waiting room.
Time to eat…
11 Likes
Your not alone is it time for Jim’s announcement
5 Likes
Josh
February 22, 2024, 5:53pm
5448
Are you saying this was a clue about a lead in a riddle that pointed toward Thursday 22 Feb 2024 update?
Upon reevaluating the facts @JimCollinson did indeed promise certainly, under oath that he will reveal his secret today. This much is almost clear.
6 Likes
Zoki
February 22, 2024, 6:22pm
5449
Is today’s update later than usual?
6 Likes
@mav has been busy on the token claim/distribution mechanism and has a nice solution for Omni MAID holders who can sign a message (so good for hardware wallets too):
maidsafe:alpha ← iancoleman:faucet_sigs
opened 11:49PM - 25 Feb 24 UTC
The bitcoin maid address is used to sign a safe wallet address. The signed walle… t address is used by the faucet as the recipient of the distribution for that maid.
This still uses snapshot to determine distributions, but instead of the faucet creating a random wallet to distribute to, it uses the safe wallet address submitted by the user.
This removes the need for ecies encryption/decryption.
This also removes the need for people to have the maid private key regularly available, since only the signature is required to claim.
Hardware wallets don't have ecies but can sign a message, so this makes the claim process much easier for people with maid using hardware wallets.
The main downside to this approach is safe wallet keys are not currently stored securely, so users may submit a safe wallet address which isn't secure (fine for test nets) and then neglect to update their safe wallet address before main net.
This PR only implements the faucet side of the logic. The client currently has no way to get their distribution. The client code is ready to go but will be a separate PR after this is merged (or not).
Some conversation about using ecies vs signatures for claiming:
https://forum.autonomi.community/t/update-25-january-2024/39127/74
https://forum.autonomi.community/t/update-8-february-2024/39188/39
## Description
reviewpad:summary
17 Likes
Sonder
February 26, 2024, 3:58pm
5451
So we don’t have to send the tokens?
1 Like
Just out of curiosity, how would that work? I understand the signing a message part. But, I do not understand how that would prevent someone from using a CEX or DEX shortly after to sell the coins one has already converted to SNT (or whatever it’s going to be called).
