sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Make 'status bar item' error icon more noticeable or customisable
Labels: feature-request,languages-basic,workbench-status

<!-- ⚠️⚠️ 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. -->
## Problem
The status bar item's error indicator is too hard to see, so it's very easy to miss an alert.

## Example
In this example, Prettier's own status bar implementation clearly indicates an error.  Compare it to the status bar item: the icon difference is so small that it's effectively unnoticeable, so users will miss the prompt.
![Image](https://github.com/user-attachments/assets/a36a72ef-3bbd-49d7-a810-b7d142b98b95)

## Suggestion
- Let the user/theme customise the colour when there's an error status (e.g. to red)
- Or otherwise make the error icon more noticeable

## Benefits of change
- Users able to notice errors more easily
- Hopefully encourages more uptake of status bar icon/extension standardisation
- No longer need to use a magnifying glass to see it
Repository: vscode
Issue: Highlight tabs whose file has problems, is untracked or modified compared to repo version
Labels: feature-request,workbench-tabs

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

Could you please provide a highlighting colors setting for tabs whose file is modified compared to repo version, or became untracked after a file renaming ?

I know there is a little U or M appearing on the right of file names when file is Untracked or Modified:

![Image](https://github.com/user-attachments/assets/c74bc568-d5e8-4e34-85a8-fe46b02d802a)

This is not highlighting these tabs enough imo. 
Also, if VSCode identifies problems in the file, the problem count is displayed next to the M letter, but the file name's font color changes from orange to default color.

The orange or custom color should stay, even if a problem is identified in the file.

Ability to have a different color for staged and unstaged changed files, and untracked files would be ideal, especially after a file renaming.

Thanks in advance
Mathias
Repository: vscode
Issue: Debug: Search inside collapsed nodes
Labels: feature-request,debug


Type: <b>Feature Request</b>

Would it be possible to add an option to the debug -> variables to filter/search inside collapsed notes, looking at the key & values for data buried data, this is something that's available within Pycharm so it must be possible to do ;-)

At the moment the only way to search deep inside a large dict or array of dicts is to issue a json.dumps on the console for that variable and search outside VSCode.

There is no native search inside data wranger and the export here is only CSV or parquet.

How it looks inside Pycharm:
![Image](https://github.com/user-attachments/assets/c90179d1-ee78-4188-9ed0-9136f9400049)



VS Code version: Code 1.96.0 (138f619c86f1199955d53b4166bef66ef252935c, 2024-12-11T02:29:09.626Z)
OS version: Windows_NT x64 10.0.19045
Modes:


<!-- generated by issue reporter -->
Repository: react-native
Issue: Click events do not take effect in animation views （Some Android devices, Huawei）
Labels: Platform: Android,Needs: Author Feedback,Needs: Repro,Newer Patch Available,Type: New Architecture

### Description

On some Android devices (Huawei), the buttons in the animation view cannot respond to click events normally, and you need to click many times before you can touch them occasionally.

### Steps to reproduce

1、install the application with yarn android
2、click '显示弹框'
3、click '关闭'，It takes many clicks to close

### React Native Version

0.74.1

### Affected Platforms

Runtime - Android

### Areas

Fabric - The New Renderer

### Output of `npx react-native info`

```text
System:
  OS: macOS 13.4
  CPU: (10) arm64 Apple M2 Pro
  Memory: 90.55 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.0.0
    path: /usr/local/bin/node
  Yarn:
    version: 1.22.19
    path: /usr/local/bin/yarn
  npm:
    version: 8.6.0
    path: /usr/local/bin/npm
  Watchman:
    version: 2024.01.22.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.12.1
    path: /Users/01400926/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 22.4
      - iOS 16.4
      - macOS 13.3
      - tvOS 16.4
      - watchOS 9.4
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.10671973
  Xcode:
    version: 14.3/14E222b
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 20.0.2
    path: /usr/bin/javac
  Ruby:
    version: 3.2.2
    path: /Users/01400926/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.1
    wanted: 0.74.1
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: true
iOS:
  hermesEnabled: Not found
  newArchEnabled: false
```


### Stacktrace or Logs

```text
not
```


### Reproducer

https://github.com/peaktangf/rnnotresponsedemo

### Screenshots and Videos

https://private-user-images.githubusercontent.com/14729675/370210228-5d7ec6d6-2cbd-4dbd-926d-7005db2dbf38.MOV?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzQ1MzM0MDEsIm5iZiI6MTczNDUzMzEwMSwicGF0aCI6Ii8xNDcyOTY3NS8zNzAyMTAyMjgtNWQ3ZWM2ZDYtMmNiZC00ZGJkLTkyNmQtNzAwNWRiMmRiZjM4Lk1PVj9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNDEyMTglMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjQxMjE4VDE0NDUwMVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPWZhODE5ODBmYTA2ZGJlODVkNmEzYTliYzU3ZDY4ODRkNTBhNjdhYmJkNDBhOTY5ZTQxMjlhZTkwODBlOTAwZTEmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.lgaB0R8Y_wmD0RhvjYn9vUpMtiH1EfmeV4TxVEoyLFw
Repository: rust
Issue: compiletest: debugger ignore logic papers over debugger failing to init
Labels: A-testsuite,A-debuginfo,T-compiler,T-bootstrap,E-medium,C-bug,A-compiletest

Example in https://github.com/rust-lang/rust/pull/134458#issuecomment-2551321173:

```
tests\debuginfo\issue-13213.rs ... ignored, ignored when the debugger is cdb (Fails with exit code 0xc0000135 ("the application failed to initialize properly"))
```
Repository: vscode
Issue: terminal suggest becomes buggy when the content wraps
Labels: bug,terminal-suggest

No issues occur if I make the terminal wider cc @Tyriar 

https://github.com/user-attachments/assets/5cb4c533-181e-4b23-9376-546325b7f53e
Repository: flutter
Issue: Semantics of elements are not same in listview and Column
Labels: framework,a: accessibility,has reproducible steps,P3,team-accessibility,triaged-accessibility,found in release: 3.27,found in release: 3.28

### Steps to reproduce

1. Paste in a DartPad

### Expected results

The rendering of `Column` should be the same whether it's in a `ListView` or a `Column`.

<img width="753" alt="image" src="https://github.com/user-attachments/assets/60ea1a05-91ad-4575-880a-8c67f29670f5" />

### Actual results

`Column` are rendered differently in `ListView` and `Column`.

I don't know how to explain it.
Items in the column appear merged when in a list.

<img width="753" alt="image" src="https://github.com/user-attachments/assets/7fecf0d6-1fdb-4800-83f9-5167739098d0" />


### Code sample

<details open><summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(const MyApp());
}

class MyApp extends StatelessWidget {
  const MyApp({super.key});

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      showSemanticsDebugger: true,
      home: Scaffold(
        body: SafeArea(
          child: Column(
            children: [
              SizedBox(
                height: 100,
                child: ListView(
                  children: [_MyWidget()],
                ),
              ),
              Column(
                mainAxisSize: MainAxisSize.min,
                children: [_MyWidget()],
              ),
            ],
          ),
        ),
      ),
    );
  }
}

class _MyWidget extends StatelessWidget {
  const _MyWidget();

  @override
  Widget build(BuildContext context) {
    return Column(
      children: [
        Text('Hello, World!'),
        ElevatedButton(
          onPressed: () {},
          child: Text("Button"),
        ),
      ],
    );
  }
}
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

https://pastebin.com/qWntn72P

</details>

### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Based on Dart SDK 3.7.0-243.0.dev and Flutter SDK 3.28.0-1.0.pre.104
```

</details>
Repository: rust
Issue: Incorrect suggestion to derive `Clone` on `Vec` directly
Labels: A-diagnostics,T-compiler,A-suggestion-diagnostics,D-invalid-suggestion

### Code

```Rust
pub struct NotClone {}

pub fn foo(v: &Vec<NotClone>) {
    let _v = v.clone();
}
```

### Current output

```Shell
warning: call to `.clone()` on a reference in this situation does nothing
 --> src/lib.rs:4:15
  |
4 |     let _v = v.clone();
  |               ^^^^^^^^
  |
  = note: the type `Vec<NotClone>` does not implement `Clone`, so calling `clone` on `&Vec<NotClone>` copies the reference, which does not do anything and can be removed
  = note: `#[warn(noop_method_call)]` on by default
help: remove this redundant call
  |
