Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

ci: Chinese copywrite #9410

Closed
Sn0rt opened this issue May 5, 2023 · 0 comments · Fixed by #9411
Closed

ci: Chinese copywrite #9410

Sn0rt opened this issue May 5, 2023 · 0 comments · Fixed by #9411

Comments

@Sn0rt
Copy link
Contributor

Sn0rt commented May 5, 2023

Current Behavior

can't pass the CI (this ci doesn't work before

Expected Behavior

pass the ci

Error Logs

/usr/bin/docker run --name ed866eeb562d5d663453d381bb62bb0b52fdd7_8a5fa8 --label ed866e --workdir /github/workspace --rm -e "INPUT_ARGS" -e "HOME" -e "GITHUB_JOB" -e "GITHUB_REF" -e "GITHUB_SHA" -e "GITHUB_REPOSITORY" -e "GITHUB_REPOSITORY_OWNER" -e "GITHUB_REPOSITORY_OWNER_ID" -e "GITHUB_RUN_ID" -e "GITHUB_RUN_NUMBER" -e "GITHUB_RETENTION_DAYS" -e "GITHUB_RUN_ATTEMPT" -e "GITHUB_REPOSITORY_ID" -e "GITHUB_ACTOR_ID" -e "GITHUB_ACTOR" -e "GITHUB_TRIGGERING_ACTOR" -e "GITHUB_WORKFLOW" -e "GITHUB_HEAD_REF" -e "GITHUB_BASE_REF" -e "GITHUB_EVENT_NAME" -e "GITHUB_SERVER_URL" -e "GITHUB_API_URL" -e "GITHUB_GRAPHQL_URL" -e "GITHUB_REF_NAME" -e "GITHUB_REF_PROTECTED" -e "GITHUB_REF_TYPE" -e "GITHUB_WORKFLOW_REF" -e "GITHUB_WORKFLOW_SHA" -e "GITHUB_WORKSPACE" -e "GITHUB_ACTION" -e "GITHUB_EVENT_PATH" -e "GITHUB_ACTION_REPOSITORY" -e "GITHUB_ACTION_REF" -e "GITHUB_PATH" -e "GITHUB_ENV" -e "GITHUB_STEP_SUMMARY" -e "GITHUB_STATE" -e "GITHUB_OUTPUT" -e "RUNNER_OS" -e "RUNNER_ARCH" -e "RUNNER_NAME" -e "RUNNER_TOOL_CACHE" -e "RUNNER_TEMP" -e "RUNNER_WORKSPACE" -e "ACTIONS_RUNTIME_URL" -e "ACTIONS_RUNTIME_TOKEN" -e "ACTIONS_CACHE_URL" -e GITHUB_ACTIONS=true -e CI=true -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/apisix/apisix":"/github/workspace" ed866e:eb562d5d663453d381bb62bb0b52fdd7 autocorrect --lint --no-diff-bg-color ./docs/zh/latest/
................................................................................................................................

docs/zh/latest/plugins/proxy-mirror.md:44:1
-| path | string | 否   |        |        | 指定镜像请求的路径。如果不指定,则默认会使用当前路径。 如果是为了镜像 grpc 流量,这个选项不再适用。|
+| path | string | 否   |        |        | 指定镜像请求的路径。如果不指定,则默认会使用当前路径。如果是为了镜像 grpc 流量,这个选项不再适用。|

docs/zh/latest/plugins/proxy-mirror.md:45:178
-作为镜像请求的路径。当然如果是为了镜像 grpc 流量,这个选项也不再适用。|
+作为镜像请求的路径。当然如果是为了镜像 grpc 流量,这个选项也不再适用。|

docs/zh/latest/CHANGELOG.md:77:56
-响应头:
+响应头:

docs/zh/latest/CHANGELOG.md:81:3
-:sunrise: 支持将路由证书存储在 secrets manager 中:
+:sunrise: 支持将路由证书存储在 secrets manager 中:

docs/zh/latest/CHANGELOG.md:82:3
-:sunrise: 支持通过配置绕过 Admin API 身份验证:
+:sunrise: 支持通过配置绕过 Admin API 身份验证:

docs/zh/latest/CHANGELOG.md:86:3
-:sunrise: fault-injection 插件支持请求头注入:
+:sunrise: fault-injection 插件支持请求头注入:

docs/zh/latest/CHANGELOG.md:87:3
-:sunrise: 提供在其他插件中引用 proxy-rewrite 插件中路由改写捕捉到的变量支持:
+:sunrise: 提供在其他插件中引用 proxy-rewrite 插件中路由改写捕捉到的变量支持:

docs/zh/latest/CHANGELOG.md:88:[48](https://github.com/apache/apisix/actions/runs/4888721584/jobs/8727097694?pr=9388#step:3:50)
-redis 认证方式:
+redis 认证方式:

docs/zh/latest/CHANGELOG.md:92:3
-修复 etcd 数据同步异常:
+修复 etcd 数据同步异常:

docs/zh/latest/CHANGELOG.md:93:32
-中的无效缓存:
+中的无效缓存:

docs/zh/latest/CHANGELOG.md:94:3
-修复由健康检查引起的高 CPU 和内存占用:
+修复由健康检查引起的高 CPU 和内存占用:

docs/zh/latest/CHANGELOG.md:95:39
-时生效:
+时生效:

docs/zh/latest/CHANGELOG.md:96:36
-插件中的引用:
+插件中的引用:

docs/zh/latest/CHANGELOG.md:97:3
-修复启动时无法连接到 etcd 的问题:
+修复启动时无法连接到 etcd 的问题:

docs/zh/latest/CHANGELOG.md:98:3
-修复域节点的健康检查泄漏问题:
+修复域节点的健康检查泄漏问题:

docs/zh/latest/CHANGELOG.md:100:3
-确保 hold_body_chunk 函数对每个插件设置独立缓冲区,避免数据污染:
+确保 hold_body_chunk 函数对每个插件设置独立缓冲区,避免数据污染:

docs/zh/latest/CHANGELOG.md:101:3
-确保 batch-requests 插件能够在尾部响应头存在时能够正确读取:
+确保 batch-requests 插件能够在尾部响应头存在时能够正确读取:

Steps to Reproduce

more detail can find from
image

Environment

  • APISIX version (run apisix version):
  • Operating system (run uname -a):
  • OpenResty / Nginx version (run openresty -V or nginx -V):
  • etcd version, if relevant (run curl http://127.0.0.1:9090/v1/server_info):
  • APISIX Dashboard version, if relevant:
  • Plugin runner version, for issues related to plugin runners:
  • LuaRocks version, for installation issues (run luarocks --version):

https://github.com/apache/apisix/actions/runs/4888721584/jobs/8727097694?pr=9388#logs

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant