sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: Test the built -in server is very slow, use ApacheBench.
Labels: bug,Runtime

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
$ npx --no-install next info

    Operating System:
      Platform: linux
      Arch: x64
      Version: #1 SMP PVE 5.15.107-2 (2023-05-10T09:10Z)
    Binaries:
      Node: 18.16.0
      npm: 9.5.1
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.4.5-canary.6
      eslint-config-next: 13.4.4
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.0.4
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

### Link to the code that reproduces this issue or a replay of the bug

npx create-next-app@latest 

### To Reproduce

```
npx create-next-app@latest 
```
use default config.

```
npm run build
npm run start
```

### Describe the Bug

Very slow response speed and concurrency.

```
$ ab -n 10000 -c 100 http://192.168.100.10:3000/   
This is ApacheBench, Version 2.3 <$Revision: 1903618 $>
Copyright 1996 Adam Twiss, Zeus Technology Ltd, http://www.zeustech.net/
Licensed to The Apache Software Foundation, http://www.apache.org/

Benchmarking 192.168.100.10 (be patient)
Completed 1000 requests
Completed 2000 requests
Completed 3000 requests
Completed 4000 requests
Completed 5000 requests
Completed 6000 requests
Completed 7000 requests
Completed 8000 requests
Completed 9000 requests
Completed 10000 requests
Finished 10000 requests


Server Software:        
Server Hostname:        192.168.100.10
Server Port:            3000

Document Path:          /
Document Length:        16160 bytes

Concurrency Level:      100
Time taken for tests:   11.076 seconds
Complete requests:      10000
Failed requests:        0
Total transferred:      164740000 bytes
HTML transferred:       161600000 bytes
Requests per second:    902.82 [#/sec] (mean)
Time per request:       110.764 [ms] (mean)
Time per request:       1.108 [ms] (mean, across all concurrent requests)
Transfer rate:          14524.49 [Kbytes/sec] received

Connection Times (ms)
              min  mean[+/-sd] median   max
Connect:        0    0   0.2      0       3
Processing:    37  110  14.5    107     257
Waiting:       32  110  14.4    107     257
Total:         37  110  14.5    107     257

Percentage of the requests served within a certain time (ms)
  50%    107
  66%    111
  75%    115
  80%    118
  90%    126
  95%    135
  98%    145
  99%    160
 100%    257 (longest request)
```

### Expected Behavior

Real：
```
Requests per second:    856.75 [#/sec] (mean)
```
Estimate
```
Requests per second:    5000.75 [#/sec] (mean)
```

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

