This repository has been archived by the owner on Nov 15, 2023. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
Failed to open peer storage #404
Labels
I4-annoyance
The client behaves within expectations, however this “expected behaviour” itself is at issue.
Comments
Still needs a fix so that the code automatically deletes the invalid peer storage. |
tomaka
added
the
I4-annoyance
The client behaves within expectations, however this “expected behaviour” itself is at issue.
label
Jul 23, 2018
I can take care of a fix. |
chevdor
added a commit
to chevdor/substrate
that referenced
this issue
Jul 23, 2018
chevdor
added a commit
to chevdor/substrate
that referenced
this issue
Jul 24, 2018
gavofyork
pushed a commit
that referenced
this issue
Jul 27, 2018
* Reset peers.json if the content is not loadable Fix #404 * Whitespace
lamafab
pushed a commit
to lamafab/substrate
that referenced
this issue
Jun 16, 2020
liuchengxu
pushed a commit
to chainx-org/substrate
that referenced
this issue
Aug 23, 2021
* Impl `From` instead of impl `Into` * Remove `Deref` impl of `GenericTrusteeSessionInfo` * Add doc for some types * Remove useless `GenericAllSessionInfo` type Signed-off-by: koushiro <koushiro.cqx@gmail.com>
liuchengxu
pushed a commit
to autonomys/substrate
that referenced
this issue
Jun 3, 2022
Add support for building runtime and executables via manual trigger
helin6
pushed a commit
to boolnetwork/substrate
that referenced
this issue
Jul 25, 2023
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
I4-annoyance
The client behaves within expectations, however this “expected behaviour” itself is at issue.
This issue is more to document the problem and the solution. I don´t think a fix is worth it.
Feel free to comment/close the issue once read.
CC @gavofyork (I think you changed things on the topic recently).
Details
nodes.json new format:
Older format:
When a node starts and
nodes.json
contains old data, it reportsFailed to open peer storage
and say the peer data will not be saved.Either we do a fix that wipes the old file and move on, or we document that users need to delete the file (which I kinda do in this issue :))
The text was updated successfully, but these errors were encountered: