sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: restarting a kubelet should never affect the running workload
Labels: kind/bug,sig/node,priority/important-longterm,triage/accepted

### What happened?

1.Node label changed.
Node label changed is because the operation and maintenance engineer organized the node label, such as hpc=true, and removed this label. When a pod is compatible with this label, restarting the node kubelet will cause the pod to be rebuilt. This actually shouldn’t be the case. It will affect the normal operation of the business.
2.https://github.com/kubernetes/kubernetes/issues/123971
3.https://github.com/kubernetes/kubernetes/issues/123816
After the above three scenarios occur, as long as the kubelet is restarted, the pod will be evicted. Obviously, this is not as expected. It is also an undesirable result for online business.

### What did you expect to happen?

Restarting a kubelet should not cause any disruption to the running workload (which likely will mean skip admission of running pods, but let's not run ahead of ourselves) and backlink to this issue is probably the best way forward still.

### How can we reproduce it (as minimally and precisely as possible)?

Before restarting the kubelet, fully check the scenarios mentioned above.

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.17", GitCommit:"a7736eaf34d823d7652415337ac0ad06db9167fc", GitTreeState:"clean", BuildDate:"2022-12-08T11:47:36Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.17", GitCommit:"a7736eaf34d823d7652415337ac0ad06db9167fc", GitTreeState:"clean", BuildDate:"2022-12-08T11:42:04Z", GoVersion:"go1.16.15", Compiler:"gc", Platform:"linux/amd64"}
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: node
Issue: shellJS.exec() or child_process.exec() freezes after running nodeJS instance for long hours
Labels: wrong repo

### Version

v20.11.1

### Platform

Darwin BAN-C02YD6WFJG5J 23.3.0 Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58 PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64 x86_64

### Subsystem

shellJS.exec() or child_process.exec() or child_process.spawn()

### What steps will reproduce the bug?

I'm invoking shell commands using shelljs.exec() and child_process.exec() from macOS menulet app (menubar app). Menubar runs indefinitely till user quit the application.
Recently we found an issue related with exec() function (shellJS and child_process). This callback function is not getting executed or return if the machine/application is kept idle for long hours (8-10).
There is no error or exception coming in the logs. In the below code snippet, callback function ((error, stdout, stderr) => {}) never executes or returns and stuck over there.

I can replicate the issue on demand also. There is no code change from our side. This is 3-4 year old code and this was working fine till NodeJS version < v20. What should be the issue?  Anyway to run trace and locate the error?

const { exec } = require("child_process");

console.log("Before executing EXEC [L]");
exec("ls -la", (error, stdout, stderr) => {
if (error) {
console.log(`error: ${error.message}`);
return;
}
if (stderr) {
console.log(`stderr: ${stderr}`);
return;
}
console.log(`stdout: ${stdout}`);

  console.log("****Finished execution EXEC()");
});

What should be the issue? How do i troubleshoot this issue to get more detailed logs? 

The following are the environment details:
NodeJS : v20.11.1 macOs version : sonoma 14.3 ShellJS version : 0.8.5

Is there anyway to get the trace of issue?

**NOTE:-** The issue happens only if you run NodeJS instance for long hours (8-10) and try to execute a shell command from ShellJS or child_process packages. ShellJS team confirmed this as an issue with NodeJS. In normal scenario it works fine.









### How often does it reproduce? Is there a required condition?

After running NodeJS instance (idle) for long hours - 6-8 hours

### What is the expected behavior? Why is that the expected behavior?

The issue happens only if you run NodeJS instance for long hours (8-10) and try to execute a shell command from ShellJS or child_process packages. In our case NodeJS is running as a backend service on macOS desktop and web page (browser) sends requests  to the backend to execute shell commands. This fails if you keep the instance for long hours.

ShellJS.exec() or child_process.exec() or child_process.spawn() freezes and never returns.

### What do you see instead?

ShellJS.exec() or child_process.exec() or child_process.spawn() freezes and never returns if you keep NodeJS backend service for long hours.

### Additional information

There is no code change in our side. The same code was working earlier. we noticed his in recent versions of NodeJS - v20 and above.
Repository: angular
Issue: No clarification about definition of content initialization
Labels: help wanted,P3,area: docs

### Describe the problem that you experienced

Docs should define the term "content fully initialized".
to understand what "content fully initialized" term mean, I did some observation in my personal projects.

My understanding is, When we say component is initialized (not view initialized) , it means, for all content children

- constructor is invoked. if coded
- ngOnChanges is invoked. if coded
- ngOnInit is invoked. if coded
- ngDoCheck is invoked. if coded.

That all reduces to : Component is initialized mean angular has called all the hooks required before first change detection cycle and change detection is not yet triggered. 

Is my understanding correct?

I am finding for what is the exact contract of ngAfterContentInit life cycle hook? 

### Enter the URL of the topic with the problem

https://angular.io/api/core/AfterContentInit

### Describe what you were looking for in the documentation

concise crisp definition of what a component and content initialization means. so, that developer has concise crisp expectation from the ngAfterContentInit hook.

### Describe the actions that led you to experience the problem

I was reading a doc of lifecycle hook.  and I found out that initialization term can be defined well.

### Describe what you want to experience that would fix the problem

concise crisp definition of what a component and content initialization means. so, that developer has concise crisp expectation from the ngAfterContentInit hook.

### Add a screenshot if that helps illustrate the problem

NA

### If this problem caused an exception or error, please paste it here

```true
NA
```


### If the problem is browser-specific, please specify the device, OS, browser, and version

```true
NA
```


### Provide any additional information here in as much as detail as you can

```true
NA
```
Repository: godot
Issue: Editor can't handle complex Animation State Machine Advanced Expressions
Labels: enhancement,topic:editor,usability,topic:animation

### Tested versions

Reproducible in v4.2.stable.official [46dc27791]

### System information

Windows 10 - Godot v4.2.stable.official [46dc27791]

### Issue description

If you use a boolean valued function in the Advanced Expression of an Animation State Machine transition, it works when the project is run, but it seems to halt in the editor.

It would be very useful for this to work, especially because I can't find an easier way to implement conditions that are consumed by transitions.

### Steps to reproduce

- Create an animation state machine with at least one transition
- Create a script for the Advanced Expression Base Node
- Create a function in the advanced expressions script that returns a boolean
- Call that function as the advanced expression in one of the transitions

### Minimal reproduction project (MRP)

[AnimationStateMachineAdvancedExpressionBug.zip](https://github.com/godotengine/godot/files/14646674/AnimationStateMachineAdvancedExpressionBug.zip)
Repository: flutter
Issue: Infinite Loops and Hangs on CanvasKit Web 
Labels: c: crash,engine,platform-web,e: web_canvaskit,assigned for triage,P2,e: wasm,e: web_skwasm,team-web,triaged-web

### Steps to reproduce

Occasionally when running into out of memory problems you will get stuck in an infinite loop in the WASM code. 

The problem is that CanvasKit is being compiled with aborting malloc enabled. However, CanvasKit uses Mutexes like this:

https://github.com/google/skia/blob/main/modules/skparagraph/src/ParagraphCache.cpp

This mutex will lock until its destructor is called. The problem is that if abort() is called, stack unwinding won't happen and the mutex won't call its destructor and CanvasKit will be left in an invalid state where the next call will lock the process. Normally, abort() would terminate the process, but it doesn't in WASM. 

The solution is to turn off aborting malloc, and turn on wasm exceptions, so that destructors are properly called, exceptions can be caught, and stack unwinding can happen. 

CanvasKit needs to be compiled with -fwasm-exceptions AND -sABORTING_MALLOC=0 in flutter web engine to fix these problems.





### Expected results

Don't go into infinite loops and leave mutexes locked.

### Actual results

App will hang if entering code locked by a mutex in canvaskit and then an exception occurs (OOM is easiest way to simulate).

### Code sample

See: https://github.com/flutter/flutter/issues/145134

It can be hard to repro because of other issues that cause flutter to stop working when unhandled exceptions happen in places that aren't guarded, but in a local build I've fixed a lot of those problems, and this hang be reproduced 100% of the time.

### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[Paste your output here]
```

</details>
Repository: angular
Issue: Router.navigateByUrl navigate to base URL i.e. / when % used as prefix/suffix/in-middle in query param
Labels: area: router,router: URL parsing/generation,P3

### Which @angular/* package(s) are the source of the bug?

router

### Is this a regression?

Yes

### Description

Router.navigateByUrl navigate to base URL i.e. / when % used as prefix/suffix/in-middle in query param even if encode them explicitly 

For example below URL(s) when used to navigate, it will jump to base URL without any error

`http://localhost:4200/#/main/search/144/results?Name=test%`
`http://localhost:4200/#/main/search/144/results?Name=test%test`
`http://localhost:4200/#/main/search/144/results?Name=%test`
`http://localhost:4200/#/main/search/144/results?Name=test%25`
`http://localhost:4200/#/main/search/144/results?Name=%25test`
`http://localhost:4200/#/main/search/144/results?Name=test%25test`

![image](https://github.com/angular/angular/assets/4208015/11a5dbf5-1982-419c-82b0-ab84032100eb)


### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

```true
NA
```


### Please provide the environment you discovered this bug in (run `ng version`)

```true
/ \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | | 
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | | 
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|                |___/
    

Angular CLI: 17.1.2
Node: 18.13.0
Package Manager: npm 10.2.5
OS: win32 x64

Angular: 17.1.2
... animations, cdk, cli, common, compiler, compiler-cli, core
... forms, language-service, platform-browser
... platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------    
@angular-devkit/architect       0.1701.2
@angular-devkit/build-angular   17.1.2
@angular-devkit/core            17.1.2
@angular-devkit/schematics      17.1.2
@schematics/angular             17.1.2
rxjs                            7.8.1
typescript                      5.3.3
zone.js                         0.14.3
```


### Anything else?

_No response_
Repository: vscode
Issue: vscode was error closed while saving the file 
Labels: upstream,freeze-slow-crash-leak,windows,electron,under-discussion

Type: <b>Bug</b>

1. Click on the file header to create a new file but use Ctrl + s to save it
2. This problem will occur when the file name is index/component/view or others, but using default name Untitled-1 will not

VS Code version: Code - Insiders 1.88.0-insider (b356b209a5a41743b45f25d569a7afb733d347a9, 2024-03-18T16:36:07.814Z)
OS version: Windows_NT x64 10.0.19045
Modes:

https://github.com/microsoft/vscode/assets/102725920/5cf8799c-d25b-49ea-8d64-5c7068054aa6

<details>

<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 x 2808)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|15.87GB (7.03GB free)|
|Process Argv|--crash-reporter-id 5db62d60-a6db-471f-9a20-2cd2cbe2e849|
|Screen Reader|no|
|VM|0%|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
vsaa593cf:30376535
py29gd2263:30784851
vscaat:30438846
c4g48928:30535728
962ge761:30841072
pythongtdpath:30726887
welcomedialog:30812478
pythonidxpt:30768918
pythonnoceb:30776497
asynctok:30898717
dsvsc013:30777762
dsvsc014:30777825
dsvsc015:30821418
pythontestfixt:30866404
pythonregdiag2:30926734
pyreplss1:30879911
pythonmypyd1:30859725
pythoncet0:30859736
2e7ec940:30992800
pythontbext0:30879054
accentitlementst:30870582
dsvsc016:30879898
dsvsc017:30880771
dsvsc018:30880772
d6fi2104:30968146
pydisww2:30991134
cppperfnew:30980852
d34g3935:30961436
fegfb526:30952798
bg6jg535:30979844
ccp2r6:30958154
pythonait:30973460
gee8j676:30988845

```

</details>

<!-- generated by issue reporter -->
Repository: node
Issue: Remove `v8_initializers_slow` GYP target
Labels: build,blocked

Added in https://github.com/nodejs/node/pull/52083

We should be able to do it once GCC >=13 is expected for the build.
Repository: next.js
Issue: Fetch is throwing error when headers are attached and application is deployed on vercel
Labels: bug,Pages Router

### Link to the code that reproduces this issue

https://github.com/shorthander/next-fetch-issue

### To Reproduce

1. checkout repo
2. yarn install
3. yarn dev
4. check http://localhost:3000 -> everything fine
5. check deployment https://next-fetch-issue.vercel.app/ -> fetch not working

### Current vs. Expected behavior

I expect the fetch function to work locally as well as in deployed state. 

On my local machine everything works fine. 

The version deployed on vercel is throwing an error while attaching headers to the fetch like this:
```
const res = await fetch(finalUrl, {headers: headers()});
```
Error: 
> Headers cannot be modified. Read more: https://nextjs.org/docs/app/api-reference/functions/headers

Workaround from @icyJoseph (thanks again!)
```
const res = await fetch(finalUrl, {headers: new Headers(headers())});
```


### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 ZEN SMP PREEMPT_DYNAMIC Sun, 03 Mar 2024 00:30:23 +0000
Binaries:
  Node: 21.6.2
  npm: 10.5.0
  Yarn: 1.22.22
  pnpm: 8.15.4
Relevant Packages:
  next: 14.1.3
  eslint-config-next: 14.1.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.2
Next.js Config:
  output: N/A
```


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

Data fetching (gS(S)P, getInitialProps)

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

Vercel (Deployed)

### Additional context

Initial ticket where the workaround was found:
https://github.com/vercel/next.js/discussions/63236
Repository: vscode
Issue: Confusion with copy/paste key bindings with file explorer 
Labels: bug,file-explorer,web

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.87.2
- OS Version: N/A - vscode.dev

Steps to Reproduce:

1. Open vscode.dev (I tested with 1.87.2)
2. Open some text editor
3. Ctrl + c from file explorer, Ctrl +v to the text editor will paste the file path as expected.
4. Go to external editor and copy some text from there, and do Copy + v to see it is pasted in the notepad.
5. Go back to vscode text editor and do: 
- context menu (right click)-> paste will copy from windows as expected
- Ctrl + v will copy from from previous clipboard

See the following video:
https://github.com/microsoft/vscode/assets/9718939/92984d44-d036-4923-9b45-b1eee8c4071e

Also this scenario is a bit problematic:
1. ctrl + c from file explorer on some file 
2. cannot paste to external editor
Repository: godot
Issue: The issue of setting high-definition images in godot controls on mobile devices
Labels: discussion,topic:gui

### Tested versions

4.2

### System information

macos 14.2.1 (23C71)

### Issue description

In the iOS project, after using the colorPicker.add_theme_icon_override("picker_cursor",grabber_icon_texture) method to replace high-definition @ 3x images, the Godot control was unable to shrink the image, resulting in the control becoming larger.

All controls have this issue, such as HSlider(grabber), LineEdit(clear), ColorPicket(picker_cursor), etc

![image](https://github.com/godotengine/godot/assets/134466716/f3fa8d86-09d2-4978-a9e1-ffde61e4bc8c)


### Steps to reproduce

null

### Minimal reproduction project (MRP)

null
Repository: storybook
Issue: Onboarding story type error
Labels: bug,documentation,sev:S2,addon: onboarding

### Describe the bug

![image](https://github.com/storybookjs/storybook/assets/488689/2b35c9a6-9676-498b-81a3-25de58b739b6)

We should fix the onboarding syntax which looks wrong. We should also default to TS4.9 and above now in both onboarding and docs.

### To Reproduce

-

### System

```bash
-
```


### Additional context

_No response_
Repository: PowerToys
Issue: Quick Accent layover stuck
Labels: Issue-Bug,Needs-Triage,Product-Quick Accent

### Microsoft PowerToys version

0.79.0

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

Quick Accent

### Steps to reproduce

I haven't been able to reproduce this bug or catch any screenshots yet. But multiple times when i am gaming or generally have a lot of keyboard inputs the Quick accent overlay is displayed on the top of the screen and i cannot close it in any way.

### ✔️ Expected Behavior

The accent overlay disappearing after use

### ❌ Actual Behavior

The accent overlay is stuck on the top of the screen and the only way to close it is by shutting down the application.

### Other Software

_No response_
Repository: pytorch
Issue: [FX Graph Mode Quantization] Prepare model fails with Linear-BN when `affine=False`
Labels: oncall: quantization

### 🐛 Describe the bug

```python
import torch
from torch import nn
from torch.ao.quantization import quantize_fx, QConfigMapping

model = nn.Sequential(
    nn.Linear(10, 20),
    nn.BatchNorm1d(20, affine=False),
)
model.eval()

qconfig_mapping = QConfigMapping()
model_prepared = quantize_fx.prepare_fx(model, qconfig_mapping, (torch.randn(1, 10),))
```

```
--> [133] bn_scale = bn_w * torch.rsqrt(bn_rv + bn_eps)
    [135] fused_w = linear_w * bn_scale.unsqueeze(-1)
    [136] fused_b = (linear_b - bn_rm) * bn_scale + bn_b

TypeError: unsupported operand type(s) for *: 'NoneType' and 'Tensor'
```

Basically `fuse_linear_bn_weights()` needs to handle the case when batch norm weight and bias is None. Conv-BN version already handles that.

### Versions

Shouldn't matter. I used latest PyTorch (2.2.1)

cc @jerryzh168 @jianyuh @raghuramank100 @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel
Repository: PowerToys
Issue: Always on top deadlock
Labels: Issue-Bug,Product-Always On Top,Needs-Triage

### Microsoft PowerToys version

0.078.0

### Installation method

WinGet

### Running as admin

No

### Area(s) with issue?

Always on Top

### Steps to reproduce

1. Open the Onenote with win + n
2. wirte something
3. aktivate "always on top" win + str + t
4. mark the text
5. right click -> table -> insert table

### ✔️ Expected Behavior

the insert table dialog is on top of the onenote window

### ❌ Actual Behavior

The insert table dialog is behind the OneNote window and isn't acessable. I cant move or close OneNote because it locks the OneNote window.

### Other Software

_No response_