Evan Lowry

@zachaller yep, PR in - will get it reviewed and tested on Monday and report back. Thanks!

1.4.1 doesn't not appear to have addressed the issue. ``` Recovered from panic: runtime error: invalid memory address or nil pointer dereference goroutine 337 [running]: runtime/debug.Stack() /usr/local/go/src/runtime/debug/stack.go:24 +0x65 github.com/argoproj/argo-rollouts/utils/controller.processNextWorkItem.func1.1.1() /go/src/github.com/argoproj/argo-rollouts/utils/controller/controller.go:149...

Sure thing! Some nouns edited and some annotations / labels removed ```yaml apiVersion: argoproj.io/v1alpha1 kind: Rollout metadata: annotations: argocd.argoproj.io/sync-wave: '10' rollout.argoproj.io/revision: '46' rollout.argoproj.io/workload-generation: '52' creationTimestamp: '2022-06-03T17:50:51Z' generation: 39 labels: app.kubernetes.io/instance:...

It's more frustrating, because there is jfrog documentation (blog posts) that suggests this should work - but as shown above, does not. https://jfrog.com/help/r/title-artifactory-how-to-use-jfrog-cli-to-add-build-info-to-images-built-with-docker-buildx/artifactory-how-to-use-jfrog-cli-to-add-build-info-to-images-built-with-docker-buildx https://jfrog.com/help/r/jfrog-cli/pushing-docker-images-using-buildx The underlying check (which I believe...

`on.workflow_call` tends to be the types of workflows of which I use inputs the most. Not having `getInput` return the input greatly diminishes the utility of github-script imo!

Still an issue, at least w.r.t. invalid output. This is using CLI version 2.40.0 ``` Error details: instance.runs[0].tool.driver.rules[1].help requires property "text" { "path": [ "runs", 0, "tool", "driver", "rules", 1,...

@Or-Gabay this does not fix the issue, ports are still held open w/ exhaustion on all the ports, resulting in a TCP timeout. @eyalbe4 I think I would have looked...

Some different thoughts that floated to mind: Batching queries, to make less roundtrips, or putting in retries on failure. Doesn't solve the TCP stuff directly, but does increase the overall...

@eyalbe4 yep, I confirmed it was 1.39.3 before posting. But for completing the circle:  Versions I have observed this issue with: 1.35.5 1.37.1 1.38.2 1.38.4 1.39.3

``` jobs: build: runs-on: ubuntu-latest steps: - name: Checkout uses: actions/checkout@v2 - name: Setup Jfrog CLI uses: jfrog/setup-jfrog-cli@v1 with: VERSION: 1.39.3 env: JF_ARTIFACTORY_1: ${{ secrets.ARTIFACTORY_CONFIG }} - name: Install Dependencies...