helloadhavan/github_issues huggingface dataset:
Repository: facebook/react
Pull request: [ci] Rename temporary build parts

Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom):
* #30388
* #30387
* #30380
* #30376
* #30375
* #30374
* __->__ #30385

Adds an _ prefix to temporary build parts from parallelization to allow
easier merging in later passes.

Changed files:
filename: .github/workflows/runtime_build_and_test.yml
patch: @@ -180,9 +180,8 @@ jobs:
       - name: Archive build
         uses: actions/upload-artifact@v4
         with:
-          name: build_${{ matrix.worker_id }}_${{ matrix.release_channel }}
-          path: |
-            build
+          name: _build_${{ matrix.worker_id }}_${{ matrix.release_channel }}
+          path: build
 
   test_build:
     name: yarn test-build
@@ -242,6 +241,7 @@ jobs:
       - name: Restore archived build
         uses: actions/download-artifact@v4
         with:
+          pattern: _build_*
           path: build
           merge-multiple: true
       - name: Display structure of build
@@ -269,6 +269,7 @@ jobs:
       - name: Restore archived build
         uses: actions/download-artifact@v4
         with:
+          pattern: _build_*
           path: build
           merge-multiple: true
       - name: Display structure of build
@@ -311,6 +312,7 @@ jobs:
       - name: Restore archived build
         uses: actions/download-artifact@v4
         with:
+          pattern: _build_*
           path: build
           merge-multiple: true
       - name: Display structure of build
@@ -341,6 +343,7 @@ jobs:
       - name: Restore archived build
         uses: actions/download-artifact@v4
         with:
+          pattern: _build_*
           path: build
           merge-multiple: true
       - name: Display structure of build
@@ -370,6 +373,7 @@ jobs:
       - name: Restore archived build
         uses: actions/download-artifact@v4
         with:
+          pattern: _build_*
           path: build
           merge-multiple: true
       - name: Display structure of build
@@ -407,6 +411,7 @@ jobs:
       - name: Restore archived build
         uses: actions/download-artifact@v4
         with:
+          pattern: _build_*
           path: build
           merge-multiple: true
       - name: Display structure of build
@@ -462,6 +467,7 @@ jobs:
       - name: Restore archived build
         uses: actions/download-artifact@v4
         with:
+          pattern: _build_*
           path: build
           merge-multiple: true
       - run: ./scripts/circleci/pack_and_store_devtools_artifacts.sh
@@ -507,6 +513,7 @@ jobs:
       - name: Restore archived build
         uses: actions/download-artifact@v4
         with:
+          pattern: _build_*
           path: build
           merge-multiple: true
       - run: |
Repository: nodejs/node
Pull request: doc: add missing Zstd strategy constants

Documents the ZSTD_c_strategy parameter and its possible values (ZSTD_fast … ZSTD_btultra2) that were already exposed in zlib.constants but missing from the API docs and added an example for reference.

Fixes: #59290 

Changed files:
filename: doc/api/zlib.md
patch: @@ -750,6 +750,34 @@ The most important options are:
 * `ZSTD_c_compressionLevel`
   * Set compression parameters according to pre-defined cLevel table. Default
     level is ZSTD\_CLEVEL\_DEFAULT==3.
+* `ZSTD_c_strategy`
+  * Select the compression strategy.
+  * Possible values are listed in the strategy options section below.
+
+#### Strategy options
+
+The following constants can be used as values for the `ZSTD_c_strategy`
+parameter:
+
+* `zlib.constants.ZSTD_fast`
+* `zlib.constants.ZSTD_dfast`
+* `zlib.constants.ZSTD_greedy`
+* `zlib.constants.ZSTD_lazy`
+* `zlib.constants.ZSTD_lazy2`
+* `zlib.constants.ZSTD_btlazy2`
+* `zlib.constants.ZSTD_btopt`
+* `zlib.constants.ZSTD_btultra`
+* `zlib.constants.ZSTD_btultra2`
+
+Example:
+
+```js
+const stream = zlib.createZstdCompress({
+  params: {
+    [zlib.constants.ZSTD_c_strategy]: zlib.constants.ZSTD_btultra,
+  },
+});
+```
 
 #### Pledged Source Size
Repository: ollama/ollama
Pull request: Restore locale patch


Changed files:
filename: llm/patches/04-locale.diff
patch: @@ -0,0 +1,13 @@
+diff --git a/llama.cpp b/llama.cpp
+index b27aa272..99372f9c 100644
+--- a/llama.cpp
++++ b/llama.cpp
+@@ -9360,7 +9360,7 @@ struct llm_tokenizer_wpm {
+     }
+ 
+     uint32_t to_lower(uint32_t code) {
+-        static const std::locale locale("en_US.UTF-8");
++        static const std::locale locale("");
+ #if defined(_WIN32)
+         if (code > 0xFFFF) {
+             return code;
Repository: electron/electron
Pull request: ci: change patches stats DataDog metric type to gauge

#### Description of Change

<!--
Thank you for your Pull Request. Please provide a description above and review
the requirements below.

Contributors guide: https://github.com/electron/electron/blob/main/CONTRIBUTING.md
-->

Fixing this as now that they're uploading I can see we need these to be logged as gauge metrics, otherwise showing a monthly view will add up the counts on any given day, which is not what we want. You can manually update the metric type on DataDog's dashboard so I've done that to fix it on that side for now, but we should upload new datapoints as the correct type.

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [x] PR description included and stakeholders cc'd

#### Release Notes

Notes: none <!-- Please add a one-line description for app developers to read in the release notes, or 'none' if no notes relevant to app developers. Examples and help on special cases: https://github.com/electron/clerk/blob/main/README.md#examples -->


Changed files:
filename: script/patches-stats.mjs
patch: @@ -57,7 +57,7 @@ async function main () {
                 value: patchCount
               }
             ],
-            type: 1 // COUNT
+            type: 3 // GAUGE
           },
           {
             metric: 'electron.patches.lineCount',
@@ -67,7 +67,7 @@ async function main () {
                 value: patchesLineCount
               }
             ],
-            type: 1 // COUNT
+            type: 3 // GAUGE
           }
         ]
       })
Repository: vercel/next.js
Pull request: Turbopack: Use `RawValue` for `mappings` inside `SourceMapJson`

Normally `serde_json` has to handle JSON string escaping, which has some overhead. With `Box<RawValue>` it can just memcpy the raw string instead. More ideally we'd use `&RawValue`, but we'd need a `str` instead of a `Rope` to do that.

https://docs.rs/serde_json/latest/serde_json/value/struct.RawValue.html

This works because we don't care about the value of `mappings` here, we just want to make sure it's passed through when the struct is re-serialized.

We use `RawValue` a lot in the `swc-sourcemap` crate: https://github.com/swc-project/swc-sourcemap/blob/main/src/lazy/mod.rs

Closes PACK-5569

Changed files:
filename: turbopack/crates/turbopack-core/Cargo.toml
patch: @@ -30,7 +30,7 @@ rustc-hash = { workspace = true }
 regex = { workspace = true }
 serde = { workspace = true, features = ["rc"] }
 serde_bytes = { workspace = true }
-serde_json = { workspace = true, features = ["preserve_order"] }
+serde_json = { workspace = true, features = ["preserve_order", "raw_value"] }
 smallvec = { workspace = true }
 swc_sourcemap = { workspace = true }
 swc_core = { workspace = true, features = ["ecma_preset_env", "common"] }

filename: turbopack/crates/turbopack-core/src/source_map/utils.rs
patch: @@ -60,7 +60,10 @@ struct SourceMapJson {
     sources_content: Option<Vec<Option<String>>>,
     #[serde(skip_serializing_if = "Option::is_none")]
     names: Option<Vec<String>>,
-    mappings: String,
+    // We just need to hold onto `mappings` for serialization/deserialization, so there's no point
+    // in decoding/encoding the string. Store it as a `RawValue`. Ideally this would be a reference
+    // to the RawValue, but we deserialize using `from_reader`, which does not support that.
+    mappings: Box<serde_json::value::RawValue>,
     #[serde(skip_serializing_if = "Option::is_none")]
     ignore_list: Option<Vec<u32>>,
Repository: electron/electron
Pull request: ci: add a problem matcher for ESLint output

Backport of #47303

See that PR for details.


Notes: none <!-- Please add a one-line description for app developers to read in the release notes, or 'none' if no notes relevant to app developers. Examples and help on special cases: https://github.com/electron/clerk/blob/main/README.md#examples -->


Changed files:
filename: .github/problem-matchers/eslint-stylish.json
patch: @@ -0,0 +1,22 @@
+{
+  "problemMatcher": [
+    {
+      "owner": "eslint-stylish",
+      "pattern": [
+        {
+          "regexp": "^\\s*([^\\s].*)$",
+          "file": 1
+        },
+        {
+          "regexp": "^\\s+(\\d+):(\\d+)\\s+(error|warning|info)\\s+(.*)\\s\\s+(.*)$",
+          "line": 1,
+          "column": 2,
+          "severity": 3,
+          "message": 4,
+          "code": 5,
+          "loop": true
+        }
+      ]
+    }
+  ]
+}

filename: .github/workflows/pipeline-electron-lint.yml
patch: @@ -62,6 +62,9 @@ jobs:
         curl -sL "https://chromium.googlesource.com/chromium/src/+/${chromium_revision}/buildtools/DEPS?format=TEXT" | base64 -d > src/buildtools/DEPS
 
         gclient sync --spec="solutions=[{'name':'src/buildtools','url':None,'deps_file':'DEPS','custom_vars':{'process_deps':True},'managed':False}]"
+    - name: Add ESLint problem matcher
+      shell: bash
+      run: echo "::add-matcher::src/electron/.github/problem-matchers/eslint-stylish.json"
     - name: Run Lint
       shell: bash
       run: |
Repository: facebook/react
Pull request: [ci][ez] Rename artifact from process_artifacts_combined

Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom):
* __->__ #30364

Build artifacts are uniquely associated to a single workflow run, so
appending the sha was unnecessary. I originally included it to make it
easier to download later but this turns out to be unneeded.

Drops the sha suffix to make downloading the artifact in a separate
script / workflow more straightforward.

Changed files:
filename: .github/workflows/runtime_build_and_test.yml
patch: @@ -285,7 +285,7 @@ jobs:
       - name: Archive build artifacts
         uses: actions/upload-artifact@v4
         with:
-          name: combined_artifacts_${{ github.sha }}
+          name: artifacts_combined
           path: |
             ./build.tgz
             ./build2.tgz
Repository: electron/electron
Pull request: ci: add a problem matcher for ESLint output

#### Description of Change

<!--
Thank you for your Pull Request. Please provide a description above and review
the requirements below.

Contributors guide: https://github.com/electron/electron/blob/main/CONTRIBUTING.md
-->

Will catch errors like the lint failure currently on `main`. This is taken verbatim from https://github.com/actions/setup-node/blob/49933ea5288caeca8642d1e84afbd3f7d6820020/.github/eslint-stylish.json, which is automatically injected for jobs using `actions/setup-node`, but we usually use the Node.js version on our runners, and specifically our lint job does not use `actions/setup-node`.

#### Checklist
<!-- Remove items that do not apply. For completed items, change [ ] to [x]. -->

- [x] PR description included and stakeholders cc'd

#### Release Notes

Notes: none <!-- Please add a one-line description for app developers to read in the release notes, or 'none' if no notes relevant to app developers. Examples and help on special cases: https://github.com/electron/clerk/blob/main/README.md#examples -->


Changed files:
filename: .github/problem-matchers/eslint-stylish.json
patch: @@ -0,0 +1,22 @@
+{
+  "problemMatcher": [
+    {
+      "owner": "eslint-stylish",
+      "pattern": [
+        {
+          "regexp": "^\\s*([^\\s].*)$",
+          "file": 1
+        },
+        {
+          "regexp": "^\\s+(\\d+):(\\d+)\\s+(error|warning|info)\\s+(.*)\\s\\s+(.*)$",
+          "line": 1,
+          "column": 2,
+          "severity": 3,
+          "message": 4,
+          "code": 5,
+          "loop": true
+        }
+      ]
+    }
+  ]
+}

