helloadhavan/github_issues huggingface dataset:
Repository: nodejs/node
Pull request: doc: correct concurrency wording in test() documentation

This PR updates the test runner documentation for the `concurrency` option.

- Replaces “application thread” with “test process”
- Clarifies that concurrency is achieved using child processes, not threads
- Changes “parallel” to “concurrent” for accuracy

As discussed in #60721.

Requesting reviews from @Ethan-Arrowood and @cjihrig.

Changed files:
filename: doc/api/test.md
patch: @@ -1619,7 +1619,7 @@ changes:
 * `options` {Object} Configuration options for the test. The following
   properties are supported:
   * `concurrency` {number|boolean} If a number is provided,
-    then that many tests would run in parallel within the application thread.
+    then that many tests would run asynchronously (they are still managed by the single-threaded event loop).
     If `true`, all scheduled asynchronous tests run concurrently within the
     thread. If `false`, only one test runs at a time.
     If unspecified, subtests inherit this value from their parent.
@@ -3882,7 +3882,7 @@ changes:
 * `options` {Object} Configuration options for the subtest. The following
   properties are supported:
   * `concurrency` {number|boolean|null} If a number is provided,
-    then that many tests would run in parallel within the application thread.
+    then that many tests would run asynchronously (they are still managed by the single-threaded event loop).
     If `true`, it would run all subtests in parallel.
     If `false`, it would only run one test at a time.
     If unspecified, subtests inherit this value from their parent.
Repository: huggingface/transformers
Pull request: [kernels] Fix kernel CI

# What does this PR do?

Fix the kernel CI by simply changing the import path of `lazy_import_flash_attention`

Changed files:
filename: tests/kernels/test_kernels.py
patch: @@ -321,7 +321,7 @@ def test_load_and_register_flash_attn_like_kernel(self):
 
         with (
             patch("transformers.integrations.hub_kernels.get_kernel", return_value=kernel_obj),
-            patch("transformers.integrations.hub_kernels.lazy_import_flash_attention", return_value=None),
+            patch("transformers.modeling_flash_attention_utils.lazy_import_flash_attention", return_value=None),
         ):
             attn_impl = "org/model"
             load_and_register_attn_kernel(attn_impl)
Repository: vercel/next.js
Pull request: Update self-hosting.mdx

small typo fix

Changed files:
filename: docs/01-app/02-guides/self-hosting.mdx
patch: @@ -218,7 +218,7 @@ module.exports = {
 
 ## Usage with CDNs
 
-When using a CDN in front on your Next.js application, the page will include `Cache-Control: private` response header when dynamic APIs are accessed. This ensures that the resulting HTML page is marked as non-cacheable. If the page is fully prerendered to static, it will include `Cache-Control: public` to allow the page to be cached on the CDN.
+When using a CDN in front of your Next.js application, the page will include `Cache-Control: private` response header when dynamic APIs are accessed. This ensures that the resulting HTML page is marked as non-cacheable. If the page is fully prerendered to static, it will include `Cache-Control: public` to allow the page to be cached on the CDN.
 
 If you don't need a mix of both static and dynamic components, you can make your entire route static and cache the output HTML on a CDN. This Automatic Static Optimization is the default behavior when running `next build` if dynamic APIs are not used.
Repository: ggml-org/llama.cpp
Pull request: ci : bump komac version

Completely untested, hopefully fixes https://github.com/ggml-org/llama.cpp/issues/18509#issuecomment-3912882761

Changed files:
filename: .github/workflows/winget.yml
patch: @@ -17,7 +17,7 @@ jobs:
 
       - name: Install komac
         run: |
-          cargo binstall komac@2.11.2 -y
+          cargo binstall komac@2.15.0 -y
 
       - name: Find latest release
         id: find_latest_release
Repository: ollama/ollama
Pull request: Add Terminal App for README.md

add a very useful Terminal App for README.md

Changed files:
filename: README.md
patch: @@ -361,6 +361,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [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
+- [aichat](https://github.com/sigoden/aichat) All-in-one LLM CLI tool featuring Shell Assistant, Chat-REPL, RAG, AI tools & agents, with access to OpenAI, Claude, Gemini, Ollama, Groq, and more.
 
 ### Apple Vision Pro
 - [Enchanted](https://github.com/AugustDev/enchanted)
Repository: facebook/react
Pull request: [eslint-plugin-react-compiler] Fix type error with recommended config

## Summary

In the recommended configuration for `eslint-plugin-react-compiler`, i.e. `reactCompiler.configs.recommended`, the rule is typed as `string` rather than `eslint.Linter.RuleEntry` or anything assignable thereto, which results in the following type error if you type check your eslint configuration: 
```
Property ''react-compiler/react-compiler'' is incompatible with index signature.
  Type 'string' is not assignable to type 'RuleEntry | undefined'.
```
Simply adding a const assertion fixes the error.

## How did you test this change?

I emitted declarations for the module and confirmed that the rule is now typed as the string literal `'error'`

Changed files:
filename: compiler/packages/eslint-plugin-react-compiler/src/index.ts
patch: @@ -25,7 +25,7 @@ const configs = {
       },
     },
     rules: {
-      'react-compiler/react-compiler': 'error',
+      'react-compiler/react-compiler': 'error' as const,
     },
   },
 };
Repository: huggingface/transformers
Pull request: [Quantization] Fixing some tests

# What does this PR do?

Fix some remaining tests 

Changed files:
filename: src/transformers/quantizers/quantizer_bitnet.py
patch: @@ -81,7 +81,6 @@ def _process_model_before_weight_loading(
             model,
             modules_to_not_convert=self.modules_to_not_convert,
             quantization_config=self.quantization_config,
-            pre_quantized=self.pre_quantized,
         )
 
     def adjust_max_memory(self, max_memory: dict[str, int | str]) -> dict[str, int | str]:

filename: tests/quantization/bnb/test_4bit.py
patch: @@ -722,13 +722,13 @@ def test_serialization(self, quant_type="nf4", double_quant=True):
                         self.assertTrue(v0 == v1)
 
         # comparing forward() outputs
-        encoded_input = tokenizer(self.input_text, return_tensors="pt").to(torch_device)
+        encoded_input = tokenizer(self.input_text, return_tensors="pt", return_token_type_ids=False).to(torch_device)
         out_0 = model_0(**encoded_input)
         out_1 = model_1(**encoded_input)
         torch.testing.assert_close(out_0["logits"], out_1["logits"], rtol=0.05, atol=0.05)
 
         # comparing generate() outputs
-        encoded_input = tokenizer(self.input_text, return_tensors="pt").to(torch_device)
+        encoded_input = tokenizer(self.input_text, return_tensors="pt", return_token_type_ids=False).to(torch_device)
         output_sequences_0 = model_0.generate(**encoded_input, max_new_tokens=10)
         output_sequences_1 = model_1.generate(**encoded_input, max_new_tokens=10)
 

filename: tests/quantization/torchao_integration/test_torchao.py
patch: @@ -677,7 +677,7 @@ def test_autoquant(self):
         self.assertIn(tokenizer.decode(output[0], skip_special_tokens=True), EXPECTED_OUTPUTS)
 
 
-@require_torchao_version_greater_or_equal("0.11.0")
+@require_torchao_version_greater_or_equal("0.15.0")
 @slow
 class TorchAoSerializationTest(unittest.TestCase):
     input_text = "What are we having for dinner?"
Repository: ollama/ollama
Pull request: Add GoLamify in Libraries section

### GoLamify Package

This PR adds the [GoLamify](https://github.com/prasad89/golamify), a Go package designed to simplify integration of Go projects with Ollama. 

The GoLamify package provides an easy and efficient way to connect Go applications with Ollama services, allowing for seamless interaction and enhanced functionality.

Changed files:
filename: README.md
patch: @@ -417,6 +417,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Ollama PHP](https://github.com/ArdaGnsrn/ollama-php)
 - [Agents-Flex for Java](https://github.com/agents-flex/agents-flex) with [example](https://github.com/agents-flex/agents-flex/tree/main/agents-flex-llm/agents-flex-llm-ollama/src/test/java/com/agentsflex/llm/ollama)
 - [Ollama for Swift](https://github.com/mattt/ollama-swift)
+- [GoLamify](https://github.com/prasad89/golamify)
 
 ### Mobile
Repository: vuejs/vue
Pull request: test: correcting existing test case

Fix the location of the test case

<!--
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)

- [ ] Bugfix
- [ ] Feature
- [ ] Code style update
- [ ] Refactor
- [ ] Build-related changes
- [x] Other, please describe: correcting existing test case

**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: test/unit/features/global-api/set-delete.spec.js
patch: @@ -52,6 +52,24 @@ describe('Global API: set/delete', () => {
         expect(vm.$el.innerHTML).toBe('')
       }).then(done)
     })
+
+    it('be able to use string type index in array', done => {
+      const vm = new Vue({
+        template: '<div><p v-for="obj in lists">{{obj.name}}</p></div>',
+        data: {
+          lists: [
+            { name: 'A' },
+            { name: 'B' },
+            { name: 'C' }
+          ]
+        }
+      }).$mount()
+      expect(vm.$el.innerHTML).toBe('<p>A</p><p>B</p><p>C</p>')
+      Vue.set(vm.lists, '0', { name: 'D' })
+      waitForUpdate(() => {
+        expect(vm.$el.innerHTML).toBe('<p>D</p><p>B</p><p>C</p>')
+      }).then(done)
+    })
   })
 
   describe('Vue.delete', () => {
@@ -96,23 +114,5 @@ describe('Global API: set/delete', () => {
         expect(vm.$el.innerHTML).toBe('')
       }).then(done)
     })
-
-    it('be able to use string type index in array', done => {
-      const vm = new Vue({
-        template: '<div><p v-for="obj in lists">{{obj.name}}</p></div>',
-        data: {
-          lists: [
-            { name: 'A' },
-            { name: 'B' },
-            { name: 'C' }
-          ]
-        }
-      }).$mount()
-      expect(vm.$el.innerHTML).toBe('<p>A</p><p>B</p><p>C</p>')
-      Vue.set(vm.lists, '0', { name: 'D' })
-      waitForUpdate(() => {
-        expect(vm.$el.innerHTML).toBe('<p>D</p><p>B</p><p>C</p>')
-      }).then(done)
-    })
   })
 })
Repository: ollama/ollama
Pull request: Added Chrome and Firefox extension link to documentation

Link to a browser extension that enables using Ollama for interacting with web pages.

Changed files:
filename: README.md
patch: @@ -454,6 +454,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [Discord-Ollama Chat Bot](https://github.com/kevinthedang/discord-ollama) (Generalized TypeScript Discord Bot w/ Tuning Documentation)
 - [Discord AI chat/moderation bot](https://github.com/rapmd73/Companion) Chat/moderation bot written in python. Uses Ollama to create personalities.
 - [Headless Ollama](https://github.com/nischalj10/headless-ollama) (Scripts to automatically install ollama client & models on any OS for apps that depends on ollama server)
+- [Local AI Helper](https://github.com/ivostoykov/localAI) (Chrome and Firefox extensions that enable interactions with the active tab and customisable API endpoints. Includes secure storage for user prompts.)
 - [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)
Repository: ggml-org/llama.cpp
Pull request: build : link ws2_32 as PUBLIC on Windows

Related to https://github.com/ggml-org/llama.cpp/pull/19623

Changed files:
filename: tools/server/CMakeLists.txt
patch: @@ -59,8 +59,4 @@ target_include_directories(${TARGET} PRIVATE ../mtmd)
 target_include_directories(${TARGET} PRIVATE ${CMAKE_SOURCE_DIR})
 target_link_libraries(${TARGET} PRIVATE server-context PUBLIC common cpp-httplib ${CMAKE_THREAD_LIBS_INIT})
 
-if (WIN32)
-    TARGET_LINK_LIBRARIES(${TARGET} PRIVATE ws2_32)
-endif()
-
 target_compile_features(${TARGET} PRIVATE cxx_std_17)

filename: vendor/cpp-httplib/CMakeLists.txt
patch: @@ -17,7 +17,7 @@ endif()
 target_link_libraries(${TARGET} PRIVATE Threads::Threads)
 
 if (WIN32 AND NOT MSVC)
-    target_link_libraries(${TARGET} PRIVATE ws2_32)
+    target_link_libraries(${TARGET} PUBLIC ws2_32)
 endif()
 
 target_compile_features(${TARGET} PRIVATE cxx_std_17)
Repository: ggml-org/llama.cpp
Pull request: build : cleanup library linking logic


Changed files:
filename: common/CMakeLists.txt
patch: @@ -5,7 +5,6 @@ find_package(Threads REQUIRED)
 llama_add_compile_flags()
 
 # Build info header
-#
 
 if(EXISTS "${PROJECT_SOURCE_DIR}/.git")
     set(GIT_DIR "${PROJECT_SOURCE_DIR}/.git")
@@ -110,29 +109,16 @@ if (BUILD_SHARED_LIBS)
     set_target_properties(${TARGET} PROPERTIES POSITION_INDEPENDENT_CODE ON)
 endif()
 
-# TODO: use list(APPEND LLAMA_COMMON_EXTRA_LIBS ...)
-set(LLAMA_COMMON_EXTRA_LIBS build_info)
-set(LLAMA_COMMON_EXTRA_LIBS ${LLAMA_COMMON_EXTRA_LIBS} cpp-httplib)
+target_link_libraries(${TARGET} PRIVATE
+    build_info
+    cpp-httplib
+)
 
 if (LLAMA_LLGUIDANCE)
     include(ExternalProject)
     set(LLGUIDANCE_SRC ${CMAKE_BINARY_DIR}/llguidance/source)
     set(LLGUIDANCE_PATH ${LLGUIDANCE_SRC}/target/release)
-
-    # Set the correct library file extension based on platform
-    if (WIN32)
-        set(LLGUIDANCE_LIB_NAME "llguidance.lib")
-        # Add Windows-specific libraries
-        set(LLGUIDANCE_PLATFORM_LIBS
-            ws2_32    # Windows Sockets API
-            userenv   # For GetUserProfileDirectoryW
-            ntdll     # For NT functions
-            bcrypt    # For BCryptGenRandom
-        )
-    else()
-        set(LLGUIDANCE_LIB_NAME "libllguidance.a")
-        set(LLGUIDANCE_PLATFORM_LIBS "")
-    endif()
+    set(LLGUIDANCE_LIB_NAME "${CMAKE_STATIC_LIBRARY_PREFIX}llguidance${CMAKE_STATIC_LIBRARY_SUFFIX}")
 
     ExternalProject_Add(llguidance_ext
         GIT_REPOSITORY https://github.com/guidance-ai/llguidance
@@ -154,8 +140,10 @@ if (LLAMA_LLGUIDANCE)
     add_dependencies(llguidance llguidance_ext)
 
     target_include_directories(${TARGET} PRIVATE ${LLGUIDANCE_PATH})
-    # Add platform libraries to the main target
-    set(LLAMA_COMMON_EXTRA_LIBS ${LLAMA_COMMON_EXTRA_LIBS} llguidance ${LLGUIDANCE_PLATFORM_LIBS})
-endif ()
+    target_link_libraries(${TARGET} PRIVATE llguidance)
+    if (WIN32)
+        target_link_libraries(${TARGET} PRIVATE ws2_32 userenv ntdll bcrypt)
+    endif()
+endif()
 
-target_link_libraries(${TARGET} PRIVATE ${LLAMA_COMMON_EXTRA_LIBS} PUBLIC llama Threads::Threads)
+target_link_libraries(${TARGET} PUBLIC llama Threads::Threads)
Repository: vuejs/vue
Pull request: fix #5941, should check $vnode existence before accessing ssrContext

[#5941](https://github.com/vuejs/vue/issues/5941)

<!--
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/core/index.js
patch: @@ -11,7 +11,7 @@ Object.defineProperty(Vue.prototype, '$isServer', {
 Object.defineProperty(Vue.prototype, '$ssrContext', {
   get () {
     /* istanbul ignore next */
-    return this.$vnode.ssrContext
+    return this.$vnode && this.$vnode.ssrContext
   }
 })
 

filename: test/ssr/ssr-basic-renderer.spec.js
patch: @@ -50,4 +50,21 @@ describe('SSR: basicRenderer', () => {
       done()
     })
   })
+
+  // #5941
+  it('should work peoperly when accessing $ssrContext in root component', done => {
+    let ssrContext
+    renderToString(new Vue({
+      template: `
+        <div></div>
+      `,
+      created () {
+        ssrContext = this.$ssrContext
+      }
+    }), (err, result) => {
+      expect(err).toBeNull()
+      expect(ssrContext).toBeUndefined()
+      done()
+    })
+  })
 })
Repository: facebook/react
Pull request: [eprh] Don't transpile to es5


Now that we've moved the sync location of the plugin, we no longer need this since those restrictions no longer apply.
---
[//]: # (BEGIN SAPLING FOOTER)
Stack created with [Sapling](https://sapling-scm.com). Best reviewed with [ReviewStack](https://reviewstack.dev/facebook/react/pull/32669).
* __->__ #32669
* #32668

Changed files:
filename: scripts/rollup/build.js
patch: @@ -26,7 +26,6 @@ const {asyncRimRaf} = require('./utils');
 const codeFrame = require('@babel/code-frame').default;
 const Wrappers = require('./wrappers');
 const commonjs = require('@rollup/plugin-commonjs');
-const {getBabelOutputPlugin} = require('@rollup/plugin-babel');
 
 const RELEASE_CHANNEL = process.env.RELEASE_CHANNEL;
 
@@ -418,12 +417,6 @@ function getPlugins(
           bundle
         )
       ),
-      // For Meta internal requirements this package needs to be built targeting ES5.
-      bundle.name === 'eslint-plugin-react-hooks'
-        ? getBabelOutputPlugin({
-            presets: ['@babel/preset-env'],
-          })
-        : false,
       // Remove 'use strict' from individual source files. We skip eslint-plugin-react-hooks because
       // it bundles compiler-type code that may examine "use strict" used outside of a directive
       // context, e.g. as a StringLiteral.
@@ -503,7 +496,7 @@ function getPlugins(
           // takes care of it.
           renaming: false,
         }),
-      (needsMinifiedByClosure || bundle.name === 'eslint-plugin-react-hooks') &&
+      needsMinifiedByClosure &&
         // Add the whitespace back
         prettier({
           parser: 'flow',
Repository: vercel/next.js
Pull request: Fix: Missing null check in LRU cleanup

Unfortunately this field is not strongly typed because it's a cyclic type and I wasn't able to soundly model it with TypeScript. Skill issue I'm sure.

Don't have an exact repro yet but the previous code was obviously wrong.

The way this should have been structured regardless is to delete the wrapper MapEntry object instead of the value it contains. The non-nullness of the wrapper object _is_ properly typed, and avoids an unnecessary indirection.

As a follow up, I'll look into how to model this type properly.

Changed files:
filename: packages/next/src/client/components/segment-cache/cache-map.ts
patch: @@ -396,7 +396,7 @@ function dropRef<V extends MapValue>(value: V): void {
   value.ref = null
 }
 
-function deleteMapEntry<V extends MapValue>(entry: MapEntry<V>): void {
+export function deleteMapEntry<V extends MapValue>(entry: MapEntry<V>): void {
   // Delete the entry from the cache.
   const emptyEntry: EmptyMapEntry<V> = entry as any
   emptyEntry.value = null

filename: packages/next/src/client/components/segment-cache/lru.ts
patch: @@ -1,5 +1,5 @@
 import type { MapEntry } from './cache-map'
-import { deleteFromCacheMap } from './cache-map'
+import { deleteMapEntry } from './cache-map'
 
 // We use an LRU for memory management. We must update this whenever we add or
 // remove a new cache entry, or when an entry changes size.
@@ -119,7 +119,7 @@ function cleanup() {
     if (tail !== null) {
       // Delete the entry from the map. In turn, this will remove it from
       // the LRU.
-      deleteFromCacheMap(tail.value)
+      deleteMapEntry(tail)
     }
   }
 }