sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Image without `priority` gets preloaded if it is set to `loading="eager"`
Labels: Image (next/image)

### Link to the code that reproduces this issue

https://github.com/derweili/next-image-preload-test

Deployed on Vercel: https://image-preload-test.vercel.app/

### To Reproduce

1. Add an image using the `<Image>` tag to your page.
2. Set the image to load eager using `<Image loading="eager" />`
3. On the frontend, inspect the code, especially the document head `<head>`.
4. In the `<head>` you will find a preload link for this image `<link rel="preload" as="image">` altough you didn't set the `priority` param

### Current vs. Expected behavior

**Current behavior:**
When a image is set to load eager by `loading="eager"` it gets preloaded.

_Example_:
```
<Image src="https://picsum.photos/seed/priority/400/300" alt="Logo" width={400} height={300} priority **/>**
<Image src="https://picsum.photos/seed/no-priority-loading-eager/400/300" alt="Logo" width={400} height={300} loading="eager" />
```
In this example, only the first image has set `priority` while the second does not have the `priority` tag but is only set to loading `eager`.
However, currently both get preloaded using a preload link.

**Expected behavior**
If a image is set to `loading="eager"` without `priority` it should not get preloaded.
Only images with `priority` should get preloaded.



### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 23.6.0: Thu Sep 12 23:35:29 PDT 2024; root:xnu-10063.141.1.701.1~1/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 20.12.2
  npm: 10.5.0
  Yarn: 1.22.22
  pnpm: 9.0.4
Relevant Packages:
  next: 14.2.5 // An outdated version detected (latest is 15.1.2), upgrade is highly recommended!
  eslint-config-next: 14.2.21
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.7.2
Next.js Config:
  output: N/A


This issue can be replicated with next@14 and next@15
```


### Which area(s) are affected? (Select all that apply)

Image (next/image)

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local), Vercel (Deployed)

### Additional context

I tested app router and pages router, this issue only happens on app router, but not on pages router. On pages router, only the image with `priority` gets preloaded.

I tested various versions and could replicate the issue from `next@13.4` (with react@18) to the latest canary versions `15.1.1-canary.17` and `next@14.3.0-canary.87` (both with react@19).

I noticed that when editing component, the wrong preload link sometimes gets removed during HMR. But when doing a hard refresh, its rendered again.

The preload link is included in the SSR response, so its no a client side rendering issue.
Repository: ui
Issue: [bug]: Combobox not working
Labels: bug

### Describe the bug

As stated in the title, the Combobox is not working across different components. When open, cannot select any options as it is stuck on the first option in the list

![Capture](https://github.com/user-attachments/assets/07280ab4-67b8-4122-89fd-307022391a1b)


### Affected component/components

Combobox 

### How to reproduce

1. Isolated the component to a new blank screen
2. Cleared all styling
3. Used it in incognito
4. Reinstalled it

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Chrome browser: Version 131.0.6778.140 (Official Build) (64-bit)
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: storybook
Issue: [Bug]: optimizePackageImports do not work in @storybook/nextjs
Labels: bug,needs triage

### Describe the bug

Some server code exported from barrel file. It works in nextjs itself because of optimizePackageImports, but fails to resolve some node packages in storybook.

### Reproduction link

https://stackblitz.com/edit/github-dvxhuih6-cb6t3t3m?file=src%2Fshared%2Findex.ts

### Reproduction steps

_No response_

### System

```bash
System:
    OS: Linux 5.0 undefined
    CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 1.0 - /bin/jsh
  Binaries:
    Node: 18.20.3 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.2.3 - /usr/local/bin/npm <----- active
    pnpm: 8.15.6 - /usr/local/bin/pnpm
  npmPackages:
    @storybook/addon-essentials: ^8.5.0-beta.4 => 8.5.0-beta.4 
    @storybook/addon-interactions: ^8.5.0-beta.4 => 8.5.0-beta.4 
    @storybook/addon-onboarding: ^8.5.0-beta.4 => 8.5.0-beta.4 
    @storybook/blocks: ^8.5.0-beta.4 => 8.5.0-beta.4 
    @storybook/nextjs: ^8.5.0-beta.4 => 8.5.0-beta.4 
    @storybook/react: ^8.5.0-beta.4 => 8.5.0-beta.4 
    @storybook/test: ^8.5.0-beta.4 => 8.5.0-beta.4 
    storybook: ^8.5.0-beta.4 => 8.5.0-beta.4
```

### Additional context

_No response_
Repository: PowerToys
Issue: Unnecessary information
Labels: Needs-Triage

### Description of the new feature / enhancement

Good afternoon, your application is wonderful, I want to suggest a little minimalism in the output of information. The fact is that I have enabled only 5 functions, and when I call for help on commands, I see many commands that are no longer relevant to me at the time of work. In the future, I suggest displaying only those hints that are enabled by the user, thank you for your understanding. I repeat, I like your project and I'm just suggesting changes that you might like too. I wish you a good development! Good luck!![Image](https://github.com/user-attachments/assets/4695e231-8390-44a4-817c-6d1675caaeab)
![Image](https://github.com/user-attachments/assets/b133d3ab-137f-4723-8b9b-44d024f245ea)


### Scenario when this would be used?

Calling for help on commands

### Supporting information

_No response_
Repository: TypeScript
Issue: Incorrect type returned by TextEncoder.encode
Labels: Bug,Help Wanted,Domain: lib.d.ts

### 🔎 Search Terms

TypedArray, Uint8Array, ArrayBufferLike, TextEncoder

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about TextEncoder



### ⏯ Playground Link

[Playground link](https://www.typescriptlang.org/play/?target=99#code/MYewdgzgLgBAJgQygmBeGYCmB3GAVTADygFExQ5MAnACgEoA6TckSmgIgAtMAbHkdnQCwAKAD0YmFJgA9APwwAqgEswUABwBBKlQQBPADzbdegEIBXAGaXqAGWUBrTAD5RE-NxgADY-ovW7R0wvGABbfRhVYB5zSm8AZU4EKkw4XzMrGyovABoYACNzWC9mCkx6ELdJcB49GAhzAAdGkCooCG90-yzc+pAYKE5lDvyUhAcOspgiRsxgKFUAcxgEME6dP0zqLwZRUUtzcgXwGEaqEGBMCAgAESQEGjgALhgurao6GABvUSl3OH60EyogAvnsRGcLldbvdHvcGIUAh8YO48EMOhBOCBzDw4DBsK0HHlCrAUi02qkVh0oHpZtMdK0gA)

### 💻 Code

```ts
const data = new TextEncoder().encode("hello")
//    ^? Uint8Array<ArrayBufferLike>
// The `ArrayBufferLike` may include `SharedArrayBuffer`, but `encode()` 
// only supports `ArrayBuffer`, so this breaks code expecting an `ArrayBuffer`.

function processData(d: ArrayBuffer) {
  // do stuff
}

