Cannot change anonymity levels with persistence between runs. #2722

davterra · 2019-12-05T14:51:46Z

I am not able to change the anonymity levels in my settings and have the changes be persistent from one run to another. They appear to "stick" when changed, but upon restart revert to the original 2/21/50 setting.
Using Ubuntu 19.04 + i3

MaxHillebrand · 2019-12-05T15:45:24Z

I can reproduce on Qubes 4 Debian 10.
The anonset target is not remembered and sets back to the default.

davterra · 2019-12-05T17:47:47Z

UPDATE:
I find that, after changing my anonymity levels, if I leave the settings window open when I exit wasabi, the new/desired settings persist. If I close the settings window before I exit wasabi, the new/desired anonymity settings are gone, replaced by previous settings.

Perhaps the settings window could eventually benefit from a "Save Settings" button to both ensure all changes are saved, and to give the user confidence that changes have been recorded. It's relatively uncommon, IMO to see a site's setting page not give the user a "Save" button of some kind to push, even if it's technically not necessary to save any changes.

kravens · 2019-12-05T18:01:57Z

On Windows 10 I can change anonymity levels, restart WasabiWallet, and see the new levels in effect.
Also when I close the Settings tab before restarting, the new levels are in effect after restart of WasabiWallet.
So can't reproduce this on W10 with i7 CPU.

molnard · 2019-12-06T09:06:45Z

The issue accepted 2 points.

RiccardoMasutti · 2019-12-06T10:10:10Z

UPDATE:
I find that, after changing my anonymity levels, if I leave the settings window open when I exit wasabi, the new/desired settings persist. If I close the settings window before I exit wasabi, the new/desired anonymity settings are gone, replaced by previous settings.

Perhaps the settings window could eventually benefit from a "Save Settings" button to both ensure all changes are saved, and to give the user confidence that changes have been recorded. It's relatively uncommon, IMO to see a site's setting page not give the user a "Save" button of some kind to push, even if it's technically not necessary to save any changes.

Had the same problem and I can reproduce that on Debian 10 and TAILS.

MaxHillebrand · 2019-12-08T15:26:59Z

Agreed with @molnard , this issue is 2 points, good catch

nopara73 · 2019-12-09T10:25:24Z

It's something that must be fixed for the release so I put it to the 3 point category.

nopara73 · 2019-12-09T11:02:13Z

I take it.

nopara73 · 2019-12-09T11:07:04Z

I am not able to change the anonymity levels in my settings and have the changes be persistent from one run to another. They appear to "stick" when changed, but upon restart revert to the original 2/21/50 setting.
Using Ubuntu 19.04 + i3

I cannot reproduce it. (win10)

Open Wasabi.
Go to Settings.
Change an anonset level.
Close Wasabi.
Open again.
See anonset level change persisted as it should.

nopara73 · 2019-12-09T11:09:40Z

The anonset target is not remembered and sets back to the default.

@MaxHillebrand That is a different issue. I cannot reproduce that either. (win10)

Open Wasabi.
Load a wallet.
Change anonset target.
Close Wasabi.
Open and load again.
See anonset target change persisted as it should.

nopara73 · 2019-12-09T11:11:56Z

I find that, after changing my anonymity levels, if I leave the settings window open when I exit wasabi, the new/desired settings persist. If I close the settings window before I exit wasabi, the new/desired anonymity settings are gone, replaced by previous settings.

I cannot reproduce it either. (win10)

Open Wasabi.
Go to Settings.
Change an anonset level.
Close Settings.
Close Wasabi.
Open again.
See anonset level change persisted as it should.

nopara73 · 2019-12-09T11:13:55Z

Perhaps the settings window could eventually benefit from a "Save Settings" button to both ensure all changes are saved, and to give the user confidence that changes have been recorded. It's relatively uncommon, IMO to see a site's setting page not give the user a "Save" button of some kind to push, even if it's technically not necessary to save any changes.

ACK. As a historical context, the settings did not have any text input field when we decided on this, it was just dropdowns. The text input fields makes things interesting.

nopara73 · 2019-12-09T11:16:40Z

