ChrisPage-AT

Do we know if the plan is to fix DLC in the aws-ecr orb or to remove the DLC options from the commands/job? I don't want to reinvent the wheel...

How do I go about using that "ts" value to update a message? I know how to use "ts" to reply in a thread but trying to use app.client.chat_update requires...

Ah, I see closed PR now. Do you know if this is something the Cypress.io team is interested in still? Those `totalDuration`, `totalFailed`, `totalPassed`, etc fields would help me do...

That would be perfectly fine since if anyone needs that much detail they can just look at the Cypress Cloud site. I'm just looking for whatever data variables you'd use...

I'm also seeing this but it just fails the workflows instead of being slow. It doesn't happen with every build but it does force us to rebuild when it fails....

I am also running into this issue: > Successfully dispatched workflow: > Repository: *** > Branch: *** > Workflow ID: ***.yml > Distinct ID: 348a1190-04f9-4c90-b5e5-ef3608dd4265 > Attempt to extract run...

@Codex- Using the api calls listed in your readme, I can find the triggered pipeline with `List Workflow Runs` and use the id to see the jobs with `List Jobs...

Of course! The JSON itself is fine, it just ends up not being usable in later steps when certain CVEs are present. I have some bash steps after I run...

Awesome! And yeah that totally makes sense to me. Definitely don't want to change default behaviors on folks without proper warning.

I was able to get the pod's cpu/ram data using the following two lines, if it helps: `CPUS=$(( $(cat /sys/fs/cgroup/cpu/cpu.cfs_quota_us) / $(cat /sys/fs/cgroup/cpu/cpu.cfs_period_us) ))` `MEMORY_BYTES=$(cat /sys/fs/cgroup/memory/memory.limit_in_bytes)`