sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Error with Continue on Codespace
Labels: bug,continue-working-on

* I went to https://github.dev/microsoft/monaco-editor/pull/4354
* I undid the changes in `package-lock.json`
* I chose "Continue Working in GitHub Codespaces"
* I chose to save my data with my GitHub account
> <img width="1477" alt="image" src="https://github.com/microsoft/vscode/assets/5047891/76522522-5cd5-421d-96d6-f0a2d36183d7">
* After landing in a CodeSpace I see the following errors
> <img width="1882" alt="image" src="https://github.com/microsoft/vscode/assets/5047891/e83e9863-0b66-4361-9465-585ed12bbcd1">

Errors from dev tools:
```
  ERR Cannot register two commands with the same id: workbench.action.focusCommentsPanel: Error: Cannot register two commands with the same id: workbench.action.focusCommentsPanel
    at h (https://assets.github.dev/insider/81725794264e4c0fddbc1b3b728013744ae90840/out/vs/workbench/workbench.web.main.js:680:19341)
    at y.R (https://assets.github.dev/insider/81725794264e4c0fddbc1b3b728013744ae90840/out/vs/workbench/workbench.web.main.js:2638:151851)
    at y.H (https://assets.github.dev/insider/81725794264e4c0fddbc1b3b728013744ae90840/out/vs/workbench/workbench.web.main.js:2638:146285)
    at l.value (https://assets.github.dev/insider/81725794264e4c0fddbc1b3b728013744ae90840/out/vs/workbench/workbench.web.main.js:2638:146030)
    at h.y (https://assets.github.dev/insider/81725794264e4c0fddbc1b3b728013744ae90840/out/vs/workbench/workbench.web.main.js:87:1902)
    at h.fire (https://assets.github.dev/insider/81725794264e4c0fddbc1b3b728013744ae90840/out/vs/workbench/workbench.web.main.js:87:2119)
    at n.add (https://assets.github.dev/insider/81725794264e4c0fddbc1b3b728013744ae90840/out/vs/workbench/workbench.web.main.js:2109:101906)
    at n.sb (https://assets.github.dev/insider/81725794264e4c0fddbc1b3b728013744ae90840/out/vs/workbench/workbench.web.main.js:2638:143259)
    at n.N (https://assets.github.dev/insider/81725794264e4c0fddbc1b3b728013744ae90840/out/vs/workbench/workbench.web.main.js:2638:132971)
    at https://assets.github.dev/insider/81725794264e4c0fddbc1b3b728013744ae90840/out/vs/workbench/workbench.web.main.js:2638:133465
```

```
ERR CodeExpectedError: ENOPRO: No file system provider found for resource 'vscode-vfs://github%2B7b2276223a312c22726566223a7b2274797065223a332c226964223a2234333534227d7d/microsoft/monaco-editor/package-lock.json'
    at n.j (VM58 workbench.web.main.js:655:14870)
    at async n.m (VM58 workbench.web.main.js:655:14962)
    at async n.readFileStream (VM58 workbench.web.main.js:655:19328)
    at async r.M (VM58 workbench.web.main.js:2223:42883)
    at async r.readStream (VM58 workbench.web.main.js:2223:42640)
    at async D.Cb (VM58 workbench.web.main.js:2212:61483)
    at async D.resolve (VM58 workbench.web.main.js:2212:59930)
    at async s.W (VM58 workbench.web.main.js:2223:39034)
    at async s.ib (VM58 workbench.web.main.js:1944:41953)
    at async Promise.all (/index 1)
```
Repository: rust
Issue: Missing comma in function arguments can result in a misleading diagnostic about missing arguments
Labels: A-diagnostics,T-compiler

### Code

```Rust
fn a(a: u64, b: u64, c: u64) { todo!() }

fn main() {
    let a_neat_first_argument = 42;
    let a_neat_second_argument_array_in_disguise = [42u8; 3];
    a(
        a_neat_first_argument,
        a_neat_second_argument_array_in_disguise.len() as u64
        &a_neat_second_argument_array_in_disguise as *const _ as u64,
    )
}
```


