sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ollama
Issue: GGML_ASSERT(ggml_nelements(a) == ne0*ne1*ne2) failed
Labels: bug

### What is the issue?

If I try to run the `llama3.2-vision` model using  `ollama run llama3.2-vision` on my Arch Linux machine, I get this error:
```
Error: llama runner process has terminated: GGML_ASSERT(ggml_nelements(a) == ne0*ne1*ne2) failed
```
`ollama run llama3.2` and `ollama run llava` works fine.

I have an i7-6700K and a GeForce GTX 1060 6GB. I installed ollama using `pacman -S ollama`

### OS

Linux

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.4.1
Repository: godot
Issue: Evaluator has no access to autoload singletons
Labels: bug,topic:editor

### Tested versions

4.4 dev4

### System information

Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; 31.0.15.4633) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)

### Issue description

When you try to access autoload singleton via evaluator, you will get error `Invalid named index 'AutoloadName' for base type Object`
The workaround is to access it by path `get_node(/root/AutoloadName` (if you are inside Node script)

### Steps to reproduce

1. Add autoload singleton
2. Run a script with breakpoint
3. Type the autoloat's name in the Debugger's Evaulator

### Minimal reproduction project (MRP)

N/A
Repository: godot
Issue: Evaluator does not work without breakpoint
Labels: bug,topic:editor

### Tested versions

4.4 dev4

### System information

Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; 31.0.15.4633) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)

### Issue description

When you try to use Evaluator without a breakpoint (by using Pause Running Project), you'll get `GDScriptLanguage::debug_get_stack_level_instance: Index p_level = -1 is out of bounds (_call_stack.stack_pos = 0).` error and the project will resume.
The error is expected (expected, i.e. there is really no stack trace), the resume part is some weird bug. But the evaluator should just stay disabled in this case. Yet you can write and execute expression.

### Steps to reproduce

1. Run project from editor
2. Pause it (F7)
3. Use Debugger's Evaluator

### Minimal reproduction project (MRP)

N/A
Repository: godot
Issue: Built-in script live reloading is broken again
Labels: bug,topic:gdscript,topic:editor,regression

### Tested versions

Broken in 4.4 dev4
Works in 4.4 dev3

### System information

Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; 31.0.15.4633) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)

### Issue description

#94012 implemented live reloading for built-in scrpipts. But it's not working in 4.4 dev4. Modifying and saving a built-in script while the project is running will result in
```
E GDScriptLanguage::reload_scripts: Condition "fresh.is_null()" is true. Continuing.
  <C++ Source>   modules\gdscript\gdscript.cpp:2668 @ GDScriptLanguage::reload_scripts()
```
and the runtime script is unchanged.

### Steps to reproduce

