sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Setting a Node's clip_children property to "clip + draw" lower its texture's opacity across the entire texture
Labels: bug,topic:rendering,needs testing

### Tested versions

- Reproducible in: 4.3.beta3.official [82cedc83c]

### System information

Godot v4.3.beta3 - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 (NVIDIA; 32.0.15.5585) - Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz (8 Threads)

### Issue description

If a Node has a texture with some colors with opacity lower than 1.0, then setting the Node clip_children property to "Clip + draw" lower the opacity value of those colors.
Colors with opacity 1.0 aren't affected.
This only happens if the Node has at least one child, even if that child doesn't overlap the parent at all.

### Steps to reproduce

- Get a texture with some transparency (I edited the box' background in the Godot icon)
- Create a node and load that texture, eg. Sprite2D, TextureRect, ... 
- Create a children for that node, eg. Sprite2D
- Set the parent's clip_children property to Clip and Draw
- The texture will become more transparent.

Here is an example : 
clip_children = disabled : 
![image](https://github.com/user-attachments/assets/6093151e-8611-4aff-94da-4b408be1e000)
clip_children = clip + draw : 
![image](https://github.com/user-attachments/assets/55b7b41d-b113-4464-9c52-62222ffd5409)

You can see the transparent color becomes a lot more transparent, and the ColorRect (that isn't a child) becomes brighter as a result.

### Minimal reproduction project (MRP)

[transparency-mrp.zip](https://github.com/user-attachments/files/16353055/transparency-mrp.zip)
Repository: flutter
Issue: Avoid release builds from timing out
Labels: P1,team-release

Long-term tracking issue for https://github.com/flutter/flutter/issues/151249.

TL;DR the issue is that there is less capacity in dart-internal (which engine release builds use) than flutter prod (which engine main branch builds use), which leads to longer queue times, which leads to builds which schedule and than collect sub-builds to timeout.

To prevent this in the future, we should:

- [x] Hard-code in the top-level release builders to have longer timeouts - the repo is internal, but these are already set to timeout after 5 hours: https://dart-internal.googlesource.com/dart-internal/+/refs/heads/main/flutter-internal/engine.star#57
- [x] edit the recipes--when scheduling sub-builds and on a release branch, to use a longer timeout https://flutter-review.googlesource.com/c/recipes/+/59360
- [ ] Increase bot capacity in dart-internal
Repository: vscode
Issue: Hint default profile in label descriptions
Labels: polish,user-profiles

Testing #223080

Currently in the profiles editor, the "In use" profile is shown, but I would also expect the default profile to be shown so I can easily navigate to it vs. clicking through each individual profile
Repository: yt-dlp
Issue: Emit ConEmu-compatible ANSI escape codes when printing download progress
Labels: enhancement,core:downloader

### 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 have **updated yt-dlp to nightly or master** ([update instructions](https://github.com/yt-dlp/yt-dlp#update-channels))
- [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

By default yt-dlp is printing a colored download progress
![image](https://github.com/user-attachments/assets/662481fc-934d-48f4-932b-fc1477ecaebb)

It would be nice if along with the color ANSI codes, there were emitted [progress codes](https://learn.microsoft.com/en-us/windows/terminal/tutorials/progress-bar-sequences) as well. This would give immediate feedback on the taskbar in compatible terminal emulators even when the task is long-running and/or in the background.

This is adjacent to #8043, but will require less work I think.

### 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: rust
Issue: Confusing error around 2024 impl trait lifetime capture
Labels: A-diagnostics,T-compiler,D-confusing,A-edition-2024,F-lifetime_capture_rules_2024,I-edition-triaged

I'm finding the error message for 2024 impl trait lifetime capture a little confusing. In the following example:

```rust
#![feature(lifetime_capture_rules_2024)]

trait Trait1 {
    type Item;
}
trait Trait2<'a> {}

struct Example;

impl Trait1 for Example {
    type Item = Element;
}

struct Element;
impl<'a> Trait2<'a> for Element {}

fn foo<'a>() -> impl for<'b> Trait1<Item = impl Trait2<'a>> {
    Example
}
```

Produces the following output:

```text
error[E0657]: `impl Trait` cannot capture higher-ranked lifetime from outer `impl Trait`
  --> src/lib.rs:19:44
   |
19 | fn foo<'a>() -> impl for<'b> Trait1<Item = impl Trait2<'a>> {
   |                                            ^^^^^^^^^^^^^^^ `impl Trait` implicitly captures all lifetimes in scope
   |
note: lifetime declared here
  --> src/lib.rs:19:26
   |
19 | fn foo<'a>() -> impl for<'b> Trait1<Item = impl Trait2<'a>> {
   |                          ^^

For more information about this error, try `rustc --explain E0657`.
```

For someone that is not familiar with how impl trait capturing works, it seems confusing to understand why the compiler thinks that `impl Trait2` is trying to capture anything, since I'm not telling it to.

I'm not entirely certain what would help here, but here are some suggestions:

* Indicate the exact lifetime (and exact impl trait) in the error message, instead of using generic statements like "all lifetimes". For example, it could say: `impl Trait2 is capturing 'b`. Be concrete and short about what is happening.
* Show how to fix it (with ` + use<'a>`). I assume this is blocked on `precise_capturing`, and I'm not sure if there are intentions to do that. It would be nice if that explanation also explained to the user *why* that works ("explicitly capturing 'a indicates that the `impl Trait2` does not capture any other lifetimes"). 
* Would also be nice if it also explained *why* this is an error. Perhaps give a small hint that "use<> is required to be explicit about which lifetimes are being captured" or whatever explanation makes sense.
* Add a link to the edition-guide chapter that explains capture rules (@traviscross is currently working on these docs).


### Version

```
rustc 1.82.0-nightly (92c6c0380 2024-07-21)
binary: rustc
commit-hash: 92c6c03805408a1a261b98013304e9bbf59ee428
commit-date: 2024-07-21
host: aarch64-apple-darwin
release: 1.82.0-nightly
LLVM version: 18.1.7
```
Repository: vscode
Issue: Debug console sticky scroll is much larger than its content
Labels: bug,debug,tree-sticky-scroll

Repro:

A logged a large array when testing a proposed API and saw this:

<img width="1356" alt="Screenshot 2024-07-23 at 1 57 41 PM" src="https://github.com/user-attachments/assets/b48d4b96-567f-45aa-82fc-95c4d49082a2">

Code:

```ts
	const disposable = vscode.commands.registerCommand('test.helloWorld', async () => {
		const result = await vscode.workspace.findFiles2New(["**/*.ts"]);
		console.log(result);
	});
```
Repository: react-native
Issue: Accessibility issue - Android with TalkBack - accessibilityRole="link" is not available when user tries to navigate via links (TalkBack menu)
Labels: Issue: Author Provided Repro,Platform: Android

### Description

Used `accessibilityRole="link"` on a Pressable and it's semantics is properly announced to TalkBack.

The problem is that users can not navigate via links when they want to use "TalkBack menu" feature in the TalkBack (https://support.google.com/accessibility/android/answer/6006598?hl=en).

TalkBack menu navigate by Headings, Paragraphs, Buttons etc. seem to work fine, but links do not work.



### Steps to reproduce

Basically it drills down to this part of code:

`<Pressable style={styles.link} onPress={handlePress} accessibilityRole="link">
  <Text>{name}</Text>
  </Pressable>`

I've made a simple Expo Snack that can be used for testing: https://snack.expo.dev/HjDqJulTWJJtcolH3eHue

Expo SDK: 51.0.0
Android: 14
TalkBack version: Accessibility 15.1.00.7

### React Native Version

0.74.3

### Affected Platforms

Runtime - Android

### Output of `npx react-native info`

```text
Not Applicable
```


### Stacktrace or Logs

```text
Not Applicable
```


### Reproducer

https://snack.expo.dev/HjDqJulTWJJtcolH3eHue

### Screenshots and Videos

Please check https://youtu.be/I-KUxd3EZdc
Repository: vscode
Issue: Render Whitespace: spaces are hard to see with dark theme
Labels: bug,themes,editor-core

Whitespace characters are rendered subtly, understandably, using gray. Space characters are shown as small gray disks. With my glasses, my monitor at its default resolution and the default zoom level, I find it hard to notice them with the dark theme, in particular when they are trailing. If I know where they are, they are not hard to see, but if I don't, they are far from obvious:
![image](https://github.com/user-attachments/assets/1253e7b9-ad7d-4c7b-bce3-06558f31a66b)

I would argue this is somewhat of a bug since I perceive the contrast as greater in the normal mode than in dark mode: 
![image](https://github.com/user-attachments/assets/5dbada53-a274-4ac1-8d65-2bd4c0b70c16)

In my opinion, the perceived contrast is considerably lower in dark mode.

1. Open a file with spaces
1. Enable the Render Whitespace setting (editor.action.toggleRenderWhitespace)
1. Switch to the dark theme (workbench.action.toggleLightDarkThemes)
2. Evaluate how much time you need to identify all lines with trailing whitespace (and compare with the time needed in normal mode)

VS Code version: Code 1.91.1 (f1e16e1e6214d7c44d078b1f0607b2388f29d729, 2024-07-09T22:06:49.809Z)
OS version: Windows_NT x64 10.0.19045

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|12th Gen Intel(R) Core(TM) i7-12850HX (24 x 2419)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|63.69GB (37.04GB free)|
|Process Argv|--file-uri vscode-remote://attached-container%2B7b22636f6e7461696e65724e616d65223a222f6465762d766d2d7361672d6f732d31227d/home/user/repos/sqin-outils-dev/sqin.code-workspace|
|Screen Reader|no|
|VM|0%|
<!-- generated by issue reporter -->
Repository: vscode
Issue: Only one changed variable gets announced by screen reader
Labels: bug,accessibility

Testing #222239

1. use this script and create a launch config to launch it with node.
```
console.log('here');
let j = 0;
let i =0;
console.log('done');
```
2. Set a breakpoint on the first and last lines. Add `i` and `j` to the watch.
3. monitor the screen reading between the first and second
4. Notice that only `j=0` is announced when you go from the first to second breakpoint.
Repository: TypeScript
Issue: `'X' only refers to a type` error in JSDoc comments
Labels: Bug

### 🔎 Search Terms

- JSDoc
- only refers to a type
- `@link`

### 🕗 Version & Regression Information

5.6.0-dev.20240723

Not a regression

### ⏯ Playground Link

_No response_

### 💻 Code

When editing JSDoc comments that use `@link`, I occasionally see errors such as:

```
'TextDocument' only refers to a type, but is being used as a value here.ts(2693)
```

This seems to happen most often in larger projects, such as the VS Code codebase

As soon as I make another edit, the error goes away


Attached log shows the error showing up and then going away once an edit is made: [tsserver.log](https://github.com/user-attachments/files/16354619/tsserver.log)



### 🙁 Actual behavior

Transient errors are occasionally reported. Seems to happen most often when editing jsdoc comments

### 🙂 Expected behavior

No error. The code is valid

### Additional information about the issue

_No response_
Repository: TypeScript
Issue: Hovering @param comments duplicates the comment in the hover
Labels: Bug,Help Wanted

Testing microsoft/vscode#223154

<img width="1136" alt="Screenshot 2024-07-23 at 2 07 23 PM" src="https://github.com/user-attachments/assets/0d7b65b4-ecbc-4a3c-8937-bca3421c6d00">

<img width="771" alt="Screenshot 2024-07-23 at 2 07 57 PM" src="https://github.com/user-attachments/assets/026428f6-eb04-4bd8-9199-f4b837cd73b7">
Repository: electron
Issue: [Bug]: sleeping main process makes renderer process unresponsive, even without IPC
Labels: bug :beetle:,has-repro-gist,31-x-y

### 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 bug report that matches the one I want to file, without success.

### Electron Version

31.2.1

### What operating system(s) are you using?

macOS

### Operating System Version

macOS 14.4

### What arch are you using?

arm64 (including Apple Silicon)

### Last Known Working Electron version

_No response_

### Expected Behavior

While the main process is busy/sleeping, a renderer process is still responsive, unless it's blocked on IPC.

### Actual Behavior

While the main process is busy/sleeping, a renderer process is always completely unresponsive. For example, hover events are not registered and CSS `:hover` styles are not applied.

### Testcase Gist URL

https://gist.github.com/jameshfisher/4820da47e04481dc8f4e328f15161b81

### Additional Information

Based on [the Electron process model](https://www.electronjs.org/docs/latest/tutorial/process-model), I expected that a blocked main process would not cause unresponsiveness in a renderer process, unless that renderer process is somehow waiting on the main process.

There is no IPC happening in this app. Nothing in the docs suggests that e.g. hover events would somehow be making IPC calls to the main process.
Repository: godot
Issue: Fake corrupted file warnings (`Scene file appears to be invalid/corrupt.`)
Labels: topic:editor,needs testing

### Tested versions

4.2.2.stable

### System information

Win10, AMD Radeon 6570, 15.201.1151.1008, GLES3 Angle

### Issue description

Godot 4.2.2 keeps giving false warnings about a corrupted file, when I look at the files, they are normal, and after deleting the .godot folder and reopening Godot a few times, it starts reading the file normally again, but after a Time comes again and gives the same problem

### Steps to reproduce

Not know

### Minimal reproduction project (MRP)

N/A
Repository: vscode
Issue: Find/Replace field does not scroll to cursor position when typing a newline
Labels: editor-find,under-discussion

<!-- ⚠️⚠️ 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

<!-- 🪓 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.91.1
- OS Version: macOS Sonoma 14.5

Steps to Reproduce:

1. Open the Find or Find/Replace menu
2. Type enough to trigger horizontal overflow
3. Press `Ctrl-Enter` to type a newline

What happens: The cursor moves to a new line, but the field is not scrolled to the cursor, so the cursor is now off the viewport.

Curiously, if you paste a newline from your clipboard, this does not happen.
Repository: vscode
Issue: Cmd-Down escapes Find/Replace field
Labels: editor-find,under-discussion

<!-- ⚠️⚠️ 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

<!-- 🪓 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.91.1
- OS Version: macOS Sonoma 14.5

Steps to Reproduce:

1. Open the Find or Find/Replace menu
2. Press `Cmd-Down`

What happens: The cursor escapes the Find/Replace field and moves back to the editor
What should happen: `Cmd-Down` should navigate the cursor within the Find/Replace field
Repository: vscode
Issue: Cannot horizontally scroll Find/Replace fields
Labels: editor-find,under-discussion

<!-- ⚠️⚠️ 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

<!-- 🪓 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.91.1
- OS Version: macOS Sonoma 14.5

Steps to Reproduce:

0. Get a mouse with a horizontal scrollwheel
1. Open the Find or Find/Replace menu
2. Type enough to trigger horizontal overflow
3. Try to scroll horizontally

What happens: Absolutely nothing
Repository: vscode
Issue: Terminal suggest: Allow viewing completion detail similar to in the editor
Labels: feature-request,terminal-suggest

Testing #223130



![Image](https://github.com/user-attachments/assets/501f41d1-f50c-41e2-a87b-e4352badbf8d)

I noticed that some of the arg suggestions for `code` and `code-insiders` are quite long. I wonder if we can leverage something like what we have in settings for dropdowns. 

![Image](https://github.com/user-attachments/assets/405c00d3-c843-4e54-a2cc-9730095bbcfc)

Makes sense for us to just keep it as is, but I'm assuming that it can cut off some important info.
Repository: pytorch
Issue: Bug with capture_scalar_outputs item
Labels: actionable,bug,oncall: pt2,module: dynamic shapes,module: inductor,oncall: cpu inductor

### 🐛 Describe the bug

```
import torch
torch._dynamo.config.capture_scalar_outputs = True

@torch.compile()
def foo(x):
    return x.sum().item()

foo(torch.rand([20]))
```

> /tmp/torchinductor_eellison/fr/cfrfzajv2dejwjldopygxy72s4w2x7tsivjkz32drrkh5upoaua5.cpp:6:21: error: ‘zuf0’ was not declared in this scope
    6 |         auto tmp0 = zuf0;

### Versions

master

cc @chauhang @penguinwu @ezyang @bobrenjc93 @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @aakhundov @BoyuanFeng @anijain2305
Repository: vscode
Issue: VS Code Speech - Adjust reading rate / speed
Labels: feature-request,workbench-voice

<!-- ⚠️⚠️ 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. -->
Add a VS Code Speech extension setting for the rate that the reading aloud happens.  
I find that the reading rate is slower than I would like. 
Ideally tis would be in words per minute. 
Outlook has a slider under the under the read aloud popup settings icon that adjust the reading speed. 

As a ... user with reading disability (dyslexia) 
I want ... to set a reading speed for the VS Code Speech extension to use when reading text. The setting I want would be adjustable from 100 to 500 words per minute.  
So that ... I can be more productive when interacting with Copilot chat.
Repository: flutter
Issue: [platform view]make ad benchmark projects running on Android
Labels: platform-android,c: performance,a: platform-views,P2,team-android,triaged-android

This includes the scrolling ad banner (https://github.com/flutter/flutter/issues/143257) and the bottom anchored banner (https://github.com/flutter/flutter/issues/150230). 

These are the most common use case for ad banners. It will be helpful for us to measure the improvements and catch potential regressions. 

CC @jonahwilliams