sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: [Accessibility]: Consider replacing audioCues.lineHasInlineSuggestion with less distruptive lower-pitch sound
Labels: feature-request,accessibility,accessibility-signal

CC @isidorn @meganrogge @AFre100 @hediet

I have turned on `audioCues.lineHasInlineSuggestion` for copilot all day long, and have found the audio cue too distruptive and felt very tired to hear the high pitch alert sound when played frequently. Just imagine that you hear the current high-pitch inline suggestion audio cues 100 times while coding.

I still  feel like the audio signal instrumental, but could you please consider implementing less distruptive (e.g., clicking) sound? The new diff inserted audio cue is a good example.
Repository: rust
Issue: nightly 1.71-2023-04-17 overflows the recursion limit
Labels: A-diagnostics,T-compiler,regression-from-stable-to-stable,C-bug,A-monomorphization

I now get this error from one of my dependent crates (rust-miniscript) when compiling with the `--release` flag

```
error[E0275]: overflow evaluating the requirement `F: FnMut<(&Pk,)>`
  |
  = help: consider increasing the recursion limit by adding a `#![recursion_limit = "256"]` attribute to your crate (`miniscript`)
  = note: required for `&mut F` to implement `FnMut<(&Pk,)>`
  = note: 128 redundant requirements hidden
  = note: required for `&mut &mut &mut &mut &mut &mut &mut &mut &mut &mut &mut &mut &mut &mut &mut &mut &mut &mut &mut &mut &mut &mut &mut ...` to implement `FnMut<(&Pk,)>`
  = note: the full type name has been written to '/home/ben/projects/mutiny-node/target/wasm32-unknown-unknown/release/deps/miniscript-e33708ffc0e16b91.long-type-8328810264563709237.txt'

```
Repository: yt-dlp
Issue: special characters ($) in outtmpl causing incorrect download locations
Labels: bug,triage

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm asking a question and **not** reporting a bug or requesting a feature
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I'm running yt-dlp version **2023.03.04** ([update instructions](https://github.com/yt-dlp/yt-dlp#update)) or later (specify commit)
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar questions **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Please make sure the question is worded well enough to be understood

```py
outputfile = '\\test\\$$$'
ydl_opts = {
            'format': 'mp3/bestaudio/best',
            'postprocessors': [{
                'key': 'FFmpegExtractAudio',
                'preferredcodec': 'mp3',
                'preferredquality': '320',#highest quality
            }],
            'ignoreerrors': True, #ignore errors
            'outtmpl': outputfile+'.%(ext)s', #save songs here .%(ext)s
            'logger': MyLogger(),
            'progress_hooks': [my_hook],
            'cookiefile': COOKIE_FILE, #cookies for downloading age restricted videos
        }
with yt_dlp.YoutubeDL(ydl_opts) as ydl:
    ydl.download(["https://www.youtube.com/watch?v=pAm1PDrfi4o&ab_channel=revenge"])
