sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: Process does not exit after https request with keepAlive enabled (now default in Node 19)
Labels: confirmed-bug,http,https

### Version

v19.8.1

### Platform

Linux Jake-Framework 6.2.7-arch1-1 #1 SMP PREEMPT_DYNAMIC Sat, 18 Mar 2023 01:06:36 +0000 x86_64 GNU/Linux

### Subsystem

https

### What steps will reproduce the bug?

Run a script containing:

```js
const https = require("https");
const url = "https://github.com/dprint/dprint/releases/download/0.35.3/dprint-x86_64-unknown-linux-gnu.zip";
https.get(url, { method: "HEAD" }, console.log);
```

This will hang.

### How often does it reproduce? Is there a required condition?

100% of the time; downgrade to Node 18 and it no longer hangs.

### What is the expected behavior? Why is that the expected behavior?

No hang. Run this:

```js
const https = require("https");
const url = "https://github.com/dprint/dprint/releases/download/0.35.3/dprint-x86_64-unknown-linux-gnu.zip";
https.get(url, { method: "HEAD", agent: new https.Agent({ keepAlive: false }) }, console.log);
```

And it will succeed.

### What do you see instead?

Hang; the request succeeds and the response is given, but the process never exits.

### Additional information

This is a change I saw in the Node 19 release blog post; keep-alive is enabled by default now, but, it seems to cause a hang.
Repository: pytorch
Issue: After the release of pytorch 2.0.0, the compilation of ACLs is problematic.
Labels: module: build,triaged

I found that when I installed torch2.0.0 using pip, I carried a torch.libs folder with three ACL so files and two libgomp files. I wanted to know the detailed compilation options and ACL versions of the three ACL so files. What are the sources of the other two libgomp files?
libarm_compute-860e7a78.so
libarm_compute_graph-ab857ce5.so  
libgomp-d22c30c5.so.1.0.0
libarm_compute_core-0793f69d.so  
libgomp-adceddde.so.1.0.0

As for why I want to know this, I want to compile pytorch in the source code to link my self-installed ACLs and find that it is much slower than the torch installed using pip, under the same version of torch.

My Compilation Environment:
GCC 10.2
ACL 23.0.1
torch 2.0.0

cc @malfet @seemethere
Repository: react
Issue: [DevTools Bug] Cannot add child "1161" to parent "942" because parent node was not found in the Store.
Labels: Type: Bug,Status: Unconfirmed,Resolution: Needs More Information,Component: Developer Tools

### Website or app

chrome on local host

### Repro steps

it happen with every component that i mount 
<img width="1470" alt="Screenshot 2023-03-23 at 1 04 00 PM" src="https://user-images.githubusercontent.com/110327079/227134701-d665feca-3326-401e-b957-007c41318be6.png">


### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-extensions

### DevTools version (automated)

4.27.2-1a88fbb67

### Error message (automated)

Cannot add child "1161" to parent "942" because parent node was not found in the Store.

### Error call stack (automated)

```text
at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:27939:43
    at bridge_Bridge.emit (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:25892:22)
    at chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:26061:14
    at listener (chrome-extension://fmkadmapgofadopljbjfkapdkoienihi/build/main.js:56323:39)
```


### Error component stack (automated)

_No response_

### GitHub query string (automated)

```text
https://api.github.com/search/issues?q=Cannot add child  to parent  because parent node was not found in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
```
Repository: go
Issue: testing: Testable examples collapse `Output` newlines, making them impossible to pass
Labels: help wanted,NeedsFix

<!--
Please answer these questions before submitting your issue. Thanks!
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.20.2 darwin/amd64
</pre>

> ⚠️ This also appears to affect go1.19, though I believe it worked at some point in the past

### Does this issue reproduce with the latest release?

Yes

### What operating system and processor architecture are you using (`go env`)?

❌ Not relevant, this happens in multiple environments including Go Playground with Go 1.19 and Go 1.20

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on go.dev/play is best.
-->

