fsspec / fsspec/filesystem_spec
Add more logging of exceptions in backends
Open
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 1.4k
- Forks
- 490
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 38
Description
A lot of backends can throw exceptions that are swallowed by fsspec, we should at least log these errors in debug or info level using the builtin loggers with exc_info=True to improve the debugging experience of the library.
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
Locate the backend exception-handling paths where fsspec currently swallows errors, then review how builtin loggers are used. Confirm which exceptions are swallowed and choose appropriate debug or info logging with exc_info=True; done means those failures provide useful exception details without changing backend behavior.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend, observability
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100