Christian Kruse

I am not particularly worried with handling the load with a canned 503 responses. Agents have had a pretty reasonable default backoff strategy (starting at 1s and doubling each retry...

@echlebek it looks like our queue library is implemented as a pub/sub that relies on the backend id getter daemon for discovering subscribers/backends. It also appears to only be used...

@fguimond I'm a little confused about what we are meant to be estimating here. Everything in the epic?

I do not think that a config flag or a global config resource like `web/v1.GlobalConfig` is the right answer here. We should probably rework silences in 7.0 to require an...

@calebhailey after reviewing with eng, I think we're recommending that this feature be put on hold until 7.x. Noted Concerns: * This change at the API level would necessitate a...

Work in progress document capturing some of the options here: https://docs.google.com/document/d/1OfT6fLIqKggGt0pKcFiBGa6Jb5KgygX7DpSy9Pt0XSo/edit?usp=sharing

Currently this is held up pending the 6.8.2 release. The 6.8.0 and 6.8.1 releases have targeted a diverging version of the api/core/v3 module. This diversion needs corrected before we can...

Migration strategy doc: https://docs.google.com/document/d/1WkxACxR7e769a7IkdJW9FLO0cBik7azVENVLRUgU9Lg/edit?usp=sharing

More generally, the issue is that `cue get go` makes an assumption that all of the types referenced in a given package belong to either the current package or a...

> Life permitting I will attempt a PR this weekend. That weekend really got away from me 😆. Confirmed that this is still an issue in v0.4.3, and would (of...