Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

Parity default paths changed. (app-dirs) #8418

Closed
cosminstefane opened this issue Apr 17, 2018 · 5 comments
Closed

Parity default paths changed. (app-dirs) #8418

cosminstefane opened this issue Apr 17, 2018 · 5 comments
Labels
F2-bug 🐞 The client fails to follow expected behavior. M2-config 📂 Chain specifications and node configurations. P0-dropeverything 🌋 Everyone should address the issue now.

Comments

@cosminstefane
Copy link

cosminstefane commented Apr 17, 2018

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.

@Tbaut
Copy link
Contributor

Tbaut commented Apr 17, 2018

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

@Tbaut Tbaut added Z1-question 🙋‍♀️ Issue is a question. Closer should answer. Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. M2-config 📂 Chain specifications and node configurations. labels Apr 17, 2018
@Tbaut Tbaut added this to the 1.11 milestone Apr 17, 2018
@cosminstefane
Copy link
Author

cosminstefane commented Apr 17, 2018

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.

@5chdn 5chdn added F2-bug 🐞 The client fails to follow expected behavior. P0-dropeverything 🌋 Everyone should address the issue now. and removed Z0-unconfirmed 🤔 Issue might be valid, but it’s not yet known. Z1-question 🙋‍♀️ Issue is a question. Closer should answer. labels Apr 17, 2018
@5chdn
Copy link
Contributor

5chdn commented Apr 17, 2018

Introduced in #8355 via andybarron/app-dirs-rs#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 Data

Note: This is a breaking change so if this project follows semantic versioning it should be released as a major version bump.

@5chdn 5chdn changed the title Parity ignores config file Parity default paths changed. (app-dirs) Apr 17, 2018
@5chdn
Copy link
Contributor

5chdn commented Apr 17, 2018

@cosminstefane please downgrade to 1.9.5 while we work on a solution

@cosminstefane
Copy link
Author

Already did, thanks!

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
F2-bug 🐞 The client fails to follow expected behavior. M2-config 📂 Chain specifications and node configurations. P0-dropeverything 🌋 Everyone should address the issue now.
Projects
None yet
Development

No branches or pull requests

3 participants