Skip to content
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

fixes to deal with the limitations of mongodb, grpc-gatway and bson #12

Merged
merged 1 commit into from
Jan 19, 2024

Conversation

robinbryce
Copy link
Collaborator

@robinbryce robinbryce commented Jan 19, 2024

fix: oneof doesn't play well with grpc gateway (apparently)

Instead of the (much cleaner) oneof, we will have a single message in the event per proof mech. only one of them will be present in any event

fix: mongo cant store unsigned integers of any size

So we use a different message for storing the proof details for mongo. It encodes the idtimestamp as a fixed lenght hex string. this preserves the sortable and comparible properties.

For now we keep the other unsigned types as they wont use the full range of bits until a single tenant log has 2^63 events in it.

fix: the field ordinals for merkle log messages were benignly 'wrong'. All message fields for merkle log messages start at ordinal 1 now

AB#8859

fix: oneof doesn't play well with grpc gateway (apparently)

Instead of the (much cleaner) oneof, we will have a single message in
the event per proof mech. only one of them will be present in any event

fix: mongo cant store unsigned integers of any size

So we use a different message for storing the proof details for mongo.
It encodes the idtimestamp as a fixed lenght hex string. this preserves
the sortable and comparible properties.

For now we keep the other unsigned types as they wont use the full range
of bits until a single tenant log has 2^63 events in it.

fix: the field ordinals for merkle log messages were benignly 'wrong'.
All message fields for merkle log messages start at ordinal 1 now

AB#8859
@robinbryce robinbryce merged commit 73f875c into main Jan 19, 2024
3 checks passed
@robinbryce robinbryce deleted the dev/robin/8859-assetconfirmer-forestrie-changes-3 branch January 19, 2024 18:48
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.

2 participants