```

Sorry for my poor explanation but this is my first time asking a question here,

when using multiple "$"'s in the outtmpl of my ydl_opts, in this case: 3, the file saved after downloading is not what I expect it to be

example: 
when using 

outputfile = '\\test\\$'
the output file will be "$.mp3"

outputfile = '\\test\\$$'
the output file will be "$$.mp3"

This is where it starts to act weird:

outputfile = '\\test\\$$$'
the output file will be "$$.mp3" 

outputfile = '\\test\\$$$$'
the output file will be "$$$.mp3"

outputfile = '\\test\\$$$$$'
the output file will be "$$$.mp3"

outputfile = '\\test\\$$$$$$'
the output file will be "$$$$.mp3"

is there something I am overlooking when putting the dollar sign character in the outtmpl? if so how would I ensure that yt_dlp downloads to the location which I would expect it to
(not sure if this is a bug or a feature so i'll put it up as a question)
### Provide verbose output that clearly demonstrates the problem

- [ ] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [ ] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

_No response_
Repository: PowerToys
Issue: Replace filename with checksum
Labels: Idea-Enhancement,Product-PowerRename,Status-In progress,Needs-Triage

### Description of the new feature / enhancement

It's very common for me to receive `image.png` or `image.jpg` files lately, and I'd like a snappy way to be give them a unique name (currently, I'm facerolling my keyboard). Would it be possible for PowerRename to simply rename the file using a checksum, or some other unique value?

Unfortunately, the download modal doesn't offer to append (1) or such in windows.

### Scenario when this would be used?

endless files with the same name that need to be unique somehow.

### Supporting information

_No response_
Repository: PowerToys
Issue: Improved subpixel text rendering for OLED (WRGB stripe, RGB triangular) -- Unfixable by ClearType Tuner (Over 100 upvotes in Feedback Hub)
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

# EDIT: January 24th, 2025:

- Proposed: [Alternative PowerToy Method: "Display Shaders PowerToy"](https://github.com/microsoft/PowerToys/issues/25595#issuecomment-2571621204)
- Proposed: [Free Open Source Coding Offer to Microsoft to contribute "Display Shaders PowerToy"](https://github.com/microsoft/PowerToys/issues/25595#issuecomment-2611345767)
- Related: [Blur Busters Open Source Display Shaders v1.0.2 specifcation](https://blurbusters.com/osi#spec)
(will include WOLED/QDOLED shader)

# NOTE: I do paid work with display manufacturers. 

Repost of incorrectly-closed github item that someone else posted:

> ClearType alters anti-aliasing assuming an RGB stripe subpixel configuration. More WOLED (WRGB stripe) and QD-OLED (RGB triangular) monitors are coming to market and have noticeable chromatic aberration/color fringing on edges of text. It would be nice if Windows had a built-in option to alter text rendering based on subpixel configuration of the monitor.
> 
> ### Scenario when this would be used?
> When using a WOLED or QD-OLED monitor with WRGB stripe or RGB triangular subpixel configuration to improve text clarity.
> 
> ### Supporting information
> https://www.youtube.com/watch?v=52eiLP3Zy-s
> 
> https://youtu.be/k-6yc1dA--0?t=602
> 
> https://youtu.be/PR-1tMih0fM?t=442

It is definitely a real problem caused by unresolvable ClearType limitations.  The earlier github item (#25568) was incorrectly closed by someone who thought it was a feature already built into windows; so creating new GitHub issue.

_____

# EDIT January 24th, 2025
Repository: rust
Issue: Purge Python
Labels: T-bootstrap

Running the command: `fd --extension py -E src/llvm-project` gives a list of python files in `rust-lang/rust`:

```text
compiler/rustc_codegen_gcc/tools/check_intrinsics_duplicates.py
compiler/rustc_codegen_gcc/tools/generate_intrinsics.py
library/core/src/unicode/printable.py
src/bootstrap/bootstrap.py
src/bootstrap/bootstrap_test.py
src/bootstrap/configure.py
src/ci/cpu-usage-over-time.py
src/ci/docker/host-x86_64/test-various/uefi_qemu_test/run.py
src/ci/docker/scripts/android-sdk-manager.py
src/ci/docker/scripts/fuchsia-test-runner.py
src/ci/github-actions/calculate-job-matrix.py
src/ci/scripts/upload-build-metrics.py
src/etc/dec2flt_table.py
src/etc/gdb_load_rust_pretty_printers.py
src/etc/gdb_lookup.py
src/etc/gdb_providers.py
src/etc/generate-deriving-span-tests.py
src/etc/generate-keyword-tests.py
src/etc/htmldocck.py
src/etc/lldb_batchmode.py
src/etc/lldb_lookup.py
src/etc/lldb_providers.py
src/etc/rust_types.py
src/tools/cargo/ci/generate.py
src/tools/cargo/publish.py
src/tools/clippy/util/versions.py
src/tools/miri/ci/scrape-targets.py
src/tools/miri/test-cargo-miri/run-test.py
src/tools/publish_toolstate.py
tests/debuginfo/auxiliary/dependency-with-embedded-visualizers.py
tests/debuginfo/embedded-visualizer-point.py
tests/debuginfo/embedded-visualizer.py
tests/run-make/debugger-visualizer-dep-info/my_gdb_script.py
tests/run-make/libtest-junit/validate_junit.py
x.py
```

While there will (probably) always be a need for a little bit of Python in `bootstrap`, we should aim to replace misc scripts that really should be Written In Rust. Especially relevant are files like `src/etc/htmldocck.py` which is the `rustdoc` UI test harness(!); we should rewrite this in Rust.

Extra points:
- I wonder if CI scripts do actually need to be Python?
- Longer term, I wonder if we can require a host installation of Rust (we just download one anyway) and use that for `bootstrap`?
Repository: stable-diffusion-webui
Issue: [Bug]: log image ext should follow setting
Labels: bug-report

### Is there an existing issue for this?

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

### What happened?

![image](https://user-images.githubusercontent.com/167966/232671155-25d88e32-acbd-48fa-b474-e3dcea8c0d9f.png)



### Steps to reproduce the problem

![image](https://user-images.githubusercontent.com/167966/232671270-d050d61c-e704-4405-be05-268dd6421bd5.png)

### What should have happened?

should not create jpg

### Commit where the problem happens

803d44c4

### What platforms do you use to access the UI ?

_No response_

### What browsers do you use to access the UI ?

_No response_

### Command Line Arguments

```Shell
.
```


### List of extensions

.

### Console logs

```Shell
.
```


### Additional information

_No response_
Repository: yt-dlp
Issue: IF operator for boolean fields
Labels: enhancement,triage

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm requesting a feature unrelated to a specific site
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I'm running yt-dlp version **2023.03.04** ([update instructions](https://github.com/yt-dlp/yt-dlp#update)) or later (specify commit)
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Provide a description that is worded well enough to be understood

I don't know if it's difficult to implement, but just to put the idea out there:

# feature suggestion

It would be helpful if boolean field values (true/false) could be tested with an IF operator (either the current `&` operator or a new one).

# example
```shell
yt-dlp TSNbCSF13Zo --skip-download --no-config --print is_live
False

