You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Runtime logs to stderr if libgssapi_krb5 is not available #126251
Npgsql 10 started to use GSSAPI encryption for PostgreSQL by default . Npgsql will always try to use GSSAPI first and then fall back to another mechanism if it's not available.
If libgssapi_krb5 is not available on the system (like in the default chiseled containers) this unfortunately causes the runtime to write an error to stderr:
Cannot load library libgssapi_krb5.so.2
Error: libgssapi_krb5.so.2: cannot open shared object file: No such file or directory
This causes some confusion since you get an error on stderr that isn't actually a problem. Would it be an option for the runtime to just not log this message? Since the caller must deal with the TypeInitializationException anyway, I'm not sure this is even needed.
Activity
dotnet-policy-service commentedon Mar 28, 2026
Tagging subscribers to this area: @agocke, @jeffschwMSFT, @elinor-fung
See info in area-owners.md if you want to be subscribed.
dotnet-policy-service commentedon Mar 28, 2026
Tagging subscribers to this area: @karelz, @dotnet/ncl
See info in area-owners.md if you want to be subscribed.
wfurt commentedon Mar 28, 2026
It would make sense to me. we should emit .NET event IMHO.
dotnet-policy-service commentedon Mar 30, 2026
Tagging subscribers to this area: @dotnet/ncl, @bartonjs, @vcsjones
See info in area-owners.md if you want to be subscribed.
Remove stderr logging in GSSAPI initialization (dotnet#126647)
Remove stderr logging in GSSAPI initialization (#126647)