sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: NativeScript's `class_name` property is shadowed by the keyword
Labels: bug,topic:gdextension

<!-- 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. -->
Ubuntu 19.10 x86_64

**Issue description:**
<!-- What happened, and what was expected. -->
Expected: can access `NativeScript.class_name` as a property
Happened: `Expected classifier as member` error, probably because `class_name` is a keyword.

**Steps to reproduce:**
```gdscript
	var ns = NativeScript.new()

	ns.set_class_name("class") # ok
	print(ns.get_class_name()) # ok

	ns.class_name = "class" # error
	print(ns.class_name) # error
```
Repository: pytorch
Issue: Custon C++ classes are not traceable 
Labels: oncall: jit,weeks

## 🐛 Bug

Attempt to trace model utilizing custom C++ classes built according to https://pytorch.org/tutorials/advanced/torch_script_custom_classes.html
end up with error below:
```
RuntimeError: false INTERNAL ASSERT FAILED at "/home/mark/.local/lib/python3.6/site-packages/torch/include/ATen/core/builtin_function.h":62, please report a bug to PyTorch. BuiltinFunction had a graph requested from it. This probably indicates that the JIT calling context needs a special case on Function::isGraphFunction()
```
Note, model is script-able, but not traceable.

## To Reproduce

build any class according to https://pytorch.org/tutorials/advanced/torch_script_custom_classes.html and trace it

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

I would expect model to be traceable with custom C++ classes exactly as with custom ops. 

