helloadhavan/github_issues huggingface dataset:
Repository: nodejs/node
Pull request: test: aix: mark test-emit-on-destroyed as flaky

Re-enable the exclusion of this test which was re-enabled in https://github.com/nodejs/node/pull/51995 after previously being excluded in https://github.com/nodejs/node/issues/50262 as I /have/ been able to reproduce the failures in the CI 79/1000 times with the stress job this week.

Ref: https://github.com/nodejs/node/issues/50245

<!--
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/async-hooks/async-hooks.status
patch: @@ -21,3 +21,5 @@ test-callback-error: PASS, FLAKY
 [$system==freebsd]
 
 [$system==aix]
+# https://github.com/nodejs/node/issues/50245
+test-emit-after-on-destroyed: PASS, FLAKY
Repository: ggml-org/llama.cpp
Pull request: Fix KleidiAI FetchContent build failure on AGP CMake 3.22.1

Using `GGML_CPU_KLEIDIAI=ON` with AGP (CMake 3.22.1) fails because `DOWNLOAD_EXTRACT_TIMESTAMP` is passed unconditionally (this is only supported in newer cmake).

Changed files:
filename: ggml/src/ggml-cpu/CMakeLists.txt
patch: @@ -572,9 +572,11 @@ function(ggml_add_cpu_backend_variant_impl tag_name)
 
         set(KLEIDIAI_FETCH_ARGS
             URL ${KLEIDIAI_DOWNLOAD_URL}
-            DOWNLOAD_EXTRACT_TIMESTAMP NEW
             URL_HASH MD5=${KLEIDIAI_ARCHIVE_MD5}
         )
+        if (CMAKE_VERSION VERSION_GREATER_EQUAL "3.24")
+            list(APPEND KLEIDIAI_FETCH_ARGS DOWNLOAD_EXTRACT_TIMESTAMP NEW)
+        endif()
 
         if (CMAKE_VERSION VERSION_GREATER_EQUAL "3.28")
             FetchContent_Declare(KleidiAI_Download
Repository: ollama/ollama
Pull request: api: remove unused RetrieveModelResponse type


Changed files:
filename: api/types.go
patch: @@ -466,13 +466,6 @@ type ProcessModelResponse struct {
 	SizeVRAM  int64        `json:"size_vram"`
 }
 
-type RetrieveModelResponse struct {
-	Id      string `json:"id"`
-	Object  string `json:"object"`
-	Created int64  `json:"created"`
-	OwnedBy string `json:"owned_by"`
-}
-
 type TokenResponse struct {
 	Token string `json:"token"`
 }

filename: server/routes_test.go
patch: @@ -474,14 +474,14 @@ func TestRoutes(t *testing.T) {
 					t.Fatalf("failed to read response body: %v", err)
 				}
 
-				var retrieveResp api.RetrieveModelResponse
-				err = json.Unmarshal(body, &retrieveResp)
+				var m openai.Model
+				err = json.Unmarshal(body, &m)
 				if err != nil {
 					t.Fatalf("failed to unmarshal response body: %v", err)
 				}
 
-				if retrieveResp.Id != "show-model" || retrieveResp.OwnedBy != "library" {
-					t.Errorf("expected model 'show-model' owned by 'library', got %v", retrieveResp)
+				if m.Id != "show-model" || m.OwnedBy != "library" {
+					t.Errorf("expected model 'show-model' owned by 'library', got %v", m)
 				}
 			},
 		},
Repository: vuejs/vue
Pull request: fix(v-pre): do not alter attributes (fix #10087)

Fix #10087

<!--
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:**
When attributes under a v-pre match the list in `isBooleanAttr`, the value is replaced. This goes against the purpose of v-pre which is to leave all elements as-is.

An example of this bug can be found at https://jsfiddle.net/fp1omdaw/1/ as well as further details under #10087

Changed files:
filename: src/platforms/web/runtime/modules/attrs.js
patch: @@ -39,7 +39,7 @@ function updateAttrs (oldVnode: VNodeWithData, vnode: VNodeWithData) {
     cur = attrs[key]
     old = oldAttrs[key]
     if (old !== cur) {
-      setAttr(elm, key, cur)
+      setAttr(elm, key, cur, vnode.data.pre)
     }
   }
   // #4391: in IE9, setting type can reset value for input[type=radio]
@@ -59,8 +59,8 @@ function updateAttrs (oldVnode: VNodeWithData, vnode: VNodeWithData) {
   }
 }
 
