sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: database/sql: few usable connections in connection pool after network packet loss event
Labels: NeedsInvestigation

### Go version

go version go1.20.6 linux/amd64

### What operating system and processor architecture are you using (`go env`)?

```shell
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/shipeng/.cache/go-build"
GOENV="/home/shipeng/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/pay/src/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/pay/src/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.20.6"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-O2 -g"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-O2 -g"
CGO_FFLAGS="-O2 -g"
CGO_LDFLAGS="-O2 -g"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/pay/tmp/go-build1095428125=/tmp/go-build -gno-record-gcc-switches"
```


### What did you do?

We’re using pgx v4 as driver and database/sql as connection pool for client requests and database connections. Our server and database are in different regions, causing a 50 - 60 ms network latency. We're having an issue where our host can't recover and complete client queries in time, even after network recovered from prior packet loss events. Check this link to see how to reproduce the issue with script: https://github.com/spencer-x/go-database-sql-issue#ways-to-reproduce-the-issue-in-linux-machine.

### What did you expect to see?

Service host should be able to serve requests within timeout limits after network recovers.

### What did you see instead?

Even after the network between the host and the database recovered, client requests continued to timeout. The number of open connections reported from the connection pool stats was considerably higher (200) than the actual number of connections reported from the PostgreSQL database (20-30).

