sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: electron
Issue: [Bug]: Mouse event forwarding is buggy `win.setIgnoreMouseEvents(true, {forward: true});`
Labels: platform/windows,bug :beetle:,status/confirmed,has-repro-gist,14-x-y,21-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Electron Version

14.0.0

### What operating system are you using?

Windows

### Operating System Version

OS build 19043.1165

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

:hover and mouse enter/leave event work without issue

### Actual Behavior

:hover and mouse enter/leave event do not work(unreliable/flickering)

### Testcase Gist URL

https://gist.github.com/7c945234e55000f21a5db29cc11600cd

### Additional Information

I was trying to create a minimal repro of a bug we encountered with our product, the original issue is: mouseleave event / :hover pseudo class not working reliably on Windows after `win.setIgnoreMouseEvents(true, {forward: true})`.

However the actual repro "exceeds" my expectation and acts much weirder. 

![electron-forward-mouse-event-issue](https://user-images.githubusercontent.com/970430/131805640-0ca18497-1371-4419-a193-7c034954622b.gif)
Repository: vscode
Issue: Git - Remove "Changes actions" when changes list is empty
Labels: feature-request,git

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

It's a bit confusing to see the "plus" action etc.. when there'e no changes at all.

Maybe remove the whole row or just the actions on the right side..

![image](https://user-images.githubusercontent.com/13297000/131814379-fbb8356d-bc47-411d-942f-e6fdbea3b969.png)


<!-- Describe the feature you'd like. -->
Repository: create-react-app
Issue: Add .esm.js to Webpack config.resolve.extensions
Labels: issue: proposal,needs triage

[Headless UI](https://headlessui.dev/react/) provides amazing headless components and focus utilities that make it really easy to create keyboard- and screen-reader-accessible components. However, those utilities are contained in a `.esm.js` file. They have associated typings and don't seem to be private from what I can tell, so I (and my IDE's auto-import) thought this would be OK:

```ts
import {Focus, focusIn}      from '@headlessui/react/dist/utils/focus-management'
```

Turns out, that causes Webpack to throw a huge fit because it doesn't know that `.esm.js` files are a thing. My IDE and the type checker pick up on the existence of the .d.ts file, but webpack refuses to load the .esm.js file, and throws an error.

This [craco](https://github.com/gsoft-inc/craco/blob/master/packages/craco) config fixes the problem:

```
module.exports = {
	webpack: {
		configure: (config) => {
			config.resolve.extensions.push('.esm.js')
			return config
		}
	}
}
```

This causes everything to start working. More specifically, I propose adding `.esm.js` to this array:

https://github.com/facebook/create-react-app/blob/f0a837c1f07ebd963ddbba2c2937d04fc1b79d40/packages/react-scripts/config/paths.js#L34-L46

It looks like you already support `.web.x`, so maybe just go ahead and put `.esm.x` after it, like so:

```js
const moduleFileExtensions = [
  'web.mjs',
  'esm.mjs',
  'mjs',
  'web.js',
  'esm.js',
  'js',
  'web.ts',
  'esm.ts',
  'ts',
  'web.tsx',
  'esm.tsx',
  'tsx',
  'json',
  'web.jsx',
  'esm.jsx',
  'jsx',
];
```
Repository: go
Issue: x/build: allow x/mobile tests run on darwin/arm64
Labels: Builders,NeedsInvestigation

The x/mobile is an experimental repository that skips many builders. Its current builders include android/386, android/amd64, and ios/arm64.

While working on [CL 346150](https://go-review.googlesource.com/c/mobile/+/346150/comments/5ed05f18_9477bffb), we found that tests in x/mobile are not tested on a macOS. This may cause issues:

- `cmd/gomobile` may be partially broken without any notice (Mac tests had broken for quite a long time until recent fixes), which leads to the runtime support for iOS being unverifiable (not a wanted behavior).
- it can cause the review process to confuse because a Mac-specific change is also not verifiable through a Trybot run.

Since we already have a darwin/arm64 environment (`darwin-arm64-11_0-toothrot`), we may use it as a builder for x/mobile.

A further concern is that x/mobile tests may require an Xcode installation with a valid Apple Developer account. However, Xcode is not forward-compatible (earlier Xcode versions may not work with later Xcode-specific changes). If a CL targets a newer Xcode release, it may not be testable until the environment is ready. Consider this reason, a dedicated environment with multiple Xcode installations may be better.

@dmitshur @hyangah @hajimehoshi
Repository: ant-design
Issue: TimePicker scrolls only after selection on mobile
Labels: 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/antd-reproduction-template-forked-n4fkx)

### Steps to reproduce
1. Press the time picker input
2. The dropdown of choosing time components (hours/minutes/seconds) is shown
3. Try to scroll the time component without selecting/touching an initial value

### What is expected?
To be able to scroll the time components on the initial state after popover is shown

### What is actually happening?
Can't scroll the time components until you select a random option from each time component

| Environment | Info |
|---|---|
| antd | 4.16.7 |
| React | 17.0.2 |
| System | Android v10 |
| Browser | Google chrome mobile v92.0.4515.166 |

---
It seems like a problem with the initial focus on the component. This issue makes the users think that the time selection is limited to the initial opened list (because it can't scroll) - this is misleading.
On a lot of systems, there are no visible scroll handles so you can't know what is scrollable and what is not.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: go
Issue: x/crypto/bn256:  wrong formulas in comments
Labels: NeedsFix

bn256/gfp6.go : 251 in latest version of go
```
// On the other hand (xj²τ² + yjτ + z)(xjτ² + yj²τ + z)
// = τ²(y²-ξxz) + τ(ξx²-yz) + (z²-ξxy)
//
// So that's why A = (z²-ξxy), B = (ξx²-yz), C = (y²-ξxz)
```

while the right one is :
```
// On the other hand (xj²τ² + yjτ + z)(xjτ² + yj²τ + z)
// = τ²(y²-xz) + τ(ξx²-yz) + (z²-ξxy)
//
// So that's why A = (z²-ξxy), B = (ξx²-yz), C = (y²-xz)
```

in addition,  http://arxiv.org/pdf/0904.0854v3.pdf which is referenced by optate.go : 9  also has wrong formulas :

<img width="1000" alt="截屏2021-09-02 下午5 42 01" src="https://user-images.githubusercontent.com/32356175/131823681-4d693367-86ce-4eef-b090-a2f6348edb16.png">
Repository: create-react-app
Issue: Lazy loaded component not loading css-module
Labels: stale,needs triage,issue: bug report

in DEV mode when lazy chunk evaluated, its styles aren't evaluated.
`
const AuthRoute = lazy(() => import("./auth"))
`
and later:
`
<Switch>
      <Route path={ROUTES.AUTH} render={() => <AuthRoute/>} />
 </Switch>
`

and If child components contains ' **import classes from "./styles.module.scss"** '  style doesn't render 

in PROD mode (**react-scripts build**) everything works, but with DEV (**react-scripts start**)-  doesn't

Tested with react-scripts@4.0.2  + sass/node-sass
Repository: yt-dlp
Issue: [Site Request] altbalaji.com
Labels: site-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 yt-dlp:
- First of, make sure you are using the latest version of yt-dlp. Run `yt-dlp --version` and ensure your version is 2021.09.02. If it's not, see https://github.com/yt-dlp/yt-dlp 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://github.com/yt-dlp/yt-dlp. yt-dlp 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: https://github.com/yt-dlp/yt-dlp. DO NOT post duplicates.
- Finally, put x into all relevant boxes like this [x] (Dont forget to delete the empty space)
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running yt-dlp version **2021.09.02**
- [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] The provided URLs do not contain any DRM to the best of my knowledge
- [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.altbalaji.com/show/coldd-lassi-aur-chicken-masala/292



## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

Please add site support from altbalaji.com
Repository: material-ui
Issue: [docs] Branding theme should match Material design theme
Labels: docs,discussion

## Current Behavior 😯

The docs currently have two different theme interfaces:
1. Material design
2. the docs theme (https://github.com/mui-org/material-ui/blob/f5e1da0f3e4c72b7e80aa84d41ab035d84500177/docs/src/modules/brandingTheme.ts)

The problem is that docs components assume the branding theme while they can be used inside the Material  design context (e.g. https://github.com/mui-org/material-ui/blob/0979e6a54ba47c278d1f535953c0520a86349811/docs/src/modules/components/DemoSandboxed.js#L121-L128) leading to https://github.com/mui-org/material-ui/issues/28102 or https://github.com/mui-org/material-ui/issues/28105

I've experimented with two different approaches:
1. Fallback to Material design (https://github.com/mui-org/material-ui/pull/28109)
2. Lint against importing docs components and ensure components are only used within a new branding theme (stopped midway since it's a lot of work)

Both of these approaches require a considerable amount of maintenance. It seems to me that the easiest approach is to match interfaces so that we can safely move forward.

What I noticed is that the extended palette isn't even used directly in some places. Even though we have  6-10 different `warning` colors we still sometimes apply an alpha filter (e.g. https://github.com/mui-org/material-ui/blob/0a7298cd865d772f32ec20c9fae7ce5ab7e80553/docs/src/components/home/AdvancedShowcase.tsx#L97-L97). So it seems like the palette isn't even that useful.

/cc @siriwatknp @danilo-leal
Repository: vscode
Issue: [Bug] `revealCursor` doesn't respect `editor.cursorSurroundingLines`
Labels: bug,help wanted,editor-commands

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->

Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->

- VS Code Version: 1.60.0-insider
- OS Version: Windows 10

Steps to Reproduce:

1. Set `"editor.cursorSurroundingLines": 10` in `settings.json`.
2. Add the following keybindings into `keybindings.json`:

   ```json
   [
     {
       "key": "ctrl+up",
       "command": "-scrollLineUp",
       "when": "textInputFocus"
     },
     {
       "key": "ctrl+up",
       "command": "editorScroll",
       "when": "textInputFocus",
       "args": {
         "to": "up",
         "value": 10,
         "by": "line",
         "revealCursor": true
       }
     },
     {
       "key": "ctrl+down",
       "command": "-scrollLineDown",
       "when": "textInputFocus"
     },
     {
       "key": "ctrl+down",
       "command": "editorScroll",
       "when": "textInputFocus",
       "args": {
         "to": "down",
         "value": 10,
         "by": "line",
         "revealCursor": true
       }
     }
   ]
   ```

3. Use <kbd>Ctrl</kbd>+<kbd>Up</kbd> or <kbd>Ctrl</kbd>+<kbd>Down</kbd> across pages in a long file.
4. The cursor position may appear at the top or at the bottom in the process, `editor.cursorSurroundingLines` is not respected.
Repository: go
Issue: crypto/tls: wrap handshake errors
Labels: NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
1.14.12
</pre>

### Does this issue reproduce with the latest release?
Not sure


### What operating system and processor architecture are you using (`go env`)?
Busybox OS, ARM architecture

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env

</pre></details>

### What did you do?
We are trying to print the certs in the event when the cert based handshake fails. 

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->



### What did you expect to see?
In the event of invalid certs being provided to establish a connection the tls handshake should fail, and trying to print the bad certificate using errors.As should log the certificate.


### What did you see instead?
From the code it looks like its done wrong for client certs.
chains, err := certs[0].Verify(opts)
if err != nil {
  c.sendAlert(alertBadCertificate)
  return errors.New("tls: failed to verify client certificate: " + err.Error())
}
Repository: rust
Issue: doctests: unhelpful error messages for non-Rust code blocks
Labels: T-rustdoc,A-diagnostics,A-doctests

I recently added the a docstring to one of my functions that looked similar to this:

```rust
/**
This function does the following:

    1. Print `foo`
    2. Return
*/
pub fn foo() {
    println!("foo");
}
``` 
When I then ran `cargo test` to execute tests defined in other parts of the project, I got the error messages

```none
---- src/lib.rs - foo (line 4) stdout ----
error: unknown start of token: `
 --> src/lib.rs:5:10
  |
3 | 1. Print `foo`
  |          ^
  |
help: Unicode character '`' (Grave Accent) looks like ''' (Single Quote), but it is not
  |
3 | 1. Print 'foo`
  |          ^

error: unknown start of token: `
 --> src/lib.rs:5:14
  |
3 | 1. Print `foo`
  |              ^
  |
help: Unicode character '`' (Grave Accent) looks like ''' (Single Quote), but it is not
  |
3 | 1. Print `foo'
  |              ^

error: expected one of `.`, `;`, `?`, `}`, or an operator, found `Print`
 --> src/lib.rs:5:4
  |
3 | 1. Print `foo`
  |    ^^^^^ expected one of `.`, `;`, `?`, `}`, or an operator

error: aborting due to 3 previous errors
```
It took me a while to figure out the issue: the list items shouldn't be indented, because the indentation makes them a code block instead of a list. With the indentation, Rust tries to run the list as a doctest, and the error messages are due to the list content not being valid Rust code.

`cargo check` didn't yield any insights, either -- in fact it did not produce any warning at all.

`cargo doc`, on the other hand, produced the following very helpful output:
```none
warning: could not parse code block as Rust code
 --> src/lib.rs:4:5
  |
4 | /     1. Print `foo`
5 | |     2. Return
  | |_____________^
  |
  = note: error from rustc: unknown start of token: `
  = note: error from rustc: unknown start of token: `
```
This pointed me directly in the right direction of something being parsed as Rust code.

I know that this is a minor issue, but so far I have been amazed by the incredibly helpful error message in the Rust eco system, and this was one of the few times where the original message was of little help. I don't know anything about how `cargo test` and `cargo doc` differ in their parsing, but the helpful output of `cargo doc` shows that a similar message should be possible for `cargo test`.

This is with Cargo `1.50.0 (f04e7fab7 2021-02-04)`.
Repository: rust
Issue: Clippy suggests an unstable attribute instead of a deprecated one for #[cfg_attr(rustfmt, rustfmt_skip)]
Labels: A-attributes,C-bug,E-needs-mcve,A-clippy

I'm disabling rustfmt for some lines of my code because I have functions with multiple arguments and for the sake of exposing the logical reasoning of the algorithm, I want to group them on multiple lines. Therefore, I am using:

```rust
#[cfg_attr(rustfmt, rustfmt_skip)]
...
```

Running `cargo clippy` tells me:
```
`cfg_attr` is deprecated for rustfmt and got replaced by tool attributes
...
help: use: `#[rustfmt::skip]`
```

However, if I replace these with `#[rustfmt::skip]`, I'm getting the following error:
```
error[E0658]: attributes on expressions are experimental
...
note: see issue #15701 <https://github.com/rust-lang/rust/issues/15701> for more information
```

I assume it is a bug for a tool in stable Rust to suggest to use an experimental code to replace valid (although deprecated) code.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.53.0 (53cb7b09b 2021-06-17)
binary: rustc
commit-hash: 53cb7b09b00cbea8754ffb78e7e3cb521cb8af4b
commit-date: 2021-06-17
host: x86_64-unknown-linux-gnu
release: 1.53.0
LLVM version: 12.0.1
```

</details>
Repository: pytorch
Issue: Add support for ROCm MIOpen miopenConvolutionForwardBias and miopenConvolutionBackwardBias
Labels: module: rocm,triaged


This is a tracking ticket for adding support for  miopenConvolutionForwardBias and miopenConvolutionBackwardBias. 

The original code utilized this functionality that is removed in this PR, due to lack of NHWC support: https://github.com/pytorch/pytorch/pull/63617

**Relevant internal AMD tickets:** 
- PyTorch frameworks : https://ontrack-internal.amd.com/browse/SWDEV-301466
- MIOpen : https://ontrack-internal.amd.com/browse/SWDEV-301464


cc @jeffdaily @sunway513 @jithunnair-amd @ROCmSupport
Repository: neovim
Issue: Borders for popup menu windows (pum, Pmenu)
Labels: enhancement,ui,completion,floatwin

### Feature already in Vim?

Not in Vim I dont believe. Maybe with `completepopup` ?

### Feature description

I believe neovim should add the support to have borders configurable for pum windows. Floating windows and other things like it are able to have their own borders and configurations for them, but pums do not yet. 
I couldn't find anything on the google or any issue that relates to well shockingly because I feel it would be quite a nice feature to have. 

For example completion menus, it would be quite nice to be able to turn on borders for them and you can set the characters or what not for those borders and colors.

Let me know if I could be more specific. Thanks!
Repository: godot
Issue: Multi camera 3d setup doesn't update collision shapes translation properly
Labels: bug,confirmed,topic:physics,topic:3d

### Godot version

3.3.3 stable

### System information

windows 10, gles3, intel hd 520

### Issue description

when instancing a two viewport + camera with different cull layers to display different  objects at the same time in the same screen space, the second camera updates object's translation but if the object have a collision shape this won't be updated.

As far as I can see the collision shape translation is asigned always to the first camera translation.

having a two camera setup is handy in shmup genre with one orthographic static camera rendering entities and one perspective dynamic camera rendering stage objects.

### Steps to reproduce

.node

..kinematicbody
...meshinstance (visual instance 1)
...collisionshape

..kinematicbody2
...meshinstance (visual instance 2)
...collisionshape

.viewportcontainer
..viewport
...camera (cull 1)

viewportcontainer2
..viewport
...camera (cull 2)


### Minimal reproduction project

in the proyect I've added an animation player moving the second camera translation, might need to check visible collision shapes in debug menu

[MultiCamSetup.zip](https://github.com/godotengine/godot/files/7100451/MultiCamSetup.zip)
Repository: go
Issue: cmd/go: add per-test timeouts
Labels: Proposal,Proposal-Accepted,GoCommand

Tests have an overall timeout for the entire binary but no timeout for a specific test case.
You often want to limit any particular test case to a time much shorter than the overall binary.
I propose to add the concept of per-test (function) timeouts to the go command user experience as follows.

1. Each test gets a per-test timeout. The timer for a given test only ticks down when the test is running. It does not tick down when the test is blocked in t.Parallel, nor when it is blocked in t.Run running a subtest.

2. The default per-test case timeout is 1m (one minute). If the new `-testtimeout` flag is specified explicitly, then that sets a different default. If the `-testtimeout` flag is omitted but `-timeout` is specified explicitly, then that sets the default too. This way, if you have one really long test and use `go test -timeout=30m`, the per-case timeout doesn't kick in after 1 minute and kill it anyway.

3. There is a new testing.TB method `SetTimeout(d time.Duration)` that allows a test to set its own timeout. Calling SetTimeout does not reset the timer. If a test runs for 30 seconds and then calls `t.SetTimeout(1*time.Second)`, it gets killed for having timed out. A timeout set this way is inherited by subtests. (They each have their own timer.)

4. When a test timeout happens, the whole process still gets killed. There's nothing we can really do about that. But the failure does say which test function timed out.

This change will help users generally, and it will also help fuzzing, because any individual invocation of a fuzz function will now have a testing.T with a 1-minute timer, providing for detection of inputs that cause infinite loops or very slow execution.