sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: kubernetes
Issue: Endpoints controller uses stale endpoints in reconciling, the endpoint Subsets will be wrong and never restores correctly
Labels: kind/bug,sig/apps,lifecycle/rotten,needs-triage

### What happened?

I have a service with two pods . These pods are ready, the endpoints subset contains these pods.

1. these pod became not ready at 12:35:39.149052Z
2. the endpoints controller update the endpoint, and move these pods to `notReadyAddresses`
3. one pod became Ready at 12:35:39.763051Z
4. the endpoints controller try to update the endpoint, but it failed with error: the object has been modified; please apply your changes to the latest version and try again
5. the other pod became Ready at 12:35:39.786936Z
6. the endpoints controller don't reconcile this endpoint any more, these pod are all in `notReadyAddresses`


The endpoint controller compare the endpoint subset (from cache) to pod status. At step 6, the endpoint informer watch is delayed,   the controller use the stale endpoint for comparison. From then on, the  endpoint subset is wrong. 


### What did you expect to happen?

The endpoint subset should be reconciled to correctly status

### How can we reproduce it (as minimally and precisely as possible)?

It is a little hard to reproduce, we need mock the endpoint watch delay.

### Anything else we need to know?

The controller pod informer resync not work in this case. Pod sync event will be ignore in `podEndpointsChanged`

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
Client Version: v1.31.0-aliyun.1
Kustomize Version: v5.4.2
Server Version: v1.31.0-aliyun.1
```

</details>


### Cloud provider

<details>
Alibaba cloud
</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: godot
Issue: In Godot 4.4 dev 2, typed dictionaries not compatible with JSON.parse_string
Labels: discussion,topic:core,documentation

### Tested versions

-Reproducible in Godot 4.4 dev 2

### System information

Windows 10, Godot 4.4 dev 2, Forward+

### Issue description

(I'm sorry if there is an open issue about this case and I didn't find it before opening this issue)

When using JSON.parse_string as an assignment to a typed dictionary that is not declared as `Dictionary[Variant, Variant]` (Example from my use case: `Dictionary[String, Dictionary]`) I get the error:

> Invalid assignment of property or key with value of type 'Dictionary'



### Steps to reproduce

- Add a new script to a node
- Add the following script:
```
extends Node

var d : Dictionary[String, Variant] = {}

