sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: create-react-app
Issue: Let jsxImportSource be configurable through tsconfig.json
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

Right now it's only suggested for `tsconfig.json` to set `"jsx": "react"` but it's not enforced. 

TS 4.1 will bring new JSX-related option ([`jsxImportSource`](https://github.com/weswigham/TypeScript/blob/e02e55f2f99384a30c6c99d7cd944459e1b4cdc4/src/compiler/commandLineParser.ts#L792)) and new possible values for the `jsx` option ([`react-jsx` & `react-jsxdev`](https://github.com/weswigham/TypeScript/blob/e02e55f2f99384a30c6c99d7cd944459e1b4cdc4/src/compiler/commandLineParser.ts#L5-L11)) - both of those changes are related to the new JSX runtimes.

TS also has an ability to change what exact JSX namespace is used for type-checking based on the used jsx factory [as per the documentation](https://www.typescriptlang.org/docs/handbook/jsx.html#factory-functions). This probably means that there is a problem for some possible configuration today:
TS can do its typechecking thinking that another factory is used (when one would configure [jsxFactory](https://www.typescriptlang.org/tsconfig#jsxFactory)) but in fact the emitted code uses the default factory of `React.createElement` because the transpilation is done by Babel that is not aware of TS configuration.

I'm not really interested in fixing this problem - I haven't found any issue about this so the audience for this is probably very little and it's just a possible problem that I have thought of and not something that affects me.

However, I would really love to be able to configure `jsxImportSource` globally and while you don't allow for Babel customization (which is understandable tradeoff here) you allow for some `tsconfig.json` configuration. It (`tsconfig.json`) seems to be a good match for inferring this particular configuration for a vast number of consumers (as TS is used by *a lot* of people).

### Motivation

I'm a maintainer of [Emotion](https://emotion.sh/docs/introduction) which is a popular CSS-in-JS solution for React (3.4M downloads/week) which comes with the CSS prop API that is based on `@jsx` pragma (although not all of our consumers use the CSS prop API as we expose the popular styled API as well).

Right now the `@jsx` pragma in CRA has to be used all over the place. We personally don't find it to be that problematic but we get complaints about this regularly from the community. Having a way to configure this (new transforms, not the old pragma) globally in CRA would probably result in a huge DX improvement for us.

### Describe the solution you'd like

Provide custom `importSource` to `@babel/preset-react`, based on the `jsxImportSource` from `tsconfig.json`

### Describe alternatives you've considered

If this is something that you don't want to support then I strongly believe that you should disallow configuring `jsxImportSource` in the `tsconfig.json` altogether because it causes a configuration mismatch between TS and Babel and this might be a footgun for people.

---

- [x] Implementation intent
Repository: three.js
Issue: NodeMaterial: Support MaterialX Standard Nodes
Labels: Suggestion,Bounty

I'd like to suggest that we work toward supporting equivalents of the MaterialX Standard Nodes within NodeMaterial. That is not necessarily to say that everything needs to be named the same, but ideally it should be possible to compose any given MaterialX node from, say, <5 three.js nodes. A lot of the standard nodes are actually covered already:

https://www.materialx.org/assets/MaterialX.v1.38D1.Spec.pdf

Note that this does not require supporting the MaterialX format; just having equivalent nodes seems like a good starting point. MaterialX provides [open source OSL code](https://www.materialx.org/ThirdPartySupport.html#Shaders-OSL) for each standard node, as well. MaterialX has support in tools by Adobe, Autodesk, and Pixar — if there's a real chance at being able to exchange shader networks with 3D modeling tools in the long run, I'd be willing to bet that MaterialX is it.
Repository: pytorch
Issue: Autograd support for the tensor multiplication of sparse tensors
Labels: module: sparse,module: autograd,triaged,function request

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->

Autograd support for the tensor multiplication of sparse tensors (sparse * sparse, sparse * dense).

## Motivation

<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->

Currently, an error occur during the calculation of autograd of a tensor generated by multiplication of sparse tensors.
The detail of error and sample code is described the link below.
https://discuss.pytorch.org/t/autograd-error-for-sparse-tensor-pytorch-1-6/99927

Since multiplication of sparse and dense tensor can be useful for building Graph Neural Network, 
the feature will help many users.

## Pitch

<!-- A clear and concise description of what you want to happen. -->

Autograd works without error regardless of the existence of sparse tensor for generating target variable.

## Alternatives

<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @aocsa @mruberry
Repository: flutter
Issue: setSystemUIOverlayStyle doesn't support hot-restart on Xiaomi Mi9 SE
Labels: e: device-specific,engine,a: layout,P2,team-engine,triaged-engine

## Steps to Reproduce

1.  Run your app. Status-bar is semi-trasparent.
2. Add the following code into your `main` function:
```dart
await SystemChrome.setSystemUIOverlayStyle(
    SystemUiOverlayStyle.light.copyWith(statusBarColor: custom_colors.mainWhite),
  );
```
3. Make a hot-reload. Status bar turns **black** (and it's undesired too, I wanted pure white color).
4. Remove the aforementioned code and make a hot-reload again.
Result: Status bar is still black!

<Details>
<Summary>Flutter doctor output</Summary>

```
[√] Flutter (Channel stable, 1.22.2, on Microsoft Windows [Version 10.0.19041.572], locale ru-RU)
    • Flutter version 1.22.2 at D:\Flutter\Flutter SDK
    • Framework revision 84f3d28555 (5 days ago), 2020-10-15 16:26:19 -0700
    • Engine revision b8752bbfff
    • Dart version 2.10.2

 
[√] Android toolchain - develop for Android devices (Android SDK version 30.0.0-rc2)
    • Android SDK at D:\Android_SDK
    • Platform android-30, build-tools 30.0.0-rc2
    • Java binary at: D:\Program Files\Android\Android Studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Android Studio (version 4.0)
    • Android Studio at D:\Program Files\Android\Android Studio
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] Connected device (1 available)
    • Mi 9 SE (mobile) • 2fb52829 • android-arm64 • Android 10 (API 29)
```

</Details>
Repository: vscode
Issue: vscode.debug.startDebugging should support named automatic (dynamic) and global (user settings) debug configurations
Labels: debug,under-discussion

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

I'd like to use `vscode.debug.startDebugging` to switch between debuggers (compare https://github.com/microsoft/vscode/issues/97921, where the proposed solution is to write an extension - I'd like to try this).

Unfortunately, `vscode.debug.startDebugging` is restricted to named configurations from `launch.json` files: that means, global (a.k.a. user settings) `launch` configurations are not supported, and neither are automatic (a.k.a. dynamic) debug configurations. This is according to the documentation here:
https://code.visualstudio.com/api/references/vscode-api#debug

A similar request has been made in https://github.com/microsoft/vscode/issues/77782, but that was hidden in an issue about very specific compound configurations. The core issue is much broader.

Alternatively, there should be a way to query all debug configurations available to the user in the _Run_ dropdown, without having to parse all possible `json` files.
Repository: kubernetes
Issue: RFE: Kubectl wait for multiple conditions
Labels: priority/backlog,area/kubectl,kind/feature,sig/cli,needs-triage

**What would you like to be added**:
I'd like `kubectl wait` to support multiple wait conditions at once so these are evaluated on the resource with the same ResourceVersion. Like:
```
kubectl wait <resource> --for='condition=Available=True' --for='condition=Progressing=False' --for='condition=Degraded=False
```

**Why is this needed**:
The current workaround
```
kubectl wait <resource> --for='condition=Available=True' && \
kubectl wait <resource> --for='condition=Progressing=False' && \
kubectl wait <resource> --for='condition=Degraded=False'
```
isn't atomic and the first condition can change before it evaluates the next one. It's also slower and uses more calls to the apiserver.

/sig cli
fyi @soltysh
Repository: storybook
Issue: Vue ArgsTable missing prop if slot with same name
Labels: bug,vue,block: argstable

**Describe the bug**
If I define a prop and a slot with the same name, `ArgsTable` only displays the `slot`

**To Reproduce**
Create a vue component with a prop and slot using the same name.
See component example below.

**Screenshots**
**Using the same name**
![image](https://user-images.githubusercontent.com/16105726/96722815-14d9fe00-13ae-11eb-9f13-201c4a31ed96.png)

**Changing the prop name**
![image](https://user-images.githubusercontent.com/16105726/96722942-3b983480-13ae-11eb-80a3-d0683780d04f.png)


**Code snippets**
```vue
<template>
  <span>
    <!-- @slot Pass a custom title -->
    <slot name="title">
      {{ title }}
    </slot>
  </span>
</template>

<script>
import Vue from 'vue';

export default {
  name: 'Title',
  props: {
    /** Title */
    title: {
      type: String,
      default: null,
    },
  },
};
</script>
```

**System**
```sh
Environment Info:

  System:
    OS: macOS 10.15.6
    CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
  Binaries:
    Node: 12.18.0 - ~/.nvm/versions/node/v12.18.0/bin/node
    npm: 6.14.4 - ~/.nvm/versions/node/v12.18.0/bin/npm
  Browsers:
    Chrome: 86.0.4240.80
    Firefox: 79.0
    Safari: 13.1.2
  npmPackages:
    @storybook/addon-a11y: ^6.0.26 => 6.0.26 
    @storybook/addon-essentials: ^6.0.26 => 6.0.26 
    @storybook/vue: 6.0.26 => 6.0.26 
```
Repository: go
Issue: x/build: "gomote ssh" to plan9-386 instance fails due to a "drawterm" loading error
Labels: OS-Plan9,Builders,NeedsInvestigation

```
~/go-review/src$ go version
go version devel +9848e93cb7 Wed Oct 21 09:34:39 2020 +0000 linux/amd64

~/go-review/src$ go version -m $(which gomote)
/usr/local/google/home/bcmills/bin/gomote: devel +1f48afe8db Fri Oct 16 14:26:34 2020 -0400
        path    golang.org/x/build/cmd/gomote
        mod     golang.org/x/build      (devel)
        dep     cloud.google.com/go     v0.54.0 h1:3ithwDMr7/3vpAMXiH+ZQnYbuIsh+OPhUPMFC9enmn0=
        dep     github.com/aws/aws-sdk-go       v1.30.15        h1:Sd8QDVzzE8Sl+xNccmdj0HwMrFowv6uVUx9tGsCE1ZE=
        dep     github.com/golang/groupcache    v0.0.0-20200121045136-8c9f03a8e57e      h1:1r7pUrabqp18hOBcwBwiTsbnFeTZHV9eER/QT5JVZxY=
        dep     github.com/golang/protobuf      v1.3.4  h1:87PNWwrRvUSnqS4dlcBU/ftvOIBep4sYuBLlh6rX2wk=
        dep     github.com/googleapis/gax-go/v2 v2.0.5  h1:sjZBwGj9Jlw33ImPtvFviGYvseOtDM7hkSKB7+Tv3SM=
        dep     github.com/jmespath/go-jmespath v0.3.0  h1:OS12ieG61fsCg5+qLJ+SsW9NicxNkg3b25OyT2yCeUc=
        dep     go.opencensus.io        v0.22.3 h1:8sGtKOrtQqkN1bp2AtX+misvLIlOmsEsNd+9NIcPEm8=
        dep     golang.org/x/net        v0.0.0-20200301022130-244492dfa37a      h1:GuSPYbZzB5/dcLNCwLQLsg3obCJtX9IJhpXkvY7kzk0=
        dep     golang.org/x/oauth2     v0.0.0-20200107190931-bf48bf16ab8d      h1:TzXSXBo42m9gQenoE3b9BGiEpg5IG2JkU5FkPIawgtw=
        dep     golang.org/x/sync       v0.0.0-20190911185100-cd5d95a43a6e      h1:vcxGaoTs7kV8m5Np9uUNQin4BrLOthgV7252N8V+FwY=
        dep     golang.org/x/sys        v0.0.0-20200302150141-5c8b2ff67527      h1:uYVVQ9WP/Ds2ROhcaGPeIdVq0RIXVLwsHlnvJ+cT1So=
        dep     golang.org/x/text       v0.3.2  h1:tW2bmiBqwgJj/UpqtC8EpXEZVYOwU0yG4iWbprSVAcs=
        dep     google.golang.org/api   v0.20.0 h1:jz2KixHX7EcCPiQrySzPdnYT7DbINAypCqKZ1Z7GM40=
        dep     google.golang.org/genproto      v0.0.0-20200305110556-506484158171      h1:xes2Q2k+d/+YNXVw0FpZkIDJiaux4OVrRKXRAzH6A0U=
        dep     google.golang.org/grpc  v1.27.1 h1:zvIju4sqAGvwKspUQOhwnpcqSbzi7/H6QomNNjTL4sk=
        dep     gopkg.in/inf.v0 v0.9.1  h1:73M5CoZyi3ZLMOyDlQh031Cx6N9NDJ2Vvfl76EDAgDc=

~/go-review/src$ gomote ssh user-bcmills-plan9-386-0
$ ssh -p 2222 user-bcmills-plan9-386-0@farmer.golang.org # auth using https://github.com/bcmills.keys
Enter passphrase for key '/usr/local/google/home/bcmills/.ssh/id_rsa':
# Welcome to the gomote ssh proxy, bcmills.
# Connecting to/starting remote ssh...
#
# `gomote push` and the builders use:
# - workdir: /tmp/workdir
# - GOROOT: /tmp/workdir/go
# - GOPATH: /tmp/workdir/gopath
# - env: GO_BUILDER_NAME=plan9-386 GO_TEST_TIMEOUT_SCALE=3
# Happy debugging.
# Plan9 user/pass: …
/usr/local/bin/drawterm: error while loading shared libraries: libX11.so.6: cannot open shared object file: No such file or directory
Connection to farmer.golang.org closed.
```

CC @0intro @millerresearch @fhs @golang/release
Repository: vscode
Issue: [html] Unecessary warning when script contains quotes on the same line as an onFoo attribute using the same quotes
Labels: bug,html

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.50.1
- OS Version: Windows 10 2004

Steps to Reproduce:

1. Open HTML file and paste: `<script>"L"</script><a onclick="show();"></a>`
2. Notice 

![image](https://user-images.githubusercontent.com/15063294/96733057-515f2700-13b9-11eb-9b5f-befaf29a0f93.png)

3. When the line is split into 2 it's not affected

```html
<script>"L"</script>
<a onclick="show();"></a>
```

Originally reported in: https://github.com/trullock/NUglify/issues/166. As the owner of NUglify states: The problem is the VSC HTML parser/IntelliSense when you have a script which contains quotes on the same line as an onFoo attribute using the same quotes

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
Repository: rust
Issue: Lint on calling `to_owned` on a reference
Labels: A-lints,T-compiler,C-bug

The `ToOwned` trait has a blanket impl for `T: Clone`. Since references implement `Clone`, it's possible to call `&SomeNonCloneType.to_owned()` - this returns a new reference `&SomeNonCloneType`, *not* an owned `SomeNonCloneType`. This can result in a confusing error message:

```rust
struct Foo;

fn main() {
    let a = &Foo;
    let b: Foo = a.to_owned();
}
```

```
error[E0308]: mismatched types
 --> src/main.rs:5:18
  |
5 |     let b: Foo = a.to_owned();
  |            ---   ^^^^^^^^^^^^ expected struct `Foo`, found `&Foo`
  |            |
  |            expected due to this

```

Here, adding `#[derive(Clone)]` to `Foo` makes this code compile, but it's not at all obvious from looking at the error message.

We should lint on calling `val.to_owned()` or `val.clone()`, when `val` is a reference, and treated as the `Self` type (as opposed to being called on a reference to some non-reference type that implemented `Clone`). This is very likely a mistake, and in any case can be written more succinctly as `*val`
Repository: pytorch
Issue: Future returned by RPC should print a warning message on destruction if it's not waited
Labels: oncall: distributed,module: bootcamp,triaged,enhancement,module: rpc

#46559 mentioned that it's hard to debug async RPC, as the error is only thrown when users call `Future.wait()` but users might miss that. 

@lw suggested that, to have a better user experience, one option could be let the [Future](https://github.com/pytorch/pytorch/blob/master/aten/src/ATen/core/ivalue_inl.h#L308) object record whether it has been waited or not. If it was not waited but destructed, it can print a warning message to remind users. 

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @rohan-varma @xush6528 @jjlilley @osalpekar @jiayisuse @agolynski
Repository: pytorch
Issue: Converting object detector model to TorchScript
Labels: oncall: jit

Hi,
Currently I try to convert this https://github.com/yhenon/pytorch-retinanet implentation of retinanet to torchscript so be able to make inference in c++ environment. But faced with some problems. 

P5_x : torch.Tensor = self.P5_1(C5) , in this line I had an error as : Tried to access nonexistent attribute or method 'P5_1' of type 'Tensor (inferred)'.:

So P5_1 is nn.Conv2d(C5_size, feature_size, kernel_size=1, stride=1, padding=0). 

So what should I do to eliminate this error.
I hope question is clear enough. Thanks in advance

cc @gmagogsfm
Repository: angular
Issue: Better documentation for multiple projects within one workspace
Labels: P4,area: docs

### Bug Report or Feature Request (mark with an `x`)
```
- [ ] bug report -> please search issues before submitting
- [ ] feature request
- [x] documentation improvement request
```

Regarding: https://github.com/angular/angular-cli/wiki/stories-multiple-projects

It would be nice to have a better documentation and examples about how to handle 2 or more applications which run totally independently but still want to share some code. From the current documentation page it is not very clear how to achieve it and what are the best practices.
Repository: flutter
Issue: Regression in timeToFirstFrameRasterizedMicros flutter_gallery_ios32__start_upsmoke_catalina_start_up_ios
Labels: c: regression,tool,c: performance,perf: speed,team: benchmark,P2,team-tool,triaged-tool

See https://flutter-flutter-perf.skia.org/e/?begin=1603144085&end=1603212591&keys=Xe58c4638b290dfd947817edd92e937ac&num_commits=50&request_type=1&xbaroffset=22096.

First occurred at https://github.com/flutter/flutter/pull/68538, so I'm wondering if this caused by the test and not really the regression. @jonahwilliams can you confirm?
Repository: create-react-app
Issue: Cannot add license key to generated package.json file in template
Labels: needs triage,issue: bug report

<!--
    Please note that your issue will be fixed much faster if you spend about
    half an hour preparing it, including the exact reproduction steps and a demo.

    If you're in a hurry or don't feel confident, it's fine to report bugs with
    less details, but this makes it less likely they'll get fixed soon.

    In either case, please use this template and fill in as many fields below as you can.

    Note that we don't provide help for webpack questions after ejecting.
    You can find webpack docs at https://webpack.js.org/.
-->

### Describe the bug

**When using the 4.0 alpha**, I cannot figure out a way to add a license key to the package.json file in the template. Therefore when I create a project with my create-react-app template it always gives me the "warning ../../package.json: No license field" warning. Please add the ability to add a license key in the template.json file of the templates or let me know if there is already a way to achieve this.

### Steps to reproduce

<!--
  How would you describe your issue to someone who doesn’t know you or your project?
  Try to write a sequence of steps that anybody can repeat to see the issue.
-->

(Write your steps here:)

1. Using the 4.0 alpha of create-react-app and a custom template, add license key in template.json
2. Create a project with your custom template
3. Run 'yarn start'

### Expected behavior

<!--
  How did you expect the tool to behave?
  It’s fine if you’re not sure your understanding is correct.
  Just write down what you thought would happen.
-->

To start up with no warnings and have a "license" key in the package.json file.

### Actual behavior

<!--
  Did something go wrong?
  Is something broken, or not behaving as you expected?
  Please attach screenshots if possible! They are extremely helpful for diagnosing issues.
-->

It started up, but with the "warning ../../package.json: No license field" warning and does not have a "license" key in the package.json file.
Repository: storybook
Issue: Question: Does a plugin exists to simulate safe-area-inset margins ?
Labels: feature request,addon: viewport

# Does a plugin exists to simulate safe-area-inset margins with storybook ? 

Typicaly for tablets or mobile devices.

# Goal

Don't waste time testing on the devices, but test directly in storybook

Thanks a lot for your help !
Repository: go
Issue: doc: introduce a page for CI best practices
Labels: Documentation,NeedsInvestigation

Most CI scripts and defaults do just the basics: `go test ./...`

There are many more commands that likely make sense for a majority of projects, and some are well known, but we don't have a single place to document and maintain them well. For example:

* Enforce `gofmt` from a specific version of Go, e.g. `test -z $(gofmt -l .)` or `gofmt -l -check .` with https://github.com/golang/go/issues/46289
* Use `go test -race ./...` to catch data races in tests
* Use `go vet ./...`, since `go test` only runs a subset of `go vet`
* Ensure that  `go mod tidy` results in no changes in `go.mod` and `go.sum` - or `go mod tidy -check` with https://github.com/golang/go/issues/27005
* Use `go mod verify` to ensure that `go.sum` agrees with what's in the module cache
* Use `go test -run=- -bench=. -benchtime=1x ./...` to catch stale benchmarks (see https://github.com/golang/go/issues/41824)
* When explicitly testing multiple Go versions via a matrix, set `GOTOOLCHAIN=local` to ensure old versions do not automatically download and use newer toolchains

And potentially `staticcheck ./...` too, since it's now sort of recommended by gopls as an extension to `go vet`. Though note that this should be a small set of recommendations that most projects should follow, so it shouldn't include an endless list of linters that might be interesting to some users.

We should include a ready-to-use script containing all of the recommended steps, for example in POSIX Shell. We could document each step directly via script comments, meaning that the entire thing could be copy-pasted and self-documenting.

I'm happy to kickstart this work during the freeze. /cc @bcmills @jayconrod @myitcv @jadekler