sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: terminal
Issue: Dimmed UAC-prompt in Windows freezes it when logged in Windows terminal with user other than the one logged in
Labels: Issue-Bug,Needs-Author-Feedback,Needs-Triage,No-Recent-Activity

### Windows Terminal version

1.21.3231.0

### Windows build number

 10.0.26100.0

### Other Software

UAC-prompt that dims Windows causes this issue that freezes the entire OS.

### Steps to reproduce

1.	Start Windows Terminal either as Administrator (if the logged in user account does not have admin privileges) or as other user and use an account other than the one logged in.
2.	Perform any action that triggers a UAC-promt in Windows. The setting needs to be set so it dims Windows.

### Expected Behavior

UAC-prompt should appear as normal when Windows Terminal is started with a different account than the one logged in Windows. 

### Actual Behavior

Windows freezes when a UAC-prompt pops up for any reason, even when not concerning Windows Terminal. This happens when Windows Terminal is started with a different user than the one logged in Windows. This is recreated with a user that has admin privileges and unsure if this happens with accounts without admin privileges. When doing anything that triggers a UAC-prompt where it dims Windows it freezes it completely. The screen dims, but no UAC-prompt is displayed. You can CTRL+ALT+DEL back to Windows, but all windows and taskbar is almost non-responsive. You can control the cursor, but it seem to not register any clicks and nothing from the keyboard as well. The CPU works extra hard as it’s fan speeds up to max and there is a considerably delay when clicking on different windows like the are responding, but heavily delayed so Windows is not usable.

The only way to resolve the issue is to turn off the computer on the power button.

Cannot find any issue within the Event viewer. This issue has been reproduced on two different laptops with multiple reinstalls of Windows.
Repository: rust
Issue: `PostAnalysisNormalize` can introduce new `{type_error}`
Labels: I-ICE,T-compiler,C-bug

```rust
#![feature(type_alias_impl_trait)]
type Tait = impl Copy;

fn set(x: &isize) -> isize {
    *x
}

fn d(x: Tait) {
    set(x);
}

fn other_define() -> Tait {
    ()
}

fn main() {}
```
This results in an ICE with `rustc src/main.rs -Zvalidate-mir -Zinline-mir=yes` 
```
error: concrete type differs from previous defining opaque type use
  --> src/main.rs:13:5
   |
13 |     ()
   |     ^^ expected `&'static isize`, got `()`
   |
note: previous use here
  --> src/main.rs:9:5
   |
9  |     set(x);
   |     ^^^^^^

error: internal compiler error: compiler/rustc_middle/src/mir/tcx.rs:118:21: deref projection of non-dereferenceable ty PlaceTy { ty: {type error}, variant_index: None }


thread 'rustc' panicked at compiler/rustc_middle/src/mir/tcx.rs:118:21:
Box<dyn Any>
stack backtrace:
  15:     0x7f1f7416d320 - rustc_middle[6ec8af473b9179e3]::util::bug::bug_fmt
  16:     0x7f1f7871f15c - <rustc_middle[6ec8af473b9179e3]::mir::tcx::PlaceTy>::projection_ty.cold
  17:     0x7f1f77ccac3c - rustc_mir_transform[ddf46edc4b25c392]::validate::validate_types
  18:     0x7f1f77cc03da - <rustc_mir_transform[ddf46edc4b25c392]::validate::Validator as rustc_mir_transform[ddf46edc4b25c392]::pass_manager::MirPass>::run_pass
  19:     0x7f1f75584745 - rustc_mir_transform[ddf46edc4b25c392]::pass_manager::validate_body
  20:     0x7f1f77204b6c - rustc_mir_transform[ddf46edc4b25c392]::pass_manager::run_passes_inner
  21:     0x7f1f7733d234 - rustc_mir_transform[ddf46edc4b25c392]::optimized_mir
