8000 "Bad changeset" errors should indicate primary key where applying change failed · Issue #6204 · realm/realm-core · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content
"Bad changeset" errors should indicate primary key where applying change failed #6204
Closed
@sync-by-unito

Description

@sync-by-unito

Often, a failure to apply changesets on the client results in a crash and traceback. However, without knowing which object was the one being modified when the bad changeset error was triggered, there is limited context so debugging the root cause is much more difficult.
See the linked HELP tickets on https://jira.mongodb.org/browse/RCORE-734 for example.

Metadata

Metadata

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

    0