You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 11, 2024. It is now read-only.
Peers should be passed down correctly after each filter stage.
Actual behavior
At latency stage, if latency protection not set, selected peers were reverting back to original peers instead of the peers from the prior filtering stage.
Steps to reproduce
npm t
Which version(s) does this affect? (Environment, OS, etc...)
2.3
The text was updated successfully, but these errors were encountered:
Expected behavior
Peers should be passed down correctly after each filter stage.
Actual behavior
At latency stage, if latency protection not set, selected peers were reverting back to original peers instead of the peers from the prior filtering stage.
Steps to reproduce
npm t
Which version(s) does this affect? (Environment, OS, etc...)
2.3
The text was updated successfully, but these errors were encountered: