sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: electron
Issue: Backdrop filters no longer function/apply between View's
Labels: platform/windows,platform/linux,bug :beetle:,has-repro-gist,34-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

34.0.0

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

Other Linux

### Operating System Version

6.12.8

### What arch are you using?

x64

### Last Known Working Electron version

34.0.0-beta.3

### Expected Behavior

If 2 views or more are on top of each other, and the top one has a backdrop filter or similar, then the view below it should be taken into account, as shown in a screenshot from pre-v34.0.0:

![Image](https://github.com/user-attachments/assets/c4ebf3ca-2ee8-47fe-bb2f-bb16cf4aa993)

### Actual Behavior

The backdrop filter does not take the view below it into account, as shown in a screenshot post-v34.0.0 (happens on latest nightly as well):

![Image](https://github.com/user-attachments/assets/dbf6e8a6-9de8-4ce2-8186-eb860c660a9a)

### Testcase Gist URL

https://gist.github.com/KiruPoruno/7ba1d4ba3fbf2f4f1878a335801f75f7

### Additional Information

From my testing this started happening after v34.0.0-beta.3, didn't test nightly versions for more specificity, but hope that info helps.
Repository: deno
Issue: Support sending OTEL data over a unix socket or printed to stdout.
Labels: otel

It would be nice to be able to your the collected opentelemetry data to either STDOUT or a unix socket. Might be helpful with local development, or in certain contexts where it would be helpful to skip the networking stack.
Repository: vscode
Issue: fallo
Labels: info-needed


Type: <b>Bug</b>

crear nuevo perfil

VS Code version: Code 1.96.2 (fabdb6a30b49f79a7aba0f2ad9df9b399473380f, 2024-12-19T10:22:47.216Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|12th Gen Intel(R) Core(TM) i7-1255U (12 x 2611)|
|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<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|15.64GB (4.75GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (24)</summary>

Extension|Author (truncated)|Version
---|---|---
ng-template|Ang|19.0.3
vscode-eslint|dba|3.0.10
EditorConfig|Edi|0.16.4
prettier-vscode|esb|11.0.0
svg|joc|1.5.4
vscode-language-pack-es|MS-|1.96.2024121109
sqltools|mtx|0.28.3
reload|nat|0.0.7
java|red|1.38.0
vscode-xml|red|0.27.2
errorlens|use|3.22.0
intellicode-api-usage-examples|Vis|0.2.9
vscodeintellicode|Vis|1.3.2
vscode-boot-dev-pack|vmw|0.2.1
vscode-spring-boot|vmw|1.59.0
vscode-gradle|vsc|3.16.4
vscode-java-debug|vsc|0.58.1
vscode-java-dependency|vsc|0.24.1
vscode-java-pack|vsc|0.29.0
vscode-java-test|vsc|0.43.0
vscode-maven|vsc|0.44.0
vscode-spring-boot-dashboard|vsc|0.14.0
vscode-spring-initializr|vsc|0.11.2
console-ninja|Wal|1.0.377

(1 theme extensions excluded)

</details>
<!-- generated by issue reporter -->
Repository: neovim
Issue: boolean in vim.lsp.Config to determine if a language server should be enabled.
Labels: enhancement,lsp

### Problem

I'd like to disable some language servers based on what the path / cwd is. For example, I don't want to run [harper-ls](https://github.com/Automattic/harper) if the path is outside of my development paths. eg: Don't run on public cloned trees.

I was thinking something like a `enabled = function(...):boolean` or similar. I'm aware that I can have this logic around where I call `vim.lsp.enable()`, but having it in the LS definition table feels cleaner.

I can create a PR if this is a feature that would be accepted. Thanks.

Related: https://github.com/neovim/neovim/issues/31762

### Expected behavior

Have the ability to enable/disable a language server from the `vim.lsp.Config` table.
Repository: svelte
Issue: Wrong "Unused CSS selector" in slotted content
Labels: css

### Describe the bug

CSS `:has` selector is incorrectly reported as unused in slotted content.

### Reproduction

[https://svelte.dev/playground/f4f152811664414b927a42289c904a52?version=5.18.0](https://svelte.dev/playground/f4f152811664414b927a42289c904a52?version=5.18.0)

### Logs

```shell

```

### System Info

```shell
System:                                              
    OS: Windows 11 10.0.22631                          
    CPU: (16) x64 13th Gen Intel(R) Core(TM) i5-1350P  
    Memory: 15.85 GB / 31.69 GB                        
  Binaries:                                            
    Node: 20.11.0 - C:\Program Files\nodejs\node.EXE   
    npm: 10.2.5 - C:\Program Files\nodejs\npm.CMD      
    pnpm: 9.15.2 - ~\AppData\Local\pnpm\pnpm.CMD       
  Browsers:                                            
    Internet Explorer: 11.0.22621.3527                 
  npmPackages:                                         
    svelte: ^5.18.0 => 5.18.0
```

### Severity

blocking an upgrade
Repository: pytorch
Issue: [dynamo] Model `__dict__` with `ConstDictVariable` rather than `GetAttrVariable`
Labels: triaged,oncall: pt2,module: dynamo

This tracks (1) from https://github.com/pytorch/pytorch/pull/144419#pullrequestreview-2541259169.

It'll lead to removal of duplicated logic for dictionary object handling below, and make it easier to reason about `__dict__` in general.
https://github.com/pytorch/pytorch/blob/d85ae4be734cfd53f5b893240894381ac65fe8b4/torch/_dynamo/variables/misc.py#L1027-L1074

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames
Repository: pytorch
Issue: [dynamo] Support mutation on type objects
Labels: triaged,oncall: pt2,module: dynamo

This tracks (2) from https://github.com/pytorch/pytorch/pull/144419#issuecomment-2583533712.

Repro:
```python
@torch.compile(backend="eager", fullgraph=True)
def f(x):
    Foo.a = 1
    return x + 1

f(torch.ones(1))
#  File ".../torch/_dynamo/symbolic_convert.py", line 1843, in STORE_ATTR
#    BuiltinVariable(setattr).call_function(
#  File ".../torch/_dynamo/variables/builtin.py", line 1003, in call_function
#    return handler(tx, args, kwargs)
#           ^^^^^^^^^^^^^^^^^^^^^^^^^
#  File ".../torch/_dynamo/variables/builtin.py", line 845, in builtin_dispatch
#    unimplemented(error_msg)
#  File ".../torch/_dynamo/exc.py", line 356, in unimplemented
#    raise Unsupported(msg, case_name=case_name)
#torch._dynamo.exc.Unsupported: builtin: setattr [<class 'torch._dynamo.variables.user_defined.UserDefinedClassVariable'>, <class 'torch._dynamo.variables.constant.ConstantVariable'>, <class 'torch._dynamo.variables.constant.ConstantVariable'>] False
```

We _might_ also want to support mutation on `__dict__` object as a result, although that could be subsumed by #144873.

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames
Repository: vscode
Issue: Terminal suggest: support absolute paths well on Windows
Labels: feature-request,windows,terminal-suggest

Some test cases:

- `cd |` should show `C:\`, `D:\`, etc., whatever drives are available
- `cd C:\|` should show dirs in `C:\` with same prefix (eg. `C:\Windows`)
- `cd :|` should show all drives (should get for free with first test case)
Repository: pytorch
Issue: [Monitoring] Display on HUD the information about runners that failed to be created (which cause jobs to queue)
Labels: module: ci,triaged

## Context
When job queuing for a significant period of time, it'll usually be for one of the following reasons:
- The desired machine is out of stock. We'll retry creating that instance until it becomes available
- There's a bug preventing that runner type from coming online, or perhaps even being provisioned
- Some other AWS issue that prevented the runner from being provisioned

## The Ask
This has two parts: Data Export and Visualization

### Data Export
Update the autoscaler lambdas to export the following data to ClickHouse:
- When instances are provisioned successfully
- When instances fail to get provisioned, along with their error codes
- Number of instances currently being retried

### Visualization
Add a new charts to HUD to show the number of runners of each type that have been provisioned, the number that failed (along with the reason), and the number currently waiting to be retried.

This could end up looking similar to the internal charts we have at https://fburl.com/unidash/z3wfjdwv.

Why do we need new charts if similar data is already available internally? Because the internal charts cannot capture stats about the LF fleet, and we want to be able to track service health across both the Meta and LF fleets.

cc @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: kubernetes
Issue: Document why kernel tunable `kernel/panic` needs to be set to 10
Labels: sig/node,kind/feature,sig/docs,needs-triage

### What would you like to be added?

Running kubelet on a system without this tunable is unsupported and causes kubelet to terminate. It's fine to set this and be done with it, but I can't figure out why?

Looking through the code/github, it seems that this pull request from @brendandburns first added this sysctl and requirement:
https://github.com/kubernetes/kubernetes/pull/17202/
```
[Refactor an interface for style](https://github.com/kubernetes/kubernetes/pull/17202/commits/fb576f30c8381aa30067e261c5af37adbcdfc3df)
```

Nothing in the commit or PR seems to indicate why this was added, and I don't seem to find anything in the project since that explains why this is enforced. Is there something relevant to `kubelet` that happens in that timeframe?

### Why is this needed?

Hard requirement of specific kernel configuration, but nothing apparent in the project seems to explain why.
Repository: rust
Issue: Type inference failure: Unable to infer closure parameter type
Labels: C-discussion

I tried this code:

```rust
fn test_map_err() {
    let mut m = None;
    let a: i32;
    let c = m.map_or(a, |v| v.min(a));
}
```

I expected to see this happen: 
The compiler should be able to infer the type of the closure parameter v and compile the code successfully.

Instead, this happened:
The compiler failed to infer the type and produced the following error:

![Image](https://github.com/user-attachments/assets/7d9e1606-4ba4-4f04-9322-8da70ec19244)

### Meta

> i have already try nightly version compiler, and meet the same behavior

`rustc --version --verbose`:
```
rustc 1.84.0 (9fc6b4312 2025-01-07)
binary: rustc
commit-hash: 9fc6b43126469e3858e2fe86cafb4f0fd5068869
commit-date: 2025-01-07
host: x86_64-unknown-linux-gnu
release: 1.84.0
LLVM version: 19.1.5
```
Repository: vscode
Issue: Terminal suggest: Handle paths on git bash
Labels: feature-request,windows,terminal-shell-git-bash

Git Bash uses special paths that map to Windows ones and then strictly uses the `/` separator:

![Image](https://github.com/user-attachments/assets/77f844a4-0dc8-4d40-ac8c-2afb133487b2)

We should support these well.
Repository: rust
Issue: Single use lifetimes lint suggests using unstable feature on stable
Labels: A-lints,A-diagnostics,T-compiler,L-false-positive

### Code

[playground link](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=c63ad1a23efb14d71f23d0255132631c)

```Rust
#[allow(dead_code)]
#[warn(single_use_lifetimes)]
fn foo<'a>(_items: impl IntoIterator<Item = &'a i64>) -> Vec<f64> {
    vec![]
}
```

### Current output

```Shell
warning: lifetime parameter `'a` only used once
 --> src/lib.rs:3:8
  |
3 | fn foo<'a>(_items: impl IntoIterator<Item = &'a i64>) -> Vec<f64> {
  |        ^^ this lifetime...                   -- ...is used only here
  |
note: the lint level is defined here
 --> src/lib.rs:2:8
  |
2 | #[warn(single_use_lifetimes)]
  |        ^^^^^^^^^^^^^^^^^^^^
help: elide the single-use lifetime
  |
3 - fn foo<'a>(_items: impl IntoIterator<Item = &'a i64>) -> Vec<f64> {
3 + fn foo(_items: impl IntoIterator<Item = &i64>) -> Vec<f64> {
```

### Desired output

```Shell
No warning
```

### Rationale and extra context

The feature required to elide the single use lifetime is unstable


### Rust Version

```Shell
$ rustc --version --verbose
rustc 1.84.0 (9fc6b4312 2025-01-07)
binary: rustc
commit-hash: 9fc6b43126469e3858e2fe86cafb4f0fd5068869
commit-date: 2025-01-07
host: x86_64-unknown-linux-gnu
release: 1.84.0
LLVM version: 19.1.5
```

and

```
$ rustc --version --verbose
rustc 1.82.0 (f6e511eec 2024-10-15)
binary: rustc
commit-hash: f6e511eec7342f59a25f7c0534f1dbea00d01b14
commit-date: 2024-10-15
host: x86_64-unknown-linux-gnu
release: 1.82.0
LLVM version: 19.1.1
```
Repository: next.js
Issue: Parallel routes do not apply individual `loading.tsx` when used with nested routes
Labels: Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://codesandbox.io/p/github/jrhackett/app-router-test/main?import=true

### To Reproduce

1. Start application in CodeSandbox
2. Click on "Broken subpath example" link
3. Note that the loading state for the "Slot" is showing "Loading Dashboard..." and not "Loading Slot..."

### Current vs. Expected behavior

The linked application in CodeSandbox has an example application with a route for `/broken/sub` that has a layout defined to display a parallel route called `@slot` and the `children` of the layout. The slot and the nested path both have their own `loading.tsx` files. The file structure is:

<img width="122" alt="Image" src="https://github.com/user-attachments/assets/09800db8-14c0-4fdb-8b62-fdf6e98ff12c" />

### **Current behavior**

The nested path's `loading.tsx` gets applied as expected but the slot's does not. The slot, instead, gets the parent directory's (`dashboard`) `loading.tsx` file.

<img width="542" alt="Image" src="https://github.com/user-attachments/assets/cf8ae6a4-be78-4536-a4df-ecee97b170cc" />

### **Expected behavior**

The loading state for `@slot` should display `Loading Slot...` instead of `Loading Dashboard...`.

 


### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.12.1
  npm: 10.5.0
  Yarn: 1.22.19
  pnpm: 8.15.6
Relevant Packages:
  next: 15.1.4 // Latest available version is detected (15.1.4).
  eslint-config-next: 15.1.4
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A
```

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

Parallel & Intercepting Routes

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

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

### Additional context

I've also tested this against `next@v14.2.23` and the behavior is the same.
Repository: pytorch
Issue: FlexAttention Compilation Uses Non-Standard Invocation Of Inductor Ops
Labels: triaged,oncall: pt2,module: inductor,module: higher order operators,module: pt2-dispatcher,module: flex attention

### 🐛 Describe the bug

`Modification Wrapper` uses a non-standard way of invoking inductor operators. 

In https://github.com/pytorch/pytorch/blob/d065e8a9de7d6b91bd18286bf45e5094f1278f9f/torch/_inductor/select_algorithm.py#L623-L634 

it passes string arguments to `subgraph.data.inner_fn(())` instead of `CSEVariable`. This makes the typing incorrect throughout codegen, and prevents relying on the properties of CSEVariable. I recently adding tracking of Dtypes to every intermediary in inductor codegen and enabled tests in opinfos. I would like to rely on them in codegen bc it enables:

- [Deletion of 7 ops from the inductor opset](https://github.com/pytorch/pytorch/blob/069419569d01c168952dc80bcc61bcb81a2bf3de/torch/_inductor/ops_handler.py#L719-L744)

- [Some codegen cleanups](https://github.com/pytorch/pytorch/blob/069419569d01c168952dc80bcc61bcb81a2bf3de/torch/_inductor/codegen/triton.py#L1374)


Dtype tracking is also being used today for both MTIA for low-precision, and prologue fusion low-precision (neither of which interaction with flex attention today).

I suspect this is also related to this error: https://github.com/pytorch/pytorch/issues/144869

When this is fixed we should be able to remove this special casing https://github.com/pytorch/pytorch/blob/069419569d01c168952dc80bcc61bcb81a2bf3de/torch/_inductor/dtype_propagation.py#L69.

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @aakhundov @zou3519 @ydwu4 @bdhirsh @Chillee @drisspg @yanboliang @BoyuanFeng 

### Versions

on master
Repository: godot
Issue: Incorrect behaviour using `draw_list_begin_for_screen`
Labels: bug,topic:rendering

### Tested versions

- v4.4.dev.custom_build [1fa1f5c75]
- v4.4.dev7.official [46c8f8c5c]

### System information

Godot v4.4.dev (1fa1f5c75) - macOS Sequoia (15.2.0) - Multi-window, 2 monitors - Metal (Forward+) - integrated Apple M1 Max (Apple7) - Apple M1 Max (10 threads)

### Issue description

The `draw_list_begin_for_screen` API renders to the previous frame buffer. The symptoms are most visible when targeting Metal, as the previous frame buffer is unavailable, so the logs are filled with errors.

The issue is

1. The script calls `draw_list_begin_for_screen`, which finds the frame buffer for the screen:

https://github.com/godotengine/godot/blob/62ea2f76b46ff825ecf4f497aa0a2eaac6c88da9/servers/rendering/rendering_device.cpp#L4210

2. when Godot blits the render targets to the screen, it calls `screen_prepare_for_drawing`:

https://github.com/godotengine/godot/blob/e88e30c273fe7e8eb2e5eab13098132efdebc0f3/servers/rendering/renderer_rd/renderer_compositor_rd.cpp#L39-L40

which happens _after_ any calls made by GDScript, and this call erases that frame buffer to acquire the next:

https://github.com/godotengine/godot/blob/62ea2f76b46ff825ecf4f497aa0a2eaac6c88da9/servers/rendering/rendering_device.cpp#L4094-L4095

So the call to `draw_list_begin_for_screen` in GDScript is targeting the prior, invalid frame buffer.

### Steps to reproduce

Run one of the example projects, which uses the `draw_list_begin_for_screen` API.

### Minimal reproduction project (MRP)

- https://github.com/thimenesup/GodotIndirectDrawExample 
- https://github.com/thimenesup/GodotBufferAddressExample
Repository: godot
Issue: Light behaves unexpectedly when using a screen-space material
Labels: bug,topic:rendering,confirmed

### Tested versions

- Reproducible on v4.3.stable.mono.official [77dcf97d8]

### System information

Godot v4.3.stable.mono - EndeavourOS #1 SMP PREEMPT_DYNAMIC Fri, 27 Dec 2024 14:24:37 +0000 - Wayland - Vulkan (Forward+) - dedicated AMD Radeon RX 7800 XT (RADV NAVI32) - AMD Ryzen 5 3600 6-Core Processor (12 Threads)

### Issue description

When assigning the albedo as the screen color for a mesh through the "Next Pass" or "Material Overlay" properties, it causes light to behave weirdly with the Forward+ renderer. In the case of regular lights, it seems to intensify the attenuation of the light while darkening non-lit parts (it's a bit hard to tell exactly what happens). For negative lights, it causes sufficiently bright spots to "wrap around" into being fully lit (white) rather than dark.

Worth noting is that with the Compatibility renderer, the issue is not present for negative lights (regular lights still exhibit very similar "intensifying").

No shader, regular lights:
![Image](https://github.com/user-attachments/assets/680e7cd1-15a0-4c80-b697-5e4acb792cd4)

Shader present, regular lights:
![Image](https://github.com/user-attachments/assets/522dcb57-8502-4fb9-8f17-364bf63092db)

No shader, negative lights:
![Image](https://github.com/user-attachments/assets/19e8dd9c-5842-4467-b2ec-b2ac7f571690)

Shader present, negative lights:
![Image](https://github.com/user-attachments/assets/7f28b1bb-1ec2-41ee-9b39-b94a23a5699b)

While the shader code is in the MRP, I'll paste it here since it's so tiny:
```glsl
shader_type spatial;

uniform sampler2D SCREEN_TEXTURE: hint_screen_texture, filter_linear;

void fragment() {
	vec3 screen_color = textureLod(SCREEN_TEXTURE, SCREEN_UV, 0.0).rgb;
	ALBEDO = screen_color;
}
```

### Steps to reproduce

1. Add a shader that assigns the screen color to albedo as the Material Overlay or Next pass of any mesh
2. Add some lights
3. Observe unexpected light behavior

### Minimal reproduction project (MRP)

[light-screen-texture-demo.zip](https://github.com/user-attachments/files/18428830/light-screen-texture-demo.zip)
Repository: PowerToys
Issue: dashboard keeps popping up
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

General

### Steps to reproduce

just started powertoys manually.  after a while the full powertoys dashboard window pops up on my screen. close it with x.  after a while it pops up again. rinse & repeat.

i might have interacted with the quick access & more panels

### ✔️ Expected Behavior

dashboard should never pop up

### ❌ Actual Behavior

dashboard keeps popping up

### Other Software

_No response_