-
Notifications
You must be signed in to change notification settings - Fork 906
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
lightningd: refuse to upgrade db on non-released versions by default. #5550
lightningd: refuse to upgrade db on non-released versions by default. #5550
Conversation
Looks like we are getting an access to uninitialized memory in |
What about release candidates? (I tend to start those using |
You need only launch it differently once. You could also have |
Yeah, tell systemd to stop, do But really, you can just put |
ba5762c
to
a2a5904
Compare
Rebased on master, fixed uninitialized var. |
0ee3a42
to
3a612b8
Compare
4c73cf1
to
3bbcf1d
Compare
This is a good sanity check that users understand that if they upgrade to master mid-cycle they can't go back! Suggested-by: @wtogami Changelog-Added: Config: `--database-upgrade=true` required if a non-release version wants to (irrevocably!) upgrade the db. Signed-off-by: Rusty Russell <rusty@rustcorp.com.au>
3bbcf1d
to
1cbfa92
Compare
That was weird... First CI seemed to have the wrong version, then I seemed to push an empty tree. But I've rebased onto master now... |
1cbfa92
to
262dbf9
Compare
Rebased on top of ACK 262dbf9 |
Seems we have a false positive for memleak (guessing the bool flag?). |
262dbf9
to
1cbfa92
Compare
No, it's a valgrind error. But I do initialize it in this commit (I didn't initialize it previously), and indeed, I checked it's correct locally... Trivial rebase |
Ok fine... |
This is a good sanity check that users understand that if they upgrade
to master mid-cycle they can't go back!
Suggested-by: @wtogami
Changelog-Added: Config:
--database-upgrade=true
required if a non-release version wants to (irrevocably!) upgrade the db.