Skip to content

Fix: use TelemetryConfig in init_tracer to resolve type mismatch#693

Open
smiletech092-code wants to merge 1 commit into
kellymusk:masterfrom
smiletech092-code:fix/tracer-telemetry-config
Open

Fix: use TelemetryConfig in init_tracer to resolve type mismatch#693
smiletech092-code wants to merge 1 commit into
kellymusk:masterfrom
smiletech092-code:fix/tracer-telemetry-config

Conversation

@smiletech092-code

@smiletech092-code smiletech092-code commented Jun 29, 2026

Copy link
Copy Markdown

closes #541
closes #542
closes #543
closes #544

Problem
src/main.rs:189 reports expected &TracingConfig, found &TelemetryConfig during init_tracer call.

Why this matters
This currently blocks clean compilation and safe deployment workflows.

Proposed fix
Align tracer init signature and config type usage so startup compiles with telemetry enabled.

Acceptance criteria
Project compiles for the relevant target/feature set.
Startup/worker path behaves as expected under default env settings.
Add/adjust tests where practical.

Align init_tracer to accept TelemetryConfig from AppConfig and remove the duplicate local TracingConfig type. This fixes the compile-time type mismatch when telemetry is enabled.

Changes:

  • src/telemetry/tracer.rs: import TelemetryConfig from crate::config and update init_tracer signature.

No behavioral change beyond using the centralized config type.

@drips-wave

drips-wave Bot commented Jun 29, 2026

Copy link
Copy Markdown

@smiletech092-code Great news! 🎉 Based on an automated assessment of this PR, the linked Wave issue(s) no longer count against your application limits.

You can now already apply to more issues while waiting for a review of this PR. Keep up the great work! 🚀

Learn more about application limits

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

1 participant