sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [rfc] Add a "core only" build flag
Labels: module: build,triaged,enhancement,better-engineering

Usually when developing on something outside of the "math" side of PyTorch (i.e. c10, utils things, jit), I end up adding a ton a build flags to speed up the build as much as possible, e.g.:

```bash
export BUILD_TEST=0
export BUILD_CAFFE2_OPS=0
export USE_NUMPY=0
export USE_KINETO=0
export USE MKLDNN=0
export USE_NNPACK=0
export USE_TENSORPIPE=0
export USE_QNNPACK=0
export USE_DISTRIBUTED=0
export USE_MPI=0
export BUILD_CAFFE2=0
```

It'd be nice if we could roll up a recommended set of these (I mostly picked these out of `setup.py`) into a single `MINIMAL_BUILD` or something that includes as few external libraries as possible

cc @malfet @seemethere @walterddr
Repository: pytorch
Issue: torch.gradient  not throwing error when spacing to be equal to 0
Labels: module: autograd,low priority,triaged

From the mathematical definition of functions, for an input point of a function there can only be one output point.

However, when spacing is equal to zero in any dimension, then this corresponds to multiple different values for a given input point. It would be nice torch.gradient to point this issue when we call it with inputs of 0-spacing.

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer
Repository: pytorch
Issue: scripting LSTM module generates a script that has no .code, no .graph, and cannot be executed. 
Labels: oncall: jit,triaged

## ❓ Questions and Help

### Please note that this issue tracker is not a help form and this issue will be closed.
Ok, I need to script pytorch LSTM as when I do tracing it gets different answers with different inputs. But when I do:

script_module=torch.jit.script(torch.nn.modules.rnn.LSTM(768, 256, num_layers=2, batch_first=True, bidirectional=True))

the resulting script_module prints as: RecursiveScriptModule(original_name=LSTM), but unlike other recursivescriptmodules (for example, as shown here: https://pytorch.org/tutorials/beginner/Intro_to_TorchScript_tutorial.html, and successfully replicated by me) it has no .code or .graph attribute, and it cannot be executed.

So what am I doing wrong? It obviously "thinks" it has produced a correct script.  This seems like a pretty common use case. 

cc @gmagogsfm
Repository: pytorch
Issue: AVX512 and Vec512
Labels: feature,triaged,module: vectorization

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->
Introduce Vec512 into pytorch to support AVX512

## 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 -->
In this issue I would like to discuss introduction of 512b vectors into ATen backend. In the private PyTorch fork of the company I am working for I successfully introduced and tested them (not for x86 architecture though). Therefore if there is a general consensus that Vec512 is needed I can try to add them. 

## Pitch

<!-- A clear and concise description of what you want to happen. -->
Mirror implementation of `Vec256`. i.e. add `aten/src/ATen/cpu/vec512` folder with base class `vec512_base.h` which will implement scalar version of the ops. Then I would add classes which vectorize base class for the specific vector element type i.e. `vec512_double` etc. I would also add unifying header file `vec.h` with `VecType<>` aliasing either `Vec256` or `Vec512` depending on the cpu capability. Lastly I would replace all usages of `Vec256` with generic `VecType` and double check that all kernels (and tests) using it rely on the vector size and don't have it hardcoded.

Let me know what you guys think! I am open to any ideas :)

## Alternatives

<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->
As far as I know there is no way of using 512b vectors inside ATen backend right now.

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->
Repository: go
Issue: os: ReadAt should check bounds before re-slicing destination buffer
Labels: NeedsInvestigation

<!--
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`)?

<pre>
$ go version
go version go1.15.5 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

GOOS=linux
GOARCH=amd64

### What did you do?

Called the `(*os.File).ReadAt` method with a 2-byte destination slice.

### What did you expect to see?

Data in the destination slice and no error or panic.

### What did you see instead?

```
panic: runtime error: slice bounds out of range [4:2]
goroutine 63 [running]:
os.(*File).ReadAt(...)
    /usr/local/go/src/os/file.go:140 +0x3e5
