sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Crash when using the eyedropper function to select a color on the screen if editor settings are changed at the same time
Labels: bug,topic:editor,confirmed,crash

### Godot version

3.4

### System information

Ubuntu 20.04

### Issue description

Godot crashes when selecting a color for the theme using the button that allows you to select a color on the screen.

I wanted to change the base color of the Godot interface theme, so in the menu I went to "editor" / "editor settings" / "interface" / "Theme"
then to select a color I used the button that allows taking a tone on the screen, I observe that the blockage occurs when the cursor leaves the configuration window.

I am using Godot_v3.4-stable_mono_x11.64. on ubuntu 20.04. Godot's version number is [206ba70f4].

In advance I appreciate the attention paid to this bug.

### Steps to reproduce

I wanted to change the base color of the Godot interface theme, so in the menu I went to "editor" / "editor settings" / "interface" / "Theme"
then to select a color I used the button that allows taking a tone on the screen, I observe that the blockage occurs when the cursor leaves the configuration window.

### Minimal reproduction project

_No response_
Repository: rust
Issue: rustdoc: improve searching for duplicate functions of generic types
Labels: T-rustdoc,A-rustdoc-search

This is coming from `std::simd` (https://github.com/rust-lang/portable-simd/pull/191).

Consider searching `std` for `Simd::abs`: https://doc.rust-lang.org/nightly/std/simd/?search=Simd%3A%3Aabs

This search only returns the first instance of the `abs` function, which right now is `Simd::<i8, LANES>::abs`.  The problem here is that `abs` is implemented for other integers, as well as `f32` and `f64`, making those additional implementations hard to discover.  Should perhaps each implementation appear in search?  Or should it be easier to find other functions with the same name?
Repository: PowerToys
Issue: Tabs vs Spaces Video References Windows 10
Labels: Issue-Docs,Priority-3

### Provide a description of requested docs changes

https://docs.microsoft.com/en-us/windows/powertoys/#powertoys-video-walk-through

We should update this at some point.
Repository: godot
Issue: Tileset, collision, new polygon, first click not shown
Labels: bug,topic:editor,topic:2d

### Godot version

3.3.4.stable and 3.4.stable

### System information

Windows 21H1

### Issue description

Drawing a `New polygon` collision shape in the TileSet window,
doesn't show anything on the first mouse click.

![godot_tileset_collision_new_polygon](https://user-images.githubusercontent.com/13420573/141838181-a81909a1-6934-44dd-b817-52c87aa5f707.gif)

Could it be a regression?
Because this video shows the first point. The author is using Godot `3.2.stable`
(the version can be seen at the beginning of the video).

Tilemap Collisions Godot Tutorial 3.2
https://www.youtube.com/watch?v=qfTbzc5Qzok

The new polygon is drawn at 1 minute: https://youtu.be/qfTbzc5Qzok?t=60


### Steps to reproduce

- Create a new project
- Add a `TileMap` node
- In the Inspector, click on Tile Set: `[empty]`
- Choose: `New TileSet` and click on the just added `TileSet`
- In the bottom TileSet window,
Click on the bottom left plus button: `Add Texture(s) to TileSet.`
- Choose `Icon.png` and click `Open`
- At the top right of the TileSet window, click on `New Single Tile`
- Select a region by mouse dragging from the top left to the bottom right
- Click on the `Collision` button
- Click on the `New Polygon` button
- Click on the icon inside the previously drawn region

#### Observed
Nothing happens.
Moving the mouse doesn't show anything either.

#### Expected
The polygons first point should be shown.
And a line should be drawn from the first point,
and it should follow the mouse pointers movements.

### Notes
Clicking a second time, shows the first two points and a line between them.
Therefore, the first point was registered correctly, it just didn't appear.

Drawing a `New Rectangle` collision, shows all four points.
Both when mouse clicking once, which fills the selected tileset region.
Or when mouse dragging.

![godot_tileset_collision_new_rectangle](https://user-images.githubusercontent.com/13420573/141840117-6c8a5b37-2adb-4090-957e-c47992c2a356.gif)




### Minimal reproduction project

_No response_
Repository: flutter
Issue: Write API documentation for the DisplayList classes
Labels: engine,P2,team-engine,triaged-engine

The header for the new DisplayList format is well documented, but it's lacking API documentation for the specific draw calls that are defined in the format.

Right now the draw calls are almost exactly a 1:1 mapping to their Skia equivalents, but we should really have API docs in the header file.
Repository: PowerToys
Issue: Fancy Zones - Smarter new zone size when editing
Labels: Idea-Enhancement,FancyZones-Editor,Product-FancyZones

### Description of the new feature / enhancement

When adding new zones while editing/creating a layout, make the default size for a newly created zone the same size as whichever zone's size you last edited. If you're trying to create 30 new zones of the same size, you shouldn't have to resize every new zone you create 30 times.

### Scenario when this would be used?

When editing/creating layouts

### Supporting information

_No response_
Repository: flutter
Issue: Automatically delete CMakeCache.txt when new Visual Studio toolchain installed
Labels: tool,platform-windows,a: desktop,P2,team-windows,triaged-windows

Upon upgrading from Visual Studio 2019 to 2022, we need to delete CMakeCache.txt in application builds, or we'll encounter a build failure.

Repro steps:
1. Create a boilerplate flutter app.
2. Invoke `flutter run` with Visual Studio 2019 installed.
3. Install Visual Studio 2022.
4. Invoke `flutter run` in the same app.

Expected result: the app builds and runs

Actual result:
```
Launching lib\main.dart on Windows in debug mode...
CMake Error: Error: generator : Visual Studio 17 2022
Does not match the generator used previously: Visual Studio 16 2019
Either remove the CMakeCache.txt file and CMakeFiles directory or choose a different binary directory.
Building Windows application...
Exception: Unable to generate build files
``` 

Currently, users need to fix this by running:
```
flutter clean
```

However, in this situation it would be much better if we would automatically delete `CMakeCache.txt` and re-run the failing step. If it fails again, then we should bail out.

Related: https://github.com/flutter/flutter/issues/85922
Repository: vscode
Issue: Incorrect URI casing passed to extensions on Windows after file rename
Labels: under-discussion,uri

Version: 1.62.2 (user setup)
Commit: 3a6960b964327f0e3882ce18fcebd07ed191b316
Date: 2021-11-11T20:56:38.428Z
Electron: 13.5.2
Chrome: 91.0.4472.164
Node.js: 14.16.0
V8: 9.1.269.39-electron.0
OS: Windows_NT x64 10.0.22000

On Linux, I'm seeing that a file gets a didClose/didOpen when renamed while open.  On Windows, if the rename only alters the casing of the filename, no new didClose/didOpen occurs.  VS Code will continue to refer to the file using the old casing.  If the workspace is reloaded with the file still open, the new session continues to refer to the file using the old casing.

Our extension (C/C++) relies on VS Code referring to the same file consistently with the same URI, and that URI matching the actual case of the file in the file system.  We may need to match paths not received from VS Code, with URIs received from VS Code.  We can work around the issue by always going to disk to detect the file system casing before doing any comparison against a URI received from VS Code.  Though, I suspect this scenario is a bug and the intention is for VS Code URI's to refer to files consistently with casing that matches the file system.

A potential fix would be to issue didClose/didOpen for files on Windows even if only casing was changed.
Repository: material-ui
Issue: [material-ui][Icon] Font size is not applied to Material font icons
Labels: bug 🐛,component: Icon,package: icons,package: material-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

Set <Icon> component props as for example `fontSize="small"` or `sx={{ fontSize: 30 }}`  don't modify size of icon. It doesn't work for Material Icons. Change font size for FontAwesome icons works correctly. 

![obraz](https://user-images.githubusercontent.com/62357939/141852796-deeec7ec-0021-4fc1-9a43-cd92ff92c506.png)

![obraz](https://user-images.githubusercontent.com/62357939/141852846-a7cf77e1-a014-41bb-b92c-e84969d3e2f2.png)


### Expected behavior 🤔

Icon size should be changed after set `fontSize="small"` or `sx={{ fontSize: 30 }}` 

### Steps to reproduce 🕹

Steps:

1. Go to https://mui.com/components/icons/#font-material-icons
2. See that icon size is not changed for the two last icons 

### Context 🔦

I tried to insert icon and change its size using <Icon> component

### Your environment 🌎

```
  System:
    OS: Linux 5.13 Linux Mint 20.2 (Uma)
  Binaries:
    Node: 16.13.0 - /usr/bin/node
    Yarn: Not Found
    npm: 8.1.0 - /usr/bin/npm
  Browsers:
    Chrome: 95.0.4638.69
    Firefox: 94.0
  npmPackages:
    @emotion/react: ^11.5.0 => 11.6.0 
    @emotion/styled: ^11.3.0 => 11.6.0 
    @mui/core:  5.0.0-alpha.54 
    @mui/icons-material: ^5.0.4 => 5.1.0 
    @mui/lab: ^5.0.0-alpha.54 => 5.0.0-alpha.54 
    @mui/material: ^5.0.4 => 5.1.0 
    @mui/private-theming:  5.1.0 
    @mui/styled-engine:  5.1.0 
    @mui/system:  5.1.0 
    @mui/types:  7.1.0 
    @mui/utils:  5.1.0 
    @mui/x-data-grid: ^5.0.0-beta.7 => 5.0.0-beta.7 
    @types/react: ^17.0.30 => 17.0.34 
    react: 17.0.2 => 17.0.2 
    react-dom: 17.0.2 => 17.0.2 
    typescript: ^4.4.4 => 4.4.4 

```
Repository: excalidraw
Issue: Feature Request: Pie Chart Generation
Labels: charts

I'm absolutely amazed by the copy/paste charting feature, and my girlfriend uses it to generate quick charts for presentations. I wanted to help her by creating the option to also generate pie charts.

I can implement it but based on past discussions it looks like there are several challenges (i.e. unique colors). I was wondering if anyone already has tips, ideas and ways to build these pie charts - I think it would be a useful chart option to add:)

**tl:dr: Can we implement pie chart generation? I can do it.**
Repository: vscode
Issue: Scope Emmet custom snippets to their respective workspaces
Labels: feature-request,emmet

See https://github.com/microsoft/vscode/issues/117519#issuecomment-952397804

For multi-root workspaces, 
Current behaviour: Emmet custom snippets from the first workspace folder are accessible from files under the second workspace folder, and vice versa.
Expected behaviour: Emmet custom snippets from the first workspace folder should only be accessible from files under the first workspace folder.
Repository: pytorch
Issue: ImportError: cannot import name 'ProcessGroup' from 'torch.distributed'
Labels: module: binaries,oncall: distributed,module: macos

## 🐛 Bug

When trying to import ProcessGroup from torch.distributed I get import error: 'ImportError: cannot import name 'ProcessGroup' from 'torch.distributed'. I guess it comes from the fact that I am using macOS with M1 chip and PyTorch does not provide torch.distributed with its pre-built package. Indeed, torch.distributed.is_available() is False.
## To Reproduce

Steps to reproduce the behavior:

`from torch.distributed import ProcessGroup`

## Environment

 - PyTorch Version: Tried on both 1.10 and 1.9.1 post3
 - OS (e.g., Linux): MacOS
 - How you installed PyTorch (`conda`, `pip`, source): conda
 - Python version: 3.8


cc @ezyang @seemethere @malfet @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang @albanD
Repository: pytorch
Issue: [subgraph_rewriter] Support for non-Tensor replacement
Labels: triaged,module: fx

## 🐛 Bug

Currently the pattern subgraph-rewriter can only represent Node, not primitive numbers etc.

## To Reproduce

```
from torch.fx import subgraph_rewriter
from torch.fx import symbolic_trace
import torch

class M(torch.nn.Module):
    def forward(self, x):
        return x + 3

def pattern(x, num):
    return x + num

def replacement(x, num):
    return x - num

m = M()
m = symbolic_trace(m)
subgraph_rewriter.replace_pattern(m, pattern, replacement)
print(m)

```

```
M()



def forward(self, x):
    add = x + 3;  x = None
    return add
```

## Expected behavior
`+` should be `replaced` to `-`

```
M()



def forward(self, x):
    add = x - 3;  x = None
    return add
```

cc @ezyang @SherlockNoMad
Repository: go
Issue: x/pkgsite: storage.Client displays as struct {} instead of struct { ... } in snippet
Labels: NeedsInvestigation,pkgsite

### What is the URL of the page with the issue?
 
https://pkg.go.dev/search?q=storage.Client&m=symbol

 
### What is your user agent?

Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/95.0.4638.54 Safari/537.36 
 
### Screenshot

<img width="689" alt="Screen Shot 2021-11-15 at 7 05 15 PM" src="https://user-images.githubusercontent.com/104030/141871973-cb4e7069-e71b-47d0-b467-7070c8c841ac.png">
 
### What did you do?

Search for storage.Client.
 
### What did you expect to see?
 
I expected the top snippet, for cloud.google.com/go/storage's Client,
to say `type Client struct { ... }`, like the many other results.

### What did you see instead?

It says `type struct {}` instead, which is unexpected and (I think) inaccurate.
Clicking through to type Client shows:

<img width="481" alt="Screen Shot 2021-11-15 at 7 08 27 PM" src="https://user-images.githubusercontent.com/104030/141872086-fef986ff-57ea-4713-af0c-b746a604478f.png">

which supports the expectation of the `...`.
Repository: rust
Issue: `must_not_suspend` should trigger for temporary in match expression (but does not)
Labels: A-lints,C-bug,A-async-await,AsyncAwait-Triaged

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust

#![feature(must_not_suspend)]
#![deny(must_not_suspend)]

use std::cell::RefCell;

struct S (RefCell<Inner>);

struct Inner {
}

impl Inner {
    async fn do_stuff(&self) {
        futures::future::ready(()).await;
    }
}

#[tokio::main]
async fn main() {
    let s = S ( RefCell::new(Inner {}) );
    println!("OUTside of match");
    match s.0.borrow_mut().do_stuff().await {
        () => {
          // The next line `panic()`-s.
          s.0.borrow_mut();
          println!("INside of match")
        }
    };
}
```

I expected to see this happen: compile-time error. Something like

```
error: `RefMut` held across a suspend point, but should not be
```

Instead, this happened: run-time panic (see below)

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`: nightly on playground (1.58.0-nightly, 2021-11-14 ad442399...)

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
thread 'main' panicked at 'already borrowed: BorrowMutError', src/main.rs:24:15
stack backtrace:
   0: rust_begin_unwind
             at /rustc/ad442399756573dccacb314b6bf8079964bcc72a/library/std/src/panicking.rs:498:5
   1: core::panicking::panic_fmt
             at /rustc/ad442399756573dccacb314b6bf8079964bcc72a/library/core/src/panicking.rs:106:14
   2: core::result::unwrap_failed
             at /rustc/ad442399756573dccacb314b6bf8079964bcc72a/library/core/src/result.rs:1613:5
   3: core::result::Result<T,E>::expect
             at /rustc/ad442399756573dccacb314b6bf8079964bcc72a/library/core/src/result.rs:1255:23
   4: core::cell::RefCell<T>::borrow_mut
             at /rustc/ad442399756573dccacb314b6bf8079964bcc72a/library/core/src/cell.rs:946:9
   5: playground::main::{{closure}}
             at ./src/main.rs:24:11
[...]
```

</p>
</details>
Repository: pytorch
Issue: Windows multi machine multi card training, card initialization in GLOO communication.
Labels: oncall: distributed,module: windows,triaged

[## 📚 Documentation
Thank you very much for your support for windows distributed training, which is a very friendly and excellent work. However, according to the documents in the following links, I have encountered some problems under Windows:
https://pytorch.org/docs/stable/distributed.html

The following problems occur when there are multiple machines and multiple cards:
It is stuck in GLOO communication initialization.

I have two computers equipped with Windows system. Each computer has a GPU of RTX 2080.
pytorch：1.10
environment： conda
python:  3.6.7
cuda: 10.2

One communication setting code of machine 0 is as follows:
init_method = f"file:///{os.path.join('F:/examples/distributed', 'ddp_example')}"
print("dist.init_process_group start")
dist.init_process_group(backend="gloo", init_method=init_method, rank=0, world_size=2)
print("dist.init_process_group over")

One communication setting code of machine 1 is as follows:
init_method = f"file://////{os.path.join('DESKTOP-GH9ALBP', 'distribute', 'ddp_example')}"
print("dist.init_process_group start")
dist.init_process_group(backend="gloo", init_method=init_method, rank=1, world_size=2)
print("dist.init_process_group over")

If I on machine 0, set rank = 0 ,  world_size = 1, and a single card is used, which is equivalent to a single card. GLOO communication can be initialized and trained normally.

Is there an official example of multi machine and multi card training under windows?




cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang @peterjc123 @mszhanyi @skyline75489 @nbcsm
Repository: neovim
Issue: bufadd does not sanitize windows drive letter capitalization
Labels: bug,platform:windows

### Neovim version (nvim -v)

NVIM v0.6.0-dev+463-g68b2a9e56

### Vim (not Nvim) behaves the same?

N/A (pretty sure the pathing code diverged a long time ago)

### Operating system/version

Widnows 10

### Terminal name/version

Windows Termianal

### $TERM environment variable

N/A

### Installation

source build

### How to reproduce the issue

```lua
file_location = os.getenv('TEMP')

local file_1 = file_location .. "\\file_1.txt"
local buffer_1 = vim.fn.bufadd(file_1)
print(vim.api.nvim_buf_get_name(buffer_1))

local drive_letter = string.sub(file_location, 1, 1)
local tail = string.sub(file_location, 2)
local perturbed_path = string.lower(drive_letter) .. tail
local file_2 = perturbed_path .. "\\file_2.txt"

local buffer_2 = vim.fn.bufadd(file_2)
print(vim.api.nvim_buf_get_name(buffer_2))
```


### Expected behavior

vim.api.nvim_buf_get_name should show consistent capitalization for drive letters on windows regardless of the input to buf_add (which based on the code seems like it depends more on bufadd behavior than buf_get_name)

### Actual behavior

```
C:\Users\michael\AppData\Local\Temp\file_1.txt
c:\Users\michael\AppData\Local\Temp\file_2.txt
```
Repository: go
Issue: encoding/binary: Varint signature/docs could benefit from name result parameters
Labels: Documentation,help wanted,NeedsFix

https://pkg.go.dev/encoding/binary@master#Varint says:

```
func Varint(buf []byte) (int64, int)
```
> Varint decodes an int64 from buf and returns that value and the number of bytes read (> 0). If an error occurred, the value is 0 and the number of bytes n is <= 0 with the following meaning:
```
n == 0: buf too small
n  < 0: value larger than 64 bits (overflow)
        and -n is the number of bytes read
```

--

That signature and docs (referencing `n` that's never named) are really asking to have named results.
Repository: terminal
Issue: x:Bind not Binding
Labels: Help Wanted,Area-TerminalControl,Product-Terminal,Issue-Task,good first issue

Per @Austin-Lamb ... We should avoid Binding everywhere we can and use x:Bind instead.

This represents not forgetting about this by tomorrow morning as it popped in my head and reminded me as I tried to sleep.
Repository: flutter
Issue: [Proposal] Add DatePicker and DateRangePicker Theme
Labels: c: new feature,framework,f: material design,f: date/time picker,c: proposal,team-design,triaged-design

## Use case
Hi, I was itching to get my app look like Material 3 spec. I didn't had any problems changing the border radiuses, font-size, app bar height, some padding, maybe not all of them, but mostly buttons without icons look fine. I have even customized a bit the TimePicker. Mainly changing OutlineBorder or ShapeBorder shapes to some elements, including the border radius of the Dialog. I looked at how can I customize the shape and the border radius of the selected and current dates in the DatePicker. I have found that it's shape is hardcoded in the code and cannot be changed by any means. Currently the DatePicker is a black box. The only thing I could customize is the Dialog radius. No colors, no text styles, no shapes. It is very tricky to rely on the colorScheme only as some parts of the DatePicker are shades of those colors, some other parts are colors with opacity.

## Proposal
I would like at least a minimal Theme for the DatePicker and DateRangePicker that gives the possibility to change the shape and the border radius of the selected/ current dates. In the end I would like to be able to customize the DatePicker the same way I can the TimePicker, it has colors, text styles, shapes.
Repository: create-react-app
Issue: Compress with gzip on npm run start
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

It's annoying having to deploy and check whether your improvements have worked or not, we can't get the localhost server to verify if lighthouse in devtools passes to a reasonable score.


### Describe the solution you'd like

Whilst developing and fixing issues with lighthouse in devtools, it would be nice, on localhost we can provide an argument `npm run start --compress=true` so locahost serves compress gzipped CSS and JS etc. 

This will prevent me from finding workarounds and increase my productivity tremendously.

Alternatively a flag on the package.json can also be an option, but I prefer the cli option, as it can be optionally added on cli `npm start --compressed` this way I can use it on the fly only when I need to and not always active/inactive.
Repository: angular
Issue: Angular property binding begin with colon should throw error
Labels: area: core,area: compiler,P4,compiler: parser

### Which @angular/* package(s) are the source of the bug?

compiler

### Is this a regression?

No

### Description

with this code, Angular will treat the button as **disabled**(xxxx is any random string)
```
<button :disabled="xxxx">Disabled Button</button>
```

First, is there any document that Angular support this code style begin with colon(:) for property binding ?
If not, I think it is better to throw  error



### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

_No response_

### Anything else?

_No response_