sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Fancy Zones issue 
Labels: Issue-Bug,Product-FancyZones,Needs-Triage

### Microsoft PowerToys version

0.78.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

FancyZones

### Steps to reproduce

When selecting the Fancy Zones option "Move newly created windows to their last known zone", I am then unable to unlock password protected documents. I can open the document, but am no longer prompted to enter the password, and am therefore unable to view the content.

### ✔️ Expected Behavior

To be able to open the document, enter the password, and view the content

### ❌ Actual Behavior

Open the document, but no prompt to enter password.

### Other Software

_No response_
Repository: flutter
Issue: Run plugin tests against the debug engine
Labels: team,team-ecosystem,P2,triaged-ecosystem

Right now plugin tests run against the release version of the flutter engine.  The release version of the engine has less verification for correctness.  For example, in https://github.com/flutter/packages/pull/6069 it was found that a platform channel in the `google_maps_flutter` plugin was being used from a background thread which is a [violation](https://docs.flutter.dev/platform-integration/platform-channels?tab=type-mappings-swift-tab#channels-and-platform-threading) that can introduce race conditions.  It is silently ignored in release engines, but if plugin tests were run against the debug engine we'd catch those failures and potentially others.

It is my understanding that we save debug builds but they may not be readily served by the flutter tool.

This will solve the issue for our plugins, ideally this feature would be available to external plugin developers.
Repository: kubernetes
Issue: Add event for "container Died" when container get killed
Labels: sig/node,sig/api-machinery,kind/feature,triage/accepted

### What happened?

There is mission critical application we have for which we need events recorded for Container death in all cases including restarting event that is possibly indicated by BackOff event
While checking this, we found that the Container stopped event is recorded when a pod is deleted.
However, in other cases, there is no clear indication that the container was stopped and deleted.


### What did you expect to happen?

There should be a log message for container death

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

You can check it by creating a deployment/pod and deleting the container explicitly.
The container will restart but there wont be log for old container deletion..


### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
```

</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: pytorch
Issue: Cudnn 9.2 is out!
Labels: module: cudnn,triaged,enhancement

### 🚀 The feature, motivation and pitch

speed up free!
changelog: https://docs.nvidia.com/deeplearning/cudnn/release-notes.html

### Alternatives

_No response_

### Additional context

_No response_

cc @csarofeen @ptrblck @xwang233
Repository: go
Issue: x/website/_content/doc: "Uninstalling Go" has no mention of Go's configuration directory
Labels: Documentation,help wanted,NeedsFix

Modern versions of Go store configuration in the user's configuration directory, under a directory named "go". For example, an `env` file that stores Go configuration as set by `go env -w` invocations.

As pointed out in https://github.com/golang/go/issues/65568#issuecomment-1932657199, the instructions for uninstalling Go at https://go.dev/doc/manage-install#uninstalling currently don't mention directories for configuration, which can cause confusion.
Repository: flutter
Issue: Tests with many goldens (i.e. `flutter/test/painting/star_border_test.dart`) make Skia gold angry
Labels: c: crash,P2,c: tech-debt,team-engine,triaged-engine

I personally run into this a bunch in "Framework Smoke Tests" on `flutter/engine`. I suspect it impacts framework CI as well.

[Example](https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8756728186957789137/+/u/Framework_test/test:_Framework_test/stdout) output:

```txt
19:17 +7651 ~121: /b/s/w/ir/cache/flutter/packages/flutter/test/painting/star_border_test.dart: StarBorder parameters                                                                                  
══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following HttpException was thrown while running async test code:
Connection closed before full header was received, uri =
https://flutter-gold.skia.org/img/images/c4be4c17b9a965d6cd1b33d7467419b6.png

When the exception was thrown, this was the stack

The exception was caught asynchronously.
════════════════════════════════════════════════════════════════════════════════════════════════════

19:17 +7651 ~121 -1: /b/s/w/ir/cache/flutter/packages/flutter/test/painting/star_border_test.dart: StarBorder parameters [E]                                                                           
  Test failed. See exception logs above.
  The test description was: StarBorder parameters
  

