sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Show both selection and semantic occurrences in the scrollbar
Labels: feature-request,editor-highlight

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

The scrollbar can only show markers for either semantic or selection-based occurrences of other text in the document. This depends on whether semantic occurrences are available for a document type or not. Semantic occurrences always have priority and disable the selection-based highlighting. This applies only to the scrollbar, all highlighting already exists in the editor itself.

There are two closed issues about this: #16042 (scrollbar) and #101552 (minimap). They were closed as "as designed". This issue is about changing that design.

The semantic occurrences are marked with a grey dot in the scrollbar. I've set up the colours in the editor to match those of Visual Studio, that is a warm grey.

The selection highlighting would also be marked with a grey dot in the scrollbar. I've set up the colours in the editor to match those of Notepad++ (and also [my similar extension for Visual Studio](https://marketplace.visualstudio.com/items?itemName=ygoe.SelectionTodoHighlighter) that already does the scrollbar highlighting), that is a light green.

It would be great to use both types of highlighting in the scrollbar. Each with their own colour to match that in the editor. Both colours need their own settings key to adjust them and tell the markers apart.

Because semantic highlighting often fails or cannot work at all. In plain JavaScript files, many symbols are unknown and cannot be understood by the editor alone. And when looking for text that isn't even a symbol, like strings or comments, semantic highlighting can never work anywhere. This is when selection highlighting comes in. It's not an either-or, it's a both. One must not suppress the other, even less so when the suppressing one itself has nothing to say while the other would be helpful; both must coexist. I use these selection highlights a lot to navigate my code. In Notepad++ I have to scroll to find other occurrences. Showing them in the scrollbar is a lot healthier for the hands because I don't need to scroll so much. So simply saying it wasn't designed like this isn't enough. If the design fails, it needs to be changed. That's the purpose of this issue.

If it doesn't work to show both at the same time, I'd still prefer the selection highlighting, and then also in a specific colour for selection highlights in the editor (green in my case). Semantic occurrenses can always be seen when not selecting anything. But with a non-empty selection, a stronger indication was made by the user to prioritise searching for exactly this, not something the editor *thinks* it recognises.
Repository: vscode
Issue: Copy vscode.dev Link for modified documents
Labels: feature-request,github

Testing #153319

* Clone a repository from github
* Add some empty lines at the beginning of a file
* Copy vscode.dev link for a line at the end of the file (or copy a link for a newly added line)
* Notice how the selection does not match / the newly added line is not available

Expected outcome: Show an error message.
Repository: vscode
Issue: Git - git.terminalGitEditor should return focus to the terminal after being closed
Labels: git,polish

Testing #153366

We do this when you run `code --wait <file>` which I think was added specifically for manually setting up the git editor for the terminal. 