-function setAttr (el: Element, key: string, value: any) {
-  if (el.tagName.indexOf('-') > -1) {
+function setAttr (el: Element, key: string, value: any, isInPre: any) {
+  if (isInPre || el.tagName.indexOf('-') > -1) {
     baseSetAttr(el, key, value)
   } else if (isBooleanAttr(key)) {
     // set attribute for blank value

filename: test/unit/features/directives/pre.spec.js
patch: @@ -42,4 +42,13 @@ describe('Directive v-pre', function () {
     vm.$mount()
     expect(vm.$el.firstChild.tagName).toBe('VTEST')
   })
+
+  // #10087
+  it('should not compile attributes', function () {
+    const vm = new Vue({
+      template: '<div v-pre><p open="hello">A Test</p></div>'
+    })
+    vm.$mount()
+    expect(vm.$el.firstChild.getAttribute('open')).toBe('hello')
+  })
 })
Repository: ollama/ollama
Pull request: fix data race in WriteGGUF

err in the go routine should not be shared with the outer scope

Changed files:
filename: fs/ggml/gguf.go
patch: @@ -569,7 +569,7 @@ func WriteGGUF(f *os.File, kv KV, ts []*Tensor) error {
 		t := t
 		w := io.NewOffsetWriter(f, offset+int64(t.Offset))
 		g.Go(func() error {
-			_, err = t.WriteTo(w)
+			_, err := t.WriteTo(w)
 			return err
 		})
 	}
Repository: vercel/next.js
Pull request: tweak LRU sentinel cache key

We originally prefixed the TTL sentinel with the null-byte separator to avoid collisions with real invocation IDs, but that makes `extractInvocationID` return "ttl" instead of undefined for TTL-mode keys.

This switches to a reserved magic string sentinel so TTL-mode entries are correctly treated as “no invocation ID”.

Changed files:
filename: packages/next/src/server/response-cache/index.ts
patch: @@ -63,10 +63,9 @@ const KEY_SEPARATOR = '\0'
 
 /**
  * Sentinel value used for TTL-based cache entries (when invocationID is undefined).
- * Uses KEY_SEPARATOR prefix to guarantee uniqueness since null bytes cannot appear
- * in HTTP headers (RFC 7230), making collision with real invocation IDs impossible.
+ * Chosen to be a clearly reserved marker for internal cache keys.
  */
-const TTL_SENTINEL = `${KEY_SEPARATOR}ttl`
+const TTL_SENTINEL = '__ttl_sentinel__'
 
 /**
  * Entry stored in the LRU cache.
Repository: huggingface/transformers
Pull request: [MoE] Use int input for histc on CUDA to support deterministic algorithms

# What does this PR do?

`torch.histc` with deterministic algorithms enabled behaves differently across devices:

**CPU**: only supports float input
**CUDA**: only supports int input

This PR updates `grouped_mm_experts_forward` to use the appropriate dtype based on device type, enabling compatibility with `torch.use_deterministic_algorithms(True)` on CUDA.

Simple reproduction script:
```
import torch

def test_histc_deterministic(device: str):
    print(f"\n=== Testing on {device.upper()} ===")
    
    num_experts = 8
    expert_ids = torch.randint(0, num_experts, (100,), device=device)
    
    torch.use_deterministic_algorithms(True)
    
    # Test float input
    try:
        result = torch.histc(expert_ids.float(), bins=num_experts, min=0, max=num_experts - 1)
        print(f"✅ float input works with deterministic mode")
    except RuntimeError as e:
        print(f"❌ float input fails: {e}")
    
    # Test int input
    try:
        result = torch.histc(expert_ids, bins=num_experts, min=0, max=num_experts - 1)
        print(f"✅ int input works with deterministic mode")
    except (RuntimeError, NotImplementedError) as e:
        print(f"❌ int input fails: {e}")
    
    torch.use_deterministic_algorithms(False)

if __name__ == "__main__":
    print(f"PyTorch version: {torch.__version__}")
    
    test_histc_deterministic("cpu")
    
    if torch.cuda.is_available():
        test_histc_deterministic("cuda")
```

Hi @vasqu , please help review this PR, thanks!

Changed files:
filename: src/transformers/integrations/moe.py
patch: @@ -226,7 +226,9 @@ def grouped_mm_experts_forward(
 
     # Compute offsets for grouped_mm
     # using histc instead of bincount to avoid cuda graph issues
-    num_tokens_per_expert = torch.histc(expert_ids_g.float(), bins=self.num_experts, min=0, max=self.num_experts - 1)
+    # With deterministic algorithms, CPU only supports float input, CUDA only supports int input.
+    histc_input = expert_ids_g.float() if device.type == "cpu" else expert_ids_g.int()
+    num_tokens_per_expert = torch.histc(histc_input, bins=self.num_experts, min=0, max=self.num_experts - 1)
     offsets = torch.cumsum(num_tokens_per_expert, dim=0, dtype=torch.int32)
 
     # --- Up projection per expert (grouped) ---
Repository: ggml-org/llama.cpp
Pull request: ci : clarify gh command for viewing issues

cont #20756 

- Clarify the `gh` command to use to avoid the agent just running `gh issue view 1234` and not getting any output
- Repurpose the action to search for "related", not "duplicate" issues


Changed files:
filename: .github/workflows/ai-issues.yml
patch: @@ -5,7 +5,7 @@ on:
     types: [opened]
 
 jobs:
-  find-duplicates:
+  find-related:
     if: github.event.action == 'opened'
     runs-on: [self-hosted, opencode]
 
@@ -19,7 +19,7 @@ jobs:
         with:
           fetch-depth: 1
 
-      - name: Find duplicates
+      - name: Find related
         env:
           GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
           OPENCODE_PERMISSION: |
@@ -35,15 +35,15 @@ jobs:
 
           Issue number: ${{ github.event.issue.number }}
 
-          Lookup this issue with gh issue view ${{ github.event.issue.number }}.
+          Lookup this issue with `gh issue view ${{ github.event.issue.number }} --json title,body,url,number`
 
           Perform the following task and then post a SINGLE comment (if needed).
 
           ---
 
-          TASK : DUPLICATE CHECK
+          TASK : FIND RELATED ISSUES
 
-          Search through existing issues (excluding #${{ github.event.issue.number }}) to find potential duplicates.
+          Search through existing issues (excluding #${{ github.event.issue.number }}) to find related or similar issues.
           Consider:
           1. Similar titles or descriptions
           2. Same error messages or symptoms
@@ -56,13 +56,13 @@ jobs:
 
           Based on your findings, post a SINGLE comment on issue #${{ github.event.issue.number }}. Build the comment as follows:
 
-          If no duplicates were found, do NOT comment at all.
+          If no related issues were found, do NOT comment at all.
 
-          If duplicates were found, include a section about potential duplicates with links using the following format:
+          If related issues were found, include a section listing them with links using the following format:
 
           [comment]
-          This issue might be a duplicate of:
-          - #[issue_number]: [brief description of similarity]
+          This issue might be similar or related to:
+          - #[issue_number]: [brief description of how they are related]
 
           _This comment was auto-generated locally using **$GA_ENGINE** on **$GA_MACHINE**_
           [/comment]
Repository: ggml-org/llama.cpp
Pull request: chat : handle tool calls with no required args in TAG_WITH_TAGGED format

regarding #20650

When a tool has no required args, the model may emit <tool_call>name</tool_call> with no arg tags. The grammar tried to peek ahead for an arg tag after the tool name, even when all args were optional, so the peek failed, and the tool call was not recognized.

Changed files:
filename: common/chat-auto-parser-generator.cpp
patch: @@ -369,7 +369,9 @@ common_peg_parser analyze_tools::build_tool_parser_tag_tagged(parser_build_conte
             func_parser = p.atomic(p.tool_open(function.name_prefix + p.tool_name(p.literal(name)) + function.name_suffix) +
                 call_id_section) + p.space() + args_seq;
             matched_atomic = true;
-        } else if (!arguments.name_prefix.empty() && properties.size() > 0) {
+        } else if (!arguments.name_prefix.empty() && !required_parsers.empty()) {
+            // Only peek for an arg tag when there are required args that must follow.
+            // When all args are optional, the model may emit no arg tags at all (#20650).
             func_parser = p.atomic(p.tool_open(function.name_prefix + p.tool_name(p.literal(name)) + function.name_suffix) +
                 call_id_section + p.space() + p.peek(p.literal(arguments.name_prefix))) + args_seq;
             matched_atomic = true;

filename: tests/test-chat.cpp
patch: @@ -1934,6 +1934,24 @@ static void test_template_output_peg_parsers(bool detailed_debug) {
                 { "special_function_with_opt", R"({"arg1": 1, "arg2": 2})", {} },
             })
             .run();
+
+        // #20650: tool with no required args, model emits <tool_call>name</tool_call> with no arg tags.
+        {
+            static common_chat_tool no_args_tool{
+                "read_file_diff_md", "Reads a file diff",
+                R"({"type":"object","properties":{"review_id":{"type":"string"},"file_id":{"type":"string"}}})",
+            };
+            tst.test(
+                   "Let me read the diff content."
+                   "</think>"
+                   "<tool_call>read_file_diff_md</tool_call>")
+                .enable_thinking(true)
+                .reasoning_format(COMMON_REASONING_FORMAT_DEEPSEEK)
+                .tools({ no_args_tool })
+                .expect_reasoning("Let me read the diff content.")
+                .expect_tool_calls({{ "read_file_diff_md", "{}", {} }})
+                .run();
+        }
     }
 
     // Kimi-K2-Thinking tests - custom parser
Repository: nodejs/node
Pull request: build,win: fix vs2022 compilation

When we added VS2026 support, by accident we broke VS2022 compilation if you have both VS2026 and VS2022 installed (eg, you had to provide the `vs2022` parameter). This PR fixes that bug.

Changed files:
filename: vcbuild.bat
patch: @@ -270,7 +270,7 @@ if %target_arch%==%msvs_host_arch% set vcvarsall_arg=%target_arch%
 
 @rem Look for Visual Studio 2026
 :vs-set-2026
-if defined target_env if "%target_env%" NEQ "vs2026" goto msbuild-not-found
+if defined target_env if "%target_env%" NEQ "vs2026" goto vs-set-2022
 echo Looking for Visual Studio 2026
 @rem VCINSTALLDIR may be set if run from a VS Command Prompt and needs to be
 @rem cleared first as vswhere_usability_wrapper.cmd doesn't when it fails to
Repository: vercel/next.js
Pull request: Update font data

This auto-generated PR updates font data with latest available

Changed files:
filename: packages/font/src/google/font-data.json
patch: @@ -7551,7 +7551,7 @@
   "Kedebideri": {
     "weights": ["400", "500", "600", "700", "800", "900"],
     "styles": ["normal"],
-    "subsets": ["latin"]
+    "subsets": ["beria-erfe", "latin"]
   },
   "Kelly Slab": {
     "weights": ["400"],

filename: packages/font/src/google/index.ts
patch: @@ -11920,7 +11920,7 @@ export declare function Kedebideri<
   preload?: boolean
   fallback?: string[]
   adjustFontFallback?: boolean
-  subsets?: Array<'latin'>
+  subsets?: Array<'beria-erfe' | 'latin'>
 }): T extends undefined ? NextFont : NextFontWithVariable
 export declare function Kelly_Slab<
   T extends CssVariable | undefined = undefined,
Repository: ollama/ollama
Pull request: Update README.md

Add Flufy

Changed files:
filename: README.md
patch: @@ -397,6 +397,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [1Panel](https://github.com/1Panel-dev/1Panel/) (Web-based Linux Server Management Tool)
 - [AstrBot](https://github.com/Soulter/AstrBot/) (User-friendly LLM-based multi-platform chatbot with a WebUI, supporting RAG, LLM agents, and plugins integration)
 - [Reins](https://github.com/ibrahimcetin/reins) (Easily tweak parameters, customize system prompts per chat, and enhance your AI experiments with reasoning model support.)
+- [Flufy](https://github.com/Aharon-Bensadoun/Flufy) (A beautiful chat interface for interacting with Ollama's API. Built with React, TypeScript, and Material-UI.)
 - [Ellama](https://github.com/zeozeozeo/ellama) (Friendly native app to chat with an Ollama instance)
 - [screenpipe](https://github.com/mediar-ai/screenpipe) Build agents powered by your screen history
 - [Ollamb](https://github.com/hengkysteen/ollamb) (Simple yet rich in features, cross-platform built with Flutter and designed for Ollama. Try the [web demo](https://hengkysteen.github.io/demo/ollamb/).)
Repository: vuejs/vue
Pull request: fix #11391: translate attribute had incorrectly the key as it's value

When present, translate attribute had translate as it's value, which is not valid, the value should
remain as specified by the user, that's why we removed it form isBooleanAttr map

fix #11391

<!--
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:**


Changed files:
filename: src/platforms/web/util/attrs.js
patch: @@ -35,7 +35,7 @@ export const isBooleanAttr = makeMap(
   'default,defaultchecked,defaultmuted,defaultselected,defer,disabled,' +
   'enabled,formnovalidate,hidden,indeterminate,inert,ismap,itemscope,loop,multiple,' +
   'muted,nohref,noresize,noshade,novalidate,nowrap,open,pauseonexit,readonly,' +
-  'required,reversed,scoped,seamless,selected,sortable,translate,' +
+  'required,reversed,scoped,seamless,selected,sortable,' +
   'truespeed,typemustmatch,visible'
 )
Repository: facebook/react
Pull request: [DevTools] Lazily compute initial Tree state

When we start out with no inspected element, we default to the last selected host instance. However, this can be an instance that is no longer rendered issuing warnings when we try to get its index.

Even though we no longer inspect that element, rendering the TreeContextController would issue warnings since the default state was computed on every render.

This gets rid of the warning by lazily computing the state.

Changed files:
filename: packages/react-devtools-shared/src/devtools/views/Components/TreeContext.js
patch: @@ -803,6 +803,45 @@ type Props = {
   defaultInspectedElementIndex?: ?number,
 };
 
+function getInitialState({
+  defaultOwnerID,
+  defaultInspectedElementID,
+  defaultInspectedElementIndex,
+  store,
+}: {
+  defaultOwnerID?: ?number,
+  defaultInspectedElementID?: ?number,
+  defaultInspectedElementIndex?: ?number,
+  store: Store,
+}): State {
+  return {
+    // Tree
+    numElements: store.numElements,
+    ownerSubtreeLeafElementID: null,
+
+    // Search
+    searchIndex: null,
+    searchResults: [],
+    searchText: '',
+
+    // Owners
+    ownerID: defaultOwnerID == null ? null : defaultOwnerID,
+    ownerFlatTree: null,
+
+    // Inspection element panel
+    inspectedElementID:
+      defaultInspectedElementID != null
+        ? defaultInspectedElementID
+        : store.lastSelectedHostInstanceElementId,
+    inspectedElementIndex:
+      defaultInspectedElementIndex != null
+        ? defaultInspectedElementIndex
+        : store.lastSelectedHostInstanceElementId
+          ? store.getIndexOfElementID(store.lastSelectedHostInstanceElementId)
+          : null,
+  };
+}
+
 // TODO Remove TreeContextController wrapper element once global Context.write API exists.
 function TreeContextController({
   children,
@@ -866,32 +905,16 @@ function TreeContextController({
     [store],
   );
 
-  const [state, dispatch] = useReducer(reducer, {
-    // Tree
-    numElements: store.numElements,
-    ownerSubtreeLeafElementID: null,
-
-    // Search
-    searchIndex: null,
-    searchResults: [],
-    searchText: '',
-
-    // Owners
-    ownerID: defaultOwnerID == null ? null : defaultOwnerID,
-    ownerFlatTree: null,
-
-    // Inspection element panel
-    inspectedElementID:
-      defaultInspectedElementID != null
-        ? defaultInspectedElementID
-        : store.lastSelectedHostInstanceElementId,
-    inspectedElementIndex:
-      defaultInspectedElementIndex != null
-        ? defaultInspectedElementIndex
-        : store.lastSelectedHostInstanceElementId
-          ? store.getIndexOfElementID(store.lastSelectedHostInstanceElementId)
-          : null,
-  });
+  const [state, dispatch] = useReducer(
+    reducer,
+    {
+      defaultOwnerID,
+      defaultInspectedElementID,
+      defaultInspectedElementIndex,
+      store,
+    },
+    getInitialState,
+  );
   const transitionDispatch = useMemo(
     () => (action: Action) =>
       startTransition(() => {