```

The panic corresponds with the source line `b = b[m:]`.
Before re-slicing the destination buffer, a bounds-check is needed. Apparently, it's possible for lower layers to return more than the requested number of bytes within the initial read.
Repository: PowerToys
Issue: Ubisoft Connect - Padding on all 4 sides after dragging into a Fancy Zone
Labels: Product-FancyZones,Area-App Compat

### Microsoft PowerToys version

0.35.0

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

Drag the Ubisoft Connect application into any of the Fancy Zones. I've tried resizing zones and tried both of my monitors.

https://user-images.githubusercontent.com/33392093/114936478-1d415c00-9e5a-11eb-9bbe-23df75b9458c.mp4

Here's the video.

### ✔️ Expected Behavior

The padding on all 4 sides should not exist.

### ❌ Actual Behavior

There is a padding on all 4 sides of the zone I dragged it into, as shown in the video.

![fZCeHFQbbB](https://user-images.githubusercontent.com/33392093/114936589-3ea24800-9e5a-11eb-8477-d17bf61d0275.png)



### Other Software

Ubisoft Connect, the exe file just says 2.0.0
Repository: electron
Issue: Consumer facing APIs that use LookupIconFromFilepath should expose scale
Labels: enhancement :sparkles:

As of #28676 the `LookupIconFromFilepath` API in Chromium takes a `scale` third parameter, for usages of that API that we expose as part of the Electron API we should add that `scale` parameter as an optional option.
Repository: pytorch
Issue: [FX] Issues with names of functions in user packages
Labels: module: bootcamp,triaged,module: fx

## 🐛 Bug

FX has issues adding `call_function` nodes for functions whose "module path" and actual user-facing name differ. In particular, this common pattern is a problem:
```
pkg/
__init__.py
_thing.py
```
where `__init__.py` has something like:
```
from ._thing import func
```

## To Reproduce

Came from trying to insert a function call to [`torch_scatter.segment_csr`](https://github.com/rusty1s/pytorch_scatter):
```python
g = torch.fx.Graph()
x = g.placeholder("x")
out_node = g.call_function(segment_csr, args=(x, x))
g.output(out_node)
print(g.python_code(''))
# =>
import torch_scatter
def forward(self, x):
    segment_csr = torch_scatter.segment_csr.segment_csr(x, x);  x = None
    return segment_csr
```
`torch_scatter.segment_csr.segment_csr` is invalid, since to an importing package, `torch_scatter.segment_csr.segment_csr` is trying to access the attribute `segment_csr` on the function `segment_csr`.

Trying to use a string doesn't help:
```python
g = torch.fx.Graph()
x = g.placeholder("x")
out_node = g.call_function("torch_scatter.segment_csr", args=(x, x))
g.output(out_node)
print(g.python_code(''))
---------------------------------------------------------------------------
AssertionError                            Traceback (most recent call last)
torch/fx/graph.py in emit_node(node)
    666                 return
    667             elif node.op == 'call_function':
--> 668                 assert callable(node.target)
    669                 # pretty print operators
    670                 if node.target.__module__ == '_operator' and node.target.__name__ in magic_methods:
