sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: net/http: HTTP2 pushing is suprisingly slow
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.17.7 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/mitar/.cache/go-build"
GOENV="/home/mitar/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/mitar/.go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/mitar/.go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.17.7"
GCCGO="/usr/bin/gccgo"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build680865618=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

I am trying to push multiple requests using HTTP2.

### What did you expect to see?

From reading `pusher.Push` documentation, my expectation was that pushing negligibly impacts time the main request is served, as all pushing happens in separate goroutines.

### What did you see instead?

I am observing that this is not the case. I made a simple test and pushing 100 requests with 10 KB large responses takes 8 ms on my local machine, pushing 100 requests with 1 MB large responses takes 35 ms. So this is just additional time added to the main request handling to call `pusher.Push` in a loop. Not how long it takes for the pushed responses themselves to be delivered. This is a surprising amount to me.

From [looking at the code](https://cs.opensource.google/go/x/net/+/master:http2/server.go;l=2828-2853), I think the issue is that `pusher.Push` waits until it can send a `startPushRequest` message to `serveMsgCh` and with many push requests this can block for non-trivial amount of time.

I made a small example [here](https://github.com/mitar/go-slow-http2-push). See README for instructions how to run it.
Repository: create-react-app
Issue: [react-script] jsx-key Missing "key" prop for element in array when there is no array/iteration
Labels: needs triage,issue: bug report

<!--
    Please note that your issue will be fixed much faster if you spend about
    half an hour preparing it, including the exact reproduction steps and a demo.

    If you're in a hurry or don't feel confident, it's fine to report bugs with
    less details, but this makes it less likely they'll get fixed soon.

    In either case, please use this template and fill in as many fields below as you can.

    Note that we don't provide help for webpack questions after ejecting.
    You can find webpack docs at https://webpack.js.org/.
-->

### Describe the bug
I have upgraded the package react-scripts from "4.0.3" to "5.0.0". 

I have got the "Missing "key" prop for element in array" everywhere on my codebase. 

I hope this is the issue with `eslint-plugin-react@7.29.0`


```
└─┬ react-scripts@5.0.0
  └─┬ eslint-config-react-app@7.0.0
    └── eslint-plugin-react@7.29.0

```

### Did you try recovering your dependencies?
- yes

### Environment

<!--
  To help identify if a problem is specific to a platform, browser, or module version, information about your environment is required.
  This enables the maintainers quickly reproduce the issue and give feedback.

  Run the following command in your React app's folder in the terminal.
  Note: The result is copied to your clipboard directly.

  `npx create-react-app --info`

  Paste the output of the command in the section below.
-->

```
Environment Info:

  current version of create-react-app: 5.0.0
  running from /<user_name>/.npm/_npx/69132/lib/node_modules/create-react-app

  System:
    OS: macOS 11.2.3
    CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
  Binaries:
    Node: 14.17.0 - ~/.nvm/versions/node/v14.17.0/bin/node
    Yarn: 1.22.17 - /usr/local/bin/yarn
    npm: 6.14.13 - ~/.nvm/versions/node/v14.17.0/bin/npm
  Browsers:
    Chrome: 98.0.4758.109
    Edge: Not Found
    Firefox: 96.0
    Safari: 14.0.3
  npmPackages:
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    react-scripts: ^5.0.0 => 5.0.0
  npmGlobalPackages:
    create-react-app: Not Found

```
Repository: material-ui
Issue: Custom new variant throws error but works
Labels: breaking change,component: menu

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯
https://github.com/mui/material-ui/issues/22602
I'm having the exact same issue but with the latest version of MUI and MuiMenu.
Although the styles I'm applying work, the error is thrown.

MuiMenu: { variants: [ { props: { variant: "nestedfilter" }, style: ...

And getting error:

`Warning: Failed prop type: Invalid prop "variant" of value "nestedfilter" supplied to "ForwardRef(Menu)", expected one of ["menu","selectedMenu"].`

### Expected behavior 🤔

Not to throw error.

### Steps to reproduce 🕹

Steps:

1. Create new variant in theme.js (createTheme) for MuiMenu
2. Apply prop variant="nestedfilter" to Menu (Menu from @mui/material)
3. Run project
4. Error is thrown


### Context 🔦

A custom menu styling.



### Your environment 🌎


Using 98.0.4758.102 (Official Build) (arm64)

<details>
  <summary>`npx @mui/envinfo`</summary>

```
  System:
    OS: macOS 12.1
  Binaries:
    Node: 17.3.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 8.3.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 98.0.4758.109
    Edge: Not Found
    Firefox: Not Found
    Safari: 15.2
  npmPackages:
    @emotion/react: ^11.7.1 => 11.7.1 
    @emotion/styled: ^11.6.0 => 11.6.0 
    @mui/base:  5.0.0-alpha.69 
    @mui/icons-material: ^5.4.1 => 5.4.1 
    @mui/material: ^5.3.1 => 5.4.3 
    @mui/private-theming:  5.4.2 
    @mui/styled-engine:  5.4.2 
    @mui/system:  5.4.3 
    @mui/types:  7.1.2 
    @mui/utils:  5.4.2 
    @types/react:  17.0.38 
    react: ^17.0.2 => 17.0.2 
    react-dom: ^17.0.2 => 17.0.2 
    typescript:  4.5.5 

```
</details>
Repository: flutter
Issue: [Android] SystemChrome.setPreferredOrientations doesn't set more than one orientation
Labels: platform-android,engine,a: layout,has reproducible steps,P2,found in release: 2.10,found in release: 2.11,team-android,triaged-android

## Steps to Reproduce

1.  add the following code into your main() method:

```dart
import 'package:flutter/material.dart';

void main() async {
  WidgetsFlutterBinding.ensureInitialized();
  await SystemChrome.setPreferredOrientations([
    DeviceOrientation.portraitUp,
    DeviceOrientation.landscapeLeft,
  ]);
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData(
        primarySwatch: Colors.blue,
      ),
      home: Scaffold(
        body: Center(
          child: ElevatedButton(
            onPressed: () {},
            child: const Text("Hello"),
          ),
        ),
      ),
    );
  }
}

```

**Expected results:**
The app should be able to run in landscape left mode and portrait mode

**Actual results:**
The app is locked to the first orientation inputted, in the case of the example, in portrait mode.

  <summary>Logs</summary>

<!--
     Run `flutter analyze` and attach any output of that command below.
     If there are any analysis errors, try resolving them before filing this issue.
-->

```
Analyzing example...                                                    
No issues found! (ran in 2.9s)

```

<!-- Finally, paste the output of running `flutter doctor -v` here. -->

```
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 2.10.2, on macOS 12.2.1 21D62 darwin-arm, locale it-IT)
[✓] Android toolchain - develop for Android devices (Android SDK version 32.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2021.1)
[✓] Connected device (2 available)
[✓] HTTP Host Availability

• No issues found!

```

</details>
Repository: vscode
Issue: Better path presentation in quick open window
Labels: feature-request,good first issue,quick-open

<!-- ⚠️⚠️ 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. -->

<!-- Describe the feature you'd like. -->
The way a file path is being presented in quick open window makes it sometimes hard to realise which file to pick. Let's consider two files:

- some_project/some_longer_pathsome_longer_pathsome_longer_pathsome_longer_path/fruits/apples/Main.js
- some_project/some_longer_pathsome_longer_pathsome_longer_pathsome_longer_path/fruits/bananas/Main.js

If we type "Main" in searchbox the list of results shows only begining of paths and the filenames and it looks ... excactly the same. At this point we have to randomly pick one of the files to check if it's the one we'd like especially since there's no preview editor triggered while navigating through result list (#8939).

![image](https://user-images.githubusercontent.com/2445240/155712282-6e656066-1771-42a2-a71a-63b9b68a263d.png)

The solution is to present the ending of a path rather than begining, just like it's done in Sublime Text (please notice where ellipsis is added):

![image](https://user-images.githubusercontent.com/2445240/155712089-383fe37a-c584-473d-8499-98abc2dc12f9.png)

Additionally path could be presented in a separate line for more clarity.
Repository: material-ui
Issue: [TextField] Label position and triangle icon button for drop down lists are not tied to root font size
Labels: bug 🐛,component: text field

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

Text field label position and small triangle button for drop down lists are not tied to root font size and become misaligned vertically if the root font changes, normally done for responsive fonts.
If the font is higher than 16px they remain too low
If the font is lower than 16px they remain too high

It happens because their position is specified in px and not rem, like the other parts of the components.
![mui bug1](https://user-images.githubusercontent.com/100418276/155717781-276ae2e8-f47b-4060-9b19-5fd8987cc44b.png)


The two issues are related and should be solved together because there are components that use both elements, like select and autocomplete

### Expected behavior 🤔

They should be tied to root font size to avoid misalignment and center them horizontally, like they are when font size is 16px


### Steps to reproduce 🕹

Steps:

1.Set any other root font size than the default 16px via css or browser settings
2.Check the position of the label when clicking inside it
3.
4.


### Context 🔦

it affects textfield, select and any other components that use them like autocomplete 

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>

```
    @emotion/react: ^11.7.1 => 11.7.1
    @emotion/styled: ^11.6.0 => 11.6.0
    @mui/base:  5.0.0-alpha.69
    @mui/icons-material: ^5.4.2 => 5.4.2
    @mui/material: ^5.4.2 => 5.4.2
    @mui/private-theming:  5.4.2
    @mui/styled-engine:  5.4.2
    @mui/system:  5.4.2
    @mui/types:  7.1.2
    @mui/utils:  5.4.2
    @types/react:  17.0.32
    react: ^17.0.2 => 17.0.2
    react-dom: ^17.0.2 => 17.0.2
    typescript:  4.5.5

any browser
```
</details>
Repository: material-ui
Issue: [Select] Two clicks needed to change to another element
Labels: component: select

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

1. Click first `<Select>` 
2. Click on second `<Select>` (closes the first one but doesn't switch to the next one)
3. Click on second `<Select>`again

### Expected behavior 🤔

1. Click first `<Select>` 
2. Click on second `<Select>` (closes the first one but switches to the next one)

### Steps to reproduce 🕹

Steps:

1. Click first `<Select>` 
2. Click on second `<Select>` (closes the first one but doesn't switch to the next one)
3. Click on second `<Select>`again

### Context 🔦

I want to have inline select components and be able to switch to either one of them with one click and not two.

### Your environment 🌎

Forked demo
https://codesandbox.io/s/selectvariants-material-demo-forked-zyw54r?file=/demo.js

<details>
  <summary>`npx @mui/envinfo`</summary>

```

  System:
    OS: macOS 12.1
  Binaries:
    Node: 17.3.0 - /usr/local/bin/node
    Yarn: Not Found
    npm: 8.3.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 98.0.4758.109
    Edge: Not Found
    Firefox: Not Found
    Safari: 15.2
  npmPackages:
    @emotion/react: ^11.7.1 => 11.7.1 
    @emotion/styled: ^11.6.0 => 11.6.0 
    @mui/base:  5.0.0-alpha.69 
    @mui/icons-material: ^5.4.1 => 5.4.1 
    @mui/material: ^5.3.1 => 5.4.3 
    @mui/private-theming:  5.4.2 
    @mui/styled-engine:  5.4.2 
    @mui/system:  5.4.3 
    @mui/types:  7.1.2 
    @mui/utils:  5.4.2 
    @types/react:  17.0.38 
    react: ^17.0.2 => 17.0.2 
    react-dom: ^17.0.2 => 17.0.2 
    typescript:  4.5.5 

```
</details>
Repository: material-ui
Issue: [material-ui][docs][Table] Clarify that all native HTML attributes that are supported
Labels: docs,component: table,package: material-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

I simply wanted to span a **TableCell** to 2 columns.

- I went to the official mui **TableCell** documentation, ie. https://mui.com/api/table-cell/
- Searched for options to do that in the props, and did not find anything.
- I tried to do it manually, and somehow decided to check on google, and found that There is a **colSpan** prop for that. And used it.


This is frustrating, since the documentation of mui doesn't all the list of props we can use. And Hence we have to search around for everything. This makes it hard to learn and work with.

### Expected behavior 🤔


- I go to the official mui **TableCell** documentation, ie. https://mui.com/api/table-cell/
- Search for props that allow to span columns
- Find it in the prop section and use it
Repository: PowerToys
Issue: provide setting to start web search in Incognito mode
Labels: Idea-Enhancement,Product-PowerToys Run,Run-Plugin

### Description of the new feature / enhancement

as title

### Scenario when this would be used?

in PowerToys Run

### Supporting information

_No response_
Repository: pytorch
Issue: ufunc codegen support for dtypes that are supported on CUDA but not CPU
Labels: triaged,module: codegen

### 🐛 Describe the bug

https://github.com/pytorch/pytorch/pull/65851#discussion_r813382618

### Versions

master

cc @ezyang @bhosmer @bdhirsh
Repository: rust
Issue: Trait resolution on associated type breaks with type inference for references
Labels: A-lifetimes,A-trait-system,A-associated-items,T-compiler,C-bug,fixed-by-next-solver

I tried this code ([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=7d833ff4e6403c0b4109c82b7cd98f85)):

```rust
fn foo<C>(_: C)
where
    for <'a> &'a C: IntoIterator,
    for <'a> <&'a C as IntoIterator>::IntoIter: ExactSizeIterator,
{}

fn main() {
    foo::<_>(vec![true, false]);
    // But this compiles fine
    // foo::<Vec<bool>>(vec![true, false]);
}
```

I expected this to compile just fine.
Instead, the following error is produced:
```log
 Compiling ref-into-inter-infer v0.1.0 (/home/veetaha/junk/rust-sandbox/crates/ref-into-inter-infer)
error[E0277]: the trait bound `for<'a> <&'a _ as IntoIterator>::IntoIter: ExactSizeIterator` is not satisfied
 --> crates/ref-into-inter-infer/src/main.rs:8:5
  |
8 |     foo::<_>(vec![true, false]);
  |     ^^^^^^^^ the trait `for<'a> ExactSizeIterator` is not implemented for `<&'a _ as IntoIterator>::IntoIter`
  |
  = help: the following implementations were found:
            <&mut I as ExactSizeIterator>
note: required by a bound in `foo`
 --> crates/ref-into-inter-infer/src/main.rs:4:49
  |
1 | fn foo<C>(_: C)
  |    --- required by a bound in this
...
4 |     for <'a> <&'a C as IntoIterator>::IntoIter: ExactSizeIterator,
  |                                                 ^^^^^^^^^^^^^^^^^ required by this bound in `foo`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `ref-into-inter-infer` due to previous error
```
Note that when an explicit type is specified in generic parameters, the code compiles just fine.

### Meta

`rustc --version --verbose`:
```
rustc 1.58.1 (db9d1b20b 2022-01-20)
binary: rustc
commit-hash: db9d1b20bba1968c1ec1fc49616d4742c1725b4b
commit-date: 2022-01-20
host: x86_64-unknown-linux-gnu
release: 1.58.1
LLVM version: 13.0.0
```
Repository: flutter
Issue: Need a way to include only a specific platform implementation from a plugin
Labels: c: new feature,tool,P3,a: plugins,team-tool,triaged-tool

How can we enable plugins for a single platform only?
Problem:-  I need to use a plugin in Android implementation. But I don't want to use the same on iOS.
Repository: flutter
Issue: Use dependency graph to determine plugin initialization order
Labels: tool,P2,a: plugins,team-tool,triaged-tool

Currently the initialization order of plugins is arbitrary (probably alphabetical right now); we should use the package dependency graph to initialize them in an order that matches the dependencies in case there are registration-time calls between them.
Repository: PowerToys
Issue: Provide shortcut to increase snapped windows size
Labels: Idea-Enhancement,Product-FancyZones

### Description of the new feature / enhancement

say if the middle window is not large enough, I want to use a keystroke like Win+'+' or something to increase the width, maybe 10% each time.

it shall temporarily increase the zone size.

### Scenario when this would be used?

zone

### Supporting information

_No response_
Repository: vscode
Issue: Replace `resourceUriProvider` web api with a descriptive/template variant
Labels: feature-request,extension-host,web

This would help with supporting loading extensions running in the web worker extension host from the server and allowing that they are able to create web workers. The current synchronous function based API cannot be invoked from a child worker.

This would help in supporting #144235

cc @jrieken
Repository: godot
Issue: Control Node: Reparent to New Node doesn’t use its children’s data for Rect Size and XY Position
Labels: enhancement,discussion,topic:editor,usability

### Godot version

3.4.2 Stable

### System information

macOS 12.1 (21C52)

### Issue description

When using the command "Reparent to New Node", which essentially is a fancy way of saying "Group to New Node", the newly created Node should use its children Rect data for its own Rect data, as it is the case in all industry standard softwares like Figma, Illustrator and others.

This would avoid many, many unnecessary clicks and headaches.

### Steps to reproduce

1. Add a Node.
2. Change its size and position it elsewhere than the default position.
3. Create another Node.
4. Change its size and position it elsewhere than the default position and the previous node’s position.
5. Select both Nodes.
6. Use the Reparent to New Node command.
7. Notice how the newly created Node completely ignores its children’s Rect data, by using a 40 x 40 Rect Size with a 0, 0 Position.

### Minimal reproduction project

_No response_
Repository: vscode
Issue: Unable to rename/create a file when window has no focus.
Labels: bug,file-explorer

Does this issue occur when all extensions are disabled?: Yes

Version: 1.65.0-insider (Universal)
Commit: a0da9978b10ae0b9307c7f545b50a8500efff7eb
Date: 2022-02-21T05:14:59.303Z
Electron: 16.0.9
Chromium: 96.0.4664.174
Node.js: 16.9.1
V8: 9.6.180.23-electron.0
OS: Darwin x64 21.3.0

Steps to Reproduce:

1. Make sure the window is not focused
2. Right click a file and choose 'Rename', 'New File' or 'New Folder'
3. Type a name

Expected result:
Either the window gains focus after right clicking, or the context menu never appears, or the options that cause issues are greyed out, or the text field doesn't disappear once the window gains focus.

Actual result:
Rename text field appears without a focus highlight, and it's impossible to (re)name a file. Focussing the window makes the text field disappear and the rename/file creation operation is aborted.

https://user-images.githubusercontent.com/2737650/155749032-9bacaca6-0e85-45ee-b0ee-8fa5a6520885.mp4
Repository: material-ui
Issue: [migration] How to solve conflict between my project using v5 and third-party packages using v4?
Labels: support: question,v5.x migration

My project has just been updated to Mui v5 (https://mui.com/). And one of used package react-page (https://github.com/react-page/react-page) in the project uses Mui v4 (https://v4.mui.com/). And some conflicts just showed up. When I use the module importing the react-page, the style sheet of mui v4 covered the current style sheet of mui v5. How can I prevent mui v4 from covering all style sheets and make sure mui v5 is still working as before?
Repository: flutter
Issue: Maintain scroll location to prevent content jumping when network images or dynamic network content loads into a listview that has already been laid out
Labels: framework,f: scrolling,d: stackoverflow,P3,team-framework,triaged-framework

Consider, if there is a `ListView` with a number of variable height Widgets with further contain network image's that load at their own pace.

When the images load, the height of each individual listview item widget will change (increase) appropriately

If this set of events occurs above the users current scroll position in the listview, then the content will shift / jump.  The result is that the user is now looking at content that was formerly above their last viewed position.  

This gives for bad user experience.

Is it possible to add an option to listviews (or any scrollable view) that the scroll position should maintain itself relative to the bottom extent of the listview when a layout change occurs above the current position or vice versa when it occurs under neath the current position (as it is currently works).  In this way from the user POV, there is not content jumping effect

In the HTML/CSS world this effect has sometimes been called Layout Jank (https://css-tricks.com/the-fight-against-layout-jank/) which has been addressed with various forms of scroll anchoring 
(https://blog.chromium.org/2017/04/scroll-anchoring-for-web-developers.html)  
(https://developer.mozilla.org/en-US/docs/Web/CSS/overflow-anchor/Guide_to_scroll_anchoring)

https://www.youtube.com/watch?time_continue=15&v=-Fr-i4dicCQ&feature=emb_title

In this case, it would apply to not just a webview but I guess anything that could be controlled by a `ScrollContoller`?