Action Requested: App Configuration Problems Found in repo [copilot-runtime-bazel-cache]
还没有人认领这个 Issue。
评估
- 难度
- 4/5
- 预计耗时
- 3-5 天
- 新手友好度
- 35/100
- Issue 类型
- 缺陷
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- go, kubernetes
- 领域
- devops, infrastructure
调研方向
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.
由索引模型根据 Issue 内容生成。
描述
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
- 主要语言
- Shell
- 星标
- 11.3k
- 派生
- 2k
- PR 合并指标
- 30 天内没有已合并 PR
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 没有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
github/copilot-cli 的其他 Issue
-
area:configuration area:input-keyboard
难度 2/5 1-3 小时 新手友好度 62/100
github/copilot-cli#5159 ·
-
area:sessions
难度 2/5 1-3 小时 新手友好度 72/100
github/copilot-cli#5147 · 1 条评论 ·
-
area:input-keyboard
难度 2/5 1-3 小时 新手友好度 66/100
github/copilot-cli#5113 ·
-
area:sessions
难度 2/5 1-3 小时 新手友好度 72/100
github/copilot-cli#4996 ·
-
triage
难度 1/5 1 小时以内 新手友好度 88/100
github/copilot-cli#4963 · 1 条评论 ·
查看 github/copilot-cli 的全部 Issue
相似的 Issue
-
gdsa opencode: keep-alive cleanup trap fails with 'keepalive_pid: unbound variable'可能已有人在做 @darribas 今天认领。 未关闭
难度 2/5 1-3 小时 新手友好度 85/100
-
bug
难度 2/5 1-3 小时 新手友好度 74/100
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 65/100
-
icon request
难度 2/5 1-3 小时 新手友好度 66/100
-
难度 1/5 1 小时以内 新手友好度 78/100