sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: search.action.focusFilesToExclude and Include not working
Labels: bug,search-editor

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.95.3
- OS Version: linux mint mate 21.3

Version: 1.95.3
Commit: https://github.com/microsoft/vscode/commit/f1a4fb101478ce6ec82fe9627c43efbf9e98c813
Date: 2024-11-13T14:50:04.152Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Linux x64 5.15.0-126-generic

__Issue__
search.action.focusFilesToExclude and search.action.focusFilesToInclude  not working 
( the relevant inputboxes are not getting highlighted )
checked by key binding these action items 

__Steps to Reproduce:__

1. Assign keybindings alt + I and alt + O to search.action.focusFilesToInclude and search.action.focusFilesToExclude
2. set when expression for both as 'searchInputBoxFocus || searchViewletFocus'
3. now in search side bar pane focused, either focus in inputbox or the result area, trigger the newly set keybindings to focus the include or exclude input boxes. 
We see no transfer of focus to these input boxes.

When checked with developer: keyboard shortcuts troubleshooting
the keybindings do get triggered, but relevant action is not executed.


__Additionally,__
only action item is present to focus these 2 include & exclude boxes
there is __NO when clause__ items to check while triggering keybindings
focusFilesToInclude & focusFilesToExclude
Repository: PowerToys
Issue: Video Cut/Trim
Labels: Needs-Triage

### Description of the new feature / enhancement

I got no idea why this isn't already a default windows feature, to simply cut/trim videos. And when I tried using some applications, they either put a watermark over my video, significantly lowered the quality, or are a general nuisance that requires 5 steps to use and requires waiting for minutes. There is no way that cutting/trimming a video is that software heavy, since my phone can do it in a couple of seconds and with longer videos. This would be extremely helpful, thanks!

### Scenario when this would be used?

Simple video trimming, I use AMD replay record, that automatically records last 1 and a half minutes of my screen and audio and upon pressing a shortcut I am able to save a video of the last minute and a half, of course more often then not I do not need that much time, but I don't want to lower it in case I do need it and lose the funny moment forever. I actually end up sending the videos to my phone via discord or mail (if they are too large) just to trim them, and send them back. This way I could do that in a matter of seconds.

### Supporting information

I feel that I explained the scene enough, as for other people I heard my friends complain about it.
Repository: go
Issue: x/tools/gopls: feature: "move declaration" refactoring
Labels: FeatureRequest,gopls,Tools,Refactoring

A generalization of renaming a symbol X to Y is to rename X to otherpkg.Y, causing the declaration of X, along with any necessary supporting declarations, to be moved into some file in the designated other package. There are a fair number of edge cases to consider, and UI questions such as how best to obtain the name of otherpkg: the only current LSP operation that supports dialog is Rename, which rather forces our hand. (Another possibility is to use the web interface, which could give a rich interactive menu of which declarations should be moved and optionally renamed at the same time.)
Repository: rust
Issue: Tracking Issue for `slice_as_array`
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(slice_as_array)]`

This is a tracking issue for adding conversion functions from slices to arrays.

### Public API

```rust
impl<T> [T] {
    pub const fn as_array<const N: usize>(&self) -> Option<&[T; N]>;

    pub const fn as_mut_array<const N: usize>(&mut self) -> Option<&mut [T; N]>;
}

impl<T> *const [T] {
    pub const fn as_array<const N: usize>(self) -> Option<*const [T; N]>;
}

impl<T> *mut [T] {
    pub const fn as_mut_array<const N: usize>(self) -> Option<*mut [T; N]>;
}

// alloc::boxed

impl<T> Box<[T]> {
    pub fn into_array<const N: usize>(self) -> Option<Box<[T; N]>>;
}

// alloc::rc

impl<T> Rc<[T]> {
    pub fn into_array<const N: usize>(self) -> Option<Rc<[T; N]>>;
}

// alloc::sync

