helloadhavan/github_issues huggingface dataset:
Repository: denoland/deno
Pull request: fix(inspector): crash on "Debugger.setBlackboxPatterns"

Closes https://github.com/denoland/deno/issues/24196

Changed files:
filename: Cargo.lock
patch: @@ -1303,9 +1303,9 @@ dependencies = [
 
 [[package]]
 name = "deno_core"
-version = "0.288.0"
+version = "0.289.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "e569b7a3e463a9f3b111a4279afa06b6909f6ecdc27aeedd3c310a57184ac217"
+checksum = "9e22f78a33feec9a7b211253b0aefbb8cb3b0081483ee8cec7bd954c76ac072a"
 dependencies = [
  "anyhow",
  "bincode",
@@ -1761,9 +1761,9 @@ dependencies = [
 
 [[package]]
 name = "deno_ops"
-version = "0.164.0"
+version = "0.165.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "748c200b559272ba65d98c25fc38e789901c847c41273e0232cc0df4cf6cad8b"
+checksum = "063c6ab08f9275a958878ae54e470cc6ce16f81c1fef16129db0c99d46c5fd35"
 dependencies = [
  "proc-macro-rules",
  "proc-macro2",
@@ -5774,9 +5774,9 @@ dependencies = [
 
 [[package]]
 name = "serde_v8"
-version = "0.197.0"
+version = "0.198.0"
 source = "registry+https://github.com/rust-lang/crates.io-index"
-checksum = "fb8b2ba47cda7f2941f66b4a0eec34b5f21d4ac3566fbc89598ff499a300f406"
+checksum = "491380c88077b81b2390e5f0cc10f64860819ba03369bb154bb9e4a587b31a01"
 dependencies = [
  "num-bigint",
  "serde",

filename: Cargo.toml
patch: @@ -44,7 +44,7 @@ repository = "https://github.com/denoland/deno"
 
 [workspace.dependencies]
 deno_ast = { version = "=0.39.2", features = ["transpiling"] }
-deno_core = { version = "0.288.0" }
+deno_core = { version = "0.289.0" }
 
 deno_bench_util = { version = "0.150.0", path = "./bench_util" }
 deno_lockfile = "0.20.0"

filename: tests/integration/inspector_tests.rs
patch: @@ -499,12 +499,14 @@ async fn inspector_does_not_hang() {
     .send_many(&[
       json!({"id":1,"method":"Runtime.enable"}),
       json!({"id":2,"method":"Debugger.enable"}),
+      json!({"id":3,"method":"Debugger.setBlackboxPatterns","params":{"patterns":["/node_modules/|/bower_components/"]}}),
     ])
     .await;
   tester.assert_received_messages(
       &[
         r#"{"id":1,"result":{}}"#,
-        r#"{"id":2,"result":{"debuggerId":"#
+        r#"{"id":2,"result":{"debuggerId":"#,
+        r#"{"id":3,"result":"#,
       ],
       &[
         r#"{"method":"Runtime.executionContextCreated","params":{"context":{"id":1,"#
@@ -513,21 +515,21 @@ async fn inspector_does_not_hang() {
     .await;
 
   tester
-    .send(json!({"id":3,"method":"Runtime.runIfWaitingForDebugger"}))
+    .send(json!({"id":4,"method":"Runtime.runIfWaitingForDebugger"}))
     .await;
   tester
     .assert_received_messages(
-      &[r#"{"id":3,"result":{}}"#],
+      &[r#"{"id":4,"result":{}}"#],
       &[r#"{"method":"Debugger.paused","#],
     )
     .await;
 
   tester
-    .send(json!({"id":4,"method":"Debugger.resume"}))
+    .send(json!({"id":5,"method":"Debugger.resume"}))
     .await;
   tester
     .assert_received_messages(
-      &[r#"{"id":4,"result":{}}"#],
+      &[r#"{"id":5,"result":{}}"#],
       &[r#"{"method":"Debugger.resumed","params":{}}"#],
     )
     .await;
Repository: huggingface/transformers
Pull request: Fix meta state dict loading with quantizers

# What does this PR do?

This is a temporary fix, while seeing if we can refactor hqq and b&b 4bits to work without the full state dict but only a given param one at a time.

Changed files:
filename: src/transformers/modeling_utils.py
patch: @@ -752,7 +752,11 @@ def _load_state_dict_into_meta_model(
         device_map_regex = "|".join([re.escape(k) for k in sorted(device_map.keys(), reverse=True)])
 
     is_quantized = hf_quantizer is not None
-    is_meta_state_dict = shard_file.endswith(".safetensors")
+    is_hqq_or_bnb = is_quantized and hf_quantizer.quantization_config.quant_method in [
+        QuantizationMethod.HQQ,
+        QuantizationMethod.BITS_AND_BYTES,
+    ]
+    is_meta_state_dict = shard_file.endswith(".safetensors") and not is_hqq_or_bnb
     file_pointer = None
     if is_meta_state_dict:
         file_pointer = safe_open(shard_file, framework="pt", device=tensor_device)
@@ -4828,14 +4832,18 @@ def _load_pretrained_model(
             caching_allocator_warmup(model_to_load, expanded_device_map, factor=2 if hf_quantizer is None else 4)
 
         error_msgs = []
+        is_hqq_or_bnb = is_quantized and hf_quantizer.quantization_config.quant_method in [
+            QuantizationMethod.HQQ,
+            QuantizationMethod.BITS_AND_BYTES,
+        ]
         # Iterate on all the shards to load the weights
         for shard_file in checkpoint_files:
             # Skip the load for shards that only contain disk-offloaded weights
             if shard_file in disk_only_shard_files:
                 continue
 
             map_location = "cpu"
-            if shard_file.endswith(".safetensors"):
+            if shard_file.endswith(".safetensors") and not is_hqq_or_bnb:
                 map_location = "meta"
             elif (
                 device_map is not None
Repository: vercel/next.js
Pull request: [logging] improve logging of port retry

### What

Only log once of the port retries, with the original port and the final listening port.

| Before | After |
|:--|:--|
| ⚠ Port 3000 is in use, trying 3001 instead.<br>⚠ Port 3001 is in use, trying 3002 instead. | ⚠ Port 3000 is in use, using available port 3002 instead. |

Changed files:
filename: packages/next/src/server/lib/start-server.ts
patch: @@ -203,6 +203,7 @@ export async function startServer(
   })
 
   let portRetryCount = 0
+  const originalPort = port
 
   server.on('error', (err: NodeJS.ErrnoException) => {
     if (
@@ -212,7 +213,6 @@ export async function startServer(
       err.code === 'EADDRINUSE' &&
       portRetryCount < 10
     ) {
-      Log.warn(`Port ${port} is in use, trying ${port + 1} instead.`)
       port += 1
       portRetryCount += 1
       server.listen(port, hostname)
@@ -244,6 +244,12 @@ export async function startServer(
 
       port = typeof addr === 'object' ? addr?.port || port : port
 
+      if (portRetryCount) {
+        Log.warn(
+          `Port ${originalPort} is in use, using available port ${port} instead.`
+        )
+      }
+
       const networkHostname =
         hostname ?? getNetworkHost(isIPv6(actualHostname) ? 'IPv6' : 'IPv4')
 

filename: test/integration/cli/test/index.test.js
patch: @@ -675,7 +675,9 @@ describe('CLI Usage', () => {
         await killApp(appTwo).catch(console.error)
       }
 
-      expect(output).toMatch('⚠ Port 3000 is in use, trying 3001 instead.')
+      expect(output).toMatch(
+        '⚠ Port 3000 is in use, using available port 3001 instead.'
+      )
     })
 
     test('-p reserved', async () => {
Repository: ggml-org/llama.cpp
Pull request: Fix includes in arg.cpp and gemma3-cli.cpp

Wonder how this was missed. The source [uses](https://github.com/ggml-org/llama.cpp/blob/7a84777f42a9b3ba47db5d20b7662f8ddf92f652/common/arg.cpp#L242) `filesystem`, but does not include it.

Changed files:
filename: common/arg.cpp
patch: @@ -18,6 +18,7 @@
 #include <algorithm>
 #include <climits>
 #include <cstdarg>
+#include <filesystem>
 #include <fstream>
 #include <regex>
 #include <set>

filename: examples/llava/gemma3-cli.cpp
patch: @@ -10,7 +10,7 @@
 
 #include <vector>
 #include <limits.h>
-#include <inttypes.h>
+#include <cinttypes>
 
 #if defined (__unix__) || (defined (__APPLE__) && defined (__MACH__))
 #include <signal.h>
Repository: facebook/react
Pull request: Clear performance marks after measuring

Once we've measured an event duration, we no longer need the marks. This PR adds calls to [`clearMarks`](https://developer.mozilla.org/en-US/docs/Web/API/Performance/clearMarks) to remove them from the browser's performance entry buffer. (They'll still be in the exported profiling JSON which is what the scheduling profiler needs.)

Changed files:
filename: packages/react-devtools-shared/src/PerformanceLoggingUtils.js
patch: @@ -27,6 +27,8 @@ function measure(markName: string): void {
   if (supportsUserTiming) {
     performance.mark(markName + '-end');
     performance.measure(markName, markName + '-start', markName + '-end');
+    performance.clearMarks(markName + '-start');
+    performance.clearMarks(markName + '-end');
   }
 }
Repository: nodejs/node
Pull request: test: remove unnecessary `await` in test-watch-mode

No need to await for the function `writeFileSync`.
<!--
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: test/sequential/test-watch-mode.mjs
patch: @@ -225,7 +225,7 @@ describe('watch mode', { concurrency: !process.env.TEST_PARALLEL, timeout: 60_00
 
     try {
       await restart();
-      await writeFileSync(envFile, `${envKey}=value1\n${envKey2}=newValue`);
+      writeFileSync(envFile, `${envKey}=value1\n${envKey2}=newValue`);
 
       // Second restart, after env change
       const { stderr, stdout } = await restart();
Repository: electron/electron
Pull request: build: update appveyor image to latest version

This PR updates appveyor.yml to the latest baked image, e-129.0.6638.0.

Notes: none

Changed files:
filename: appveyor-woa.yml
patch: @@ -29,7 +29,7 @@
 
 version: 1.0.{build}
 build_cloud: electronhq-16-core
-image: e-129.0.6636.0
+image: e-129.0.6638.0
 environment:
   GIT_CACHE_PATH: C:\Users\appveyor\libcc_cache
   ELECTRON_OUT_DIR: Default

filename: appveyor.yml
patch: @@ -29,7 +29,7 @@
 
 version: 1.0.{build}
 build_cloud: electronhq-16-core
-image: e-129.0.6636.0
+image: e-129.0.6638.0
 environment:
   GIT_CACHE_PATH: C:\Users\appveyor\libcc_cache
   ELECTRON_OUT_DIR: Default
Repository: nodejs/node
Pull request: buffer: coerce extrema to int in `blob.slice`

Fixes: https://github.com/nodejs/node/issues/55139
<!--
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/blob.js
patch: @@ -54,6 +54,7 @@ const {
   lazyDOMException,
 } = require('internal/util');
 const { inspect } = require('internal/util/inspect');
+const { convertToInt } = require('internal/webidl');
 
 const {
   codes: {
@@ -239,6 +240,12 @@ class Blob {
   slice(start = 0, end = this[kLength], contentType = '') {
     if (!isBlob(this))
       throw new ERR_INVALID_THIS('Blob');
+
+    // Coerce values to int
+    const opts = { __proto__: null, signed: true };
+    start = convertToInt('start', start, 64, opts);
+    end = convertToInt('end', end, 64, opts);
+
     if (start < 0) {
       start = MathMax(this[kLength] + start, 0);
     } else {

filename: test/parallel/test-blob.js
patch: @@ -483,6 +483,7 @@ assert.throws(() => new Blob({}), {
 
   assert.ok(blob.slice(0, 1).constructor === Blob);
   assert.ok(blob.slice(0, 1) instanceof Blob);
+  assert.ok(blob.slice(0, 1.5) instanceof Blob);
 }
 
 (async () => {
Repository: ggml-org/llama.cpp
Pull request: common: custom hf endpoint support

Add support for custom huggingface endpoints via HF_ENDPOINT environment variable

You can now specify a custom huggingface endpoint using the HF_ENDPOINT environment variable when using the --hf-repo flag, which works similarly to huggingface-cli's endpoint configuration.

Example usage:
HF_ENDPOINT=https://hf-mirror.com/ ./bin/llama-cli --hf-repo Qwen/Qwen1.5-0.5B-Chat-GGUF --hf-file qwen1_5-0_5b-chat-q2_k.gguf -p "The meaning to life and the universe is"

The trailing slash in the URL is optional:
HF_ENDPOINT=https://hf-mirror.com ./bin/llama-cli --hf-repo Qwen/Qwen1.5-0.5B-Chat-GGUF --hf-file qwen1_5-0_5b-chat-q2_k.gguf -p "The meaning to life and the universe is"

*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: common/arg.cpp
patch: @@ -656,9 +656,13 @@ static void common_params_handle_model(
                 }
             }
 
-            // TODO: allow custom host
-            model.url = "https://huggingface.co/" + model.hf_repo + "/resolve/main/" + model.hf_file;
-
+            std::string hf_endpoint = "https://huggingface.co/";
+            const char * hf_endpoint_env = getenv("HF_ENDPOINT");
+            if (hf_endpoint_env) {
+                hf_endpoint = hf_endpoint_env;
+                if (hf_endpoint.back() != '/') hf_endpoint += '/';
+            }
+            model.url = hf_endpoint + model.hf_repo + "/resolve/main/" + model.hf_file;
             // make sure model path is present (for caching purposes)
             if (model.path.empty()) {
                 // this is to avoid different repo having same file name, or same file name in different subdirs
Repository: facebook/react
Pull request: Updated the utfDecodeString() method to avoid call stack exceeded error

Resolves #22293

I'd like to add a test for this, but I'm not sure how. (Even if I disable the infinite loop detection, trying to provoke this scenario crashes Jest.)

I think this is an exception where it's okay to fix without a test.

Changed files:
filename: packages/react-devtools-shared/src/utils.js
patch: @@ -126,7 +126,16 @@ export function getUID(): number {
 }
 
 export function utfDecodeString(array: Array<number>): string {
-  return String.fromCodePoint(...array);
+  // Avoid spreading the array (e.g. String.fromCodePoint(...array))
+  // Functions arguments are first placed on the stack before the function is called
+  // which throws a RangeError for large arrays.
+  // See github.com/facebook/react/issues/22293
+  let string = '';
+  for (let i = 0; i < array.length; i++) {
+    const char = array[i];
+    string += String.fromCodePoint(char);
+  }
+  return string;
 }
 
 export function utfEncodeString(string: string): Array<number> {
Repository: nodejs/node
Pull request: doc: remove outdated https import reference

Refs: https://github.com/nodejs/node/pull/53822
Fixes: https://github.com/nodejs/node/issues/55091


Changed files:
filename: doc/api/module.md
patch: @@ -869,9 +869,6 @@ behaviors.
 
 #### Import from HTTPS
 
-In current Node.js, specifiers starting with `https://` are experimental (see
-\[HTTPS and HTTP imports]\[]).
-
 The hook below registers hooks to enable rudimentary support for such
 specifiers. While this may seem like a significant improvement to Node.js core
 functionality, there are substantial downsides to actually using these hooks:
Repository: facebook/react
Pull request: VerticalScrollView -> fixed  typos

fitst ---> fits
contnet ---> content

Changed files:
filename: packages/react-devtools-scheduling-profiler/src/view-base/VerticalScrollView.js
patch: @@ -287,7 +287,7 @@ export class VerticalScrollView extends View {
 
     // Don't allow wheel events to bubble past this view even if we've scrolled to the edge.
     // It just feels bad to have the scrolling jump unexpectedly from in a container to the outer page.
-    // The only exception is when the container fitst the contnet (no scrolling).
+    // The only exception is when the container fits the content (no scrolling).
     if (contentHeight === containerHeight) {
       return false;
     }
Repository: electron/electron
Pull request: build: fix build when `enable_pdf_viewer` and `enable_electron_extensions` disabled

Backport of #43206

See that PR for details.


Notes: none

Changed files:
filename: shell/browser/api/electron_api_session.cc
patch: @@ -47,6 +47,7 @@
 #include "net/base/completion_repeating_callback.h"
 #include "net/base/load_flags.h"
 #include "net/base/network_anonymization_key.h"
+#include "net/base/registry_controlled_domains/registry_controlled_domain.h"
 #include "net/http/http_auth_handler_factory.h"
 #include "net/http/http_auth_preferences.h"
 #include "net/http/http_cache.h"

filename: shell/browser/electron_browser_context.cc
patch: @@ -373,8 +373,10 @@ ElectronBrowserContext::~ElectronBrowserContext() {
   DCHECK_CURRENTLY_ON(BrowserThread::UI);
   NotifyWillBeDestroyed();
 
+#if BUILDFLAG(ENABLE_ELECTRON_EXTENSIONS)
   // the DestroyBrowserContextServices() call below frees this.
   extension_system_ = nullptr;
+#endif
 
   // Notify any keyed services of browser context destruction.
   BrowserContextDependencyManager::GetInstance()->DestroyBrowserContextServices(
Repository: facebook/react
Pull request: Scheduling profiler: Fix typo in View.js



<!--
  Thanks for submitting a pull request!
  We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory.

  Before submitting a pull request, please make sure the following is done:

  1. Fork [the repository](https://github.com/facebook/react) and create your branch from `main`.
  2. Run `yarn` in the repository root.
  3. If you've fixed a bug or added code that should be tested, add tests!
  4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development.
  5. Run `yarn test --prod` to test in the production environment. It supports the same options as `yarn test`.
  6. If you need a debugger, run `yarn debug-test --watch TestName`, open `chrome://inspect`, and press "Inspect".
  7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`).
  8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files.
  9. Run the [Flow](https://flowtype.org/) type checks (`yarn flow`).
  10. If you haven't already, complete the CLA.

  Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html
-->

## Summary
Fixed typo.
```
heirarchy -> hierarchy
```
<!--
 Explain the **motivation** for making this change. What existing problem does the pull request solve?
-->

## How did you test this change?

<!--
  Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface.
  How exactly did you verify that your PR solves the issue you wanted to solve?
  If you leave this empty, your PR will very likely be closed.
-->


Changed files:
filename: packages/react-devtools-scheduling-profiler/src/view-base/View.js
patch: @@ -58,7 +58,7 @@ export class View {
   _needsDisplay = true;
 
   /**
-   * Whether the heirarchy below this view has subviews that need display.
+   * Whether the hierarchy below this view has subviews that need display.
    *
    * NOTE: Do not set directly! Use `setSubviewsNeedDisplay`.
    *
Repository: denoland/deno
Pull request: fix(ext/webgpu): fix surface creation panic when adapter not initialized

Fixes https://github.com/denoland/deno/issues/23433


Changed files:
filename: ext/webgpu/byow.rs
patch: @@ -24,7 +24,9 @@ pub fn op_webgpu_surface_create(
   p1: *const c_void,
   p2: *const c_void,
 ) -> Result<ResourceId, AnyError> {
-  let instance = state.borrow::<super::Instance>();
+  let instance = state.try_borrow::<super::Instance>().ok_or_else(|| {
+    type_error("Cannot create surface outside of WebGPU context. Did you forget to call `navigator.gpu.requestAdapter()`?")
+  })?;
   // Security note:
   //
   // The `p1` and `p2` parameters are pointers to platform-specific window