## 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
```
mark@MEREMEEV-LT:~$ python3 collect_env.py
Collecting environment information...
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 18.04.5 LTS (x86_64)
GCC version: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
Clang version: 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
CMake version: version 3.10.2

Python version: 3.6 (64-bit runtime)
Is CUDA available: True
CUDA runtime version: 10.2.89
GPU models and configuration: GPU 0: GeForce GTX 1650
Nvidia driver version: 450.66
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.8.0.2
/usr/lib/x86_64-linux-gnu/libcudnn_adv_infer.so.8.0.2
/usr/lib/x86_64-linux-gnu/libcudnn_adv_train.so.8.0.2
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_infer.so.8.0.2
/usr/lib/x86_64-linux-gnu/libcudnn_cnn_train.so.8.0.2
/usr/lib/x86_64-linux-gnu/libcudnn_ops_infer.so.8.0.2
/usr/lib/x86_64-linux-gnu/libcudnn_ops_train.so.8.0.2
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.17.4
[pip3] torch==1.6.0
[pip3] torch2trt==0.1.0
[pip3] torchfile==0.1.0
[pip3] torchnet==0.0.4
[pip3] torchsummary==1.5.1
[pip3] torchvision==0.7.0
[conda] Could not collect


## Additional context

<!-- Add any other context about the problem here. -->


cc @gmagogsfm
Repository: godot
Issue: Image thumbnails in FileSystem distorted
Labels: bug,topic:editor,confirmed

<!-- 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. -->
v3.2.3.stable.official

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->

macOS Catalina 10.15.7

**Issue description:**
<!-- What happened, and what was expected. -->
Image assets containing text menu in the official [tutorial](https://docs.godotengine.org/en/stable/getting_started/step_by_step/ui_main_menu.html), when imported to Godot, they look like this:

![image](https://user-images.githubusercontent.com/1202134/97797420-d8cd5580-1c57-11eb-9b97-5a6bf65f5b98.png)

I believe neat, elegant UI will makes you guys more efficiency.

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
[MainMenuDesign.zip](https://github.com/godotengine/godot/files/5470340/MainMenuDesign.zip)
Repository: pytorch
Issue: Grad strides do not match bucket view strides.
Labels: oncall: distributed,module: memory format,module: ddp

[W reducer.cpp:313] Warning: Grad strides do not match bucket view strides. This may indicate grad was not created according to the gradient layout contract, or that the param's strides changed since DDP was constructed.  This is not an error, but may impair performance.
grad.sizes() = [1024, 1024, 1, 1], strides() = [1024, 1, 1024, 1024]
bucket_view.sizes() = [1024, 1024, 1, 1], strides() = [1024, 1, 1, 1] (function operator())

this problem impair performance .
what can i do?

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @SciPioneer @H-Huang @VitalyFedyunin @jamesr66a @ppwwyyxx
Repository: neovim
Issue: concealcursor not set from ftplugin when loaded via bufadd+bufload+nvim_win_set_buf
Labels: bug,api,options

### Bug

Setting a custom `concealcursor` value in an after/ftplugin does not "stick" when a buffer is loaded via bufadd + bufload. Other values from the ftplugin _are_ set correctly.

- `nvim --version`: v0.5.0-773-g932585fd9 (edit: also v0.5.0-787-g98024853f)
- Operating system/version: WSL/Ubuntu
- Terminal name/version: alacritty
- `$TERM`: xterm-256color

### Steps to reproduce using `nvim -u NORC`

See https://github.com/taylan97/concealcursor-bug.vim for reproduction fixture and instructions.

_This may not be a bug, it's unclear if loading a file via `bufadd -> bufload -> nvim_win_set_buf` is intended to load ftplugins or not. It definitely does apply some settings from the ftplugins file, so probably._

### Actual behaviour

`concealcursor `value is not correctly set from `after/ftplugin` file.

### Expected behaviour

`concealcursor `value should be set according to ftplugin.

Thank you for your time.
Repository: flutter
Issue: [web] Scroll is not recognized by the browser
Labels: framework,engine,f: scrolling,customer: crowd,platform-web,has reproducible steps,P2,team-web,triaged-web,found in release: 3.19,found in release: 3.20

## Steps to Reproduce

Flutter is painted on a canvas and the browser doesn't detect the scroll.

This causes problems when the native browser uses the scroll to perform their own actions. 

Current problems:

- Safari and Chrome iOS/Android address and bottom bar navigation doesn't collapse when scrolling:
Issues: https://github.com/flutter/flutter/issues/64572 https://github.com/flutter/flutter/issues/68877

|  Current behavior  |  Expected behavior (would also need to scroll) |
|---|---|
|   <img height="400" src="https://user-images.githubusercontent.com/19904063/97805735-36fa3880-1c58-11eb-92ca-0c7436080c6f.gif" />  |   <img height="400" src="https://user-images.githubusercontent.com/19904063/97805757-52654380-1c58-11eb-95a5-8d747c560240.gif" />  |
- iOS scroll to top by tapping on the status bar doesn't work. A feature available for any website in any ios browser or WKWebView

- iOS GoogleMaps, Google Assistant, Facebook & Facebook Messenger displays in-app websites inside a draggable modal. Because of scroll is not detected, the modal is closed instead of scrolling upwards.

<img height="400" src="https://user-images.githubusercontent.com/19904063/97805974-9efd4e80-1c59-11eb-941a-910518366ac0.gif" />
Repository: rust
Issue: Variables not always moved into `async move` block
Labels: A-closures,A-borrow-checker,T-compiler,A-async-await,AsyncAwait-Triaged

[Playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=4d231e147d97e7e83cc0ebec8fe58f16):

```rust
use std::cell::UnsafeCell;
use std::sync::{Arc, Mutex};

#[tokio::main]
async fn main() {
    let arena = 0;
    let mut track = Vec::new();
    async move { track.push(&arena) }.await;
}
```

rustc v1.47.0 stable

Error:
```
error[E0597]: `arena` does not live long enough
 --> src/main.rs:8:29
  |
7 |     let mut track = Vec::new();
  |         --------- lifetime `'1` appears in the type of `track`
8 |     async move { track.push(&arena) }.await;
  |                  -----------^^^^^^- - `arena` dropped here while still borrowed
  |                  |          |
  |                  |          borrowed value does not live long enough
  |                  argument requires that `arena` is borrowed for `'1`