### Current output

```Shell
error[E0061]: this function takes 3 arguments but 2 arguments were supplied
  --> src/main.rs:6:5
   |
6  |       a(
   |  _____^-
7  | |         a_neat_first_argument,
8  | |         a_neat_second_argument_array_in_disguise.len() as u64
9  | |         &a_neat_second_argument_array_in_disguise as *const _ as u64,
10 | |     )
   | |_____- an argument of type `u64` is missing
   |
note: function defined here
  --> src/main.rs:1:4
   |
1  | fn a(a: u64, b: u64, c: u64) { todo!() }
   |    ^ ------  ------  ------
help: provide the argument
   |
6  ~     a(a_neat_first_argument, a_neat_second_argument_array_in_disguise.len() as u64
7  +         &a_neat_second_argument_array_in_disguise as *const _ as u64, /* u64 */)
   |
```


### Desired output

Admittedly a long shot, but a suggestion to add a comma after `a_neat_second_argument_array_in_disguise.len() as u64` would be neat if we were able to somehow make sense out of this.

### Rationale and extra context

This is pretty hard one to do something about – the second argument is actually a valid expression even with the missing comma. However the layout of the code is screaming "TWO SEPARATE ARGUMENTS HERE" no matter how you look at this. Not to mention the missing comma can be pretty hard to spot, so the user may be left counting the arguments and trying to understand how in the world Rust counts 2 rather than 3 here.

### Other cases

_No response_

### Rust Version

```Shell
1.77.0-nightly (2024-02-01 bf3c6c5bed498f41ad81)
```


### Anything else?

_No response_
Repository: PowerToys
Issue: With *large* SVG file preview (ditto thumbnails) needs to either a) timeout or  b) ignore if over some size threshold
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

File Explorer: Preview Pane

### Steps to reproduce

Try to preview (or get a thumbnail) of a rather large SVG.  (see attached example .svg.   I have some that are even larger)

FYI:  Process explorer is reporting that "PowerToys.SvgPreviewHandler..."  is using 2.8GBs of working set (and > 3GB of private) when it tries to render a 123MB file which may also be part of the cause.

FWIW I have a number of machine generated SVGs  which a part of on going research. The larger ones are admittedly "outliers", however, I'd rather not have to turn off  the SVG preview etc entirely since there are a lot of small examples that I'd still like to see in the file explorer window.


Would it be possible to  either 
1. add a check on the file size and set an upper-bound on supported file size be set  OR
2. (better) add a time out  on the render? 

If the above is triggered, then perhaps display a default image (eg "too large to display")

