chore(pulsar): bump base image to 4.x, replacing the wait for log strategy with wait for listening port (deterministic)

[mdelapenya]

• chore(deps): bump Pulsar image to 4.x
• fix(pulsar): change wait strategy, from log to listening port

What does this PR do?

• Bumps the default Pulsar image from 2.10.2 to 4.0.9 across source, tests, examples, and docs
• Replaces the wait.ForLog strategy with wait.ForListeningPort for a more deterministic readiness check

Why is it important?

Pulsar 2.10.2 bundles an older JDK that crashes with a NullPointerException on cgroups v2 hosts (including modern GitHub Actions runners), preventing the container from starting. Upgrading to 4.0.9 resolves this incompatibility.

The log-based wait strategy was also fragile since the log message could change between versions. Waiting for the listening port is more reliable.

Related issues

• Closes Pulsar module: container fails to start due to cgroups v2 incompatibility #3570

[netlify]

✅ Deploy Preview for testcontainers-go ready!

Name	Link
🔨 Latest commit	47bf7b0
🔍 Latest deploy log	https://app.netlify.com/projects/testcontainers-go/deploys/69ac2b17a4c9110008032b5c
😎 Deploy Preview	https://deploy-preview-3573--testcontainers-go.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[coderabbitai]

Summary by CodeRabbit

• Documentation

  • Updated Pulsar documentation and examples to version 4.0.9

• Tests

  • Updated test configurations to use Pulsar 4.0.9

• Improvements

  • Updated container readiness detection to use port listening instead of log matching

Walkthrough

The Pulsar module is updated to use container image version 4.0.9 instead of 2.10.2 across documentation, examples, and tests. The module's waiting strategy is changed from checking log messages to listening on the Pulsar port.

Changes

Cohort / File(s)	Summary
Image Version Updates docs/modules/pulsar.md, modules/pulsar/examples_test.go, modules/pulsar/pulsar_test.go	Updated Pulsar container image from version 2.10.2 to 4.0.9 in documentation example, test examples, and test suites.
Waiting Strategy & Runtime Update modules/pulsar/pulsar.go	Updated container image to 4.0.9 and replaced wait strategy from log message listening to port listening in defaultWaitStrategies.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• #3426: Modifies wait-strategy setup and touching RunContainer/Run in the pulsar module similarly.

Suggested labels

chore

Poem

🐰 A hop to version four-point-oh,
Pulsar's port now sets the flow,
No more logs to chase and scan,
Just listening—that's the plan!
Whiskers twitch, the upgrade's set, ✨

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Docstring Coverage	⚠️ Warning	Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%.	Write docstrings for the functions missing them to satisfy the coverage threshold.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title accurately summarizes the main changes: bumping Pulsar base image to 4.x and replacing the wait strategy from log to listening port.
Description check	✅ Passed	The description provides clear context about what the PR does, why it's important, and references the related issue, all directly aligned with the changeset.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[coderabbitai]

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)

modules/pulsar/pulsar.go (1)

24-31: ⚠️ Potential issue | 🟠 Major

Don't replace broker readiness with a socket-open check.

wait.ForListeningPort(defaultPulsarPort) only proves that 6650/tcp is accepting TCP connections. It does not prove the Pulsar broker is ready for client operations, so Run can return while producers/consumers still race the broker startup path. Please keep a broker-level readiness signal here as well (the previous log wait, or another application-level probe) and use the port check as an additional deterministic guard instead of a replacement.

Based on learnings: In testcontainers-go ArangoDB module, the wait strategy combines port listening check with HTTP readiness check using wait.ForAll - both strategies are required and complementary, not redundant.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@modules/pulsar/pulsar.go` around lines 24 - 31, The current
defaultWaitStrategies replaced an application-level readiness probe with only
wait.ForListeningPort(defaultPulsarPort); restore an application-level broker
readiness check alongside the socket check by composing the HTTP admin probe
(the existing
wait.ForHTTP("/admin/v2/clusters").WithPort(defaultPulsarAdminPort).WithResponseMatcher(...))
and the port probe using wait.ForAll so both must succeed; update the
defaultWaitStrategies slice to use wait.ForAll(...) containing the HTTP
readiness strategy and wait.ForListeningPort(defaultPulsarPort) (keep the
existing response matcher and port settings) so Run only returns after both
application-level and TCP readiness are satisfied.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@modules/pulsar/pulsar.go`:
- Around line 24-31: The current defaultWaitStrategies replaced an
application-level readiness probe with only
wait.ForListeningPort(defaultPulsarPort); restore an application-level broker
readiness check alongside the socket check by composing the HTTP admin probe
(the existing
wait.ForHTTP("/admin/v2/clusters").WithPort(defaultPulsarAdminPort).WithResponseMatcher(...))
and the port probe using wait.ForAll so both must succeed; update the
defaultWaitStrategies slice to use wait.ForAll(...) containing the HTTP
readiness strategy and wait.ForListeningPort(defaultPulsarPort) (keep the
existing response matcher and port settings) so Run only returns after both
application-level and TCP readiness are satisfied.

---

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: f2548de0-8adf-44d3-8e79-d44771fda3da

📥 Commits

Reviewing files that changed from the base of the PR and between 7cb85f8 and 47bf7b0.

📒 Files selected for processing (4)

• docs/modules/pulsar.md
• modules/pulsar/examples_test.go
• modules/pulsar/pulsar.go
• modules/pulsar/pulsar_test.go