sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: Content projection with `select` can be confusing
Labels: area: core,core: content projection,type: confusing,P3

### Description

Content projection with the `select` attribute can be confusing for users. `select` only works on root-level elements, but sometimes users will wrap an element in `<ng-container *ngIf="...">`, not realizing that the `ng-container` is unnecessary. In their mind this is just some control flow logic but the root-level element is still the thing inside the `<ng-container>`. However, Angular actually considers `<ng-container>` to be the root element and projects the element into an unexpected slot. We see this come up in issues on the Angular Components repo sometimes, since we have several components that project content into different slots.


## 🔬 Minimal Reproduction

https://stackblitz.com/edit/angular-ivy-grarvn?file=src%2Fapp%2Fapp.module.ts
Repository: electron
Issue: Add whenReady API to BrowserWindows to await their set up/rendering
Labels: enhancement :sparkles:,component/BrowserWindow

### Preflight Checklist
* [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
* [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
* [x] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

### Problem Description
I have some code that creates a window (via `window.open`) and then immediately tells the main process to print it. The problem is that the window hasn't finished loading yet / rendering, so it prints a blank page.

I don't really want to have to add a did-finish-load or ready-to-show event for all these windows that I create.

### Proposed Solution
Can we add an API for BrowserWindows (or webcontents?) that returns a promise that resolves once the window has finished loading and renderering? And then we can do:

const win = BrowserWindow.fromId(1);
await win.whenReady();
win.webContents.print(...);

(I guess we'd have to define what exactly `whenReady` means. Maybe use the broad definition of everything has finished loading and rendering)
Repository: pytorch
Issue: Add support for rsample to MixtureSameFamily Distribution
Labels: module: distributions,triaged,enhancement

## 🚀 Feature

It would be great if MixtureSameFamily had the rsample() functionality so as to make the parameters of the MixturesameFamily distribution trainable. 

## Motivation

rsample() is a valuable tool for making the parameters defining distributions trainable. Mixture Models have recently been added to the set of distributions pytorch provides, but the reparameterization trick cannot be applied to them, for, say, a mixture of gaussians.

## Pitch

It would be great if this could be implemented! Not much of a pitch to sell here, but just think having such functionality if possible would be a great addition to what MixtureSameFamily can offer. 

## Alternatives

<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->

One could feasibly do this manually by hardcoding the mixture distribution, but I think that defeats the purpose of having the MixtureSameFamily option

## Additional context

Thanks for your help! Totally understand if for some  reason this isn't implementable or low on priority list.


cc @vincentqb @fritzo @neerajprad @alicanb @vishwakftw
Repository: TypeScript
Issue: Incorrect Indenting Behavior in VS
Labels: Visual Studio,Needs Investigation,Domain: Smart Indentation

***Ported from https://github.com/dotnet/roslyn/issues/44607 by @DanielRosenwasser***

_This issue has been moved from [a ticket on Developer Community](https://developercommunity.visualstudio.com/content/problem/1050808/wrong-indenting-2.html)._

---
<p>Found this problem was reported before, appears to have been reported as fixed.  But it is happening again…   The title info for the original report is:</p>
<p>TITLE:  Wrong indenting<br>
DATE:  Olaf van der Spek reported 12/7/2018, 12:54:20 PM</p>
<p>Problems is effectively the same.   Running VS 2019 v16.6.0.  When you select the editor’s  setting for “Indenting” which can be one of  [NONE|BLOCK|SMART], selecting ‘BLOCK’  the cursor, most of the time, upon present ENTER goes to column 1 on the next line.   Appears “INDENTING is behaving as “NONE” is selected.<br>
Not sure when started, bouncing between VS 2017 and 2019, never have seen the problem in 2017, can’t say it ever worked in 2019 for that matter.</p>

---
### Original Comments

#### Visual Studio Feedback System on 5/27/2020, 03:16 AM: 

<p>We have directed your feedback to the appropriate engineering team for further evaluation. The team will review the feedback and notify you about the next steps.</p>


---
### Original Solutions
(no solutions)
Repository: material-ui
Issue: [Tabs] Keyboard navigation does not work with disabled tabs
Labels: accessibility,component: tabs

- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Current behavior
Tabs keyboard navigation does not behave correctly when there are disabled tab items


## Expected Behavior 🤔
Keyboard navigation should either allow the selected tabs to be focusable but not selectable or skip them. According to W3C accessibility standards, they should be focusable but not selectable. 

## Steps to Reproduce 🕹
https://codesandbox.io/s/material-demo-v5ddi?file=/demo.js

Steps:

1. Try to use the keyboard to navigate through the tabs after focusing it

| Tech        | Version |
| ----------- | ------- |
| Material-UI | v4.10.0  |
Repository: TypeScript
Issue: Change default inference from arrays to tuples and primitives to literals
Labels: Suggestion,Awaiting More Feedback

I am working on functional project now and I'm getting a lot of errors related to too wide type inference for values. It looks like

```typescript
function test(a: { data: 1 | 2 }) { return a }
const a = { data: 2 }
// Types of property 'data' are incompatible.
// Type 'number' is not assignable to type '2'.ts(2345)
const b = test(a)
```

There're really many errors like this, and the main problem is that you can convert type A to type B, but not vice versa.

```typescript
type A = { data: 2 }
type B = { data: number }
```
So, I ask you to add a new compiler option (to not break existing code) that will make type checker infer types as narrow as possible. It will be very helpful for functional programming.
Repository: storybook
Issue: Controls: boolean control throws a red warning
Labels: bug,addon: controls

**Describe the bug**

Playing with `"@storybook/addon-controls": "6.0.0-beta.17"` I got this warning after clicking a boolean control, which is the `inverseColors` input (at the beggining of the screenshot):

![image](https://user-images.githubusercontent.com/260185/83174657-4f31be80-a0e0-11ea-9839-239a7faab0af.png)

Upcoming clicks in the checkbox doesn't throw this,
as it seems that the checkbox is already changed to controlled.

**System:**

```
Environment Info:

  System:
    OS: Linux 5.4 Ubuntu 20.04 LTS (Focal Fossa)
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 10.18.0 - ~/.nvm/versions/node/v10.18.0/bin/node
    Yarn: 1.22.4 - /usr/bin/yarn
    npm: 6.14.2 - ~/.nvm/versions/node/v10.18.0/bin/npm
  Browsers:
    Chrome: 83.0.4103.61
    Firefox: 76.0.1
  npmPackages:
    @storybook/addon-a11y: 6.0.0-beta.17 => 6.0.0-beta.17 
    @storybook/addon-actions: 6.0.0-beta.17 => 6.0.0-beta.17 
    @storybook/addon-controls: 6.0.0-beta.17 => 6.0.0-beta.17 
    @storybook/addon-docs: 6.0.0-beta.17 => 6.0.0-beta.17 
    @storybook/addon-links: 6.0.0-beta.17 => 6.0.0-beta.17 
    @storybook/addon-viewport: 6.0.0-beta.17 => 6.0.0-beta.17 
    @storybook/addons: 6.0.0-beta.17 => 6.0.0-beta.17 
    @storybook/angular: 6.0.0-beta.17 => 6.0.0-beta.17 
    @storybook/cli: 6.0.0-beta.17 => 6.0.0-beta.17 
    @storybook/source-loader: 6.0.0-beta.17 => 6.0.0-beta.17
```
Repository: flutter
Issue: [gen_l10n] Newly written arb files not detected during hot reload/restart or rebuild
Labels: tool,a: internationalization,P3,team-tool,triaged-tool

If an arb file with a name that includes a locale suffix, but no `@@locale` value, is added to a project then the corresponding class isn't generated and, if the app tries to retrieve strings from that locale, it fails ugly with an NPE.

For example, if app_es.arb is added:

```json
{
   "helloWorld": "Hola Mundo!"
}
```

If the current locale is 'es' then `AppLocalizations.of(context).helloWorld` fails:
```dart
flutter: The following NoSuchMethodError was thrown building HelloWorld(dirty, dependencies:
flutter: [_LocalizationsScope-[GlobalKey#fb104]]):
flutter: The getter 'helloWorld' was called on null.
flutter: Receiver: null
flutter: Tried calling: helloWorld
```

This is because lib/l10n/app_localizations_es.dart wasn't generated.  If the `@@locale` is included, then all is well:
```json
{
  "@@locale": "es",

   "helloWorld": "Hola Mundo!"
}
```

Originally, the `@@locale` entry was optional, since the locale could be inferred from the filename.

In cases where the requested locale really isn't present, we should fail more gracefully.

To set up this test case:
- Create a new Flutter project.
- Add a flutter_localizations section to the pubspec.yaml file's dependencies, or just use this [sample pubspec.yaml](https://gist.github.com/HansMuller/57667a3ddbb0f9633977a7b170f310bf).
- Add [this l10n.yaml](https://gist.github.com/HansMuller/83dde034cfdacf9622e35642e42d9ec6) file to the top level of your project.
- Add a lib/l10n directory to the project.
- Add [this template ARB](https://gist.github.com/HansMuller/561ec39803d4f32965278779515907d4) file to lib/l10n.
- Replace lib/main.dart with [this l10n demo](https://gist.github.com/HansMuller/57c569cf99997a6530eb05f64906042f).
Repository: flutter
Issue: Add mouse cursor support to the remaining widgets
Labels: c: new feature,framework,f: material design,f: cupertino,a: mouse,team-design,triaged-design

While https://github.com/flutter/flutter/pull/57628 added mouse cursor support to a number of material widgets, there are other widgets remaining to support.

- Material:
  - Card (probably)
  - Tooltip
  - NavigationRail
  - ReorderableList
  - Stepper
  - TimePicker
  - Chip
  - DataTable
  - Hyperlinks (not a widget; actually `InlineSpan` with tap gesture recognizers)
- Cupertino widgets (we might not do this until we start to support iPadOS cursors)

Please comment if widgets not mentioned here should also support mouse cursors.
Repository: TypeScript
Issue: Code generated for optional call could be optimized when the result is unused
Labels: Suggestion,Help Wanted,Effort: Moderate,Experience Enhancement

The generated code for optional chaining is a little verbose when the "return" value of the expression is not being used.  For example, when simply calling a function:

```typescript
maybe.close?.()
```

Here is a more [complete example](https://www.typescriptlang.org/play/#code/C4TwDgpgBAsghiARhAwgGwPYGc6LdAXigG8BYAKCigGNMsIB+ALigAoBKKAgPhIF8A3BUEUKAEwi04AJ2jUMAOyzAoAWwTIW8JKjq58Q8gHojAeQXQMYYAEtFcNBXU6AdLWyMXHUeVCQoAAoQ0gAWcGBY2shcJBRUzsjMsBq62PoQhnzikmgycorKUJCh4VgsQSURURkUJgAqAO4YUFa29mhYFMVhES4Jnu70DF7sAkA).

The second example generates:

```typescript
(_c = (_b = perhaps.maybe) === null || _b === void 0 ? void 0 : _b.close) === null || _c === void 0 ? void 0 : _c.call(_b);
```

But could be optimized to:
```typescript
(_b = perhaps.maybe) !== null && _b !== void 0 && (_c = _b.close) !== null && _c !== void 0 && _c.call(_b);
```

It's not a huge difference, but it saves 8 characters for each link in the chain.

While the spec says something like: "_the expression short-circuits with a return value of undefined_", when the return value is meaningless, then only the "short-circuit" part is important.
Repository: PowerToys
Issue: [Run] Ability to pin first result for query
Labels: Idea-Enhancement,Product-PowerToys Run,Area-User Interface

# Summary of the new feature/enhancement
Wox has the ability to set a first result for a specific query to improve the search results.
E.g. when often using visual studio, typing "vis" brings up VS Code first and then VS. I want to have VS as a first result ( 

# Proposed technical implementation details (optional)
Wox has this, as I see an attribution in the Settings I imagine there is already some sort of cooperation, so might be worth taking a deeper look!
Repository: TypeScript
Issue: Ensure find-all-refs works on unresolved locals
Labels: Suggestion,In Discussion,Experimentation Needed,Domain: Symbol Navigation,Rescheduled

Spoke with @amcasey about this one.

Given the following

```ts
blah.yadda.yadda
```

`blah` will be an unresolved and should be an error, but we still want find-all-references on this symbol to work reasonably well. This is especially important in the mode described in #37713, where TypeScript won't have access to symbols in the global scope.

This can potentially be achieved by creating an "error scope" whose symbol table contents are progressively populated every time resolution fails.
Repository: godot
Issue: Tree control contents draw over border
Labels: bug,topic:gui

**Godot version:**
v3.2.1 stable

**OS/device including version:**
Fedora 32 (64 bit), RX 5700 XT using Navi10 driver, GLES3.

**Issue description:**
The contents of Tree controls draw over any border. This can be seen in the editor.

![Screenshot from 2020-05-28 15-44-41](https://user-images.githubusercontent.com/16503728/83201867-51554680-a0fb-11ea-9935-e765a02d7e9b.png)
Repository: godot
Issue: Custom resources cannot be created in FileSystem or Inspector docks in 4.0
Labels: bug,topic:editor,topic:plugin

**Godot version:**
4.0

**OS/device including version:**
Windows 10

**Issue description:**
<!-- What happened, and what was expected. -->
While working on #34828, I tried to set a resource property in the inspector to a new custom resource. The property menu closed, but the property remained unchanged. The console printed 2 errors:
```
 Cannot get class 'CustomResource'.
 editor\editor_properties.cpp:2496 - Condition "!resp" is true. Breaking.
```
I tried to make the custom resource again by right clicking in the FileSystem dock and selecting "New Resource." I selected my custom resource and clicked create, but the "Create New Resource" window closed without creating the resource. This error was printed:
```
 editor\filesystem_dock.cpp:1801 - Condition "!r" is true.
```
**Steps to reproduce:**

1. Add a custom resource via a EditorPlugin
2. Try to set a resource property in the inspector to an instance of your custom resource. You could try to do this via the Inspector or via the FileSystem. You will find that either method will result in an error.

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
[ResourceTest.zip](https://github.com/godotengine/godot/files/4698689/ResourceTest.zip)
Repository: create-react-app
Issue: Read xml files and other data
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

I don't understand why we still have to face "you may need an appropriate loader to handle this file type" kind of error. I'm trying to load an xml file from my assets, which doesn't sound like something completely crazy in a web environment, and I get this message.

I would just expect webpack to be configured to load the unknown files extensions as raw text, or at least common web extensions like xml, xhtml, and such.

### Describe the solution you'd like

I think that we could just update the webpack configuration to load xml as raw text. This way at least we would be able to parse it.

### Describe alternatives you've considered

The only alternative I know of right now would be to eject, which is not much of an alternative...
Repository: electron
Issue: Expose user preference for double-click speed
Labels: enhancement :sparkles:

Internet specifications don't provide a great way to distinguish single- and double-clicks; in the DOM, `onClick` will always fire as a part of `onDoubleClick`. The generally-accepted wisdom is to avoid putting both single- and double-click callbacks on a single DOM element, and when this can't be done, to manually handle the single-double distinction by allowing a timeout to elapse before considering a click to be a single-click.

Fair enough, but in that case, it seems like a no-brainer that, with the extra privileges allowed to Electron, we could make this timeout as comfortable as possible to the user, by respecting their OS setting for what constitutes a double-click, rather than using an arbitrary timeout. This also has accessibility implications for people who need to set especially long double-click speeds on their machines.

I propose a method on [systemPreferences](https://www.electronjs.org/docs/api/system-preferences) which returns what the OS reports as the double-click speed.
Repository: flutter
Issue: TimeSensistiveTests in message_loop_unittests are sometimes failing on Fuchsia
Labels: customer: fuchsia,framework,dependency: fuchsia,platform-fuchsia,P2,team-framework,triaged-framework

They are filtered out in run_tests.sh because they sometimes time-out, causing test flakes
Repository: flutter
Issue: Add a clipBehavior property to the flutter/animations OpenContainer class
Labels: c: new feature,package,c: proposal,p: animations,team-ecosystem,P3,triaged-ecosystem

When using the OpenContainer class, I do not want it to clip the child within. For example, to allow a child's box shadow to show through and not be clipped.
Repository: rust
Issue: is_x86_feature_detected! does not work with $:literal argument
Labels: O-x86_64,T-compiler,A-SIMD,C-bug,O-x86_32

```rust
macro_rules! my_is_x86_feature_detected {
    ($feat:literal) => {  // changing to $feat:tt makes it work
        is_x86_feature_detected!($feat)
    };
}

fn main() {
    let _ = is_x86_feature_detected!("mmx");  // works
    let _ = my_is_x86_feature_detected!("mmx");  // does not work
}
```

```console
error: unknown x86 target feature: mmx
 --> src/main.rs:8:13
  |
8 |     let _ = my_is_x86_feature_detected!("mmx");
  |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  |
  = note: this error originates in a macro (in Nightly builds, run with -Z macro-backtrace for more info)
```

The [std::is_x86_feature_detected!](https://doc.rust-lang.org/stable/std/macro.is_x86_feature_detected.html) macro appears to work when called with a string literal argument, and works when called with a $:tt argument, but does not work with a $:literal argument. I believe that it should work all three ways.
Repository: pytorch
Issue: Negative stride values in `as_strided`
Labels: module: internals,module: error checking,triaged,module: memory format

## 🐛 Bug

`as_strided` accepts negative stride values, but acts as though the stride value is equal to one.
<!-- A clear and concise description of what the bug is. -->

## To Reproduce

Steps to reproduce the behavior:

``` python
x = torch.arange(16)
x.as_strided((4, ), (-42, ), 8)
# tensor([ 8,  9, 10, 11])
```
<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Expected behavior

Either

 * An exception is thrown (if negative strides are not supported), or
 * stride backwards from storage_offset.

<!-- A clear and concise description of what you expected to happen. -->

## Environment

```
Collecting environment information...
PyTorch version: 1.5.0+cu101
Is debug build: No
CUDA used to build PyTorch: 10.1

OS: Ubuntu 18.04.3 LTS
GCC version: (Ubuntu 7.5.0-3ubuntu1~18.04) 7.5.0
CMake version: version 3.12.0

Python version: 3.6
Is CUDA available: No
CUDA runtime version: 10.1.243
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: /usr/lib/x86_64-linux-gnu/libcudnn.so.7.6.5

Versions of relevant libraries:
[pip3] numpy==1.18.4
[pip3] torch==1.5.0+cu101
[pip3] torchsummary==1.5.1
[pip3] torchtext==0.3.1
[pip3] torchvision==0.6.0+cu101
[conda] Could not collect
```

Also the same on Mac OSX with torch 1.5.0 and numpy 1.18.4.

## Additional context

<!-- Add any other context about the problem here. -->


cc @ezyang @bhosmer @smessmer @ljk53 @bdhirsh @ailzhang @VitalyFedyunin @jamesr66a @ppwwyyxx
Repository: scrcpy
Issue: Demo mode by passing a flag
Labels: feature request,custom actions

 - [x] I have checked that a similar [feature request](https://github.com/Genymobile/scrcpy/issues?q=is%3Aopen+is%3Aissue+label%3A%22feature+request%22) does not already exist.

**Is your feature request related to a problem? Please describe.**
Right now I'm using [this](https://android.googlesource.com/platform/frameworks/base/+/master/packages/SystemUI/docs/demo_mode.md) particular script to enable the demo mode and then run scrcpy. It would be better if this is an inbuilt thing.