C#

using \d n regexes does not perform as expected, and in many cases [0-9] should be preferred (as discovered here).

• Review existing uses of \d and replace with [0-9] where appropriate
• Consider adding this to the docs somewhere. Not sure where this would be appropriate to document, perhaps some discussion

What's the issue you encountered?

Fire Emblem: Three Houses is a single-player game, but it has several asynchronous multiplayer features. Among them is the possibility, during weekly planning scenes (the 'calendar' screen), to look up what other players have done on the current week. This is entirely reliant on Nintendo's servers and completely useless to anyone playing on Ryujinx, but eve

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

Describe the Bug

Sending invalid GUIDs to API endpoints will cause them to return an error code "500 Internal Server Error".

Steps To Reproduce

1. HTTP DELETE to API endpoint such as /api/emergency-access/ with invalid GUID like "asd"

Expected Result

Endpoint returns a "400 Bad Request"

Actual Result

Endpoint returns a "500 Internal Server Error"

Environment

What's the Problem?

It is not any type of problem.

Solution/Idea

This project is currently missing the Code of Conduct. If you have any plan on adding that then I would be more than glad to do that for you by adding a PR for that. Please let me know what do you think about that.

Alternatives

According to Google:

A code of conduct defines standards for how to eng

{
  "$schema": "http://json-schema.org/draft-07/schema#",
  "$ref": "#/definitions/foo",
  "definitions": {
    "foo": {
      "type": "object",
      "properties": {
        "bar": {
          "$ref": "bar.json#"
        },
      },
      "required": [
        "bar"
      ],
    },
    "title": "foo"
  }
}

Running quicktype CLI with this Schema produces

Error

Various characters (e.g. |) if used in a Params will end up invalidating the generated markdown, causing it to render incorrectly. It'd be helpful if benchmarkdotnet could escape the markdown output, e.g. output \| instead of |.