sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: Eviction never happens on pods with long-lived postStart lifecycle phase
Labels: kind/bug,sig/node,priority/important-longterm,triage/accepted

### What happened?

While a pod's postStart lifecycle phase is running, the pod is not evicted even if its usage exceeds limits.


### What did you expect to happen?

As soon as the pod exceeds ephemeral disk usage limits, it should be evicted, regardless of active lifecycle phases

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

The following pod demonstrates the problem:

```
apiVersion: v1
kind: Pod
metadata:
  name: test2
spec:
  containers:
  - name: test
    image: busybox
    command:
      - /bin/sh
    args:
      - -c
      - |-
        _term() {
            echo "Caught SIGTERM signal!"
        }
        trap _term SIGTERM
        while true; do
          dd if=/dev/zero of=/tmp/zero bs=1M count=20 oflag=append conv=notrunc
          sleep 3600
        done
    resources:
      limits:
        cpu: "100m"
        memory: "50Mi"
        ephemeral-storage: "10Mi"
    lifecycle:
      postStart:
        exec:
          command:
            - sleep
            - inf
```

### Anything else we need to know?

This issue was originally reported as part of the Kubernetes HackerOne bug bounty program. The current security posture of the Kubernetes Security Response Committee is to treat issues like this as security hardening bugs, and not as a CVE. Thanks to Shiming Zhang (wzshiming on HackerOne) for reporting this issue.

### Kubernetes version

<details>

```console
Server Version: version.Info{Major:"1", Minor:"29+", GitVersion:"v1.29.0-alpha.0.372+714e77595c8b19-dirty", GitCommit:"714e77595c8b19b693925bda2a96ab80c307d38f", GitTreeState:"dirty", BuildDate:"2023-12-07T17:32:58Z", GoVersion:"go1.20.7", Compiler:"gc", Platform:"linux/amd64"}
```

</details>


### Cloud provider

<details>
Tested on a local-up cluster
</details>


### OS version

<details>
Tested on Fedora 37
</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: vscode
Issue: Widget navigation steals editor focus
Labels: bug,keybindings,papercut :drop_of_blood:

<!-- ⚠️⚠️ 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/No

<!-- 🪓 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. -->

```
2023-12-07 09:49:34.783 [info] [KeybindingService]: \ From 22 keybinding entries, matched widgetNavigation.focusNext, when: inputFocus && navigableContainerFocused || navigableContainerFocused && !listFocus || navigableContainerFocused && listScrollAtBoundary == 'both' || navigableContainerFocused && listScrollAtBoundary == 'bottom', source: built-in.
2023-12-07 09:49:34.784 [info] [KeybindingService]: / Received  keydown event - modifiers: [meta], code: ArrowDown, keyCode: 40, key: ArrowDown
2023-12-07 09:49:34.784 [info] [KeybindingService]: | Converted keydown event - modifiers: [meta], code: ArrowDown, keyCode: 18 ('DownArrow')
2023-12-07 09:49:34.784 [info] [KeybindingService]: | Resolving meta+[ArrowDown]
2023-12-07 09:49:34.784 [info] [KeybindingService]: \ From 22 keybinding entries, matched widgetNavigation.focusNext, when: inputFocus && navigableContainerFocused || navigableContainerFocused && !listFocus || navigableContainerFocused && listScrollAtBoundary == 'both' || navigableContainerFocused && listScrollAtBoundary == 'bottom', source: built-in.
2023-12-07 09:49:34.785 [info] [KeybindingService]: + Invoking command widgetNavigation.focusNext.
```

Not sure how did I end with this state but often I can't `cmd+down`anymore in editor and the shortcut is stolen by widgetNavigation
Repository: flutter
Issue: Selection context menu position incorrect if Overlay is not "fullscreen"
Labels: framework,has reproducible steps,P2,f: selection,team-framework,triaged-framework,found in release: 3.16,found in release: 3.18

