sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: UI: set_default_colors is missing gui=... attributes
Labels: bug-vim,ui-extensibility,highlight,options

<!-- Before reporting: search existing issues and check the FAQ. -->

- `nvim --version`: NVIM v0.5.0-690-g4d3ef578e

### Steps to reproduce using `nvim -u NORC`

With a UI that has the `ext_linegrid` and `rgb` extensions, use `:hi Normal gui=strikethrough`. Here's a reproducer:

```python
import time
from pynvim import attach
from threading import Thread

interesting_events = []

class UIThread(Thread):
    def __init__(self, nvim):
        Thread.__init__(self)
        self.nvim = nvim
        self.do_print = False
    def run(self):
        self.nvim.run_loop(self.callback, self.callback)
    def callback(self, event_name, events):
        [print(event) for event in events if (event[0] in interesting_events)]

nvim = attach('child', argv=["/home/me/bin/nvim", "--embed", "-u", "NORC", "-i", "NONE", "-c", "set laststatus=0"])
ui = UIThread(nvim)
ui.start()

# Create UI
nvim.async_call(nvim.ui_attach, 12, 2, ext_linegrid = True, rgb = True)

# Wait for setup information to arrive
time.sleep(1)

# Now start logging "hl_attr_define" and "default_colors_set"
interesting_events = interesting_events + ["hl_attr_define", "default_colors_set"]

# Change Normal highlight. This creates a new highlight id
nvim.async_call(nvim.input, ":hi Normal ctermfg=white ctermbg=black cterm=strikethrough guifg=white guibg=black gui=strikethrough")
nvim.async_call(nvim.input, "<Enter>")

# Enter insert mode
nvim.async_call(nvim.input, "a")

# Wait a bit for changes to settle
time.sleep(1)

# Now start logging grid_line too
interesting_events = interesting_events + ["grid_line"]

# Insert character, not striked through!
nvim.async_call(nvim.input, "a")

#Quit
time.sleep(1)
interesting_events = []
nvim.async_call(nvim.input, "<Esc>:qa!<Enter>")
time.sleep(1)
```

### Actual behaviour

UI is not told to strike text through:
```
['hl_attr_define', [58, {'foreground': 0, 'background': 16777215}, {}, []], [59, {'strikethrough': True, 'foreground': 16777215, 'background': 0}, {'strikethrough': True}, []], [60, {'foreground': 0}, {'foreground': 0}, []]]
['default_colors_set', [16777215, 0, 16711680, 16, 1]]
['grid_line', [1, 0, 0, [['a', 0]]], [1, 2, 6, [['1', 1], [','], ['2']]]]
```

### Expected behaviour

UI is told to strike through. This could be implemented in three ways:
1) Grid_lines are sent with the real highlight id instead of "default one".
2) A separate "default_strikethrough_set" event is set to tell the UI that default hl should be striked through.
3) Instead of sending "default_colors_set", nvim sends a "set_default_hl_id" event that tells the UI what hl id should be used to paint when hl ID 0 is found.

@bfredl what solution do you think is best? I think I prefer 1) as it's a simplification but maybe this would cause performance issues by making the rpc messages bigger?
Repository: create-react-app
Issue: react-scripts are not executed correctly
Labels: stale,needs triage

- The standard scripts for create-react-app are no longer running correctly.

- As an example, I needed to access the `start` script directly from node_modules `"node node_modules / react-scripts / scripts / start.js"`.

- The same is happening in the `test` using `jest`.

```json
"scripts": {
    "start": "node node_modules/react-scripts/scripts/start.js",
    "build": "react-scripts build",
    "test": "jest",
    "eject": "react-scripts eject"
  },
```

```json
"devDependencies": {
    "eslint": "6.6.0",
    "eslint-config-airbnb": "^18.2.0",
    "eslint-config-prettier": "^6.11.0",
    "eslint-plugin-import": "^2.22.0",
    "eslint-plugin-jsx-a11y": "^6.3.1",
    "eslint-plugin-react": "^7.20.3",
    "eslint-plugin-react-hooks": "^4.0.8",
    "jest": "24.9.0",
    "prettier": "^2.0.5"
  }
```

