Possible deadlock on `map_raster()`?
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 394
- Forks
- 95
- Avg merge
- 4d 3h
- Merged PRs (30d)
- 7
Description
This CI job got stuck on test_map.py. Let's keep an eye on that in case it happens again. It could be a deadlock related to dask.
https://github.com/scverse/spatialdata/actions/runs/20681259139/job/59375803959?pr=942
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
Start with test_map.py and the linked CI job, then inspect the map_raster() path for the reported dask-related hang. Done means reproducing or ruling out the deadlock and documenting the confirmed failure scope; the issue does not specify a fix or regression test.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- testing-qa
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100