UliPlabst comments

Results 10 comments of


                                            UliPlabst

StableDiffusion.inpaint API polish

Did anybody investigate where the issue with the 8px boundary comes from?

Nullable object must have a value thrown for a query with DefaultIfEmpty()

I have the same exception using a simple group by statement, I think the root cause might be the same. You can run this in roslyn pad to reproduce. ```cs...

No coercion operator is defined between types 'System.IO.MemoryStream' and 'System.Nullable`1[System.Text.Json.JsonElement]'

I'm running in the same issue. I have a minimal repro [here](https://github.com/UliPlabst/ngpsql_jsonelement_issue_repro) for you. I have my postgres up and running on localhost:5432 with user **posgres.**. My password is in...

No coercion operator is defined between types 'System.IO.MemoryStream' and 'System.Nullable`1[System.Text.Json.JsonElement]'

In my case I'm sure that it worked in Npgsql 7.

No coercion operator is defined between types 'System.IO.MemoryStream' and 'System.Nullable`1[System.Text.Json.JsonElement]'

I just tried to apply a workaround based on @taspeotis suggestion of the underlying issue. I can now confirm that applying a custom IPropertyAddedConvention fixed the issue in my reproduction...

No coercion operator is defined between types 'System.IO.MemoryStream' and 'System.Nullable`1[System.Text.Json.JsonElement]'

Fyi I confirmed today, the workaround is working for my project

Cannot View the Source Code Definitions of csproj ProjectReference Include

I'm running into the same issue as well. I have a solution file containing all projects so I don't know why go to reference is not working. Additionally if I...

Strange inlining behavior of TomlTable when serializing

I looked into supporting my use-case but as it turns out TOML has a lot of ambiguity in it's grammar in how the same thing (like an object) can be...

With "enableAnalyzersSupport': true, `System.InvalidOperationException: Unable to load Microsoft.Extensions.Logging.Generators`

Related [#6718](https://github.com/dotnet/vscode-csharp/issues/6718) and #2627 . Analyzers and omnisharp have been broken forever. We **really** need a fix for this. There is a workaround: ```false``` in csproj but this disables all...

Failed to handle request textDocument/codeAction, Unable to load Microsoft.Extensions.Logging.Generators

I am running into the same issue... Can only fix it with adding ``` false ``` under PropertyGroup in csproj. This will disable all analyzers though and I need them...