fix: dag-json encode egress events #193
Merged
Conversation
This file contains hidden or 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
travis
approved these changes
Nov 18, 2025
fforbeck
force-pushed
the
feat/dagjson-egress-event
branch
from
9bb98f1 to
6332a33
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Fix egress queue serialization using DAG-JSON encoding
Replace manual array/object serialization with DAG-JSON encoding for egress tracking queue messages. This properly handles CIDs and Uint8Arrays, fixing "Unexpected end of data" errors in the egress-consumer.
Changes
dagJSON.encode()to serialize queue messages containing invocation data and CIDs