MapColonies / MapColonies/GpkgMerger
Merger puts tasks 'In-Progress' for each task type that exists parallely (MAPCO-4446)
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 1
- Forks
- 2
- Avg merge
- 21m
- Merged PRs (30d)
- 1
Description
If exists, TilesMerger pulls a task for each task type, if tasks exist then all but one are "lost" and get a status of In-Progress.
The relevant code is in the MainRunner file:
https://github.com/MapColonies/GpkgMerger/blob/653bdd5b9e4a17823d70ea03bbf751198c7944fc/MergerService/Runners/MainRunner.cs#L36-L40
phenomenon:
Once three ingestion processes are in parallel, tasks from all ingestion processes are moved to status In-Progress, although the merger does not work on them.
To Reproduce
Run multiple (at least 2) ingestion jobs with different ingestion types with existing tasks. (swap, new, update).
Actual behavior
Merger moves tasks to In-Progress although not working on them.
Expected behavior
Merger will "mark" only one task as In-Progress and work on it.
Contributor guide
No contributing guide indexed for this repository
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
Start with MergerService/Runners/MainRunner.cs, especially lines 36-40, and reproduce the issue by running at least two ingestion jobs with different types such as swap, new, and update. Trace which tasks are marked In-Progress when multiple tasks exist. Done means only the task being processed is marked In-Progress while the others remain available.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- csharp
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 45/100