sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: context menu display on another monitor
Labels: bug,help wanted,upstream,macos,electron,multi-monitor,system-context-menu


Type: <b>Bug</b>

Open a file and select some code and right click it.
Then the context menu display on another monitor.

VS Code version: Code 1.85.1 (Universal) (0ee08df0cf4527e40edc9aa28f4b5bd38bbff2b2, 2023-12-13T09:48:06.308Z)
OS version: Darwin x64 22.6.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-1038NG7 CPU @ 2.00GHz (8 x 2000)|
|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>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)|7, 6, 5|
|Memory (System)|16.00GB (0.50GB free)|
|Process Argv|--crash-reporter-id 03366245-4f03-4e9f-818f-a12ad67e1d90|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (29)</summary>

Extension|Author (truncated)|Version
---|---|---
Bookmarks|ale|13.4.2
markdown-mermaid|bie|1.21.0
vscode-svgviewer|css|2.0.0
vscode-eslint|dba|2.4.2
githistory|don|0.6.20
gitlens|eam|14.6.1
prettier-vscode|esb|10.1.0
auto-close-tag|for|0.5.15
auto-rename-tag|for|0.1.10
shell-format|fox|7.2.5
copilot|Git|1.143.0
copilot-chat|Git|0.11.1
vscode-pull-request-github|Git|0.78.1
path-autocomplete|ion|1.25.0
vscode-pont|jas|1.5.12
vscode-leetcode|Lee|0.18.1
git-graph|mhu|1.30.0
vscode-json5|mrm|1.0.0
vscode-language-pack-zh-hans|MS-|1.85.2023121309
color-highlight|nau|2.5.0
cssvar|pho|2.6.4
vscode-yaml|red|1.14.0
LiveServer|rit|5.7.9
vscode-stylelint|sty|1.3.0
language-stylus|sys|1.16.0
debug-leetcode|wan|0.2.3
vscode-todo-highlight|way|1.0.5
markdown-all-in-one|yzh|3.5.1
vscode-i18n-linter|zwe|1.5.1


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vsdfh931cf:30280410
vshan820:30294714
vstes263cf:30335440
vscod805cf:30301675
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
py29gd2263:30899288
vscaat:30438848
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
azure-dev_surveyone:30548225
89544117:30613380
showlangstatbar:30737416
0bi6i642:30917235
fixshowwlkth:30771522
showindicator:30805244
pythongtdpath:30769146
i26e3531:30792625
pythonidxpt:30866567
pythonnoceb:30805159
asynctok:30898717
dsvsc013:30795093
dsvsc014:30804076
dsvsc015:30845448
pythontestfixt:30902429
pyreplss1:30897532
pythonmypyd1:30879173
pythoncet0:30885854
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
aa_t_chat:30882232
dsvsc019cf:30917260
cp7184t:30925682

```

</details>

<!-- generated by issue reporter -->
Repository: rust
Issue: query cycle: specialisation `cycle detected when building specialization graph of trait`
Labels: A-diagnostics,T-compiler,F-specialization,I-cycle

### Code

```Rust
#![feature(specialization)]

trait Trait<T> {
    type Assoc;
}

impl<T> Trait<T> for Vec<T> {}

impl Trait<u8> for Vec<u32> {
    type Assoc = u8;
}

impl<T> Trait<T> for String {
    type Assoc = ();
}

impl Trait<<Vec<u8> as Trait<u8>>::Assoc> for String {}

fn main() {}
```


### Current output

```Shell
warning: the feature `specialization` is incomplete and may not be safe to use and/or cause compiler crashes
 --> 43273EB829A15349E16F5931020795BF70C210EEDA25D591DFCCF621A1677EA0.rs:1:12
  |
1 | #![feature(specialization)]
  |            ^^^^^^^^^^^^^^
  |
  = note: see issue #31844 <https://github.com/rust-lang/rust/issues/31844> for more information
  = help: consider using `min_specialization` instead, which is more stable and complete
  = note: `#[warn(incomplete_features)]` on by default

error[E0391]: cycle detected when building specialization graph of trait `Trait`
 --> 43273EB829A15349E16F5931020795BF70C210EEDA25D591DFCCF621A1677EA0.rs:3:1
  |
