Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
While debugging, i realised it was hard to follow and filter all the logs relatively to a single order.
As we can see here, some logs refer to some internal reference, but not all logs include it:
In this case, its hard for me to say if the API call is for that specific order.
Printing all the static input or the TX in each log is too verbose. This is why we give the order on each run a unique identifier:
ownerCount.orderCount@block
This will allow to find the order we want (by TX hash for example). After that we can filter for just that order and block easily
This is an example of an OUTPUT after the changes in this PR:
Result
This will make it super easy to check:
@29779465
, being 29779465 the block we want to see1.5@29779465
being 1 the owner internal count, and5
the internal count for the order.