sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Current implementation of c10::complex does not support being used in shared memory
Labels: triaged,module: complex

Open an issue here in case this task is forgotten.

We are unable to declare a `c10::complex` array for shared memory in a CUDA kernel. The initialization of `c10::complex` needs to be changed to fix it.

Note:
```C++
struct A {
    int a = 0;
    A() = default;
};
__global__ void f(A *p) {
    __shared__ A s[5];  // error: error: initializer not allowed for __shared__ variable 
    s[0] = *p;
}
```
and
```C++
struct A {
    int a;
    A(): a(0){};
};
__global__ void f(A *p) {
    __shared__ A s[5];  // this works!
    s[0] = *p;
}
```

See discussion here: https://github.com/pytorch/pytorch/pull/39063#discussion_r431928098


cc @ezyang @anjali411 @dylanbespalko
Repository: TypeScript
Issue: Intellisense concatenates field description from subtypes
Labels: Bug,Domain: Quick Info

<!-- 🚨 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:**  3.9.2.

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** intellisense concat concatenation 

**Code**

```ts
import React from 'react';

type Base<T> = {
    /**
     * Original description
     */
    b: T;
}
type BaseClone<T> = {
    /**
     * Clone description
     */
    b: T;
}

type Combined = Base<boolean> & BaseClone<boolean>;

const Component: React.FC<Combined> = (props: Combined) => <div></div>;

<Component b />;
```

