sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: [PowerToys Run] - Add a Setting for VSCode Plugin to Remoe Extra information from List
Labels: Idea-Enhancement,Status-In progress,Needs-Triage,Run-Plugin

### Description of the new feature / enhancement

I use Development Container a lot while working on my projects using Docker Containers and noticed that these random Sequences appears after the name of the Directory/File

![image](https://github.com/microsoft/PowerToys/assets/54078496/eab935e4-11e0-418e-9131-5163f740caef)

My proposal is to add a setting specifically for the VS Code plugin that is a check box which would either include (Checked) or exclude (Unchecked) the extra sequence. 

Note sure about whether we want to have a default of checked/unchecked, but that can be decided after a discussion.

### Scenario when this would be used?

Not really a specific scenario that this is either useful or not useful it just feels like unnecessary information being displayed out sense most of the time the user should know which directory they are accessing via the "Project Folder in "XXXX") section under the name 

This would also setup the foundation for future settings that might be useful, such as adding for example the ability to clear out results using a button on the user interface, that can be left for a different feature/task. 

### Supporting information

_No response_
Repository: react
Issue: [DevTools Bug]: Can’t import chrome trace into react devtools
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

https://tsk9sq.csb.app/

### Repro steps

1. Go to the page and open devtools
2. Go to performance tab and start recording
3. Interact with the application
4. Stop recording
5. Download trace
6. Upload to react devtools
7. Expected - React timeline tab should display trace
8. Actual - React devtools fails to import the trace and shows an error - "e.sort is not a function. Try importing another Chrome performance profile."
![image](https://github.com/facebook/react/assets/5317985/a292d82b-36d0-4924-9e9d-1681b60fe17a)

I think its is an issue with how we are parsing the chrome trace [here](https://github.com/facebook/react/blob/e3ebcd54b98a4f8f5a9f7e63982fa75578b648ed/packages/react-devtools-timeline/src/import-worker/importFile.js#L22C1-L23C1).
Chrome outputs the trace file in the following format:
```json
{
  "traceEvents": [
    {"name": "Asub", "cat": "PERF", "ph": "B", "pid": 22630, "tid": 22630, "ts": 829},
    {"name": "Asub", "cat": "PERF", "ph": "E", "pid": 22630, "tid": 22630, "ts": 833}
  ],
  "displayTimeUnit": "ns",
  "systemTraceEvents": "SystemTraceData",
  "otherData": {
    "version": "My Application v1.0"
  },
  "stackFrames": {...}
  "samples": [...],
}
```
 
 but react devtools expects the file to contain only `traceEvents` array. 
React DevTools should be able to handle both formats because they are valid according to this document: https://docs.google.com/document/d/1CvAClvFfyA5R-PhYUmn5OOQtYMH4h6I0nSsKchNAySU/preview
 

### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: PowerToys
Issue: Clicking text in Peek disables arrow key navigation "permanently"
Labels: Issue-Bug,Needs-Triage,Product-Peek

### Microsoft PowerToys version

0.80.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Peek

### Steps to reproduce

1. Peek at something with selectable text (tested on .txt, .c, .rtf, .docx) in a folder with multiple files
2. Select or click on some of the file's text (placing a caret in the file preview) - sometimes this is unnecessary
3. Try pressing the arrow keys to move to another file

### ✔️ Expected Behavior

There should be some way to stop controlling the caret (click the title bar?) so you can go back to navigating between files.

### ❌ Actual Behavior

The arrow keys are now stuck controlling the caret/selection and can no longer navigate between files. Peek has to be closed to get that behavior back.

### Other Software

Peek is set to "always run unelevated"
Repository: angular
Issue: docs: Reactive Forms disable/enable functions are not part of the Reactive Forms guide
Labels: P3,area: docs

### Describe the problem that you experienced

Disabling a field is a common task.
However by using Reactive Forms you cannot longer rely on `disabled` attribute to disable a field: https://stackblitz.com/edit/stackblitz-starters-e5vfle

This issue does not question it.
But the only mention to enable/disable functions is in the **Strictly typed reactive forms** guide, as a link (https://stackblitz.com/edit/stackblitz-starters-e5vfle). Even here, that's just a link to the API reference, without proper explanation about the related functions to look at.

### Enter the URL of the topic with the problem

https://angular.io/guide/reactive-forms

### Describe what you were looking for in the documentation

enable/disable functions should be explained.

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

The Reactive Forms guide (https://angular.io/guide/reactive-forms) should include a section about enabling/disabling fields.

### Add a screenshot if that helps illustrate the problem

_No response_

### If this problem caused an exception or error, please paste it here

_No response_

### If the problem is browser-specific, please specify the device, OS, browser, and version

_No response_

### Provide any additional information here in as much as detail as you can

_No response_
Repository: rust
Issue: Tracking Issue for `feature(cfg_ub_checks)` and `-Zub-checks`
Labels: C-tracking-issue

The feature gate for the issue is `#![feature(cfg_ub_checks)]`

This feature allows writing code that detects if the compiler will emit UB checks, simlar to how `cfg(debug_assertions) detects if debug assertions are enabled.

We also track the `-Zub-checks` flag here; that should eventually become `-Cub-checks` similar to `-Coverflow-checks`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps

- [x] Implement feature.
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs

### Unresolved Questions


### Implementation history
https://github.com/rust-lang/rust/pull/123411
Repository: next.js
Issue: Next docs for nonce appears inaccurate; nonce behavior is inconsistent  
Labels: bug

### Link to the code that reproduces this issue

https://github.com/arackaf/next-csp-repro

### To Reproduce

npm install and run the application.

I'm using `14.2.0-canary.58`

I've implemented the behavior described [here](https://nextjs.org/docs/app/building-your-application/configuring/content-security-policy#reading-the-nonce).

Storing the nonce in an x-nonce header, and reading it in a server component, to add to a Script tag immediately jumped out at me as being non-viable. router.refresh() causes that value to change, while the original nonce value in the page's response header remains unchanged.

But in attempting to repro, I found that it works. 

Run http://localhost:3000/ 
Click the button to call router.refresh()
Click the link to go to page 2
(it turns out you don't even need the router.refresh() call - middleware sets a new x-nonce header value just by navigating, even though the layout doesn't invalidate and re-run, to show the new value in my demo)

The script is still added (causing a message to show on the screen), no csp errors show, and all is well.

Even more crazy is that you can remove the nonce from the Script component, or even *pass an incorrect nonce* and it **still** works

Change <Script to <script in renderScript.tsx, and repeat to confirm that it does indeed fail, as it should (so CSP is indeed configured)

It feels like someone realized the x-nonce header value would not be stable, modified the Script component to always use the correct nonce in the csp header, but forgot to update the docs? Can someone confirm this?

Unfortunately if you go back to the Next Script component, and set `strategy="beforeInteractive"` then it never works. Ever. Oddly, there's no CSP error, just a hydration warning, but it never works.

To be more specific, with `strategy="beforeInteractive"` refreshing on page2 (which should always work) never works, nor does browsing from page1, using the incorrect nonce.

So, the nonce behavior I'm seeing is that afterInteractive forcibly always uses the correct nonce (good!) while beforeInteractive never works under any circumstances. 

### Current vs. Expected behavior

See above 

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:28:58 PST 2023; root:xnu-10002.81.5~7/RELEASE_X86_64
  Available memory (MB): 16384
  Available CPU cores: 16
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.15
  pnpm: 6.11.0
Relevant Packages:
  next: 14.2.0-canary.58 // Latest available version is detected (14.2.0-canary.58).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.4
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local)

### Additional context

See above
Repository: godot
Issue: Bug of render scenes 3D in Mode Compatibility
Labels: bug,platform:windows,topic:rendering,topic:thirdparty,needs testing,topic:3d

### Tested versions

Godot 4.3 Dev5 , Godot 4.2.x Stable, Godot 4.1.x Stable

### System information

Win10, AMD Radeon 6570, 15.201.1151.1008, GLES3

### Issue description


https://github.com/godotengine/godot/assets/54606139/7e558438-e88f-4ba9-a037-f831cfad1c05



### Steps to reproduce

https://github.com/godotengine/godot/assets/54606139/7e558438-e88f-4ba9-a037-f831cfad1c05


### Minimal reproduction project (MRP)

N/A
Repository: vscode
Issue: Terminal is zoomed in and out to be very large or small with the mouse wheel while holding Ctrl
Labels: bug,confirmation-pending,terminal-layout

<!-- ⚠️⚠️ 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.88.0
- OS Version: win10

Steps to Reproduce:

1.  Set "terminal.integrated.mouseWheelZoom": true
2.  Open a new vscode windows, and toggle terminal
3.  Zoom in or out terminal with the mouse wheel while holding Ctrl.  terminal can be zoomed in and out to be very large or small.

https://github.com/microsoft/vscode/assets/49320365/af854838-2653-416c-9b93-47810770d0a0


This phenomenon occurs when the terminal is zoomed in and out for the first time, and the subsequent scaling is normal, with the font size increasing or decreasing by one each time
Repository: vscode
Issue: diffs are barely visible in HC light theme
Labels: bug,accessibility,diff-editor

1. set color theme to be HC light
2. make some changes in a file
3. see gutter decorations, but barely noticeable ones in the editor of different colors
4. switch themes, see the diffs

https://github.com/microsoft/vscode/assets/29464607/867fd555-d2ac-42cd-82c3-b9470df1ca13
Repository: vscode
Issue: Inline editing of debug variables
Labels: feature-request,debug

@hediet showed me his extension that has "edit variable" code lens in certain places over variables in the code while debugging. It led me to thinking that we could have an in-editor "Edit Variable" experience that would look kind of similar to the input opened during inline chat.

DAP doesn't have knowledge of variable placements, but we do have the EvaluatableExpressionProvider. In the case where inline values are turned on, they could be clickable to edit them. Additional/otherwise, this could be surfaced through an "edit" action in debug hovers. Editing a variable would open an overlaid input box, prefilled with the variables current value, and the variable would be updated in the DA once changed and submitted.
Repository: pytorch
Issue: torch._C.JitType annotation is busted
Labels: oncall: jit,module: typing

torch._C.JitType doesn't even exist! The actual thing is torch.Type. However, we cannot type torch._C.Type correctly, because we import a different `Type` in torch/_C/__init__.pyi.in...

cc @EikanWang @jgong5 @wenzhe-nrv @sanchitintel @ezyang @malfet @xuzhao9 @gramster
Repository: PowerToys
Issue: PowerRename Apply to Filename only default choice
Labels: Idea-Enhancement,Product-PowerRename,Needs-Triage

add the option to change the default "Apply to" choice from "Filename + extension" to "Filename only"
Repository: pytorch
Issue: lintrunner-noclang job may diverge from `lintrunner` locally
Labels: module: typing,module: lint,triaged

I ran `lintrunner -a` locally, but it did not catch the errors that showed up on https://github.com/pytorch/pytorch/pull/123109 

cc @ezyang @malfet @xuzhao9 @gramster
Repository: terminal
Issue: ResizeWithReflow doesn't clamp _virtualBottom if the cursor is above the viewport
Labels: Area-Output,Issue-Bug,Product-Terminal,Priority-2

### Windows Terminal version

1a6ba43

### Windows build number

_No response_

### Other Software

_No response_

### Steps to reproduce

TBA: Exact steps unclear, but it was found by @zadjii-msft in #16937 as part of reflow tests.
However, repro steps aren't quite necessary as the flaw can be clearly seen here:
https://github.com/microsoft/terminal/blob/1a6ba43dd220d4a318627006bf2a6c8b9a70c7bc/src/host/screenInfo.cpp#L1404-L1407

There's no `min()`. (Alternatively, you can just patch `Reflow()` to put the cursor at 0,0 after a reflow.)

`Terminal::UserResize` doesn't use its `newCursorPos` either.

### Expected Behavior

_No response_

### Actual Behavior

The viewport should always contain the cursor, even if the cursor is above the viewport.
Repository: PowerToys
Issue: PowerRename show checked items only under "Renamed"
Labels: Idea-Enhancement,Product-PowerRename,Needs-Triage

when you uncheck "Original" items, don't show them under "Renamed" so it's easier to see which items will be affected
Repository: PowerToys
Issue: PowerRename trim whitespace at end of filename
Labels: Idea-Enhancement,Product-PowerRename,Needs-Triage

when you rename files, if there is whitespace at the end of the file name before the extension, trim the same way as it's done with whitespace at the beginning of the file name
Repository: pytorch
Issue: Undefined behavior when an OpOverload's Library is deleted but the OpOverload continues to be used
Labels: triaged

We should raise a nice error message in this case.
Repository: PowerToys
Issue: Always On Top QOL feature
Labels: Idea-Enhancement,Product-Always On Top,Needs-Triage

### Description of the new feature / enhancement

Somewhere under the always on top settings, such as below the "excluded apps" area, it would help me greatly to see another box that reports all of the processes that are currently being affected by the app.

### Scenario when this would be used?

I always forgot to use the hotkey to UNPIN whatever process, and then suffer tons of notifications that something is being used by Always On Top. But I can't remember what the heck to open up and UNPIN. There doesn't seem to be a way to check what needs hot-keying to stop these notifications, at the moment. If there is, someone should tell Copilot, because I've just had some very frustrating runaround-type exchanges with it, to try to find this information, and it always ends up getting to a step that says something like, "Now go to the processes tab and look for the file you suspect to be affected, and blah..." It doesn't seem to understand that if I had any suspicions whatsoever, I'd have just gone there and not to the AI for help. 🤦‍♂️
Of course, I did look to see if there was an assist available that is smarter than Co-Pilot with regards to the Always On Top feature of PowerToys, but no joy. If a help line is available I didn't see it. So I came to give this suggestion, instead.

### Supporting information

I'm sure there is a way to make this info available right there on the settings page, or perhaps make the notifications reveal WHICH file you should pop up and hot-key. This sounds like a pretty fast and easy fix that would have saved me about three hours so far today, and however long it's still going to take me to find that stupid window.
Repository: excalidraw
Issue: Default pan mode
Labels: mobile

Thank you very much for this awesome plugin.
I think many (including myself) would drastically benefit from an optional default pan mode.
Currently, one is being brought back to Select mode, which is not great on mobile
Repository: rust
Issue: Compiler wants to add bound which already exists to generic.
Labels: A-diagnostics,A-trait-system,A-associated-items,T-compiler,C-bug,F-trait_alias,fixed-by-next-solver

It looks like the compiler can't unify associated types with their actual types when given a concrete type inside an `impl`. Additionally, the diagnostics are very misleading. Here's a minimum reproducible example:

```rust
#![feature(trait_alias)]

trait Something {}

trait Test<A> { type T; }

trait Alias<A, T: Test<A>> = Test<A> where T::T: Something;

trait ArgHaver { type Arg; }
impl<T> ArgHaver for T { type Arg = T; }

trait Q<A: ArgHaver> {
    fn f<X, T: Test<A::Arg>>() where X: Alias<A::Arg, T>;
}

impl<F> Q<()> for F {
    // both versions don't work
    // fn f<X, T: Test<<() as ArgHaver>::Arg>>() where X: Alias<<() as ArgHaver>::Arg, T> {}
    fn f<X, T: Test<()>>() where X: Alias<(), T> {}
}
```

I expected to see this happen: The program compiles successfully.

Instead, this happened:
```
error[E0277]: the trait bound `T: Test<()>` is not satisfied
  --> <source>:19:5
   |
19 |     fn f<X, T: Test<()>>() where X: Alias<(), T> {}
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ the trait `Test<()>` is not implemented for `T`
   |
help: consider further restricting this bound
   |
19 |     fn f<X, T: Test<()> + Test<()>>() where X: Alias<(), T> {}
   |                         ++++++++++

error[E0276]: impl has stricter requirements than trait
  --> <source>:19:16
   |
13 |     fn f<X, T: Test<A::Arg>>() where X: Alias<A::Arg, T>;
   |     ----------------------------------------------------- definition of `f` from trait
...
19 |     fn f<X, T: Test<()>>() where X: Alias<(), T> {}
   |                ^^^^^^^^ impl has extra requirement `T: Test<()>`

error[E0277]: the trait bound `X: Alias<(), T>` is not satisfied
  --> <source>:19:37
   |
19 |     fn f<X, T: Test<()>>() where X: Alias<(), T> {}
   |                                     ^^^^^^^^^^^^ the trait `Test<()>` is not implemented for `X`, which is required by `X: Alias<(), T>`
   |
   = note: required for `X` to implement `Alias<(), T>`
note: the requirement `X: Alias<(), T>` appears on the `impl`'s method `f` but not on the corresponding trait's method
  --> <source>:13:8
   |
12 | trait Q<A: ArgHaver> {
   |       - in this trait
13 |     fn f<X, T: Test<A::Arg>>() where X: Alias<A::Arg, T>;
   |        ^ this trait's method doesn't have the requirement `X: Alias<(), T>`
help: consider further restricting this bound
   |
19 |     fn f<X, T: Test<()>>() where X: Alias<(), T> + Test<()> {}
   |                                                  ++++++++++
```

### Meta
`rustc --version --verbose`:
```
rustc 1.79.0-nightly (88c2f4f5f 2024-04-02)
binary: rustc
commit-hash: 88c2f4f5f50ace5ddc7655ea311435104d3659bd
commit-date: 2024-04-02
host: x86_64-unknown-linux-gnu
release: 1.79.0-nightly
LLVM version: 18.1.2
```
Repository: kubernetes
Issue: api: v1.KubeSchedulerConfiguration Go type is not compatible with controller-gen
Labels: kind/bug,sig/scheduling,sig/api-machinery,triage/accepted

## What would you like to be added?

I am using the `kubescheduler.config.k8s.io/v1.KubeSchedulerConfiguration` type as a field in my CustomResourceDefinition. However, when I try to generate CRD manifests from the Go type for the CRD using the command I get various errors.

## Why is this needed

I'm curious if this use case is supported. It can help projects like kubeadm, [Cluster API](https://cluster-api.sigs.k8s.io/) or [Kamaji](https://kamaji.clastix.io/) accept KubeSchedulerConfiguration objects as a field to customize the provisioned cluster's kube-scheduler config differently between clusters. The only other option to do so is to either deal with `runtime.RawExtensions` or use a YAML/JSON stored as `string`.

## Errors from `controller-gen crd`

When I use the `controller-gen crd` command to generate CustomResourceDefinition manifests for a Go type that has a struct member of type KubeSchedulerConfiguration, I get errors about float types (presumably QPS/Burst) in the `componentbaseconfigv1alpha1.ClientConnectionConfiguration`:

> `
/Users/abalkan/go-athens/pkg/mod/k8s.io/component-base@v0.29.1/config/v1alpha1/types.go:79:6: found float, the usage of which is highly discouraged, as support for them varies across languages. Please consider serializing your float as string instead. If you are really sure you want to use them, re-run with crd:allowDangerousTypes=true`

And a few errors about various [[]byte fields](https://github.com/kubernetes/kube-scheduler/blob/94ff27f8b9eb26561417aa148314397395e6faef/config/v1/types.go#L385-L396) that have `+listType=atomic`:

> `/Users/abalkan/go-athens/pkg/mod/k8s.io/kube-scheduler@v0.29.1/config/v1/types.go:388:2: must apply listType to an array, found string`

> `/Users/abalkan/go-athens/pkg/mod/k8s.io/kube-scheduler@v0.29.1/config/v1/types.go:392:2: must apply listType to an array, found string`

> `/Users/abalkan/go-athens/pkg/mod/k8s.io/kube-scheduler@v0.29.1/config/v1/types.go:396:2: must apply listType to an array, found string`

/sig scheduling
/sig api-machinery
/kind bug