sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: CUDA error: device-side assert triggered @ model.cuda()
Labels: needs reproduction,module: cuda,triaged

## 🐛 Bug

I'm trying to run BERT model. However, when I try to tell pytorch to run this model on the GPU, using: `model.cuda()`, I got the CUDA error: device-side assert triggered error. 

## Detailed error message

```
---------------------------------------------------------------------------
RuntimeError                              Traceback (most recent call last)
<command-41501> in <module>
     10 
     11 # Tell pytorch to run this model on the GPU.
---> 12 model.cuda()

/databricks/python/lib/python3.7/site-packages/torch/nn/modules/module.py in cuda(self, device)
    302             Module: self
    303         """
--> 304         return self._apply(lambda t: t.cuda(device))
    305 
    306     def cpu(self):

/databricks/python/lib/python3.7/site-packages/torch/nn/modules/module.py in _apply(self, fn)
    199     def _apply(self, fn):
    200         for module in self.children():
--> 201             module._apply(fn)
    202 
    203         def compute_should_use_set_data(tensor, tensor_applied):

/databricks/python/lib/python3.7/site-packages/torch/nn/modules/module.py in _apply(self, fn)
    199     def _apply(self, fn):
    200         for module in self.children():
--> 201             module._apply(fn)
    202 
    203         def compute_should_use_set_data(tensor, tensor_applied):

/databricks/python/lib/python3.7/site-packages/torch/nn/modules/module.py in _apply(self, fn)
    199     def _apply(self, fn):
    200         for module in self.children():
--> 201             module._apply(fn)
    202 
    203         def compute_should_use_set_data(tensor, tensor_applied):

/databricks/python/lib/python3.7/site-packages/torch/nn/modules/module.py in _apply(self, fn)
    221                 # `with torch.no_grad():`
    222                 with torch.no_grad():
--> 223                     param_applied = fn(param)
    224                 should_use_set_data = compute_should_use_set_data(param, param_applied)
    225                 if should_use_set_data:

/databricks/python/lib/python3.7/site-packages/torch/nn/modules/module.py in <lambda>(t)
    302             Module: self
    303         """
--> 304         return self._apply(lambda t: t.cuda(device))
    305 
    306     def cpu(self):

RuntimeError: CUDA error: device-side assert triggered
```

## Environmental Parameter
Pytorch version: 1.4.0

cc @ngimel
Repository: TypeScript
Issue: Support parsing TSDoc string comments 
Labels: Suggestion,Experience Enhancement

Hi there! 

I had a issue trip around Github and finally ended up here :) 

Last issue was: https://github.com/microsoft/vscode/issues/95408

I am using String Literal types to define classnames and would love to populate with some more information.

So basically:

```ts
type TClassnames = 
   /** Some docs about red-500 */
    | 'bg-color-red-500'
   /** Some docs about red-600 */
    | 'bg-color-red-600'
```

I would expect it to populate the docs on the right side of the intellisense:

<img width="521" alt="Screenshot 2020-02-12 at 07 31 36" src="https://user-images.githubusercontent.com/3956929/74308921-c0d04180-4d69-11ea-8953-48b7da62baa7.png">

This is how we can document with properties:

