sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: FileDialog minor UI inconveniences
Labels: enhancement,usability,topic:gui

**Godot version:** 3.2-stable
**OS/device including version:** Debian Buster amd64

**Issue description:**
Currently, FileDialog behaves very differently from what you would expect in any other system file dialog. With a few minor changes, it would be much more "pleasant to use". Those don't deserve separate issues because it's all one thing - "Fix FileDialog design".

- "Open" button state (enabled/disabed) is determined by selection only, not by what's typed.

This is pretty confusing. Currently, the "Open" button is disabled when nothing is selected, and enabled when you select something. This leads to a lot of confusion when coupled with typing things manually. I can type the file name in the bottom LineEdit, but "Open" is still disabled. But I can press "Enter", and it will work. Or I can select a file and then type a nonexistent filename - the button is enabled, but clicking it does nothing. My suggestion is: either disable the button "properly" (when nothing is selected AND there is no text in LineEdit), or don't disable it at all (error checking is already there, so it won't be any worse).

- Entering a full path/name manually (instead of navigating to it) should work.

For example, the dialog is asking you to locate a certain file on your filesystem. Typing "/usr/bin/myfile" is MUCH faster than navigating to that file, especially with folders containing a lot of files. Currently, typing a filename is possible, but typing a full path+name does not work.

- Typing a path and hitting "Enter" should navigate to this path.

Currently, it is possible to type the path in the top LineEdit to navigate there, but not in the bottom one. So we have to click the top one, delete everything there (no "Clear" button!), enter the path, then click the bottom one, enter the file name, wonder why "Open" is still not active, and hit "Enter" hoping for the best.

Some of those may be tricky to implement considering various modes of the same FileDialog, but we can have a discussion here about it. Maybe there are other "usually present" features I have missed.

I've tried to tackle such a "cosmetic polish" myself, but no, I can't handle C++ in an unfamiliar project...
Repository: svelte
Issue: Strange behaviour with interrupted crossfade transitions
Labels: bug

Similar to  https://github.com/sveltejs/svelte/issues/3398
Here is a very basic setup to test for the crossfade transition:
https://svelte.dev/repl/7b633681d5a849968771c4fe9b7e7536?version=3.18.1

The duration is set to `2s` so you have time to interrupt the transition by clicking a second time on the button.

On the first interruption, the transition is working as expected: the forward transition stops, and the backward transition starts where the forward transition stopped.

However, on second and following interruptions, the transition isn't smooth anymore. The crossfade fallback is called for the forward transition, and the backward transition doesn't start where the transition was stopped, but where it was stopped in the first interruption.

You will have to reload the script to observe the expected behaviour again.
Repository: next.js
Issue: Swipe back on mobile browser with getInitialProps flickers the previous page
Labels: good first issue,Navigation

# Bug report

## Describe the bug

