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

feat: resume an interrupted xmlupload (DEV-3323) #853

Merged
merged 35 commits into from Mar 7, 2024

Conversation

jnussbaum
Copy link
Collaborator

No description provided.

@jnussbaum jnussbaum self-assigned this Mar 4, 2024
Copy link

linear bot commented Mar 4, 2024

Copy link
Collaborator

@Nora-Olivia-Ammann Nora-Olivia-Ammann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

In the file: src/dsp_tools/commands/xmlupload/resource_create_client.py
line: 48.
What happens if the post is already done but we do not have the answer from the server yet but it is a sucessful upload?

If there is no interrupted upload to finish i get a non-200 error, which it retries... that is for a future PR but we should keep in mind to clean that up.

Bad news: The number of triples in the db is not the same after an interrupted upload than a normal one:

  • Regular xmlupload project systematic: 3735
  • Test 1: Interrupted 2 times: 3763
  • Test 2: interrupted 1 times: 3766
    Both interruptions were not during the stash upload.
    I have not done more precise investigations what happened, but clearly something is wrong.

docs/cli-commands.md Outdated Show resolved Hide resolved
@jnussbaum
Copy link
Collaborator Author

In the file: src/dsp_tools/commands/xmlupload/resource_create_client.py line: 48. What happens if the post is already done but we do not have the answer from the server yet but it is a sucessful upload?

If there is no interrupted upload to finish i get a non-200 error, which it retries... that is for a future PR but we should keep in mind to clean that up.

Bad news: The number of triples in the db is not the same after an interrupted upload than a normal one:

* Regular xmlupload project systematic: 3735

* Test 1: Interrupted 2 times: 3763

* Test 2: interrupted 1 times: 3766
  Both interruptions were not during the stash upload.
  I have not done more precise investigations what happened, but clearly something is wrong.

Thanks a lot for your valuable feedback. We noted these points and created a follow-up ticket: https://linear.app/dasch/issue/DEV-3392/tidy-up-resume-xmlupload-follow-up

@jnussbaum jnussbaum enabled auto-merge (squash) March 7, 2024 16:14
@jnussbaum jnussbaum merged commit 4acf841 into main Mar 7, 2024
10 checks passed
@jnussbaum jnussbaum deleted the wip/DEV-3323-resume-an-interrupted-xmlupload branch March 7, 2024 16:14
@daschbot daschbot mentioned this pull request Mar 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants