Skip to content

Conversation

@hawkw
Copy link
Member

@hawkw hawkw commented Jan 16, 2026

This branch makes a couple very small refactors to ereport reporting (which I intend to merge as independent commits and are best reviewed as such). In particular:

  • cosmo-seq: use microcbor for Vcore ereports (cf2e23b)

    Presently, the cosmo_seq::vcore module still uses serde to encode
    ereports rather than using microcbor. This is due to some kind of
    oversight on my part. It's sad for it to do that because the new
    microcbor crate lets us have a statically calculated buffer length for
    the ereport. This commit changes it to use the new and proper ereport
    serialization API instead of the old and unpreferred one.

  • packrat-api: Rename and document ereport delivery methods (f9f4a9d)

    @cbiffle noted (quite rightly!) yesterday that the name of
    Packrat::encode_ereport was somewhat unclear, as it both encodes the
    ereport and delivers it to Packrat. This commit renames the method and
    adds some slightly nicer documentation to it.

@hawkw hawkw requested review from cbiffle and labbott January 16, 2026 19:17
@hawkw hawkw force-pushed the eliza/erefactor branch 2 times, most recently from 108e2e8 to b142c9c Compare January 16, 2026 20:21
Copy link
Collaborator

@cbiffle cbiffle left a comment

Choose a reason for hiding this comment

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

Great improvement!

hawkw added a commit that referenced this pull request Jan 27, 2026
Presently, the `cosmo_seq::vcore` module still uses `serde` to encode
ereports rather than using `microcbor`. This is due to some kind of
oversight on my part. It's sad for it to do that because the new
`microcbor` crate lets us have a statically calculated buffer length for
the ereport. This commit changes it to use the new and proper ereport
serialization API instead of the old and unpreferred one.
hawkw added a commit that referenced this pull request Jan 27, 2026
Presently, the `cosmo_seq::vcore` module still uses `serde` to encode
ereports rather than using `microcbor`. This is due to some kind of
oversight on my part. It's sad for it to do that because the new
`microcbor` crate lets us have a statically calculated buffer length for
the ereport. This commit changes it to use the new and proper ereport
serialization API instead of the old and unpreferred one.
hawkw added a commit that referenced this pull request Jan 27, 2026
@cbiffle noted (quite rightly!) yesterday that the name of
`Packrat::encode_ereport` was somewhat unclear, as it both encodes the
ereport *and* delivers it to Packrat. This commit renames the method and
adds some slightly nicer documentation to it.
@hawkw hawkw enabled auto-merge (rebase) January 27, 2026 18:09
hawkw added 2 commits January 28, 2026 10:23
Presently, the `cosmo_seq::vcore` module still uses `serde` to encode
ereports rather than using `microcbor`. This is due to some kind of
oversight on my part. It's sad for it to do that because the new
`microcbor` crate lets us have a statically calculated buffer length for
the ereport. This commit changes it to use the new and proper ereport
serialization API instead of the old and unpreferred one.
@cbiffle noted (quite rightly!) yesterday that the name of
`Packrat::encode_ereport` was somewhat unclear, as it both encodes the
ereport *and* delivers it to Packrat. This commit renames the method and
adds some slightly nicer documentation to it.
@hawkw hawkw merged commit 7cb5e03 into master Jan 28, 2026
174 checks passed
@hawkw hawkw deleted the eliza/erefactor branch January 28, 2026 18:36
hawkw added a commit that referenced this pull request Jan 28, 2026
Presently, the `cosmo_seq::vcore` module still uses `serde` to encode
ereports rather than using `microcbor`. This is due to some kind of
oversight on my part. It's sad for it to do that because the new
`microcbor` crate lets us have a statically calculated buffer length for
the ereport. This commit changes it to use the new and proper ereport
serialization API instead of the old and unpreferred one.
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