sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ant-design
Issue: Unable to mention a user via email - new search firing after '@' sign before domain - @gmail.com for example.
Labels: 🐛 Bug,Inactive

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/sad-cohen-p5bs3)

### Steps to reproduce
type in `@` then write an email - `jackjack@gaml.com`

### What is expected?
only `jackjack@gaml.com` should be in the dropdown

### What is actually happening?
both `jackjack@gaml.com` and `alex@gaml.com` appear in the dropdown - this is because the new search fired after second @ sign and the search string is `gaml.com`

| Environment | Info |
|---|---|
| antd | 3.21.1 |
| React | 16.10.2 |
| System | macOS 10.14.6 |
| Browser | chrome |

---
Search shouldn't be triggered second time until user selected from dropdown or search cancelled


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: TypeScript
Issue: `extends ArrayBufferLike` works for own package; but causes errors for downstream users
Labels: Suggestion,Needs Proposal

<!-- 🚨 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.5.1

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

+ `extends ArrayBufferLike`
+ TS2312
+ An interface can only extend an object type or intersection of object types with statically known members.

**Code**

Repro,
https://github.com/AnyhowStep/ts-issue-35172

The line of code that introduced the problem,
https://github.com/AnyhowStep/type-mapping/commit/cb420b8e14dda4de5bf017bcc4a3ab3f35e71de5#diff-f84343d86daf9a112cfa32bdb89c7cdaR2

The following is safe to use on own package and downstream packages,
```ts
interface Buffer {
    ___doesNotExist? : any;
}
```

The following causes downstream packages to break,
```ts
interface Buffer extends ArrayBufferLike {
    ___doesNotExist? : any;
}
```

**Expected behavior:**

Option A:
+ Should crash for own package
+ Should crash for downstream packages

Option B:
+ Should not crash for own package
+ Should not crash for downstream packages

**Actual behavior:**

+ Does not crash for own package
+ Crashes for downstream packages

**Playground Link:** 

None.

But I have repro steps,

https://github.com/AnyhowStep/ts-issue-35172

**Related Issues:** 

None that I could find.
Repository: rust
Issue: cargo doc: add option to document specific private items
Labels: T-rustdoc,C-feature-request

## Problem

I often find myself wanting to expose documentation for a private API that shouldn't be called directly, but is an important enough implementation detail for the advanced users of my library to benefit from reading it.

## Proposal

