cryptoadvance / cryptoadvance/specter-desktop
v1.8.1 Cannot find debug.log during testnet sync
- Dominant language
- Python
- Stars
- 847
- Forks
- 259
- Avg merge
- 6d 18h
- Merged PRs (30d)
- 2
Description
When performing the initial sync of a local pruned testnet node, attempting to view the bitcoind logs via the "See Bitcoind Logs" in the "Debug" section, it seems like there is a pathing issue as the following "server error" shows up
However, manually drilling into the path shows an additional subdir "testnet3," which is where the debug.log file is kept and is appropriately being updated
Contributor guide
Research direction
Reproduce the initial sync of a local pruned testnet node and use the Debug section's “See Bitcoind Logs” action. Compare the path it requests with the manually observed testnet3/debug.log location; done when the action opens the current debug.log during testnet sync.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- desktop
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100