```
The body of `d` does not contain any type errors while building, so we actually build a body:
https://gist.github.com/lcnr/70f559aa69c4a733ca28f47b4a247113

We then normalize `Tait` to `{type error}`: https://gist.github.com/lcnr/92bde9605c555818cc90ea4e0321a258

Resulting in a deref projection of that type error after inlining: https://gist.github.com/lcnr/138f486799689a556d840f3a172b6068

We've got multiple ways forward here:
- more gracefully handle type errors in mir validation/optimizations
- replace the body with a dummy when normalizing to a type error

I believe this can be triggered with RPIT as well, it'd just be a bit more cumbersome
Repository: kubernetes
Issue: [Flaking test] Service is not reachable within 2m0s timeout on endpoint 172.31.0.12:xx over TCP protocol
Labels: sig/network,kind/flake,triage/accepted

### Which jobs are flaking?

master-informing
- Conformance-EC2-arm64-master

### Which tests are flaking?

Kubernetes e2e suite.[It] [sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance]
Kubernetes e2e suite.[It] [sig-network] Services should be able to create a functioning NodePort service [Conformance]
Kubernetes e2e suite.[It] [sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance]
Kubernetes e2e suite.[It] [sig-network] Services should have session affinity work for NodePort service [LinuxOnly] [Conformance]

### Since when has it been flaking?

According to Triage, these tests have flaking since begining of Jan. 
[15/01/2025, 15:23:29](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-ubuntu-ec2-containerd/1879383533215027200)
[15/01/2025, 05:40:06](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-ec2-arm64-conformance-latest/1879236563192254464)
[14/01/2025, 15:24:02](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-ubuntu-ec2-arm64-containerd/1879021141591330816)
[13/01/2025, 12:38:25](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-kubernetes-e2e-ec2-eks-al2023/1878617225812774912)


### Testgrid link

https://testgrid.k8s.io/sig-release-master-informing#Conformance%20-%20EC2%20-%20arm64%20-%20master

### Reason for failure (if possible)

Kubernetes e2e suite: [It] [sig-network] Services should be able to change the type from ExternalName to NodePort [Conformance] expand_less	2m9s
```
{ failed [FAILED] service is not reachable within 2m0s timeout on endpoint 172.31.0.12:32411 over TCP protocol
In [It] at: k8s.io/kubernetes/test/e2e/network/service.go:1463 @ 01/14/25 19:11:58.851
}
```
Kubernetes e2e suite: [It] [sig-network] Services should be able to create a functioning NodePort service [Conformance] expand_less	2m10s
```
{ failed [FAILED] service is not reachable within 2m0s timeout on endpoint 172.31.0.12:31225 over TCP protocol
In [It] at: k8s.io/kubernetes/test/e2e/network/service.go:1278 @ 01/14/25 19:53:46.5
}
```
Kubernetes e2e suite: [It] [sig-network] Services should be able to switch session affinity for NodePort service [LinuxOnly] [Conformance] expand_less	2m12s
```
{ failed [FAILED] service is not reachable within 2m0s timeout on endpoint 172.31.0.12:30190 over TCP protocol
In [It] at: k8s.io/kubernetes/test/e2e/network/service.go:4265 @ 01/14/25 20:18:35.329
}
```
Kubernetes e2e suite: [It] [sig-network] Services should have session affinity work for NodePort service [LinuxOnly] [Conformance] expand_less	2m12s
```
{ failed [FAILED] service is not reachable within 2m0s timeout on endpoint 172.31.0.12:32080 over TCP protocol
In [It] at: k8s.io/kubernetes/test/e2e/network/service.go:4265 @ 01/14/25 20:31:55.907
}
```

### Anything else we need to know?

N/A

### Relevant SIG(s)

/sig network
Repository: next.js
Issue: Error: The Edge Function "middleware" size is 1.02 MB and your plan size limit is 1 MB.
Labels: Middleware

### Link to the code that reproduces this issue

https://github.com/Olgoetz/CraftTech

### To Reproduce

Deploy the project on Vercel.


### Current vs. Expected behavior

Building this project on Vercel results in

Error: The Edge Function "middleware" size is 1.02 MB and your plan size limit is 1 MB. Learn More: https://vercel.link/edge-function-size

altough this function is far below 1 MB according to the build logs (see screenshot)

<img width="1093" alt="Image" src="https://github.com/user-attachments/assets/482fc43d-ba7b-4927-9d3c-c3cfa2eb4be9" />

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:16:46 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T8112
  Available memory (MB): 8192
  Available CPU cores: 8
Binaries:
  Node: 20.18.1
  npm: 10.8.2
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 15.1.4 // Latest available version is detected (15.1.4).
  eslint-config-next: 15.1.4
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A
```

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

Developer Experience, Middleware

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

Vercel (Deployed)

### Additional context

_No response_
Repository: next.js
Issue: next v15 with turbo causes "params should be awaited" error without params usage but with icon.svg file and slug in root path in app router
Labels: Internationalization (i18n),Turbopack

### Link to the code that reproduces this issue

https://github.com/Cielquan/nextjs-params-async-turbo-issue

### To Reproduce

1. Clone repo
1. Install dependencies e.g. `pnpm i`
1. Run the `dev` script e.g. `pnpm dev`
1. Goto http://localhost:3000/de-DE/app and see icon in tab and no error in console
1. Stop `dev` script
1. Run `dev` script with `--turbo` e.g. `pnpm dev --turbo`
1. Goto http://localhost:3000/de-DE/app and see icon in tab and now error in console:
    ```
    Error: Route "/[locale]/app" used `params.locale`. `params` should be awaited before using its properties. Learn more: https://nextjs.org/docs/messages/sync-dynamic-apis
        at tree.children.children.metadata.icon (.next/server/chunks/ssr/c488b_next_dist_esm_build_templates_app-page_3dcdb1.js:71:376)
        at Array.map (<anonymous>)
    ```
1. Delete `src/app/[locale]/app/icon.svg` file
1. Goto http://localhost:3000/de-DE/app and see icon in tab and no error in console

### Current vs. Expected behavior

### Current

`icon.svg` somehow causes an error where `params.locale` is used but not awaited, even so my code does not use `params` at all anywhere.

### Expected

`icon.svg` should not causes the error.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #49~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Wed Nov  6 17:42:15 UTC 2
  Available memory (MB): 15994
  Available CPU cores: 4
Binaries:
  Node: 20.12.1
  npm: 10.5.0
  Yarn: 1.22.19
  pnpm: 9.11.0
Relevant Packages:
  next: 15.1.4 // Latest available version is detected (15.1.4).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A
