John Eckersberg
John Eckersberg
> What is the motivation for using select() and not epoll() or poll()? select() is worse in every way, the only reason to use it is if you are on...
CI/cargo-fmt fix in #555
> @cgwalters Do you know if there's there a way for Rust to detect what platform your system is running? I'm able to find and match against the arch of...
> By "platform" I meant e.g. AWS vs GCP vs OpenStack etc. Ah gotcha. That's what I get for not reading back far enough for context. Carry on!
The vast majority of the code already lives as a separate library crate under https://github.com/containers/bootc/tree/main/lib. The current bootc cli is really just a thin wrapper around the library. It looks...
From: https://github.com/containers/bootc/blob/9a1e29cf3f0d2aa45206845a7e69bb9f21a4a157/lib/src/task.rs#L89 Currently setting the environment `RUST_LOG=debug` should provide this with output like: `DEBUG exec: "ostree" "--repo=/ostree/repo" "rev-parse" "--single"` Is that sufficient? If so, at the very least it sounds...
Confirmed, the code for the status command doesn't consult that flag at all today: https://github.com/containers/bootc/blob/593a93225813f6c99afd66010f0edb8539dc2415/lib/src/status.rs#L302-L327 The `--booted` flag is available in `StatusOpts.booted`, but note the only thing we consult in...
I think this is a *fantastic* idea that really drives home the big-picture model of how this is all supposed to work together.
Ok, I've pushed my rebased and seemingly-working fork onto the original here so I can continue to iterate here instead of off in my own world. I know there are...
~~Something else that needs fixed:~~ ~~`ERROR Status: Computing status: Booted deployment: Reading deployment metadata: Reading manifest data from commit: Missing ostree.manifest-digest metadata on merge commit`~~ ~~I get that if I...