sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: transformers
Issue: Feature to configure `stop_strings` in `generation_config.json` or other config files
Labels: Feature request,Generation

### Feature request

The transformer library should offer a way to configure `stop_strings` and the tokenizer for it.

`model.generate()` can take a `stop_strings` argument to use custom stop tokens for generation, but a tokenizer object needs to be passed as well.

```
model.generate(...,
               stop_strings=["<stop token>"],
               tokenizer=tokenizer)
```

If we add `stop_strings` to `generation_config.json`, which can be loaded correctly [code](https://github.com/huggingface/transformers/blob/33868a057c02f0368ba63bd1edb746be38fe3d90/src/transformers/generation/configuration_utils.py#L144-L145), it will return the following error, as it requires a tokenizer object, which cannot be defined in the config file. 

```
>>> from transformers import AutoTokenizer, AutoModelForCausalLM
>>> tokenizer = AutoTokenizer.from_pretrained(model_path)
>>> model = AutoModelForCausalLM.from_pretrained(model_path, device_map="auto")
>>> model.generate(**tokenizer("Hi how are you?", return_tensors="pt", return_token_type_ids=False))

...

ValueError: There are one or more stop strings, either in the arguments to `generate` or in the model's generation config, but we could not locate a tokenizer. When generating with stop strings, you must pass the model's tokenizer to the `tokenizer` argument of `generate`.
```


### Motivation

The user shouldn't be bothered by adding extra arguments to `generate()` or `pipeline`.

For example, [nvidia/Mistral-NeMo-Minitron-8B-Instruct](https://huggingface.co/nvidia/Mistral-NeMo-Minitron-8B-Instruct) needs to use `stop_strings` but so many people simply calls `generate()` without `stop_strings` and share complaints.


### Your contribution

I'd be happy to create a PR but need guidance for the design choice.
Repository: neovim
Issue: mapping callback error report doesn't indicate where the error came from
Labels: bug,lua,mappings

### Problem

The error report should mention the mapping that generated the error
(or at least that it was a mapping). Some better examples are below.

There's no indication that this error came from a mapping callback

```
E5108: Error executing lua: [string ":source (no file)"]:2: in F2()
stack traceback:
        [C]: in function 'error'
        [string ":source (no file)"]:2: in function 'F2'
        [string ":source (no file)"]:5: in function 'F1'
        [string ":source (no file)"]:8: in function 'handler'
        [string ":source (no file)"]:15: in function <[string ":source (no file)"]:12>
```


### Steps to reproduce

Source the following and mouse click.
```lua
local function F2()
    error("in F2()")
end
local function F1()
    F2()
end
local function handler()
    F1()
end

vim.keymap.set('n', '<LeftMouse>', function()
    handler()
end)
```


### Expected behavior

The error report should mention the mapping that generated the error.

Here's examples for `autocommand` and `on_key` callbacks.
The first one looks like the gold standard.

```
Error detected while processing OptionSet Autocommands for "*":
Error executing lua callback: [string ":source (no file)"]:2: in F2()
stack traceback:
        [C]: in function 'error'
        [string ":source (no file)"]:2: in function 'F2'
        [string ":source (no file)"]:5: in function 'F1'
        [string ":source (no file)"]:8: in function 'handler'
        [string ":source (no file)"]:13: in function <[string ":source (no file)"]:12>
```

```
Error executing vim.on_key() callbacks: vim/_editor.lua:0: 
With ns_id 11: [string ":source (no file)"]:6: in F2()                                              
stack traceback:                                                                                    
        [C]: in function 'error'                                                                    
        [string ":source (no file)"]:6: in function 'F2'                                            
        [string ":source (no file)"]:9: in function 'F1'                                            
        [string ":source (no file)"]:12: in function <[string ":source (no file)"]:11>              
        [C]: in function 'xpcall'                                                                   
        vim/_editor.lua: in function <vim/_editor.lua:0>                                            
```


### Nvim version (nvim -v)

https://github.com/neovim/neovim/commit/b34e137e43d359c8db4fb76028dea3b410842aff

### Vim (not Nvim) behaves the same?

NA

### Operating system/version

ubuntu

### Terminal name/version

gnome-terminal

### $TERM environment variable

xterm-256color

### Installation

make install
Repository: ui
Issue: [feat]: Fix sidebar error in astro
Labels: area: request

### Feature description

TLDR;
Astro will not render if you do not make the following change:
Pls use `import { type VariantProps, cva } from "class-variance-authority";  ` istead of `import { VariantProps, cva } from "class-variance-authority"; 


### Affected component/components

Sidebar

### Additional Context

Error detail:

hook.js:608 [astro-island] Error hydrating /src/dashboard/main.tsx SyntaxError: The requested module '/node_modules/.vite/deps/class-variance-authority.js?v=0c4d54d3' does not provide an export named 'VariantProps' (at sidebar.tsx:3:10)

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: electron
Issue: [Bug] Behaviour changed for middle-click window title in gnome 46
Labels: platform/linux,bug :beetle:,blocked/upstream ❌

### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

30.5.1 (the version used in the latest vscode)

### What operating system(s) are you using?

Ubuntu

### Operating System Version

ubuntu 24.04

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

I use the mouse middle click (on a window's titlebar) to lower the window - so I can easily cycle through open windows. This setting is set via the shell, or the gnome tweaks tool.

### Actual Behavior

That changed in when upgrading to gnome 46. It doesn't honor that gnome setting anymore. So a middle click on the titlebar does nothing.

I've experienced this bug in a number of electron-based apps, including vscode.

### Testcase Gist URL

_No response_

### Additional Information

_No response_
Repository: neovim
Issue: foldtextresult() is inconsistent with the new 'foldtext' set to empty string feature
Labels: bug,folds

### Problem

When 'foldtext' is set to an empty string per PR #20750, calling the `foldtextresult()` function with the line number of a closed fold returns something like "+-- 4 lines folded".  I wonder if it would be more consistent with it's documentation to just return the actual buffer line's text --basically like `getline()`.

### Steps to reproduce

1. nvim --clean
2. `:set foldtext=`
3. paste some text in the buffer, e.g.

>  START FOLD AFTER THIS LINE
> Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua.
> Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat.
> Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur.
> Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.
>  END FOLD BEFORE THIS LINE

5. fold some of the text manually ('foldmethod' doesn't matter)
6. `:echom foldtextresult(2)`
7. given the above text, result will be "+-- 4 lines folded"




### Expected behavior

Return a string of the text being displayed for the closed fold--essentially what `getline()` would give you for that line.

### Nvim version (nvim -v)

v0.11.0-dev-1075+gb34e137e43

### Vim (not Nvim) behaves the same?

nvim only feature

### Operating system/version

Windows 11

### Terminal name/version

Windows Terminal

### $TERM environment variable

NA

### Installation

Download and extract from releases
Repository: godot
Issue: Crash when inserting rotation keyframe
Labels: bug,topic:editor,crash,topic:animation

### Tested versions

Godot Engine v4.3.stable.flathub

### System information

Godot v4.3.stable (77dcf97d8) - Freedesktop SDK 24.08 (Flatpak runtime) - X11 - Vulkan (Forward+) - dedicated AMD Radeon RX 6600 (RADV NAVI23) - 12th Gen Intel(R) Core(TM) i5-12600K (16 Threads)

### Issue description

crash occurs when attempting to insert a rotation keyframe on a bone in this hierarchy 
spine -> spine.001 -> spine.002 -> spine.003 -> upper_arm.L
the skeleton and model mesh are imported from an FBX i downloaded off of itch.io
here: [https://dblob-ua.itch.io/low-poly-characterchar-ronin-01](url)

### Steps to reproduce

1. download the file and import it to godot
2. open it as a new inherited scene
3. place the animation track as a child to Skeleton3D
4. create a new animation
5. add upper_arm.L and upper_arm.R rotation to the track
6. insert a keyframe

godot will crash.

### Minimal reproduction project (MRP)

[keyframe_crash.zip](https://github.com/user-attachments/files/17605539/keyframe_crash.zip)
Repository: godot
Issue: Function _exit_tree() is not called properly in editor mode
Labels: bug,topic:core

### Tested versions

v4.3.stable

### System information

Godot v4.3.stable (77dcf97d8) - Windows 10.0.22621 - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 4070 Ti (NVIDIA; 32.0.15.6094) - 13th Gen Intel(R) Core(TM) i5-13600KF (20 Threads)

### Issue description

```gdscript
extends Node2D


func _enter_tree() -> void:
	print("_enter_tree")
	pass


# Called when the node enters the scene tree for the first time.
func _ready() -> void:
	print("_ready")
	pass # Replace with function body.


func _exit_tree() -> void:
	print("_exit_tree")
	pass

```
I expect the print result:
```gdscript
_enter_tree
_ready
_exit_tree
```
But currently the print result:
```gdscript
_enter_tree
_ready
```

### Steps to reproduce

Run the project in the editor and close the window.
Check the print results.

### Minimal reproduction project (MRP)

[bugtest.zip](https://github.com/user-attachments/files/17605660/bugtest.zip)
Repository: neovim
Issue: `nvim_get_autocmd()` should return filepath and line-number
Labels: enhancement,api,events

### Problem

`nvim_get_autocmd()` unlike `autocmd [group]` doesnt return the line number and the filepath, which it should

### Expected behavior

running `nvim_get_autocmd()`  should return the filepath and line number
Repository: ui
Issue: [bug]: Popover doesn't work on firefox
Labels: bug

### Describe the bug

popover doesn't work on firefox browsers

### Affected component/components

popover

### How to reproduce

1.open app on firefox browsers
2.create popover and add trigger on button

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Ubuntu 24.04.1,firefox developer edition 133.0b3, firefox 132.0,next 14.2.15, react 18
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ollama
Issue: [Model request] The First-Ever Comprehensive Benchmark for Multimodal Large Language Models in Industrial Anomaly Detection
Labels: model request

https://github.com/jam-cc/MMAD
![examples](https://github.com/user-attachments/assets/7e76cd00-b93d-4c0a-acf9-17d1ab1609e7)

The First-Ever Comprehensive Benchmark for Multimodal Large Language Models in Industrial Anomaly Detection
Repository: svelte
Issue: Docs: Playground snippet demo not showing letters in dark mode
Labels: documentation

### Describe the bug

As you can see in the following screenshot, it is hard to read letters in the table when using a darkmode.

![image](https://github.com/user-attachments/assets/d5ecd081-6431-48c2-8727-49e39a738e0e)


### Reproduction

[Demo](https://svelte.dev/playground/untitled?version=5.1.9#H4sIAAAAAAAAE41Sy27bMBD8lYVcwHYrW4kBXxRFaP-htzgHSqQsojLJkuu2BqF_74qUrfhxCHQRh7MzO9z1SSM74ZL8zSeKHUSSJz-MSdIET2Y4uD-iQ0Fnp4-2HpDC1VYaLHdqh_JgtEX4yapOQGP1AebrLJzWsXD-QjQi1lo5JMZRooNXeBuwHXoYLHOYM2OoiXkKv_GUwzYFY2VNFxvo0xtqxRR9F-7z04X8fE-uW2GtnJQ3E_tpvYV-oL9Ti0U2hVJFjMMZslcfW-5DWj9zShojEFrBuLCLZR_9CmzLQCwy-psw8rxBgvkNhhpZd8F8NppE7Stbq_8u-GTKS8_XQ9Keqnl5BZP1AzTYP2bDV7i7_9hLEeda0iocNJeNFDzJ0R5Fn142JzA-uzsdBfLhldPxPdMhIPS0H1-M1cYtlnejwdBDfBXZjHXTFOg4BhuOtvTfrVDEmAZG2ew5ezYV-Ew2fVzVAivNTyPHzwSr29AlMAe8f6g-zuWDts-GusAmdBSkv3P7qnB4GpMEEHwsRPEPV6yTe5VDJxp8iXClLRmtnGG1VHva3oCPHQd9QJsrbFd1Kzu-2Khvz8uzZsXqX3urj4rnMBNCXNUG83zf6Yp1C2yXKdxA_KJjGOfRfb0Vh7MKDShEuV-M9_4_nq6svF4EAAA=)

### Logs

_No response_

### System Info

```shell
N/A
```


### Severity

annoyance
Repository: PowerToys
Issue: Transparent screensaver/screenlock
Labels: Needs-Triage

### Description of the new feature / enhancement

Would be nice to have a transparent screensaver. Computer is locked but can see everything on the screen. Very helpful for people who observing datas.  The opacity should be adjustable from 0-100%. Unlock the screensaver with the current user password, a lokal password, or better with the members of an Active Directory group.

### Scenario when this would be used?

In all offices where people have to observe screens/dashboards. Like in OPS centres.

### Supporting information

_No response_
Repository: godot
Issue: Popup windows that are opened with popup_centered will open at the top left corner on linux when started visible
Labels: bug,topic:gui

### Tested versions

Reproducible in v4.4.dev3.official [f4af8201b], v4.3.stable.official [77dcf97d8], v4.2.1.stable.official [b09f793f5], v4.1.stable.official [970459615]

Not reproducible in v4.0.4.stable.official [fc0b241c9]

Not reproducible on Windows, only linux

Reproducible on both X11 and Wayland

### System information

Godot v4.3.stable - Linux Mint 22 (Wilma) - X11 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 960 (nvidia; 550.120) - AMD FX(tm)-6300 Six-Core Processor (6 Threads)

### Issue description

On linux, when you call popup_centered on a visible window it appears at the top left of the screen. It looks like it has the correct position for a frame or two, but then snaps to the corner.

Here is a video of the bug happening on 4.4.dev3:

https://github.com/user-attachments/assets/3e9ddb60-70db-4944-9582-7ac23fb19c30

You can see that both visible and not visible have a few frames in the beginning where it appears in a different place. It's even happening on the main game window. I suspect these are the same bug.

Here is what it looks like on 4.0.4:

https://github.com/user-attachments/assets/d4fdaf5a-0a7b-44d6-8727-957557d25572

This also happens in other places, like the "Export" and "Export All" window.

https://github.com/user-attachments/assets/791437fc-8fd1-4136-8f7e-21ef88f16aef

I had a look at the source code and in the ProjectExportDialog::_export_all_dialog method, it looks like it's calling the "show" method. Commenting this out resulted in the same behavior as in the first video, where not showing it made it open at the center but with the wrong position for a frame.

### Steps to reproduce

1. Open the editor on linux
2. Go to Project  > Export
3. Set up an export, then click "Export All"
4. The dialog will open in the top left corner

Alternatively:

1. Open the example project
2. Run the game with window.tscn's visibility off, it opens at the center.
3. Run the game with window.tscn's visibility on, it opens at the top left corner.

### Minimal reproduction project (MRP)

[popup test.zip](https://github.com/user-attachments/files/17606275/popup.test.zip)
Repository: deno
Issue: deno_terminal: ansi color does not be handled correctly in file
Labels: bug,needs info,dx

Steps to reproduce:

```sh
deno install --log-level trace npm:zustand
```
Ansi color displays correctly in terminal.

But with this:
```
deno install --log-level trace npm:zustand &> log
```
Ansi color does not be handled correctly, I think it should be stripped.

If I use npm cli, ansi color displays correctly in terminal, and it is stripped in file.
Repository: flutter
Issue: Stop pinning dependencies
Labels: customer: crowd,team-infra,P2,triaged-infra

### Use case

One of the biggest pain points for package authors (and probably app developers too) that have been brought up during the Dart & Flutter Package Ecosystem Summits is that Flutter has pinned versions of its dependencies.

Why do we not want pinned dependencies? Because it leads to a lot trickier dependency version resolution than it needs to be for the end user. I would say almost all Flutter developers have at some point ended up in dependency resolution hell, before they realize that some dependencies needs to be treated with special care.

Since all of the pinned dependencies are controlled by Google it should be fairly straight forward to set up a process so that they all have some tests towards Flutter before doing a new non-breaking release or doing deprecations.
The main ones are: intl, meta, collection path, vector_math and async.

The Flutter team’s rationale for using pinned versions is outlined in [this document](https://github.com/dart-lang/sdk/blob/main/docs/Flutter-Pinned-Packages.md) but **I have been told that removing the dependency pinning is on the radar, so I just want to open this so that we can track it somewhere.**

### Proposal

Things that needs to be solved:
 - [ ] Flutter builds should be hermetic.
 - [ ] When dependencies bump their versions they should not be able to break Flutter.

For the first one I'm thinking that it could be solved with a lock file that isn't shipped with Flutter, but used for the builds.

For the second one my suggestion is that we introduce CI checks that needs to run before releasing a new version of the dependencies to make sure that they don't break anything in Flutter. Deprecations have to be taken into consideration here too, since they are not counted as breaking in semver.
Repository: rust
Issue: Tracking issue for release notes of #130660: Tracking Issue for `const_char_encode_utf16`
Labels: T-libs-api,relnotes,relnotes-tracking-issue


This issue tracks the release notes text for #130660.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Tracking Issue for `const_char_encode_utf16`](https://github.com/rust-lang/rust/issues/130660)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @bjoernager -- origin issue/PR authors and assignees for starting to draft text
Repository: neovim
Issue: kitty keyboard protocol + shifted keys; qwertz keyboard not handling c-]
Labels: bug,tui,input

### Problem

Alacritty 0.14 released with a [kitty keyboard protocol fix](https://github.com/alacritty/alacritty/pull/7993) that causes key combinations like `c-]` with a qwertz keyboard layout to be interpreted as `<c-9>` of `c-]` within nvim.

~I'm not entirely sure if that's a alacritty regression, or if the kitty keyboard support in neovim is the problem. In vim the same works.~ Fairly sure it's a neovim kitty keyboard protocol issue, other terminals like ghostty have the same problem

### Steps to reproduce

- Install alacritty 0.14 and setup qwertz keyboard layout 
- nvim --clean
- Enter insert mode
- Type `c-v` followed by `c-]` (or try to use tagfunc)

In case it matters: This is on linux with sway.

### Expected behavior

Inserts `^]`  instead of `<c-9>`

### Nvim version (nvim -v)

NVIM v0.11.0-dev-1082+g3688a33354

### Vim (not Nvim) behaves the same?

No

### Operating system/version

Archlinux

### Terminal name/version

alacritty 0.14

### $TERM environment variable

alacritty

### Installation

CMAKE_BUILD_TYPE=RelWithDebInfo make
Repository: TypeScript
Issue: [Regression] Failed to assign to a discriminated union class property when its type is inferred from constructor
Labels: Bug,Help Wanted

### 🔎 Search Terms

property infer constructor discriminated

### 🕗 Version & Regression Information

- This changed between versions 4.3.5 and 4.4.4 (also in latest)


### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=4.4.4#code/C4TwDgpgBAysCGxoF4oG8qkgLigcgCcBXAOxIEsSBzPAGigGdIIATXEogWwCMICoAvlAA+6TOAi48DYAHswkFnkEBuAFBqAxgBt4DBlACCmufzRqolqGALkAbomgzH6q1AD07t1YB6Afg03TVkSGWITWQIACgBKdAtvS2AAC3IGADpnJChUDCxJfBl5RWUhPVgEJFcrAUCrYhIopghWdi5eAjjzRKTUjKyUMXypBopqOkZmFkEEy1qBIA

### 💻 Code

```ts
type State = { type: 'running', speed: number } | { type: 'stopped' };

class Actor {
    private state;
    //       ^? Actor.state: State

    constructor() {
        this.state = { type: 'stopped' } as State;
    }

    run(speed: number) {
        this.state = { type: 'running', speed }
    }
}
```


### 🙁 Actual behavior

`Type 'string' is not assignable to type '"running" | "stopped"'.(2322)`

### 🙂 Expected behavior

No error, as in 4.3.5.

### Additional information about the issue

If the property's type is explicitly declared as `private state: State` the error is gone.