sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: storybook
Issue: Make subcomponents more customizable and controllable
Labels: feature request,addon: docs,block: argstable

Subcomponents are very useful, but its implementation is not customizable and not controllable. 

**The problem:**

```ts
const controls: Meta<TypographyProps> = {
         title: 'Typography',
         component: Typography,
         subcomponents: {
              'Title': Typography.Title
         }
         argTypes: {
              ....
        }
}
```

<img width="1033" alt="Снимок экрана 2020-10-23 в 0 04 28" src="https://user-images.githubusercontent.com/803674/96929841-7d66cf00-14c3-11eb-8996-8407807ebf9b.png">

<img width="1045" alt="Снимок экрана 2020-10-23 в 0 04 40" src="https://user-images.githubusercontent.com/803674/96929857-848ddd00-14c3-11eb-8fc8-11713c5d67f0.png">


**The proposal:**

```ts
const controls: Meta<TypographyProps, TypographyTitleProps> = [
    {
         title: 'Typography',
         component: Typography,
         argTypes: {
               ....
        }
    },
    {
         title: 'Title',
         component: Typography.Title,
         argTypes: {
               ....
        }
    }
];
```

<img width="1075" alt="Снимок экрана 2020-10-23 в 0 10 07" src="https://user-images.githubusercontent.com/803674/96930284-2281a780-14c4-11eb-8c0a-ff34e03dcbc2.png">

I believe it can be implemented with backward compatibility.
Repository: go
Issue: x/tools/gopls: improve diagnostics for empty go files
Labels: NeedsDecision,gopls,Tools

I propose not to generate diagnostics for the newly created, empty file. 

Assume this user workflow:

  - mkdir hello; cd hello
  - run `go mod init example.com/hello`
  - open the folder from an editor (e.g. vscode with gopls enabled by default)
  - create a new file `hello.go`, using the editor's feature

The first thing the user will notice is a diagnostic error message.

```
[Trace - 17:35:12.131 PM] Received notification 'textDocument/publishDiagnostics'.
Params: {"uri":"file:///Users/hakim/hello/hello.go","diagnostics":[{"range":{"start":{"line":0,"character":0},"end":{"line":0,"character":0}},"severity":1,"source":"syntax","message":"expected ';', found 'EOF'"}]}
```
It's not a critical, major issue, but it's not nice nor useful to present an error message before the user starts typing anything.
Repository: go
Issue: x/tools/gopls: trace of error response is missing
Labels: gopls,Tools

I triggered a codeAction that will fail and couldn't find the matching `"Received response ..."` from gopls trace. 
The 'Error' entry is from vscode client (in response of the error reply) and doesn't include the message id. This makes it difficult for trace viewer to process the trace.

```
[Trace - 18:36:44.832 PM] Sending request 'textDocument/codeAction - (8)'.
Params: {"textDocument":{"uri":"file:///Users/hakim/hello/b.go"},"range":{"start":{"line":0,"character":1},"end":{"line":0,"character":1}},"context":{"diagnostics":[]}}

...
[Error - 6:36:44 PM] Request textDocument/codeAction failed.
  Message: no packages returned: packages.Load error
  Code: 0 
```

The following is the corresponding trace recorded from the client side.

```
[Trace - 6:36:44 PM] Sending request 'textDocument/codeAction - (8)'.
Params: {
    "textDocument": {
        "uri": "file:///Users/hakim/hello/b.go"
    },
    "range": {
        "start": {
            "line": 0,
            "character": 1
        },
        "end": {
            "line": 0,
            "character": 1
        }
    },
    "context": {
        "diagnostics": []
    }
}
...
[Trace - 6:36:44 PM] Received response 'textDocument/codeAction - (8)' in 39ms. Request failed: no packages returned: packages.Load error (0).
```
Repository: go
Issue: runtime, cmd/compile: implicit allocations allowed in the runtime
Labels: NeedsInvestigation,FeatureRequest,compiler/runtime

