helloadhavan/github_issues huggingface dataset:
Repository: ollama/ollama
Pull request: Add vim-intelligence-bridge to Terminal section  in README

I'm proposing to add vim-intelligence-bridge to the Terminal section. This plugin is unique as it's the only one that integrates Ollama directly with traditional Vim (not Neovim). Key benefits:

- Expands Ollama's reach to Vim users
- Promotes local, private AI processing within Vim
- Enhances developer productivity by integrating Ollama in the Vim workflow

This addition showcases Ollama's versatility and encourages wider adoption in the developer community.
Proposed change:

[vim-intelligence-bridge](https://github.com/pepo-ec/vim-intelligence-bridge) Simple interaction of "Ollama" with the Vim editor

Changed files:
filename: README.md
patch: @@ -338,6 +338,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [gollama](https://github.com/sammcj/gollama)
 - [Ollama eBook Summary](https://github.com/cognitivetech/ollama-ebook-summary/)
 - [Ollama Mixture of Experts (MOE) in 50 lines of code](https://github.com/rapidarchitect/ollama_moe)
+- [vim-intelligence-bridge](https://github.com/pepo-ec/vim-intelligence-bridge) Simple interaction of "Ollama" with the Vim editor
 
 ### Apple Vision Pro
 - [Enchanted](https://github.com/AugustDev/enchanted)
Repository: vercel/next.js
Pull request: [turbopack] Move turbo-tasks-testing to dev-dependencies

This is testonly so shouldn't be built as part of our release

Changed files:
filename: crates/next-api/src/operation.rs
patch: @@ -148,7 +148,7 @@ async fn pick_endpoint(
     op: OperationVc<Entrypoints>,
     selector: EndpointSelector,
 ) -> Result<Vc<OptionEndpoint>> {
-    let endpoints = op.connect().strongly_consistent().await?;
+    let endpoints = op.read_strongly_consistent().await?;
     let endpoint = match selector {
         EndpointSelector::InstrumentationNodeJs => {
             endpoints.instrumentation.as_ref().map(|i| i.node_js)

filename: turbopack/crates/turbo-tasks-backend/Cargo.toml
patch: @@ -55,7 +55,6 @@ thread_local = { workspace = true }
 turbo-persistence = { workspace = true }
 turbo-rcstr = { workspace = true }
 turbo-tasks = { workspace = true }
-turbo-tasks-testing = { workspace = true }
 
 [dev-dependencies]
 criterion = { workspace = true, features = ["async_tokio"] }
@@ -64,6 +63,7 @@ regex = { workspace = true }
 tempfile = { workspace = true }
 turbo-tasks-malloc = { workspace = true }
 rstest = { workspace = true }
+turbo-tasks-testing = { workspace = true }
 
 
 [[bench]]
Repository: vuejs/vue
Pull request: fix prevent default unit test


Changed files:
filename: test/unit/features/directives/on.spec.js
patch: @@ -86,15 +86,14 @@ describe('Directive v-on', () => {
     vm = new Vue({
       el,
       template: `
-        <div @click="bar">
-          <div @click.stop="foo"></div>
-        </div>
+        <input type="checkbox" ref="input" @click.prevent="foo">
       `,
-      methods: { foo: spy, bar: spy2 }
+      methods: { foo: spy2 }
     })
-    triggerEvent(vm.$el.firstChild, 'click')
-    expect(spy).toHaveBeenCalled()
-    expect(spy2).not.toHaveBeenCalled()
+    vm.$refs.input.checked = false
+    triggerEvent(vm.$refs.input, 'click')
+    expect(spy2).toHaveBeenCalled()
+    expect(vm.$refs.input.checked).toBe(false)
   })
 
   it('should support capture', () => {
Repository: facebook/react
Pull request: [flags] make enableScrollEndPolyfill dynamic

Will roll this out in www

Changed files:
filename: packages/shared/forks/ReactFeatureFlags.www-dynamic.js
patch: @@ -39,6 +39,7 @@ export const enableUseEffectCRUDOverload = __VARIANT__;
 export const enableFastAddPropertiesInDiffing = __VARIANT__;
 export const enableLazyPublicInstanceInFabric = false;
 export const enableViewTransition = __VARIANT__;
+export const enableScrollEndPolyfill = __VARIANT__;
 
 // TODO: These flags are hard-coded to the default values used in open source.
 // Update the tests so that they pass in either mode, then set these

filename: packages/shared/forks/ReactFeatureFlags.www.js
patch: @@ -37,6 +37,7 @@ export const {
   transitionLaneExpirationMs,
   enableFastAddPropertiesInDiffing,
   enableViewTransition,
+  enableScrollEndPolyfill,
 } = dynamicFeatureFlags;
 
 // On WWW, __EXPERIMENTAL__ is used for a new modern build.
@@ -116,7 +117,5 @@ export const enableLazyPublicInstanceInFabric = false;
 
 export const enableSwipeTransition = false;
 
-export const enableScrollEndPolyfill = false;
-
 // Flow magic to verify the exports of this file match the original version.
 ((((null: any): ExportsType): FeatureFlagsType): ExportsType);
Repository: ollama/ollama
Pull request: readme: add Obsidian Quiz Generator plugin to community integrations

**Plugin Demo**

https://github.com/user-attachments/assets/24e57fcf-2cbf-4797-a161-4c4a05e518bf



Changed files:
filename: README.md
patch: @@ -431,6 +431,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [vnc-lm](https://github.com/jk011ru/vnc-lm) (A containerized Discord bot with support for attachments and web links)
 - [LSP-AI](https://github.com/SilasMarvin/lsp-ai) (Open-source language server for AI-powered functionality)
 - [QodeAssist](https://github.com/Palm1r/QodeAssist) (AI-powered coding assistant plugin for Qt Creator)
+- [Obsidian Quiz Generator plugin](https://github.com/ECuiDev/obsidian-quiz-generator)
 
 ### Supported backends
Repository: huggingface/transformers
Pull request: Align tie weights in Idefics

# What does this PR do?

As per the title

Changed files:
filename: src/transformers/models/idefics/modeling_idefics.py
patch: @@ -1107,31 +1107,15 @@ def __init__(self, config, vision_model=None):
             bias=False,
             partially_freeze=config.freeze_lm_head,
         )
+        if config.additional_vocab_size > 0:
+            self._tied_weights_keys = {
+                "lm_head.weight": "model.embed_tokens.weight",
+                "lm_head.additional_fc.weight": "model.embed_tokens.additional_embedding.weight",
+            }
 
         # Initialize weights and apply final processing
         self.post_init()
 
-    def tie_weights(self, **kwargs):
-        """
-        Overwrite `transformers.modeling_utils.PreTrainedModel.tie_weights` to handle the case of
-        IdeficsDecoupledLinear and IdeficsDecoupledEmbedding.
-        """
-        output_embeddings = self.get_output_embeddings()
-        input_embeddings = self.get_input_embeddings()
-
-        if getattr(self.config, "tie_word_embeddings", True):
-            output_embeddings.weight = input_embeddings.weight
-            if input_embeddings.num_additional_embeddings > 0:
-                assert output_embeddings.out_additional_features == input_embeddings.num_additional_embeddings
-                output_embeddings.additional_fc.weight = input_embeddings.additional_embedding.weight
-
-        if hasattr(output_embeddings, "out_features") and hasattr(input_embeddings, "num_embeddings"):
-            output_embeddings.out_features = input_embeddings.num_embeddings
-            if hasattr(output_embeddings, "out_additional_features") and hasattr(
-                input_embeddings, "num_additional_embeddings"
-            ):
-                output_embeddings.out_additional_features = input_embeddings.num_additional_embeddings
-
     @can_return_tuple
     @auto_docstring
     def forward(
Repository: ollama/ollama
Pull request: Fix incremental builds on linux

Building in containers worked fine.  Building iteratively on a persistent filesystem doesn't. Running the install function twice on a second generate caused an error cp: cannot stat '../build/linux/amd64/cpu/bin/libllama.so': No such file or directory

Changed files:
filename: llm/generate/gen_common.sh
patch: @@ -137,7 +137,7 @@ wait_for_compress() {
 
 install() {
     echo "Installing libraries to bin dir ${BUILD_DIR}/bin/"
-    for lib in $(find ${BUILD_DIR} -name \*.${LIB_EXT}); do
+    for lib in $(find ${BUILD_DIR} -name \*.${LIB_EXT} | grep -v "${BUILD_DIR}/bin/" ); do
         rm -f "${BUILD_DIR}/bin/$(basename ${lib})"
         cp -af "${lib}" "${BUILD_DIR}/bin/"
     done
Repository: electron/electron
Pull request: fix: release mouse buttons on focus loss on Wayland

Backport of #48752

See that PR for details.

Notes: Fixed an issue on Wayland (Linux) where right-clicking in the titlebar could  break mouse interactions.

Changed files:
filename: patches/chromium/.patches
patch: @@ -142,3 +142,4 @@ revert_partial_remove_unused_prehandlemouseevent.patch
 allow_electron_to_depend_on_components_os_crypt_sync.patch
 expose_referrerscriptinfo_hostdefinedoptionsindex.patch
 chore_disable_protocol_handler_dcheck.patch
+fix_release_mouse_buttons_on_focus_loss_on_wayland.patch

filename: patches/chromium/fix_release_mouse_buttons_on_focus_loss_on_wayland.patch
patch: @@ -0,0 +1,34 @@
+From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
+From: Mitchell COhen <mitch.cohen@me.com>
+Date: Sun, 2 Nov 2025 15:30:56 -0500
+Subject: fix: release mouse buttons on focus loss on Wayland
+
+Fixes an issue where the mouse flags would get stuck if you right-click
+the CSD titlebar in Wayland.
+
+Bug: 455147429
+Change-Id: I9f5a9f395b3c1d85094a40a92d40691a897dbd05
+Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7091872
+Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
+Reviewed-by: Kramer Ge <fangzhoug@chromium.org>
+Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
+Cr-Commit-Position: refs/heads/main@{#1538048}
+
+diff --git a/ui/ozone/platform/wayland/host/wayland_event_source.cc b/ui/ozone/platform/wayland/host/wayland_event_source.cc
+index 4cc15e842b633e93f1d6654225765769eb75fffd..4e421ccbd36d4efebd43c9def5b575b7d8d5e336 100644
+--- a/ui/ozone/platform/wayland/host/wayland_event_source.cc
++++ b/ui/ozone/platform/wayland/host/wayland_event_source.cc
+@@ -336,6 +336,13 @@ void WaylandEventSource::OnPointerFocusChanged(
+     // Save new pointer location.
+     pointer_location_ = location;
+     window_manager_->SetPointerFocusedWindow(window);
++  } else {
++    // The compositor may swallow the release event for any buttons that are
++    // pressed when the window loses focus, e.g. when right-clicking the
++    // titlebar to open the system menu on GNOME.
++    if (!connection_->IsDragInProgress()) {
++      ReleasePressedPointerButtons(window, ui::EventTimeForNow());
++    }
+   }
+ 
+   auto closure = focused ? base::NullCallback()
Repository: vuejs/vue
Pull request: cache vnodes length


Changed files:
filename: src/core/vdom/vnode.js
patch: @@ -89,8 +89,9 @@ export function cloneVNode (vnode: VNode): VNode {
 }
 
 export function cloneVNodes (vnodes: Array<VNode>): Array<VNode> {
-  const res = new Array(vnodes.length)
-  for (let i = 0; i < vnodes.length; i++) {
+  const len = vnodes.length
+  const res = new Array(len)
+  for (let i = 0; i < len; i++) {
     res[i] = cloneVNode(vnodes[i])
   }
   return res
Repository: nodejs/node
Pull request: doc: add info about renamed flag in `cli.md`

<!--
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: doc/api/cli.md
patch: @@ -1958,7 +1958,8 @@ added: v22.6.0
 changes:
   - version: v25.2.0
     pr-url: https://github.com/nodejs/node/pull/60600
-    description: Type stripping is now stable.
+    description: Type stripping is now stable, the flag was renamed from
+                 `--no-experimental-strip-types` to `--no-strip-types`.
   - version:
       - v23.6.0
       - v22.18.0
Repository: ggml-org/llama.cpp
Pull request: ggml-cpu: arm64: Q4_K repack (i8mm) scale unroll and vectorization

While working on https://github.com/ggml-org/llama.cpp/pull/18860 I found out a small perf optimization when loading the subblock scales.
Behavior unchanged, it's a manual unroll + vectorization.

Llama-bench:

| model          | test  | old t/s | new t/s | speedup |
| -------------- | ----- | ------: | ------: | ------- |
| lfm2 1.2B Q4_K | pp512 |  658.53 |  682.69 | 1.04   |
| lfm2 350M Q4_K | pp512 | 2052.76 | 2159.47 | 1.05   |
| Qwen 8B Q4_K - Medium | pp512 | 94.21 | 99.51 | 1.06  |


No changes observed in the perplexities for Qwen3 8B 128K Q4_K_M and lfm2 1.2B Q4_K_M


cc: @tdakhran 


Changed files:
filename: ggml/src/ggml-cpu/arch/arm/repack.cpp
patch: @@ -3148,16 +3148,17 @@ void ggml_gemm_q4_K_8x8_q8_K(int                        n,
 
                         // Scales[i] corresponds to column i
                         const int scale_offset = cp * 2;
-                        for (int blk = 0; blk < 2; blk++) {
-                            const int32x4_t block_scale = {
-                                (int32_t) q4sb_scales[blk][scale_offset],
-                                (int32_t) q4sb_scales[blk][scale_offset],
-                                (int32_t) q4sb_scales[blk][scale_offset + 1],
-                                (int32_t) q4sb_scales[blk][scale_offset + 1],
-                            };
-                            acc[cp]     = vmlaq_s32(acc[cp], sb_acc[blk], block_scale);
-                            acc[cp + 4] = vmlaq_s32(acc[cp + 4], sb_acc[blk + 2], block_scale);
-                        }
+                        const int32_t scale_00 = q4sb_scales[0][scale_offset];
+                        const int32_t scale_01 = q4sb_scales[0][scale_offset + 1];
+                        const int32_t scale_10 = q4sb_scales[1][scale_offset];
+                        const int32_t scale_11 = q4sb_scales[1][scale_offset + 1];
+                        const int32x4_t block_scale_0 = vcombine_s32(vdup_n_s32(scale_00), vdup_n_s32(scale_01));
+                        const int32x4_t block_scale_1 = vcombine_s32(vdup_n_s32(scale_10), vdup_n_s32(scale_11));
+
+                        acc[cp]     = vmlaq_s32(acc[cp], sb_acc[0], block_scale_0);
+                        acc[cp + 4] = vmlaq_s32(acc[cp + 4], sb_acc[2], block_scale_0);
+                        acc[cp]     = vmlaq_s32(acc[cp], sb_acc[1], block_scale_1);
+                        acc[cp + 4] = vmlaq_s32(acc[cp + 4], sb_acc[3], block_scale_1);
                     }
 
                     // Multiply Acc bsum + mins
Repository: ollama/ollama
Pull request: Update requirements.txt

With chromadb==0.4.7, ingest.py still fails with 
`Cannot submit more than 5,461 embeddings at once. Please submit your embeddings in batches of size 5,461 or less.`

See 
- https://github.com/ollama/ollama/issues/4476
- https://github.com/ollama/ollama/issues/2572
- https://github.com/ollama/ollama/issues/533

Changed files:
filename: examples/langchain-python-rag-privategpt/requirements.txt
patch: @@ -1,6 +1,6 @@
 langchain==0.0.274
 gpt4all==1.0.8
-chromadb==0.4.7
+chromadb==0.5.0
 llama-cpp-python==0.1.81
 urllib3==2.0.4
 PyMuPDF==1.23.5
@@ -12,4 +12,4 @@ pandoc==2.3
 pypandoc==1.11
 tqdm==4.66.1
 sentence_transformers==2.2.2
-numpy>=1.22.2 # not directly required, pinned by Snyk to avoid a vulnerability
\ No newline at end of file
+numpy>=1.22.2 # not directly required, pinned by Snyk to avoid a vulnerability
Repository: huggingface/transformers
Pull request: Allow `validation_fn` to be `None` in `validate_rope`

Custom models which specify `mrope` as their `rope_type` were failing to initialise because of an attribute error when attempting to get `_validate_mrope_rope_parameters`, which doesn't exist.

The lines following this `getattr` indicate that this is suppose to trigger a warning, not an error.

This PR fixes that.

Changed files:
filename: src/transformers/modeling_rope_utils.py
patch: @@ -692,14 +692,14 @@ def validate_rope(self: "PreTrainedConfig", ignore_keys: Optional[set] = None):
 
         for rope_parameters in rope_parameters_dict.values():
             rope_type = rope_parameters.get("rope_type", rope_parameters.get("type", "default"))
-            validation_fn = getattr(self, f"_validate_{rope_type}_rope_parameters")
+            validation_fn = getattr(self, f"_validate_{rope_type}_rope_parameters", None)
             rope_parameters["rope_type"] = rope_type
 
             if validation_fn is not None:
                 validation_fn(rope_parameters, ignore_keys=ignore_keys)
             else:
                 logger.warning(
-                    f"Missing validation function mapping in `ROPE_VALIDATION_FUNCTIONS` for 'rope_type'='{rope_type}'"
+                    f"Missing validation function in 'RotaryEmbeddingConfigMixin' for 'rope_type'='{rope_type}'"
                 )
 
     def _validate_default_rope_parameters(self, rope_parameters: dict, ignore_keys: Optional[set] = None):
Repository: electron/electron
Pull request: fix: release mouse buttons on focus loss on Wayland

Backport of #48752

See that PR for details.


Notes: Fixed an issue on Wayland (Linux) where right-clicking in the titlebar could  break mouse interactions.

Changed files:
filename: patches/chromium/.patches
patch: @@ -143,3 +143,4 @@ expose_referrerscriptinfo_hostdefinedoptionsindex.patch
 chore_disable_protocol_handler_dcheck.patch
 fix_check_for_file_existence_before_setting_mtime.patch
 revert_cleanup_remove_feature_windelayspellcheckserviceinit.patch
+fix_release_mouse_buttons_on_focus_loss_on_wayland.patch

filename: patches/chromium/fix_release_mouse_buttons_on_focus_loss_on_wayland.patch
patch: @@ -0,0 +1,34 @@
+From 0000000000000000000000000000000000000000 Mon Sep 17 00:00:00 2001
+From: Mitchell COhen <mitch.cohen@me.com>
+Date: Sun, 2 Nov 2025 15:30:56 -0500
+Subject: fix: release mouse buttons on focus loss on Wayland
+
+Fixes an issue where the mouse flags would get stuck if you right-click
+the CSD titlebar in Wayland.
+
+Bug: 455147429
+Change-Id: I9f5a9f395b3c1d85094a40a92d40691a897dbd05
+Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/7091872
+Reviewed-by: Thomas Anderson <thomasanderson@chromium.org>
+Reviewed-by: Kramer Ge <fangzhoug@chromium.org>
+Commit-Queue: Thomas Anderson <thomasanderson@chromium.org>
+Cr-Commit-Position: refs/heads/main@{#1538048}
+
+diff --git a/ui/ozone/platform/wayland/host/wayland_event_source.cc b/ui/ozone/platform/wayland/host/wayland_event_source.cc
+index 4cc15e842b633e93f1d6654225765769eb75fffd..4e421ccbd36d4efebd43c9def5b575b7d8d5e336 100644
+--- a/ui/ozone/platform/wayland/host/wayland_event_source.cc
++++ b/ui/ozone/platform/wayland/host/wayland_event_source.cc
+@@ -336,6 +336,13 @@ void WaylandEventSource::OnPointerFocusChanged(
+     // Save new pointer location.
+     pointer_location_ = location;
+     window_manager_->SetPointerFocusedWindow(window);
++  } else {
++    // The compositor may swallow the release event for any buttons that are
++    // pressed when the window loses focus, e.g. when right-clicking the
++    // titlebar to open the system menu on GNOME.
++    if (!connection_->IsDragInProgress()) {
++      ReleasePressedPointerButtons(window, ui::EventTimeForNow());
++    }
+   }
+ 
+   auto closure = focused ? base::NullCallback()
Repository: facebook/react
Pull request: [compiler][ez] Add validation for auto-deps config


numRequiredArgs has to be more than 0 and the pass depends on that

--


Changed files:
filename: compiler/packages/babel-plugin-react-compiler/src/HIR/Environment.ts
patch: @@ -285,7 +285,7 @@ const EnvironmentConfigSchema = z.object({
       z.array(
         z.object({
           function: ExternalFunctionSchema,
-          numRequiredArgs: z.number(),
+          numRequiredArgs: z.number().min(1, 'numRequiredArgs must be > 0'),
         }),
       ),
     )

filename: compiler/packages/babel-plugin-react-compiler/src/__tests__/envConfig-test.ts
patch: @@ -24,6 +24,24 @@ describe('parseConfigPragma()', () => {
     );
   });
 
+  it('effect autodeps config must have at least 1 required argument', () => {
+    expect(() => {
+      validateEnvironmentConfig({
+        inferEffectDependencies: [
+          {
+            function: {
+              source: 'react',
+              importSpecifierName: 'useEffect',
+            },
+            numRequiredArgs: 0,
+          },
+        ],
+      } as any);
+    }).toThrowErrorMatchingInlineSnapshot(
+      `"InvalidConfig: Could not validate environment config. Update React Compiler config to fix the error. Validation error: numRequiredArgs must be > 0 at "inferEffectDependencies[0].numRequiredArgs""`,
+    );
+  });
+
   it('can parse stringy enums', () => {
     const stringyHook = {
       effectKind: 'freeze',