Hacktoberfest 2026: as issues que os mantenedores marcaram para outubro, abertas e boas para iniciantes. Ver issues do Hacktoberfest

Action Requested: App Configuration Problems Found in repo [copilot-runtime-bazel-cache]

Aberta
  • Algo errado?
#5,174 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
4/5
Tempo estimado
3-5 dias
Facilidade para iniciantes
35/100
Tipo de issue
Bug
Clareza
Razoavelmente clara
Status de atividade
Ativa
Stack de tecnologia
go, kubernetes
Domínio
devops, infrastructure

Direção de pesquisa

Start with config/kubernetes/production/deployments/deployment.yaml and go.mod, then read the linked moda-linter rule documentation for the three reported checks. Review the container probes, the Go service paved path, and the metrics-proxy GOMAXPROCS setting; verify corrections by opening a PR and checking the linter annotations.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

triage
What is this?

In order to help ensure a smooth and painless deployment experience, we scan each repository for potential configuration problems. Our scanner has identified some problems with copilot-runtime-bazel-cache's configuration which might cause unexpected application behavior. These issues were found on copilot-runtime-bazel-cache's default branch during the last linter run.

NOTE: moda-linter validates configurations for all repos regardless of deployment strategy.

What do I need to do?
  1. Review the list of problems below.
  2. Fix the problems listed by correcting the problem or adding an ignore rule. There are links on each item for more information on how to do so.
  3. Verify the fix by opening a new PR. The linter will automatically run and annotate any remaining problems on your PR. If your fixes are correct, you should not see any new annotations.
  4. Once the fixes have been merged, feel free to close this issue.
Does a rule not apply to your configuration? False positives?

We are aware of certain exceptions to our rules, but our bot is not. If you would like to ignore a rule, please see the following documentation: Ignoring Rules.
Please be certain that you need to ignore a rule before doing so. These checks are here to help prevent hard-to-debug deployment issues, lighten the burden on the support team, and ultimately make the deployment process smoother.

What happens now?

This check will run on a regular interval. If we detect configuration problems in copilot-runtime-bazel-cache's default branch, this issue will be reopened.

Help!

Each rule includes a link to documentation explaining the violation and how to fix it. If you still have questions after reading the docs, please use the owning team and Slack contact information included with that violation in the list below.

The linter framework is maintained by #dx-pathfinders.

Detected Configuration Problems
Issue File More Info
kube-validation#container with unrecommended probes policy deployment.yaml Workload copilot-runtime-bazel-cache has a container with an un-recommended probes policy


More info: https://github.com/github/moda-linter/blob/main/rules/docs/container_with_unrecommended_probes_policy.md

Reach out to #dx-pathfinders for assistance.
This rule is owned by: @github/dx-pathfinders
kube-validation#go sdlc paved path go.mod This Go application does not use the go-server paved path (github.com/github/go-server). Using go-server is the required approach for Go services deployed on Moda. See https://github.com/github/go-server for more information. If you require an exception, go to https://github.com/github/paved-path-exceptions.


More info: https://github.com/github/moda-linter/blob/main/rules/docs/go_sdlc_paved_path.md

Reach out to #go-services-framework-discussion for assistance.
This rule is owned by: @github/dx-pathfinders
kube-validation#validate gomaxprocs deployment.yaml Container metrics-proxy in Deployment copilot-runtime-bazel-cache: GOMAXPROCS environment variable is not set


More info: https://github.com/github/moda-linter/blob/main/rules/docs/validate_gomaxprocs.md

Reach out to #performance-engineering for assistance.
This rule is owned by: @github/performance-engineering

cc @github/copilot-cli

Linguagem predominante
Shell
Estrelas
11.3k
Forks
2k
Nenhum PR com merge em 30d

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de github/copilot-cli

Todas as issues de github/copilot-cli

Issues semelhantes

Mais issues de Shell/Bash

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.