I want to propose a `#[doc(visible)]` attribute that is analogous to the `#[doc(hidden)]` one. The new attribute would exclude the labeled item from being removed by the [`strip-private`](https://doc.rust-lang.org/rustdoc/passes.html#strip-private) rustdoc pass.

## Alternative solutions considered:

### Making the API public.

Solves the problem, but also creates a new one. Especially bad if the API in question is by itself unsafe and relies heavily on implementation of other parts of the library to guarantee safety. I really don't want users to call such an API.

### Fake item

I could create a fake public struct / method and add my "hidden" documentation to it. This however does not really solve the problem, as the documentation has links to private items that wouldn't work without making the items public. In addition, it's just a nightmare to debug and support such documentation.

### Module-level documentation

Same problem as above, links still will not work.

### `cargo doc --document-private-items`

See https://github.com/rust-lang/cargo/issues/1520.

Also solves the problem, but creates a new one: it adds a ton of clutter making all the documentation much less readable and useful.
Repository: youtube-dl
Issue: Unsupported URL: alphavoice.io
Labels: site-support-request

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2019.11.05**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones

https://www.alphavoice.io/video/jordan-peterson/the-death-and-resurrection-of-christ-a-commentary-in-five-parts
Repository: godot
Issue: [3.x] Typing the entire signal name breaks emit_signal autocomplete
Labels: bug,topic:editor,confirmed,usability

**Godot version:**
3.2 beta 1

**OS/device including version:**
Windows 10

**Issue description:**
Typing the entire signal name wont give you the option to automatically insert quotation marks, and the autocomplete wont appear anymore unless you delete the parenthesis. This may also affect `preload()` file names since it uses a similar autocomplete.

**Steps to reproduce:**
With a script like this
```GDScript
extends Node

signal test

func _ready() -> void:
	emit_signal("test")

```

Type `emit_signal(` which will give all the possible signals that can be emitted.
Now type `test` entirely. Once the word `test` is completely typed it will no longer show up in the autocomplete list to be selected. This breaks the autocomplete so you have to erase the parenthesis and add the parenthesis again to get the autocomplete back.

Here is a demonstration
![gif_output](https://user-images.githubusercontent.com/11450875/69110093-99f2bf80-0a47-11ea-8676-80b99c9b8a1e.gif)
Repository: TypeScript
Issue: Suggestions for property names don't show available keys
Labels: Bug,Help Wanted,Effort: Moderate,Domain: Completion Lists

<!-- 🚨 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.
-->

From https://github.com/microsoft/vscode/issues/84976

<!--
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.8.0-dev.20191116

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
- suggest / suggestion
- completions

**Repo**
For the code:

```ts
interface testObject {

    'Type': 'Example 1',
    'Option 1': string,
    'Option 2': string,
    'Option 3': string

};

interface otherObject {

    'Type': 'Example 2',
    'Option 1': string

};

class Test {

    property?: testObject | otherObject;

};

const example = new Test();

example.property = {

    'Type': 'Example 1',
    ''
}
```

Trigger suggestions inside the `''` in the definition of `example.property`

**Expected behavior:**
Return suggestions for `'Option 1'`, `'Option 2'`, and `'Option 3'`

**Actual behavior:**
Only suggestion for  `'Option 1'` returned:

```
Trace  - 03:11:48.240] <semantic> Response received: completionInfo (16). Request took 1 ms. Success: true 
Result: {
    "isGlobalCompletion": false,
    "isMemberCompletion": true,
    "isNewIdentifierLocation": false,
    "entries": [
        {
            "name": "Option 1",
            "kind": "property",
            "kindModifiers": "",
            "sortText": "0"
        },
        {
            "name": "Type",
            "kind": "property",
            "kindModifiers": "",
            "sortText": "0"
        }
    ]
}
```
Repository: vue-element-admin
Issue: permission 里的next({ ...to, replace: true }) to 加上... 就会出现这个问题Uncaught (in promise) undefined
Labels: enhancement :star:

<!--
    注意：为更好的解决你的问题，请参考模板提供完整信息，准确描述问题，信息不全的 issue 将被关闭。

    Note: In order to better solve your problem, please refer to the template to provide complete information, accurately describe the problem, and the incomplete information issue will be closed.
-->


## Bug report（问题描述）

#### Steps to reproduce（问题复现步骤）
<!--
1. [xxx]
2. [xxx]
3. [xxxx]
-->

#### Screenshot or Gif（截图或动态图）
[https://imgchr.com/i/MgGOYj](https://imgchr.com/i/MgGOYj)
[https://imgchr.com/i/MgGLkQ](https://imgchr.com/i/MgGLkQ)
#### Link to minimal reproduction（最小可在线还原demo）

<!--
Please only use Codepen, JSFiddle, CodeSandbox or a github repo
-->

#### Other relevant information（格外信息）
- Your OS:
- Node.js version:
- vue-element-admin version:
Repository: rust
Issue: Borrow checker bug: `cannot return reference to temporary value`
Labels: C-enhancement,A-diagnostics,T-compiler,D-confusing

Hi, here is an [example of very strange error](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=94a8a50f292d4414c9bf1fcabe99635b) I have stuck with:
```rust
struct Baz {
    pub foo: &'static str
}

trait Foo {
    fn foo() -> &'static str;
}

trait Bar {
    fn bar() -> &'static [Baz];
}

struct Test;

impl Foo for Test {
    fn foo() -> &'static str {
        "Hello, World!"
    }
}

struct Bat {
    test: Test
}

impl Bar for Bat {
    fn bar() -> &'static [Baz] {
        use Foo;

        &[
            /// This compiles 
            {
                Baz { foo: "Hello, World!" }
            },
            
            /// but, this cause an error "cannot return reference to temporary value"
            {
                let foo = "Hello, World!";
                Baz { foo }
            },
            
            /// this cause an error, also
            {
                let foo = Test::foo();
                Baz { foo }
            },
            
            /// and this cause an error, too
            {
                Baz { foo: Test::foo() }
            }
        ]
    }
}
```
and the error message:
```
error[E0515]: cannot return reference to temporary value
  --> src/lib.rs:29:9
   |
29 |            &[
   |  __________^-
   | | _________|
   | ||
30 | ||             /// This compiles 
31 | ||             {
32 | ||                 Baz { foo: "Hello, World!" }
...  ||
50 | ||             }
51 | ||         ]
   | ||         ^
   | ||_________|
   | |__________returns a reference to data owned by the current function
   |            temporary value created here
```
Repository: neovim
Issue: setqflist called from autocmd does not change current qf list
Labels: bug-vim

<!-- Before reporting: search existing issues and check the FAQ. -->

- `nvim --version`: NVIM v0.4.3
- `vim -u DEFAULTS` (version: 8.1, patches 1-2268) behaves the same.
- Operating system/version: Arch Linux
- Terminal name/version: termite v15
- `$TERM`: xterm-termite

### Steps to reproduce using `nvim -u NONE`

```
nvim -u NONE your-project
mistype something to populate qf list
:autocmd QuickFixCmdPost make call setqflist([], "a", {"nr": 2, "items": []})
:make
:cwindow
:chistory
```

### Actual behaviour
After qf list is populated, the autocmd above creates another qf list at index 2. The initial qf list is still selected:

```
> error list 1 of 2; 13 errors    :make
  error list 2 of 2; 0 errors     :setqflist()
```

### Expected behaviour
After qf list is populated, the autocmd above should create another qf list at index 2 and set it as the selected. Like when I call `setqflist` manually after `:make`.
```
  error list 1 of 2; 13 errors    :make
> error list 2 of 2; 0 errors     :setqflist()
```
Repository: material-ui
Issue: [Autocomplete] support pagination on Asynchronous requests
Labels: new feature,component: autocomplete,ready to take

Would be very nice to add any ability for support pagination on Asynchronous requests
Many resources have limitations on requests and we can not get all results at once 
Also reading everything page by page can lead to exceed limit of requests and it will be too slow

We would likely need to extend the API:

```diff
diff --git a/packages/material-ui/src/Autocomplete/Autocomplete.d.ts b/packages/material-ui/src/Autocomplete/Autocomplete.d.ts
index a2929c4867..39fa7130b3 100644
--- a/packages/material-ui/src/Autocomplete/Autocomplete.d.ts
+++ b/packages/material-ui/src/Autocomplete/Autocomplete.d.ts
@@ -143,6 +143,11 @@ export interface AutocompleteProps<
    * @default false
    */
   loading?: boolean;
+  /**
+   * If `true`, the `loadingMoreText` message is displayed at the bottom of the displayed options.
+   * @default false
+   */
+   loadingMore?: boolean;
   /**
    * Text to display when in a loading state.
    *
@@ -150,6 +155,13 @@ export interface AutocompleteProps<
    * @default 'Loading…'
    */
   loadingText?: React.ReactNode;
+  /**
+   * Text to display when in a loading more state.
+   *
+   * For localization purposes, you can use the provided [translations](/guides/localization/).
+   * @default 'Loading more…'
+   */
+  loadingMoreText?: React.ReactNode;
   /**
    * The maximum number of tags that will be visible when not focused.
    * Set `-1` to disable the limit.
```

<img width="457" alt="Capture d’écran 2021-07-24 à 19 24 53" src="https://user-images.githubusercontent.com/3165635/126876529-285878f9-02c5-4983-b4d3-d7630ca4af2f.png">

### Benchmark

- https://github.com/JedWatson/react-select/pull/1237
- https://select2.org/data-sources/ajax#pagination
Repository: godot
Issue: Preview cache is not refreshed after reimport
Labels: bug,topic:editor,confirmed,topic:import

**Godot version:**
3.2 beta1

**Issue description:**
If you change import settings that impact texture ("Invert Color" in my case) the preview is not updated. You can see that it should work, because when you move the texture to another directory it looks correctly.
![yaJpQdcafL](https://user-images.githubusercontent.com/2223172/69177026-1698a300-0b07-11ea-92e4-36367af3f3ee.gif)
It will keep happening until you modify the file, which will refresh the cache.
Repository: vscode
Issue: Web: Comment View should listen to Gesture.Change event to scroll itself
Labels: debt,web,ios-ipados,touch/pointer

* Open Web on iPad OS
* Install GH PR extension
* Leave comments
* Try to use finger to scroll the comment thread, nothing happens.
Repository: rust
Issue: impl Trait cannot work well with lifetime bounds
Labels: C-enhancement,A-lifetimes,T-lang,A-impl-trait

[Playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=8615db4e00b2b417d3041b1caa27acb7)
```rust
pub struct S<'t>(usize, &'t str);

impl<'t> S<'t> {
    // error[E0700]: hidden type for `impl Trait` captures lifetime that does not appear in bounds
    pub fn foo<'s>(&'s mut self) -> impl FnMut() + 's {
        move || self.0 += 1
    }
}

fn main() {
    let mut s = S(0, "hello");
    s.foo()();
    println!("{}", s.0);
}
```

The `self: &'s mut S<'t>` implies `'t: 's`, so the signature should be correct. But compiler still complain that `'t` is captured but does not appear in `impl` bounds.

I checked the [error description of `E0700`](https://doc.rust-lang.org/stable/error-index.html#E0700) and tried `impl FnMut() + 's where 't: 's` and `impl FnMut() + 's + 't`, while it still fails.

Note that when using `dyn Trait` as `pub fn foo<'s>(&'s mut self) -> Box<dyn FnMut() + 's>`, it compiles.
Repository: rust
Issue: const fn in panic=abort land
Labels: A-testsuite,C-enhancement,E-needs-test,T-compiler,A-const-eval

It is untested what happens when const eval panics in panic=abort mode. We should add some tests and fix the implementation as per https://github.com/rust-lang/rust/pull/66507/files#r347262825
Repository: rust
Issue: unused imports should not be fixed from `use foo;\n` to `\n`
Labels: C-enhancement,A-diagnostics,T-compiler,E-help-wanted,A-suggestion-diagnostics,D-papercut,D-invalid-suggestion

Right now rustfix fixes unused imports by removing but instead of replacing an unused import `use foo;\n` with ``, it inserts `\n`. This gets really annoying when you have a single block of imports and it ends up looking "hole punched":

```rust
use crate::archival::libarchive::bb_archive::file_header_t;
use crate::libbb::llist::llist_t;


use crate::librb::bb_uidgid_t;
use crate::librb::fd_pair;
use crate::librb::size_t;
use crate::librb::uoff_t;

use libc;
use libc::close;
use libc::fprintf;
use libc::free;

use libc::gid_t;
use libc::lstat;
use libc::mode_t;
use libc::off_t;
use libc::pid_t;

use libc::printf;
use libc::stat;

use libc::strcpy;
use libc::uid_t;
use libc::FILE;
```
On its own this wouldn't be that big of a deal but since these have now been split into separate import "blocks" rustfmt will no longer condense them.
Repository: rust
Issue: rustc recommends a trait from a crate the current crate doesn't depend on
Labels: A-diagnostics,T-compiler,C-bug,A-suggestion-diagnostics,D-invalid-suggestion,S-has-mcve

I ran into this in a crate that depends directly on `anyhow`, and depends very indirectly on `quick-error`. When trying to use the `context` method, in a case that wouldn't work with `anyhow` because the error type didn't implement Error, rustc said:

```
help: the following trait is implemented but not in scope, perhaps add a `use` for it:
   |
1  | use quick_error::ResultExt;
   |
```

However, since the crate doesn't directly depend on `quick-error`, it can't add such a `use`.

Rough steps to reproduce:

- Have a top-level binary crate that depends on library crates `c1` and `c2`
- Have crate `c1` provide an extension trait with some requirements (such an extension trait on `Result` that places requirements on the error type).
- Have crate `c2` depend on crate `c3`.
- Have crate `c3` provide an extension trait that works on any type.
- Have the top-level binary crate import the extension trait from `c1`, and attempt to use it, but not satisfy the required trait bounds.

This should result in rustc suggesting `use c3::ExtensionTrait` for use in the top-level binary crate, even though the top-level binary crate doesn't depend on `c3`.
Repository: flutter
Issue: [web] Scrolling error in a11y mode in Desktop
Labels: framework,a: accessibility,f: scrolling,platform-web,P2,team-web,triaged-web

Scrolling only works for going down on a list of contents. It does not work for going up.

Tested on: Safari, MacOS, VoiceOver
Repository: flutter
Issue: [web] Toggle error in a11y mode in Desktop Browser
Labels: framework,a: accessibility,platform-web,a: desktop,P2,team-framework,triaged-framework

Toggle widget is announcing the value wrong for a11y. For example for toggle on the value is announced as toggle off.

Tested on: Safari, MacOS, VoiceOver
Repository: flutter
Issue: [web] Live area error in a11y mode in Desktop
Labels: framework,f: material design,a: accessibility,platform-web,a: desktop,P2,team-design,triaged-design

Live areas (such as a toast, dialog) does not receive the a11y focus. The information in those fields will be either impossible (if the toast disappears) or very hard for the assistive technology user to understand.

Tested on: Safari, MacOS, VoiceOver
Repository: flutter
Issue: [web] a11y support for tables
Labels: framework,f: material design,a: accessibility,P2,customer: castaway,team-design,triaged-design

There are many a11y features for [tables](https://dequeuniversity.com/screenreaders/voiceover-keyboard-shortcuts#vo-mac-tables) which includes:

- Read column header 
- Read row
- Read column
- Move up or down in a column
- Move across a row

We should add support for these use cases in Flutter for Web.

https://api.flutter.dev/flutter/widgets/Table-class.html
https://api.flutter.dev/flutter/material/DataTable-class.html
https://api.flutter.dev/flutter/material/PaginatedDataTable-class.html
| OS | role |
|--------|--------|
| web |table |
| ios | - |
| macos |  NSAccessibilityTableRole |
| windows | ROLE_SYSTEM_TABLE |
| android | android.widget.TableLayout | 



https://api.flutter.dev/flutter/widgets/TableRow/children.html
https://api.flutter.dev/flutter/material/DataCell-class.html
| OS | role |
|--------|--------|
| web |cell |
| ios | - |
| macos |  NSAccessibilityCellRole |
| windows | ROLE_SYSTEM_CELL |
| android | - | 


https://api.flutter.dev/flutter/widgets/TableRow-class.html
https://api.flutter.dev/flutter/material/DataRow-class.html
| OS | role |
|--------|--------|
| web |row |
| ios | - |
| macos |  NSAccessibilityGroupRole, NSAccessibilityTableRowSubrole |
| windows | ROLE_SYSTEM_ROW |
| android | android.widget.TableRow | 

https://api.flutter.dev/flutter/material/DataColumn/label.html
| OS | role |
|--------|--------|
| web |columnheader |
| ios | - |
| macos |  NSAccessibilityCellRole |
| windows | ROLE_SYSTEM_COLUMNHEADER |
| android | - |
Repository: flutter
Issue: CupertinoTimerPicker's width should not be fixed
Labels: framework,f: cupertino,c: proposal,P3,team-design,triaged-design

Thank @nikitadol  for pointing out that the native timer picker does not have a fixed width, e.g., when used as the `inputView`, the separators can be as wide as the screen:

 `textField.inputView = UIDatePicker()`

![image](https://user-images.githubusercontent.com/31859944/69198771-beec3e80-0aea-11ea-9c16-fe9da7a89ac4.png)
Repository: flutter
Issue: Suppress clutter in console from Android system messages
Labels: c: new feature,platform-android,tool,P3,team-android,triaged-android


## Use case

The default behavior of the console running on an Android device is to send a set of debug messages every time that a touch event goes high or low. This can often crowd the console, making it difficult to see important information like exceptions or print statements.

The proposed solution [in this SO post](https://stackoverflow.com/questions/56677628/how-do-i-hide-this-message-in-the-flutter-console-viewpostime-pointer-0) involves piping the output of flutter run to grep, but that will not affect starting a debug session in VSCode or Android Studio. 

## Proposal

It would be helpful to add a flag to the `flutter run` command to allow for suppressing these messages and, perhaps, have that enabled by default or otherwise make it so that these messages don't go to the console in an IDE's debugging session.