1. Provide a testable example of _a function which returns output containing successive newlines_
2. Example cannot pass tests, since the `Output` annotation is modified by the `testing` parser

#### Minimal example

Viewable here: https://go.dev/play/p/LFktKVr75lz

✅ The `ExampleFoo` function returns data containing successive newlines:
```md
Single newline:

Double newline:


Final text
```
✅ The `ExampleFoo` contains an embedded `Output:` annotation with the same expected output:
```go
	//Output:
	//Single newline:
	//
	//Double newline:
	//
	//
	//Final text
```
✅ The `Output` and `stdout` are compared, with leading and trailing whitespace removed
❌ Multiple newlines are collapsed into single newlines, making the test fail - only solution is to modify the function under test (which is _not_ an option)

### What did you expect to see?

`Output:` should be parsed as-is, not modified (beyond trimming leading and trailing whitespace)

### What did you see instead?

The multiple empty lines are collapsed into a single empty line


### Additional context

Did a little hunting to see if I could find a root cause, no success yet

Currently suspect it's either hidden somewhere within the `testing` package, or is an unintended side effect of how chains of single line comments are parsed by `ast`
Repository: storybook
Issue: [Bug]: Addon-interactions. Interactions panel does not show steps after error has thrown even if I handle this error.
Labels: bug,good first issue,help wanted,addon: interactions,sev:S3

### Describe the bug

Intstumented functions always bubble up errors to interactions panel. But in play function I can handle error. After that code will continue to run and all interations will be done. But in my panel I won't see anything after error, which was handled.