So, the issue doesn't happen on Windows 10, neither me nor @kravens can reproduce it. It's really strange though. There's no platform specific or suspect code to around to cause anything like this. Anyhow, turning to our resident Linux gurus, @lontivero or @jmacato can you take it over?

molnard · 2019-12-09T11:37:26Z

Neither on win10 or macOS I could reproduce. It looks like a Linux only problem.

lontivero · 2019-12-09T13:07:05Z

I've being playing with these levels for almost and hour and I cannot reproduce on Ubuntu. We need the step-by-step how to reproduce it and also the log entries, if there is any related. Otherwise I think we will not be able to catch this one.

nopara73 · 2019-12-09T13:09:47Z

Maybe it was in the released version, but not on the master. Anyway, at this point I think we should close this.

jmacato · 2019-12-09T13:13:20Z

Yeah, can't repro this on either Manjaro ARM nor Ubuntu 18.04 LTS with latest master branch

RiccardoMasutti · 2019-12-09T16:44:29Z

I'm still investigating.

lontivero · 2019-12-09T22:13:22Z

@davterra could you share your Config.json and UiConfig.json here?

davterra · 2019-12-09T22:58:45Z

Yes, happy to....but can't until I get home.... about an hour from now....will post as soon as possible.

davterra · 2019-12-09T23:44:49Z

@lontivero

OK,
ICYMI, here is a more detailed description of how to replicate the issue:

There are two procedures that I've been testing.
Procedure # 1 does NOT result in updated anonymity params,
Procedure # 2 DOES result in updated anonymity params.

Procedure #1:

start wasabi
open settings
change anonymity settings
close settings tab
reopen settings tab to verify new params still there.
close settings tab
exit wasabi
restart wasabi
open settings tab. When I follow this procedure, my A.S. settings
are not as they were when I exited wasabi. They reflect prior settings, instead of the update.

Procedure #2:

start wasabi
open settings
change A.S. params
LEAVE SETTINGS TAB OPEN & exit wasabi
restart wasabi
open settings tab. When I follow this procedure, my A.S. settings are as
they were when I exited wasabi - Updated and correct.

config.json:
{
"Network": "TestNet",
"MainNetBackendUriV3": "http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion/",
"TestNetBackendUriV3": "http://testwnp3fugjln6vh5vpj7mvq3lkqqwjj3c2aafyu7laxz42kgwh2rad.onion/",
"MainNetFallbackBackendUri": "https://wasabiwallet.io/",
"TestNetFallbackBackendUri": "https://wasabiwallet.co/",
"RegTestBackendUriV3": "http://localhost:37127/",
"UseTor": true,
"StartLocalBitcoinCoreOnStartup": false,
"StopLocalBitcoinCoreOnShutdown": true,
"LocalBitcoinCoreDataDir": "/home/user/.bitcoin",
"TorSocks5EndPoint": "127.0.0.1:9050",
"MainNetBitcoinP2pEndPoint": "tralfaz.dynu.net:8333",
"TestNetBitcoinP2pEndPoint": "127.0.0.1:18333",
"RegTestBitcoinP2pEndPoint": "127.0.0.1:18444",
"MixUntilAnonymitySet": 100,
"PrivacyLevelSome": 44,
"PrivacyLevelFine": 77,
"PrivacyLevelStrong": 101,
"DustThreshold": "0.0001"
}

UiConfig.json:

{
"WindowState": "Maximized",
"Height": 815.0,
"Width": 1600.0,
"FeeTarget": 2,
"FeeDisplayFormat": 3,
"Autocopy": true,
"IsCustomFee": false,
"LurkingWifeMode": false,
"LockScreenActive": false,
"LockScreenPinHash": ""
}

Logs.txt

UNSUCCESSFUL ATTEMPT IN UPDATING ANON SET PARAMS IN THE BELOW RUN, BY CLOSING SETTING TAB BEFORE EXITING

2019-12-09 15:03:54 INFO Program (44) Wasabi GUI started (1e90f063-f152-4a92-b96a-b6928dd29254).
2019-12-09 15:03:56 INFO Global (158) Config is successfully initialized.
2019-12-09 15:03:56 INFO TorProcessManager (249) Starting Tor monitor...
2019-12-09 15:03:56 INFO Global (220) TorProcessManager is initialized.
2019-12-09 15:03:56 INFO TransactionStore (28) MempoolStore.InitializeAsync finished in 202 milliseconds.
2019-12-09 15:03:57 INFO TransactionStore (28) ConfirmedStore.InitializeAsync finished in 289 milliseconds.
2019-12-09 15:03:57 INFO AllTransactionStore (27) InitializeAsync finished in 363 milliseconds.
2019-12-09 15:03:57 INFO TorProcessManager (66) Tor is already running.
2019-12-09 15:04:00 INFO Global (387) Loaded AddressManager from /home/user/.walletwasabi/client/AddressManager/AddressManagerTestNet.dat.
2019-12-09 15:04:00 INFO MainWindow.xaml (74) UiConfig is successfully initialized.
2019-12-09 15:04:06 INFO IndexStore (43) InitializeAsync finished in 10 seconds.
2019-12-09 15:04:06 INFO BitcoinStore (39) InitializeAsync finished in 10 seconds.
2019-12-09 15:04:06 INFO HostedServices (49) Stared Software Update Checker.
2019-12-09 15:04:06 INFO Global (329) Start connecting to nodes...
2019-12-09 15:04:06 INFO Global (351) Start synchronizing filters...
2019-12-09 15:04:24 INFO MainWindow.xaml (168) UiConfig is saved.
2019-12-09 15:04:24 INFO MainWindow.xaml (176) WalletManagerViewModel closed.
2019-12-09 15:04:24 INFO Global (775) Disposed FeeProviders.
2019-12-09 15:04:24 INFO Global (782) CoinJoinProcessor is disposed.
2019-12-09 15:04:24 INFO Global (789) Synchronizer is stopped.
2019-12-09 15:04:24 INFO HostedServices (78) Stopped Software Update Checker.
2019-12-09 15:04:24 INFO HostedServices (130) Disposed Software Update Checker.
2019-12-09 15:04:24 INFO Global (798) Stopped background services.
2019-12-09 15:04:24 INFO Global (809) AddressManager is saved to /home/user/.walletwasabi/client/AddressManager/AddressManagerTestNet.dat.
2019-12-09 15:04:24 INFO Global (822) Nodes are disposed.
2019-12-09 15:04:25 INFO Global (847) TorManager is stopped.
2019-12-09 15:04:25 INFO Global (855) AsyncMutex(es) are stopped.
2019-12-09 15:04:25 INFO Program (62) Wasabi GUI stopped gracefully (1e90f063-f152-4a92-b96a-b6928dd29254).

SUCCESSFULLY UPDATED ANON SET PARAMS IN THE BELOW RUN, BY EXITING WITH SETTINGS TAB OPEN

2019-12-09 15:04:31 INFO Program (44) Wasabi GUI started (94efa5ea-4f9c-45cc-941a-ea5b2b2e54b9).
2019-12-09 15:04:34 INFO Global (158) Config is successfully initialized.
2019-12-09 15:04:35 INFO TorProcessManager (249) Starting Tor monitor...
2019-12-09 15:04:35 INFO Global (220) TorProcessManager is initialized.
2019-12-09 15:04:35 INFO TransactionStore (28) MempoolStore.InitializeAsync finished in 419 milliseconds.
2019-12-09 15:04:35 INFO TransactionStore (28) ConfirmedStore.InitializeAsync finished in 507 milliseconds.
2019-12-09 15:04:35 INFO AllTransactionStore (27) InitializeAsync finished in 568 milliseconds.
2019-12-09 15:04:36 INFO TorProcessManager (66) Tor is already running.
2019-12-09 15:04:36 INFO Global (387) Loaded AddressManager from /home/user/.walletwasabi/client/AddressManager/AddressManagerTestNet.dat.
2019-12-09 15:04:36 INFO MainWindow.xaml (74) UiConfig is successfully initialized.
2019-12-09 15:04:44 INFO IndexStore (43) InitializeAsync finished in 9 seconds.
2019-12-09 15:04:44 INFO BitcoinStore (39) InitializeAsync finished in 9 seconds.
2019-12-09 15:04:44 INFO HostedServices (49) Stared Software Update Checker.
2019-12-09 15:04:44 INFO Global (329) Start connecting to nodes...
2019-12-09 15:04:44 INFO Global (351) Start synchronizing filters...
2019-12-09 15:04:52 INFO MainWindow.xaml (168) UiConfig is saved.
2019-12-09 15:04:52 INFO MainWindow.xaml (176) WalletManagerViewModel closed.
2019-12-09 15:04:52 INFO Global (775) Disposed FeeProviders.
2019-12-09 15:04:52 INFO Global (782) CoinJoinProcessor is disposed.
2019-12-09 15:04:52 INFO Global (789) Synchronizer is stopped.
2019-12-09 15:04:52 INFO HostedServices (78) Stopped Software Update Checker.
2019-12-09 15:04:52 INFO HostedServices (130) Disposed Software Update Checker.
2019-12-09 15:04:52 INFO Global (798) Stopped background services.
2019-12-09 15:04:52 INFO Global (809) AddressManager is saved to /home/user/.walletwasabi/client/AddressManager/AddressManagerTestNet.dat.
2019-12-09 15:04:52 INFO Global (822) Nodes are disposed.
2019-12-09 15:04:52 INFO Global (847) TorManager is stopped.
2019-12-09 15:04:52 INFO Global (855) AsyncMutex(es) are stopped.
2019-12-09 15:04:52 INFO Program (62) Wasabi GUI stopped gracefully (94efa5ea-4f9c-45cc-941a-ea5b2b2e54b9).

