-
Notifications
You must be signed in to change notification settings - Fork 18
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
Runaway condition causes infinite round-trip #15
Comments
Sorry @jocrau I haven't forgotten about this, I've just been taking time to think through the next steps on the project. I'll add a temp fix for you for now, but we're starting to make progress on more general solutions for things here. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
There is a runaway condition in Datsync. It seems as if transacting the :txInstant is sent to the other side to be transacted which causes a round-trip.
This occurs after I implemented a handler for the key :dat.sync.client.bootstrap/complete?. This caused an error on the client side and stopped the round trip.
Here is an excerpt of the JS log:
The text was updated successfully, but these errors were encountered: