Npgsql.NpgsqlException (0x80004005): Exception while reading from stream - 8.0.0 #5430

yunfandev · 2023-11-21T10:10:23Z

The issue

var multi = await _dbContext.Database.GetDbConnection().QueryMultipleAsync(querySql + summarySql, paramters);
var items = await multi.ReadAsync<ItemModel>();
var summary = await multi.ReadFirstAsync<SummaryModel>();

After upgrading to 8.0, the third line of code runs with the following error:

System.InvalidOperationException: The reader is closed
   at void Npgsql.ThrowHelper.ThrowInvalidOperationException(string message)
   at void Npgsql.NpgsqlDataReader.CheckClosedOrDisposed()+Throw(ReaderState state)
   at async Task<bool> Npgsql.NpgsqlDataReader.NextResult(bool async, bool isConsuming, CancellationToken cancellationToken)
   at async Task Dapper.SqlMapper+GridReader.OnAfterGridAsync(int index) in /_/Dapper/SqlMapper.GridReader.Async.cs:line 148
   at async Task<IEnumerable<T>> Dapper.SqlMapper+GridReader.ReadBufferedAsync<T>(int index, Func<DbDataReader, object> deserializer) in /_/Dapper/SqlMapper.GridReader.Async.cs:line 246

Further technical details

Npgsql version: 8.0
PostgreSQL version: 15.3
Operating system: Debian 12 in Docker

The text was updated successfully, but these errors were encountered:

NinoFloris · 2023-11-21T13:32:24Z

Could you make this a runnable sample? Adding the (if possible, simplified) definitions of querySql, summarySql, ItemModel and SummaryModel would help me investigate.

yunfandev · 2023-11-21T15:29:09Z

Ok, Give me some time.

yunfandev · 2023-11-21T15:52:49Z

I have a feeling that this problem is actually caused by another issue. When the SQL query returns a lot of content, the first thing I encounter is a timeout before The reader is closed

Hopefully this will help in investing the problem

Npgsql.NpgsqlException (0x80004005): Exception while reading from stream
 ---> System.TimeoutException: Timeout during reading attempt
   at async ValueTask Npgsql.Internal.NpgsqlReadBuffer.Ensure(int count, bool async)+EnsureLong(?)
   at async Task Npgsql.Internal.NpgsqlReadBuffer.Skip(int len, bool async)
   at async Task Npgsql.NpgsqlDataReader.ConsumeRow(bool async)+ConsumeRowSequential(?)
   at async bool Npgsql.NpgsqlDataReader.NextResult()+ConsumeResultSet(?)
   at async Task<bool> Npgsql.NpgsqlDataReader.NextResult(bool async, bool isConsuming, CancellationToken cancellationToken) x 2
   at async Task Dapper.SqlMapper+GridReader.OnAfterGridAsync(int index) in /_/Dapper/SqlMapper.GridReader.Async.cs:line 148

I continued to try to write a runnable sample.

Could you make this a runnable sample? Adding the (if possible, simplified) definitions of querySql, summarySql, ItemModel and SummaryModel would help me investigate.

NinoFloris · 2023-11-21T16:49:50Z

Hopefully this will help in investing the problem

It does help, it confirms my suspicion we're going off the rails somewhere, likely losing protocol sync.

I continued to try to write a runnable sample.

Thanks.

