helloadhavan/github_issues huggingface dataset:
Repository: huggingface/transformers
Pull request: Fix parent classes of AllKwargsForChatTemplate

# What does this PR do?

Remove unused members of AllKwargsForChatTemplate

Changed files:
filename: src/transformers/processing_utils.py
patch: @@ -455,18 +455,10 @@ class ProcessorChatTemplateKwargs(ChatTemplateLoadKwargs, TokenizerChatTemplateK
     return_dict: Optional[bool] = False
 
 
-class AllKwargsForChatTemplate(
-    TextKwargs, ImagesKwargs, VideosKwargs, AudioKwargs, CommonKwargs, ProcessorChatTemplateKwargs
-):
-    processor_kwargs: ProcessingKwargs = {
-        **ProcessingKwargs.__annotations__,
-    }
-    mm_load_kwargs: ChatTemplateLoadKwargs = {
-        **TextKwargs.__annotations__,
-    }
-    template_kwargs: ProcessorChatTemplateKwargs = {
-        **ProcessorChatTemplateKwargs.__annotations__,
-    }
+class AllKwargsForChatTemplate(TypedDict, total=False):
+    processor_kwargs: ProcessingKwargs
+    mm_load_kwargs: ChatTemplateLoadKwargs
+    template_kwargs: ProcessorChatTemplateKwargs
 
 
 @dataclass
Repository: facebook/react
Pull request: Add packageManager fields for Corepack compat

## Summary

For users with Yarn defaulted to >1 / Berry, setting up the repo will result in the creation of the `.yarn/` directory, `yarn.lock` updates, and `package.json` edits. This change enables [corepack](https://nodejs.org/api/corepack.html) users to automatically detect and use Yarn Classic with no effect on anyone else.

I targeted the latest version of Yarn Classic as a guess, since there were no engines entries to key off of. Happy to change this as desired.

## How did you test this change?

Before this, running `yarn` in a fresh clone in either the root or compiler workspaces resulted in Yarn Berry making the above changes to the repo: 2000+ `.yarn/cache` entries, lockfile regeneration, and `package.json` formatting changes.

After this, `yarn` is handled by Yarn Classic as expected and no changes occur (and repo functions as expected).

Changed files:
filename: compiler/package.json
patch: @@ -49,5 +49,6 @@
   },
   "resolutions": {
     "react-is": "19.0.0-beta-b498834eab-20240506"
-  }
+  },
+  "packageManager": "yarn@1.22.22"
 }

filename: package.json
patch: @@ -139,5 +139,6 @@
   "resolutions": {
     "react-is": "npm:react-is",
     "jsdom": "22.1.0"
-  }
+  },
+  "packageManager": "yarn@1.22.22"
 }
Repository: denoland/deno
Pull request: fix(ext/node): `StatementSync.iterate()` should reset `is_iter_finished` flag on every call

Closes #30144

Changed files:
filename: ext/node/ops/sqlite/database.rs
patch: @@ -576,7 +576,7 @@ impl DatabaseSync {
       use_big_ints: Cell::new(false),
       allow_bare_named_params: Cell::new(true),
       allow_unknown_named_params: Cell::new(false),
-      is_iter_finished: false,
+      is_iter_finished: Cell::new(false),
     })
   }
 