```

## Expected behavior

FX should either figure out a way to generate a call to functions like this that is valid, or should allow function names to be given as strings so that the user can work around this issue.

## Environment

 - PyTorch Version (e.g., 1.0): 1.8.0
 - OS (e.g., Linux): Linux
 - How you installed PyTorch (`conda`, `pip`, source): conda
 - Build command you used (if compiling from source):
 - Python version: 3.8.5
 - CUDA/cuDNN version: n/a
 - GPU models and configuration: n/a
 - Any other relevant information: n/a

## Additional context

One workaround for this — specifically for `torch_scatter` — is to call the `torch.ops` versions of the functions:
```python
out = graph_out.call_function(
        torch.ops.torch_scatter.segment_sum_csr,
        ...
)
```


cc @ezyang @SherlockNoMad
Repository: TypeScript
Issue: Type is not checked when using object spread and computed property of type `number`
Labels: Bug

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

spread computed property number reduce

### 🕗 Version & Regression Information

<!-- When did you start seeing this bug occur?

"Bugs" that have existed in TS for a long time are very likely to be FAQs; refer to
  https://github.com/Microsoft/TypeScript/wiki/FAQ#common-bugs-that-arent-bugs

If possible, please try testing the nightly version of TS to see if it's already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly

Note: The TypeScript Playground can be used to try older versions of TypeScript.

Please keep and fill in the line that best applies:
-->
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about _________

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?#code/CYUwxgNghgTiAEYD2A7AzgF3gS2ALnhQFcBbAIxBgG4AoGjATwAcEBBMMeAXngG94A2gGsQDAphjYUAcwC6BYuUrwAvrVCRYCZOixQOBdmFo0A9KfgBRAB4swGEMHiUYSGABp4ZIlmlIsKKggAHTwgDLkNDqY8PpgAEyGHNx8NPBp8MGZse6p6QK48vAA5FIAblAQuEU5akA)

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
declare const id: number;

type Acc = { [key: string]: number };
declare const acc: Acc;

// Expected error, but got none. ❌
const acc2: Acc = {
    ...acc,
    [id]: 'invalid',
};
```

If we change the type of the computed property `id` from `number` to `string`, it works as expected (we get an error).

```tsx
declare const id: string;

type Acc = { [key: string]: number };
declare const acc: Acc;

// Expected error, and got none. ✅
const acc2: Acc = {
    ...acc,
    [id]: 'invalid',
};
```

Alternatively, if we remove the spread of `acc` it works as expected:

```tsx
declare const id: number;

type Acc = { [key: string]: number };
// declare const acc: Acc;

// Expected error, and got none. ✅
const acc2: Acc = {
    [id]: 'invalid',
};
```

My workaround for now is to convert the type before it's used as a computed property:

```tsx
declare const id: number;

type Acc = { [key: string]: number };
declare const acc: Acc;

// Expected error, and got none. ✅
const acc2: Acc = {
    ...acc,
    [id.toString()]: 'invalid',
};
```

### 🙁 Actual behavior

See code comments above.

### 🙂 Expected behavior

See code comments above.
Repository: flutter
Issue: Test for l10n changes between running l10n Google script & branch cut
Labels: a: tests,team,framework,a: internationalization,P2,team-framework,triaged-framework

it would be nice to have a test that we run on release branches that ensures a change didn't land between running the scripts pulling l10n strings in from the translation console and the actual release branch cut.

cc @christopherfujino (who suggested it after I missed the l10n script execution this release) and @HansMuller for someone on his team to think about.
Repository: godot
Issue: [3.x] Autocomplete doesn't work for function names in strings
Labels: enhancement,topic:gdscript,topic:editor

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
<!-- Specify commit hash if using non-official build. -->
3.2.3

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Windows 10

**Issue description:**
<!-- What happened, and what was expected. -->

https://user-images.githubusercontent.com/50304111/114949231-c9108a80-9e0d-11eb-92a8-6be0b3a1e2f6.mp4



**Steps to reproduce:**
See above

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
n/a
Repository: electron
Issue: [Bug]: Renderer spellcheck API does not work on Windows
Labels: platform/windows,bug :beetle:,has-repro-gist,11-x-y,12-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Electron Version

12.0.4

### What operating system are you using?

Windows

### Operating System Version

Windows 10 1909

### What arch are you using?

x64

### Last Known Working Electron version

None

### Expected Behavior

Expecting `require('electron').webFrame.isWordMisspelled('testt')` to return `true`.

### Actual Behavior

`require('electron').webFrame.isWordMisspelled('testt')` returns `false`.

### Testcase Gist URL

https://gist.github.com/lishid/53782e6e43f4bc431ac1fed3bff33c85
Repository: storybook
Issue: Arguments are not escaping special characters.
Labels: question / support,has workaround,addon: controls

