This repository has been archived by the owner on Oct 19, 2024. It is now read-only.
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.
Motivation
There is a problem currently in EscalatingPending Future implementation, which is responsible for backing the
send_escalating
method inMiddleware
.The problem is in the part of the Future which tests for the
nonce too low
issues. That test consists of checking if the error'sDisplay
contains stringnonce too low
. The point here is that the error's display might not havenonce too low
. For instance, a custom error's Display might not provide the desirednonce too low
, while Debug would. Here is an example from POC which shows Display (error_display
) and Debug(error_debug
) of an errorDebug line produces:
Solution
Obviously, Debug includes wrapped parts, which expose the desired line, whereas Display shows only
Max requests reached
. In order to fix the test I propose to change the format fromformat!("{}", e)
toformat!("{:?}", e)
, which would expose the debug.