InvalidIndex exception triggers pulpcore deprecation warning in CI
Maintainers usually reply within 1 day
@git-hyagi is already working on this.
Since Oct 9, 2026.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 74/100
Research direction
Start with the InvalidIndex class in pulp_maven.app.path_index.format, which currently inherits only from ValueError. Read how pulpcore's _execute_task classifies caught exceptions, then run test_path_index_error_reports_offending_path. Done when InvalidIndex also derives from PulpException, the task still fails as expected, and the deprecation warning no longer appears.
Written by the indexing model from the issue text.
Description
Summary
The InvalidIndex exception in pulp_maven.app.path_index.format inherits from ValueError, which causes pulpcore's task executor to emit a deprecation warning whenever it is raised during task execution.
Pulpcore's _execute_task (and _aexecute_task) checks whether a caught exception is an instance of PulpException, APIException, or aiohttp.ClientError. If not, it logs:
Exception (InvalidIndex: ...) will be sanitized in pulpcore 3.130
This warning is captured by the CI deprecation artifacts and causes the deprecations job to fail, since that job asserts no deprecation warnings are emitted.
Reproduction
The warning is triggered by test_path_index_error_reports_offending_path, which intentionally creates a MavenArtifact named index.html that collides with a generated MavenIndexPage at the same relative_path. The resulting InvalidIndex is expected (the test asserts the task fails), but the deprecation warning is a side effect.
Example failing run: https://github.com/pulp/pulp_maven/actions/runs/37953001385/job/113907719999
Fix
Make InvalidIndex inherit from PulpException (in addition to ValueError for backward compatibility) so that pulpcore recognizes it as a known plugin exception and skips the deprecation warning path.
- Dominant language
- Python
- Stars
- 5
- Forks
- 30
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 26
Getting set up
- No Dockerfile or Docker Compose file
- Has a 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 pulp/pulp_maven
-
Nightly s3 unit tests fail under pytest 9.2.0: 'S3Storage' object has no attribute 'location'Possibly taken @dkliban claimed this 4 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pulp/pulp_maven#566 ·
Maintainers usually reply within 1 day
-
Difficulty 5/5 Over a week Newbie friendliness 45/100
pulp/pulp_maven#568 ·
Maintainers usually reply within 1 day
-
Difficulty 4/5 3-5 days Newbie friendliness 55/100
pulp/pulp_maven#563 ·
Maintainers usually reply within 1 day
-
_save_prefixes_txt crashes with DoesNotExist when two domains produce identical prefixes.txtPossibly taken @git-hyagi claimed this 7 days ago. OpenIssue
Difficulty 4/5 3-5 days Newbie friendliness 57/100
pulp/pulp_maven#557 ·
Maintainers usually reply within 1 day
-
Redeploying the same coordinates with different content returns 201 but keeps serving the old filePossibly taken @aevnsvi claimed this 14 days ago. Open
Difficulty 4/5 1-2 days Newbie friendliness 58/100
pulp/pulp_maven#551 ·
Maintainers usually reply within 1 day
Similar issues
-
DBFS append mode silently overwrites existing filesPossibly taken @IlyaKhalafi claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
fsspec/filesystem_spec#2429 ·
Maintainers usually reply within 1 day
-
[Bug]: Retrieval rerank fallback statistics stay zero after provider failurePossibly taken A pull request linked to this issue is open or already merged. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
volcengine/OpenViking#7014 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
fedora-copr/copr#4600 ·
Maintainers usually reply within 2 days
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
ansys/pydpf-core#3620 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 1 day