filename: ext/node/ops/sqlite/statement.rs
patch: @@ -74,7 +74,7 @@ pub struct StatementSync {
   pub allow_bare_named_params: Cell<bool>,
   pub allow_unknown_named_params: Cell<bool>,
 
-  pub is_iter_finished: bool,
+  pub is_iter_finished: Cell<bool>,
 }
 
 impl Drop for StatementSync {
@@ -692,7 +692,7 @@ impl StatementSync {
         VALUE.v8_string(scope).unwrap().into(),
       ];
 
-      if statement.is_iter_finished {
+      if statement.is_iter_finished.get() {
         let values = &[
           v8::Boolean::new(scope, true).into(),
           v8::undefined(scope).into(),
@@ -706,7 +706,7 @@ impl StatementSync {
 
       let Ok(Some(row)) = statement.read_row(scope) else {
         let _ = statement.reset();
-        statement.is_iter_finished = true;
+        statement.is_iter_finished.set(true);
 
         let values = &[
           v8::Boolean::new(scope, true).into(),
@@ -734,7 +734,7 @@ impl StatementSync {
       // SAFETY: `context` is a valid pointer to a StatementSync instance
       let statement = unsafe { &mut *(context.value() as *mut StatementSync) };
 
-      statement.is_iter_finished = true;
+      statement.is_iter_finished.set(true);
       let _ = statement.reset();
 
       let names = &[
@@ -787,6 +787,8 @@ impl StatementSync {
       values,
     );
 
+    self.is_iter_finished.set(false);
+
     Ok(iterator)
   }
 

filename: tests/unit_node/sqlite_test.ts
patch: @@ -461,3 +461,22 @@ Deno.test("[node/sqlite] calling StatementSync methods after connection has clos
   assertThrows(() => stmt.setReadBigInts(true), Error, errMessage);
   assertThrows(() => stmt.sourceSQL, Error, errMessage);
 });
+
+// Regression test for https://github.com/denoland/deno/issues/30144
+Deno.test("[node/sqlite] StatementSync iterate should not reuse previous state", () => {
+  using db = new DatabaseSync(":memory:");
+  db.exec("CREATE TABLE numbers (value INTEGER)");
+
+  const stmt = db.prepare("SELECT value FROM numbers");
+  assertEquals(Array.from(stmt.iterate()), []);
+
+  db.exec("INSERT INTO numbers (value) VALUES (10), (20), (30)");
+  assertEquals(Array.from(stmt.iterate()), [
+    { value: 10, __proto__: null },
+    { value: 20, __proto__: null },
+    { value: 30, __proto__: null },
+  ]);
+
+  db.exec("DELETE FROM numbers");
+  assertEquals(Array.from(stmt.iterate()), []);
+});
Repository: denoland/deno
Pull request: fix(node): stub missing process.sourceMapsEnabled

See https://nodejs.org/api/process.html#processsourcemapsenabled

This fixes an issue in Fresh with vite's environment API which relies on this property to check if vite should map stack traces https://github.com/vitejs/vite/blob/main/packages/vite/src/module-runner/sourcemap/index.ts#L17

Changed files:
filename: ext/node/polyfills/process.ts
patch: @@ -756,6 +756,15 @@ process.setSourceMapsEnabled = (_val: boolean) => {
   // TODO(@satyarohith): support disabling source maps if needed.
 };
 
+// Source maps are always enabled in Deno.
+Object.defineProperty(process, "sourceMapsEnabled", {
+  get() {
+    return true; // Source maps are always enabled in Deno.
+  },
+  enumerable: true,
+  configurable: true,
+});
+
 /**
  * Returns the current high-resolution real time in a [seconds, nanoseconds]
  * tuple.

filename: tests/unit_node/process_test.ts
patch: @@ -1207,6 +1207,14 @@ Deno.test({
   },
 });
 
+Deno.test({
+  name: "process.sourceMapsEnabled",
+  fn() {
+    // @ts-ignore: not available in the types yet.
+    assertEquals(process.sourceMapsEnabled, true);
+  },
+});
+
 // Regression test for https://github.com/denoland/deno/issues/23761
 Deno.test({
   name: "process.uptime without this",
Repository: nodejs/node
Pull request: build: disable `v8_enable_pointer_compression_shared_cage` on non-64bit

Refs https://github.com/nodejs/node/pull/58171

Ensure `v8_enable_pointer_compression_shared_cage` is also disabled on non-64-bit architectures, as V8 pointer compression only supports 64bit architectures.

<!--
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: common.gypi
patch: @@ -113,6 +113,7 @@
       # V8 pointer compression only supports 64bit architectures.
       ['target_arch in "arm ia32 mips mipsel"', {
         'v8_enable_pointer_compression': 0,
+        'v8_enable_pointer_compression_shared_cage': 0,
         'v8_enable_31bit_smis_on_64bit_arch': 0,
         'v8_enable_external_code_space': 0,
         'v8_enable_sandbox': 0
Repository: facebook/react
Pull request: Add hyperlink for Good First Issues header

## Summary

The "Good First Issues" header in the README was missing a hyperlink where the other similar headlines had one. 

<!--
 Explain the **motivation** for making this change. What existing problem does the pull request solve?
-->

## How did you test this change?

N/A

<!--
  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: README.md
patch: @@ -69,7 +69,7 @@ Facebook has adopted a Code of Conduct that we expect project participants to ad
 
 Read our [contributing guide](https://legacy.reactjs.org/docs/how-to-contribute.html) to learn about our development process, how to propose bugfixes and improvements, and how to build and test your changes to React.
 
-### Good First Issues
+### [Good First Issues](https://github.com/facebook/react/labels/good%20first%20issue)
 
 To help you get your feet wet and get you familiar with our contribution process, we have a list of [good first issues](https://github.com/facebook/react/labels/good%20first%20issue) that contain bugs that have a relatively limited scope. This is a great place to get started.
Repository: denoland/deno
Pull request: feat(BREAKING/compile): require providing `--` for script arguments

This is to reduce confusion when someone puts `deno compile` arguments after the script name instead of before.

Closes https://github.com/denoland/deno/issues/30334

Changed files:
filename: cli/args/flags.rs
patch: @@ -2559,8 +2559,16 @@ On the first invocation of `deno compile`, Deno will download the relevant binar
       .arg(env_file_arg())
       .arg(
         script_arg()
-          .required_unless_present("help")
-          .trailing_var_arg(true),
+          .num_args(0..=1)
+          .required_unless_present("help"),
+      )
+      .arg(
+        Arg::new("args")
+          .num_args(0..)
+          .help("Arguments to provide for Deno.args (must be preceded by `--`)")
+          .action(ArgAction::Append)
+          .value_name("ARGS")
+          .last(true)
       )
   })
 }
@@ -5520,9 +5528,11 @@ fn compile_parse(
   flags.type_check_mode = TypeCheckMode::Local;
   runtime_args_parse(flags, matches, true, false, true)?;
 
-  let mut script = matches.remove_many::<String>("script_arg").unwrap();
-  let source_file = script.next().unwrap();
-  let args = script.collect();
+  let source_file = matches.remove_one::<String>("script_arg").unwrap();
+  let args = matches
+    .remove_many::<String>("args")
+    .unwrap_or_default()
+    .collect();
   let output = matches.remove_one::<String>("output");
   let target = matches.remove_one::<String>("target");
   let icon = matches.remove_one::<String>("icon");
@@ -11598,7 +11608,7 @@ mod tests {
   #[test]
   fn compile_with_flags() {
     #[rustfmt::skip]
-    let r = flags_from_vec(svec!["deno", "compile", "--include", "include.txt", "--exclude", "exclude.txt", "--import-map", "import_map.json", "--no-code-cache", "--no-remote", "--config", "tsconfig.json", "--no-check", "--unsafely-ignore-certificate-errors", "--reload", "--lock", "lock.json", "--cert", "example.crt", "--cached-only", "--location", "https:foo", "--allow-read", "--allow-net", "--v8-flags=--help", "--seed", "1", "--no-terminal", "--icon", "favicon.ico", "--output", "colors", "--env=.example.env", "https://examples.deno.land/color-logging.ts", "foo", "bar", "-p", "8080"]);
+    let r = flags_from_vec(svec!["deno", "compile", "--include", "include.txt", "--exclude", "exclude.txt", "--import-map", "import_map.json", "--no-code-cache", "--no-remote", "--config", "tsconfig.json", "--no-check", "--unsafely-ignore-certificate-errors", "--reload", "--lock", "lock.json", "--cert", "example.crt", "--cached-only", "--location", "https:foo", "--allow-read", "--allow-net", "--v8-flags=--help", "--seed", "1", "--no-terminal", "--icon", "favicon.ico", "--output", "colors", "--env=.example.env", "https://examples.deno.land/color-logging.ts", "--", "foo", "bar", "-p", "8080"]);
     assert_eq!(
       r.unwrap(),
       Flags {

filename: tests/integration/compile_tests.rs
patch: @@ -81,6 +81,7 @@ fn standalone_args() {
       "--output",
       &exe.to_string_lossy(),
       "./compile/args.ts",
+      "--",
       "a",
       "b",
     ])
Repository: ollama/ollama
Pull request: os specific ctrl-z

Add OS specific readline functions. Windows does not support these suspend system calls, so make ctrl-z a no-op on windows. This fixes development windows native builds.

resolves #1414

Changed files:
filename: readline/readline.go
patch: @@ -192,14 +192,7 @@ func (i *Instance) Readline() (string, error) {
 		case CharCtrlW:
 			buf.DeleteWord()
 		case CharCtrlZ:
-			if err := UnsetRawMode(fd, termios); err != nil {
-				return "", err
-			}
-
-			syscall.Kill(0, syscall.SIGSTOP)
-
-			// on resume...
-			return "", nil
+			return handleCharCtrlZ(fd, termios)
 		case CharEnter:
 			output := buf.String()
 			if output != "" {

filename: readline/readline_unix.go
patch: @@ -0,0 +1,18 @@
+//go:build !windows
+
+package readline
+
+import (
+	"syscall"
+)
+
+func handleCharCtrlZ(fd int, termios *Termios) (string, error) {
+	if err := UnsetRawMode(fd, termios); err != nil {
+		return "", err
+	}
+
+	syscall.Kill(0, syscall.SIGSTOP)
+
+	// on resume...
+	return "", nil
+}

filename: readline/readline_windows.go
patch: @@ -0,0 +1,6 @@
+package readline
+
+func handleCharCtrlZ(fd int, state *State) (string, error) {
+	// not supported
+	return "", nil
+}
Repository: facebook/react
Pull request: feat(hyperlink): added a hyperlink to Node in README.md file

As a fellow beginner to React, I didn't even know React runs on top of Node when I started. 

So, some beginners might get confused about what is Node and how to find details about it or how to download it. 

So, I thought to add a hyperlink to Node replacing the word Node in the README.md file. I think this might be a valuable contribution. 

- Januda

Changed files:
filename: README.md
patch: @@ -4,7 +4,7 @@ React is a JavaScript library for building user interfaces.
 
 * **Declarative:** React makes it painless to create interactive UIs. Design simple views for each state in your application, and React will efficiently update and render just the right components when your data changes. Declarative views make your code more predictable, simpler to understand, and easier to debug.
 * **Component-Based:** Build encapsulated components that manage their own state, then compose them to make complex UIs. Since component logic is written in JavaScript instead of templates, you can easily pass rich data through your app and keep the state out of the DOM.
-* **Learn Once, Write Anywhere:** We don't make assumptions about the rest of your technology stack, so you can develop new features in React without rewriting existing code. React can also render on the server using Node and power mobile apps using [React Native](https://reactnative.dev/).
+* **Learn Once, Write Anywhere:** We don't make assumptions about the rest of your technology stack, so you can develop new features in React without rewriting existing code. React can also render on the server using [Node](https://nodejs.org/en) and power mobile apps using [React Native](https://reactnative.dev/).
 
 [Learn how to use React in your project](https://react.dev/learn).
Repository: huggingface/transformers
Pull request: Skip `VitMatteImageProcessingTest::test_fast_is_faster_than_slow`

# What does this PR do?

So many times ...

https://app.circleci.com/pipelines/github/huggingface/transformers/145119/workflows/e763cbaa-6a14-421e-b6f2-dc26f0b4d38c/jobs/1918234

Changed files:
filename: tests/models/vitmatte/test_image_processing_vitmatte.py
patch: @@ -23,7 +23,6 @@
 
 from transformers.image_utils import load_image
 from transformers.testing_utils import (
-    is_flaky,
     require_torch,
     require_torch_accelerator,
     require_vision,
@@ -267,7 +266,7 @@ def test_image_processor_preprocess_arguments(self):
             self.assertGreaterEqual(len(raised_warnings), 1)
             self.assertIn("extra_argument", messages)
 
-    @is_flaky()
+    @unittest.skip(reason="TODO: Yoni")
     def test_fast_is_faster_than_slow(self):
         if not self.test_slow_image_processor or not self.test_fast_image_processor:
             self.skipTest(reason="Skipping speed test")
Repository: facebook/react
Pull request: [compiler:publish] Don't check branch in debug mode

Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom):
* __->__ #29153
* #29150
* #29149
* #29147
* #29148



Changed files:
filename: compiler/scripts/release/publish-manual.js
patch: @@ -163,7 +163,8 @@ async function main() {
       const pkgDir = path.resolve(__dirname, `../../packages/${pkgName}`);
       const { hash } = await hashElement(pkgDir, {
         encoding: "hex",
-        files: { exclude: [".DS_Store", "node_modules"] },
+        folders: { exclude: ["node_modules"] },
+        files: { exclude: [".DS_Store"] },
       });
       const truncatedHash = hash.slice(0, 7);
       const newVersion = `0.0.0-experimental-${truncatedHash}-${dateString}`;
Repository: huggingface/transformers
Pull request: [serve] re-enable tests

# What does this PR do?

`RUN_SLOW=1 py.test tests/commands/test_serving.py` is crashing locally. I couldn't pin the exact cause, the but it is triggered by a UX-related warning.

This PR:
- removes the test-crashing warning, so we can run tests
- adds the needed requirements to `extras[testing]` so these tests actually run in our daily CI 👀 (atm, we're skipping a few tests, see [here](https://github.com/huggingface/transformers/actions/runs/17482128457/job/49654564234))

Changed files:
filename: setup.py
patch: @@ -364,6 +364,7 @@ def run(self):
     + extras["retrieval"]
     + extras["modelcreation"]
     + extras["mistral-common"]
+    + extras["serving"]
 )
 
 extras["deepspeed-testing"] = extras["deepspeed"] + extras["testing"] + extras["optuna"] + extras["sentencepiece"]

filename: src/transformers/commands/serving.py
patch: @@ -687,10 +687,6 @@ async def lifespan(app: FastAPI):
             logger.warning_once(
                 "CORS allow origin is set to `*`. This is not recommended for production environments."
             )
-        else:
-            logger.warning_once(
-                "Some apps may require CORS. Consider launching the server with `--enable-cors` if you see errors."
-            )
 
         @app.post("/v1/chat/completions")
         def chat_completion(request: dict):
Repository: facebook/react
Pull request: [compiler:publish] Bump time to reconsider to 3s

Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom):
* #29153
* __->__ #29150
* #29149
* #29147
* #29148



Changed files:
filename: compiler/scripts/release/publish-manual.js
patch: @@ -159,7 +159,8 @@ async function main() {
       const pkgDir = path.resolve(__dirname, `../../packages/${pkgName}`);
       const { hash } = await hashElement(pkgDir, {
         encoding: "hex",
-        files: { exclude: [".DS_Store", "node_modules"] },
+        folders: { exclude: ["node_modules"] },
+        files: { exclude: [".DS_Store"] },
       });
       const truncatedHash = hash.slice(0, 7);
       const newVersion = `0.0.0-experimental-${truncatedHash}-${dateString}`;
Repository: vercel/next.js
Pull request: [codemod] return origin src in viewport mod if not changed

early return the metadata viewport codemod if possible with original source, to avoid the extra formatting by jscodeshift

Changed files:
filename: packages/next-codemod/transforms/metadata-to-viewport-export.ts
patch: @@ -18,17 +18,18 @@ export default function transformer(file: FileInfo, _api: API) {
   })
 
   if (metadataExport.size() !== 1) {
-    return
+    return file.source
   }
 
   const metadataObject = metadataExport.find(j.ObjectExpression).get(0).node
   if (!metadataObject) {
     console.error('Could not find metadata object')
-    return
+    return file.source
   }
 
   let metadataProperties = metadataObject.properties
   let viewportProperties
+  let hasChanges = false
 
   const viewport = metadataProperties.find(
     (prop) => prop.key.name === 'viewport'
@@ -38,6 +39,7 @@ export default function transformer(file: FileInfo, _api: API) {
     metadataProperties = metadataProperties.filter(
       (prop) => prop.key.name !== 'viewport'
     )
+    hasChanges = true
   } else {
     viewportProperties = []
   }
@@ -50,6 +52,7 @@ export default function transformer(file: FileInfo, _api: API) {
     metadataProperties = metadataProperties.filter(
       (prop) => prop.key.name !== 'colorScheme'
     )
+    hasChanges = true
   }
 
   const themeColor = metadataProperties.find(
@@ -60,6 +63,12 @@ export default function transformer(file: FileInfo, _api: API) {
     metadataProperties = metadataProperties.filter(
       (prop) => prop.key.name !== 'themeColor'
     )
+    hasChanges = true
+  }
+
+  // Only apply changes if there were actual modifications
+  if (!hasChanges) {
+    return file.source
   }
 
   // Update the metadata export
Repository: facebook/react
Pull request: [compiler:publish] Prompt for OTP

Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom):
* #29153
* #29150
* __->__ #29149
* #29147
* #29148

Makes running the script a little more ergonomic by prompting for OTP
upfront.

Changed files:
filename: compiler/scripts/release/publish-manual.js
patch: @@ -159,7 +159,8 @@ async function main() {
       const pkgDir = path.resolve(__dirname, `../../packages/${pkgName}`);
       const { hash } = await hashElement(pkgDir, {
         encoding: "hex",
-        files: { exclude: [".DS_Store", "node_modules"] },
+        folders: { exclude: ["node_modules"] },
+        files: { exclude: [".DS_Store"] },
       });
       const truncatedHash = hash.slice(0, 7);
       const newVersion = `0.0.0-experimental-${truncatedHash}-${dateString}`;
Repository: ollama/ollama
Pull request: Add support for mixture of experts (MoE) and Mixtral

To build this branch:

```
go generate ./...
go build .
```

```
./ollama serve

# in another terminal
./ollama run jmorgan/mixtral
```

resolves #1470 
resolves #1457 
resolves #1502 

Changed files:
filename: llm/llama.cpp/gguf
patch: @@ -1 +1 @@
-Subproject commit 23b5e12eb5a76489b4c3ee22213a081da68b1809
+Subproject commit 948ff137ec37f1ec74c02905917fa0afc9b97514