I've attached a zipped version of a 123M SVG generated from the well-known Stanford Dragon 3D model.
[dragon.zip](https://github.com/microsoft/PowerToys/files/14167332/dragon.zip)


### ✔️ Expected Behavior

I was hoping rather the system wouldn't grind to a (virtual) halt.  I'd be happy with a grey box or "too large" being displayed.

### ❌ Actual Behavior

File explorer can become unresponsive requiring it to either be killed (via task explorer) or a reboot.

### Other Software

_No response_
Repository: TypeScript
Issue: [Decorators] Missing error when calling `addInitializer` after that the decorator is done
Labels: Needs Investigation

### 🔎 Search Terms

decorators addInitializer error

### 🕗 Version & Regression Information

- This is the behavior in every version I tried since Stage 3 decorators where implemented


### ⏯ Playground Link

https://www.typescriptlang.org/play?#code/DYUwLgBAhgJjCSA7AlmZVjIF4gE4DFcB7AWwEYAuCAERAGMjcoxGBhIxMEADzAG0ARLAQo0GbHgEBdANwBYAFCKAZgFdEdNBwgx6ZABQB9KlEQBPADQRN3KrQZMWudpx5gAlBADeiiNDhIqOiYOATE5BAAvNZg3AB0woFiIXjyCgC+iirqmsjaunQATEYm5laGhaVmnj4KfomiwRJhpAb6npEAfN7p7r7WHADORKBxwEQA5voCAILU1ACi1AJ9GVkKdMBQg4MQM979AAIFhUcFZP3KRERREGRpmUoKQA

### 💻 Code

```ts
let addInitializerFrom1: DecoratorContext["addInitializer"];

function dec1(_: any, ctx: DecoratorContext) {
  addInitializerFrom1 = ctx.addInitializer;
}

function dec2(_: any, _2: any) {
  addInitializerFrom1(() => {})
  console.log("ADDED")
}

class A {
  @dec2
  @dec1
  foo = 1;
}
```


### 🙁 Actual behavior

The `addInitializerFrom1` call should throw

### 🙂 Expected behavior

`addInitializerFrom1` doesn't throw

### Additional information about the issue

Spec: https://ci.tc39.es/preview/tc39/ecma262/sha/59003ed603d09485b957a0f579b46697f49a96a6/#sec-applydecoratorstoelementdefinition

After that `dec1` is called, _decorationState_.[[Finished]] for the _decorationState_ relative to `dec1` is set to `false` and thus calling `addInitializer` should throw.
Repository: pytorch
Issue: torch_function objects passed as non-Tensor args should trigger overrides
Labels: triaged,module: __torch_function__,module: dynamic shapes

## Context

@soumith and I are investigating how to productionize torchdim. There are roughly two approaches:
- thread torchdim's new "Dim" object through C++
- re-implement torchdim using the torch_function mechanism

The second is lower effort (it is really difficult to add a new type to PYTorch), but has slower eager-mode performance. We would also need to change how torch_function works -- one can only use torch_function objects as arguments to Tensor inputs to torch.* operators. The rest of this issue assumes we take the latter approach.

thoughts? @zdevito @ezyang @albanD 

## Repro

```py
import torch

class Dim:
    @classmethod
    def __torch_function__(cls, func, types, args=(), kwargs=None):
        if kwargs is None:
            kwargs = {}
        return func(*args, **kwargs)

dim = Dim()
x = torch.randn(3)
torch.sum(x, dim)
```
gives
```
TypeError: sum() received an invalid combination of arguments - got (Tensor, Dim), but expected one of
 * (Tensor input, *, torch.dtype dtype)
 * (Tensor input, tuple of ints dim, bool keepdim, *, torch.dtype dtype, Tensor out)
 * (Tensor input, tuple of names dim, bool keepdim, *, torch.dtype dtype, Tensor out)
```

## Pitch

- torch_function objects can be marked as "tensor-like" or "anything goes". The "tensor-like" torch_function objects work like they do today: they may only be used in the place of Tensor arguments to torch APIs. The "anything goes" torch_function objects may be used in place of all arguments.
- At the extreme, this is like adding a schema to all torch APIs. For the codegenned torch.* APIs this is not difficult (we already have typing information), for the other torch.* ops there needs to be manual intervention.

cc @hameerabbasi @rgommers @peterbell10 @ezyang
Repository: flutter
Issue: Black screen when startup macOS app
Labels: platform-mac,a: desktop,has reproducible steps,P2,found in release: 3.16,found in release: 3.20,team-macos,triaged-macos

### Steps to reproduce

Just use the default empty Application template and debug (or release)

### Expected results

Fully loaded to show the window, and I don't want to see the black screen

### Actual results

Black screen for a while and load the content

By the way, I try the **Release Mode** or use command `flutter build macos`, but it still have black screen when startup, it’s just that the black screen time will be shorter

### Code sample

```dart
// ignore_for_file: prefer_const_constructors

import 'package:flutter/material.dart';
// import 'package:window_manager/window_manager.dart';

void main() async {
  runApp(const MainApp());
}

class MainApp extends StatelessWidget {
  const MainApp({super.key});

  @override
  Widget build(BuildContext context) {
    return const MaterialApp(
      home: Scaffold(
        body: Center(
          child: Text('Hello World!'),
        ),
      ),
    );
  }
}
```


### Screenshots or Video

https://github.com/flutter/flutter/assets/54197427/7bde3915-5bec-4c39-ad4e-aefc5ddac0ec

### Logs

```bash
Launching lib/main.dart on macOS in Debug mode...
```

### Flutter Doctor output

```bash
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.16.9, on macOS 14.2 23C64 darwin-x64, locale
    zh-Hans-CN)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] IntelliJ IDEA Community Edition (version 2023.2.4)
[✓] VS Code (version 1.86.0)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!
```
Repository: deno
Issue: Unexpected error from `addInitializer` called after decorator throws
Labels: bug,upstream,swc

Version: Deno 1.40.3

```js
let addInitializer;
function dec(_, ctx) { throw { addInitializer } = ctx; }
try { class A { @dec m() {} } } catch {}

addInitializer(() => {});
```

The `addInitializer(() => {})` call should not throw according to the proposal spec, but it does in Deno.
Repository: svelte
Issue: Sibling selectors does not work when passing style variables to a component, because of "display: contents;" element
Labels: feature request

### Describe the problem

When passing style variables to a component, svelte inserts a new root element with `display: contents`. At first, this seems like an elegant solution for scoping and setting style variables per component instance, but when using a sibling selector, the added parent DOM element, makes it so that components which are siblings in code, are no longer siblings when loading the page.

Then relying on the sibling selector is volatile when you have the option of passing style variables.

### Describe the proposed solution

I would like style variables to be slightly more integrated with a svelte component, as the current solution feels somewhat like an oversimplified workaround, which has this negative side effect. 

I guess my proposed easiest solution would be to be able to disable insertion of the new parent element which has `display: contents;`, for a given component. In this case the variables would be set on the first element in the component, leaving it up to the developer to have a component root element. 

Unless this is already possible in some way?

### Importance

would make my life easier
Repository: pytorch
Issue: load_inline should always recompile a kernel if it failed
Labels: module: cpp-extensions,triaged

### 🐛 Describe the bug

Repro in the real world here https://github.com/cuda-mode/lectures/blob/main/lecture3/pmpp.ipynb

If you try to load a kernel without ninja the load will fail but then if you `pip install ninja` and try to reload the kernel it will still fail. So instead I've noticed users are adding an `;` in source code to force a recompilation but that doesn't seem great

### Versions

A standard google colab instance

cc @malfet @zou3519
Repository: vscode
Issue: Debug Console filter with Go is difficult to use and inaccurate
Labels: bug,debug,debug-console

<!-- ⚠️⚠️ 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.86.0
- OS Version: Linux x64 6.5.0-15-generic

Steps to Reproduce:

1. Open a Go project that prints a good amount of debugging detail via log
2. Try to:
   - filter on specific text
   - select all
   - use the mouse to select with scroll
   - type in the filter box using ordinary text editing keys such as home, end
   - rerun the debugger with an active filter

Generally speaking the filter box malfunctions so much that it can't be used.

1. Filtering on specific text doesn't work. It will show lines that don't match the text. The "Showing x of y" is frequently out of sync with what is shown.
2. There's no reasonable way to copy the debug output (to paste it in a text document for example)
3. Using the mouse to select doesn't work. When the select mouse is outside of the window, the selection is lost. That's the main way to scroll, so it is very difficult to select when scrolling is required. There's no keyboard select support so no workaround.
4. The text editing box doesn't process home or end. Pressing end for example takes you out of the box. Pressing ctrl+home and ctrl+end seem to do what home and end should do.
5. Upon a rerun with an existing filter, the results are wrong. There are false positives, false negatives, inaccurate count of what's shown.
Repository: next.js
Issue: next/navigation useRouter hook fails in React Three Fiber Canvas component.
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://codesandbox.io/p/github/frankievx/francis-xavier-portfolio/main?file=%2Fsrc%2Fapp%2Flayout.tsx%3A19%2C6-20%2C11&workspaceId=25db4d3b-916c-4475-9db7-4f00c844610c

### To Reproduce

1. Double click the image in the center of the page.

### Current vs. Expected behavior

**Current Behavior**
User is navigated to the /tea page but encounters the dispatcher.use error.

**Expected Behavior**
User should navigate to the /tea page with an animation that will zoom the camera forward and no error or rerender of the component should occur.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.19
  pnpm: 8.14.0
Relevant Packages:
  next: 14.1.1-canary.27 // Latest available version is detected (14.1.1-canary.27).
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, Routing (next/router, next/navigation, next/link)

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context
<img width="732" alt="Screenshot 2024-02-05 at 11 42 23 AM" src="https://github.com/vercel/next.js/assets/12982201/8251eabf-187f-439c-b3e8-ce1e34065e27">


I've tried reverting my next version all the way to 13.5.6. I still encounter the error.

The router push line that causes this issue is found in /src/app/components/Frame.tsx:80.
Repository: PowerToys
Issue: PowerToys Run Input Smoothing Enhancement
Labels: Needs-Triage

### Description of the new feature / enhancement

### Allow Input Smoothing to show results after a certain time _every_ time after a character is written or deleted

## Current problems
Currently PowerToys Run waits a specified amount in milliseconds after Input is changed to display results. If the input is changed while PowerToys waits, this timer resets. Meaning, if one writes fast enough there won't be any results until one has finished typing.
It is already possible to set the delay to short delays or 0ms but this leads to white flickering when using dark mode and is also not recommended by the app.

## New feature
The new feature would update the results the specified amount of time after the input is changed, with a delay. After a character is typed or deleted, the search results that the current input string would lead to will be shown a specific time later, even if the input changes while waiting.

### Scenario when this would be used?

## Easier and faster searching
When searching, especially when using Windows search one often doesn't know what the best search string is. At times the desired result will even show up and be replaced by something ostensibly more "relevant" as one continues typing the exact name of what is searched. Results may also show up earlier than expected often with only two characters typed. In those cases it is unnecessary to type more than needed and seeing the desired results while still typing would save time.
When unsure of how exactly something is spelled or what it is called, seeing the results while typing may relieve one from waiting for the update timer to end.
## Faster access to results
Additionally you could already see how often you should tap the tab bar, arrow keys or where you should move your mouse while typing.

## Potential performance benefits
Although this has a higher processing cost I would expect people to type less, which may actually alleviate system load slightly.

### Supporting information


https://github.com/microsoft/PowerToys/assets/68426724/0250841e-1bc6-497d-81ad-3e84e8d03413
Repository: flutter
Issue: Native assets: visionOS support
Labels: c: new feature,platform-ios,tool,P3,team-ios,triaged-ios

Once we start work on having `flutter run` and `flutter build` support visionOS devices, we should also support native assets for visionOS.

Tracking bug for `flutter run` and `flutter build`:

* https://github.com/flutter/flutter/issues/129638

Prerequisites upstream for native assets:

* https://github.com/dart-lang/native/issues/961

We can't really start working for support on visionOS for native assets before `flutter run` and `flutter build` can target visionOS.

I'm happy to work on this once the prerequisite work has been done.
Repository: vscode
Issue: move to npm-run-all2 in dev scripts
Labels: tasks,debt

Since contributors can't modify `yarn.lock`, this is an issue to track what was #204251

Basically, npm-run-all is no longer actively maintained and there's now a better maintained `npm-run-all2` which is actually lighter, has security fixes, etc.

Would make sense to move across (many already have).

Low priority but should be an easy enough drop-in replacement (it is a direct fork)