microsoft / microsoft/markitdown
markitdown convert xlsx file out of time
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 186k
- Forks
- 13.7k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 49
Description
markitdown 0.1.6
python 3.13.10
test.xlsx 102108.46 KB
execute : markitdown "text.xlsx" > "output.md"
over 45minutes , there is no result returned , and the markitdown is still runing and converting .
Can it use GPU?
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 by reproducing the markitdown "text.xlsx" > "output.md" CLI conversion with the reported 102108.46 KB workbook and inspect the conversion path used for .xlsx files. Measure where the 45-minute run spends time and check whether the issue is conversion behavior or a GPU-support question. Done should include a confirmed cause and a reproducible outcome or clearly documented limitation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- cli, tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100