Exported on 9/20/2025 at 14:12:45 EDT from Cursor (1.6.35)
User
I want to work on jira issue @https://issues.redhat.com/browse/AIPCC-5343 by creating a bin/build_wheels.sh script that wraps the pipeline-api/build_wheels.sh script similar to how bin/bootstrap.sh works.
The new script should take as input a containerfile, a constraints file, and a graph file.
Exported on 9/19/2025 at 15:52:43 EDT from Cursor (1.5.11)
User
I want to work on jira ticket @https://issues.redhat.com/browse/AIPCC-5335 . Start by looking at ci-wheelhouse.yml and .gitlab-test-jobs.yaml to see how the test bootstrap-and-onboard jobs in this repository are defined. Then add a new base job to the ci-wheelhouse.yml file using the variable-based parameterized jobs there as examples. Set the same variables for the new job that appear in the jobs in .gitlab-test-jobs.yaml.
Exported on 9/6/2025 at 17:53:19 EDT from Cursor (1.5.9)
User
I want to add an option to the to-dot command that will reduce the graph that is output to only include nodes that have some fromager overrides, settings, patches, or plugins. Nodes without any of those things should not be included in the graph, but relationships between the nodes should be. If package A depends on B and B depends on C but only packages A and C are output, then A should show a dependency directly on C without a B node in between.
| v1.5.1505+rhelai-rocm-ubi9 transformers==4.50.1 2025-03-26 18:54:52 +0000 | |
| v1.5.1505+rhelai-gaudi-ubi9 transformers==4.50.1 2025-03-26 18:54:52 +0000 | |
| v1.5.1505+rhelai-cuda-ubi9 transformers==4.50.1 2025-03-26 18:54:52 +0000 | |
| v1.5.1495+rhelai-rocm-ubi9 transformers==4.50.1 2025-03-26 06:28:22 +0100 | |
| v1.5.1495+rhelai-gaudi-ubi9 transformers==4.50.1 2025-03-26 06:28:22 +0100 | |
| v1.5.1495+rhelai-cuda-ubi9 transformers==4.50.1 2025-03-26 06:28:22 +0100 | |
| v1.5.1491+rhelai-rocm-ubi9 transformers==4.50.1 2025-03-25 20:15:50 +0000 | |
| v1.5.1491+rhelai-gaudi-ubi9 transformers==4.50.1 2025-03-25 20:15:50 +0000 | |
| v1.5.1489+rhelai-cuda-ubi9 transformers==4.50.1 2025-03-25 20:05:15 +0000 | |
| v1.5.1482+rhelai-rocm-ubi9 transformers==4.50.0 2025-03-24 10:44:55 +0100 |
| 19:01:08 INFO loading settings from /home/dhellmann/devel/aipcc/builder/overrides/settings.yaml | |
| 19:01:08 INFO loading constraints from collections/accelerated/cpu-ubi9/constraints.txt | |
| 19:01:08 INFO Looking for updates to vllm (constraint: vllm==0.9.1) | |
| 19:01:08 INFO vllm: found get_resolver_provider override | |
| 19:01:08 WARNING Could not check versions for vllm: get_resolver_provider() missing 1 required positional argument: 'ignore_platform' | |
| 19:01:08 INFO Looking for updates to torch (constraint: torch==2.7.0) | |
| 19:01:08 INFO Found 2 newer version(s) for torch | |
| 19:01:08 INFO Looking for updates to torchaudio (constraint: torchaudio==2.7.0) | |
| 19:01:08 INFO Found 2 newer version(s) for torchaudio | |
| 19:01:08 INFO Looking for updates to torchvision (constraint: torchvision==0.22.0) |
Exported on 8/20/2025 at 18:54:07 EDT from Cursor (1.4.5)
User
I want to add a new command similar to list-versions that takes as input a constraints file and for each valid requirements specifier in the file it prints versions of the package that are newer than the version selected with == in the constraint.
If the constraint sets a lower bound by using >= then the constraint should be ignore.
Exported on 8/9/2025 at 16:30:40 EDT from Cursor (1.3.9)
User
I want to add a new command to this project to list all versions of a package based on an input requirement specifier. The command should use the get_resolver_provider hook to retrieve a resolver provider for the package in case there is a custom provider. It should use the returned provider to print a list of all of the version numbers, in increasing order, for packages that match the input requirement. Describe how you would build that, including mentioning any new files that should be created.
Exported on 8/9/2025 at 16:18:02 EDT from Cursor (1.3.9)
User
I want to add a new command to this project to list all versions of a package based on an input requirement specifier. The command should use the get_resolver_provider hook to retrieve a resolver provider for the package in case there is a custom provider. It should use the returned provider to print a list of all of the version numbers, in increasing order, for packages that match the input requirement. Describe how you would build that, including mentioning any new files that should be created.