chore: fix bedrock transport tests

[TejasGhatte]

Summary

Replaces nil logger arguments with a noopLogger{} instance in Bedrock transport tests to ensure tests use a valid logger implementation rather than a nil value.

Changes

• Replaced nil with noopLogger{} when calling NewBedrockProvider across all Bedrock transport tests to provide a proper no-op logger, avoiding potential nil pointer dereferences during test execution.

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

go test ./core/providers/bedrock/...

All Bedrock transport tests should pass without nil pointer panics or logger-related errors.

Screenshots/Recordings

N/A

Breaking changes

• Yes
• No

Related issues

N/A

Security considerations

No security implications. This is a test-only change that swaps a nil logger for a no-op implementation.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 42fcfcfd-733d-448d-971d-b485b3c3c613

📥 Commits

Reviewing files that changed from the base of the PR and between 584816b and 6a4a944.

📒 Files selected for processing (1)

• core/providers/bedrock/transport_test.go

---

📝 Walkthrough

Summary by CodeRabbit

Release Notes

• Tests
  • Updated Bedrock transport configuration test infrastructure.

---

Note: This release contains internal test improvements with no user-facing changes to functionality.

Walkthrough

Update eight Bedrock transport configuration tests to initialize NewBedrockProvider with noopLogger{} instead of nil.

Changes

Bedrock Transport Test Logger Updates

Layer / File(s)	Summary
Transport test logger initialization core/providers/bedrock/transport_test.go	Eight transport test cases for HTTP/2 config, max connections, TLS configuration, and HTTP/2 enforcement now pass a concrete noopLogger{} instance instead of nil to NewBedrockProvider.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Suggested reviewers

• akshaydeo
• danpiths

Poem

🐰 With logger's eyes now open bright,
The tests see through the transport light,
No nil shall pass—the noop's in place,
A logger true in every test's embrace!

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

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

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'chore: fix bedrock transport tests' directly and clearly summarizes the main change - fixing Bedrock transport tests by replacing nil loggers with noopLogger instances.
Description check	✅ Passed	The PR description covers all critical sections of the template including Summary, Changes, Type of change, Affected areas, How to test, Breaking changes, and Security considerations with appropriate detail and completeness.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

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

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 05-25-chore_fix_bedrock_transport_tests

Warning

There were issues while running some tools. Please review the errors and either fix the tool's configuration or disable the tool if it's a critical failure.

🔧 golangci-lint (2.12.2)

level=error msg="[linters_context] typechecking error: pattern ./...: directory prefix . does not contain main module or its selected dependencies"

---

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

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

tejas ghatte seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[TejasGhatte]

• chore: fix bedrock transport tests #3735 👈 (View in Graphite)
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Confidence Score: 5/5

Test-only change that swaps nil for a well-defined no-op logger; no production code is touched.

Every changed call site now uses the noopLogger{} already defined in the same file, which fully satisfies the schemas.Logger interface. The fix is consistent with the rest of the test suite and carries no risk of behavioral change outside of tests.

No files require special attention.

Important Files Changed

Filename	Overview
core/providers/bedrock/transport_test.go	Replaces 8 nil logger arguments with noopLogger{} in Bedrock transport tests; noopLogger is already defined in the same file and fully implements schemas.Logger.

_{Reviews (1): Last reviewed commit: "chore: fix bedrock transport tests" | Re-trigger Greptile}

[akshaydeo]

Merge activity

• May 25, 4:34 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• May 25, 4:35 PM UTC: @akshaydeo merged this pull request with Graphite.