.NET

Right now these tests don't run if it's close to midnight, so that they don't have to account for the file number wrapping back to 0 in the middle of test execution. This also means we don't have any tests that verify that file names/numbers behave correctly on the new day boundary. We should mock the system clock like SignalR does so we can test his behavior: https://github.com/dotnet/aspnetcore/

facebook/react-native@1d92454 Adds 2 new events to <Text> - onPressin/onPressOut. We could add them too.

Describe the bug

The current implementation of the authorization header parsing has (at least) the following issues:

• A value can't contain any commas
• A value can't start or end with a doublequote
• A value can't contain special characters
  • HTTP Headers only allow ASCII characters
  • There is no option to encode/decode the values (using base64 or urlencoding)
• When a value c

We can build much smaller Mono runtime for .NET Core purposes by simply removing code we don't need in this configuration. We did a few easy initial steps but we can go much further.

This list is not comprehensive but parts like

• Culture Data
• Any PAL related code
• Unused icalls

Bug Report

Ryujinx is not detecting Quotes even though it is defined.

What's the issue you encountered?

Ryujinx is not detecting quotes( ' ) when inputted.

How can the issue be reproduced?

You can first encounter this issue in the Input configuration where it won't detect quotes when reassigning keys.

Log file

No Log

Environment?

• Ryujinx version: 1.0.0

Whenever I submit a GET request to the api/public/groups endpoint, the "collections" field for each group returns "None" on every group, even if they have access to collections. I can verify that the

Remove logging line, or modify from ch.Info to ch.Trace:
https://github.com/dotnet/machinelearning/blob/5dbfd8acac0bf798957eea122f1413209cdf07dc/src/Microsoft.ML.Mkl.Components/SymSgdClassificationTrainer.cs#L813

For my text dataset, this logging line dumps ~100 pages of floats to my console. That level of verbosity is unneeded at the Info level.

I'd recommend just removing the loggin

The original issue was reported in dotnet/performance#1701:

// Benchmark Process Environment Information:
// Runtime=.NET 6.0.0 (6.0.21.11801), X64 RyuJIT
// GC=Concurrent Workstation
// Job: Job-AQTFSE(PowerPlanMode=00000000-0000-0000-0000-000000000000, IterationTime=250.0000 ms, MaxIterationCount=20, MinIterationCount=15, WarmupCount=1)

OverheadJitting