filename: .github/workflows/pipeline-electron-lint.yml
patch: @@ -62,6 +62,9 @@ jobs:
         curl -sL "https://chromium.googlesource.com/chromium/src/+/${chromium_revision}/buildtools/DEPS?format=TEXT" | base64 -d > src/buildtools/DEPS
 
         gclient sync --spec="solutions=[{'name':'src/buildtools','url':None,'deps_file':'DEPS','custom_vars':{'process_deps':True},'managed':False}]"
+    - name: Add ESLint problem matcher
+      shell: bash
+      run: echo "::add-matcher::src/electron/.github/problem-matchers/eslint-stylish.json"
     - name: Run Lint
       shell: bash
       run: |
Repository: ggml-org/llama.cpp
Pull request: contrib : stale PRs

Rebasing on top of latest `master` branch keeps the PR up-to-date and sends notifications to people who are subscribed to it -> increasing chances for review

Changed files:
filename: CONTRIBUTING.md
patch: @@ -16,7 +16,7 @@ The project differentiates between 3 levels of contributors:
     - If you modified a `ggml` operator or added a new one, add the corresponding test cases to `test-backend-ops`
 - Create separate PRs for each feature or fix. Avoid combining unrelated changes in a single PR
 - Consider allowing write access to your branch for faster reviews, as reviewers can push commits directly
-- If your PR becomes stale, don't hesitate to ping the maintainers in the comments
+- If your PR becomes stale, rebase it on top of latest `master` to get maintainers attention
 - Maintainers will rely on your insights and approval when making a final decision to approve and merge a PR
 - Consider adding yourself to [CODEOWNERS](CODEOWNERS) to indicate your availability for reviewing related PRs
 - Using AI to generate PRs is permitted. However, you must (1) explicitly disclose how AI was used and (2) conduct a thorough manual review before publishing the PR. Note that trivial tab autocompletions do not require disclosure.
Repository: nodejs/node
Pull request: test: update WPT for WebCryptoAPI to ff26d9b307

This is an automated update of the WPT for WebCryptoAPI to https://github.com/web-platform-tests/wpt/commit/ff26d9b307b981b3f1b88f454268e6bb8933e6c2.

Changed files:
filename: test/fixtures/wpt/README.md
patch: @@ -34,7 +34,7 @@ Last update:
 - wasm/jsapi: https://github.com/web-platform-tests/wpt/tree/cde25e7e3c/wasm/jsapi
 - wasm/webapi: https://github.com/web-platform-tests/wpt/tree/fd1b23eeaa/wasm/webapi
 - web-locks: https://github.com/web-platform-tests/wpt/tree/10a122a6bc/web-locks
-- WebCryptoAPI: https://github.com/web-platform-tests/wpt/tree/1d2c5fb36a/WebCryptoAPI
+- WebCryptoAPI: https://github.com/web-platform-tests/wpt/tree/ff26d9b307/WebCryptoAPI
 - webidl/ecmascript-binding/es-exceptions: https://github.com/web-platform-tests/wpt/tree/2f96fa1996/webidl/ecmascript-binding/es-exceptions
 - webmessaging/broadcastchannel: https://github.com/web-platform-tests/wpt/tree/6495c91853/webmessaging/broadcastchannel
 - webstorage: https://github.com/web-platform-tests/wpt/tree/1d2c5fb36a/webstorage

