API issues with updated network continue and are not due to mobile broadband

[happybeing]

In an effort to get my app built I have moved all interactions with Autonomi network to a VPS, to bypass problems that might be being caused by my mobile broadband connection.

I've upgraded my app to build for the APIs released this Monday: safe_network branch stable (2024-07-25).

Running a combination of safe files upload and my app on the VPS has confirmed earlier problems still exist using the Autonomi network, including panics, repeated problems creating a register, and corruption of the wallet being used for uploads. So none of these issues are solely due to operation over mobile broadband.

I've collected the terminal output from two scripts below, each of which is attempting to upload files and publish metadata and a register, for one of four websites. I did succeed in publishing the first two websites, but in part by using safe files upload rather than the API to upload the website files, since that part of the API seemed particularly unreliable over mobile broadband.

The logfiles show terminal output from my app mixed with crash reports (panics in other crates), running in a loop until I terminated the script used to control the operations in each section.

Summary section 1

The following describes the process I'm using to upload three websites in the following order: 1) v0-autonomi-demo, 2) v0-dweb-blog and 3) v0-publii-dweb

• pre-upload: I have pre-uploaded all files for all three websites using safe files upload -p on the VPS. This seems fairly reliable (I'm not sure there we zero errors, but I have succeeded with that and been able to continue afterwards using my app as in the next item). No wallet issues at this point.
• app operations: once files are uploaded, I run my app on the VPS to upload the same directories (avoiding issues with paying or uploading these files because of the 'pre-upload' above), create a chunk of metadata, pay for that chunk and upload it, and after that create a register, and write to metadata address to it.
• failures occur frequently in all of the API 'app-operations' related to metdata and register. Sometimes panics, others records not found etc. (Note that with the previous network has panics when uploading a directory, see #1979)
• failed app operations are automatically repeated using a script, so the logfile attached shows repeated failures until a particular website gets all the way through (having created and written to a register).
• the attached logfile was terminated due to endless failures trying to publish the 'v0-publii-dweb' website, having succeeded in publishing the 'v0-autonomi-demo' and 'v0-dweb-blog' websites

Summary section 2

Based on metadata from the above, I run a script which generates a fourth website 'awe-some-sites' and uses my app to both upload the files, and do the metadata and register creation. This fails right away due to problems with the wallet caused by the failures above.

• a different script attempts to do both the files upload (in my app this time), and then the same app-operations listed above to publish the 'awe-some-sites' website. However, this fails at the upload stage due to pre-unconfirmed operations (see second logfile). I know of no way to recover that wallet, which will also now fail to work with safe files upload, so I cannot complete the process.

Logfiles:

• summary section 1: awe-upload-tests-v0testnet-sites.txt

• summary section 2: awe-make-awe-some-sites--force-publish.txt

Safe client version

$ safe -V
sn_cli 0.94.0

safe_network crates used to build app

# Generated using: awe-dependencies --branch stable (2024-07-25)
sn_cli = { version = "0.94.0" }
sn_client = { version = "0.109.0" }
sn_peers_acquisition = { version = "0.4.1" }
sn_registers = { version = "0.3.16" }
sn_transfers = { version = "0.18.9" }
sn_protocol = { version = "0.17.6" }