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

Reflect updated record when resolving UPDATE in order to propagate UPDATE record to sync chain #280

Closed
wants to merge 1 commit into from

Conversation

@darkdh
Copy link
Member

darkdh commented Feb 4, 2019

fix #231

@darkdh darkdh self-assigned this Feb 4, 2019
UPDATE record to sync chain

fix #231
@darkdh darkdh force-pushed the record-update branch from de5458f to 0b9d403 Feb 4, 2019
Copy link
Member

SergeyZhukovsky left a comment

Won't we reapply records on client side that were not really changed with that fix?

@darkdh
Copy link
Member Author

darkdh commented Feb 4, 2019

It turns out to be the bug in brave-core and I will link the brave-core PR later.

@darkdh
Copy link
Member Author

darkdh commented Feb 4, 2019

brave/brave-core#1572 and it is sometimes affected by
#281

@darkdh darkdh deleted the record-update branch May 13, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked issues

Successfully merging this pull request may close these issues.

2 participants
You can’t perform that action at this time.