Action Requested: App Configuration Problems Found in repo [copilot-runtime-bazel-cache]
Personne n'a encore pris cette issue.
Évaluation
- Difficulté
- 4/5
- Temps estimé
- 3-5 jours
- Accessibilité débutants
- 35/100
- Type d'issue
- Bug
- Clarté
- Plutôt claire
- Activité
- Active
- Stack technique
- go, kubernetes
- Domaine
- devops, infrastructure
Piste de recherche
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.
Rédigé par le modèle d'indexation à partir du texte de l'issue.
Description
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
- Langage dominant
- Shell
- Étoiles
- 11.3k
- Forks
- 2k
- Métriques de merge des PR
- Aucune PR mergée en 30 j
Préparer son environnement
- Aucun Dockerfile ni fichier Docker Compose
- Aucun modèle de pull request
- Lire le guide de contribution
Par où commencer
- Lisez l'issue en entier, puis le guide de contribution du projet.
- Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
- Forkez le dépôt et travaillez sur une branche.
- Ouvrez une pull request qui référence le numéro de l'issue.
Autres issues de github/copilot-cli
-
area:configuration area:input-keyboard
Difficulté 2/5 1-3 heures Accessibilité débutants 62/100
github/copilot-cli#5159 ·
-
area:sessions
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
github/copilot-cli#5147 · 1 commentaire ·
-
area:input-keyboard
Difficulté 2/5 1-3 heures Accessibilité débutants 66/100
github/copilot-cli#5113 ·
-
area:sessions
Difficulté 2/5 1-3 heures Accessibilité débutants 72/100
github/copilot-cli#4996 ·
-
triage
Difficulté 1/5 Moins d'une heure Accessibilité débutants 88/100
github/copilot-cli#4963 · 1 commentaire ·
Toutes les issues de github/copilot-cli
Issues similaires
-
bug good first issue
Difficulté 2/5 1-3 heures Accessibilité débutants 68/100
scarif-labs/horus#61 ·
Les mainteneurs répondent en général sous 1 jour
-
documentation
Difficulté 2/5 1-3 heures Accessibilité débutants 88/100
IntersectMBO/developer-experience#362 ·
Les mainteneurs répondent en général sous 2 jours
-
Difficulté 2/5 1-3 heures Accessibilité débutants 78/100
registrystack/registry-stack#2168 ·
Les mainteneurs répondent en général sous 1 jour
-
Difficulté 1/5 Moins d'une heure Accessibilité débutants 92/100
Les mainteneurs répondent en général sous 2 jours
-
Bug triage/confirmed
Difficulté 2/5 Une demi-journée Accessibilité débutants 85/100
agentscope-ai/agentscope#3355 ·
Les mainteneurs répondent en général sous 2 jours