impl<T> Arc<[T]> {
    pub fn into_array<const N: usize>(self) -> Option<Arc<[T; N]>>;
}
```

### Steps / History

- [x] API change proposal (ACP): [#496](https://github.com/rust-lang/libs-team/issues/496/)
- [x] Implementation for `[T]`, `*const [T]`, and `*mut [T]`: #133512
- [x] Fix docs for `<[T]>::as_array`: #133743
- [x] Implementation for `Box<[T]>`, `Rc<[T]>`, and `Arc<[T]>`: #134379
- [ ] Final comment period (FCP)
- [ ] Stabilization PR

### Unresolved Questions

- `const`-compatible for the non-primitive types?
- `Option` or `Result` for the owning conversions?
- Implementation for `Mutex` and `RwLock`?
Repository: electron
Issue: Bugs filed against nightlies get `blocked/need-info ❌` label
Labels: bug :beetle:,status/confirmed

### 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

33.2.0

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

macOS

### Operating System Version

macOS Sequioa 15.1.1

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

_No response_

### Expected Behavior

A bug filed against the current Electron nightly version does not get tagged with [blocked/need-info ❌](https://github.com/electron/electron/labels/blocked%2Fneed-info%20%E2%9D%8C).

In the best possible case, it would get tagged with whatever the tag for the version is.

### Actual Behavior

The Electron issue triage bot assigns the [blocked/need-info ❌](https://github.com/electron/electron/labels/blocked%2Fneed-info%20%E2%9D%8C) label.

See #44849 as an example.

### Testcase Gist URL

_No response_

### Additional Information

_No response_
Repository: storybook
Issue: [Bug]: Vue code snippets incorrect after 8.3
Labels: bug,vue3,upgrade:8.3

### Describe the bug

After updating to anything past 8.3, most of our autodoc code snippets are incorrect and can no longer be copied/pasted.  

Here is a very simple example:

Prior to 8.3
![Image](https://github.com/user-attachments/assets/62a3ffe9-2a34-4141-8323-70b75ee77d33)

After 8.3
![Image](https://github.com/user-attachments/assets/0a8333e7-cb8b-4971-adfa-cab59a1d5a1b)

The issue is that for some of our stories, we are simply passing Vuetify components into the story and documenting how we want them used internally rather that exporting our own components.  For some reason, the code snippets are replacing the code we wrote and rewriting it using a component that doesn't actually exist (in this case `v-btn` changes to `Button`).

I suspect this comes from the Vue code snippet improvements done in this [PR](https://github.com/storybookjs/storybook/pull/27194), but I haven't been able to figure out a way to get around it without simply downgrading to 8.2.9.

If there is a config or some other option that I'm missing, I'd love to hear it.  


### Reproduction link

https://stackblitz.com/edit/github-d6xn5f?file=.storybook%2Fmain.ts

### Reproduction steps

1. In the Preview pane, open the Show Code panel
2. You'll see that the code shows `Button` instead of `v-btn`

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.6.1
    CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.12.1 - ~/.nvm/versions/node/v20.12.1/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.9.1 - ~/source/shared-components/node_modules/.bin/npm <----- active
    pnpm: 9.9.0 - ~/.nvm/versions/node/v20.12.1/bin/pnpm
  Browsers:
    Chrome: 131.0.6778.86
    Safari: 18.1
  npmPackages:
    @storybook/addon-a11y: ^8.4.5 => 8.4.5 
    @storybook/addon-designs: ^8.0.4 => 8.0.4 
    @storybook/addon-essentials: ^8.4.5 => 8.4.5 
    @storybook/addon-interactions: ^8.4.5 => 8.4.5 
    @storybook/addon-links: ^8.4.5 => 8.4.5 
    @storybook/addon-themes: ^8.4.5 => 8.4.5 
    @storybook/addon-viewport: ^8.4.5 => 8.4.5 
    @storybook/blocks: ^8.4.5 => 8.4.5 
    @storybook/test: ^8.4.5 => 8.4.5 
    @storybook/vue3: ^8.4.5 => 8.4.5 
    @storybook/vue3-vite: ^8.4.5 => 8.4.5 
    chromatic: ^11.18.1 => 11.18.1 
    eslint-plugin-storybook: ^0.11.1 => 0.11.1 
    storybook: ^8.4.5 => 8.4.5
```

### Additional context

_No response_
Repository: vscode
Issue: Command copied from fish shell gets line wrap
Labels: bug,terminal-shell-fish

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.95.3
- OS Version: Arch Linux, GNOME 47

Steps to Reproduce:

1. Prepare a very long command in terminal.
2. Select the command, Copy, and Paste into a file.