On mobile browsers (tested with Chrome and Firefox), swiping back or forward on a dynamic page (one that gets data from `getInitialProps`) will sometimes "flash" the previous page while the content is loading. [Here is a video](https://share.getcloudapp.com/2NurgWDe) that shows the problem.

## To Reproduce
1. Create a next.js app with the following pages:

`index.js`
```
import Link from "next/link";

export default function Index() {
  return (
    <div>
      <p><Link href="data"><a>Link</a></Link></p>
    </div>
  );
}
```

`data.js`
```
const Index = props => {
  return (
    <div>
      <h1>Test mobile back</h1>
      <ul>
        {props.data.map(name => (
          <li key={name}>
              <a>{name}</a>
          </li>
        ))}
      </ul>
    </div>
  )
};

function sleep(ms) {
  return new Promise((resolve) => {
    setTimeout(resolve, ms);
  });
}

Index.getInitialProps = async function() {
  await sleep(1000)

  return {
    data: ["one", "two", "three", "four", "five", "six"]
  };
};

export default Index;
```

2. Run it, and access it with a mobile browser.
3. Click on the link, you are now on a page with "one", "two"...
4. Swipe back
5. Now swipe forward. Notice the "flash" of the previous screen.

Now, add `"seven"` to the data returned in `data.js`, and notice the problem doesn't happen anymore

## Expected behavior

No flash of the previous page when swiping forward or backward on mobile browser. [This is what happens now](https://share.getcloudapp.com/2NurgWDe) vs [this is what should happen](https://share.getcloudapp.com/p9u5vYDA)

## System information

- OS: MacOS
- Browser (if applies): Mobile Safari, chrome and firefox
- Version of Next.js: 9.2.1
Repository: go
Issue: x/exp/apidiff: resolution of type aliases depends on type names
Labels: NeedsInvestigation

```go
package v1
type T interface { F() }
func F(T) {}
```

```go
package v2
import "example.com/x/common"
type T = common.T2
func F(T) {}
```

```go
package common
type T2 interface { F() }
```

```shell
$ apidiff example.com/x/v1 example.com/x/v2
Incompatible changes:
- F: changed from func(T) to func(example.com/x/common.T2)
- T: changed from T to example.com/x/common.T2
```

This is obviously wrong: `v1` and `v2` have identical APIs; we've just extracted the `v2.T` type into a separate package.

At first I thought apidiff wasn't keeping track of type aliases, but if I keep the exact same API but keep the *name* of the type the same (`common.T`, not `common.T2`) then it reports no API change.
Repository: material-ui
Issue: [Switch] ref attribute is not the root element
Labels: bug 🐛,breaking change,component: switch

- [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 😯

When attempting to use the width of a Switch component, I don't get the width of the surrounding span.

## Expected Behavior 🤔

When getting the offsetWidth of the Switch's ref, it should be the width of the entire component.

## Steps to Reproduce 🕹
Attempt to use the ref component and retrieve the width. Set a component to marginLeft to share that width. (I've also reset the margin).

https://codesandbox.io/s/gifted-joliot-gxzni

## Context 🔦
I would expect the helper text to align with the label of the switch (see codesandbox example)

I noticed that the ref was pointing to SpanBase: https://github.com/mui-org/material-ui/blob/7f4b81ffb7b76f73319b38f1b9f287f43c74e6d0/packages/material-ui/src/Switch/Switch.js#L162-L187

Perhaps the ref should be the span and an 'innerRef' would point to the SpanBase? I'm unsure of the right way forward. Maybe I'm misinterpreting what "root" should be, however I would like to get the width of the Switch itself, parent span CSS included.

## Your Environment 🌎

| Tech        | Version |
| ----------- | ------- |
| Material-UI | v4.9.1  |
| React       |    v16.12.0     |
| Browser     |    Chrome    |
Repository: flutter
Issue: [google_sign_in] Retrieve authorization code instead of token
Labels: p: google_sign_in,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

## Use case

- I want to implement `Google sign in`  in my app with an option to specify the `responseType="code"` to get an authorization code. (it's not token, not access token!)

- Click on the `Google sign in` button will bring up a popup window for user to select account. After user select one and the window closes, you'll get the code from the button's callback function.

- Send this code to backend server's JWT endpoint. And use JWT token to access protected resources.

## Proposal

- Provide an option in SignIn function to specify responseType like in [react-google-login](https://github.com/anthonyjgrove/react-google-login)
Repository: rust
Issue: MIR SourceScopes stay around even when all their uses were removed.
Labels: A-debuginfo,C-enhancement,P-low,T-compiler,A-MIR

We already have a testcase, namely [`simplify_try`](https://github.com/rust-lang/rust/blob/85ffd44d3d86214fc06be4add039e26f85261a2b/src/test/mir-opt/simplify_try.rs), which replaces enough of the original body to make some `SourceScope`s unused.

However, despite no statements/terminators using those scopes anymore, they stick around.
The fact that they're gone is in itself a problem (debuginfo is lost, see comments on #66282), but we could argue that `SourceScope`s only used in unreachable code should still be removed, e.g.:
```rust
if false {
    let x = 123;
}
```
There is no reason to have debuginfo for `x` tracked anywhere once the `x = 123;` block is removed.

@rust-lang/wg-mir-opt
Repository: vscode
Issue: Allow to use decorations in quick input (e.g. for editors picker)
Labels: feature-request,file-decorations,quick-open

For the recently used menu (which is bound to <kbd>Ctrl</kbd> + <kbd>Tab</kbd>) I would like to see git decoration status (modified/untracked/...) just like they work for **OPEN EDITORS** View.

![Screenshot (142)](https://user-images.githubusercontent.com/9638156/74091650-a9bff400-4aca-11ea-82ba-0218fe7a50e5.png)
Repository: pytorch
Issue: QNNPACK: GNU aarch64 assembler does not support 4s on neon mov
Labels: oncall: mobile

Unlike clang, GNU assembler does not support 4s type on neon mov and gives these errors:

> 8x8-dq-aarch64-neon.S: Assembler messages:
> 8x8-dq-aarch64-neon.S:657:
> Error: operand mismatch -- `mov V8.4s,V9.4s'
> Info:    did you mean this?
> Info:            mov v8.8b, v9.8b
> Info:    other valid variant(s):
> Info:            mov v8.16b, v9.16b

Changing to 16b fixes the issue.
Repository: godot
Issue: iOS export completely overwrites directories
Labels: bug,platform:ios,topic:editor,topic:porting,confirmed

**Godot version:**
3.2

**OS/device including version:**
macOS 10.15.2

**Issue description:**
I accidentally exported an iOS project out to the same directory my game project was in. Because the names were the same, it overwrote my entire game directory without warning.

**Steps to reproduce:**
Export iOS project to parent directory containing game project, save as same name. Instead of throwing a warning up or just adding files to the directory, it overwrites everything.
Repository: rust
Issue: rust-mingw is missing libssp*
Labels: O-windows-gnu,T-infra,C-bug

The GCC compiler that comes with rust-mingw understands `-fstack-protector-strong` and emits stack-protector code, but the build further fails to link with messages like:
```
C:\Users\task_1581171456\repo\git-core\libcinnabar.a(cinnabar-fast-import.o):cinnabar-fast-import.c:(.text+0x291): undefined reference to `__stack_chk_fail'
```

The missing symbol is normally added by `gcc` to the `ld` command line via `-lssp_nonshared -lssp`, when it's passed `-fstack-protector-strong` during linking. Adding `-fstack-protector-strong` via `RUSTFLAGS=-Clink-arg=-fstack-protector-strong` doesn't actually work because of `-nostdlib` that rust adds on its own, but `RUSTFLAGS=-Clink-arg=-lssp_nonshared -Clink-arg=-lssp` doesn't work either because libssp* is not provided by rust-mingw.
Repository: rust
Issue: Can't use ASAN with Xcode clang
Labels: A-linkage,O-macos,T-compiler,A-sanitizers,C-bug

When building rust code with `-Zsanitizer=address` and following through with `-fsanitize=address` for C/C++ code that might be compiled by build scripts, the build ends up failing with (using Xcode 11.3 on travis):
```
  = note: Undefined symbols for architecture x86_64:
            "___asan_version_mismatch_check_apple_1100", referenced from:
                _asan.module_ctor in libcinnabar.a(cinnabar-fast-import.o)
                _asan.module_ctor in libcinnabar.a(cinnabar-helper.o)
                _asan.module_ctor in libcinnabar.a(cinnabar-notes.o)
                _asan.module_ctor in libcinnabar.a(cinnabar-util.o)
                _asan.module_ctor in libcinnabar.a(hg-bundle.o)
                _asan.module_ctor in libcinnabar.a(hg-connect.o)
                _asan.module_ctor in libcinnabar.a(hg-connect-http.o)
                ...
          ld: symbol(s) not found for architecture x86_64
          clang: error: linker command failed with exit code 1 (use -v to see invocation)
```

There's probably nothing rust can do about it, so this is more about SEOing for people who might hit the same problem.
Repository: TypeScript
Issue: Feat: Non-Detail view for Error Messages
Labels: Suggestion,Needs Proposal

## Suggestion

The following is a case where I'm missing a single field from an object:

<img width="354" alt="Screen Shot 2020-02-08 at 6 08 45 PM" src="https://user-images.githubusercontent.com/14002040/74093917-47e99500-4a9e-11ea-886a-78759f601d50.png">
<img width="925" alt="Screen Shot 2020-02-08 at 6 08 57 PM" src="https://user-images.githubusercontent.com/14002040/74093918-48822b80-4a9e-11ea-8948-3f3933822fc7.png">
<img width="401" alt="Screen Shot 2020-02-08 at 6 09 02 PM" src="https://user-images.githubusercontent.com/14002040/74093919-4a4bef00-4a9e-11ea-94b6-2a47e92c79ea.png">

The amount of detail in this error message is very useful for extreme scenarios, but in a general day to day scenario, it's a bit overwhelming.

It would be really nice to have detailed messages like this hidden behind a "See More" item, and instead show the simplest form of the error.  In this case the error could be 
```
missing prop "fields" of type "object"
```
 I don't need to know what the object type is, or what the parent type is.  I can just get that error message later.


## Use Cases
Almost 100% of the errors I get in TypeScript would be improved by this.  It's very rare that I want to know all the information, and almost always that I just want a simple reminder of what tiny slip up it is.

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: TypeScript
Issue: Control flow doesn't affect spreaded properties
Labels: Bug

**TypeScript Version:**  3.7.4

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** `react required props`

![image](https://user-images.githubusercontent.com/6340841/74095711-715bee00-4aa9-11ea-9475-e622e95dfa35.png)


**Code**

```tsx
import React from 'react'

type Props = {
  foo?: string
}

const Example = (props: Props) => (
  <>
    {/* [bug?] Throws an error about required prop, despite null check */}
    {props.foo && <Component {...props} />}


    {/* Shows an error, as expected, because lack of null-check  */}
    <Component {...{ ...props, foo: props.foo }} />

    {/* Workaround 1: No error */}
    {props.foo && <Component {...{ ...props, foo: props.foo }} />}


    {/* Shows an error, as expected, because lack of null-check  */}
    <Component {...props} foo={props.foo} />

    {/* Workaround 2: No error */}
    {props.foo && <Component {...props} foo={props.foo} />}
  </>
)

const Component = ({ foo }: Required<Props>) => <p>{foo}</p>

export default Example
```

**Expected behavior:**

TypeScript would detect that we're inside a null check, and treat the checked property as non-nullish.

**Actual behavior:**

TypeScript doesn't notice that the checked property is non-null, because it's inside an object spread. 

As a workaround, the null-check will still work if the property is explicitly added to the spread object (workaround 1) or explicitly passed as a prop (workaround 2).
Repository: pytorch
Issue: Python package using CMake
Labels: module: build,low priority,triaged,enhancement

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->
Use existing CMake build to create a python .whl file
## Motivation
The CMake build is clear and well documented. It would be helpful if a corresponding Python WHL package is built using the existing CMake script.
<!-- 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 -->
The python build is esoteric in nature. This will benefit users who are prone to building CMake using a GUI rather than a command line approach.
## Pitch

<!-- A clear and concise description of what you want to happen. -->
If "build python package" is selected in CMake, then , during sudo make install, the python files and associated binaries and libraries should be installed in the /usr/local/lib/x86_64/python3/dist_packages folder. Currently, only the "caffe2" python binding is installed
## Alternatives

<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->
Repository: flutter
Issue: Request: locator for labelText in flutter driver
Labels: c: new feature,tool,t: flutter driver,P3,team-tool,triaged-tool

Hi please could you help.
When using a form - there is attribute 'labeltext' which is the default text .  There is currently no way to extract this  I tried using Gettext but this does pull it. Please can you advise.
Repository: rust
Issue: Add `with_exact_size` and `with_size_hint` to `Iterator`
Labels: T-libs-api,C-feature-request,A-iterators

Usually iterator adaptors do a fine job at keeping information about the length of an iterator. But once you throw something like `filter` in your iterator chain, the lower bound is 0, meaning that collecting into a collection can't properly pre-allocate. Also, some iterator adaptors (like `chain`) cannot implemented `ExactSizeIterator` although in many real world cases, the size is perfectly known. 

Currently, working around those limitations is often tedious and requires quite a bit of additional code. I think it would be a lot nicer to just add a `.with_exact_size(27)` somewhere into your chain. So I'd like to propose adding the following to `Iterator`:

- **`fn with_size_hint(self, lower: usize, upper: Option<usize>) -> SizeHint`**
  - `SizeHint` would implement `Iterator::size_hint` with the given values, forwarding all other methods to the inner iterator (and implementing the same traits)
- **`fn with_exact_size(self, size: usize) -> ExactSize`**
  - `ExactSize` would implement `ExactSizeIterator` with the given value and override `Iterator::size_hint`. All other methods are forwarded to the inner iterator (and implementing the same traits, plus `ExactSizeIterator`)

I would have created this as a PR, but I'm short on time and wanted to hear some opinions first.
Repository: node
Issue: HTTP2 Server Upgrade listener undocumented
Labels: doc,http2

- All versions that have HTTP2 and HTTPS* implemented
- Documentation problem

The code below shows what is up. I wonder what could be the reason that it works even-tough it is undocumented even in the typescript definitions that come with npm.
I would say this is due to C++ inheritance from HTTPServer to HTTPSServer and HTTP2Server, but no idea, someone could look into it to make sure.

```
const server = http2.createServer({
  allowHTTP1: true
});

server.on('upgrade', (request, socket, head) => {
  // This does work, but no documentation anywhere (internet, TS definitions, ancestor classes neither)
  // (One could add as ws upgrade handler here)
});
```

**Edit:** apparently it is undocumented in the node HTTPS Server as well.
Repository: angular
Issue: Angular IVY Animation issue - element is not getting removed
Labels: type: bug/fix,area: animations,freq2: medium,regression,state: confirmed,P2

# 🐞 bug report

### Affected Package
Angular animations in combination with IVY, and maybe some other stuff mixed in. Unkown because unable to reproduce in stackblitz.


### Is this a regression?
Yeah, sort of, I don't have the issue pre-IVY

### Description
![image](https://user-images.githubusercontent.com/1098243/74107230-248e1b00-4b6e-11ea-8a44-c9617b325d66.png)
![image](https://user-images.githubusercontent.com/1098243/74107234-2c4dbf80-4b6e-11ea-8629-d69bd5c62d85.png)
2 screenshots above.
The first one has this as DOM:
![image](https://user-images.githubusercontent.com/1098243/74107250-425b8000-4b6e-11ea-9246-9689db0c5243.png)
the class combination-container can only happen once (it's in an *ngIf).
But in combination with
![image](https://user-images.githubusercontent.com/1098243/74107274-60c17b80-4b6e-11ea-85b9-c44bee0e18e9.png)
it seems that somehow, the previous elements are not removed.
I've tried my best to reproduce the situation in a stackblitz:
https://stackblitz.com/edit/components-issue-tdugpz?file=src%2Fapp%2Fcontainer.ts
with the minimal component logic I have. But I don't succeed. In the stackblitz it works but in the application it doesn't.
It happens when the elements are changed while you're in the first tab. So it seems to have to with the fact that the fadein animation is running while the element is not on screen.
If I remove the fadein animation, the elements are correctly removed.






## 🔬 Minimal Reproduction
<!--
Please create and share minimal reproduction of the issue starting with this template: https://stackblitz.com/fork/angular-issue-repro2
-->
https://stackblitz.com/edit/components-issue-tdugpz?file=src%2Fapp%2Fcontainer.ts
=> failed reproduction, but shows the hierarchy where I have the issue.

## 🔥 Exception or Error
None

**Angular Version:**
9.0.0
cli 9.0.1
Repository: go
Issue: x/mobile: add option to pass in gobind
Labels: NeedsInvestigation,mobile

```zsh
% ~/go/bin/gomobile bind -target iOS ./lib
```
will not work until you set PATH environment variable which points to `gobind`.
It is something that I don't expect.

I expect that `~/go/bin/gomobile init` will fix all issues and everything will be fine.
Could you add option to set path to binary `gobind`?

```zsh
% ~/go/bin/gomobile bind -bin ~/go/bin/gobind -target iOS ./lib
```