Updating comment (linter plz dont kill me )
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Feb 24 2025
Updated !unreachable() comment and removed assert comments
Merged imports
Updated the assert!() so that it will now anticipate 404 errors, renamed function names to be explicit
don't shadow j either
Rename blockchain_info_ipc
To ensure no breaking changes from the updated IPC file, run ./contrib/teamcity/build-configurations.py chronik-client-integration-tests from bitcoin-abc to run typescript tests.
Maybe we could actually print to stdout what step is running and what it does instead of the comment, since stdout is captured by default and not shown upon success. But we can do that later if it feels necessary.
I can see a reason to enforce the char limit. When dealing with UI representation of the donation address, you can be certain that it will fit in your UI field that way.
Another reason is that an abc server might be rejected for invalid content by clients checking the limit if such a thing exists.
Feb 23 2025
CI failure most likely unrelated, but will have to investigate anyway (tomorrow)
Feb 22 2025
Backported as a dependency of https://github.com/bitcoin/bitcoin/pull/27596/commits/f073917a9e7ba423643dcae0339776470b628f65
lint
lint
fix comment layout
Feb 21 2025
Please make the linter happy
back to your queue
remove debug log
rebase
Still lgtm
Added unreachable panic, renamed test_blockchain_info to blockchain_info and added comments
more finds
works on my machine
more atoms_vec finds
apologies for the phab noise here ... not sure how to find all these locally. ninja check-functional is passing
more atoms_vec