sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Drag and Drop issue with High Contrast Mode
Labels: themes,accessibility


Type: <b>Bug</b>

Drag and Drop actions, such as move a file from a folder to another, do not provide have hover style when using a dark contrast mode. Making it hard to see where the file is going to be moved. 

VS Code version: Code 1.73.1 (6261075646f055b99068d3688932416f2346dd3b, 2022-11-09T04:27:29.066Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No
Remote OS version: Linux x64 5.4.0-1098-azure

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

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz (12 x 2592)|
|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>skia_renderer: enabled_on<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: disabled_off|
|Load (avg)|undefined|
|Memory (System)|63.76GB (40.67GB free)|
|Process Argv|--crash-reporter-id e8cef2df-0a22-4d43-9526-340d5ef10881|
|Screen Reader|yes|
|VM|0%|

|Item|Value|
|---|---|
|Remote|Codespaces|
|OS|Linux x64 5.4.0-1098-azure|
|CPUs|Intel(R) Xeon(R) Platinum 8168 CPU @ 2.70GHz (32 x 2693)|
|Memory (System)|62.81GB (19.94GB free)|
|VM|0%|
</details><details><summary>Extensions (21)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-firefox-debug|fir|2.9.8
codespaces|Git|1.13.5
vscode-graphql-syntax|Gra|1.0.5
remote-containers|ms-|0.266.1
remote-ssh|ms-|0.94.0
remote-ssh-edit|ms-|0.84.0
remote-wsl|ms-|0.72.0
vscode-remote-extensionpack|ms-|0.23.0
remote-explorer|ms-|0.0.3
debugger-for-chrome|msj|4.13.0
ejs-language-support|Qas|0.0.1
gitlens|eam|13.2.0
prettier-vscode|esb|9.10.4
codespaces|Git|1.13.5
vscode-pull-request-github|Git|0.50.0
vscode-graphql|Gra|0.8.4
vscode-graphql-execution|Gra|0.1.6
vscode-graphql-syntax|Gra|1.0.5
vscode-typescript-tslint-plugin|ms-|1.3.4
ejs-language-support|Qas|0.0.1
project-snippets|reb|0.5.0

(2 theme extensions excluded)

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

```
vsliv368cf:30146710
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
vslsvsres303:30308271
pythonvspyl392:30443607
vserr242cf:30382550
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263cf:30335440
vscoreces:30445986
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30410667
cppdebug:30492333
vsclangdf:30486550
c4g48928:30535728
dsvsc012cf:30540253
azure-dev_surveyone:30548225
pyindex848:30577860
nodejswelcome1cf:30587006
282f8724:30602487
89544117:30613380
fim-prod:30623723

```

</details>

<!-- generated by issue reporter -->
Repository: storybook
Issue: [Bug]: Color theme of fenced code blocks in MDX (7 beta 28)
Labels: bug,has workaround,theming,mdx,sev:S3

### Describe the bug

Can’t set the theme of fenced code blocks to dark in SB 7 beta

Previously, doing this in MDX would work:

\`\`\`javascript dark
	let foo;
\`\`\`

But all code blocks appear light now. 

Using a Source block works as expected:

`<Source language=“javascript” dark code={myCode} />`


### To Reproduce

Just add this to an MDX file to preview it:

\`\`\`javascript dark
	let foo;
\`\`\`


### System

```shell
Environment Info:

  System:
    OS: macOS 13.1
    CPU: (4) x64 Intel(R) Core(TM) i5-8210Y CPU @ 1.60GHz
  Binaries:
    Node: 18.3.0 - /usr/local/opt/node@18/bin/node
    npm: 8.12.2 - /usr/local/opt/node@18/bin/npm
  Browsers:
    Chrome: 109.0.5414.87
    Safari: 16.2
  npmPackages:
    @storybook/addon-a11y: ^7.0.0-beta.28 => 7.0.0-beta.28 
    @storybook/addon-actions: ^7.0.0-beta.28 => 7.0.0-beta.28 
    @storybook/addon-essentials: ^7.0.0-beta.28 => 7.0.0-beta.28 
    @storybook/addon-interactions: ^7.0.0-beta.28 => 7.0.0-beta.28 
    @storybook/addon-links: ^7.0.0-beta.28 => 7.0.0-beta.28 
    @storybook/addon-postcss: ^2.0.0 => 2.0.0 
    @storybook/jest: ^0.0.11-next.0 => 0.0.11-next.0 
    @storybook/test-runner: ^0.10.0-next.4 => 0.10.0-next.4 
    @storybook/testing-library: ^0.0.14-next.1 => 0.0.14-next.1 
    @storybook/vue3: ^7.0.0-beta.28 => 7.0.0-beta.28 
    @storybook/vue3-vite: ^7.0.0-beta.28 => 7.0.0-beta.28
```


### Additional context

_No response_
Repository: PowerToys
Issue: Smooth Scroll
Labels: Needs-Triage

### Description of the new feature / enhancement

https://www.smoothscroll.net/win/

### Scenario when this would be used?

tutte le finestre

### Supporting information

Assurdo che non sia possibile regolarlo di default su windows!! o che debba pagare...
Repository: PowerToys
Issue: Irregular friendly name of PowerRename
Labels: Issue-Docs,Needs-Triage

### Provide a description of requested docs changes

In the code and documentation there are many mentions of "PowerRename" but also many mentions of "Power Rename" Which one is correct?
Repository: pytorch
Issue: [discussion] Fused MLPs
Labels: feature,triaged,oncall: pt2,module: inductor

### 🚀 The feature, motivation and pitch

I just stumbled on https://twitter.com/DrJimFan/status/1615018393601716224, there is https://github.com/NVlabs/tiny-cuda-nn which fuses small MLPs for fast training and inference. Can Inductor / Triton generate similar PTX / memory placement?

It seems at least as a good comparison target for benchmark

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @soumith @msaroufim @wconstab @ngimel @bdhirsh @mlazos @voznesenskym @yanboliang @penguinwu @anijain2305 @EikanWang @jgong5 @Guobing-Chen @chunyuan-w @XiaobingSuper @zhuhaozhe @blzheng @Xia-Weiwen @wenzhe-nrv @jiayisunx @peterbell10 @desertfire
Repository: tauri
Issue: [bug] Cannot sign MacOs app when the productName contains Latin-Extended characters
Labels: type: bug,status: needs triage

### Describe the bug

MacOS codesign fails when the productName contains Latin-Extended characters (e.g. ō).
Removing the character fixes the build.

This happens when building apps for 3rd party distribution (notarised) or the AppStore.

### Reproduction

1. create a new Tauri app (I'm on 1.2.2, but 1.1.x had the same issue)
2. Specify the env vars required for signing and notarisation, e.g.:
    - `export APPLE_SIGNING_IDENTITY='xxx'`
    - `export APPLE_ID='xxx@xxx.xx'`
    - `export APPLE_PASSWORD='xxx-xxx-xxx-xxx'`
3. open `tauri-conf.json` and change `package.productName` to `Ensō` (note the diacritic char above `o`)
4. `npm run tauri build -- --target universal-apple-darwin`


### Expected behavior

The app should build and the resulting binary should have the correct name.


### Platform and versions


```sh
Environment
  › OS: Mac OS 13.0.0 X64
  › Node.js: 18.9.0
  › npm: 8.19.1
  › pnpm: Not installed!
  › yarn: Not installed!
  › rustup: 1.25.1
  › rustc: 1.65.0
  › cargo: 1.65.0
  › Rust toolchain: stable-aarch64-apple-darwin 

Packages
  › @tauri-apps/cli [NPM]: 1.2.2
  › @tauri-apps/api [NPM]: 1.2.0
  › tauri [RUST]: 1.2.0,
  › tauri-build [RUST]: 1.2.0,
  › tao [RUST]: 0.15.6,
  › wry [RUST]: 0.22.3,

App
  › build-type: bundle
  › CSP: unset
  › distDir: ../dist
  › devPath: http://localhost:1420/
  › framework: React
  › bundler: Vite

App directory structure
  ├─ types
  ├─ dist
  ├─ node_modules
  ├─ src-tauri
  ├─ build
  ├─ .git
  ├─ .vscode
  └─ src
```

### Stack trace

_No response_

### Additional context

Running the failing codesign command directly from the terminal results in a segfault.
Repository: pytorch
Issue: distributions.Beta returning incorrect results at 0 and 1
Labels: module: distributions,triaged

### 🐛 Describe the bug

The beta distribution has support either on [0, 1] or, for some implementations, on (0, 1). However, the PyTorch version appears to have support on [0, 1] but it returns `-inf` or `nan` on those values.

```
In [31]: beta = torch.distributions.Beta(torch.tensor([1.0]), torch.tensor([1.0]), validate_args=True)

In [32]: beta.support
Out[32]: Interval(lower_bound=0.0, upper_bound=1.0)

In [33]: beta.log_prob(torch.tensor([1.0]))
Out[33]: tensor([nan])

In [34]: beta.log_prob(torch.tensor([0.0]))
Out[34]: tensor([nan])

In [35]: beta = torch.distributions.Beta(torch.tensor([2.0]), torch.tensor([2.0]), validate_args=True)

In [36]: beta.log_prob(torch.tensor([0.0]))
Out[36]: tensor([-inf])

In [37]: beta.log_prob(torch.tensor([1.0]))
Out[37]: tensor([-inf])
```

Note that we did not get a `ValueError` when we passed 0 and 1 even though `validate_args=True` was set, but we did get `-inf` and/or `nan` even though that's not the correct answer. Also, the `support` seems to indicate that 0 and 1 are legal (though I couldn't find documentation of the `Interval` class so I'm not sure if that's supposed to be inclusive or exclusive).

### Versions

PyTorch version: 1.13.0+cu116
Is debug build: False
CUDA used to build PyTorch: 11.6
ROCM used to build PyTorch: N/A

OS: Debian GNU/Linux 11 (bullseye) (x86_64)
GCC version: (Debian 10.2.1-6) 10.2.1 20210110
Clang version: Could not collect
CMake version: version 3.18.4
Libc version: glibc-2.31

Python version: 3.10.6 (main, Oct 11 2022, 01:13:46) [GCC 10.2.1 20210110] (64-bit runtime)
Python platform: Linux-5.10.0-20-cloud-amd64-x86_64-with-glibc2.31
Is CUDA available: True
CUDA runtime version: 11.8.89
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA A100-SXM4-40GB
Nvidia driver version: 520.61.05
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

Versions of relevant libraries:
[pip3] numpy==1.24.1
[pip3] torch==1.13.0+cu116
[pip3] torchvision==0.14.0+cu116
[conda] Could not collect


cc @fritzo @neerajprad @alicanb @nikitaved
Repository: rust
Issue: error: invalid register `tp`: the thread pointer cannot be used as an operand for inline asm
Labels: A-inline-assembly

There are certain assumptions made by Rust (LLVM?) about register usage on various platforms (RISC-V in this example) which are true only for some platforms, but not true for variety of embedded use cases.  `clang` provide some workarounds with register variables extension and options like `-ffixed-x10`, but in Rust it is not clear how to efficiently get same functionality without copy of 'reserved' register into 'general purpose one'.

```
 unsafe fn get_sys_buf() -> *mut u8 {
        let syscall_buf: *mut u8;
        unsafe { asm!("", out("tp") syscall_buf) };
        syscall_buf
    }
```
Repository: vscode
Issue: Problems pane gives incorrect advice about `launch.json`.
Labels: bug,debug

<!-- ⚠️⚠️ 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.74.3
- OS Version: Linux x64 5.15.79.1-microsoft-standard-WSL2

Steps to Reproduce:

```json
{
  // Use IntelliSense to learn about possible attributes.
  // Hover to view descriptions of existing attributes.
  // For more information, visit: https://go.microsoft.com/fwlink/?linkid=830387
  "version": "0.2.0",
  "configurations": [
    {
      "name": "Debug Main Process",
      "type": "node",
      "request": "launch",
      "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/electron",
      "windows": {
        "runtimeExecutable": "${workspaceRoot}/node_modules/.bin/electron.cmd"
      },
      "runtimeArgs": [
        "--remote-debugging-port=9229",
        "."
      ],
      "envFile": "${workspaceFolder}/.vscode/.debug.env",
      "console": "integratedTerminal"
    },
    {
      "name": "Debug Renderer Process",
      "port": 9229,
      "request": "attach",
      "type": "chrome",
      "timeout": 60000,
      "skipFiles": [
        "<node_internals>/**",
        "${workspaceRoot}/node_modules/**",
        "${workspaceRoot}/dist-electron/**",
        // Skip files in host(VITE_DEV_SERVER_URL)
        "http://127.0.0.1:3344/**"
      ]
    },
  ],
  "compounds": [
    {
      "name": "Debug App",
      "preLaunchTask": "Before Debug",
      "configurations": [
        "Debug Main Process",
        "Debug Renderer Process"
      ],
      "presentation": {
        "hidden": false,
        "group": "",
        "order": 1
      },
      "stopAll": true
    }
  ],
}
```

1. Use provided launch.json
2. Open it in VSC


![image](https://user-images.githubusercontent.com/75278/212758339-f38005a3-8768-49a2-9f78-d1add8363032.png)

In this case, it is suggested that I add `name`, `type` and `request` fields to the `windows` section, which does not work and is documented here https://code.visualstudio.com/docs/editor/debugging#_platformspecific-properties
Repository: material-ui
Issue: [material-ui][Button] Provide an accessible focus alternative when `disableRipple` prop is set
Labels: accessibility,component: button,package: material-ui

### What's the problem? 🤔

When you use the `disableRipple: true`, property on the `theme.components` as such 
```
    MuiButtonBase: {
      defaultProps: {
        disableRipple: true,
      },
    },
```
Then all of the components that rely on the `Mui-focusVisible` class for ripple styling become unaccessible. When you focus them with keyboard nothing happens, you can't tell they are focused.

Ripple|Disabled Ripple
---|---
![ripple](https://user-images.githubusercontent.com/61479393/212763599-3ccee89f-3bfd-424e-b93c-dbf260dd7b34.gif)|![no-ripple](https://user-images.githubusercontent.com/61479393/212763590-2d7c72a7-1d16-4965-a483-4dd83cd4210e.gif)


### What are the requirements? ❓

There needs to be some kind of fallback on that. I did that in my app and was left scratching my head for a while, why nothing is working, including:
* Radio Buttons
* Checkboxes
* Buttons

### What are our options? 💡

What I have done in my app is a global style to the:
```
.Mui-focusVisible: {
outline: 2px solid #000
}
```
There should be some fallback

### Proposed solution 🟢

I am unaware of the internals of MUI and someone with more knowledge should propose a solution. My solution to my application is what I wrote in the "What are our options? 💡" section.

### Resources and benchmarks 🔗

_No response_
Repository: neovim
Issue: TUI Client can handle server crashes
Labels: enhancement,api,tui,channels-rpc,has:plan,remote

### Problem

One of the main advantages of having separate processes for backend server and TUI client is that a segfault in the server doesn't need to be fatal for the client. The client could display a message what happened, clear the terminal or even try to restart the server.

At the moment, users just observe a crash without information what happened.

Example of a crash https://github.com/nvim-treesitter/nvim-treesitter/issues/4170 . In case of a SEGFAULT, users could get a link to a wiki page that explains how to obtain coredumps or debug the crashing process via gdb.

### Expected behavior

I would expect to read an error message on a unexpected termination of the server and including the bad return code and if possible whether the server process was kill by a signal. Users could be informed whether there are any steps to investigate and report the issue or where to find possible logs or stderr of the child process.

OBS for instance uses a separate process for ffmpeg muxing. When it segfaults or crashes in another way you get a error message explaining what happened.

The terminal client might even have enough state information to offer to try to recover the crashed session.
Repository: stable-diffusion-webui
Issue: [Feature Request]: 2nd txt2img tab
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Have a second txt2img tab, just like the existing one, for trying out different settings when you don't want to lose what you already generated, without having to constantly save and reload temporary images. For example, if I generate a batch of say 40 images in txt2img, I'd like to pick one and have a button (like the current "Send To..." buttons, which would send the currently viewed image to the 2nd txt2img tab (with all its settings and seed), where I can then play around with it  (changing prompt etc) without losing the initial batch in the 1st txt2img tab.

### Proposed workflow

1. Generate one or more images, either in a batch or xy plot 
2. Select one of the images
3. Click a "send to txt2img2" (or something similar)
4. Click the txt2img2 tab and make changes to prompts, settings, etc
5. Generate new variations and save if desired
6. Go back to main txt2img tab and continue browsing previous images


### Additional information

_No response_
Repository: godot
Issue: Clicking on an exported script variable in the node inspector will not open script editor if script is in array
Labels: bug,topic:editor,usability

### Godot version

v4.0.beta12.official [3c9bf4bc2]

### System information

Pop!_OS 22.04 LTS

### Issue description

Normally, I can click on an exported script in the editor's node inspector and it will open that script in the scripting editor, but that does not work if the script is in an exported array.

Also, clicking an exported script in an exported resource works, but not if the resource is in an exported array.

### Steps to reproduce

Create a node script that exports an array of scripts and add at least one different script to the array that can be edited in Godot. Clicking on that script in the node inspector will do nothing.

### Minimal reproduction project

[MinimalProject.zip](https://github.com/godotengine/godot/files/10429727/MinimalProject.zip)
Repository: stable-diffusion-webui
Issue: [Feature Request]: Requested description section of properties of output images.
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Add the description portion of the details tab of the properties of the images produced with stable diffusion. Then setting it up to have the comments section to include more details about the prompt used, which model was used, and other such data.

### Proposed workflow

1. Right-clicking the images produced and selecting properties.
2. Go to the details tab and have the pertinent information about how the image was produced stored in the comments section.
3. Currently, there is no description portion of the details tab on the properties of the images.
4. The comments section could store more information than the title of the image can as well as allow the users to keep more detailed records of what model was used, the seed used, the guidance scale, the prompt for the image, etc.


### Additional information

![Capture](https://user-images.githubusercontent.com/116048802/212783272-3c8e9d54-0b84-498d-af81-ace75cfcd592.JPG)
Currently there is no description portion in the properties of output images.
Repository: TypeScript
Issue: Property autocompletion includes `Symbol` when object has a well-known symbol as key
Labels: Bug,Help Wanted,Domain: Completion Lists

# Bug Report

### 🔎 Search Terms

property autocompletion symbol well-known

### 🕗 Version & Regression Information

TypeScript 4.9.4

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about _?_

### ⏯ Playground Link

[Playground link with relevant code](https://www.typescriptlang.org/play?experimentalDecorators=false&emitDecoratorMetadata=false&target=99&module=1&ts=4.9.4&downlevelIteration=true#code/MYewdgzgLgBCBGArGBeGBvAUDGAzAlgKYA2AJgFwwAMANNjANoDKAngLbwjEB0AhhCzDAAklEIAnXlBDiAugAoAlBgC+mFQG5MmBIm5A)

Sorry but please note that I wasn't able to reproduce the issue on the playground. The issue was reproducible on my VSCode 1.74.3, with extensions disabled, and TypeScript 4.9.4.

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
const obj = {
  field: 0,
  [Symbol.asyncIterator]() {}
};

obj.
//  ^autocompletion here
```

tsconfig.json:

```json
{
  "compilerOptions": {
    "target": "esnext",
    "strict": true
  },
  "include": ["index.ts"]
}
```

### 🙁 Actual behavior

`Symbol` is shown as a autocompletion candidate.

![スクリーンショット 2023-01-17 11 06 07](https://user-images.githubusercontent.com/748348/212794015-dc912ee1-d5c5-4808-a876-f37d931fbcc5.png)

Selecting it produces `obj[Symbol]` which isn't correct.

### 🙂 Expected behavior

Should offer `Symbol.asyncIterator`.