RiccardoMasutti · 2019-12-10T00:58:27Z

@lontivero

OK,
ICYMI, here is a more detailed description of how to replicate the issue:

There are two procedures that I've been testing.
Procedure # 1 does NOT result in updated anonymity params,
Procedure # 2 DOES result in updated anonymity params.

Procedure #1:

start wasabi

open settings

change anonymity settings

close settings tab

reopen settings tab to verify new params still there.

close settings tab

exit wasabi

restart wasabi

open settings tab. When I follow this procedure, my A.S. settings
are not as they were when I exited wasabi. They reflect prior settings, instead of the update.

Procedure #2:

start wasabi

open settings

change A.S. params

LEAVE SETTINGS TAB OPEN & exit wasabi

restart wasabi

open settings tab. When I follow this procedure, my A.S. settings are as
they were when I exited wasabi - Updated and correct.

config.json:
{
"Network": "TestNet",
"MainNetBackendUriV3": "http://wasabiukrxmkdgve5kynjztuovbg43uxcbcxn6y2okcrsg7gb6jdmbad.onion/",
"TestNetBackendUriV3": "http://testwnp3fugjln6vh5vpj7mvq3lkqqwjj3c2aafyu7laxz42kgwh2rad.onion/",
"MainNetFallbackBackendUri": "https://wasabiwallet.io/",
"TestNetFallbackBackendUri": "https://wasabiwallet.co/",
"RegTestBackendUriV3": "http://localhost:37127/",
"UseTor": true,
"StartLocalBitcoinCoreOnStartup": false,
"StopLocalBitcoinCoreOnShutdown": true,
"LocalBitcoinCoreDataDir": "/home/user/.bitcoin",
"TorSocks5EndPoint": "127.0.0.1:9050",
"MainNetBitcoinP2pEndPoint": "tralfaz.dynu.net:8333",
"TestNetBitcoinP2pEndPoint": "127.0.0.1:18333",
"RegTestBitcoinP2pEndPoint": "127.0.0.1:18444",
"MixUntilAnonymitySet": 100,
"PrivacyLevelSome": 44,
"PrivacyLevelFine": 77,
"PrivacyLevelStrong": 101,
"DustThreshold": "0.0001"
}

UiConfig.json:

{
"WindowState": "Maximized",
"Height": 815.0,
"Width": 1600.0,
"FeeTarget": 2,
"FeeDisplayFormat": 3,
"Autocopy": true,
"IsCustomFee": false,
"LurkingWifeMode": false,
"LockScreenActive": false,
"LockScreenPinHash": ""
}

Logs.txt

UNSUCCESSFUL ATTEMPT IN UPDATING ANON SET PARAMS IN THE BELOW RUN, BY CLOSING SETTING TAB BEFORE EXITING

