gofr · Issues· 125 open

Decide the coverage threshold gate once the post-merge figure is published (follow-up to #3940)

gcp traces submodule: drop the `replace gofr.dev` once a release contains pkg/gofr/traces/exporters

tracing: a failed or unsupported TRACE_EXPORTER installs a BatchSpanProcessor over a nil exporter and silently drops every span

traces: no IAM-authenticated exporter for Google Cloud — OTLP trace exporter is pinned to plaintext, unlike metrics

Raise submodule test coverage: 13 files at 0% with generated mocks already in place

WebSocket handler context is self-referential, causing an unrecoverable stack overflow

Serve detailed health map on the metrics port (follow-up to #3802)

Dgraph: Client.Mutate never commits, so a mutation without CommitNow is silently dropped

Add response time unit in json logs

Data race on the shared duration in Google Pub/Sub Subscribe

Add span links in MQTT

AddStaticFiles with a trailing slash in the endpoint registers a silently dead route

Graceful stop establishes no happens-before edge: lost server shutdown (nil-check-as-started) + cron Stop() without job join

metrics/gcp: docs say roles/monitoring.metricWriter but the endpoint is telemetry.googleapis.com, whose reference mandates roles/telemetry.writer

redis sentinel support