Observed on MacOS: The context menu is not positioned correctly as seen in the screenshot below and nothing in the context menu can be selected. I suspect that it incorrectly assumes that the Overlay (added by MaterialApp) is covering the full screen, which is not true in the example given below.

<img width="912" alt="Screenshot 2023-12-07 at 9 54 35 AM" src="https://github.com/flutter/flutter/assets/1227763/0c4ad174-b1ed-4e0f-b553-fbe3bebd56b4">

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(_MyApp());
}

class _MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return const Center(
      child: SizedBox(
        height: 100,
        width: 100,
        child: MaterialApp(
          debugShowCheckedModeBanner: false,
          home: SelectionArea(
            child: Scaffold(
              body: Center(
                child: Text('Hello World'),
              ),
            ),
          ),
        ),
      ),
    );
  }
}

```
Repository: vscode
Issue: Deleted collapsed folders remain visible until explorer refresh
Labels: bug,tree-widget

<!-- ⚠️⚠️ 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.85.0-insider (Universal) and 1.84.2 (Universal).
- OS Version: macOS 14.1.1

Steps to Reproduce:
1. Create a folder named **folder1** and place **folder2** inside it.
2. Optionally, add any files or folders within **folder2**.
3. Collapse the content of **folder2**.
4. Delete **folder2** using the file explorer.

Expected Result:
Upon deletion, **folder2** should immediately disappear from the file explorer interface.

Actual Result:
**folder2** remains visible, persisting until the explorer is manually refreshed.

Additional Information:
This issue consistently occurs when a collapsed folder, with the parent folder containing no other content except the folder being deleted, is removed. This behavior is observed except in cases where the deleted folder is located at the root of the open editor.

Screencast:

https://github.com/microsoft/vscode/assets/116561995/793be63a-ad03-4864-a543-37890f46d712
Repository: vscode
Issue: IPython ?/?? output doesn't render nicely in the text editor
Labels: bug,notebook-output

### Applies To

- [X] Notebooks (.ipynb files)
- [ ] Interactive Window and\/or Cell Scripts (.py files with \#%% markers)

### What happened?

IPython provides `?` and `??` to get a quick access to the help and source code of an object. When the output of this magic command is too long VSCode suggests opening it in a text editor (`Output exceeds the size limit. Open the full output data in a text editor`). However, I believe that IPython expects the output to be displayed in a terminal and as such colorizes it. This doesn't render nicely at all in the text editor.

Execute the following in a Notebook cell:
```python
import string
string??
```

![image](https://user-images.githubusercontent.com/35924738/205607998-68d17b66-72b1-43c6-8715-772d1bec37a1.png)

Follow the suggestion and open the text editor, you'll see:
![image](https://user-images.githubusercontent.com/35924738/205607898-92fb03b3-e2f5-43cc-b21c-ae352eeecbb0.png)

(Originally reported in https://github.com/holoviz/hvplot/issues/984)

### VS Code Version

Version: 1.73.1 (Universal) Commit: 6261075646f055b99068d3688932416f2346dd3b Date: 2022-11-09T02:08:38.961Z Electron: 19.0.17 Chromium: 102.0.5005.167 Node.js: 16.14.2 V8: 10.2.154.15-electron.0 OS: Darwin x64 21.4.0 Sandboxed: No

### Jupyter Extension Version

v2022.9.1303220346

### Jupyter logs

_No response_

### Coding Language and Runtime Version

_No response_

### Language Extension Version (if applicable)

_No response_

### Anaconda Version (if applicable)

_No response_

### Running Jupyter locally or remotely?

None
Repository: pytorch
Issue: torch._fused_sdp_choice for fake and real tensors returns different results
Labels: triaged,module: fakeTensor,module: sdpa

### 🐛 Describe the bug

For some reason `torch._fused_sdp_choice` returns a different backend choice for fake cuda inputs compared to real inputs:
```py
import torch
from torch._subclasses.fake_tensor import FakeTensor, FakeTensorMode

