Chris Evich

I'm not sure hooking into repo. dispatch is a good idea, since that's the only available 'if nothing else applies' event. In other words, it's not possible to predict how...

> could it happen cause we update the VM. Most probably. Here's what happes at image-build time: https://github.com/containers/automation_images/blob/main/cache_images/fedora-netavark_packaging.sh#L72-L76 So if I understand correctly, we need to add 'default' to the...

@lmr noted: > Well, I'd say to remove it (maybe set a file DEBUG variable to print that if we are so inclined to resolve a bug).

I shamelessly agree. Though to calm sceptics, it may make sense to marshal everything through a shim layer. This can also help hide compatibility issues which are otherwise ugly to...

Sure, here's a recent one: https://cirrus-ci.com/build/4901845003665408

Oh..wait a sec...they ARE there! I just blew my window up to full-screen and they appeared :confused: Though if the value could be included with an ellipse (...) when the...

I'm running into this problem as well now. In case it helps, the version-retraction mechanism in go is explained here: https://go.dev/ref/mod#go-mod-file-retract It seems like the `rollback` feature should be in...

Suggestion: Look into the old RHTS (old internal Red Hat client test execution system) code, perhaps there's useful nuggets there that could be 'borrowed'.

I'm not a go expert, but I can be dangerous. Have I read the code correctly in that most of this feature only needs updates to `pkg/engine/config.go`? It seems the...

> if you don't have the cycles to do this let me know I'll give it a go this week. I'd like to make time for it, but certainly not...