sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [flutter_tools] iOS debugging dump not logged after 30 seconds
Labels: platform-ios,tool,team-tool

In https://github.com/flutter/flutter/pull/101763 I landed a change that will pause the Flutter app, have lldb dump a backtrace, and then resume the app after the tool has waited 30 seconds for the observatory URL to be logged. Note that the call to `pauseDumpBacktraceResume()` comes directly after the tool logs `'iOS Observatory not discovered after 30 seconds. This is taking much longer than expected...'` to STDERR.

However, in both:
1. https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20cubic_bezier_perf_ios_sksl_warmup__timeline_summary/2084/overview
2. https://ci.chromium.org/ui/p/flutter/builders/prod/Mac_ios%20flutter_gallery_ios__start_up/4207/overview

The test timed out after 30 minutes. However, in the former (1), we never see the STDERR log printed, even though the overall build times out after 30 minutes. This makes me think that maybe the tool was stuck.

```
[cubic_bezier_perf_ios_sksl_warmup__timeline_summary] [STDOUT] stdout: [ +123 ms] success
[cubic_bezier_perf_ios_sksl_warmup__timeline_summary] [STDOUT] stdout: [        ] Application launched on the device. Waiting for observatory url.
```

In the latter (2), we see the error log after 30 seconds, we send lldb the request to pause the app, however, this request times out after 20 seconds.

```
[flutter_gallery_ios__start_up] [STDOUT] stdout: [ +186 ms] success
[flutter_gallery_ios__start_up] [STDOUT] stdout: [        ] Application launched on the device. Waiting for observatory url.
[flutter_gallery_ios__start_up] [STDOUT] stderr: [+30004 ms] iOS Observatory not discovered after 30 seconds. This is taking much longer than expected...
[flutter_gallery_ios__start_up] [STDOUT] stdout: [   +8 ms] (lldb) process interrupt
[flutter_gallery_ios__start_up] [STDOUT] stdout: [+19998 ms] error: Failed to halt process: Halt timed out. State = running
```
Repository: pytorch
Issue: Depthwise Conv1d performance (a naive CUDA kernel is 10x faster)
Labels: module: cuda,triaged

### 🚀 The feature, motivation and pitch

Please improve the CUDA performance of Depthwise Conv1d :)

FYI, I write a naive CUDA kernel and it's already 10x faster than pytorch:

https://github.com/BlinkDL/RWKV-CUDA

RTX3090:
pytorch = fwd 14ms bwd 65ms
CUDA kernel v3 = fwd 0.8ms bwd 5.5ms

### Alternatives

_No response_

### Additional context

_No response_

cc @ngimel
Repository: terminal
Issue: Tab position is not restored for `restoreLastClosed` action
Labels: Help Wanted,Issue-Bug,Area-UserInterface,Product-Terminal,Priority-3

The problem with this is the tab position is not restored, if tab closed is first one, the restored tab is the last one.
the position should also be restored

_Originally posted by @swinder0161 in https://github.com/microsoft/terminal/issues/960#issuecomment-1098341305_


This might be tricky - we might be able to remember the location of the tab, but I'd expect it to work weird if the tabs get reordered before restoring the tab. This might be acceptable though.
Repository: vscode
Issue: Long output from remote machine freezes VSCode
Labels: bug,freeze-slow-crash-leak,confirmation-pending,terminal-process

Issue Type: <b>Bug</b>

1. Start VSCode
2. SSH to Linux machine
3. Run the following python script
```
import requests
print(requests.get("https://api.github.com/repos/iNavFlight/inav/releases").json())
```
4. The script should finish and print everything. Then the entire VSCode will freeze (and stop responding)

Sometimes I need to resize some parts of the window for it to freeze.
Sometimes I also get this popup that it stopped responding.
<details><summary>spoiler warning</summary>

