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
In looking at automating some of the drawings from #1139 (and interactive features beyond), there are a few CLI features that would be very helpful to have as (related) schema-constrained JSON:
The other would be trace-level information, which would pretty much preclude interactive stdin:
pixi run -v --jsonl [--environment] [TASK]
I'm imagining this would be streaming JSONL, rather than a big slug emitted at the end with the return code, very similar to run -v. I haven't looked at how deeply the stdout and stderr of started processes are being managed, but that's a pretty big one to be able to reason about (otherwise one has to do a lot of sniffing), and would get even more complex if parallel execution were added.
Hopefully much of this would pretty much be taken care of by flipping a switch somewhere in the logging infrastructure, but I don't really know where to look. There are likely conventions (of which I'm not aware) for field naming, but things like dates as UTC ISO8601 are fairly predictable.
With the above, pretty much any task-oriented UI could be built on top of the pixi CLI.
Getting up to an understandable env definition (much less feature-oriented UI) will be... harder to reason about, for sure (been there)!
The text was updated successfully, but these errors were encountered:
Problem description
Thank you for
pixi
!In looking at automating some of the drawings from #1139 (and interactive features beyond), there are a few CLI features that would be very helpful to have as (related) schema-constrained JSON:
https://pixi.sh/latest/schema/taskinfo/schema.json
https://pixi.sh/latest/schema/trace/schema.json
The other would be trace-level information, which would pretty much preclude interactive
stdin
:I'm imagining this would be streaming JSONL, rather than a big slug emitted at the end with the return code, very similar to
run -v
. I haven't looked at how deeply thestdout
andstderr
of started processes are being managed, but that's a pretty big one to be able to reason about (otherwise one has to do a lot of sniffing), and would get even more complex if parallel execution were added.Hopefully much of this would pretty much be taken care of by flipping a switch somewhere in the logging infrastructure, but I don't really know where to look. There are likely conventions (of which I'm not aware) for field naming, but things like dates as UTC ISO8601 are fairly predictable.
With the above, pretty much any task-oriented UI could be built on top of the
pixi
CLI.Getting up to an understandable env definition (much less
feature
-oriented UI) will be... harder to reason about, for sure (been there)!The text was updated successfully, but these errors were encountered: