stat.S_ISXXX can raise OverflowError for remote file modes
Open
Nobody has claimed this yet.
3.8 (EOL)
3.9 (EOL)
stdlib
type-bug
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- PR merge metrics
- PR metrics pending
Description
| BPO | 39729 |
|---|---|
| Nosy | @tiran, @wiggin15, @ammaraskar |
Note: these values reflect the state of the issue at the time it was migrated and might not reflect the current state.
Show more details
GitHub fields:
assignee = None
closed_at = None
created_at = <Date 2020-02-23.10:08:44.805>
labels = ['3.8', 'type-bug', 'library', '3.9']
title = 'stat.S_ISXXX can raise OverflowError for remote file modes'
updated_at = <Date 2020-02-29.00:05:46.367>
user = 'https://github.com/wiggin15'
bugs.python.org fields:
activity = <Date 2020-02-29.00:05:46.367>
actor = 'terry.reedy'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)']
creation = <Date 2020-02-23.10:08:44.805>
creator = 'wiggin15'
dependencies = []
files = []
hgrepos = []
issue_num = 39729
keywords = []
message_count = 3.0
messages = ['362499', '362501', '362521']
nosy_count = 3.0
nosy_names = ['christian.heimes', 'wiggin15', 'ammar2']
pr_nums = []
priority = 'normal'
resolution = None
stage = None
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue39729'
versions = ['Python 3.8', 'Python 3.9']
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 locating the stat.S_ISXXX entry points and reproduce the reported OverflowError with a remote file mode. Check the existing issue discussion and related Library (Lib) code or tests, then add coverage for the failing mode and verify that the S_ISXXX helpers handle it without raising.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100