microsoft / microsoft/markitdown
Problem with mapped network files
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 186k
- Forks
- 13.7k
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 49
Description
I have a python script that watches a folder and when someone drops a Word or HTML document into it, it converts it to markdown and then converts the document format DocX <=> HTML.
The code runs fine when I use it on a local folder but I get the following error when I use it on a mapped network drive [Filepath] would be the file path of the document dropped into the folder.
markitdown._markitdown.FileConversionException: Could not convert '[File path]. While converting the file, the following error was encountered:
Traceback (most recent call last):
File "C:\Dev\Mammoth\Lib\site-packages\markitdown_markitdown.py", line 1239, in _convert
res = converter.convert(local_path, **_kwargs)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File "C:\Dev\Mammoth\Lib\site-packages\markitdown_markitdown.py", line 506, in convert
with open(local_path, "rb") as docx_file:
PermissionError: [Errno 13] Permission denied: '[File path]'
So far I have checked:
- Folder permissions
- Path is pointing to a file
When I run MarkItDown in the command line, it works fine.
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
Begin with _markitdown.py at lines 1239 and 506, then compare the failing library path with the command-line invocation on the mapped drive. Verify whether the same file path and process permissions are used and capture a minimal reproducible case. Done means identifying a reproducible library-side difference or documenting that the issue is environment-specific.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100