Steve Kuznetsov comments

Results 190 comments of


                                            Steve Kuznetsov

event-watcher: don't parse resource version

> Without it, it will always process all the current events, meaning if you restart the service, you'd get duplicates. Makes sense? @agalue that is not how the informer library...

HOSTEDCP-1466: test/ginkgo: allow many external binaries

/close

HOSTEDCP-1466: auditloganalyzer: don't parse the URL unless we need to

/retest

HOSTEDCP-1466: auditloganalyzer: don't parse the URL unless we need to

``` INFO[2024-03-11T13:29:22Z] Tagging openshift/release:rhel-8-release-golang-1.20-openshift-4.16 into pipeline:root. ERRO[2024-03-11T14:04:23Z] Could not resolve tag root in imagestream pipeline. error=timed out waiting for the condition ``` Seems like CI is busted for this repo...

HOSTEDCP-1466: auditloganalyzer: don't parse the URL unless we need to

/test all

HOSTEDCP-1466: auditloganalyzer: don't parse the URL unless we need to

WTF? /retest

HOSTEDCP-1466: auditloganalyzer: don't parse the URL unless we need to

/retest

HOSTEDCP-1466: auditloganalyzer: don't parse the URL unless we need to

/close

Ability to indicate that when upgrading, you can't skip y+1

Is it common for projects to follow strict semantic versioning? Even very-well-funded projects like Kubernetes don't, and require migrations through versions. Is it realistic to only support strict semver?

Ability to indicate that when upgrading, you can't skip y+1

> The thing is - we have a second option: replaces/skips/skipRanges. We also have many, many years of customer feedback on this system and it is not very positive.