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

Sync: failed DCHECK when delete device record arrives twice #2817

Closed
AlexeyBarabash opened this issue Jan 4, 2019 · 6 comments
Closed

Sync: failed DCHECK when delete device record arrives twice #2817

AlexeyBarabash opened this issue Jan 4, 2019 · 6 comments
Assignees
Labels
feature/sync priority/P3 The next thing for us to work on. It'll ride the trains. QA/No release-notes/exclude

Comments

@AlexeyBarabash
Copy link
Contributor

Description

If two delete device records arrives to sync service, there is a failed DCHECK

[83053:775:0103/160933.609992:FATAL:sync_devices.cc(175)] Check failed: existing_it != std::end(devices_).

brave/brave-core#1193 (comment)

Steps to Reproduce

No steps to reproduce for QA, because this appears on debug builds only.
Could be reproduced with a related PR unit-test.

Brave version (brave://version info)

Version 0.61.0 Chromium: 72.0.3626.28 (Developer Build) (64-bit)

Reproducible on current release:

  • Does it reproduce on brave-browser dev/beta builds?
    no
@AlexeyBarabash AlexeyBarabash self-assigned this Jan 4, 2019
@rebron rebron added this to the 1.x Backlog milestone Jan 4, 2019
@rebron rebron added the priority/P3 The next thing for us to work on. It'll ride the trains. label Jan 4, 2019
@kjozwiak
Copy link
Member

@AlexeyBarabash can this issue negatively affect users on production? It's labelled as P3 but the issue mentions that it only happens in debug mode. If this is going to cause issues when users are removing devices, we should fix this before releasing sync in 0.59.x.

@AlexeyBarabash
Copy link
Contributor Author

@kjozwiak correct, this issue cannot negatively affect users on production, this appears only in debug builds.
This is not going to cause issues when users are removing devices.

@rebron rebron removed this from the 1.x Backlog milestone Feb 7, 2019
@AlexeyBarabash
Copy link
Contributor Author

Closed with brave/brave-core#1125 .

@rebron
Copy link
Collaborator

rebron commented Mar 13, 2019

@AlexeyBarabash can you set the right milestone for this?

@kjozwiak
Copy link
Member

brave/brave-core#1125 should also have a milestone 👍

@AlexeyBarabash AlexeyBarabash added this to the 0.62.x - Beta milestone Mar 14, 2019
@AlexeyBarabash
Copy link
Contributor Author

Thanks @rebron @kjozwiak , just had set the correct milestones.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature/sync priority/P3 The next thing for us to work on. It'll ride the trains. QA/No release-notes/exclude
Projects
None yet
Development

No branches or pull requests

3 participants