yt-dlp TSNbCSF13Zo --skip-download --no-config --print "%(is_live&live|notlive)s"
live    # should be "notlive" because is_live=false
``` 

# implementation
* either change the existing behaviour so that for boolean variables not the existence is checked but its true/false value, so that `boolean_variable_with_value_false&` = `false` (and not `true` as currently handled)
* or [a new operator is required](https://github.com/yt-dlp/yt-dlp/issues/6848#issuecomment-1512427900) for this
* or it could also be solved by allowing logical operations in the `________&` part, for example:
    * `%(is_live=true&live|notlive)s`
    * `%(duration<1800&short film|)s`

# use cases
* #6852
* #6300
* #6848

### Provide verbose output that clearly demonstrates the problem

- [ ] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [ ] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [ ] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

_No response_
Repository: godot
Issue: Subsurface Scattering breaks per-pixel transparency blend modes
Labels: bug,topic:rendering,topic:porting,confirmed,topic:3d

### Godot version

4.0.2

### System information

Windows 10, Vulkan / Forward+, Nvidia 2070 Super

### Issue description

Enabling Subsurface Scattering on a material causes whole scene to use additive blending instead of mix for opaque materials and additive for transparent materials

![image](https://user-images.githubusercontent.com/1384496/232685684-a85ad3fa-ffb0-43d6-ac77-2dca6c3a54ef.png)

![image](https://user-images.githubusercontent.com/1384496/232685756-0a9ea429-5199-445d-879d-9483c6f35d31.png)


### Steps to reproduce

1. Enable display/window/per_pixel_transparency/allowed in the project settings
2. Set  get_viewport().transparent_bg = true
3. DisplayServer.window_set_flag(DisplayServer.WINDOW_FLAG_TRANSPARENT, true, 0).
4. set WorldEnvironment background to Color(0,0,0,0)
5. create a mesh instance
6. add material to instance and enable SubsurfaceScattering 

### Minimal reproduction project

[transparent_test.zip](https://github.com/godotengine/godot/files/11258460/transparent_test.zip)
Repository: vscode
Issue: Reverting notebook does not restore cells as they were
Labels: bug,notebook

Steps:
* change a notebook cell
* select File > Revert

=> 🐛 cell is not restored

I was using the GH issues notebook extension:

![Recording 2023-04-18 at 09 55 08](https://user-images.githubusercontent.com/900690/232710307-87963e23-683e-4de7-9d11-036921452ff1.gif)
Repository: rust
Issue: Missing coverage for entire function with #[tracing::instrument(...)]
Labels: C-bug,A-code-coverage

I tried this code:

```rust
use tracing::warn;

#[tracing::instrument(level = "info", skip_all)]
fn fun() {
    print!("Hello World!");
}

#[cfg(test)]
mod tests {
    use crate::fun;