![image](https://user-images.githubusercontent.com/24775036/163142074-3b9046eb-1232-4c48-8ed0-5f4c7cf1d67b.png)

</details>

Extension version: 0.78.0
VS Code version: Code 1.66.2 (dfd34e8260c270da74b5c2d86d61aee4b6d56977, 2022-04-11T07:46:01.075Z)
OS version: Windows_NT x64 10.0.19044
Restricted Mode: No
Remote OS version: Linux x64 5.4.166-1-pve

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-8086K CPU @ 4.00GHz (12 x 4008)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: enabled<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|undefined|
|Memory (System)|31.94GB (21.75GB free)|
|Process Argv|--disable-extensions --crash-reporter-id ca7d3459-126c-4192-afb9-ddbde83a055d|
|Screen Reader|no|
|VM|0%|

|Item|Value|
|---|---|
|Remote|SSH: 192.168.1.176|
|OS|Linux x64 5.4.166-1-pve|
|CPUs|AMD Ryzen 5 3600 6-Core Processor (12 x 2206)|
|Memory (System)|31.28GB (23.87GB free)|
|VM|0%|
</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyl392:30443607
pythontb:30283811
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscorecescf:30445987
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
vsc1dst:30438360
pythonvs932:30410667
wslgetstarted:30449410
pythonvsnew555:30457759
vscscmwlcmt:30465135
vscaat:30438848
pynewfile477:30463512

```

</details>

<!-- generated by issue reporter -->
Repository: TypeScript
Issue: Return namespan for constructor elements 
Labels: Bug,Help Wanted

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

- navTree
- Outline
- nameSpan

### 🕗 Version & Regression Information
4.7-beta

Not a regression

### 💻 Code

For the code:

```ts
export class TestClass {
    public constructor() { }
    public foo() { }
}

new TestClass().foo();
```

1. Look at the `navtree` response for the document and look at the entry for `constructor`

### 🙁 Actual behavior

The entry for `constructor` does not set a `nameSpan`:

```
"childItems": [
    {
        "text": "constructor",
        "kind": "constructor",
        "kindModifiers": "public",
        "spans": [
            {
                "start": {
                    "line": 2,
                    "offset": 5
                },
                "end": {
                    "line": 2,
                    "offset": 29
                }
            }
        ]
    },
    ...
]
```

### 🙂 Expected behavior

The entry should also set the `nameSpan` that covers the range of `constructor`

In VS Code, we use the namespan in a few different ways:

- Reference code lens
- Highlighting names within symbol ranges

Right now we have to compute the nameSpan ourselves. It would be better if TS could compute this for us
Repository: neovim
Issue: Lua function using `vim.schedule()` triggered on `CmdlineEnter` causes line-wrapped `input()` prompt to display incorrectly
Labels: bug,event-loop,display

### Neovim version (nvim -v)

NVIM v0.7.0-dev+1446-g18152cf6f

### Vim (not Nvim) behaves the same?

N/A

### Operating system/version

ArchLinux

### Terminal name/version

konsole 21.12.3

### $TERM environment variable

xterm-256color

### Installation

AUR

### How to reproduce the issue

1. `nvim --clean`
2. `:lua _G.on_cmdline_enter = function() vim.schedule(function() end) end`
3. `:autocmd CmdlineEnter * lua _G.on_cmdline_enter()`
4. `:lua vim.fn.input("Insert a really long text prompt that does not fit within a single line and thus causes the prompt to get wrapped around to the next line which triggers the bug with the first line of the input prompt being printed twice before the rest of the prompt")`


### Expected behavior

Prompt shows normally with each line only appearing once

### Actual behavior

Some wrapped lines from the beginning appear twice and then the rest of the lines appear normally

### Screenshot

![image](https://user-images.githubusercontent.com/29580810/163254293-ec5c3d0a-d664-4c83-a847-817d49d314e3.png)
Repository: TypeScript
Issue: Return namespan on default exports 
Labels: Suggestion,Help Wanted,Experience Enhancement

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

- navTree
- Outline
- nameSpan

### 🕗 Version & Regression Information
4.7-beta

Not a regression

### Related issues 
- #48674

### 💻 Code

For the code:

```ts
// index.ts
import bla from './index'

export default 123;
```

1. Look at the `navtree` response for the document and look at the entry for the export

### 🙁 Actual behavior

The entry for  the default export does not set a `nameSpan`:

```
[Trace  - 19:20:39.65] <syntax> Response received: getOutliningSpans (346). Request took 1 ms. Success: true 
Result: []
[Trace  - 19:20:39.117] <syntax> Sending request: navtree (347). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "/Users/matb/projects/san/index.ts"
}
[Trace  - 19:20:39.118] <syntax> Response received: navtree (347). Request took 1 ms. Success: true 
Result: {
    "text": "\"index\"",
    "kind": "module",
    "kindModifiers": "",
    "spans": [
        {
            "start": {
                "line": 1,
                "offset": 1
            },
            "end": {
                "line": 4,
                "offset": 21
            }
        }
    ],
    "childItems": [
        {
            "text": "default",
            "kind": "const",
            "kindModifiers": "export",
            "spans": [
                {
                    "start": {
                        "line": 4,
                        "offset": 1
                    },
                    "end": {
                        "line": 4,
                        "offset": 20
                    }
                }
            ]
        },
        {
            "text": "bla",
            "kind": "alias",
            "kindModifiers": "",
            "spans": [
                {
                    "start": {
                        "line": 2,
                        "offset": 8
                    },
                    "end": {
                        "line": 2,
                        "offset": 11
                    }
                }
            ],
            "nameSpan": {
                "start": {
                    "line": 2,
                    "offset": 8
                },
                "end": {
                    "line": 2,
                    "offset": 11
                }
            }
        }
    ]
}
```

### 🙂 Expected behavior
On the default export, a namespan is set for the span of `default`

This is something VS Code computes itself today. It helps us implement the references code lens
Repository: TypeScript
Issue: Different 'find all references' results on export default depending on trigger position
Labels: Bug,Help Wanted,Domain: Symbol Navigation

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

- find all references
- f12
- default export

### 🕗 Version & Regression Information
4.7-beta

Not a regression


### 💻 Code

For the code:

```ts
// index.ts
import bla from './index'