var s : String = '{"A": "Hi","B": "Hey"}'
"""

func _ready() -> void:
	d = JSON.parse_string(s)
```

- Run the script (I got an error)
- Modify the dictionary to be `Dictionary[Variant, Variant]`
- Run the code again (Worked for me)

There is a MRP that has this script, with an extra line (commented by default) that loads the data from a .json file

### Minimal reproduction project (MRP)

[MRP.zip](https://github.com/user-attachments/files/17039753/MRP.zip)
Repository: excalidraw
Issue: Adding a child element with flowchart to an already preset set of childs overlap earlier childs if the shapes are large
Labels: good first issue

![flochart-overlap](https://github.com/user-attachments/assets/6fda05c9-e0a6-48be-8ccd-12bc3bf1877a)
Repository: rust
Issue: `-C instrument-coverage` misses regions in const assertions
Labels: T-compiler,C-bug,A-code-coverage

Hey, I've run into a problem with `-C instrument-coverage`, const generics and assertions.

I tried this code:
```rust
const fn check_even<const N: usize>() {
    assert!(N % 2 == 0, "will fail once");
}

#[test]
fn true_branch() {
    check_even::<8>();  // even number
}

#[test]
#[should_panic = "will fail once"]
fn false_branch() {
    check_even::<9>();  // will trigger the assertion
}
```
I prepared a reproducer with `cargo`, which is not exactly a MCVE, but the code itself is rather minimal. Therefore the following commands will set up a Cargo project with the aforementioned code in the `lib.rs`-file.
```bash
cargo new --lib repro
RUSTFLAGS="-C instrument-coverage" cargo test --manifest-path repro/Cargo.toml --tests
llvm-profdata merge -sparse repro/default_* -o merged.profdata
llvm-cov report --instr-profile merged.profdata repro/target/debug/deps/repro-* --show-branch-summary=false  # make sure, the correct test binary is picked up
```

I expected to see this happen: as all branches/regions are covered, I expect 100% test coverage. 

Instead, this happened: only 80% region coverage (but 100% line coverage as expected):
```text
Filename                                Regions    Missed Regions     Cover   Functions  Missed Functions  Executed       Lines      Missed Lines     Cover
------------------------------------------------------------------------------------------------------------------------------------------------------------
/home/jfrimmel/git/repro/src/lib.rs           5                 1    80.00%           3                 0   100.00%           9                 0   100.00%
------------------------------------------------------------------------------------------------------------------------------------------------------------
TOTAL                                         5                 1    80.00%           3                 0   100.00%           9                 0   100.00%
```
Specifically, the region containing the assertion message is not covered, despite it clearly has to be used, since the tests would fail due to the wrong panic message.
![llvm-cov show](https://github.com/user-attachments/assets/510087a4-48be-4d64-b1d7-88749febffa2)

For reference: this actually hits me in a project of mine, which aims to have 100% coverage. The only regions not covered are caused by assertions. The CI logs are located [here](https://app.circleci.com/pipelines/github/jfrimmel/emballoc/77/workflows/61129ef5-0baf-45a1-a367-61b337db5883/jobs/565?invite=true#step-102-4963_171).

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.81.0 (eeb90cda1 2024-09-04)
binary: rustc
commit-hash: eeb90cda1969383f56a2637cbd3037bdf598841c
commit-date: 2024-09-04
host: x86_64-unknown-linux-gnu
release: 1.81.0
LLVM version: 18.1.7
```
This also reproduces with the nightlies 2024-09-18, 2024-09-09, 2024-09-01 and 2024-08-01.

@rustbot label +A-code-coverage
Repository: vscode
Issue: TS: import does not follow `.js` suffix requirement
Labels: bug,typescript,debt

Steps to Reproduce:

1. open `keybindingsEditor.ts`
2. somewhere use the `unmnemonicLabel` method
3. let it auto import

=> 🐛 it adds `import { unmnemonicLabel } from '../../../../base/common/labels';` which is not ESM compatible.
Repository: rust
Issue: Rustonomicon and ManuallyDrop's documentation contradict each other about relying on drop order.
Labels: T-lang,T-libs-api,A-docs,C-bug

### Location

https://doc.rust-lang.org/nomicon/dropck.html#a-related-side-note-about-drop-order
https://doc.rust-lang.org/std/mem/struct.ManuallyDrop.html#manuallydrop-and-drop-order

### Summary

The Rustonomicon [states](https://doc.rust-lang.org/nomicon/dropck.html#a-related-side-note-about-drop-order):
> While the drop order of fields inside a struct is defined, relying on it is fragile and subtle. When the order matters, it is better to use the `ManuallyDrop` wrapper.

The docs for `ManuallyDrop` [states](https://doc.rust-lang.org/std/mem/struct.ManuallyDrop.html#manuallydrop-and-drop-order):
> Rust has a well-defined [drop order](https://doc.rust-lang.org/reference/destructors.html) of values. To make sure that fields or locals are dropped in a specific order, reorder the declarations such that the implicit drop order is the correct one.
> It is possible to use ManuallyDrop to control the drop order, but this requires unsafe code and is hard to do correctly in the presence of unwinding.

That is, when you rely on fields being dropped in a specific order, the Rustonomicon recommends using `ManuallyDrop`, while the `ManuallyDrop` documentation recommends using field ordering. Which of the two is correct?
Repository: vscode
Issue: debug restart does not work in test mode
Labels: info-needed

<!-- ⚠️⚠️ 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.93.1 
- OS Version: Sonoma 14.5

Steps to Reproduce:

1. run a test from the integrated test runner 
2. hook the debugger on a breakpoint
3. click the restart button

I also tried this on the latest insiders build, but it fails with the same error as in the current vs code

> Invalid message: either "program", "module", or "code" must be specified

<img width="1706" alt="Screenshot 2024-09-18 at 10 20 18" src="https://github.com/user-attachments/assets/187ec496-6a0e-4d2e-b3c8-3bad1c7ac65d">

I found others discussing this issue in the playright issues in a couple of places related to vscode and I opened an issue there that pulled those threads together

https://github.com/microsoft/playwright/issues/32655

but I then realised that that was probably the wrong repo.

This change would make testing with debugging so much more efficient - I hit this issue multiple times a day - debug restart works on all my scripts, but not my tests :-(
Repository: kubernetes
Issue: When the pod is deleted, GC the current image.
Labels: sig/node,kind/feature,lifecycle/rotten,needs-triage

### What would you like to be added?

I want to add an Image GC strategy. When a single Pod is deleted, the image is marked as needing GC and deleted when the next GC cycle starts.

### Why is this needed?

When a cluster has an Image P2P distribution system, each node is used as a proxy node for the image. This will cause an image to exist twice on the node, resulting in low disk utilization. Therefore, it is hoped that the image at runtime will be deleted and only the image in the P2P system will be retained.
Repository: stable-diffusion-webui
Issue: [Feature Request]: The EC2 instance type is g6e.xlarge, but it's taking 8 seconds to render an image via the API, which is too long. What should I do?
Labels: enhancement

### Is there an existing issue for this?

- [ ] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Speed up the rendering time on G6e.xlarge.

### Proposed workflow

![image](https://github.com/user-attachments/assets/32dee60b-f1b1-46df-9e46-13543a03891d)


### Additional information

_No response_
Repository: react
Issue: [React 19] Export SuspenseException 
Labels: Type: Feature Request,React 19

## Problem Statement
Currently, in React's `use(promise)` mechanism, there is no straightforward way to determine whether an exception originates from a promise suspended within the `use` hook. This makes it challenging for developers to:
- Accurately catch and handle errors related to suspended promises.
- Differentiate between errors caused by `use(promise)` and other unrelated errors, complicating error handling logic.

## Proposal
React should export either:
1. A `SuspenseException` class that can be used to identify errors originating from a promise suspension, or
2. A utility function to check whether a given error is caused by a suspended promise in `use(promise)`.

### Example Usage

1. **SuspenseException Class:**
    ```jsx
    import { SuspenseException } from 'react';

    try {
      use(fetchData());
    } catch (error) {
      if (error === SuspenseException) {
        // Handle Suspense-related logic
      } else {
        // Handle other types of errors
      }
    }
    ```

2. **Utility Function:**
    ```jsx
    import { isSuspenseException } from 'react';

    try {
      use(fetchData());
    } catch (error) {
      if (isSuspenseException(error)) {
        // Handle Suspense-related logic
      } else {
        // Handle other types of errors
      }
    }
    ```

## Benefits
- **Error differentiation:** Clear distinction between promise suspensions and other errors.
- **Enhanced debugging:** Easier diagnosis of Suspense-related issues in both development and production.
- **Safer error handling:** Prevents unintended catches of non-Suspense errors during Suspense management.


## Conclusion
By exporting either a `SuspenseException` or a utility function, React would offer developers more control over managing Suspense-related errors, improving both error handling and debugging in applications.
Repository: opencv
Issue: JS: Support new `using` javascript keyword for explicit resource management
Labels: feature,category: javascript (js),community help requested

### Describe the feature and motivation

There is a TC39 proposal to add the `using` keyword to JavaScript:
https://github.com/tc39/proposal-explicit-resource-management

This is already implemented in TypeScript:
https://www.typescriptlang.org/docs/handbook/release-notes/typescript-5-2.html#using-declarations-and-explicit-resource-management

It would be great if, instead of having to call `.delete()` manually on objects, we could use the `using` keyword to ensure memory cleanup.

### Additional context

_No response_
Repository: vscode
Issue: Making all the code-cell outputs scrollable 
Labels: feature-request

<!-- ⚠️⚠️ 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. -->

Even when editing the setting of VS Code called `notebook.output.scrolling` to `true`, the output of a code-cell in a notebook (i.e. file with extension `.ipynb`) does not get restricted, except when using the function `print(...)` to create output. 
![image](https://github.com/user-attachments/assets/6c45fcfa-dbb8-4f42-b7fb-b61ce6085a71)
 

If you for example try using either: 
- the function `display(...)` from `IPython.display` to display a `pandas.DataFrame`, or 
![image](https://github.com/user-attachments/assets/0bea2d79-fdbf-4866-b60c-2e28e0d7c22f)
- making a plot using `matplotlib.pyplot` and displaying it in the output (or any kind of an image), 
![image](https://github.com/user-attachments/assets/53b2082b-31d0-4a2b-bc7a-1b73d69a7de5)
then the size of the code-cell output is not restricted and scrollable, but stretches all the way until the whole element (either the `pandas.DataFrame`, or the plot) is displayed. 
 
Is there an option in VS Code which will allow its user to restrict the size of a code-cell output, not matter how the output is created (i.e. no matter if the output is generated using the function `display(...)`, if it is a plot, if it is using the function `print(...)`)? 



**Note**: There was previously a similar issue created: [the_issue](https://github.com/microsoft/vscode/issues/206226), but the requestor never wrote a reply to what you had to say. I think that my request is a bit different, because I would not change the fact that each output is independent, but I would only make it possible to make either:
1. make a setting which would allow the user to specify that if all the outputs of one code-cell exceed some size, to the code-cell output (looking at the code-cell output as an output, no matter if is actually comprised out of multiple outputs logically) scrollable
2. make it possible to specify for each of the outputs of one code-cell individually to be scrollable if they exceed a certain size.

In my opinion, it would be the best if both of these settings were implemented, but having at least one of the two would do the trick for most of the people.
Repository: vscode
Issue: Windows integration crash
Labels: bug,freeze-slow-crash-leak,windows,integration-test-failure

https://dev.azure.com/monacotools/Monaco/_build/results?buildId=293714&view=results
Repository: PowerToys
Issue: Auto-type clipboard content as keystrokes (paste)
Labels: Resolution-Helped User

### Description of the new feature / enhancement

When I'm required to use different vendors' password managers, RMMs, and remote connection tools for work, I often find myself unable to copy-paste a password (or any text) from the host machine to the guest. In my humble opinion, it would be an excellent feature if a specific keyboard combination could auto-type the text from the clipboard as keystrokes.

Similar to how KeePass auto-fills passwords.

### Scenario when this would be used?

It would be useful for helpdesk engineers and sysadmins who often have to "jump" into servers or workstations through multiple remote connection tools, particularly when the copy/paste function doesn't work (e.g., in Quick Assist).

### Supporting information

_No response_
Repository: ui
Issue: [feat]: Stepper UI component
Labels: area: request

### Feature description

Is it possible to implement a stepper using components already in shadcn

e.g. Googel Maps
![image](https://github.com/user-attachments/assets/72583fe7-9a73-4303-97fc-b3d94570f4a7)

e.g. GMPRO Viewer
![image](https://github.com/user-attachments/assets/05af91e4-81c0-4873-9c4a-b7352fa2d009)


### Affected component/components

_No response_

### Additional Context

_No response_

### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues and PRs
Repository: PowerToys
Issue: Workspaces Does Not Span Virtual Desktops
Labels: Issue-Bug,Needs-Triage,Product-Workspaces

### Microsoft PowerToys version

0.84.1

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

General, Workspaces

### Steps to reproduce

I love the new workspaces concept, but it does not span virtual desktops.  This to me seems like a bug as it severely limits the usefulness of this utility.  Would also be nice to have it remember the open tabs of the browser and what web URLs they had open. 

### ✔️ Expected Behavior

Workspaces to record and use all virtual desktops. 

### ❌ Actual Behavior

Workspaces only records the active virtual desktop. 

### Other Software

_No response_
Repository: go
Issue: x/tools/go/analysis/passes/printf: suggest Printf calls without args to use Print
Labels: NeedsInvestigation,Tools

### Go version

1.23.1

### Output of `go env` in your module/workspace:

```shell
no relevant
```


### What did you do?

Run the "printf" pass with `go vet` or `golangci-lint`

### What did you see happen?

It doesn't detect anything for `fmt.Printf("some message")`.

### What did you expect to see?

Maybe it should suggest to rewrite `fmt.Printf("some message")` => `fmt.Print("some message")`, because it doesn't use any argument.
Repository: PowerToys
Issue: Everything freezes - PresentationFramework issue
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.81.1.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

General

### Steps to reproduce

[2024-09-18.txt](https://github.com/user-attachments/files/17043491/2024-09-18.txt)


### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

Everything freezes (two external display setup connected to closed Lenovo laptop with USB-C docking station) until I open the laptop.

### Other Software

Google Chrome version 128.0.6613.138
Repository: neovim
Issue: ansi color code highlight util
Labels: enhancement,defaults,input,complexity:low,highlight,pager

# Problem

Nvim is a pretty good pager for "man", but can't easily replace `less -R` for other (non-manpage) terminal output containing ANSI color codes.

Programs like kitty terminal, allow configuring any program such as `less -R` or `nvim` for displaying terminal "scrollback". `less -R` colorizes ANSI color codes, but Nvim doesn't.

Currently, this is the `kitty.config` setting I use:

    scrollback_pager nvim --clean --cmd 'set eventignore=FileType' +'%s/\e\[[0-9;]*m//g' +'set nomodified readonly' +'$' -

but that removes the escape codes instead of colorizing them.



# Expected behavior

- ✅ document `nvim_open_term` snippet
- provide a `nvim_open_term` wrapper as command/function that makes it easy to colorize a buffer containing ANSI escape codes.
    - https://github.com/folke/dot/blob/39602b7edc7222213bce762080d8f46352167434/nvim/lua/util/init.lua#L68-L93
    - https://github.com/neovim/neovim/issues/30415#issuecomment-2368519968
- expose `:terminal highlights` as highlight groups. https://github.com/neovim/neovim/pull/7406#issuecomment-337363444

## Reference

previous implementations:

- https://github.com/neovim/neovim/issues/5054 and other posts mention ye olde AnsiEsc.vim 
- https://github.com/lucc/nvimpager
Repository: PowerToys
Issue: Color Picker closes automatically
Labels: Needs-Triage,Product-Color Picker,Status-Reproducible

### Description of the new feature / enhancement

The color picker closes after a short time. Why? This is very annoying.

### Scenario when this would be used?

Whenever anyone uses the color picker.

### Supporting information

Please don't say use the shortcut. Eff the shortcut. When I open the damn editor, I want it to stay open until I close it. If you're obsessed with keeping it open, then at least provide a setting somewhere that will allow users to override this "feature".
Repository: svelte
Issue: Update of $state variable overwrites it instead of update
Labels: documentation

### Describe the bug

Update of $state variable overwrites it instead of update when the state variable was returned by a function.

As you can see in the 2nd log line, `count2` is not a state proxy anymore.

```
<script>
//App.svelte
	import { createStore } from './Stores.svelte.js';

	let count = $state({});
	let count2 = createStore();

	console.log('stores', count, count2);

	count = { some: 'value' };
	count2 = { some: 'value' };

	console.log('stores after', count, count2);

</script>
```


```
//Stores.svelte.js
export function createStore() {
  let store = $state({});
	return store;
}
```

### Reproduction

https://svelte-5-preview.vercel.app/#H4sIAAAAAAAAA3WRTWrDMBCFrzKIghwINnhpp4WcIcu6C1cZFwVZMtIobRG6e-UfEps0aCFmnt684VNgnVToWPUemG57ZBU7DgPbM_odxsJdURGm2hlvxdg5OGHlQG-NTodkPxhLEEBYbAlPZCxChM6aHnheTLXL5yn5xfF6tikkEMZrgld4cZScWYi7eiOVSVtNzXaLVxjtjMJcma-MuymA72fLcpX3p3NEAGd6rIBfW-WRQ6xvavlM_j8J2o7QPssrihMifFrz7dDCYm_0oVgxSyx7c5adxDOryHqM-xv6Da77J1zc-gPwZ0LeeS1IGr1lBKHRACPDad9HvBbJWz2rqREf1_mIf_bmXW4VAgAA

### Logs

```shell
- stores Proxy(Object) {} Proxy(Object) {}
- stores after Proxy(Object) {some: 'value'} {some: 'value'}
```


### System Info

```shell
Svelte 5.0.0-next.251
```


### Severity

blocking an upgrade