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.
What
The problem now is that despite requests are cached the metrics are still showing that requests has happened.
Why
We want not to report cached responses in requests metrics.
How
So the order of the inject matters with web3 middlewares. When we inject middlewares with
level = 0
we always append to the end of the queue of middlewares. So to fail fast with cache middleware we need it to be injected first to achieve order:[..., cache middleware, other middlewares which we shouldn't reach after cache]