![Screenshot 2020-02-12 at 10 10 59](https://user-images.githubusercontent.com/3956929/74324332-31398b80-4d87-11ea-8f2e-e15b3ff67433.png)

Which would be amazing to have on string literals.

I thought it was a TSDoc issue, but given this context: https://github.com/microsoft/tsdoc/issues/164, it seems to be VSCode not parsing it... though then it seems to actually be Typescript related?
Repository: flutter
Issue: Flutter - Set target file base on Android product flavors
Labels: c: new feature,platform-android,tool,d: api docs,a: build,P3,team-android,triaged-android

Currently I am using **Flutter** to build my application.

**Background**
I have followed some guide on building different environments entry files:
https://iirokrankka.com/2018/03/02/separating-build-environments/
which create main_dev.dart and main_prod.dart.

Also I have learnt to build flavor for both iOS and Android: https://medium.com/@salvatoregiordanoo/flavoring-flutter-392aaa875f36
which now I can use --flavor <FLAVOR> in the command to build different flavor application.

Now I have encountered a problem when I try to combine two skills.

**Target Result**
Below is what I would like to achieve:

development flavor -> main_dev.dart entry file
production flavor -> main_prod.dart entry file

Problem Encounter
in iOS side, I can target the entry file in .xcconfig file like following:

```
// ios/Flutter/development.xcconfig

#include "Generated.xcconfig"

FLUTTER_TARGET=lib/main_dev.dart
```

I know I can add -t lib/main_dev.dart after flutter run command.
However I would like to ask if there is any solution to set
the flutter target file in Android side inside flavor config?

Appreciate for any help.
Repository: pytorch
Issue: Misleading documentation in torch.nn.functional.fold
Labels: module: docs,module: nn,triaged

Related to this [discussion](https://discuss.pytorch.org/t/how-to-unfold-a-tensor-into-sliding-windows-and-then-fold-it-back/55890), I would like to report a misleading warning in https://github.com/pytorch/pytorch/blob/master/torch/nn/functional.py#L3676. As far as I can see, there is a mismatch between what the inline docs state, i.e. _"Currently, only 4-D output tensors (batched image-like tensors) are supported"_ and what is actually allowed in the function (3-D tensors).

I am reporting this as an issue in the documentation, but maybe this is also worth considering as a bug, since it feels weird that the 'fold' function doesn't accept 4-D tensors.
Repository: opencv
Issue: Feature request: masked cross-correlation of two images
Labels: feature,category: imgproc

##### Detailed description
Current implementation of template matching allows masked templates, but test images cannot be masked. Supporting test-image masking is really important, and has a lot of applications.

I believe this feature is relatively [easy to implement](https://9c0a87a5-a-62cb3a1a-s-sites.googlegroups.com/site/dirkpadfield/Home/MaskedFFTRegistrationPresentation.pdf?attachauth=ANoY7crwDzRQuLAxdVr7Xjvw1OIeNVEkbHJjUxBDmVNQ-MQ-k4EATlr9XCcDrVofPW1ZvJ0Mf4qP3nYdGw83p9dHKmIjSVG97ikT0dMyMu82RgkEfPwCUIQlFvaRCbHECCwBU_r1s1-AS1vMOZV3TOOUBf0HIYuGZXKAYbbWoz8Jw4D0geYcKqJb1TgmKEno6DTAfJ-egP6sNXtfBdfI1g2TrN6qRcLPx-b74AS_8VObIqH-tTQVx0AlZ1H9yBzwgQgapu98_5Cu&attredirects=0), and there are several open source implementations of it with compatible licenses.

In fact, I already found [an implementation](https://github.com/qedsoftware/masked_normxcorr) that is OpenCV-ready. @vpisarev @alalek What do you think?
Repository: youtube-dl
Issue: Please add https://premium.liebscher-bracht.com/
Labels: site-support-request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2020.03.24. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2020.03.24**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single video (this one requies a login): https://premium.liebscher-bracht.com/programs/5-minuten-premium-routinen_migranemp4-93e740
- Playlist (does not require login): https://premium.liebscher-bracht.com/programs/dehnubungen-deutschland-hat-rucken-e05e74?categoryId=16347
- Catalog page (all): https://premium.liebscher-bracht.com/catalog
- Catalog page (all free): https://premium.liebscher-bracht.com/categories/category-wPWkkNebtCQ

## Description

This site's content is in german. Some videos are for free (even without login account) and some of them requires a subscription (actually there is a free trial program for now)

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

If needed, login account can be created here: https://premium.liebscher-bracht.com/orders/customer_info?o=26414
Actually 3 month for free. Requires credit card or Paypal on creation and must be terminated before the trial period expires or continued on a paid subscription base.
Repository: terminal
Issue: Add support for `open-settings` subcommand
Labels: Product-Terminal,Issue-Task,Area-Commandline

From the original spec: 

> #### `open-settings`
> 
> `open-settings [--defaults,-d]`
> 
> Open the settings file. If this command is provided alone, it does not open the
> terminal window.
> 
> **Parameters**:
> * `--defaults,-d`: Open the `defaults.json` file instead of the `profiles.json`
>   file.
Repository: terminal
Issue: Add support for `list-profiles` subcommand
Labels: Product-Terminal,Issue-Task,Area-Commandline


From the original spec: 

> #### `list-profiles`
> 
> `list-profiles [--all,-A] [--showGuids,-g]`
> 
> Displays a list of each of the available profiles. Each profile displays it's
> name, separated by newlines.
> 
> **Parameters**:
> * `--all,-A`: Show all profiles, including profiles marked `"hidden": true`.
> * `--showGuids,-g`:  In addition to showing names, also list each profile's
>   guid. These GUIDs should probably be listed _first_ on each line, to make
>   parsing output easier.
Repository: terminal
Issue: Add support for `--file,-f configuration_file` for reading a list of commands from a file
Labels: Product-Terminal,Issue-Task,Area-Commandline


From the original spec: 
> Run these commands in the given Windows Terminal session. Enables opening new
> tabs in already running Windows Terminal windows. See [Future
> Considerations](#Future-Considerations) for more details.
Repository: rust
Issue: Mismatched type error message when `!` (never) used as return
Labels: A-diagnostics,T-compiler,D-papercut

<!--
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.
-->

I tried this code:

```rust
// Experiment: Dangling Reference
fn main() {
    let s:&str = "Hello";
    dangling_reference(s);
}

fn dangling_reference(s:&str) -> ! {

}
```

I expected to see this happen: 
A suggestion to add `loop{}` inside `dangling_reference(s:&str)` function.

Instead, this happened:
```
mismatched types

expected `!`, found `()`

note:   expected type `!`
      found unit type `()`rustc(E0308)
main.rs(8, 4): implicitly returns `()` as its body has no tail or `return` expression
main.rs(8, 34): expected `!`, found `()`
```

### 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.41.0 (5e1a79984 2020-01-27)
binary: rustc
commit-hash: 5e1a799842ba6ed4a57e91f7ab9435947482f7d8
commit-date: 2020-01-27
host: x86_64-unknown-linux-gnu
release: 1.41.0
LLVM version: 9.0
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
$ RUST_BACKTRACE=1 cargo build
   Compiling rust_experiment v0.0.1 (/home/jajay/Projects/rust-experiment)
error[E0308]: mismatched types
 --> src/main.rs:8:34
  |
8 | fn dangling_reference(s:&str) -> ! {
  |    ------------------            ^ expected `!`, found `()`
  |    |
  |    implicitly returns `()` as its body has no tail or `return` expression
  |
  = note:   expected type `!`
          found unit type `()`

error: aborting due to previous error

For more information about this error, try `rustc --explain E0308`.
error: could not compile `rust_experiment`.
```

</p>
</details>
Repository: angular
Issue: [i18n] how to best support a library author providing translations for their library
Labels: feature,area: i18n,freq1: low,P4,feature: under consideration,area: docs

We should discuss *how to best support a library author providing translations for their library*.
Repository: pytorch
Issue: Saved model behaves differently on same data
Labels: needs reproduction,module: serialization,triaged

```
def get_model():
    model = PointModel()
    model.cuda()
    logging.info('load model from {}'.format(MODEL_PATH_POINTCNN))
    model.load_state_dict(torch.load(MODEL_PATH_POINTCNN)['model_state'])
    model.eval()

    return model

net = get_model()
inputs = torch.randn(2, 4096, 8).cuda()
for i in range(2):
    with torch.no_grad():
        y = net(inputs)
        print(y)
```
The question is that the above `y` is changed if the pretrained model is loaded, otherwise it is the same.  This questions only occur in some network.
Repository: pytorch
Issue: can't wrap two models in the same class
Labels: needs reproduction,triaged

## 🐛 Bug

I define a class with model initializer. When I wrap one model with that class
it looks fine, but with two model instances, it does not converge.

Code example:

def wrapper(nn.Module):

    def __init__(self, model):
          self.model = model
    def forward(self, x):
         return self.model(x)



model1 = net1()

w_model1 = wrapper(mode1)


model2 = net2()

#when I include this line, w_model1 does not converge.
w_model2 = wrapper(model2)

## To Reproduce

Steps to reproduce the behavior:

1.
1.
1.

<!-- 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):
 - OS (e.g., Linux): Linux
 - How you installed PyTorch (`conda`, `pip`, source): pip
 - Build command you used (if compiling from source):
 - Python version: 3.7
 - CUDA/cuDNN version:
 - GPU models and configuration:
 - Any other relevant information:

## Additional context

<!-- Add any other context about the problem here. -->
Repository: godot
Issue: Creating new image for ImageTexture logs errors to console
Labels: bug,topic:editor,confirmed

**Godot version:**
 v3.2.2.rc.custom_build.36a30f681

**OS/device including version:**
Windows 10

**Issue description:**
It is not possible to create new image for ImageTexutre in editor. Errors are logged in console:

` drivers\gles3\rasterizer_storage_gles3.cpp:1097 - Condition "texture->data_size == 0 && !texture->render_target" is true. Returned: Ref<Image>()`
` drivers\gles3\rasterizer_storage_gles3.cpp:832 - Condition "!read.ptr()" is true.`

Also trying to load image shows warning 
![image](https://user-images.githubusercontent.com/11059246/79985948-9c9c8980-84ab-11ea-99db-bb23ca25ef64.png)

**Steps to reproduce:**
- Add Sprite node
- Select Sprite
- In Inspector for Sprite pick ImageTexture for Texture property
- Click on ImageTexture to expand it
- Click on [Empty] for Image property
- Click New Image
Repository: godot
Issue: Light Bleeding - Irregulrities in OmniLight/Shadow Atlas
Labels: bug,topic:rendering,topic:3d

**Godot version:**
v3.2.2.beta.custom_build.c7ad8f539

**OS/device including version:**
Linux (GeForce 940M)

**Issue description:**
Light bleeding depending on OmniLight rotation; independent of object position and rotation. It looks like there some kind of irregularities in the *OmniLight sphere*, especially at multiples of 90°:
[video_irregularities_omnilight.zip](https://github.com/godotengine/godot/files/4516164/video_irregularities_omnilight.zip)
In the video I only rotate the green sphere but the light bleeding position on the cube stays there, even if I translate/move the big green sphere.

This effect is not fixable by changing the bias or (indirect)energy of the light.

**Steps to reproduce:**
1. Open the minimal Project: No light bleeding should occur on the cube
2. Set "Project Settings ... -> Rendering -> Quality -> Shadow Atlas -> Size" to 8192: Light bleeding should now occur
3. Reset shadow atlas size to default: Light bleeding still occurs
 ![image](https://user-images.githubusercontent.com/18660100/79984290-3f9fd400-84a9-11ea-964e-0be481da8c03.png)

Every object in the scene is only moved on the world x axis; object translation for y = 0 and z = 0.
Used project settings in the video (for better visibility):
![video_settings](https://user-images.githubusercontent.com/18660100/79984118-00718300-84a9-11ea-8c53-24a0960eb4fd.png)

With the default settings the issue seems to be very subtle. I use this kind of setup in one of my prototypes and the issue seems to occur just with different "intensities" (I was looking for the reason why objects behind my planet are still visible)

**Minimal reproduction project:**
[omnilight_project.zip](https://github.com/godotengine/godot/files/4516419/omnilight_project.zip)
Repository: rust
Issue: mailgun can stop delivering silently
Labels: P-low,T-infra

Recently, it has come up that mailgun will suppress sending to a particular email if we bounce (too many times? unclear). We currently have no tracking, and the nature of our mailing lists means that such suppressions are really hard to notice for subscribers.

Infra wants to setup some monitoring so that we get an email or notification through our existing alerting system that this has happened.
Repository: angular
Issue: Structural directive using selector with format "element[attribute]"
Labels: hotlist: error messages,area: core,core: directive matching,type: confusing,P4

<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅

Oh hi there! 😄

To expedite issue processing please search open and closed issues before submitting a new one.
Existing issues often contain information about workarounds, resolution, or progress updates.

🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->


# 🐞 bug report

### Affected Package
<!-- Can you pin-point one or more @angular/* packages as the source of the bug? -->
<!-- ✍️edit: --> The issue is related to package @angular/core and @angular/compiler, or if the behavior is by design, then it's a "documentation bug", since this directive selector usage is not said to not work when using directives with the "sugared" asterisk syntax.


### Is this a regression?

<!-- Did this behavior use to work in the previous version? -->
<!-- ✍️--> Not sure


### Description

<!-- ✍️--> When one try to create a structural directive using a selector with format "element[attribute]", Angular does not recognize the directive as valid for the element.


## 🔬 Minimal Reproduction
<!--
Please create and share minimal reproduction of the issue starting with this template: https://stackblitz.com/fork/angular-issue-repro2
-->
<!-- ✍️--> https://angular.io/generated/live-examples/structural-directives/stackblitz.html
Change the selector of directive appUnless to "p[appUnless]"

<!--
If StackBlitz is not suitable for reproduction of your issue, please create a minimal GitHub repository with the reproduction of the issue.
A good way to make a minimal reproduction is to create a new app via `ng new repro-app` and add the minimum possible code to show the problem. 
Share the link to the repo below along with step-by-step instructions to reproduce the problem, as well as expected and actual behavior.

Issues that don't have enough info and can't be reproduced will be closed.

You can read more about issue submission guidelines here: https://github.com/angular/angular/blob/master/CONTRIBUTING.md#-submitting-an-issue
-->

## 🔥 Exception or Error
<pre><code>Error in /turbo_modules/@angular/compiler@9.0.7/bundles/compiler.umd.js (2724:21)
Template parse errors:
Can't bind to 'appUnless' since it isn't a known property of 'p'.
</code></pre>


## 🌍  Your Environment

(see stackblitz)
Repository: excalidraw
Issue: Intermediate slider changes shouldn't persist in the undo stack
Labels: bug,history

1. Select something
2. Change opacity by a slider
3. Undo

Expected: it jumps to the previous "final" value
Actual: it barely changes because each intermediate slider movement is a part of undo stack