helloadhavan/github_issues huggingface dataset:
Repository: ollama/ollama
Pull request: doc Update:  Linux uninstall

Linux instructions now correctly tell u how to uninstall ollama completely

Changed files:
filename: docs/linux.md
patch: @@ -186,3 +186,9 @@ sudo rm -r /usr/share/ollama
 sudo userdel ollama
 sudo groupdel ollama
 ```
+
+Remove installed libraries:
+
+```shell
+sudo rm -rf /usr/local/lib/ollama
+```
Repository: facebook/react
Pull request: [Flight] Don't increase serializedSize for every recursive pass

I noticed that we increase this in the recursive part of the algorithm. This would mean that we'd count a key more than once if it has Server Components inside it recursively resolving. This moves it out to where we enter from toJSON. Which is called once per JSON entry (and therefore once per key).

Changed files:
filename: packages/react-server/src/ReactFlightServer.js
patch: @@ -2302,6 +2302,9 @@ function renderModel(
   key: string,
   value: ReactClientValue,
 ): ReactJSONValue {
+  // First time we're serializing the key, we should add it to the size.
+  serializedSize += key.length;
+
   const prevKeyPath = task.keyPath;
   const prevImplicitSlot = task.implicitSlot;
   try {
@@ -2416,8 +2419,6 @@ function renderModelDestructive(
   // Set the currently rendering model
   task.model = value;
 
-  serializedSize += parentPropertyName.length;
-
   // Special Symbol, that's very common.
   if (value === REACT_ELEMENT_TYPE) {
     return '$';
Repository: ggml-org/llama.cpp
Pull request: ggml: update comments for backends which have no memory to report

Ref: #20150

This PR updates the comments for backends which have no memory to report. By default, llama.cpp will default to host memory information if the backend reports `*free = 0; *total = 0;`.

This will help maintainers understand that reporting 0 bytes is not a bug, but rather, allow downstream GGML consumers to decide what they want to do in the event that the backend reports 0 bytes.

Changed files:
filename: ggml/src/ggml-blas/ggml-blas.cpp
patch: @@ -339,8 +339,8 @@ static const char * ggml_backend_blas_device_get_description(ggml_backend_dev_t
 }
 
 static void ggml_backend_blas_device_get_memory(ggml_backend_dev_t dev, size_t * free, size_t * total) {
-    // TODO
-    *free = 0;
+    // no memory to report
+    *free  = 0;
     *total = 0;
 
     GGML_UNUSED(dev);

filename: ggml/src/ggml-opencl/ggml-opencl.cpp
patch: @@ -5345,7 +5345,8 @@ static const char * ggml_backend_opencl_device_get_description(ggml_backend_dev_
 }
 
 static void ggml_backend_opencl_device_get_memory(ggml_backend_dev_t dev, size_t * free, size_t * total) {
-    *free = 0;
+    // no memory to report
+    *free  = 0;
     *total = 0;
 
     GGML_UNUSED(dev);
Repository: facebook/react
Pull request: [eslint-plugin-react-hooks] update doc url for rules of hooks

<!--
  Thanks for submitting a pull request!
  We appreciate you spending the time to work on these changes. Please provide enough information so that others can review your pull request. The three fields below are mandatory.

  Before submitting a pull request, please make sure the following is done:

  1. Fork [the repository](https://github.com/facebook/react) and create your branch from `main`.
  2. Run `yarn` in the repository root.
  3. If you've fixed a bug or added code that should be tested, add tests!
  4. Ensure the test suite passes (`yarn test`). Tip: `yarn test --watch TestName` is helpful in development.
  5. Run `yarn test --prod` to test in the production environment. It supports the same options as `yarn test`.
  6. If you need a debugger, run `yarn test --debug --watch TestName`, open `chrome://inspect`, and press "Inspect".
  7. Format your code with [prettier](https://github.com/prettier/prettier) (`yarn prettier`).
  8. Make sure your code lints (`yarn lint`). Tip: `yarn linc` to only check changed files.
  9. Run the [Flow](https://flowtype.org/) type checks (`yarn flow`).
  10. If you haven't already, complete the CLA.

  Learn more about contributing: https://reactjs.org/docs/how-to-contribute.html
-->

## Summary

<!--
 Explain the **motivation** for making this change. What existing problem does the pull request solve?
-->

![CleanShot 2025-05-05 at 08 48 05@2x](https://github.com/user-attachments/assets/30b90299-43af-4d2d-a4ba-1abbab0654b8)

In the editor, the eslint extension displays corresponding links when errors occur.

## How did you test this change?

<!--
  Demonstrate the code is solid. Example: The exact commands you ran and their output, screenshots / videos if the pull request changes the user interface.
  How exactly did you verify that your PR solves the issue you wanted to solve?
  If you leave this empty, your PR will very likely be closed.
-->


Changed files:
filename: packages/eslint-plugin-react-hooks/src/rules/RulesOfHooks.ts
patch: @@ -128,7 +128,7 @@ const rule = {
     docs: {
       description: 'enforces the Rules of Hooks',
       recommended: true,
-      url: 'https://reactjs.org/docs/hooks-rules.html',
+      url: 'https://react.dev/reference/rules/rules-of-hooks',
     },
   },
   create(context: Rule.RuleContext) {
Repository: ollama/ollama
Pull request: build: add missing dependencies

- `hsa-runtime64` used `_` so it was filtered out
- add missing `rocsparse` and `rocsolver`

Changed files:
filename: CMakeLists.txt
patch: @@ -96,11 +96,12 @@ if(CMAKE_HIP_COMPILER)
 
     if(AMDGPU_TARGETS)
         add_subdirectory(${CMAKE_CURRENT_SOURCE_DIR}/ml/backend/ggml/ggml/src/ggml-hip)
+
         set(OLLAMA_HIP_INSTALL_DIR ${OLLAMA_INSTALL_DIR}/rocm)
         install(TARGETS ggml-hip
             RUNTIME_DEPENDENCIES
                 DIRECTORIES ${HIP_BIN_INSTALL_DIR} ${HIP_LIB_INSTALL_DIR}
-                PRE_INCLUDE_REGEXES amdhip64 hipblas rocblas amd_comgr hsa_runtime64 rocprofiler-register drm_amdgpu drm numa
+                PRE_INCLUDE_REGEXES hipblas rocblas amdhip64 rocsolver amd_comgr hsa-runtime64 rocsparse rocprofiler-register drm drm_amdgpu
                 PRE_EXCLUDE_REGEXES ".*"
                 POST_EXCLUDE_REGEXES "system32"
             RUNTIME DESTINATION ${OLLAMA_HIP_INSTALL_DIR} COMPONENT HIP
Repository: vercel/next.js
Pull request: Turbopack: prefetch children too

### What?

children need to be prefetched too, since connect_child accesses the child to check for scheduling

Changed files:
filename: turbopack/crates/turbo-tasks-backend/src/backend/operation/mod.rs
patch: @@ -1003,6 +1003,7 @@ impl<B: BackingStorage> TaskGuard for TaskGuardImpl<'_, B> {
         let map = iter_many!(self, OutputDependency { target } => (target, TaskDataCategory::Meta))
             .chain(iter_many!(self, CellDependency { target } => (target.task, TaskDataCategory::All)))
             .chain(iter_many!(self, CollectiblesDependency { target } => (target.task, TaskDataCategory::All)))
+            .chain(iter_many!(self, Child { task } => (task, TaskDataCategory::All)))
             .collect::<FxIndexMap<_, _>>();
         (map.len() > 1).then_some(map)
     }
Repository: vuejs/vue
Pull request: Update downloads badge to point to graph of downloads

<!--
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] Other: update link for download badge in readme

**Does this PR introduce a breaking change?** (check one)

- [ ] Yes
- [x] No

**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
- [ ] All tests are passing (It's not passing but I don't think it's because of the change to the readme)

**Other information:**

Hi! I noticed that your "npm" badge and "downloads" badge currently both point to the same page for the project on npmjs.org  

I was wondering if you might prefer having the download badge point to a [download chart](https://npmcharts.com/compare/vue?minimal=true) instead?

If not, feel free to close and apologies for the drive-by PR 😄

Changed files:
filename: README.md
patch: @@ -3,7 +3,7 @@
 <p align="center">
   <a href="https://circleci.com/gh/vuejs/vue/tree/dev"><img src="https://img.shields.io/circleci/project/vuejs/vue/dev.svg" alt="Build Status"></a>
   <a href="https://codecov.io/github/vuejs/vue?branch=dev"><img src="https://img.shields.io/codecov/c/github/vuejs/vue/dev.svg" alt="Coverage Status"></a>
-  <a href="https://www.npmjs.com/package/vue"><img src="https://img.shields.io/npm/dm/vue.svg" alt="Downloads"></a>
+  <a href="https://npmcharts.com/compare/vue?minimal=true"><img src="https://img.shields.io/npm/dm/vue.svg" alt="Downloads"></a>
   <a href="https://www.npmjs.com/package/vue"><img src="https://img.shields.io/npm/v/vue.svg" alt="Version"></a>
   <a href="https://www.npmjs.com/package/vue"><img src="https://img.shields.io/npm/l/vue.svg" alt="License"></a>
   <a href="https://chat.vuejs.org/"><img src="https://img.shields.io/badge/chat-on%20discord-7289da.svg" alt="Chat"></a>
Repository: ggml-org/llama.cpp
Pull request: context: ignore zero scale LoRAs when checking sameness

When passed a set of input LoRAs, `set_adapters_lora` never stores zero scale LoRAs in the `loras` field, but `adapters_lora_are_same` expects the number of inputs to be equal to the number of stored LoRAs. So there will always be a mismatch if zero scale adapters are passed repeatedly.

This causes a server started with `--lora-init-without-apply` to re-reserve the graph for every token when handling requests with `"lora": [{"id": 0, "scale": 0.0}]`.

Tested:

* Started a server with `llama-server --model tmp/ggml-org_stories15M_MOE_stories15M_MOE-F16.gguf --lora tmp/moe_shakespeare15M.gguf --lora-init-without-apply`
* Sent a chat request with `"lora": [{"id": 0, "scale": 0.0}]` via the Web UI
* Results without this patch: The server logs print `sched_reserve: reserving ...` for every token
* Results with this patch: The server prints `sched_reserve: reserving ...` just once (or not at all)

The server unit tests still pass, but I don't know how to add a test specifically for this bug (unless I want to rely on inference performance, which seems suboptimal).

Alternative fixes considered:

* Filter the list of adapters in `set_adapters_lora` before calling `adapters_lora_are_same`. However, that would require allocating even for the not-modified case, which it seemed better to avoid.
* Filter the list of adapters in the server code. However, this functionality is exposed via the public `llama_set_adapters_lora` API, so it seemed better to fix this for everyone.

AI Disclaimer: Claude Code was used to identify the problem after describing the symptoms. The patch was authored by a human (me).

Changed files:
filename: src/llama-context.cpp
patch: @@ -1039,18 +1039,26 @@ void llama_context::set_adapters_lora(llama_adapter_lora ** adapters, size_t n_a
 bool llama_context::adapters_lora_are_same(llama_adapter_lora ** adapters, size_t n_adapters, float * scales) {
     LLAMA_LOG_DEBUG("%s: adapters = %p\n", __func__, (void *) adapters);
 
-    if (n_adapters != loras->size()) {
-        return false;
-    }
+    // Adapters with a zero scale are never added to `loras`, so also ignore them for the comparison.
+    size_t n_non_zero = 0;
 
     for (size_t i = 0; i < n_adapters; i ++) {
+        if (scales[i] == 0.0f) {
+            continue;
+        }
+        n_non_zero++;
+
         auto it = loras->find(adapters[i]);
 
         if (it == loras->end() || it->second != scales[i]) {
             return false;
         }
     }
 
+    if (n_non_zero != loras->size()) {
+        return false;
+    }
+
     return true;
 }
Repository: vuejs/vue
Pull request: fix(types): fix wrong errorCaptured type

<!--
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
- [ ] 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:**
`errorCaptured` lifecycle hook actually receives some parameters. https://vuejs.org/v2/api/#errorCaptured

Changed files:
filename: types/options.d.ts
patch: @@ -80,7 +80,7 @@ export interface ComponentOptions<
   updated?(): void;
   activated?(): void;
   deactivated?(): void;
-  errorCaptured?(): boolean | void;
+  errorCaptured?(err: Error, vm: Vue, info: string): boolean | void;
 
   directives?: { [key: string]: DirectiveFunction | DirectiveOptions };
   components?: { [key: string]: Component<any, any, any, any> | AsyncComponent<any, any, any, any> };

filename: types/test/options-test.ts
patch: @@ -199,7 +199,10 @@ Vue.component('component', {
   updated() {},
   activated() {},
   deactivated() {},
-  errorCaptured() {
+  errorCaptured(err, vm, info) {
+    err.message
+    vm.$emit('error')
+    info.toUpperCase()
     return true
   },
Repository: facebook/react
Pull request: [compiler] ValidatePreservedManualMemoization reports detailed errors

Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom):
* __->__ #33095

This pass didn't previously report the precise difference btw inferred/manual dependencies unless a debug flag was set. But the error message is really good (nice job @mofeiz): the only catch is that in theory the inferred dep could be a temporary that can't trivially be reported to the user.

But the messages are really useful for quickly verifying why the compiler couldn't preserve memoization. So here we switch to outputting a detailed message about the discrepancy btw inferred/manual deps so long as the inferred dep root is a named variable. I also slightly adjusted the message to handle the case where there is no diagnostic, which can occur if there were no manual deps but the compiler inferred a dependency.

Changed files:
filename: compiler/packages/babel-plugin-react-compiler/src/Validation/ValidatePreservedManualMemoization.ts
patch: @@ -5,7 +5,6 @@
  * LICENSE file in the root directory of this source tree.
  */
 
-import prettyFormat from 'pretty-format';
 import {CompilerError, ErrorSeverity} from '../CompilerError';
 import {
   DeclarationId,
Repository: ollama/ollama
Pull request: Add simple-discord-ai to README.md

Hi there, I decided to pick up this project just for fun.

The main goal is to have a simple, small codebase that is easy to use and deploy. 
Currently, I am the only developer and just began this yesterday. It would certainly help gain publicity and contributors if you accepted this PR.

Currently the only feature missing is memories, which I plan on adding eventually via Redis or SQL (Likely SQL, although I havent fully decided yet)

The main feature, being prompts works fine. The user can ask questions by mentioning the bot and it will respond. (With the exception of follow up questions, again, due to the lack of a memory database.)

Changed files:
filename: README.md
patch: @@ -535,6 +535,7 @@ See the [API documentation](./docs/api.md) for all endpoints.
 - [TextCraft](https://github.com/suncloudsmoon/TextCraft) (Copilot in Word alternative using Ollama)
 - [Alfred Ollama](https://github.com/zeitlings/alfred-ollama) (Alfred Workflow)
 - [TextLLaMA](https://github.com/adarshM84/TextLLaMA) A Chrome Extension that helps you write emails, correct grammar, and translate into any language
+- [Simple-Discord-AI](https://github.com/zyphixor/simple-discord-ai)
 
 ### Supported backends
Repository: vuejs/vue
Pull request: fix(types): make render option in functional components to optional

<!--
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
- [ ] 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:**
Since we can write a template of functional component in SFC, the `render` option of functional component can be omitted now.


Changed files:
filename: types/options.d.ts
patch: @@ -110,7 +110,7 @@ export interface FunctionalComponentOptions<Props = DefaultProps, PropDefs = Pro
   props?: PropDefs;
   inject?: InjectOptions;
   functional: boolean;
-  render(this: undefined, createElement: CreateElement, context: RenderContext<Props>): VNode;
+  render?(this: undefined, createElement: CreateElement, context: RenderContext<Props>): VNode;
 }
 
 export interface RenderContext<Props=DefaultProps> {

filename: types/test/options-test.ts
patch: @@ -331,6 +331,10 @@ Vue.component('functional-component-object-inject', {
   }
 })
 
+Vue.component('functional-component-check-optional', {
+  functional: true
+})
+
 Vue.component("async-component", ((resolve, reject) => {
   setTimeout(() => {
     resolve(Vue.component("component"));
Repository: facebook/react
Pull request: [compiler] Fix for string attribute values with emoji

Stack from [ghstack](https://github.com/ezyang/ghstack) (oldest at bottom):
* __->__ #33096

If a JSX attribute value is a string that contains unicode or other characters that need special escaping, we wrap the attribute value in an expression container. However, our unicode to detect this only handled the basic unicode character plane, not the "astral" plane which includes emojis.

This PR updates the regex to detect such extended characters and also use an expression container.

Expands on the fix from #29141, #29648, etc.

Closes #32915.

Changed files:
filename: compiler/packages/babel-plugin-react-compiler/src/ReactiveScopes/CodegenReactiveFunction.ts
patch: @@ -2327,9 +2327,12 @@ function codegenInstructionValue(
  * u0080 to u009F: C1 control codes
  * u00A0 to uFFFF: All non-basic Latin characters
  * https://en.wikipedia.org/wiki/List_of_Unicode_characters#Control_codes
+ *
+ * u010000 to u10FFFF: Astral plane characters
+ * https://mathiasbynens.be/notes/javascript-unicode
  */
 const STRING_REQUIRES_EXPR_CONTAINER_PATTERN =
-  /[\u{0000}-\u{001F}\u{007F}\u{0080}-\u{FFFF}]|"|\\/u;
+  /[\u{0000}-\u{001F}\u{007F}\u{0080}-\u{FFFF}\u{010000}-\u{10FFFF}]|"|\\/u;
 function codegenJsxAttribute(
   cx: Context,
   attribute: JsxAttribute,

filename: compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/jsx-string-attribute-expression-container.expect.md
patch: @@ -11,6 +11,7 @@ function Component() {
       <Text value={'Lauren'} />
       <Text value={'சத்யா'} />
       <Text value={'Sathya'} />
+      <Text value={'welcome 👋'} />
     </div>
   );
 }
@@ -42,6 +43,7 @@ function Component() {
         <Text value="Lauren" />
         <Text value={"\u0B9A\u0BA4\u0BCD\u0BAF\u0BBE"} />
         <Text value="Sathya" />
+        <Text value={"welcome \uD83D\uDC4B"} />
       </div>
     );
     $[0] = t0;
@@ -74,4 +76,4 @@ export const FIXTURE_ENTRYPOINT = {
       
 ### Eval output
 (kind: ok) <div><span>
-</span><span>A	E</span><span>나은</span><span>Lauren</span><span>சத்யா</span><span>Sathya</span></div>
\ No newline at end of file
+</span><span>A	E</span><span>나은</span><span>Lauren</span><span>சத்யா</span><span>Sathya</span><span>welcome 👋</span></div>
\ No newline at end of file

filename: compiler/packages/babel-plugin-react-compiler/src/__tests__/fixtures/compiler/jsx-string-attribute-expression-container.js
patch: @@ -7,6 +7,7 @@ function Component() {
       <Text value={'Lauren'} />
       <Text value={'சத்யா'} />
       <Text value={'Sathya'} />
+      <Text value={'welcome 👋'} />
     </div>
   );
 }
Repository: huggingface/transformers
Pull request: QwenVL: add skipped keys in `setattr` as well

# What does this PR do?

As per title, getattr and setattr skip different set of keys now 


Changed files:
filename: src/transformers/models/qwen2_5_vl/configuration_qwen2_5_vl.py
patch: @@ -304,7 +304,7 @@ def __init__(
     def __setattr__(self, key, value):
         if (
             (text_config := super().__getattribute__("__dict__").get("text_config")) is not None
-            and key not in ["dtype", "_attn_implementation_internal"]
+            and key not in ["_name_or_path", "model_type", "dtype", "_attn_implementation_internal"]
             and key in text_config.__dict__
         ):
             setattr(text_config, key, value)

filename: src/transformers/models/qwen2_vl/configuration_qwen2_vl.py
patch: @@ -292,7 +292,7 @@ def __init__(
     def __setattr__(self, key, value):
         if (
             (text_config := super().__getattribute__("__dict__").get("text_config")) is not None
-            and key not in ["dtype", "_attn_implementation_internal"]
+            and key not in ["_name_or_path", "model_type", "dtype", "_attn_implementation_internal"]
             and key in text_config.__dict__
         ):
             setattr(text_config, key, value)
Repository: electron/electron
Pull request: build: fixup release notes generation

Backport of #49302

See that PR for details.


Notes: <!-- Please add a one-line description for app developers to read in the release notes, or 'none' if no notes relevant to app developers. Examples and help on special cases: https://github.com/electron/clerk/blob/main/README.md#examples -->none


Changed files:
filename: script/release/notes/notes.ts
patch: @@ -108,7 +108,8 @@ const runGit = async (dir: string, args: string[]) => {
   const response = spawnSync('git', args, {
     cwd: dir,
     encoding: 'utf8',
-    stdio: ['inherit', 'pipe', 'pipe']
+    stdio: ['inherit', 'pipe', 'pipe'],
+    maxBuffer: 100 * 1024 * 1024 // 100MB buffer to handle large git outputs
   });
   if (response.status !== 0) {
     throw new Error(response.stderr.trim());