sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Material Design Color System Guidance Bug
Labels: framework,f: material design,a: quality,P2,team-design,triaged-design

While I was updating my App with the latest buttons and color schemes I found an inconsistency in the Material Design Specs.

Looking at the `ColorScheme.light` constructor, it creates a `ColorScheme` with 100% black text. It follows the recommendations [here](https://material.io/design/color/the-color-system.html#color-theme-creation).

But, the recommendations [here](https://material.io/design/color/text-legibility.html#text-backgrounds) are that black text should have an opacity of 87%, which makes both specs contradict one another.

This was already reported to the Material Design Team in private messages and they confirmed it's a bug on the Color System Guidance.

I am opening this issue here so we can track the changes into the `ColorScheme` class to reflect the Color System Guidance fixes.

cc @willlarche
Repository: TypeScript
Issue: JS IntelliSense only picks up JSDoc @inherits rule in class definition but not on children or instances
Labels: Domain: JSDoc,Needs Investigation

*TS Template added by @mjbvz*

**TypeScript Version**: 4.1.0-dev.20201026

**Search Terms**
- jsdoc

---

<!-- ⚠️⚠️ 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: 18.04

Steps to Reproduce:

I apologize if this is not the correct place for this issue, I tried hard finding the repository that is responsible for js intellisense.

1. Create a new js file
2. Copy below code into the file

```js
function Mixin1 (base) {
  return class extends base {
    foo() {}
  }
}

function Mixin2 (base) {
  return class extends base {
    bar() {}
  }
}

class IntermediateDummyClass extends Mixin1(Object) {}

/**
 * @implements {IntermediateDummyClass}
 */
class Composite extends Mixin2(IntermediateDummyClass) {
  
}

let c = new Composite;

c.
```
3. Observe autocomplete suggestions - within `Composite` class both `foo` and `bar` are suggested

![image](https://user-images.githubusercontent.com/14002806/97178100-b5119780-179f-11eb-991e-ff6bf775a38c.png)

However when instantiated or extended only `bar` is picked up.   


![image](https://user-images.githubusercontent.com/14002806/97178126-bd69d280-179f-11eb-895d-31a13731f2bc.png)

![image](https://user-images.githubusercontent.com/14002806/97178925-dde65c80-17a0-11eb-9846-48fe60d57da0.png)



<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes
Repository: pytorch
Issue: Support deleting a parameter/buffer by name
Labels: feature,module: nn,triaged,module: ux

This is need for some reparametrization code.

Weight norm [code](https://github.com/pytorch/pytorch/blob/6dc763df3098485f158eeed2b9621cffaa229669/torch/nn/utils/weight_norm.py#L44) uses `del module._parameters[name]` for that.

Also requested on forum: https://discuss.pytorch.org/t/how-to-unregister-a-parameter-from-a-module/36424 and many other: https://discuss.pytorch.org/t/exclude-parameters-from-model/77238/6 https://discuss.pytorch.org/t/how-to-exclude-parameters-from-model/6151 https://discuss.pytorch.org/t/delete-unregister-a-parameter-in-a-module/66302. Maybe it is a duplicate issue as well? I may have missed it

I used `module.register_parameter('weight', None)` for that goal (to overwrite an existing parameter with a None one)

Having an explicit/documented method may be useful

cc @albanD @mruberry
Repository: flutter
Issue: `flutter drive` does not output `print`, swallows exception info when test fails in profile/release modes
Labels: a: tests,a: debugging,platform-web,a: error message,P2,team-web,triaged-web

## Steps to Reproduce

1. In the Flutter repo `cd dev/integration_tests/flutter_gallery`
2. Edit `dev/integration_tests/flutter_gallery/test_driver/run_demos.dart` and throw an exception in the middle of the test, e.g. right after one of `pumpAndSettle()`. Also add some `print` statements prior to throwing the exception.
3. Run this command: `flutter drive --driver=test_driver/transitions_perf_e2e_test.dart --target=test_driver/transitions_perf_e2e.dart --browser-name=chrome -d web-server --profile`

**Expected results:**

The test prints the output from the `print` statements, then fails outputting the exception message and stack trace.

**Actual results:**

All you see in the output is this:

```
$ flutter drive --driver=test_driver/transitions_perf_e2e_test.dart --target=test_driver/transitions_perf_e2e.dart --browser-name=chrome -d web-server --profile
Running "flutter pub get" in flutter_gallery...                    450ms
Launching test_driver/transitions_perf_e2e.dart on Web Server in profile mode...
Compiling test_driver/transitions_perf_e2e.dart for the Web...        30.5s
test_driver/transitions_perf_e2e.dart is being served at http://localhost:46067
The web-server device requires the Dart Debug Chrome extension for debugging. Consider using the Chrome or Edge devices for an improved development
workflow.
Application finished.
Failure Details:
Failure in method: all demos

end of failure 1
```

This is reproducible in e7b66ac7ad45728d19e67034255fb9c303430c0e
Repository: kubernetes
Issue: Move disallow volume expansion test ouside of storage driver testsuite
Labels: kind/cleanup,sig/storage,help wanted,needs-triage

<!-- Please only use this template for submitting enhancement requests -->

**What would you like to be added**:
Move [this testcase](https://github.com/kubernetes/kubernetes/blob/87cc9bca0fcbbdf1b8232c9c71e50023d62667c3/test/e2e/storage/testsuites/volume_expand.go#L153) outside of driver testsuite, perhaps using csi mock driver.

**Why is this needed**:
See comments [here](https://github.com/kubernetes/kubernetes/pull/95780#discussion_r512365244)
Repository: create-react-app
Issue: Make ESLint configuration flexible
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

Setting up ESLint is always a pain point in CRA. For most of the time, everything seems to work fine, right until I run a separate lint check command like `eslint 'src/**/*.js'`, then I realize that the eslint result return by the CRA is incomplete/broken, and the root cause is mainly because of the CRA is fixing version for certain eslint related package, for instance, `@typescript-eslint/parser`. And so far, my workaround is to use tools like [craco](https://github.com/gsoft-inc/craco) + [craco-eslint-webpack-plugin](https://www.npmjs.com/package/craco-eslint-webpack-plugin) to replace the entire eslint module in CRA, it's hacky but works great for me. And as we all know things break by using tools like this. 

### Describe the solution you'd like

Make the eslint configuration even flexible, don't include default eslint setup/packages by default. And yes I know, things will break, but it's just problematic the current eslint setup, let us the developers handle the problem.

### Describe alternatives you've considered

At least don't fix the eslint package like `@typescript-eslint/parser`, etc.

### Additional context

None
Repository: pytorch
Issue: CUDA out of memory when using torch.load
Labels: module: cuda,triaged

## 🐛 Bug

<!-- A clear and concise description of what the bug is. -->
Yesterday I use the same code, and the program is well, but today I get this error, RuntimeError: CUDA error: out of memory

## To Reproduce

Steps to reproduce the behavior:

1. I instantiate my model like this:
`model = NSP(my_config)`
NSP is a Bert Next Sentence Prediction model using huggingface's transformers, and the nvidia-smi got this:
![image](https://user-images.githubusercontent.com/31238754/97250172-5ea86580-1840-11eb-9e67-58411d5b8094.png)
I used the NO.1 GPU
1. Loading my parameters like this(it size is about 400M):
`state_dict = torch.load(my_config.continue_training_path)`
then the error coming:
![image](https://user-images.githubusercontent.com/31238754/97252018-02474500-1844-11eb-9bdb-95cf604ffeb4.png)



<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

<!-- A clear and concise description of what you expected to happen. -->

## Environment

Please copy and paste the output from our
[environment collection script](https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py)
(or fill out the checklist below manually).

You can get the script and run it with:
```
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py
```

 - PyTorch Version (e.g., 1.0): 1.5.1
 - OS (e.g., Linux): Linux version 3.10.0-514.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.5 20150623 (Red Hat 4.8.5-11) (GCC) ) #1 SMP Tue Nov 22 16:42:41 UTC 2016
 - How you installed PyTorch (`conda`, `pip`, source): source
 - Build command you used (if compiling from source): make
 - Python version: 3.8.3 64bit
 - CUDA/cuDNN version: CUDA Version: 10.2
 - GPU models and configuration: RTX-2080
 - Any other relevant information:

## Additional context

<!-- Add any other context about the problem here. -->


cc @ngimel
Repository: pytorch
Issue: How to use clang as a cuda compiler instead of nvcc?
Labels: module: build,triaged,enhancement

I want to ask if we can use clang as a cuda compiler instead of nvcc, such as 'TF_CUDA_CLANG', 'CLANG_CUDA_COMPILER_PATH' options similar to tensorflow/third_party/gpus/cuda_configure.bzl?


cc @malfet @seemethere @walterddr
Repository: svelte
Issue: Unclear what a custom easing function should return
Labels: stale-bot,documentation

This is about the docs.

While I was trying to implement a particular transition in my site I've tried to implement a custom easing function. I've had difficulties because I could not figure out what my custom easing function was supposed to return based on the `t` parameter. And also the meaning of the `t` parameter is not totally clear. Although `t` is probably a fraction of the point of time we're in within the transition as a value between 0 and 1. 

Questions that come to my mind about the return value:

- What will Svelte do with that value? 
- Does it need to be a value between 0 and 1?
- Can it return a value below 0? What will happen then?
- Can it return a value above 1? What will happen then?
- Does the value returned depend in any way on the value returned in the previous call? Maybe just the difference between the previous and the current value matters?

When looking at the API docs (e.g. in https://svelte.dev/docs#svelte_easing) I couldn't find anything.
Repository: pytorch
Issue: Authentication for RPC
Labels: oncall: distributed,triaged,module: rpc,module: tensorpipe

## 🚀 Feature
Consider a multi machine setup with an open network infrastructure. At the moment pyTorch RPC provides no way of securing the masters endpoint through authentication methods. This leads to following two vulnerabilities:
- Attackers might query gradients/ weights from the master node to gain access to a model without owning the data.
- Anyone could disquise as a worker and send random gradients/ weights to the master to obscure the final model.

## Motivation
As a Software Engineer I want to provide solutions that ensure safety and security.

## Pitch
Make multi machine RPC training secure!

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @rohan-varma @xush6528 @jjlilley @osalpekar @jiayisuse @lw @beauby @agolynski
Repository: TypeScript
Issue: Not all leading tab characters in diagnostic messages are replaced with spaces
Labels: Bug,Help Wanted

The error diagnostics that are used by default do not replace ALL leading tab characters with a single space.

As one would expect from seeing this code line in souce code:
https://github.com/microsoft/TypeScript/blob/85ef91e2233fa384e980005c109fadc04376ce3e/src/compiler/program.ts#L410

This line only replaces the first leading tab character. Which causes way too much leading whitespace printed in the logs when errors occur during tsc build.

**TypeScript Version:**  4.0.3

**Search Terms:**
tabs diagnostics, reporter, formatCodeSpan, formatDiagnosticsWithColorAndContext, leading tabs,

**Expected behavior:**
Source code has four leading tabs for indentation.

`[line number] [gutter seperator] [space] [space] [space] [space] [line content]`

![image](https://user-images.githubusercontent.com/4201102/97279104-d5426480-183a-11eb-87c9-5e33a9a26c21.png)

**Actual behavior:**
`[line number] [gutter seperator] [space] [tab] [tab] [tab] [line content]`

![image](https://user-images.githubusercontent.com/4201102/97279149-e68b7100-183a-11eb-8e7f-1d0558b21f0e.png)

**PR**
I can submit a PR for this that would change this line:
`lineContent = lineContent.replace("\t", " ");    // convert tabs to single spaces`
to:
`lineContent = lineContent.replace(/\t/gy, " "); // convert all leading tabs to single spaces`
Repository: vscode
Issue: Support theme icon colour in all API places
Labels: api,debt

re https://github.com/microsoft/vscode/issues/109453

Today, `ThemeIcon#themeColor` is only honoured in custom trees. We should support it in all places where theme icons are supported. Those are

* [ ] `QuickInputButton` @chrmarti 
* [x] `WorkspaceEditEntryMetadata` @jrieken 

/cc @alexr00 for help on how these to implement this
Repository: flutter
Issue: Windows shader compilation errors 
Labels: engine,dependency: skia,platform-windows,a: desktop,P2,team-windows,triaged-windows

windows applications are failing shader compilation on some Win 7 devices with AMD display driver .

The full error log is here:  [full errors](https://gist.github.com/zhileichen/f0c4fe4b3c8f9385f1a8697a139d3670)
```
Shader compilation error:
------------------------
   1    // Vertex SKSL
   2    uniform float4 sk_RTAdjust;in float2 position;in half4 color;out half4 vcolor_Stage0;void main() {// Primitive Processor QuadPerEdgeAAGeometryProcessor
   3    vcolor_Stage0 = color;sk_Position = float4(position.x , position.y, 0, 1);}
   4    // Fragment SKSL
   5    in half4 vcolor_Stage0;out half4 sk_FragColor;
   6    void main() {half4 outputColor_Stage0;half4 outputCoverage_Stage0;{ // Stage 0, QuadPerEdgeAAGeometryProcessor
   7    outputColor_Stage0 = vcolor_Stage0;outputCoverage_Stage0 = half4(1);}{ // Xfer Processor: Porter Duff
   8    sk_FragColor = outputColor_Stage0 * outputCoverage_Stage0;}}
   9    // Vertex GLSL
  10    #version 300 es
  11
  12    precision mediump float;
  13    precision mediump sampler2D;
  14    uniform highp vec4 sk_RTAdjust;
  15    in highp vec2 position;
  16    in mediump vec4 color;
  17    out mediump vec4 vcolor_Stage0;
  18    void main() {
  19        vcolor_Stage0 = color;
  20        gl_Position = vec4(position.x, position.y, 0.0, 1.0);
  21        gl_Position = vec4(gl_Position.xy * sk_RTAdjust.xz + gl_Position.ww * sk_RTAdjust.yw, 0.0, gl_Position.w);
  22    }
  23
  24    // Fragment GLSL
  25    #version 300 es
  26
  27    precision mediump float;
  28    precision mediump sampler2D;
  29    out mediump vec4 sk_FragColor;
  30    in mediump vec4 vcolor_Stage0;
  31    void main() {
  32        mediump vec4 outputColor_Stage0;
  33        {
  34            outputColor_Stage0 = vcolor_Stage0;
  35        }
  36        {
  37            sk_FragColor = outputColor_Stage0;
  38        }
  39    }
  40
  41
Errors:

```

My flutter version:
```
[√] Flutter (Channel master, 1.24.0-2.0.pre.86, on Microsoft Windows [Version 10.0.18362.1139], locale zh-CN)
    • Flutter version 1.24.0-2.0.pre.86 at C:\Users\ee\Workspace\flutter
    • Framework revision dde20448f7 (7 days ago), 2020-10-20 00:59:56 -0400
    • Engine revision ea2aea1c61
    • Dart version 2.11.0 (build 2.11.0-234.0.dev)
    • Pub download mirror https://pub.flutter-io.cn        
    • Flutter download mirror https://storage.flutter-io.cn
```

The windows devices which failed to compile Shader 
[DxDiag.txt](https://github.com/flutter/flutter/files/5444656/DxDiag.txt)
[DxDiag2.txt](https://github.com/flutter/flutter/files/5444668/DxDiag22.txt)

Was this fiexed in https://github.com/flutter/flutter/pull/64809 ? @dnfield
Repository: pytorch
Issue: SummaryWriter deletes data automatically when there are too many
Labels: module: tensorboard,oncall: visualization

## ❓ Questions and Help

I use SummaryWriter torch.utils.tensorboard to record data every epoch (1k global timesteps). At first SummaryWriter worked out fine, but I found out that after around 300 epochs(event file about 1M), the Summary starts to lose data. (Like when you see tensorboard visualizer at around 30 epochs, all data are kept and it goes like 1,2,3,4,5,6,7...  and at around 300 epochs and you look at tensorboard again, the data becomes 1,5,9,12,13,15...)

I wonder if this is normal? and any idea what might have caused this?

I ues Python 3.8.3,  tensorboard '2.3.0',  torch '1.4.0',
I use `from torch.utils.tensorboard import SummaryWriter` in my code,
and use `tensorboard --logdir=log` in server's bash.
I use ssh tunnel tosee results on my pc.
Repository: vscode
Issue: Suggest widget: do not grow horizontally to the left if I am dragging to the right
Labels: suggest,under-discussion

Testing #109394

1. Have a vscode window not take the full screen 
2. Have the suggest widget wide almost the way to the right
3. Take the right sash and drag it out of the VS Code window
4. Suggest widget grows to the left 🐛 

![recording (3)](https://user-images.githubusercontent.com/1926584/97297856-df705d00-1852-11eb-9e64-988e3b0496e4.gif)
Repository: vscode
Issue: Suggest widget: Details view doesn't resize width to fit content
Labels: ux,suggest,under-discussion

Testing #109394

The details view correctly resizes the height to fit more lines, but the width stays the same no matter the content.
![NoSizeChanges](https://user-images.githubusercontent.com/42123497/97301877-94594880-1858-11eb-9ef4-3ff2a49ad530.gif)
I think it should resize up to the edge of the editor and add a scrollbar if needed.
Alternatively the width I set should persist across sessions so I can drag it to the edge once and never think about it again.
Repository: vscode
Issue: Details pane flips to the left instead of the top
Labels: suggest,under-discussion

Testing #109394

See screen cast. I would have expected the details pane positioned to the top than to the left since it was position to the bottom before.

![cast](https://user-images.githubusercontent.com/1931590/97310434-852bc800-1863-11eb-8676-c19636056f45.gif)
Repository: pytorch
Issue: Jacobians computed by autograd.functional.jacobian with compute_graph sometimes set requires_grad True
Labels: module: autograd,triaged

## 🐛 Bug

The Jacobians computed by torch.autograd.functional.jacobian sometimes have require_grad=True when compute_graph=True is given, but not always. It depends on the concrete function that is input to the Jacobian computation. 

## To Reproduce

Steps to reproduce the behavior:

`import torch

def f1(x):
    return x

def f2(x):
    return x*x

x0 = torch.tensor([4., 2., 2.])
print("x0.requries_grad", x0.requires_grad)
print("--- Returning just x with create graph ---")

J1  = torch.autograd.functional.jacobian(f1, (x0), create_graph=True)
print("J1.requires_grad", J1.requires_grad)

print("--- Returning x*x with create graph ---")
x0 = torch.tensor([4., 2., 2.])
J2  = torch.autograd.functional.jacobian(f2, (x0), create_graph=True)
print("J2.requires_grad", J2.requires_grad)

print("--- Returning x*x without create graph ---")
x0 = torch.tensor([4., 2., 2.])
J3  = torch.autograd.functional.jacobian(f2, (x0))
print("J3.requires_grad", J3.requires_grad)`

The output here is

> x0.requries_grad False
> --- Returning just x with create graph ---
> J1.requires_grad False
> --- Returning x*x with create graph ---
> J2.requires_grad True
> --- Returning x*x without create graph ---
> J3.requires_grad False

## Expected behavior

In the example above, J2.requires_grad should be False.

## Environment

PyTorch version: 1.8.0.dev20201027
Is debug build: True
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: False
CUDA runtime version: No CUDA
GPU models and configuration: No CUDA
Nvidia driver version: No CUDA
cuDNN version: No CUDA
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.17.4
[pip3] torch==1.8.0.dev20201027
[pip3] torchvision==0.8.0.dev20201026
[conda] Could not collect

## Additional context

-


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved
Repository: go
Issue: cmd/go: 'go vet cmd' fails with "use of internal package" when run in GOROOT/src/cmd
Labels: NeedsInvestigation,GoCommand,Analysis

```
~/go-review/src/cmd$ go version
go version devel +320cc79002 Tue Oct 27 12:36:54 2020 +0000 linux/amd64

~/go-review/src/cmd$ go vet cmd
package cmd/vendor/github.com/google/pprof/driver
        vendor/github.com/google/pprof/driver/driver.go:24:2: use of internal package github.com/google/pprof/internal/driver not allowed
package cmd/vendor/github.com/google/pprof/driver
        vendor/github.com/google/pprof/driver/driver.go:25:2: use of internal package github.com/google/pprof/internal/plugin not allowed
…

~/go-review/src/cmd$ cd ..

~/go-review/src$ go vet cmd

~/go-review/src$
```

I'm not actually sure whether this bug is in `cmd/go` or in `cmd/vet`.

There was a similar issue (#41358) in `cmd/api` which we resolved by omitting the vendored packages. However, in this case I think we really should be running `vet` on these packages — we just need to get `go vet` to interpret the imports from within those packages correctly.

This comment in `cmd/go` is related:
https://github.com/golang/go/blob/ece7a33386a4fbd2ff9859902f780ed82120b985/src/cmd/go/internal/modload/load.go#L1151-L1155

CC @matloob @jayconrod