helloadhavan/github_issues huggingface dataset:
Repository: denoland/deno
Pull request: tests(node/ext): ignore zlib kmaxlength tests

Deno pre-loads polyfills as ESM, so kMaxLength is a live binding that can't be snapshotted like Node.js CJS require

Ignore 3 node_compat tests:
- test-zlib-kmaxlength-rangeerror
- test-zlib-brotli-kmaxlength-rangeerror
- test-zlib-zstd-kmaxlength-rangeerror


Changed files:
filename: tests/node_compat/config.jsonc
patch: @@ -1595,7 +1595,12 @@
     "parallel/test-zlib-brotli-flush.js": {},
     "parallel/test-zlib-brotli-from-brotli.js": {},
     "parallel/test-zlib-brotli-from-string.js": {},
-    // "parallel/test-zlib-brotli-kmaxlength-rangeerror.js": {},
+    "parallel/test-zlib-brotli-kmaxlength-rangeerror.js": {
+      "darwin": false,
+      "linux": false,
+      "windows": false,
+      "reason": "Deno pre-loads polyfills as ESM, so kMaxLength is a live binding that can't be snapshotted like Node.js CJS require"
+    },
     "parallel/test-zlib-brotli.js": {},
     "parallel/test-zlib-close-after-error.js": {},
     "parallel/test-zlib-close-after-write.js": {},
@@ -1624,7 +1629,12 @@
     "parallel/test-zlib-invalid-arg-value-brotli-compress.js": {},
     // "parallel/test-zlib-invalid-input-memory.js": {},
     "parallel/test-zlib-invalid-input.js": {},
-    // "parallel/test-zlib-kmaxlength-rangeerror.js": {},
+    "parallel/test-zlib-kmaxlength-rangeerror.js": {
+      "darwin": false,
+      "linux": false,
+      "windows": false,
+      "reason": "Deno pre-loads polyfills as ESM, so kMaxLength is a live binding that can't be snapshotted like Node.js CJS require"
+    },
     "parallel/test-zlib-maxOutputLength.js": {},
     "parallel/test-zlib-no-stream.js": {},
     "parallel/test-zlib-not-string-or-buffer.js": {},
@@ -1647,7 +1657,12 @@
     "parallel/test-zlib-zstd-flush.js": {},
     "parallel/test-zlib-zstd-from-string.js": {},
     "parallel/test-zlib-zstd-from-zstd.js": {},
-    // "parallel/test-zlib-zstd-kmaxlength-rangeerror.js": {},
+    "parallel/test-zlib-zstd-kmaxlength-rangeerror.js": {
+      "darwin": false,
+      "linux": false,
+      "windows": false,
+      "reason": "Deno pre-loads polyfills as ESM, so kMaxLength is a live binding that can't be snapshotted like Node.js CJS require"
+    },
     "parallel/test-zlib-zstd-pledged-src-size.js": {},
     "parallel/test-zlib-zstd.js": {},
     "parallel/test-zlib.js": {},
Repository: nodejs/node
Pull request: doc: fix the version tls.DEFAULT_CIPHERS was added

42be7f6a0335c396810be91c3f3724007029f83d (originally included in 19.8.0 and later backported to 18.16.0) added documentation on how to use `tls.DEFAULT_CIPHERS`.
However, that commit added the documentation with the version specified as `REAPLCEME`, causing the published documentation to state that `tls.DEFAULT_CIPHERS` was added in 19.8.0 and 18.16.0, which is incorrect - that commit states that `tls.DEFAULT_CIPHERS` already existed, and the only thing it added was an explanation on how to use it.

In fact, by examining the git log, it can be seen that `tls.DEFAULT_CIPHERS` was added by commit
af80e7bc6e6f33c582eb1f7d37c7f5bbe9f910f7, which was included in 0.11.3.

Fixes: https://github.com/nodejs/node/issues/59246

<!--
Before submitting a pull request, please read:

- the CONTRIBUTING guide at https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md
- the commit message formatting guidelines at
  https://github.com/nodejs/node/blob/HEAD/doc/contributing/pull-requests.md#commit-message-guidelines

For code changes:
1. Include tests for any bug fixes or new features.
2. Update documentation if relevant.
3. Ensure that `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes.

If you believe this PR should be highlighted in the Node.js CHANGELOG
please add the `notable-change` label.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.
-->


Changed files:
filename: doc/api/tls.md
patch: @@ -2427,9 +2427,7 @@ added: v11.4.0
 ## `tls.DEFAULT_CIPHERS`
 
 <!-- YAML
-added:
- - v19.8.0
- - v18.16.0
+added: v0.11.3
 -->
 
 * Type: {string} The default value of the `ciphers` option of
Repository: ollama/ollama
Pull request: patch: use default locale in wpm tokenizer


Changed files:
filename: llm/patches/03-locale.diff
patch: @@ -0,0 +1,13 @@
+diff --git a/llama.cpp b/llama.cpp
+index b19616e8..519b9602 100644
+--- a/llama.cpp
++++ b/llama.cpp
+@@ -9938,7 +9938,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: vercel/next.js
Pull request: Turbopack: increase retry duration, reduce busy looping when there is other work

### What?

The short retry timeout of 10s could lead to false panics. Increasing the retry count to 60s makes it less likely.

There is this case where the job need to wait for another job in the same queue to continue. This is handled by re-enqueuing the job at the end of the queue again. But it's not optimal to spend 1ms in busy waiting initially. So early retries will re-enqueue faster and the busy loop is only used aggressively after a bunch of retries.

Closes PACK-5564

Changed files:
filename: turbopack/crates/turbo-tasks-backend/src/backend/operation/aggregation_update.rs
patch: @@ -1285,7 +1285,7 @@ impl AggregationUpdateQueue {
         let _span = trace_span!("lost follower (n uppers)", uppers = upper_ids.len()).entered();
 
         // see documentation of `retry_loop` for more information why this is needed
-        let result = retry_loop(|| {
+        let result = retry_loop(retry, || {
             let mut follower = ctx.task(
                 lost_follower_id,
                 // For performance reasons this should stay `Meta` and not `All`
@@ -1452,7 +1452,7 @@ impl AggregationUpdateQueue {
         .entered();
 
         // see documentation of `retry_loop` for more information why this is needed
-        let result = retry_loop(|| {
+        let result = retry_loop(retry, || {
             swap_retain(&mut lost_follower_ids, |&mut lost_follower_id| {
                 let mut follower = ctx.task(
                     lost_follower_id,
@@ -2476,7 +2476,7 @@ impl Operation for AggregationUpdateQueue {
 struct RetryTimeout;
 
 const MAX_YIELD_DURATION: Duration = Duration::from_millis(1);
-const MAX_RETRIES: u16 = 10000;
+const MAX_RETRIES: u16 = 60000;
 
 /// Retry the passed function for a few milliseconds, while yielding to other threads.
 /// Returns an error if the function was not able to complete and the timeout was reached.
@@ -2492,13 +2492,17 @@ const MAX_RETRIES: u16 = 10000;
 /// successful, the update is added to the end of the queue again. This is important as the "add"
 /// update might even be in the current thread and in the same queue. If that's the case yielding
 /// won't help and the update need to be requeued.
-fn retry_loop(mut f: impl FnMut() -> ControlFlow<()>) -> Result<(), RetryTimeout> {
+fn retry_loop(mut retry: u16, mut f: impl FnMut() -> ControlFlow<()>) -> Result<(), RetryTimeout> {
     let mut time: Option<Instant> = None;
     loop {
         match f() {
             ControlFlow::Continue(()) => {}
             ControlFlow::Break(()) => return Ok(()),
         }
+        if retry == 0 {
+            return Err(RetryTimeout);
+        }
+        retry -= 1;
         yield_now();
         if let Some(t) = time {
             if t.elapsed() > MAX_YIELD_DURATION {
Repository: facebook/react
Pull request: [ci] Remove DevTools jobs from circleci build_and_test

Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom):
* #30359
* #30358
* #30357
* #30356
* #30355
* #30354
* #30353
* __->__ #30352

Now that these run in GH, we can remove these jobs from the circleci
build_and_test workflow to speed up the remaining jobs left in circleci
since this was the long pole.

I have left the definition of these jobs in tact however, as they are
used for devtools_regression_tests which has yet to be migrated to GH.

Changed files:
filename: .circleci/config.yml
patch: @@ -481,12 +481,6 @@ workflows:
       - RELEASE_CHANNEL_stable_yarn_test_dom_fixtures:
           requires:
             - yarn_build
-      - build_devtools_and_process_artifacts:
-          requires:
-            - yarn_build
-      - run_devtools_e2e_tests:
-          requires:
-            - build_devtools_and_process_artifacts
       - run_fixtures_flight_tests:
           requires:
             - yarn_build
Repository: denoland/deno
Pull request: tests: enable some node child-process tests

Enable these tests:

- parallel/test-child-process-fork-close.js
- parallel/test-child-process-stdin.js

Changed files:
filename: tests/node_compat/config.jsonc
patch: @@ -185,6 +185,7 @@
     "parallel/test-child-process-exit-code.js": {},
     "parallel/test-child-process-flush-stdio.js": {},
     "parallel/test-child-process-fork-and-spawn.js": {},
+    "parallel/test-child-process-fork-close.js": {},
     "parallel/test-child-process-fork-detached.js": {},
     "parallel/test-child-process-fork-no-shell.js": {},
     "parallel/test-child-process-fork-ref.js": {},
@@ -206,6 +207,7 @@
     "parallel/test-child-process-spawnsync-validation-errors.js": {},
     "parallel/test-child-process-spawnsync.js": {},
     "parallel/test-child-process-stdin-ipc.js": {},
+    "parallel/test-child-process-stdin.js": {},
     "parallel/test-child-process-stdio-big-write-end.js": {},
     "parallel/test-child-process-stdio-inherit.js": {},
     "parallel/test-child-process-stdio-overlapped.js": {},
Repository: denoland/deno
Pull request: tests(ext/node): remove typo of double .js


Changed files:
filename: tests/node_compat/config.jsonc
patch: @@ -89,7 +89,7 @@
     "parallel/test-buffer-alloc.js": {},
     "parallel/test-buffer-arraybuffer.js": {},
     "parallel/test-buffer-ascii.js": {},
-    "parallel/test-buffer-backing-arraybuffer.js.js": {
+    "parallel/test-buffer-backing-arraybuffer.js": {
       "darwin": false,
       "linux": false,
       "windows": false,
Repository: ggml-org/llama.cpp
Pull request: vulkan: set all memory allocations to high priority

For #17605, though I'm not sure whether it'll help.

Changed files:
filename: ggml/src/ggml-vulkan/ggml-vulkan.cpp
patch: @@ -519,6 +519,7 @@ struct vk_device_struct {
     bool fp16;
     bool bf16;
     bool pipeline_robustness;
+    bool memory_priority;
     vk::Device device;
     uint32_t vendor_id;
     vk::DriverId driver_id;
@@ -2369,7 +2370,13 @@ static vk_buffer ggml_vk_create_buffer(vk_device& device, size_t size, const std
 
     vk::PhysicalDeviceMemoryProperties mem_props = device->physical_device.getMemoryProperties();
 
-    const vk::MemoryAllocateFlagsInfo mem_flags_info { mem_flags };
+    const vk::MemoryPriorityAllocateInfoEXT mem_priority_info { 1.0f };
+
+    vk::MemoryAllocateFlagsInfo mem_flags_info { mem_flags };
+
+    if (device->memory_priority) {
+        mem_flags_info.setPNext(&mem_priority_info);
+    }
 
     for (auto it = req_flags_list.begin(); it != req_flags_list.end(); it++) {
         const auto & req_flags = *it;
@@ -4340,6 +4347,9 @@ static vk_device ggml_vk_get_device(size_t idx) {
 #endif
             } else if (strcmp("VK_KHR_pipeline_executable_properties", properties.extensionName) == 0) {
                 pipeline_executable_properties_support = true;
+            } else if (strcmp("VK_EXT_memory_priority", properties.extensionName) == 0 &&
+                       getenv("GGML_VK_ENABLE_MEMORY_PRIORITY")) {
+                device->memory_priority = true;
             }
         }
 
@@ -4531,6 +4541,16 @@ static vk_device ggml_vk_get_device(size_t idx) {
             device_extensions.push_back("VK_EXT_pipeline_robustness");
         }
 
+        VkPhysicalDeviceMemoryPriorityFeaturesEXT memory_priority_features;
+        memory_priority_features.pNext = nullptr;
+        memory_priority_features.sType = VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_MEMORY_PRIORITY_FEATURES_EXT;
+        memory_priority_features.memoryPriority = VK_FALSE;
+        if (device->memory_priority) {
+            last_struct->pNext = (VkBaseOutStructure *)&memory_priority_features;
+            last_struct = (VkBaseOutStructure *)&memory_priority_features;
+            device_extensions.push_back("VK_EXT_memory_priority");
+        }
+
         VkPhysicalDeviceSubgroupSizeControlFeaturesEXT subgroup_size_control_features;
         subgroup_size_control_features.pNext = nullptr;
         subgroup_size_control_features.sType = VK_STRUCTURE_TYPE_PHYSICAL_DEVICE_SUBGROUP_SIZE_CONTROL_FEATURES_EXT;
Repository: facebook/react
Pull request: [ez] Add gh actions status badges to readme

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

Update readme with new badges.

Changed files:
filename: .github/workflows/runtime_build_and_test.yml
patch: @@ -349,7 +349,7 @@ jobs:
       - name: Archive devtools build
         uses: actions/upload-artifact@v4
         with:
-          name: react-devtools.tgz
+          name: react-devtools
           path: build/devtools.tgz
       # Simplifies getting the extension for local testing
       - name: Archive chrome extension
Repository: nodejs/node
Pull request: doc: clarify glob's exclude option behavior

Add a note that negation patterns (e.g. `!pattern`) are not supported in the exclude option.

<!--
Before submitting a pull request, please read:

- the CONTRIBUTING guide at https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md
- the commit message formatting guidelines at
  https://github.com/nodejs/node/blob/HEAD/doc/contributing/pull-requests.md#commit-message-guidelines

For code changes:
1. Include tests for any bug fixes or new features.
2. Update documentation if relevant.
3. Ensure that `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes.

If you believe this PR should be highlighted in the Node.js CHANGELOG
please add the `notable-change` label.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.
-->


Changed files:
filename: doc/api/fs.md
patch: @@ -1112,6 +1112,9 @@ changes:
   * `exclude` {Function|string\[]} Function to filter out files/directories or a
     list of glob patterns to be excluded. If a function is provided, return
     `true` to exclude the item, `false` to include it. **Default:** `undefined`.
+    If a string array is provided, each string should be a glob pattern that
+    specifies paths to exclude. Note: Negation patterns (e.g., '!foo.js') are
+    not supported.
   * `withFileTypes` {boolean} `true` if the glob should return paths as Dirents,
     `false` otherwise. **Default:** `false`.
 * Returns: {AsyncIterator} An AsyncIterator that yields the paths of files
Repository: ollama/ollama
Pull request: Rename ROCm deps file to avoid confusion


Changed files:
filename: Dockerfile
patch: @@ -46,7 +46,7 @@ RUN mkdir /tmp/scratch && \
     done && \
     (cd /opt/rocm/lib && tar cf - rocblas/library) | (cd /tmp/scratch/ && tar xf - ) && \
     mkdir -p /go/src/github.com/jmorganca/ollama/dist/deps/ && \
-    (cd /tmp/scratch/ && tar czvf /go/src/github.com/jmorganca/ollama/dist/deps/rocm-amd64-deps.tgz . )
+    (cd /tmp/scratch/ && tar czvf /go/src/github.com/jmorganca/ollama/dist/deps/ollama-linux-amd64-rocm.tgz . )
 
 
 FROM --platform=linux/amd64 centos:7 AS cpu-builder-amd64
