Dataset Publish Lock: Publish lock remains when publish fails in case of simultaneous update
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 564
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 29
Description
This is not a high likelihood scenario but since we were looking at places where lock may get stuck, here's one:
Open the same unpublished dataset in two browser tabs.
In one tab upload a hundred files and save with reserve file pids enabled or something that will take some time to complete.
In the other tab, click publish.
Notice the failure message and the publish lock at the same time. Publish lock remains.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Reproduce the failure by opening the same unpublished dataset in two browser tabs, starting a long upload and then publishing from the other tab. Trace the publish failure and lock cleanup; done means a failed publish no longer leaves the publish lock in place.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100