2019-12-09 15:03:54 INFO Program (44) Wasabi GUI started (1e90f063-f152-4a92-b96a-b6928dd29254).
2019-12-09 15:03:56 INFO Global (158) Config is successfully initialized.
2019-12-09 15:03:56 INFO TorProcessManager (249) Starting Tor monitor...
2019-12-09 15:03:56 INFO Global (220) TorProcessManager is initialized.
2019-12-09 15:03:56 INFO TransactionStore (28) MempoolStore.InitializeAsync finished in 202 milliseconds.
2019-12-09 15:03:57 INFO TransactionStore (28) ConfirmedStore.InitializeAsync finished in 289 milliseconds.
2019-12-09 15:03:57 INFO AllTransactionStore (27) InitializeAsync finished in 363 milliseconds.
2019-12-09 15:03:57 INFO TorProcessManager (66) Tor is already running.
2019-12-09 15:04:00 INFO Global (387) Loaded AddressManager from /home/user/.walletwasabi/client/AddressManager/AddressManagerTestNet.dat.
2019-12-09 15:04:00 INFO MainWindow.xaml (74) UiConfig is successfully initialized.
2019-12-09 15:04:06 INFO IndexStore (43) InitializeAsync finished in 10 seconds.
2019-12-09 15:04:06 INFO BitcoinStore (39) InitializeAsync finished in 10 seconds.
2019-12-09 15:04:06 INFO HostedServices (49) Stared Software Update Checker.
2019-12-09 15:04:06 INFO Global (329) Start connecting to nodes...
2019-12-09 15:04:06 INFO Global (351) Start synchronizing filters...
2019-12-09 15:04:24 INFO MainWindow.xaml (168) UiConfig is saved.
2019-12-09 15:04:24 INFO MainWindow.xaml (176) WalletManagerViewModel closed.
2019-12-09 15:04:24 INFO Global (775) Disposed FeeProviders.
2019-12-09 15:04:24 INFO Global (782) CoinJoinProcessor is disposed.
2019-12-09 15:04:24 INFO Global (789) Synchronizer is stopped.
2019-12-09 15:04:24 INFO HostedServices (78) Stopped Software Update Checker.
2019-12-09 15:04:24 INFO HostedServices (130) Disposed Software Update Checker.
2019-12-09 15:04:24 INFO Global (798) Stopped background services.
2019-12-09 15:04:24 INFO Global (809) AddressManager is saved to /home/user/.walletwasabi/client/AddressManager/AddressManagerTestNet.dat.
2019-12-09 15:04:24 INFO Global (822) Nodes are disposed.
2019-12-09 15:04:25 INFO Global (847) TorManager is stopped.
2019-12-09 15:04:25 INFO Global (855) AsyncMutex(es) are stopped.
2019-12-09 15:04:25 INFO Program (62) Wasabi GUI stopped gracefully (1e90f063-f152-4a92-b96a-b6928dd29254).

SUCCESSFULLY UPDATED ANON SET PARAMS IN THE BELOW RUN, BY EXITING WITH SETTINGS TAB OPEN

