Aaron Batilo

Are these 3 runs happening within the same workflow? Or is it 3 different workflow executions happening at the same time?

I tried using this for logging in to AWS via GitHub instead of Okta and ran into the problem that the only grant types that are supported are the ones...

Oh, that's an interesting idea. I hadn't considered the idea of putting hooks in with the env execution also but in hindsight it makes a lot of sense!

> Actually, I feel like the repository has `master` and `main` branches at the same time. Can you check that? @draftcode sorry for the delay. It does not appear that...

Ohhhhh interesting. @draftcode. Look at the output of: ``` ⇒ av stack tree master main Import-datadog-namespace Reference-namespace-resource-for-pg-secret ``` For some reason, master is still in the av tree? I don't...

I tracked the problem down to this line: https://github.com/aviator-co/av/blob/9b993bb53f138f6fe1af37605dacbbabd4f90ae7/internal/git/git.go#L41 If you have a repo that had a previous default branch name. Like in my case our repo used to have...

Thanks for responding @kevin85421. My original question still stands then. Is there no way to have the jobs running in progress survive after the Ray head gets restarted? I see...

Oh goodness. 🤦 Thank you for pointing that out. With the former syntax, is there a way to still instantiate things like the `json` formatter while keeping the init one...

I appreciate the warm welcome and extremely fast responses from contributors to this repo! The frustration at least turned into a great learning experience. My recent background is almost entirely...

After doing some more debugging: ```rust use tracing::{debug, info}; use tracing_subscriber::EnvFilter; fn main() { tracing_subscriber::fmt() .with_env_filter(EnvFilter::from_default_env()) .init(); info!("INFO Hello World!"); debug!("DEBUG Hello World!"); } ``` Explicitly calling `with_env_filter` makes this...