sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Viewport's Control derived nodes bug when in-editor
Labels: bug,topic:plugin

**Godot version:**
3.2.2 RC1


**OS/device including version:**
Ubuntu 20.04

**Issue description:**
I'm making a plugin using viewports in-editor (tool keyword) and UI doesnt work, I'm using as basis the demo 3d-in-2d.

It works when you press F6 to run game, but in-editor doesnt work.

**Steps to reproduce:**
* Download MRP below
* Install inside addons/ of an existing project
* Open Node.tscn
* Press F6
* See the button working
* Now activate the plugin
* press F8 to open the dialog
* See that button is not working

**Minimal reproduction project:**
[file.zip](https://github.com/godotengine/godot/files/4792441/file.zip)
Repository: PowerToys
Issue: HTML <details> tab breaks markdown preview
Labels: Product-File Explorer

Adding collapsible section in markdown using html details tag is not supported and all of the embedded markdown in the details tag is shows as is:

Use HTML tag details
    \<details>
      < summary >Click to expand!< /summary >
      
      ## Add collapsible section
      1. All of this is shown
      2.  with 
         * no line breaks 
         * or rendering
    </ details>
Repository: flutter
Issue: datetime keyboard input type for Samsung keyboards doesn't allow for separators
Labels: platform-android,framework,f: material design,f: date/time picker,a: fidelity,e: OS-version specific,has reproducible steps,P2,e: samsung,found in release: 3.3,found in release: 3.7,team-android,triaged-android

With the new date picker, the manual input entry requires a / separator which is not present in the Samsung keyboard that is invoked with the TextInputType.datetime for the InputDatePickerFormField widget.

Flutter version: 1.17.0
Device: Samsung Galaxy S6 - Android 7.0

![image](https://user-images.githubusercontent.com/35256345/84918519-99430a00-b0b8-11ea-84bc-b06eed31c72e.png)
Repository: rust
Issue: intra-rustdoc-link: Cannot use core in core crate
Labels: T-rustdoc,S-blocked,A-intra-doc-links,D-confusing

I tried to document this code in libcore (`./x.py doc src/libcore`):

```rust
impl<T: Deref, E> Result<T, E> {
    /// Converts from `Result<T, E>` (or `&Result<T, E>`) to `Result<&<T as Deref>::Target, &E>`.
    ///
    /// [`core::ops::Deref`]
    pub fn as_deref(&self) -> Result<&T::Target, &E>;
}
```

I expected to see the above code build pass.

Instead, this happened: Build failed the following errors:

```rust
 Documenting core v0.0.0 (/home/lzutao/fork/rust/compiler/src/libcore)
error: `[core::ops::Deref]` cannot be resolved, ignoring it.
    --> src/libcore/result.rs:1151:68
     |
1151 |     /// Coerces the [`Ok`] variant of the original [`Result`] via [`core::ops::Deref`]
     |                                                                    ^^^^^^^^^^^^^^^^^^ cannot be resolved, ignoring
     |
note: the lint level is defined here
    --> src/libcore/lib.rs:64:9
     |
64   | #![deny(intra_doc_link_resolution_failure)] // rustdoc is run without -D warnings
     |         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
     = help: to escape `[` and `]` characters, just add '\' before them like `\[` or `\]`

error: Could not document `core`.
```

cc #43466
cc @Manishearth @GuillaumeGomez @jyn514
Repository: react-native
Issue: Redesign Native RedBox 
Labels: Type: Discussion,Type: Enhancement,Never gets stale

## Overview

LogBox handles most errors users see but we still display native RedBoxes in cases where:
- JavaScript has not loaded (e.g. Metro is unavailable)
- JavaScript is unavailable (e.g. a syntax error in the bundle)
- LogBox fails to render (e.g. an error in LogBox JavaScript)
- Native log errors (e.g. RCTLogFatal)

This issue is to improve the fallback RedBox in these cases for a better experience.

## Tasks

- Update design to be in line with LogBox (see below)
- Cleanup code by removing the symbolication logic (as this is handled by LogBox)
- Remove stack trace since for all errors that this can occur the stack trace is not relevant

## Designs

### JavaScript has not loaded (Metro is unavailable)
![image](https://user-images.githubusercontent.com/2440089/84919627-2d4cab80-b090-11ea-958a-dc8717be86f4.png)

### JavaScript is not available (syntax error)

![image](https://user-images.githubusercontent.com/2440089/84919926-89173480-b090-11ea-9de4-4e53cae6ea8e.png)

###  LogBox fails to render

![image](https://user-images.githubusercontent.com/2440089/84921438-7998eb00-b092-11ea-8238-064fe96d8d4d.png)


### Native log errors

![image](https://user-images.githubusercontent.com/2440089/84921062-fa0b1c00-b091-11ea-88bc-8bd687ddd15d.png)
Repository: flutter
Issue: Refresh indicator and VoiceOver
Labels: platform-ios,framework,f: material design,a: accessibility,f: cupertino,d: examples,team-design,triaged-design

There does not appear to be a way to trigger a `RefreshIndicator` on iOS when using VoiceOver.
Repository: TypeScript
Issue: improper declared type cause narrow type not work when its computed type is not union.
Labels: Bug,Has Repro

<!-- 🚨 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

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

```ts repro
interface A {
    type:'A'
}

interface B {
    type:'B'
}

function assert(x:any) :asserts x is A|B{

}

function foo(x: any): any {
    x;  // any
    assert(x);
    x;  // A | B
    if (x.type === 'A') {
        return x;
    }
    x;  // B
    if (x.type === 'B') {
        return x;
    }
    x;  // B, but should be never.
//  ^?
}
```

**Expected behavior:**
the last x should be never.

**Actual behavior:**
still B.

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->
https://www.typescriptlang.org/play/index.html?ts=4.0.0-dev.20200615&ssl=1&ssc=1&pln=25&pc=2#code/JYOwLgpgTgZghgYwgAgIIG8BQyfLATwAcIAuAclTMwF9NNRJZEUAhLXPI0slq2zGAFcQCMMAD2IZHADOM6GAAUADxJwQ+AJTI1chTOTLkwA6gA+bOvyEixk5DHHiVJaRs2v1+ZO1zKA3DgA9EFu+Ni4svJQSsqa-hE4AcGhqMhmyCyJxjDIKgB0BMTIALxlyBRk2r4cOFAQYIJQUgHZtBzJyCGZ2cC5BUUoZSUVvNXZHPWNzYYJHO1+gV2hWdRAA

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: flutter
Issue: Make a logging macro for Window embedding
Labels: engine,platform-windows,a: desktop,P3,c: tech-debt,team-windows,triaged-windows

Currently we're just using `stderr`; it would be good to have a logging macro that lets us adjust how we do logging over time, have debug-only vs debug-or-release logging, etc.
Repository: flutter
Issue: Document how AA works in Flutter API docs and what "conflation" artifacts are expected
Labels: engine,dependency: skia,d: api docs,c: rendering,P3,team-engine,triaged-engine

As Flutter uses Skia, it's limited by Skia's AA algorithm. We have to clearly document such limitations.

See https://groups.google.com/g/skia-discuss/c/2ULlxsL8Aek/m/phyycURxAAAJ and https://github.com/flutter/flutter/issues/58547#issuecomment-639917241 for some more details.
Repository: terminal
Issue: Prompt before closing pane with multiple client apps
Labels: Issue-Feature,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
Some console apps, like vim, neovim, far, etc, are ignored when you accidentally hit Ctrl+W and your unsaved work is gone forever.
<!-- 
A clear and concise description of what the problem is that the new feature would solve.
Describe why and how a user would use this new functionality (if applicable).
-->

# Proposed technical implementation details (optional)
I'm not sure how to do that, but it would be nice to offer an API or something to block closing if some return code is not met.

<!-- 
A clear and concise description of what you want to happen.
-->
Repository: flutter
Issue: [SelectableText] Edit menu position is incorrect when Selected text exceeds the Screen size
Labels: platform-android,platform-ios,framework,f: material design,a: typography,has reproducible steps,found in release: 3.3,found in release: 3.6,team-design,triaged-design

## Steps to Reproduce
1. Use `SelectableText(LONG_TEXT, showCursor: true)` **Edit:** Text needs to be longer than fits on screen
2. Highlight text -> Select All
3. Text is selected but `Copy` is not an option. Tap/LongTap will remove the selection.


<details>
  <summary>flutter doctor -v</summary>
[✓] Flutter (Channel stable, v1.17.3, on Linux, locale en_US.UTF-8)
    • Flutter version 1.17.3 at /home/jacob/tools/flutter
    • Framework revision b041144f83 (13 days ago), 2020-06-04 09:26:11 -0700
    • Engine revision ee76268252
    • Dart version 2.8.4

 
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.0)
    • Android SDK at /home/jacob/Android/Sdk
    • Platform android-30, build-tools 30.0.0
    • Java binary at: /snap/android-studio/90/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Android Studio (version 4.0)
    • Android Studio at /snap/android-studio/90/android-studio
    • Flutter plugin version 46.0.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] Connected device (1 available)
    • sdk gphone x86 • emulator-5554 • android-x86 • Android 11 (API 30) (emulator)

• No issues found!
</details>
Repository: PowerToys
Issue: [FancyZones Options] Add a button to exclude a window name with a drag and drop widget 
Labels: Idea-Enhancement,Help Wanted,FancyZones-Settings,Product-FancyZones,Needs-Spec

# Summary of the new feature/enhancement

I would find it faster to drag and drop a targeting crosshair over a window to add it to the list of excluded window names in the FancyZones options.

I imagine a button that looks like a crosshair that you can click to pickup, drag over a window, and drop-- then the window's name will be added to the list of excluded items.

# Proposed technical implementation details (optional)

This could probably be done by creating a drag-and-droppable widget that is not bounded by the options window, and capture the window handle upon `DragEnter()`, and add the window's name to the list upon `DragDrop()`.

> You can enable user drag-and-drop operations within a Windows-based application by handling a series of events, most notably the DragEnter, DragLeave, and DragDrop events.

from https://docs.microsoft.com/en-us/dotnet/framework/winforms/advanced/drag-and-drop-operations-and-clipboard-support
Repository: rust
Issue: Confusing 'type mismatch' error when using function pointer as fn trait
Labels: A-diagnostics,A-lifetimes,T-compiler,D-confusing

The following code:

```rust
struct MyType;

fn parse_header<T, F: FnOnce(&MyType) -> T>(parse: F) -> T {
    panic!()
}

fn make_it(val: &MyType) -> &MyType { panic!() }

pub fn from_url<'a>() -> &'a MyType {
    parse_header(make_it)
}

fn main() {}
```

gives this error:

```
error[E0271]: type mismatch resolving `for<'r> <for<'s> fn(&'s MyType) -> &'s MyType {make_it} as std::ops::FnOnce<(&'r MyType,)>>::Output == _`
  --> src/main.rs:10:5
   |
3  | fn parse_header<T, F: FnOnce(&MyType) -> T>(parse: F) -> T {
   |                                          - required by this bound in `parse_header`
...
10 |     parse_header(make_it)
   |     ^^^^^^^^^^^^ expected bound lifetime parameter, found concrete lifetime
```

There are several issues with this error:

* The 'type mismatch' message contains several pieces of 'internal' rust syntax (multiple consecutive `for<>` binders, the weird `{make_it}` syntax for function pointers, and an inference variable).
* We call the return type `T` a 'bound', even though it's clearly not a bound.
* We give an confusing 'expected bound lifetime parameter, found concrete lifetime' message, which doesn't really explain what's going on
* We don't point at `make_it`, even though it's part of the issue.

This was minimized from code posted by @rvolosatovs.
Repository: PowerToys
Issue: [Shortcut Guide] Improve Desktop Preview when using multiple displays
Labels: Idea-Enhancement,Product-Shortcut Guide

When using the Shortcut-Guide only the active window will be shown in preview. But all displays will be available in the preview area.

# Environment

```
Windows build number: Microsoft Windows [Version 10.0.18363.900]
PowerToys version: Release v0.18.2
PowerToy module for which you are reporting the bug (if applicable): Shortcut Guide
```

# Steps to reproduce

Open the Shortcut Guide

# Expected behavior

Not sure. There are 2 possible behaviors in my opinion.

a) Show the desktop in the preview area just like it is
b) Only show the active window but hide the display previews 

The current behavior

c) Display all available displays as black squares in the preview area but only show the active window

# Actual behavior

When bringing up the Shortcut Guide it displays all avilable displays as "black boxes" but only shows the active window - if one is selected.

# Screenshots

![Pkg2V2lXYj](https://user-images.githubusercontent.com/4655466/84966151-0da99780-b111-11ea-9adc-e9b1704b8b34.jpg)
Repository: pytorch
Issue: C++ API for torch.autograd.functional.jacobian
Labels: module: cpp,module: autograd,triaged

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->

Add C++ API for [`torch.autograd.functional.jacobian`](https://pytorch.org/docs/stable/_modules/torch/autograd/functional.html#jacobian)

## Motivation

<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->

I would like to calculate the jacobian of my model output wrt to the input and the feature is available in the python api but was dismayed to find out that it was not in the C++ API.

## Pitch

<!-- A clear and concise description of what you want to happen. -->

Include `torch::autograd::functional::jacobian` functionality in C++ API

## Alternatives

<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->

N/A

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->

Just some links for easy browsing:
https://github.com/pytorch/pytorch/tree/master/torch/csrc/autograd
https://pytorch.org/cppdocs/api/namespace_torch__autograd.html
https://pytorch.org/docs/stable/_modules/torch/autograd/functional.html#jacobian


cc @ezyang @SsnL @albanD @zou3519 @gqchen @yf225 @glaringlee
Repository: flutter
Issue: TabBar shadows are clipped and indicator height cannot be reduced
Labels: framework,f: material design,has reproducible steps,found in release: 3.3,found in release: 3.7,team-design,triaged-design

Hello!

To understand what am I trying to achieve, have a look at the attached image.
<img width="426" alt="Screenshot 2020-06-18 at 3 36 51" src="https://user-images.githubusercontent.com/29690177/84968863-b955e600-b117-11ea-9f6c-37d9bb3c2fb7.png">

But as you can see, the tab's shadow can not fit inside the Tab. So how do I make space for the shadow?
Also, how do I change the indicators size? For example, I want to make my tabs indicator height smaller.
I can't find any way to configure that.

Here is how I build a Tab:
```
Tab buildTab(CategoryModel category) {
    return Tab(child: ConstrainedBox(
      constraints: BoxConstraints(
        minWidth: 48,
      ),
      child: Text(category.name, textAlign: TextAlign.center,),
    ),);
  }
```
And this is how I builde the TabBar:
```
return TabBar(
      indicator: BoxDecoration(
          color: Colors.blue,
          borderRadius: const BorderRadius.all(
            const Radius.circular(999.0),
          ),
          boxShadow: const [BoxShadow(color: Colors.blueAccent, blurRadius: 6.0)]
      ),
      unselectedLabelColor: Colors.blue,
      labelColor: Colors.white,
      isScrollable: true,
      tabs: tabs,
    );
```
Repository: flutter
Issue: Support building Windows applications from macOS
Labels: c: new feature,platform-mac,platform-windows,a: desktop,a: build,P3,team-windows,triaged-windows


![image](https://user-images.githubusercontent.com/1920873/84974712-618a9f80-b156-11ea-9ca6-254401843d7c.png)
![image](https://user-images.githubusercontent.com/1920873/84974889-bc23fb80-b156-11ea-94bc-5916d0139bbc.png)
Repository: godot
Issue: Abnormal Android audio recording
Labels: bug,platform:android,topic:porting,topic:audio

Gdodt Editor Version : 3.2.1 Stable
Windows Version : Win10
Android Version : 10
Phone Model : Huawei ELE-AL00

Project settings--Audio--Mix Rate : (8000、16000、or other)
default_bus_layout--Record--Format : 8-Bit

Recording parameters are normal in Windows

But the parameters are abnormal after recording on Android
Mix_Rate : always 44100

**When using Android recording！
Project settings--Audio--Mix Rate : (8000、16000、or other)
This parameter does not take effect on Android when setting！

It is recommended to add "Mix Rate" property setting in "Audioeffectrecord"**
Repository: rust
Issue: Duplicating mut Copy variables doesn't warn or error
Labels: A-lints,A-closures,T-compiler,C-bug

https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=6dee1348129e0c1938c67eb66a8f62b0
```rust
fn main() {
    let mut x = 0;
    let closure = move || {
        let mut closure2 = move || {
            x += 1;
        };
        closure2();
        println!("{}", x);
    };
    closure();
}
```

The inner closure essentially forks the mutable variable `x` into *two* variables. I would expect rustc to give a warning or error, but there is no warning or error. I understand the logic behind allowing this but I think it can lead to surprising results. rust-analyzer warns that assignment to `x` in `closure2` is never read. This led me to a real bug in our code.

Seems to me that duplicating a `mut` `Copy` variable like this deserves some kind of warning at least.
Repository: react
Issue: Proposition about onInput/onChange
Labels: Status: Unconfirmed

Hi :)

In ReactDom we can find:

``` javascript
function getTargetInstForInputOrChangeEvent(topLevelType, targetInst) {
	if (topLevelType === TOP_INPUT || topLevelType === TOP_CHANGE) {
		return getInstIfValueChanged(targetInst);
	}
}
```

Why not adding an extra condition here like:
``` javascript
function getTargetInstForInputOrChangeEvent(topLevelType, targetInst) {
	if ((!React.$$useRealOnChange && topLevelType === TOP_INPUT) || topLevelType === TOP_CHANGE) {
		return getInstIfValueChanged(targetInst);
	}
}
```

By checking `React.$$useRealOnChange` in this function, a user could add this line:
``` javascript
React.$$useRealOnChange = true;
```
anywhere in their code (before or after including ReactDom) to find back the more native behavior.

I'm sorry in advance if this proposition has already been proposed
Repository: flutter
Issue: [Linux][GTK] Flutter apps will not display properly (Release mode)
Labels: engine,platform-linux,c: rendering,a: desktop,a: build,a: release,P2,team-linux,triaged-linux

Sometimes, Flutter app is not displayed properly. In debug mode, It seems no problem.

![Screenshot from 2020-06-17 21-35-01](https://user-images.githubusercontent.com/62131389/84979054-6ad13780-b169-11ea-95bc-efc89a199ca2.png)

## Steps to Reproduce

1. $ mkdir flutter_sample
2. $ cd flutter_sample
3. $ flutter create .
4. $ flutter build linux
5. $ ./build/linux/release/bundle/flutter_sample
6. Exit the app
7. go to No. 5 step. (Repeat several times)

```
[ERROR:flutter/shell/platform/embedder/embedder_surface_gl.cc(108)] Could not create a resource context for async texture uploads. Expect degraded performance. Set a valid make_resource_current callback on FlutterOpenGLRendererConfig.
[ERROR:flutter/shell/platform/embedder/embedder_surface_gl.cc(108)] Could not create a resource context for async texture uploads. Expect degraded performance. Set a valid make_resource_current callback on FlutterOpenGLRendererConfig.
```

<details>
  <summary>flutter doctor -v</summary>

```
$ flutter doctor -v
[✓] Flutter (Channel master, 1.20.0-1.0.pre.91, on Linux, locale ja_JP.UTF-8)
    • Flutter version 1.20.0-1.0.pre.91 at /opt/flutter
    • Framework revision 9c3f0faa6d (6 hours ago), 2020-06-17 18:47:54 -0400
    • Engine revision 965fbbed17
    • Dart version 2.9.0 (build 2.9.0-14.0.dev 2b917f5b6a)

 
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /home/matsu/Android/Sdk
    • Platform android-29, build-tools 29.0.2
    • Java binary at: /usr/local/android-studio/jre/bin/java
    • Java version OpenJDK Runtime Environment (build
      1.8.0_202-release-1483-b49-5587405)
    ✗ Android licenses not accepted.  To resolve this, run: flutter doctor
      --android-licenses

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Linux toolchain - develop for Linux desktop
    • clang version 6.0.0-1ubuntu2 (tags/RELEASE_600/final)
    • cmake version 3.10.2
    • ninja version 1.8.2
    • pkg-config version 0.29.1

[!] Android Studio (version 3.5)
    • Android Studio at /usr/local/android-studio
    ✗ Flutter plugin not installed; this adds Flutter specific functionality.
    ✗ Dart plugin not installed; this adds Dart specific functionality.
    • Java version OpenJDK Runtime Environment (build
      1.8.0_202-release-1483-b49-5587405)

[✓] VS Code (version 1.46.0)
    • VS Code at /usr/share/code
    • Flutter extension version 3.11.0

[✓] Connected device (3 available)
    • Linux      • Linux      • linux-x64      • Linux
    • Web Server • web-server • web-javascript • Flutter Tools
    • Chrome     • chrome     • web-javascript • Google Chrome 83.0.4103.106

! Doctor found issues in 2 categories.
```

</details>

Thank you.