sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: TypeScript
Issue: Object destructuring causes deprecated status to get lost
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

object destructing deprecated status lost @deprecated

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries

I don't think this is a regression, I haven't seen it work in the past.


### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/FAFwngDgpgBAylEBXCAlKBnJAbEMC8MA3sDGTAPQBUVMAAgCZQQBOUAxgIYhQMxUVS5ALYB7JADsQALhgAKAJQEAfDABuogJYNgAX2DBqtRszZcefJBlgZRwxAAtNEgOYwo2a-0EAzSexBNUQkYa2QIRVkEcPQsXGIhMjZkFhCiMUkZeSV8VSJdfX1gdmCMPDY4vEIwlEUAbmAKnBAAOgypRUMKch6APRgmVg5uXhhODHcAD2gA3gBCAxKJMuIYdrxdAlDEWoUG9c6Kbv6GUUwJAHI8F0Q1zhYAa1HxgdNhiyA

### 💻 Code

```ts

type SetupResult = {
    /** @deprecated */
    mount: () => void
}

/** @deprecated use something else */
function setup(): SetupResult {
    return {mount: () => {}}
}

const result = setup();
result.mount()
//       ^ deprecated as expected!

const { mount } = setup();
mount()
// ^ doesn't get marked as deprecated
```


### 🙁 Actual behavior

The destructered `mount` property doesn't show up as deprecated when called.

### 🙂 Expected behavior

The destructered `mount` function should show up as deprecated when called.

### Additional information about the issue

_No response_
Repository: vscode
Issue: Unable to scroll text in hover dialogs
Labels: bug,confirmation-pending,workbench-hover

<!-- ⚠️⚠️ 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
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: v1.90.1 (user setup)
- OS Version: Windows 11 Enterprise

Steps to Reproduce:

1. Position the mouse over any integrated terminal tab
2. Wait for hover to appear:

![pwshext_vscode_s](https://github.com/microsoft/vscode/assets/134162878/a90cc43d-ccbb-43eb-8535-f9043d487d42)

It's not completely apparent from the screen recording above, but I attempt to use the arrow keys, mouse scroll wheel and page down function to scroll to the bottom of the dialog -- all to no avail.  Finally, I select the dialog by holding down the <kbd>ALT</kbd> key and clicking on it.  

By subsequently pressing the <kbd>TAB</kbd> key, I am able to bring the <kbd>Show environment contributions</kbd> button (previously out of bounds / clipped) into focus. Note that this behavior causes not only the aforementioned button to be obscured out of view, but also every other selectable menu option that typically appears in these hovers, including "Relaunch terminal" and the others.
Repository: PowerToys
Issue: PowerToys Run can't be activated
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.81.1

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

1. Open PowerToys
2. On the left side, click on PowerToys Run
3. Press the buttons to activate PowerToys Run (default is Alt + Space)

### ✔️ Expected Behavior

PowerToys Run launcher is shown

### ❌ Actual Behavior

No launcher pops up. I've tried with various settings, changing the default activation shortcut to Alt + R, checking the "Centralized keyboard hook" box, but nothing will trigger it. I've even tried it from the Quick Access menu, but it still doesn't run. I've also tried clicking on "Welcome to PowerToys" > "PowerToys Run" > Launch PowerToys Run, but it still doesn't trigger it.

If any, on my personal computer, it works. However, it doesn't work on my Lenovo laptop (ThinkPad T14 Gen 3).

I've attached a bug report to see if it helps with the troubleshooting?
[PowerToysReport_2024-06-18-00-36-40.zip](https://github.com/user-attachments/files/15874514/PowerToysReport_2024-06-18-00-36-40.zip)

### Other Software

_No response_
Repository: stable-diffusion-webui
Issue:  installation error  line 48,39, 386
Labels: bug-report

### Checklist

- [ ] 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
- [ ] The issue has not been reported before recently
- [ ] The issue has been reported before but has not been fixed yet

### What happened?

some of the files are apparently damaged.

### Steps to reproduce the problem

I did the installation step via https://rentry.org/voldy

### What should have happened?

web initialization 

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

_No response_

### Sysinfo

error

### Console logs

```Shell
venv "C:\Users\Adm\Desktop\stable-diffusion-webui\venv\Scripts\Python.exe"
Python 3.10.6 (main, Dec 22 2022, 15:39:53) [MSC v.1934 64 bit (AMD64)]
Version: v1.9.4
Commit hash: feee37d75f1b168768014e4634dcb156ee649c05
Traceback (most recent call last):
  File "C:\Users\Adm\Desktop\stable-diffusion-webui\launch.py", line 48, in <mod
ule>
    main()
  File "C:\Users\Adm\Desktop\stable-diffusion-webui\launch.py", line 39, in main

    prepare_environment()
  File "C:\Users\Adm\Desktop\stable-diffusion-webui\modules\launch_utils.py", li
ne 386, in prepare_environment
    raise RuntimeError(
RuntimeError: Torch is not able to use GPU; add --skip-torch-cuda-test to COMMAN
DLINE_ARGS variable to disable this check
Pressione qualquer tecla para continuar. . .
```


### Additional information

my setup is basic.
win 8.1 pro
intel grafic
Repository: TypeScript
Issue: Typescript ignores package.json export maps
Labels: Needs More Info

<!-- ⚠️⚠️ 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.90.1
- OS Version: macos 14.5

Steps to Reproduce:

1. `mkdir meth && cd meth && npm init -y && npm i micro-eth-signer && touch a.mjs`
2. Open a.mjs and enter `import * as net from 'micro-eth-signer/net';` or any other module. VSCode would not see the module even though [it's clearly specified in pkg.json](https://github.com/paulmillr/micro-eth-signer/blob/956b88dcf4c305b2f7314acc358981d6c7e2bf81/package.json#L40-L43)
3. Doesn't matter which tsconfig is used, i've tried all options (moduleResolution, module, whatever)

I maintain many libraries and I export their functionality in sub-modules instead of importing everything into one big `index.js` file. This is useful and helps with tree-shaking. Seems like vscode doesn't support export maps in node.js.
Repository: flutter
Issue: Add support for "Squeeze" gesture for Apple Pencil Pro
Labels: c: new feature,framework,engine,f: gestures,P3,team-ios,triaged-ios

The Apple Pencil Pro released this year (May 15, 2024) now has support for a brand new gesture, Squeeze.
From preliminary inspection it looks like it could be implemented the same way Double-Tap was attempted to be added to flutter. 
https://github.com/flutter/engine/pull/39267/files

Documentation: 
https://developer.apple.com/documentation/applepencil/handling-squeezes-from-apple-pencil
https://developer.apple.com/documentation/SwiftUI/View/onPencilSqueeze(perform:)
Repository: TypeScript
Issue: TypeScript refactoring: option to use `export default` with "Move to a new file"
Labels: Suggestion,Awaiting More Feedback

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Among other reasons, I'd like to [avoid barrel files](https://vitejs.dev/guide/performance#avoid-barrel-files) and I find that default exports make doing so more intuitive (named exports are easily spread into a barrel file while default exports not so much).

[Some files like default exports and some folks do not](https://github.com/sindresorhus/meta/discussions/6). I get that.

Unless there's a need to do so, I'd like VSCode to make it just as easy to use default exports as named exports. Today, [TypeScript refactoring with Visual Studio Code](https://code.visualstudio.com/docs/typescript/typescript-refactoring) favors named exports. This default behavior may provide some encouragement/bias to use them and not use default exports as much.

There is also a "Convert between default export and named export" refactoring which is handy but requires another step and an aware/intentional decision to use default exports.

Can "Move to a new file" be split into two options or otherwise support prompting developers to explicitly select which type of export to use while they are refactoring?

e.g.
1. "Move to a new file as default export"
1. "Move to a new file as named export"
Repository: vscode
Issue: "Cannot set property activeDebugSession of #<Object> which has only a getter" when trying to change active debug session
Labels: feature-request,debug

`vs.debug.activeDebugSession` is marked as mutable in the definition:

https://github.com/microsoft/vscode/blob/be0e53510d8128ee4d17205fcb9511963a5bbb43/src/vscode-dts/vscode.d.ts#L16259

But trying to set it results in the following runtime exception:

```
Exception has occurred: TypeError: Cannot set property activeDebugSession of #<Object> which has only a getter
t VsCodeApiImpl.<anonymous> (c:\Dev\Dart-Code\Dart-Code\out\dist\extension.js:6563:45)
	at Generator.next (<anonymous>)
```

I'm trying to improve the UI for launching some additional tooling and it allows the user to select a debug session to launch the tool far. To improve the experience, I'd like to allow the user to  use a "selected" debug session but I don't want a different selection to VS Code - I'd like to sync changes made in either place into a single selected debug session.

I also looked for a command, but I only found `workbench.action.debug.selectDebugSession` which seems to just show a pick-list and not allow us to provide a session explicitly.
Repository: vscode
Issue: caching code actions on save based on loaded extensions
Labels: feature-request,editor-code-actions

One other thing to be aware of is that this intellisense will only pick up code actions for active languages. This at least ensures that only valid source actions are shown, but could also confuse users if they try configuring the setting without activating the language extension first (that's what the static contribution was trying to solve)

You could potentially solve this by caching the source actions for each extension across restarts. May be worth tracking in a new issue

_Originally posted by @mjbvz in https://github.com/microsoft/vscode/pull/215475#pullrequestreview-2123701935_
Repository: storybook
Issue: [Bug]: Setting theme for DocsContainer dynamically breaks styles
Labels: bug,help wanted,addon: docs,sev:S3

### Describe the bug

When you manually set the theme passed to DocsContainer and it changes after page load, the margin can suddenly change 

It seems there's some styles that work based on what the theme "was" when the page loads, which breaks if you change the theme passed to DocsContainer.

https://github.com/storybookjs/storybook/assets/719814/81e3e658-aedb-4bd2-aa2d-a0df0371a30d



### Reproduction link

https://stackblitz.com/edit/vitejs-vite-yow74x

### Reproduction steps

1. Cancel the vite process
2. Run `npm run storybook`
3. Open the test story (in a new tab, not within the stackblitz UI)
4. Change the theme from light to dark (using the toolbar theme switcher)
5. You'll see the left margin incorrectly change on header
6. Refresh, and the theme should stay dark but with the correct left margin
7. Change from dark to light (using the toolbar theme switcher)
8. You'll see the left margin incorrectly change on header

### System

```bash
Storybook Environment Info:

  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.1.10 => 8.1.10 
    @storybook/addon-interactions: ^8.1.10 => 8.1.10 
    @storybook/addon-links: ^8.1.10 => 8.1.10 
    @storybook/addon-onboarding: ^8.1.10 => 8.1.10 
    @storybook/addon-themes: ^8.1.10 => 8.1.10 
    @storybook/blocks: ^8.1.10 => 8.1.10 
    @storybook/react: ^8.1.10 => 8.1.10 
    @storybook/react-vite: ^8.1.10 => 8.1.10 
    @storybook/test: ^8.1.10 => 8.1.10 
    storybook: ^8.1.10 => 8.1.10
```


### Additional context

I'm using what appears to be a private API to access the theme set by the toolbar theme switcher, but I think this is irrelevant to the bug – the bug is caused by the theme object being passed to DocsContainer changing.
Repository: TypeScript
Issue: Semantic Tokens for TypeScript Template Literal Strings
Labels: Help Wanted,Possible Improvement

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

(moved from typescript-language-server/typescript-language-server#901)

## Problem

In VS Code, semantic token theme colors override textmate token colors (even when they are user defined).  This usually makes sense, as the semantic tokens are intended to provide **more specific** information about tokens than what is available from syntax alone.

However, based on the output of VS Code's `Developer: Inspect Editor Tokens and Scopes` command, it appears that `typescript-language-server` labels all template strings with the generic `string` scope.  As a result, template strings will not receive syntax highlighting when semantic tokens are enabled, **degrading the user experience writing TypeScript** when semantic highlighting is enabled.

As you can see from the image below, the `textmate` grammar knows that `animal` is a variable inside of a template string, but the semantic token `string` is taking precedence.

![help](https://github.com/microsoft/vscode/assets/221963/9cbda12d-2140-43c2-8cee-b2d9c590c6b5)

## Possible Solutions

* The best would be to add more granular semantic tokens for template literal strings.
* Another possible solution would to allow more fine-grained control over the interaction between semantic highlighting and textmate highlighting.  At the moment, semantic highlights always get priority. 

## Related Issues

* typescript-language-server/typescript-language-server#901
* microsoft/vscode#97063
Repository: rust
Issue: rustc hangs / infinite loop on small example with generic_const_exprs and specialization
Labels: P-low,C-bug,I-hang,A-const-generics,F-generic_const_exprs

This code hangs on nightly

```
#![feature(specialization)]
#![feature(generic_const_exprs)]

use std::mem;
use std::marker::PhantomData;

trait Repr1 {
  type Elem;
}

struct TypeWithSize<T, const TSize: usize>(PhantomData<T>);

impl<T> Repr1 for TypeWithSize<T, 1> {
  type Elem = u8;
}

impl<T: Sized> Repr1 for T
where
  TypeWithSize<T, { mem::size_of::<T>() }>: Repr1,
{
  type Elem = <TypeWithSize<T, { mem::size_of::<T>() }> as Repr1>::Elem;
}
```

https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=8e9e36d48923272ac7366e521d379170

It works fine if there is a Repr2 to apparently break the cycle

```
#![feature(specialization)]
#![feature(generic_const_exprs)]
use std::mem;
use std::marker::PhantomData;
trait Repr1 {
  type Elem;
}

struct TypeWithSize<T, const TSize: usize>(PhantomData<T>);

impl<T> Repr1 for TypeWithSize<T, 1> {
  type Elem = u8;
}

trait Repr2 {
  type Elem;
}

impl<T: Sized> Repr2 for T
where
  TypeWithSize<T, { mem::size_of::<T>() }>: Repr1,
{
  type Elem = <TypeWithSize<T, { mem::size_of::<T>() }> as Repr1>::Elem;
}
```

https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=753784ec4df8b6cca783f3d7bbd935b7
Repository: flutter
Issue: [camera_android_camerax] Allow concurrent preview, video capture, and image streaming/capture for all devices
Labels: platform-android,p: camera,package,P2,team-android,triaged-android

In older versions of CameraX, concurrent displaying of the preview and video capture in conjunction with  image streaming and/or image capture had limited availability based on the camera level of the devices (at the time of writing, this can be seen in https://developer.android.com/media/camera/camerax/architecture#combine-use-cases). Because of this, `camera_android_camerax` introduced logic to avoid use of unsupported concurrent use cases (see https://github.com/flutter/flutter/issues/144414). However in recent changes to the CameraX library, a shared stream feature was introduced to allow these concurrent use cases despite device capabilities.

Thus, we should test removing the logic blocking the use of certain camera use case combinations based on device capabilities and remove it if possible to allow wider access to these concurrent camera usages.

See the release notes for more info on the shared stream feature:
- https://developer.android.com/jetpack/androidx/releases/camera#1.3.0-alpha04
- https://developer.android.com/jetpack/androidx/releases/camera#1.3.0-alpha05
- https://developer.android.com/jetpack/androidx/releases/camera#1.3.0-rc01

We currently use version 1.3.4 in the plugin, so this would not require a bump to the CameraX version that the plugin depends on.

FYI this is splitting off from https://github.com/flutter/flutter/issues/149947, which has some more context.
Repository: TypeScript
Issue: Feature Request: Display JSDoc Array of Objects as Array
Labels: Suggestion,Awaiting More Feedback

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

Hey guys,

I tried searching for a similar issue, but couldn't find one. If there is another, I'm happy to close this one. Essentially, when specifying that a particular entity is an array of objects with a definite shape, I would like it if those were displayed as an actual array. Given the following Javascript:

```javascript
/**
 * @param {Object} params
 * @param {Object[]} params.items - Array of items
 * @param {string} params.items[].name - Name of the item
 * @param {string} params.items[].value - Value of the item
*/
function myFunc({ items = []}){
    items.map(item => {
        console.log(item.name, item.value)
    })
}
```

Currently, on hover, VSCode displays the type hinting as:

```
function myFunc({ items }: {
    items: {
        name: string;
        value: string;
    };
}): void
```

However, this makes it appear that items is an object. That is incorrect because items is instead an array of objects, and is specified as such in the JSDoc. I would expect something akin to when you specify the properties inline:

#### JS:
```javascript
/**
 * @param {Object} params
 * @param {{name: string, data: string}[]} params.items - Array of items
*/
function myFunc({ items = []}){
    items.map(item => {
        console.log(item.name, item.value)
    })
}
```

#### Hover:
```
function myFunc({ items }: {
    items: {
        name: string;
        data: string;
    }[];
}): void
```

The problem with using the inline format is the lack of an explanation of individual properties, and some object shapes can get very long, and even be nested. Additionally, the above solution waits until the end of the object definition to denote that the property should be an array. It seems that it would be more user-friendly if it was denoted as an array at the beginning, like this:

```
function myFunc({ items }: {
    items: [{
        name: string;
        data: string;
    }];
}): void
```

Thanks for your time and the great product!!
Repository: TypeScript
Issue: Visual hint when using a deprecated children prop in a React component 
Labels: Suggestion,Awaiting More Feedback

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
Add a visual hint when using the children in a React component are deprecated

Using children as prop you get the visual hint:
![image](https://github.com/microsoft/vscode/assets/579417/2cd0e5d0-9c18-4eae-8959-52afc66e2cc1)

There is no hint when used as a child element:

![image](https://github.com/microsoft/vscode/assets/579417/9a73196b-ef10-4ba0-b711-63366a0aa267)
Repository: flutter
Issue: Migrate packages to Swift 6 language mode
Labels: platform-ios,platform-mac,P2,team-ios,triaged-ios

# Background

Swift 6 language mode enables strict concurrency checking. Code changes may be necessary to upgrade a package to the Swift 6 language mode.

A Swift 6 app can depend on Swift 5 packages and vice-versa. The Swift 6 compiler supports [both Swift 6 and Swift 5 language modes](https://www.swift.org/migration/documentation/swift-6-concurrency-migration-guide/swift6mode/).

WWDC session: https://www.youtube.com/watch?v=75-c6jSE8kU
Migration docs: https://www.swift.org/migration/documentation/swift-6-concurrency-migration-guide/swift6mode/

See also:
* https://github.com/flutter/flutter/issues/150939
* https://github.com/flutter/website/issues/10820

# Work

Migrate packages that use Swift (this list may be incomplete):

* [ ] file_selector_ios
* [ ] file_selector_macos
* [ ] interactive_media_ads
* [ ] ios_platform_images
* [ ] path_provider_foundation
* [ ] pigeon
* [ ] pointer_interceptor_ios
* [ ] quick_actions_ios
* [ ] shared_preferences_foundation
* [ ] url_launcher_ios
* [ ] url_launcher_macos