Bump Go version to 1.25.8 by ycombinator · Pull Request #10156 · elastic/elastic-agent

ycombinator · 2025-09-25T17:46:23Z

This PR bumps up the Golang version to 1.25.8. It also:

removes the ms_tls13kdf Golang build tag when building in FIPS mode because this tag was only needed before Golang versions 1.24.x.
sets ths GODEBUG=tlsmlkem=0 environment variable when running FIPS140-only unit tests. This prevents errors like so: Failed to connect: crypto/ecdh: use of X25519 is not allowed in FIPS 140-only mode.

elasticmachine · 2025-09-25T17:46:27Z

Pinging @elastic/elastic-agent-control-plane (Team:Elastic-Agent-Control-Plane)

ycombinator · 2025-09-25T19:12:54Z

The fips140=only unit tests are failing like so:

crypto/ecdh: use of X25519 is not allowed in FIPS 140-only mode

These appear to be golang/go#75148, which should be fixable when golang/go#74630 is implemented. However, in order to upgrade to Go 1.25.1 now, we'll need to find a workaround.

dev-tools/mage/otel/deps_test.go

ycombinator · 2025-09-25T22:43:15Z

The fips140=only unit tests are failing like so:
crypto/ecdh: use of X25519 is not allowed in FIPS 140-only mode
These appear to be golang/go#75148, which should be fixable when golang/go#74630 is implemented. However, in order to upgrade to Go 1.25.1 now, we'll need to find a workaround.

These errors are coming from Go downloading dependencies before executing the tests. The errors can be simulated like so:

GODEBUG=fips140=only go mod download -x
# get https://proxy.golang.org/github.com/opencontainers/image-spec/@v/v1.1.1.info
# get https://proxy.golang.org/github.com/opencontainers/image-spec/@v/v1.1.1.info: Get "https://proxy.golang.org/github.com/opencontainers/image-spec/@v/v1.1.1.info": crypto/ecdh: use of X25519 is not allowed in FIPS 140-only mode
...

So we probably just need to download the dependencies explicitly, ensuring that GODEBUG=fips140=only is not set for this step.

ycombinator · 2025-09-26T05:23:10Z

So we probably just need to download the dependencies explicitly, ensuring that GODEBUG=fips140=only is not set for this step.

I've implemented this approach in this PR and it has helped. However, now CI is failing with this odd error which seems unrelated to FIPS in any way.

https://buildkite.com/elastic/elastic-agent/builds/27575#0199842f-d9dd-4481-9d46-37baa5c789b1/155-822

=== FAIL: dev-tools/mage TestGoTest_CaptureOutput/capture_panic (1.61s)
--
  | >> go test: asserts Testing
  | >> ARGS: asserts Command: gotestsum --no-color --junitfile-hide-skipped-tests -f standard-quiet -- -test.run TestGoTest_Helper_WithPanic .
  | 2025/09/26 04:35:17 exec: gotestsum --no-color --junitfile-hide-skipped-tests -f standard-quiet -- -test.run TestGoTest_Helper_WithPanic .
  | exec: gotestsum --no-color --junitfile-hide-skipped-tests -f standard-quiet -- -test.run TestGoTest_Helper_WithPanic .
  | gotest_test.go:120: GoTest output mismatch:
  | want:
  | (?sm:
  | === FAIL: dev-tools/mage TestGoTest_Helper_WithPanic.*
  | panic: Kaputt. \[recovered\].*
  | panic: Kaputt.*
  | )
  |  
  | got:
  | FAIL	github.com/elastic/elastic-agent/dev-tools/mage	0.021s
  |  
  | === Failed
  | === FAIL: dev-tools/mage TestGoTest_Helper_WithPanic (0.00s)
  | panic: Kaputt. [recovered, repanicked]
  |  
  | goroutine 21 [running]:
  | testing.tRunner.func1.2({0xcd39e0, 0xf923f0})
  | /opt/buildkite-agent/.asdf/installs/golang/1.25.1/go/src/testing/testing.go:1872 +0x237
  | testing.tRunner.func1()
  | /opt/buildkite-agent/.asdf/installs/golang/1.25.1/go/src/testing/testing.go:1875 +0x35b
  | panic({0xcd39e0?, 0xf923f0?})
  | /opt/buildkite-agent/.asdf/installs/golang/1.25.1/go/src/runtime/panic.go:783 +0x132
  | github.com/elastic/elastic-agent/dev-tools/mage.TestGoTest_Helper_WithPanic(0xc000103880?)
  | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1758859361500881345/elastic/elastic-agent/dev-tools/mage/gotest_test.go:329 +0x30
  | testing.tRunner(0xc000103880, 0xea4750)
  | /opt/buildkite-agent/.asdf/installs/golang/1.25.1/go/src/testing/testing.go:1934 +0xea
  | created by testing.(*T).Run in goroutine 1
  | /opt/buildkite-agent/.asdf/installs/golang/1.25.1/go/src/testing/testing.go:1997 +0x465
  |  
  | DONE 1 tests, 1 failure in 0.022s
  |  
  | === FAIL: dev-tools/mage TestGoTest_CaptureOutput (26.02s)

