You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ensure unique package requirements and constraints
Exported on 7/3/2025 at 16:34:28 EDT from Cursor (1.2.1)
User
I want to write a python program in test/collection_linter.py to ensure that the sets of requirements and constraints defined by multiple collections of python packages are unique. There are two input collections, "accelerated" and "non-accelerated". The files for the collections are under the "./collections" directory, organized with one collection in each subdirectory. Within each collection, there are directories for "build variants". The build variants may be different for each collection. Within each build variant will be a requirements.txt file and a constraints.txt file.
The entries in the requirements.txt files for all build variants of a collection should be combined to find the set of unique names. The versions do not matter. There should not be any items in the non-accelerated collection's requirements that appear in the accelerated collection's requirements.
Exported on 6/24/2025 at 18:46:26 EDT from Cursor (1.1.5)
User
I want to work on github issue 538. Let's start by adding documentation to the using.md file explaining the high level steps that are taken when bootstrapping a project.
The documentation for this project should use concise clear language.
Exported on 6/10/2025 at 18:32:13 EDT from Cursor (1.0.0)
User
I need to add a new "stats" command to fromager to show some information about how many packages of different types are included in a build. It should take as input a requirements.txt file and a fromager graph.json file. It should produce as output a table showing:
how many unique packages were included in the build based on the package names in the graph file
Exported on 5/31/2025 at 14:51:08 EDT from Cursor (0.50.7)
User
I need to write a bash script to test the "fromager graph to-constraints" command. It should be similar to the other test scripts in the e2e directory. It should use the file e2e/graph-with-dependency-conflict.json as the input file for the fromager command, and it should report an error when trying to create a constraints file from the graph file.
Exported on 5/31/2025 at 10:22:48 EDT from Cursor (0.50.7)
User
I want to add a new class to this file like the GitHubTagProvider but that looks at a GitLab repository for the tag values instead of github.com. The constructor should take a URL for the gitlab server, the full path to the project on that server, and regular expression to use to match tag names and parse the version part out of the name. The default regex should match everything. The _find_tags() method should use the requests library to access the gitlab API and iterate through the tags that match the regex, yielding a Version object created from the version portion of the tag.
Exported on 5/19/2025 at 14:32:03 EDT from Cursor (0.50.5)dhellmann
User
Add a new subcommand to this file called build-parallel. It should take the same arguments as build_sequence except instead of a build_order_file it should take a graph_file