![Recording 2022-06-28 at 07 31 41](https://user-images.githubusercontent.com/2193314/176205449-c9f03fda-e1fb-4d2a-bc41-6282361693d2.gif)
Repository: vscode
Issue: Git - Should focus return to the SCM view after closing COMMIT_EDITMSG?
Labels: git,polish

Testing #153366

Same as https://github.com/microsoft/vscode/issues/153499 but for the SCM view, should focus return to the text area after saving and closing the commit message such that publish branch is easily accessible via the keyboard?
Repository: vscode
Issue: Git - Support line length warnings in editor
Labels: feature-request,git

Testing #153366

This is functionality that is lost in the editor vs the SCM textarea:

![image](https://user-images.githubusercontent.com/2193314/176208536-22ed5343-29c8-4f7c-820c-b6fccdad534b.png)
Repository: vscode
Issue: Git - Show Banner To Close The File To Continue
Labels: feature-request,git,ux

Testing #153317

![image](https://user-images.githubusercontent.com/2931520/176209760-c6f54902-288d-4d00-9f11-a31de556f6d6.png)

This Banner:
![image](https://user-images.githubusercontent.com/2931520/176209919-009bf4cc-7f54-4400-9891-b7134d32cfa5.png)

Could have a text "Close this file to commit"
Repository: next.js
Issue: when i setting exportPathMap in next.config.js, dynamic route will not working
Labels: bug

### Verify canary release

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

### Provide environment information

 Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 16.15.1
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.1.7-canary.52
      eslint-config-next: 12.1.6
      react: 18.2.0
      react-dom: 18.2.0

### Which example does this report relate to?

https://github.com/uxin603s/next_dynamic_bug

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

_No response_

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

next dev

### Describe the Bug

next.config.conf setting exportPathMap
![image](https://user-images.githubusercontent.com/7101286/176203920-23d41578-f155-440a-9dd8-cf6f7ec1c051.png)
make a dynamic route page,it 's named [id].js
![image](https://user-images.githubusercontent.com/7101286/176208785-9f006d56-2700-488d-b2d4-63e4d5095ff5.png)
dynamic route not working↓
![image](https://user-images.githubusercontent.com/7101286/176209127-c8a5cd27-c5f8-4060-9cb7-c3c3a5b34734.png)
dynamic route working↓
![image](https://user-images.githubusercontent.com/7101286/176209258-38acf284-1850-4db7-99f2-3a1826881bc8.png)




### Expected Behavior

route dynamic id=1 will working↓
![image](https://user-images.githubusercontent.com/7101286/176209258-38acf284-1850-4db7-99f2-3a1826881bc8.png)

### To Reproduce

https://github.com/uxin603s/next_dynamic_bug
Repository: vscode
Issue: Replacing with capture groups writes the first match's values to all matches in that line
Labels: bug,search,confirmed

Issue Type: <b>Bug</b>

When using [Search and Replace](https://code.visualstudio.com/docs/editor/codebasics#_search-and-replace) (haven't tested with find and replace), it seems that when a given line contains multiple matches and the replacement string uses capture group tokens, the replacement operation only writes values from the groups of the *first* match (meaning *all* the matches get the values captured from the *first* match).

Example:
- regex: `(=|%3D)(?=\d\d\d\d)`
- replacement string: `$1%2B`
- input:
```
plainkey=1234,urlkey%3D1234
urlkey%3D1234,plainkey=1234
```

- expected output after replace:
```
plainkey=%2B1234,urlkey%3D%2B1234
urlkey%3D%2B1234,plainkey=%2B1234
```
- actual output after replace:
```
plainkey=%2B1234,urlkey=%2B1234
urlkey%3D%2B1234,plainkey%3D%2B1234
```

----

VS Code version: Code - OSS 1.68.1 (30d9c6cd9483b2cc586687151bcbcd635f373630, 2022-06-16T08:22:04.269Z)
OS version: Linux x64 5.18.5-arch1-1
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 7 PRO 5850U with Radeon Graphics (16 x 1900)|
|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: disabled_off<br>opengl: enabled_on<br>rasterization: disabled_software<br>raw_draw: disabled_off_ok<br>skia_renderer: enabled_on<br>video_decode: disabled_software<br>video_encode: disabled_software<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|1, 1, 1|
|Memory (System)|30.19GB (3.93GB free)|
|Process Argv|--unity-launch|
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|undefined|
|XDG_CURRENT_DESKTOP|undefined|
|XDG_SESSION_DESKTOP|undefined|
|XDG_SESSION_TYPE|undefined|
</details>Extensions: none
<!-- generated by issue reporter -->
Repository: vscode
Issue: Edit sessions - staged files not maintained
Labels: feature-request,scm,continue-working-on

Testing #153386

1. Open a folder/workspace that contains a git repository
2. Edit multiple files in the folder/workspace
3. Stage one of the files that were edited
4. Create an edit session
5. Open the same folder/workspace on a separate machine
6. Restore the latest edit session
    - All files appear in the list of changes
    - No files appear in the list of staged changes
Repository: TypeScript
Issue: Type where type of second tuple item is dependent on the type of the first doesn't get filtered completion lists after the first item has been entered
Labels: Suggestion,Help Wanted,Domain: Completion Lists,Experience Enhancement

# Bug Report

### 🔎 Search Terms

recursive
tuples
the joint type

### 🕗 Version & Regression Information
"typescript": "4.6.4"

### ⏯ Playground Link
[Playground link with relevant code](https://www.typescriptlang.org/play?ts=4.5.0-dev.20211020#code/FAFwngDgpgBAkiKBbGBeGBvYMYEMBcm2OMARoQEwDcxOAxoaQPZMA2UuAdjTgL48wAJoSwkYUQgGZivYgDNCARhqzQkWAHEoIANJQwAZwA8AFQB8aIjgDaOmAEtOMANb6mcmCYC6hWwBoYADpggAoTWy9xAA9ETkEDGCZSACsoOhAYAH4YLV19Y3CdLwtfLwBKL2Bea1cwd09KtWhPJlMLdFEHOKgowly9QzaqGAB6EZgAGRZnRwBzGDkmACcAd1wlwRgQJhhrAHJcPYC90j3IgB9dg6OYPbozmEv9wRu9qAenvbkzquBgOiYnAMGSSyUIJlaCGQ7SsXUEPV8exex3eXgCYxgAAV1rgkNooEsYBQsUsmEgIBlSI8YHRqbBLh4AKJRaDpKCbbYwCCk8kZKBVIA)

### 💻 Code


```ts

type Item = {
  a: {
    b: 2;
    c: boolean;
  };
  d: {
    e: 3
  }
  f: 1;
}

type GetKeys<T> = {
  [K in keyof T]: [K, ...(T[K] extends object ? GetKeys<T[K]> : [])]
}[keyof T]

type To<T> = {
  index: GetKeys<T>; // Looking forward to ['a', 'b'] | ['a', 'c'] | ['d', 'e'] | ['f']
}

const obj: To<Item> = {
  index: ['d', 'e'], // Parameter 2 Prompt b | c | e | f Expected to prompt e
}

```

### 🙁 Actual behavior

obj.index Parameter 2 Prompt b | c | e | f 

### 🙂 Expected behavior

Expected to prompt e
Repository: pytorch
Issue: Revisit OpInfo samples for nn.functional.max_poolNd
Labels: module: nn,triaged,actionable,module: pooling,module: testing

As mentioned [here](https://github.com/pytorch/pytorch/issues/80314#issuecomment-1168426818), the `nn.functional.max_poolNd` OpInfo entries test input combinations extensively, resulting in long test run times. From the times reported [here](https://observablehq.com/d/b95f7b67261147ba), they appear to be within the top 15 longest running tests:

```
TestOps.test_dtypes_nn_functional_max_pool1d_cuda    45.902 sec
TestOps.test_dtypes_nn_functional_max_pool2d_cuda    61.708 sec
TestOps.test_dtypes_nn_functional_max_pool3d_cuda    27.613 sec
```

We should revisit these OpInfo entries and consider reducing the number of samples to bring down these test times.

cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345 @saketh-are
Repository: vscode
Issue: Git - should origin appear first in the list?
Labels: help wanted,feature-request,git,ux

Testing #153317

<img width="1324" alt="Screen Shot 2022-06-28 at 1 05 21 PM" src="https://user-images.githubusercontent.com/29464607/176241583-ab4864d3-9fdc-4d23-9777-7013a063bd2c.png">
Repository: go
Issue: x/vulndb: "no metadata for C" when computing derived symbols
Labels: NeedsInvestigation,vulncheck or vulndb

```
$ go run ./cmd/vulnreport fix reports/GO-2022-0417.yaml
2022/06/28 10:03:00 fix("reports/GO-2022-0417.yaml"): addExportedSymbols("github.com/containers/buildah", ""): packages.Load:
could not import C (no metadata for C)
invalid operation: cannot compare d.dh == nil (operator == not defined on untyped nil)
invalid operation: cannot compare c.ctx == nil (operator == not defined on untyped nil)
invalid operation: cannot compare key.k == nil (operator == not defined on untyped nil)
exit status 1
```

This is a report for the package `"github.com/containers/buildah"`; from the error, it looks like we have a problem with analyzing packages with a transitive C dependency.

See also #36547.
Repository: next.js
Issue: [next/jest] adds log message to Jest's JSON test result output
Labels: bug,linear: next

### Verify canary release

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

### Provide environment information

    Operating System:
      Platform: linux
      Arch: x64
      Version: #58~20.04.1-Ubuntu SMP Tue Jun 14 11:29:12 UTC 2022
    Binaries:
      Node: 16.13.2
      npm: 8.10.0
      Yarn: 1.22.18
      pnpm: 7.3.0
    Relevant packages:
      next: 12.2.0
      eslint-config-next: N/A
      react: 18.1.0
      react-dom: 18.1.0


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

_No response_

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

_No response_

### Describe the Bug

Next.js's "env" module seems to be injecting the following log line to the stdout output of `jest`:

```
info  - Loaded env from /some/path/to/.env
{"numFailedTestSuites":0,"numFailedTests":0,"numPassedTestSuites":8,"numPassedTests":30, ....}
```

The added log line breaks Jest's unit test result in JSON format, when it's called with the `--json` flag, which in turn causes problems with my build tools that try to parse the output.

### Expected Behavior

Jest's unit test JSON output should not be modified so it can be parsed

### Link to reproduction

https://github.com/tiguchi/jest-log-line

### To Reproduce

Run `npm test`, then open `output.json` in the project's base directory. The first line will be a log output line followed by Jest's test result.
Repository: vscode
Issue: Expose hiding/showing all comments in context menu of gutter 
Labels: feature-request,comments

Testing #153314

![image](https://user-images.githubusercontent.com/2644648/176251893-c00c9f5a-81dd-44dd-b067-206eed31524e.png)

Let me right click on the diamond to pull up a context menu that allows me to hide all/show all of the comments in this file. I still want to see the gutter so it's not the same as the TPI linked, but I think it'll help in quickly hiding all comments so I can focus on making changes to the code.
Repository: vscode
Issue: Delay when switching between settings sections
Labels: bug,perf,settings-editor

Testing #153351

1. In the VS Code workspace
2. Open settings and search `@id:editor.wordWrap @lang:markdown`
3. Click on `User [markdown]`
4. Then click to switch to `Workspace [markdown]`

**bug**

For me, there is a second or so long delay when switching between setting sections. Profiling suggests `onConfigUpdate @ settingsEditor2.ts:1157:16` is taking the bulk of this time:

<img width="332" alt="Screen Shot 2022-06-28 at 11 32 14 AM" src="https://user-images.githubusercontent.com/12821956/176256763-a59116b4-f634-4c55-82a6-b191b4e73598.png">
Repository: PowerToys
Issue: Space Around Zones - Different spacing options between apps vs the outer screen/taskbar border.
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

Ability to control spacing between zones separately than spacing between zones and screen edges and taskbar.

### Scenario when this would be used?

I utilize the spacing between zones, but currently that spacing also applies to the screen edges and taskbar.  I would prefer to have less spacing there (possibly even none), while keeping separation between actual zones.

### Supporting information

_No response_
Repository: rust
Issue: Unhelpful error message when using traits + duplicate libraries in tree
Labels: A-diagnostics,T-compiler,E-needs-mcve

When users have more than one copy of a dependency in their tree, trait resolution can give very unhelpful error messages,
typically of the form 

> error[E0277]: the trait bound `LookTransformPlugin: Plugin` is not satisfied

The user however will have provided their own implementation for this trait, but the version mismatch causes the traits to not line up.

Ideally, the error message should a) alert the user that they have duplicate dependencies in their tree (as is currently done for structs) b) declare which version of the crate each trait instance is coming from.
Repository: vscode
Issue: Allow merging from right to left with diff arrows view
Labels: feature-request,diff-editor

Testing https://github.com/microsoft/vscode/issues/25887

The arrows work for merging from the left hand to the right-hand file, that's great 👍 

However, there's no way to do the opposite. I was thinking I could alt or shift-click on the arrow (or at least have a context menu) to go the other direction, but I cannot.
Repository: flutter
Issue: build dashboard should show, for each shard, how many green builds since the last red
Labels: c: new feature,team,team-infra,P3,triaged-infra

It would be cool if, when hovering over the builder name, it showed how many green builds that builder has had since the last red build. I'm often interested in this if I'm interested if a failure i'm seeing is a known flake.
Repository: pytorch
Issue: Negative values still produced by torch.nn.functional.kl_div
Labels: high priority,module: nn,triaged

### 🐛 Describe the bug

## 🐛 Bug
Despite a fix in https://github.com/pytorch/pytorch/issues/32520, kl_div in torch.nn.functional still outputs negative values. 
## To Reproduce
Say we have outputs with the same values:
```python
a = torch.tensor([[1,2,3], [5.0, 5.0, 5.0]])
b = torch.tensor([[1,2,3], [5.0, 5.0, 5.0]])
torch.nn.functional.kl_div(torch.nn.functional.log_softmax(a, 1), torch.nn.functional.softmax(b, 1), reduction="none")
tensor([[ 0.0000e+00,  0.0000e+00, -1.9826e-08],
        [ 0.0000e+00,  0.0000e+00,  0.0000e+00]])
```
Or, say we have outputs with arbitrarily-chosen different values. https://github.com/pytorch/pytorch/issues/32520 attempts to resolve negative outputs by allowing for a target in log-space, however this has no effect here:
```python
a = torch.tensor([[1,2,3], [5.0, 5.0, 5.0]])
b = torch.tensor([[8,10,6], [5.0, 5.0, 5.0]])
torch.nn.functional.kl_div(torch.nn.functional.log_softmax(a, 1), torch.nn.functional.log_softmax(b, 1), reduction="none", log_target=True)
tensor([[ 0.0310,  1.0962, -0.0593],
        [ 0.0000,  0.0000,  0.0000]])
```
or with a log-space target:
```python
a = torch.tensor([[1,2,3], [5.0, 5.0, 5.0]])
b = torch.tensor([[8,10,6], [5.0, 5.0, 5.0]])
torch.nn.functional.kl_div(torch.nn.functional.log_softmax(a, 1), torch.nn.functional.softmax(b, 1), reduction="none")
tensor([[ 0.0310,  1.0962, -0.0593],
        [ 0.0000,  0.0000,  0.0000]])
```
## Expected Behavior
Outputs with values >= 0.

### Versions

pytorch==1.12.0 (same behavior in 1.8.2 LTS)
torchvision==0.13.0
cudatoolkit=11.3.1

cc @ezyang @gchanan @zou3519 @albanD @mruberry @jbschlosser @walterddr @kshitij12345 @saketh-are
Repository: PowerToys
Issue: I wish I could use doble click “Ctrl" key to activate PowerToys Run
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

I often use doble click  ”CMD“ key to activate Alfred in macos, and it has become a habit.
I hope to continue this habit when using PowerToys Run in Windows.

### Scenario when this would be used?

Every time I want to activate PowerToys Run.

### Supporting information

_No response_
Repository: godot
Issue: set_deferred() and call_deferred() on Area2D monitoring/monitorable reports collisions inconsistently
Labels: bug,topic:physics,topic:2d

### Godot version

3.5 rc5

### System information

Windows 11

### Issue description

I have 2 Area2D nodes, Area A and Area B. B is trying to detect if A entered it. B has `monitoring/monitorable` on to begin, while A has those off. In code, I set the `monitoring` and `monitorable` properties of A on within code, via a keypress. However, Godot recommends I use set_deferred for those to avoid any physics problems, so I do. 

The strange part is that the order which you set these seems to matter. Setting `monitorable` first *before* `monitoring` for A causes B to fire the `area_entered` signal. But setting `monitoring` before `monitorable` does not fire any signal.
I have tested multiple permutations of these and screenshotted which permutations fire an `area_entered` signal and which ones do not, including the use of call_deferred just to see if it behaves any differently.

![image](https://user-images.githubusercontent.com/45138063/176337488-990ae193-99dc-4e3f-9ec8-951c9cf6fd20.png)

The other strange thing is that this behaves differently on 3.4.4 stable. It does not fire `area_entered` in any of these permutations, which might be a symptom of a regression. I am not sure if this is correct behavior either, since it would make sense to me that an Area being enabled inside of another Area would count as "entering" that Area.

![image](https://user-images.githubusercontent.com/45138063/176337709-e92fc4d6-eb0b-442b-b368-6cc39cd88b07.png)


### Steps to reproduce

I set up a minimal reproduction project with 2 Area2Ds whose collision shapes are already intersecting each other. Area2D1 has its monitoring/monitorable properties turned off, while the Area2D2 has those enabled. 
Area2D2 will print "Area2D2 detected an area!" if it fires the `area_entered` signal.
I assigned different permuations of setting monitoring/monitorable to different keys to test which ones report collisions.
Pressing the following keys set monitoring/monitorable differently:

- 1 sets `monitorable` true, then `monitoring` true
- 2 sets only `monitorable` true
- 3 sets only `monitoring` true
- 4 sets `monitoring` true, then `monitorable` true
- 5 does call_deferred, which sets `monitorable` true, then `monitoring` true
- 6 does call_deferred, which sets `monitoring` true, then `monitorable` true
- Q sets `monitorable` false, then `monitoring` false
- W sets `monitoring` false, then `monitorable` false

### Minimal reproduction project

[TestCollision.zip](https://github.com/godotengine/godot/files/9006750/TestCollision.zip)
Repository: godot
Issue: Vulkan: Memory leak on `vkQueueSubmit()` on macOS
Labels: bug,platform:macos,topic:rendering,confirmed

### Godot version

v4.0.alpha10.official [4bbe7f0b9]

### System information

macOS Monterey 12.4(apple m1 pro 2020  16G)

### Issue description

![QQ20220629-0](https://user-images.githubusercontent.com/46029824/176340625-9412f0e6-8358-4b05-bb1a-4b222d0571ee.jpg)



### Steps to reproduce

1. open the software
2. create an empty item
3. wait for memory leak

### Minimal reproduction project

_No response_