Drop XML parsing, switch to using dnf excludepkgs (#5) #32

Merged

adamwill merged 1 commit from dnf-excludepkgs into main 2026-04-20 18:32:30 +00:00

Conversation 8 Commits 1 Files changed 30 +81 -1258

adamwill commented 2026-04-17 22:44:46 +00:00

Owner

Copy link

Instead of painfully retrieving, decompressing, parsing, editing
and reconstructing the repodata, let's use dnf's excludepkgs
option to achieve the same thing. This is much simpler, faster,
and more robust.

To 'modify' the modified base repos, we use dnf repoquery to
list the packages they contain and their source RPM names, then
construct a table with the NEVRs to be removed for each repo.
Then when we do the repoclosure command, we pass
--setopt .excludepkgs= for each modified repo.
This tells dnf to act as if the specified NEVRs simply do not
exist in the specified repo, which is exactly what we want to
achieve.

Signed-off-by: Adam Williamson awilliam@redhat.com

Instead of painfully retrieving, decompressing, parsing, editing and reconstructing the repodata, let's use dnf's excludepkgs option to achieve the same thing. This is much simpler, faster, and more robust. To 'modify' the modified base repos, we use dnf repoquery to list the packages they contain and their source RPM names, then construct a table with the NEVRs to be removed for each repo. Then when we do the repoclosure command, we pass --setopt <repo>.excludepkgs=<nevrlist> for each modified repo. This tells dnf to act as if the specified NEVRs simply do not exist in the specified repo, which is exactly what we want to achieve. Signed-off-by: Adam Williamson <awilliam@redhat.com>

adamwill added 1 commit 2026-04-17 22:44:47 +00:00

Drop XML parsing, switch to using dnf excludepkgs (#5) ... b8d1c41a08

Instead of painfully retrieving, decompressing, parsing, editing
and reconstructing the repodata, let's use dnf's excludepkgs
option to achieve the same thing. This is much simpler, faster,
and more robust.

To 'modify' the modified base repos, we use dnf repoquery to
list the packages they contain and their source RPM names, then
construct a table with the NEVRs to be removed for each repo.
Then when we do the repoclosure command, we pass
--setopt <repo>.excludepkgs=<nevrlist> for each modified repo.
This tells dnf to act as if the specified NEVRs simply do not
exist in the specified repo, which is exactly what we want to
achieve.

Signed-off-by: Adam Williamson <awilliam@redhat.com>

adamwill commented 2026-04-17 22:46:03 +00:00

Author

Owner

Copy link

Wow, I should have tried this sooner. Would've saved me a week of messing about with XML parsers. OTOH, I know a lot more about writing a streaming XML token parser now.

The only thing that worries me here is potentially exceeding subprocess' or bash's or something's argument length limit for extremely big updates. I tried it with a 60 package update and it worked, but I'd be worried with those 400+ package KDE updates. I'll see if I can test this somehow before merging. If that's a problem we can probably switch to using config files.

Wow, I should have tried this sooner. Would've saved me a week of messing about with XML parsers. OTOH, I know a lot more about writing a streaming XML token parser now. The only thing that worries me here is potentially exceeding subprocess' or bash's or something's argument length limit for extremely big updates. I tried it with a 60 package update and it worked, but I'd be worried with those 400+ package KDE updates. I'll see if I can test this somehow before merging. If that's a problem we can probably switch to using config files.

adamwill added the

ai-review-please

label 2026-04-17 22:46:08 +00:00

forgejo-actions removed the

ai-review-please

label 2026-04-17 22:46:29 +00:00

forgejo-actions commented 2026-04-17 22:47:07 +00:00

Copy link

AI Code Review

📋 MR Summary

Replaces manual XML repository metadata manipulation with DNF's native excludepkgs functionality for faster and more robust dependency testing.

• Key Changes:
  • Removed custom XML decompression, parsing, and modification logic.
  • Eliminated lxml and compression-related dependencies.
  • Introduced dnf repoquery to identify package NEVRs based on source names.
  • Added --setopt=<repo>.excludepkgs=<nevrlist> to dynamically hide packages during repoclosure.
• Impact: rmdepcheck.py (core logic), tests/test_rmdepcheck.py (test suite), Dependency management (pyproject.toml, tox.requires)
• Risk Level: 🟡 Medium - While architecturally sound, the changes introduce risks regarding shell argument length limits (ARG_MAX) for massive exclusion lists and potential crashes from unvalidated subprocess stdout parsing.

Detailed Code Review

The architectural shift from manual XML parsing to utilizing native DNF capabilities is an excellent move for both performance and maintainability. It significantly reduces the tool's complexity and fragility.

However, there are two primary edge cases to address to ensure robustness. First, subprocess output parsing assumes a strict comma-separated format from dnf repoquery, which can fail if DNF outputs warnings or progress text to stdout. Second, as discussed, injecting potentially thousands of NEVRAs via command-line arguments risks exceeding OS ARG_MAX limits. Mitigating the ARG_MAX issue by dynamically generating a temporary .repo config file instead of relying heavily on command-line flags would guarantee scalability.

Lastly, there are a few residual artifacts from the previous implementation, such as unused directory parameters, that can be cleaned up.

📂 File Reviews

📄 `rmdepcheck.py` - Core execution script restructured to use DNF queries and options rather than XML manipulation.

• Major [Bug]: Unvalidated parsing of dnf repoquery output. If DNF outputs any warnings, blank lines, or unexpected metadata to stdout, line.split(",") will throw a ValueError and crash the execution.
  • Suggestion: Add validation to ensure the line contains a comma before attempting to unpack it, and use maxsplit=1 for safety.

        for line in out.splitlines():
            if "," not in line:
                continue
            sname, nevr = line.split(",", 1)
            if sname in removes:
                repo_excludes.setdefault(mrepo, []).append(nevr)

• Major [Architecture]: Risk of exceeding ARG_MAX limits. If excludes grows very large, passing it via --setopt in subprocess.run will throw OSError: [Errno 7] Argument list too long.

  • Suggestion: Instead of --repofrompath and --setopt, dynamically generate a temporary DNF configuration file containing the [repo] blocks and excludepkgs=... lists, then pass it to DNF using -c.

• Minor [Style]: The mreposdir argument is still passed to get_modified_and_new_repoclosure but is no longer used anywhere inside the function body.

  • Suggestion: Remove the mreposdir parameter from the function signature and the corresponding call in main().

def get_modified_and_new_repoclosure(
    mrepos: Iterable[str],
    nmrepos: Iterable[str],
    nrepos: Iterable[str],
    removes: Iterable[str],
) -> tuple[str, str]:

✅ Summary

• Overall Assessment: The architectural pivot is solid, but major issues exist with unprotected string parsing and potential ARG_MAX limitations.
• Priority Issues:
  • Safeguard dnf repoquery output parsing against unexpected output lines lacking commas.
  • Address the ARG_MAX vulnerability by switching from command-line --setopt to generated temporary configuration files if exclusion lists can grow arbitrarily large.
• Minor Suggestions:
  • Remove the unused mreposdir parameter from get_modified_and_new_repoclosure.

---

🤖 AI Code Review | Generated with ai-code-review | Model: gemini-3.1-pro-preview

⚠️ AI-generated suggestions may be incorrect. Verify before applying. Not a replacement for human review.

## AI Code Review ### 📋 MR Summary Replaces manual XML repository metadata manipulation with DNF's native `excludepkgs` functionality for faster and more robust dependency testing. - **Key Changes:** - Removed custom XML decompression, parsing, and modification logic. - Eliminated `lxml` and compression-related dependencies. - Introduced `dnf repoquery` to identify package NEVRs based on source names. - Added `--setopt=<repo>.excludepkgs=<nevrlist>` to dynamically hide packages during `repoclosure`. - **Impact:** rmdepcheck.py (core logic), tests/test_rmdepcheck.py (test suite), Dependency management (pyproject.toml, tox.requires) - **Risk Level:** 🟡 Medium - While architecturally sound, the changes introduce risks regarding shell argument length limits (ARG_MAX) for massive exclusion lists and potential crashes from unvalidated subprocess stdout parsing. ### Detailed Code Review The architectural shift from manual XML parsing to utilizing native DNF capabilities is an excellent move for both performance and maintainability. It significantly reduces the tool's complexity and fragility. However, there are two primary edge cases to address to ensure robustness. First, subprocess output parsing assumes a strict comma-separated format from `dnf repoquery`, which can fail if DNF outputs warnings or progress text to `stdout`. Second, as discussed, injecting potentially thousands of NEVRAs via command-line arguments risks exceeding OS `ARG_MAX` limits. Mitigating the `ARG_MAX` issue by dynamically generating a temporary `.repo` config file instead of relying heavily on command-line flags would guarantee scalability. Lastly, there are a few residual artifacts from the previous implementation, such as unused directory parameters, that can be cleaned up. #### 📂 File Reviews <details> <summary><strong>📄 `rmdepcheck.py`</strong> - Core execution script restructured to use DNF queries and options rather than XML manipulation.</summary> - **Major** [Bug]: Unvalidated parsing of `dnf repoquery` output. If DNF outputs any warnings, blank lines, or unexpected metadata to `stdout`, `line.split(",")` will throw a `ValueError` and crash the execution. - *Suggestion:* Add validation to ensure the line contains a comma before attempting to unpack it, and use `maxsplit=1` for safety. ```` for line in out.splitlines(): if "," not in line: continue sname, nevr = line.split(",", 1) if sname in removes: repo_excludes.setdefault(mrepo, []).append(nevr) ```` - **Major** [Architecture]: Risk of exceeding `ARG_MAX` limits. If `excludes` grows very large, passing it via `--setopt` in `subprocess.run` will throw `OSError: [Errno 7] Argument list too long`. - *Suggestion:* Instead of `--repofrompath` and `--setopt`, dynamically generate a temporary DNF configuration file containing the `[repo]` blocks and `excludepkgs=...` lists, then pass it to DNF using `-c`. - **Minor** [Style]: The `mreposdir` argument is still passed to `get_modified_and_new_repoclosure` but is no longer used anywhere inside the function body. - *Suggestion:* Remove the `mreposdir` parameter from the function signature and the corresponding call in `main()`. ```` def get_modified_and_new_repoclosure( mrepos: Iterable[str], nmrepos: Iterable[str], nrepos: Iterable[str], removes: Iterable[str], ) -> tuple[str, str]: ```` </details> ### ✅ Summary - **Overall Assessment:** The architectural pivot is solid, but major issues exist with unprotected string parsing and potential ARG_MAX limitations. - **Priority Issues:** - Safeguard `dnf repoquery` output parsing against unexpected output lines lacking commas. - Address the `ARG_MAX` vulnerability by switching from command-line `--setopt` to generated temporary configuration files if exclusion lists can grow arbitrarily large. - **Minor Suggestions:** - Remove the unused `mreposdir` parameter from `get_modified_and_new_repoclosure`. --- 🤖 **AI Code Review** | Generated with [ai-code-review](https://gitlab.com/redhat/edge/ci-cd/ai-code-review) | **Model:** `gemini-3.1-pro-preview` ⚠️ *AI-generated suggestions may be incorrect. Verify before applying. Not a replacement for human review.*

adamwill force-pushed dnf-excludepkgs from b8d1c41a08 to 3a96888ca9 2026-04-18 03:43:11 +00:00 Compare

adamwill force-pushed dnf-excludepkgs from 3a96888ca9 to db1414151c 2026-04-18 03:46:21 +00:00 Compare

adamwill commented 2026-04-18 06:52:56 +00:00

Author

Owner

Copy link

So I tested and this handles a 224-package update with panache and aplomb. ARG_MAX seems to be 2097152 in typical Fedora environments, which really ought to be enough for any foreseeable update (famous last words, hah) - we're only putting package NEVRs in here, they're typically like 10-50 characters long, so if we save 97k characters for contingencies, we can have like 40,000 packages in there. So I think I'm inclined to go with this at least until it blows up. Switching to using config files is a bit of a faff.

So I tested and this handles a 224-package update with panache and aplomb. ARG_MAX seems to be 2097152 in typical Fedora environments, which really ought to be enough for any foreseeable update (famous last words, hah) - we're only putting package NEVRs in here, they're typically like 10-50 characters long, so if we save 97k characters for contingencies, we can have like 40,000 packages in there. So I think I'm inclined to go with this at least until it blows up. Switching to using config files is a bit of a faff.

adamwill added the

ai-review-please

label 2026-04-18 06:53:13 +00:00

forgejo-actions removed the

ai-review-please

label 2026-04-18 06:53:15 +00:00

forgejo-actions commented 2026-04-18 06:53:43 +00:00

Copy link

AI Code Review

📋 MR Summary

This MR drastically simplifies dependency checking by replacing complex manual XML parsing with DNF's native excludepkgs option via repoquery and repoclosure.

• Key Changes:
  • Removed manual XML metadata downloading, decompressing, parsing, and modification logic.
  • Eliminated standard external tool dependencies like curl, zstd, gzip, and lxml.
  • Introduced get_modified_and_new_repoclosure which relies on dnf repoquery to build an exclusion list and applies it using --setopt <repo>.excludepkgs=<nevrlist>.
• Impact: rmdepcheck.py, tests/test_rmdepcheck.py, Packaging & Requirements (pyproject.toml, tox.requires)
• Risk Level: 🟢 Low - The changes remove a highly complex, fragile XML parsing layer in favor of established DNF tooling, drastically lowering maintenance overhead. The primary edge case (ARG_MAX limits) is acknowledged and deemed acceptable for current scaling needs.

Detailed Code Review

Overall, this is an excellent refactor that greatly reduces technical debt by leveraging the native capabilities of dnf instead of trying to replicate repository modifications through raw XML mutation. The test suite has been properly trimmed down to match the simplified logic.

From a performance standpoint, there's a minor but standard algorithmic improvement possible. String concatenation in a loop (excludes += ...) has an O(N^2) complexity in Python. While the number of packages is typically small (e.g., 200-300), switching to an array append and .join() is a safer best practice to handle larger scale inputs effectively. Other than that, the new approach perfectly handles the intended design.

📂 File Reviews

📄 `rmdepcheck.py` - Replaced manual XML editing functionalities with sub-process calls leveraging DNF configuration parameters.

• Minor [Performance]: String concatenation inside a loop has O(N^2) time complexity. It is recommended to append elements to a list and use ','.join() to generate the excludes string, which is O(N) and significantly more efficient if the exclusion list grows large.
  • Suggestion: Collect matching NEVRs in a list and join them after the loop.

        excludes_list = []
        args = queryargs + ["--repofrompath", f"{hash_repo(mrepo)},{mrepo}"]
        out = SUBPCAPTURE(args).stdout
        for line in out.splitlines():
            # sname, nevr
            elems = line.split(",")
            if len(elems) != 2:
                continue  # pragma: no cover
            if elems[0] in removes:
                excludes_list.append(elems[1])
        
        excludes = ",".join(excludes_list)

✅ Summary

• Overall Assessment: No critical issues identified. The transition to DNF options is robust, with a minor algorithmic optimization suggested for string joining.
• Minor Suggestions:
  • Switch the string concatenation loop for excludes to list .append() and ','.join() for optimal O(N) performance.

---

🤖 AI Code Review | Generated with ai-code-review | Model: gemini-3.1-pro-preview

⚠️ AI-generated suggestions may be incorrect. Verify before applying. Not a replacement for human review.

## AI Code Review ### 📋 MR Summary This MR drastically simplifies dependency checking by replacing complex manual XML parsing with DNF's native `excludepkgs` option via `repoquery` and `repoclosure`. - **Key Changes:** - Removed manual XML metadata downloading, decompressing, parsing, and modification logic. - Eliminated standard external tool dependencies like `curl`, `zstd`, `gzip`, and `lxml`. - Introduced `get_modified_and_new_repoclosure` which relies on `dnf repoquery` to build an exclusion list and applies it using `--setopt <repo>.excludepkgs=<nevrlist>`. - **Impact:** rmdepcheck.py, tests/test_rmdepcheck.py, Packaging & Requirements (pyproject.toml, tox.requires) - **Risk Level:** 🟢 Low - The changes remove a highly complex, fragile XML parsing layer in favor of established DNF tooling, drastically lowering maintenance overhead. The primary edge case (ARG_MAX limits) is acknowledged and deemed acceptable for current scaling needs. ### Detailed Code Review Overall, this is an excellent refactor that greatly reduces technical debt by leveraging the native capabilities of `dnf` instead of trying to replicate repository modifications through raw XML mutation. The test suite has been properly trimmed down to match the simplified logic. From a performance standpoint, there's a minor but standard algorithmic improvement possible. String concatenation in a loop (`excludes += ...`) has an O(N^2) complexity in Python. While the number of packages is typically small (e.g., 200-300), switching to an array append and `.join()` is a safer best practice to handle larger scale inputs effectively. Other than that, the new approach perfectly handles the intended design. #### 📂 File Reviews <details> <summary><strong>📄 `rmdepcheck.py`</strong> - Replaced manual XML editing functionalities with sub-process calls leveraging DNF configuration parameters.</summary> - **Minor** [Performance]: String concatenation inside a loop has O(N^2) time complexity. It is recommended to append elements to a list and use `','.join()` to generate the `excludes` string, which is O(N) and significantly more efficient if the exclusion list grows large. - *Suggestion:* Collect matching NEVRs in a list and join them after the loop. ```` excludes_list = [] args = queryargs + ["--repofrompath", f"{hash_repo(mrepo)},{mrepo}"] out = SUBPCAPTURE(args).stdout for line in out.splitlines(): # sname, nevr elems = line.split(",") if len(elems) != 2: continue # pragma: no cover if elems[0] in removes: excludes_list.append(elems[1]) excludes = ",".join(excludes_list) ```` </details> ### ✅ Summary - **Overall Assessment:** No critical issues identified. The transition to DNF options is robust, with a minor algorithmic optimization suggested for string joining. - **Minor Suggestions:** - Switch the string concatenation loop for `excludes` to list `.append()` and `','.join()` for optimal O(N) performance. --- 🤖 **AI Code Review** | Generated with [ai-code-review](https://gitlab.com/redhat/edge/ci-cd/ai-code-review) | **Model:** `gemini-3.1-pro-preview` ⚠️ *AI-generated suggestions may be incorrect. Verify before applying. Not a replacement for human review.*

adamwill commented 2026-04-18 06:55:48 +00:00

Author

Owner

Copy link

switching to an array append and .join() is a safer best practice to handle larger scale inputs effectively

typing didn't like that, unless I use two different variable names for it, so I went with this. ehh. Fine, I'll just use two variables, I guess.

> switching to an array append and .join() is a safer best practice to handle larger scale inputs effectively typing didn't like that, unless I use two different variable names for it, so I went with this. ehh. Fine, I'll just use two variables, I guess.

adamwill commented 2026-04-18 06:58:55 +00:00

Author

Owner

Copy link

actually, no I won't, because that makes pylint complain about too many locals. We'll stick with this.

actually, no I won't, because that makes pylint complain about too many locals. We'll stick with this.

adamwill force-pushed dnf-excludepkgs from db1414151c to 251fd11d3b 2026-04-18 07:06:05 +00:00 Compare

adamwill referenced this pull request 2026-04-18 19:12:32 +00:00

Test pygixml to see if it provides significant performance boost over lxml #30

adamwill referenced this pull request 2026-04-18 19:13:19 +00:00

Experiment with running repoclosures in parallel to speed up overall operation #27

adamwill commented 2026-04-20 01:27:37 +00:00

Author

Owner

Copy link

ARG_MAX seems to be 2097152 in typical Fedora environments

Well, StackOverflow notes that "The maximum size for a single string argument is limited to 131072", and that does seem to be the case in my environment. Still, that seems like enough. Still assuming 50 character NVRs, that's enough room for 2621 of them.

> ARG_MAX seems to be 2097152 in typical Fedora environments Well, [StackOverflow notes](https://stackoverflow.com/questions/29801975/why-is-the-subprocess-popen-argument-length-limit-smaller-than-what-the-os-repor/29802900#29802900) that "The maximum size for a single string argument is limited to 131072", and that does seem to be the case in my environment. Still, that seems like enough. Still assuming 50 character NVRs, that's enough room for 2621 of them.

adamwill commented 2026-04-20 18:32:22 +00:00

Author

Owner

Copy link

This looks to be working fine in testing on staging so far - gives all results the same as prod, including some correct failures. So let's go with it.

This looks to be working fine in testing on staging so far - gives all results the same as prod, including some correct failures. So let's go with it.

adamwill merged commit 251fd11d3b into main 2026-04-20 18:32:30 +00:00

adamwill deleted branch dnf-excludepkgs 2026-04-20 18:32:31 +00:00

adamwill referenced this pull request 2026-04-20 19:26:13 +00:00

Investigate using DNF excludepkgs config option instead of repository metadata modification #5

Sign in to join this conversation.

Reviewers

No reviewers

Labels

Clear labels   

ai-review-please

label for requesting AI code review

  

Backlog Status

Needs Review

Work items that have been created or updated but need review, refinement, or approval before they can be considered ready for sprint planning.

  

Backlog Status

Ready

Work items that have been reviewed, refined, and are ready to be committed to a sprint. These items have clear requirements and can be worked on immediately when capacity is available.

  

chore

Work that needs to be done but doesn't add new functionality or fix bugs. Maintenance tasks that keep the system running smoothly and the codebase clean.

  

documentation

Work focused on creating, updating, or improving documentation for users, developers, or system administrators.

  

points

01

A task that is simple, small, and has very little uncertainty. It should be easy enough for any team member to pick up and complete quickly, without a lot of discussion or research.

  

points

02

This is a task that is slightly more complex or larger than a "1." It might involve two or three simple steps, but the outcome is still very clear and there's little uncertainty.

  

points

03

Medium-sized task with some noticeable complexity. It might require a bit more thought or collaboration. The steps are well-defined, but it's not a trivial change.

  

points

05

A significant piece of work. It has more complexity and a higher degree of uncertainty than smaller tasks. It might require some research, a design discussion, or collaboration across multiple teams.

  

points

08

Complex task with a lot of uncertainty. It's often the largest size that a team will consider for a single sprint. It likely requires a detailed breakdown and multiple team members to complete.

  

points

13

Any task that feels like it's a "13" or more is considered an Epic. These are too large and uncertain to be worked on in a single sprint and should be broken down.

  

Priority

Critical

This is for work that is urgent and of critical importance and so and must be addressed immediately with a higher priority than all other work, even if not originally planned for the current sprint.

  

Priority

High

This is for work that is critical and needs to be addressed in the next sprint. It's often for urgent bugs, important features, or a major piece of technical debt that is blocking other work.

  

Priority

Low

This is for work that is good to do but not urgent. It's a candidate for being worked on when there's extra time or when it rises in importance. It can stay in the backlog for a longer period.

  

Priority

Medium

This is for important work that should be done soon, but isn't as urgent as a high-priority item. It will likely be considered for the next 1-2 sprints.

  

Sprint Status

Blocked

Work items that cannot progress due to external dependencies, blockers, or issues that need resolution.

  

Sprint Status

Done

Work items that have been completed, reviewed, and integrated. No further work is needed within the current sprint.

  

Sprint Status

In Progress

Work items currently being worked on by a team member. Active development, research, or implementation is happening.

  

Sprint Status

Review

Work items that are complete but need review, testing, or approval before being marked as done.

  

Sprint Status

To Do

Work items that are committed to the sprint but haven't been started yet. These items are ready to be picked up by team members.

  

Technical Debt

Work that addresses shortcuts, workarounds, or suboptimal implementations that were done previously to meet deadlines. These items improve code quality, maintainability, or performance without adding new features.

  

Work Item

Bug

Issues where the system is not working as intended or designed. Bugs represent deviations from expected behavior.

  

Work Item

Epic

Large initiatives that are broken down into multiple smaller work items (user stories, tasks, bugs). Epics represent significant features or projects that span multiple sprints.

  

Work Item

Spike

Time-boxed research, investigation, or proof-of-concept work to reduce uncertainty or explore solutions. Spikes help inform future development decisions.

  

Work Item

Task

Used to break down larger user stories into smaller, manageable implementation pieces. They focus on the specific technical steps needed to deliver the user story's value.

  

Work Item

User Story

User-facing features or functionality that can be framed from a user perspective, describing what someone wants to accomplish and why.

No labels

ai-review-please

Backlog Status

Needs Review

Backlog Status

Ready

chore

documentation

points

01

points

02

points

03

points

05

points

08

points

13

Priority

Critical

Priority

High

Priority

Low

Priority

Medium

Sprint Status

Blocked

Sprint Status

Done

Sprint Status

In Progress

Sprint Status

Review

Sprint Status

To Do

Technical Debt

Work Item

Bug

Work Item

Epic

Work Item

Spike

Work Item

Task

Work Item

User Story

Milestone

Clear milestone

No items

No milestone

Projects

Clear projects

No items

No project

Assignees

Clear assignees

No assignees

2 participants

Notifications

Subscribe

Due date

The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference

quality/rmdepcheck!32

No description provided.