Action Requested: App Configuration Problems Found in repo [copilot-runtime-bazel-cache]
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 4/5
- Tempo stimato
- 3-5 giorni
- Idoneità per principianti
- 35/100
- Tipo di issue
- Bug
- Chiarezza
- Abbastanza chiara
- Stato di attività
- Attiva
- Stack tecnologico
- go, kubernetes
- Ambito
- devops, infrastructure
Direzione di ricerca
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.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
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?
- Review the list of problems below.
- 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.
- 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.
- 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
- Lingua principale
- Shell
- Stelle
- 11.3k
- Fork
- 2k
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di github/copilot-cli
-
area:configuration area:input-keyboard
Difficoltà 2/5 1-3 ore Idoneità per principianti 62/100
github/copilot-cli#5159 ·
-
area:sessions
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
github/copilot-cli#5147 · 1 commento ·
-
area:input-keyboard
Difficoltà 2/5 1-3 ore Idoneità per principianti 66/100
github/copilot-cli#5113 ·
-
area:sessions
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
github/copilot-cli#4996 ·
-
triage
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
github/copilot-cli#4963 · 1 commento ·
Tutte le issue di github/copilot-cli
Issue simili
-
[安全] 为粘贴到 Shell 的代码引用转义路径Forse già presa @myot233 l’ha presa oggi. Aperta
Difficoltà 2/5 1-3 ore Idoneità per principianti 74/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 85/100
facebookincubator/muse-gadget-sdk#249 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 88/100
-
bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 78/100
I maintainer di solito rispondono entro 2 giorni
-
Difficoltà 1/5 1-3 ore Idoneità per principianti 78/100
btclib-org/portanode#699 ·
I maintainer di solito rispondono entro 1 giorno