We have a test in the compiler that ensures that we don't have any implicit allocations in the runtime. We want all allocations that the runtime does to be explicit (to avoid things like self-deadlock when allocating inside malloc).
That test doesn't catch all the allocations. In particular, it doesn't catch the allocation required to assign non-pointer types to interfaces. There may be others, I haven't checked.

I hacked a simple test into the compiler, and found a bunch of situations where this implicit allocation happens. An example:
```
func goPanicIndex(x int, y int) {
	panicCheck1(getcallerpc(), "index out of range")
	panic(boundsError{x: int64(x), signed: true, y: y, code: boundsIndex})
}
```
This code needs to allocate a `boundsError` and put its address in the data field of an interface.
All current missed interface-conversion allocations are of this form (an argument to `panic`).

I ran into this issue in a CL I'm working on where implicit allocations were happening in a bad place, and it took me a while to track it down. It would have been much easier for the compiler to give me an error.

Update #42076

@josharian
Repository: rust
Issue: Intra-doc links should be styled according to the kind of their target
Labels: T-rustdoc,C-feature-request,A-intra-doc-links,A-rustdoc-ui

Rustdoc generally has fairly consistent ways of styling documentation items. For example, in the default Light theme, structs are magenta, traits are lavender, functions and methods are gold, etc., and are always set in a sans-serif or monospace font. However, this convention does not seem to get applied to intra-documentation links.

Right now, if I write

    /// [Result]

the link will be blue and set in serifs; if I write

    /// [`Result`]

it'll be blue and set in monospace.

It would be more attractive and consistent for `[Result]` to be set in magenta sans-serif, and ``[`Result`]`` to be set in magenta monospace.
Repository: pytorch
Issue: Quantization - we need a better solution for tracking quantization backend settings in a model
Labels: oncall: quantization,triaged

## 🐛 Bug: Quantization - we need a better solution for tracking quantization backend settings in a model

Currently, there are various points of confusion:
1. a target backend (qnnpack / fbgemm) is usually chosen during model preparation, but it is not saved in the model
2. in a Python environment, a global flag `torch.backends.quantized.engine`, which must be manually set, controls whether qnnpack or fbgemm kernels should be used.
3. with `reduce_range` in particular, it's easy to do the wrong thing
4. there are no clear guidelines on what users should do if they need a model which works well on all backends

A potential high level set of improvements could be:
1. target backend and reduce_range settings used during model prepare and convert are saved on the model as metadata and persist throughout the `prepare` and `convert` steps
2. the global `torch.backends.quantized.engine` flag is deprecated.  Instead, a local per-model flag is used to control which kernels are used.
3. there is tooling which throws a clear warning when the user tries to do something which is not supported, such as running a model which was trained without reduce_range with the `fbgemm` backend

Creating this issue to finalize the end state we want, and track progress.

cc @ezyang @gchanan @zou3519 @bdhirsh @jbschlosser @anjali411 @jerryzh168 @jianyuh @dzhulgakov @raghuramank100 @jamesr66a @vkuzo
Repository: rust
Issue: Incoherent error when a method and the containing impl require the same trait with different lifetimes
Labels: A-lifetimes,A-trait-system,T-compiler,A-impl-trait

While trying to make the lifetimes work in a `-> impl Iterator` method, I ran into a weird error. Minimal test case:

```rust
trait Trait<'a> {}

struct Struct<'a, T>(&'a T);

impl<'a, T: Trait<'a>> Struct<'a, T> {
    pub fn method<'b>(&self)
    where
        T: Trait<'b>,
    {
    }
}
```

As far as I can tell, this should be valid code. However, it gives this bizarre error message:

```
error[E0283]: type annotations needed
 --> src/lib.rs:5:13
  |
1 | trait Trait<'a> {}
  | --------------- required by this bound in `Trait`
...
5 | impl<'a, T: Trait<'a>> Struct<'a, T> {
  |             ^^^^^^^^^ cannot infer type for type parameter `T`
  |
  = note: cannot satisfy `T: Trait<'a>`