3 | trait Trait<T> {
  | ^^^^^^^^^^^^^^
  |
  = note: ...which immediately requires building specialization graph of trait `Trait` again
note: cycle used when coherence checking all impls of trait `Trait`
 --> 43273EB829A15349E16F5931020795BF70C210EEDA25D591DFCCF621A1677EA0.rs:3:1
  |
3 | trait Trait<T> {
  | ^^^^^^^^^^^^^^
  = note: see https://rustc-dev-guide.rust-lang.org/overview.html#queries and https://rustc-dev-guide.rust-lang.org/query.html for more information

error: aborting due to 1 previous error; 1 warning emitted

For more information about this error, try `rustc --explain E0391`.
```


### Desired output

```Shell
We should have a proper diagnostic here pointing out where the cyclic problem is
```


### Rationale and extra context

cc https://github.com/rust-lang/rust/issues/119321

### Other cases

_No response_

### Anything else?

_No response_
Repository: deno
Issue: [BUG] Deno KV: Using only prefix selector in kv.list, you can't get an exact match key.
Labels: bug,ext/kv

Version: Deno 1.39.1 (the most recent release)

# Summary

The prefix selector of `kv.list()` cannot get an entry for an exact match key, but it can if `start` is specified.
The `start` is supposed to be for narrowing down, but it is odd behavior that this would increase the number of entries.

## Test code

- test.ts
```typescript
const data = [
  { key: ["data"], value: 0 },
  { key: ["data", 1], value: 1 },
];

const db = await Deno.openKv("./test.sqlite3");
for (const d of data) {
  await db.set(d.key, d.value);
}

console.log("only prefix");
for await (const entry of db.list({ prefix: ["data"] })) {
  console.log(entry.value);
}

console.log("prefix and start");
for await (const entry of db.list({ prefix: ["data"], start: ["data"] })) {
  console.log(entry.value);
}

db.close();
```

## Result

```bash
$ deno run -A --unstable-kv ./test.ts
only prefix
1
prefix and start
0
1
```
Repository: next.js
Issue: [Env]:  Issue with Parsing `$` Symbol in .env Files
Labels: bug

### Link to the code that reproduces this issue

https://github.com/Innei/next-env-symbol-reproduction

### To Reproduce

1. run `dev`

### Current vs. Expected behavior

1. current .env file is 

```
RAW_SYMBOL='111$11111'
WITH_SYMBOL=111$11111

```

The first one is wrapped in single quotes, and the env should not be added to the variable in the terminal. The second one should be inserted into the variable

But currently, all of this is like the second one.

![CleanShot 2023-12-27 at 5  08 02@2x](https://github.com/vercel/next.js/assets/41265413/8da8d667-2c3f-44f1-ba39-9fc449594611)
2. Expected, only parsed the second one, instead of the first.

### 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 23.2.0: Wed Nov 15 21:55:06 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6020
Binaries:
  Node: 20.8.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.11.0
Relevant Packages:
  next: 14.0.4
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: N/A
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Additional context

_No response_
Repository: ant-design
Issue: [Tooltip] 滑动过快或导致页面闪现滚动条
Labels: 🐛 Bug,Inactive

### Reproduction link

[https://konva-ceph.pages.dev/](https://konva-ceph.pages.dev/)

### Steps to reproduce

https://github.com/Mt-Youya/konva-ceph.git 

这是我的项目代码,可以看,应该是样式问题

步骤:
1. 随便上传一张图片
2. 在右上角表格中滚动到最下面,找到 Ptm-U6(mm) 这行,鼠标放到最右边的info 图标上,快速向上滑动滚轮,就会导致root根节点出现滚动条


### What is expected?

tooltip自然消失,不会影响其他元素

### What is actually happening?

tooltip自然消失,root出现滚动条

| Environment | Info |
| --- | --- |
| antd | 5.10.2 |
| React | 18.2.0 |
| System | Win11 22H2 22621.2861 |
| Browser | Version 120.0.6099.130 (Official Build) (64-bit) |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: [google_maps_flutter] Add `onTap` for DefaultMarker
Labels: c: new feature,p: maps,package,c: proposal,team-ecosystem,P2,triaged-ecosystem

### GooleMap displays default markers on surrounding landmarks. However, We can't detect `onTap` for that.

<img src="https://github.com/flutter/flutter/assets/50433979/3cf9dc6f-43d0-4714-b72e-0f172a262be3" width="300">

### Use case

let's say I want to set a destination by tapping the default marker on Map.
When I tap the marker, the value I want is the coordinate the marker points to, not the coordinate I tapped.

This may sound the same, but since the marker is not a point, a low zoom level makes a big difference.

### To be sure, here is the solution I am now doing instead.

1. `onTap` to get the `LatLng`.
2. use Google Maps API geocode the `LatLng` obtained in 1 to get the Place id.
3. use places api with the Place id obtained in step 2 to get the location information and point to the marker.

This works in many cases, but not reliably.


### Proposal

```dart
{void Function(LatLng)? onDefaultMarkerTap}
```
Repository: godot
Issue: CTRL + Click opens documentation even if CTRL was not just pressed
Labels: discussion,topic:editor

### Tested versions

Godot 4.2.1

### System information

Godot v4.2.1.stable - Ubuntu 23.10 23.10

### Issue description

Very often when I need to copy code, I use `CTRL + C` or `CTRL` and drag text around. However, under some conditions, this unexpectedly causes the doc of a function to open, or moves me the definition of an object. This can make the editor very inconvenient to use.

This is the cases where this happens:
- To quickly copy an identifier, I double-click and begin pressing CTRL simultaneously, then press C. Because I have CTRL held when the second click happens, this causes the doc of the item, or it's declaration, to open.
- Same thing when I paste to replace something, quite often when i'm quick, this moves me to the declaration of the object, causing me to past code at the wrong location (very annoying).
- This also sometime happens on drag and drop with CTRL held, but I can't reproduce it on purpose.

This issue could be mitigated the following ways:
- Open the doc only on full clicks, not just when releasing the mouse button (check for both a press and release).
- Do not open the doc on click if there were another click right before, as this would therefore be a double-click.
- Do not open the doc if any key press is performed between pressing CTRL and clicking.

### Steps to reproduce

In any project:

1. Find a native identifier that is underlined when holding CTRL.
2. Double-click on that identifier to select it, and start pressing CTRL in between your two clicks.
3. Observe a documentation Screamer.

Another way to reproduce:

1. Find **two different** user-defined identifiers that are underlined when holding CTRL, preferable names close to each other, on consecutive lines.
2. Select one of the identifier, hold CTRL and press C to copy it. **Keep CTRL pressed**.
3. Double-click the second identifier and press V to paste what you just copied (with the intent of replacing it).
5. Observe you just pasted your code at a completely different location than the one expected.

### Minimal reproduction project (MRP)

N/A
Repository: godot
Issue: Undoing creation of a dropped visual shader node results in error
Labels: bug,topic:editor,topic:shaders

### Tested versions

4.3 dev1 and earlier

### System information

Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; 30.0.15.1403) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)

### Issue description

When you drop a texture to visual shader and undo it, you will get `EditorProperty is outside inspector.` error.

### Steps to reproduce

1. Create VisualShader
2. Drag and drop a texture into the shader
3. Undo

### Minimal reproduction project (MRP)

N/A
Repository: PowerToys
Issue: Unable to open settings 
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.76.2

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Settings

### Steps to reproduce

Right click icon in task bar, select settings - a white box opens, but then closes again rather than displaying settings menu

### ✔️ Expected Behavior

settings menu

### ❌ Actual Behavior

a white box appeared briefly then closed
powertoys remained running in taskbar
[PowerToysReport_2023-12-27-21-15-35.zip](https://github.com/microsoft/PowerToys/files/13778288/PowerToysReport_2023-12-27-21-15-35.zip)


### Other Software

_No response_
Repository: TypeScript
Issue: When the initial element of the tuple is a rest element, it is not possible to correctly infer the type of the initial element.
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

initial element of the tuple is a rest element

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

```ts
type T1 = [...string[], number, boolean]

declare const head: T1[0]
         // Actual: string | number | boolean
         // Expected: string | number
```

### 📃 Motivating Example

-

### 💻 Use Cases

[https://github.com/microsoft/TypeScript/issues/56883](https://github.com/microsoft/TypeScript/issues/56883)
Repository: transformers
Issue: How to add new merge rules in AutoTokenizer
Labels: New model

### Model description

I'm training new tokenizer from llama2, however, it seems that BPE tokenizer will clear the origin "vocab" and "merge" dict, and the training result is highly bias in my own datasets (about 6M C function) with some ugly tokens.

I wonder that is it possible to train a tokenizer from llama2 with the origin "vocab" and "merge" dict unchanged, only add some new vocab and merge rules from our datasets to support my requirement?


### Open source status

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

### Provide useful links for the implementation

_No response_
Repository: go
Issue: cmd/go: -buildmode=pie requires external (cgo) linking, but cgo is not enabled
Labels: NeedsInvestigation,arch-riscv,compiler/runtime

### Go version

go version go1.22rc1 linux/riscv64

### What operating system and processor architecture are you using (`go env`)?

```shell
GO111MODULE=''
GOARCH='riscv64'
GOBIN=''
GOCACHE='/home/andreas/.cache/go-build'
GOENV='/home/andreas/.config/go/env'
GOEXE=''
GOEXPERIMENT=''
GOFLAGS=''
GOHOSTARCH='riscv64'
GOHOSTOS='linux'
GOINSECURE=''
GOMODCACHE='/home/andreas/go/pkg/mod'
GONOPROXY=''
GONOSUMDB=''
GOOS='linux'
GOPATH='/home/andreas/go'
GOPRIVATE=''
GOPROXY='https://proxy.golang.org,direct'
GOROOT='/usr/lib64/go/1.22'
GOSUMDB='sum.golang.org'
GOTMPDIR=''
GOTOOLCHAIN='local'
GOTOOLDIR='/usr/lib64/go/1.22/pkg/tool/linux_riscv64'
GOVCS=''
GOVERSION='go1.22rc1'
GCCGO='gccgo'
AR='ar'
CC='gcc'
CXX='g++'
CGO_ENABLED='1'
GOMOD='/dev/null'
GOWORK=''
CGO_CFLAGS='-O2 -g'
CGO_CPPFLAGS=''
CGO_CXXFLAGS='-O2 -g'
CGO_FFLAGS='-O2 -g'
CGO_LDFLAGS='-O2 -g'
PKG_CONFIG='pkg-config'
GOGCCFLAGS='-fPIC -pthread -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=/tmp/go-build1658771557=/tmp/go-build -gno-record-gcc-switches'
```


### What did you do?

```
$ CGO_ENABLED=0 go build -buildmode=pie hellogo.go
-buildmode=pie requires external (cgo) linking, but cgo is not enabled
```

### What did you expect to see?

```
$ CGO_ENABLED=0 /usr/lib64/go/1.21/bin/go build -buildmode=pie hellogo.go
# command-line-arguments
loadinternal: cannot find runtime/cgo
```

### What did you see instead?

```
$ CGO_ENABLED=0 go build -buildmode=pie hellogo.go
-buildmode=pie requires external (cgo) linking, but cgo is not enabled
```
Repository: vscode
Issue: Moving outline view out of explorer makes command name weird
Labels: bug,outline

1. Take out the outline view from the explorer into the activity bar
2. See the command name "Focus on outline view" to be come weird 

https://github.com/microsoft/vscode/assets/16353531/8652eeaa-006f-4bda-a482-947f51a614c4


Version: 1.86.0-insider
Commit: 9621add46007f7a1ab37d1fce9bcdcecca62aeb0
Date: 2023-12-20T05:47:39.317Z
Electron: 27.1.3
ElectronBuildId: 25612240
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Darwin arm64 23.1.0
Repository: material-ui
Issue: [material-ui][Switch] Color issue
Labels: component: switch,package: material-ui,enhancement

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://codesandbox.io/p/sandbox/switch-mui5-6vfyvs

Steps:

1. Add a switch 
2. Set color secondary
3. Observe the root element of the switch 


![Screenshot 2023-12-27 170022](https://github.com/mui/material-ui/assets/12841157/690cc82b-5e80-472c-9989-3d7346f66e99)


### Current behavior 😯

The color from the prop is not applied to the `switch-root` element. It's applied only to the `switch-base` element. Leaving out the posibility to target the track, as they are siblings in the switch root element.

### Expected behavior 🤔

The color should be present at the root of the component not only to some child

### Context 🔦

I am trying to override the secondary color from the theme. I cannot target the track component directly from the `colorSecondary` rule. 

I think the color should be on the `switch-root` as it's the root of this component. I was able to change it with the `+` and `span` but I don't think it should be like this

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: pytorch
Issue: Numpy like Masked/where operations
Labels: triaged,enhancement,module: masked operators

### 🚀 The feature, motivation and pitch

Numpy allows me to do masked operations such as mean/variance using `where` argument for mask:

```python
mean_value = np.mean(x, where=mask)
var_value = np.mean(x, where=mask) 
```

[Numpy docs for same](https://numpy.org/doc/stable/reference/generated/numpy.ma.mean.html)


This format of defining mean and variance is much more concise and less error inducing than the one decribed for pythorch [here](https://stackoverflow.com/a/69314298/4488940).

Having something similar for pytorch would be extremely valuable in making these tasks less error-prone and concise.

### Alternatives

_No response_

### Additional context

_No response_
Repository: flutter
Issue: Allow Autocomplete and RawAutocomplete to distinguish onFocus and onTap events
Labels: a: text input,framework,f: material design,c: proposal,P2,team-design,triaged-design

### Use case

Currently both `Autocomplete` and `RawAutocomplete` widgets trigger the `optionsBuilder` callback when widget becomes focused and then a dropdown with the list of options is immediately being shown after that.

However the widget could get focus in a several different ways:

* tap on the widget (both on mobile or web/desktop)
* using keyboard and tabbing through the form fields (this is especially relevant on web/desktop)

For the latter, it is not always desirable to have options immediately shown. Especially with an async `optionsBuilder` that may make a network call.

### Proposal

It would be great to have an option in both `Autocomplete` and `RawAutocomplete` widgets to control onFocus vs onTap behaviour.

Additionally it would make sense to have `AutocompleteNextOptionIntent` and `AutocompletePreviousOptionIntent` to trigger the `optionsBuilder`, so we could have custom UI (e.g. a dropdown chevron) or custom action shortcuts (e.g. Ctrl-Down as in common Windows shortcut for dropdowns fields) to open the list of options.
Repository: flutter
Issue: [camerax] Remove references of initial UseCase target rotations/flash mode & expose getters for current target rotations/flash mode
Labels: p: camera,package,P2,team-android,triaged-android

Currently, the `camera_android_camerax` plugin wraps `UseCase`s and fields for their initial target rotations and flash modes, e.g. https://github.com/flutter/packages/blob/36a7b99381f85e86914e82c75fc7d9038ed96cca/packages/camera/camera_android_camerax/lib/src/image_capture.dart#L51. As these `UseCase`s are managed by the wrapped CameraX library, so are there current rotations and flash modes, so the initial target rotation and flash mode (which are literally targets and may not be achievable by CameraX) are irrelevant and should not be referenced for determining the current rotation or flash mode.

The initial target rotation and flash mode should not be saved since it should never be referenced beyond the `UseCase` constructors and instead, getters for the flash mode and target rotation of the `UseCase` like https://developer.android.com/reference/androidx/camera/core/ImageCapture#getTargetRotation(), for example, should be exposed.
Repository: rustdesk
Issue: Window is completely white (blank) (powertoys, flutter not ok, sciter ok)
Labels: bug

### Bug Description

Opening up RustDesk, the window is completely white. Sometimes restarting allows the main window to open normally, but trying to remote into an endpoint results in a white desk.

### How to Reproduce

Trying to load an installed version or running the .exe fresh.

### Expected Behavior

Window is visible, usable, and remote session windows are visible and interactable.

### Operating system(s) on local side and remote side

Windows 10 -> Windows 10/11

### RustDesk Version(s) on local side and remote side

1.2.3

### Screenshots

![image](https://github.com/rustdesk/rustdesk/assets/8880292/85e00abb-55c2-4c7f-950c-bc7610ce7a05)


### Additional Context

_No response_