Config:

linters:
  disable-all: true
  enable:
  - goimports
  - gci
  fast: false

linters-settings:
  goimports:
    local-prefixes: istio.io/

Input:

package main

import (
	"fmt"
	"istio.io/istio/pkg/test/framework/resource"
	"os"

	"istio.io/istio/pkg/test/framework/resource"
)

var (
	_ = resource.Cluster
	_ = fmt.Println
	_ = os.Stdout
)

Is your feature request related to a problem? Please describe.

Following the guidance of github, many developers are moving to main as their default branch. Saving developers from the very small hindrance of using DEFAULT_BRANCH: main would contribute to smoothing the transition.

Describe the solution you'd like

The default branch should be main. If it does not exist, use `m

Summary

Backend error: Exit status: 500, message: {"Type":"ExecutableNotFoundError","Message":"OCI runtime exec failed: exec failed: container_linux.go:349: starting container process caused \"exec: \\\"bash\\\": executable file not found in $PATH\": unknown","Handle":"","ProcessID":"","Binary":""}

Steps to reproduce

Use @vito buildkit container, or any container which doe

JanitorConfigurator should have an option to delete logs for specific builders (or tags). Users might want to delete logs for only specific builders, or might want to keep logs for specific builders for longer duration.

http://docs.buildbot.net/latest/manual/cfg-configurators.html#janitorconfigurator currently doesn't seems to contain any such option.

I would welcome a feature when, at the same url which is set to respond with OK status, I could have an error response generated with a random seed.

I am developing an Observable pattern to perform a series of retries to call an endpoint, with increasing delay. The problem is that during testing, I cannot really mock up the condition by randomly switching between two mocky.io urls (error and ok

As shown in #204, there's a need to being able to disable the UID and GID checks of the "Container Security Context" check without disabling the other checks that are made. I'm therefore proposing to split this check into three separate ones:

• Container Security Context User/Group