helloadhavan/github_issues huggingface dataset:
Repository: facebook/react
Pull request: Add header to ReactAllWarnings Meta-only file

Adds missing headers to the generated file.

Changed files:
filename: scripts/print-warnings/print-warnings.js
patch: @@ -79,7 +79,19 @@ gs([
       const warningsArray = Array.from(warnings);
       warningsArray.sort();
       process.stdout.write(
-        `export default ${JSON.stringify(warningsArray, null, 2)};\n`
+        `/**
+ * Copyright (c) Meta Platforms, Inc. and affiliates.
+ *
+ * This source code is licensed under the MIT license found in the
+ * LICENSE file in the root directory of this source tree.
+ *
+ * @flow strict
+ * @noformat
+ * @oncall react_core
+ */
+
+export default ${JSON.stringify(warningsArray, null, 2)};
+`
       );
     } else {
       process.stdout.write(
Repository: huggingface/transformers
Pull request: Use np.pad instead of np.lib.pad.

# What does this PR do?

`audio_utils.py` still uses `np.lib.pad` from numpy 1.X rather than `np.pad`. This fixes the single remaining call in `transformers` to use `np.pad`.


## Who can review?

cc: @ArthurZucker, @Rocketknight1


Changed files:
filename: src/transformers/audio_utils.py
patch: @@ -1157,9 +1157,7 @@ def fram_wave(waveform: np.array, hop_length: int = 160, fft_window_size: int =
             frame = waveform[i : i + fft_window_size]
             frame_width = frame.shape[0]
             if frame_width < waveform.shape[0]:
-                frame = np.lib.pad(
-                    frame, pad_width=(0, fft_window_size - frame_width), mode="constant", constant_values=0
-                )
+                frame = np.pad(frame, pad_width=(0, fft_window_size - frame_width), mode="constant", constant_values=0)
         frames.append(frame)
 
     frames = np.stack(frames, 0)
Repository: facebook/react
Pull request: [ci] try to fix commit_artifacts step

Tries to fix the failure from https://github.com/facebook/react/actions/runs/7142005723/job/19450371514

I think it failed because we cannot `mv` into a folder with existing files or folders.

Changed files:
filename: .github/workflows/commit_artifacts.yml
patch: @@ -119,26 +119,25 @@ jobs:
             build/oss-experimental/react-refresh/cjs/react-refresh-babel.development.js
       - name: Move relevant files for React in www into compiled
         run: |
-          mkdir -p ./compiled
-          mkdir -p ./compiled/facebook-www/__test_utils__
-          mkdir -p ./compiled/babel-plugin-react-refresh
-
-          # Copy the facebook-www folder into compiled
+          # Move the facebook-www folder into compiled
+          mkdir ./compiled
           mv build/facebook-www ./compiled
 
-          # Copy WARNINGS to facebook-www
+          # Move WARNINGS to facebook-www
+          mkdir ./compiled/facebook-www/__test_utils__
           mv build/WARNINGS ./compiled/facebook-www/WARNINGS
           mv build/__test_utils__/ReactAllWarnings.js ./compiled/facebook-www/__test_utils__/ReactAllWarnings.js
 
-          # Copy eslint-plugin-react-hooks into facebook-www
+          # Move eslint-plugin-react-hooks into facebook-www
           mv build/oss-experimental/eslint-plugin-react-hooks/cjs/eslint-plugin-react-hooks.development.js \
             ./compiled/facebook-www/eslint-plugin-react-hooks.js
 
-          # Copy unstable_server-external-runtime.js into facebook-www
+          # Move unstable_server-external-runtime.js into facebook-www
           mv build/oss-stable/react-dom/unstable_server-external-runtime.js \
             ./compiled/facebook-www/unstable_server-external-runtime.js
 
-          # Copy react-refresh-babel.development.js into babel-plugin-react-refresh
+          # Move react-refresh-babel.development.js into babel-plugin-react-refresh
+          mkdir ./compiled/babel-plugin-react-refresh
           mv build/oss-experimental/react-refresh/cjs/react-refresh-babel.development.js \
             ./compiled/babel-plugin-react-refresh/index.js
Repository: nodejs/node
Pull request: quic: fix debug log

<!--
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: lib/internal/quic/quic.js
patch: @@ -776,7 +776,7 @@ class QuicStream {
   [kSendHeaders](headers) {
     validateObject(headers, 'headers');
     if (this.pending) {
-      debug('pending stream enqueing headers', headers);
+      debug('pending stream enqueuing headers', headers);
     } else {
       debug(`stream ${this.id} sending headers`, headers);
     }

filename: src/quic/streams.cc
patch: @@ -1109,7 +1109,7 @@ void Stream::Acknowledge(size_t datalen) {
 }
 
 void Stream::Commit(size_t datalen) {
-  Debug(this, "Commiting %zu bytes", datalen);
+  Debug(this, "Committing %zu bytes", datalen);
   STAT_RECORD_TIMESTAMP(Stats, acked_at);
   if (outbound_) outbound_->Commit(datalen);
 }
Repository: ggml-org/llama.cpp
Pull request: CANN: Support eager execution mode under ACL graph compilation

Add support for running operators in eager mode while ACL graph compilation is enabled. This allows bypassing graph execution and directly submitting ops, which is useful for debugging and reducing graph build overhead in certain scenarios.

*Make sure to read the [contributing guidelines](https://github.com/ggml-org/llama.cpp/blob/master/CONTRIBUTING.md) before submitting a PR*


Changed files:
filename: docs/backend/CANN.md
patch: @@ -314,3 +314,7 @@ Controls automatic cleanup of the memory pool. This option is only effective whe
 
 Converting the matmul weight format from ND to NZ can significantly improve performance on the 310I DUO NPU.
 
+### GGML_CANN_DISABLE_ACL_GRAPH
+
+When this variable is set, ACL graph execution is disabled and operators are executed in an op-by-op (eager) mode.
+This mode is mainly intended for debugging or for cases where the overhead of graph construction and execution is not desirable.

filename: ggml/src/ggml-cann/common.h
patch: @@ -395,6 +395,7 @@ struct ggml_backend_cann_context {
 #ifdef USE_ACL_GRAPH
     /// Cached CANN ACL graph used for executing the current ggml computation graph.
     std::unique_ptr<ggml_cann_graph> cann_graph;
+    bool acl_graph_mode = true;
 #endif
     cann_task_queue task_queue;
     bool async_mode;
@@ -404,7 +405,6 @@ struct ggml_backend_cann_context {
     ggml_cann_tensor_cache rms_norm_one_tensor_cache;
     ggml_cann_tensor_cache rms_norm_zero_tensor_cache;
 
-
     aclrtStream streams[GGML_CANN_MAX_STREAMS] = {nullptr}; /**< Array of streams for the device. */
 
     /**
@@ -419,6 +419,13 @@ struct ggml_backend_cann_context {
         async_mode = parse_bool(get_env("GGML_CANN_ASYNC_MODE").value_or(""));
         GGML_LOG_INFO("%s: device %d async operator submission is %s\n", __func__,
             device, async_mode ? "ON" : "OFF");
+#ifdef USE_ACL_GRAPH
+        acl_graph_mode = !(parse_bool(get_env("GGML_CANN_DISABLE_ACL_GRAPH").value_or("")));
+        GGML_LOG_INFO("%s: device %d execution mode is %s (%s)\n",
+              __func__, device,
+              acl_graph_mode ? "GRAPH" : "EAGER",
+              acl_graph_mode ? "acl graph enabled" : "acl graph disabled");
+#endif
     }
 
     /**

filename: ggml/src/ggml-cann/ggml-cann.cpp
patch: @@ -2252,6 +2252,10 @@ static enum ggml_status ggml_backend_cann_graph_compute(
     bool use_cann_graph = true;
     bool cann_graph_update_required = false;
 
+    if (!cann_ctx->acl_graph_mode) {
+        use_cann_graph = false;
+    }
+
     if (use_cann_graph) {
         if (cann_ctx->cann_graph == nullptr) {
             cann_ctx->cann_graph.reset(new ggml_cann_graph());
Repository: vercel/next.js
Pull request: Unflake `segment cache (CDN cache busting)` redirect test

[Flakiness Metrics](https://app.datadoghq.com/ci/test/runs?query=test_level%3Atest%20env%3Aci%20%40git.repository.id%3Agithub.com%2Fvercel%2Fnext.js%20%40test.service%3Anextjs%20%40test.status%3Afail%20%40test.name%3A%22segment%20cache%20%28CDN%20cache%20busting%29%20perform%20fully%20prefetched%20navigation%20when%20a%20third-party%20proxy%20performs%20a%20redirect%22%20%40git.branch%3Acanary&agg_m=count&agg_m_source=base&agg_t=count&currentTab=overview&eventStack=&fromUser=false&index=citest&start=1750359565225&end=1750964365225&paused=false)

I can repro the failure locally consistently with:

```
NEXT_SKIP_ISOLATE=1 pnpm test-start-turbo test/e2e/app-dir/segment-cache/cdn-cache-busting/cdn-cache-busting.test.ts -t 'perform fully prefetched navigation when a third-party proxy performs a redirect'
```

---

When a prefetch is responded with a redirect by a third-party proxy, we need to give the browser time to follow the redirect, before continuing our request assertions inside of `act`. We do that by waiting for the very next request to respond. Otherwise, we might exit early, before the request was added to the pending requests set.

Changed files:
filename: test/e2e/app-dir/segment-cache/router-act.ts
patch: @@ -375,6 +375,24 @@ Choose a more specific substring to assert on.
               await browserResponse.finished()
             }
           }
+
+          if (fulfilled.status === 307 || fulfilled.status === 308) {
+            // If this was a redirect, give the browser time to follow the
+            // redirect, before continuing. We do that by waiting for the very
+            // next request to respond. Otherwise, we might exit early, before
+            // the request was added to the pending requests set.
+            await new Promise<void>((resolve) => {
+              page.once('request', (req) => {
+                const handleResponse = (res: Playwright.Response) => {
+                  if (res.url() === req.url()) {
+                    page.off('response', handleResponse)
+                    resolve()
+                  }
+                }
+                page.on('response', handleResponse)
+              })
+            })
+          }
         }
 
         // After flushing the queue, wait for the microtask queue to be
Repository: denoland/deno
Pull request: fix(ext/webgpu): fix incorrect description of UnsafeWindowSurface

`NSView*` should be the third argument when the system is "cocoa".

@littledivy 

<!--
Before submitting a PR, please read https://docs.deno.com/runtime/manual/references/contributing

1. Give the PR a descriptive title.

  Examples of good title:
    - fix(std/http): Fix race condition in server
    - docs(console): Update docstrings
    - feat(doc): Handle nested reexports

  Examples of bad title:
    - fix #7123
    - update docs
    - fix bugs

2. Ensure there is a related issue and it is referenced in the PR text.
3. Ensure there are tests that cover the changes.
4. Ensure `cargo test` passes.
5. Ensure `./tools/format.js` passes without changing files.
6. Ensure `./tools/lint.js` passes.
7. Open as a draft PR if your work is still in progress. The CI won't run
   all steps, but you can add '[ci]' to a commit message to force it to.
8. If you would like to run the benchmarks on the CI, add the 'ci-bench' label.
-->


Changed files:
filename: cli/tsc/dts/lib.deno.unstable.d.ts
patch: @@ -18,7 +18,7 @@ declare namespace Deno {
    *
    *  | system            | winHandle     | displayHandle   |
    *  | ----------------- | ------------- | --------------- |
-   *  | "cocoa" (macOS)   | `NSView*`     | -               |
+   *  | "cocoa" (macOS)   | -             | `NSView*`       |
    *  | "win32" (Windows) | `HWND`        | `HINSTANCE`     |
    *  | "x11" (Linux)     | Xlib `Window` | Xlib `Display*` |
    *  | "wayland" (Linux) | `wl_surface*` | `wl_display*`   |
Repository: denoland/deno
Pull request: fix(repl): panic when user `delete globalThis.globalThis`

<!--
Before submitting a PR, please read https://docs.deno.com/runtime/manual/references/contributing

1. Give the PR a descriptive title.

  Examples of good title:
    - fix(std/http): Fix race condition in server
    - docs(console): Update docstrings
    - feat(doc): Handle nested reexports

  Examples of bad title:
    - fix #7123
    - update docs
    - fix bugs

2. Ensure there is a related issue and it is referenced in the PR text.
3. Ensure there are tests that cover the changes.
4. Ensure `cargo test` passes.
5. Ensure `./tools/format.js` passes without changing files.
6. Ensure `./tools/lint.js` passes.
7. Open as a draft PR if your work is still in progress. The CI won't run
   all steps, but you can add '[ci]' to a commit message to force it to.
8. If you would like to run the benchmarks on the CI, add the 'ci-bench' label.
-->
Closes #28959 

### Before the pr
![image](https://github.com/user-attachments/assets/6e52a87d-9454-4531-a28a-540293dc99e2)

### With the pr
![image](https://github.com/user-attachments/assets/a958ac92-3507-4f5e-ab32-b03bc156f03e)
At least it didn't panic

Changed files:
filename: cli/tools/repl/mod.rs
patch: @@ -63,9 +63,13 @@ impl Repl {
 
           // We check for close and break here instead of making it a loop condition to get
           // consistent behavior in when the user evaluates a call to close().
-          if self.session.closing().await? {
-            break;
-          }
+          match self.session.closing().await {
+            Ok(closing) if closing => break,
+            Ok(_) => {}
+            Err(err) => {
+              println!("Error: {:?}", err)
+            }
+          };
 
           println!("{}", output);
         }

filename: cli/tools/repl/session.rs
patch: @@ -313,12 +313,10 @@ impl ReplSession {
 
   pub async fn closing(&mut self) -> Result<bool, AnyError> {
     let expression = format!(r#"{}.closed"#, *REPL_INTERNALS_NAME);
-    let closed = self
-      .evaluate_expression(&expression)
-      .await?
-      .result
+    let result = self.evaluate_expression(&expression).await?.result;
+    let closed = result
       .value
-      .unwrap()
+      .ok_or_else(|| anyhow!(result.description.unwrap()))?
       .as_bool()
       .unwrap();
Repository: vercel/next.js
Pull request: Check if target workflow is enabled before triggering front sync

This change adds a check to ensure the front sync workflow is enabled before attempting to trigger it. Previously, when the workflow was disabled, the dispatch would fail and cause false alerts about deployment test failures.

Now, if the workflow is disabled, the sync trigger is skipped with clear logging. The on-call person should be aware that the workflow is disabled and can manually rerun the sync once the workflow is re-enabled.

I tested this by commenting out the tests and just running the check if workflow is enabled step and it worked:
![CleanShot 2025-07-08 at 14 57 48](https://github.com/user-attachments/assets/e56e3e2c-61c2-4c56-935a-025d508d3fa2)


Closes PACK-5032

Changed files:
filename: .github/workflows/test_e2e_deploy_release.yml
patch: @@ -114,9 +114,38 @@ jobs:
         run: gh auth status
         env:
           GITHUB_TOKEN: ${{ secrets.GH_UPDATE_NEXT_WORKFLOW_TRIGGER }}
+      - uses: actions/github-script@v7
+        name: Check if target workflow is enabled
+        id: check-workflow-enabled
+        with:
+          retries: 3
+          retry-exempt-status-codes: 400,401,404
+          github-token: ${{ secrets.GH_UPDATE_NEXT_WORKFLOW_TRIGGER }}
+          result-encoding: string
+          script: |
+            try {
+              const response = await github.request(
+                "GET /repos/{owner}/{repo}/actions/workflows/{workflow_id}",
+                {
+                  owner: "vercel",
+                  repo: "front",
+                  workflow_id: "cron-update-next.yml",
+                }
+              );
+              
+              const isEnabled = response.data.state === 'active';
+              console.info(`Target workflow state: ${response.data.state}`);
+              console.info(`Target workflow enabled: ${isEnabled}`);
+              
+              return isEnabled ? 'true' : 'false';
+            } catch (error) {
+              console.error('Error checking workflow status:', error);
+              return 'false';
+            }
       - uses: actions/github-script@v7
         name: Trigger vercel/front sync
         id: trigger-front-sync
+        if: steps.check-workflow-enabled.outputs.result == 'true'
         with:
           retries: 3
           retry-exempt-status-codes: 400,401,404
Repository: facebook/react
Pull request: Enable flag disableModulePatternComponents for native-fb

#27742 will remove this feature flag altogether, this just already removes the dynamic flag for the Meta React Native build ahead of time.

Changed files:
filename: packages/shared/forks/ReactFeatureFlags.native-fb-dynamic.js
patch: @@ -21,7 +21,6 @@ import typeof * as DynamicFlagsType from 'ReactNativeInternalFeatureFlags';
 // update the test configuration.
 
 export const alwaysThrottleRetries = __VARIANT__;
-export const disableModulePatternComponents = __VARIANT__;
 export const enableDeferRootSchedulingToMicrotask = __VARIANT__;
 export const enableUnifiedSyncLane = __VARIANT__;
 export const enableUseRefAccessWarning = __VARIANT__;

filename: packages/shared/forks/ReactFeatureFlags.native-fb.js
patch: @@ -19,7 +19,6 @@ import * as dynamicFlags from 'ReactNativeInternalFeatureFlags';
 // the exports object every time a flag is read.
 export const {
   alwaysThrottleRetries,
-  disableModulePatternComponents,
   enableDeferRootSchedulingToMicrotask,
   enableUnifiedSyncLane,
   enableUseRefAccessWarning,
@@ -28,6 +27,7 @@ export const {
 } = dynamicFlags;
 
 // The rest of the flags are static for better dead code elimination.
+export const disableModulePatternComponents = true;
 export const enableDebugTracing = false;
 export const enableSchedulingProfiler = __PROFILE__;
 export const enableProfilerTimer = __PROFILE__;

filename: scripts/flow/xplat.js
patch: @@ -9,7 +9,6 @@
 
 declare module 'ReactNativeInternalFeatureFlags' {
   declare export var alwaysThrottleRetries: boolean;
-  declare export var disableModulePatternComponents: boolean;
   declare export var enableDeferRootSchedulingToMicrotask: boolean;
   declare export var enableUnifiedSyncLane: boolean;
   declare export var enableUseRefAccessWarning: boolean;
Repository: denoland/deno
Pull request: feat: Allow access to NO_COLOR env var without --allow-env

Since `Deno.noColor` exists, it makes sense to allow accessing
`NO_COLOR` env var without `--allow-env` permission.

Changed files:
filename: ext/os/lib.rs
patch: @@ -22,14 +22,10 @@ pub mod sys_info;
 
 pub use ops::signal::SignalError;
 
-pub static NODE_ENV_VAR_ALLOWLIST: Lazy<HashSet<String>> = Lazy::new(|| {
+pub static NODE_ENV_VAR_ALLOWLIST: Lazy<HashSet<&str>> = Lazy::new(|| {
   // The full list of environment variables supported by Node.js is available
   // at https://nodejs.org/api/cli.html#environment-variables
-  let mut set = HashSet::new();
-  set.insert("NODE_DEBUG".to_string());
-  set.insert("NODE_OPTIONS".to_string());
-  set.insert("FORCE_COLOR".to_string());
-  set
+  HashSet::from(["NODE_DEBUG", "NODE_OPTIONS", "FORCE_COLOR", "NO_COLOR"])
 });
 
 #[derive(Clone, Default)]
@@ -195,7 +191,7 @@ fn op_get_env(
   state: &mut OpState,
   #[string] key: String,
 ) -> Result<Option<String>, OsError> {
-  let skip_permission_check = NODE_ENV_VAR_ALLOWLIST.contains(&key);
+  let skip_permission_check = NODE_ENV_VAR_ALLOWLIST.contains(key.as_str());
 
   if !skip_permission_check {
     state.borrow_mut::<PermissionsContainer>().check_env(&key)?;
Repository: ggml-org/llama.cpp
Pull request: ggml-backend: raise GGML_MAX_SPLIT_INPUTS

With FlashAttention enabled Gemma 3n can crash when using many GPUs due to `GGML_MAX_SPLIT_INPUTS` being too low, see https://github.com/ggml-org/llama.cpp/pull/15434#issuecomment-3243129756 . The maximum value with which I can provoke the issue is 19 when using 6 GPUs. This PR sets the value to 30 so that there is some margin above this value.

Changed files:
filename: ggml/src/ggml-backend.cpp
patch: @@ -651,7 +651,7 @@ static bool ggml_is_view_op(enum ggml_op op) {
 #endif
 
 #ifndef GGML_SCHED_MAX_SPLIT_INPUTS
-#define GGML_SCHED_MAX_SPLIT_INPUTS GGML_MAX_SRC
+#define GGML_SCHED_MAX_SPLIT_INPUTS 30
 #endif
 
 #ifndef GGML_SCHED_MAX_COPIES
Repository: nodejs/node
Pull request: test: skip uv-thread-name on IBM i

<!--
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.
-->


Similar to AIX, IBM i does not support get/set thread name from libuv.
See: https://github.com/libuv/libuv/pull/4599#issuecomment-2498376606


CC
@nodejs/platform-ibmi 

Changed files:
filename: test/addons/uv-thread-name/test.js
patch: @@ -1,8 +1,9 @@
 'use strict';
 const common = require('../../common');
 
-if (common.isAIX) {
-  common.skip('AIX is not supported by libuv');
+if (common.isAIX || common.isIBMi) {
+  // see: https://github.com/libuv/libuv/pull/4599#issuecomment-2498376606
+  common.skip('AIX, IBM i do not support get/set thread name');
 }
 
 const assert = require('node:assert');