helloadhavan/github_issues huggingface dataset:
Repository: facebook/react
Pull request: [Flight] Don't dedupe references to deferred objects

If we're about to defer an object, then we shouldn't store a reference to it because then we can end up deduping by referring to the deferred string. If in a different context, we should still be able to emit the object.

Changed files:
filename: packages/react-server/src/ReactFlightServer.js
patch: @@ -4345,6 +4345,12 @@ function renderDebugModel(
       if (parentReference !== undefined) {
         // If the parent has a reference, we can refer to this object indirectly
         // through the property name inside that parent.
+        if (counter.objectLimit <= 0 && !doNotLimit.has(value)) {
+          // If we are going to defer this, don't dedupe it since then we'd dedupe it to be
+          // deferred in future reference.
+          return serializeDeferredObject(request, value);
+        }
+
         let propertyName = parentPropertyName;
         if (isArray(parent) && parent[0] === REACT_ELEMENT_TYPE) {
           // For elements, we've converted it to an array but we'll have converted
Repository: ollama/ollama
Pull request: fix(integration): move waitgroup Add(1) outside goroutine to avoid potential issue

Detailed description:
- Moved waitgroup.Add(1) out of the goroutine to ensure the WaitGroup counter is properly set before any goroutine starts.
- Prevents potential issues where waitgroup.Wait() might return prematurely due to scheduling delays.
- Aligns with best practices for using sync.WaitGroup.

Changed files:
filename: integration/max_queue_test.go
patch: @@ -52,8 +52,8 @@ func TestMaxQueue(t *testing.T) {
 	embedCtx := ctx
 
 	var genwg sync.WaitGroup
+	genwg.Add(1)
 	go func() {
-		genwg.Add(1)
 		defer genwg.Done()
 		slog.Info("Starting generate request")
 		DoGenerate(ctx, t, client, req, resp, 45*time.Second, 5*time.Second)
@@ -71,8 +71,8 @@ func TestMaxQueue(t *testing.T) {
 	counterMu := sync.Mutex{}
 	var embedwg sync.WaitGroup
 	for i := 0; i < threadCount; i++ {
+		embedwg.Add(1)
 		go func(i int) {
-			embedwg.Add(1)
 			defer embedwg.Done()
 			slog.Info("embed started", "id", i)
 			embedReq := api.EmbeddingRequest{
Repository: vuejs/vue
Pull request: [automated] Patreon sponsors update

This is an automated pull request.

Changed files:
filename: BACKERS.md
patch: @@ -214,6 +214,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/shopware_ag.svg">
         </a>
       </td>
+      <td align="center" valign="middle">
+        <a href="http://x-team.com/join" target="_blank">
+          <img width="148px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/x_team.png">
+        </a>
+      </td>
     </tr><tr></tr>
   </tbody>
 </table>

filename: README.md
patch: @@ -219,6 +219,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/shopware_ag.svg">
         </a>
       </td>
+      <td align="center" valign="middle">
+        <a href="http://x-team.com/join" target="_blank">
+          <img width="148px" src="https://raw.githubusercontent.com/vuejs/vuejs.org/master/themes/vue/source/images/x_team.png">
+        </a>
+      </td>
     </tr><tr></tr>
   </tbody>
 </table>
Repository: ggml-org/llama.cpp
Pull request: Fix model selector locked to first loaded model with multiple models

*Make sure to read the [contributing guidelines](https://github.com/ggml-org/llama.cpp/blob/master/CONTRIBUTING.md) before submitting a PR*

## Fix model selector locked to first loaded model with multiple models

<img width="799" height="509" alt="auto-select" src="https://github.com/user-attachments/assets/ff8cea34-d5b4-4006-b67e-389c2468a99e" />

Fixes a regression from #20403 where, with multiple models loaded in
router mode, the user could not switch to any model other than the first
one.

The auto-select `$effect` in `ChatFormActions` was re-firing on every
`loadedModelIds` change (e.g. after `fetchRouterModels` completes),
overriding whatever the user had manually picked.

**Fix:** guard the else-if branch with `!modelsStore.selectedModelId` so
auto-select only kicks in when no model is chosen yet.

Close #20488

Changed files:
filename: tools/server/webui/src/lib/components/app/chat/ChatForm/ChatFormActions/ChatFormActions.svelte
patch: @@ -65,7 +65,8 @@
 	$effect(() => {
 		if (conversationModel) {
 			modelsStore.selectModelByName(conversationModel);
-		} else if (isRouter && modelsStore.loadedModelIds.length > 0) {
+		} else if (isRouter && !modelsStore.selectedModelId && modelsStore.loadedModelIds.length > 0) {
+			// auto-select the first loaded model only when nothing is selected yet
 			const first = modelOptions().find((m) => modelsStore.loadedModelIds.includes(m.model));
 			if (first) modelsStore.selectModelById(first.id);
 		}
Repository: ollama/ollama
Pull request: Update README.md

Corrected the URL so it does not say document not found. Pointing it to the main repository and stats for easy access.

Changed files:
filename: README.md
patch: @@ -291,7 +291,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Typescript UI](https://github.com/ollama-interface/Ollama-Gui?tab=readme-ov-file)
 - [Minimalistic React UI for Ollama Models](https://github.com/richawo/minimal-llm-ui)
 - [Ollamac](https://github.com/kevinhermawan/Ollamac)
-- [big-AGI](https://github.com/enricoros/big-AGI/blob/main/docs/config-local-ollama.md)
+- [big-AGI](https://github.com/enricoros/big-AGI) 
 - [Cheshire Cat assistant framework](https://github.com/cheshire-cat-ai/core)
 - [Amica](https://github.com/semperai/amica)
 - [chatd](https://github.com/BruceMacD/chatd)
Repository: ollama/ollama
Pull request: Update README.md

[GGUF-to-Ollama](https://github.com/jonathanhecl/gguf-to-ollama) - Importing GGUF to Ollama made easy

Changed files:
filename: README.md
patch: @@ -440,6 +440,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [DeepShell](https://github.com/Abyss-c0re/deepshell) Your self-hosted AI assistant. Interactive Shell, Files and Folders analysis.
 - [orbiton](https://github.com/xyproto/orbiton) Configuration-free text editor and IDE with support for tab completion with Ollama.
 - [orca-cli](https://github.com/molbal/orca-cli) Ollama Registry CLI Application - Browse, pull and download models from Ollama Registry in your terminal.
+- [GGUF-to-Ollama](https://github.com/jonathanhecl/gguf-to-ollama) - Importing GGUF to Ollama made easy (multiplatform)
 
 ### Apple Vision Pro
Repository: huggingface/transformers
Pull request: Fix lm_head weight tying in Mistral3ForConditionalGeneration

## Problem
Ministral-3-3B-Instruct-2512 generates gibberish because `lm_head.weight` is not tied to `embed_tokens.weight`.

## Root Cause  
The Ministral-3-3B config has `text_config.tie_word_embeddings=True`, and the checkpoint only stores `model.language_model.embed_tokens.weight` (no `lm_head.weight`).  
However, for Mistral3 the top-level `config.tie_word_embeddings` was never set, so the base tying logic that relies on `_tied_weights_keys` was effectively disabled and `lm_head.weight` was randomly initialized.

## Solution
Instead of overriding `tie_weights()`, set `tie_word_embeddings=True` by default in `Mistral3Config` so that the existing weight-tying mechanism (`_tied_weights_keys = {"lm_head.weight": "model.language_model.embed_tokens.weight"}`) is applied correctly to Mistral3-based VLMs.

## Changes
- Updated `src/transformers/models/mistral3/configuration_mistral3.py`:
  - Added a `tie_word_embeddings: bool = True` argument to `Mistral3Config.__init__`
  - Stored it as `self.tie_word_embeddings`

Changed files:
filename: src/transformers/models/mistral3/configuration_mistral3.py
patch: @@ -44,6 +44,8 @@ class Mistral3Config(PreTrainedConfig):
             Whether to use bias in the multimodal projector.
         spatial_merge_size (`int`, *optional*, defaults to 2):
             The downsampling factor for the spatial merge operation.
+        tie_word_embeddings (`bool`, *optional*, defaults to `True`):
+            Whether to tie the input and output embeddings.
 
     Example:
 
@@ -82,6 +84,7 @@ def __init__(
         vision_feature_layer=-1,
         multimodal_projector_bias=False,
         spatial_merge_size=2,
+        tie_word_embeddings: bool = True,
         **kwargs,
     ):
         self.image_token_index = image_token_index
@@ -133,6 +136,7 @@ def __init__(
         self.text_config = text_config
         self.multimodal_projector_bias = multimodal_projector_bias
         self.spatial_merge_size = spatial_merge_size
+        self.tie_word_embeddings = tie_word_embeddings
 
         super().__init__(**kwargs)
Repository: facebook/react
Pull request: [compiler] Fix for consecutive DCE'd branches with phis


This is an optimized version of @asmjmp0's fix in https://github.com/facebook/react/pull/31940. When we merge consecutive blocks we need to take care to rewrite later phis whose operands will now be different blocks due to merging. Rather than iterate all the blocks on each merge as in #31940, we can do a single iteration over all the phis at the end to fix them up.

Note: this is a redo of #31959

---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/react/pull/33725).
* #33726
* __->__ #33725

Changed files:
filename: compiler/packages/babel-plugin-react-compiler/src/HIR/MergeConsecutiveBlocks.ts
patch: @@ -107,6 +107,17 @@ export function mergeConsecutiveBlocks(fn: HIRFunction): void {
     merged.merge(block.id, predecessorId);
     fn.body.blocks.delete(block.id);
   }
+  for (const [, block] of fn.body.blocks) {
+    for (const phi of block.phis) {
+      for (const [predecessorId, operand] of phi.operands) {
+        const mapped = merged.get(predecessorId);
+        if (mapped !== predecessorId) {
+          phi.operands.delete(predecessorId);
+          phi.operands.set(mapped, operand);
+        }
+      }
+    }
+  }
   markPredecessors(fn.body);
   for (const [, {terminal}] of fn.body.blocks) {
     if (terminalHasFallthrough(terminal)) {

filename: compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/repro-missing-phi-after-dce-merge-scopes.expect.md
patch: @@ -0,0 +1,52 @@
+
+## Input
+
+```javascript
+function Component() {
+  let v3, v4, acc;
+  v3 = false;
+  v4 = v3;
+  acc = v3;
+  if (acc) {
+    acc = true;
+    v3 = acc;
+  }
+  if (acc) {
+    v3 = v4;
+  }
+  v4 = v3;
+  return [acc, v3, v4];
+}
+
+export const FIXTURE_ENTRYPOINT = {
+  fn: Component,
+  params: [],
+};
+
+```
+
+## Code
+
+```javascript
+import { c as _c } from "react/compiler-runtime";
+function Component() {
+  const $ = _c(1);
+  let t0;
+  if ($[0] === Symbol.for("react.memo_cache_sentinel")) {
+    t0 = [false, false, false];
+    $[0] = t0;
+  } else {
+    t0 = $[0];
+  }
+  return t0;
+}
+
+export const FIXTURE_ENTRYPOINT = {
+  fn: Component,
+  params: [],
+};
+
+```
+      
+### Eval output
+(kind: ok) [false,false,false]
\ No newline at end of file

filename: compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/repro-missing-phi-after-dce-merge-scopes.js
patch: @@ -0,0 +1,20 @@
+function Component() {
+  let v3, v4, acc;
+  v3 = false;
+  v4 = v3;
+  acc = v3;
+  if (acc) {
+    acc = true;
+    v3 = acc;
+  }
+  if (acc) {
+    v3 = v4;
+  }
+  v4 = v3;
+  return [acc, v3, v4];
+}
+
+export const FIXTURE_ENTRYPOINT = {
+  fn: Component,
+  params: [],
+};
Repository: facebook/react
Pull request: [Flight] Don't track Promise stack if there's no owner

This is a compromise because there can be a lot of Promise instances created. They're useful because they generally provide a better stack when batching/pooled connections are used.

This restores stack collection for I/O nodes so we have something to fallback on if there's no owner.

That way we can at least get a name or something out of I/O that was spawned outside a render but mostly avoids collecting starting I/O outside of render.

Changed files:
filename: packages/react-server/src/ReactFlightAsyncSequence.js
patch: @@ -26,7 +26,7 @@ type PromiseWithDebugInfo = interface extends Promise<any> {
 export type IONode = {
   tag: 0,
   owner: null | ReactComponentInfo,
-  stack: null, // callsite that spawned the I/O
+  stack: null | ReactStackTrace, // callsite that spawned the I/O
   start: number, // start time when the first part of the I/O sequence started
   end: number, // we typically don't use this. only when there's no promise intermediate.
   promise: null, // not used on I/O

filename: packages/react-server/src/ReactFlightServerConfigDebugNode.js
patch: @@ -149,10 +149,11 @@ export function initAsyncDebugInfo(): void {
               previous: current === undefined ? null : current, // The path that led us here.
             }: UnresolvedAwaitNode);
           } else {
+            const owner = resolveOwner();
             node = ({
               tag: UNRESOLVED_PROMISE_NODE,
-              owner: resolveOwner(),
-              stack: parseStackTrace(new Error(), 5),
+              owner: owner,
+              stack: owner === null ? null : parseStackTrace(new Error(), 5),
               start: performance.now(),
               end: -1.1, // Set when we resolve.
               promise: new WeakRef((resource: Promise<any>)),
@@ -170,10 +171,11 @@ export function initAsyncDebugInfo(): void {
         ) {
           if (trigger === undefined) {
             // We have begun a new I/O sequence.
+            const owner = resolveOwner();
             node = ({
               tag: IO_NODE,
-              owner: resolveOwner(),
-              stack: null,
+              owner: owner,
+              stack: owner === null ? parseStackTrace(new Error(), 3) : null,
               start: performance.now(),
               end: -1.1, // Only set when pinged.
               promise: null,
@@ -185,10 +187,11 @@ export function initAsyncDebugInfo(): void {
             trigger.tag === UNRESOLVED_AWAIT_NODE
           ) {
             // We have begun a new I/O sequence after the await.
+            const owner = resolveOwner();
             node = ({
               tag: IO_NODE,
-              owner: resolveOwner(),
-              stack: null,
+              owner: owner,
+              stack: owner === null ? parseStackTrace(new Error(), 3) : null,
               start: performance.now(),
               end: -1.1, // Only set when pinged.
               promise: null,
Repository: huggingface/transformers
Pull request: fix gguf recent conversion issues

# What does this PR do?
Fixes #43452

Changed files:
filename: src/transformers/modeling_utils.py
patch: @@ -4113,7 +4113,7 @@ def from_pretrained(
 
         # If it is a model with generation capabilities, attempt to load generation files (generation config,
         # custom generate function)
-        if model.can_generate() and hasattr(model, "adjust_generation_fn"):
+        if model.can_generate() and hasattr(model, "adjust_generation_fn") and not gguf_file:
             model.adjust_generation_fn(
                 generation_config,
                 from_auto_class,

filename: src/transformers/models/qwen2/tokenization_qwen2.py
patch: @@ -42,8 +42,6 @@ def __init__(
         self,
         vocab: str | dict[str, int] | None = None,
         merges: str | list[str] | None = None,
-        vocab_file=None,
-        merges_file=None,
         unk_token: str = "
",
         bos_token=None,
         eos_token: str = "
",
@@ -89,8 +87,6 @@ def __init__(
         )
 
         super().__init__(
-            vocab_file=vocab_file,
-            merges_file=merges_file,
             unk_token=unk_token,
             bos_token=bos_token,
             eos_token=eos_token,

filename: src/transformers/tokenization_utils_base.py
patch: @@ -1607,6 +1607,7 @@ def from_pretrained(
 
         pretrained_model_name_or_path = str(pretrained_model_name_or_path)
         vocab_files = {}
+        additional_files_names = {}
         init_configuration = {}
 
         is_local = os.path.isdir(pretrained_model_name_or_path)

filename: src/transformers/tokenization_utils_tokenizers.py
patch: @@ -33,6 +33,8 @@
 from tokenizers.models import BPE, Unigram
 from tokenizers.trainers import BpeTrainer, UnigramTrainer, WordLevelTrainer, WordPieceTrainer
 
+from transformers.utils.hub import cached_file
+
 from .integrations.ggml import convert_gguf_tokenizer
 from .modeling_gguf_pytorch_utils import load_gguf_checkpoint
 from .tokenization_utils_base import (
@@ -250,7 +252,8 @@ def __init__(self, *args, **kwargs):
             fast_tokenizer = TokenizerFast.from_file(fast_tokenizer_file)
         elif gguf_file is not None:
             # We need to convert a slow tokenizer to build the backend
-            gguf_param = load_gguf_checkpoint(kwargs.get("vocab_file"))
+            gguf_path = cached_file(kwargs.get("name_or_path", ""), gguf_file, **kwargs)
+            gguf_param = load_gguf_checkpoint(gguf_path)
             architecture = gguf_param["config"]["model_type"]
             tokenizer_dict = gguf_param["tokenizer"]
             tokenizer_config = gguf_param["tokenizer_config"]
Repository: vercel/next.js
Pull request: [ci] Exclude tests by filename when merging manifests

Follow-up to #88824.

When merging multiple test manifests, a test file may be included in `suites` by one manifest, but excluded in `rules` by another. This change ensures that if a test file is excluded by filename (and not by pattern), the exclusion takes precedence over the inclusion.

Specifically, this allows us to skip Cache Components deploy tests via the `exclude` rules in `cache-components-tests-manifest.json`, even though those may be included in the `suites` of `deploy-tests-manifest.json`.

Alternatively, we could maintain separate deploy tests manifests for Cache Components and non-Cache Components deploy tests.

Changed files:
filename: test/get-test-filter.js
patch: @@ -80,7 +80,13 @@ function getTestFilter() {
       tests
         .filter((test) => {
           // Check to see if this was included as-is in the manifest.
-          if (test.file in manifest.suites) return true
+          if (test.file in manifest.suites) {
+            // When merging multiple manifests, a test file may be included in
+            // the suites by one manifest, but excluded in the rules by another.
+            // If it's excluded by filename (and not by pattern), the exclusion
+            // takes precedence over the inclusion.
+            return !manifest.rules.exclude?.includes(test.file)
+          }
 
           // If this file doesn't match any of the include patterns, then it
           // should be excluded.
Repository: facebook/react
Pull request: [Flight] Fix stack getting object limited

Because the object limit is unfortunately depth first due to limitations of JSON stringify, we need to ensure that things we really don't want outlined are first in the enumeration order.

We add the stack length to the object limit to ensure that the stack frames aren't outlined. In console all the user space arguments are at the end of the args. In server component props, the props are at the end of the properties of the element.

For the `value` of I/O we had it before the stack so it could steal the limit from the stack. The fix is to put it at the end.


Changed files:
filename: packages/react-server/src/ReactFlightServer.js
patch: @@ -4072,10 +4072,6 @@ function emitIOInfoChunk(
     start: relativeStartTimestamp,
     end: relativeEndTimestamp,
   };
-  if (value !== undefined) {
-    // $FlowFixMe[cannot-write]
-    debugIOInfo.value = value;
-  }
   if (env != null) {
     // $FlowFixMe[cannot-write]
     debugIOInfo.env = env;
@@ -4088,6 +4084,10 @@ function emitIOInfoChunk(
     // $FlowFixMe[cannot-write]
     debugIOInfo.owner = owner;
   }
+  if (value !== undefined) {
+    // $FlowFixMe[cannot-write]
+    debugIOInfo.value = value;
+  }
   const json: string = serializeDebugModel(request, objectLimit, debugIOInfo);
   const row = id.toString(16) + ':J' + json + '\n';
   const processedChunk = stringToChunk(row);
Repository: ollama/ollama
Pull request: Update README.md

There was a project that changed its name, so I went ahead and updated it to reflect on the Ollama Community Integrations.

Changed files:
filename: README.md
patch: @@ -348,7 +348,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [PartCAD](https://github.com/openvmp/partcad/) (CAD model generation with OpenSCAD and CadQuery)
 - [Ollama4j Web UI](https://github.com/ollama4j/ollama4j-web-ui) - Java-based Web UI for Ollama built with Vaadin, Spring Boot and Ollama4j
 - [PyOllaMx](https://github.com/kspviswa/pyOllaMx) - macOS application capable of chatting with both Ollama and Apple MLX models.
-- [Claude Dev](https://github.com/saoudrizwan/claude-dev) - VSCode extension for multi-file/whole-repo coding
+- [Cline](https://github.com/cline/cline) - Formerly known as Claude Dev is a VSCode extension for multi-file/whole-repo coding
 - [Cherry Studio](https://github.com/kangfenmao/cherry-studio) (Desktop client with Ollama support)
 - [ConfiChat](https://github.com/1runeberg/confichat) (Lightweight, standalone, multi-platform, and privacy focused LLM chat interface with optional encryption)
 - [Archyve](https://github.com/nickthecook/archyve) (RAG-enabling document library)
Repository: vuejs/vue
Pull request: Template compiler warning

**What kind of change does this PR introduce?** (check at least one)

- [ ] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [X] 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
- [ ] 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
- [ ] New/updated tests are included

If adding a **new feature**, the PR's description includes:
- [X] 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:**

This is the pull request I've created in response to the suggestion issue I submitted (#9734). In that issue, I was told there wasn't a test for this.


Changed files:
filename: packages/vue-template-compiler/index.js
patch: @@ -5,10 +5,12 @@ try {
 var packageName = require('./package.json').name
 var packageVersion = require('./package.json').version
 if (vueVersion && vueVersion !== packageVersion) {
+  var vuePath = require.resolve('vue')
+  var packagePath = require.resolve('./package.json')
   throw new Error(
     '\n\nVue packages version mismatch:\n\n' +
-    '- vue@' + vueVersion + '\n' +
-    '- ' + packageName + '@' + packageVersion + '\n\n' +
+    '- vue@' + vueVersion + ' (' + vuePath + ')\n' +
+    '- ' + packageName + '@' + packageVersion + ' (' + packagePath + ')\n\n' +
     'This may cause things to work incorrectly. Make sure to use the same version for both.\n' +
     'If you are using vue-loader@>=10.0, simply update vue-template-compiler.\n' +
     'If you are using vue-loader@<10.0 or vueify, re-installing vue-loader/vueify should bump ' + packageName + ' to the latest.\n'