sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: editor.selectionClipboard option has no effect on vscode.dev
Labels: bug,editor-clipboard

<!-- ⚠️⚠️ 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: Ubuntu 22.04

Steps to Reproduce:

1. Set `editor.selectionClipboard` to `False` in the settings.
2. Create a new empty text file.
3. Write some text.
4. Select the text.
5. Middle click.

In the desktop app, changing the setting affects the behavior, however in vscode.dev in a Chromium browser, the setting has no effect.

Desktop app working as expected:

[vokoscreenNG-2023-04-27_11-37-47.webm](https://user-images.githubusercontent.com/963645/234931114-12b84acb-7c06-47a4-ace1-a23e30d0c640.webm)

Web app (vscode.dev) not working as expected:

[vokoscreenNG-2023-04-27_11-40-48.webm](https://user-images.githubusercontent.com/963645/234931646-24bb37ff-8433-41f1-9aae-750ee943feef.webm)
Repository: vscode
Issue: Web support for sovereign aka national/gov clouds e.g. Mooncake, DoD
Labels: feature-request,microsoft-authentication

Continuation of https://github.com/microsoft/vscode/issues/162539 but for the web.
Repository: vscode
Issue: Codespaces open documentation link: Error: The file is not displayed in the text editor because it is a directory.
Labels: bug,remote-explorer

From verifying: [179298](https://github.com/microsoft/vscode/issues/179298)

Type: <b>Bug</b>

1. Open a codespace
2. Quickly in the remote explorer, click on the `read documentation` option

**Bug**
A new editor opens that shows:

```
Error: The file is not displayed in the text editor because it is a directory.
```

 
<img width="2160" alt="Screenshot 2023-04-27 at 10 16 42 AM" src="https://user-images.githubusercontent.com/12821956/234940415-0d112954-9f9e-4eff-bd3b-e8a560ed2234.png">


VS Code version: Code - Insiders 1.78.0-insider (Universal) (d6290ef6582acecbf3bca1558111f2ee64375801, 2023-04-27T05:23:32.446Z)
OS version: Darwin x64 22.4.0
Modes:
Sandboxed: Yes
Remote OS version: Linux x64 5.4.0-1105-azure

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz (16 x 2400)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>metal: disabled_off<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|5, 4, 3|
|Memory (System)|32.00GB (1.09GB free)|
|Process Argv|--crash-reporter-id 48781ca2-1705-4f64-9bab-325055aab55d|
|Screen Reader|no|
|VM|0%|

|Item|Value|
|---|---|
|Remote|Codespaces|
|OS|Linux x64 5.4.0-1105-azure|
|CPUs|Intel(R) Xeon(R) Platinum 8370C CPU @ 2.80GHz (2 x 2793)|
|Memory (System)|3.84GB (2.01GB free)|
|VM|0%|
</details>
<!-- generated by issue reporter -->
Repository: go
Issue: x/tools/gopls: move analyzers to an extensible sidecar
Labels: Thinking,FeatureRequest,gopls,Tools,Analysis,gopls/analysis

We've talked a lot about how users can extend the set of analyzers that gopls runs so it can include org-specific checkers. Historically the challenge was that users would have to re-build gopls with the extended set of analyzers (which is not difficult but is inconvenient), or gopls would have to communicate with a separate process that contains the analyzers, which means it would have to do type checking yet again. (gopls already does--and must do--type checking of each package twice: once for its main index, and again for analysis.) But today @findleyr pointed out that, as of v0.12.0, there's no real efficiency reason not to move all of gopls' analysis into the sidecar process, so that the net number of invocations of the type checker is unchanged.

In essence, gopls would fork+exec a long-lived child process and communicate with it over a pipe. (The child process wouldn't need any other capabilities.) A request would send the metadata, source files, facts, and export data required to analyze a package, and the child would do the work and return serialized facts and diagnostics over the pipe. By default the child program would be a mode of gopls itself (e.g. 'gopls analyze'), but users could specify an alternative program that implements the same interface, analogous to the way 'go vet -vettool=...' runs an alternative unitchecker-based tool.

This approach still requires the user to build an executable containing both gopls code (the driver and core analyzers) and user code (their analyzers), but this could be done automatically by gopls: it would generate a main file from the user's configuration and then execute it, a bit like 'go test'. But perhaps this approach (and the potential for version skew of both the go toolchain and the gopls source) is more complex than the simple "re-build" approach.  Something to think about.
Repository: godot
Issue: CSG polygons stop following their set path node when removed and re-added to the scene
Labels: bug,topic:core,topic:3d

### Godot version

4.0.2.stable.mono

### System information

Kubuntu 22.04

### Issue description

I am working with some CSGPolygon3Ds, which follows paths that change sometimes.

For optimization purposes, it gets converted to a MeshInstance whenever the path isn't supposed to change. To do so, the CSGPolygon3D child is removed and a converted MeshInstance is added.

The problem is, when the opposite has to be done (adding the CSG back) it simply stops following the path.

The video below shows what happens:

[csg_path_bug.webm](https://user-images.githubusercontent.com/60024671/234949628-2b0c28f7-0bc7-4f2b-86f2-693dd87fc158.webm)

The moment two of the polygons stop moving is because all of them were removed and quickly re-added. One still works due to a workaround.

### Steps to reproduce

1. Create a Path3D node that moves its points;
2. Create a few CSGPolygon3D nodes that follow it;
3. During runtime, remove them from the scene and quickly add back;
4. The polygons will stop following the path.

> By setting the polygon mode to Path through a script (even if it is already Path), it returns to normal behavior.

### Minimal reproduction project

A workaround can be seen on the project:

[CSG_reparent_movement_bug.zip](https://github.com/godotengine/godot/files/11346548/CSG_reparent_movement_bug.zip)

(press Space or Enter to trigger the bug)
Repository: godot
Issue: autocomplete on call argument sometimes fail when no object is available
Labels: bug,topic:gdscript,topic:editor,confirmed

### Godot version

master (240ed28291)

### System information

windows 11

### Issue description

when trying to autocomplete the argument of a function call and it can't find an associated object it won't autocomplete.
I found two case where he might not found an object first it can be if the scene is not opened or if referencing a node from a node path

In both cases i tested to autocomplete the first parameter of `emit_signal`. Might be only related to it.





```gdscript
extends Node2D

@export var path : NodePath
@onready var target : Node2D = get_node(path)

func _ready():
	target.emit_signal()

```

### Steps to reproduce

- copy paste the script above
- set the `NodePath `to some `Node2D`
- try to autocomplete something it will work
- try to autocomplete the first argument of `emit__signal` it won't work

### Minimal reproduction project

N/A
Repository: rust
Issue: Test `x.py install` in CI
Labels: A-testsuite,T-bootstrap

Sometimes it's pretty broken without anyone noticing because it's not tested.

For example, #110906 was broken
Repository: TypeScript
Issue: JSDoc type aliases aren't parsed or bound at the end of blocks
Labels: Suggestion,Awaiting More Feedback,Domain: JSDoc

# Bug Report

Followup to #54037 and #53624 
This is not a regression, and fixing it would require 

- the parser to check for jsdoc before each close brace
- the ast to store optional jsdoc on each close brace, and store the close brace on each block
- the binder to visit each close brace to check for jsdoc to bind

So I think it's too expensive for a feature that nobody has noticed missing until recently.

### 🔎 Search Terms

JSDoc type alias ignored

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### 💻 Code

```js
// @filename: typedefAtEndOfBlock.js
// @checkJs: true
// @outdir: dist
// @declaration: true
function f() {
  /* @type {A} */
  var a = 2
  /** @typedef {string} A */
}
{
  /* @type {B} */
  var b = 2
  /** @typedef {string} B */
}
export class Class {
  /* @type {C} */
  c = 1
  /** @typedef {string} C */
}
const Dlass = class {
  /* @type {D} */
  d = 1
  /** @typedef {string} D */
}
```

### 🙁 Actual behavior

None of the typedefs are parsed or bound.

### 🙂 Expected behavior

The typedefs are parsed and bound.
(And none are visible outside their containers, which is not true for classes right now).
Repository: godot
Issue: Tilemap rendering incorrectly when positioned exactly on .5
Labels: bug,topic:rendering,needs testing,topic:2d

### Godot version

v4.0.2.stable.official [7a0977ce2]

### System information

Windows 11

### Issue description

When using typical settings for obtaining pixel-perfect rendering (texture filter nearest, stretch mode viewport), tilemaps do not render correctly when they (or the camera) are exactly positioned on a half-pixel (e.g. 0.5). Looks like the left-most column is duplicated and the right-most column is cut off. Only tested for a horizontal .5 coordinate.


https://user-images.githubusercontent.com/51884888/234953179-581a33e9-73e3-4cc0-a6e6-10aa57c88686.mp4



### Steps to reproduce

Set up new project with a tilemap. Build a simple tilemap. Set texture filter to nearest and stretch mode viewport. Make resolution very small to make issue more apparent.

### Minimal reproduction project

[tilemap_rendering.zip](https://github.com/godotengine/godot/files/11346653/tilemap_rendering.zip)
Repository: flutter
Issue: x86_64 iOS simulators do not work with Xcode 14.3 and Flutter
Labels: platform-ios,tool,t: xcode,P3,team-ios,triaged-ios

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Steps to reproduce
Edit: It make not be directly related to Xcode 14.3, I had just happened to just download Xcode 14.3 so I thought that was the issue. Looks like this has happened in the past for people on previous version of Xcode (14): https://github.com/flutter/flutter/issues/116248. Seems like it only happens on M1 Macs.

1. Download Xcode 14.3 - May not be required, could have been introduced with Xcode 14?
2. Pick an iOS simulator with x86_64 architecture (you can do `xcrun xcdevice list` to find which have the arch)
3. Open the x86_64 iOS simulator
4. Do `flutter run -d device-id-xxx` with any flutter app



### Actual results
Results in this error:
```
Error waiting for a debug connection: The log reader failed unexpectedly
Error launching application on iPhone SE (2nd generation).
```
Expected: no error
### Logs

<details>
<summary>Logs</summary>

```console

<!-- Paste your logs here -->

```

</details>


### Flutter Doctor output

<details>
<summary>Doctor output</summary>

```console
[!] Flutter (Channel master, 3.10.0-15.0.pre.31, on macOS 13.3.1 22E261 darwin-arm64, locale en)
    • Flutter version 3.10.0-15.0.pre.31 on channel master at xxx
    • Framework revision ea179fe033 (61 minutes ago), 2023-04-27 13:32:25 -0400
    • Engine revision 3d6d915cb7
    • Dart version 3.1.0 (build 3.1.0-49.0.dev)
    • DevTools version 2.23.1

[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at xxx
    • Platform android-33, build-tools 33.0.0
    • ANDROID_SDK_ROOT = xxx
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E222b
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.1)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 11.0.15+0-b2043.56-8887301)

[✓] VS Code (version 1.77.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.62.0

[✓] Connected device (5 available)
    xxx

[✓] Network resources
    • All expected network resources are available.
```

</details>
Repository: vscode
Issue: Storing edit session in local git repo asks to push my branch repeatedly
Labels: bug,continue-working-on

- Open a workspace with a git repo that is not on github
- Run "Store working changes in cloud"
- Get this dialog
<img width="622" alt="image" src="https://user-images.githubusercontent.com/323878/234974474-7d63a516-5a56-4a4b-bc00-2c1c31b6e565.png">

- dismiss it, it pops up again
- It keeps popping up
Repository: vscode
Issue: JSDoc comments paste with incorrect indentation
Labels: bug,javascript,editor-autoindent,on-unit-test

<!-- ⚠️⚠️ 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: macOS 12.6.5

Steps to Reproduce:

1. Copy this JSDoc comment:
   ```js
   /**
    * @typedef {
    * }
    */
   ```
2. Paste into a Javascript file in VSCode

It pastes as:

```js
/**
 * @typedef {
* }
*/
```

Notice that the lines from the `}` lose their single space indentation. It seems that the braces are interpreted as affecting the indentation, but only if part of an `@something` rule.

As a work-around, pressing Undo immediately after pasting will revert the indentation back to being correct.
Repository: next.js
Issue: Renaming file from `file.extension` to `file/index.extension` is not picked up by dev server
Labels: bug

### 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: 16.16.0
      npm: 8.11.0
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.3.2-canary.11
      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)

_No response_

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/focused-tereshkova-13cb43

### To Reproduce

1. Create a simple component and then import it, something like:
```
// component.jsx

export default () => <p>Some component</p>
```

```
// page.jsx

import Component from 'component'

export default () => <Component />
```

2. Start the dev server (`npm run dev`)

3. Now rename `component.js` to `component/index.js`. You should get an import error:
<img width="995" alt="Screenshot 2023-04-27 at 15 25 07" src="https://user-images.githubusercontent.com/40037115/234970405-dfe77245-37e2-49b7-8c99-55c7d1c48781.png">


4. Restart the server — the import should now be resolved without changing the import.

### Describe the Bug

Renaming files by adding or removing `index` causes an import error until the server is manually restarted.

### Expected Behavior

Since `component.js` and `component/index.js` are effectively the same (`import Component from 'component'`), the rename shouldn't cause an error.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: flutter
Issue: Migrate iOS golden tests to Skia Gold
Labels: platform-ios,engine,c: proposal,P3,team-ios,triaged-ios

## Design doc
https://docs.google.com/document/d/1Bul-389Gp_iwKyJSwyX4j8295AO1jWMOos8se7CHA8c/edit#heading=h.ooqos4vcuipb

## Summary
Migrate iOS golden image tests in scenario_app to use the infrastructure developed for Impeller to get the golden image tests on Skia Gold for better tooling and to match the tooling used by Impeller, web and Android.

cc @cyanglaz @jmagman
Repository: terminal
Issue: Use synchronous APIs for AppExtensionCatalog
Labels: Area-Settings,Product-Terminal,Issue-Task,Area-Quality

MSFT-43215694 added `IAppExtensionCatalog2::FindAll` and `IAppExtension3::GetPublicFolder`. _If_ they release publicly, we should use those in the settings model because `extractValueFromTaskWithoutMainThreadAwait` is slow, wrong and ✨pain✨ (just that one call to `FindAllAsync` + await is like 4% of the total startup cost). I personally wouldn't even keep the old code because of that.
Repository: go
Issue: x/text/message/pipeline: TestFullCycle failures
Labels: NeedsInvestigation

```
#!watchflakes
post <- pkg == "golang.org/x/text/message/pipeline" && test == "TestFullCycle"
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/b2b58985d0943ebb72b08e3ddd6289af685e45e1)):

    SIGSEGV: segmentation violation
    PC=0x101ebc2 m=8 sigcode=1
    
    rax    0x5fdb820
    rbx    0xc00003e138
    rcx    0x5fdb820
    rdx    0x0
    rdi    0x0
    rsi    0x200001
    rbp    0x700000742e98
    ...
    	/tmp/buildlet/go/src/runtime/proc.go:398 +0xce fp=0xc000094c48 sp=0xc000094c28 pc=0x1038c2e
    runtime.chanrecv(0xc00012e150, 0xc000094d2f, 0x1)
    	/tmp/buildlet/go/src/runtime/chan.go:583 +0x3cd fp=0xc000094cc0 sp=0xc000094c48 pc=0x1005e2d
    runtime.chanrecv1(0x190c680?, 0x13f8380?)
    	/tmp/buildlet/go/src/runtime/chan.go:442 +0x12 fp=0xc000094ce8 sp=0xc000094cc0 pc=0x1005a32
    testing.(*T).Run(0xc0000836c0, {0xc0000a8b3c?, 0x36?}, 0xc00014e270)
    	/tmp/buildlet/go/src/testing/testing.go:1649 +0x3c8 fp=0xc000094da8 sp=0xc000094ce8 pc=0x11171e8
    golang.org/x/text/message/pipeline.TestFullCycle(0xc0000836c0)
    	/tmp/buildlet/gopath/src/golang.org/x/text/message/pipeline/pipeline_test.go:76 +0x718 fp=0xc000094f70 sp=0xc000094da8 pc=0x13cac58
    testing.tRunner(0xc0000836c0, 0x14c1910)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: vscode
Issue: kernel quick pick flashes
Labels: bug,polish,quick-pick

Testing microsoft/vscode-jupyter#11963

* use new kernel picker
* explore all options a few times
* :bug: notice how QP flashes, between the options it hides and re-shows which shouldn't happen. It should be a QP always on flow without the flicker/flashing

https://user-images.githubusercontent.com/1794099/204783292-647d9f76-a17c-461a-b121-83b97eb71fa1.mov
Repository: pytorch
Issue: tensor with dims marked with torch._dynamo.mark_dynamic loses dynamic dim marks after being moved to a different device
Labels: triaged,oncall: pt2,module: dynamic shapes

### 🐛 Describe the bug

I'm trying to mark some tensor dims as dynamic with `torch._dynamo.mark_dynamic`, and later move it to a target device. If the target device and the device the tensor was on when `torch._dynamo.mark_dynamic` called, `_dynamo_dynamic_indices` is lost on the new tensor.

Repro1 (cpu -> cuda): 
```
import torch._dynamo


t = torch.ones((1, 20))
assert not hasattr(t, "_dynamo_dynamic_indices")

torch._dynamo.mark_dynamic(t, 0)
assert t._dynamo_dynamic_indices == {0}

t_cuda = t.to("cuda")
assert t_cuda._dynamo_dynamic_indices == {0}
```

Repro2 (cuda -> cpu): 
```
import torch._dynamo


t = torch.ones((1, 20)).to("cuda")
assert not hasattr(t, "_dynamo_dynamic_indices")

torch._dynamo.mark_dynamic(t, 0)
assert t._dynamo_dynamic_indices == {0}

t_cpu = t.to("cpu")
assert t_cpu._dynamo_dynamic_indices == {0}
```

Both repros yield the same error log
```
Traceback (most recent call last):
  File "*****", line *, in <module>
    assert t_cuda._dynamo_dynamic_indices == {0}
AttributeError: 'Tensor' object has no attribute '_dynamo_dynamic_indices'
```

### Expected Output:

No Errors

### Versions

torch version: `2.1.0.dev20230427+cu117`

cc @ezyang @soumith @msaroufim @wconstab @ngimel @bdhirsh