sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: libgcc_s.so.1 must be installed for pthread_cancel to work
Labels: high priority,module: binaries,triaged

## 🐛 Bug

Only get error with nightly, 1.5.1 works fine.

(Edit: I saw this at other places. The main problem of getting this error is I can't see the original error trace.)

## How to reproduce

```
>>> import torchvision
>>> x = torchvision.models.resnet.resnet50(True)
Downloading: "https://download.pytorch.org/models/resnet50-19c8e357.pth" to /home-nfs/rluo/.cache/torch/hub/checkpoints/resnet50-19c8e357.pth
100%|███████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████████| 97.8M/97.8M [00:01<00:00, 65.4MB/s]
libgcc_s.so.1 must be installed for pthread_cancel to work
Aborted
```

By stepping in, it seems the error occurs at the end of downloading.

## Environment
Collecting environment information...
PyTorch version: 1.7.0.dev20200709+cu101
Is debug build: No
CUDA used to build PyTorch: 10.1

OS: CentOS Linux 7 (Core)
GCC version: (GCC) 7.5.0
CMake version: version 3.14.0

Python version: 3.7
Is CUDA available: Yes
CUDA runtime version: 10.1.243
GPU models and configuration:
GPU 0: GeForce GTX 1080 Ti
GPU 1: GeForce GTX 1080 Ti

Nvidia driver version: 418.43
cuDNN version: Could not collect

Versions of relevant libraries:
[pip] detectron-pytorch==0.1
[pip] gluoncv-torch==0.0.3
[pip] numpy==1.18.4
[pip] numpydoc==0.9.2
[pip] pytorch-lightning==0.8.6.dev0
[pip] pytorch-pretrained-bert==0.6.2
[pip] torch==1.7.0.dev20200709+cu101
[pip] torchvision==0.8.0.dev20200719+cu101
[conda] blas                      1.0                         mkl
[conda] cudatoolkit               10.1.243             h6bb024c_0
[conda] detectron-pytorch         0.1                       dev_0    <develop>
[conda] gluoncv-torch             0.0.3                    pypi_0    pypi
[conda] magma-cuda102             2.5.2                         1    pytorch
[conda] mkl                       2019.5                      281    conda-forge
[conda] mkl-include               2020.1                      217
[conda] mkl-service               2.3.0            py37he904b0f_0
[conda] mkl_fft                   1.0.15           py37ha843d7b_0
[conda] mkl_random                1.1.0            py37hd6b4f25_0
[conda] numpy                     1.17.2                   pypi_0    pypi
[conda] numpydoc                  0.9.2                      py_0
[conda] pytorch-lightning         0.8.6.dev0                dev_0    <develop>
[conda] pytorch-pretrained-bert   0.6.2                    pypi_0    pypi
[conda] torch                     1.7.0.dev20200709+cu101          pypi_0    pypi
[conda] torchvision               0.8.0.dev20200719+cu101          pypi_0    pypi


cc @ezyang @gchanan @zou3519 @seemethere @malfet
Repository: TypeScript
Issue: jsdoc @type is not working properly for some class method variant
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 STOP 🚨 STOP 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  4.0.0-beta and 3.9.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** jsdoc, type, typedef, class method, typechecking

**Code**

```ts
// @strict: false

/**
 * @typedef {(newNumber: number) => void} SetNumberFunc
 */

class A {
    /**
     * @type {number}
     */
    a = 0;

    constructor() {
        this.a = 0;
    }

    /**
     * @type {SetNumberFunc}
     */
    setAVariant1(newNumber) {
        this.a = newNumber;
    }
}
```

**Expected behavior:** The `newNumber` param should have a `number` type when hovering on the `setAVariant1` method.

**Actual behavior:** The `newNumber` param have `any` type when hovering on the `setAVariant1` method.

**Playground Link:** [Playground Link](https://www.typescriptlang.org/play?ts=4.0.0-beta&useJavaScript=true#code/PQKhFgCgAIWgBALgTwA4FMAm6Bm0DeAFAHboDuAcgK4C2ARugE4Bc0xtDjAlNALwB80AG4B7AJaYAvtADK6RNXpMAYlWIBjKLGBQo6gDYBDAM7HoAQQJboN0BBg2bcJGnQF2SxpOuOQOhzaGfNAADADcugHQ6iLExoiMVOqIIoyEPPg+jjaIABZixgB0QbyhEVHekFl2WbAIKBgEcgocKmrqldl1wMDQFCKI0ADqqQDWYsQA5tCEABIiQkzQeW408rkimGyGa9CGxFvG6G6klK2My67QBXvEyFy1fllHiOYAaoaMYvuIAIwk5EUnAytUceQKxWCpyBTHK2Uq1TAj3qV3wzRhjFUGk62TgPWGYwm0zmCyWK2gazym22u32h2ObEB50ujRuHmBj382Re70+32IiAATMEcO1EGJYjNoecQVFsuCiiVGWdPFkEVEanLnA03Gj5BisR1kfiRoxxlMZvNFhdyZSNltiDs3HToEcTkzPCy3GyZZznvJeV8fgBmKEezh8QSZOVg-KKsMqzhqqCSIA)

**Related Issues:** <!-- Did you find other bugs that looked similar? --> -
Repository: godot
Issue: [Mono] 3.2.2 Android Plugin - Mono: Core API hash mismatch.
Labels: bug,platform:android,topic:porting,topic:dotnet

<!-- 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.2.stable.mono.official


**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Android with GLES3


**Issue description:**
<!-- What happened, and what was expected. -->
Just use the GodotGooglePlayBilling on a Android Custom build on a project that uses Mono C# and it will warning on the console

```bash
07-20 01:03:29.042  9543  9576 I godot   : Godot Engine v3.2.2.stable.mono.official - https://godotengine.org
07-20 01:03:29.054  9543  9576 I godot   : OpenGL ES 3.0 Renderer: Adreno (TM) 506
07-20 01:03:29.087  9543  9576 I godot   :
07-20 01:03:29.396  9543  9576 E godot   : **ERROR**: Mono: Core API hash mismatch.
07-20 01:03:29.396  9543  9576 E godot   :    At: modules/mono/mono_gd/gd_mono.cpp:494:_init_godot_api_hashes() - Mono: Core API hash mismatch.
07-20 01:03:29.398  9543  9576 I godot   : Mono: Logfile is: /data/data/org.godotengine.gpbiapmono/files/mono/mono_logs/2020_07_20 01.03.29 (9543).txt
07-20 01:03:29.802  9543  9576 I godot   : GPB: startConnection
07-20 01:03:30.546  9543  9576 I godot   : GPB: connected
```

**Steps to reproduce:**
Download the GPB_IAP_MONO.zip from the following section

![image](https://user-images.githubusercontent.com/2466466/87845814-4ddf6f80-c8a1-11ea-832a-e268e50b4661.png)
Install Android Build Template

Build and Run on Android Device

Check the adb logcat

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
[GPB_IAP_MONO.zip](https://github.com/godotengine/godot/files/4945448/GPB_IAP_MONO.zip)
Repository: pytorch
Issue: [Feature Request] named tensor support for `tensordot`(tensor contract)
Labels: triaged,enhancement,module: named tensor

## 🚀 Feature
`tensordot` use name to specify which rank to contract

## Motivation

when tensor rank is high, `tensordot`(contract) is not easy to specify the contract rank

## Pitch

eg: there is two rank-2 tensor a and b
`torch.tensordot(a, b, dims=(["first name of a", "second name of a"], ["second name of b", "first name of b"]))`

## Alternatives

currently, we need to wrap `tensordot`, analyze the tensor name, and then tensordot, and then recovery the names


cc @zou3519
Repository: node
Issue: debug code run inside vm doesn't support inline sourcemaps 
Labels: inspector

<!--
Thank you for reporting an issue.

This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help


Please fill in as much of the template below as you're able.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name
-->

* **Version**: v14.5.0
* **Platform**: Darwin Kernel Version 19.5.0
* **Subsystem**: vm
* **Chrome Version**: 86.0.4207.0

### What steps will reproduce the bug?

<!--
Enter details about your bug, preferably a simple code snippet that can be
run using `node` directly without installing third-party dependencies.
-->
testcase: https://github.com/denghongcai/node-vm-sourcemap-test-case

I insert a `debugger` statement in `src/index.ts` 's `sayHello` method

not working step (use vm):
```bash
npm run build
npm run inspect
```
in devtools, no sourcemap detected
![image](https://user-images.githubusercontent.com/1433247/87911348-0c67e380-ca9e-11ea-913d-1d8dd2b2f08f.png)


working step (no vm):
```bash
npm run build
npm test
npm run inspect-index
```

seems if vm run code with inline sourcemap, it will not be parsed by chrome devtools?

### How often does it reproduce? Is there a required condition?

always

### What is the expected behavior?

<!--
If possible please provide textual output instead of screenshots.
-->
I expected when debug in devtools, sourcemap will be parsed, displayed correctly
Repository: terminal
Issue: Feature: Set text to display in the background of a terminal instead of just an image
Labels: Issue-Feature,Area-Extensibility,Area-Settings,Product-Terminal

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

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

Within Profile Settings add the ability to not only have a Background image but also background text. This is set-up within the Profile Settings as either within Background Image Settings or as its own group of properties.

Why:  When using multiple profiles with lots of Tabs open its handy to be able to recognise which server etc I'm working on at any one time and having an opaque reminder is really handy. Currently I'm doing this with images (see Mockup Below), however it would be nicer to have the option to just add text to the background.

Example Mockup: 

![ms-feature](https://user-images.githubusercontent.com/1574649/87923536-9059a580-ca75-11ea-9796-135f0fed9b62.png)


# Proposed technical implementation details (optional)

Within Profile Settings and "list"

```
"list":
        [	   
            {
                // Make changes here to the powershell.exe profile.
                "guid": "{61c54bbd-c2c6-5271-96e7-009a87ff44bf}",
                "name": "Windows PowerShell",
                "commandline": "powershell.exe",
                "hidden": false,
		"backgroundText" : "IamServer1",
		"backgroundTextFontStyle" : "Bold",
		"backgroundTextFontSize" : "32",
		"backgroundTextFont": "Sans-Serif"
		"backgroundTextFontColor": "#93f533"
		"backgroundTextAlign": "centre"
		"backgroundTextOpacity": 0.1"
            },
```
Repository: godot
Issue: Parameter Hints for Functions defined in Singletons not showing up
Labels: bug,topic:gdscript,topic:editor

**Godot version:**
3.2.2.stable.official


**OS/device including version:**
Both Windows 10 1909 and Fedora 31

**Issue description:**
When typing functions from a custom singleton script, no parameter hints are shown, makes it hard to fill out real big functions. Then poor ol' me is left stranded to remember what parameters should go in here.

**Steps to reproduce:**

Make a script, e.g. "Node2.gd", put in a function with parameters, and define it as a singleton.

![node2](https://user-images.githubusercontent.com/9379526/87924506-e713af00-ca76-11ea-9035-3cc5ac1f2a16.PNG)

Have another script, e.g. "Node.gd", autocomplete Node2.gd's function as normal. Parameter hints will not show up as they otherwise do.

What happens:
![badhint](https://user-images.githubusercontent.com/9379526/87924640-12969980-ca77-11ea-9e10-102b0c7c1fb4.PNG)

Expected behaviour (these hints do show up if trying to call the function within the same script file):
![gooodhint](https://user-images.githubusercontent.com/9379526/87924666-19bda780-ca77-11ea-98c3-8f0ce1a39f9a.PNG)

**Minimal reproduction project:**
[parameter_hints.zip](https://github.com/godotengine/godot/files/4946873/parameter_hints.zip)
Repository: opencv
Issue: I got "CONFIGURATION IS NOT SUPPORTED: validate setupvars script in install   directory" when I cmake opencv4.4,win10
Labels: priority: low,category: build/install

##### System information (version)
<!-- Example
- OpenCV => 4.2
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2017
-->

- OpenCV => :4.4:
- Operating System / Platform => :Windows 10:
- Compiler => :vs 2017:

##### Detailed description
When I install OpenCV 4.4 on Windows 10 by VS2017, I got this error when I use Cmake:
```
Registering hook 'INIT_MODULE_SOURCES_opencv_dnn': G:/opencv4.4/opencv-4.4.0/modules/dnn/cmake/hooks/INIT_MODULE_SOURCES_opencv_dnn.cmake
CMake Warning at cmake/OpenCVGenSetupVars.cmake:54 (message):
  CONFIGURATION IS NOT SUPPORTED: validate setupvars script in install
  directory
Call Stack (most recent call first):
  CMakeLists.txt:968 (include)

```
Repository: PowerToys
Issue: [Run] Exclude unwanted file extensions
Labels: Idea-Enhancement,Product-PowerToys Run

# Summary of the new feature/enhancement
I use phpstorm for web development and when I search for a project or a file from that project it's show some unusual file extension from recentFiles folder

# Proposed technical implementation details (optional)
An option where you can exclude a specific folder OR a specific extension will be nice.

![image](https://user-images.githubusercontent.com/67105249/87936396-6dda8300-ca9b-11ea-96c1-99d93239f4e2.png)
Repository: react
Issue: Should act() warnings be deduplicated by component stack?
Labels: Type: Discussion,Component: Reconciler

React version: `16.13.1` (latest) and `0.0.0-7f28234f8` (next)

## Steps To Reproduce

1. Create component that has multiple effects (i.e. `useEffect` calls)
2. Render component in a jest test


Link to code example: https://codesandbox.io/s/long-sound-xhe5w?file=/package.json

## The current behavior

A error is logged for each call of `useEffect`.

## The expected behavior

An error per component calling `useEffect`.

## Context

Current errror:
```
Warning: An update to Component ran an effect, but was not wrapped in act(...).

When testing, code that causes React state updates should be wrapped into act(...):

act(() => {
  /* fire events that update state */
});
/* assert on the output */

This ensures that you're testing the behavior the user would see in the browser. Learn more at https://fb.me/react-wrap-tests-with-act
    at Component (https://xhe5w.csb.app/src/index.test.js:23:20)
    at App (https://xhe5w.csb.app/src/index.test.js:35:20)
```

The prescription is to wrap the update in act(). The warning may be unintented because a component with an effect rendered unexpectedly. But due to the rules of hooks it's unlikely that we remove a `useEffect` call: It's easier to prevent rendering a component (wrong branch logic, return early etc) than preventing an effect (which requires moving it to a component we render conditionally).

From my experience most of these cases come down to adding an `act()` and not changing component implementation. In these cases firing errors for each effect makes the console output unreadable. Especially if you compose custom hooks and end up with 4+ effects per component.

An alternate solution would be to only fire an error if the effect was actually scheduled (see #19318).
Repository: rust
Issue: asm!: `push offset` causes `unexpected token!`
Labels: A-inline-assembly,C-bug,F-asm

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

### Code

```rust
#![feature(asm)]

fn main() {
    unsafe {
        asm!(
            "
            push offset 1f
            1:
            "
        );
    }
}
```

### Expectation

Compilable as this assembly code follows the syntax of `.intel_syntax noprefix`.

### Actual

The code will not compile, emitting these errors:

```
error: unexpected token!
 --> src/main.rs:7:13
  |
7 |             push offset 1f
  |             ^
  |
note: instantiated into assembly here
 --> <inline asm>:3:25
  |
3 |             push offset 1f
  |                         ^

error: aborting due to previous error

error: could not compile `rust`.
```

### Other info

See the comments of the question I posted:
https://stackoverflow.com/questions/62989703/push-label-pushs-label-not-the-address-of-label-rust-asm?noredirect=1#62989703

The equivalent code written in GAS compiles with `gcc`:

```asm
    .intel_syntax noprefix

    .globl main

    .section text
main:
    push offset 1f
1:
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.46.0-nightly (346aec9b0 2020-07-11)
binary: rustc
commit-hash: 346aec9b02f3c74f3fce97fd6bda24709d220e49
commit-date: 2020-07-11
host: x86_64-unknown-linux-gnu
release: 1.46.0-nightly
LLVM version: 10.0
```



</p>
</details>
Repository: PowerToys
Issue: [Settings] Design a mechanism to propagate specific system settings to the Settings app
Labels: Idea-Enhancement,Product-Settings

Some modules may need to check system settings to decide when turn on/off some module's feature.
FancyZones needs to check animation settings, PT Run needs to check the enhanced search mode and so on.

Those settings can be retrieved by the modules, but may also also effect the Settings UI.
Since those values should not be persisted in the module's settings, we need a general design to avoid code duplication and to keep the Settings' code as clean as possible.
Repository: rust
Issue: Handle fully-qualified syntax in intra doc links
Labels: T-rustdoc,C-enhancement,P-low,A-intra-doc-links

Related: https://github.com/rust-lang/rust/issues/62834

https://github.com/rust-lang/rust/pull/74489 makes it so that `Type::Item` works for trait items. There currently is anchor ambiguity between multiple traits that share an item, so it's not worth disambiguating further, however if we can fix that It would be nice if `<Type as Trait>::Item` could link to the appropriate bit in the type's impl section.

This would involve parsing the path as _two_ paths, perhaps just using `rustc_ast` and parsing it as a [`TyKind::Path`](https://doc.rust-lang.org/nightly/nightly-rustc/rustc_ast/ast/enum.TyKind.html#variant.Path).
Repository: go
Issue: x/tools/go/expect: test fails when run from the module cache
Labels: Testing,NeedsFix,Tools

The test for `golang.org/x/tools/go/expect` fails when run from another module.

A `go.mod` file was added to the package's `testdata` directory in [CL 216838](https://golang.org/cl/216838). However, that cuts off the `testdata` directory from the rest of the module: there is no special handling for `go.mod` files in `testdata` directories (see #27852). The missing `testdata` directory causes the test to fail when it is run from anywhere other than a clone of the `tools` repository — notably, including when it is run from the module cache, including as a dependency of any other module.

```
$ go version
go version devel +0951939f Fri Jul 17 19:09:40 2020 +0000 linux/amd64

$ go test golang.org/x/tools/go/expect
--- FAIL: TestMarker (0.00s)
    --- FAIL: TestMarker/testdata/test.go (0.00s)
        expect_test.go:57: open testdata/test.go: no such file or directory
    --- FAIL: TestMarker/testdata/go.mod (0.00s)
        expect_test.go:57: open testdata/go.mod: no such file or directory
FAIL
FAIL    golang.org/x/tools/go/expect    0.012s
FAIL

-- go.mod --
module example.com

go 1.15

require golang.org/x/tools v0.0.0-20200720150256-cf97b7f4a4c1 // indirect
```

CC @stamblerre @ridersofrohan @ianthehat
Repository: pytorch
Issue: TypeError: cannot create 'generator' instances
Labels: triaged,module: data parallel

My code works fine with one gpu but I am getting the below error on running with multiple gpu's 
(While using gpu's, I am using torch.nn.DataParallel also)

```
TypeError                                 Traceback (most recent call last)
<ipython-input-22-4eff65f3db67> in <module>
----> 1 model_trainer.train()

<ipython-input-20-76eb25df828c> in train(self)
     47             aux_losses = []
     48 
---> 49             for mlm_loss, aux_loss, is_last in self.model(next(train_loader), max_batch_size = MAX_BATCH_SIZE, return_loss = True):
     50                 loss = mlm_loss + aux_loss
     51                 (loss / grad_accum_every).backward()

/opt/conda/envs/tfgpu37/lib/python3.7/site-packages/torch/nn/modules/module.py in __call__(self, *input, **kwargs)
    548             result = self._slow_forward(*input, **kwargs)
    549         else:
--> 550             result = self.forward(*input, **kwargs)
    551         for hook in self._forward_hooks.values():
    552             hook_result = hook(self, input, result)

/opt/conda/envs/tfgpu37/lib/python3.7/site-packages/torch/nn/parallel/data_parallel.py in forward(self, *inputs, **kwargs)
    154         replicas = self.replicate(self.module, self.device_ids[:len(inputs)])
    155         outputs = self.parallel_apply(replicas, inputs, kwargs)
--> 156         return self.gather(outputs, self.output_device)
    157 
    158     def replicate(self, module, device_ids):

/opt/conda/envs/tfgpu37/lib/python3.7/site-packages/torch/nn/parallel/data_parallel.py in gather(self, outputs, output_device)
    166 
    167     def gather(self, outputs, output_device):
--> 168         return gather(outputs, output_device, dim=self.dim)
    169 
    170 

/opt/conda/envs/tfgpu37/lib/python3.7/site-packages/torch/nn/parallel/scatter_gather.py in gather(outputs, target_device, dim)
     66     # Setting the function to None clears the refcycle.
     67     try:
---> 68         res = gather_map(outputs)
     69     finally:
     70         gather_map = None

/opt/conda/envs/tfgpu37/lib/python3.7/site-packages/torch/nn/parallel/scatter_gather.py in gather_map(outputs)
     61             return type(out)(((k, gather_map([d[k] for d in outputs]))
     62                               for k in out))
---> 63         return type(out)(map(gather_map, zip(*outputs)))
     64 
     65     # Recursive function calls like this create reference cycles.

TypeError: cannot create 'generator' instances
```

Some one please help me with this Issue

Environment: 
Pytorch 1.5.1