export default 123;
```


### 🙁 Actual behavior
1. Run `find all references` on `export`. Notice no results returned


```
[Trace  - 19:25:55.949] <semantic> Sending request: references (831). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "/Users/matb/projects/san/index.ts",
    "line": 4,
    "offset": 2
}
[Trace  - 19:25:55.952] <semantic> Response received: references (831). Request took 3 ms. Success: true 
Result: {
    "refs": [],
    "symbolName": "export",
    "symbolStartOffset": 1,
    "symbolDisplayString": "(property) default: 123"
}
```


1. Now Run `find all references` on `default`. Notice the two correct references are returned


```
[Trace  - 19:26:16.509] <semantic> Sending request: references (837). Response expected: yes. Current queue length: 0
Arguments: {
    "file": "/Users/matb/projects/san/index.ts",
    "line": 4,
    "offset": 11
}
[Trace  - 19:26:16.511] <semantic> Response received: references (837). Request took 2 ms. Success: true 
Result: {
    "refs": [
        {
            "file": "/Users/matb/projects/san/index.ts",
            "start": {
                "line": 4,
                "offset": 8
            },
            "end": {
                "line": 4,
                "offset": 15
            },
            "contextStart": {
                "line": 4,
                "offset": 1
            },
            "contextEnd": {
                "line": 4,
                "offset": 20
            },
            "lineText": "export default 123; ",
            "isWriteAccess": true,
            "isDefinition": true
        },
        {
            "file": "/Users/matb/projects/san/index.ts",
            "start": {
                "line": 2,
                "offset": 8
            },
            "end": {
                "line": 2,
                "offset": 11
            },
            "contextStart": {
                "line": 2,
                "offset": 1
            },
            "contextEnd": {
                "line": 2,
                "offset": 26
            },
            "lineText": "import bla from './index'",
            "isWriteAccess": true,
            "isDefinition": false
        }
    ],
    "symbolName": "default",
    "symbolStartOffset": 8,
    "symbolDisplayString": "(property) default: 123"
}
```

### 🙂 Expected behavior
I think both cases should return the same references
Repository: terminal
Issue: Terminal doesn't detect developer command prompt on ARM64
Labels: Issue-Bug,Product-Terminal,Tracking-External

### Windows Terminal version

1.12.10733.0

### Windows build number

10.0.22000.613

### Other Software

Visual C++ Build Tools 2022 17.1.4

### Steps to reproduce

* Install Visual C++ Build Tools 2022 on Windows 11 ARM64
* Install Windows Terminal 1.12
* Run Windows Terminal

### Expected Behavior

There are profiles for Developer Command Prompt and Developer PowerShell for VS2022 in Terminal.

### Actual Behavior

There are no such profiles.
Repository: material-ui
Issue: [Backdrop] Stuck open at 0% opacity and blocks all clicks on the page due to react-transition-group bug
Labels: bug 🐛,external dependency,component: backdrop

### Current behavior 😯

backdrop should always unmount when animation is done

### Expected behavior 🤔

backdrop gets stuck open, blocks interaction with page

### Steps to reproduce 🕹

Honestly it is hard to replicate. Turn on strict mode and interact with the Menu rapidly, or hack the code to unmount & re-mount with the "existing" state when `onExit` fires but before `onExited`

### Context 🔦

Please see this issue where I have done detailed work to isolate and write up what the issue is.
https://github.com/reactjs/react-transition-group/issues/817

As shown here it gets stuck with `in={false}` and `EXITING`, it does not ever goto `EXITED` and unmount, from my user's perspective the whole app is crashed/frozen and they need to reload the page now.
![Screen Shot 2022-04-13 at 11 55 48 AM](https://user-images.githubusercontent.com/97546767/163265629-48504b8f-4b64-42d1-878f-ac7178ca5221.png)

This is because `onExited` fails to fire, due to race conditions, and it never hits here https://github.com/mui/material-ui/blob/master/packages/mui-base/src/PopperUnstyled/PopperUnstyled.js#L202-L204

### Your environment 🌎

Chrome, but it's irrelevant based on what I understand about this bug

<details>
  <summary>`npx @mui/envinfo`</summary>

```

  System:
    OS: macOS 11.6.4
  Binaries:
    Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
    Yarn: 1.22.17 - ~/.nvm/versions/node/v16.14.0/bin/yarn
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.2/bin/npm
  Browsers:
    Chrome: 100.0.4896.88
    Edge: Not Found
    Firefox: Not Found
    Safari: 15.4
  npmPackages:
    @emotion/react: ^11.7.1 => 11.8.1 
    @emotion/styled: ^11.6.0 => 11.8.1 
    @mui/base:  5.0.0-alpha.70 
    @mui/icons-material: ^5.3.1 => 5.4.4 
    @mui/lab: ^5.0.0-alpha.66 => 5.0.0-alpha.71 
    @mui/material: ^5.3.1 => 5.4.4 
    @mui/private-theming:  5.4.4 
    @mui/styled-engine:  5.4.4 
    @mui/system: ^5.4.0 => 5.4.4 
    @mui/types: ^7.1.0 => 7.1.2 
    @mui/utils: ^5.3.0 => 5.4.4 
    @types/react: 17.0.30 => 17.0.30 
    react: ^18.0.0 => 18.0.0 
    react-dom: ^18.0.0 => 18.0.0 
    styled-components: 5.3.3 => 5.3.3 
    typescript: ~4.4.3 => 4.4.4 