![image](https://user-images.githubusercontent.com/36301054/95021860-023f9500-064a-11eb-9a4e-b94533276b73.png)

- [GitHub Project](https://github.com/zehguilherme/personal-curriculum)
Repository: javascript
Issue: JSX is not displayed correctly in webpage
Labels: pull request wanted,editorial,react

## Description
- The JSX example is not correctly displayed in the webpage, there is no problem with the Readme file though

## Screenshot
![image](https://user-images.githubusercontent.com/49222186/95022085-959cb880-0692-11eb-956c-e7df32b5cd6c.png)

## Reason
I think the markdown to HTML convertor is what causing the issue
Repository: rust
Issue: Don't redirect doc.rust-lang.org to www.rust-lang.org/learn
Labels: C-enhancement,A-docs,T-infra

I assume it's for some kind of backwards-compatibility, but frequently I forget to add `/std` and I have to re-type the URL. Also it would be nice to have a listing at doc.rust-lang.org/ of all the documentation hosted there:

- libraries: `std`, `core`, `alloc`, `proc_macro`, `test`, others?
- compiler: `nightly-rustc`
- books
  - the book
  - the unstable book
  - the nomicon
  - the rustdoc book
  - etc.
Repository: pytorch
Issue: Traceback for "Warning: Mixed memory format inputs detected while calling the operator."
Labels: triaged,module: memory format

## 🚀 Feature
Please add a traceback for this type of warnings:


> [W TensorIterator.cpp:924] Warning: Mixed memory format inputs detected while calling the operator. The operator will output channels_last tensor even if some of the inputs are not in channels_last format. (function operator())
> [W TensorIterator.cpp:918] Warning: Mixed memory format inputs detected while calling the operator. The operator will output contiguous tensor even if some of the inputs are in channels_last format. (function operator())

It's just too hard to find the issue in the code (especially in large codebases). 

I tried adding a traceback, as suggested on Stack Overflow, but it didn't show any further information:

```python
import traceback
import warnings
import sys

def warn_with_traceback(message, category, filename, lineno, file=None, line=None):

    log = file if hasattr(file,'write') else sys.stderr
    traceback.print_stack(file=log)
    log.write(warnings.formatwarning(message, category, filename, lineno, line))

warnings.showwarning = warn_with_traceback 
```

Thank you very much



cc @VitalyFedyunin @jamesr66a @ppwwyyxx
Repository: TypeScript
Issue: Union with non-distinct discriminating property breaks inference somewhat (confusing error messages, invalid intellisense)
Labels: Domain: Error Messages,Experience Enhancement

<!-- 🚨 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.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** discriminated union, error messages

**Code**

```ts
type Action = {
    type: 'action1';
    payload: {
        property1: string;
    };
} | {
    type: 'action1';
    payload: {
        property2: number;
    };
} | {
    type: 'action2';
    payload: {
        property3: boolean;
    };
}

const action: Action = { // Actual error is here
    type: 'action1',
    payload: {
        property3: true // Expected error here
    }
}
```

**Expected behavior:**

Expected error at `action.payload.property3` declaration, perhaps something like:

```
Object literal may only specify known properties, and 'property3' does not exist in type '{ property1: string; } | { property2: number; }'.
```

Also, once the object has been refined by the type `action1`, intellisense should only provide `property1` and `property2` as a suggestion when declaring the `payload`.

**Actual behavior:**

An error message at the first line of the declaration: 

```
Type '{ type: "action1"; payload: { property3: true; }; }' is not assignable to type 'Action'.
  Type '{ type: "action1"; payload: { property3: true; }; }' is not assignable to type '{ type: "action2"; payload: { property3: boolean; }; }'.o
      Type '"action1"' is not assignable to type '"action2"'.(2322)
```

Also, once the object has been refined by the type `action1`, intellisense still provides `property3` as a suggestion when declaring the `payload`.

**Playground Link:** https://www.typescriptlang.org/play?#code/C4TwDgpgBAggxsAlgewHZQLxQN4CgoFSiQBcUA5AIYIqoCM5A3PoWJSADbKUAmZehQVDAAnZJBGg6ZAM7ARiVAHNmggL7M1UAD44WBYhDJUaaBqtbsuvfvqGjxESSABMZVAFcAtgCMnFgg1cLV0BQkNjaiQ0FyY7Nk5uPj0hVjEJUABmMh9kZA4ISlQAqCC1XFw4NDkoKNoyeGj0LDCDcCMKOrNyABp4qyTbVIIHDJBsohEPCDtytSA
Repository: rust
Issue: std::process::exit() on MSVC bypasses writing LLVM InstrProf counters to profraw file
Labels: O-windows-msvc,C-bug,A-code-coverage,A-process

This bug does not occur on Linux or MacOS.

Note that I observed this unexpected behavior when compiling on Windows, targeting MSVC.

I have not confirmed the behavior on Windows targeting GNU.

The minimal reproducible example (MRE) here shows the problem even when returning a success status code (`0`), and while a Rust program will generate a `0` status for programs that return a `Result::OK` or a `()`, and a `1` status for programs that return `Result::Err`, as far as I know, we need to call `std::process::exit(...)` to return any other status code.

Therefore, any program that requires the ability to return a status other than `0` or `1` may get empty, or worse, incomplete, coverage results when testing coverage under MSVC.

I tried this code:

```rust
fn main() {
    std::process::exit(0);
}
```

```shell
$ build/x86_64-pc-windows-msvc/stage1/bin/rustc.exe -Zinstrument-coverage basic.rs
$ LLVM_PROFILE_FILE=basic.profraw ./basic.exe
$ ls -l basic.profraw
-rw-r--r-- 1 richkadel Domain Users 0 Oct  4 15:32 basic.profraw
```

I expected to see this happen: *The same result as on Linux and MacOS, and the same result that I get if the call to `std::process::exit(0)` is removed. In both cases, the `basic.profraw` file size is greater than `0`. In the working cases, the non-empty `basic.profraw` file can be used with `llvm-profdata` and `llvm-cov` tools to generate and view coverage reports.*

Here is the expected result on Linux, for example:

```shell
$ build/x86_64-unknown-linux-gnu/llvm/bin/llvm-profdata merge -sparse basic.profraw -o basic.profdata
$ build/x86_64-unknown-linux-gnu/llvm/bin/llvm-cov show --instr-profile=basic.profdata basic
    1|      1|fn main() {
    2|      1|    std::process::exit(0);
    3|      1|}
```

Instead, this happened: *The `basic.profraw` file size is `0` (as shown in the example above). LLVM coverage reports show no results.*

### Meta

```shell
./build/x86_64-unknown-linux-gnu/stage1/bin/rustc --version --verbose
rustc 1.49.0-dev
binary: rustc
commit-hash: unknown
commit-date: unknown
host: x86_64-unknown-linux-gnu
release: 1.49.0-dev
LLVM version: 11.0
```
Repository: scrcpy
Issue: [Linux] scrcpy freezes when minimized
Labels: obs

 - [x] I have read the [FAQ](https://github.com/Genymobile/scrcpy/blob/master/FAQ.md).
 - [x] I have searched in existing [issues](https://github.com/Genymobile/scrcpy/issues).

**Environment**
 - OS: Ubuntu 20.04.1 LTS x86_64
 - scrcpy version:

```
scrcpy 1.16

dependencies:
 - SDL 2.0.8
 - libavcodec 57.107.100
 - libavformat 57.83.100
 - libavutil 55.78.100
```

 - installation method: snap
 - device model: Xiaomi Redmi Note 8
 - Android version: 10

**Describe the bug**
When the scrcpy window is minimized, scrcpy is frozen and doesn't update the screen. (I have it minimized for adding scrcpy as a scene with OBS).

```
INFO: scrcpy 1.16 <https://github.com/Genymobile/scrcpy>
/usr/local/share/scrcpy/scrcpy-server:...shed. 0.1 MB/s (33622 bytes in 0.621s)
/usr/share/libdrm/amdgpu.ids: No such file or directory
[server] INFO: Device: Xiaomi Redmi Note 8 (Android 10)
INFO: Renderer: opengl
INFO: OpenGL version: 4.6 (Compatibility Profile) Mesa 20.0.8
INFO: Trilinear filtering enabled
INFO: Initial texture: 1080x2336
[nothing else is printed]
```
Repository: PowerToys
Issue: [FancyZones] detect / support unconventional dragging of Windows in some programs
Labels: Idea-Enhancement,Help Wanted,Product-FancyZones,Issue-DCR

## 📝 Provide a description of the new feature

_What is the expected behavior of the proposed feature?  What is the scenario this would be used?_
Programs such as IBKR TWS have custom window formats and their dragging doesn't get registered by PowerToys and so they don't snap into FancyZones. 

FancyZones are probably the most used feature of PowerToys. Adding "unconventional window drag" support will do a lot of good.

I would be able to do some tests if someone can tell me how to get Debug running. IBKR TWS could be having exactly the same issue as explained in: https://github.com/microsoft/PowerToys/issues/2634 which is probably missing the bolded START and END lines. The center line "LocationChange" still happens but PowerToys would not like to change the window dragging handler to work based on just "LocationChange" (not sure about the reason):
**1 event 0x000A EVENT_SYSTEM_MOVESIZESTART**
several events 0x800B EVENT_OBJECT_LOCATIONCHANGE
**1 event 0x000B EVENT_SYSTEM_MOVESIZEEND**

My suggestion:
PowerToys should add a Custom Drag "enable/disable" button that enables the "custom" window drag handler that allows for programs that do not conform to get snapped as well. This feature will be OFF by default and only is only enabled when needed.

Reference:
https://github.com/microsoft/PowerToys/issues/6631#issuecomment-703079137
https://github.com/microsoft/PowerToys/issues/6771#issuecomment-703029271
Repository: youtube-dl
Issue: Voot premium Videos Download Failed
Labels: site-support-request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->
Voot Videos Download failed

## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2020.09.20. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2020.09.20**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [ ] I've checked that none of provided URLs violate any copyrights
- [ ] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->



## Description

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.



C:\Users\Babin Mondal>cd downloads

C:\Users\Babin Mondal\Downloads>cd youtube-dl

C:\Users\Babin Mondal\Downloads\youtube-dl>youtube-dl https://www.voot.com/shows/bigg-boss/14/978245/bigg-boss-new-episode/1002225
[Voot] 1002225: Downloading JSON metadata
[Voot] 1002225: Downloading m3u8 information
ERROR: Failed to download m3u8 information: HTTP Error 404: Not Found (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

C:\Users\Babin Mondal\Downloads\youtube-dl>

WRITE DESCRIPTION HERE
Repository: flutter
Issue: TextField TextInputType "name" overrides TextCapitalization "words"
Labels: a: text input,platform-ios,framework,f: material design,has reproducible steps,P2,found in release: 3.3,found in release: 3.7,team-framework,triaged-framework

It appears that `TextField`'s `keyboardType` of `name` prevents the iOS keyboard from offering capital letters at the beginning of words, even when specifying `textCapitalization: TextCapitalization.words`.

Repro:
```
TextField(
  keyboardType: TextInputType.name,
  textCapitalization: TextCapitalization.words,
);
```

**Expected result:**
When the user selects the `TextField`, the keyboard pops up with uppercase characters.

**Actual result:**
When the user selects the `TextField`, the keyboard pops up with lowercase character.

This same issue might happen on Android but I haven't looked.

**Flutter version:**
```
Flutter 1.22.0-10.0.pre.9 • channel master • https://github.com/flutter/flutter.git
Framework • revision 8fa5c55e54 (5 weeks ago) • 2020-08-30 19:05:20 -0700
Engine • revision 1e302a111d
Tools • Dart 2.10.0 (build 2.10.0-76.0.dev)
```
Repository: flutter
Issue: Make "fields" in FormState not a private member
Labels: a: text input,framework,c: proposal,P3,team-framework,triaged-framework

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

I want to implement feature that when form validated fail scroll to that FormField.

currently I implement with copy `form.dart` file  and change `_field` to `field` to make it public

and do some validation like [document](https://flutter.dev/docs/cookbook/forms/validation) said

and scroll to specify field with 

```dart
formKey.currentState.validate();
Scrollable.ensureVisible(formKey.currentState.fields.first.context,
        duration: Duration(milliseconds: 500));
```

## Proposal

<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->
form.dart
```dart
...
class FormState extends State<Form> {
  int _generation = 0;
  final Set<FormFieldState<dynamic>> fields = <FormFieldState<dynamic>>{};
...
```


What do you think ?

Thank you.
Repository: angular
Issue: Syntax errors in template tags are not caught by the compiler
Labels: type: bug/fix,area: compiler,P4,compiler: parser

# 🐞 bug report

### Affected Package
The issue is caused by Angular Compiler (unsure which package tbh).

### Is this a regression?

Not sure.

### Description

If there is a syntax error in a tag in a template outside of property bindings/event bindings/html attributes, such as a forgotten semicolon, the compiler won't notify the user about that syntax error. Instead, the malformed code slips to the build and appears in the runtime as an error with cryptic message.


## 🔬 Minimal Reproduction
https://stackblitz.com/edit/angular-ivy-ifdubu?file=src%2Fapp%2Fapp.component.html

## 🔥 Exception or Error
<pre><code>
core.js:6241 ERROR Error: Uncaught (in promise): InvalidCharacterError: Failed to execute 'setAttribute' on 'Element': ';' is not a valid attribute name.
Error: Failed to execute 'setAttribute' on 'Element': ';' is not a valid attribute name.
    at EmulatedEncapsulationDomRenderer2.setAttribute (platform-browser.js:1203)
    at BaseAnimationRenderer.setAttribute (animations.js:596)
    at setUpAttributes (core.js:5111)
    at Module.ɵɵelementStart (core.js:21281)
    at InternalDocumentComponent_Template (internal-document.component.html:5)
    at executeTemplate (core.js:12169)
    at renderView (core.js:11939)
    at renderComponent (core.js:13518)
    at renderChildComponents (core.js:11740)
    at renderView (core.js:11965)
    at resolvePromise (zone-evergreen.js:798)
    at resolvePromise (zone-evergreen.js:750)
    at zone-evergreen.js:860
    at ZoneDelegate.invokeTask (zone-evergreen.js:399)
    at Object.onInvokeTask (core.js:41645)
    at ZoneDelegate.invokeTask (zone-evergreen.js:398)
    at Zone.runTask (zone-evergreen.js:167)
    at drainMicroTaskQueue (zone-evergreen.js:569)
    at ZoneTask.invokeTask [as invoke] (zone-evergreen.js:484)
    at invokeTask (zone-evergreen.js:1621)
</code></pre>


## 🌍  Your Environment

**Angular Version:**
<pre><code>
Angular CLI: 9.1.12
Node: 12.16.2
OS: darwin x64

Angular: 9.1.12
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Ivy Workspace: Yes

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.901.12
@angular-devkit/build-angular     0.901.12
@angular-devkit/build-optimizer   0.901.12
@angular-devkit/build-webpack     0.901.12
@angular-devkit/core              9.1.12
@angular-devkit/schematics        9.1.12
@angular/cdk                      9.2.4
@angular/material                 9.2.4
@ngtools/webpack                  9.1.12
@schematics/angular               9.1.12
@schematics/update                0.901.12
rxjs                              6.6.3
typescript                        3.8.3
webpack                           4.42.0
</code></pre>

**Anything else relevant?**

Nope.