sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: create-react-app
Issue: Percentage opacities in CSS files will compile to "1%" in a production build
Labels: tag: underlying tools,issue: bug report

Originally reported by @mruiz42: https://github.com/facebook/react/issues/19747

* Source code: https://codesandbox.io/s/trusting-glitter-0icl7
* Deployed sandbox: https://csb-0icl7.netlify.app/

[Recap of the problem](https://github.com/facebook/react/issues/19747#issuecomment-686297888), courtesy of @eps1lon:

> What a frustrating bug. It originates in `react-scripts` (reported in https://github.com/facebook/create-react-app/issues/7980). It seems like the underlying fix wasn't propagated. If you go further down you find https://github.com/NMFR/optimize-css-assets-webpack-plugin/issues/118 and https://github.com/cssnano/cssnano/pull/881. 
>
> I'd suggest tracking down which package didn't publish the fix by upgrading their relevant dependencies. 
>
> Maybe @gaearon can move this issue to create-react-app. Otherwise we should file a [new bug report with create-react-app](https://github.com/facebook/create-react-app/issues/new?labels=issue%3A+bug+report%2C+needs+triage&template=bug_report.md) and close it here.
Repository: neovim
Issue: Structural Editing : Tracking Issue
Labels: enhancement,syntax,treesitter

# Structural editing

Currently, we use treesitter as an overlay over buffer contents.
While this is already really cool, what would be better is being able to edit the tree itself and change the content of the buffer, keeping it in a valid state syntactically speaking : this is Structural Editing.

We can think of two way of using it :arrow_double_down: 

- Inserting things in the buffer, and keeping it in a valid state, think of it as some kind of snippet
- Changing multiple parts of the tree at the same time, by moving nodes around, like some really powerful search and replace

## Blockers

We need the insights of @maxbrunsfeld here, because the relation between text and tree is only one way as of today (and from what we know), but we don't have a way to edit the tree itself, and dump the new text generated from there.

Furthermore, we would need to insert partially complete nodes, like a `binary_expression` node looking like
```
binary_expression
    left: MISSING
    right: MISSING
```
So that one can go down in this tree by adding the nodes one by one.
Repository: vscode
Issue: setting UI: support color settings
Labels: feature-request,settings-editor

#105811 added the `screencastMode.mouseIndicatorColor` setting representing a color

- open the JSON settings (JSON), add "screencastMode.mouseIndicatorColor": "#ff00ff"
- see that there's a color decorator and that there's validation if you change the value to an invalid color

Now open the same setting in the settings UI:
- enter an invalid value `#foo`. No error
- a color decorator would also be nice

The color support in JSON comes from annotating the configuration schema with `"format": "color-hex"`
Repository: go
Issue: x/playground: falsely detects a deadlock when running Cmd.StderrPipe example code
Labels: NeedsDecision

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

The playground

### Does this issue reproduce with the latest release?

Works on latest released web site

### What did you do?

Clicked "Run" on the [example for Cmd.StderrPipe](https://golang.org/pkg/os/exec/#Cmd.StderrPipe)


### What did you expect to see?

It runs

### What did you see instead?

```
fatal error: all goroutines are asleep - deadlock!

goroutine 1 [IO wait]:
internal/poll.runtime_pollWait(0x7efd408c4ee8, 0x72, 0x505300)
	/usr/local/go-faketime/src/runtime/netpoll.go:220 +0x55
internal/poll.(*pollDesc).wait(0xc000104198, 0x72, 0xc00011c001, 0x200, 0x200)
	/usr/local/go-faketime/src/internal/poll/fd_poll_runtime.go:87 +0x45
internal/poll.(*pollDesc).waitRead(...)
	/usr/local/go-faketime/src/internal/poll/fd_poll_runtime.go:92
internal/poll.(*FD).Read(0xc000104180, 0xc00011c000, 0x200, 0x200, 0x0, 0x0, 0x0)
	/usr/local/go-faketime/src/internal/poll/fd_unix.go:159 +0x1b1
os.(*File).read(...)
	/usr/local/go-faketime/src/os/file_posix.go:31
os.(*File).Read(0xc000102018, 0xc00011c000, 0x200, 0x200, 0xc00011c000, 0x0, 0x0)
	/usr/local/go-faketime/src/os/file.go:116 +0x71
bytes.(*Buffer).ReadFrom(0xc000068e88, 0x505200, 0xc000102018, 0x505200, 0x4eb2f0, 0x0)
	/usr/local/go-faketime/src/bytes/buffer.go:204 +0xb1
io/ioutil.readAll(0x505200, 0xc000102018, 0x200, 0x0, 0x0, 0x0, 0x0, 0x0)
	/usr/local/go-faketime/src/io/ioutil/ioutil.go:36 +0xe5
io/ioutil.ReadAll(...)
	/usr/local/go-faketime/src/io/ioutil/ioutil.go:45
main.main()
	/tmp/sandbox971301426/prog.go:21 +0x1ca

Program exited.
```
Repository: fastapi
Issue: Automatic OPTIONS request with route schema
Labels: feature,investigate,reviewed

### First check

Yes to all (great list of checks btw, I might copy them to pydantic 👍 )

### Thank you

@tiangolo FastAPI is great. This is the first time I've used it in production and I'm really impressed by both the range of features and particularly the documentation. I've written and deployed web apps using django, flask, aiohttp, starlette and now fastapi. FastAPI is the only python web framework I've seen to come close to django in terms of quality of documentation, it's definitely now my go-to web framework.

**Thank you for the amazing project**, I feel really proud to have contributed to it indirectly.

### Feature Request

The only thing I've seen missing from fastpi is support for informative OPTIONS requests for all/most/some endpoints, automatically included based in the route's definition.

I effectively want the following:

```py
class LoginForm(BaseModel):
    email: EmailStr
    password: SecretStr

@app.post('/login/')
async def login(login_form: LoginForm):
   ...

@app.options('/login/', include_in_schema=False)
async def login_options():
    return LoginForm.schema(by_alias=True)
```

Without having to define the second endpoint. This is so my react frontend can build forms without having to duplicate the field definitions.

I guess it might have to be slightly more complex to include parameters, query args and body model(s).

I know I can get the information I need from `/openapi.json`, but that involves more processing in js and more data downloaded.

In the past when I've implemented a feature like this myself, I had to deal with `OPTIONS` requests associated with preflight checks separately, but that's relatively easy by looking for the `Access-Control-Request-Method` header.

I guess if this feature was to be approved it would have to be optional, default off. I guess through a keyword arg on `FastAPI`, `include_router` and each route.
Repository: godot
Issue: Crash IDE when connecting nodes
Labels: bug,confirmed,topic:visualscript,crash


**Godot version:**
v3.2.3.rc4.official


**OS/device including version:**
OS: Windows 10 64-bit
Graphics card: NVIDIA GeForce 930M


**Issue description:** 
When these nodes are connected, the IDE just crashes.
I understand that this is not the correct connection, but it can be reported somehow better =)

**Steps to reproduce:**
![error](https://user-images.githubusercontent.com/7114353/92126869-5ec05200-ee09-11ea-952a-f508226891d1.jpg)

**Minimal reproduction project:**
[error.zip](https://github.com/godotengine/godot/files/5169187/error.zip)
Repository: rust
Issue: Add regression tests for rust-lldb python wrappers
Labels: A-testsuite,T-compiler,T-infra,C-bug

I am posting this issue mostly as a reminder that we should investigate why our current test suite didn't seem to catch the breakage from #76006 on any of our CI platforms
Repository: PowerToys
Issue: PowerToysRun: Custom labels on results
Labels: Idea-Enhancement

It would be useful to add "tags" or "labels" to current results (mainly for running process) and use them in search. 
Something like labels in github issues or gmail.

For example if I have many Chrome or VisualStudio windows opened, now I am "forced" to search for "chrome":

![image](https://user-images.githubusercontent.com/971450/92137608-97fac100-ee0d-11ea-9d3c-9c7b02e5986e.png)

but maybe I know that first chrome window contains a "javascript tutorial" and the second one are "assigned issues" so why not naming and searching them exactly as I have in mind:
just right click -> choose "add label" -> input label

![image](https://user-images.githubusercontent.com/971450/92136576-7816cd80-ee0c-11ea-89a2-f8597573e575.png)

and finally I can search for them:

![image](https://user-images.githubusercontent.com/971450/92138653-ed839d80-ee0e-11ea-99f2-b4338b17b2bc.png)
Repository: rust
Issue: Add file owner to os::windows::fs::MetadataExt
Labels: O-windows,T-libs-api,C-feature-request,A-io

`os::unix::fs::MetadataExt` has [a uid method](https://doc.rust-lang.org/std/os/unix/fs/trait.MetadataExt.html#tymethod.uid) for getting the file owner, but there is no equivalent for `os::windows::fs::MetadataExt`.

It would be great to have this as an option.
Repository: terminal
Issue: Allow color fields to refer back to the active color scheme (like "cursorColor = yellow")
Labels: Area-Settings,Product-Terminal,Issue-Task

I can't do this

"cursorColor": "yellow"

AFAICT, to get a "yellow" cursor I must (look up and) hard code the "yellow" value from the current theme.

Is there a better way?  If not I suggest that you allow color names for "cursorColor"

And what's the difference between "#rgb" and "#rrggbb"?
Repository: kubernetes
Issue: test/e2e/upgrade tests are not running
Labels: priority/important-soon,sig/cluster-lifecycle,sig/testing,kind/failing-test,sig/architecture,lifecycle/frozen

**Which test(s) are failing**:

All tests in https://github.com/kubernetes/kubernetes/tree/master/test/e2e/upgrades

**Which jobs are failing**:

All jobs running those tests, e.g. https://prow.k8s.io/job-history/gs/kubernetes-jenkins/logs/ci-kubernetes-e2e-gce-stable2-stable1-upgrade-cluster

**Since when has it been failing**:

1.18 (see https://github.com/kubernetes/release/pull/868#issuecomment-673727541)

**Reason for failure**:

The immediate cause is that the bringup scripts for the upgrade tests expect sha1 hash files that were removed in 1.18. If that was fixed, I don't know what the next blocker would be.

**Anything else we need to know**:

Lack of upgrade test signal puts the project at risk for introducing regressions. Examples of things these tests caught in the past or that we have open issues to add to our upgrade test suite:
- https://github.com/kubernetes/kubernetes/issues/64789#issuecomment-394883173
- https://github.com/kubernetes/kubernetes/issues/78904
- https://github.com/kubernetes/kubernetes/issues/78633

It also blocks ongoing dev/feature work:
- https://github.com/kubernetes/enhancements/pull/1912#discussion_r463692617
- https://github.com/kubernetes/kubernetes/pull/93455#issuecomment-686539615

cc @kubernetes/sig-testing @BenTheElder
Repository: terminal
Issue: Text selection breaks in funny ways when program keeps printing to console
Labels: Help Wanted,Area-Rendering,Issue-Bug,Area-TerminalControl,Product-Terminal,Priority-2

![image](https://user-images.githubusercontent.com/1041752/92165193-f12b1a80-ee36-11ea-8dd9-a8442fa0a0a4.png)
Repository: PowerToys
Issue: [Run] Improve priority of results having match from start of a word.
Labels: Issue-Bug,Product-PowerToys Run,Area-Quality

I would expect `Microsoft teams` to show above `Steam` in results on querying `Team`.

![issue_teams](https://user-images.githubusercontent.com/10995909/92165626-2fe7b300-edec-11ea-96ac-65b0c48392ec.png)
Repository: go
Issue: x/website: make supported OS versions easier to find
Labels: Documentation,NeedsFix,website

I spent a long time just now trying to identify which versions of Go support which operating system versions.
I thought this used to be documented on the install page.
All I can find is the text _inside_ the "featured download" buttons on https://golang.org/dl/.
That can't be the only source for this info.
FreeBSD is a first-class port but not a featured download.
What version of FreeBSD do we support?
I can't find out.

https://golang.org/doc/install/source links back to /doc/install for "overall system requirements".

It is possible that the recent install page rewrite is what dropped the info, and we need to bring it back one way or another.
Repository: pytorch
Issue: [Feature Request] Add an option to run GPU tests only, and skip all CPU tests
Labels: feature,module: tests,triaged

## 🚀 Feature

Add an option to run GPU tests only, and skip all CPU tests

For example, we can have an environment variable `PYTORCH_TEST_GPU_ONLY=1`.

## Motivation

Usually, when people only want to test GPU functionalities, they can skip CPU tests to save plenty of times. 

## Pitch

<!-- A clear and concise description of what you want to happen. -->

For example, some pytorch tests look like (assuming pytorch built with GPU)
```python
def test_something(self, device):
    # do something
```
At runtime, two tests `test_something_cpu` and `test_something_cuda` will be generated. The goal is to skip the `test_something_cpu` test and only run `test_something_cuda`. 

For example, we can do it like this
```bash
PYTORCH_TEST_GPU_ONLY=1 python test/run_test.py
```

## Alternatives

N/A

## How to implement 

If I understand the code correctly, this feature can be easily implemented like this

1. Add `TEST_GPU_ONLY = os.getenv('PYTORCH_TEST_GPU_ONLY', '0') == '1' ` here
https://github.com/pytorch/pytorch/blob/665feda15bc45d0f50326596ecde6f2d96ac6644/torch/testing/_internal/common_utils.py#L346-L347

2. Add something like
```python
    if TEST_GPU_ONLY:
        fullname = self.id().lower()
        is_cuda_test = 'gpu' in fullname or 'cuda' in fullname or 'cuda' in torch.tensor([]).device.type
        if not is_cuda_test:
            raise unittest.SkipTest("Test is probably not a GPU test. We disabled it with PYTORCH_TEST_GPU_ONLY")
```
here in `setup` of `class common_utils.TestCase`
https://github.com/pytorch/pytorch/blob/665feda15bc45d0f50326596ecde6f2d96ac6644/torch/testing/_internal/common_utils.py#L825-L833

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->

N/A 

cc @mruberry @VitalyFedyunin @ptrblck @ngimel
Repository: material-ui
Issue: Add Image component
Labels: new feature,waiting for 👍

- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Summary 💡

Implement an enhanced version of the native `<img>` element.

## Examples 🌈

```jsx
import { Image } from '@material-ui/core';

<Image src="" />
```

## Motivation 🔦

A couple of features we could bring:

1. Use `display: inline-block;` to avoid layout jumps when the image is loading or broken.
1. Provide a custom fallback component when the image fails to load.
1. Support a loading indicator when the image takes too much time to load, e.g Skeleton.
1. Add a smooth animation for displaying the image once loaded.
1. Support a placeholder to display while image's loading. An image of lower resolution.
1. Lazy loading? Maybe not relevant considering https://caniuse.com/#feat=loading-lazy-attr and https://web.dev/native-lazy-loading/.
1. Support aspect ratio. For instance, it allows rendering an image with a width constraint without having to wait for the image to load over the networks to resolve its height (which might lead to a layout shift).

## Benchmark

- https://github.com/imgix/react-imgix
- https://github.com/gatsbyjs/gatsby/blob/master/packages/gatsby-image/src/index.js
- https://amp.dev/documentation/examples/components/amp-img/?format=websites
- https://vuetifyjs.com/en/components/images/#images
- https://bootstrap-vue.js.org/docs/components/image
- https://github.com/chakra-ui/chakra-ui/blob/master/packages/chakra-ui/src/Image/index.js
- https://github.com/jossmac/react-images
- https://backpack.github.io/components/image?platform=web
- https://ionicframework.com/docs/api/img
- https://github.com/FormidableLabs/react-progressive-image
- https://joshwcomeau.com/performance/embracing-modern-image-formats/
- https://github.com/konvajs/use-image/
- https://github.com/mbrevda/react-image
- https://github.com/gokcan/react-shimmer
- https://react-spectrum.adobe.com/react-spectrum/Image.html
- https://github.com/fpapado/react-lazy-images
- https://github.com/react-component/image
Repository: material-ui
Issue: Support simple badges
Labels: new feature,waiting for 👍,component: badge

- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Summary 💡

Broaden the use cases supported by the Chip/Badge component, make it support the use cases of what most designers and developers associate with a "badge".

## Examples 🌈

```jsx
import { Chip } from '@material-ui/core';

<Typography variant="h3">
   Example heading
  <Chip size="xsmall" color="success">New</Badge>
</Typography>
```

<img width="245" alt="Capture d’écran 2020-09-04 à 01 30 42" src="https://user-images.githubusercontent.com/3165635/92183368-72da7280-ee4e-11ea-98d7-42b5ba134f9c.png">

## Motivation 🔦

Designers often display "badges" in a wide variety of contexts: table cell, side nav link, headline1 adornment, etc.
The current Chip component tries to solve this problem, but it could likely be improved:

- Broaden the supported colors
- Provide a mode with more density
- Allow changing the shape from circular to rounded

At the same time, we have a Badge component that supports a narrower use case for what most expect with what a "badge" is traditionally used for.

## Benchmark

- https://getbootstrap.com/docs/4.5/components/badge/#contextual-variations
- https://theme-ui.com/components/badge
- https://chakra-ui.com/badge
- https://ant.design/components/badge/#components-badge-demo-no-wrapper
- https://tailwindui.com/components/application-ui/elements/badges
Repository: material-ui
Issue: Add Stat component
Labels: new feature,discussion,waiting for 👍

- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Summary 💡

Display one number on a dashboard.

## Examples 🌈

```jsx
  <Stat>
    <StatLabel>Avg. Open Rate</StatLabel>
    <StatNumber>58.16%</StatNumber>
    <StatHelperText>
      <StatArrow type="increase" />
      5.4%
    </StatHelperText>
  </Stat>
```

<img width="186" alt="Capture d’écran 2020-09-04 à 13 17 45" src="https://user-images.githubusercontent.com/3165635/92233697-0a70ad00-eeb1-11ea-943a-64cb0044032c.png">

*This is a fictional example, it's not meant to be the final design nor API*

## Motivation 🔦

[Many](https://material-ui.com/blog/2020-developer-survey-results/#15-what-are-you-building) developers use Material-UI to build dashboards. For such an item, it's very frequent to have to display stats. 

## Benchmarks

- Public: https://mui-org.notion.site/Stat-component-cbf8ec1d45a34f3fadd6b16f21114487
- For edits: https://www.notion.so/mui-org/Stat-component-cbf8ec1d45a34f3fadd6b16f21114487
Repository: terminal
Issue: Build with ASAN (address sanitizer) and run against those builds in Helix
Labels: Area-Build,Product-Meta,Issue-Task,Area-CodeHealth

> ASan is a fast memory error detector that can find runtime memory issues such as use-after-free and perform out of bounds checks.
> ([source](https://devblogs.microsoft.com/cppblog/addresssanitizer-asan-for-windows-with-msvc/))
Repository: pytorch
Issue: Deadlock with RPC and dist.barrier() for TensorPipeAgent and NCCL.
Labels: triaged,module: nccl,module: rpc,module: tensorpipe

## 🐛 Bug

I ran into an interesting issue when using TensorPipe GPU tensors with dist.barrier() (backend being NCCL). Something simple like the following, would hang occasionally due to a deadlock (each worker executes the following):

```
# Worker0 sends RPC to Worker1 and Worker1 sends to Worker0
rpc.rpc_sync(dst, torch.add, args=(t, t))
dist.barrier()
```

The reason is as follows:

1. On worker1, the rpc_sync completes faster and it is waiting on dist.barrier() to completed.
2. worker0 now performs an RPC using GPU tensors on worker1. This causes a CPU to GPU copy on worker1 which in turn calls a cudaStreamSynchronize().
3. Although, the cudaStreamSynchronize() gets blocked since the barrier() hasn't completed yet on the GPU.
4. Since, cudaStreamSynchronize() is blocked on the remote end the rpc on worker0 never completed and as a result it never executes the barrier().
5. We essentially have a deadlock which causes the hang.

I got around this in my unit test by using rpc._wait_all_workers or we can use "gloo" in dist.barrier() to get around this
## To Reproduce

The following code with TensorPipeAgent as the RPC backend:

```
# Worker0 sends RPC to Worker1 and Worker1 sends to Worker0
rpc.rpc_sync(dst, torch.add, args=(t, t))
dist.barrier()
```
## Expected behavior

Ideally, something single like this causing a deadlock would be surprising for users and maybe we can use a different stream to execute some of the TensorPipe ops.

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @rohan-varma @xush6528 @jjlilley @osalpekar @jiayisuse @lw @beauby
Repository: flutter
Issue: [macOS] Launch isolate with an entrypoint from another library?
Labels: platform-mac,c: proposal,a: desktop,P2,team-macos,triaged-macos

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

I'm trying to port the [`flutter_isolate`](https://pub.dev/packages/flutter_isolate) plugin to macOS. On iOS, it uses the [`-runWithEntrypoint:libraryURI:`](https://api.flutter.dev/objcdoc/Classes/FlutterEngine.html#/c:objc(cs)FlutterEngine(im)runWithEntrypoint:libraryURI:) function in [`FlutterEngine`](https://api.flutter.dev/objcdoc/Classes/FlutterEngine.html) to launch an isolate with an entrypoint inside the plugin's Dart code - but this function doesn't seem to exist on macOS. Only [`-runWithEntrypoint:`](https://api.flutter.dev/objcdoc/Classes/FlutterEngine.html#/c:objc(cs)FlutterEngine(im)runWithEntrypoint:) does, which can only launch isolates from the main library.

Futhermore, the [`FlutterCallbackCache`](https://api.flutter.dev/objcdoc/Classes/FlutterCallbackCache.html) and [`FlutterCallbackInformation`](https://api.flutter.dev/objcdoc/Classes/FlutterCallbackInformation.html) classes seem to be missing, making it impossible to get information from a callback id.
## Proposal

I'd like there to be a way on macOS to do what [`-runWithEntrypoint:libraryURI:`](https://api.flutter.dev/objcdoc/Classes/FlutterEngine.html#/c:objc(cs)FlutterEngine(im)runWithEntrypoint:libraryURI:) can do on iOS.