filename: test/fixtures/wpt/WebCryptoAPI/import_export/okp_importKey_failures_fixtures.js
patch: @@ -432,7 +432,7 @@ var mismatchedKtyField =  {
 // The 'kty' field doesn't match the key algorithm.
 var mismatchedCrvField =  {
     "Ed25519": "X25519",
-    "X25519": "Ed448",
-    "Ed448": "X25519",
-    "X448": "Ed25519",
+    "X25519": "Ed25519",
+    "Ed448": "X448",
+    "X448": "Ed448",
 }

filename: test/fixtures/wpt/versions.json
patch: @@ -96,7 +96,7 @@
     "path": "web-locks"
   },
   "WebCryptoAPI": {
-    "commit": "1d2c5fb36a6e477c8f915bde7eca027be6abe792",
+    "commit": "ff26d9b307b981b3f1b88f454268e6bb8933e6c2",
     "path": "WebCryptoAPI"
   },
   "webidl/ecmascript-binding/es-exceptions": {
Repository: ollama/ollama
Pull request: warn when json format is expected but not mentioned in prompt

This is a complimentary PR to #3080 

If `format: json` is specified but the prompt makes no mention of JSON log a warning. This is a lenient, rather than rejecting the request.

Changed files:
filename: llm/dyn_ext_server.go
patch: @@ -198,6 +198,9 @@ func (llm *dynExtServer) Predict(ctx context.Context, predict PredictOpts, fn fu
 
 	if predict.Format == "json" {
 		request["grammar"] = jsonGrammar
+		if !strings.Contains(strings.ToLower(predict.Prompt), "json") {
+			slog.Warn("Prompt does not specify that the LLM should response in JSON, but JSON format is expected. For best results specify that JSON is expected in the system prompt.")
+		}
 	}
 
 	retryDelay := 100 * time.Microsecond
Repository: facebook/react
Pull request: [compiler] Show outlined functions in logging, playground

Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom):
* __->__ #30344
* #30332
* #30331
* #30330
* #30329
* #30328

Updates focus mode logging and playground to show outlined functions at each step:

<img width="1723" alt="Screenshot 2024-07-16 at 12 07 59 PM" src="https://github.com/user-attachments/assets/5425e430-93ee-47e3-b45e-b67d3f7ade00">


Changed files:
filename: compiler/apps/playground/components/Editor/EditorImpl.tsx
patch: @@ -42,6 +42,8 @@ import {
   default as Output,
   PrintedCompilerPipelineValue,
 } from "./Output";
+import { printFunctionWithOutlined } from "babel-plugin-react-compiler/src/HIR/PrintHIR";
+import { printReactiveFunctionWithOutlined } from "babel-plugin-react-compiler/src/ReactiveScopes/PrintReactiveFunction";
 
 function parseInput(input: string, language: "flow" | "typescript") {
   // Extract the first line to quickly check for custom test directives
@@ -242,7 +244,7 @@ function compile(source: string): [CompilerOutput, "flow" | "typescript"] {
               kind: "hir",
               fnName,
               name: result.name,
-              value: printHIR(result.value.body),
+              value: printFunctionWithOutlined(result.value),
             });
             break;
           }
@@ -251,7 +253,7 @@ function compile(source: string): [CompilerOutput, "flow" | "typescript"] {
               kind: "reactive",
               fnName,
               name: result.name,
-              value: printReactiveFunction(result.value),
+              value: printReactiveFunctionWithOutlined(result.value),
             });
             break;
           }

filename: compiler/packages/babel-plugin-react-compiler/src/ReactiveScopes/CodegenReactiveFunction.ts
patch: @@ -51,7 +51,6 @@ import { buildReactiveFunction } from "./BuildReactiveFunction";
 import { SINGLE_CHILD_FBT_TAGS } from "./MemoizeFbtAndMacroOperandsInSameScope";
 import { ReactiveFunctionVisitor, visitReactiveFunction } from "./visitors";
 import { ReactFunctionType } from "../HIR/Environment";
-import { logReactiveFunction } from "../Utils/logger";
 
 export const MEMO_CACHE_SENTINEL = "react.memo_cache_sentinel";
 export const EARLY_RETURN_SENTINEL = "react.early_return_sentinel";

filename: compiler/packages/babel-plugin-react-compiler/src/ReactiveScopes/PrintReactiveFunction.ts
patch: @@ -31,7 +31,7 @@ export function printReactiveFunctionWithOutlined(
   const writer = new Writer();
   writeReactiveFunction(fn, writer);
   for (const outlined of fn.env.getOutlinedFunctions()) {
-    writer.writeLine("\n" + printFunction(outlined.fn));
+    writer.writeLine("\nfunction " + printFunction(outlined.fn));
   }
   return writer.complete();
 }
Repository: ggml-org/llama.cpp
Pull request: metal : fix build

cont #17766 

