Dylan Arbour
Dylan Arbour
Tested with: https://github.com/suborbital/e2core/actions/runs/3191431125/jobs/5207735085
>I guess we will have to wait on spf13/cobra#754 to finish before taking further action here. Why? Re: submit completions to the main repository
`term_timeout` should work for our case (similar to @villesau) but I feel like the `/shutdown` endpoint is safer. I can guarantee it if the job takes 5 seconds or 5...
Understood. Some of our jobs may run for many hours and some others (like migration) complete reasonably. The migration task is far far more common. Feels strange to set a...
We also use a single workspace to manage another 33. Would love to be able to bitflip locking from Git instead of the GUI. 😁
I ran into this by hoping I could use the Github App that is already set up, by passing `oauth_token_id = ""` which is currently what the API has set.
This is still an outstanding issue.
Should this just be notifications or should it be the entire resource isn't reconciled based on selective file patterns?
We're seeing this issue with `v2.5.0`. We're able to reproduce it by looping over a large number of requests (in our case its a customer-driven CSV import) which calls `.publish()`...
So after some analysis, it's timeout errors that are causing the duplication. Simply, if we hit `.publish()` without waiting for a response (the Promise) it will eventually start: ``` {...