sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: create-react-app
Issue: eslint-config-react-app is not respecting "no-unused-vars" rule when variable name is h1, div etc.
Labels: needs triage,issue: bug report

### Describe the bug

eslint-config-react-app is not respecting "no-unused-vars" rule if the variable name is same as HTML Intristic elements used in the same component. 

### Did you try recovering your dependencies?
Yes

### Environment
Devlopment

### Steps to reproduce
In project root run below command
`npm run lint`

### Expected behavior
It should show `h1` & `div` is unused

### Actual behavior
It shows no lint errors

### Reproducible demo
https://codesandbox.io/s/silent-leaf-vv3vt?file=/src/App.tsx
Repository: youtube-dl
Issue: Support for Funimation LATAM (Portuguese (Brazil), Spanish)
Labels: site-support-request

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## 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 2021.02.22. 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 **2021.02.22**
- [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


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single video: https://www.funimation.com/pt-br/shows/akudama-drive/se7en/simulcast/?lang=japanese&qid=
- Anime page: https://www.funimation.com/pt-br/shows/akudama-drive/?qid=


## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

The video works fine while using Chrome but after trying to download the content with Youtube-DL, it returns the "Unsupported URL" error.
Repository: vscode
Issue: Issue reporter should let me create a draft issue on github, even when signed in
Labels: feature-request,issue-reporter


Issue Type: <b>Feature Request</b>

1. Sign in with github
1. Open issue reporter

**Feature Request**
There is currently only a `create on github` button. I'd like an button that lets me create an issue using the issue reporter's previous flow, which started with a draft issue instead. This is useful if you need to upload images to an issue or generally like filling in the issue on github instead 

VS Code version: Code - Insiders 1.54.0-insider (c47da720f351455681978a48edc4d9a0d095ea0e, 2021-02-24T12:22:35.736Z)
OS version: Darwin x64 20.3.0


<!-- generated by issue reporter -->
Repository: go
Issue: x/tools/gopls: apply internal rules to packages named internal
Labels: FeatureRequest,gopls,Tools,gopls/analysis

![image](https://user-images.githubusercontent.com/10288044/109117883-8c190780-777d-11eb-9f82-4f6494b7222e.png)

```bash
╰─$ gopls version                                                                                                                                                                                                                                                                                                       2 ↵
golang.org/x/tools/gopls v0.6.6
    golang.org/x/tools/gopls@v0.6.6 h1:GmCsAKZMEb1BD1BTWnQrMyx4FmNThlEsmuFiJbLBXio=
```
Repository: vscode
Issue: Diff editor scrolls horizontally when dragging selection vertically
Labels: bug,editor-rendering

This bug has probably been around forever, funny how it doesn't show up often.

![recording (4)](https://user-images.githubusercontent.com/22350/109131013-36097d00-7707-11eb-8b9c-344dc41da8c6.gif)
Repository: create-react-app
Issue: react-error-overlay breaks code hot reload throwing `Expected options to be injected.` error when `stopReportingRuntimeErrors` was used
Labels: needs triage,issue: bug report

### Describe the bug

Calling `stopReportingRuntimeErrors` from `react-error-overlay` produces `Expected options to be injected.` error wich breaks hot reload. Error overlay does not show up on errors as expected but when any change done in code - `Expected options to be injected.` shows up in console and hot reload is broken

### Steps to reproduce

1. Call `stopReportingRuntimeErrors` from `react-error-overlay` package at the beginning of the project ike this:
```js
import { stopReportingRuntimeErrors } from "react-error-overlay";

if (process.env.NODE_ENV === "development") {
  stopReportingRuntimeErrors();
}
```
2. Then make any changes in code

### Expected behavior

Hot reload is working and updating bundle

### Actual behavior

Error is thrown in console `Expected options to be injected.` and hot reload is broken.

### Investigation

By investigating the source code it looks like that `stopReportingRuntimeErrors` is setting `currentRuntimeErrorOptions  = null` here: https://github.com/facebook/create-react-app/blob/master/packages/react-error-overlay/src/index.js#L116
while `updateIframeContent` function has check for it which throws an error: https://github.com/facebook/create-react-app/blob/master/packages/react-error-overlay/src/index.js#L158
I'm wondering does this check makes sense there ? I don't see `currentRuntimeErrorOptions` is used in scope of `updateIframeContent` function.
Repository: rust
Issue: Rustc Confuses Associated Types on Type Inference
Labels: A-trait-system,A-associated-items,T-compiler,C-bug

The following code does not compile ([playground link](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=4ca706e8932e3fb5f4309389473554ee)):

```rust
pub trait Trait {
	type Value;
	type AccountId: Default;
}

pub enum A<T: Trait> {
	_C(
		(T::AccountId, T::AccountId),
	),
}

impl<T: Trait> A<T>
where
	(T::Value, T::Value): Default,
{
	fn foo() -> Self {
		A::_C(Default::default())
	}
}
```

I expected to see this happen: Successful compilation

Instead, this happened: I get `E0271`
```
error[E0271]: type mismatch resolving `<T as Trait>::AccountId == <T as Trait>::Value`
  --> src/lib.rs:17:3
   |
17 |         A::_C(Default::default())
   |         ^^^^^^^^^^^^^^^^^^^^^^^^^ expected Trait::AccountId, found Trait::Value
   |
   = note: expected associated type `<T as Trait>::AccountId`
              found associated type `<T as Trait>::Value`
```
Ways to get this to compile (that shouldn't matter/don't change the semantics):
+ remove the `where` bound
+ use explicit call to default `<(T::AccountId, T::AccountId)>::default()` 

### Meta
`rustc --version --verbose`:
```
rustc 1.50.0 (cb75ad5db 2021-02-10)
binary: rustc
commit-hash: cb75ad5db02783e8b0222fee363c5f63f7e2cf5b
commit-date: 2021-02-10
host: x86_64-unknown-linux-gnu
release: 1.50.0
```
(also happens on 1.52-nightly)
Repository: storybook
Issue: Display Typescript type "lowest level"
Labels: feature request,vue,typescript

**Describe the bug**
In the UI, in the description column of the table, the type that's written in the name of the type 'as is', instead of its value.

**To Reproduce**
1. Create Vue+TS+Storybook project
2. Create a new component
3. Create prop to the new component with typescript type
4. Create a story for the component
5. Look at the description column of the prop

**Expected behavior**
I'd expect to be able to choose between the alias of the type \ its value

**Screenshots**
![image](https://user-images.githubusercontent.com/38460810/109141031-ee660e00-7765-11eb-8ba8-1f258235a60a.png)
![image](https://user-images.githubusercontent.com/38460810/109141063-f756df80-7765-11eb-989e-a94dae36d11b.png)
![image](https://user-images.githubusercontent.com/38460810/109141079-fcb42a00-7765-11eb-81df-7182a549ed16.png)

**Code snippets**
`type Placement = 'bottom' | 'top'`
`props: { placemenet: { type: String as Prop<Placement > } }`
in the description box we will see `Placement` instead of `'bottom' | 'top'`

**System**
System:
  OS: Windows 10 10.0.19041
  CPU: (8) x64 Intel(R) Core(TM) i7-1065G7 CPU @ 1.30GHz
Binaries:
  Node: 12.15.0 - C:\Program Files\nodejs\node.EXE
  npm: 6.13.4 - C:\Program Files\nodejs\npm.CMD
Browsers:
  Chrome: 88.0.4324.182
  Edge: Spartan (44.19041.423.0), Chromium (88.0.705.74)
npmPackages:
  @storybook/addon-essentials: 6.1.17 => 6.1.17
  @storybook/addon-links: 6.1.17 => 6.1.17
  @storybook/vue: 6.1.17 => 6.1.17
Repository: next.js
Issue: Rewrites to public folder not working in production with basepath and i18n
Labels: bug,Navigation,Internationalization (i18n)

**What version of Next.js are you using?**

10.0.7

**What version of Node.js are you using?**

14.6.0

**What browser are you using?**

Chrome

**What operating system are you using?**

macOS

**How are you deploying your application?**

next start

**Describe the Bug**

I'm hosting a cms-SPA in my public folder, and I'm trying to make rewrites in next.config.js work. We have some i18n-config and a basepath which complicates things. It works in development mode, but when I run next build & next start the rewrite doesn't work anymore. Could this be a bug in next start?

**Expected Behavior**

When I've set up the rewrite, have ran `next build` & `next start` and go to `localhost/basepath/cms` I want next to deliver me the cms-SPA which is hosted in the publicfolder.

**To Reproduce**

I've made a minimal repo that reproduces the problem here: https://github.com/winsvold/bug-reproduction-nextjs-rewrite

File structure:
```
- pages
  * index.js
- public
  - cms
    * index.html
    * code.js
next.config.js
```

next.config.js:
```
module.exports = {
    basePath: '/basepath',
    rewrites: () => [
        {source: "/no/cms/:path*", destination: "/cms/index.html", locale: false}
    ],
    i18n: {
        locales: ["no", "en"],
        defaultLocale: "no",
    },
}
```

When I go to /basepath/cms in development the rewrite works nicely
When I go to /basepath/cms in production I get 404 - not found
Repository: TypeScript
Issue: Error messaging improvements when accidentally missing an = in JSX attributes
Labels: Suggestion,Experience Enhancement

# Bug Report

I think we could give better errors when you miss an `=` between JSX attributes. Coming from [this tweet](https://twitter.com/Jordy_vD_/status/1364880932642119680). 

### 🔎 Search Terms

JSX spread expected attribute 

### 🕗 Version & Regression Information

N/A - Tested in nightly

### ⏯ Playground Link

```ts
import React from "react"

const shouldDisable = true
const b = () => {
    <div aria-disabled {shouldDisable} />
//                      ^^^^^^^^^^^^^ error: '...' expected.(1005)
}
```

The gist is that TypeScript thinks you will always be using `{thing}` as a spread `{...thing}` - but it's also just possible that you missed the `=`. In this case specifically, `shouldDisable` is a boolean, which can never spread.

Two ways we could safely improve:

Checking the type of the value in the `{ }`:

```ts
// In this case `aria-disabled` is a boolean, and so including it here defaults to 'true' (and doesn't error)

// shouldDisable is a boolean which can never spread like current error: '...' expected.(1005)
// TS could check if token before is a jsx identifier and then recommend to add the `=`
// error: "'shouldDisable' cannot be spread, did you mean to write 'aria-disabled={shoudlDisable}"?
const shouldDisable = true
const b = () => {
    <div aria-disabled {shouldDisable} />
}

```

Checking whether the identifier matches an attribute:

```ts
import React from "react"
const onFocus = () => {}

// onFocus known to be function, so this 2nd error:  '...' expected.(1005)
// TS could first look to see if there's an attribute with the same name and recommend:
// error: "'onFocus' is not being used to spread inside the JSX element, did you mean to write 'onFocus={onFocus}"?
const a = () => {
    <div onFocus {onFocus} />
}


```

[Workbench Repro](https://www.typescriptlang.org/dev/bug-workbench/?#code/JYWwDg9gTgLgBAJQKYEMDG8BmUIjgIilQ3wCg0IA7AZ3ioDEI0BXauAXjgAoBKDgPjgBvAL6lSAeglwGTVnADWlCAHdKcGBDgAjJHEzNKGYFQA0calpgALYGwBMlACZwkUHFABccOAHIAdIG+rgAeYEgYSE7+XACMAAzxAKw8ktIAKgDKcBTMADYumMBQtHB5EBAKGlrUSHrAmBrWbki+bCjqKDAwUMDazDB6KsA2TXrUKCB6lJN6HS5EFCBTzp5pru7Q3vi+sizUwXZwyvC6wJQA5nCsUdUWYEQoLufUwE56NnoAUpkAGq55JArGDmJxvOAATwgzDgUw6dxUvUGfj2rHYQlR1BE+AA-OQqKUUBxuHx2IIhKQfD4ADxggBuMkojH2wkxIjgEn4pDE6wAkuobEc0ChanAAAYoXooAC0YIm2kBTjFcCORO0FUBHXM8wsWnOaDyzDBlxV8GaRDg70wKHyMDYmj8PWYrXEUgs1mhBQAInYUAr6u0dBrUOoVLY0NYcvDKEg6W57o8XHlgAo9Cx3EhKPA3B5vAEgqFwpFonFEil1lkcp6XBGIlUGtVU+pdJhoAG4ESAFbUEIq95ZhrAeM6z7qRa4FYuB1PKfNcXsMXrHNbAhtD35Jw++WA4LCygnHTjB6oJyg8FQmFwgVaREjPS+SXAGVyv2K9HUddOPJb19IbF4igaHgD9qx-f1iSdJB8SAnRiV4ARhEpKlaWABlH2fX1-RcIQQI3MDAXZTluVIIA)


### 🙁 Actual behavior

It's always an error and assumed to be a spread but without the spread

### 🙂 Expected behavior

It'd still be an error, but it could be an error which provides the next step.
Repository: vue
Issue: `.once` modifier on input event prevents v-model from updating value on input element.
Labels: bug

### Version
2.6.11

### Reproduction link
[https://jsfiddle.net/fxdez9qh/](https://jsfiddle.net/fxdez9qh/)







### Steps to reproduce
Type some text in the input field.

### What is expected?
The input handler is executed and the value in the input is updated.

### What is actually happening?
The input handler is executed but the first update to the model is not applied. This means the first character typed will not show up.

---
I found this issue: https://github.com/vuejs/vue/issues/6552 It's a few years old and it was fixed but it seems to be the same problem.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: storybook
Issue: Storybook Docs won't render ArgsTable from proptypes
Labels: react,block: argstable

**Describe the bug**
Past few weeks I've been working on creating a component library using storybook 6.1.2 and webpack 5. However, Storybook won't generate the Argstable from the proptypes i've defined for each of the components.

**To Reproduce**
I'm using sb6.1.20, webpack5, emotion css and tailwind. 
I setup my stories as described in the Storybook docs:

```
export default {
  title: 'Components/Button',
  component: Button,
}

export const DefaultButton = (args) => <Button {...args}>Button</Button>
```

Also I tried setting it up with controls like this:
```
export default {
  title: 'Components/Button',
  component: Button,
}

const Template = (args) => <Button {...args}>Button</Button>

export const DefaultButton = Template.bind({})
DefaultButton.args = {
  primary: false,
  disabled: false,
  small: false,
  fullWidth: false,
  to: '',
}
```

**Expected behavior & screenshots**
I was hoping for something pretty like this:
![storybook example](https://storybook.js.org/e06054348ff0d9b06b93b5031a4fbb7d/button-story-default-docs-code.png)
But instead I got something like this:
![Screenshot](https://user-images.githubusercontent.com/17950354/109172172-c507ab00-7782-11eb-929d-531a50d454ef.png)
And with controls setup i got this:
![Screenshot 2021-02-25 at 16 04 14](https://user-images.githubusercontent.com/17950354/109172663-4fe8a580-7783-11eb-8928-240e87a53276.png)

**System**
  System:
    OS: macOS 11.1
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 12.20.1 - ~/.nvm/versions/node/v12.20.1/bin/node
    Yarn: 1.22.10 - ~/.nvm/versions/node/v12.20.1/bin/yarn
    npm: 6.14.10 - ~/.nvm/versions/node/v12.20.1/bin/npm
  Browsers:
    Chrome: 88.0.4324.192
    Firefox: 85.0.2
    Safari: 14.0.2
  npmPackages:
    @storybook/addon-actions: ^6.1.20 => 6.1.20 
    @storybook/addon-docs: ^6.1.18 => 6.1.20 
    @storybook/addon-essentials: ^6.1.15 => 6.1.20 
    @storybook/addon-links: ^6.1.15 => 6.1.20 
    @storybook/addons: ^6.1.18 => 6.1.20 
    @storybook/react: ^6.1.15 => 6.1.20 
    @storybook/theming: ^6.1.18 => 6.1.20
Repository: react
Issue: Component summary view by type
Labels: Type: Feature Request,Component: Developer Tools,Resolution: Stale

A DevTools user has requested the following feature (reworded by me):
Expose an ordered table of all component types (names) along with the number of instances currently mounted. This would help identify the most impactful components to examine for memory related optimizations.

The Profiler isn't very useful in this scenario because it's too CPU-centric.

cc @yungsters
Repository: vscode
Issue: Flutter apps crash due to old core16 gdk-pixbuf loaders in snap
Labels: bug,help wanted,linux,snap

See: https://github.com/flutter/flutter/issues/73611#issuecomment-785410480

**Setup:**

- VS Code Version: 1.53.2 (snap)
- OS Version: Ubuntu 20.04

**Steps to Reproduce:**

1. Install Flutter using the "manual" method:
https://flutter.dev/docs/get-started/install/linux#install-flutter-manually
2. Create a Flutter app:
```
flutter channel dev
flutter upgrade
flutter config --enable-linux-desktop
flutter create my_app
```
3. Install the Dart Code extension.
4. Open the my_app directory you created in step 2.
5. Navigate to /lib/main.dart, and click "Run" above void main().
Repository: flutter
Issue: Windows: Add option to use Direct Composition for presenting flutter surface
Labels: engine,platform-windows,a: desktop,P3,team-windows,triaged-windows

Using direct composition allows the top level window to be created with `WS_EX_NOREDIRECTIONBITMAP` flag, which gets rid of redirection bitmap, reducing memory usage and increasing performance. This potentially also allows for blur effect behind flutter view. 

This should be an opt-in, because direct composition is not available on Windows 7.
Repository: create-react-app
Issue: Rename env-var "build-path" -> it deletes all projects for us because already existing
Labels: issue: proposal,needs triage

In our company we have already an environment variable named build-path pointing to D:\build and inside there are all projects. We are starting using react and npm. We are using this since one year. Yesterday we want to create a new app and start with 

npx create-react-app someapp

and 

npm run build

and after this all projects on D:\build were missing. Before we were using Version 4.0.0 and everthing was fine.

Please rename this environment variable, this name is not dedecating enough.
The approach using .env with build_path=somethingElse doesn't work because it only works if the environment variable doens't exist, so you are not even able to override global settings (env var) with local settings (.env).
Repository: react
Issue: React throws many fake errors when warnings are issued
Labels: Type: Discussion

In describeNativeComponentFrame, the component rendering is intentionally failed so that we can gather details from the stack trace for some warnings. The Chrome dev tools will break on every single one of these, sometimes more than once. We have many, many components in our call stack before the warning is triggered, throwing many false errors, making it very difficult for us to use the dev tools to investigate unrelated errors when the warnings are present.

React version: 17.0.1

1. Create a simple minimal React page.
2. Render a simple "hello world" component with a warning.
3. Open the Chrome dev tools, click break on all exceptions with caught exceptions, and then reload the page.

Link to code example:

https://github.com/markboyall/react-break-example

The current behaviour is that it breaks once per component in the stack frame, causing an unmanageable number of fake breaks. The expected behaviour is that React does not interfere with the browser dev tools can be used to debug our own code.

Previous versions of React could issue warnings with one break at the warning site only at most, which was an acceptable tradeoff.
Repository: pytorch
Issue: [feature request] F.interpolate_as
Labels: module: nn,triaged,function request,module: interpolation

To make easier computation of shape parameter for `F.interpolate`

I stumbled on this need when coding an auto-encoder (given that padding / strides are hard to compute properly)

cc @albanD @mruberry @jbschlosser
Repository: rust
Issue: -crt-static on musl links with libgcc_s
Labels: A-linkage,T-compiler,O-musl,C-bug

Hi, I am building dynamic libraries that I call from scripting languages (elixir nif, nodejs native addon, etc) on Alpine Linux. I have been successful using the `x86_64-unknown-linux-musl` target with `-C target-feature=-crt-static` to enable building `cdylib`s. However, I find that any `cdylib` produced this way links dynamically not only to `musl` but also to `libgcc_s`:

```
$ ldd target/release/libhello.so
/lib/ld-musl-x86_64.so.1 (0x7ffa2d2fb000)
libgcc_s.so.1 => /usr/lib/libgcc_s.so.1 (0x7ffa2d1cd000)
libc.musl-x86_64.so.1 => /lib/ld-musl-x86_64.so.1 (0x7ffa2d2fb000)
```

Unfortunately, the Alpine Linux docker image does not include the `libgcc` package by default, and the packages for most scripting languages do not depend on it, so users of my library will be required to explicitly install it, which is an inconvenience.

Below is the line in the `unwind` crate that dynamically links to `libgcc_s` on `musl` targets when `crt-static` is disabled:
https://github.com/rust-lang/rust/blob/b36f77012dcbfbcf7d04e29fb9a10c8ead9b3ab1/library/unwind/src/lib.rs#L41

Is there a path to compiling `cdylib`s for `musl` without dynamically linking to `libgcc_s`? Perhaps while unwinding across FFI boundaries remains undefined behavior, `-crt-static` on `musl` could statically link the unwind functionality like it does with `+crt-static`?

Related issues:
https://github.com/rust-lang/rust/issues/29527
https://github.com/rust-lang/rust/issues/55120

`rustc --version --verbose`:
```
rustc 1.50.0 (cb75ad5db 2021-02-10)
binary: rustc
commit-hash: cb75ad5db02783e8b0222fee363c5f63f7e2cf5b
commit-date: 2021-02-10
host: x86_64-unknown-linux-musl
release: 1.50.0
```
Repository: PowerToys
Issue: Move Cpp.Build.props and Directory.Build.props out of root dir
Labels: Area-Build

These two files should be moved out of the root directory.

`src` i'd imagine is the appropriate directory