Changed files:
filename: examples/save-load-state/save-load-state.cpp
patch: @@ -241,6 +241,12 @@ int main(int argc, char ** argv) {
 
     llama_batch_free(batch);
 
+    // this one is managed by common_init_result
+    //llama_free(ctx);
+
+    llama_free(ctx2);
+    llama_free(ctx3);
+
     if (result0 != result2) {
         fprintf(stderr, "\n%s : error : the seq restore generation is different\n", __func__);
         return 1;

filename: ggml/src/ggml-metal/ggml-metal-device.m
patch: @@ -574,22 +574,26 @@ ggml_metal_rsets_t ggml_metal_rsets_init(void) {
     // the requests stop after a certain amount of time (keep_alive_s) of inactivity
     dispatch_queue_t d_queue = dispatch_get_global_queue(QOS_CLASS_DEFAULT, 0);
     dispatch_group_async(res->d_group, d_queue, ^{
-          while (!atomic_load_explicit(&res->d_stop, memory_order_relaxed)) {
-              if (atomic_load_explicit(&res->d_loop, memory_order_relaxed) > 0) {
-                  [res->lock lock];
+#if defined(GGML_METAL_HAS_RESIDENCY_SETS)
+        if (@available(macOS 15.0, iOS 18.0, tvOS 18.0, visionOS 2.0, *)) {
+              while (!atomic_load_explicit(&res->d_stop, memory_order_relaxed)) {
+                  if (atomic_load_explicit(&res->d_loop, memory_order_relaxed) > 0) {
+                      [res->lock lock];
 
-                  for (int i = 0; i < (int) res->data.count; ++i) {
-                      [res->data[i] requestResidency];
-                  }
+                      for (int i = 0; i < (int) res->data.count; ++i) {
+                          [res->data[i] requestResidency];
+                      }
 
-                  atomic_fetch_sub_explicit(&res->d_loop, 1, memory_order_relaxed);
+                      atomic_fetch_sub_explicit(&res->d_loop, 1, memory_order_relaxed);
 
-                  [res->lock unlock];
-              }
+                      [res->lock unlock];
+                  }
 
-              // half a second
-              usleep(500 * 1000);
-          }
+                  // half a second
+                  usleep(500 * 1000);
+              }
+        }
+#endif
     });
 
     return res;
@@ -600,6 +604,7 @@ void ggml_metal_rsets_free(ggml_metal_rsets_t rsets) {
         return;
     }
 
+    // note: if you hit this assert, most likely you haven't deallocated all Metal resources before exiting
     GGML_ASSERT([rsets->data count] == 0);
 
     atomic_store_explicit(&rsets->d_stop, true, memory_order_relaxed);
@@ -787,9 +792,6 @@ ggml_metal_device_t ggml_metal_device_init(void) {
                 dev->rsets = nil;
             }
 
-
-            // --------------------------------------------------
-
             // print MTL GPU family:
             GGML_LOG_INFO("%s: GPU name:   %s\n", __func__, dev->props.name);
Repository: vercel/next.js
Pull request: Turbopack: drop ASTs when only tracing

These modules are never codgen-ed, so we can drop the AST after the analysis.

```
before:
analyze ecmascript module [project]/packages/next/dist/compiled/babel-packages/packages-bundle.js [externals-tracing] (ecmascript)
Allocated memory: 274.32MB, Deallocated memory: 250.51MB

after:
analyze ecmascript module [project]/packages/next/dist/compiled/babel-packages/packages-bundle.js [externals-tracing] (ecmascript)
Allocated memory: 273.46MB, Deallocated memory: 271.77MB
```

Closes PACK-5572

Changed files:
filename: turbopack/crates/turbopack-ecmascript/src/references/mod.rs
patch: @@ -401,6 +401,10 @@ impl AnalyzeEcmascriptModuleResultBuilder {
 
         let references: Vec<_> = self.references.into_iter().collect();
 
+        if !self.analyze_mode.is_code_gen() {
+            debug_assert!(self.code_gens.is_empty());
+        }
+
         self.code_gens.shrink_to_fit();
         Ok(AnalyzeEcmascriptModuleResult::cell(
             AnalyzeEcmascriptModuleResult {
@@ -575,7 +579,12 @@ async fn analyze_ecmascript_module_internal(
         .await?;
     }
 
-    let parsed = parsed.await?;
+    let parsed = if !analyze_mode.is_code_gen() {
+        // We are never code-gening the module, so we can drop the AST after the analysis.
+        parsed.final_read_hint().await?
+    } else {
+        parsed.await?
+    };
 
     let ParseResult::Ok {
         program,