From fbead53442f11080e41463baa36fc3f3b4c74cc9 Mon Sep 17 00:00:00 2001 From: Shay Rojansky Date: Sun, 2 Mar 2025 09:19:49 +0200 Subject: [PATCH] Update dotnet SDK and docfx versions --- .github/workflows/build-documentation.yml | 4 ++-- conceptual/Npgsql/diagnostics/tracing.md | 4 ++-- conceptual/Npgsql/release-notes/9.0.md | 2 +- 3 files changed, 5 insertions(+), 5 deletions(-) diff --git a/.github/workflows/build-documentation.yml b/.github/workflows/build-documentation.yml index 781783bf..847938b2 100644 --- a/.github/workflows/build-documentation.yml +++ b/.github/workflows/build-documentation.yml @@ -39,7 +39,7 @@ jobs: - name: Setup .NET Core uses: actions/setup-dotnet@v4.3.0 with: - dotnet-version: 7.0.x + dotnet-version: 9.0.x - name: Checkout Npgsql uses: actions/checkout@v4 @@ -67,7 +67,7 @@ jobs: working-directory: EFCore.PG - name: Get docfx - run: dotnet tool install --version 2.78.0 -g docfx + run: dotnet tool install --version 2.78.3 -g docfx - name: Build docs run: docfx --warningsAsErrors diff --git a/conceptual/Npgsql/diagnostics/tracing.md b/conceptual/Npgsql/diagnostics/tracing.md index 5ab16550..7d6a9ef6 100644 --- a/conceptual/Npgsql/diagnostics/tracing.md +++ b/conceptual/Npgsql/diagnostics/tracing.md @@ -37,7 +37,7 @@ In this trace, the Npgsql query (to database testdb) took around 800ms, and was > > This feature was introduced in Npgsql 9.0 -Once you've enabled Npgsql tracing as above, you can tweak its configuration via the API: +Once you've enabled Npgsql tracing as above, you can tweak its configuration via the API: ```csharp dataSourceBuilder.ConfigureTracing(o => o @@ -56,7 +56,7 @@ This allows you to: ## Using `AsyncLocal` to pass arbitrary information to your callbacks -The callbacks available via only accept the or as their parameters; this makes it difficult to e.g. assign arbitrary names to your commands, so that show up as the span names in your tracing monitor. You can use .NET [`AsyncLocal`](https://learn.microsoft.com/dotnet/api/system.threading.asynclocal-1) to flow arbitrary information from the command call site (where you execute the command) to your tracing callbacks to achieve this. +The callbacks available via only accept the or as their parameters; this makes it difficult to e.g. assign arbitrary names to your commands, so that show up as the span names in your tracing monitor. You can use .NET [`AsyncLocal`](https://learn.microsoft.com/dotnet/api/system.threading.asynclocal-1) to flow arbitrary information from the command call site (where you execute the command) to your tracing callbacks to achieve this. For example, the following adds an `ExecuteReaderWithSpanNameAsync` extension method to : diff --git a/conceptual/Npgsql/release-notes/9.0.md b/conceptual/Npgsql/release-notes/9.0.md index 26941449..3f16f77e 100644 --- a/conceptual/Npgsql/release-notes/9.0.md +++ b/conceptual/Npgsql/release-notes/9.0.md @@ -7,7 +7,7 @@ Npgsql.EntityFrameworkCore.PostgreSQL version 9.0 is out and available on [nuget ## Tracing improvements -Several quality-of-life improvements have been implemented for Npgsql's OpenTelemetry tracing support. You can now do the following via the new API: +Several quality-of-life improvements have been implemented for Npgsql's OpenTelemetry tracing support. You can now do the following via the new API: * Specify a filter which determines which commands get traced * Set the the tracing span name (e.g. use the command's SQL as the span name)