Infinite loop(?)
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 3.1k
- Forks
- 430
- PR merge metrics
- No merged PRs in 30d
Description
tippecanoe appears to never finish on the linked file (http://static.skysight.io/2200.gz) (or at least, my patience expired after 4 hours on a fast machine)
Yes, it's large and complex, but I've been processing similarly complex files within 50% of the size typically in around 1-3 minutes.
command: tippecanoe --detect-shared-borders --coalesce --reorder -z4 -D 14 -d 14
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 by reproducing the tippecanoe command with the linked 2200.gz file, then profile the run to identify where processing stops making progress. Compare its behavior with the similarly complex files described in the report. Done means the input completes reliably without an extreme runtime or infinite loop.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- cli, performance
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100