```
</details>
Repository: TypeScript
Issue: Improve `https` import support for `node` 16 and beyond
Labels: Suggestion,In Discussion,Domain: node

[Node now has flagged support for `https` imports.](https://github.com/nodejs/node/pull/36328) At least with flags, this support is supposed to be backported to node 16. It has some unique features which need some special coding in TS:
* Only `https` and `http` loopback imports are allowed within a `http[s]` imported file (unsure if these can be cross-origin or not - I think they can be right now, but that may be subject to change). This means no direct visibility for node builtins or `node_module`s within these files!
* Potential on-disk cache for offline use - the current implementation does not download to a cache, but it's possible or likely that imported modules will be cached to either `node_modules/.https` or something like `web_modules` so the compilation can be done offline. This is still in flux.

Those indicate changes we may need to make specific to node, and will need to track node closely. Beyond that, our URL handling is crusty, so could use some improvements in general:
* Detection of loopback URLs to treat the same same as `file://localhost/` is today (as a project-local lookup).
* No longer mistakenly looking up URLs on disk (as discovered by @amcasey )
* ATA for URL-fetched files (including the ability to specify where a declaration file is for a js file within the js file itself, similar to `sourceMappingUrl`, without abusing `reference type` syntax like `deno` does)

This is probably a good time to reflect on how we handle URLs - we haven't made them a priority in years from what I know - not since `module: commonjs` became our default mode. Given that, there's probably other edges around URL handling we could sand off - like making `paths` mappings for URLs less cumbersome.
Repository: TypeScript
Issue: `this` does not appear in autocomplete when certain JSDoc annotations are present
Labels: Bug,Help Wanted,Domain: Completion Lists

