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

Ongoing POST uploads does not reflect real-time LocalChange updates #2433

Open
MJ1998 opened this issue Feb 6, 2024 · 2 comments
Open

Ongoing POST uploads does not reflect real-time LocalChange updates #2433

MJ1998 opened this issue Feb 6, 2024 · 2 comments
Labels
P1 High priority issue

Comments

@MJ1998
Copy link
Collaborator

MJ1998 commented Feb 6, 2024

Describe the bug
In AllLocalChanges UploadStrategies, when the LocalChange list is split across multiple bundle upload requests, database consolidation during those uploads could modify the original LocalChange records. Those modifications should extend to LocalChanges currently in the upload process.

To be solved after #2450

Component
Engine

To Reproduce
Steps to reproduce the behavior:

  1. Go to '...'
  2. Click on '....'
  3. Scroll down to '....'
  4. See error

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Smartphone (please complete the following information):

  • Device: [e.g. Pixel4a emulator]
  • Android version: [e.g. Settings -> About phone -> Android version]
  • Build number: [e.g. Settings -> About phone -> Build number]
  • Version [e.g. 22]

Additional context
Add any other context about the problem here.

Would you like to work on the issue?
Please state if this issue should be assigned to you or who you think could help to solve this issue.

@santosh-pingle santosh-pingle added the P1 High priority issue label Feb 12, 2024
@santosh-pingle
Copy link
Collaborator

santosh-pingle commented Mar 6, 2024

I see that this issue is also relevant to the SingleResourceUpload strategy with Post http verb, where once a reference is synced to the FHIR server, the received resource ID needs to replace the old reference in local changes as well.

@santosh-pingle
Copy link
Collaborator

It seems like this issue may be addressed as part of resource creation using the POST HTTP verb, #2440.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
P1 High priority issue
Projects
Status: New
Development

No branches or pull requests

2 participants