starred/fake-gcs-server

Fork 0

mirror of https://github.com/fsouza/fake-gcs-server.git synced 2026-04-26 06:05:54 +03:00

[GH-ISSUE #1531] Panic runtime error on 1.47.8 #205

New issue

Closed

opened 2026-03-03 12:09:07 +03:00 by kerem · 7 comments

kerem commented

2026-03-03 12:09:07 +03:00

Owner

Originally created by @nordnet-robkui on GitHub (Mar 12, 2024).
Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/1531

We're using the fake-gcs-server container for tests in our application. We're getting the error message below when using the latest version 1.47.8. Running these tests locally using Mac M1 works fine with 1.47.8, but not on Linux (debian:12.5-slim). Downgrading to 1.47.7 makes it work fine everywhere.

Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (<IP> ports: [<PORT>] should be listening)
	at org.testcontainers.containers.wait.strategy.HostPortWaitStrategy.waitUntilReady(HostPortWaitStrategy.java:112)
	at org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52)
	at org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:912)
	at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:503)
	... 130 common frames omitted
ERROR Log output from the failed container:
panic: runtime error: slice bounds out of range [125:64]

goroutine 1 [running]:
os.(*File).ReadAt(0xa8980e8, {0xa8a2e03, 0x40, 0x40}, 0x0)
	/usr/local/go/src/os/file.go:142 +0x1f3
google.golang.org/protobuf/internal/detrand.binaryHash()
	/go/pkg/mod/google.golang.org/protobuf@v1.32.0/internal/detrand/rand.go:63 +0x2c2
google.golang.org/protobuf/internal/detrand.init()
	/go/pkg/mod/google.golang.org/protobuf@v1.32.0/internal/detrand/rand.go:38 +0x1a

Originally created by @nordnet-robkui on GitHub (Mar 12, 2024). Original GitHub issue: https://github.com/fsouza/fake-gcs-server/issues/1531 We're using the fake-gcs-server container for tests in our application. We're getting the error message below when using the latest version 1.47.8. Running these tests locally using Mac M1 works fine with 1.47.8, but not on Linux (debian:12.5-slim). Downgrading to 1.47.7 makes it work fine everywhere. ``` Caused by: org.testcontainers.containers.ContainerLaunchException: Timed out waiting for container port to open (<IP> ports: [<PORT>] should be listening) at org.testcontainers.containers.wait.strategy.HostPortWaitStrategy.waitUntilReady(HostPortWaitStrategy.java:112) at org.testcontainers.containers.wait.strategy.AbstractWaitStrategy.waitUntilReady(AbstractWaitStrategy.java:52) at org.testcontainers.containers.GenericContainer.waitUntilContainerStarted(GenericContainer.java:912) at org.testcontainers.containers.GenericContainer.tryStart(GenericContainer.java:503) ... 130 common frames omitted ERROR Log output from the failed container: panic: runtime error: slice bounds out of range [125:64] goroutine 1 [running]: os.(*File).ReadAt(0xa8980e8, {0xa8a2e03, 0x40, 0x40}, 0x0) /usr/local/go/src/os/file.go:142 +0x1f3 google.golang.org/protobuf/internal/detrand.binaryHash() /go/pkg/mod/google.golang.org/protobuf@v1.32.0/internal/detrand/rand.go:63 +0x2c2 google.golang.org/protobuf/internal/detrand.init() /go/pkg/mod/google.golang.org/protobuf@v1.32.0/internal/detrand/rand.go:38 +0x1a ```

kerem closed this issue

2026-03-03 12:09:08 +03:00

kerem commented

2026-03-03 12:09:09 +03:00

Author

Owner

@fsouza commented on GitHub (Mar 13, 2024):

Hmm that's interesting, I don't see anything in 1.47.8 that could've caused this (unless it's caused by a dependency upgrade).

Do you have more logs? The stacktrace is cut-off there. Alternatively, can you provide instructions for reproducing the issue? Thanks!

@fsouza commented on GitHub (Mar 13, 2024): Hmm that's interesting, I don't see anything in 1.47.8 that could've caused this (unless it's caused by a dependency upgrade). Do you have more logs? The stacktrace is cut-off there. Alternatively, can you provide instructions for reproducing the issue? Thanks!

kerem commented

2026-03-03 12:09:09 +03:00

Author

Owner

@nordnet-robkui commented on GitHub (Mar 14, 2024):

Thanks for responding. I don't have anymore logs right now, but I'm aiming to create a reproducible stripped example. I just need to find some time at work. I'll get back to you when I got more data/logs.

The interesting part is that it worked fine last week on our Linux build server 😅 So, in essence it worked for some time using the new version, but then all of a sudden it didn't.

@nordnet-robkui commented on GitHub (Mar 14, 2024): Thanks for responding. I don't have anymore logs right now, but I'm aiming to create a reproducible stripped example. I just need to find some time at work. I'll get back to you when I got more data/logs. The interesting part is that it worked fine last week on our Linux build server 😅 So, in essence it worked for some time using the new version, but then all of a sudden it didn't.

kerem commented

2026-03-03 12:09:09 +03:00

Author

Owner

@glebbash commented on GitHub (Mar 20, 2024):

We also see this problem, 1.47.8 works fine on CI but we get test timeouts locally on both Linux and MacOS. 1.47.7 has no such issues.

@glebbash commented on GitHub (Mar 20, 2024): We also see this problem, 1.47.8 works fine on CI but we get test timeouts locally on both Linux and MacOS. 1.47.7 has no such issues.

kerem commented

2026-03-03 12:09:09 +03:00

Author

Owner

@fsouza commented on GitHub (Mar 23, 2024):

Given that between 1.47.7 and 1.47.8 the only difference was that we bumped some dependencies, can you give that another shot now that 1.48.0 is out?

@fsouza commented on GitHub (Mar 23, 2024): Given that between 1.47.7 and 1.47.8 the only difference was that we bumped some dependencies, can you give that another shot now that 1.48.0 is out?

kerem commented

2026-03-03 12:09:09 +03:00

Author

Owner

@nordnet-robkui commented on GitHub (Mar 25, 2024):

I just tried 1.48.0 and it seems to work fine on my small example 👍 I'll try it out on all our tests.

@nordnet-robkui commented on GitHub (Mar 25, 2024): I just tried 1.48.0 and it seems to work fine on my small example 👍 I'll try it out on all our tests.

kerem commented

2026-03-03 12:09:09 +03:00

Author

Owner

@glebbash commented on GitHub (Mar 25, 2024):

Same here, 1.48 fixed the issue 🎇

@glebbash commented on GitHub (Mar 25, 2024): Same here, 1.48 fixed the issue 🎇

kerem commented

2026-03-03 12:09:09 +03:00

Author

Owner

@nordnet-robkui commented on GitHub (Mar 25, 2024):