<!-- ⚠️⚠️ 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.66.2
- OS Version: Windows 10 Pro 21H1

Steps to Reproduce:

1. Open a new file with the language parser type set to "JavaScript"
2. Create an empty class like the following:
```js
class Test {
    constructor() {
        this.callback = null;
    }
}
```
3. Begin typing "this", note that the `this` keyword shows up in the autocomplete as expected.
![test1](https://user-images.githubusercontent.com/10872887/163265632-17bd5395-c95a-4df4-be79-74d65105f8cd.gif)
4. Add a JSDoc annotation to any element in the class containing a type definition of `function` with `this` set to some specific type:
```js
class Test {
    constructor() {
        /** @type {function(this: HTMLElement)} */
        this.callback = null;
    }
}
```
4. Begin typing "this", note that the keyword for `this` no longer appears, VSCode autocorrects to `globalThis` instead.
![test2](https://user-images.githubusercontent.com/10872887/163267071-3bde5eda-5513-45de-870a-8e8a415c9050.gif)

Notes:
This seems to occur no matter where the JSDoc comment is in the file. Here it is with it in a `@param` tag on a class method:
![test3](https://user-images.githubusercontent.com/10872887/163267178-5ae5a8ed-7f79-4601-b04e-39a0237103a8.gif)

I could be making incorrect JSDoc syntax, but I have my doubts, as this syntax throws no errors and gives me proper Intellisense for `this` when I create my callback functions when calling a method like the above with an inline function definition, which is what I wanted.
Repository: storybook
Issue: `@storybook/theming` does not work with Next.js
Labels: bug,theming

**Describe the bug**

1. Create new Next.js project
   - I also tested these steps in a fresh CRA project, which does not produce the error
2. Add `@storybook/theming@6.5.0-alpha.31` or later
   - `@storybook/theming@6.5.0-alpha.30` or earlier does not produce the error (see commit history)
3. Use within project
4. Run `yarn dev` or `yarn build`

Here's the error:

![Screenshot of error](https://github.com/kylegach/storybook-theming-bundling-bug-2/raw/main/Error.png)

**To Reproduce**

https://github.com/kylegach/storybook-theming-bundling-bug-2

**System**

<details>
<summary>Output</summary>

```
  System:
    OS: macOS 12.3
    CPU: (8) arm64 Apple M1 Pro
  Binaries:
    Node: 16.13.2 - ~/.nvm/versions/node/v16.13.2/bin/node
    Yarn: 3.2.0 - ~/.nvm/versions/node/v16.13.2/bin/yarn
    npm: 8.1.2 - ~/.nvm/versions/node/v16.13.2/bin/npm
  Browsers:
    Chrome: 100.0.4896.88
    Firefox: 98.0
    Safari: 15.4
  npmPackages:
    @storybook/theming: 6.5.0-alpha.31 => 6.5.0-alpha.31
```

</details>

**Additional context**

I think these links are relevant:

- Release: https://github.com/storybookjs/storybook/compare/v6.5.0-alpha.30...v6.5.0-alpha.31
- PR: https://github.com/storybookjs/storybook/pull/17000