```

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

Turbopack, Internationalization (i18n)

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

next dev (local)

### Additional context

_No response_
Repository: ollama
Issue: Segmentation fault
Labels: bug,needs more info

### What is the issue?

Dear Ollama Team,
I encountered an issue while attempting to run the 'ollama service' command after installation. Here are the detailed steps I followed and the error message I received:
1. I downloaded the 'ollama-linux-amd64.tgz' file from your official source because my research network has some access limitations.
2. I unzipped the file to the path '/usr/local/bin/ollama'.
3. When I executed the command 'ollama service', I encountered a 'Segmentation fault' error.
I would appreciate it if you could look into this issue and provide any possible solutions or workarounds. Thank you for your attention to this matter.

Best regards

### OS

Linux

### GPU

Nvidia

### CPU

_No response_

### Ollama version

_No response_
Repository: pytorch
Issue: Connection Limitation in PyTorch Distributed (Vanilla) with c10d Rendezvous Backend
Labels: oncall: distributed

### 🐛 Describe the bug

Hello PyTorch team,

I am encountering an issue while using PyTorch Distributed Vanilla with the c10d rendezvous backend. I am currently running PyTorch version 2.5.1.

When trying to establish connections across multiple nodes, I can only manage up to 75 simultaneous connections. The plan was to test with 128, 256, and 512 nodes, but I can't exceed this 75-connection limit.

The following error occurs when attempting to establish more connections:


```shell
Traceback (most recent call last):
  File "/projects/I20240002/alicia.oliveira/arm_dist_env/lib/python3.10/site-packages/torch/distributed/elastic/multiprocessing/errors/__init__.py", line 355, in wrapper
  ...
    raise RendezvousConnectionError(
torch.distributed.elastic.rendezvous.api.RendezvousConnectionError: The connection to the C10d store has failed. See inner exception for details.
```
I am running the setup on an x86 architecture with InfiniBand. I would like to know if this is a known limitation of the c10d rendezvous backend or if there are any configurations or adjustments I can make to allow more connections.

Thank you in advance for your help!


### Versions

PyTorch version: 2.5.1
Rendezvous backend: c10d
Architecture: x86
Network: InfiniBand

cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o
Repository: PowerToys
Issue: Find and Replace feature
Labels: Needs-Triage

### Description of the new feature / enhancement

I would like to request the addition of a Find and Replace feature in PowerToys. This utility would allow users to search for specific text or patterns within files and optionally replace them, streamlining workflows involving repetitive text edits across multiple documents.

### Scenario when this would be used?

Developers or writers editing configuration files, codebases, or text documents.
Professionals who need to update file content in bulk (e.g., replacing outdated terms or correcting common typos).
Anyone looking to efficiently search and modify text in multiple files or within a specific directory.
Every one is doing there work online or browser if this feature implement that will be great for every one

### Supporting information

A flexible Find and Replace tool can be inspired by existing solutions like Notepad++ or Visual Studio Code.
Features like regex (regular expression) support, file filtering by type, and case sensitivity toggles would greatly enhance its functionality.
Integrating this feature into PowerToys would provide users with a powerful utility that complements existing tools like FancyZones and PowerToys Run, making PowerToys an even more comprehensive productivity suite.
Repository: godot
Issue: Visual profiler "16.66 ms" graph rendering out of bounds
Labels: bug,topic:editor

### Tested versions

reproducible in 4.4.dev7;    4.3 stable (v4.3.stable.official [77dcf97d8]); probably in all of 4.x

### System information

Windows 7, 4.4dev7, Compatabillity. GPU: GeForce 540M

### Issue description

Visual bug where the measurement of "16.67 ms" in Visual Profiler goes out of windows bounds and renders on the 3d preview window, as seen in the screenshot.

![Image](https://github.com/user-attachments/assets/c3ee62ff-4ab7-44f8-b445-452b22db2588)

### Steps to reproduce

Start any scene, open Visual Profiler, start Profiling, stop Profiling, turn of "fit to frame", observe the bug.

### Minimal reproduction project (MRP)

"N/A"

not really needed
Repository: godot
Issue: Closing documentation selects random script
Labels: bug,topic:editor,usability

### Tested versions

v4.4.beta.custom_build [4ce466d7f]

### System information

Fedora Linux 40 (KDE Plasma) on Wayland - Wayland display driver, Single-window

### Issue description

Opening a documentation by ctrl clicking in a script and then closing the documentation with ctrl+w then selects a random script

https://github.com/user-attachments/assets/99d26238-076a-4099-99fb-208f9d457705


### Steps to reproduce

^

### Minimal reproduction project (MRP)

[doc.zip](https://github.com/user-attachments/files/18423536/doc.zip)
Repository: vscode
Issue: Test Explorer Test Item
Labels: info-needed,under-discussion

<!-- ⚠️⚠️ 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. -->

Hi Team,

I would like to know is there any way by which we can access the Test item which gets displayed in Test explorer VS code using vs code api.
I want to bind some kind of event to Parent Test item which is shown in Test explorer.


I can see on right click there are some menus assigned to it and they perform some function like Go to test and hide test.

Looking out for same approach on click.

Any help is appreciated.
Repository: material-ui
Issue: [material-ui][Tabs] Out of a sudden broken with esm.sh
Labels: external dependency,component: tabs,package: material-ui

### Steps to reproduce

Steps:
1. Open this link to live example: https://stackblitz.com/edit/stackblitz-starters-a4bz6g3w?file=index.html
2. see that neither Tabs nor TabList is rendered at all


### Current behavior

there are even no dom elements, and also nothing rendered

![Image](https://github.com/user-attachments/assets/cc11042e-12bc-48e0-983c-5937028ca732)

### Expected behavior

I would like to see tabs in one way or another

### Context

This error happens precisely after clearing cache of my browser (I still had an old cache from yesterday on my firefox and when deleting it, I get the same error while before it was all good). It is really today Wednesday 15. January that it broke.

I tried several different versions of mui and the same error occurs everywhere. From 5.16.14 to 6.4.0 (EDIT: I was previously running on 6.1.10 where I stilled had the working cache mentioned below)

### Your environment

https://stackblitz.com/edit/stackblitz-starters-a4bz6g3w?file=index.html

using firefox and brave

**Search keywords**: tabs
Repository: pytorch
Issue: torch.nn.functional.scaled_dot_product_attention is_causal fails for kv-cache case (sequential and further parallel attention)
Labels: triaged,module: sdpa

### 🚀 The feature, motivation and pitch

**Behaviour found for torch version 2.2.2**

It would be great if scaled_dot_product_attention could be (easily) used for the case of sequential token generation when a kv-cache is present. However, currently when is_causal is set and a single query vector is put in, the function only compares against the earliest k and v resulting in repeatedly producing the same vector in sequential token generation.

More generally, in cases where further parallel attention is required - even when already a kv-cache has been generated - I found the correct attention matrix difficult to generate. The code I converged to is
`mask = torch.tril(torch.ones(w, w, dtype=torch.bool))[-h:, :]`
with 
w = sequence length of KV-cache
h = sequence length of queries
since a lower-triangular attention mask is required which is all-true for the case of a single query vector.

Is this indeed the intended way to use scaled_dot_product_attention or am I doing something dumb?

### Alternatives

for is_causal=True, I propose to use the attention mask generated by the code above (plus some unsqueezing for broadcasting).

### Additional context

Behaviour found for torch version 2.2.2
Repository: kubernetes
Issue: kube-proxy --cleanup issues
Labels: sig/network,triage/accepted

1. We don't actually document `kube-proxy --cleanup` anywhere.
2. It could probably do a _slightly_ better job than it actually does (eg, https://github.com/kubernetes/kubeadm/issues/3133#issuecomment-2592104802)
Repository: next.js
Issue: Client-side navigation error with rewrites and catch-all routes
Labels: Middleware,Navigation,Pages Router

### Link to the code that reproduces this issue

repository: https://github.com/klaasman/nextjs-rewrite-catchall-conflict

preview deployment: https://nextjs-rewrite-catchall-conflict.vercel.app/

### To Reproduce

A routing precedence issue arises when URL rewrites conflict with catch-all routes during client-side navigation, but only when middleware exists AND the catch-all route has `fallback: false` AND the resource served by the proxied host returns a 2xx response.

To reproduce, either  [clone the repository](https://github.com/klaasman/nextjs-rewrite-catchall-conflict) and run it, or open the preview deployment at https://nextjs-rewrite-catchall-conflict.vercel.app, or follow the steps below:

1. Create a Next.js project (using pages-router, didn't test with app router)
2. Add a `middleware.ts` file (can be an empty function).
2. Add a catch-all route file `pages/[...segments].tsx` where `getStaticPaths` is configured with `fallback: false`.
3. Set up `next.config.js` rewrite rule to proxy incoming requests (using `fallback` rewrites)
4. Ensure the proxied endpoint (e.g., httpstat.us/200) returns a 2xx status code.
5. Navigate to `/200` using client-side navigation (via Link component).



### Current vs. Expected behavior

**Current behavior:**

During client-side navigation, the catch-all route takes precedence over the configured rewrite when the proxied endpoint returns a 2xx response. This results in incorrect routing behavior. (see [preview-deployment](https://nextjs-rewrite-catchall-conflict.vercel.app/))

**Expected behavior:**

The client-side navigation should follow the rewrite rule, correctly routing to the proxied endpoint regardless of the 2xx response. The catch-all route should not interfere with the rewrite when the endpoint returns a successful response.


### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 22.12.0
  npm: 10.9.0
  Yarn: 1.22.19
  pnpm: 9.14.2
Relevant Packages:
  next: 15.2.0-canary.11 // Latest available version is detected (15.2.0-canary.11).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A
```

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

Middleware, Pages Router, Navigation

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

next dev (local), next start (local), Vercel (Deployed)

### Additional context

_No response_
Repository: ollama
Issue: most powerful model with 4m context MiniMax-Text-01
Labels: model request

https://huggingface.co/MiniMaxAI/MiniMax-Text-01
https://x.com/MiniMax__AI/status/1879226391352549451