helloadhavan/github_issues huggingface dataset:
Repository: ggml-org/llama.cpp
Pull request: tests : add non-cont, inplace rope tests

ref https://github.com/ggml-org/llama.cpp/pull/18986#issuecomment-3841942982
ref https://github.com/ggml-org/llama.cpp/issues/19128#issuecomment-3807441909
ref https://github.com/ggml-org/llama.cpp/issues/19292

This type of rope is needed during rope shift:

https://github.com/ggml-org/llama.cpp/blob/cf36c21b221aac7c7ce6dca9def898311415e56b/src/llama-kv-cache.cpp#L1626-L1635

We are updating the KV cache data, so the op is inplace. Since the changes in #18986 the tensor is now also non-contiguous.

Based on the discussion in https://github.com/ggml-org/llama.cpp/pull/18986#issuecomment-3841942982, it appears that the Vulkan backend currently does not support this case. cc @jeffbolznv @0cc4m 

Changed files:
filename: tests/test-backend-ops.cpp
patch: @@ -8032,6 +8032,8 @@ static std::vector<std::unique_ptr<test_case>> make_test_cases_eval() {
         for (int mode : {GGML_ROPE_TYPE_NORMAL, GGML_ROPE_TYPE_NEOX, GGML_ROPE_TYPE_MROPE, GGML_ROPE_TYPE_IMROPE, GGML_ROPE_TYPE_VISION}) {
             for (bool ff : {false, true}) {
                 test_cases.emplace_back(new test_rope(type, {128,  32, 2, 1}, 128, mode, 512, 1.4245f, 0.7465f, 1.4245f, ff, 0, true, true));
+                test_cases.emplace_back(new test_rope(type, {128,  32, 2, 1}, 128, mode, 512, 1.4245f, 0.7465f, 1.4245f, ff, 1, true, true));
+                test_cases.emplace_back(new test_rope(type, {128,  32, 2, 3}, 128, mode, 512, 1.4245f, 0.7465f, 1.4245f, ff, 1, true, true));
             }
         }
     }
Repository: vuejs/vue
Pull request: typo fix

### typo fix
-  nomralization / normalzation → normalization


Changed files:
filename: src/compiler/codegen/index.js
patch: @@ -302,10 +302,10 @@ function genChildren (el: ASTElement, checkSkip?: boolean): string | void {
   }
 }
 
-// determine the normalzation needed for the children array.
+// determine the normalization needed for the children array.
 // 0: no normalization needed
 // 1: simple normalization needed (possible 1-level deep nested array)
-// 2: full nomralization needed
+// 2: full normalization needed
 function getNormalizationType (children): number {
   let res = 0
   for (let i = 0; i < children.length; i++) {
Repository: facebook/react
Pull request: fix[react-devtools-fusebox]: add extension globals to build

We started using these globals in `react-devtools-shared/src/frontend` code, forward-fixing https://github.com/facebook/react/pull/32262.

Changed files:
filename: packages/react-devtools-fusebox/webpack.config.frontend.js
patch: @@ -83,6 +83,9 @@ module.exports = {
       __PROFILE__: false,
       __TEST__: NODE_ENV === 'test',
       __IS_NATIVE__: true,
+      __IS_CHROME__: false,
+      __IS_FIREFOX__: false,
+      __IS_EDGE__: false,
       'process.env.DEVTOOLS_PACKAGE': `"react-devtools-fusebox"`,
       'process.env.DEVTOOLS_VERSION': `"${DEVTOOLS_VERSION}"`,
       'process.env.EDITOR_URL': EDITOR_URL != null ? `"${EDITOR_URL}"` : null,
Repository: nodejs/node
Pull request: test: add more logs to test-esm-loader-hooks-inspect-wait

This provides a bit more information about where & when the child processes crashes when it crashes / flakes in the CI.

Refs: https://github.com/nodejs/node/issues/54346

<!--
Before submitting a pull request, please read:

- the CONTRIBUTING guide at https://github.com/nodejs/node/blob/HEAD/CONTRIBUTING.md
- the commit message formatting guidelines at
  https://github.com/nodejs/node/blob/HEAD/doc/contributing/pull-requests.md#commit-message-guidelines

For code changes:
1. Include tests for any bug fixes or new features.
2. Update documentation if relevant.
3. Ensure that `make -j4 test` (UNIX), or `vcbuild test` (Windows) passes.

If you believe this PR should be highlighted in the Node.js CHANGELOG
please add the `notable-change` label.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.
-->


Changed files:
filename: test/parallel/test-esm-loader-hooks-inspect-wait.js
patch: @@ -12,6 +12,7 @@ const { NodeInstance } = require('../common/inspector-helper.js');
 
 async function runTest() {
   const main = fixtures.path('es-module-loaders', 'register-loader.mjs');
+  process.env.NODE_DEBUG = 'esm,async_loader_worker';
   const child = new NodeInstance(['--inspect-wait=0'], '', main);
 
   const session = await child.connectInspectorSession();
@@ -24,7 +25,11 @@ async function runTest() {
   ]);
   await session.send({ method: 'NodeRuntime.disable' });
   await session.waitForDisconnect();
-  assert.strictEqual((await child.expectShutdown()).exitCode, 0);
+  const result = await child.expectShutdown();
+  assert.deepStrictEqual(result, {
+    exitCode: 0,
+    signal: null,
+  });
 }
 
 runTest();
Repository: huggingface/transformers
Pull request: Skip failing irrelevant test for ColQwen2

ColQwen2 doesn't do weight tying in the normal way, so this test fails and isn't too relevant anyway.

Changed files:
filename: tests/models/colqwen2/test_modeling_colqwen2.py
patch: @@ -279,6 +279,10 @@ def test_sdpa_can_dispatch_on_flash(self):
     def test_sdpa_can_compile_dynamic(self):
         pass
 
+    @unittest.skip(reason="This architecture doesn't support weight tying/untying.")
+    def test_load_save_without_tied_weights(self):
+        pass
+
 
 @require_torch
 class ColQwen2ModelIntegrationTest(unittest.TestCase):
Repository: vuejs/vue
Pull request: Recommend user to provide reproduction repository for ssr issue

For SSR issue, it's better to recommend the user to privide reproduction repository.

Changed files:
filename: .github/CONTRIBUTING.md
patch: @@ -28,7 +28,7 @@ Hi! I’m really excited that you are interested in contributing to Vue.js. Befo
 
 - It is recommended that you make a JSFiddle/JSBin/Codepen to demonstrate your issue. You could start with [this template](http://jsfiddle.net/df4Lnuw6/) that already includes the latest version of Vue.
 
-- For bugs that involves build setups, you can create a reproduction repository with steps in the README.
+- For potential SSR (Server Side Rendering) issue or bugs that involves build setups, you can create a reproduction repository with steps in the README.
 
 - If your issue is resolved but still open, don’t hesitate to close it. In case you found a solution by yourself, it could be helpful to explain how you fixed it.
 

filename: .github/ISSUE_TEMPLATE.md
patch: @@ -24,7 +24,7 @@ Reporting a bug?
 
 - It is recommended that you make a JSFiddle/JSBin/Codepen to demonstrate your issue. You could start with [this template](http://jsfiddle.net/5sH6A/) that already includes the latest version of Vue.
 
-- For bugs that involves build setups, you can create a reproduction repository with steps in the README.
+- For potential SSR (Server Side Rendering) issue or bugs that involves build setups, you can create a reproduction repository with steps in the README.
 
 - If your issue is resolved but still open, don’t hesitate to close it. In case you found a solution by yourself, it could be helpful to explain how you fixed it.
Repository: facebook/react
Pull request: DevTools: fix host component filter option title

Overlook that in https://github.com/facebook/react/pull/32086, because of ternany, it is already string literals, so html entities names no longer needed.

Changed files:
filename: packages/react-devtools-shared/src/devtools/views/Settings/ComponentsSettings.js
patch: @@ -478,8 +478,8 @@ export default function ComponentsSettings({
                     <option value={ElementTypeForwardRef}>forward ref</option>
                     <option value={ElementTypeHostComponent}>
                       {__IS_NATIVE__
-                        ? 'host components (e.g. &lt;RCTText&gt;)'
-                        : 'dom nodes (e.g. &lt;div&gt;)'}
+                        ? 'host components (e.g. <RCTText>)'
+                        : 'dom nodes (e.g. <div>)'}
                     </option>
                     <option value={ElementTypeMemo}>memo</option>
                     <option value={ElementTypeOtherOrUnknown}>other</option>
Repository: vercel/next.js
Pull request: Turbopack: bail instead of panic

Eventual consistency strikes again

We already had the infrastructure here to store a result in the swc visitor.

Changed files:
filename: turbopack/crates/turbopack-ecmascript/src/lib.rs
patch: @@ -1316,7 +1316,8 @@ async fn merge_modules(
             // corresponding export in the module that exports it.
             if let Some(&module) = self.reverse_module_contexts.get(ctxt) {
                 let eval_context_exports = self.export_contexts.get(&module).unwrap();
-                // TODO looking up an Atom in a Map<RcStr, _>
+                // TODO looking up an Atom in a Map<RcStr, _>, would ideally work without creating a
+                // RcStr every time.
                 let sym_rc_str: RcStr = sym.as_str().into();
                 let (local, local_ctxt) = if let Some((local, local_ctxt)) =
                     eval_context_exports.get(&sym_rc_str)
@@ -1329,10 +1330,11 @@ async fn merge_modules(
                     // generating this variable.
                     (None, SyntaxContext::empty())
                 } else {
-                    panic!(
+                    self.error = Err(anyhow::anyhow!(
                         "Expected to find a local export for {sym} with ctxt {ctxt:#?} in \
                          {eval_context_exports:?}",
-                    );
+                    ));
+                    return;
                 };
 
                 let global_ctxt = self.get_context_for(module, local_ctxt);
Repository: huggingface/transformers
Pull request: add require_deterministic_for_xpu to make the case pass in xpu

make xpu pass in  pytest -rA tests/models/dac/test_modeling_dac.py::DacIntegrationTest::test_integration_0_dac_16khz and pytest tests/models/xcodec/test_modeling_xcodec.py::XcodecIntegrationTest

Changed files:
filename: tests/models/dac/test_modeling_dac.py
patch: @@ -21,7 +21,13 @@
 from parameterized import parameterized
 
 from transformers import AutoProcessor, DacConfig, DacModel
-from transformers.testing_utils import is_torch_available, require_torch, slow, torch_device
+from transformers.testing_utils import (
+    is_torch_available,
+    require_deterministic_for_xpu,
+    require_torch,
+    slow,
+    torch_device,
+)
 
 from ...test_configuration_common import ConfigTester
 from ...test_modeling_common import ModelTesterMixin, floats_tensor
@@ -658,6 +664,7 @@ def compute_rmse(arr1, arr2):
 @require_torch
 class DacIntegrationTest(unittest.TestCase):
     @parameterized.expand([(model_name,) for model_name in EXPECTED_PREPROC_SHAPE.keys()])
+    @require_deterministic_for_xpu
     def test_integration(self, model_name):
         # load model and processor
         model_id = f"descript/{model_name}"

filename: tests/models/xcodec/test_modeling_xcodec.py
patch: @@ -28,6 +28,7 @@
 from transformers import AutoFeatureExtractor, XcodecConfig
 from transformers.testing_utils import (
     is_torch_available,
+    require_deterministic_for_xpu,
     require_torch,
     slow,
     torch_device,
@@ -303,6 +304,7 @@ def compute_rmse(arr1, arr2):
 @require_torch
 class XcodecIntegrationTest(unittest.TestCase):
     @parameterized.expand(EXPECTED_OUTPUTS_JSON)
+    @require_deterministic_for_xpu
     def test_integration(
         self, test_name, repo_id, bandwidth, exp_codes, exp_decoded, exp_codec_err, codec_tol, dec_tol
     ):
Repository: ollama/ollama
Pull request: fix: comment typo


Changed files:
filename: llm/server.go
patch: @@ -409,7 +409,7 @@ func NewLlamaServer(gpus gpu.GpuInfoList, model string, ggml *GGML, adapters, pr
 		}
 
 		if err = s.cmd.Start(); err != nil {
-			// Detect permission denied and augment them essage about noexec
+			// Detect permission denied and augment the message about noexec
 			if errors.Is(err, os.ErrPermission) {
 				finalErr = fmt.Errorf("unable to start server %w.  %s may have noexec set.  Set OLLAMA_TMPDIR for server to a writable executable directory", err, dir)
 				continue
Repository: facebook/react
Pull request: Reconciler: Combine identical cases in findParent

## Summary

When lookup `Parent`, `HostRoot` and `HostPortal` should be merged, because when creating a `Portal`, it will also include `containerInfo`(So we can directly use this `containerInfo` to delete the real DOM nodes.), so there is no need to handle them separately.

## How did you test this change?

No behavior changes, all existing tests pass.

Changed files:
filename: packages/react-reconciler/src/ReactFiberCommitWork.js
patch: @@ -2007,11 +2007,7 @@ function commitDeletionEffects(
           hostParentIsContainer = false;
           break findParent;
         }
-        case HostRoot: {
-          hostParent = parent.stateNode.containerInfo;
-          hostParentIsContainer = true;
-          break findParent;
-        }
+        case HostRoot:
         case HostPortal: {
           hostParent = parent.stateNode.containerInfo;
           hostParentIsContainer = true;
Repository: ollama/ollama
Pull request: Fix import image width

This gives more reasonable output for the images:

<img width="1183" alt="Screenshot 2024-08-27 at 14 10 33" src="https://github.com/user-attachments/assets/428cee86-ba62-4270-b308-2bacc07a1460">


Changed files:
filename: docs/import.md
patch: @@ -5,7 +5,7 @@
   * [Importing a Safetensors adapter](#Importing-a-fine-tuned-adapter-from-Safetensors-weights)
   * [Importing a Safetensors model](#Importing-a-model-from-Safetensors-weights)
   * [Importing a GGUF file](#Importing-a-GGUF-based-model-or-adapter)
-  * [Sharing models on ollama.com](#Sharing-your-model-on-ollama.com)
+  * [Sharing models on ollama.com](#Sharing-your-model-on-ollamacom)
 
 ## Importing a fine tuned adapter from Safetensors weights
 
@@ -158,15 +158,15 @@ You can share any model you have created by pushing it to [ollama.com](https://o
 
 First, use your browser to go to the [Ollama Sign-Up](https://ollama.com/signup) page. If you already have an account, you can skip this step.
 
-<img src="images/signup.png" alt="Sign-Up" width="756" height="1192">
+<img src="images/signup.png" alt="Sign-Up" width="40%">
 
 The `Username` field will be used as part of your model's name (e.g. `jmorganca/mymodel`), so make sure you are comfortable with the username that you have selected.
 
 Now that you have created an account and are signed-in, go to the [Ollama Keys Settings](https://ollama.com/settings/keys) page.
 
 Follow the directions on the page to determine where your Ollama Public Key is located.
 
-<img src="images/ollama-keys.png" alt="Ollama Keys" width="1524" height="1134">
+<img src="images/ollama-keys.png" alt="Ollama Keys" width="80%">
 
 Click on the `Add Ollama Public Key` button, and copy and paste the contents of your Ollama Public Key into the text field.
Repository: ggml-org/llama.cpp
Pull request: ci : fix sanitize workflow to enable ggml sanitizers too

fix https://github.com/ggml-org/llama.cpp/pull/19291#issuecomment-3843594581

We need to sanitize also the ggml when sanitizing the llama.

Success: https://github.com/ggerganov/tmp2/actions/runs/21667569266/job/62466865225

Changed files:
filename: .github/workflows/build.yml
patch: @@ -293,6 +293,7 @@ jobs:
           cmake -B build \
             -DLLAMA_FATAL_WARNINGS=ON \
             -DLLAMA_SANITIZE_${{ matrix.sanitizer }}=ON \
+            -DGGML_SANITIZE_${{ matrix.sanitizer }}=ON \
             -DCMAKE_BUILD_TYPE=${{ matrix.build_type }}
           cmake --build build --config ${{ matrix.build_type }} -j $(nproc)
 
@@ -303,6 +304,7 @@ jobs:
           cmake -B build \
             -DLLAMA_FATAL_WARNINGS=ON \
             -DLLAMA_SANITIZE_${{ matrix.sanitizer }}=ON \
+            -DGGML_SANITIZE_${{ matrix.sanitizer }}=ON \
             -DCMAKE_BUILD_TYPE=${{ matrix.build_type }} \
             -DGGML_OPENMP=OFF
           cmake --build build --config ${{ matrix.build_type }} -j $(nproc)
Repository: vuejs/vue
Pull request: add unit test for dynamic component with props

add unit test for dynamic component with props



Changed files:
filename: test/unit/features/component/component.spec.js
patch: @@ -87,23 +87,52 @@ describe('Component', () => {
       },
       components: {
         'view-a': {
-          template: '<div>foo</div>',
+          template: '<div>foo {{view}}</div>',
           data () {
             return { view: 'a' }
           }
         },
         'view-b': {
-          template: '<div>bar</div>',
+          template: '<div>bar {{view}}</div>',
           data () {
             return { view: 'b' }
           }
         }
       }
     }).$mount()
-    expect(vm.$el.outerHTML).toBe('<div view="view-a">foo</div>')
+    expect(vm.$el.outerHTML).toBe('<div view="view-a">foo a</div>')
     vm.view = 'view-b'
     waitForUpdate(() => {
-      expect(vm.$el.outerHTML).toBe('<div view="view-b">bar</div>')
+      expect(vm.$el.outerHTML).toBe('<div view="view-b">bar b</div>')
+      vm.view = ''
+    })
+    .then(() => {
+      expect(vm.$el.nodeType).toBe(8)
+      expect(vm.$el.data).toBe('')
+    }).then(done)
+  })
+
+  it('dynamic with props', done => {
+    const vm = new Vue({
+      template: '<component :is="view" :view="view"></component>',
+      data: {
+        view: 'view-a'
+      },
+      components: {
+        'view-a': {
+          template: '<div>foo {{view}}</div>',
+          props: ['view']
+        },
+        'view-b': {
+          template: '<div>bar {{view}}</div>',
+          props: ['view']
+        }
+      }
+    }).$mount()
+    expect(vm.$el.outerHTML).toBe('<div>foo view-a</div>')
+    vm.view = 'view-b'
+    waitForUpdate(() => {
+      expect(vm.$el.outerHTML).toBe('<div>bar view-b</div>')
       vm.view = ''
     })
     .then(() => {
Repository: vuejs/vue
Pull request: Enforce to loop through children to get the correct normalize type (fix #4564)

fix #4564 

Changed files:
filename: src/compiler/codegen/index.js
patch: @@ -307,18 +307,20 @@ function genChildren (el: ASTElement, checkSkip?: boolean): string | void {
 // 1: simple normalization needed (possible 1-level deep nested array)
 // 2: full nomralization needed
 function getNormalizationType (children): number {
+  let res = 0
   for (let i = 0; i < children.length; i++) {
     const el: any = children[i]
     if (needsNormalization(el) ||
         (el.if && el.ifConditions.some(c => needsNormalization(c.block)))) {
-      return 2
+      res = 2
+      break
     }
     if (maybeComponent(el) ||
         (el.if && el.ifConditions.some(c => maybeComponent(c.block)))) {
-      return 1
+      res = 1
     }
   }
-  return 0
+  return res
 }
 
 function needsNormalization (el: ASTElement) {

filename: test/unit/modules/compiler/codegen.spec.js
patch: @@ -434,6 +434,14 @@ describe('codegen', () => {
     )
   })
 
+  it('generate component with v-for', () => {
+    // normalize type: 2
+    assertCodegen(
+      '<div><child></child><template v-for="item in list">{{ item }}</template></div>',
+      `with(this){return _c('div',[_c('child'),_l((list),function(item){return [_v(_s(item))]})],2)}`
+    )
+  })
+
   it('not specified ast type', () => {
     const res = generate(null, baseOptions)
     expect(res.render).toBe(`with(this){return _c("div")}`)
Repository: nodejs/node
Pull request: test: mark stringbytes-external-exceed-max tests as flaky on AIX

I doesn't look like anyone is going to fix them any time soon. Mark them as flaky as they've been flaking the CI pretty frequently (11+9+8+.... out of last 100 CI runs):

Refs: https://github.com/nodejs/node/issues/60494
Refs: https://github.com/nodejs/reliability/blob/main/reports/2025-11-03.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: test/addons/addons.status
patch: @@ -20,3 +20,13 @@ openssl-providers/test-no-legacy-provider-option: SKIP
 zlib-binding/test: SKIP
 # https://github.com/nodejs/node/issues/34410
 register-signal-handler/test: PASS,FLAKY
+
+[$system==aix]
+# https://github.com/nodejs/node/issues/60494
+stringbytes-external-exceed-max/test-stringbytes-external-exceed-max: PASS,FLAKY
+stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-hex: PASS,FLAKY
+stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-utf8: PASS,FLAKY
+stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-base64: PASS,FLAKY
+stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-2: PASS,FLAKY
+stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-ascii: PASS,FLAKY
+stringbytes-external-exceed-max/test-stringbytes-external-exceed-max-by-1-binary: PASS,FLAKY
Repository: ollama/ollama
Pull request: Update manual instructions with discrete ROCm bundle


Changed files:
filename: docs/linux.md
patch: @@ -28,6 +28,11 @@ Download and extract the Linux package:
 curl -fsSL https://ollama.com/download/ollama-linux-amd64.tgz | sudo tar zx -C /usr
 ```
 
+If you have an AMD GPU, also download and extract the ROCm package into the same location
+```bash
+curl -fsSL https://ollama.com/download/ollama-linux-amd64-rocm.tgz | sudo tar zx -C /usr
+```
+
 ### Adding Ollama as a startup service (recommended)
 
 Create a user for Ollama: