Skip to content

chore: switch from gob to JSON encoding for digests #971

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

Merged
merged 1 commit into from
May 15, 2025

Conversation

thedadams
Copy link
Contributor

The gob encoder is dependent on the order in which it sees types. So, even encoding a completely new type could change the "digest" of a type with the same values. This is not in the flavor or producing a digest.

This change switches to JSON, which will produce a consistent encoding.

StrongMonkey
StrongMonkey previously approved these changes May 15, 2025
The gob encoder is dependent on the order in which it sees types. So,
even encoding a completely new type could change the "digest" of a type
with the same values. This is not in the flavor or producing a digest.

This change switches to JSON, which will produce a consistent encoding.

Signed-off-by: Donnie Adams <[email protected]>
@thedadams thedadams merged commit 9b2832d into gptscript-ai:main May 15, 2025
10 checks passed
@thedadams thedadams deleted the gob-to-json branch May 15, 2025 16:28
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