sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Views with different id sometimes will cause multi activitybar 
Labels: bug,workbench-views,confirmation-pending

<!-- ⚠️⚠️ 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.77.3
- OS Version: Window10

Steps to Reproduce:

1. When I develop a vscode extension, I have the demo below:
![image](https://user-images.githubusercontent.com/95005411/232742396-a59da18c-1164-4d21-9825-3b5bd16a215e.png)
![image](https://user-images.githubusercontent.com/95005411/232742557-53b75c52-e27b-4920-a258-6d7c7107002e.png)

2.It causes multiple activity bars when I debug in the extension host
![image](https://user-images.githubusercontent.com/95005411/232742842-628c8ff9-21ba-494d-b129-a26754534859.png)
![image](https://user-images.githubusercontent.com/95005411/232743430-70256bd2-3871-4877-9f4d-da8425ab75c1.png)
Repository: rust
Issue: Tracking Issue for using `raw-dylib` in the standard library
Labels: T-compiler,C-tracking-issue,T-libs

With the `raw-dylib` feature close to finishing stabilization, it'd be great to start using it in the Windows parts of the standard library so that we're not dependent on finding a Windows SDK for builds.

This issue is to track progress towards this goal and any issues that may arise from using raw-dylib generated import libraries instead of user-supplied import libraries. However, in doing so it's important not to lose out on any features people may be relying on.

Things to investigate include how this interacts with the different crate-types (e.g. lib. dylib, staticlib, etc) and how this may affect different linking scenarios, e.g. linking a Rust staticlib into a C++ project that wants to override imports.

Note that this issue is about the standard library only. The standard library is somewhat unique in that it is distributed pre-built therefore there's very limited ability to configure its behaviour.

### Steps / History

- [x] `raw-dylib` stabilization: #109677
- [ ] `cg_clif` support for `raw-dylib` https://github.com/rust-lang/rustc_codegen_cranelift/issues/1345
- [ ] Use `raw-dylib` in the standard library

I'm tentatively tagging this with `t-compiler` as well as `t-libs` as there may be issues that concern the implementation of raw-dylib.

### Unresolved Questions

- How is `staticlib` linking affected?
Repository: PowerToys
Issue: File Locksmith can't recognize mounted ISOs
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.69.1

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

File Locksmith

### Steps to reproduce

1. Download a .iso file
2. Mount the .iso in Windows Explorer
3. Use "What's using this file" to see what's using the file
4. See that there's nothing there

### ✔️ Expected Behavior

File shows up as being opened by the system (because it's mounted and therefore unable to be deleted)

### ❌ Actual Behavior

The file doesn't seem to be used by anything

### Other Software

_No response_
Repository: flutter
Issue: Dart compilation errors in flutter app builds should have a more user friendly error message
Labels: tool,platform-mac,a: error message,has reproducible steps,P2,found in release: 3.7,found in release: 3.10,team-tool,triaged-tool

When a Flutter app contains a library that doesn't have null safety -- because it has a `// @dart=2.9` version maker -- the `flutter run` command fails with a very convoluted message:

```
mit-macbookpro7:unsoundflutter mit$ flutter run
Resolving dependencies...
+ characters 1.3.0
+ collection 1.17.1
+ flutter 0.0.0 from sdk flutter
+ js 0.6.7
+ material_color_utilities 0.2.0 (0.3.0 available)
+ meta 1.9.1
+ sky_engine 0.0.99 from sdk flutter
+ vector_math 2.1.4
Changed 8 dependencies!
Launching lib/main.dart on macOS in debug mode...
lib/unsound.dart:1:1: Error: Library doesn't support null safety.
// @dart=2.9
^^^^^^^^^^^^
Target kernel_snapshot failed: Exception

Command PhaseScriptExecution failed with a nonzero exit code
warning: Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Flutter Assemble' from project 'Runner')
** BUILD FAILED **

Building macOS application...
Exception: Build process failed
```

Can we catch this specific error from the compiler and omit this part of the error output?
```
Target kernel_snapshot failed: Exception

Command PhaseScriptExecution failed with a nonzero exit code
warning: Run script build phase 'Run Script' will be run during every build because it does not specify any outputs. To address this warning, either add output dependencies to the script phase, or configure it to run in every build by unchecking "Based on dependency analysis" in the script phase. (in target 'Flutter Assemble' from project 'Runner')
** BUILD FAILED **

Building macOS application...
Exception: Build process failed
```
Repository: pytorch
Issue: torch.nn.functional.multilabel_margin_loss cuda lacks checking of "out of bound"
Labels: module: nn,module: cuda,module: error checking,triaged

### 🐛 Describe the bug

Though [#73176](https://github.com/pytorch/pytorch/issues/73176) lists a lot of APIs lacks checking out of bound in cuda. It still  can be repro in torch.nn.functional.multilabel_margin_loss.
```
import torch
results={}
arg_1 = torch.as_tensor([[0.0360, 0.6321, 0.6267, 0.4555]])
print(arg_1)
arg_2 = torch.as_tensor([[-2489,  -776,   380, -1566]])
print(arg_2)
arg_3 = "mean"
try:
  results["res_cpu"] = torch.nn.functional.multilabel_margin_loss(input=arg_1,target=arg_2,reduction=arg_3,)
except Exception as e:
  results["err_cpu"] = "ERROR:"+str(e)
arg_1 = arg_1.clone().cuda()
arg_2 = arg_2.clone().cuda()
try:
  results["res_gpu"] = torch.nn.functional.multilabel_margin_loss(input=arg_1,target=arg_2,reduction=arg_3,)
except Exception as e:
  results["err_gpu"] = "ERROR:"+str(e)
print(results)
#res: {'err_cpu': "ERROR:argument #2 'target' is out of range", 'res_gpu': tensor(0., device='cuda:0')}
```

Also it still can be seen in torch.nn.MultiLabelMarginLoss, even though [#73176](https://github.com/pytorch/pytorch/issues/73176) has fixed this issue.
```
import torch
results={}
arg_class = torch.nn.MultiLabelMarginLoss()
arg_1_0 = torch.as_tensor([[0.3449, 0.5441, 0.7594, 0.5161]])
print(arg_1_0)
arg_1_1 = torch.as_tensor([[-59,  45, 187, 131]])
print(arg_1_1)
arg_1 = [arg_1_0,arg_1_1,]
try:
  results["res_cpu"] = arg_class(*arg_1)
except Exception as e:
  results["err_cpu"] = "ERROR:"+str(e)
arg_class = arg_class.cuda()
arg_1_0 = arg_1_0.clone().cuda()
arg_1_1 = arg_1_1.clone().cuda()
arg_1 = [arg_1_0,arg_1_1,]
try:
  results["res_gpu"] = arg_class(*arg_1)
except Exception as e:
  results["err_gpu"] = "ERROR:"+str(e)
print(results)
# results: {'err_cpu': "ERROR:argument #2 'target' is out of range", 'res_gpu': tensor(0., device='cuda:0')}
```


### Versions

pytorch version: 2.0.0+cu118

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @ngimel @malfet
Repository: pytorch
Issue: The meta implementation of `index_put` does not do any check
Labels: triaged,module: meta tensors,release notes: Meta API

### 🐛 Describe the bug

For example, the following code breaks in eager but successfully runs under `torch.compile`:

```python
Before, the following code would not error out

@compile()
def f(x, y, z):
    x.index_put_((y,), z)
    return x

x = torch.randn(3, 2, 4, device="cuda")
y = torch.arange(2, device="cuda")
z = torch.zeros(4, 2, 4, device="cuda")
f(x, y, z)
```

FWIW, reusing the meta function from `index.Tensor` breaks every subsystem. See https://github.com/pytorch/pytorch/pull/98589. I've seen that most tests special-case `index.Tensor`, so something similar would need to be done for this function.

### Versions

master

cc @ezyang @eellison @bdhirsh @soumith
Repository: transformers
Issue: Add CLIP-ViP
Labels: New model,Vision

### Model description

[CLIP-ViP](https://github.com/microsoft/XPretrain/tree/main/CLIP-ViP) is a video-language model which is based on a pre-trained image-text model [CLIP](https://openai.com/blog/clip/) then further pre-trained (post-pretraining) on a large-scale video-text dataset [HD-VILA-100M](https://github.com/microsoft/XPretrain/tree/main/hd-vila-100m). This work is accepted by ICLR 2023.

### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

[The official implementation](https://github.com/microsoft/XPretrain/tree/main/CLIP-ViP)
This repo has model implementation and pre-trained weights.
@hellwayxue
Repository: godot
Issue: Non-selectable TreeItem still triggers "item_activated" signal on Tree 
Labels: bug,topic:gui

### Godot version

4.0.2

### System information

Ubuntu 22.04, Vulkan

### Issue description

A non-selectable TreeItem (a TreeItem with `set_selectable(0, false)`) still triggers `item_activated` on the Tree node when double-clicked. This doesn't look like the intended behavior, since it looks like it would be the case that a "non-selectable" tree item should not be activated either by double-clicking on it. 

The specific use-case I was looking at was a project in which I had to create in-editor behavior, and some functionality on the Scene Tree Inspector had to be disabled (more specifically, nodes should not be selectable). But setting `set_selectable` was not sufficient, because double-clicking on any node would trigger the Scene Tree Inspector functionality with the `item_activated` signal.

### Steps to reproduce

Call `set_selectable(0,false)` on a TreeItem, and double-click on it.

### Minimal reproduction project

[TreeItem Bug.zip](https://github.com/godotengine/godot/files/11262817/TreeItem.Bug.zip)
Repository: next.js
Issue: Incorrect resolving of "catch all" routes (pages/ directory)
Labels: bug,Navigation

### Verify canary release

- [x] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 22.4.0: Mon Mar  6 20:59:28 PST 2023; root:xnu-8796.101.5~3/RELEASE_ARM64_T6000
Binaries:
  Node: 18.12.1
  npm: 8.19.2
  Yarn: 1.22.19
  pnpm: N/A
Relevant packages:
  next: 13.3.1-canary.13
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue

https://github.com/vvlad5/next-dynamic-routes

### To Reproduce

1. Go to https://next-dynamic-routes-five.vercel.app/blog.
You'll see the corresponding page with the data from its `getServerSideProps` function.

2. Click on "**Go to blog/[pid]**" to navigate to the dynamic route.
Same thing, the page works as expected, no issues.

3. Click on "**Go to blog/[...slug]**" to navigate to the "catch all" route.
Locally this will be resolved as expected, BUT on deployment you will see the **blog/[...slug]** page with the data from `getServerSideProps` of the **blog/index** page. Then, if you try to refresh the page, you will actually see **blog/index**, although the URL will still match the "catch all" route.

### Describe the Bug

The `[...catch-all]` route, if it's in the same directory with some `[dynamic]` route, resolves to an index page. Reproducible only when the app is deployed somewhere, from NextJS `13.2.0` up to `13.3.1-canary.13` (the last release I tested).

### Expected Behavior

The `[...catch-all]` route should resolves correctly according to the documentation:
https://nextjs.org/docs/routing/dynamic-routes#caveats

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: next.js
Issue: App dir with typed routes not working when "moduleResolution" is set to "nodenext"
Labels: TypeScript

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
System Software Overview:
      System Version: macOS 13.3.1 (22E261)
      Kernel Version: Darwin 22.4.0

Binaries:
      Node: 18.12.1
      pnpm: 8.2.0

Relevant packages:
      next: 13.3.0
      eslint-config-next: 13.3.0
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App directory (appDir: true), Routing (next/router, next/navigation, next/link), TypeScript (plugin, built-in types)

### Link to the code that reproduces this issue

https://codesandbox.io/p/github/Dwlad90/next-13-app/nodenext

### To Reproduce

Conditions to reproduce:
1. set "moduleResolution": "NodeNext" in tsconfig.json
2. set "typedRoutes": true in next.config.js
3. run "next build"

### Describe the Bug

Throw the following error when trying to build an app:

```zsh
info  - Linting and checking validity of types ..Failed to compile.

src/app/layout.tsx
Type error: Layout "src/app/layout.tsx" does not match the required types of a Next.js Layout.
  Invalid configuration "default":
```

### Expected Behavior

Successfully building an application

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: pytorch
Issue: Question about GRU(RNN/LSTM) outputs shape
Labels: module: docs,module: nn,module: rnn,triaged,actionable

### 📚 The doc issue

[https://pytorch.org/docs/1.8.1/generated/torch.nn.GRU.html#torch.nn.GRU](https://pytorch.org/docs/1.8.1/generated/torch.nn.GRU.html#torch.nn.GRU)
[https://pytorch.org/docs/1.9.0/generated/torch.nn.GRU.html#torch.nn.GRU](https://pytorch.org/docs/1.9.0/generated/torch.nn.GRU.html#torch.nn.GRU)
Versions of pytorch after 1.9.0 have made some changes to the GRU(RNN/LSTM?) documentation.

The h_n of shape of 1.8.1 is like this:
  **(num_layers * num_directions, batch, hidden_size):**
The h_n of shape of 1.9 is like this:
**(D∗num_layers,N,Hout)**
where D is "2 if bidirectional=True otherwise 1"
So I think D is the num_directions of the previous version, then h_n of shape after 1.9.0 is:
  **(num_directions * num_layers, batch, hidden_size)**

This is inconsistent with the order of the previous version in the first two dimensions. What should I do if I want to fetch the data of the last layer? Is there something wrong with my understanding?

In addition, I also found that two different descriptions exist at the same time in version 2.0, which is a bit confusing...
[https://pytorch.org/docs/stable/generated/torch.ao.nn.quantized.dynamic.GRU.html](https://pytorch.org/docs/stable/generated/torch.ao.nn.quantized.dynamic.GRU.html)
[https://pytorch.org/docs/stable/generated/torch.nn.GRU.html#torch.nn.GRU](https://pytorch.org/docs/stable/generated/torch.nn.GRU.html#torch.nn.GRU)

### Suggest a potential alternative/fix

_No response_

cc @svekars @carljparker @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @zou3519
Repository: next.js
Issue: [middleware] - NextResponse.next({...}) not working
Labels: bug,Runtime

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: arm64
      Version: Darwin Kernel Version 22.3.0: Mon Jan 30 20:39:35 PST 2023; root:xnu-8792.81.3~2/RELEASE_ARM64_T8103
    Binaries:
      Node: 16.19.0
      npm: 8.19.3
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.3.1-canary.13
      eslint-config-next: 13.1.6
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue

https://github.com/NicuB93/next-js-middleware-issue

### To Reproduce

1. Clone repository
2. Run yarn install or npm install
3. Run project
4. Navigate to localhost:3000/about
5. Check terminal where you ran yarn dev / npm run dev

### Describe the Bug

I've made a big jump in terms of Next.js version on our project. It was on 12.3.0, then updated to 13.3.0 and then to the latest canary. I was doing some permission checking so if the logged in user had no permission to view a page, middleware would return a `403` status code, then get the status code in `getServerSideProps` then in the actual component. The same goes with the other status codes.
In version 12.3.0 I was returning the status code like this: `return NextResponse.next({ status: 403 })` and was working perfectly.
In version 13.x.x regardless of what I return in the NextResponse, in `getServerSideProps` it would read status code `200`, even the set headers won't return correctly.

### Expected Behavior

Expecting the `ctx.res.statusCode` in `getServerSideProps` to return a `403` status code.

### Which browser are you using? (if relevant)

Chrome 111.0.5563.146

### How are you deploying your application? (if relevant)

_No response_
Repository: vscode
Issue: Iframe content in WebviewPanel appears to drop Copy/Paste and other keyboard events, as well as context menu events
Labels: bug,webview

Steps to Reproduce:

1. Load a simple page in a WebviewPanel that contains an iframe:
```
  <html>
  <title>Documentation</title>
  <body>
  This is a non-iframe test.
  <iframe src="http://127.0.0.1:8080/test.html" width="100%" height="200px"></iframe>
  </body>
  </html>
```
The embedded page can contain any content, but something trivial is enough to reproduce the problem.

2. Right-click on the non-iframe text (result: context menu is shown)
3. Select non-iframe text and Cmd+C to copy (result: text is copied)
4. Right-click on content in the iframe (result: no context menu)
5. Select iframe text and Cmd+C to copy (result: no copy)
6. Select iframe text and choose system "Copy" command from application Edit menu (result: text is copied)

I can get some keyboard and context menu events to break in Developer Tools, but NEVER events that originated from the iframe. I can see clearly that when the non-iframe part of the page has focus, keyboard events make their way to VSCode (e.g. I can do Cmd+Shift+P to show the command palette). If I am focused on the iframe, keyboard events are swallowed.


```
Version: 1.76.2 (Universal)
Commit: ee2b180d582a7f601fa6ecfdad8d9fd269ab1884
Date: 2023-03-14T17:54:09.061Z
Electron: 19.1.11
Chromium: 102.0.5005.196
Node.js: 16.14.2
V8: 10.2.154.26-electron.0
OS: Darwin arm64 21.5.0
Sandboxed: No
```
Repository: TypeScript
Issue: Generic constraint is not validated in a recursive type
Labels: Bug,Help Wanted

# Bug Report

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, starting from 4.1 where recursive conditional types were added

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?ts=5.0.4#code/KYDwDg9gTgLgBDAnmYcDCEC2YCuNgBKAhgHYDmwAMhBAM7AA8AUHHAHJyj4kAmtcJHJgBGwKABoWcAsFo4ANvC7Be-AIJQoRRA0EixAPjgBeOAG0AupKOmZcxWYDk8lWRgALRxc4hufdnAA-NKyCvAAXOhYuPjE5FQ09Axs4uYAdBl2YalZDs6uHl4WBkxMSChwaiZR2HiEpBTUdIwA3nAAZjSRMFA4qAC+JeWoalWmGLWxDQnNDACMAAwlTKCQsAjIqBMx9fEAyj0AlgDGMMysHMqqAkKiElK5Sr4q-hpaOnp3NuZWTN+Xz2unzEUmCjycLnIhW8V38HDBoUUcEi2zqcQoBygJzOKXSmURMByBIhBU8FmKUkiJGAADcQWVNnAAELVVFTfZHU4MNqdCDdXoDIaMpks8bRNHTTHY+ZLIA)

### 💻 Code

```ts
export type ComputeRangeLoose<
  N extends number,
  Result extends Array<number> = [],
> = Result['length'] extends N ? Result : ComputeRangeLoose<N, [...Result, Result['length']]>

type A = ComputeRangeLoose<{ foo: true }>

export type ComputeRangeStrict<
  N extends number,
  Result extends Array<number> = [],
> = N extends number
  ? Result['length'] extends N ? Result : ComputeRangeStrict<N, [...Result, Result['length']]>
  : never

type B = ComputeRangeStrict<{ foo: true }>
```

### 🙁 Actual behavior

`ComputeRangeLoose<{ foo: true }>` allows to pass a type that is not related to `number`, throwing `Type instantiation is excessively deep and possibly infinite.`

`ComputeRangeStrict<{ foo: true }>` throws an expected `Type '{ foo: true; }' does not satisfy the constraint 'number'`

### 🙂 Expected behavior

Both `ComputeRangeLoose` and `ComputeRangeStrict` throw `Type '{ foo: true; }' does not satisfy the constraint 'number'`

---

As the issue is reproducible since 4.1, I'm pretty sure it was already mentioned somewhere however I failed to find a suitable issue
Repository: godot
Issue: Missing implementation for template functions in godot-cpp headers
Labels: bug,topic:gdextension

### Godot version

v4.0.2.stable.official.7a0977ce2

### System information

Windows 11

### Issue description

When creating a GDExtension, I tried to call `Callable::bind`, the problem is that this function is a template variadic function, which doesn't seem to have the respective implementation, the result is that when trying to compile the project, it throws the LNK2019 linker error saying that the symbol for `Callable::bind<unsigned __int64>(unsigned __int64 const &)  const` is unresolved (when trying to call this function with a uint64_t as argument).
I don't know if it's only with this particular function or if there are more examples of this bug.

### Steps to reproduce

1. Follow the [official GDExtension tutorial](https://docs.godotengine.org/en/stable/tutorials/scripting/gdextension/gdextension_cpp_example.html)
2. In any portion of the code, try to call any template function, for example `Callable::bind`.

### Minimal reproduction project

N/A