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

mvreg in a nested ormap not getting joined after replication #287

Open
jimpick opened this issue May 25, 2019 · 0 comments
Open

mvreg in a nested ormap not getting joined after replication #287

jimpick opened this issue May 25, 2019 · 0 comments

Comments

@jimpick
Copy link
Member

jimpick commented May 25, 2019

I'm encountering this issue between filecoin-pickaxe-agent and filecoin-pickaxe-direct-deal.

A property named 'agentState' lives in a mvreg inside an ormap inside another ormap. When it is updated in filecoin-pickaxe-agent (a bot with no UI), the mvreg has only one value. But on the replicated side inside filecoin-pickaxe-direct-deal (the UI app), it has multiple values!

Set {
        '{"state":"started"}',
        '{"state":"one"}',
        '{"state":"two"}',
        '{"state":"three"}',
        '{"state":"done"}' }

This is a blocker.

jimpick added a commit to filecoin-shipyard/filecoin-pickaxe-agent that referenced this issue May 25, 2019
jimpick added a commit to jimpick/js-delta-crdts that referenced this issue May 28, 2019
Peer-base uses Buffers for ids, which were getting serialized in
strange ways so the mvreg CRDT wasn't converging when syncing.

See: peer-base/peer-base#287

This fix encodes the ids to strings, using a similar method as what
is used in the rga type.
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

No branches or pull requests

1 participant