-
Notifications
You must be signed in to change notification settings - Fork 1.3k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make processing burningman accounting data optional #6644
Make processing burningman accounting data optional #6644
Conversation
Signed-off-by: HenrikJannsen <[email protected]>
Add popup when selecting a burningman to ask for enabling processing Signed-off-by: HenrikJannsen <[email protected]>
… set. Signed-off-by: HenrikJannsen <[email protected]>
…t is in progress. We use a postfix to the header title and not a busy animation, as the busy animation is quite CPU intense. Signed-off-by: HenrikJannsen <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
utACK
@@ -160,6 +164,10 @@ public void onParseBlockChainComplete() { | |||
|
|||
@Override | |||
public void addListeners() { | |||
if (!preferences.isProcessBurningManAccountingData()) { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
A problem (bug) here is it prevents seednodes from processing Accounting data! 😱
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I can confirm the bug!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Saw it too late, but seem its fixed by @jmacxx already
Processing burningman accounting data an take quite some time and CPU. As most Bisq users are likely not interested in those data, this PR deactivates it by default.
Users who are interested in that data can enable it in the settings at the DAO section (requires restart) or when selecting a BM in the table they get a popup to enable it.
If not enabled the UI shows a "(accounting data not updated)" post fix to the "Selected contributor" header. The displayed data is the one from the last update or the one shipped by the release.
If enabled and still processing data we show a "(still processing data...)" post fix to the "Selected contributor" header.
We do not use a busy animation as this is quite CPU intense.
Once all data is processed the post fix is removed.