test_pull_path_non_ascii_or_trailing_whitespace fails with XPASS(strict)
Maintainers usually reply within 3 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 66/100
Research direction
Start with test/property/test_pebble_multipart.py and inspect test_pull_path_non_ascii_or_trailing_whitespace and its strict xfail marks. Run the reported cases to confirm why they now pass unexpectedly, then check the email parser behavior those tests cover. Done when the outdated expected failures are handled and the property test job passes.
Written by the indexing model from the issue text.
Description
Summary
test/property/test_pebble_multipart.py::test_pull_path_non_ascii_or_trailing_whitespace failed in the test job, with three failures marked [XPASS(strict)]. The failures suggest the email parser mangles filenames that contain non-ASCII or trailing whitespace.
Failures
- test:
test/property/test_pebble_multipart.py::test_pull_path_non_ascii_or_trailing_whitespace[/srv/caf\xe9]failed with[XPASS(strict)] the email parser mangles the filename - test:
test/property/test_pebble_multipart.py::test_pull_path_non_ascii_or_trailing_whitespace[/srv/file ]failed with[XPASS(strict)] the email parser mangles the filename - test:
test/property/test_pebble_multipart.py::test_pull_path_non_ascii_or_trailing_whitespace[/srv/file\t]failed with[XPASS(strict)] the email parser mangles the filename
Workflow: ops Property Tests (nightly)
Run: https://github.com/canonical/operator/actions/runs/44762491044
- Dominant language
- Python
- Stars
- 267
- Forks
- 156
- Avg merge
- 5d 3h
- Merged PRs (30d)
- 43
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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 canonical/operator
-
rainy day small item
Difficulty 2/5 1-3 hours Newbie friendliness 71/100
Maintainers usually reply within 3 days
-
Cleaning up inconsistencies in the Manage relations how-to pagePossibly taken @tromai claimed this 1 day ago. Opendocs roadmap
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
canonical/operator#2688 · 3 comments · 1 assignee ·
Maintainers usually reply within 3 days
-
docs rainy day tests
Difficulty 3/5 1-2 days Newbie friendliness 56/100
canonical/operator#2952 · 1 reaction ·
Maintainers usually reply within 3 days
-
docs rainy day
Difficulty 3/5 1-2 days Newbie friendliness 43/100
Maintainers usually reply within 3 days
-
rainy day
Difficulty 4/5 3-5 days Newbie friendliness 48/100
Maintainers usually reply within 3 days
All issues in canonical/operator
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
abetlen/llama-cpp-python#2424 ·
Maintainers usually reply within 1 day
-
Bug IronPython Python 3
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pyrevitlabs/pyRevit#4184 ·
Maintainers usually reply within 1 day
-
Difficulty 1/5 Under an hour Newbie friendliness 74/100
jqueryscript/awesome-claude-code#1009 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
Maintainers usually reply within 1 day
-
[Plugin] 群聊记忆 · 人格养成Open
Difficulty 1/5 1-3 hours Newbie friendliness 74/100