4 -     let _v = v.clone();
4 +     let _v = v;
  |
help: if you meant to clone `Vec<NotClone>`, implement `Clone` for it
 --> /playground/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/vec/mod.rs:397:1
  |
39+ #[derive(Clone)]
39| pub struct Vec<T, #[unstable(feature = "allocator_api", issue = "32838")] A: Allocator = Global> {
  |
```

### Desired output

```Shell
warning: call to `.clone()` on a reference in this situation does nothing
 --> src/lib.rs:4:15
  |
4 |     let _v = v.clone();
  |               ^^^^^^^^
  |
  = note: the type `Vec<NotClone>` does not implement `Clone`, so calling `clone` on `&Vec<NotClone>` copies the reference, which does not do anything and can be removed
  = note: `#[warn(noop_method_call)]` on by default
help: remove this redundant call
  |
4 -     let _v = v.clone();
4 +     let _v = v;
  |
help: if you meant to clone `Vec<NotClone>`, implement `Clone` for it
 --> /playground/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/alloc/src/vec/mod.rs:397:1
  |
1+ #[derive(Clone)]
2| pub struct NotClone {}
  |
```

### Rationale and extra context

Encountered this while investigating around #134467. Obviously the `derive` is placed at the wrong place.

### Other cases

```Rust

```

### Rust Version

```Shell
1.85.0-nightly

(2024-12-17 a4cb3c831823d9baa56c)
```

### Anything else?

_No response_

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"cyrgani"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: TypeScript
Issue: tsc looses trailing comments in the produced js files
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

"missing comments", "missing comments in .js output", "trailing comments"

### 🕗 Version & Regression Information

Happens in every version available in the playground (3.3.3 to v5.8.0-dev.20241218)

### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.7.2#code/MYGwhgzhAECC0G8CwAoa7oHpPQNYFN8AHAWggHsAnAF3wBNoJqwbUNoBbfagC3LtgAKAJSI27DMHIA7CiHwA6EOQDmggEQUa9dcIDc49AF9DWHAWJkqtBvml1URoA

### 💻 Code

```ts
class A {
    // keep-sorted start
    methodA() {
        console.log("sorted");
    }
    // keep-sorted end
}
```


### 🙁 Actual behavior

`// keep-sorted end` is missing in the .js output.

### 🙂 Expected behavior

`// keep-sorted end` is retained in the .js output.

### Additional information about the issue

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Maximum size for Inpaint "Resize to"
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 ?

When inpainting and then sending the generated image back to inpaint, the "Resize to" width and height are changed to the size of the image. This should not be a huge issue, but if the image is big and one continues inpainting without paying attention to this width and height, the automatic1111 backend crashes the computer(!). 

