chore: update go to 1.24 #9673
Merged
chore: update go to 1.24 #9673
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
b577db3 to
0401d7a
Compare
Closed
Signed-off-by: Justin Chadwell <me@jedevc.com>
0401d7a to
e24521e
Compare
sipsma
approved these changes
Feb 24, 2025
jpadams
pushed a commit
to jpadams/dagger
that referenced
this pull request
Feb 25, 2025
Signed-off-by: Justin Chadwell <me@jedevc.com>
gerhard
added a commit
that referenced
this pull request
Mar 10, 2025
Still not sure about the name - `call-2025-03-10` is not great - but I am more interested to check if this fixes the issue. After all Alternative CI jobs started failing since #9673, this introduces a separate `call` action which is only used by these alternative CI runners. We want something simpler that has a separate lifecyle from the main `call` action that we use in the primary CI runners. The problem with the current `call` action logging config is that GitHub Actions UI breaks, as well as the Namespace UI, so troubleshooting the source of this issue is very difficult. I even downloaded the logs locally, which did not make it easier to find the issue. FTR: ~/Downloads/logs_35440011783 on ☁️ ❯ ls -lah total 264M drwx------ 11 gerhard staff 352 Mar 10 19:24 . drwxr-xr-x 59 gerhard _lpoperator 1.9K Mar 10 19:24 .. -rw-rw-r-- 1 gerhard staff 28M Nov 30 1979 '0_docs-lint-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '1_docs-lint-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 86M Nov 30 1979 '2_test-cli-engine-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '3_sdk-go-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '4_sdk-python-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 31M Nov 30 1979 '5_sdk-typescript-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '6_sdk-go-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '7_sdk-typescript-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '8_sdk-python-dev-on-namespace-local-engine _ local-dagger-engine.txt' What's most peculiar about this issue is that the trace in Dagger Cloud doesn't show any issues: https://v3.dagger.cloud/dagger/traces/57d1391e843c1d8a7cfb473f60c034e2 Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
gerhard
added a commit
that referenced
this pull request
Mar 11, 2025
Still not sure about the name - `call-2025-03-10` is not great - but I am more interested to check if this fixes the issue. After all Alternative CI jobs started failing since #9673, this introduces a separate `call` action which is only used by these alternative CI runners. We want something simpler that has a separate lifecyle from the main `call` action that we use in the primary CI runners. The problem with the current `call` action logging config is that GitHub Actions UI breaks, as well as the Namespace UI, so troubleshooting the source of this issue is very difficult. I even downloaded the logs locally, which did not make it easier to find the issue. FTR: ~/Downloads/logs_35440011783 on ☁️ ❯ ls -lah total 264M drwx------ 11 gerhard staff 352 Mar 10 19:24 . drwxr-xr-x 59 gerhard _lpoperator 1.9K Mar 10 19:24 .. -rw-rw-r-- 1 gerhard staff 28M Nov 30 1979 '0_docs-lint-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '1_docs-lint-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 86M Nov 30 1979 '2_test-cli-engine-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '3_sdk-go-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '4_sdk-python-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 31M Nov 30 1979 '5_sdk-typescript-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '6_sdk-go-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '7_sdk-typescript-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '8_sdk-python-dev-on-namespace-local-engine _ local-dagger-engine.txt' What's most peculiar about this issue is that the trace in Dagger Cloud doesn't show any issues: https://v3.dagger.cloud/dagger/traces/57d1391e843c1d8a7cfb473f60c034e2 Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
gerhard
added a commit
that referenced
this pull request
Mar 11, 2025
Still not sure about the name - `call-2025-03-10` is not great - but I am more interested to check if this fixes the issue. After all Alternative CI jobs started failing since #9673, this introduces a separate `call` action which is only used by these alternative CI runners. We want something simpler that has a separate lifecyle from the main `call` action that we use in the primary CI runners. The problem with the current `call` action logging config is that GitHub Actions UI breaks, as well as the Namespace UI, so troubleshooting the source of this issue is very difficult. I even downloaded the logs locally, which did not make it easier to find the issue. FTR: ~/Downloads/logs_35440011783 on ☁️ ❯ ls -lah total 264M drwx------ 11 gerhard staff 352 Mar 10 19:24 . drwxr-xr-x 59 gerhard _lpoperator 1.9K Mar 10 19:24 .. -rw-rw-r-- 1 gerhard staff 28M Nov 30 1979 '0_docs-lint-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '1_docs-lint-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 86M Nov 30 1979 '2_test-cli-engine-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '3_sdk-go-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '4_sdk-python-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 31M Nov 30 1979 '5_sdk-typescript-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '6_sdk-go-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '7_sdk-typescript-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '8_sdk-python-dev-on-namespace-local-engine _ local-dagger-engine.txt' What's most peculiar about this issue is that the trace in Dagger Cloud doesn't show any issues: https://v3.dagger.cloud/dagger/traces/57d1391e843c1d8a7cfb473f60c034e2 Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
gerhard
added a commit
that referenced
this pull request
Mar 17, 2025
Still not sure about the name - `call-2025-03-10` is not great - but I am more interested to check if this fixes the issue. After all Alternative CI jobs started failing since #9673, this introduces a separate `call` action which is only used by these alternative CI runners. We want something simpler that has a separate lifecyle from the main `call` action that we use in the primary CI runners. The problem with the current `call` action logging config is that GitHub Actions UI breaks, as well as the Namespace UI, so troubleshooting the source of this issue is very difficult. I even downloaded the logs locally, which did not make it easier to find the issue. FTR: ~/Downloads/logs_35440011783 on ☁️ ❯ ls -lah total 264M drwx------ 11 gerhard staff 352 Mar 10 19:24 . drwxr-xr-x 59 gerhard _lpoperator 1.9K Mar 10 19:24 .. -rw-rw-r-- 1 gerhard staff 28M Nov 30 1979 '0_docs-lint-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '1_docs-lint-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 86M Nov 30 1979 '2_test-cli-engine-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '3_sdk-go-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '4_sdk-python-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 31M Nov 30 1979 '5_sdk-typescript-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '6_sdk-go-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '7_sdk-typescript-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '8_sdk-python-dev-on-namespace-local-engine _ local-dagger-engine.txt' What's most peculiar about this issue is that the trace in Dagger Cloud doesn't show any issues: https://v3.dagger.cloud/dagger/traces/57d1391e843c1d8a7cfb473f60c034e2 Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
gerhard
added a commit
that referenced
this pull request
Mar 17, 2025
After all Alternative CI jobs started failing since #9673, this introduces a separate `call-ci-alt-runner` action which is only used by these alternative CI runners. We want something simpler that has a separate lifecyle from the main `call` action that we use in the primary CI runners. The problem with the current `call` action logging config is that GitHub Actions UI breaks, as well as the Namespace UI, so troubleshooting the source of this issue is very difficult. I even downloaded the logs locally, which did not make it easier to find the issue. FTR: ~/Downloads/logs_35440011783 on ☁️ ❯ ls -lah total 264M drwx------ 11 gerhard staff 352 Mar 10 19:24 . drwxr-xr-x 59 gerhard _lpoperator 1.9K Mar 10 19:24 .. -rw-rw-r-- 1 gerhard staff 28M Nov 30 1979 '0_docs-lint-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '1_docs-lint-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 86M Nov 30 1979 '2_test-cli-engine-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '3_sdk-go-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '4_sdk-python-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 31M Nov 30 1979 '5_sdk-typescript-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '6_sdk-go-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '7_sdk-typescript-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '8_sdk-python-dev-on-namespace-local-engine _ local-dagger-engine.txt' What's most peculiar about this issue is that the trace in Dagger Cloud doesn't show any issues: https://v3.dagger.cloud/dagger/traces/57d1391e843c1d8a7cfb473f60c034e2 Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
gerhard
added a commit
that referenced
this pull request
Mar 17, 2025
After all Alternative CI jobs started failing since #9673, this introduces a separate `call-ci-alt-runner` action which is only used by these alternative CI runners. We want something simpler that has a separate lifecyle from the main `call` action that we use in the primary CI runners. The problem with the current `call` action logging config is that GitHub Actions UI breaks, as well as the Namespace UI, so troubleshooting the source of this issue is very difficult. I even downloaded the logs locally, which did not make it easier to find the issue. FTR: ~/Downloads/logs_35440011783 on ☁️ ❯ ls -lah total 264M drwx------ 11 gerhard staff 352 Mar 10 19:24 . drwxr-xr-x 59 gerhard _lpoperator 1.9K Mar 10 19:24 .. -rw-rw-r-- 1 gerhard staff 28M Nov 30 1979 '0_docs-lint-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '1_docs-lint-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 86M Nov 30 1979 '2_test-cli-engine-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '3_sdk-go-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '4_sdk-python-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 31M Nov 30 1979 '5_sdk-typescript-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '6_sdk-go-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '7_sdk-typescript-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '8_sdk-python-dev-on-namespace-local-engine _ local-dagger-engine.txt' What's most peculiar about this issue is that the trace in Dagger Cloud doesn't show any issues: https://v3.dagger.cloud/dagger/traces/57d1391e843c1d8a7cfb473f60c034e2 Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
gerhard
added a commit
that referenced
this pull request
Mar 17, 2025
After all Alternative CI jobs started failing since #9673, this introduces a separate `call-ci-alt-runner` action which is only used by these alternative CI runners. We want something simpler that has a separate lifecyle from the main `call` action that we use in the primary CI runners. The problem with the current `call` action logging config is that GitHub Actions UI breaks, as well as the Namespace UI, so troubleshooting the source of this issue is very difficult. I even downloaded the logs locally, which did not make it easier to find the issue. FTR: ~/Downloads/logs_35440011783 on ☁️ ❯ ls -lah total 264M drwx------ 11 gerhard staff 352 Mar 10 19:24 . drwxr-xr-x 59 gerhard _lpoperator 1.9K Mar 10 19:24 .. -rw-rw-r-- 1 gerhard staff 28M Nov 30 1979 '0_docs-lint-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '1_docs-lint-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 86M Nov 30 1979 '2_test-cli-engine-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '3_sdk-go-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '4_sdk-python-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 31M Nov 30 1979 '5_sdk-typescript-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '6_sdk-go-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '7_sdk-typescript-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '8_sdk-python-dev-on-namespace-local-engine _ local-dagger-engine.txt' What's most peculiar about this issue is that the trace in Dagger Cloud doesn't show any issues: https://v3.dagger.cloud/dagger/traces/57d1391e843c1d8a7cfb473f60c034e2 Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
gerhard
added a commit
that referenced
this pull request
Mar 18, 2025
After all Alternative CI jobs started failing since #9673, this introduces a separate `call-ci-alt-runner` action which is only used by these alternative CI runners. We want something simpler that has a separate lifecyle from the main `call` action that we use in the primary CI runners. The problem with the current `call` action logging config is that GitHub Actions UI breaks, as well as the Namespace UI, so troubleshooting the source of this issue is very difficult. I even downloaded the logs locally, which did not make it easier to find the issue. FTR: ~/Downloads/logs_35440011783 on ☁️ ❯ ls -lah total 264M drwx------ 11 gerhard staff 352 Mar 10 19:24 . drwxr-xr-x 59 gerhard _lpoperator 1.9K Mar 10 19:24 .. -rw-rw-r-- 1 gerhard staff 28M Nov 30 1979 '0_docs-lint-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '1_docs-lint-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 86M Nov 30 1979 '2_test-cli-engine-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '3_sdk-go-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '4_sdk-python-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 31M Nov 30 1979 '5_sdk-typescript-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '6_sdk-go-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '7_sdk-typescript-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '8_sdk-python-dev-on-namespace-local-engine _ local-dagger-engine.txt' What's most peculiar about this issue is that the trace in Dagger Cloud doesn't show any issues: https://v3.dagger.cloud/dagger/traces/57d1391e843c1d8a7cfb473f60c034e2 Signed-off-by: Gerhard Lazu <gerhard@dagger.io>
kpenfound
pushed a commit
to kpenfound/dagger
that referenced
this pull request
Mar 21, 2025
After all Alternative CI jobs started failing since dagger#9673, this introduces a separate `call-ci-alt-runner` action which is only used by these alternative CI runners. We want something simpler that has a separate lifecyle from the main `call` action that we use in the primary CI runners. The problem with the current `call` action logging config is that GitHub Actions UI breaks, as well as the Namespace UI, so troubleshooting the source of this issue is very difficult. I even downloaded the logs locally, which did not make it easier to find the issue. FTR: ~/Downloads/logs_35440011783 on ☁️ ❯ ls -lah total 264M drwx------ 11 gerhard staff 352 Mar 10 19:24 . drwxr-xr-x 59 gerhard _lpoperator 1.9K Mar 10 19:24 .. -rw-rw-r-- 1 gerhard staff 28M Nov 30 1979 '0_docs-lint-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '1_docs-lint-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 86M Nov 30 1979 '2_test-cli-engine-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '3_sdk-go-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 30M Nov 30 1979 '4_sdk-python-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 31M Nov 30 1979 '5_sdk-typescript-on-namespace-remote-engine _ remote-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 15M Nov 30 1979 '6_sdk-go-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '7_sdk-typescript-dev-on-namespace-local-engine _ local-dagger-engine.txt' -rw-rw-r-- 1 gerhard staff 16M Nov 30 1979 '8_sdk-python-dev-on-namespace-local-engine _ local-dagger-engine.txt' What's most peculiar about this issue is that the trace in Dagger Cloud doesn't show any issues: https://v3.dagger.cloud/dagger/traces/57d1391e843c1d8a7cfb473f60c034e2 Signed-off-by: Gerhard Lazu <gerhard@dagger.io> Signed-off-by: kpenfound <kyle@dagger.io>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.