reduce port range to 3000 to keep the same effective range of ports
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Mon, Dec 16
Collision on port 33380, Lets try to reduce the port range first to not conflict with docker ports (see D16048)
adding docs, style clean-ups, remove default type as it is not used anymore, remove unnecessary code duplication
very cool!
do this without the macro from D17355 (need to study macros more to make it work), fix clippy::needless-question-mark
rebase
use consistent error message "Unknown transaction id"
test all errors responses
now it works even if electrum is not synced to the tip btw
I would love to see a test for these error cases, since blockchain.transaction.get has both a mandatory and an optional arg it fits perfectly
This may be subjective but I'm not seeing a drastic improvement after updating to latest and hard refreshing twice. In some instances prod loaded the home screen and agora pages quicker than the test site, though that could also be the hosting infra playing a part. Tests were done with wallets having agora txs in tx history
=== p2pkh instead of !== p2sh
confirm there that load times are significantly improved for wallets with Agora txs
rebase
implementing feedback (add parse method, clean up existing methods, doc, remove unused interfaces and imports now that stuff is cleaned up)
Sun, Dec 15
ts build lint
simplify constructor, pure functions for legacy() and cash(), better error handling for withPrefix
Use '===' and not '=='
Sat, Dec 14
Let's wait to see if tests pass on CI or we get port collisions. The direct parent diff is a draft, this one was supposed to be one too.
rebase
Moved modules/bitcoinsuite-chronik-client next to other modules in workspace. Moved chronik-proto = { path = "../../chronik/chronik-proto/"} to other local dependencies
@bot build-chronik build-chronik-plugins
This unbreaks the explorer deployment, however we should find a fix for this issue
These issues are likely port collisions
2024-12-13T20:49:51.570827Z [chronik/chronik-lib/src/bridge.rs:181] [<chronik unknown>] Starting Chronik Electrum interface bound to [(127.0.0.1:33252, Tcp)] 2024-12-13T20:49:51.574474Z [chronik/chronik-indexer/src/indexer.rs:1491] [<chronik unknown>] Chronik Electrum failed serving: Address already in use (os error 98) 2024-12-13T20:49:51.574503Z [/work/src/shutdown.cpp:22] [AbortNode] *** ERROR Chronik in ChronikElectrumServer::serve 2024-12-13T20:49:51.574521Z [/work/src/noui.cpp:42] [noui_ThreadSafeMessageBox] Error: Chronik Electrum failed serving: Address already in use (os error 98)
Updating lint
Fri, Dec 13
There seems to be some kind if intermittent issue introduced by this diff or it's parent. To be investigated.
Deleted newline in hash.rs
Import chronik-proto from /chronik