To run this test again: /b/s/w/ir/cache/flutter/bin/cache/dart-sdk/bin/dart test /b/s/w/ir/cache/flutter/packages/flutter/test/painting/star_border_test.dart -p vm --plain-name 'StarBorder parameters'
```

I am going to send a PR to temporarily disable this test, but I have two recommendations:

1. `star_border_test` has too many golden files (by my count, over 70 in this particular unit test). That seems excessive.
2. `skia_gold_client` needs some combination of respecting HTTP status codes, and potentially queueing/backoff
Repository: stable-diffusion-webui
Issue: [Feature Request]: Maybe integrate sd-webui-forge?
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 ?

It would be nice to integrate [sd-webui-forge](https://github.com/lllyasviel/stable-diffusion-webui-forge) into regular sd-webui

### Proposed workflow

.

### Additional information

_No response_
Repository: next.js
Issue: Web Worker creation heuristics
Labels: bug

### Link to the code that reproduces this issue

https://github.com/brandonjpierce/nextjs-workers

### To Reproduce

`npm run dev` to boot up the app. You should see a runtime exception. If you go to `src/playground/worker-struct.ts` you can comment out `c` and `e` in the `workers` object to see it "working" without the runtime exceptions.

### Current vs. Expected behavior

```javascript
const path = new URL("./workers/a", import.meta.url);
const file = "a";