We tried to look into the issue and found that many connections were closed during the network packet loss event. Subsequently, even after the network was recovered, pgx continued to close the connection when clients canceled the query due to context timeout. The connection opener in database/sql rapidly [increased](https://github.com/golang/go/blob/2c358ffe9762ba08c8db0196942395f97775e31b/src/database/sql/sql.go#L1206C6-L1206C13) the count of db.numOpen, but the opening of new connections [was sequential and relatively slow](https://github.com/golang/go/blob/2c358ffe9762ba08c8db0196942395f97775e31b/src/database/sql/sql.go#L1222C7-L1222C24). Consequently, there were few usable connections available from the connection pools.
Repository: node
Issue: HTTP/2 null pointer exceptions in insecure server.
Labels: http2

### Version

v20.9.0

### Platform

Darwin KH7JWKR9RD 23.1.0 Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000 arm64

### Subsystem

_No response_

### What steps will reproduce the bug?

I am trying to write an insecure HTTP2 web server. However it crashes on any inputs.

Code to reproduce:

```typescript
import { createServer } from 'node:http2';

import createExpressApp from 'express';
import http2ExpressBridge from 'http2-express-bridge';

// Test with: curl --insecure -v -k --http2-prior-knowledge "http://[::]:8080"
function main(): void {
  const app = http2ExpressBridge(createExpressApp);

  app.get('*', (request, response) => {
    response.setHeader('Content-Type', 'text/plain');
    response.status(200);
    response.write('Server reached');
    response.end();
  });

  const server = createServer(app);

  server.listen({ port: 8080 });

  // Triggered by CMD/CTRL + C .
  process.on('SIGINT', () => {
    server.close();
    process.exit(0);
  });
}

try {
  main();
} catch (error) {
  console.error(error);
  process.exit(1);
}
```

when I run the server and then query it with `curl --insecure -v -k --http2-prior-knowledge "http://[::]:8080"` it crashes with a short stacktrace deep within node that I'm unable to debug/troubleshoot.

### How often does it reproduce? Is there a required condition?

Happens every time.

### What is the expected behavior? Why is that the expected behavior?

When I add an SSL cert to this server, and run `createSecureServer` instead of `createServer`, everything work fine.

```shell
web-platform % curl --insecure -v -k --http2-prior-knowledge "http://[::]:8080"
Server reached%
```    

### What do you see instead?

Instead `curl` hangs, and the server crashes with the following stack trace:

```shell
> tsx src/example/http2BugRepro.ts

node:events:492
      throw er; // Unhandled 'error' event
      ^

TypeError: Cannot read properties of undefined (reading 'readable')
    at IncomingMessage._read (node:_http_incoming:214:19)
    at Readable.read (node:internal/streams/readable:547:12)
    at resume_ (node:internal/streams/readable:1048:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
Emitted 'error' event on IncomingMessage instance at:
    at emitErrorNT (node:internal/streams/destroy:151:8)
    at errorOrDestroy (node:internal/streams/destroy:214:7)
    at Readable.read (node:internal/streams/readable:549:7)
    at resume_ (node:internal/streams/readable:1048:12)
    at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
```

### Additional information

As you can see this only happens when there's no SSL and stracktrace contains no other pointer for me to latch onto.
Repository: vscode
Issue: Allow creation of multiple files and folders using comma-separated input
Labels: feature-request,file-explorer

<!-- ⚠️⚠️ 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. -->

### Description:
As a user of VSCode, I often find the need to create multiple files and folders simultaneously within the editor. Presently, there isn't a native functionality to create multiple files or folders through a single input command.

### Feature Request:
I propose implementing a feature that enables users to create multiple files and folders by entering their names in a comma-separated format.

### Expected Behavior:

- **For creating multiple files**: Users should be able to input a list of file names separated by commas (e.g., server.ts, app.ts) in the input box. Upon execution, VSCode will create these files accordingly.

- **For creating multiple folders:** Users should be able to input a list of folder names ending with a forward slash (e.g., utils/, routes/) in input box. Subsequently, VSCode will create these folders within the project workspace.

### Example Input:

- **To create multiple files:**  server.ts, app.ts

- **To create multiple folders:** utils/, routes/

- **Create multiple files and folders at once:** server.ts, app.ts, utils/, routes/, utils/db.ts, utils/data.json, routes/index.ts

### Expected Output:
Upon inputting the specified file and folder names, VSCode should create the requested files and folders in the current working directory.

### Additional Notes:
This feature would significantly enhance productivity by allowing users to create the necessary file and folder structure swiftly within VSCode itself, reducing manual efforts and streamlining the development process.
Repository: svelte
Issue: Add the `onappinstalled` event to `window`'s type declarations
Labels: types / typescript

### Describe the problem

The Svelte type declarations for the `svelte:window` already include `onbeforeinstallprompt`, but its counterpart [`onappinstalled`](https://developer.mozilla.org/en-US/docs/Web/API/Window/appinstalled_event) isn't recognized:

![image](https://github.com/sveltejs/svelte/assets/119128472/d1052433-65ed-4384-b212-8bf8018e8d0c)


### Describe the proposed solution

Add `onappinstalled` to `SvelteWindowAttributes`

### Alternatives considered

N/A

### Importance

nice to have
Repository: svelte
Issue: Add the specific event type for `onbeforeinstallprompt`
Labels: types / typescript

### Describe the problem

`svelte:window` recognizes the `onbeforeinstallprompt` event, but its event type is just `Event` rather than `BeforeInstallPromptEvent`, whereas `BeforeInstallPromptEvent` has other important, specific properties/methods, like `prompt()` and `userChoice`, which anyone listening for `onbeforeinstallprompt` is almost always interested in.
See [MDN](https://developer.mozilla.org/en-US/docs/Web/API/BeforeInstallPromptEvent).

### Describe the proposed solution

Would you please consider adding the type? Since `onbeforeinstallprompt` is already recognized, it makes sense to go all the way and provide the accurate typing for it as well.

### Alternatives considered

Manually declaring a type and doing a type assertion.

### Importance

nice to have
Repository: PowerToys
Issue:  issue causing FancyZones not to be able to zone specific apps: League of Legends in window'd mode 
Labels: Issue-Bug,Product-FancyZones,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.76.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

League of Legends in window'd mode 
Hold shift key to activate while dragging window - OFF 

### ✔️ Expected Behavior

Window to snap into fancy zone as it did on older versions of the app

### ❌ Actual Behavior

Window does not highlight the zones and does not snap into place 

### Other Software

_No response_
Repository: rust
Issue: consistently elide/don't elide types in diagnostics
Labels: A-diagnostics,T-compiler,E-medium

right now, the decision of whether to fully elide the type as `_` is inconsistent - it never happens for functions, fn pointers, tuples, refs where the pointee types are equal, or adts, but it *does* happen for primitives and ADTs behind a raw pointer. that is probably not intended? might be worth moving the `t1 == t2` comparison up above the big match for consistency. https://github.com/rust-lang/rust/blob/eb53721a34d1d910b900aa753e0a00dc72ef41ac/compiler/rustc_infer/src/infer/error_reporting/mod.rs#L1510-L1512

here is an example of it being inconsistent: https://github.com/rust-lang/rust/blob/cf2dff2b1e3fa55fa5415d524200070d0d7aacfe/tests/ui/issues/issue-17905-2.stderr#L23-L26
`isize` is elided but `str` is not.

i originally changed this to almost always elide the type, but @estebank is worried that will be confusing:
![image](https://github.com/rust-lang/rust/assets/23638587/0fa3d986-b0cf-472c-afe1-f04373e255eb)
he suggested instead eliding if the type has either type params or projection types ("looks complicated", basically).

_Originally posted by @jyn514 in https://github.com/rust-lang/rust/issues/118730#issuecomment-1846520771_

@rustbot label +A-diagnostics +E-medium
Repository: deno
Issue: WebAssembly streaming API fails with inspector
Labels: bug,debugger

- Steps to reproduce by slightly altering the example of <https://docs.deno.com/runtime/manual/runtime/webassembly/using_streaming_wasm>
  - Run `curl https://wpt.live/wasm/incrementer.wasm -o incrementer.wasm` to get the wasm file
  - Create a file named "index.ts" with following contents:
  ```typescript
  const { instance, module } = await WebAssembly.instantiateStreaming(
    fetch(new URL("./incrementer.wasm", import.meta.url)),
  );
  const increment = instance.exports.increment as (input: number) => number;
  console.log(increment(41));
  ```
  - Run `deno run --inspect-brk --allow-read ./index.ts`
  - Visit `chrome://inspect` to connect to the debugger and execute the program

- Expected output
  - Log `42` on the console

- Actual output
```
error: Uncaught (in promise) TypeError: WebAssembly.compile(): Argument 0 must be a buffer source
    at eventLoopTick (ext:core/01_core.js:178:11)
```

Also tested with VSCode debugger

- Version: 
  - Deno 1.38.4
  - Chrome 120.0.6099.71
  - VSCode 1.84.2
  - macOS Sonoma 14.0
Repository: puppeteer
Issue: Fix ng-schematics release-please
Labels: bug,upstream,confirmed

Somehow the release please config was not updated so it resulted in duplicate releases https://github.com/puppeteer/puppeteer/pull/11508
Repository: material-ui
Issue: [styled-engine-sc] TS error when using a `css`-variable within `styled`
Labels: typescript,package: system,customization: theme,customization: css

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://codesandbox.io/p/devbox/mui-theme-scoping-within-css-and-css-within-styled-knpr8m?file=%2Fsrc%2FApp.tsx

Steps:

1. Open the provided link


### Current behavior 😯

1. TS throws error when using a `css`-variable within `styled`: `Property 'variants' is missing in type 'Interpolation<object>[]' but required in type 'CSSObjectWithVariants<any>'.`
2. We have to use `THEME_ID` to access the MUI theme

### Expected behavior 🤔

1. It must be possible to use a `css`-variable within `styled`, without getting a TS error.
2. Theme scoping should work fine, also within `css`. There should be no need to use the `THEME_ID` variable

### Context 🔦

We try to use MUI with theme scoping with styled-components v6.

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Used Browser: Chrome

  System:
    OS: macOS 12.6.1
  Binaries:
    Node: 16.20.1 - /usr/local/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 8.19.4 - /usr/local/bin/npm
  Browsers:
    Chrome: 119.0.6045.199
    Edge: Not Found
    Safari: 15.6.1
  npmPackages:
    @mui/base:  5.0.0-beta.25
    @mui/core-downloads-tracker:  5.14.19
    @mui/material: 5.14.19 => 5.14.19
    @mui/private-theming:  5.14.19
    @mui/styled-engine:  5.14.19
    @mui/styled-engine-sc: 6.0.0-alpha.7 => 6.0.0-alpha.7
    @mui/system:  5.14.19
    @mui/types:  7.2.10
    @mui/utils:  5.14.19
    @types/react: 17.0.70 => 17.0.70
    react: 17.0.2 => 17.0.2
    react-dom: 17.0.2 => 17.0.2
    styled-components: 6.1.0 => 6.1.0
    typescript: 4.8.4 => 4.8.4
```
</details>

### Support Key
#80425
Repository: material-ui
Issue: [material-ui][Drawer] Non-temporary `Drawer` does not support `component` prop
Labels: waiting for 👍,component: drawer,package: material-ui,enhancement

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

We would like to use the `nav`-html-element for rendering the `Drawer`. This would be possible easily, if the `Drawer` would provide a `component`-prop, as most other MUI components do.

### Examples 🌈

```ts
<Drawer variant="permanent" component="nav" />
```

### Motivation 🔦

Proper semantics in the html dom tree.

### Support Key
#80425
Repository: PowerToys
Issue: Have PT Run search engine support all languages installed when searching in Run for typing
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

For all people having multiple keyboard layouts there is problem when user is typing something in one language meaning to use different language. I suggest adding auto-transliteration (hope that what its called). All browsers do that and this is very convienent.

What i mean by that:
Sometimes i need to launch Word using Run. I start typing "word" but because layut is wrong in search field will appear цщкв, and i wont get any results:
![image](https://github.com/microsoft/PowerToys/assets/119590853/1dabaa1c-4cf5-44b3-94d6-aeba4724793b)

Example in firefox:
![image](https://github.com/microsoft/PowerToys/assets/119590853/370ca70a-c09e-410e-a63d-874a93cf4ed9)
In google:
![image](https://github.com/microsoft/PowerToys/assets/119590853/4c9c5cc1-554f-4a22-838c-1d5fc045ea99)


### Scenario when this would be used?

This will make using run faster as user will not have to worry what layout is currently on. And will be usefull for any non-english countries which there are planty of.

### Supporting information

_No response_
Repository: neovim
Issue: nvim_err_writeln behavior with tab characters (^I)
Labels: bug,api,messages

### Problem

nvim_err_writeln cannot print tab characters literally -- but instead show as a keycode (`^I`).

### Steps to reproduce

```
:lua vim.g.err = debug.traceback()   -- a multiline string that contains '^I' (tab)
:lua vim.api.nvim_err_writeln(vim.g.err)
```

Produces:
```
[string ":lua"]:1: stack traceback:
^I[string ":lua"]:1: in main chunk
```

Expected:
```
[string ":lua"]:1: stack traceback:
        [string ":lua"]:1: in main chunk
```


### Expected behavior

Tab characters should be printed as whitespaces as `:echoerr` does, not `^I`, because `nvim_err_writeln` APIs are often used to print "error" messages (including traceback) like `:echoerr`.


### Additional Context

Note that `:echon g:err` prints the tab character correctly, `:echom` cannot.

`:echon`, `:echoerr` (#25380)
```
[string ":lua"]:1: stack traceback:
        [string ":lua"]:1: in main chunk
```

`:echom` (see #25350)

```
stack traceback:^@^I[string ":lua"]:1: in main chunk
```

Three different behaviors, feels confusing.

### Neovim version (nvim -v)

0.9.4, 0.10-nightly

### Vim (not Nvim) behaves the same?

n/a

### Operating system/version

macOS 13

### Terminal name/version

iTerm2

### $TERM environment variable

xterm-256color

### Installation

build from repo
Repository: neovim
Issue: visual area matcher + newline matcher causes wrong substitution
Labels: bug-vim,marks,needs:vim-patch

### Problem

`\%V` and `\_.` together causes wrong matching

### Steps to reproduce

`nvim --clean`, type

```
aaaaa
bbbbb
ccccc
ddddd
eeeee
```

cursor on the first `a`, press `vj`, now `aaaaa\nb` is selected.

Now `:'<,'>s/\%V\_.*\%V/&?/`

the result is
```
aaaaa
?bbbbb
?ccccc
ddddd
eeeee
```

### Expected behavior

```
aaaaa
?bbbbb
ccccc
ddddd
eeeee
```

### Neovim version (nvim -v)

v0.10.0-dev-1793+g808fbe67a

### Vim (not Nvim) behaves the same?

yes, VIM - Vi IMproved 9.0 (2022 Jun 28, compiled Dec 02 2023 14:23:11)

### Operating system/version

irrelevant

### Terminal name/version

irrelevant

### $TERM environment variable

irrelevant

### Installation

github release
Repository: PowerToys
Issue: Problem with the Euro character
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response,Product-Mouse Without Borders

### Microsoft PowerToys version

0.76.0

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

General

### Steps to reproduce

Hello,

I update the PowerToys to the lastest version (from 0.75.1 to 0.76.0). Since the installation, it's impossible to have the Euro character (the key combinaison Alt Gr+e) doesn't work anymore.

When I stop the Powertoys, I can use the key combinaison. I didn't check all other keys combinaisons.

### ✔️ Expected Behavior

The keys combinaison should work

### ❌ Actual Behavior

Impossible to use the key combinaison

### Other Software

_No response_
Repository: next.js
Issue: Building on local perfectly fine. but vercel doesn't build next.js app without showing any errors.
Labels: bug

### Link to the code that reproduces this issue

https://github.com/mthakur5/harothTEMP

### To Reproduce

1. push project in github or publish from vercel CLI.
2. start building (Small Video while building below)
3. shown error. (Shared picture)

https://github.com/vercel/next.js/assets/138131563/414093e6-0f12-4daf-8415-ebb5618a7a85


<img width="1512" alt="Screenshot 2023-12-08 at 3 04 35 PM" src="https://github.com/vercel/next.js/assets/138131563/af31c215-ebaf-4b5f-a279-bb0ebd7c0ec0">



### Current vs. Expected behavior

After 20-27 min. project should build successfully. 

### 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: arm64
  Version: Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000
Binaries:
  Node: 18.18.0
  npm: 9.8.1
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.0.5-canary.1
  eslint-config-next: 14.0.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.2.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Additional context

i have tested with other hosting services like netify & aws amplify. working fine along with locally.
Repository: material-ui
Issue: [material-ui][Radio] Large size shows warning in console
Labels: component: button,enhancement

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Steps to reproduce 🕹

Link to live example: https://stackblitz.com/edit/react-hbyt9f-iryn4i?file=Demo.tsx

I've created new size for Radio button , the large size , but I got this warning in chrome developer console. It seems it's because of [this line of code ](https://github.com/mui/material-ui/blob/ae8678a6d29c1308ec31fd5518289a79582177fc/packages/mui-material/src/Radio/RadioButtonIcon.js#L69) 

Here is the warning : 

```
react.development.js:209 Warning: Failed prop type: Invalid prop `fontSize` of value `large` supplied to `RadioButtonIcon`, expected one of ["small","medium"].
    at RadioButtonIcon (http://localhost:5173/node_modules/.vite/deps/chunk-HMV62V6O.js?v=72451cad:130:5)
    at Radio2 (http://localhost:5173/node_modules/.vite/deps/chunk-HMV62V6O.js?v=72451cad:240:17)
    at label
```

I've created a Stackblitz live demo so you can check it.

### Current behavior 😯

It show warning in console for <Radio size="large" />

### Expected behavior 🤔

It should accept custom size without showing warning.

### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: next.js
Issue: error.js should catch the error, the page shouldn't return a 500 error
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/wandering-sound-rwq9jt

### To Reproduce

In a structure similar to the following:
```
- app
   - lorem
      - page.tsx
      - error.tsx
   - page.tsx
   - layout.tsx
```
I am intentionally throwing an error in `lorem/page.tsx` if a certain condition isn't met. When I visit the page in a browser, the error.tsx content is displayed, but the page is returning a 500 error.

### Current vs. Expected behavior

Currently the whole page returns a 500 error when an error is thrown in the application. I would expect that using error boundaries though the `error.tsx` files, the application would consider the error 'caught' and wouldn't return a 500 error. In this instance, I am expecting and handling the error (by using a `error.tsx` file).

### 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: arm64
  Version: Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:24 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6000
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.0.3
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router

### Additional context

_No response_