-
Notifications
You must be signed in to change notification settings - Fork 912
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
Remove --enable-experimental-features, use all runtime flags. #6209
Merged
rustyrussell
merged 11 commits into
ElementsProject:master
from
rustyrussell:guilt/no-experimental-build
May 23, 2023
Merged
Changes from 1 commit
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
488087e
lnprototest: update to avoid compulsory option_anchors init.
rustyrussell 3edfc70
tools: remove optional csv field handling.
rustyrussell d042220
tools/generate-wire.py: intuit tlvs field if a tlv type is mentioned.
rustyrussell 24e98ca
wire: remove our own blinded payments patch since it's in spec.
rustyrussell fd65758
channeld: allow stfu based on peer features, not EXPERIMENTAL_FEATURES.
rustyrussell c89d505
channeld: use explicit --experimental-upgrade flag, not #ifdef EXPERI…
rustyrussell f9c412f
plugins/fetchinvoice: remove obsolete check for feature 102.
rustyrussell b34a597
build: don't generate experimental variants of wire files.
rustyrussell bca6812
listtransactions: remove annotations, which were only in EXPERIMENTAL…
rustyrussell 4d9e332
pytest: remove EXPERIMENTAL_FEATURES as a consideration.
rustyrussell 6efc1c5
build: remove --enable-experimental-features / EXPERIMENTAL_FEATURES
rustyrussell File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can this be a breaking change for cln-grpc?
Also if people are not using it, the grpc could complain about different model, but for now it is also easy to upgrade
So I just put my though here
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No, because it was experimental only, the fields didn't exist for most people anyway.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not think that the code generation is smart enough to catch the experimental field or these changes in the rust model are unrelated? https://github.com/ElementsProject/lightning/pull/6209/files#diff-af0e7f481b7fd8fc471ab4d5a808c9b4512e0d347bfceff633effc80acdcf5fe
But maybe the proto-buff do not complain when there is the optional fields