```

This occurs on both stable and nightly.

## More details

The error still occurs if we replace one lifetime with `'static` - either
```rust
trait Trait<'a> {}

struct Struct<T>(T);

impl<'a, T: Trait<'a>> Struct<T> {
    pub fn method(&self)
    where
        T: Trait<'static>,
    {
    }
}
```
or
```rust
trait Trait<'a> {}

struct Struct<T>(T);

impl<T: Trait<'static>> Struct<T> {
    pub fn method<'b>(&self)
    where
        T: Trait<'b>,
    {
    }
}
```
But it doesn't occur if either bound is removed, or if the same lifetime is used in both bounds, or if the bounds differ by a type parameter rather than a lifetime parameter.

On stable, the error message is even less helpful if the trait has an associated type:
```rust
trait Trait<'a> {
    type A;
}

struct Struct<'a, T>(&'a T);

impl<'a, T: Trait<'a>> Struct<'a, T> {
    pub fn method<'b>(&self)
    where
        T: Trait<'b>,
    {
    }
}
```

```
error[E0282]: type annotations needed
 --> src/lib.rs:7:13
  |
7 | impl<'a, T: Trait<'a>> Struct<'a, T> {
  |             ^^^^^^^^^ cannot infer type
```

But on nightly, the error is the same either way.
Repository: pytorch
Issue: Memory leak when creating new tensors inside nn.DataParallel on multiple GPUs
Labels: oncall: distributed,triaged

## 🐛 Bug

I need to create tensors of different shapes in my module's forward method. When running on multiple GPUs using nn.DataParallel, the memory of the created new tensors is not properly freed, causing huge memory leakage.

## To Reproduce

Steps to reproduce the behavior:

1. Save the following code to a main.py file
```python
import torch
import torch.nn as nn

device = torch.device('cuda' if torch.cuda.is_available() else 'cpu')

class Test(nn.Module):
    def __init__(self):
        super().__init__()

    def forward(self, shape):
        test = torch.zeros(*shape)
        return None

if __name__ == '__main__':

    model = nn.DataParallel(Test()).to(device)
    model.train()

    for i in range(1000):
        for j in range(1000):
            shape = (8, 850 + i, 180 + j)
            model(shape)
```
2. Run `python main.py` on a Linux machine with two or more GPUs.
3. You will see unreasonable memory usage, and the memory usage seems to go higher as the program continues to run.

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->
<img width="949" alt="截屏2020-10-23 上午10 00 52" src="https://user-images.githubusercontent.com/26025487/96947799-ad8b8d80-1516-11eb-89ee-c3e8e5c8241b.png">


## Expected behavior

The memory usage of such a simple program should not be so high, and it should not keeps growing as the program continues. I've also tested with `env CUDA_VISIBLE_DEVICES=0 python main.py`. The memory usage seems normal with only one GPU.

<img width="955" alt="截屏2020-10-23 上午10 06 49" src="https://user-images.githubusercontent.com/26025487/96948122-79fd3300-1517-11eb-8c12-d1852aafab10.png">

<!-- A clear and concise description of what you expected to happen. -->

## Environment

PyTorch version: 1.6.0
Is debug build: False
CUDA used to build PyTorch: 10.2
ROCM used to build PyTorch: N/A