**Describe the bug**
Storybook is not supporting special characters

**To Reproduce**
Steps to reproduce the behavior:

1. Go to Storybook,
2. Click on the example button component
3. Put "To be or not to be, that's the question" on the label field
4. Click on the preview mode
5. See error

**Expected behavior**
The preview mode should render "To be or not to be, that's the question"

**Screenshots**
![image](https://user-images.githubusercontent.com/25183741/114956709-ccb80780-9e35-11eb-9c32-5e694d6597ab.png)
![image](https://user-images.githubusercontent.com/25183741/114956795-f96c1f00-9e35-11eb-88b6-9980678fc16e.png)

**System**
Environment Info:

  System:
    OS: Windows 10 10.0.19041
    CPU: (8) x64 Intel(R) Core(TM) i7-7700 CPU @ 3.60GHz
  Binaries:
    Node: 12.18.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.5 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Chrome: 89.0.4389.114
    Edge: Spartan (44.19041.423.0), Chromium (89.0.774.76)
  npmPackages:
    @storybook/addon-actions: ^6.2.8 => 6.2.8
    @storybook/addon-essentials: ^6.2.8 => 6.2.8
    @storybook/addon-links: ^6.2.8 => 6.2.8
    @storybook/html: ^6.2.8 => 6.2.8


**Additional context**
Add any other context about the problem here.
Repository: opencv
Issue: About LU Decomp
Labels: category: core

https://github.com/opencv/opencv/blob/cfb77091ca66333f43b328328544b6aa45233415/modules/core/src/matrix_decomp.cpp#L44-L54
if alpha close to 0, just continue the loop will be more efficient.
Repository: pytorch
Issue: Error message regarding Padding of Conv2d needs improving
Labels: module: convolution,triaged,module: padding

## 🐛 Bug
This is a small yet interesting bug. The error message with respect to the padding of `torch.nn.Conv2d` needs improving. Different large padding values produce irrelevant error messages, which is unexpected.

## To Reproduce
I feed specific "magic" values as padding into `torch.nn.Conv2d`. I found them with binary search, just out of curiosity:)

`6442450944` is the smallest integer when `negative padding` is reported, while `9223372036854775808` is the smallest integer when `argument 'padding' must be tuple of ints, but found element of type int at pos 1` is reported.
Firstly, `6442450944` itself is not negative. Furthermore, the error message for `9223372036854775808` does not make sense, because `padding` shouldn't be `tuple of ints` actually, and should be `int` anyway.

 ```
import torch
def validate():
    paddings = [6442450944 - 1, 6442450944, 9223372036854775808-1, 9223372036854775808]
    image = torch.rand(1, 3, 16, 16).cuda()
    for pad in paddings:
        try:
            net = torch.nn.Conv2d(3, 4, kernel_size=3, padding=pad).cuda()
            out = net(image)
            print(pad, "passed")
        except Exception as e:
            print(str(e))

validate()
```
The output is
```
6442450943 passed
negative padding is not supported
negative padding is not supported
conv2d(): argument 'padding' must be tuple of ints, but found element of type int at pos 1
```

## Expected behavior
It would be appreciated if the correct error message are produced for large padding values.

## Environment
PyTorch Version (e.g., 1.0): 1.8
OS (e.g., Linux): Linux
How you installed PyTorch (conda, pip, source): pip
Python version: 3.6.6
CUDA/cuDNN version: cuDNN 11.1
GPU models and configuration: A100

## Additional context

<!-- Add any other context about the problem here. -->
Repository: ant-design
Issue: menu選單在進入頁面時會出現閃爍
Labels: Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[https://drive.google.com/file/d/1KQp5Jf2hnKJ6rQzSlcNDW3_ZRHNZn72Y/view?usp=sharing](https://drive.google.com/file/d/1KQp5Jf2hnKJ6rQzSlcNDW3_ZRHNZn72Y/view?usp=sharing)

### Steps to reproduce
重新整理

### What is expected?
希望不會有一開始的瞬間閃動

### What is actually happening?
重新整理後菜單會散開然後才合併

| Environment | Info |
|---|---|
| antd | undefined |
| React | 17.0.1 |
| System | window10 |
| Browser | chrome 版本 89.0.4389.114 |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: Half precision support for torch.sparse.mm
Labels: feature,triaged,module: half

## 🚀 Feature
Add half-precision support for native `torch.sparse.mm`

## Motivation
Mixed precision training is widely adopted today, it would be better to add half precision support for native sparse functions like `torch.sparse.mm`
<!-- 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 -->

## Pitch

<!-- A clear and concise description of what you want to happen. -->
```python
import torch

if __name__ == '__main__':
    a = torch.randn(5, 8) > 0
    a = a * 1.0
    a = a.to_sparse().half()

    b = torch.randn(8, 5) > 0
    b = b * 1.0
    b = b.to_sparse().half()

    out = torch.sparse.mm(a, b)
    # The above line will trigger a RuntimeError: "sparse_matmul" not implemented for 'Half'
    # Need support for half precision
    print(out)
```
Repository: ant-design
Issue: Select: define the width of  select item option
Labels: help wanted,💡 Feature Request,Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### What problem does this feature solve?
I has more the 50 items in a multi-select.  I think a wide and multi-column or grid drop down panel is better than current single column drop down list. 

### What does the proposed API look like?
```TypeScript
 // the width of select item option (default is as wide as the drop down list )
selectItemWidth: number | string; 
```


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: optim.Adadelta: local variable 'lr' referenced before assignment
Labels: module: optimizer,triaged

## 🐛 Bug
Previously I used pytorch1.7.0 and the code works well. After I upgrade my pytorch to 1.8.1, I got this bug for my optimizer with the same code.

## To Reproduce
```
optimizer1 = optim.Adadelta(params, lr=learning_rate)
optimizer1.zero_grad()
#other code to compute loss
optimizer1.step()  
optimizer1.zero_grad()
```

The error shows:
```
Traceback (most recent call last):
  File "run_debug.py", line 179, in <module>
    network, stop_flag, epoch = network_training.train_network(training_data, mean_train,std_train, mean_lps, std_lps, writer, epoch)
  File "/data07/mayi/code/asvtorch/asvtorch/src/networks/network_training_single.py", line 154, in train_network
    optimizer1.step()
  File "/data07/mayi/anaconda3/envs/asvtorch2/lib/python3.7/site-packages/torch/optim/optimizer.py", line 89, in wrapper
    return func(*args, **kwargs)
  File "/data07/mayi/anaconda3/envs/asvtorch2/lib/python3.7/site-packages/torch/autograd/grad_mode.py", line 27, in decorate_context
    return func(*args, **kwargs)
  File "/data07/mayi/anaconda3/envs/asvtorch2/lib/python3.7/site-packages/torch/optim/adadelta.py", line 85, in step
    lr,
UnboundLocalError: local variable 'lr' referenced before assignment
```

 - PyTorch Version (e.g., 1.0): 1.8.1
 - OS (e.g., Linux): Ubuntu
 - How you installed PyTorch (`conda`, `pip`, source): conda
 - Build command you used (if compiling from source):
 - Python version:3.7
 - CUDA/cuDNN version:10.2
 - GPU models and configuration: 2080
 - Any other relevant information:


cc @vincentqb
Repository: vscode
Issue: Notebook cell focus feedback should disappear when clicking the empty view content or somewhere else
Labels: ux,under-discussion,notebook-layout

I finally figured out the details of something that annoys me all the time our notebooks. Notice in the GIF how that border of the focused cell doesn't disappear when clicking elsewhere... I can only make it disappear when pressing <kbd>Escape</kbd>.

![recording (6)](https://user-images.githubusercontent.com/22350/114997392-a35aa400-9e54-11eb-8b13-e3d7f42ec9fe.gif)