next start
Repository: terminal
Issue: Ability to close tabs with mouse middle click when close ("x") button is hidden (#3335)
Labels: Help Wanted,Issue-Bug,Area-UserInterface,Product-Terminal,Priority-3



# Description of the new feature/enhancement

## Problem
Can't close tab using mouse middle click.

## Consequence
This is a consequence of #3335 (hide close button (x) on tabs).

## Possible workaround not perfect
I think keyboard shortcuts are not a solution when you browse tabs with mouse.


# Feature result

When close button is hidden, user can close tab using the mouse middle click
Repository: godot
Issue: GPUParticles2D speed_scale = 0 does not pause & causes  artifacts when damping != 0
Labels: bug,topic:rendering,confirmed,topic:particles

### Godot version

4.1-dev4_linux

### System information

Godot v4.1.dev4 - Fedora Linux 37 (Workstation Edition) - Vulkan (Forward+) - integrated Intel(R) Graphics (ADL GT2) () - 12th Gen Intel(R) Core(TM) i7-1280P (20 Threads)

### Issue description

**Expected behavior**

Setting `speed_scale = 0` should pause particles, based on this tooltip:

![speed_scale tooltip](https://github.com/godotengine/godot/assets/364501/8d38856c-12ae-41c6-ab22-d9654c4f227d)

**Actual behavior**

Setting `speed_scale = 0` causes jitter in even a "default" particle effect. If the particles include damping, a scale of zero has significant visual bugs (perhaps timejumping backwards?). If they include a scale ramp, it also seems to undo that ramp:

[particle-freeze-bug.webm](https://github.com/godotengine/godot/assets/364501/9d473a43-94c2-4b79-b549-5a679cb699fe)


### Steps to reproduce

1. Add a GPUParticles2D node & set up a minimal configuration to see some particles
2. Give it damping and a scale ramp
3. Set `speed_scale = 0`

### Minimal reproduction project

[particle-freeze-bug.zip](https://github.com/godotengine/godot/files/11666260/particle-freeze-bug.zip)
Repository: godot
Issue: Godot crashes entire Computer when building C# script
Labels: bug,platform:windows,needs testing,topic:dotnet,crash

### Godot version

4.0.3

### System information

Windows 7 

### Issue description

Hello,

whenever i try to compile and build a C# script in Godot, it gets stuck at 0% and crashes my entire PC.
I run Windows 7 SP2.

### Steps to reproduce

Just add a C# script to a node and try to run the scene.

### Minimal reproduction project

[instancing_starter.zip](https://github.com/godotengine/godot/files/11666295/instancing_starter.zip)
Repository: godot
Issue: ItemList focus rectangle can be drawn outside of the bounds of a ScrollContainer
Labels: bug,confirmed,topic:gui

### Godot version

v4.0.2.stable.official [7a0977ce2]

### System information

Windows 10, Forward+

### Issue description

Somewhat related to #36164, ScrollContainers don't seem to clip the focus rectangle of ItemLists, causing a visual bug:
<img width="223" alt="image" src="https://github.com/godotengine/godot/assets/85553012/494844c3-b19f-4adb-947c-405ccae1006e">
The issue seems to be specific to ItemLists, I've tested it with both Buttons and LineEdits, and both had the content as well
as the focus rectangle clipped correctly.


https://github.com/godotengine/godot/assets/85553012/6b57bc75-729c-4155-b535-d7ad30873185



### Steps to reproduce

Bug can be reproduced with a similar node tree:
![image](https://github.com/godotengine/godot/assets/85553012/1f0985b1-7266-4711-b9a3-99feb8a86afd)


### Minimal reproduction project

N/A
Repository: next.js
Issue: Image serving broken when using custom handler in dev mode with a `basePath` after `v13.4.3-canary.2`
Labels: bug,Image (next/image)

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.5.0: Mon Apr 24 20:51:50 PDT 2023; root:xnu-8796.121.2~5/RELEASE_X86_64
    Binaries:
      Node: 18.14.0
      npm: 8.19.2
      Yarn: 1.22.19
      pnpm: N/A
    Relevant packages:
      next: 13.4.5-canary.6
      eslint-config-next: 13.4.4
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.3
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Image optimization (next/image, next/legacy/image)

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/next-img-double-prefix-bug-7yxito?file=%2Fpackage.json%3A8%2C29

### To Reproduce

1. Create a new Next.js project
2. Configure a non-empty `basePath`
3. Create a simple custom server (I used express)
4. Add a bitmap image (png, jpeg, etc.) to the rendered page

### Describe the Bug

The resulting image URL is output with the `basePath` applied twice, which causes the ensuing browser fetch to fail with a 404.

I did some digging and found that the cause of this bug is that [this line](https://github.com/vercel/next.js/blob/43fb7249b6c3a4dfdc9cae6a8a99addc00fde6ee/packages/next/src/server/config.ts#L335) gets run twice, both times resulting in the `imageConfigDefault.path` being modified. I have traced this bug down to [between v13.4.3-canary.2 and v13.4.3-canary.3](https://github.com/vercel/next.js/compare/v13.4.3-canary.2...v13.4.3-canary.3).

### Expected Behavior

The `basePath` should only be applied once

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

express
Repository: material-ui
Issue: [material-ui][Stepper] Add props to StepIcon so we can change the error and completed Icon.
Labels: new feature,component: stepper,package: material-ui

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

So I was ask to change the StepIcon icon when the state of the step is completed or error.

The default step icon in itself is fine with the numbering logic and all, and can also be overwrite with a static icon with the icon props instead of number. So all this is good. But if you want to keep this logic and all, but use a different static icon for error or completed step, then I did not find any elegant way of doing so. I think simply adding the props iconError and iconCompleted would solve this problems and make it more elegant and easier to do so.

At the moment to do this I had to make my own custom StepIcon component where I take your original code and replace the StepIconRoot "as" props with my own custom icon in the error and completed condition. Then feed this custom component to the StepIconComponent props of the StepLabel component.

Unless there a better way of doing this, I think my proposition is the simplest way to have an elegant solution for this use case. Also not sure why those 2 icon are "hardcoded" in the first place.

### Examples 🌈

Here the link to the original code i'm referring to (line 74 and 86):

https://github.com/mui/material-ui/blob/master/packages/mui-material/src/StepIcon/StepIcon.js



### Motivation 🔦

Simply want an elegant solution for this use case where I don't have to use one of your component original code and change 2 line of it, make the maintenance of this component harder since I would have to update it every time  you update it on your side.

I could probably do a PR for this, but wanted to discuss it here before to make sure what i'm saying make sense and if there not a beater solution already in place to solve this use case.
Repository: rust
Issue: Constify BuildHasherDefault construction
Labels: T-libs-api,C-feature-request,A-const-eval

This would enable building HashMaps in const contexts.
Repository: nvm
Issue: "help" intercepts commands run by exec and run
Labels: informational,pull request wanted

<!-- Thank you for being interested in nvm! Please help us by filling out the following form if you‘re having trouble. If you have a feature request, or some other question, please feel free to clear out the form. Thanks! -->

#### Command

```bash
# Run node --help with the specified version
nvm exec lts/hydrogen node --help
```

#### What happened?

NVM outputs its help command.

#### What did you expect to happen?

I expected the `--help` flag to be passed to `node`

#### Potential Solution

I understand why the `help` command takes precedense since its useful for just plopping it at the end of a command to get help on said command. However, this really ruins any situations where one might be using `nvm exec` as a replacement to `node`, effectively making it a pain to run anything else's help command.

My primary usage is to use nvm behind-the-scenes as an environment manager, so any time someone specifies "help" in my use-case, it is intended for node, npm, or whatever the command they are running is and **not** NVM. The user would never be running `nvm` directly, but rather a custom CLI that passes args through NVM when necessary to run them at the correct version **without** updating the default NVM version that's in use elsewhere on the user's machine.

Thus, I propose `NVM_NO_HELP=1`.

```diff
...
  # nvm.sh, line 2820
  case $i in
    --) break ;;
    '-h'|'help'|'--help')
    NVM_NO_COLORS=""
+   if [[ "$NVM_NO_HELP" -eq 1 ]]; then
+     break;
+   fi
    for j in "$@"; do
...
```

This flag, if specified, will instruct NVM to not respond to help requests.

I'm not very skilled with bash so I imagine there's a better solution out there; but the code snippet above works on my local installation of nvm and lets me bypass the help command.

```bash
NVM_NO_HELP=1 nvm exec lts/hydrogen node --help
# correctly outputs node v18's help command!
```

#### Conclusion

Please let me know if you think this is something that is worth fixing in future versions of NVM. It would certainly help my use-case and allow me to avoid modifying `nvm.sh` just to escape help commands.

Thanks.
Repository: terminal
Issue: Support "hide taskbar icon"
Labels: Product-Terminal,Issue-Task,Area-Windowing

# Description of the new feature/enhancement

I'd like an option to always hide the taskbar icon, which would often be used with "Always display an icon in the notification area". This frees up taskbar space for those of us who always use global summon or Quake mode.

# Proposed technical implementation details (optional)

[ConEmu](https://github.com/Maximus5/ConEmu) source should have the API call somewhere, per its setting: General > Task bar > Taskbar buttons > Don't show ConEmu window on Taskbar.

Perhaps the setting would look like this, but open to suggestions:  
![image](https://github.com/microsoft/terminal/assets/6148201/7bdabb94-de53-4748-ba9e-97f7f2bce5e6)
Repository: vscode
Issue: Test Explorer: Sort tests by name
Labels: feature-request,testing

I want to run one specific test from the Test Explorer. The tree view is organized well, but tests in the same file are not sorted in any way that makes them easy to find. The only workaround is the search bar.

Please add a setting to sort tests in the same file by name.
Repository: puppeteer
Issue: [Bug]: Download failure error reports are misleading and should include the URL
Labels: feature,confirmed,disable-analyzer

### Bug expectation

I expect that the error message displayed and logged when npm install fails due to a download failure will indicate that there was a download failure, and will include the URL that failed.

Instead, the error message is:

```
ERROR: Failed to set up Chrome r113.0.5672.63!
```
Technically this is correct, but "set up" implies that there was some sort of configuration error.  It would be much clearer if the error message indicated it was a "download" failure rather than a "set up" failure, and it should include the URL:

```
ERROR: Failed to download Chrome r113.0.5672.63 from https://edgedl.me.gvt1.com/edgedl/chrome/chrome-for-testing/113.0.5672.63/win64/chrome-win64.zip
```

### Bug behavior

- [ ] Flaky
- [ ] PDF

### Minimal, reproducible example

```Batchfile
echo "127.0.0.1 edgedl.me.gvt1.com" >> C:\Windows\System32\drivers\etc\hosts
npm add puppeteer
```


### Error string

Failed to set up Chrome r113.0.5672.63!

### Puppeteer configuration

_No response_

### Puppeteer version

20.5.0

### Node version

18.14.1

### Package manager

npm

### Package manager version

9.6.7

### Operating system

Windows
Repository: godot
Issue: Changing Group Order of a Thread Group doesn't seem to change or do anything.
Labels: bug,topic:core,topic:editor

### Godot version

4.1 dev4

### System information

Windows 10, Nvidia GTX 1660Ti, Vulkan

### Issue description

I tried to set Thread Order but it always stays at 0. I set the thread to main as well as sub no changes.
I tried this with different 3D nodes but to no avail.
I've tried checking the group order by script but it also only prints 0, I also tried to change it through a script but that also returns only 0.
I tried to enable threading in all settings in godot I could find in case it mattered (?).

I'm not sure if I'm doing anything wrong or missing something but I can't find anyone else who would know or was able to help - well it's a brand new feature.

I apologize if I'm missing something, my brain has a size of pea. :(

(It was added in dev 3 release, same issue so I labeled this with the latest I tried)

### Steps to reproduce

Open a new project, add Node3D and then in Inspector in Process section change Group to Sub Thread/Main Thread and then try changing Group Order to anything but zero. Nothing changes.

### Minimal reproduction project

None, there's no special set up for this.
Repository: opencv
Issue: CV_DnnSuperResSingleOutputTest and CV_DnnSuperResMultiOutputTest test failures on Core 2 Duo
Labels: bug,category: superres,category: dnn

### System Information

OpenCV version: 4.7.0
Operating System / Platform: Guix System
Compiler & compiler version: GCC 11.3.0

### Detailed description

Attempting to build OpenCV .4.7.0 on a Core 2 Duo old x86_64 processor (Q6700 quad core) causes 3 test suites to fail:

```
The following tests FAILED:
          8 - opencv_test_photo (Failed)
         12 - opencv_test_dnn (SEGFAULT)
         13 - opencv_test_dnn_superres (Failed)
```

The full build log is attached.
[vw95zg7kngg50959l70q72cy092sc7m9-opencv-4.7.0.drv.txt](https://github.com/opencv/opencv/files/11669159/vw95zg7kngg50959l70q72cy092sc7m9-opencv-4.7.0.drv.txt)


### Steps to reproduce
```
# Install Guix on an Core 2 Duo x86_64 machine
wget -O- guix-install.sh https://guix-install.sh && yes | sudo ./guix-install.sh

# Have it on the same commit used to test:
guix pull --commit=deda3cc9057f20b1e3d34d63a64da0bdd6ca1998

# Logout, then back in.

# Run the test
guix build opencv --keep-failed
```
### 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
- [X] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: PowerToys
Issue: Explorer file preview: Scrolling not working with external trackpoint keyboard, scrollbar not working after mouse left window during dragging
Labels: Issue-Bug,Priority-3,Product-File Explorer

### Microsoft PowerToys version

0.70.1

### Installation method

PowerToys auto-update, Microsoft Store

### Running as admin

No

### Area(s) with issue?

File Explorer: Preview Pane

### Steps to reproduce

1. Buy an external Thinkpad keyboard with trackpoint (I have a Bluetooth one) and set it up
2. Click a PDF or text file in Explorer
3. Press Ctrl+Space to activate the file preview
4. Attempt to scroll in the preview with the external keyboard
5. Notice that it doesn't work
6. Attempt to scroll by dragging the scrollbar
7. Move the mouse a bit outside the window while dragging
8. Notice that it snaps back to the top (while this is not an issue in other programs, try in Chrome for example)

### ✔️ Expected Behavior

Scrolling working normally (scrolling with external keyboard working, dragging scrollbar working even when mouse is a bit outside the window)

### ❌ Actual Behavior

* Using the trackpoint on the external Thinkpad keyboard to scroll has no effect.
* Dragging the scrollbar and leaving the window with the mouse while dragging it makes the scrollbar jump back to where it was instead of following the mouse's Y position anyway.

### Other Software

Driver from https://support.lenovo.com/us/en/solutions/pd026744-thinkpad-compact-bluetooth-keyboard-with-trackpoint-overview-and-service-parts

I'm on Windows 10 22H2
Repository: pytorch
Issue: Increased / more verbose type aliases for improved readability of user defined content
Labels: module: typing,triaged,enhancement,needs research

### 🚀 The feature, motivation and pitch

Right now PyTorch exports a few classes and has a few type aliases under `torch.types`. 
While these are useful, for those working with pytorch there may be a case to use `TypeAlias` to help clarify arguments and return statements. For example consider just a few of the following aliases:

```python
TorchDevice: TypeAlias = Union[Device, TorchDeviceTypes]


TorchTensor: TypeAlias = Union[tuple(torch._tensor_classes)] # could be just torch.Tensor, but doesn't offer all the hints
TorchTensors: TypeAlias = Sequence[TorchTensor]
TorchLayer: TypeAlias = torch.nn.Module
TorchLayers: TypeAlias = Sequence[TorchLayer]

TorchLoss: TypeAlias = torch.nn.Module
TorchLosses: TypeAlias = Sequence[TorchLoss]

StateDict: TypeAlias = dict
MaskTensor: TypeAlias = Union[torch.BoolTensor, torch.IntTensor]

HiddenState: TypeAlias = TorchTensor
CellState: TypeAlias = TorchTensor

GRUState: TypeAlias = HiddenState
LSTMStates: TypeAlias = Tuple[HiddenState, CellState]

RNNStates: TypeAlias = Union[GRUState, LSTMStates]
```

Suppose someone is defining custom layer that users can initialize with either a `GRU` or `LSTM`.  Showing that the forward call returns `Tuple[Tensor, RNNStates]` may help developer more readily remember that `RNNStates` is either a single `tensor`, or a `tuple`, which could otherwise be overlooked. 

Likewise `TorchLayer` and `TorchLoss`, while both an alias for `nn.Module` would help clarify if someone is passing a loss function or a layer into a model a wider variety of what expect input is. 


Does PyTorch need an `torch.aliases` submodule  with a bunch of different aliases to use? Not technically. I do, however, find working with others on projects where doing so can make things much more clear for collaboration. One could also just use longer type annotations, but I find those eventually clutter code e.g.

```
def foo(..., rnn_states: Union[torch.Tensor, Tuple[torch.Tensor, torch.Tensor]], ...):
    pass
```

It is just a preference.

### Alternatives

_No response_

### Additional context

I put it in a [PR](https://github.com/pytorch/pytorch/pull/102914#issuecomment-1578935718)

cc @ezyang @malfet @rgommers @xuzhao9 @gramster