SimpleHTTPServer throwed an exception due to negtive st_mtime attr in file
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
Research direction
Start with the attached test, “strange last modified date,” and reproduce the exception in SimpleHTTPServer on Windows using a file with a negative st_mtime. Trace the response path and add a regression test; done means the server handles that timestamp without throwing.
Written by the indexing model from the issue text.
Description
| BPO | 25534 |
|---|---|
| Nosy | @terryjreedy, @pfmoore, @tjguk, @vadmium, @zware, @truebit, @zooba, @zhangyangyu |
| Files |
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 2015-11-02.15:35:17.357>
labels = ['type-bug', 'library', 'OS-windows']
title = 'SimpleHTTPServer throwed an exception due to negtive st_mtime attr in file'
updated_at = <Date 2015-11-07.01:41:26.823>
user = 'https://github.com/truebit'
bugs.python.org fields:
activity = <Date 2015-11-07.01:41:26.823>
actor = 'martin.panter'
assignee = 'none'
closed = False
closed_date = None
closer = None
components = ['Library (Lib)', 'Windows']
creation = <Date 2015-11-02.15:35:17.357>
creator = 'Sean.Wang'
dependencies = []
files = ['40929']
hgrepos = []
issue_num = 25534
keywords = []
message_count = 8.0
messages = ['253926', '253927', '253948', '254081', '254082', '254083', '254246', '254249']
nosy_count = 8.0
nosy_names = ['terry.reedy', 'paul.moore', 'tim.golden', 'martin.panter', 'zach.ware', 'Sean.Wang', 'steve.dower', 'xiang.zhang']
pr_nums = []
priority = 'normal'
resolution = None
stage = 'needs patch'
status = 'open'
superseder = None
type = 'behavior'
url = 'https://bugs.python.org/issue25534'
versions = ['Python 2.7', 'Python 3.4', 'Python 3.5', 'Python 3.6']
- Dominant language
- Python
- Stars
- 77.2k
- Forks
- 36k
- Avg merge
- 1d 9h
- Merged PRs (30d)
- 558
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.
More from python/cpython
-
docs pending
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
stdlib type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
build type-bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
-
stdlib topic-email type-feature
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
-
🐛 Bug 🔔 Pending processing
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
jumpserver/jumpserver#17584 ·