Add v1 recipe debugging using py-rattler-build - #5950
Merged
Conversation
jsmolic
force-pushed
the
v1-integration-debug
branch
from
April 19, 2026 12:36
5fc7b14 to
0f0f302
Compare
3 tasks
jsmolic
force-pushed
the
v1-integration-debug
branch
2 times, most recently
from
April 29, 2026 13:54
db8167d to
7a752fa
Compare
jaimergp
previously approved these changes
Apr 29, 2026
jaimergp
enabled auto-merge (squash)
April 29, 2026 14:12
jaimergp
disabled auto-merge
April 29, 2026 14:53
jsmolic
force-pushed
the
v1-integration-debug
branch
from
April 29, 2026 14:56
7a752fa to
bd9073b
Compare
Contributor
Author
|
Example debug session: recipe.yaml: I'll add a test for |
Member
Should we use |
Contributor
Author
oh yes, I was going to use |
jsmolic
force-pushed
the
v1-integration-debug
branch
from
April 29, 2026 22:37
bd9073b to
8554afe
Compare
Contributor
Author
|
Hmm there is a newly added v1 recipe test on windows that seems to be flaky, need to investigate why is that |
jsmolic
force-pushed
the
v1-integration-debug
branch
2 times, most recently
from
May 5, 2026 09:02
4a6bc1d to
b6b9268
Compare
jaimergp
reviewed
May 6, 2026
jaimergp
reviewed
May 6, 2026
jaimergp
reviewed
May 6, 2026
jaimergp
reviewed
May 6, 2026
jaimergp
reviewed
Jul 2, 2026
jaimergp
reviewed
Jul 2, 2026
jaimergp
reviewed
Jul 2, 2026
jaimergp
approved these changes
Jul 7, 2026
This commit introduces support for debugging v1 recipes using py-rattler-build's debug API [1]. While py-rattler-build provides more functionality, we are currently using it only to setup debug environment and scripts, to match `conda-debug`'s behavior with v0 recipes. The process loads and renders the recipe, and invokes `DebugSession.create()` method to setup the environment before printing debugging instructions to the console. [1] https://rattler-build.prefix.dev/dev/py-rattler-build/reference/debug/
- Reword the prompt when multiple outputs are found - Properly raise an error when no recipe files are found in the directory - Error out when `recipe.yaml` and `meta.yaml` are found in the same dir - Drop redundant recipe path from the debug failure report - Drop redundant check for commands in process_recipe()
jsmolic
force-pushed
the
v1-integration-debug
branch
from
July 8, 2026 14:31
51048b1 to
213cb88
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
This PR introduces support for debugging v1 recipes using
py-rattler-build's debug API [1].
While py-rattler-build provides more functionality, we are currently
using it only to setup debug environment and scripts, to match
conda-debug's behavior with v0 recipes.The process loads and renders the recipe, and invokes
DebugSession.create()method to setup the environment before printingdebugging instructions to the console.
[1] https://rattler-build.prefix.dev/dev/py-rattler-build/reference/debug/
NOTE: This PR depends on #5924
Checklist - did you ...
newsdirectory (using the template) for the next release's release notes?