    fn function() {
        fun();
    }
}
```
And created a coverage report of it with:
```
RUSTFLAGS="-C instrument-coverage" cargo test
rust-profdata merge -sparse -o 1.profdata **/*.profraw
rust-cov show target/debug/deps/coverage_mini-280555d4395f82aa --instr-profile 1.profdata main.rs
```
I expected to see the function `fun` marked as covered.

Instead, it is shown as not being possible to cover:
```
    1|      1|use tracing::warn;
    2|       |
    3|      2|#[tracing::instrument(level = "info", skip_all)]
    4|       |fn fun() {
    5|       |    print!("Hello World!");
    6|       |}
    7|       |
    8|       |#[cfg(test)]
    9|       |mod tests {
   10|       |    use crate::fun;
   11|       |
   12|      1|    #[test]
   13|      1|    fn function() {
   14|      1|        fun();
   15|      1|    }
   16|       |}
```

Without the `#[tracing::instrument(...)]` it works fine:
```
    1|      1|use tracing::warn;
    2|       |
    3|      1|fn fun() {
    4|      1|    print!("Hello World!");
    5|      1|}
    6|       |
    7|       |#[cfg(test)]
    8|       |mod tests {
    9|       |    use crate::fun;
   10|       |
   11|      1|    #[test]
   12|      1|    fn function() {
   13|      1|        fun();
   14|      1|    }
   15|       |}
```

### Meta
`rustc --version --verbose`:
```
rustc 1.71.0-nightly (7908a1d65 2023-04-17)
binary: rustc
commit-hash: 7908a1d65496b88626e4b7c193c81d777005d6f3
commit-date: 2023-04-17
host: x86_64-unknown-linux-gnu
release: 1.71.0-nightly
LLVM version: 16.0.2
```
Repository: ant-design
Issue: Table filter is sluggish when it has high number of options
Labels: Inactive,⚡️ Performance,improvement

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/filter-and-sorter-antd-5-4-1-forked-n0w4j0)

### Steps to reproduce

1. Click on filter in name column.
2. Click on some check box.
3. Click OK to close filter.  - it takes 3seconds to get list of options. Also clicking checkbox for some option - takes over 1 second to have box checked. Closing filter - it takes as well around 3 seconds.

### What is expected?

1. Filter dropdown is opened with similar speed as it would be for address column
2. Checkbox is selected instantly
3. Filter dropdown id closed immediately

### What is actually happening?

1. it takes approx 3 seconds to open dropdown ( for address column it is "instant")
2. takes approx 2 seconds to have checkbox selected after clicking it.
3. it takes almost 4 seconds to close filter. After 2 seconds table is updated (filter dialog still open), then after another 1 second it jumps to new position (or flickers under FireFox) and then closes.

| Environment | Info |
| --- | --- |
| antd | 5.4.1 |
| React | 18.2.0 |
| System | Ubuntu 22.04.2 |
| Browser | Chromium 111.0.5563.146, FireFox 111.0.1, Chrome 107.0.5304.110 |

---
Flickering in point 3 was reported in https://github.com/ant-design/ant-design/issues/38442

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: godot
Issue: Shapecast2D get_collider(0) returns error if null
Labels: documentation,topic:physics

### Godot version

4.0.2 stable

### System information

Windows 10

### Issue description

When using a ShapeCast2D node with `force_shapecast_update()`, `get_collider()` is meant to return null:
![image](https://user-images.githubusercontent.com/16231628/232730651-f4fd04e9-0ae7-47e9-bd5c-19df4e67e060.png)
But it actually returns an error if checked:
![image](https://user-images.githubusercontent.com/16231628/232730724-443eee49-d4eb-4489-8ff0-297f3272e50d.png)

EDIT: I tried `shapecast_node.get_collider(shapecast_node.get_collision_count())` and that still produces an error.

### Steps to reproduce

- Add Shapecast2d node.
- Use `force_shapecast_update()` to immediately check for an overlap.
-  Check `get_collider(0)` to grab the first collider it finds.
- See the debugger error message of it being null.

### Minimal reproduction project

N/A.
Repository: godot
Issue: Label's center alignment does not use stylebox margin
Labels: bug,topic:gui

### Godot version

4.0.2.stable

### System information

Arch Linux

### Issue description

Lable's horizontal center alignment ignores stylebox margins.

Other alignment modes including vertical center alignment use stylebox margins.

In this screenshot, the background stylebox's content margin is 24, 24, 0, 0 (left, top, right, bottom). Texts in the center column should shift to the right.

![ksnip_20230418-171052](https://user-images.githubusercontent.com/372476/232730868-42676a22-7e66-4da5-a66c-55f444378ed8.png)


### Steps to reproduce

1. Create a Label, put some text, set it to center horitonally.
2. Add a stylebox to the label and set its content margin asymmetrical horizontally.

### Minimal reproduction project

[test-4.zip](https://github.com/godotengine/godot/files/11259982/test-4.zip)
Repository: next.js
Issue: Occasionally, getStaticProps failed to generate page.html and page.json
Labels: bug

### Verify canary release

- [ ] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Binaries:
      Node: 16.17.0
      npm: 8.15.0
      Yarn: 1.22.18
      pnpm: 8.1.0
    Relevant packages:
      next: 12.2.5
      eslint-config-next: 12.2.5
      react: 17.0.2
      react-dom: 17.0.2
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

_No response_

### Link to the code that reproduces this issue

It rarely appears and cannot be reproduced.

### To Reproduce

It rarely appears and cannot be reproduced.

### Describe the Bug

Occasionally, getStaticProps failed to generate page.html and page.json. At this point, other pages are successfully generated and updated (revalidate: 10). This situation can only be resolved by restarting the pod.
![image](https://user-images.githubusercontent.com/51522799/232740667-6d1e9f47-52e3-40dc-8056-ec90f6bb126e.png)

### Expected Behavior

All pages can be generated and updated successfully at all times

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: PowerToys
Issue: Quick accent characters not matching the key
Labels: Issue-Bug,Needs-Triage,Product-Quick Accent

### Microsoft PowerToys version

0.69.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Quick Accent

### Steps to reproduce

use outside text editor

### ✔️ Expected Behavior

When I am using quick accent in a text editor like word or notepad everything works fine.

### ❌ Actual Behavior


When trying to use it in a text fiel for example in a browser the suggestions are all messed up and changing every time I use the function. For example I tried the letter **O** 6 times and this was the first result: ĺÿḃñ₋̂‒

### Other Software

_No response_
Repository: rust
Issue: Bad coverage with macro_rules!
Labels: C-bug,A-code-coverage

I tried this code:

```rust
// Foo
// Foo
// Foo
// Foo
// Foo
// Foo
// Foo
// This is a simple macro named `say_hello`.
macro_rules! say_hello {
    // `()` indicates that the macro takes no argument.
    () => {
        // The macro will expand into the contents of this block.
        println!("Hello!");
    };
}

fn main() {
    // This call will expand into `println!("Hello");`
    say_hello!()
}
```
And ran: `RUSTFLAGS="-C instrument-coverage" cargo run && rust-profdata merge -sparse -o 1.profdata **/*.profraw && rust-cov show target/debug/deps/coverage_mini-280555d4395f82aa --instr-profile 1.profdata main.rs`
I expected to see say_hello be covered or uncovered, the comments should have no coverage associated.

Instead, I got this output:
```
    1|      0|// Foo
    2|       |// Foo
    3|       |// Foo
    4|       |// Foo
    5|      0|// Foo
    6|      0|// Foo
    7|      0|// Foo
    8|       |// This is a simple macro named `say_hello`.
    9|       |macro_rules! say_hello {
   10|       |    // `()` indicates that the macro takes no argument.
   11|       |    () => {
   12|       |        // The macro will expand into the contents of this block.
   13|      0|        println!("Hello!");
   14|      0|    };
   15|      0|}
   16|      0|
   17|       |fn main() {
   18|       |    // This call will expand into `println!("Hello");`
   19|       |    say_hello!()
   20|       |}
```
So it seems that the coverage information gets confused by the macro and now considers the comments as somehow executable. The main function isn't even shown as coverable anymore.

The displayed blocks make no sense as well:

![Screenshot 2023-04-18 at 11 45 22](https://user-images.githubusercontent.com/2335377/232739130-48fbbdae-630d-4ef6-9502-9a8e806b249a.png)

### Meta

`rustc --version --verbose`:
```
rustc 1.71.0-nightly (7908a1d65 2023-04-17)
binary: rustc
commit-hash: 7908a1d65496b88626e4b7c193c81d777005d6f3
commit-date: 2023-04-17
host: x86_64-unknown-linux-gnu
release: 1.71.0-nightly
LLVM version: 16.0.2
```