Repository navigation
fix(lyracore): send numeric GUIDs in structured actors - #12
Merged
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
The Account ownership Module refuses cleanup requests from adapter release
v0.1.0-alpha.9because the structured Actor encodes its GUID as a JSON string.Print canonical decimal digits as a JSON number without numeric conversion. Legacy reducer arguments stay compatible. Invalid or zero-prefixed input is refused before calling the CLI.
All four offline shell suites and syntax checks pass. The revised contract fails against the old adapter. A SpacetimeDB 2.7.1 call with the same JSON changed the durable row for GUID
9007199254740993exactly, proving that values above2^53survive. Independent review found no blocker.Implemented with GPT-6 Astra at high effort using Codex T3.