_Before filing a new issue, please provide the following information._
I'm running:
- Which Parity version?: 1.9.6 and 1.10.1
- Which operating system?: Windows
- How installed?: via installer
- Are you fully synchronized?: yes
- Which network are you connected to?: ethereum
- Did you try to restart the node?: yes
_Your issue description goes here below. Try to include actual vs. expected behavior and steps to reproduce the issue._
I updated parity first to 1.9.6 after running 1.9.5. For some reason it doesn't load up the config.toml file. Even when I use -c options it tells me the config is not a preset. I need to run parity with some settings, including non-standard location for the DB. Tried 1.10.1 and it's the same.
You most probably have changed the work directory and your config file isn't found. How do you launch parity ? can you paste the logs here?
Try parity --config /absolute/path/to/config.toml
I did and it works. I believe the default locations have been changed on windows somehow. I also noticed neither one of my accounts are "imported" into parity either.
1.10.1 Keys path C:\Users\XXX\AppData*Local\Parity\Ethereum\keys\Foundation
1.9.5 Keys path C:\Users\XXX\AppData*Roaming\Parity\Ethereum\keys\Foundation
For some reason the location changed from ROAMING as before to LOCAL...
This is not expected behavior for upgrade.
I have tried 1.9.6 and location also changed in LOCAL. That's why it was not working.
Is this normal behavior? I haven't seen such info in the changes for 1.9.6.
Introduced in #8355 via https://github.com/AndyBarron/app-dirs-rs/pull/18:
This changes the location of several folders to match Windows standards. The full list can be found at https://msdn.microsoft.com/en-us/library/windows/desktop/dd378457(v=vs.85).aspx, though you will have to go to other MSDN articles to get details of their intended use:
Local App Data
Roaming App Data
Program DataNote: This is a breaking change so if this project follows semantic versioning it should be released as a major version bump.
@cosminstefane please downgrade to 1.9.5 while we work on a solution
Already did, thanks!