helloadhavan/github_issues huggingface dataset:
Repository: facebook/react
Pull request: [Fizz] Skip past hidden inputs when attempting to hydrate hydration boundaries

Originally reported in https://github.com/vercel/next.js/issues/79995

We already skip past hidden inputs when hydrating elements and text. This just copies the logic  to the hydration boundary path which affects Suspense and Activity.

Changed files:
filename: packages/react-dom-bindings/src/client/ReactFiberConfigDOM.js
patch: @@ -3580,7 +3580,14 @@ function canHydrateHydrationBoundary(
   inRootOrSingleton: boolean,
 ): null | SuspenseInstance | ActivityInstance {
   while (instance.nodeType !== COMMENT_NODE) {
-    if (!inRootOrSingleton) {
+    if (
+      instance.nodeType === ELEMENT_NODE &&
+      instance.nodeName === 'INPUT' &&
+      (instance: any).type === 'hidden'
+    ) {
+      // If we have extra hidden inputs, we don't mismatch. This allows us to
+      // embed extra form data in the original form.
+    } else if (!inRootOrSingleton) {
       return null;
     }
     const nextInstance = getNextHydratableSibling(instance);

filename: packages/react-dom/src/__tests__/ReactDOMFizzForm-test.js
patch: @@ -23,6 +23,7 @@ let container;
 let React;
 let ReactDOMServer;
 let ReactDOMClient;
+let Suspense;
 let useFormStatus;
 let useOptimistic;
 let useActionState;
@@ -35,6 +36,7 @@ describe('ReactDOMFizzForm', () => {
     React = require('react');
     ReactDOMServer = require('react-dom/server.browser');
     ReactDOMClient = require('react-dom/client');
+    Suspense = React.Suspense;
     useFormStatus = require('react-dom').useFormStatus;
     useOptimistic = require('react').useOptimistic;
     act = require('internal-test-utils').act;
@@ -588,6 +590,7 @@ describe('ReactDOMFizzForm', () => {
     function App() {
       return (
         <form action={action} ref={ref} method={null}>
+          <Suspense />
           <input type="text" name="foo" defaultValue="bar" />
         </form>
       );
Repository: huggingface/transformers
Pull request: Fix incorrect timestamp calculation in Qwen3VL Processor

## What does this PR do?

Fixes #43519

### Problem

The Qwen3VL processor was incorrectly using `merge_size` (spatial merging) instead of `temporal_patch_size` (temporal grouping) when calculating video frame timestamps.

```python
# Before (incorrect)
curr_timestamp = self._calculate_timestamps(
    metadata.frames_indices,
    metadata.fps,
    self.video_processor.merge_size,  # Wrong! This is for spatial merging
)
```

### Root Cause

The video processor has two different parameters:
- `temporal_patch_size`: Groups consecutive frames together temporally (default 2)
- `merge_size`: Groups pixels spatially (default 2)

When calculating timestamps, we're grouping frames temporally to compute their average timestamp. Using `merge_size` instead of `temporal_patch_size` produces incorrect timestamp values because:
1. The grouping factor could be different between spatial and temporal dimensions
2. Conceptually, we're averaging timestamps across time, not space

### Solution

Use `temporal_patch_size` for timestamp calculation:

```python
# After (correct)
curr_timestamp = self._calculate_timestamps(
    metadata.frames_indices,
    metadata.fps,
    self.video_processor.temporal_patch_size,  # Correct!
)
```

The fix is applied to both `processing_qwen3_vl.py` and `modular_qwen3_vl.py`.

## Who can review?

VLM maintainers

Changed files:
filename: src/transformers/models/qwen3_vl/modular_qwen3_vl.py
patch: @@ -1509,7 +1509,7 @@ def __call__(
                     curr_timestamp = self._calculate_timestamps(
                         metadata.frames_indices,
                         metadata.fps,
-                        self.video_processor.merge_size,
+                        self.video_processor.temporal_patch_size,
                     )
 
                     video_placeholder = ""

filename: src/transformers/models/qwen3_vl/processing_qwen3_vl.py
patch: @@ -152,7 +152,7 @@ def __call__(
                     curr_timestamp = self._calculate_timestamps(
                         metadata.frames_indices,
                         metadata.fps,
-                        self.video_processor.merge_size,
+                        self.video_processor.temporal_patch_size,
                     )
 
                     video_placeholder = ""
Repository: ollama/ollama
Pull request: skip quantizing per_layer_token_embd

this tensor isn't compatible with cuda when quantized to q4_K so skip it

Changed files:
filename: server/quantization.go
patch: @@ -231,6 +231,8 @@ func newType(t *fsggml.Tensor, kv fsggml.KV, qs *quantizeState, ftype fsggml.Fil
 	// do not quantize relative position bias (T5)
 	quantize = quantize && !strings.Contains(name, "attn_rel_b.weight")
 
+	quantize = quantize && !strings.Contains(name, "per_layer_token_embd.weight")
+
 	newType := fsggml.TensorType(t.Kind)
 	if quantize {
 		// get more optimal quantization type based on the tensor shape, layer, etc.
Repository: vuejs/vue
Pull request: fix(ssr): textarea keeps undefined/null values

<!--
Please make sure to read the Pull Request Guidelines:
https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#pull-request-guidelines
-->

<!-- PULL REQUEST TEMPLATE -->
<!-- (Update "[ ]" to "[x]" to check a box) -->

**What kind of change does this PR introduce?** (check at least one)

- [x] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [ ] Other, please describe:

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

If yes, please describe the impact and migration path for existing applications:

**The PR fulfills these requirements:**

- [x] It's submitted to the `dev` branch for v2.x (or to a previous version branch), _not_ the `master` branch
- [x] When resolving a specific issue, it's referenced in the PR's title (e.g. `fix #xxx[,#xxx]`, where "xxx" is the issue number)
- [x] All tests are passing: https://github.com/vuejs/vue/blob/dev/.github/CONTRIBUTING.md#development-setup
- [x] New/updated tests are included

If adding a **new feature**, the PR's description includes:
- [ ] A convincing reason for adding this feature (to avoid wasting your time, it's best to open a suggestion issue first and wait for approval before working on it)

**Other information:**
Closes #10803 

Changed files:
filename: src/platforms/web/server/modules/dom-props.js
patch: @@ -2,7 +2,7 @@
 
 import VNode from 'core/vdom/vnode'
 import { renderAttr } from './attrs'
-import { isDef, isUndef, extend } from 'shared/util'
+import { isDef, isUndef, extend, toString } from 'shared/util'
 import { propsToAttrMap, isRenderableAttr } from '../util'
 
 export default function renderDOMProps (node: VNodeWithData): string {
@@ -28,7 +28,7 @@ export default function renderDOMProps (node: VNodeWithData): string {
     } else if (key === 'textContent') {
       setText(node, props[key], false)
     } else if (key === 'value' && node.tag === 'textarea') {
-      setText(node, props[key], false)
+      setText(node, toString(props[key]), false)
     } else {
       // $flow-disable-line (WTF?)
       const attr = propsToAttrMap[key] || key.toLowerCase()

filename: test/ssr/ssr-string.spec.js
patch: @@ -1594,6 +1594,25 @@ describe('SSR: renderToString', () => {
 
     renderToString(vueInstance, err => done(err))
   })
+
+  it('undefined v-model with textarea', done => {
+    renderVmWithOptions({
+      render (h) {
+        return h('div', [
+          h('textarea', {
+            domProps: {
+              value: null
+            }
+          })
+        ])
+      }
+    }, result => {
+      expect(result).toContain(
+        '<div data-server-rendered="true"><textarea></textarea></div>'
+      )
+      done()
+    })
+  })
 })
 
 function renderVmWithOptions (options, cb) {
Repository: vercel/next.js
Pull request: fix(image): findClosestQuality returns 0 for low quality values

Fixes #89620

Fix `findClosestQuality` returning `0` when the `quality` prop on `<Image>` is set to a low value (e.g. `quality={1}`), which causes the image optimization server to reject the request with a 400 error.

### Cause

The `reduce` call in `findClosestQuality` used `0` as its initial accumulator. Since `0` is not a valid quality value (must be 1-100), it would win the "closest" comparison for any `quality <= 37` with the default `qualities: [75]` config. This produced `q=0` in the image URL, which the server rejects.

### Fix Description

Changed the `reduce` initializer from `0` to `config.qualities[0]`. This is safe because the early return above already handles the empty array case, so `config.qualities[0]` is always defined when reached.

Added a unit test for `quality=1` with `qualities=[75]` to verify it returns `75` instead of `0`.


Changed files:
filename: packages/next/src/shared/lib/find-closest-quality.ts
patch: @@ -16,6 +16,6 @@ export function findClosestQuality(
   }
   return config.qualities.reduce(
     (prev, cur) => (Math.abs(cur - q) < Math.abs(prev - q) ? cur : prev),
-    0
+    config.qualities[0]
   )
 }

filename: test/unit/image-optimizer/find-closest-quality.test.ts
patch: @@ -71,6 +71,18 @@ describe('findClosestQuality', () => {
       input: [14, { qualities: [100, 10, 75, 15] }],
       output: 15, // use closet input even when config is out of order
     },
+    {
+      input: [1, { qualities: [75] }],
+      output: 75, // low quality should not return 0
+    },
+    {
+      input: [4, { qualities: [5, 25] }],
+      output: 5, // ensure low quality still rounds up
+    },
+    {
+      input: [6, { qualities: [5, 25] }],
+      output: 5, // ensure low quality still rounds down
+    },
   ])('for quality $input expected $output', ({ input, output }) => {
     expect(findClosestQuality(...input)).toEqual(output)
   })
Repository: nodejs/node
Pull request: test: print stack immediately avoiding GC interleaving

`require(mod)` does not keep the mod in require cache if mod throws synchronously.
This fixes the tests to print the stack immediately in case that source map cache
could be cleaned up when the CJS module is reclaimed by GC in the next event loop
tick.

Refs: https://github.com/nodejs/node/pull/61002#issuecomment-3846108521

Changed files:
filename: lib/internal/source_map/source_map_cache_map.js
patch: @@ -13,6 +13,9 @@ const {
     source_map_data_private_symbol,
   },
 } = internalBinding('util');
+let debug = require('internal/util/debuglog').debuglog('source_map', (fn) => {
+  debug = fn;
+});
 
 /**
  * Specialized map of WeakRefs to module instances that caches source map
@@ -46,6 +49,7 @@ class SourceMapCacheMap {
     ArrayPrototypeForEach(keys, (key) => {
       const ref = this.#weakModuleMap.get(key);
       if (ref && ref.deref() === undefined) {
+        debug(`Cleanup obsolete source map cache entry with key: ${key}`);
         this.#weakModuleMap.delete(key);
       }
     });

filename: test/fixtures/source-map/output/source_map_sourcemapping_url_string.js
patch: @@ -7,7 +7,5 @@ Error.stackTraceLimit = 2;
 try {
   require('../typescript-sourcemapping_url_string');
 } catch (err) {
-  setTimeout(() => {
-    console.info(err);
-  }, 10);
+  console.info(err);
 }

filename: test/fixtures/source-map/output/source_map_throw_catch.js
patch: @@ -7,7 +7,5 @@ Error.stackTraceLimit = 2;
 try {
   require('../typescript-throw');
 } catch (err) {
-  setTimeout(() => {
-    console.info(err);
-  }, 10);
+  console.info(err);
 }
Repository: ollama/ollama
Pull request: fs/ggml: add multiplier in graph estimates


Changed files:
filename: fs/ggml/ggml.go
patch: @@ -555,7 +555,7 @@ func (f GGML) GraphSize(context, batch uint64, numParallel int, kvCacheType stri
 			// vocab graph
 			4*batch*(embedding+vocab)+embedding*vocab*105/128,
 		)
-	case "gemma", "gemma2", "gemma3":
+	case "gemma", "gemma2", "gemma3", "gemma3n":
 		fullOffload = max(
 			4*batch*(embedding+vocab),
 			4*batch*(2+context+context*heads+2*embedding+2*embeddingHeadsK*heads),
@@ -568,6 +568,11 @@ func (f GGML) GraphSize(context, batch uint64, numParallel int, kvCacheType stri
 				embedding*embeddingHeadsK*heads*9/16,
 		)
 
+		if f.KV().Architecture() == "gemma3n" {
+			fullOffload *= 4
+			partialOffload *= 4
+		}
+
 		// Gemma2 also has sliding window attention but we only have an optimized implementation in the Ollama
 		// engine. Gemma3 always uses the Ollama engine.
 		if f.KV().Architecture() == "gemma3" {
Repository: nodejs/node
Pull request: doc: document `url.format(urlString)` as deprecated under DEP0169

Because `url.format("...")` passes its argument via `url.parse()` before formatting it, this usage is covered under the application-runtime deprecation behaviour of DEP0169. This was not previously documented.

Separating out the documentation for `url.format(urlString)` from `url.format(urlObject)` seems like the cleanest approach. The latter signature remains legacy.

Changed files:
filename: doc/api/deprecations.md
patch: @@ -3776,6 +3776,9 @@ Type: Application (non-`node_modules` code only)
 have security implications. Use the [WHATWG URL API][] instead. CVEs are not
 issued for `url.parse()` vulnerabilities.
 
+Passing a string argument to [`url.format()`][] invokes `url.parse()`
+internally, and is therefore also covered by this deprecation.
+
 ### DEP0170: Invalid port when using `url.parse()`
 
 <!-- YAML

filename: doc/api/url.md
patch: @@ -1739,9 +1739,8 @@ changes:
                  times.
 -->
 
-* `urlObject` {Object|string} A URL object (as returned by `url.parse()` or
-  constructed otherwise). If a string, it is converted to an object by passing
-  it to `url.parse()`.
+* `urlObject` {Object} A URL object (as returned by `url.parse()` or
+  constructed otherwise).
 
 The `url.format()` method returns a formatted URL string derived from
 `urlObject`.
@@ -1822,6 +1821,48 @@ An automated migration is available ([source](https://github.com/nodejs/userland
 npx codemod@latest @nodejs/node-url-to-whatwg-url
 ```
 
+### `url.format(urlString)`
+
+<!-- YAML
+added: v0.1.25
+changes:
+  - version:
+      - v24.0.0
+    pr-url: https://github.com/nodejs/node/pull/55017
+    description: Application deprecation.
+-->
+
+> Stability: 0 - Deprecated: Use the WHATWG URL API instead.
+
+* `urlString` {string} A string that will be passed to `url.parse()` and then
+  formatted.
+
+`url.format(urlString)` is shorthand for `url.format(url.parse(urlString))`.
+
+Because it invokes the deprecated [`url.parse()`][], passing a string argument
+to `url.format()` is itself deprecated.
+
+Canonicalizing a URL string can be performed using the WHATWG URL API, by
+constructing a new URL object and calling [`url.toString()`][].
+
+```mjs
+import { URL } from 'node:url';
+
+const unformatted = 'http://[fe80:0:0:0:0:0:0:1]:/a/b?a=b#abc';
+const formatted = new URL(unformatted).toString();
+
+console.log(formatted); // Prints: http://[fe80::1]/a/b?a=b#abc
+```
+
+```cjs
+const { URL } = require('node:url');
+
+const unformatted = 'http://[fe80:0:0:0:0:0:0:1]:/a/b?a=b#abc';
+const formatted = new URL(unformatted).toString();
+
+console.log(formatted); // Prints: http://[fe80::1]/a/b?a=b#abc
+```
+
 ### `url.parse(urlString[, parseQueryString[, slashesDenoteHost]])`
 
 <!-- YAML
Repository: ggml-org/llama.cpp
Pull request: fix-pointer-dangling

<!--In the JNI layer of the sample Android program, when calling processUserInput, the pointer of user_prompt is freed before being referenced, and if the memory is overwritten during this period, it will not be possible to correctly retrieve the input.
-->

Changed files:
filename: examples/llama.android/lib/src/main/cpp/ai_chat.cpp
patch: @@ -365,13 +365,13 @@ Java_com_arm_aichat_internal_InferenceEngineImpl_processSystemPrompt(
     const auto *system_prompt = env->GetStringUTFChars(jsystem_prompt, nullptr);
     LOGd("%s: System prompt received: \n%s", __func__, system_prompt);
     std::string formatted_system_prompt(system_prompt);
-    env->ReleaseStringUTFChars(jsystem_prompt, system_prompt);
 
     // Format system prompt if applicable
     const bool has_chat_template = common_chat_templates_was_explicit(g_chat_templates.get());
     if (has_chat_template) {
         formatted_system_prompt = chat_add_and_format(ROLE_SYSTEM, system_prompt);
     }
+    env->ReleaseStringUTFChars(jsystem_prompt, system_prompt);
 
     // Tokenize system prompt
     const auto system_tokens = common_tokenize(g_context, formatted_system_prompt,
@@ -414,13 +414,13 @@ Java_com_arm_aichat_internal_InferenceEngineImpl_processUserPrompt(
     const auto *const user_prompt = env->GetStringUTFChars(juser_prompt, nullptr);
     LOGd("%s: User prompt received: \n%s", __func__, user_prompt);
     std::string formatted_user_prompt(user_prompt);
-    env->ReleaseStringUTFChars(juser_prompt, user_prompt);
 
     // Format user prompt if applicable
     const bool has_chat_template = common_chat_templates_was_explicit(g_chat_templates.get());
     if (has_chat_template) {
         formatted_user_prompt = chat_add_and_format(ROLE_USER, user_prompt);
     }
+    env->ReleaseStringUTFChars(juser_prompt, user_prompt);
 
     // Decode formatted user prompts
     auto user_tokens = common_tokenize(g_context, formatted_user_prompt, has_chat_template, has_chat_template);
Repository: ollama/ollama
Pull request: fs/ggml: add missing architecture to OllamaEngineRequired()


Changed files:
filename: fs/ggml/ggml.go
patch: @@ -174,6 +174,7 @@ func (kv KV) Bools(key string, defaultValue ...[]bool) []bool {
 func (kv KV) OllamaEngineRequired() bool {
 	return slices.Contains([]string{
 		"gemma3",
+		"gemma3n",
 		"mistral3",
 		"llama4",
 		"mllama",
Repository: facebook/react
Pull request: [DevTools] Avoid tearing Suspense store

Same as https://github.com/facebook/react/pull/34119 but for the Suspense store

Changed files:
filename: packages/react-devtools-shared/src/devtools/views/SuspenseTab/SuspenseRects.js
patch: @@ -55,7 +55,7 @@ function SuspenseRects({
 
   const suspense = store.getSuspenseByID(suspenseID);
   if (suspense === null) {
-    console.warn(`<Element> Could not find suspense node id ${suspenseID}`);
+    // getSuspenseByID will have already warned
     return null;
   }
 

filename: packages/react-devtools-shared/src/devtools/views/SuspenseTab/SuspenseTreeContext.js
patch: @@ -81,7 +81,7 @@ function SuspenseTreeContextController({children}: Props): React.Node {
 
   useEffect(() => {
     const handleSuspenseTreeMutated = () => {
-      transitionDispatch({
+      dispatch({
         type: 'HANDLE_SUSPENSE_TREE_MUTATION',
       });
     };
@@ -91,7 +91,7 @@ function SuspenseTreeContextController({children}: Props): React.Node {
       // At the moment, we can treat this as a mutation.
       // We don't know which Elements were newly added/removed, but that should be okay in this case.
       // It would only impact the search state, which is unlikely to exist yet at this point.
-      transitionDispatch({
+      dispatch({
         type: 'HANDLE_SUSPENSE_TREE_MUTATION',
       });
     }
Repository: huggingface/transformers
Pull request: Fix slack-report workflow file

# What does this PR do?



Changed files:
filename: .github/workflows/slack-report.yml
patch: @@ -94,6 +94,7 @@ jobs:
           pip install huggingface_hub
           pip install slack_sdk
           pip show slack_sdk
+          pip install .
           if [ "$quantization_matrix" != "" ]; then
             python utils/notification_service.py "$quantization_matrix"
           else
Repository: vuejs/vue
Pull request: [automated] Patreon sponsors update

This is an automated pull request.

Changed files:
filename: BACKERS.md
patch: @@ -21,7 +21,7 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
     <img width="260px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/stdlib.png">
   </a>
 </p>
-
+  
 <!--special end-->
 
 <h2 align="center">Platinum via Patreon</h2>
@@ -236,6 +236,11 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
           <img width="148px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/staff_augmentation.png">
         </a>
       </td>
+      <td align="center" valign="middle">
+        <a href="https://piratebay.ink" target="_blank">
+          <img width="148px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/piratebay_proxy.png">
+        </a>
+      </td>
     </tr><tr></tr>
   </tbody>
 </table>

filename: README.md
patch: @@ -241,6 +241,11 @@ Funds donated via Patreon go directly to support Evan You's full-time work on Vu
           <img width="148px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/staff_augmentation.png">
         </a>
       </td>
+      <td align="center" valign="middle">
+        <a href="https://piratebay.ink" target="_blank">
+          <img width="148px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/piratebay_proxy.png">
+        </a>
+      </td>
     </tr><tr></tr>
   </tbody>
 </table>
Repository: facebook/react
Pull request: Fix Flow issue from land race

A Flow upgrade removed the bundled library definitinos for SynthaticEvent and we probably want to use our internal definitions. Those are not properly typed at this point yet, but we can look into that as a followup.


Changed files:
filename: packages/react-devtools-shared/src/devtools/views/SuspenseTab/SuspenseTimeline.js
patch: @@ -24,6 +24,10 @@ import {TreeDispatcherContext} from '../Components/TreeContext';
 import {useHighlightHostInstance} from '../hooks';
 import {SuspenseTreeStateContext} from './SuspenseTreeContext';
 import styles from './SuspenseTimeline.css';
+import typeof {
+  SyntheticEvent,
+  SyntheticPointerEvent,
+} from 'react-dom-bindings/src/events/SyntheticEvent';
 
 // TODO: This returns the roots which would mean we attempt to suspend the shell.
 // Suspending the shell is currently not supported and we don't have a good view
@@ -126,7 +130,7 @@ export default function SuspenseTimeline(): React$Node {
     });
   }, [timeline, value]);
 
-  function handleChange(event: SyntheticEvent<HTMLInputElement>) {
+  function handleChange(event: SyntheticEvent) {
     const pendingValue = +event.currentTarget.value;
     for (let i = 0; i < timeline.length; i++) {
       const forceFallback = i > pendingValue;
@@ -164,7 +168,7 @@ export default function SuspenseTimeline(): React$Node {
     highlightHostInstance(suspense.id);
   }
 
-  function handlePointerMove(event: SyntheticPointerEvent<HTMLInputElement>) {
+  function handlePointerMove(event: SyntheticPointerEvent) {
     const bbox = inputBBox.current;
     if (bbox === null) {
       throw new Error('Bounding box of slider is unknown.');
Repository: ggml-org/llama.cpp
Pull request: [SYCL] fix wrong variable check by assert

Fix the issue: https://github.com/ggml-org/llama.cpp/pull/19920#issuecomment-4107430630
Correct the variable to be checked by assert.

Changed files:
filename: ggml/src/ggml-sycl/add-id.cpp
patch: @@ -56,7 +56,7 @@ void ggml_sycl_add_id(ggml_backend_sycl_context& ctx, ggml_tensor* dst) {
   float* dst_d = (float*)dst->data;
 
   const unsigned int max_work_group_size = ggml_sycl_info().max_work_group_sizes[ctx.device];
-  assert(work_group_size % (WARP_SIZE * WARP_SIZE) == 0);
+  GGML_ASSERT(max_work_group_size % (WARP_SIZE * WARP_SIZE) == 0);
 
   int threads = std::min((unsigned int)ne00, max_work_group_size);  // cols