Details
Minor Description
As reported on the forum, purging a document while a continuous push replication is running causes the pusher to try to send the nonexistent document.
It's a simple bug in Pusher::dbChanged() – the code does not take into account that a C4DatabaseChange can represent a purge. It should ignore such change entries.
This does not appear to be causing any significant problems, just unexpected logs.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Summary | Continuous push attempts to replicate a purged document | Continuous push attempts to replicate purged documents |
| Fix Version/s | Hydrogen [ 16189 ] |
| Story Points | 3 |
| Fix Version/s | Lithium [ 16190 ] | |
| Fix Version/s | Hydrogen [ 16189 ] | |
| Priority | Minor [ 4 ] | Major [ 3 ] |
| Rank | Ranked higher |
| Assignee | The Lite [ cbgto ] | Jim Borden [ jimb ] |
| Rank | Ranked higher |
| Rank | Ranked lower |
| Required Mobile Fields |
Mandatory:
- CBL / SG Version: - SG Config: - Steps to Reproduce: - Actual Result: - Expected Result: - Logs : SGW LOGS: sgcollect info CBL LOGS: Logcat LOGS: for Android tickets - Github link for the code: - Jenkins job failure link: - Pytest Command - What is the last build this test passed: |
| Rank | Ranked lower |
| Assignee | Jim Borden [ jimb ] | The Lite [ cbgto ] |
| Priority | Major [ 3 ] | Minor [ 4 ] |
| Priority | Minor [ 4 ] | Major [ 3 ] |
| Priority | Major [ 3 ] | Minor [ 4 ] |
| Assignee | The Lite [ cbgto ] | Jianmin Zhao [ JIRAUSER25274 ] |
| Sprint | Jianmin 50 [ 1670 ] |
| Rank | Ranked higher |
| Resolution | Fixed [ 1 ] | |
| Status | Open [ 1 ] | Resolved [ 5 ] |
| Status | Resolved [ 5 ] | Closed [ 6 ] |