q = torch.ones(1, 2, 12, 8, dtype=torch.float16, device='cuda')
k = torch.ones(1, 2, 14, 8, dtype=torch.float16, device='cuda')
v = torch.ones(1, 2, 14, 8, dtype=torch.float16, device='cuda')
mask = torch.ones(1, 2, 12, 14, dtype=torch.bool, device='cuda')

meta_q = q.to("meta")
meta_k = k.to("meta")
meta_v = v.to("meta")
meta_mask = mask.to("meta")

with FakeTensorMode() as mode:
    fake_q = FakeTensor(mode, meta_q, q.device)
    fake_k = FakeTensor(mode, meta_k, k.device)
    fake_v = FakeTensor(mode, meta_v, v.device)
    fake_mask = FakeTensor(mode, meta_mask, mask.device)

expected_backend = torch._fused_sdp_choice(q, k, v, mask) # 2
actual_backend = torch._fused_sdp_choice(fake_q, fake_k, fake_v, fake_mask) # 0
assert expected_backend == actual_backend # This assertion fails!
```

### Versions

2.2.0a0+git4fa1ff8 (recent main)

cc @jbschlosser @bhosmer @cpuhrsch @erichan1 @drisspg @mikaylagawarecki @eellison
Repository: godot
Issue: AudioStream preview doesn't update after enabling 'Trim' on Import
Labels: bug,needs testing,topic:audio,topic:import

### Tested versions

Reproducible in Godot v4.2.stable.mono.official.46dc27791

### System information

macOS 14.1.2 - Godot v4.2.stable.mono

### Issue description

After importing a .wav file and opening it up to the inspector, a waveform is generated for the AudioStream's preview that doesn't update after reimporting the .wav with the 'Trim' boolean enabled. This leads me to believe the trimming doesn't work, even though it does. The waveform should probably reflect the imported and processed AudioStream at all times?

<img width="1728" alt="Screenshot 2023-12-07 at 18 58 58" src="https://github.com/godotengine/godot/assets/5611323/288e5766-5478-4fb6-a67c-25f6d8aaddd8">


### Steps to reproduce

1. Import a .wav file with some silence at the start.
2. Double click on the .wav file in the FileSystem to open it up in the Inspector. Notice the gap at the start of the waveform.
3. Reimport the .wav file with the 'Trim' boolean enabled.
4. Notice that the gap of the waveform is still there.

### Minimal reproduction project (MRP)

Here's a .wav file with some silence at the start: 
[HahaFart.wav.zip](https://github.com/godotengine/godot/files/13603508/HahaFart.wav.zip)
Repository: vscode
Issue: VSC freezes when uploading a file
Labels: bug,macos,confirmed

<!-- ⚠️⚠️ 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.84.2 (Universal)**
- OS Version: **Darwin x64 23.0.0**

Steps to Reproduce:

1. make a new project
2. click make a new file but don't add anything or close it (don't actual make the file)
3. upload a file in the same folder as the the uncreated file


<img width="184" alt="Screenshot 2023-12-07 at 12 56 55" src="https://github.com/microsoft/vscode/assets/88513373/f4ad1328-d066-44fb-b460-483c52b76b02">
<img width="1136" alt="Screenshot 2023-12-07 at 12 57 07" src="https://github.com/microsoft/vscode/assets/88513373/c4517464-736b-4434-9867-d7929edaaa21">
Repository: terminal
Issue: [Comment] Invalid URL
Labels: Issue-Docs,Product-Meta,Area-CodeHealth

The [link at the line 591 of src/renderer/gdi/state.cpp](https://github.com/microsoft/terminal/blob/20dad624710249f3a4ee77c47a58d4ca367a820b/src/renderer/gdi/state.cpp#L591
) redirect to an error page.

It would be appreciated if it could be updated to the right link.

https://github.com/microsoft/terminal/blob/20dad624710249f3a4ee77c47a58d4ca367a820b/src/renderer/gdi/state.cpp#L588-L593
Repository: kubernetes
Issue: Ephemeral storage limits do not account for data written to /dev/termination-log, pods are not evicted
Labels: kind/bug,sig/node,priority/important-longterm,triage/accepted

### What happened?

A pod with an ephemeral storage limit is never evicted due to excessive data written to `/dev/termination-log`.

### What did you expect to happen?

Data written to `/dev/termination-log` should count against a pod's ephemeral storage limit and result in eviction once too much data is written.

### How can we reproduce it (as minimally and precisely as possible)?

The following pod demonstrates the problem:

```
---
apiVersion: v1
kind: Pod
metadata:
  name: dev-termination-log-test
