NetherGranite

For example, if you want to be able to do stencil tests in a canvas, you must now say `love.graphics.setCanvas{canvas, stencil = true}`; moonshine will fail if you pass a...

**Is your feature request related to a problem? Please describe.** It is not possible to write extension methods for the builder returned by `.AddMicrosoftIdentityWebApp()` (`MicrosoftIdentityWebAppAuthenticationBuilder`) that configure the OpenID Connect...

Filtering calendar view by open extensions or single value extended properties results in a 500 internal server error response

3

**Describe the bug** If I try to filter calendar view by the `extensions` or `singleValueExtendedProperties` collections, I get an error response with code `ErrorInternalServerError` and message `An internal server error...

Incorrect syntax exception with generate-changelog if using single quotes in table names in a database with many tables with SQL Server

1

### Search first - [X] I searched and no similar issues were found ### Description This is potentially a revival of #3825. Having a single quote in a table name...

generate-changelog --replace-if-exists-types default not respected for .mssql.sql

6

### Search first - [X] I searched and no similar issues were found ### Description `generate-changelog` by default sets `--replace-if-exists-types` to `` according to the [documentation](https://docs.liquibase.com/commands/inspection/generate-changelog.html). However, when using a...

Scopes not being included by default in the OpenTelemetry distro may be insufficiently documented

2

Looking at [this comment](https://github.com/Azure/azure-sdk-for-net/issues/42177#issuecomment-1996055961_), it sounds like there was intent to document the fact that using the OpenTelemetry distro for Azure Monitor doesn't include scopes by default was going to...

Don't marshal async continuations to the captured context

2

Currently, `async`/`await` continuations and `Task.ContinueWith(...)` continuations are marshalled back to the captured context (`TaskScheduler` or `SynchronizationContext`) as is the default behavior with these tools. I believe there is no reason...