Skip to content

Updated handling of configuration ledger entries#3522

Closed
dmkozh wants to merge 7 commits intostellar:masterfrom
dmkozh:config_setting_le
Closed

Updated handling of configuration ledger entries#3522
dmkozh wants to merge 7 commits intostellar:masterfrom
dmkozh:config_setting_le

Conversation

@dmkozh
Copy link
Contributor

@dmkozh dmkozh commented Aug 30, 2022

Description

These updates are based on my previous work on SPEEDEX configuration PR.

  • Update the code to handle proposed XDR changes (Update configuration-related XDR stellar-xdr#27)
  • Make configuration not removable (this seems like a feature that has potential to end up as a footgun)
  • Increase test coverage by generating configuration entries by default, but either ensuring the uniqueness of generated ledger entries or by explicitly excluding them where relevant.

Checklist

  • Reviewed the contributing document
  • Rebased on top of master (no merge commits)
  • Ran clang-format v8.0.0 (via make format or the Visual Studio extension)
  • Compiles
  • Ran all tests
  • If change impacts performance, include supporting evidence per the performance document

.gitmodules Outdated
ignore = dirty
[submodule "src/protocol-next/xdr"]
path = src/protocol-next/xdr
url = https://github.com/stellar/stellar-xdr-next.git
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suspect this needs to switch back to the stellar repo?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Sure (hence the !removeme commit) - IIUC that's the only way to make the tests pass before the XDR changes are merged.

This is to support how the new XDR is generated.
While this can be supported from the ledger standpoint, I think that semantically these shouldn't be removed and hence it's better to introduce some harness to make sure we don't accidentally remove it.
- Add methods to generate unique entries, so that we don't need to exclude `CONFIG_SETTING` entry from the fuzzer due to them having key collisions
- Add methods to generate entries of given type and entries with exclusions to be more explicit about including/excluding the entry types where relevant
@dmkozh dmkozh force-pushed the config_setting_le branch from c259687 to d53312b Compare January 12, 2023 22:28
@sisuresh sisuresh mentioned this pull request Mar 9, 2023
6 tasks
@MonsieurNicolas
Copy link
Contributor

I think this is now obsolete -- @dmkozh you can close it

@dmkozh dmkozh closed this Apr 24, 2023
@dmkozh dmkozh deleted the config_setting_le branch November 21, 2025 18:58
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants