examples/features/opentelemetry: Include OpenTelemetry tracing plugin usage and output in example server and client #8056

janardhanvissa · 2025-01-30T16:44:57Z

RELEASE NOTE:

examples/features/opentelemetry: included OpenTelemetry tracing plugin usage and output in example server and client.

codecov · 2025-01-30T16:51:45Z

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 82.25%. Comparing base (a510cf5) to head (06f4309).
Report is 15 commits behind head on master.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #8056      +/-   ##
==========================================
+ Coverage   82.16%   82.25%   +0.09%     
==========================================
  Files         387      392       +5     
  Lines       38941    39140     +199     
==========================================
+ Hits        31997    32196     +199     
+ Misses       5619     5612       -7     
- Partials     1325     1332       +7

see 43 files with indirect coverage changes

🚀 New features to boost your workflow:

❄ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

purnesh42H · 2025-02-05T19:23:27Z

examples/features/opentelemetry/client/main.go

@@ -33,37 +33,90 @@ import (
 	"google.golang.org/grpc/stats/opentelemetry"

 	"github.com/prometheus/client_golang/prometheus/promhttp"
+	"go.opentelemetry.io/contrib/instrumentation/google.golang.org/grpc/otelgrpc"


why do we need otelgrpc?

this will automatically instrument grpc client calls with otel tracing and metrics.

purnesh42H · 2025-02-05T19:25:11Z

examples/features/opentelemetry/client/main.go

+		log.Fatalf("Error setting up tracing: %v", err)
+	}
+	defer func() { _ = tp.Shutdown(context.Background()) }()
+
 	do := opentelemetry.DialOption(opentelemetry.Options{MetricsOptions: opentelemetry.MetricsOptions{MeterProvider: provider}})


how wll the tracing work? You are not adding the trace options. Please see this POC code https://github.com/purnesh42H/grpc-go/pull/6/files#diff-719b01b6393a1e9b5a7d2a3908effb85dd904e5e2799f2ace99fab70d606f810R68

purnesh42H · 2025-02-05T19:27:15Z

examples/features/opentelemetry/client/main.go


 	// Make an RPC every second. This should trigger telemetry to be emitted from
 	// the client and the server.
 	for {
-		r, err := c.UnaryEcho(ctx, &echo.EchoRequest{Message: "this is examples/opentelemetry"})
+		reqCtx, cancel := context.WithTimeout(ctx, time.Second)
+		_, span := tracer.Start(reqCtx, "UnaryEchoClientCall")


we are showing the example of grpc tracing plugin. We don't need to start the span here outside. The example needs to show that once you add the trace options to client, grpc will create the required spans and traces and emit into exporter.

purnesh42H · 2025-02-05T19:27:53Z

examples/features/opentelemetry/server/main.go

+	if err != nil {
+		log.Fatalf("Error setting up tracing: %v", err)
+	}
+	defer func() { _ = tp.Shutdown(context.Background()) }()

 	so := opentelemetry.ServerOption(opentelemetry.Options{MetricsOptions: opentelemetry.MetricsOptions{MeterProvider: provider}})


same comments as client. Please do similar to whats done here https://github.com/purnesh42H/grpc-go/pull/6/files#diff-719b01b6393a1e9b5a7d2a3908effb85dd904e5e2799f2ace99fab70d606f810R68

purnesh42H

@janardhanvissa please use any of the trace exporter from here https://opentelemetry.io/docs/languages/go/exporters/. May be otlptracehttp or stdouttrace are good candidates

Also, please refer to https://opentelemetry.io/docs/languages/go/getting-started/ for writing otel trace exporting parts in client and server. We should try to avoid as much custom code as possible here to make it easy and fast for users to pick up.

purnesh42H · 2025-02-19T04:41:43Z

examples/features/opentelemetry/client/main.go

 	"google.golang.org/grpc"
 	"google.golang.org/grpc/credentials/insecure"
 	"google.golang.org/grpc/examples/features/proto/echo"
+	experimental "google.golang.org/grpc/experimental/opentelemetry"


we can name it as oteltracing and "google.golang.org/grpc/stats/opentelemetry" as otelmetrics

examples/features/opentelemetry/client/main.go

purnesh42H · 2025-02-19T04:45:01Z

examples/features/opentelemetry/client/main.go

+	"go.opentelemetry.io/otel/propagation"
+	"go.opentelemetry.io/otel/sdk/metric"
+	"go.opentelemetry.io/otel/sdk/trace"
+	"go.opentelemetry.io/otel/sdk/trace/tracetest"


we shouldn't be using tracetest for example. Can you check other exporters that otel provides? For example, here in https://opentelemetry.io/docs/languages/go/getting-started/, they are using stdouttrace. We can use the same.

using otlptracer

purnesh42H · 2025-02-19T04:46:33Z

examples/features/opentelemetry/client/main.go

@@ -48,26 +51,49 @@ func main() {
 		log.Fatalf("Failed to start prometheus exporter: %v", err)
 	}
 	provider := metric.NewMeterProvider(metric.WithReader(exporter))
-	go http.ListenAndServe(*prometheusEndpoint, promhttp.Handler())
+
+	spanExporter := tracetest.NewInMemoryExporter()


As above, we shouldn't be using tracetest for examples. They are meant for testing only.

purnesh42H · 2025-02-19T04:48:16Z

examples/features/opentelemetry/client/main.go

+	spanExporter := tracetest.NewInMemoryExporter()
+	spanProcessor := trace.NewSimpleSpanProcessor(spanExporter)
+	tracerProvider := trace.NewTracerProvider(trace.WithSpanProcessor(spanProcessor))
+	textMapPropagator := propagation.NewCompositeTextMapPropagator(opentelemetry.GRPCTraceBinPropagator{})


For main example, we should be using only W3CContextPropagator. We will have separate example for opencensus migration, where we can showcase the GRPCTraceBinPropagator

purnesh42H · 2025-02-19T05:42:00Z

examples/features/opentelemetry/server/main.go

 	"go.opentelemetry.io/otel/sdk/metric"
+	"go.opentelemetry.io/otel/sdk/trace"
+	"go.opentelemetry.io/otel/sdk/trace/tracetest"


same comment as client about tracetest

purnesh42H · 2025-02-19T05:42:50Z

examples/features/opentelemetry/client/main.go

@@ -48,26 +51,49 @@ func main() {
 		log.Fatalf("Failed to start prometheus exporter: %v", err)
 	}
 	provider := metric.NewMeterProvider(metric.WithReader(exporter))
-	go http.ListenAndServe(*prometheusEndpoint, promhttp.Handler())
+
+	spanExporter := tracetest.NewInMemoryExporter()


let's rename the exporters more explicit. For trace, call it traceExporter and for metric call it metricExporter

purnesh42H · 2025-02-19T05:43:17Z

examples/features/opentelemetry/server/main.go


-	so := opentelemetry.ServerOption(opentelemetry.Options{MetricsOptions: opentelemetry.MetricsOptions{MeterProvider: provider}})
+	spanExporter := tracetest.NewInMemoryExporter()


same comment as client about naming of exporters.

purnesh42H · 2025-02-19T05:43:31Z

examples/features/opentelemetry/server/main.go

+	}
+
+	go func() {
+		log.Printf("Starting Prometheus metrics server at %s\n", *prometheusEndpoint)


same comment as client about prometheus

purnesh42H · 2025-02-19T05:43:40Z

examples/features/opentelemetry/server/main.go

+		}
+	}()
+
+	so := opentelemetry.ServerOption(opentelemetry.Options{


same comment as client

janardhanvissa · 2025-02-19T09:36:16Z

examples/features/opentelemetry/client/main.go

 )

 var (
 	addr               = flag.String("addr", ":50051", "the server address to connect to")
 	prometheusEndpoint = flag.String("prometheus_endpoint", ":9465", "the Prometheus exporter endpoint")
 )

+// initTracer initializes OpenTelemetry tracing
+func initTracer() (*trace.TracerProvider, error) {
+	exporter, err := stdouttrace.New(stdouttrace.WithPrettyPrint())


@purnesh42H Can we use this way? Previously I did like this.

purnesh42H · 2025-02-24T05:16:26Z

examples/features/opentelemetry/client/main.go

@@ -47,26 +47,33 @@ import (
 var (
 	addr               = flag.String("addr", ":50051", "the server address to connect to")
 	prometheusEndpoint = flag.String("prometheus_endpoint", ":9465", "the Prometheus exporter endpoint")
+	otlpEndpoint       = flag.String("otlp_endpoint", "localhost:4318", "the OTLP collector endpoint")


nit: localhost is not needed. Keep it same as other endpoints. Also, lets be more explicit in naming since we both traces and metrics. the Prometheus exporter endpoint for metrics and the OTLP collector endpoint for traces

purnesh42H · 2025-02-24T05:17:05Z

examples/features/opentelemetry/server/main.go

@@ -46,6 +46,8 @@ import (
 var (
 	addr               = flag.String("addr", ":50051", "the server address to connect to")
 	prometheusEndpoint = flag.String("prometheus_endpoint", ":9464", "the Prometheus exporter endpoint")
+	otlpEndpoint       = flag.String("otlp_endpoint", "localhost:4318", "the OTLP collector endpoint")


same. localhost not needed

Also, lets be more explicit in naming since we both traces and metrics. the Prometheus exporter endpoint for metrics and the OTLP collector endpoint for traces

purnesh42H · 2025-02-24T05:20:48Z

examples/go.mod

@@ -41,6 +45,7 @@ require (
 	github.com/aws/aws-sdk-go-v2/service/sts v1.33.5 // indirect
 	github.com/aws/smithy-go v1.22.1 // indirect
 	github.com/beorn7/perks v1.0.1 // indirect
+	github.com/cenkalti/backoff/v4 v4.3.0 // indirect


Why do we need this? Let's remove unnecessary dependencies.

these are generated using go mod tidy and no other changes in my local.

purnesh42H · 2025-02-24T05:21:20Z

examples/go.mod

@@ -54,6 +59,7 @@ require (
 	github.com/google/uuid v1.6.0 // indirect
 	github.com/googleapis/enterprise-certificate-proxy v0.3.4 // indirect
 	github.com/googleapis/gax-go/v2 v2.14.1 // indirect
+	github.com/grpc-ecosystem/grpc-gateway/v2 v2.25.1 // indirect


Similar comment about its necessity. Let's remove unnecessary dependencies.

these are generated using go mod tidy and no other changes in my local.

examples/features/opentelemetry/README.md

purnesh42H · 2025-02-28T11:20:11Z

examples/features/opentelemetry/README.md

+    * **Docker Jaeger:**
+
+        ```
+        docker run -d -p 16686:16686 -p 14268:14268 \


so, we need to have docker to run this example?

we can do with or without docker

purnesh42H · 2025-02-28T11:20:39Z

examples/features/opentelemetry/README.md

+            file:
+
+            ```
+            docker run -d -p 4317:4317 -p 4318:4318 \


same: can we do it without docker command?

yes we can do that. we are just providing the user to do either of the ways.

purnesh42H · 2025-02-28T11:22:37Z

examples/go.mod

@@ -1,11 +1,22 @@
 module google.golang.org/grpc/examples

+// NOTE:


what is this NOTE for? It is generated?

It's not generated. Removing from here and keeping in the readme file

examples/features/opentelemetry/README.md

purnesh42H · 2025-02-28T11:27:37Z

examples/features/opentelemetry/README.md

-The client continuously makes RPC's to a server. The client and server both
-expose a prometheus exporter to listen and provide metrics. This defaults to
-:9464 for the server and :9465 for the client.
+* **Continuous RPC Calls:** The client continuously makes RPC calls to


why this change about metrics? Let's not make too many changes for metrics. Let's keep this PR focused on adding content for tracing only.

purnesh42H · 2025-02-28T11:28:47Z

examples/features/opentelemetry/README.md

+
+    * **Local Collector:**
+        * Install the `otelcol-contrib` binary.
+        * Create a configuration file (e.g., `collector-config.yaml`)


as i mentioned in the meeting. We should not ask the user to create a config.yaml file. We should provide a yaml which should work as is. If user want to modify that, they can

purnesh42H · 2025-02-28T11:29:59Z

examples/features/opentelemetry/README.md

-Curling to the exposed Prometheus ports outputs the metrics recorded on the
-client and server.
+    * Open `http://localhost:16686` in your browser.
+    * Search for traces to visualize the RPC call flow. The traces will


you can mention the name of some of the traces that gRPC emit

purnesh42H · 2025-03-04T06:34:05Z

examples/features/opentelemetry/README.md

+
+    * This starts the gRPC client, which continuously makes RPC calls to the
+    server and is configured to send trace data via OTLP and expose
+    Prometheus metrics.


why "expose Prometheus metrics"? Aren't we talking about traces?

purnesh42H · 2025-03-04T06:36:12Z

examples/features/opentelemetry/README.md

+        * For the OpenTelemetry Collector Core distribution specifically, see
+            [OpenTelemetry Collector Core Releases](https://github.com/open-telemetry/
+            opentelemetry-collector-releases/tree/main/distributions/otelcol).
+        * Create a `collector-config.yaml` file with the following content:


we should have the yaml file in the example itself. Not mention in readme. In readme we should just mention the collector will use the this yaml.

purnesh42H · 2025-03-04T06:37:05Z

examples/features/opentelemetry/client/main.go

+		otlptracehttp.WithEndpoint("localhost:4318"),
+		otlptracehttp.WithInsecure(),
+	)
+	traceExporter, err := otlptrace.New(context.Background(), otlpclient)


where did you change this? Its still creating a new context. Please use single context throughout which is cancelable

examples/features/opentelemetry/client/main.go

purnesh42H · 2025-03-04T06:40:40Z

examples/features/opentelemetry/client/main.go

 	}
 	defer cc.Close()
 	c := echo.NewEchoClient(cc)

-	// Make an RPC every second. This should trigger telemetry to be emitted from
+	// Make an RPC every second. This should trigger telemetry on prometheus
+	// server along with traces in the otlptracer exporter to be emitted from
 	// the client and the server.


this is only about client, so let's omit server?

purnesh42H · 2025-03-04T06:43:10Z

examples/features/opentelemetry/server/main.go

+		otlptracehttp.WithEndpoint("localhost:4318"),
+		otlptracehttp.WithInsecure(),
+	)
+	traceExporter, err := otlptrace.New(context.Background(), client)


Its not done. Please use same context throughout that was created initially

…ment to resource.New

purnesh42H · 2025-03-04T10:23:45Z

examples/features/opentelemetry/server/main.go

 )

 var (
 	addr               = flag.String("addr", ":50051", "the server address to connect to")
-	prometheusEndpoint = flag.String("prometheus_endpoint", ":9464", "the Prometheus exporter endpoint")
+	prometheusEndpoint = flag.String("prometheus_endpoint", ":9464", "the Prometheus exporter endpoint for metrics")
+	otlpEndpoint       = flag.String("otlp_endpoint", ":4318", "the OTLP collector endpoint for traces")


should be a different endpoint that client

purnesh42H · 2025-03-04T10:24:03Z

examples/features/opentelemetry/collector-config.yaml

@@ -0,0 +1,20 @@
+receivers:


please do separate configs for client and server

…e collector config

This reverts commit c5a1dcf.

purnesh42H · 2025-03-07T11:15:06Z

examples/features/opentelemetry/server/collector-config.yaml

@@ -0,0 +1,19 @@
+receivers:


same. Link the url for example collector config

purnesh42H · 2025-03-07T11:16:18Z

examples/features/opentelemetry/server/main.go

+	}
+	spanProcessor := trace.NewSimpleSpanProcessor(traceExporter)
+	tp := trace.NewTracerProvider(trace.WithSpanProcessor(spanProcessor), trace.WithResource(res))
+	otel.SetTracerProvider(tp)


same. We shouldn't be doing it. gRPC tracing code is already doing it.

purnesh42H · 2025-03-07T11:26:12Z

examples/features/opentelemetry/README.md


-```
-curl localhost:9464/metrics


We can't remove these because they are for metrics.

Create separate sections "See metrics" and "See traces". "See metrics" can have this part and "See traces" should have collector part.

purnesh42H · 2025-03-07T11:27:02Z

examples/features/opentelemetry/README.md

-OpenTelemetry is configured on both the client and the server, and exports to
-the Prometheus exporter. The exporter exposes metrics on the Prometheus ports
-described above.
+4.  **View Traces in the Collector Output:**


Can't we do curl similar to metrics?

purnesh42H · 2025-03-07T11:27:54Z

examples/features/opentelemetry/README.md

-The client continuously makes RPC's to a server. The client and server both
-expose a prometheus exporter to listen and provide metrics. This defaults to
-:9464 for the server and :9465 for the client.
+    * **Local Collector:**


Does this need to be running before client and server? If yes, we need to move this up and and mention in brackets (Only for traces)

purnesh42H · 2025-03-07T11:29:41Z

examples/features/opentelemetry/README.md


-Curling to the exposed Prometheus ports outputs the metrics recorded on the


Same. We can't remove this. As this is for metrics.

purnesh42H · 2025-03-07T11:30:23Z

examples/features/opentelemetry/client/collector-config.yaml

@@ -0,0 +1,19 @@
+receivers:


Please link a URL at the top for collector config format

purnesh42H · 2025-03-07T11:35:51Z

examples/features/opentelemetry/client/main.go

+	}
+	spanProcessor := trace.NewSimpleSpanProcessor(traceExporter)
+	tp := trace.NewTracerProvider(trace.WithSpanProcessor(spanProcessor), trace.WithResource(res))
+	otel.SetTracerProvider(tp)


@dfawley was there any reason we decided to set these outside of gRPC? If we are asking user to set these, do we need it to be in TraceOptions?

We don't really want to be using this global in our implementation. We should be able to delete this line since we should be using the TracerProvider in TraceOptions. Global state should generally be avoided.

purnesh42H · 2025-03-07T11:36:11Z

examples/features/opentelemetry/server/main.go

+	if err != nil {
+		log.Fatalf("Failed to create otlp trace exporter: %v", err)
+	}
+	// resource.New adds service metadata to telemetry, enabling context and


is this mandatory for the tracing to work? If not, we don't need to add here

dfawley · 2025-03-07T20:39:53Z

examples/features/opentelemetry/client/main.go

+	"go.opentelemetry.io/otel/sdk/metric"
+	"go.opentelemetry.io/otel/sdk/resource"
+	"go.opentelemetry.io/otel/sdk/trace"


I would prefer to rename these imports as otelmetric/etc so there is no confusion. "trace" and "metric" are such generic names that it could be confusing.

dfawley · 2025-03-07T20:48:03Z

examples/features/opentelemetry/client/main.go

+	}
+	spanProcessor := trace.NewSimpleSpanProcessor(traceExporter)
+	tp := trace.NewTracerProvider(trace.WithSpanProcessor(spanProcessor), trace.WithResource(res))
+	otel.SetTracerProvider(tp)


We don't really want to be using this global in our implementation. We should be able to delete this line since we should be using the TracerProvider in TraceOptions. Global state should generally be avoided.

janardhankrishna-sai and others added 9 commits December 23, 2024 07:09

replace dial with newclient

7ddbe46

Merge branch 'master' of https://github.com/janardhanvissa/grpc-go

0486355

Merge branch 'grpc:master' into master

53fa9cd

Merge branch 'grpc:master' into master

4435b8a

Merge branch 'grpc:master' into master

a413555

Merge branch 'grpc:master' into master

4e203c3

Merge branch 'grpc:master' into master

e9ad552

adding opentelemetry tracing for client-server

61e15e3

adding opentelemetry tracing for client-server

4a988a6

purnesh42H reviewed Feb 5, 2025

View reviewed changes

purnesh42H assigned janardhanvissa Feb 5, 2025

addressing review comments

58451b6

janardhanvissa force-pushed the tracing-otel branch from f463f2b to 58451b6 Compare February 6, 2025 09:56

janardhankrishna-sai added 9 commits February 6, 2025 10:03

reverting Newclient changes

9ac7ce3

reverting Newclient changes

c0e8885

adding dependency files

0b4231a

removing unused ctx

b8c0ef5

fixing vet issue

a33cc4b

adding trace to client/server

6215e98

fix vet issue

c68e570

fixing vet issue

02d9139

removing empty lines

9db8ad6

purnesh42H assigned purnesh42H and unassigned janardhanvissa Feb 18, 2025

purnesh42H changed the title ~~opentelemetry: add open telemetry trace for client/server~~ examples/features/opentelemetry: Add example to demonstrate OpenTelemetry Tracing Feb 19, 2025

purnesh42H reviewed Feb 19, 2025

View reviewed changes

purnesh42H assigned janardhanvissa and unassigned purnesh42H Feb 19, 2025

janardhanvissa commented Feb 19, 2025

View reviewed changes

janardhanvissa requested a review from purnesh42H February 21, 2025 10:40

purnesh42H reviewed Feb 24, 2025

View reviewed changes

janardhankrishna-sai and others added 8 commits February 24, 2025 06:09

explicit naming for traces and metrics

ebe37f3

Merge branch 'master' into tracing-otel

99cc7d7

putting link in go.mod for examples and updating dependencies

b10de6e

document for trace visualization

8664e40

updating readme

8fcfc33

updating README.md

0ef715a

fixing vet issue

a2fd0c0

fixing vet issue

737c458

purnesh42H reviewed Feb 28, 2025

View reviewed changes

janardhankrishna-sai added 4 commits February 28, 2025 14:16

updating readme file and removing links from go.mod file

ad5c177

fixing vet issue

5e1d020

fixing vet issue

11f0d89

adding new line for fixing vet issue

10821bb

purnesh42H reviewed Mar 4, 2025

View reviewed changes

janardhankrishna-sai added 3 commits March 4, 2025 08:18

updating readme and creating separate collector-config and adding com…

c027805

…ment to resource.New

fixing vet issue

1bb9bd4

update readme

23e0ff5

purnesh42H reviewed Mar 4, 2025

View reviewed changes

janardhankrishna-sai added 6 commits March 4, 2025 18:08

adding two separate ports for server and client collector and separat…

dcd525a

…e collector config

adding the command to execute the collector

8693ecc

updating config and dependencies

c5a1dcf

Revert "updating config and dependencies"

87e4352

This reverts commit c5a1dcf.

updating config files

545bf03

fixing vet issue

06f4309

janardhanvissa requested a review from purnesh42H March 7, 2025 04:42

purnesh42H reviewed Mar 7, 2025

View reviewed changes

dfawley reviewed Mar 7, 2025

View reviewed changes


		so := opentelemetry.ServerOption(opentelemetry.Options{MetricsOptions: opentelemetry.MetricsOptions{MeterProvider: provider}})
		spanExporter := tracetest.NewInMemoryExporter()

		@@ -1,11 +1,22 @@
		module google.golang.org/grpc/examples

		// NOTE:


		Curling to the exposed Prometheus ports outputs the metrics recorded on the

examples/features/opentelemetry: Include OpenTelemetry tracing plugin usage and output in example server and client #8056

Are you sure you want to change the base?

examples/features/opentelemetry: Include OpenTelemetry tracing plugin usage and output in example server and client #8056

Conversation

janardhanvissa commented Jan 30, 2025 • edited by purnesh42H Loading

codecov bot commented Jan 30, 2025 • edited Loading

Codecov Report

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

purnesh42H left a comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

purnesh42H Mar 4, 2025 • edited Loading

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

Choose a reason for hiding this comment

janardhanvissa commented Jan 30, 2025 •

edited by purnesh42H

Loading

codecov bot commented Jan 30, 2025 •

edited

Loading

purnesh42H Mar 4, 2025 •

edited

Loading