Stephen Benjamin

Results 35 issues of Stephen Benjamin

## Your Question I'm having an odd issue using GORM with BigQuery. I've pared things down to a very, very simple `.Find`, and unmarshalling into a struct: ```go q.Table("Tags"). Select("ROW_NUMBER()...

``` {"level":"info","ts":"2024-03-28T11:02:09Z","caller":"handler/handler.go:31","msg":"Discovering api resources"} {"level":"fatal","ts":"2024-03-28T11:02:10Z","caller":"cmd/main.go:40","msg":"failed to construct server","error":"failed to construct api group list: groupVersion \"\" does not yield exactly two result when slash splitting","stacktrace":"main.main\n\t/go/src/github.com/alvaroaleman/static-kas/cmd/main.go:40\nruntime.main\n\t/usr/local/go/src/runtime/proc.go:255"} ``` The must gather from https://prow.ci.openshift.org/view/gs/test-platform-results/logs/periodic-ci-openshift-release-master-nightly-4.16-e2e-aws-ovn-single-node/1773011563020554240...

We had originally tried to detect UPI cluster by presence of an infrastructure resource but looks like that's actually there. The best way to skip this just seems to be...

approved
lgtm
do-not-merge/hold
jira/invalid-bug
jira/valid-reference

Managed service pods are setting hard limits, instead of requests, contrary to OCP conventions. Ref: https://github.com/openshift/enhancements/blob/master/CONVENTIONS.md#resources-and-limits [OSD-21708](https://issues.redhat.com//browse/OSD-21708) tracks fixing these pods, meanwhile add exceptions so the test passes.

approved
lgtm
do-not-merge/hold
lifecycle/rotten
jira/valid-reference

From: https://github.com/openshift/microshift/tree/main/origin/patches

approved

**Client** cloud.google.com/go/bigquery v1.57.1 **Environment** Mac OS **Go Environment** ``` $ go version go version go1.21.4 darwin/arm64 $ go env GO111MODULE='' GOARCH='arm64' GOBIN='' GOCACHE='/Users/stbenjam/Library/Caches/go-build' GOENV='/Users/stbenjam/Library/Application Support/go/env' GOEXE='' GOEXPERIMENT='' GOFLAGS='' GOHOSTARCH='arm64' GOHOSTOS='darwin'...

type: feature request
api: bigquery
priority: p3

We are sometimes leaving this test with kube-apiserver operator "Progressing" -- this triggers a failure in gather-extra of the "operator conditions kube-apiserver" test, which expects operators to be stable when...

approved
lgtm
jira/valid-bug
jira/valid-reference

approved
do-not-merge/work-in-progress

I filed bugs for these in the OSD project, adding various exceptions for now to get the tests to pass.

approved