OS: Ubuntu 20.04.1 LTS (x86_64)
GCC version: (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
Clang version: Could not collect
CMake version: version 3.16.3

Python version: 3.8 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: Could not collect
GPU models and configuration:
GPU 0: GeForce RTX 2080 Ti
GPU 1: GeForce RTX 2080 Ti
GPU 2: GeForce RTX 2080 Ti
GPU 3: GeForce RTX 2080 Ti

Nvidia driver version: 450.80.02
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.19.2
[pip3] torch==1.6.0
[conda] numpy                     1.19.2                   pypi_0    pypi
[conda] torch                     1.6.0                    pypi_0    pypi

## Additional context

The same memory leakage problem doesn't occur when using nn.DistributedDataParallel.
I also tested with PyTorch 1.2.0, and the same problem exists.

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528 @osalpekar @jiayisuse @agolynski
Repository: flutter
Issue: Flutter Linux Desktop Japanese input switch
Labels: a: text input,platform-linux,a: desktop,P2,team-linux,triaged-linux

Flutter channel: master

OS: Fedora 33 running on wayland

Input method: ibus-kkc

On default Flutter application input switching doesn't work imminently - starts working when I increase counter and then switch input method.

It works on this sample app:
https://github.com/cbracken/jp_flutter

but when removing `gdk_set_allowed_backends("x11");` from `main.cc` (this line is not being created by default flutter script atm) bug occurs.

cc: @cbracken
Repository: create-react-app
Issue: Typecheck failing in one of node_modules
Labels: stale,needs triage

I installed one of our private package owned by some other team.

While development getting error after typecheck on that package as below

```
Failed to compile.

/path/to/repo/node_modules/<PACKAGE>/<SOME_FILES>.ts
TypeScript error in /path/to/repo/node_modules/<PACKAGE>/<SOME_FILES>.ts(378,17):
Type 'undefined' is not assignable to type 'SOME_DEFINITION'.  TS2322
```

How can I ask typescript to skip typechecking certain modules.

my tsconfig as below

```
{
  "compilerOptions": {
    "target": "es5",
    "lib": ["dom", "dom.iterable", "esnext"],
    "allowJs": true,
    "skipLibCheck": true,
    "resolveJsonModule": true,
    "esModuleInterop": true,
    "allowSyntheticDefaultImports": true,
    "strict": true,
    "forceConsistentCasingInFileNames": true,
    "module": "esnext",
    "moduleResolution": "node",
    "isolatedModules": true,
    "noEmit": true,
    "jsx": "react",
    "baseUrl": ".",
    "paths": {
      "@styled": ["src/styles/helpers/styled"]
    }
  },
  "include": ["src"]
}

```
Repository: svelte
Issue: Add localization files to your documentation
Labels: site,documentation

Hi, I'm middle Front-End developer from Ukraine, and know already 4 frameworks: Vue.js, React, AMP, Svelte. 

I want to be a volunteer and popularize your framework into Russian community, so I want to start translate your documentation, tutorials, etc... So how can I make this? 

Please add plugin such as "i18n" into your Github repo, add fully localizated English file. We will make RU file and some volunteers other languages files, that will have the same object structure as your original English file. Watching Github issues we will update and correct our translations. Also need to configure your site with doc. If in some languages we don't find required object with translation or our translation is not up to date, it will borrow actual from original translation (ENG).
Repository: godot
Issue: Instanced inherited scene not updated after collision layer change in base scene
Labels: bug,topic:editor

**Godot version:** 3.2.3 & current master (d5073c6)

**OS/device including version:** not graphic related


**Issue description:**
After changing the collision layer or collision mask of base scene, inherited scene's default collision layer / mask updates correctly. But instanced derived scene node's default collision layer / mask is not updated until I reopen the scene.

**Steps to reproduce:**
1. Setup the project (or use the MRP)
    1. Create a new scene with KinematicBody2D as root named `Base` (collision layer 1 is on by default)
    2. Create a new inherited scene from `Base`, name it `Derived` (collision layer 1 is on by default because of inheritance)
    3. Create a new 2D scene named `World`
    4. Instance `Base` and `Derived` in `World` (collision layer 1 is on by default)
2. Turn off collision layer 1 in `Base`
3. Inspect the collision layer and collision mask in other scenes
    * In `Derived` scene, collision layer 1 is off and not resetable
    * In `World` scene, the Derived node still has collision layer 1 on, and the collision layer is shown resetable.
        * After close & reopen the `World` scene, collision layer of Derived node is shown correctly (layer 1 off, not resetable)

**Minimal reproduction project:**[UpdateCollision.zip](https://github.com/godotengine/godot/files/5427900/UpdateCollision.zip)
Repository: PowerToys
Issue: Virtual Desktop layout is vert on top of horizontal to give more space
Labels: Idea-New PowerToy,Product-Virtual Desktop

## 📝Feature request for a better virtual desktops experience

---
The feature request is to increase the number of dimensions for adding virtual desktops from 1 to 2. Being able to have rows of virtual desktops would be a good productivity boost for some. Moving between these desktops could be done with **Ctrl+Win+Alt+[Directional Arrow]** or through the Task View (currently opened by Win+Tab).
![image](https://user-images.githubusercontent.com/17314821/96970655-4f5dab00-1514-11eb-9849-b06c2ddff947.png)

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.

I would love to hear thoughts and ideas on how to improve this further in the comments. Maybe it would be better to have a 2D grid of virtual desktops instead of several rows? Maybe another hotkey combination would be more suitable. 
Thank you
Repository: vscode
Issue: SCM Input - suggest widget is behind editor
Labels: bug,help wanted,scm,safari

* use safari
* trigger suggest in SCM view
* :bug: the widget is behind the editor

<img width="1472" alt="Screenshot 2020-10-23 at 10 54 01" src="https://user-images.githubusercontent.com/1794099/96978071-41ad2300-151e-11eb-814c-343695929be7.png">
Repository: pytorch
Issue: How to define a new data type in  native_functions.yaml?
Labels: module: internals,triaged

How to define a new data type in  native_functions.yaml? 
Such as there is exist a data type "int[]"，bu i want a data type "float[]"，what sould i do?
Looking forward to your advice, I will be very grateful！


cc @ezyang @bhosmer @smessmer @ljk53 @bdhirsh @ailzhang
Repository: terminal
Issue: Conhost high CPU usage with Windows Terminal closed
Labels: Needs-Repro,Product-Conpty,Area-Server,Issue-Bug,Priority-2

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

<!--
This bug tracker is monitored by Windows Terminal development team and other technical folks.

**Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**.
Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.

If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link.

Please use this form and describe your issue, concisely but precisely, with as much detail as possible.

-->

# Environment

Microsoft Windows [Version 10.0.19041.572]
Windows Terminal Version: 1.3.2651.0

# Steps to reproduce

Close Windows Terminal, wait 5 minutes, then check CPU usage.

<!-- A description of how to trigger this bug. -->

# Expected behavior

No CPU usage.

<!-- A description of what you're expecting, possibly containing screenshots or reference material. -->

# Actual behavior

![image](https://user-images.githubusercontent.com/6026260/96988279-6a381b80-1524-11eb-84dc-b002463d5dea.png)

<!-- What's actually happening? -->
Repository: TypeScript
Issue: Expose type level api 
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms
plugin, type, intrinsic, api

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->

## Suggestion

<!-- A summary of what you'd like to see added or changed -->

Now we have `intrinsic` type for template literal type. 

- Uppercase
- Lowercase
- Capitalize
- Uncapitalize

Could we release the type level api for customize the behavior of type? 

## Use Cases

For example 
```ts
type ToNumber<T extends string> = intrinsic

type Plus<T extends number, U extends number> = intrinsic
``` 

Related:
- #26382 
- #16607

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->

<!-- Show how this would be used and what the behavior would be -->

## Checklist

My suggestion meets these guidelines:

* [ ] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [ ] This wouldn't change the runtime behavior of existing JavaScript code
* [ ] This could be implemented without emitting different JS based on the types of the expressions
* [ ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [ ] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: material-ui
Issue: [Switch] Use role="switch"
Labels: accessibility,on hold,component: switch

- [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 💡

The switch component is announced like a checkbox, it should be announced like a switch.

## Examples 🌈

I have seen the role used in [react-switch](https://github.com/markusenglund/react-switch). After some digging, I could find this accessible resource that goes into more detail: https://scottaohara.github.io/a11y_styled_form_controls/src/checkbox--switch/. It seems that it's still too early to use the role, screenreaders support isn't high enough but we can revisit it in a year.

## Motivation 🔦

Improve the distinction between `Switch` and `Checkbox` for screen readers. It's important per https://next.material-ui.com/components/switches/#when-to-use.