helloadhavan/github_issues huggingface dataset:
Repository: facebook/react
Pull request: [Transition Tracing] Remove console.error in clearTransitionForLanes

We changed the implementation of `root.transitionLanes` so that, if there is no transitions for a given lane, we use null instead of an array. This means that this error is no longer valid, so we are removing it 

Changed files:
filename: packages/react-reconciler/src/ReactFiberLane.new.js
patch: @@ -859,13 +859,6 @@ export function clearTransitionsForLanes(root: FiberRoot, lanes: Lane | Lanes) {
     const transitions = root.transitionLanes[index];
     if (transitions !== null) {
       root.transitionLanes[index] = null;
-    } else {
-      if (__DEV__) {
-        console.error(
-          'React Bug: transition lanes accessed out of bounds index: %s',
-          index.toString(),
-        );
-      }
     }
 
     lanes &= ~lane;

filename: packages/react-reconciler/src/ReactFiberLane.old.js
patch: @@ -859,13 +859,6 @@ export function clearTransitionsForLanes(root: FiberRoot, lanes: Lane | Lanes) {
     const transitions = root.transitionLanes[index];
     if (transitions !== null) {
       root.transitionLanes[index] = null;
-    } else {
-      if (__DEV__) {
-        console.error(
-          'React Bug: transition lanes accessed out of bounds index: %s',
-          index.toString(),
-        );
-      }
     }
 
     lanes &= ~lane;
Repository: vercel/next.js
Pull request: Turbopack: avoid depending on the Project

### What?

avoid depending on the Project value directly, since it will change on every build.

Closes PACK-4521

Changed files:
filename: crates/next-api/src/middleware.rs
patch: @@ -44,7 +44,6 @@ use crate::{
 #[turbo_tasks::value]
 pub struct MiddlewareEndpoint {
     project: ResolvedVc<Project>,
-    build_id: RcStr,
     asset_context: ResolvedVc<Box<dyn AssetContext>>,
     source: ResolvedVc<Box<dyn Source>>,
     app_dir: Option<ResolvedVc<FileSystemPath>>,
@@ -56,15 +55,13 @@ impl MiddlewareEndpoint {
     #[turbo_tasks::function]
     pub fn new(
         project: ResolvedVc<Project>,
-        build_id: RcStr,
         asset_context: ResolvedVc<Box<dyn AssetContext>>,
         source: ResolvedVc<Box<dyn Source>>,
         app_dir: Option<ResolvedVc<FileSystemPath>>,
         ecmascript_client_reference_transition_name: Option<ResolvedVc<RcStr>>,
     ) -> Vc<Self> {
         Self {
             project,
-            build_id,
             asset_context,
             source,
             app_dir,

filename: crates/next-api/src/project.rs
patch: @@ -738,6 +738,11 @@ impl Project {
         *self.mode
     }
 
+    #[turbo_tasks::function]
+    pub(super) async fn is_watch_enabled(&self) -> Result<Vc<bool>> {
+        Ok(Vc::cell(self.watch.enable))
+    }
+
     #[turbo_tasks::function]
     pub(super) async fn per_page_module_graph(&self) -> Result<Vc<bool>> {
         Ok(Vc::cell(*self.mode.await? == NextMode::Development))
@@ -944,7 +949,7 @@ impl Project {
 
             // At this point all modules have been computed and we can get rid of the node.js
             // process pools
-            if self.await?.watch.enable {
+            if *self.is_watch_enabled().await? {
                 turbopack_node::evaluate::scale_down();
             } else {
                 turbopack_node::evaluate::scale_zero();
@@ -1412,7 +1417,6 @@ impl Project {
 
         Ok(Vc::upcast(MiddlewareEndpoint::new(
             self,
-            self.await?.build_id.clone(),
             middleware_asset_context,
             source,
             app_dir.as_deref().copied(),
Repository: huggingface/transformers
Pull request: Fix auto-round hfoption 

# What does this PR do?
Fixes `auto-round` docs using `hfoption`


Changed files:
filename: docs/source/en/quantization/auto_round.md
patch: @@ -184,7 +184,7 @@ inputs = tokenizer(text, return_tensors="pt").to(model.device)
 print(tokenizer.decode(model.generate(**inputs, max_new_tokens=50, do_sample=False)[0]))
 ```
 
-<hfoption>
+</hfoption>
 
 <hfoption id="inference xpu">
 
@@ -203,7 +203,7 @@ inputs = tokenizer(text, return_tensors="pt").to(model.device)
 print(tokenizer.decode(model.generate(**inputs, max_new_tokens=50, do_sample=False)[0]))
 ```
 
-<hfoption>
+</hfoption>
 
 <hfoption id="inference cuda">
 
@@ -222,7 +222,7 @@ inputs = tokenizer(text, return_tensors="pt").to(model.device)
 print(tokenizer.decode(model.generate(**inputs, max_new_tokens=50, do_sample=False)[0]))
 ```
 
-<hfoption>
+</hfoption>
 
 <hfoption id="inference backend">
 
@@ -245,7 +245,7 @@ inputs = tokenizer(text, return_tensors="pt").to(model.device)
 print(tokenizer.decode(model.generate(**inputs, max_new_tokens=50, do_sample=False)[0]))
 ```
 
-<hfoption>
+</hfoption>
 
 
 <hfoption id="format convert">
@@ -266,9 +266,9 @@ inputs = tokenizer(text, return_tensors="pt").to(model.device)
 print(tokenizer.decode(model.generate(**inputs, max_new_tokens=50, do_sample=False)[0]))
 ```
 
-<hfoption>
+</hfoption>
 
-<hfoptions>
+</hfoptions>
 
 ## Issues
Repository: denoland/deno
Pull request: test: run specs::npm::exec_file_inside_npm_package with DENO_FUTURE=1

The test is failing if run with `DENO_FUTURE=1` which is blocking
https://github.com/denoland/deno/pull/25213.

Changed files:
filename: cli/args/mod.rs
patch: @@ -1614,6 +1614,7 @@ impl CliOptions {
   pub fn use_byonm(&self) -> bool {
     if self.enable_future_features()
       && self.node_modules_dir_enablement().is_none()
+      && self.maybe_node_modules_folder.is_some()
       && self
         .workspace()
         .config_folders()

filename: tests/specs/npm/exec_file_inside_npm_package/__test__.jsonc
patch: @@ -1,4 +1,7 @@
 {
   "args": "run -A main.ts",
-  "output": "main.out"
+  "output": "main.out",
+  "envs": {
+    "DENO_FUTURE": "1"
+  }
 }
Repository: nodejs/node
Pull request: tools: disable unneeded rule ignoring in Python linting

Removing PLC1901 and RUF100 from the list of Python lint rules to ignore does not result in any errors. Keeping the ignore list as short as possible seems like a good idea, so this change removes them from the ignore list.

<!--
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: pyproject.toml
patch: @@ -33,9 +33,7 @@ ignore = [
   "E401",
   "E402",
   "E7",
-  "PLC1901",
   "RUF005",
-  "RUF100",
 ]
 
 [tool.ruff.lint.mccabe]
Repository: vercel/next.js
Pull request: Turbopack: Add support for `extension` regex in `@next/mdx`

Closes #78563 (replaces it)
Resolves #78348

This allows users the same flexibility they have with `@next/mdx` for webpack. It depends on #78733.

Test Plan: Included the integration test from #78563

Closes PACK-4523

Changed files:
filename: packages/next-mdx/index.js
patch: @@ -49,11 +49,16 @@ module.exports =
     if (process.env.TURBOPACK) {
       nextConfig.turbopack = Object.assign({}, nextConfig?.turbopack, {
         rules: Object.assign({}, nextConfig?.turbopack?.rules, {
-          '*.mdx': {
+          '#next-mdx': {
             loaders: [loader],
             as: '*.tsx',
           },
         }),
+        conditions: {
+          '#next-mdx': {
+            path: extension,
+          },
+        },
         resolveAlias: Object.assign({}, nextConfig?.turbopack?.resolveAlias, {
           'next-mdx-import-source-file':
             '@vercel/turbopack-next/mdx-import-source',

filename: test/e2e/app-dir/mdx/pages/pages/import/index.tsx
patch: @@ -1,8 +1,9 @@
-import MDXContent from './mdx-file.mdx'
+import MDContent from './md-file.md'
+
 export default function Page() {
   return (
     <>
-      <MDXContent />
+      <MDContent />
     </>
   )
 }

filename: test/e2e/app-dir/mdx/types/mdx.d.ts
patch: @@ -4,3 +4,9 @@ declare module '*.mdx' {
   let MDXComponent: (props) => JSX.Element
   export default MDXComponent
 }
+
+declare module '*.md' {
+  import type { JSX } from 'react'
+  let MDXComponent: (props) => JSX.Element
+  export default MDXComponent
+}
Repository: nodejs/node
Pull request: src: drop --experimental-permission in favour of --permission

Refs: https://github.com/nodejs/node/pull/56201

Changed files:
filename: doc/api/cli.md
patch: @@ -3088,7 +3088,6 @@ one is included in the list below.
 * `--experimental-json-modules`
 * `--experimental-loader`
 * `--experimental-modules`
-* `--experimental-permission`
 * `--experimental-print-required-tla`
 * `--experimental-require-module`
 * `--experimental-shadow-realm`

filename: src/node_options.cc
patch: @@ -470,7 +470,6 @@ EnvironmentOptionsParser::EnvironmentOptionsParser() {
             &EnvironmentOptions::permission,
             kAllowedInEnvvar,
             false);
-  AddAlias("--experimental-permission", "--permission");
   AddOption("--allow-fs-read",
             "allow permissions to read the filesystem",
             &EnvironmentOptions::allow_fs_read,
Repository: facebook/react
Pull request: Fix file path separator compatibility in scripts/babel

The problem in scripts\babel\transform-object-assign.js is that file path separator has '/' and '\' between Linux, MacOS and Windows, which causes yarn build error. See https://github.com/facebook/react/issues/24103

<!--
  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

<!--
 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: scripts/babel/transform-object-assign.js
patch: @@ -28,7 +28,7 @@ module.exports = function autoImporter(babel) {
 
     visitor: {
       CallExpression: function(path, file) {
-        if (file.filename.indexOf('shared/assign') !== -1) {
+        if (/shared(\/|\\)assign/.test(file.filename)) {
           // Don't replace Object.assign if we're transforming shared/assign
           return;
         }
@@ -40,7 +40,7 @@ module.exports = function autoImporter(babel) {
       },
 
       MemberExpression: function(path, file) {
-        if (file.filename.indexOf('shared/assign') !== -1) {
+        if (/shared(\/|\\)assign/.test(file.filename)) {
           // Don't replace Object.assign if we're transforming shared/assign
           return;
         }
Repository: huggingface/transformers
Pull request: Fix tied weight loading with TP and loading sub state_dicts

# What does this PR do?

See https://github.com/huggingface/transformers/issues/37737

Changed files:
filename: src/transformers/modeling_utils.py
patch: @@ -4978,7 +4978,10 @@ def _load_pretrained_model(
                     name: param for name, param in model.named_parameters() if not name.startswith(prefix)
                 }
                 for name, param in parameters_to_initialize.items():
-                    # First move data to correct
+                    # If it is still on meta here, it means that it's a tied weight that will be tied later anyway -> skip it
+                    if param.device.type == "meta":
+                        continue
+                    # Shard the param
                     to_contiguous, casting_dtype = _infer_parameter_dtype(model, name, param, keep_in_fp32_regex)
                     shard_and_distribute_module(
                         model,
Repository: ggml-org/llama.cpp
Pull request: fix: use the current build config for `vulkan-shaders-gen`

This solves an issue where when building on Windows on Arm with a `Release` config, `vulkan-shaders-gen` is built with `Debug` config (since no config is set), so the built binary is placed on an output folder that cmake doesn't expect, which then fails to run the built `vulkan-shaders-gen`.

Changed files:
filename: ggml/src/ggml-vulkan/CMakeLists.txt
patch: @@ -54,6 +54,11 @@ if (Vulkan_FOUND)
         -DCMAKE_RUNTIME_OUTPUT_DIRECTORY=${CMAKE_RUNTIME_OUTPUT_DIRECTORY}
     )
 
+    set(VULKAN_SHADER_GEN_CMAKE_BUILD_ARGS "")
+    if (CMAKE_BUILD_TYPE AND CMAKE_BUILD_TYPE MATCHES "Debug|Release|MinSizeRel|RelWithDebInfo")
+        list(APPEND VULKAN_SHADER_GEN_CMAKE_BUILD_ARGS --config=${CMAKE_BUILD_TYPE})
+    endif()
+
     # Test all shader extensions
     test_shader_extension_support(
         "GL_KHR_cooperative_matrix"
@@ -149,7 +154,7 @@ if (Vulkan_FOUND)
         vulkan-shaders-gen
         SOURCE_DIR ${CMAKE_CURRENT_SOURCE_DIR}/vulkan-shaders
         CMAKE_ARGS ${VULKAN_SHADER_GEN_CMAKE_ARGS}
-        BUILD_COMMAND ${CMAKE_COMMAND} --build .
+        BUILD_COMMAND ${CMAKE_COMMAND} --build . ${VULKAN_SHADER_GEN_CMAKE_BUILD_ARGS}
         INSTALL_COMMAND ${CMAKE_COMMAND} --install .
         INSTALL_DIR ${CMAKE_BINARY_DIR}
     )
Repository: vercel/next.js
Pull request: Turbopack: use unstable sort for better performance

### What?

Small performance improvement by using unstable sort

Closes PACK-4524

Changed files:
filename: turbopack/crates/turbo-persistence/src/collector.rs
patch: @@ -93,7 +93,7 @@ impl<K: StoreKey, const SIZE_SHIFT: usize> Collector<K, SIZE_SHIFT> {
     /// Sorts the entries and returns them along with the total key and value sizes. This doesn't
     /// clear the entries.
     pub fn sorted(&mut self) -> (&[CollectorEntry<K>], usize, usize) {
-        self.entries.sort_by(|a, b| a.key.cmp(&b.key));
+        self.entries.sort_unstable_by(|a, b| a.key.cmp(&b.key));
         (&self.entries, self.total_key_size, self.total_value_size)
     }
 

filename: turbopack/crates/turbo-persistence/src/write_batch.rs
patch: @@ -291,7 +291,7 @@ impl<K: StoreKey + Send + Sync, const FAMILIES: usize> WriteBatch<K, FAMILIES> {
 
         shared_error.into_inner()?;
         let seq = self.current_sequence_number.load(Ordering::SeqCst);
-        new_sst_files.sort_by_key(|(seq, _)| *seq);
+        new_sst_files.sort_unstable_by_key(|(seq, _)| *seq);
         Ok(FinishResult {
             sequence_number: seq,
             new_sst_files,
Repository: huggingface/transformers
Pull request: [generate] fix default autocompile case on gpu

# What does this PR do?

(I didn't run slow tests before merging #37709 , the CPU tests of the push ci didn't caught this issue)

reproducer, requires GPU
```py
from transformers import AutoModelForCausalLM, AutoTokenizer

tokenizer = AutoTokenizer.from_pretrained("Qwen/Qwen2.5-0.5B-Instruct")
model = AutoModelForCausalLM.from_pretrained("Qwen/Qwen2.5-0.5B-Instruct", device_map="auto")
inputs = tokenizer(["The quick brown"], return_tensors="pt").to(model.device)

# compilable cache -> compilation will happen
gen_out = model.generate(**inputs, do_sample=False, cache_implementation="static")
print(tokenizer.batch_decode(gen_out, skip_special_tokens=True))
```


Changed files:
filename: src/transformers/generation/utils.py
patch: @@ -3430,7 +3430,8 @@ def _sample(
         model_kwargs = self._get_initial_cache_position(input_ids, model_kwargs)
 
         model_forward = self.__call__
-        if self._valid_auto_compile_criteria(model_kwargs, generation_config):
+        compile_forward = self._valid_auto_compile_criteria(model_kwargs, generation_config)
+        if compile_forward:
             os.environ["TOKENIZERS_PARALLELISM"] = "0"
             model_forward = self.get_compiled_call(generation_config.compile_config)
 

filename: src/transformers/modeling_utils.py
patch: @@ -5270,6 +5270,7 @@ def get_compiled_call(self, compile_config: Optional[CompileConfig]) -> Callable
         # Only reset it if not present or different from previous config
         if "llama4" in self.config.model_type:  # TODO try to enable for FULL COMPILE HYBRID CACHE SUPPORT
             return self.__call__
+        compile_config = compile_config or CompileConfig()
         default_config = getattr(self.generation_config, "compile_config", None) or CompileConfig()
         if (
             not hasattr(self, "_compiled_call")
Repository: denoland/deno
Pull request: fix(napi): Don't run microtasks in napi_resolve_deferred

Fixes an incredibly obscure bug that causes parcel's file watcher to not get any file update notifications on macOS.

The issue was that the native addon was calling `napi_resolve_deferred`, but when we resolved the promise, v8 was running microtasks automatically. That executed JS, which called back into the native addon and broke the addon's assumption that the call wouldn't be reentrant.

Changed files:
filename: cli/napi/js_native_api.rs
patch: @@ -3307,19 +3307,30 @@ fn napi_resolve_deferred(
   check_arg!(env, result);
   check_arg!(env, deferred);
 
+  // Make sure microtasks don't run and call back into JS
+  env
+    .scope()
+    .set_microtasks_policy(v8::MicrotasksPolicy::Explicit);
+
   let deferred_ptr =
     unsafe { NonNull::new_unchecked(deferred as *mut v8::PromiseResolver) };
   let global = unsafe { v8::Global::from_raw(env.isolate(), deferred_ptr) };
   let resolver = v8::Local::new(&mut env.scope(), global);
 
-  if !resolver
+  let success = resolver
     .resolve(&mut env.scope(), result.unwrap())
-    .unwrap_or(false)
-  {
-    return napi_generic_failure;
-  }
+    .unwrap_or(false);
 
-  napi_ok
+  // Restore policy
+  env
+    .scope()
+    .set_microtasks_policy(v8::MicrotasksPolicy::Auto);
+
+  if success {
+    napi_ok
+  } else {
+    napi_generic_failure
+  }
 }
 
 #[napi_sym]
Repository: nodejs/node
Pull request: test: remove test-worker-arraybuffer-zerofill flaky designation

Refs: https://github.com/nodejs/node/pull/56053

<!--
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/parallel/parallel.status
patch: @@ -8,8 +8,6 @@ prefix parallel
 # https://github.com/nodejs/node/issues/52273
 test-shadow-realm-gc: SKIP
 test-shadow-realm-gc-module: SKIP
-# https://github.com/nodejs/node/issues/52274
-test-worker-arraybuffer-zerofill: PASS, FLAKY
 
 # https://github.com/nodejs/node/issues/51862
 test-fs-read-stream-concurrent-reads: PASS, FLAKY