![image](https://user-images.githubusercontent.com/8949234/227145533-393a9a41-75bd-40b0-8cfb-d85882556bf9.png)


### To Reproduce

```
MyStory.play = async () => {
  await userEvent.type(getTokenInput(), "newComment");
  try {
    await screen.findByTestId("IdWhichDoesntExist");
  } catch (e) {}
  await userEvent.type(getTokenInput(), ",");
};
```

This function should type two times in input. But in panel you'll see only one operation and one error.

### System

```shell
System:
    OS: Windows 10 10.0.19045
    CPU: (8) x64 AMD Ryzen 7 4700U with Radeon Graphics
  Binaries:
    Node: 16.13.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.17 - C:\Program Files\nodejs\yarn.CMD
    npm: 9.6.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (110.0.1587.57)   
  npmPackages:
    @storybook/addon-actions: ^6.5 => 6.5.16
    @storybook/addon-interactions: ^6.5.16 => 6.5.16
    @storybook/addons: ^6.5 => 6.5.16
    @storybook/builder-webpack5: ^6.5 => 6.5.16
    @storybook/jest: ^0.0.10 => 0.0.10
    @storybook/manager-webpack5: ^6.5 => 6.5.16
    @storybook/react: ^6.5 => 6.5.16
    @storybook/testing-library: ^0.0.13 => 0.0.13
    @storybook/ui: ^6.5 => 6.5.16
```


### Additional context

_No response_
Repository: pytorch
Issue: suspicious memory leak when increase DataLoader's prefetch_factor and enable pin_memory
Labels: module: dataloader,module: memory usage,triaged

### 🐛 Describe the bug

In my 8*V100 GPU training project I use torch's DataLoader and set partial arguments below.

`train_loader = torch.utils.data.DataLoader(train_dataset,
                    batch_size=8,
                    sampler=train_sampler,
                    num_workers=16,
                    pin_memory=True,
                    prefetch_factor=16,
                    persistent_workers=True)`

But while training I found the host memory cost too much(nearly 90% of total 768GB RAM), from our node's monitor.
![image](https://user-images.githubusercontent.com/8710725/227138898-bf22fe17-c100-491f-980e-484ac2eb0181.png)

When I set prefetch_factor back to 2 (default value), the memory problem disappeared.

Additional, I used NVIDIA Nsight Systems tool to profile my training job and found many cudaHostAlloc API calls even in 2000th+ steps, without any corresponding cudaFree calls, which also blocked execution of GPU Kernels.
![image](https://user-images.githubusercontent.com/8710725/227154210-afe12e86-85c0-4186-9e42-ec28deec4d01.png)

In further analysis, I found these cudaHostAlloc were called from pin_memory_loop thread in DataLoader.
So I doubt there may be some pinned memory leak bugs? Need help from other developpers .


### Versions

torch.__version__ 1.13.1+cu117
torch.version.cuda : 11.7
torch.backends.cudnn.version() : 8500
python version : 3.7.13 (miniconda)
cuda driver version : 470.57.02
GPU : Tesla V100 * 8

cc @SsnL @VitalyFedyunin @ejguan @NivekT @dzhulgakov
Repository: material-ui
Issue: [Autocomplete] Checkbox label inside paper component is causing blur when clicked
Labels: component: autocomplete,status: expected behavior

### 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/s/tender-tree-xzql42?file=/demo.js


### Current behavior 😯

I have two elements inside the paper component aside from the options, one is a button and another one is a checkbox. To prevent the autocomplete from triggering blur when the user interacts with these elements, I've called event.preventDefault() on event onMouseDown. Each element is clickable and would not trigger blur but unfortunately, clicking the label of the checkbox causes it to blur. 

### Expected behavior 🤔

 Clicking the checkbox label would just toggle the checkbox checked state and the blur method should not be called. 

### Context 🔦

What I'm trying to accomplish is I have two sets of options and when I tick the checkbox it would display another set of options. Clicking on whether the checkbox or label should not trigger the blur.

### 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: Script strategy
Labels: bug

### Verify canary release

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

### Provide environment information

```bash
"When 'strategy' is not declared in the script, it cannot be executed in a custom document but can be executed in a custom app. The default value of 'strategy' is 'afterInteractive'. The default value is inconsistent with the expected behavior."
```


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

_No response_

### Link to the code that reproduces this issue

https://stackblitz.com/edit/vercel-next-js-bxrajp?file=_document.js

### To Reproduce

1. Create custom document file. 
2. Import Script from 'next/scrip'; import {Head, Html, Main, NextScript} from 'next/document'
3. Add Script tag to Head .
4. Run the app.
`
import Document, { Html, Head, Main, NextScript } from 'next/document'
import Script from 'next/script'

class MyDocument extends Document {
  render() {
    return (
    <Html>
      <Head>
        <Script id="script1" dangerouslySetInnerHTML={{__html: `console.log(1)`}} />
        <Script id="script2" strategy="beforeInteractive" dangerouslySetInnerHTML={{__html: `console.log(2)`}} />
        <Script id="script3" strategy="afterInteractive" dangerouslySetInnerHTML={{__html: `console.log(3)`}} />
        <Script id="script4" strategy="lazyOnload" dangerouslySetInnerHTML={{__html: `console.log(4)`}} />
      </Head>
      <body>
        <Main />
        <NextScript />
      </body>
    </Html>
  )}
}

export default MyDocument`  

### Describe the Bug

"The 'strategy' has a default value regardless of whether it is declared in the script or not, and can be inserted normally in a custom document."

### Expected Behavior

"The default value should be effective even without explicit declaration."

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

_No response_

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

_No response_
Repository: godot
Issue: [4.0.1]set_anchors_and_offsets_preset behaves incorrectly after multiple set
Labels: bug,topic:gui

### Godot version

4.0.1.stable

### System information

Linux Mint 21.1 Cinnamon

### Issue description

`set_anchors_and_offsets_preset(preset, 3)` behaves incorrectly.

If you set some preset of a node and then change it.

the second time the layout is wrong.

preset from PRESET_TOP_WIDE to PRESET_HCENTER_WIDE will act wrong

but 
````
        node.set_anchors_preset(preset)

	node.set_offsets_preset(preset, 3)
````
works correctly





### Steps to reproduce

run this scene

### Minimal reproduction project

[godot_bug_01.zip](https://github.com/godotengine/godot/files/11051225/godot_bug_01.zip)
Repository: vscode
Issue: Not clear how to share attribute definitions between "attach" and "launch" configurations
Labels: feature-request,debug

<!-- ⚠️⚠️ 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. -->

<!-- 🪓 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. -->

When writing an extension that needs custom launch configuration properties, the properties can be specified in package.json using the [debuggers contribution point](https://code.visualstudio.com/api/references/contribution-points#contributes.debuggers) and adding the schema of the custom properties under the `configurationAttributes` key.

When the extension needs to specify the same custom property for both the "launch" and "attach" configurations, there seems to be no way to share the property definition between these two cases, so that you have to copy and paste the definition into both configuration sections.

This was previously reported as issue #915, which was marked "closed as completed", but the [documentation for the debuggers contribution point](https://code.visualstudio.com/api/references/contribution-points#contributes.debuggers) does not explain how to do it. I suggest that the documentation be updated to explain how to share property definitions between "launch" and "attach" configurations, or if this is not possible, to add a note explaining that copy-pasting is necessary.
Repository: deno
Issue: Deno should understand `/// <reference types="node" />` in npm packages
Labels: feat,node compat

When Deno encounters `/// <reference types="node" />` in an npm package, then it should automatically include `@types/node`.
Repository: deno
Issue: Improve "Cannot find name 'Buffer'."-like diagnostics in npm packages to suggest including the `@types/node`
Labels: feat,node compat,types

When a user gets a diagnostic like the following:

```
> deno check --all main.ts
Check file:///V:/scratch/main.ts
error: TS2580 [ERROR]: Cannot find name 'Buffer'.
        content: string | Buffer,
                          ~~~~~~
    at file:///C:/Users/david/AppData/Local/deno/npm/registry.npmjs.org/@types/imapflow/1.0.12/index.d.ts:29:27
```

...where the source is in an npm package, we should enhance the diagnostic to tell them to add `/// <reference types="npm:@types/node" />` to their code.

(In the case above, it should automatically include them though. See #18385)
Repository: PowerToys
Issue: Adjust radius based on a % vs DPI 
Labels: Idea-Enhancement,Product-Mouse Utilities

### Description of the new feature / enhancement

radius expressed in  :  percentage

now the size of the highlighter depends on the pixel density of the monitor, with two monitors of the same size but of different density the size of the highlighter will be different.

you can use a unit of measure that does not depend directly on the density

### Scenario when this would be used?

multiple monitors with different pixel density but same size:
example 2 monitor 24" ,  one FHD the other UHD, 

highlighter size will be bigger in 24" monitor

### Supporting information

_No response_
Repository: rust
Issue: diagnostics improvements for invalid target_feature error
Labels: A-diagnostics,T-compiler,A-target-feature

When a target feature is found that doesn't exist on the current target but does exist on another target, it should be explicitly pointed out in the error message. Copying the example from [this comment](https://github.com/rust-lang/rust/issues/108680#issuecomment-1479473303):

```Rust
#[target_feature(enable = "sse2", enable = "avx", enable = "sse")]
pub unsafe fn foo() {}
```

When you compile it on M1/M2 you get:

```
error: the feature named `sse2` is not valid for this target
  --> $DIR/issue-108680.rs:3:18
   |
LL | #[target_feature(enable = "sse2", enable = "avx", enable = "sse")]
   |                  ^^^^^^^^^^^^^^^ `sse2` is not valid for this target

error: the feature named `avx` is not valid for this target
  --> $DIR/issue-108680.rs:3:35
   |
LL | #[target_feature(enable = "sse2", enable = "avx", enable = "sse")]
   |                                   ^^^^^^^^^^^^^^ `avx` is not valid for this target

error: the feature named `sse` is not valid for this target
  --> $DIR/issue-108680.rs:3:51
   |
LL | #[target_feature(enable = "sse2", enable = "avx", enable = "sse")]
   |                                                   ^^^^^^^^^^^^^^ `sse` is not valid for this target

```

Ideally this would mention that these target features are valid for the `arm64` target architecture/family:

```
error: the feature named `sse2` is not valid for this target
  --> $DIR/issue-108680.rs:3:18
   |
LL | #[target_feature(enable = "sse2", enable = "avx", enable = "sse")]
   |                  ^^^^^^^^^^^^^^^ `sse2` is not valid for this target
   = note: `sse2` is present on the `x86_64` target architecture. Did you mean to compile for that target, or use conditional compilation?
```

The printing also ideally would support features present on multiple target architectures, for example the `aes` feature is present on both arm and x86: 

```Rust
// only-wasm32
#[target_feature(enable = "aes")]
pub unsafe fn foo() {}
```

For `aarch64` vs `arm` it might make sense to always mention them both if the feature is present on both, as the two languages are way different from each other (while x86 is very backwards compatible).

As a second thing, it would be nice if it could provide typo suggestions:

```Rust
#[target_feature(enable = "avc")]
pub unsafe fn foo() {}
```

```
error: the feature named `avc` is not valid for this target
 --> src/main.rs:1:18
  |
1 | #[target_feature(enable = "avc")]
  |                  ^^^^^^^^^^^^^^ `avc` is not valid for this target
  = help: a similar feature `avx` exists for this target
```

But I'm less sure if this is a good idea as target features are often very short and similar to each other. Suggesting the wrong target feature might not be detected as easily.

@rustbot label A-diagnostics A-target-feature
Repository: go
Issue: net: lookup: avoid creating a new goroutine if context is canceled and lookupIPAddr isn't actually resolving
Labels: NeedsInvestigation

Hello,

I've read https://github.com/golang/go/blob/0aa14fca8c639c9ceba264dbf0d82bd53306aeaa/src/net/lookup.go#L333-L347 and https://github.com/golang/go/issues/22724. 

I think It's preferable to avoid creating a new goroutine for waiting on a result whenever possible. If the context is canceled and `lookupIPAddr` isn't actually resolving, there's no need to wait for the result using a new goroutine.

This is how we can achieve this:

1. Add method `ForgetNonFirstChan` to `internal/singleflight.Group`, which signature is

```
// ForgetNonFirstChan tells the singleflight to forget about a channel if it is not
// for the first invocation for a key.
// Returns whether the channel was forgotten or not.
func (g *Group) ForgetNonFirstChan(key string, ch chan Result) bool 
```

2. At `lookupIPAddr`, when context canceled, call `ForgetNonFirstChan` and if it returns true, we don't need to wait for the result, and call `cancelFn` immediately without making a new goroutine.


For example, suppose there is a situation where the first call of `LookupIPAddr` takes a long time, and then calls for name resolution for the same hostname are made `n` times with a timeout of 5 seconds. Previously, even after 5 seconds had passed, `n+1` goroutines were required, but after my modification, only one goroutine is required.


I wrote a draft implementation  on [Gerrit](https://go-review.googlesource.com/c/go/+/478895)

FYI: 
I changed the data structure that holds the channels from a `slice` to a `map`. This was done to improve the search(ForgetNonFirstChan needs searching) complexity from O(N) to O(1).
Repository: PowerToys
Issue: Support removing zero-width characters when copying
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

Support setting the system clipboard to automatically delete zero-width characters

### Scenario when this would be used?

Some sites sneak zero-width characters into the text when users copy content. The hidden text is displayed in the text editors. Support for automatically removing zero-width characters will make copying and pasting easier, especially code snippets.

### Supporting information

Some blog sites such as https://www.csdn.net/ in China would insert zero-width characters about copyright information.