Pre-Dev-Update Thread! Yay! :D

If you see entries in ~/.safe/node/local-test-network/safenode-*/record_store then you are connected and storing chunks

5 Likes

NAT traversal is ready to merge and putting DBCs on top of libp2p is in progress. Then they will be able to add payments for upload, which also means choosing and implementing a pricing mechanism.

Are we there yet…? No, but fingers crossed for a nodes from home testnet this week.

19 Likes

What makes you think so?

2 Likes

AutoNAT with TCP, distinguishing local and global networks by b-zee · Pull Request #259 · maidsafe/safe_network · GitHub suggests this is close to completion.

Will it be ready for tomorrow? My recent rather conservative predictions have proved to be crap but seeing as nobody has crowd-funded me to continue making them, I will say nothing other than keep an eye on the PR queues.

9 Likes

2 Likes

yes - wanna argue?

1 Like

Just want to see you make that hat trick :crazy_face:

2 Likes

Jus to confirm, this is NAT traversal part 1. So here we are looking to correctly detect NAT or inward connectivity. Actually hole punch comes next

19 Likes

Dang! Jinxed it. But I won’t shut up :stuck_out_tongue_winking_eye:

Go Benno!

9 Likes

Ha, we spot a last minute issue and was really excited to get it going by Wednesday. Glad it finally worked out and we’re now mostly where we want to be with NAT detection! :hugs:

Thanks for the support! :pray:NAT has been very interesting to look at, at the same time it’s a hard thing to grasp and test.

:tada:

14 Likes

Payments edge a step closer…

This means that DBCs are now sitting on top of libp2p. I don’t know what else is needed but expect there is more to do before payments and praying for storage are ready.

16 Likes

This is a development I hadn’t anticipated

5 Likes

We have been doing that for a few years now :smiley: :smiley:

11 Likes

Just remember to say “Amen” in the end.

6 Likes

Prayer mat/cushion ready, altogether now … :pray: to Gabriel (seriously):

19 Likes

Breakthrough week :crossed_fingers:

14 Likes
{"physical_cpu_threads":12,"system_cpu_usage_percent":8.87408,"system_total_memory_mb":33517.777,"system_memory_used_mb":14960.186,"system_memory_usage_percent":44.633587,"network":{"interface_name":"enp0s31f6","bytes_received":1350,"bytes_transmitted":53303,"total_mb_received":2376.993,"total_mb_transmitted":749.26776},"process":{"cpu_usage_percent":4.6299543,"memory_used_mb":38.64576,"bytes_read":0,"bytes_written":16384,"total_mb_read":0.0,"total_mb_written":4.251648}}

I am almost tempted to fire up a safenode local testnet to see what the current state off --json-output is, but will hold off for now. Also, excited to pipe that data from the json format into a local influxDB and into grafana on the next testnet :smiley:.

Just curious, how often will these be logged, at a certain frequency from safenode pid or everytime a certain operation takes place?

8 Likes

every 5s at the moment (with the feature enabled)

broadcasting inactive client

I’m not sure if we have json output all over logs, or it’s just this one is json formatted actually. cc @roland ?

3 Likes

Yeah, the metric is logged every 5s which should be optimal to not clog up the log files but also provide a resolution small enough to track down mem/cpu anomaly if we were to encounter any.

The metric is written as a JSON object to the log file, should be easier for people to grep and pipe them. This is the entire log line,

[2023-06-05T12:29:59.680321Z TRACE sn_logging::metrics] {"physical_cpu_threads":12,"system_cpu_usage_percent":11.24604,"system_total_memory_mb":33517.777,"system_memory_used_mb":16400.195,"system_memory_usage_percent":48.929844,"network":{"interface_name":"enp0s31f6","bytes_received":1774,"bytes_transmitted":37947,"total_mb_received":2367.518,"total_mb_transmitted":717.744},"process":{"cpu_usage_percent":1.2671595,"memory_used_mb":35.004417,"bytes_read":0,"bytes_written":8192,"total_mb_read":0.0,"total_mb_written":0.1024}}
7 Likes

Progress, progress… :wink:

I’m not gonna say more. Whistling…

3 Likes