Ethan Davidson

For the project I have in mind, native targets are the priority. However, supporting jvm and js targets would also be desirable. The use case here is a CLI tool...

Just did a quick test and it sent the notification at "default" level, which appears to be, ahem, [the default](https://github.com/grafana/oncall/blob/88f9f118a3f98b5e2b7d37a1a1bd1d6fb2d4d929/engine/apps/alerts/tasks/notify_user.py#L28). (seems obvious in hindsight!) To add a usecase here, I'd...

Yeah, I guess that's not too bad: ``` strings.SliceRunes(input, 0, list.Min([63, len(strings.Runes(input))])) ``` I'm happy with closing this, but I'll leave that up to the maintainers. I don't remember the...

I'm also having a similar issue upgrading from 0.69.0 to 0.74.2 - The collector is failing to start, and logging `Error: invalid argument "-component.UseLocalHostAsDefaultHost" for "--feature-gates" flag: no such feature...

Something is fishy here. I just upgraded the operator helm chart from 0.79.0 to 0.86.1, and confirmed that I'm running operator v0.122.0 and collector-contrib 0.122.1. According to the changelogs, these...

I don't think it's that bug, because I do have some log settings that haven't been clobbered (`logs.encoding` and `logs.level`), plus in that bug there's no mention of the double-set...

Here's another segfault stacktrace: ``` unexpected fault address 0x0 fatal error: fault [signal SIGSEGV: segmentation violation code=0x80 addr=0x0 pc=0x46f36f] goroutine 66 [running]: runtime.throw(0xefacc1, 0x5) /usr/local/go/src/runtime/panic.go:1116 +0x72 fp=0xc00036db20 sp=0xc00036daf0 pc=0x439592 runtime.sigpanic()...

I'm also facing this issue, and it prevents the collector from being able to autoscale correctly. When new pods are scaled in, they receive no traffic because all the clients...

Hi @AlbinaBlazhko17! I do have `spec-strict-refs: error` in my config and it hasn't flagged anything. I've also manually validated some of the refs to components that are being removed, and...

Sorry for the slow responses on my end. I don't have much time to spend on this, so I've unfortunately worked around it by simply removing the `remove-unused-components` decorator. This...