spec:
  containers:
  - image: k8s.gcr.io/busybox:latest
    name: test
    command: ["/bin/sh"]
    # create 200MiB of data and write it to /dev/termination-log, then sleep forever
    args:
    - -c
    - |-
      yes $(printf 'Hello world!!!!\n%.0s' `seq 1 $((1024/16))`) | dd bs=1024 count=$((200*1024)) > /dev/termination-log
      while sleep 3600; do
        true
      done
    resources:
      limits:
        ephemeral-storage: "100Mi"
  securityContext:
    runAsUser: 0
```

### Anything else we need to know?

This issue was originally reported as part of the Kubernetes HackerOne bug bounty program. The current security posture of the Kubernetes Security Response Committee is to treat issues like this as security hardening bugs, and not as a CVE. Thanks to Chijin Zhou (chijin on HackerOne) for reporting this issue.



### Kubernetes version

<details>

```console
Server Version: version.Info{Major:"1", Minor:"29+", GitVersion:"v1.29.0-alpha.0.372+714e77595c8b19-dirty", GitCommit:"714e77595c8b19b693925bda2a96ab80c307d38f", GitTreeState:"dirty", BuildDate:"2023-12-07T17:32:58Z", GoVersion:"go1.20.7", Compiler:"gc", Platform:"linux/amd64"}
```

</details>


### Cloud provider

<details>
Tested on a local-up cluster

</details>


### OS version

<details>

Tested on Fedora 37

</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: vscode
Issue: High / elevated CPU usage when codespace disconnects
Labels: remote,performance

<!-- ⚠️⚠️ 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/No
N/A

<!-- 🪓 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.84.2
- OS Version: Windows 10 10.0.19045

Steps to Reproduce:

1. Start a codespace in VS Code desktop
2. Navigate to github.com/codespaces and stop the codespace, or just let the codespace stop due to the idle time out

The CPU usage becomes highly elevated. A core is maxed out.

I tried the same codespace on insiders and the issue wasn't nearly as bad but a modest amount of elevated CPU usage did seem present.

Left: VS Code insiders, codespace is connected
Right: VS Code insiders, codespace is disconnected
Bottom: VS Code regular, codespace is disconnected

![codespace-cpu-disconnected](https://github.com/microsoft/vscode/assets/122519877/4816ed8b-44a1-4ae6-9fbf-a10546115625)

High CPU usage seemed to start after about 10 seconds.

My impression is that there's a background task, possibly from one or more extensions or built-in functionality, and since the codespace is disconnected it's failing to access the underlying file system and getting into a fail / retry loop.
Repository: vscode
Issue: Do not autoplay videos in release notes
Labels: feature-request,release-notes

Hello, esteemed VSCode team!

Each month, you release a new version, along with a release note. I read each release note from top to bottom. (Example: [Version 1.85's release note](https://code.visualstudio.com/updates/v1_85).) But recently, a simple problem that has a simple solution has deteriorated the reading experience.

### Actual behavior

Each release note embed videos. When I open the release note, they start playing all at once. I'm forced to stop each video, rewind it, and watch it from the beginning. Here is screenshot of a video mid-playback.

![Actual behavior](https://github.com/microsoft/vscode/assets/17097175/88531c9c-59aa-4c38-8002-3934e110adf4)

### Expected behavior

However, for optimal viewing experience, they must look like this screenshot. Please note the large play button at the middle.

![Expected behavior](https://github.com/microsoft/vscode/assets/17097175/bc534af5-601c-4b7e-a99c-e9c81af5c44a)

### Solution

The problem is your HTML code.

Instead of this:

```html
<!-- 👎 NOT RECOMMENDED ❌ -->
<video src="/assets/updates/1_85/float_2.mp4" autoplay="" loop="" controls="" muted="" title="Command to Copy Editor into New Window"></video>
```

Please consider using this:

```html
<!-- 👍 RECOMMENDED ✔ -->
<video src="/assets/updates/1_85/float_2.mp4"                     controls="" muted="" title="Command to Copy Editor into New Window"></video>
```

All I did was to remove the `autoplay=""` and `loop=""` tokens. Please note their presence alone changes the browser behavior. Setting them to 1, 0, true, or false makes no difference.

Thanks in advance. 😊
Repository: stable-diffusion-webui
Issue: command line argument for set the output directory
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

I would like to be able to have a command line argument for set the output directory.  maybe something like: 

`--output-dir <location>`


### Proposed workflow

1.  use a new command line argument to set the default output directory 
` --output-dir <location>`
2. if location exists, continue, else fail and quick 

### Additional information

_No response_
Repository: deno
Issue: [deno compile] - don't include unnecessary lock file modules in compiled executable
Labels: suggestion,compile,node compat

At the moment, the deno.lock file is included in the deno compile executable along with all the modules it locks.  This seems unnecessary to have unused modules in the executable and would ideally be excluded.  [One user reported](https://discord.com/channels/684898665143206084/684898665151594506/1182435887037034528) a significantly large lock file adding some 75MB worth of modules to the executable despite being used.
Repository: bitcoin
Issue: DB_RUNRECOVERY: Fatal error, run database recovery
Labels: Wallet,macOS

### Is there an existing issue for this?

- [X] I have searched the existing issues

### Current behaviour

We are experiencing the build failures in NixPkgs both on x86_64-darwin and aarch64-darwin:

```
> 2023-12-07T14:45:33.311681Z [test] [wallet/bdb.cpp:189] [Open] BerkeleyEnvironment::Open: Error -30974 opening database environment: DB_RUNRECOVERY: Fatal error, run database recovery
> make[3]: *** [Makefile:22524: wallet/test/wallet_tests.cpp.test] Error 1
```

The full log is available from here: https://logs.ofborg.org/?key=nixos/nixpkgs.272548&attempt_id=8f5f1aaa-a3f7-4292-a194-57f85c49959a

I can reproduce the issue locally on my Macbook M1.

At first, the issue looks like a duplicate of https://github.com/bitcoin/bitcoin/issues/26869 but this time the issue is in `wallet/test/wallet_tests.cpp.test` not in `test/functional/wallet_backwards_compatibility.py`

### Expected behaviour

The test does not fail

### Steps to reproduce

1. install `nix`
2. `git clone https://github.com/nixos/nixpkgs.git`
3. `cd nixpkgs`
4. `git fetch origin pull/272548/head:pr-272548`
5. `git checkout pr-272548`
6. `nix-shell -I nixpkgs=$(pwd) -p bitcoin`

### Relevant log output

https://logs.ofborg.org/?key=nixos/nixpkgs.272548&attempt_id=8f5f1aaa-a3f7-4292-a194-57f85c49959a

### How did you obtain Bitcoin Core

Compiled from source

### What version of Bitcoin Core are you using?

26.0

### Operating system and version

macOS 13

### Machine specifications

_No response_