processData(data.buffer) // This should work, but reported as type error
```


### 🙁 Actual behavior

Values returned by TextEncoder.encode are not assignable to `ArrayBuffer`.

### 🙂 Expected behavior

Values returned by TextEncoder.encode should be assignable to `ArrayBuffer`.

### Additional information about the issue

https://stackoverflow.com/a/79300250/1494725
Repository: PowerToys
Issue: Mouse without borders looses button press functionality randomly
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

The mouse cannot click or drag windows on the other monitor. Although the pointer is visible it can neither click nor drag any objects. I need to disconnect and reconnect or restart the second desktop to get back the functionality. It happens randomly.

### ✔️ Expected Behavior

Expecting to click and drag with the mouse on the second dekstop

### ❌ Actual Behavior

Randomly looses the click/drag functionality on the second desktop even though the pointer is visible.

### Other Software

_No response_
Repository: transformers
Issue: Set output_attentions=True for model.geneate
Labels: bug,Generation

### System Info

transformers==4.44.0
Ubuntu 22.04.2 LTS  
python==3.10.13

### Who can help?

@ArthurZucker 

### Information

- [ ] The official example scripts
- [X] My own modified scripts

### Tasks

- [X] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)

### Reproduction

1. I used the LLaVA arch with LlavaQwen2ForCausalLM.
2. I will get right response with output_attentions=False in model.generate()
3. The response are not expected and some nan in scores with output_attentions=True.

### Expected behavior

I expected get normal response with attention score.
Repository: PowerToys
Issue: Workspaces should save the current state effortlessly
Labels: Needs-Triage,Product-Workspaces

### Description of the new feature / enhancement

Hi. in attempt to make it easier to get right back on track, Workspaces has to also make it easy for us to *configure* our configs/workspaces. Currently it asks us to write cli args manually ![Image](https://github.com/user-attachments/assets/81460e55-e204-4b3e-89f3-98499599e46c)

ideally this should not be the case and the capturer should be able to also capture the cli args automatically. Because if we are to write the cli args manually, then we might as well just save it all to a `.cmd` file and just double click that instead.

### Scenario when this would be used?

capturing the state of our new workspace

### Supporting information

_No response_
Repository: PowerToys
Issue: Unable to open PowerToys after update 0.87.1
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Advanced Paste

### Steps to reproduce

I don't know how to reproduce it. I have two laptops, on the first one the update caused the application to be completely blocked, on the second the update went through without problems.
What I've tried:
1) Updating from the app
2) Uninstalling PowerToys, deleting AppData\Local\Microsoft\PowerToys, reinstalling 0.87.1

Both of these options resulted in the application being completely blocked at startup.
It started working only after the **rollback to 0.82**

### ✔️ Expected Behavior

updating the app does not cause any breakage))

### ❌ Actual Behavior

after installing version 0.87.1, the application cannot be opened: clicking on the tray icon does not give any results. I tried to kill the process and restart it again - the same thing.
in the Event Viewer, I found:
```
Faulting application name: PowerToys.AdvancedPaste.exe, version: 0.87.1.0, time stamp: 0x67200000
Faulting module name: KERNELBASE.dll, version: 10.0.19041.2546, time stamp: 0xe8e9ac9b
Exception code: 0xc0000602
Fault offset: 0x000000000010fd12
Faulting process id: 0x3ff8
Faulting application start time: 0x01db55133e2c4609
Faulting application path: C:\Program Files\PowerToys\WinUI3Apps\PowerToys.AdvancedPaste.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
Report Id: 160064fa-c347-4ade-aa3f-71446e804bbf
Faulting package full name: 
Faulting package-relative application ID: 
```

Attached file contains result[PowerToysReport_2024-08-01-14-20-28.zip](https://github.com/user-attachments/files/18227891/PowerToysReport_2024-08-01-14-20-28.zip)
 of `Program Files\PowerToys\Tools>PowerToys.BugReportTool.exe /bugreport`

### Other Software

_No response_
Repository: react
Issue: Bug: forms don't behave correctly with Lit custom elements
Labels: Status: Unconfirmed

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 19.0.0

## Steps To Reproduce

1. Use Lit custom element inside a form (an input and a submit button)
2. Try to get the input value

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

- Custom element implementation: https://github.com/test-wc/test-wc/tree/feature/forms
- React usage: https://github.com/test-wc/react-wc/blob/features/forms/src/App.js

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior

Custom elements behave correctly in Angular, VanillaJS, Vue and React using `react-hook-forms` 

## The expected behavior

I'd like to see it working using the native form in React
Repository: next.js
Issue: notFound generates critical error with i18n
Labels: Navigation,Internationalization (i18n)

### Link to the code that reproduces this issue

https://github.com/GeorgeHulpoi/nextjs-not-found-bug

### To Reproduce

1. Go to `http://localhost:3000/de` and you will see the following errors in console:
![image](https://github.com/user-attachments/assets/e908966d-e927-40f9-b439-51528e771e49)


### Current vs. Expected behavior

When the `notFound` is called from `next/navigation`, seems to produce the error. Normally, it should show the default 404 page.
For example, navigating to `http://localhost:3000/en/test` render the default 404 (as expected).

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 14189
  Available CPU cores: 16
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.21
  pnpm: 9.15.0
Relevant Packages:
  next: 15.1.2 // Latest available version is detected (15.1.2).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: N/A
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Internationalization (i18n), Navigation

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local)

### Additional context

Related issues:
https://github.com/vercel/next.js/issues/59180
https://github.com/vercel/next.js/issues/55191