![image](https://user-images.githubusercontent.com/829827/83302903-fbdb7100-a1b0-11ea-828a-6aadc1357ba0.png)


**Expected behavior:** Not sure, to be honest.

**Actual behavior:** Intellisense for `b` on `Component` is the concatenation of the two types: `Original description Clone description`.

**Playground Link:** [Playground](https://www.typescriptlang.org/play/?jsx=1&ssl=1&ssc=1&pln=22&pc=17#code/JYWwDg9gTgLgBAJQKYEMDG8BmUIjgcilQ3wG4AocmATzCTgCEUBnJAHgBUA+OAXjgDe5OCLgB6AFQThouBLgB5KMADmwAHYoANnAAmSZmmVgYwCOpmiJYy3ABGALjgcKAXyq16TVgGEt59m4+QVtJaVk5OD8AvQMjYBMzCwjrW0dnN0oaOijcOw0kXWDvdjsICC1UdR4AMkYWJGj1UvLKlGqKcjRzZngfXEhm9RgnZHQYADoAMR82fpB85t0efgAKMBwwZid5xcKASj4eNl1gADcuNjFTi87KOYGA4ftxLlIgA)

This doesn't seem like a huge bug, but I just wanted to flag it in case there's behavior that makes more sense here.
Repository: TypeScript
Issue: Intellisense does not appear in JSX attributes for union types
Labels: Bug,Domain: Quick Info

<!--
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:**  Nightly

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** intellisense jsx union

**Code**

```ts
import React from 'react';

type Exclusive = {
    /**
     * Original description
     */
    a: boolean;
    b?: never;
} | {
    /**
     * Never description
     */
    a?: never;
    b: boolean;
}

const Component: React.FC<Exclusive> = () => <div></div>;
Component({
    a: true
});
<Component a />;
```

**Expected behavior:** The field description for `a` shows up in intellisense.

**Actual behavior:** It does not.

Object literal at a normal function call looks good:

![image](https://user-images.githubusercontent.com/829827/83304006-ea936400-a1b2-11ea-91a2-6e9d4d9c1e7e.png)

However, the description does not show up for JSX:

![image](https://user-images.githubusercontent.com/829827/83304046-f97a1680-a1b2-11ea-92f7-d4fb8f72354b.png)

When writing using autocomplete to enter a new field:

![image](https://user-images.githubusercontent.com/829827/83304078-0991f600-a1b3-11ea-818a-73557427b8ca.png)

![image](https://user-images.githubusercontent.com/829827/83304087-131b5e00-a1b3-11ea-8b46-07432a634c22.png)

Interestingly, JSX works in this case.

**Playground Link:** [link](https://www.typescriptlang.org/play/?jsx=1&ts=4.0.0-dev.20200528#code/JYWwDg9gTgLgBAJQKYEMDG8BmUIjgcilQ3wG4AocmATzCTgFEAPNAGwFcBnYAN3oF44Ab3JwxcAPQAqKaPFwpcAPJRgAc2AA7FKzgATJJzSqwMYBE1zxUiVbgoAXHABGECK1SaK85wH4nmkh8UBQAvnAAPsJ20rLyCnAAckFIUPqGxsCm5pbxNnYo-nCBwd7izk6u7p5hlGgWnPAAwriQgZowTsjoMAB0AGJNADzMbFy8SAB8cIIAFGA4YJxOoxzcfACUM9NDeryTQxJ7PJMUlC3gFkgdsyLyjnAwUOxI5KEbFEMXbdfwKJKnIA)

**Related Issues:** 
* https://github.com/microsoft/TypeScript/issues/27211
* https://github.com/microsoft/TypeScript/issues/38848
Repository: electron
Issue: Standardize About window across platforms
Labels: enhancement :sparkles:,platform/windows

<!--  As an open source project with a dedicated but small maintainer team, it can sometimes take a long time for issues to be addressed so please be patient and we will get back to you as soon as we can.
-->

### Preflight Checklist
<!-- Please ensure you've completed the following steps by replacing [ ] with [x]-->

* [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 for a feature request that matches the one I want to file, without success.

### Problem Description

There is different default behaviour for About window across platforms: macOS, Windows, Linux.

### Proposed Solution

Similar default behaviour of About window without setting `app.setAboutPanelOptions`.

```
app.showAboutPanel();
```

* Open about window by click on menu item with role `about`:
  * ✅ macOS: default behaviour
  * ❌ Windows: pending https://github.com/electron/electron/issues/23681
  * ❌ Linux: pending: https://github.com/electron/electron/issues/23681
* Call app.showAboutPanel without setting `app.setAboutPanelOptions`:
  * ✅ macOS: works as expected
  * ❌ Windows: opens windows without icon
  * ❌ Linux: does nothing https://github.com/electron/electron/issues/23847
* `applicationName` of `setAboutPanelOptions`:
  * ✅ macOS: `productName`
  * ✅ Windows: `productName`
  * ❌ Linux: `name`
* `applicationVersion` of `setAboutPanelOptions`:
  * ✅ macOS: `version`
  * ✅ Windows: `version`
  * ❌ Linux: nothing
* `iconPath` of `setAboutPanelOptions`:
  * ❌ Windows: icon format and image size should be documented https://github.com/electron/electron/issues/23833
  * ❌ Linux: icon format and image size should be documented.

### Additional Information

Related issues:

* https://github.com/electron/electron/issues/18918
* https://github.com/electron/electron/issues/23847
* https://github.com/electron/electron/issues/23833
* https://github.com/electron/electron/issues/22456
Repository: youtube-dl
Issue: request option '--playlist-elapsed-max'
Labels: request

## Checklist

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2020.05.29**
- [x] I've searched the bugtracker for similar feature requests including closed ones

## Description

Requesting a new command line switch which specifies the ***maximum elapsed time*** allowed for downloading, ***per channel or playlist***. Any item that starts downloading before the time expires is allowed to complete, even if doing so exceeds the allocated time. This entails that a minimum of 1 video per channel/playlist will always be downloaded.

## Details

The proposed option sets a limit on the maximum elapsed time allowed, per channel or playlist, for downloading.

- A new timer starts for each playlist (or channel) when its first item begins downloading.
- Any video that starts downloading is allowed to complete.
- Before downloading each/any additional item(s) in the playlist, the timer is checked. If the allocated time has been exceeded, then download of this playlist is discontinued, and possibly continues by proceeding to the next playlist (if any).
- A suggested name and usage for the command line option could specify the desired time in seconds, such as, _i.e._, to allow a total of 3 minutes of downloading per channel or playlist:

      --playlist-elapsed-max 180
Repository: flutter
Issue: Android PlatformView created from View of an existing Fragment does not work correctly
Labels: c: new feature,platform-android,engine,a: platform-views,e: OS-version specific,P3,team-android,triaged-android

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill our the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

Android PlatformView created from View of an existing Fragment does not work correctly

## Steps to Reproduce

<!-- You must include full steps to reproduce so that we can reproduce the problem. -->

1. Running the following app:
https://github.com/PDFTron/pdftron-flutter/tree/platform-widget4/example


**Expected results:** <!-- what did you want to see? -->
Works as if running in Android native

**Actual results:** <!-- what did you see? -->
1. In the app, the overflow popup in the toolbar menu does not open, seems like any popup window cannot be opened
2. All text became white and background specified as ?android:attr/colorBackground in the original Android package became black, changing the activity theme does not help
3. None of the text input field works

![image](https://user-images.githubusercontent.com/20527369/83305623-f7fe1d80-a1b5-11ea-802a-bedc13602756.png)




<!--
      Run your application with `flutter run --verbose` and attach all the
      log output below between the lines with the backticks. If there is an
      exception, please see if the error message includes enough information
      to explain how to solve the issue.
-->

```
```

<!--
     Run `flutter analyze` and attach any output of that command below.
     If there are any analysis errors, try resolving them before filing this issue.
-->

```
```

<!-- Finally, paste the output of running `flutter doctor -v` here. -->

```
```
Repository: flutter
Issue: [l10n] Localization class is not generated when used in a package
Labels: tool,a: internationalization,c: proposal,P3,team-tool,triaged-tool

## Steps to Reproduce
When using l10n in a project with app(s) and multiple packages, it seems that it only works (generates the localization class) if the template arb and `l10n.yaml` are located in the app. 

Our project has the following structure:
```
apps/
  |
  --- app1
  --- app2
packages
  |
  --- package1
  --- package2
  --- package3
```
Some of these packages are actually features that can be used by any of the apps and hence, have their own set of localizations. As an experiment I tried running app1 and placed the arb template and `l10n.yaml` in package2, but nothing was generated, nor did I get any exception.

In the same project, if I move the files mentioned above to app1, and run it, then the localization class is generated.

It would be great if this use case is supported since there many people using similar approach (mono repo projects).

<details>
  <summary>Logs</summary>
```
% flutter doctor -v
[✓] Flutter (Channel master, 1.19.0-2.0.pre.197, on Mac OS X 10.15.4 19E287, locale en-NL)
    • Flutter version 1.19.0-2.0.pre.197 at /Users/user/IdeaProjects/hue_blue/dev/flutter
    • Framework revision d9144bf8fc (2 hours ago), 2020-05-29 11:55:02 -0700
    • Engine revision c19459ab7d
    • Dart version 2.9.0 (build 2.9.0-11.0.dev 6489a0c68d)

 
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0-rc3)
    • Android SDK at /Users/user/Library/Android/sdk/
    • Platform android-R, build-tools 29.0.0-rc3
    • ANDROID_HOME = /Users/user/Library/Android/sdk/
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.5)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.5, Build version 11E608c
    • CocoaPods version 1.8.4

[✓] Android Studio (version 3.5)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 38.2.3
    • Dart plugin version 191.8423
    • Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)

[✓] IntelliJ IDEA Community Edition (version 2020.1)
    • IntelliJ at /Applications/IntelliJ IDEA CE.app
    • Flutter plugin version 45.1.3
    • Dart plugin version 201.7223.43

[✓] Connected device (1 available)
    • macOS • macOS • darwin-x64 • Mac OS X 10.15.4 19E287

• No issues found!
```

</details>
Repository: PowerToys
Issue: Blur background while alt+tabbing
Labels: Idea-New PowerToy

Just that
Repository: flutter
Issue: Switching from master -> stable with startup lock, shlock: unlink(flutter/bin/cache/.upgrade_lock): Operation not permitted
Labels: tool,P2,team-tool,triaged-tool

On `master` [d9144bf] 
```
$ flutter doctor
Waiting for another flutter command to release the startup lock...
```
Because the `flutter/bin/cache/.upgrade_lock` directory exists.

When I check out `stable` [5f21edf8b ] and run `flutter doctor` I get:
```
$ flutter doctor       
shlock: unlink(/Users/magder/Projects/flutter/bin/cache/.upgrade_lock): Operation not permitted
shlock: unlink(/Users/magder/Projects/flutter/bin/cache/.upgrade_lock): Operation not permitted
```
forever spew.
Repository: node
Issue: OutgoingMessage should set writable false
Labels: http,stream

In #33131 we aligned `OutgoingMessage` to properly set the `destroyed` property. We should do the same for `writable` in order to properly align with streams.
Repository: pytorch
Issue: Differentiable Optimizers
Labels: feature,module: nn,module: optimizer,triaged

## 🚀 Feature

Let's design below what an API for differential optimizers would look like. The goal is to facilitate the implementation of differential optimizer for libraries such as [higher](https://github.com/facebookresearch/higher/) (e.g. [section 4](https://arxiv.org/pdf/1910.01727.pdf))

Related discussions in #12659 and #32005, and [Internal document](https://fb.quip.com/7fsdAavbPGJ0)

cc @albanD @mruberry @vincentqb @egrefen
Repository: pytorch
Issue: Let future.wait() take in an optional timeout
Labels: triaged,enhancement,module: rpc

## 🚀 Feature
When debugging RPC-related messages under faulty scenarions, we can sometimes end up calling `future->wait()` on a future that will never be set, resulting in hard to debug issues. Allowing `wait()` to take in an optional timeout and use that in the condvar wait could be useful to ease the debugging in this situation.

## Motivation

I came across this in a call to `OwnerRRef::localValue()`, where we do a wait on the future corresponding to the RRef's value. In this case, when an `rpc.remote()` is sent to self and dropped by the network, we would wait forever on this future. 

## Pitch

An optional timeout parameter that we can pass into `future.wait()`, and we change the `finished_cv.wait()` to `finished_cv.wait_for` or `wait_until`.

cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @rohan-varma @xush6528 @jjlilley @osalpekar
Repository: PowerToys
Issue: Option to Automatically Resize File Explorer Preview Relative to Window Size
Labels: Idea-New PowerToy


With my file explorer window maximized, I like to have a larger preview pane size so I can see more of my selected file's content. There is plenty of "extra space" not occupied by my folder content details, so I typically increase the preview pane size to see more my selected file's content. However, if I shrink the window size, so I'm no longer maximized, the preview pane will remain the same pixel size, which ends up covering a lot of the content details, forcing me to manually resize the pane to correct this. 

My suggestion is to automatically resize the preview pane relative to the window size. It could be a feature that users enable/disable in settings. 

Users with higher display resolutions will probably appreciate this feature the most (which is most of us these days)...
Repository: pytorch
Issue: Caffe 2 android app not working with proguard and minifyEnabled
Labels: caffe2

## 🐛 Bug

I used this app 
https://github.com/bwasti/AICamera

It ran fine when i used it without using proguard and minifyEnabled true 



        debug {
            minifyEnabled true
            proguardFiles getDefaultProguardFile('proguard-android-optimize.txt'), 'proguard-rules.pro'
        }
 



After doing this it started crashing.


Edit 1:

I also noticed that the app is crashing when i changed the Build Variant from GUI it started crashing.
But when I enabled proguard directly using build.gradle file without touching build variant gui it was working fine.

![](https://i.ibb.co/sJfWcmv/Screenshot-84.png)


![](https://i.ibb.co/gRbjBGj/Screenshot-86.png)
Repository: godot
Issue: Animation_begin emitter not working as expected
Labels: discussion,topic:core,documentation

<!-- 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.1 stable

**OS/device including version:**
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Windows10

**Issue description:**
<!-- What happened, and what was expected. -->
I am trying to use Animation player to go from 2 - 2.5 then -.5 to 0 using animation player and it keeps inserting a frame where it has a value of .5. 

I could forgive the behavior of this if I was changing the value when the animation_finished signal emitted out of my "begin" animation (which I tried there is an alternate script you can attach to the tracker object using this method) but I am changing it at the beginning of the "end" animation. This behavior is not what I want and I don't know how to get my desired effect. 

**Steps to reproduce:**
just hit play. You'll see it appear at .5 and you'll be able to read it on the print out as well.

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
[wrap problem.zip](https://github.com/godotengine/godot/files/4705192/wrap.problem.zip)
Repository: flutter
Issue: Warn about a non existing Class in AndroidManifest.xml application element
Labels: platform-android,tool,a: quality,P2,team-android,triaged-android

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill our the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Steps to Reproduce

If you set up a Class name that does not exists in the android:name attribute of the application element, flutter Apps builds successfull, but they just deliver a white screen for part of a second and crashes.

<!-- You must include full steps to reproduce so that we can reproduce the problem. -->


Change the application element of AndroidManifest.xml like this:

![image](https://user-images.githubusercontent.com/2205193/83321649-647a2a80-a251-11ea-95fd-3be42c6b5d84.png)

flutter run -v

**Expected results:** <!-- what did you want to see? -->

A warning or error message in the log output.

**Actual results:** <!-- what did you see? -->

Output stops at

`[   +1 ms] Waiting for observatory port to be available...`

## Background Facts

Some member of our Project Team changed this by mistake following some guide. The App didn't crashed while using Hot Reload, he finished his feature, created a PR and moved on creating a new feature while creating a new feature branch based on our master.

We missed this change while reviewing his PR and merged a few finished features together. Afterwards we spend hours of debugging to find this issue.

As far as i understood there are legal cases where someone changes this value, but if the Class mentioned there is not found, flutter should drop at least a warning.

I described this behaviour in #57966, where i am sure that OP suffers from the same error.

We are some kind of new to flutter, but we really love the environment. If someone heads me into the right direction and gives me some hints, i would love to give it a try and implement a warning.

If i can provide any more informations, just ping me and i will deliver
Repository: rust
Issue: Refactor improper_ctypes to separate "UCG questions" from linting decisions
Labels: C-enhancement,A-lints,A-FFI,T-compiler,L-improper_ctypes

(Elaborating on https://github.com/rust-lang/rust/issues/66220#issuecomment-557537105)

I think that the current state of `improper_ctypes` is difficult to maintain and extend -- especially once we add [more lints that are similar but distinct](https://github.com/rust-lang/rust/pull/72700) -- because it's a big pile of mud that interleaving several different concerns: UCG-ish questions about ABI and layout guarantees, plus value judgements about how these interact with "proper" FFI, plus diagnostics code and suggestions. I imagine (but have not worked out the details) that we could improve this by separating this code into two "layers":

- A module (some queries?) answering clean-cut spec questions such as: does this type have a defined memory layout? Defined ABI? If not, why not? etc.
- Several lints that use the facts from that module as basis for emitting warnings, depending on what the lint is targeted at.

I think such an organization would make it clearer what are the language-level guarantees are (including making it easier to audit and evolve) vs what's just a choice or limitation of some lint. More importantly, it would also enable us to implement (without lots of duplication and without making the visitor even more of a big ball of mud) a broader variety of lints that need similar information. For example:

- linting transmutes of types with unspecified layout (#51294, https://github.com/rust-lang/rust/issues/50842)
- separate lints for "ABI is FFI-safe" vs "C code could actually work with this type" independent of `extern` *imports* vs *definitions*
- lints for type punning via unions ~~(the `const` alternative to `transmute`)~~
- a more opinionated version of `improper_ctypes` that e.g. prohibits references (due to their aliasing implications which are rarely appropriate in FFI)