2019-12-09 15:04:31 INFO Program (44) Wasabi GUI started (94efa5ea-4f9c-45cc-941a-ea5b2b2e54b9).
2019-12-09 15:04:34 INFO Global (158) Config is successfully initialized.
2019-12-09 15:04:35 INFO TorProcessManager (249) Starting Tor monitor...
2019-12-09 15:04:35 INFO Global (220) TorProcessManager is initialized.
2019-12-09 15:04:35 INFO TransactionStore (28) MempoolStore.InitializeAsync finished in 419 milliseconds.
2019-12-09 15:04:35 INFO TransactionStore (28) ConfirmedStore.InitializeAsync finished in 507 milliseconds.
2019-12-09 15:04:35 INFO AllTransactionStore (27) InitializeAsync finished in 568 milliseconds.
2019-12-09 15:04:36 INFO TorProcessManager (66) Tor is already running.
2019-12-09 15:04:36 INFO Global (387) Loaded AddressManager from /home/user/.walletwasabi/client/AddressManager/AddressManagerTestNet.dat.
2019-12-09 15:04:36 INFO MainWindow.xaml (74) UiConfig is successfully initialized.
2019-12-09 15:04:44 INFO IndexStore (43) InitializeAsync finished in 9 seconds.
2019-12-09 15:04:44 INFO BitcoinStore (39) InitializeAsync finished in 9 seconds.
2019-12-09 15:04:44 INFO HostedServices (49) Stared Software Update Checker.
2019-12-09 15:04:44 INFO Global (329) Start connecting to nodes...
2019-12-09 15:04:44 INFO Global (351) Start synchronizing filters...
2019-12-09 15:04:52 INFO MainWindow.xaml (168) UiConfig is saved.
2019-12-09 15:04:52 INFO MainWindow.xaml (176) WalletManagerViewModel closed.
2019-12-09 15:04:52 INFO Global (775) Disposed FeeProviders.
2019-12-09 15:04:52 INFO Global (782) CoinJoinProcessor is disposed.
2019-12-09 15:04:52 INFO Global (789) Synchronizer is stopped.
2019-12-09 15:04:52 INFO HostedServices (78) Stopped Software Update Checker.
2019-12-09 15:04:52 INFO HostedServices (130) Disposed Software Update Checker.
2019-12-09 15:04:52 INFO Global (798) Stopped background services.
2019-12-09 15:04:52 INFO Global (809) AddressManager is saved to /home/user/.walletwasabi/client/AddressManager/AddressManagerTestNet.dat.
2019-12-09 15:04:52 INFO Global (822) Nodes are disposed.
2019-12-09 15:04:52 INFO Global (847) TorManager is stopped.
2019-12-09 15:04:52 INFO Global (855) AsyncMutex(es) are stopped.
2019-12-09 15:04:52 INFO Program (62) Wasabi GUI stopped gracefully (94efa5ea-4f9c-45cc-941a-ea5b2b2e54b9).

I will try asap

lontivero · 2019-12-10T04:33:34Z

I don't see anything wrong.

davterra · 2019-12-10T13:18:54Z

@MaxHillebrand and @simonebovi are you still able to replicate this?
Simone said as recently as yesterday 12/9 that he could replicate, presumably with his Mac/Catalina.
Not had an update from Max since the changes to Master.

ghost · 2019-12-10T16:50:32Z

@davterra I just tried with the latest master and I can still replicate this following your 1st procedure using macOS Catalina.

davterra · 2019-12-10T16:57:47Z

Thanks, with mixed emotions. I'd like it if no one, including myself could replicate this, but it's also nice to know it's not just my particular setup/environment.

MaxHillebrand · 2019-12-11T09:54:59Z

Tested on Qubes 4 Debian 10 & Fedora 30

Procedure #1:

Does not safe anonset targets, they are reset to the previous

start wasabi
open settings
change anonymity settings
close settings tab
reopen settings tab to verify new params still there.
close settings tab
exit wasabi
restart wasabi
open settings tab. When I follow this procedure, my A.S. settings
are not as they were when I exited wasabi. They reflect prior settings, instead of the update.

Procedure #2:

Does safe anonset targets, they are not reset to the previous

start wasabi
open settings
change A.S. params
LEAVE SETTINGS TAB OPEN & exit wasabi
restart wasabi
open settings tab. When I follow this procedure, my A.S. settings are as
they were when I exited wasabi - Updated and correct.

MaxHillebrand added the debug label Dec 5, 2019

nopara73 added this to ToDo in 1.1.10 via automation Dec 5, 2019

molnard added this to Issues to qualify in Contribution Game Reviewed (1.1.10) via automation Dec 6, 2019

molnard moved this from Issues to qualify to Issues (2 points) in Contribution Game Reviewed (1.1.10) Dec 6, 2019

molnard added this to the Review contribution game milestone Dec 6, 2019

nopara73 removed this from ToDo in 1.1.10 Dec 8, 2019

nopara73 moved this from Issues (2 points) to Painful issues (3 points) in Contribution Game Reviewed (1.1.10) Dec 8, 2019

nopara73 closed this as completed Dec 9, 2019

molnard mentioned this issue Dec 9, 2019

[FINISHED] Contribution Game for Review of v1.1.10 #2631

Closed

RiccardoMasutti mentioned this issue Dec 9, 2019

refocus the textbox when context menu closes. #2820