Using right now: version: [v1.10.1](https://github.com/AUTOMATIC1111/stable-diffusion-webui/commit/82a973c04367123ae98bd9abdf80d9eda9b910e2)  •  python: 3.10.14  •  torch: 2.1.2+cu121  •  xformers: 0.0.23.post1  •  gradio: 3.41.2  •  checkpoint: [b1689257e6](https://google.com/search?q=b1689257e6e1b2e61544b1a41fc114e7d798f68854b3f875cd52070bfe1fbc00))

Could you please point me to the code that accepts this width/height, so I do a `min(received, 1024)` in my local deployment? Thanks!

### Proposed workflow

Ideally there would be a setting, enabled by default, "Automatically limit only-masked inpaint area width and height [to prevent the computer crashing]".


### Additional information

_No response_
Repository: rust
Issue: bootstrap: retry `cargo` invocations if stderr contains a known pattern
Labels: E-hard,C-enhancement,T-bootstrap,T-infra,A-CI,A-bootstrap-config

## Why

Our CI auto builds sometimes fail for known reasons that are not related to the PRs we are trying to merge.

Most of the times, these errors are hard to understand and fix (or can't be fixed at all), decreasing the success rate of the auto builds for several weeks or months.
The impact is that we loose days of parallel compute time and hours of maintainers time that need to analyze the error message and reschedule the PRs in the merge queue.

## Feature

We want to list the the stderr of the known issues we are aware of in the `config.toml` file that bootstrap uses. These patterns can be expressed as regex.
We want `bootstrap` to retry cargo invocations up to two times if stderr matches one of the listed patterns.

This would help reduce the failure rate of our CI because it would significantly reduce the percentage of jobs failing due to spurious errors.

The error messages need to be precise enough to avoid retrying cargo invocations over genuine problems.

Known error patterns can be found [here](https://github.com/rust-lang/rust/issues/133959). Not all of them can be listed.

As a start, we could just have 1 stderr string in the list (this one doesn't need to be a regex): 

- `ranlib.exe: could not create temporary file whilst writing archive: no more archived files` which is discussed in https://github.com/rust-lang/rust/issues/108227

## Questions

- Is `config.toml` the right place to put the known stderr patterns? In Zulip, Jieyou proposed introducing another file: `retry-patterns.toml`. I'll leave it to the bootstrap team to decide.
- Which format do we use to write the stderr patterns in the `config.toml` file? For example, it can be an array of strings. It could also be an "object" if we want to customize how many times to retry per error message. I'll leave it to the boostrap team to decide.
- how do we make sure these patterns are present in the `config.toml` used for CI? I'm not familiar with how the `config.toml` for the CI is generated.

## Zulip links

- idea proposed [here](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/CI.20improvements/near/489445485)
- agreement reached [here](https://rust-lang.zulipchat.com/#narrow/channel/242791-t-infra/topic/CI.20improvements/near/489749580)
Repository: vscode
Issue: Enable disposable tracking
Labels: debt

With https://github.com/microsoft/vscode/pull/236487 I have added a disposable tracker that uses the finalization registry. The logic is that a GC'ed disposable that hasn't been disposed is a bug that we need to fix. 

This should be enabled by default when running out of dev but before that we need to mark a couple of disposables as singletons, e.g those returned from registries (menu, command, language, editors etc...)
Repository: ui
Issue: [bug]: ContextMenu fails to update location on right-click to a new location after opening
Labels: bug

### Describe the bug

### Title: ContextMenu fails to update location on right-click to a new location after opening

#### Description:

When using the `ContextMenu` component in ShadCN UI, the context menu correctly opens when right-clicking. However, if the user right-clicks again at a different location within the same container, the context menu remains at the previous location instead of updating to the new one. The position is not recalculated when the context menu is opened at a new location.

#### Steps to Reproduce:

1. Right-click anywhere in the container to open the `ContextMenu`.
2. Without closing the context menu, right-click again at a different location within the container.
3. Notice that the context menu does not update its position and remains at the previous location.

#### Expected Behavior:

When right-clicking in a new location, the context menu should update its position to the new click location and display accordingly.

#### Actual Behavior:

The context menu stays at the previous location and does not update its position.

### Affected component/components

ContextMenu

### How to reproduce

#### Steps to Reproduce:

1. Right-click anywhere in the container to open the `ContextMenu`.
2. Without closing the context menu, right-click again at a different location within the container.
3. Notice that the context menu does not update its position and remains at the previous location.

#### Expected Behavior:

When right-clicking in a new location, the context menu should update its position to the new click location and display accordingly.

#### Actual Behavior:

The context menu stays at the previous location and does not update its position.

### Codesandbox/StackBlitz link

https://v0.dev/chat/ORkigkeuMgZ

### Logs

_No response_

### System Info

```bash
Windows 11, Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: electron
Issue: Add flag to enable PipeWire Camera support
Labels: enhancement :sparkles:

### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [x] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [x] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Problem Description

Hi,

In Chrome/Chromium, it is possible to enable the PipeWire Camera support in flags:
![Image](https://github.com/user-attachments/assets/ef07a733-edf8-4bf8-a0d9-0bd36472be98)

It allows to use camera that are supported through libcamera.

### Proposed Solution


It would be great if it was possible to add such an option to electron to enable it too.

### Alternatives Considered

Not using Electron, maybe using libcamerify to execute the electron app and expose the camera as a v4l device (I haven't tested yet)

### Additional Information

I want this to be able to use https://github.com/IsmaelMartinez/teams-for-linux/ with a pipewire camera.
Repository: PowerToys
Issue: Can you add an option that only displays the New+menu when holding down Shift？🙏🙏🙏
Labels: Issue-Docs,Needs-Triage,Product-New+

### Provide a description of requested docs changes

I'm sorry for the translation software I used
I hope to add an option for the New+menu to only appear when the Shift key is pressed, as template files are not used as frequently
And when I mistakenly use a new+ template to create a new one
Because my template is quite complex
So I may create files that exceed 5G and have a quantity of over 300+
When I mistakenly created them in the HDD
That's really scary
Repository: svelte
Issue: Client errors aren't that helpful in the docs
Labels: documentation

I've managed to trigger the `Svelte error: state_unsafe_mutation` error a couple of times while migrating my app from Svelte 4 to 5. When it happens i am a little confused as to why, and when i click on the link to the client errors in the docs i get no further explanation on common use cases, how it can happen and what to do to solve it: https://svelte.dev/docs/svelte/runtime-errors#Client-errors

It would be awesome if the docs had deeper explanations on these errors, so that i could use it as a resource for fixing the bugs that occur. I would imagine that people who google these errors would be pleasantly surprised to find an explanation and solution to these errors in the docs.
Repository: rust
Issue: Unsized types in required trait methods
Labels: A-lints,T-lang,C-feature-request,needs-rfc,T-types,A-trait-objects

so this issue is a follow up for #134422 (closed as not planned) to suggest making a lint instead.
# What the issue talked about
Rust does not check for `T: Sized` in required trait methods
```rust
trait Foo {
    fn bar(self: Self, x: str);
}
```
The above code compiles, even though `Self` and `str` are both `?Sized`

this makes the trait unimplementable
```rust
impl Foo for [u8] {
    fn bar(self: Self, x: str) {}
}
```
Produces:
```shell
The size for values of type `[u8]` cannot be known at compile time
The size for values of type `str` cannot be known at compile time
```
For more information please see the [RFC]
# Meta
for anyone who cares, here is `rustc --version --verbose`
```
rustc 1.85.0-nightly (21fe748be 2024-12-11)
binary: rustc
commit-hash: 21fe748be15271ea5804e0507cd699b675efe038
commit-date: 2024-12-11
host: x86_64-unknown-linux-gnu
release: 1.85.0-nightly
LLVM version: 19.1.5
```


Here is the [RFC]

[RFC]: https://github.com/rust-lang/rfcs/pull/3745
Repository: kubernetes
Issue: Failing test: [sig-network] Services should fail health check node port if there are only terminating endpointsimage
Labels: sig/network,kind/failing-test,needs-triage

### Which jobs are failing?

https://testgrid.k8s.io/sig-node-containerd#image-validation-ubuntu-e2e

Sig network tests are failing due to issues with curl.

### Which tests are failing?

-  [sig-network] Services should fail health check node port if there are only terminating endpointsimage
-  [sig-network] Networking should check kube-proxy urls
-  [sig-network] Services should implement NodePort and HealthCheckNodePort correctly when ExternalTrafficPolicy changes

### Since when has it been failing?

Test is red as far back as it goes

### Testgrid link

https://testgrid.k8s.io/sig-node-containerd#image-validation-ubuntu-e2e

### Reason for failure (if possible)

_No response_

### Anything else we need to know?

_No response_

### Relevant SIG(s)

/sig network
Repository: ollama
Issue: falcon3:10b gives empty response sometimes
Labels: bug

### What is the issue?

Ollama 0.5.4 with falcon3:10b randomly gives empty response. The question I asked is "Why is e^(B_t-t/2) a martingale? Specifically why is it finite?". Initial debugging with help from Ollama Discord points to structured output problems.
Server log: [com.i0ntpst.ollama.log](https://github.com/user-attachments/files/18185728/com.i0ntpst.ollama.log)


### OS

macOS

### GPU

Apple

### CPU

Apple

### Ollama version

0.5.1