sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Softlink icon is not updated for folder
Labels: bug,file-explorer

<!-- ⚠️⚠️ 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

<!-- 🪓 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. -->
Version: 1.73.1 (user setup)
Commit: 6261075646f055b99068d3688932416f2346dd3b
Date: 2022-11-09T04:27:29.066Z
Electron: 19.0.17
Chromium: 102.0.5005.167
Node.js: 16.14.2
V8: 10.2.154.15-electron.0
OS: Windows_NT x64 10.0.22621
Sandboxed: No

Steps to Reproduce:

1. create two folders
![image](https://user-images.githubusercontent.com/28779355/203738741-338a9185-d824-4bb4-932d-b80a161b2bf5.png)
2. Delete "folder2"
3. Start powershell with administrator previlege, 
4. cd the root of workspace, 
5. run command to create soft link, the created folder's name is still "folder2", here we use folder1 as the linked folder, but it does not matter. `New-Item -Path ./folder2 -ItemType SymbolicLink -Value .\folder1`

It seems like still the same:
![image](https://user-images.githubusercontent.com/28779355/203740870-efe5c6af-25bf-4f25-a8ea-d8d5cb0d6d71.png)

But if we open the folder again(or use command to reload the window):
![image](https://user-images.githubusercontent.com/28779355/203741216-ea409e5d-5634-4421-9d78-8b7de0564712.png)

NOTE: I do not test under Linux and not test for file.

PS: If this issue is not in TODO list of team, I will be glad to have a try to fix it.
Repository: PowerToys
Issue: Advance search for files
Labels: Needs-Triage

### Description of the new feature / enhancement

File Explorer add-ons:
Group files by a pattern in their name
Find file with the same pattern in the computer

### Scenario when this would be used?

when working with multiple file types that have the same id, date-created, ect...


### Supporting information

_No response_
Repository: rust
Issue: Type Alias hides lifetime errors
Labels: A-lifetimes,T-compiler,C-bug

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

Using a type alias hides certain lifetime related errors.

This is code adopted from `src/test/ui/self/self_lifetime-async.rs` that I discovered while working on #104321 

```rust
pub struct Foo<'a>(&'a ());

impl Foo<'static> {
    pub fn using_type<'a>(self: &Foo<'static>, arg: &'a ()) -> &() {
        arg
    }
}
```

as well as the async variant:

```rust
impl Foo<'static> {
    pub async fn using_type_async<'a>(self: &Foo<'static>, arg: &'a ()) -> &() {
        arg
    }
}
```

both fail with a lifetime error:

```rust
error: lifetime may not live long enough
 --> playground\async-codegen\src\lib.rs:5:9
  |
4 |     pub fn using_type<'a>(self: &Foo<'static>, arg: &'a ()) -> &() {
  |                       --        - let's call the lifetime of this reference `'1`
  |                       |
  |                       lifetime `'a` defined here
5 |         arg
  |         ^^^ associated function was supposed to return data with lifetime `'1` but it is returning data with lifetime `'a`
```

... whereas when using a type alias for `Foo<'static>`, the code compiles just fine:

```rust
type Alias = Foo<'static>;
impl Alias {
    pub fn using_alias<'a>(self: &Alias, arg: &'a ()) -> &() {
        arg
    }
    pub async fn using_alias_async<'a>(self: &Alias, arg: &'a ()) -> &() {
        arg
    }
}
```

Either I am completely misunderstanding how type aliases are supposed to work, or using an alias indeed hides problems that it shouldn’t?

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.67.0-nightly (70f8737b2 2022-11-23)
binary: rustc
commit-hash: 70f8737b2f5d3bf7d6b784fad00b663b7ff9feda
commit-date: 2022-11-23
host: x86_64-pc-windows-msvc
release: 1.67.0-nightly
LLVM version: 15.0.4
```
Repository: vscode
Issue: iPad: text selection (cursor)
Labels: bug,editor-core,ios-ipados

Text selection (with the mouse for example) crashes regularly. The workaround is to reload the window (iPadOS 16.1)
Repository: vscode
Issue: Telemetry: Avoid hardcoding remote authority names
Labels: debt,telemetry

The [list of remote names](https://github.com/Microsoft/vscode/blob/main/src/vs/platform/telemetry/common/telemetryUtils.ts#L230) used for telemetry should not be hardcoded, but taken out of product.json
Repository: storybook
Issue: [Bug]: TS type aliases can't be augmented
Labels: bug,typescript,needs triage

### Describe the bug

AFAIK TypeScript type aliases (e.g. `type Story = ...`) can't be [augmented](https://www.typescriptlang.org/docs/handbook/declaration-merging.html), as opposed to TypeScript interfaces. This is a pretty big problem when it comes to Storybook types, because it appears that pretty much all exported types are done using `type` aliases.

What this means in practice is that you can't extend the context or any other type with your own properties, and they will always be typed as `any` unless if you force cast them.

### To Reproduce

```shell
Pretty much all (with minor exceptions) of the types seem to be defined with `type` aliases instead of `interfaces` so just check any TS file in the repo. As an example: https://github.com/storybookjs/storybook/blob/next/code/renderers/server/src/types.ts
```


### System

```shell
System:
    OS: Linux 5.15 Ubuntu 20.04.2 LTS (Focal Fossa)
    CPU: (6) x64 AMD Ryzen 9 5900X 12-Core Processor
  Binaries:
    Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node
    Yarn: 3.2.0 - ~/.nvm/versions/node/v16.14.0/bin/yarn
    npm: 8.3.1 - ~/.nvm/versions/node/v16.14.0/bin/npm
  Browsers:
    Chrome: 100.0.4896.75
  npmPackages:
    @storybook/addon-a11y: ^7.0.0-alpha.42 => 7.0.0-alpha.43 
    @storybook/addon-docs: ^7.0.0-alpha.42 => 7.0.0-alpha.42 
    @storybook/addon-essentials: ^7.0.0-alpha.42 => 7.0.0-alpha.42 
    @storybook/addon-interactions: ^7.0.0-alpha.42 => 7.0.0-alpha.42 
    @storybook/addon-links: ^7.0.0-alpha.42 => 7.0.0-alpha.42 
    @storybook/jest: ^0.0.10 => 0.0.10 
    @storybook/test-runner: 0.10.0-next.1 => 0.10.0-next.1 
    @storybook/testing-library: ^0.0.13 => 0.0.13 
    @storybook/vue3: ^7.0.0-alpha.42 => 7.0.0-alpha.42 
    @storybook/vue3-vite: ^7.0.0-alpha.42 => 7.0.0-alpha.42
```


### Additional context

_No response_
Repository: flutter
Issue: Assertion should allow `semanticsLabel` for TextSpan without `text`
Labels: c: new feature,framework,a: accessibility,has reproducible steps,P3,found in release: 3.3,found in release: 3.6,team-framework,triaged-framework

I don't agree with the following assert:

https://github.com/flutter/flutter/blob/b8f7f1f9869bb2d116aa6a70dbeac61000b52849/packages/flutter/lib/src/painting/text_span.dart#L80

Let's say I'm constructing a rich text with a root `TextSpan` consisting of a few `TextSpan`s and (decorative - say - icons) `WidgetSpan`s in its `children`. And I also want to provide universal `semanticsLabel` for the whole text, that gives better meaning to screen reader users.

```
Flutter 3.3.5 • channel stable • https://github.com/flutter/flutter.git
Framework • revision d9111f6402 (5 weeks ago) • 2022-10-19 12:27:13 -0700
Engine • revision 3ad69d7be3
Tools • Dart 2.18.2 • DevTools 2.15.0
```
Repository: flutter
Issue: [pigeon] Add support for DateTime
Labels: package,c: proposal,team-ecosystem,p: pigeon,P3,triaged-ecosystem

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

`DateTime` is an extremely common type, likely to be used in many Flutter plugins. However, we need to convert `DateTime` to integer or string to communicate with the native code, and add the same logic both on Dart, Swift/ObjectiveC and Kotlin/Java, which is not type safe (one of the main goals of `pigeon`).

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal

- Accept `DateTime` type on pigeon
- Generate the code parsing `DateTime` from/to the [StandardMessageCodec](https://api.flutter.dev/flutter/services/StandardMessageCodec-class.html) using integer or string.

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching something showing what you are imagining:
      * images
      * videos
      * code samples

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->
Repository: rust
Issue: Symbol-mangling (v0) should show difference between async / closure / generator
Labels: A-linkage,A-closures,T-compiler

The following code:

```rust
pub async fn fn_with_nested_block() -> Backtrace {
    None.unwrap_or_else(|| async { Backtrace::force_capture() })
        .await
}
```

Generates the following demangled symbol with legacy demangling:

```
async_codegen::fn_with_nested_block::{{closure}}::{{closure}}::{{closure}}
```

(v0 mangling is similar, but with `{closure#0}` instead)

Whereas Windows mangling gives this fn name:

```
async_codegen::fn_with_nested_block::async_fn$0::closure$0::async_block$0
```

This makes it clear what is an async fn, closure or async block. v0 symbol mangling should make a similar distinction.

https://github.com/rust-lang/rust/pull/104333 is a first attempt to thread the necessary information through to the place that does the symbol mangling, but actually extending the v0 symbol mangling format / spec is necessary as well to fully solve this.
Repository: neovim
Issue: "echo" from autocommand not showing up with laststatus=3
Labels: bug,startup,statusline

### Neovim version (nvim -v)

NVIM v0.9.0-dev-379+g38863f524

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

N/A, vim doesn't have laststatus=3

### Operating system/version

Windows 11

### Terminal name/version

Windows Terminal 1.15.2874.0

### $TERM environment variable

N/A

### Installation

Repo

### How to reproduce the issue

```vim
" minimal.vim
set laststatus=3
:au BufEnter,BufWinEnter *.c,*.h echo 'Entering a C or C++ file'
```

```c
// Minimal C file
```

Recreate with `nvim --clean -u minimal.vim minimal.c`

### Expected behavior

"Entering a C or C++ file" to show up in the message box.

### Actual behavior

Nothing shows up, and nothing is stored in the message history.
Repository: PowerToys
Issue: File Explorer - Preview Pane - Add support for custom file extensions
Labels: Needs-Triage

### Description of the new feature / enhancement

I'd like to introduce the possibility to add custom file extension to this list:
![image](https://user-images.githubusercontent.com/46932745/203800087-22e59458-757b-499f-803c-b306e79bdcc0.png)

PowerShell files (.ps1) and Linux Shell filer (.sh) are supported by this tool, but their extension is not present in this list, it would be useful to see every working extension: (A list is not even available in the [Documentation](https://learn.microsoft.com/en-us/windows/powertoys/file-explorer))
![image](https://user-images.githubusercontent.com/46932745/203805016-984290cb-b347-4433-aefb-f251d627c54c.png)

![image](https://user-images.githubusercontent.com/46932745/203803403-3096f637-47c8-4e51-9a3e-cf4223c0e705.png) 


Batch files (.bat) have the default windows preview (white background with black text) and I'd like to be able to change it to the default Monaco style.
![image](https://user-images.githubusercontent.com/46932745/203802282-90edfe73-a2ac-456a-876e-c3af1c2d52eb.png)


Git files, like .gitignore and .gitattributes, have their preview if you have git installed (also black on white, and I'd like to override this too)
![image](https://user-images.githubusercontent.com/46932745/203802186-acba2b11-3171-4cfd-90d7-2d7d58fe8dbe.png)


This also applies to other formats I often would like to read without opening them, like:

- .lock, 
- .env
- .uproject
- .uplugin

It would be really useful to have the possibility to add custom extensions and treat them as regular .txt files (I don't really care about having fancy colors, but that would be a plus)

### Scenario when this would be used?

To preview files with custom extensions that could be easily supported "out of the box" but they are not recognized by the tool

### Supporting information

In my specific case, as an Unreal Engine dev, it would be really useful to preview project and plugin files, that have the following syntax:


.uproject file:
```
{
	"FileVersion": 3,
	"EngineAssociation": "{F606ED38-477B-4BEB-D8C5-D588318C83C6}",
	"Category": "",
	"Description": "",
	"Modules": [
		{
			"Name": "UnrealProject",
			"Type": "Runtime",
			"LoadingPhase": "Default",
			"AdditionalDependencies": [
				"Engine",
				"CoreUObject"
			]
		}
	]
}

```

.uplugin file:

```
{
	"FileVersion": 3,
	"Version": 1,
	"VersionName": "1.0",
	"Description": "Mongocxx Library",
	"Category": "Database",
	"CreatedBy": "Ares9323",
	"CreatedByURL": "",
	"MarketplaceURL": "",
	"SupportURL": "",
	"EngineVersion": "4.27.0",
	"CanContainContent": false,
	"Installed": true,
	"Modules": [
		{
			"Name": "MongoDB",
			"Type": "Runtime",
			"LoadingPhase": "EarliestPossible",
			"PlatformAllowList": [
				"Win64"
			],
			"WhitelistPlatforms" :
			[
				"Win32",
				"Win64"
			]
		}
	]
}
```
Repository: pytorch
Issue: [dynamo] RuntimeError: Failed running call_function aten.convolution_backward(*(FakeTensor(FakeTensor(..
Labels: triaged,module: dynamo,dynamo-must-fix

### 🐛 Describe the bug


```
TypeError: new_empty(): argument 'size' (position 1) must be tuple of ints, but found element of type NoneType at pos 0
...
RuntimeError: Failed running call_function aten.convolution_backward(*(FakeTensor(FakeTensor(..., device='meta', size=(2, 2, 8, 8)), cpu), FakeTensor(FakeTensor(..., device='meta', size=(2, 2, 6, 6)), cpu), FakeTensor(FakeTensor(..., device='meta', size=(2, 2, 3, 3)), cpu)), **{'bias_sizes': None, 'stride': [1, 1], 'padding': [2, 2], 'dilation': [1, 1], 'transposed': False, 'output_padding': [0], 'groups': 1, 'output_mask': [True, True, True]}):
new_empty(): argument 'size' (position 1) must be tuple of ints, but found element of type NoneType at pos 0
(scroll up for backtrace)
```


```python
import torch
import torch._dynamo as dynamo

@dynamo.optimize("eager")
def forward(grad_out, input_vec, weight):
    return torch.ops.aten.convolution_backward(
        grad_out,
        input_vec,
        weight,
        bias_sizes=None,
        stride=[1, 1],
        padding=[2, 2],
        dilation=[1, 1],
        transposed=False,
        output_padding=[0],
        groups=1,
        output_mask=[True, True, True])


forward(torch.randn(2, 2, 8, 8), torch.randn(2, 2, 6, 6),
        torch.randn(2, 2, 3, 3))
```

Full error log: https://gist.github.com/silvasean/068ec6759d9f29f0b9255e5fc1c62e0a

### Versions

Collecting environment information...
PyTorch version: 1.14.0.dev20221114+cpu
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Debian GNU/Linux rodete (x86_64)
GCC version: (Debian 12.2.0-3) 12.2.0
Clang version: 14.0.6-2
CMake version: version 3.25.0
Libc version: glibc-2.35

Python version: 3.10.8 (main, Nov 3 2022, 15:17:13) [GCC 12.2.0] (64-bit runtime)
Python platform: Linux-5.18.16-1rodete4-amd64-x86_64-with-glibc2.35
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.23.4
[pip3] torch==1.14.0.dev20221114+cpu
[pip3] torchvision==0.15.0.dev20221114+cpu
[conda] Could not collect

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @aakhundov @kadeng @mlazos @soumith @yanboliang @anijain2305 @chunyuan-w @Xia-Weiwen @desertfire
Repository: pytorch
Issue: [dynamo] RuntimeError: Failed running call_function aten.nll_loss_backward(*(FakeTensor(FakeTensor(...
Labels: triaged,module: dynamo,dynamo-must-fix

### 🐛 Describe the bug

I'm seeing the following error when running with dynamo

```
RuntimeError: Failed running call_function aten.nll_loss_backward(*(FakeTensor(FakeTensor(..., device='meta', size=(1,)), cpu), FakeTensor(FakeTensor(..., device='meta', size=(3,)), cpu)), **{'target': FakeTensor(FakeTensor(..., device='meta', size=(3,), dtype=torch.int64), cpu), 'weight': None, 'reduction': 0, 'ignore_index': 10, 'total_weight': FakeTensor(FakeTensor(..., device='meta', size=()), cpu)}):
Index tensor must have the same number of dimensions as self tensor
```

repro:

```python
import torch
import torch._dynamo as dynamo


@dynamo.optimize("eager")
def forward(grad_output, input, target, total_weight):
    return torch.ops.aten.nll_loss_backward(grad_output,
                                            input,
                                            target=target,
                                            weight=None,
                                            reduction=0,
                                            ignore_index=10,
                                            total_weight=total_weight)


forward(torch.randn(1), torch.randn(3), torch.tensor([2, 3, 0]),
        torch.tensor(3.))
```

Full error log: https://gist.github.com/silvasean/5dd4b1667c9e451d12dac84e8a473173

### Versions

Collecting environment information...
PyTorch version: 1.14.0.dev20221114+cpu
Is debug build: False
CUDA used to build PyTorch: None
ROCM used to build PyTorch: N/A

OS: Debian GNU/Linux rodete (x86_64)
GCC version: (Debian 12.2.0-3) 12.2.0
Clang version: 14.0.6-2
CMake version: version 3.25.0
Libc version: glibc-2.35

Python version: 3.10.8 (main, Nov 3 2022, 15:17:13) [GCC 12.2.0] (64-bit runtime)
Python platform: Linux-5.18.16-1rodete4-amd64-x86_64-with-glibc2.35
Is CUDA available: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.23.4
[pip3] torch==1.14.0.dev20221114+cpu
[pip3] torchvision==0.15.0.dev20221114+cpu
[conda] Could not collect

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @aakhundov @kadeng @mlazos @soumith @yanboliang @anijain2305 @chunyuan-w @Xia-Weiwen @desertfire
Repository: angular
Issue: [Feature] Add Component Life-cycle Hook `ngOnElementDestroy` for Better Animations
Labels: area: animations,P3

### Which @angular/* package(s) are relevant/related to the feature request?

animations, core

### Description

Currently, as `ngOnDestroy` is called before the removal animation of a component, a lot of fantastic removal animations cannot be implemented easily and we have to use confusing workarounds for these animations.

For example, `@angular/cdk/portal` portals will detach from the portal outlet in the `ngOnDestroy` hook. Therefore, there would be no content for portal outlets in removal animations: [StackBlitz Demo](https://stackblitz.com/edit/angular-ivy-ts-strict-enabled-atg95k?file=src%2Fapp%2Fapp.component.html)

![Portal](https://user-images.githubusercontent.com/63489409/203807440-3c6d48af-420c-4453-9e1c-013db996e2b2.gif)

The problem above can actually be easily solved by using `ngTemplateOutlet` instead of `cdkPortalOutlet`, but in many cases the problem can be really hard to work around.

I am currently working on implementing [the app "Reply" of Material Studies](https://m2.material.io/design/material-studies/reply.html) in [this repository](https://github.com/TheNightmareX/reply). I am using the directive `libLayoutProjectionNode` and the component injection tree to build a tree of nodes, so that I can implement the Container Transform animation by using the Layout Projection technique. The Layout Projection technique basically creates a snapshot of the layout before changing the dom, and transform the elements from their old layouts to their new layouts after the dom has changed.

This is the best Container Transform that we can implement using Angular:

![Reply Container Transform](https://user-images.githubusercontent.com/63489409/203804010-78000514-9507-4c59-8638-cb2102540fa0.gif)

And this is the standard Container Transform from Material Design:

![Container Transform](https://user-images.githubusercontent.com/63489409/203805888-9bd63e5f-e9de-4672-be09-e25e4c47e86b.gif)

As you can see, our Container Transform works mostly well except that there is no crossfade transition.

Here comes the problem - It's completely impossible to implement a crossfade transition because it's impossible to get the old tree of nodes as them have already been detached from their parents in the `ngOnDestroy` hook to avoid memory leak. 🤷 

### Proposed solution

I propose that we should have a new life-cycle hook, which is invoked after the element of a component is actually removed from the DOM. A proposed name can be `ngOnElementDestroy`.

Developers should consider using this new `ngOnElementDestroy` hook to clean up their components/directives if the code they put in the `ngOnDestroy` hook changes the DOM.

This should significantly make the DOM more stable for removal animations.

I know that it's probably not the best choice to introduce a new life-cycle hook, but I failed to find out a better solution. 🤷 

### Alternatives considered

Otherwise WE HAVE TO DO A LOT OF COMPLICATED WORKAROUNDS TO IMPLEMENT THESE FANTASTIC REMOVAL ANIMATIONS!!!!!!!!!