You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.
F2-bug 🐞The client fails to follow expected behavior.M4-core ⛓Core client code / Rust.P2-asap 🌊No need to stop dead in your tracks, however issue should be addressed as soon as possible.Q2-easy 💃Can be fixed by copy and pasting from StackOverflow.
The text was updated successfully, but these errors were encountered:
5chdn
added
F2-bug 🐞
The client fails to follow expected behavior.
M4-core ⛓
Core client code / Rust.
P2-asap 🌊
No need to stop dead in your tracks, however issue should be addressed as soon as possible.
labels
Nov 24, 2017
I've been unable to reproduce this. The --no-periodic-snapshot flag is parsed correctly and the snapshot watcher service is not started. Is this still happening to you? Do you have more of the logs available?
Version Parity/v1.8.4-beta-c74c8c1-20171211/x86_64-linux-gnu/rustc1.22.1 does not produce this, so I think its solved.
The snapshots folder is also empty.
I checked out v1.8.3 and couldn't reproduce it there either. Please reopen if you see this happen again.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
F2-bug 🐞The client fails to follow expected behavior.M4-core ⛓Core client code / Rust.P2-asap 🌊No need to stop dead in your tracks, however issue should be addressed as soon as possible.Q2-easy 💃Can be fixed by copy and pasting from StackOverflow.
Greetings,
I use
Parity/v1.8.3-beta-b49c44a-20171114/x86_64-linux-gnu/rustc1.21.0
precompiled release with the command:But Parity still creating snapshots:
The text was updated successfully, but these errors were encountered: