Moses Narrow

A recurring issue is that setup-nodes become unreachable: ``` [2025-04-13T08:59:22.655941308-05:00] WARN [router]: failed to dial to setup node: setupPK(0324579f003e6b4048bae2def4365e634d8e0e3054a20fc7af49daf2a179658557) error="i/o deadline reached" [2025-04-13T08:59:42.96057214-05:00] WARN [router]: failed to dial to setup...

`WARN [router]: Failed to handle transport frame: routing table: rule not found`

8

When starting the proxy client, sometimes I get the following errors: ``` [2025-03-22T17:52:05.15067992-05:00] WARN [router]: Failed to handle transport frame: route descriptor does not exist ``` Followed by: ``` [2025-03-22T16:15:22.947131457-05:00]...

I changed the archlinux packaging slightly the other day, and now I'm getting this: ``` [2025-03-15T09:22:57.729374783-05:00] WARN [tp:037734]: Failed to record log entry. error="open /opt/skywire/local/transport_logs/2025-03-15.csv: no such file or directory"...

Public visor losing transports / can't establish stcpr transport to public visor

7

on starting visor 03773464102a7fcb9021962a4a6cf3c6a23739a8720e8b43280b1fd078cfbd6bfb as a public visor,, it gets a lot of transports initially, over 200, but this number dwindles over time to less than a dozen, I've observed...

It seems I'm not able to connect to a proxy server as I am normally able to. ``` _pk=03773464102a7fcb9021962a4a6cf3c6a23739a8720e8b43280b1fd078cfbd6bfb ; skywire cli tp ad^C-ft stcpr $_pk && skywire cli proxy...

The files written by the visor are mostly useless or unnecessary & only complicate the installation / clutter the installation path. If no files need be written at runtime then...