Better logging on node init failure due to AW or TSS creation failing

[Garandor]

What

Improve error handling during node startup for PeerState creation and TSS state initialization.

Why

Lack of detailed error information when critical components fail to initialize makes it difficult to diagnose startup issues.

Background

We wasted too much time figuring out why a newly recreated node wasn't able to join the network. If it's due to the AW registration failing, it should now be obvious from the logs

Risks

• No functional changes to the code logic, only improved error handling
• The changes maintain the same behavior of panicking on critical initialization failures, but with better error reporting

[Garandor]

• Better logging on node init failure due to AW or TSS creation failing #61 👈 (View in Graphite)
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[github-actions]

PASS [ 43.171s] (2/3) lit_node::test toxiproxy::perf_tests::load_with_50ms_latency_single_link
PASS [ 43.205s] (3/3) lit_node::test toxiproxy::perf_tests::load_with_no_latency
PASS [ 88.342s] (1/3) lit_node::test toxiproxy::perf_tests::load_with_50ms_latency_all_links

[Garandor]

Merge activity

• Jan 10, 2:13 AM UTC: Graphite rebased this pull request as part of a merge.
• Jan 10, 2:38 AM UTC: @Garandor merged this pull request with Graphite.