sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react
Issue: Bug: autoFocus broken inside <dialog /> 
Labels: Type: Bug

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: 17 and 18.0.0-rc.0-next-27b569969-20220211

## Steps To Reproduce

1. render `<input /><input autoFocus />` inside `<dialog />`
2. execute the `showModal()` method of the dialog
3. you will notice that react will not set focus to the correct input element

![DialogAutoFocus](https://user-images.githubusercontent.com/4113649/154110039-dc6dbd63-f294-4089-aa25-420626088ef5.gif)


<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

https://codesandbox.io/s/dreamy-meninsky-460wbr?file=/src/App.tsx

## The current behavior

In Chrome and Safari TP the element with `autofocus="true"` will receive focus.  
However the element with `autoFocus={true}` will not receive focus.

## The expected behavior

From the html-spec https://html.spec.whatwg.org/multipage/interaction.html#the-autofocus-attribute

> The autofocus content attribute allows the author to indicate that an element is to be focused [...] as soon as the [dialog](https://html.spec.whatwg.org/multipage/interactive-elements.html#the-dialog-element) within which it finds itself is shown


From https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes/autofocus

> The autofocus [global attribute](https://developer.mozilla.org/en-US/docs/Web/HTML/Global_attributes) is a Boolean attribute indicating that an element should be focused on page load, or when the [`<dialog>`](https://developer.mozilla.org/en-US/docs/Web/HTML/Element/dialog) that it is part of is displayed

Therefore `autoFocus={true}` should also set the focus similar to `autofocus="true"` for elements inside `<dialog />`
Repository: TypeScript
Issue: For JSX Class Components, allow attributes based on the type of the class constructor
Labels: Suggestion,Awaiting More Feedback

# Suggestion

Currently, only the first argument of the constructor of a Class Component can be used as attributes in JSX. This is not in accordance with the JSX spec: In pure JavaScript, there is no problem at all defining a JSX pragma that uses JSX attributes as the third argument to construct the class.

## 🔍 Search Terms

JSX, React, CDK, class, constructor

## ✅ Viability 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, new syntax sugar for JS, etc.)
* [X] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


## ⭐ Suggestion

A generic way to introduce this would be e. g.
```tsx
declare global {
  namespace JSX {
    interface ElementAttributesFromConstructor<Constructor extends new () => unknown> {
        props: ConstructorParameters<Constructor>[2]
    }
  }
}
```

## 📃 Motivating Example

It is now possible to define JSX Class Components that take their attributes from any part of the constructor function with help of `ElementAttributesFromConstructor`. Previously, it was only possible to use the first argument to the constructor.
This is helpful when adding JSX to existing structures. One example is the AWS CDK which uses Constructs in the following form:
```ts
class ExampleConstruct extends Construct {
  constructor(scope: Construct, id: string, props: { message: string }) {
    console.log(props.message)
  }
}
```

When setting `ElementAttributesFromConstructor` like this
```ts
declare global {
  namespace JSX {
    interface ElementAttributesFromConstructor<Constructor extends new () => unknown> {
        props: ConstructorParameters<Constructor>[2]
    }
  }
}
```
TypeScript will support you when using classes in JSX:
```tsx
/* @jsx createElement */

function createElement (component: Construct,  attributes: Record<string, unknown> | null) {
  // Put the logic to create the JSX element here
}

const construct = <ExampleConstruct message="Hello World" />
```

## 💻 Use Cases

Currently, JSX is still mostly used for React and very similar libraries (e. g. Preact, Vue). But there are already other use cases for JSX (e. g. https://github.com/developit/jsxobj, https://github.com/dbartholomae/jsx-readme).
One ongoing discussion is about [configuring AWS CDK via JSX](https://github.com/aws/aws-cdk-rfcs/issues/256), which is limited by this: AWS CDK uses the third constructor parameter for properties, and while this works in JavaScript, the TypeScript types do not allow for it.
Repository: opencv
Issue: CV_LOG_STRIP_LEVEL inconsistency
Labels: category: core,category: build/install,RFC

##### System information (version)
- OpenCV => 4.x

##### Detailed description

According to the definition at: https://github.com/opencv/opencv/blob/446a278f3d144de4aab53d9a3a464717c30b0851/modules/core/include/opencv2/core/utils/logger.hpp#L61 CV_LOG_STRIP_LEVEL can be defined at compile time to whatever we want.

But the code redefines it in several places without first checking if it is defined, thus creating an ```error: 'CV_LOG_STRIP_LEVEL' macro redefined```

E.g. : https://github.com/opencv/opencv/blob/446a278f3d144de4aab53d9a3a464717c30b0851/modules/core/src/parallel/parallel.cpp#L10 or https://github.com/opencv/opencv/blob/446a278f3d144de4aab53d9a3a464717c30b0851/modules/imgproc/src/filter.dispatch.cpp#L46

We want to enclose those with an ```#ifndef CV_LOG_STRIP_LEVEL ``` right ?

##### Steps to reproduce

compile with ```-DCV_LOG_STRIP_LEVEL=2```.

##### Issue submission checklist

 - [x] I report the issue, it's not a question
 - [x] I checked the problem with documentation, FAQ, open issues,
       forum.opencv.org, Stack Overflow, etc and have not found any solution
 - [x] I updated to the latest OpenCV version and the issue is still there
Repository: PowerToys
Issue: PowerToys Run Secondary Search
Labels: Idea-Enhancement,Product-PowerToys Run

### Description of the new feature / enhancement

It would be really useful to be able to do a secondary search. 

### Scenario when this would be used?

For example, I search for "Excel" then hit Tab to move to a seoncondary search of Excel files. I could search for "Control" and then a secondary search for a specific control panel applet. I think this would make this search function much more powerful. I could search for Outlook, then for quick actions within like "New Email."

### Supporting information

_No response_
Repository: node
Issue: guidance on CJS module requires and file extensions
Labels: doc,module

### Affected URL(s)

https://nodejs.org/dist/latest-v16.x/docs/api/modules.html

### Description of the problem

The documentation states:

> If the exact filename is not found, then Node.js will attempt to load the required filename with the added extensions: .js, .json, and finally .node.

Even though `require("./foo")` and `require("./foo.js")` are both accepted, there is no recommendation about whether user code _should_ use or omit the extension.  An explicit opinion would be helpful.

The docs use both:

> In the Node.js module system, each file is treated as a separate module. For example, consider a file named foo.js:

```js
const circle = require('./circle.js');
```

and

> For example, suppose we were making a module called a.js:

> Then in another file we could do:

```js
const a = require('./a');
```
Repository: pytorch
Issue: Bazel fails in an obscure way if submodules are not initialized
Labels: low priority,triaged,module: third_party,module: bazel

### 🐛 Describe the bug

The error you get is this:

```
ezyang@devfair024:/scratch/ezyang/pytorch-tmp2$ tools/bazel build --sandbox_writable_path=$HOME/.ccache :torch                                                                                              ERROR: Error fetching repository: java.io.IOException: No WORKSPACE file found in /raid/ezyang/.cache/bazel/_bazel_ezyang/08e868d346498e93c89518b0a9346a91/external/com_google_protobuf                     
ERROR: no such package '@com_google_protobuf//': No WORKSPACE file found in /raid/ezyang/.cache/bazel/
_bazel_ezyang/08e868d346498e93c89518b0a9346a91/external/com_google_protobuf                           INFO: Elapsed time: 0.141s                                                                            
INFO: 0 processes.      
```

This error can be fixed by initializing submodules. Confusingly, the file path in the error message here refers to .cache/bazel directory, suggesting some sort of cache problem (but it's really a problem with the source checkout)

### Versions

master
Repository: go
Issue: cmd/go: fail if the user tries to modify the GOMOD environment variable
Labels: help wanted,NeedsFix,GoCommand,modules

See https://github.com/golang/go/issues/51171#issuecomment-1040765860. The user likely wants to either use `-modfile`, or `cd` into the right directory to enter or leave a module. Right now, a command like `GOMOD=foo.mod go list` will happily ignore `GOMOD=foo.mod`.

cc @bcmills @matloob
Repository: material-ui
Issue: [Button] Color prop is not passed to Button when used in Grid as component
Labels: bug 🐛,component: Grid,component: button,regression

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

The following code shows a button in the `primary` color, even though `secondary` is specified as `color`:

```jsx
 <Grid component={Button} variant="contained" color="secondary">hello</Grid>
``` 

The following code does show a button in the `secondary` color

```jsx
 <Button variant="contained" color="secondary">hello</Button>
``` 

In v4 both seemed to work correctly, in v5 the `color` is ignored

See also https://codesandbox.io/s/fullwidthgrid-material-demo-forked-3fgs89?file=/demo.js


### Expected behavior 🤔

Both the Grid as the Button should use the `secondary` color, as in v4

### Steps to reproduce 🕹

See https://codesandbox.io/s/fullwidthgrid-material-demo-forked-3fgs89?file=/demo.js

### Context 🔦

_No response_

### Your environment 🌎

codesandbox.io as launched from the MUI website with latest v5.4.2
Repository: flutter
Issue: [Win32, Keyboard] Fix synthesization of toggle keys from phase 0 to 3
Labels: a: text input,platform-windows,a: desktop,P2,team-windows,triaged-windows

The synthesization algorithm on Win32 is broken if it was last observed at phase 0 (pressed 0 toggled 0) and currently phase 3 (pressed 1 toggled 0). 

Expected: 3 events are synthesized (down, up, down)

Actual: 1 event is synthesized (down)

This has been noted as a TODO for a unit test, `SynthesizeModifiers`.
Repository: flutter
Issue: [Proposal] Provide a way to set `fontFamily` when creating the theme with `ThemeData.from`
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

## Use case

As per the [documentation](https://api.flutter.dev/flutter/material/ThemeData/ThemeData.from.html), `ThemeData.from` is the recommended way of creating a theme so that the migration to the material color scheme is smoother. 

However it seems unfeasible to then set the `fontFamily` of the `ThemeData` once its been created. Even the method `copyWith` doesn't offer the possiblity of changing the `fontFamily`. How are we supposed to set the theme `fontFamily`?

Is there some magical way of doing it by setting the typography or something? The whole thing is confusing.

## Proposal

Add `fontFamily` to the `copyWith` function of `ThemeData` to migrate away from the `ThemeData` constructor while better options are unavailable.
Repository: godot
Issue: Godot 4: Visual Script node text box doesn't focus by default
Labels: bug,topic:editor,topic:visualscript,regression

### Godot version

v4.0.alpha2.official [79077e6c1]

### System information

Windows 11, Vulkan Clustered, Intel UHD Graphics 620 v30.0.101.1340

### Issue description

When the users click in a text field to edit a node's text box in Visual Script, the focus will not be on the text box. The users will have to click on the text box one more time before they can actually edit the field. This behavior can be seen in the screen recording below:

https://user-images.githubusercontent.com/1403194/154168144-a7a4027d-71e4-42f2-b806-ec8172c08dfe.mp4

This issue is a regression from Godot 3.4. In Godot 3.4, the users do not need to click on the text box as the focus will be on the text box by default. They can edit the text field immediately, as shown in the screen recording below:

https://user-images.githubusercontent.com/1403194/154168382-c36bd99e-573b-48a3-b788-9fbf7998f1e4.mp4

I expect the focus to be on the text box by default since that is the whole reason I go to this field in the first place.

Note: I am not sure whether this is fixed in [merged PR #58026](https://github.com/godotengine/godot/pull/58026) since this issue is happening in a different place altogether.

### Steps to reproduce

1. Add the get() function from the Object base type in VisualScript for example.
2. Try to edit the Str property's text field. The text box popup won't be focused by default.

### Minimal reproduction project

_No response_
Repository: PowerToys
Issue: Fancy Zones acting strangely and a request
Labels: FancyZones-Editor,Product-FancyZones,FancyZones-VirtualDesktop,Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

I Have been using Fancy Zones now for a few months and I absolutely love it. There is however a possible bug I ran into tonight. I have a monitor with 21:9 aspect ratio. When I modify presets over time the make a long line and go off the edge off the screen so I have to scroll to find the newest configurations. I am not able to move the settings by dragging them, which would be very helpful to organize then. I have to admit that I find it a bit strange if it was not designed with that feature.

Tonight I encountered a problem because of my many presets one of them went off screen and every time I tried to scroll to it, drag the window with all the presets and other things I tried but don't recall well enough to give detailed report of. 
That issue may be temporary I haven't followed the basic reboot that fixes most problems. But ignored that because I wanted to report that strange behaviour and mention what I think may improve this already great utility.

### Scenario when this would be used?

I would use this to be able to configure very specific layouts based on the apps I'm working with. Being able to fully use every cm2 of my screen real estate is something I find very good. I then try to run certain apps in specific, layouts in certain virtual desktops and switch between desktops as needed.

### Supporting information

_No response_
Repository: react
Issue: Bug: pseudo styles don't work properly if React state does not change when clicking with right mouse button.
Labels: Type: Bug,Component: DOM

I have a button that changes background in :hover and :active states. Clicking the button with left mouse button (LMB) works fine, styles change as they should. But, clicking with right mouse button (RMB) works fine only if underlying react state is actually changed (e.g. different from the previous state)

React version: 17.0.2

## Steps To Reproduce
1. Open the code example provided below
2. Click the "Click Me" button with LMB more than 2 times (DON'T move your mouse cursor while clicking)
3. Click the "Click Me" button with RMB more than 2 times (DON'T move your mouse cursor while clicking)

Link to code example: https://codesandbox.io/s/pensive-sunset-z1t69f

## The current behavior
No mater how many times you click with LMB, the "Click Me" button consistently changes its background color to yellow when you hold LMB down, and changes it back to silver when you release LMB.

The second time RMB pressed down, the background color of the "Click Me" button remains yellow, even if you release RMB. That is, whenever you click it with RMB and the new react state is the same as the previous, the button style remains yellow even if you release RMB.
## The expected behavior
Clicking the "Click Me" button with RMB should respect styles regardless of the underlying react state.
Repository: yt-dlp
Issue: Loco.gg Downloader
Labels: site-request

### Checklist

- [X] I'm reporting a site feature request
- [X] I've verified that I'm running yt-dlp version **2022.02.04**. ([update instructions](https://github.com/yt-dlp/yt-dlp#update))
- [X] I've checked that all provided URLs are alive and playable in a browser
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues including closed ones. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)
- [X] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and I'm willing to share it if required

### Region

India

### Example URLs

https://loco.gg/stream/e2d319b4-f2f9-430f-a830-4ef76cf6c161

### Description

I confirm that i am on latest yt-dlp and this url is not supported!

### Verbose log

```shell
[debug] Command-line config: ['-vU', 'https://loco.gg/stream/e2d319b4-f2f9-430f-a830-4ef76cf6c161']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, err utf-8, pref cp1252
[debug] yt-dlp version 2022.02.04 [c1653e9ef]
[debug] Python version 3.10.1 (CPython 64bit) - Windows-10-10.0.22000-SP0
[debug] exe versions: ffmpeg 2022-02-03-git-e1a14479a8-full_build-www.gyan.dev (setts), ffprobe 2022-02-03-git-e1a14479a8-full_build-www.gyan.dev, phantomjs 2.1.1
[debug] Optional libraries: Cryptodome, mutagen, sqlite, websockets
[debug] Proxy map: {}
Latest version: 2022.02.04, Current version: 2022.02.04
yt-dlp is up to date (2022.02.04)
[debug] [generic] Extracting URL: https://loco.gg/stream/e2d319b4-f2f9-430f-a830-4ef76cf6c161
[generic] e2d319b4-f2f9-430f-a830-4ef76cf6c161: Requesting header
WARNING: [generic] Falling back on generic information extractor.
[generic] e2d319b4-f2f9-430f-a830-4ef76cf6c161: Downloading webpage
[generic] e2d319b4-f2f9-430f-a830-4ef76cf6c161: Extracting information
[debug] Looking for video embeds
ERROR: Unsupported URL: https://loco.gg/stream/e2d319b4-f2f9-430f-a830-4ef76cf6c161
Traceback (most recent call last):
  File "C:\Users\lucigendu\AppData\Local\Programs\Python\Python310\lib\site-packages\yt_dlp\YoutubeDL.py", line 1381, in wrapper
    return func(self, *args, **kwargs)
  File "C:\Users\lucigendu\AppData\Local\Programs\Python\Python310\lib\site-packages\yt_dlp\YoutubeDL.py", line 1451, in __extract_info
    ie_result = ie.extract(url)
  File "C:\Users\lucigendu\AppData\Local\Programs\Python\Python310\lib\site-packages\yt_dlp\extractor\common.py", line 612, in extract
    ie_result = self._real_extract(url)
  File "C:\Users\lucigendu\AppData\Local\Programs\Python\Python310\lib\site-packages\yt_dlp\extractor\generic.py", line 3986, in _real_extract
    raise UnsupportedError(url)
yt_dlp.utils.UnsupportedError: Unsupported URL: https://loco.gg/stream/e2d319b4-f2f9-430f-a830-4ef76cf6c161
```
Repository: godot
Issue: Input.GetVector is not working when exported in HTML5
Labels: bug,platform:web,confirmed,topic:dotnet,topic:input

### Godot version

v3.4.2.stable.mono.official (45eaa2daf)

### System information

Windows 10, at least on Chrome and Firefox

### Issue description

The method `Input.GetVector(...)` returns `(0, 0)` **only** when project is exported to HTML5 (it works fine in the editor).

It has nothing to do with input mapping since the method `Input.GetActionStrength(...)` for the same action returns a non-null vector.

### Steps to reproduce

* Setup project inputs for these actions, mapping doesn't matter, you can setup keyboard or even a controller
  * `player_up`
  * `player_down`
  * `player_left`
  * `player_right`
* Add a script to a Node in your scene
```cs
public override void _Process(float delta) {
    GD.Print(Input.GetVector("player_left", "player_right", "player_up", "player_down"));
}
```
* Export project to HTML5

### Minimal reproduction project

[input-get-vector-issue.zip](https://github.com/godotengine/godot/files/8076141/input-get-vector-issue.zip)
Repository: rust
Issue: Tracking Issue for warning on unused lifetimes (by default)
Labels: T-lang,C-tracking-issue,S-tracking-impl-incomplete

This issue is tracking the transition of the `unused_lifetimes` lint to warn-by-default (or higher).


### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps

Several concerns were raised as blocking in #92386:

* [ ] [Permit underscores to silence the lint](https://github.com/rust-lang/rust/pull/92386#issuecomment-1015740199)
* [ ] [Avoid warning on semver-exposed lifetimes](https://github.com/rust-lang/rust/pull/92386#issuecomment-1015723902)

Additionally, a plausible half step was [suggested](https://github.com/rust-lang/rust/pull/92386#issuecomment-1016025192) that enabling the lint for `impl` lifetime declarations would likely have no semver compatibility concerns and so be feasible to land more quickly.

### Known bugs (list may be incomplete)

* [ ] https://github.com/rust-lang/rust/issues/74165
* [x] https://github.com/rust-lang/rust/issues/72587
* [x] https://github.com/rust-lang/rust/issues/94307


Prior "tracking" issue: https://github.com/rust-lang/rust/issues/41960
Repository: vscode
Issue: Git - Support for Git in Msys2
Labels: feature-request,git

Now Git in Msys2 cannot be invoked correctly, and it's inconvenient to install and synchronize 2 version of git. So maybe it is necessary to add support for Git in Msys2?