Repository: ggml-org/llama.cpp
Pull request: HIP: fix RDNA4 build

Fixes RDNA4 build failure introduced with https://github.com/ggml-org/llama.cpp/pull/17576 .

Changed files:
filename: ggml/src/ggml-cuda/mma.cuh
patch: @@ -560,7 +560,7 @@ namespace ggml_cuda_mma {
                 xi[0] = xs[0];
                 xi[1] = xs[1];
 #endif // defined(RDNA4)
-            }else if constexpr (I == 16 && J == 8) {
+            } else if constexpr (I == 16 && J == 8) {
                 int64_t * xi = (int64_t *) t.x;
 #if defined(RDNA4)
                 const int64_t * xs = (int64_t *) ((const int *) xs0 + (threadIdx.x % t.I) * stride + 4 * (threadIdx.x / t.I));
@@ -577,14 +577,13 @@ namespace ggml_cuda_mma {
                 const int64_t * xs1 = xs + 2;
                 xi[2] = xs1[0];
                 xi[3] = xs1[1];
-
-            }else{
+#endif // defined(RDNA4)
+            } else {
                 NO_DEVICE_CODE;
             }
         } else {
             NO_DEVICE_CODE;
         }
-#endif // defined(RDNA4)
 #else
 #pragma unroll
         for (int l = 0; l < t.ne; ++l) {
Repository: facebook/react
Pull request: [ci] Try sharding test_build

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

The tests for the build currently take about 3.5 minutes and is at the
moment the long pole for the whole workflow. By sharding we can make
this workflow faster and save about a minute or so in overall wall time.

Changed files:
filename: .github/workflows/runtime_build_and_test.yml
patch: @@ -349,7 +349,7 @@ jobs:
       - name: Archive devtools build
         uses: actions/upload-artifact@v4
         with:
-          name: react-devtools.tgz
+          name: react-devtools
           path: build/devtools.tgz
       # Simplifies getting the extension for local testing
       - name: Archive chrome extension
Repository: facebook/react
Pull request: [ci] Add DevTools jobs to gh actions

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

Adds the devtools build and test jobs to GH actions. This is more or
less a straight copy of the jobs from circleci

Changed files:
filename: .github/workflows/runtime_build_and_test.yml
patch: @@ -345,7 +345,7 @@ jobs:
       - name: Archive devtools build
         uses: actions/upload-artifact@v4
         with:
-          name: react-devtools.tgz
+          name: react-devtools
           path: build/devtools.tgz
       # Simplifies getting the extension for local testing
       - name: Archive chrome extension
Repository: vercel/next.js
Pull request: Add internal environment variable for enabling React Compiler

We'll use this in CI to enable it on certain shards or just temporarily.
Also allows quickly testing the Compiler in our tests.
It's not just about enabling the config flag but also declaring the dependency so an easy way to switch makes sense.

Changed files:
filename: packages/next/src/server/config.ts
patch: @@ -1805,6 +1805,24 @@ function enforceExperimentalFeatures(
     }
   }
 
+  if (
+    process.env.__NEXT_ENABLE_REACT_COMPILER === 'true' &&
+    // We do respect an explicit value in the user config.
+    (config.experimental.reactCompiler === undefined ||
+      (isDefaultConfig && !config.experimental.reactCompiler))
+  ) {
+    config.experimental.reactCompiler = true
+
+    if (configuredExperimentalFeatures) {
+      addConfiguredExperimentalFeature(
+        configuredExperimentalFeatures,
+        'reactCompiler',
+        true,
+        'enabled by `__NEXT_ENABLE_REACT_COMPILER`'
+      )
+    }
+  }
+
   if (
     config.experimental.enablePrerenderSourceMaps === undefined &&
     config.experimental.cacheComponents === true

filename: test/lib/next-modes/base.ts
patch: @@ -225,6 +225,14 @@ export class NextInstance {
           ...this.packageJson?.dependencies,
         }
 
+        if (
+          process.env.__NEXT_ENABLE_REACT_COMPILER === 'true' &&
+          !finalDependencies['babel-plugin-react-compiler']
+        ) {
+          finalDependencies['babel-plugin-react-compiler'] =
+            '0.0.0-experimental-3fde738-20250918'
+        }
+
         if (skipInstall || skipIsolatedNext) {
           const pkgScripts = (this.packageJson['scripts'] as {}) || {}
           await fs.mkdir(this.testDir, { recursive: true })