error: aborting due to previous error; 2 warnings emitted
```

Which is because `track` is captured by reference and not by value, while `arena` is captured by value.

By submitting this issue, I assume that the intended semantics for `move` is:
> move value(s) into the closure/block, even if the closure/block only seems to need to store reference(s)

which would make this a bug.
Repository: pytorch
Issue: [feature request] Show warning if optimizer.zero_grad() was not called before optimizer.step()
Labels: module: nn,module: optimizer,triaged,module: ux

## Issue description

It is easy to introduce an extremely nasty bug in your code by forgetting to call `zero_grad()` or calling it at the beginning of each epoch instead of the beginning of each iteration.

I propose adding a simple check to ensure that `zero_grad()` is called before each `step()` and show a warning if it is violated. If this behavior is intentional (e.g., for gradient accumulation), one should be able to suppress the warning by passing an extra option to the `step()` function or the constructor of the optimizer


cc @albanD @mruberry @vincentqb
Repository: godot
Issue: AtlasTexture Region and Margin ignored for Line2D
Labels: bug,topic:rendering,topic:2d

**Godot version:**
v3.2.3.stable.mono.official

**OS/device including version:**
Microsoft Windows 10 Pro, version 10.0.18363 Build 18363

**Issue description:**
It's all in the title: Line2D nodes don't make use of AtlasTexture Region and Margin properties and instead use the full texture.
This makes using them with sprite sheets a hassle as you can't specify what rect is visible.
[It seems that this issue has existed for at least a couple years now, judging from this Q&A page.](https://godotengine.org/qa/36054/how-to-animate-a-line2d)

**Steps to reproduce:**
1. Create a Line2D node in the editor and add 2 or more points
2. Set its Texture to an AtlasTexture
3. Modify the Region and/or Margin properties; note how nothing changes on the line

**Minimal reproduction project:**
[AtlasBug.zip](https://github.com/godotengine/godot/files/5471781/AtlasBug.zip)
Repository: create-react-app
Issue:  react-scripts 4.0.1 errors out during npm install
Labels: stale,needs triage,issue: bug report

When using react-scripts version 4.0.0, attempting to run `npm i` causes an error. The following is then displayed:

`npm ERR! Cannot read property 'matches' of undefined`

This is specific to version 4.0.0, as everything installs fine with version 3.4.3.

Of note is the fact that the yarn installation works fine. (Sadly I do need to use npm when deploying.)

Here is what was run prior to the installation attempt:

`rm -rf node_modules/`
`rm package-lock.json`
`npm cache clear --force`

Node version: 15.0.1, npm version: 7.0.7.

If this is relevant here's the entire dependency list:

`"dependencies": {`
`    "@amcharts/amcharts4": "^4.10.9",`
`    "@amcharts/amcharts4-geodata": "^4.1.18",`
`    "react": "^17.0.1",`
`    "react-dom": "^17.0.1",`
`    "react-scripts": "4.0.0",`
`    "react-router-dom": "^5.2.0"`
`  },`
`  "devDependencies": {`
`    "eslint": "^7.12.1",`
`    "eslint-config-airbnb": "^18.2.0",`
`    "eslint-plugin-import": "^2.22.1",`
`    "eslint-plugin-jsx-a11y": "^6.4.1",`
`    "eslint-plugin-react": "^7.21.5",`
`    "eslint-plugin-react-hooks": "^4.2.0"`
`  },`
Repository: rust
Issue: error[E0391]: cycle detected when computing type of async fn
Labels: A-type-system,A-diagnostics,T-compiler,C-bug,A-async-await,AsyncAwait-Triaged,T-types

I tried this code:
```rust
use futures::future::FutureExt;

async fn foo() {
    FutureExt::boxed(async {
        foo().await;
    });
}
```
https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=19653eea2af1dd97a8d48126dfd7d683

I expected it to compile, but it gave the following error:
> error[E0391]: cycle detected when computing type of `foo::{{opaque}}#0`

edit:
With one minor change, it compiles:
```rust
async fn foo() {
    Box::new(async {
        foo().await;
    });
}
```

There are no rules that would explain why the first should fail when this succeeds.
Repository: pytorch
Issue: LayerNorm on Android will cause very high cpu usage
Labels: oncall: mobile

## 🐛 Bug

Recently, I deploy my model to android phone with arm32 cpu. I found that even my model is very simple, for example, only has one Linear and one LayerNorm, the cpu usage is still very high (about 40% when observing with top). After I discard LayerNorm layer or I can re-write laynorm by myself, the cpu usage drops to 2%~3%. Because I am working on streaming speech recognition, I do inference every 160ms to imitate the speech recording and feature extraction. 

## To Reproduce

