-
Notifications
You must be signed in to change notification settings - Fork 815
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fatxpool
: use tracing
instead of log
#5490
Comments
also: |
can i get to work on this? @michalkucharczyk |
Yes. |
A comment on how I see this. In general all Please do not change levels, and text messages. If the message contains already contains some "value: {}" or "value= {}", it should be migrated to the field. Example: polkadot-sdk/substrate/client/transaction-pool/src/fork_aware_txpool/fork_aware_txpool.rs Lines 485 to 493 in 82117ad
could be written more or less as the following: tracing::debug!(target: LOG_TARGET,
"fatp::ready_at_light",
at,
from = best_view.at.hash,
before = before_count,
to_be_removed = all_extrinsics.len(),
after,
took = start.elapsed()
); You could start with a single file, and ping me when you think it is done. We will discuss if it is OK, or if any improvements are needed. Does it sound ok for you? |
One more thought. On the polkadot-sdk/substrate/client/transaction-pool/src/fork_aware_txpool/fork_aware_txpool.rs Line 267 in 82117ad
polkadot-sdk/substrate/client/transaction-pool/src/fork_aware_txpool/fork_aware_txpool.rs Line 695 in 82117ad
and there is also macro that prints the iterator over transactions: polkadot-sdk/substrate/client/transaction-pool/src/fork_aware_txpool/fork_aware_txpool.rs Line 648 in 82117ad
I think we should get rid of the prefix in this case use the hash as regular field, e.g. |
Ok. Thank you for the clarifications. |
The text was updated successfully, but these errors were encountered: