-
Notifications
You must be signed in to change notification settings - Fork 577
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
cluster: serde_fields for various structs #23118
Conversation
- archival_metadata_stm::segment - archival_metadata_stm::start_offset_with_delta - archival_metadata_stm::truncate_archive_commit_cmd Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
- entity_value - alter_quotas_request Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
- empty_request - get_status_response - netcheck_request - netcheck_response Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
@@ -164,6 +171,8 @@ struct archival_metadata_stm::spillover_cmd | |||
static constexpr cmd_key key{9}; |
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 wonder why serde doesn't encode static fields
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.
presumably you could, but I suppose it's strictly wasted bits since the value wouldn't change per instance. or maybe more straightforwardly, "the same reason statics don't appear in structured bindings".
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.
oh yeh i think it makes sense that they do not appear in the encodings!
- copy_target Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
- node_status_metadata - node_status_request Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
Signed-off-by: Oren Leiman <oren.leiman@redpanda.com>
fd06016
to
9f93962
Compare
force push to fix merge conflict |
ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/53784#01919f3c-809c-4102-8f14-d104caa7a996 ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/53823#0191a421-7168-486c-9bc9-b364a6d551a7 ducktape was retried in https://buildkite.com/redpanda/redpanda/builds/53823#0191a421-716b-4700-a66b-2230c1ab4724 |
Which looks genuine to me. Trying this out on |
Same failure on |
This ought to fix it: #23149 |
/ci-repeat 1 |
@oleiman Curious why the force push removed this serde_fields() method? |
Oh yeah, ha, that's confusing. The reason is that it was added already upstream: redpanda/src/v/cluster/data_migration_types.h Line 134 in 5f53ab4
|
In #22782, we aim to require explicit serde_fields for serde structs that would otherwise use aggregate field order. This is one in a series of pull requests that add serde_fields to existing structs, to be followed by a PR to remove the aggregate order fallback from serde itself.
The primary acceptance criterion for this PR should be "field order unchanged". Any functional change is a bug.
Backports Required
Release Notes