I followed the steps from https://nextjs.org/docs/app/building-your-application/routing/internationalization ;
Repository: PowerToys
Issue: Settings displayed in two different languages; inability to select app language
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Settings

### Steps to reproduce

1. Completely uninstalled previous version of Power Toys with Geek.exe.
2. Installed fresh version from Microsoft Store.
3. Ran Power Toys and went to Settings -> Dashboard.
4. In the Dashboard, some settings/descriptions are in English, others in German.

**Note**: I am using a refurbished PC, which, I believe, was originally sold in a German-speaking country. However, Windows 11 was installed in English.

### ✔️ Expected Behavior

To see all descriptions, commands, tool-tips etc. in English.

### ❌ Actual Behavior

Some text is displayed in English, other text is displayed in German.

![Image](https://github.com/user-attachments/assets/829a33df-db56-4129-b0ee-bf7e1eddb0c0)


### Other Software

_No response_
Repository: neovim
Issue: `:pedit` with `splitkeep=screen` changes cursor position
Labels: bug,needs:decision,bug-vim,needs:vim-patch,editor

### Problem

Cursor changed when `:pedit` a file with option `vim.o.splitkeep=screen`

### Steps to reproduce

1. nvim --clean
2. :set splitkeep=screen
3. :edit file_one.txt  
4. move the cursor to a position
5. :pedit file_two.txt  
6. the cursor position of file_one.txt has changed

### Expected behavior

the cursor position of file_one.txt might not be changed

### Nvim version (nvim -v)

NVIM v0.11.0-dev-1401+g7e1c1ff7fc

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

vim8.2 seems like not have option `splitkeep`

### Operating system/version

WSL

### Terminal name/version

wezterm

### $TERM environment variable

tmux-256color

### Installation

build from repo
Repository: rust
Issue: Tracking Issue for debuginfo testsuite test infra woes
Labels: A-debuginfo,T-compiler,T-bootstrap,T-infra,C-tracking-issue,A-compiletest,A-test-infra

This is a tracking issue for various problems and deficiencies related to the `debuginfo` test suite located at `tests/debuginfo`, mostly on the test-infra side (and not compiler bugs).

## Environment control

- https://github.com/rust-lang/rust/issues/126092
- https://github.com/rust-lang/rust/issues/133111
- https://github.com/rust-lang/rust/issues/123621

## Test coverage issues

- https://github.com/rust-lang/rust/issues/81813
- https://github.com/rust-lang/rust/issues/129139

## Build/bootstrap issues

- https://github.com/rust-lang/rust/issues/133692
- https://github.com/rust-lang/rust/issues/69869

## compiletest issues

- https://github.com/rust-lang/rust/issues/134469
- https://github.com/rust-lang/rust/issues/128981

## External issues

### LLDB

- https://github.com/llvm/llvm-project/issues/92603
- https://github.com/llvm/llvm-project/issues/87381

### GDB

- https://github.com/rust-lang/rust/issues/29658
- https://github.com/rust-lang/rust/issues/122751

### MSVC

- https://github.com/rust-lang/rust/issues/121837

## Unknown, needs investigation

These bugs may need investigation (is it our compiler bug, our test infra bug, external bug, or a combination of both?).

- https://github.com/rust-lang/rust/issues/128973
- https://github.com/rust-lang/rust/issues/128971 (gdb or our problem?)
- https://github.com/rust-lang/rust/issues/126060 (maybe in debuginfo we emit?)
- https://github.com/rust-lang/rust/issues/77744
- https://github.com/rust-lang/rust/issues/74884 (endianness problem somewhere?)
- https://github.com/rust-lang/rust/issues/74847 (`arm-android`, good luck trying to repro this locally)

## Possible test infra cleanups/improvements

- https://github.com/rust-lang/rust/issues/134673
- https://github.com/rust-lang/rust/issues/133121
- https://github.com/rust-lang/rust/issues/134684
Repository: rust
Issue: `tests/debuginfo/numeric-types.rs` test coverage became 64-bit only
Labels: A-testsuite,A-debuginfo,T-compiler,C-bug

> Marking `numeric-types.rs` as 64-bit only for now to unblock the tree (in #133115), follow-up investigations should try to see if that can be made to work with `i686-msvc` (64-bit isize vs 32-bit isize and thus different underlying int type display). 

 _Originally posted by @jieyouxu in [#133107](https://github.com/rust-lang/rust/issues/133107#issuecomment-2480792451)_
Repository: tauri
Issue: SyntaxError: Unexpected private name #ensureObj. Cannot parse class method with private name.
Labels: type: bug,platform: macOS,status: needs triage

<img width="797" alt="Screenshot 2024-12-23 at 5 17 22 PM" src="https://github.com/user-attachments/assets/e670958d-a4da-40e2-a818-1375fe37a07b" />

[✔] Environment
    - OS: Mac OS 11.7.10 x86_64 (X64)
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.83.0 (90b35a623 2024-11-26)
    ✔ cargo: 1.83.0 (5ffbef321 2024-10-29)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-x86_64-apple-darwin (default)
    - node: 20.17.0
    - npm: 10.8.2

[-] Packages
    - tauri 🦀: 2.1.1
    - tauri-build 🦀: 2.0.3
    - wry 🦀: 0.47.2
    - tao 🦀: 0.30.8
    - tauri-cli 🦀: 2.1.0
    - @tauri-apps/api : 2.1.1
    - @tauri-apps/cli : 2.1.0

[-] Plugins
    - tauri-plugin-log 🦀: 2.2.0
    - @tauri-apps/plugin-log : not installed!

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../build
    - devUrl: http://localhost:3000/
    - framework: React
Repository: rust
Issue: Share debuginfo testsuite breakpoint setup logic
Labels: A-testsuite,A-debuginfo,E-hard,C-enhancement,T-compiler,T-bootstrap,A-compiletest,E-needs-design

> To follow up: I think the way we are setting breakpoints in our tests is pretty consistent and would probably be compatible with the approach of setting the breakpoint by function name and then looking one frame up. It would be good if that function was defined in a central place (so we don't have to copy-and-paste it into every test file) and then we'd have to update the test runner and documentation.   

 _Originally posted by @michaelwoerister in [#71437](https://github.com/rust-lang/rust/issues/71437#issuecomment-1286742097)_
Repository: terminal
Issue: Ingest latest CascadiaCode so that users don't have to uninstall previous version
Labels: Area-UserInterface,Product-Terminal,Issue-Task,Needs-Tag-Fix

https://github.com/microsoft/cascadia-code#installation

> Note: If you have previously installed a version of Cascadia Code, please uninstall the previous version prior to installing a new version. Not doing so can result in improper rendering.

![Image](https://github.com/user-attachments/assets/cfbed066-e565-44aa-84f8-21647171bc91)
Repository: PowerToys
Issue: Error on close Windows Mixed Reality
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

v0.87.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

Start Windows Mixed Reality while PowerToys is running
Exit Windows Mixed Reality. Observe below error.

Note: error does not seem to stop PowerToys from operating.
Note: it doesn't seem to do it again after the first time this errors (I can re-open and re-close Mixed Reality Portal without the error)

### ✔️ Expected Behavior

No error

### ❌ Actual Behavior


Version: 0.87.1.0
OS Version: Microsoft Windows NT 10.0.22631.0
IntPtr Length: 8
x64: True
Date: 23/12/2024 12:46:41
Exception:
System.Runtime.InteropServices.COMException (0xD0000701): 0xD0000701
   at Standard.NativeMethods.DwmExtendFrameIntoClientArea(IntPtr hwnd, MARGINS& pMarInset)
   at System.Windows.Appearance.WindowBackdropManager.UpdateGlassFrame(IntPtr hwnd, WindowBackdropType backdropType)
   at System.Windows.Appearance.WindowBackdropManager.ApplyBackdrop(IntPtr hwnd, WindowBackdropType backdropType)
   at System.Windows.Appearance.WindowBackdropManager.SetBackdrop(Window window, WindowBackdropType backdropType)
   at System.Windows.ThemeManager.ApplyStyleOnWindow(Window window, Boolean useLightColors)
   at System.Windows.ThemeManager.ApplyFluentOnWindow(Window window)
   at System.Windows.ThemeManager.OnSystemThemeChanged()
   at System.Windows.SystemResources.SystemThemeFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)



### Other Software

Mixed Reality Portal v2000.21051.1282.0