Closed dependabot[bot] closed 9 months ago
I'm currently fixing this PR to address the following:
[Sweep GHA Fix] The GitHub Actions run failed with the following error logs: ``` The command: Run thollander/actions-comment-pull-request@v2 yielded the following error: ##[error]Parameter token or opts.auth is required Here are the logs: ```
[!CAUTION]
An error has occurred: Cmd('git') failed due to: exit code(128) cmdline: git clone -v --branch=dependabot/github_actions/actions/upload-artifact-4.0.0 -- https://*****:*****@github.com/openimsdk/helm-charts.git /tmp/cache/repos/openimsdk/helm-charts/base/dependabot--github_actions--actions--upload-artifact-4--0--0 stderr: 'fatal: could not create work tree dir '/tmp/cache/repos/openimsdk/helm-charts/base/dependabot--github_actions--actions--upload-artifact-4--0--0': No space left on device ' (tracking ID: a76bc63ae1)
I'm currently fixing this PR to address the following:
[Sweep GHA Fix] The GitHub Actions run failed with the following error logs: ``` The command: Run thollander/actions-comment-pull-request@v2 yielded the following error: ##[error]Parameter token or opts.auth is required ##[group]Run # Install MySQL [36;1m# Install MySQL[0m [36;1mhelm install my-release oci://registry-1.docker.io/bitnamicharts/mysql -f infra/mysql-config.yaml -n openim --create-namespace[0m [36;1m[0m [36;1m# Install Kafka[0m [36;1mhelm install im-kafka infra/kafka -f infra/kafka-config.yaml -n openim --create-namespace[0m [36;1m[0m [36;1m# Install MinIO[0m [36;1mhelm install im-minio infra/minio -f infra/minio-config.yaml -n openim --create-namespace[0m [36;1m[0m [36;1m# Install MongoDB[0m [36;1mhelm install im-mongodb infra/mongodb -f infra/mongodb-config.yaml -n openim --create-namespace[0m [36;1m[0m [36;1m# Install Redis[0m [36;1mhelm install im-redis infra/redis -f infra/redis-config.yaml -n openim --create-namespace[0m shell: /usr/bin/bash -e {0} ##[endgroup] Pulled: registry-1.docker.io/bitnamicharts/mysql:9.16.1 Digest: sha256:3eb456c10d7829936c38c2f11d6b3c408015c64d5d960213e8cf375fdd570465 NAME: my-release LAST DEPLOYED: Sun Jan 7 19:15:54 2024 NAMESPACE: openim STATUS: deployed REVISION: 1 TEST SUITE: None NOTES: CHART NAME: mysql CHART VERSION: 9.16.1 APP VERSION: 8.0.35 ** Please be patient while the chart is being deployed ** Tip: Watch the deployment status using the command: kubectl get pods -w --namespace openim Services: echo Primary: my-release-mysql.openim.svc.cluster.local:3306 Execute the following to get the administrator credentials: echo Username: root MYSQL_ROOT_PASSWORD=$(kubectl get secret --namespace openim my-release-mysql -o jsonpath="{.data.mysql-root-password}" | base64 -d) To connect to your database: 1. Run a pod that you can use as a client: kubectl run my-release-mysql-client --rm --tty -i --restart='Never' --image m.daocloud.io/docker.io/bitnami/mysql:8.0.35-debian-11-r2 --namespace openim --env MYSQL_ROOT_PASSWORD=$MYSQL_ROOT_PASSWORD --command -- bash 2. To connect to primary service (read/write): mysql -h my-release-mysql.openim.svc.cluster.local -uroot -p"$MYSQL_ROOT_PASSWORD" Error: INSTALLATION FAILED: failed post-install: timed out waiting for the condition ##[error]Process completed with exit code 1. ##[group]Run sudo kubectl cluster-info [36;1msudo kubectl cluster-info[0m [36;1msudo kubectl get pods -n kube-system[0m [36;1mecho "current-context:" $(kubectl config current-context)[0m [36;1mecho "environment-kubeconfig:" ${KUBECONFIG}[0m shell: /usr/bin/bash -e {0} ##[endgroup] E0107 19:14:57.566758 8896 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused E0107 19:14:57.567165 8896 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused E0107 19:14:57.568628 8896 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused E0107 19:14:57.569012 8896 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused E0107 19:14:57.570410 8896 memcache.go:265] couldn't get current server API group list: Get "http://localhost:8080/api?timeout=32s": dial tcp [::1]:8080: connect: connection refused The connection to the server localhost:8080 was refused - did you specify the right host or port? To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'. ##[error]Process completed with exit code 1. Here are the logs: ```
[!CAUTION]
An error has occurred: Cmd('git') failed due to: exit code(128) cmdline: git clone -v --branch=dependabot/github_actions/actions/upload-artifact-4.0.0 -- https://*****:*****@github.com/openimsdk/helm-charts.git /tmp/cache/repos/openimsdk/helm-charts/base/dependabot--github_actions--actions--upload-artifact-4--0--0 stderr: 'fatal: could not create work tree dir '/tmp/cache/repos/openimsdk/helm-charts/base/dependabot--github_actions--actions--upload-artifact-4--0--0': No space left on device ' (tracking ID: 83db6ebe7a)
OK, I won't notify you again about this release, but will get in touch when a new version is available. If you'd rather skip all updates until the next major or minor version, let me know by commenting @dependabot ignore this major version
or @dependabot ignore this minor version
. You can also ignore all major, minor, or patch releases for a dependency by adding an ignore
condition with the desired update_types
to your config file.
If you change your mind, just re-open this PR and I'll resolve any conflicts on it.
Bumps actions/upload-artifact from 3.1.3 to 4.0.0.
Release notes
Sourced from actions/upload-artifact's releases.
Commits
c7d193f
Merge pull request #466 from actions/v4-beta13131bb
licensed cache4a6c273
Merge branch 'main' into v4-betaf391bb9
Merge pull request #465 from actions/robherley/v4-documentation9653d03
Apply suggestions from code review875b630
add limitations sectionecb2146
add compression example5e7604f
trim some repeated infod6437d0
naming1b56155
s/v4-beta/v4/gDependabot will resolve any conflicts with this PR as long as you don't alter it yourself. You can also trigger a rebase manually by commenting
@dependabot rebase
.Dependabot commands and options
You can trigger Dependabot actions by commenting on this PR: - `@dependabot rebase` will rebase this PR - `@dependabot recreate` will recreate this PR, overwriting any edits that have been made to it - `@dependabot merge` will merge this PR after your CI passes on it - `@dependabot squash and merge` will squash and merge this PR after your CI passes on it - `@dependabot cancel merge` will cancel a previously requested merge and block automerging - `@dependabot reopen` will reopen this PR if it is closed - `@dependabot close` will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually - `@dependabot show