Revert "Merge branch 'main' into vector-additional-methods"

This reverts commit 20f7b30, reversing
changes made to 1ebb378.

.config/dotnet-tools.json

@@ -15,7 +15,7 @@
       ]
     },
     "microsoft.dotnet.xharness.cli": {
-      "version": "9.0.0-prerelease.24161.1",
+      "version": "9.0.0-prerelease.24112.4",
       "commands": [
         "xharness"
       ]

.devcontainer/Dockerfile

@@ -25,5 +25,4 @@ RUN apt-get update && export DEBIAN_FRONTEND=noninteractive \
         libssl-dev \
         libkrb5-dev \
         zlib1g-dev \
-        ninja-build \
-        tzdata
+        ninja-build

.devcontainer/scripts/onCreateCommand.sh

@@ -2,26 +2,6 @@
 
 set -e
 
-function wasm_common() {
-    # prebuild for WASM, so it is ready for wasm development
-    make -C src/mono/browser provision-wasm
-    export EMSDK_PATH=$PWD/src/mono/browser/emsdk
-    case "$1" in
-    wasm)
-        # Put your common commands for wasm here
-        ./build.sh mono+libs -os browser -c Release
-        ;;
-    wasm-multithreaded)
-        # Put your common commands for wasm-multithread here
-        ./build.sh mono+libs -os browser -c Release /p:WasmEnableThreads=true
-        ;;
-    *)
-        # install dotnet-serve for running wasm samples
-    ./dotnet.sh tool install dotnet-serve --version 1.10.172 --tool-path ./.dotnet-tools-global
-    ;;
-    esac
-}
-
 opt=$1
 case "$opt" in
 
@@ -40,11 +20,13 @@ case "$opt" in
     ;;
 
     wasm)
-        wasm_common $opt
-    ;;
+        # prebuild for WASM, so it is ready for wasm development
+        make -C src/mono/browser provision-wasm
+        export EMSDK_PATH=$PWD/src/mono/browser/emsdk
+        ./build.sh mono+libs -os browser -c Release
 
-    wasm-multithreaded)
-        wasm_common $opt
+        # install dotnet-serve for running wasm samples
+        ./dotnet.sh tool install dotnet-serve --version 1.10.172 --tool-path ./.dotnet-tools-global
     ;;
 esac
 

.devcontainer/wasm/devcontainer.json

@@ -1,6 +1,6 @@
 // For format details, see https://aka.ms/devcontainer.json.
 {
-	"name": "WASM singlethreaded development (prebuilt)",
+	"name": "WASM development (prebuilt)",
 	"build": {
 		"dockerfile": "Dockerfile",
 		"args": {

.github/CODEOWNERS

@@ -21,7 +21,7 @@
 
 /src/mono @marek-safar
 
-/src/mono/llvm @vargaz @steveisok
+/src/mono/llvm @vargaz @SamMonoRT
 
 /src/mono/mono/arch @vargaz
 /src/mono/mono/eglib @vargaz @lambdageek
@@ -36,7 +36,7 @@
 
 /src/mono/mono/eventpipe @lateralusX @lambdageek
 
-/src/mono/mono/mini @vargaz @lambdageek @steveisok
+/src/mono/mono/mini @vargaz @lambdageek @SamMonoRT
 /src/mono/mono/mini/*cfgdump* @vargaz
 /src/mono/mono/mini/*exceptions* @vargaz @BrzVlad
 /src/mono/mono/mini/*llvm* @vargaz @fanyang-mono
@@ -50,7 +50,7 @@
 /src/mono/mono/mini/*simd* @fanyang-mono
 
 /src/mono/mono/profiler @BrzVlad @lambdageek
-/src/mono/mono/sgen @BrzVlad @lambdageek
+/src/mono/mono/sgen @BrzVlad @lambdageek @SamMonoRT
 
 /src/mono/mono/utils @vargaz @lambdageek
 /src/mono/mono/utils/*-win* @lateralusX @lambdageek
@@ -112,4 +112,4 @@
 # Area ownership and repo automation
 /docs/area-owners.*                                 @jeffhandley
 /docs/issue*.md                                     @jeffhandley
-/.github/policies/                                  @jeffhandley @mkArtakMSFT
+/.github/fabricbot.json                             @jeffhandley

.github/ISSUE_TEMPLATE/04_ci_known_issue.yml

@@ -0,0 +1,32 @@
+name: CI Known Issue Report
+description: Create a known issue directly
+labels: ["blocking-clean-ci","Known Build Error"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        Use this template to report issues currently affecting PR stability, be it build or test failures.
+  - type: textarea
+    id: background
+    attributes:
+      label: Error Blob
+      description: Please identify a clear error string that can help identify future instances of this issue. For more information on how to fill this check our issue triage guidelines at [Failure Analysis](/dotnet/runtime/blob/main/docs/workflow/ci/failure-analysis.md#what-to-do-if-you-determine-the-failure-is-unrelated)
+      value: |
+        ```json
+        {
+          "ErrorMessage": "",
+          "BuildRetry": false,
+          "ErrorPattern": "",
+          "ExcludeConsoleLog": true
+        }
+        ```
+    validations:
+      required: true
+  - type: textarea
+    id: repro-steps
+    attributes:
+      label: Reproduction Steps
+      description: |
+        If possible describe where you observe the issue with links and any other relevant details.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -18,6 +18,3 @@ contact_links:
   - name: Issue with WPF
     url:  https://github.com/dotnet/wpf/issues/new/choose
     about: Please open issues relating to WPF in dotnet/wpf.
-  - name: CI Known Issue Report
-    url: https://helix.dot.net/BuildAnalysis/CreateKnownIssues
-    about: Use the helper to create a Known Issue in CI if failures in your runs are unrelated to your change. See [Failure Analysis](https://github.com/dotnet/runtime/blob/main/docs/workflow/ci/failure-analysis.md#what-to-do-if-you-determine-the-failure-is-unrelated) for triage instructions.