ycombinator · 2025-09-26T10:33:21Z

So we probably just need to download the dependencies explicitly, ensuring that GODEBUG=fips140=only is not set for this step.

I've implemented this approach in this PR and it has helped. However, now CI is failing with this odd error which seems unrelated to FIPS in any way.

https://buildkite.com/elastic/elastic-agent/builds/27575#0199842f-d9dd-4481-9d46-37baa5c789b1/155-822

=== FAIL: dev-tools/mage TestGoTest_CaptureOutput/capture_panic (1.61s)
--
  | >> go test: asserts Testing
  | >> ARGS: asserts Command: gotestsum --no-color --junitfile-hide-skipped-tests -f standard-quiet -- -test.run TestGoTest_Helper_WithPanic .
  | 2025/09/26 04:35:17 exec: gotestsum --no-color --junitfile-hide-skipped-tests -f standard-quiet -- -test.run TestGoTest_Helper_WithPanic .
  | exec: gotestsum --no-color --junitfile-hide-skipped-tests -f standard-quiet -- -test.run TestGoTest_Helper_WithPanic .
  | gotest_test.go:120: GoTest output mismatch:
  | want:
  | (?sm:
  | === FAIL: dev-tools/mage TestGoTest_Helper_WithPanic.*
  | panic: Kaputt. \[recovered\].*
  | panic: Kaputt.*
  | )
  |  
  | got:
  | FAIL	github.com/elastic/elastic-agent/dev-tools/mage	0.021s
  |  
  | === Failed
  | === FAIL: dev-tools/mage TestGoTest_Helper_WithPanic (0.00s)
  | panic: Kaputt. [recovered, repanicked]
  |  
  | goroutine 21 [running]:
  | testing.tRunner.func1.2({0xcd39e0, 0xf923f0})
  | /opt/buildkite-agent/.asdf/installs/golang/1.25.1/go/src/testing/testing.go:1872 +0x237
  | testing.tRunner.func1()
  | /opt/buildkite-agent/.asdf/installs/golang/1.25.1/go/src/testing/testing.go:1875 +0x35b
  | panic({0xcd39e0?, 0xf923f0?})
  | /opt/buildkite-agent/.asdf/installs/golang/1.25.1/go/src/runtime/panic.go:783 +0x132
  | github.com/elastic/elastic-agent/dev-tools/mage.TestGoTest_Helper_WithPanic(0xc000103880?)
  | /opt/buildkite-agent/builds/bk-agent-prod-gcp-1758859361500881345/elastic/elastic-agent/dev-tools/mage/gotest_test.go:329 +0x30
  | testing.tRunner(0xc000103880, 0xea4750)
  | /opt/buildkite-agent/.asdf/installs/golang/1.25.1/go/src/testing/testing.go:1934 +0xea
  | created by testing.(*T).Run in goroutine 1
  | /opt/buildkite-agent/.asdf/installs/golang/1.25.1/go/src/testing/testing.go:1997 +0x465
  |  
  | DONE 1 tests, 1 failure in 0.022s
  |  
  | === FAIL: dev-tools/mage TestGoTest_CaptureOutput (26.02s)

Turns out this is a change in behavior in Go 1.25: https://tip.golang.org/doc/go1.25#change-to-unhandled-panic-output. Addressed in 46cc036.

magefile.go

pchila · 2025-09-29T06:06:22Z