Merged

nopara73 reopened this Dec 10, 2019

nopara73 moved this from Painful issues (3 points) to Issues (2 points) in Contribution Game Reviewed (1.1.10) Dec 10, 2019

MaxHillebrand assigned nopara73 Dec 11, 2019

davterra mentioned this issue Dec 13, 2019

Final tests before release 1.1.10 #2721

Closed

molnard mentioned this issue Dec 13, 2019

Prevent Save before load #2851

Merged

molnard closed this as completed in #2851 Dec 13, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Cannot change anonymity levels with persistence between runs. #2722

Cannot change anonymity levels with persistence between runs. #2722

davterra commented Dec 5, 2019 •

edited

Loading

MaxHillebrand commented Dec 5, 2019

davterra commented Dec 5, 2019 •

edited

Loading

kravens commented Dec 5, 2019

molnard commented Dec 6, 2019

RiccardoMasutti commented Dec 6, 2019

MaxHillebrand commented Dec 8, 2019

nopara73 commented Dec 9, 2019

nopara73 commented Dec 9, 2019

nopara73 commented Dec 9, 2019 •

edited

Loading

nopara73 commented Dec 9, 2019 •

edited

Loading

nopara73 commented Dec 9, 2019 •

edited

Loading

nopara73 commented Dec 9, 2019 •

edited

Loading

nopara73 commented Dec 9, 2019

molnard commented Dec 9, 2019

lontivero commented Dec 9, 2019

nopara73 commented Dec 9, 2019

jmacato commented Dec 9, 2019 •

edited

Loading

RiccardoMasutti commented Dec 9, 2019

lontivero commented Dec 9, 2019

davterra commented Dec 9, 2019

davterra commented Dec 9, 2019 •

edited

Loading

RiccardoMasutti commented Dec 10, 2019

lontivero commented Dec 10, 2019

davterra commented Dec 10, 2019

ghost commented Dec 10, 2019 •

edited by ghost

Loading

davterra commented Dec 10, 2019

MaxHillebrand commented Dec 11, 2019

Cannot change anonymity levels with persistence between runs. #2722

Cannot change anonymity levels with persistence between runs. #2722

Comments

davterra commented Dec 5, 2019 • edited Loading

MaxHillebrand commented Dec 5, 2019

davterra commented Dec 5, 2019 • edited Loading

kravens commented Dec 5, 2019

molnard commented Dec 6, 2019

RiccardoMasutti commented Dec 6, 2019

MaxHillebrand commented Dec 8, 2019

nopara73 commented Dec 9, 2019

nopara73 commented Dec 9, 2019

nopara73 commented Dec 9, 2019 • edited Loading

nopara73 commented Dec 9, 2019 • edited Loading

nopara73 commented Dec 9, 2019 • edited Loading

nopara73 commented Dec 9, 2019 • edited Loading

nopara73 commented Dec 9, 2019

molnard commented Dec 9, 2019

lontivero commented Dec 9, 2019

nopara73 commented Dec 9, 2019

jmacato commented Dec 9, 2019 • edited Loading

RiccardoMasutti commented Dec 9, 2019

lontivero commented Dec 9, 2019

davterra commented Dec 9, 2019

davterra commented Dec 9, 2019 • edited Loading

RiccardoMasutti commented Dec 10, 2019

lontivero commented Dec 10, 2019

davterra commented Dec 10, 2019

ghost commented Dec 10, 2019 • edited by ghost Loading

davterra commented Dec 10, 2019

MaxHillebrand commented Dec 11, 2019

Does not safe anonset targets, they are reset to the previous

Does safe anonset targets, they are not reset to the previous

davterra commented Dec 5, 2019 •

edited

Loading

davterra commented Dec 5, 2019 •

edited

Loading

nopara73 commented Dec 9, 2019 •

edited

Loading

nopara73 commented Dec 9, 2019 •

edited

Loading

nopara73 commented Dec 9, 2019 •

edited

Loading

nopara73 commented Dec 9, 2019 •

edited

Loading

jmacato commented Dec 9, 2019 •

edited

Loading

davterra commented Dec 9, 2019 •

edited

Loading

ghost commented Dec 10, 2019 •

edited by ghost

Loading