In the meantime could you try to rerun your code with AppContext.SetSwitch("Npgsql.EnableDiagnostics", true); added to your program.cs? (make sure it's set before any Npgsql code is called) The extra checks should help us get more precise exceptions. Ideally you might get an exception from the exact point where we lose sync.

Let us know what the results are, even if nothing changed!

yunfandev · 2023-11-22T11:41:44Z

Rerun your code with AppContext.SetSwitch("Npgsql.EnableDiagnostics", true); added to your program.cs

This is the exception after set AppContext.SetSwitch("Npgsql.EnableDiagnostics", true);

Npgsql.NpgsqlException (0x80004005): Exception while reading from stream
 ---> System.TimeoutException: Timeout during reading attempt
   at Npgsql.Internal.NpgsqlReadBuffer.<Ensure>g__EnsureLong|54_0(NpgsqlReadBuffer buffer, Int32 count, Boolean async, Boolean readingNotifications)
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at Npgsql.Internal.NpgsqlReadBuffer.Skip(Int32 len, Boolean async)
   at Npgsql.Internal.PgReader.Consume(Boolean async, Nullable`1 count, CancellationToken cancellationToken)
   at Npgsql.Internal.PgReader.<CommitAsync>g__CommitSlow|99_0()
   at Npgsql.NpgsqlDataReader.<ConsumeRow>g__ConsumeRowSequential|129_0(Boolean async)
   at Npgsql.NpgsqlDataReader.<NextResult>g__ConsumeResultSet|52_0(Boolean async)
   at Npgsql.NpgsqlDataReader.NextResult(Boolean async, Boolean isConsuming, CancellationToken cancellationToken)
   at Npgsql.NpgsqlDataReader.NextResult(Boolean async, Boolean isConsuming, CancellationToken cancellationToken)
   at Dapper.SqlMapper.GridReader.OnAfterGridAsync(Int32 index) in /_/Dapper/SqlMapper.GridReader.Async.cs:line 148
   at Dapper.SqlMapper.GridReader.ReadBufferedAsync[T](Int32 index, Func`2 deserializer) in /_/Dapper/SqlMapper.GridReader.Async.cs:line 246

NinoFloris · 2023-11-29T18:53:12Z

@yunfandev I think #5440 will solve your issue as well.

To confirm could you run your code on our daily build? https://www.myget.org/feed/npgsql-vnext/package/nuget/Npgsql/9.0.0-preview.1-ci.20231128T234421+sha.b21c41c58

yunfandev · 2023-11-30T08:07:35Z

Thanks! @NinoFloris
Let me have a try.

yunfandev · 2023-12-01T06:44:03Z

@NinoFloris I tested the latest Nuget package and the problem is solved! Thx!

yunfandev · 2023-12-05T09:09:21Z

@NinoFloris After upgrade to 8.0.1 we still receive this error:

Npgsql.NpgsqlException (0x80004005): Exception while reading from stream
 ---> System.TimeoutException: Timeout during reading attempt
   at async ValueTask Npgsql.Internal.NpgsqlReadBuffer.Ensure(int count, bool async)+EnsureLong(?)
   at async Task Npgsql.Internal.NpgsqlReadBuffer.Skip(int len, bool async)
   at async Task Npgsql.NpgsqlDataReader.ConsumeRow(bool async)+ConsumeRowSequential(?)
   at async bool Npgsql.NpgsqlDataReader.NextResult()+ConsumeResultSet(?)
   at async Task<bool> Npgsql.NpgsqlDataReader.NextResult(bool async, bool isConsuming, CancellationToken cancellationToken) x 2
   at async Task Dapper.SqlMapper+GridReader.OnAfterGridAsync(int index) in /_/Dapper/SqlMapper.GridReader.Async.cs:line 148
   at async Task<IEnumerable<T>> Dapper.SqlMapper+GridReader.ReadBufferedAsync<T>(int index, Func<DbDataReader, object> deserializer) in /_/Dapper/SqlMapper.GridReader.Async.cs:line 246

NinoFloris · 2023-12-05T12:27:57Z

And you're sure it was fixed with #5430 (comment) ?

Regardless, for me to do anything here I really need a runnable repro of your issue.

vonzshik · 2023-12-05T12:39:44Z

And could you also confirm that the issue doesn't happen with npgsql 7.0?

yunfandev · 2023-12-05T15:22:22Z

@vonzshik This problem doesn't occur in 7.0

@NinoFloris I'll reconfirm the issue tomorrow, as we're all docker builds without a nuget package cache, so it's unlikely to be a problem with me not upgrading to version 8.0.1

I will make a working repo as soon as I can.

kae · 2023-12-07T12:16:06Z

#5439

Was resolved for repro code.
But after update to 8.0.1 had new cases in queries that has more than 3 "skipped" columns while reading

with errors

"Internal Npgsql bug: unexpected value 0 of enum BackendMessageCode. Please file a bug."
"The read on this field has not consumed all of its bytes (pos: 4, len: 105)"

tried to repro it with simplest case and had reproducible error with code

using System;
using System.Threading.Tasks;

namespace pgTest;

public class Program {
	private const string ConnStr = "Server=pg;Port=5432;Database=temp;User id=admin;Password=admin";
	private static readonly Npgsql.NpgsqlDataSource ds = new Npgsql.NpgsqlDataSourceBuilder(ConnStr).Build();

	public static async Task Main() {
		AppContext.SetSwitch("Npgsql.EnableAssertions", true);
		try {
			Console.WriteLine($"Started");
			using var conn = await ds.OpenConnectionAsync();
			Console.WriteLine($"Connected");
			using var tx = await conn.BeginTransactionAsync();

			using var cmd = conn.CreateCommand();
			cmd.CommandTimeout = 1;
			cmd.Transaction = tx;
			cmd.CommandText = """select v.i, repeat('1', 10), repeat('2', 10), repeat('3', 10), repeat('4', 10), 1, 2 from generate_series(1, 1000) as v(i)""";
			var rdr = await cmd.ExecuteReaderAsync(System.Data.CommandBehavior.SingleResult | System.Data.CommandBehavior.SequentialAccess);
			while (await rdr.ReadAsync()) {
				_ = rdr[0];
				_ = rdr[1];
				//_ = rdr[2];
				//_ = rdr[3];
				//_ = rdr[4];
				//_ = rdr[5]; // uncomment lines for successful execution
				_ = rdr[6];
			}
			await rdr.DisposeAsync();
			await cmd.DisposeAsync();

			await tx.CommitAsync();
			await conn.DisposeAsync();
		}
		catch (Exception e) {
			Console.WriteLine(e);
		}
	}
}

But with error

Npgsql.NpgsqlException (0x80004005): Exception while reading from stream
 ---> System.TimeoutException: Timeout during reading attempt
   at Npgsql.Internal.NpgsqlReadBuffer.<Ensure>g__EnsureLong|54_0(NpgsqlReadBuffer buffer, Int32 count, Boolean async, Boolean readingNotifications)
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at Npgsql.Internal.NpgsqlReadBuffer.Skip(Int32 len, Boolean async)
   at Npgsql.NpgsqlDataReader.<>c__DisplayClass128_0.<<SeekToColumnSequential>g__Core|0>d.MoveNext()

Not sure it's tightly linked, but maybe it has same reason.

@NinoFloris

NinoFloris · 2023-12-07T13:55:27Z

@kae thanks for the repro, that's unfortunate... I've tested it against #5476 which does away with the complicated buffered sequential fast path entirely. It passes there but I'm not sure it's something we want to backport to 8.0.2. Because of that I've also created a targeted fix in #5486.

I'm sorry for the issue persisting into the 8.0.1 release.

Skayloo · 2023-12-29T09:44:27Z

I guess i have the same issue in package Npgsql.EntityFrameworkCore.PostgreSQL version 8.0.0
Sometimes it works fine

using (var multi = await connection.QueryMultipleAsync(query, parameters))
{
    result.TotalItems = multi.ReadSingle<int>();
    result.Items = multi.Read<UserForInternalAgentDto>().ToArray();
}

Stacktrace

System.InvalidOperationException: The reader is closed
   at Npgsql.ThrowHelper.ThrowInvalidOperationException(String message)
   at Npgsql.NpgsqlDataReader.<CheckClosedOrDisposed>g__Throw|138_0(ReaderState state)
   at Npgsql.NpgsqlDataReader.CheckClosedOrDisposed()
   at Npgsql.NpgsqlDataReader.NextResult(Boolean async, Boolean isConsuming, CancellationToken cancellationToken)
   at Npgsql.NpgsqlDataReader.NextResult()
   at Dapper.SqlMapper.GridReader.OnAfterGrid(Int32 index) in /_/Dapper/SqlMapper.GridReader.cs:line 450
   at Dapper.SqlMapper.GridReader.ReadDeferred[T](Int32 index, Func`2 deserializer, Type effectiveType)+<>m__Finally1() in /_/Dapper/SqlMapper.GridReader.cs:line 404
   at Dapper.SqlMapper.GridReader.ReadDeferred[T](Int32 index, Func`2 deserializer, Type effectiveType)+System.IDisposable.Dispose()
   at Dapper.SqlMapper.GridReader.ReadDeferred[T](Int32 index, Func`2 deserializer, Type effectiveType)+MoveNext() in /_/Dapper/SqlMapper.GridReader.cs:line 406
   at System.Collections.Generic.List`1..ctor(IEnumerable`1 collection)
   at System.Linq.Enumerable.ToList[TSource](IEnumerable`1 source)
   at Dapper.SqlMapper.GridReader.ReadImpl[T](Type type, Boolean buffered) in /_/Dapper/SqlMapper.GridReader.cs:line 205   at Dapper.SqlMapper.GridReader.Read[T](Boolean buffered) in /_/Dapper/SqlMapper.GridReader.cs:line 96

NinoFloris · 2024-01-17T21:43:58Z

@Skayloo you might want to open another issue with a minimal repro. EF doesn't use CommandBehavior.Sequential so it should not be affected by this particular issue.

roji · 2024-01-18T07:21:21Z

Unless I'm mistaken, QueryMultipleAsync is Dapper (which I think does use CommandBehavior.Sequential) - in any case there's no such thing in EF.

niklasweimann · 2024-01-18T12:47:45Z

Heyho 👋
Thank you for providing this Libary: We have updated to the latest 8.0.1 release from 7.0.6 and we are experiencing the following exception when there is a high load of complex queries:

Npgsql.NpgsqlException (0x80004005): Exception while reading from stream
 ---> System.TimeoutException: Timeout during reading attempt
   at Npgsql.Internal.NpgsqlReadBuffer.<Ensure>g__EnsureLong|54_0(NpgsqlReadBuffer buffer, Int32 count, Boolean async, Boolean readingNotifications)
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at Npgsql.Internal.NpgsqlConnector.ReadMessageLong(Boolean async, DataRowLoadingMode dataRowLoadingMode, Boolean readingNotifications, Boolean isReadingPrependedMessage)
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
   at Npgsql.NpgsqlDataReader.NextResult(Boolean async, Boolean isConsuming, CancellationToken cancellationToken)
   at Npgsql.NpgsqlDataReader.NextResult(Boolean async, Boolean isConsuming, CancellationToken cancellationToken)
   at Npgsql.NpgsqlDataReader.NextResult()
   at Npgsql.NpgsqlCommand.ExecuteReader(Boolean async, CommandBehavior behavior, CancellationToken cancellationToken)
   at Npgsql.NpgsqlCommand.ExecuteReader(Boolean async, CommandBehavior behavior, CancellationToken cancellationToken)
   at Npgsql.NpgsqlCommand.ExecuteReader(CommandBehavior behavior)
   at Npgsql.NpgsqlBatch.ExecuteReader(CommandBehavior behavior)
   at Npgsql.Internal.NpgsqlConnector.QueryDatabaseState(NpgsqlTimeout timeout, Boolean async, CancellationToken cancellationToken)
   at Npgsql.NpgsqlMultiHostDataSource.TryGetIdleOrNew(NpgsqlConnection conn, TimeSpan timeoutPerHost, Boolean async, TargetSessionAttributes preferredType, Func`3 stateValidator, Int32 poolIndex, IList`1 exceptions, CancellationToken cancellationToken)

The Stacktrace looks pretty simiular to this issue so i decided to post this here. Some information about our system:
We were using:

.net8
- with docker (mcr.microsoft.com/dotnet/aspnet:8.0.1-bookworm-slim@sha256:3ff67792728179308c4bf06799d8b45d155c60fddc347acf69465a496d9a20b8)
npgsql with 8.0.1
Postgres 13
We use the "Multiple Hosts"-Feature with 3 Postgres nodes where one of them is primary and the other hosts are replicas. So we set Target Session Attributes=primary.

mjauernig · 2024-01-29T19:22:55Z

@yunfandev I think #5440 will solve your issue as well.

To confirm could you run your code on our daily build? https://www.myget.org/feed/npgsql-vnext/package/nuget/Npgsql/9.0.0-preview.1-ci.20231128T234421+sha.b21c41c58

Hi,

i run in a similiar problem. I use npgsl 8.0.1 and it works fine except one case where i have a huge load of executed queries. The queries are inside a for loop and get multiple times repeated with different parameters. After a few executions it will throw a timeout execution Timeout during reading attempt.

The problem occurs also with the quoted preview release. It works normal with 7.0.6.

The exception.

kamisoft-fr · 2024-01-31T09:07:06Z

Hello, FYI same problem here with very simple query on a table with 100k rows, sometimes it works, sometimes it fails (but apparently always on the same WHERE xxx = value) with the following stack

TFM: net8.0
Npgsql lib : 8.0.1
Docker PostgreSQL 15.5 (Debian 15.5-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit

System.Data.DataException: Exception while reading from stream
 ---> Npgsql.NpgsqlException (0x80004005): Exception while reading from stream
 ---> System.TimeoutException: Timeout during reading attempt
   at Npgsql.Internal.NpgsqlReadBuffer.<Ensure>g__EnsureLong|54_0(NpgsqlReadBuffer buffer, Int32 count, Boolean async, Boolean readingNotifications)
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at Npgsql.Internal.NpgsqlReadBuffer.Skip(Int32 len, Boolean async)
   at Npgsql.NpgsqlDataReader.<>c__DisplayClass128_0.<<SeekToColumnSequential>g__Core|0>d.MoveNext()
--- End of stack trace from previous location ---
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
   at Npgsql.NpgsqlDataReader.GetValue(Int32 ordinal)
   at Npgsql.NpgsqlDataReader.get_Item(Int32 ordinal)
   at Deserializeb0d63090-174b-4788-9742-033a6792fc73(DbDataReader)
   --- End of inner exception stack trace ---
   at Dapper.SqlMapper.ThrowDataException(Exception ex, Int32 index, IDataReader reader, Object value) in /_/Dapper/SqlMapper.cs:line 3928
   at Deserializeb0d63090-174b-4788-9742-033a6792fc73(DbDataReader)
   at Dapper.SqlMapper.QueryAsync[T](IDbConnection cnn, Type effectiveType, CommandDefinition command)

Fixes #5430 (cherry picked from commit dffa843) # Conflicts: # src/Npgsql/NpgsqlDataReader.cs

roji · 2024-01-31T19:35:47Z

@NinoFloris should we move this to the 8.0.2 milestone?

NinoFloris · 2024-01-31T20:18:46Z

Moved!

NinoFloris · 2024-01-31T22:01:10Z

I want to make sure we can put this issue to bed properly with 8.0.2.

@kae would you mind running the latest ci build from myget to see if things are working correctly for you? (https://www.myget.org/feed/npgsql-vnext/package/nuget/Npgsql/9.0.0-preview.1-ci.20240131T215454+sha.882265627)

Anybody else is free to try as well of course.

zolotovvv · 2024-02-02T18:00:40Z

Hello,

To test this bug we have added integration test. The error is consistently reproduced under fairly high load (hundreds of parallel requests or more).

We have now run this test for build with the specified package version (9.0.0-preview.1-ci.20240131T215454).

Unfortunately, the error is being reproduced.

Message: "Timeout during reading attempt".

at Npgsql.Internal.NpgsqlReadBuffer.<<Ensure>g__EnsureLong|54_0>d.MoveNext()
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource.GetResult(Int16 token)
   at Npgsql.Internal.NpgsqlConnector.<ReadMessageLong>d__233.MoveNext()
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
   at Npgsql.Internal.NpgsqlConnector.<ReadMessageLong>d__233.MoveNext()
   at System.Runtime.CompilerServices.PoolingAsyncValueTaskMethodBuilder`1.StateMachineBox`1.System.Threading.Tasks.Sources.IValueTaskSource<TResult>.GetResult(Int16 token)
   at Npgsql.NpgsqlDataReader.<NextResult>d__52.MoveNext()
   at Npgsql.NpgsqlDataReader.<NextResult>d__52.MoveNext()
   at Npgsql.NpgsqlDataReader.NextResult()
   at Npgsql.NpgsqlCommand.<ExecuteReader>d__119.MoveNext()
   at Npgsql.NpgsqlCommand.<ExecuteReader>d__119.MoveNext()
   at System.Threading.Tasks.ValueTask`1.get_Result()
   at Npgsql.NpgsqlCommand.<ExecuteNonQuery>d__107.MoveNext()
   at Npgsql.NpgsqlCommand.ExecuteNonQuery()
   at Npgsql.NpgsqlBatch.ExecuteNonQuery()
   at Red.WorkPoint.Data.TmConnectionInterceptor.ConnectionOpened(DbConnection connection, ConnectionEndEventData eventData) in D:\repos\backend\Red.WorkPoint.Data\Data\TmConnectionInterceptor.cs:line 22
   at Microsoft.EntityFrameworkCore.Diagnostics.Internal.RelationalConnectionDiagnosticsLogger.ConnectionOpened(IRelationalConnection connection, DateTimeOffset startTime, TimeSpan duration)
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.OpenInternal(Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.Storage.RelationalConnection.Open(Boolean errorsExpected)
   at Microsoft.EntityFrameworkCore.Storage.RelationalCommand.ExecuteReader(RelationalCommandParameterObject parameterObject)
   at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.InitializeReader(Enumerator enumerator)
   at Microsoft.EntityFrameworkCore.Query.Internal.SingleQueryingEnumerable`1.Enumerator.<>c.<MoveNext>b__21_0(DbContext _, Enumerator enumerator)
   at Npgsql.EntityFrameworkCore.PostgreSQL.Storage.Internal.NpgsqlExecutionStrategy.Execute[TState,TResult](TState state, Func`3 operation, Func`3 verifySucceeded)

vonzshik · 2024-02-02T18:04:19Z

@zolotovvv It does makes sense that you can repro something like that under high load because the database itself will also be under high load and in turn that makes it so queries take longer to complete.

NinoFloris · 2024-02-02T18:05:08Z

@zolotovvv that is not the same issue, please create a new issue with its own runnable repro.

EF does not use CommandBehavior.Sequential, which Dapper does and where our fixes have been targeted.

kae · 2024-02-02T18:11:26Z

@kae would you mind running the latest ci build from myget to see if things are working correctly for you? (https://www.myget.org/feed/npgsql-vnext/package/nuget/Npgsql/9.0.0-preview.1-ci.20240131T215454+sha.882265627)

Checked with repro
there were no issues with "9.0.0-preview.1-ci.20240131T215454" and stable reproduction with "8.0.1"

mjauernig · 2024-02-08T21:45:49Z

I ran some tests. It looks good, the problem seems to be gone.

Thanks.

yunfandev changed the title ~~System.InvalidOperationException: The reader is closed~~ System.InvalidOperationException: The reader is closed 8.0.0 Nov 21, 2023

yunfandev changed the title ~~System.InvalidOperationException: The reader is closed 8.0.0~~ System.InvalidOperationException: The reader is closed - 8.0.0 Nov 21, 2023

NinoFloris mentioned this issue Nov 22, 2023

Fix sequential buffered seek #5440

Merged

NinoFloris self-assigned this Nov 24, 2023

NinoFloris added the bug label Nov 24, 2023

NinoFloris added this to the 8.0.1 milestone Nov 24, 2023

yunfandev closed this as completed Dec 1, 2023

yunfandev reopened this Dec 5, 2023

NinoFloris mentioned this issue Dec 7, 2023

Fix another sequential buffered seek exit state issue #5486

Merged

NinoFloris mentioned this issue Dec 21, 2023

8.0 pgreader getting confused over field size #5468

Closed

yunfandev changed the title ~~System.InvalidOperationException: The reader is closed - 8.0.0~~ Npgsql.NpgsqlException (0x80004005): Exception while reading from stream - 8.0.0 Jan 19, 2024

NinoFloris closed this as completed in dffa843 Jan 24, 2024

NinoFloris added a commit that referenced this issue Jan 31, 2024

Fix another sequential buffered seek exit state issue (#5486)

85ed424

Fixes #5430 (cherry picked from commit dffa843) # Conflicts: # src/Npgsql/NpgsqlDataReader.cs

NinoFloris modified the milestones: 8.0.1, 8.0.2 Jan 31, 2024

NinoFloris mentioned this issue Feb 6, 2024

System.InvalidOperationException: The reader is closed .NET 8 #5560

Closed

mjauernig mentioned this issue Feb 10, 2024

Random Timeouts #5569

Closed

cjlotz mentioned this issue Mar 9, 2024

InvalidCastException: Multiple constructor parameters are mapped for Composite Types #5614

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Npgsql.NpgsqlException (0x80004005): Exception while reading from stream - 8.0.0 #5430

Npgsql.NpgsqlException (0x80004005): Exception while reading from stream - 8.0.0 #5430

yunfandev commented Nov 21, 2023 •

edited

NinoFloris commented Nov 21, 2023

yunfandev commented Nov 21, 2023 •

edited

yunfandev commented Nov 21, 2023

NinoFloris commented Nov 21, 2023

yunfandev commented Nov 22, 2023

NinoFloris commented Nov 29, 2023

yunfandev commented Nov 30, 2023

yunfandev commented Dec 1, 2023

yunfandev commented Dec 5, 2023

NinoFloris commented Dec 5, 2023

vonzshik commented Dec 5, 2023

yunfandev commented Dec 5, 2023

kae commented Dec 7, 2023 •

edited

NinoFloris commented Dec 7, 2023

Skayloo commented Dec 29, 2023 •

edited

NinoFloris commented Jan 17, 2024

roji commented Jan 18, 2024

niklasweimann commented Jan 18, 2024

mjauernig commented Jan 29, 2024

kamisoft-fr commented Jan 31, 2024 •

edited

roji commented Jan 31, 2024

NinoFloris commented Jan 31, 2024

NinoFloris commented Jan 31, 2024

zolotovvv commented Feb 2, 2024

vonzshik commented Feb 2, 2024

NinoFloris commented Feb 2, 2024

kae commented Feb 2, 2024 •

edited

mjauernig commented Feb 8, 2024

Npgsql.NpgsqlException (0x80004005): Exception while reading from stream - 8.0.0 #5430

Npgsql.NpgsqlException (0x80004005): Exception while reading from stream - 8.0.0 #5430

Comments

yunfandev commented Nov 21, 2023 • edited

The issue

Further technical details

NinoFloris commented Nov 21, 2023

yunfandev commented Nov 21, 2023 • edited

yunfandev commented Nov 21, 2023

NinoFloris commented Nov 21, 2023

yunfandev commented Nov 22, 2023

NinoFloris commented Nov 29, 2023

yunfandev commented Nov 30, 2023

yunfandev commented Dec 1, 2023

yunfandev commented Dec 5, 2023

NinoFloris commented Dec 5, 2023

vonzshik commented Dec 5, 2023

yunfandev commented Dec 5, 2023

kae commented Dec 7, 2023 • edited

NinoFloris commented Dec 7, 2023

Skayloo commented Dec 29, 2023 • edited

NinoFloris commented Jan 17, 2024

roji commented Jan 18, 2024

niklasweimann commented Jan 18, 2024

mjauernig commented Jan 29, 2024

kamisoft-fr commented Jan 31, 2024 • edited

roji commented Jan 31, 2024

NinoFloris commented Jan 31, 2024

NinoFloris commented Jan 31, 2024

zolotovvv commented Feb 2, 2024

vonzshik commented Feb 2, 2024

NinoFloris commented Feb 2, 2024

kae commented Feb 2, 2024 • edited

mjauernig commented Feb 8, 2024

yunfandev commented Nov 21, 2023 •

edited

yunfandev commented Nov 21, 2023 •

edited

kae commented Dec 7, 2023 •

edited

Skayloo commented Dec 29, 2023 •

edited

kamisoft-fr commented Jan 31, 2024 •

edited

kae commented Feb 2, 2024 •

edited