You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
fredcarle opened this issue
May 15, 2024
· 0 comments
· Fixed by #2658
Assignees
Labels
area/crdtRelated to the (Merkle) CRDT systemarea/p2pRelated to the p2p networking systemrefactorThis issue specific to or requires *notable* refactoring of existing codebases and components
The text was updated successfully, but these errors were encountered:
fredcarle
added
area/crdt
Related to the (Merkle) CRDT system
refactor
This issue specific to or requires *notable* refactoring of existing codebases and components
area/p2p
Related to the p2p networking system
labels
May 15, 2024
fredcarle
changed the title
More post DAG-sync merge mechanics outside the net package.
Move post DAG-sync merge mechanics outside the net package.
May 15, 2024
## Relevant issue(s)
Resolves#2624
## Description
This PR simplifies the DAG sync process withing the `net` package and
moves the merge functionality to the `db` package. The merge is now
initiated via an event channel.
Note: I did a search and replace for `SchemaVersionId` to
`SchemaVersionID`. It's in its own commit. I've also remove the
`tests/integration/net/order` tests as they are now annoying to maintain
an will become even more irrelevant when we refactor the WaitForSync
functionality of our test framework.
Another note: I've reduced the severity of the race condition on my Mac.
We had a lot of leaking go routines and what is left of them is
WaitForSync methods that sometimes seem to leak and also badger cache
and libp2p transport that seem to leak go routines on close but I'm not
sure how to handle these last two.
area/crdtRelated to the (Merkle) CRDT systemarea/p2pRelated to the p2p networking systemrefactorThis issue specific to or requires *notable* refactoring of existing codebases and components
No description provided.
The text was updated successfully, but these errors were encountered: