pricenode goes out of sync (or degrades)

[bieber-t-beaver]

Description Maker-Taker obtains prices from pricenodes, should be within a tolerance to execute the trade. However, if one party's instance uses a pricenode that, for whatever reason is malfunctioning, one of the party (or both?) will receive the following error:

[JavaFX Application Thread] ERROR bisq.core.offer.Offer: An error occurred at task: ProcessOfferAvailabilityResponse Cannot take offer because taker's price is outside tolerance.

From a matrix thread, @suddenwhipvapor provided the following clarification on the root cause: "for some reason the two (pricenodes) are seeing an average different price from trackers.. , restarting could get you lucky and connected to the same node of the peer so the price on both sides is the same."

Version 1.19.17

Steps to reproduce

If you launch two separate clients - force one connected to a price node P1, and the other to P2; One attempts to take an offer, posted by the other.

Expected behaviour

pricenode should be consistent, and allow the trade to execute as expected. if unable to furnish the correct price, client should redirect to a reliable one --- restarting and getting lucky, as suggested, is not ideal.

Actual behaviour

both Taker and Maker (?) received the error provided above. Taker unable to execute any trade with specific peers Maker unable to complete complete their offer because its price is not within tolerance.

Screenshots

Device or machine

Linux

Additional info

There's no notification within the Support forums regarding an outage.

[boring-cyborg[bot]]

Thanks for opening your first issue here!

Be sure to follow the issue template. Your issue will be reviewed by a maintainer and labeled for further action.

[github-actions[bot]]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[github-actions[bot]]

This issue has been automatically closed because of inactivity. Feel free to reopen it if you think it is still relevant.