wileyj
wileyj
@kenrogers ? looks like you did the previous doc, can you and @andre-stacks get the updates ready or is there a PR being worked on to address?
tinkering a bit, but there may be an easier way than modifying what looks like a lot of files in stacks-core. the command *must* follow a pattern (when using a...
something like this is what i'm thinking: ```bash #!/usr/bin/env bash echo "received cmd: '$@'" ARGS=($@) # store as an array config="" for i in $(seq 1 $#); do echo "args...
> I think the approach you describe makes sense (taking advantage of the stacks core "start" command) and it is likely the least intrusive. > > Regarding container permissions: the...
https://doc.rust-lang.org/cargo/reference/profiles.html#split-debuginfo
note: grafana pyroscope and possibly some other tools used via docker would need the symbols
> And it doesn't seem we have special test workflows for `is_signer_release` case Correct - there's nothing specific to signer tests currently (although there could be). i'm more than happy...
moving to ghcr - one thing i don't like is how all the layers (tagged or not) are visible on the packages page (see link above). i have a feeling...
there is also a question of if we should be re-running all the same tests (which should have been passing prior to release in order for the changes to merge),...
update - one thing i notice that i'm not sure about (but shoudln't be a blocker to merge) is that the artifacts are being attested 2x for the same archive....