Steps to reproduce the behavior:

1. Define a simple Module with Linear and LayerNorm layers and export the model using torch.jit.script
2. Build libtorch for android after clone pytorch using ./scripts/build-android.sh
3. Run forward using C++ interface on android. Keep in mind that do inference every xx ms (you can use sleep to control the inference frequency)
4. Observing cpu usage using top 

## Expected behavior

When the model has LayerNorm, the cpu usage will be high. But if I discard LayerNorm or re-writing LayerNorm by myself, the cpu usage will be low. 

## Environment



 - PyTorch Version : 1.6.0
 - OS (e.g., Linux): 
 - How you installed PyTorch (`conda`, `pip`, source): souce, libtorch.a
 - Build command you used (if compiling from source):  ./scripts/build_android.sh
 - Python version: 3.6
 - NDK: r19c
Repository: PowerToys
Issue: [Run][WindowWalker Plugin] Display the application icon for a running process
Labels: Idea-Enhancement,Help Wanted,Product-PowerToys Run,Status-In progress,Run-Plugin

Now that we can use PT Run as just a window walker (thanks devs!) it would be useful to quickly visually identify running programs by their icons.

Currently a generic icon is used for all running processes, which means that the user has to read the text to figure out which (if any) window is the one they are looking for. Otherwise they have to keep typing (with no typos) to narrow down the query results.

The point of the window walker is to be faster than Alt+Tab, so speed is crucial.

I would like to request that the relevant application icon is used instead of the generic one. Even better – if feasible – use tab icon for each open tab in a browser.

Below are some mockups to illustrate the problem and suggested solution:

![mockup](https://user-images.githubusercontent.com/69995022/97826295-2b604d80-1cfc-11eb-8d9c-8421df60a799.png)

---

If you'd like to see this feature implemented, add a 👍 reaction to this post.
Repository: create-react-app
Issue: getPackageInfo function in createReactApp.js incorrectly parses packages with both a scope and a version
Labels: needs triage,issue: bug report

### Describe the bug

`getPackageInfo('@scope/cra-template-custom@1.2.3')` should return
```javascript
{
      name: '@scope/cra-template-custom',
      version: '1.2.3',
}
```
but instead returns:
```javascript
{
      name: '@scope/cra-template-custom',
      version: 'scope/cra-template-custom',
}
```

The relevant code from [createReactApp.js](https://github.com/facebook/create-react-app/blob/master/packages/create-react-app/createReactApp.js#L756) is:
```javascript
  } else if (installPackage.match(/.+@/)) {
    // Do not match @scope/ when stripping off @version or @tag
    return Promise.resolve({
      name: installPackage.charAt(0) + installPackage.substr(1).split('@')[0],
      version: installPackage.split('@')[1],
    });
  }
```

For the name property, it is stripping off the initial '@' with `.substr(1)` before splitting.
For the version property, the `.substr(1)` is missing.

The `packageMatch` regex in `getTemplateInstallPackage` may be a more general approach that could be used here.

`getPackageInfo` is used in the `run` function to validate the compatibility of the template version with the react-scripts version.  Because `getPackageInfo` returns a garbage version property, this check is skipped at `if (!semver.valid(packageVersion)) {`.

### Steps to reproduce

I don't have a good scenario to demo the problem because things just trudge along, but I did sketch out some unit tests.  You'll need to export getPackageInfo for these tests to run.

`getPackageInfo.test.js`
```javascript
'use strict';

const { getPackageInfo } = require('../createReactApp');

describe('getPackageInfo', () => {
  it('cra-template gives name=cra-template', async () => {
    await expect(getPackageInfo('cra-template')).resolves.toStrictEqual({
      name: 'cra-template',
    });
  });

  it('@scope/cra-template-custom gives name=@scope/cra-template-custom', async () => {
    await expect(
      getPackageInfo('@scope/cra-template-custom')
    ).resolves.toStrictEqual({
      name: '@scope/cra-template-custom',
    });
  });

  it('cra-template@1.2.3 gives name=cra-template, version=1.2.3', async () => {
    await expect(getPackageInfo('cra-template@1.2.3')).resolves.toStrictEqual({
      name: 'cra-template',
      version: '1.2.3',
    });
  });

  it('@scope/cra-template-custom@1.2.3 gives name=@scope/cra-template-custom, version=1.2.3', async () => {
    await expect(
      getPackageInfo('@scope/cra-template-custom@1.2.3')
    ).resolves.toStrictEqual({
      name: '@scope/cra-template-custom',
      version: '1.2.3',
    });
  });
});


```

### Expected behavior

This function should parse packages with any combination of scopes and versions.

### Actual behavior

It doesn't correctly parse packages with scopes and versions.

![image](https://user-images.githubusercontent.com/350287/97832158-f534b680-1c86-11eb-98c3-10fa3f4da986.png)
Repository: godot
Issue: Linking Godot project in Xcode results in entire project folder in archives
Labels: bug,platform:ios,topic:editor,confirmed,topic:export

**Godot version:**
3.2.3 stable xcode 11.3

When exporting for iOS and linking the Godot project in Xcode, the entire project folder is added to the archive that is then uploaded to App Store Connect. This includes any asset sub-folders and the .import folder which may contain no longer valid .stex resources.

a 200mb export (arm64 only) without a linked Godot project becomes a 600mb export using the linked project instructions per the docs.

 https://docs.godotengine.org/en/stable/getting_started/workflow/export/exporting_for_ios.html


**Minimal reproduction project:**
Export a project for ios and link existing Godot project. Create an archive, 'show in finder' and 'show package contents' on  products > application > app.  Compare folder structure and size to an archive created without a linked project.
Repository: terminal
Issue: hope to set padding proportionally
Labels: Area-TerminalControl,Area-Settings,Product-Terminal,Issue-Task

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

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!
-->

# Description of the new feature/enhancement

<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

In Windows Terminal, the padding around the text within the window can be set up by

```json
{
    "profiles": {
        "defaults": {
            "padding": "#, #, #, #",
        }
    }
}
```

However, the value of this setting can only be a fixed pixel size, not a scale. This can have some unintended effects in some situations.

For example, here is my Windows Terminal window.

![image](https://user-images.githubusercontent.com/38575841/97842951-73df3180-1d23-11eb-92eb-3f0c096eac55.png)

When Windows Terminal starts up at the default window size, the text is lined up normally in the display as shown in the picture.
However, when I maximize, the text is not in the position I want it to be.

![image](https://user-images.githubusercontent.com/38575841/97842909-65911580-1d23-11eb-95b0-9569313aeee1.png)

This is due to the fact that padding can only be set to a certain value of pixels, but not as a percentage of the current window size, if padding support proportional settings, then this problem can be solved, and Windows Terminal can become more beautiful and customizable.
Repository: create-react-app
Issue: Warning: validateDOMNesting(...): <table> cannot appear as a descendant of <p>.
Labels: stale

react-dom.development.js:88 Warning: validateDOMNesting(...): <table> cannot appear as a descendant of <p>.
    in table (created by ForwardRef(Table))
    in ForwardRef(Table) (created by WithStyles(ForwardRef(Table)))
    in WithStyles(ForwardRef(Table)) (created by StickyHeadTable)
    in div (created by ForwardRef(TableContainer))
    in ForwardRef(TableContainer) (created by WithStyles(ForwardRef(TableContainer)))
    in WithStyles(ForwardRef(TableContainer)) (created by StickyHeadTable)
    in div (created by ForwardRef(Paper))
    in ForwardRef(Paper) (created by WithStyles(ForwardRef(Paper)))
    in WithStyles(ForwardRef(Paper)) (created by StickyHeadTable)
    in StickyHeadTable (created by tabs)
    in p (created by ForwardRef(Typography))
    in ForwardRef(Typography) (created by WithStyles(ForwardRef(Typography)))
    in WithStyles(ForwardRef(Typography)) (created by TabPanel)
    in div (created by TabPanel)
    in div (created by TabPanel)
    in TabPanel (created by tabs)
    in div (created by tabs)
    in tabs (created by ConnectFunction)
    in ConnectFunction (created by Context.Consumer)
    in Route (created by App)
    in Switch (created by App)
    in Router (created by BrowserRouter)
    in BrowserRouter (created by App)
    in App
    in Provider