StringEpsilon

@MihaPro-CarX Just to confirm there: Are you experiencing **a memory leak** or are you seeing that kind of allocation as a baseline that does not meaningfully and permanently increase as...

@SuperMB I believe the elevated baseline memory should get it's own separate issue. I just so happen to be in the middle of refactoring a bunch of stuff and I...

I have found a new way to reproduce a proper memory leak: Formatting a source document ever so slightly increases the total memory for the LSP process, even if the...

https://github.com/dotnet/razor/issues/6241

@tmat I have only had that happen once so far from changes in the .git directory, which was when I was testing the reproduction steps for this issue. If I...

I just happened upon a commit that seems to trigger the hot reload failure reliably: ``` dotnet watch ⌚ Ignoring file updated during build: '/[redacted]/wwwroot/templates/yar2.css' (1601-01-01 00:00:00.0000000,1601-01-01 00:00:00.0000000 < 2024-10-19...

> Hot Reload doesn't currently support updating assembly level attributes, so this error is expected. That is extremely inconvenient. Is there a workaround? (Now that I know this, it explains...

Thank you very much. That fixes the hot reload breaking. Not sure how I overlooked the breaking changes article or failed to find it when I investigated the issue.

I spotted this bug independently and found ladybird behaves the same as Firefox if instead of setting `min-height`, `height` is set. Ladybird also behaves the same when setting `flex-direction: row`...