Looking at the latest build I see a couple of strange things (maybe some of those were already there and didn't notice until now)

windows 2016 unit tests have some failures which seem to be related to keeping files open/locked during cleanups
for example https://buildkite.com/elastic/elastic-agent/builds/27653#019988ea-47f4-49b3-8bfc-0710be9ad7ee/1293-1296
Locking/keeping files open seem to appear a lot also in Windows Integration tests, for example there are a few failures to remove agent executable in a row:
https://buildkite.com/elastic/elastic-agent/builds/27653#019988ea-f1b2-4aea-86d9-94c432db7258/1025-1918
https://buildkite.com/elastic/elastic-agent/builds/27653#019988ea-f1b2-4aea-86d9-94c432db7258/1025-1965
https://buildkite.com/elastic/elastic-agent/builds/27653#019988ea-f1b2-4aea-86d9-94c432db7258/1025-2042
https://buildkite.com/elastic/elastic-agent/builds/27653#019988ea-f1b2-4aea-86d9-94c432db7258/1025-2094

ycombinator · 2025-09-30T01:36:16Z

Windows build steps are failing in CI on this PR. See a lot of Access is denied errors. 🤔

elastic-sonarqube · 2025-09-30T04:44:16Z

Quality Gate passed

Issues
0 New issues
0 Fixed issues
0 Accepted issues

Measures
0 Security Hotspots
No data about Coverage
0.0% Duplication on New Code

See analysis details on SonarQube

mergify · 2025-10-03T14:42:09Z

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b bump-golang-1.25.1 upstream/bump-golang-1.25.1
git merge upstream/main
git push upstream bump-golang-1.25.1

mergify · 2025-10-16T09:38:10Z

This pull request is now in conflicts. Could you fix it? 🙏
To fixup this pull request, you can check out it locally. See documentation: https://help.github.com/articles/checking-out-pull-requests-locally/

git fetch upstream
git checkout -b bump-golang-1.25.1 upstream/bump-golang-1.25.1
git merge upstream/main
git push upstream bump-golang-1.25.1

ycombinator · 2026-03-09T01:41:06Z

Windows builds are failing like so:

=== FAIL: internal/pkg/agent/application/upgrade TestWaitForWatcher/Timeout2:_state_doesn't_get_there_in_time (0.01s)
--
testing.go:1369: TempDir RemoveAll cleanup: unlinkat C:\Users\BUILDK~1\AppData\Local\Temp\TestWaitForWatcherTimeout2_state_doesnt_get_there_in_time3776368021: The directory is not empty.

ebeahan · 2026-03-09T18:52:53Z

Looking at most of the remaining CI failures, it's consistently Win 2025 and uninstall of Agent:

fixture_install.go:758: >> running binary with: [C:\Program Files\Elastic\Agent\elastic-agent.exe uninstall --force]
--
fixture_install.go:363:
Error Trace:	C:/buildkite-agent/builds/bk-agent-prod-gcp-1773077791216426239/elastic/elastic-agent/pkg/testing/fixture_install.go:363
C:/Users/Buildkite/.go/go-1.25.8/src/testing/testing.go:1308
C:/Users/Buildkite/.go/go-1.25.8/src/testing/testing.go:1572
C:/Users/Buildkite/.go/go-1.25.8/src/testing/testing.go:1928
C:/Users/Buildkite/.go/go-1.25.8/src/runtime/asm_amd64.s:1693
Error:      	Received unexpected error:
error running uninstall command: exit status 1
Test:       	TestLongRunningAgentForLeaks
Messages:   	uninstalling agent failed. Output: "\r[    ] Stopping service  [0s] \r                              \r\r[=== ] Successfully stopped service  [5s] \r                                          \r\r[=== ] Stopping upgrade watcher; none found  [5s] \r                                                  \r\r[==  ] Removing service  [5s] \r                                                  \r\r[==  ] Successfully uninstalled service  [5s] \r                                                  \r\r[==  ] Removing install directory  [5s] \r                                                  \r\r[   =] Failed to remove install directory  [1m5s] \r                                                  \r\r[   =] Failed to uninstall agent  [1m5s] Error uninstalling. Printing logs\n2026-03-09T18:15:31.439Z\tDEBUG\t[uninstall.state_migration]\tnot attempting to migrate from action store: state store already exists\n2026-03-09T18:15:36.832Z\tDEBUG\t[uninstall.state_migration]\tnot attempting to migrate from action store: state store already exists\n2026-03-09T18:15:36.849Z\tDEBUG\t[uninstall.composable]\tStarting controller for composable inputs\n2026-03-09T18:15:36.849Z\tDEBUG\t[uninstall.composable]\tStarted controller for composable inputs\n2026-03-09T18:15:36.849Z\tDEBUG\t[uninstall.composable]\tComputing new variable state for composable inputs\n2026-03-09T18:15:36.850Z\tDEBUG\t[uninstall.composable]\tStopping controller for composable inputs\n2026-03-09T18:15:36.850Z\tDEBUG\t[uninstall.composable]\tStopped controller for composable inputs\nError: error uninstalling agent: failed to remove installation directory (C:\\Program Files\\Elastic\\Agent): timed out while removing \"C:\\\\Program Files\\\\Elastic\\\\Agent\". Last error: unlinkat C:\\Program Files\\Elastic\\Agent\\data\\elastic-agent-9.4.0-SNAPSHOT-59c6e5\\elastic-agent.exe: Access is denied.\nFor help, please see our troubleshooting guide at https://www.elastic.co/docs/troubleshoot/ingest/fleet/common-problems\n"

Unclear at this time if this is still related to golang/go#77402.

ebeahan · 2026-03-09T21:42:35Z

Was able to reproduce on a Windows 2025 server instance.

swiatekm · 2026-03-10T18:38:20Z

We're now getting

2026-03-10T17:56:54.272Z	WARN	[uninstall]	RemovePath attempt 1 failed after 119ms: unlinkat C:\Program Files\Elastic\Agent-Development\data\elastic-agent-9.4.0-SNAPSHOT-03cd7d\elastic-agent.exe: Access is denied.
        	            	2026-03-10T17:56:54.309Z	WARN	[uninstall]	file is blocked: C:\Program Files\Elastic\Agent-Development\data\elastic-agent-9.4.0-SNAPSHOT-03cd7d\elastic-agent.exe; locking processes: Elastic Agent - single, unified way to add monitoring for logs, metrics, and other types of data to a host. (PID 4960)
        	            	2026-03-10T17:56:54.310Z	WARN	[uninstall]	removeBlockingExe failed: failed to dispose handle for "C:\\Program Files\\Elastic\\Agent-Development\\data\\elastic-agent-9.4.0-SNAPSHOT-03cd7d\\elastic-agent.exe": Access is denied.

https://buildkite.com/elastic/elastic-agent/builds/35651/steps/canvas?jid=019cd8be-000e-42e3-87d6-78274e9ad672&tab=output.

swiatekm · 2026-03-11T16:39:46Z

buildkite test this

swiatekm · 2026-03-11T16:52:03Z

I fixed the remaining issues stemming from the upgrade, albeit one of them is a revert to 1.24 behavior as we investigate alternatives:

bf6e8b9 uses the 1.24 implementation of os.RemoveAll. The 1.25 implementation interacts poorly with the way we delete the agent binary during uninstall. This is a hotfix to unblock the upgrade, we should find a more robust way to do it.
83ca6d4 ensures we stop the fsnotify watcher for the upgrade marker file before exiting. This can make test cleanup fail on Windows.

swiatekm · 2026-03-11T16:53:07Z

@cmacknz @michel-laterman can you review the above changes? I'd like to get more eyes on this before we merge.

michel-laterman

Thanks for figuring this out!

internal/pkg/agent/application/upgrade/marker_watcher.go

internal/pkg/agent/install/uninstall.go

michel-laterman · 2026-03-11T17:24:22Z

internal/pkg/agent/install/uninstall.go

+// Windows use NtCreateFile with DELETE access — these are stricter about file
+// state and fail on files that have been ADS-renamed. The simple path-based
+// approach using os.Remove works correctly with the ADS rename trick that
+// RemovePath uses to delete running executables on Windows.


Overall, what's the plan here, are we going to address the changes in file permissions or do something else? Do we have a follow-up issue?

We don't have an issue, and I'm not sure what the actual root cause is. Just that the new RemoveAll implementation doesn't like the data stream renames and naive attempts to fix it don't really help. The errors aren't very informative either, you just get Access Denied.

I will file an issue describing the problem and what I tried to fix it. For now, I want to unblock this upgrade because it blocks a bunch of other updates.

Yes at this point, let's fall back to the implementation we know works and work out how to get rid of this separately. This is blocking the collector and contrib dependency updates for example, in addition to use not getting CVE fixes in Go anymore.

Co-authored-by: Michel Laterman <82832767+michel-laterman@users.noreply.github.com>

internal/pkg/agent/install/uninstall.go

cmacknz · 2026-03-11T18:27:57Z

magefile.go

+	// We also set GODEBUG=tlsmlkem=0 to disable the X25519MLKEM768 TLS key
+	// exchange mechanism; without this setting and with the GODEBUG=fips140=only
+	// setting, we get errors in tests like so:
+	// Failed to connect: crypto/ecdh: use of X25519 is not allowed in FIPS 140-only mode


Where are we using this? The FIPS mode is supposed to default you to only using FIPS compatible parts of TLS without us having to do anything. Are we explicitly testing a non-FIPS mechanism somewhere?

That, I don't really know, Shaunak is the FIPS expert and he handled that part. I say we merge as-is and he can revisit this after he's back.

=== FAIL: internal/pkg/remote TestClientWithCertificate/fips_invalid_key_fips140only (0.00s) client_fips_test.go:186: Error Trace: /Users/cmackenzie/go/src/github.com/elastic/elastic-agent/internal/pkg/remote/client_fips_test.go:186 Error: "all hosts failed: requester 0/1 to host https://127.0.0.1:64269/ errored: Get \"https://127.0.0.1:64269/echo-hello?\": crypto/ecdh: use of X25519 is not allowed in FIPS 140-only mode" does not contain "use of keys smaller than 2048 bits is not allowed in FIPS 140-only mode" Test: TestClientWithCertificate/fips_invalid_key_fips140only === FAIL: internal/pkg/remote TestClientWithCertificate/fips_valid_key_fips140only (0.00s) client_fips_test.go:181: Error Trace: /Users/cmackenzie/go/src/github.com/elastic/elastic-agent/internal/pkg/remote/client_fips_test.go:181 Error: Expected value not to be nil. Test: TestClientWithCertificate/fips_valid_key_fips140only === FAIL: internal/pkg/remote TestClientWithCertificate (0.00s)

We are using this in a bunch of places, seeing it fail in fips specific tests is concerning. This particular test has a pre-generated certificate that appears to no longer be FIPS compliant.

It also comes up in the FakeInputSuite a lot for the gRPC connection which is more concerning.

blakerouse

This overall looks good. I am interested in the answers to @cmacknz questions as well. Holding off on approval until I read those.

internal/pkg/agent/install/uninstall.go

This reverts commit 88ece11

elasticmachine · 2026-03-12T11:20:34Z

⏳ Build in-progress, with failures

Buildkite Build
Commit: 743a105

Failed CI Steps

History

💔 Build #35723 failed 3c6a49d
💔 Build #35721 failed 2316448
💔 Build #35714 failed 2da3431
💔 Build #35653 failed 684430e
💔 Build #35648 failed c3a51f5

cc @ycombinator

ycombinator requested review from a team as code owners September 25, 2025 17:46

ycombinator requested review from pchila and pkoutsovasilis September 25, 2025 17:46

ycombinator added Team:Elastic-Agent-Control-Plane Label for the Agent Control Plane team backport-active-all Automated backport with mergify to all the active branches labels Sep 25, 2025

mergify bot assigned ycombinator Sep 25, 2025

pkoutsovasilis reviewed Sep 25, 2025

View reviewed changes

dev-tools/mage/otel/deps_test.go Outdated Show resolved Hide resolved

This was referenced Sep 26, 2025

Bump Go version to 1.25.8 elastic/beats#46793

Merged

Bump Go version to 1.25.1 elastic/fleet-server#5562

Merged

ycombinator force-pushed the bump-golang-1.25.1 branch from d8c500d to 0b69f33 Compare September 26, 2025 10:20

pchila reviewed Sep 26, 2025

View reviewed changes

magefile.go Outdated Show resolved Hide resolved

ycombinator force-pushed the bump-golang-1.25.1 branch from 4db5a4a to 1ceaae8 Compare September 30, 2025 01:36

ycombinator force-pushed the bump-golang-1.25.1 branch 2 times, most recently from 52d2f67 to b6b1a81 Compare October 1, 2025 14:36

ycombinator force-pushed the bump-golang-1.25.1 branch from b6b1a81 to 92a9716 Compare October 7, 2025 00:16

pchila mentioned this pull request Oct 9, 2025

[Automation] Bump Golang version to 1.24.9 #10422

Merged

ycombinator changed the title ~~Bump Go version to 1.25.1~~ Bump Go version to 1.25.2 Oct 13, 2025

ycombinator force-pushed the bump-golang-1.25.1 branch 2 times, most recently from a41a670 to eaf3ce7 Compare October 15, 2025 00:21

swiatekm mentioned this pull request Mar 10, 2026

Fix file permission issues when uninstalling agent on Windows #13107

Draft

5 tasks

swiatekm force-pushed the bump-golang-1.25.1 branch from 684430e to 2da3431 Compare March 11, 2026 13:04

lahsivjar mentioned this pull request Mar 11, 2026

[connector/elasticapm] Add data_stream.namespace attribute as resource attribute for aggregated metrics elastic/opentelemetry-collector-components#1060

Open

5 tasks

swiatekm requested a review from michel-laterman March 11, 2026 16:01

swiatekm added 3 commits March 11, 2026 17:03

Merge branch 'main' into bump-golang-1.25.1

87dcd07

Use Go 1.24's RemoveAll in uninstall

bf6e8b9

Wait for fsnotify watcher to be released

83ca6d4

swiatekm force-pushed the bump-golang-1.25.1 branch from 2da3431 to 83ca6d4 Compare March 11, 2026 16:12

swiatekm requested a review from cmacknz March 11, 2026 16:53

michel-laterman previously approved these changes Mar 11, 2026

View reviewed changes

internal/pkg/agent/application/upgrade/marker_watcher.go Outdated Show resolved Hide resolved

internal/pkg/agent/install/uninstall.go Show resolved Hide resolved

michel-laterman reviewed Mar 11, 2026

View reviewed changes

Update internal/pkg/agent/application/upgrade/marker_watcher.go

2316448

Co-authored-by: Michel Laterman <82832767+michel-laterman@users.noreply.github.com>

swiatekm dismissed michel-laterman’s stale review via 2316448 March 11, 2026 17:34

cmacknz reviewed Mar 11, 2026

View reviewed changes

internal/pkg/agent/install/uninstall.go Show resolved Hide resolved

cmacknz reviewed Mar 11, 2026

View reviewed changes

blakerouse reviewed Mar 11, 2026

View reviewed changes

internal/pkg/agent/install/uninstall.go Show resolved Hide resolved

swiatekm added 3 commits March 11, 2026 19:42

Fix function signature in MarkerFileWatcher

a114241

Use the exact removaAll implementation from Go 1.24

88ece11

Add link to the new RemoveAll implementation

3c6a49d

cmacknz mentioned this pull request Mar 11, 2026

chore: update OTel Collector libraries to v0.147.0/v1.53.0 elastic/beats#49348

Open

Revert "Use the exact removaAll implementation from Go 1.24"

743a105

This reverts commit 88ece11

mergify bot mentioned this pull request Mar 12, 2026

Fix/bump golang 1.25.1 #13106

Draft

8 tasks

Conversation

ycombinator commented Sep 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

elasticmachine commented Sep 25, 2025

Uh oh!

ycombinator commented Sep 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

Uh oh!

ycombinator commented Sep 25, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ycombinator commented Sep 26, 2025

Uh oh!

ycombinator commented Sep 26, 2025

Uh oh!

Uh oh!

pchila commented Sep 29, 2025 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Uh oh!

ycombinator commented Sep 30, 2025

Uh oh!

elastic-sonarqube bot commented Sep 30, 2025

Quality Gate passed

Uh oh!

mergify bot commented Oct 3, 2025

Uh oh!

mergify bot commented Oct 16, 2025

Uh oh!

ycombinator commented Mar 9, 2026

Uh oh!

ebeahan commented Mar 9, 2026

Uh oh!

ebeahan commented Mar 9, 2026

Uh oh!

swiatekm commented Mar 10, 2026

Uh oh!

swiatekm commented Mar 11, 2026

Uh oh!

swiatekm commented Mar 11, 2026

Uh oh!

swiatekm commented Mar 11, 2026

Uh oh!

michel-laterman left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

Uh oh!

michel-laterman Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

swiatekm Mar 11, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

Choose a reason for hiding this comment

Uh oh!

cmacknz Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

Uh oh!

cmacknz Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

swiatekm Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

cmacknz Mar 11, 2026

Choose a reason for hiding this comment

Uh oh!

blakerouse left a comment

Choose a reason for hiding this comment

Uh oh!

Uh oh!

elasticmachine commented Mar 12, 2026 • edited Loading Uh oh! There was an error while loading. Please reload this page.

Uh oh!

⏳ Build in-progress, with failures

Failed CI Steps

History

Uh oh!

Reviewers

ycombinator commented Sep 25, 2025 •

edited

Loading

ycombinator commented Sep 25, 2025 •

edited

Loading

ycombinator commented Sep 25, 2025 •

edited

Loading

pchila commented Sep 29, 2025 •

edited

Loading

swiatekm Mar 11, 2026 •

edited

Loading

elasticmachine commented Mar 12, 2026 •

edited

Loading