![Image](https://github.com/user-attachments/assets/0c9063c5-c202-4fce-b713-5408c1faac1f)
Repository: ollama
Issue: Support for Nvidia Hymba
Labels: model request

It would be great to support Hymba in Ollama! 

https://developer.nvidia.com/blog/hymba-hybrid-head-architecture-boosts-small-language-model-performance/
Repository: storybook
Issue: [Bug]: Running Storybook with vite v6.0.0
Labels: bug,dependencies,builder-vite

### Describe the bug

Hi,
I tried running `npx storybook@latest init` after `npm create vite@latest` (using react + typescript) . I got the following from storybook.log:

npm error code ERESOLVE
npm error ERESOLVE unable to resolve dependency tree
npm error
npm error While resolving: storybook-vitev6@0.0.0
npm error Found: vite@6.0.0
npm error node_modules/vite
npm error   dev vite@"^6.0.0" from the root project
npm error
npm error Could not resolve dependency:
npm error peer vite@"^4.0.0 || ^5.0.0" from @storybook/react-vite@8.4.5
npm error node_modules/@storybook/react-vite
npm error   dev @storybook/react-vite@"^8.4.5" from the root project
npm error
npm error Fix the upstream dependency conflict, or retry
npm error this command with --force or --legacy-peer-deps
npm error to accept an incorrect (and potentially broken) dependency resolution.
npm error
npm error
npm error For a full report see:
npm error /Users/omarihab/.npm/_logs/2024-11-26T20_17_48_529Z-eresolve-report.txt
npm error A complete log of this run can be found in: /Users/omarihab/.npm/_logs/2024-11-26T20_17_48_529Z-debug-0.log


### Reproduction link

https://github.com/omarihab99/storybook-vitev6

### Reproduction steps

- `npm create vite@latest`. using react + ts template.
- `npm install`
- `npx storybook@latest init`

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 15.1
    CPU: (8) arm64 Apple M1
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 18.20.2 - ~/.nvm/versions/node/v18.20.2/bin/node
    Yarn: 1.22.22 - ~/.nvm/versions/node/v18.20.2/bin/yarn
    npm: 10.8.2 - ~/.nvm/versions/node/v18.20.2/bin/npm <----- active
  Browsers:
    Chrome: 131.0.6778.86
    Safari: 18.1
```

### Additional context

_No response_
Repository: rust
Issue: DefaultMetadataLoader was changed to private, making it difficult to print out metadata
Labels: T-compiler,C-feature-request

Hi,

A recent commit [bdacdfe](https://github.com/rust-lang/rust/commit/bdacdfe95f17188f5b047e0330e3e47f993a2016#diff-6bbf6edd930f26d3b180eb5c250b0e48d8f3c5eb474e3274909ef6ae6f0d1e61) made the `DefaultMetadataLoader` struct private to the crate.
This makes it impossible to print out the crate metadata using the given functions unless I define my own struct which implements the `MetadataLoader` trait. I'm currently just trying to understand the metadata file better, and am working with an older version of the Rust compiler so that I can access this type. I'm wondering why this type was made private.

Here is the code I'm using which works with an older version of the compiler:

```
fn main() {
    let path = std::env::args().nth(1).expect("no path given");
    let path = Path::new(&path);
    let triple = TargetTriple::from_triple("x86_64-apple-darwin");
    let target = Target::expect_builtin(&triple);
    let mut stdout = io::stdout();

    rustc_span::create_session_globals_then(Edition::Edition2018, || {
        let _ = locator::list_file_metadata(&target, path, &DefaultMetadataLoader, &mut stdout);
    });
}
```
Repository: svelte
Issue: a11y: Non-interactive element `<label>` cannot have interactive role 'tab'
Labels: a11y

### Describe the bug

this is a false positive as 
- label elements are interactive content https://html.spec.whatwg.org/multipage/dom.html#interactive-content
- it's the only way to do things progressively 

### Reproduction

```svelte
<label role="tab">
    tab <input type="checkbox" />
</label>
```

### Logs

_No response_

### System Info

```shell
none
```


### Severity

annoyance
Repository: react
Issue: [Compiler Bug]: False positive `Ref values (the `current` property) may not be accessed during render` for non-jsx code
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [ ] 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)
- [ ] 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/#N4Igzg9grgTgxgUxALhAHRFMCAEcA2AlggHYAuGA3GiTYQLYAOEMZOwOAVmAB44C+OAGYwI9HBhgIAhnDIB6bjwC0MKOQYIqdJizYcsCAEoIhA4aPGSZc7STgQSYNgGEI+fNMbYcAXhwAFMA0OHgAFoT4ACZStCT8AJR+AHzsIXiOzhnk0oQkCDAmZv6GRQEkUB4J1CShUmSwtfIAVDgAAgD6HQAKAKpGAKJdOM2KvAEYUYQAbhgANGm1oThSQsjZZLn5haZz6aFwEdGx6Yk1-DUIPMys7DhuHl4+FyD8QA

### Repro steps



following code gives false positive error

```js
const Collapse = ({
  children
}) => {
  const containerRef = useRef(null);
  return /* @__PURE__ */jsx("div", {
    ref: containerRef,
    children
  });
};
```

but not

```ts
export const Collapse: FC<{
  children: ReactNode
}> = ({ children }) => {
  const containerRef = useRef<HTMLDivElement>(null!)

  return <div ref={containerRef}>{children}</div>
}
```

### How often does this bug happen?

Every time

### What version of React are you using?

from playground

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

from playground
Repository: flutter
Issue: [DisplayList] DisplayListBuilder does not compute correct effective color for DlColorSource objects
Labels: engine,P2,team-engine,triaged-engine

(Discovered while deleting unused DlColorColorSource)

When a ColorSource is applied to a paint, it is modulated by the alpha of the color property. The code in DisplayListBuilder that computes an example color to determine if an operation is a NOP does not take this modulation into account:

https://github.com/flutter/engine/blob/9975c85013db35dd311ac27b09c932157ec881ea/display_list/dl_builder.cc#L1959
Repository: vscode
Issue: VSCode will silently never auto-update if it is not explicitly moved from the "Downloads" directory to "Application"
Labels: bug,install-update,macos

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

Related issue: https://github.com/microsoft/pylance-release/issues/6710#issuecomment-2501907909

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.89 -> 1.95
- OS Version: MacOS 14.5

Steps to Reproduce:

1. Install vscode, but forget to move it from "Downloads" to "Applications"
2. Vscode will never update automatically, making it fall behind over time.
3. Try to update manually will run into an error (see below)
4. Eventually, extensions installed on remote ssh server (which uses the same version as your local) will start subtly failing, sometimes it simply fails to boot. For example: https://github.com/microsoft/pylance-release/issues/6710

The current error message:

> Cannot update while running on a read-only volume. The application is on a read-only volume. Please move the application and try again. If you're on macOS Sierra or later, you'll need to move the application out of the Downloads directory. This might mean the application was put on quarantine by macOS. See [this link](https://github.com/microsoft/vscode/issues/7426#issuecomment-425093469) for more information.

What needs to be done, specifically, is to move from Downloads to the "Application".

# Suggestion

It would be good to update the error message to explicitly say:

> *Move the file "Visual Studio Code" from "Downloads" to "Applications"*

The link could be updated to a more relevant link, which explains how to "unquarantine" VSCode: https://stackoverflow.com/a/65422671/13837091

That error message could appear as a popup if the extension tries to automatically update but fails. Right now, the popup only appears AFTER you try to manually update with `Code: Check for updates...`.
Repository: PowerToys
Issue: Switch display apps
Labels: Needs-Triage

### Switch Apps in displays

Suppose that i have:
Applications A, B and C currently in my display number 2;
Applications X, and Y currently in my display number 1 (main);

My displays keeps on side by side, number 1 in front of me, and number 2 in its left.

For some reason, i want to give a focus on applications A, B and/or C, that are under display 2, this, in about 1h or so, would give some kind of neck pain, so knowing that, i would like to switch apps:

Applications A, B and C now are in my display 1;
Applications X and Y now are in my display 2

### Scenario when this would be used?

Suppose that i'm working remotely (RDP) in a machine in my secondary display using fullscreen mode. This would cause me too look a little bit to the left for some hours, this can be annoying, specially to my neck.
So, i would like to switch apps between displays, automatically, without need to switch apps one bye one.
This would cause, in this scenario that my RDP is now in front of me, giving me more comfort to my head, neck and eyes.

As soon as I decide to unfocus the app, i could switch back apps to their original state.

### Supporting information

_No response_
Repository: TypeScript
Issue: Some Playwright types now reported as `any` after upgrading to 5.7.2
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

I manually scrolled through all issues reported since the release of 5.7.2.

### 🕗 Version & Regression Information

- This changed between versions 5.6.3 and 5.7.2

### ⏯ Playground Link

https://github.com/mrmckeb/pw-repro

### 💻 Code

Minimal repro available here:
https://github.com/mrmckeb/pw-repro

The Playwright team are also able to reproduce:
https://github.com/microsoft/playwright/issues/33763

The affected code (from the repro) is:
```ts
import { test as base, expect } from "@playwright/test";

const test = base.extend({
  // baseUrl, page, use are now `any`
  page: async ({ baseURL, page }, use) => {
    await page.goto(baseURL);
    await use(page);
  },
});
```

### 🙁 Actual behavior

Types that were previously available are now typed as `any`. JSDoc continues to work as expected.

### 🙂 Expected behavior

Types behave as they did in TypeScript 5.6.3.

### Additional information about the issue

We found this issue when upgrading from 5.6.3 to 5.7.2. I couldn't find a related issue here, so raised it at the Playwright repo to at least verify that they could reproduce and that they didn't think it was an issue with their types.

The Playwright team also confirmed that they have 71 new errors across 41 files when moving to TypeScript 5.7.2.