1. Add a node with built-in script (which for example prints something in `_process()`
2. Run the project
3. Modify the script and save (e.g. change what it's printing)
4. The script is not reflected in the running project
5. Also error

### Minimal reproduction project (MRP)

N/A
Repository: next.js
Issue: Parallel Intercepted routes not working when accessed from 404 error pages
Labels: bug,Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://github.com/itsjavi/nextjs-demos/tree/issue/parallel-intercepted-404

### To Reproduce


1. Add a parallel intercepted route [like in this example](https://github.com/itsjavi/nextjs-demos/tree/issue/parallel-intercepted-404/src/app)
3. Add the following to your app:
   - error.tsx page
   - support for the `@modal` slot in your layout.tsx props, and put it inside the body.
   - a Link in your layout.tsx, linking to the intercepted route
7. Navigate to any non-existing route to trigger a 404 error page
8. Click to the link of the layout that would trigger the intercepted route

### Current vs. Expected behavior

### Current behavior

#### On `next dev`
When accessing Parallel Intercepted routes from a 404 page, it triggers the following client-side error:

```
UI:

Application error: a client-side exception has occurred (see the browser console for more information).

Console:

app-router.ts:52 TypeError: initialTree is not iterable
    at applyPatch (apply-router-state-patch-to-tree.ts:17:51)
    at applyRouterStatePatchToTree (apply-router-state-patch-to-tree.ts:107:26)
    at navigate-reducer.ts:208:50

The above error occurred in the <Router> component. It was handled by the <ErrorBoundaryHandler> error boundary.
```

#### On `next start`

On `next start`, after build, navigating to the intercepted route from a 404 page works, but calling router.back() will trigger the same error again.

### Expected behavior

- The intercepted route content is shown on 404 pages, when navigating to that route.
- router.back() works as expected in all the above scenarios.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:15 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 20.18.0
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: 9.12.2
Relevant Packages:
  next: 15.0.3 // Latest available version is detected (15.0.3).
  eslint-config-next: N/A
  react: 19.0.0-rc-66855b96-20241106
  react-dom: 19.0.0-rc-66855b96-20241106
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Parallel & Intercepting Routes

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

### Additional context

- The Parallel Intercepted routes work fine from error.tsx pages.
- Repository to reproduce the issue: https://github.com/itsjavi/nextjs-demos/tree/issue/parallel-intercepted-404
- PR with the problematic changes: https://github.com/itsjavi/nextjs-demos/pull/1/files

CC @feedthejim
Related issue: https://github.com/vercel/next.js/issues/48289
Repository: godot
Issue: Opening File in Script Editor Overwrites Contents of Current Tab and Doesn't Change the Tab Label
Labels: bug,topic:editor

### Tested versions

Reproducible in: v4.3.stable.official [77dcf97d8]

### System information

Godot v4.3.stable - Ubuntu 20.04.6 LTS (Focal Fossa) - X11 - Vulkan (Forward+) - dedicated Quadro P600 (nvidia; 470.256.02) - Intel(R) Core(TM) i5-8300H CPU @ 2.30GHz (8 Threads)

### Issue description

With a file currently open in the active script editor tab, opening another file (through the FileSystem Panel or the File->Open menu option in the script editor) overwrites the contents of the current file in the active tab and does not update the tab label.  I expected the operation to open the second file in a new tab with the correct label, and not overwrite the contents of the previously opened file in the old tab.

### Steps to reproduce

Open any project with at least 2 script files (say a.gd and b.gd ).  Assume the script editor shows the code from the a.gd file with a label of 'a'.  In the editor panel, open the b.gd file in the script editor via the File->Open menu selection.  No new tab opens.  Instead the contents of the 'a' tab gets overwritten with the contents of the b.gd file.

### Minimal reproduction project (MRP)

N/A
Repository: godot
Issue: physical_keycode differs between X11 and wayland
Labels: bug,platform:linuxbsd,topic:porting,topic:input

### Tested versions

Reproducible in:
- v4.3.stable.official [77dcf97d8]
- v4.4.dev4.official [36e6207bb]

### System information

Godot v4.4.dev4 - Arch Linux #1 SMP PREEMPT_DYNAMIC Fri, 01 Nov 2024 03:30:41 +0000 on Wayland - X11 display driver, Multi-window, 3 monitors - Vulkan (Mobile) - dedicated AMD Radeon RX 6900 XT (RADV NAVI21) - AMD Ryzen 9 3950X 16-Core Processor (32 threads)

### Issue description

On a swiss german keyboard layout, the physical_keycode of the § and < keys are swapped on Wayland compared to X11. keycode and key_label are the same. The keys Ü and ¨ have different physical_keycode and keycode, but the same key_label. I tested a few other ISO layouts and they had the same issue.

| Keyboard        | X11 physical_keycode | Wayland physical_keycode | X11 keycode | Wayland keycode | X11 key_label | Wayland key_label |
| --------------- | -------------------- | ------------------------ | ----------- | --------------- | ------------- | ----------------- |
| § (below Esc)   | 96                   | 167                      | 167         | 167             | 167           | 167               |
| < (left of Y)   | 167                  | 96                       | 60          | 60              | 60            | 60                |
| Ü (right of P)  | 91                   | 123                      | 91          | 123             | 220           | 220               |
| ¨ (right of Ü)  | 93                   | 125                      | 93          | 125             | 93            | 125               |


### Steps to reproduce

You need a keyboard with a physical ISO layout. JIS apparently works correctly (https://github.com/godotengine/godot/issues/99008#issuecomment-2569627474). No idea about ANSI.

Open the attached MRP and set `display/display_server/driver.linuxbsd` to `x11` or `wayland`. Start the project, press the keys from the table above and check the values in the output tab in the editor.

### Minimal reproduction project (MRP)

[bug-physical_key.zip](https://github.com/user-attachments/files/17689638/bug-physical_key.zip)
Repository: stable-diffusion-webui
Issue: [Bug]: --dump-sysinfo command line argument does not work
Labels: bug-report

### Checklist

- [X] The issue exists after disabling all extensions
- [X] The issue exists on a clean installation of webui
- [ ] The issue is caused by an extension, but I believe it is caused by a bug in the webui
- [X] The issue exists in the current version of the webui
- [X] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

Starting WebUI with the command line argument --dump-sysinfo causes a crash soon after starting.

### Steps to reproduce the problem

Start WebUI with the command line argument --dump-sysinfo

### What should have happened?

The --dump-sysinfo option should dump sysinfo.

### What browsers do you use to access the UI ?

Mozilla Firefox

### Sysinfo

[sysinfo-2024-11-09-23-37.json](https://github.com/user-attachments/files/17689692/sysinfo-2024-11-09-23-37.json)


### Console logs

```Shell
venv "E:\ai_stuff\stable-diffusion-webui\venv\Scripts\Python.exe"
no module 'xformers'. Processing without...
no module 'xformers'. Processing without...
No module 'xformers'. Proceeding without it.
E:\ai_stuff\stable-diffusion-webui\venv\lib\site-packages\pytorch_lightning\utilities\distributed.py:258: LightningDeprecationWarning: `pytorch_lightning.utilities.distributed.rank_zero_only` has been deprecated in v1.8.1 and will be removed in v2.0.0. You can import it from `pytorch_lightning.utilities` instead.
  rank_zero_deprecation(
Traceback (most recent call last):
  File "E:\ai_stuff\stable-diffusion-webui\launch.py", line 48, in <module>
    main()
  File "E:\ai_stuff\stable-diffusion-webui\launch.py", line 29, in main
    filename = launch_utils.dump_sysinfo()
  File "E:\ai_stuff\stable-diffusion-webui\modules\launch_utils.py", line 476, in dump_sysinfo
    text = sysinfo.get()
  File "E:\ai_stuff\stable-diffusion-webui\modules\sysinfo.py", line 46, in get
    res = get_dict()
  File "E:\ai_stuff\stable-diffusion-webui\modules\sysinfo.py", line 119, in get_dict
    "Extensions": get_extensions(enabled=True, fallback_disabled_extensions=config.get('disabled_extensions', [])),
AttributeError: 'str' object has no attribute 'get'
Press any key to continue . . .
```


### Additional information

_No response_
Repository: godot
Issue: Invoking .callv() when doing so would cause an error instead fails silently
Labels: bug,topic:core

### Tested versions

- Reproducible in 4.3.stable

### System information

Godot v4.3.stable - Windows 10.0.19045 - GLES3 (Compatibility)

### Issue description

Invoking .callv() in a situation that would normally produce an (invoke-related) error instead fails silently.

Qualifying errors include but are maybe not limited to:
- `Invalid type in function` 
- `Invalid call to function`

### Steps to reproduce

1. Execute the following code:
```gdscript
func _ready() -> void:
	print_int.callv(["5"]) # Fails silently. No error.
	self.callv("print_int", ["5"]) # Fails silently. No error.
	print_int.call("5") # Errors correctly: Invalid type in function '...'. Cannot convert argument 1 from String to int.
	
func print_int(number : int) -> void:
	print(number)
```
2. Observe that `.callv()` does not correctly result in an error

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: Add backgroundColor property for children in ExpansionTile
Labels: c: new feature,framework,f: material design,waiting for PR to land (fixed),c: proposal,P3,team-design,triaged-design

### Use case

### Description:

It would be helpful if the ExpansionTile widget could have a backgroundColor property specifically for its child elements. Currently, ExpansionTile provides a backgroundColor property that applies to the header area, but there’s no way to set a separate background color for the expanded children section. Adding this feature would enable more customization options for developers, allowing us to differentiate the background color of the children from the tile header.



### Proposal

- Introduce a new property, e.g., childrenBackgroundColor, in the ExpansionTile widget.
- This property should control the background color of the expanded children section only, leaving the header background color unaffected.
- Ensure that the property is compatible with both light and dark themes and can be set independently of the backgroundColor for the header.
Repository: PowerToys
Issue: Cant type in power toys run
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

I'm unsure how to trigger this, but I Frequently end up being able to enter text into power toys run after it launches. i've tried switching between admin or not, but have been unable to debug the root cause.  Would appreciate help debugging.

 [PowerToysReport_2024-11-09-18-14-33.zip](https://github.com/user-attachments/files/17689761/PowerToysReport_2024-11-09-18-14-33.zip)h


### ✔️ Expected Behavior

Can launch power toys run and type

### ❌ Actual Behavior

PowerToys run launched, but I was unable to to type into the launcher 

### Other Software

_No response_
Repository: langchain
Issue: The Qdrant Vector Store, for filtering is not using the right imports.
Labels: 🤖:docs

### URL

https://python.langchain.com/docs/integrations/vectorstores/qdrant/

### Checklist

- [X] I added a very descriptive title to this issue.
- [X] I included a link to the documentation page I am referring to (if applicable).

### Issue with current documentation:

The code https://github.com/langchain-ai/langchain/blob/master/docs/docs/integrations/vectorstores/qdrant.ipynb

```python
from qdrant_client.http import models

results = vector_store.similarity_search(
    query="Who are the best soccer players in the world?",
    k=1,
    filter=models.Filter(
        should=[
            models.FieldCondition(
                key="page_content",
                match=models.MatchValue(
                    value="The top 10 soccer players in the world right now."
                ),
            ),
        ]
    ),
)
for doc in results:
    print(f"* {doc.page_content} [{doc.metadata}]")
```

Uses a wrong import the right is: 

from qdrant_client import models

```python
from qdrant_client import models

results = vector_store.similarity_search(
    query="Who are the best soccer players in the world?",
    k=1,
    filter=models.Filter(
        should=[
            models.FieldCondition(
                key="page_content",
                match=models.MatchValue(
                    value="The top 10 soccer players in the world right now."
                ),
            ),
        ]
    ),
)
for doc in results:
    print(f"* {doc.page_content} [{doc.metadata}]")
```

Source:

https://qdrant.tech/documentation/concepts/filtering/



### Idea or request for content:

Please update the import since I changed with the one used in the Qdrant documentation the metadata filtering started working fine.

Source File: https://github.com/langchain-ai/langchain/blob/master/docs/docs/integrations/vectorstores/qdrant.ipynb
Repository: PowerToys
Issue: Keyboard Manager apps filter
Labels: Needs-Triage

### Description of the new feature / enhancement

I suggest applying application filters for the Keyboard manager function.
Sometimes I switch to other apps (like games) that don't expect to use keyboard remap

### Scenario when this would be used?

Keyboard manager

### Supporting information

_No response_
Repository: react
Issue: [Compiler Bug]: "InvalidReact: Mutating component props or hook arguments is not allowed" When Passing a MutableRef as a prop, then mutating it in child
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [X] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [X] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAgBMEAzAQygBsCSoA7OXASwjvwAUyYE7cBhCAFtsdHrgAUASnzAAOm3xxWYAhjLDKCAEql8AXnxQw20uIDkAOQhnJ8+fnzdcsNuPsP8AHgB87j174ACyZKQgFhVjEZADpY4DUNExIAX2T8AHpfBX9PQiYAN3xWPkomOABrPWApPW85bP9FZQhNaMoIAHNzAAkyfIR8IJDCQ2MAURISBEYwfAAjBB5HegB+MwAafATMTR0SaLhYbl5bBodUjKyczPdJAG55ZLs6WgZmVkHg0PCRMXF49DqHZJZLSeoOIwICZTRjiKT6bwyPxbQGJPYHI5RAxmACaCDAZncyU2AG1trtSABdU7uJwuLx5fI3OhPOggZJAA

### Repro steps

1. Instantiate a ref in the parent
2. Mutate the current property in a useEffect in the child

### How often does this bug happen?

Every time

### What version of React are you using?

18.3.1

### What version of React Compiler are you using?

19.0.0-beta-63b359f-20241101
Repository: react
Issue: [Compiler Bug]: "Mutating a value returned from 'useContext()', which should not be mutated" When the value is a Ref
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [X] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [X] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAgHgBwjALgAjggDswCBZATwGETcMCBeQmBAQ3tuPvVwApgAHWKCebALaYANggBKCAGbJ8wOLFbdlxKFKkBfYXoCUw4Rmx58AE0VsdBBVGJxcASxL4ACmw25akkgRuPiMVYXxCEjJ8DAlpOUV8ZigwBIU+AHIAOQgMkxFiCNZcWEK+cIj8AB4APgrK6qouHlwAOk8YCAA3VxsYfC62KSgERmBgWMkZeQU9PTrChsqq6gALVykrf2xiIIIAegWl6v2mugZ2zp6+o+XDiqMAbkNTYkdnNw81ja2IAN3gqEhIsiKQCMAYug4tNEnokvgUghmgw+GduAx8hVEQBRBQKBAuPghJI1MKLCKTeIzVpqGC+eEZACaCDAGQqegANPgANqUmEKAC6+QiFWKpWqVlcXXuxAMxBAeiAA

### Repro steps

1. Instantiate a Context
2. In Parent, Instantiate a ref
3. Wrap the child in the Context's Provider, and pass the ref as a value
4. Get the ref in the child, and mutate it in a useEffect

### How often does this bug happen?

Every time

### What version of React are you using?

18.3.1

### What version of React Compiler are you using?

19.0.0-beta-63b359f-20241101
Repository: neovim
Issue: Feature: Make `priority` affect `line_hl_group`
Labels: enhancement,marks

### Problem

At the moment `line_hl_group` affects extmarks using `hl_group`(gets rid of the highlight groups) but doesn't affect extmarks using `virt_text`(doesn't combine background color).

![Image](https://github.com/user-attachments/assets/12ed47ce-ed26-48ee-8226-c9e22d4145ca)
<sup>`label` text loses it's highlight group color despite having a higher priority value. The surrounding virtual text doesn't combine the background color even with `hl_mode="combine"`</sup>


So, I think it would be nice if we could add extmarks on top of `line_hl_group` via `priority` so they don't get overriden by it.

### Expected behavior

Extmarks with a higher priority than `line_hl_group` will be added **on top** of the highlight group of the line.

This way it would be possible to highlight a region of lines and have virtual texts & specific highlight groups be visible.
Repository: flutter
Issue: Setting an offset for the `Tooltip` can cause the `GestureDetector`'s tap event to become ineffective.
Labels: framework,f: material design,has reproducible steps,P2,team-design,triaged-design,found in release: 3.24,found in release: 3.27

### Steps to reproduce

I suspect that the offset is only applied to the view part, and the mask part is not handled, which is causing the issue.

```dart
Tooltip(
      message: widget.tooltip ?? '',
      // After adding these three lines, the `GestureDetector`'s tap event becomes ineffective.
      // preferBelow: false,
      // verticalOffset: -13,
      // margin: const EdgeInsets.only(left: 30),
      child: GestureDetector(onTap: widget.onPressed,)
)
```

### Expected results

tap event effective

### Actual results

tap event ineffective

### Code sample

```dart
Tooltip(
      message: widget.tooltip ?? '',
      // After adding these three lines, the `GestureDetector`'s tap event becomes ineffective.
      // preferBelow: false,
      // verticalOffset: -13,
      // margin: const EdgeInsets.only(left: 30),
      child: GestureDetector(onTap: widget.onPressed,)
)
```

### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

...
Repository: PowerToys
Issue: Advances Paste Settings, Typo/Truncated words
Labels: Issue-Bug,Product-Settings,Area-User Interface,Priority-3,Cost-Small

### Microsoft PowerToys version

0.86.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Advanced Paste, Settings

### Steps to reproduce

In the settings for Advanced Paste, some of the words are cut off. See screenshot.

![Image](https://github.com/user-attachments/assets/d9fe0818-7b2c-4cdf-9a0e-6cb1e404f814)


Ok so this seemed like a #good first issue, so I decided to try to fix it... problem is _I don't know really any coding_, but I thought I would give it a try, I even tried to get GitHub copilot to help me, but all I got was the directory where I [think ](src/settings-ui/Settings.UI/SettingsXAML/Controls/ShortcutControl/ShortcutControl.xaml.cs) the changes need to be made (turn on word wrap or maybe a bigger dialog box or something like that...) 
Well, I so badly wanted a "Thanks @technobulb" in the next release.....

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_