const workers = {
  // Works
  a: new Worker(new URL("./workers/a", import.meta.url), {
    type: "module",
    name: "worker struct > a",
  }),
  // Nextjs treats as static file, does not work
  b: new Worker(path, {
    type: "module",
    name: "worker struct > b",
  }),
  // Runtime exception
  c: new Worker(new URL(`./workers/${file}`, import.meta.url), {
    type: "module",
    name: "worker struct > c",
  }),
  // Works
  d: new Worker(new URL(`./workers/${"a"}`, import.meta.url), {
    type: "module",
    name: "worker struct > d",
  }),
  // Runtime exception
  e: getWorker("test", "a"),
};
```

I would expect at a bare minimum `a`, `c`, `d`, and `e` to work but would also like additional clarification on `b` regarding fully dynamic path values.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000
Binaries:
  Node: 18.18.2
  npm: 9.8.1
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

This is really more of a general "how should this work?" type of question / bug report but given there may actually be a bug hidden in here I decided to open an issue vs. a discussion thread. Some backstory, my team is working on some abstractions around web workers and we were running into some oddities around how Next (or Webpack presumably) handles certain scenarios. Included in the code to reproduce the issue are five scenarios.

`src/playground/worker-struct.ts`

I have deduced that `b` is likely due to the [note here](https://webpack.js.org/api/module-methods/#dynamic-expressions-in-import) regarding using fully dynamic values for import statements. The really odd one is `c` vs. `d` since those have a partially static path with `c` having a dynamic value.

⚠️ Additional note, none of the example seem to work with `next --turbo`
Repository: kubernetes
Issue: Dynamic node lease renew interval
Labels: sig/scalability,sig/node,sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

Make the node lease renew internal dynamic. For example, with default settings of `nodeLeaseDurationSeconds` being 40s, the node lease is renewed every 1/4 of `nodeLeaseDurationSeconds` (i.e. 10s). With this feature, it can be 20s, but if the renew is unsuccessful, the interval decreases to 10s and if it fails again, interval decreases to 5s. However, after 3 attempts, the interval resets to 20s.

### Why is this needed?

With increasing popularity in using k8s with a large number of nodes, it becomes a significant overhead for apiserver to just handle the node lease renew requests. As mentioned above, each node renews its lease every 10s so every node contributes 0.1 QPS just with lease renewing alone. Also worth mentioning, lease renew has to hit ETCD as it's a modification request, which is more expensive than cache read request (about 8ms vs 1ms under no stress). 

It's difficult to measure how much resource a lease renewing would cost and it's even more difficult taking extra overhead when under stress (and therefore perf degradation) into consideration but with this feature, we can potentially cut the request volume in half (i.e. 50% decrease) while minimize the risk of having fewer attempts for failed renew requests within `nodeLeaseDurationSeconds`. From non-audited observations, I expect 0.2 cores saved in a cluster of 200 nodes.
Repository: vscode
Issue: Some Hebrew letters appear with a square in JSON
Labels: bug,unicode-highlight

<!-- ⚠️⚠️ 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. -->
- VS Code Version: 1.86.0
- OS Version: Windows 10

Steps to Reproduce:

1. Paste the following JSON in VS Code:
```
{
    "a": "אבגדהוזחטיכלמנסעפצקרשת1",
    "b": "סיוט"
}
```

The letters ו, ט, י and ס are highlighted when the word is followed by a number (with no space between), or when a word consists from these characters alone (e.g. סיוט).

![image](https://github.com/microsoft/vscode/assets/1246544/8e743dca-3aec-453f-ba41-222793e1b477)
Repository: godot
Issue: Conflict between Area2D Signal's documentation and behavior
Labels: discussion,documentation,topic:physics

### Tested versions

Reproducible in 4.1.3 and 4.3-dev2

### System information

Windows 11

### Issue description

Context: We're working on a turn-based tactical RPG, and the current version of our ai is simulating possible moves to determine the best move on its turn.  To accomplish this simulation, the ai is moving an area2d around to determine what targets are in its area of effect attack for any given move.  This process is happening faster than the physics frames.  We noticed this issue when we started with `get_overlapping_areas` but noticed the documentation has another solution.

The documentation says (in the `get_overlapping_areas` method for `Area2D`) "For performance reasons (collisions are all processed at the same time) this list is modified once during the physics step, not immediately after objects are moved. **Consider using signals instead**." (emphasis mine).

But signals do not appear to work.  Signals seem to only be emitting on physics frames as well, so rapid movements into and out of area2ds (done by the code and not a player) are not registering until the next physics frame.

We're pretty confident either the code or the documentation is wrong.

### Steps to reproduce

Move an area2d to multiple locations within the same physics frame does not cause signals to be emited

### Minimal reproduction project (MRP)

Zip and link to git folder included.
https://github.com/AlchemicalPanda/Physics_Bound_Signals_MRP/tree/main
[Physics_Bound_Signal_MRP.zip](https://github.com/godotengine/godot/files/14201135/Physics_Bound_Signal_MRP.zip)
Repository: material-ui
Issue: [material-ui] Inconsistent spacing units between components under default styling
Labels: package: material-ui,enhancement

### Steps to reproduce

Link to live example: https://codesandbox.io/p/sandbox/sad-forest-g88786?file=%2Fsrc%2Findex.tsx%3A35%2C3
You'll see there is red inner content surrounded by green outer content - the hope is that this illustrates where padding is used.









### Current behavior

Spacing units is inconsistent between different components' default styles. This issue becomes very apparent when adding a custom `spacing` function to the theme.

When specifying space in the `sx` of any component the behavior is consistent and predictable
- `padding: 16` will get converted to `padding: 1.6rem`
- `padding: "16px"` stays `padding: "16px"`
- `padding: theme.spacing(20, 40)` becomes `padding: 2rem 4rem`
etc

Unfortunately with the way default styles are defined on out of the box components, this custom `spacing` function completely breaks consistency on some base styles.

For example:
- [Button's base padding](https://github.com/mui/material-ui/blob/master/packages/mui-material/src/Button/Button.js#L90) is defined as `padding: '6px 16px'` - which stays the same (`padding: '6px 16px'`)
- [CardContent's base padding](https://github.com/mui/material-ui/blob/master/packages/mui-material/src/CardContent/CardContent.js#L26) is `padding: 16` - which gets converted to `padding: 1.6rem`
- [AccordionSummary's base padding](https://github.com/mui/material-ui/blob/master/packages/mui-material/src/AccordionSummary/AccordionSummary.js#L39) is `padding: theme.spacing(0, 2)` - which gets converted to `padding: 0 0.2rem`

Button and CardContent's padding ends up matching what the original intent was and renders appropriately.
AccordionSummary's padding ends up being completely wrong.

### Expected behavior

My hope is that in the future there is consistency between component's base styles' use of units on spacing. It seems like unit-less spacing in these default styles would be preferred, so that in the end the `spacing` function is used and devs have more control over what that actually means. This seems like something that should be enforced on the project as a whole.

### Context

Above is an example (and mirrors my project's production environment) where we convert all spacing units to rem, and base it on the fact the base website font size is 10px.

### Your environment

_No response_

**Search keywords**: space spacing units theme
Repository: PowerToys
Issue: Directly enter plugin mode of powertoys run via shortcut
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage,Run-Plugin

### Description of the new feature / enhancement

suppose we're searching for opened windows, you'll do a shortcut combo and a prefix key triggering powertoys run plugin search. Do we not have something that allow us to define our own shortcut that directly triggers the plugin search.

Just as an example, in vscode we have `command`+`shift`+`p` and `command`+`p` and when doing the prior you'll see that the search bar contains a `>` prefix. Same applies here, we do a simple combo maybe 2 or 3 keys and the search bar will pop up with the prefix prefilled.

### Scenario when this would be used?

when using powertoys run plugins

### Supporting information

_No response_
Repository: vscode
Issue: Unwanted scrolling in macOS with native trackpad and pinch zoom gesture.
Labels: bug,macos,trackpad/scroll

Type: <b>Bug</b>

Inside macOS, double check that the trackpad gesture `Zoom in or out` is enabled.
Also make sure that the VS Code option `editor.mouseWheelZoom` is disabled.

Now try to execute the pinch to zoom gesture on a long file. It will scroll it vertically.

The expected behaviour should be to... do nothing!
I found an old issue reporting the same problem, but it was closed: [19637](https://github.com/Microsoft/vscode/issues/19637).

Inside the private method `_onMouseWheel` from the file `scrollableElements.ts` I noticed that the gesture is basically detected as an ordinary scrolling event and that `classifier.isPhysicalMouseWheel()` always returns true from this gesture.
I see no way to filter out the gesture event from that method, but maybe that's not even the correct way to fix the issue.

VS Code version: Code 1.86.0 (05047486b6df5eb8d44b2ecd70ea3bdf775fd937, 2024-01-31T10:29:11.933Z)
OS version: Darwin arm64 22.6.0
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Apple M1 Pro (8 x 24)|
|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>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|2, 3, 3|
|Memory (System)|32.00GB (0.62GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details>Extensions: none
<!-- generated by issue reporter -->
Repository: go
Issue: runtime: execLock might deadlock on darwin/ios
Labels: OS-Darwin,NeedsInvestigation,compiler/runtime

If you run

	GOEXPERIMENT=staticlockranking go test strings

on a Mac, it fails badly, because the preemptM can be called while holding various locks that conflict with execLock.rlock, specifically this part:

	// On Darwin, don't try to preempt threads during exec.
	// Issue #41702.
	if GOOS == "darwin" || GOOS == "ios" {
		execLock.rlock()
	}

This is indicative of a real potential deadlock on macOS and iOS, though not one that seems to have been reported yet. So probably it's very rare if it can happen at all. Unclear how to fix that.

/cc @aclements
Repository: pytorch
Issue: [c10d] accept [] in torch.distributed.all_gather_object
Labels: triaged

### 🚀 The feature, motivation and pitch

could save the effor to create [None, None, ...] (length=world_size)

similar collectives are broadcast_object_list, scatter_object_list

motivated by PR https://github.com/pytorch/pytorch/pull/118755 

### Alternatives

_No response_

### Additional context

_No response_
Repository: pytorch
Issue: [c10d][NCCL] better error msg than "Software caused connection abort"
Labels: triaged

### 🚀 The feature, motivation and pitch

if I miss configured rank or processgroup, NCCL will complain Software caused connection abort but it's less actionable. maybe error about "duplicated rank" would be helpful

motivated by mis configured sub pgs (some rank call new_group[0,1] some rank call new_group[2, 3] https://github.com/pytorch/pytorch/pull/118593

### Alternatives

_No response_

### Additional context

_No response_
Repository: flutter
Issue: [web] Flutter test suite in the web needs love.
Labels: a: tests,tool,platform-web,P2,team-web,triaged-web

While investigating [this revert](https://github.com/flutter/engine/pull/50404), a couple of concerning things were discovered wrt the Flutter test suite in the web.

1. The revert was caused because some tests failed when the `scene` of the HTML renderer started respecting the "overridden" value of `devicePixelRatio` to report its "logical size". 
    * Bad behavior that **fixed golden tests** and allowed `hostElement` to reland was introduced [here](https://github.com/flutter/engine/pull/38477).
    * This used to work before because we were using the [logical size directly from the `window` JS object](https://github.com/flutter/engine/blame/234ab4c1e9c48c20828fba58c2a0a52d169779ed/lib/web_ui/lib/src/engine/html/scene.dart#L51-L52), which doesn't care about overrides.

2. The [devicePixelRatio overridden by flutter tests](https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/web/bootstrap.dart#L252-L253) (3.0) does NOT match the [devicePixelRatio set by the browser when it starts](https://github.com/flutter/flutter/blob/master/packages/flutter_tools/lib/src/web/chrome.dart#L222). 
    * In fact, the browser is starting always with DPR=1. It should pass `'--force-device-scale-factor=X'` for other DPRs.

3. ~~By hijacking the `_matchers_web.dart` file, it seems that the `isCanvasKit` boolean used there to determine how to match a golden never returns `true` (this might be a regression)~~ Fixed by: https://github.com/flutter/flutter/pull/143128

----

TL;DR: The `flutter test` runner needs some love in the `flutter/flutter` repository.
Repository: deno
Issue: WebSocket instability
Labels: needs info,ext/websocket

Version: at least Deno 1.39.1 through 1.40.3

This is related to #17283 and probably other issues, but recently WebSockets seem to have gotten more unstable. Simply refreshing pages or navigating in a browser which is connected via a WebSocket to a Deno server can lead to various crashes of the form: `Upgrade response was not returned from callback`. This seems like a regression as it was previously relatively stable (except when using TLS).
Repository: flutter
Issue: Move //flutter/vulkan into //flutter/shell/platform/fuchsia.
Labels: P3,c: tech-debt,team-engine,triaged-engine

Fuchsia is the only user of this library (even when using Vulkan with Impeller). Some utilities like proc tables are initialized a couple of times because of similar libraries.