sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: electron
Issue: desktopCapturer crashing on linux w/XDP when the capture portal is dismissed/closed
Labels: platform/linux,bug :beetle:,32-x-y,33-x-y,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

32.0.0, 33.0.0, 34.0.0

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

Other Linux

### Operating System Version

Linux bakery 6.12.9-zen1-1-zen #1 ZEN SMP PREEMPT_DYNAMIC Fri, 10 Jan 2025 00:39:35 +0000 x86_64 GNU/Linux

### What arch are you using?

x64

### Last Known Working Electron version

31.3.1 - No crashing but cannot open another portal request. 31.4.0 & later crashes

### Expected Behavior

Doesn't crash & allows following requests

### Actual Behavior

When the user closes the portal picker electron will crash.

### Testcase Gist URL

https://www.electronjs.org/docs/latest/api/desktop-capturer the example provided is a simple repro

### Additional Information

When attempting this from chromium the same errors will be spit out but there is no crash and can make following pick attempts so I believe theyre unrelated. Other than that theres no logs.
```
[10356:10356:0114/163419.616405:ERROR:screencast_portal.cc(367)] Failed to start the screen cast session.
[10356:10356:0114/163419.616432:ERROR:base_capturer_pipewire.cc(81)] ScreenCastPortal failed: 2
```
Repository: pytorch
Issue: Something is fishy with discard_graph_changes
Labels: triaged,oncall: pt2,module: higher order operators,module: pt2-dispatcher

Discovered with @yanboliang in https://github.com/pytorch/pytorch/pull/142830#discussion_r1913437378

cc @chauhang @penguinwu @ydwu4 @bdhirsh @yf225.

What's going on is:
1) we do a discard_graph_changes
2) then we do a speculate_subgraph, which gives us some lifted_freevars

The lifted_freevars map proxies from the discard_graph_changes's subtracer INSTEAD OF the outer subtracer. This is pretty unexpected and seems like a footgun for using discard_graph_changes.

I'm not sure what to do about this right now.
Repository: pytorch
Issue: "GenericHOPVariable" / abstract out Dynamo support for HOPs
Labels: triaged,oncall: pt2,module: dynamo,module: higher order operators,module: pt2-dispatcher

From HOP sync discussion (with @xmfan).

Idea 1: abstract out Dynamo support for HOPs

Some way to create a HOP where:
1) a user defines how to construct the inputs to each subgraph from the (args, kwargs)
2) using this, we can create a GenericHOPVariable that should be able to handle FX graphs as inputs. Dynamo can always speculate_subgraph on the fx graphs using the previous function

Idea 2: Some way to tag a HOP's subgraph as being "already proven safe by Dynamo"
1) If we see it has already been tagged, then there isn't a need to speculate it again.

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames @ydwu4 @bdhirsh @yf225
Repository: next.js
Issue: `resolveSWCOptions` fails when using next.config.ts with extended tsconfig
Labels: TypeScript

### Link to the code that reproduces this issue

https://github.com/V1RE/repro-next-config-ts

### To Reproduce

1. Make your tsconfig.json extend another tsconfig
2. Remove compiler options from your main tsconfig.json
3. Use a `.ts` next config
4. Run `next dev`

### Current vs. Expected behavior

When following the steps above, [`resolveSWCOptions`](https://github.com/vercel/next.js/blob/6616e203054523961ccbc53e841f7b8877025285/packages/next/src/build/next-config-ts/transpile-config.ts#L8) throws an error, since the [parsing](https://github.com/vercel/next.js/blob/6616e203054523961ccbc53e841f7b8877025285/packages/next/src/build/next-config-ts/transpile-config.ts#L32) of the tsconfig.json file doesn't throw.

This only happens when using `next.config.ts`, .mjs and .js work as expected.

![Image](https://github.com/user-attachments/assets/2519d4a4-b03a-4072-98f5-7f32305d9490)

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.2.0: Fri Dec  6 19:03:40 PST 2024; root:xnu-11215.61.5~2/RELEASE_ARM64_T6041
  Available memory (MB): 24576
  Available CPU cores: 12
Binaries:
  Node: 23.6.0
  npm: 10.9.2
  Yarn: N/A
  pnpm: 9.15.0
Relevant Packages:
  next: 15.2.0-canary.9 // Latest available version is detected (15.2.0-canary.9).
  eslint-config-next: N/A
  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)

TypeScript, Developer Experience

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

next dev (local), next build (local)

### Additional context

_No response_
Repository: node
Issue: "What's New" section in API docs
Labels: doc,feature request

### What is the problem this feature will solve?

Finding new apis added is dificult....

### What is the feature you are proposing to solve the problem?

Since most of our documentation has "Added in" metadata now, it would be helpful if the documentation could have an automatically generated "What New In This Version" page that is automatically generated from the metadata. For folks who are looking at the docs, it is often difficult to find and identify newly added APIs.

### What alternatives have you considered?

_No response_
Repository: pytorch
Issue: Support torch.func.grad for Flex Attention
Labels: triaged,oncall: pt2,module: functorch,module: higher order operators,module: pt2-dispatcher,module: flex attention

### 🚀 The feature, motivation and pitch

Currently, flex attention does not support `torch.func.grad`:

```python
import torch

from torch.nn.attention.flex_attention import flex_attention

torch.set_default_device("cuda")

q = torch.randn(1, 1, 1, 16)
k = torch.randn(1, 1, 1, 16)
v = torch.randn(1, 1, 1, 16)

torch.func.grad(flex_attention)(q, k, v)
```

```
  File "/home/ubuntu/.local/lib/python3.10/site-packages/torch/_ops.py", line 471, in wrapper
    return self.dispatch(
  File "/home/ubuntu/.local/lib/python3.10/site-packages/torch/_ops.py", line 341, in dispatch
    return dispatch_functorch(self, args, kwargs)
  File "/home/ubuntu/.local/lib/python3.10/site-packages/torch/_functorch/pyfunctorch.py", line 294, in dispatch_functorch
    return interpreter.process(op, args, kwargs)
  File "/home/ubuntu/.local/lib/python3.10/site-packages/torch/_functorch/pyfunctorch.py", line 171, in process
    kernel = op.functorch_table[TransformType.Grad]
KeyError: <TransformType.Grad: 2>
```

### Alternatives

_No response_

### Additional context

_No response_

cc @chauhang @penguinwu @zou3519 @Chillee @samdow @kshitij12345 @ydwu4 @bdhirsh @yf225 @drisspg @yanboliang @BoyuanFeng
Repository: godot
Issue: "Snap Controls to Pixel" only partially works
Labels: bug,topic:editor,topic:2d

### Tested versions

v4.4.dev7.mono.official [46c8f8c5c]

### System information

Godot v4.4.dev7.mono - Windows 11 (build 22631) - Multi-window, 2 monitors - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 4070 Ti SUPER (NVIDIA; 32.0.15.6614) - 13th Gen Intel(R) Core(TM) i9-13900K (32 threads)

### Issue description

Snapping controls to pixels only works consistently for the position of the control, not its size.

I pasted a screenshot into Aseprite and zoomed to 25% (my game is scaled by 4x). It should look perfectly scaled, but the TextEdit and OptionButton nodes are blurry due to non-integer sizes:
![Image](https://github.com/user-attachments/assets/48fba4a4-5029-40c9-a1e1-f62788a0391f)

![Image](https://github.com/user-attachments/assets/4941a03f-97ee-4137-bf2c-dbcc03d1e71b)

Note that I had stretch mode set to CanvasItems for this screenshot (so the issue would be visible in Aseprite). Using Viewport stretching obviously renders at the correct pixel resolution, but causes other issues like the bottom row of pixels of some control nodes to occasionally be cut off.

In this screenshot, the first two control nodes have a height of 18.5, causing the bottom edge to blur. The first OptionButton has its text blurred due to the size, but the TextEdit at the top does not have this issue. The second OptionButton has a height of 19, which causes its text to render at a non-integer Y-position (9.5 offset from the top). The Position property of each node is snapped to an integer, but their sizes and internal nodes seem to ignore this.

### Steps to reproduce

In Project Settings:
- gui/common/snap_controls_to_pixels = On
- display/window/size/viewport_width = 640
- display/window/size/viewport_height = 360
- display/window/size/mode = Exclusive Fullscreen
- display/window/stretch/mode = viewport (for native pixel resolution, causes issues with rows of pixels being lost) or canvas_items (to test blurring when downscaling to viewport size)
- display/window/stretch/aspect = expand
- display/window/stretch/scale_mode = integer

### Minimal reproduction project (MRP)

N/A
Repository: flutter
Issue: [a11y] Form should have correct semantics role
Labels: framework,a: accessibility,c: proposal,P2,team-accessibility,triaged-accessibility

when using the widget https://api.flutter.dev/flutter/widgets/Form-class.html, is should have the following role

| OS | role |
|--------|--------|
| web |form |
| ios | - |
| macos |  NSAccessibilityGroupRole, AXLandmarkForm |
| windows | - |
| android | - |
Repository: flutter
Issue: [a11y] tooltip popup should have correct semantics role
Labels: framework,f: material design,a: accessibility,c: proposal,P2,team-accessibility,triaged-accessibility

When using https://api.flutter.dev/flutter/material/Tooltip-class.html, the tooltip popup (not the tooltip widget) should have following role
| OS | role |
|--------|--------|
| web | tooltip |
| ios | - |
| macos | NSAccessibilityGroupRole, AXUserInterfaceTooltip |
| windows | ROLE_SYSTEM_TOOLTIP |
| android | - |
Repository: flutter
Issue: [a11y] loading indicator should have correct semantics role
Labels: framework,f: material design,a: accessibility,c: proposal,P3,team-accessibility,triaged-accessibility

When using https://api.flutter.dev/flutter/material/CircularProgressIndicator-class.html, the loading spinner should have following role
| OS | role |
|--------|--------|
| web |- |
| ios | - |
| macos | NSAccessibilityProgressIndicatorRole |
| windows | - |
| android | - | 


When using https://api.flutter.dev/flutter/material/LinearProgressIndicator-class.html, the linear indicator should have following role
| OS | role |
|--------|--------|
| web |progressbar |
| ios | - |
| macos | NSAccessibilityLevelIndicatorRole |
| windows | ROLE_SYSTEM_PROGRESSBAR |
| android | - |
Repository: flutter
Issue: [pigeon] Support Event Channels in all supported languages
Labels: c: new feature,team-ecosystem,p: pigeon,P2,triaged-ecosystem

As of https://github.com/flutter/packages/pull/7892 Event Channel support is available in Dart, Kotlin, and Swift.

It would be nice for this feature to work on all platform/languages supported by pigeon.
Repository: angular
Issue: Event coalescing fires events too late for desired browser focus traversal and sometimes fails to fire event listeners
Labels: area: core,core: change detection,core: zoneless

### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

We have a use case where we dynamically are creating items based on previous values. In our actual application, based on certain control values, we hide or show different components. We need the tabbing to follow the order of the components with the new DOM layout. 

With `eventCoalescing` set to `false`, change detection occurs at the end of `keydown` being broadcast and the `keyup` event handler is invoked and focus is set to the new item dynamically rendered as desired.

With `eventCoalescing` set to `true`, focus is set to the wrong item due to the timing of when change detection is run. Also, the `keyup` event handler is never invoked.


### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-mfnhbni1?file=src%2Fmain.ts

### Please provide the exception or error you saw

```true
Event listener never fired
```

### Please provide the environment you discovered this bug in (run `ng version`)

```true

     _                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
 
Angular CLI: 19.0.7
Node: 18.20.3
Package Manager: npm 10.2.3
OS: linux x64

Angular: 19.0.6
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, router

Package                      Version
------------------------------------------------------
@angular-devkit/architect    0.1900.7
@angular-devkit/core         19.0.7
@angular-devkit/schematics   19.0.7
@angular/build               19.0.7
@angular/cli                 19.0.7
@schematics/angular          19.0.7
rxjs                         7.8.1
typescript                   5.6.3
zone.js                      0.15.0
```

### Anything else?

To reproduce:

1. Load stackblitz from https://stackblitz.com/edit/stackblitz-starters-mfnhbni1?file=src%2Fmain.ts
2. Put focus in the text field for `Item 1`
3. Enter any non-blank value
4. Hit tab
5. Focus is set on the `Reset` button
6. `onKeyup` method is never invoked


Then to see the desired behavior (with `eventCoalescing` off):

1. Change `providers: [provideZoneChangeDetection({ eventCoalescing: true })],` to `providers: [provideZoneChangeDetection({ eventCoalescing: false })],` (line 89)
2. Wait for page to reload
3. Put focus in the text field for `Item 1`
4. Enter any non-blank value
5. Hit tab
6. Focus is set on the `Item 2` input element
7. `onKeyup` method is fired as expected

Related issues:
- https://github.com/angular/angular/issues/57460
- https://github.com/angular/angular/issues/57528
Repository: flutter
Issue: [pigeon] Separate `PigeonOptions` api from internal usage.
Labels: team-ecosystem,p: pigeon,P2,triaged-ecosystem

There are a few issues that have been created over the past couple years due to the internal `PigeonOptions` class being used as the API surface for options for users.

There should be a new class for internal use only to avoid these issues and fix the open issues related to this.

related: https://github.com/flutter/flutter/issues/149956
Repository: rust
Issue: Crater runs for 1.85
Labels: S-waiting-on-review

Note: Please do not conduct triage on these runs without discussing how to do so with a release team member first. Thanks!
Repository: next.js
Issue: Intercepting & Parallel route on vercel is broken
Labels: Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://github.com/heecheon92/next15-test

### To Reproduce

Local Build,
1. npm i && npm run dev (or npm run start)
2. visit localhost:3000
3. visit the page -> Route Interception (or you can simply visit localhost:3000/playground/route_interception/home)
4. Visit "Progress" tab from "Home" tab. (It displays as normal page)
5. Visit "Progress" tab from "Payment" tab. (**It displays as modal**)


1. deploy the product on vercel.
2. visit the page -> Route Interception (or you can simply visit https://next15-test-gilt.vercel.app/playground/route_interception/home)
3. Visit "Progress" tab from "Home" tab. (It should display as normal page)
4. Visit "Progress" tab from "Payment" tab. (It should display as modal **but it displays as normal page**)



### Current vs. Expected behavior

In local development and production build, intercepting & parallel route behaves as expected.

In local builds, regardless of dev or prod, visiting "Progress" tab from "Payment" tab display as modal.

Once deployed to vercel, visiting "Progress" tab from "Payment" tab displays as normal page.

It should be displayed as modal just like local build.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:02:27 PDT 2024; root:xnu-11215.41.3~2/RELEASE_X86_64
  Available memory (MB): 16384
  Available CPU cores: 12
Binaries:
  Node: 20.10.0
  npm: 10.9.0
  Yarn: 1.22.21
  pnpm: 9.7.1
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.2
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)

Vercel (Deployed)

### Additional context

One weird behavior pertaining to this issue is that "prefetch" on Link component is speculatively related.

From the sample project I provided, if you explicitly set prefetch option to "false"  on Link to "Progress" tab, like this

```tsx
          <Link
            href="/playground/route_interception/progress"
            className="p-2 bg-blue-600 text-white rounded-md"
            prefetch={false}      // <-- this option
          >
            Progress
          </Link>
```

This partially fixes the issue.

In detail, when prefetch is set to false and deployed to vercel, following happens

1. Visit following pages with exact order "Home" -> "Payment" -> "Progress"
2. Progress page displays as modal just like local build
3. Close the modal, visit "Home" again and then visit "Progress"
4. Now, Progress page shows "404 page not found"

Following page is built on exactly same source code but prefetch option for the Link to Progress page is set to false.

https://next15-test-git-prefetchdisabled-heecheon92s-projects.vercel.app/playground/route_interception/home
Repository: ollama
Issue: Multi GPU, default GPU setting, specific model pin to specific GPU
Labels: feature request

I have a multi GPU configuration and they are different GPU models with different memory size.
I wish:
1. we could select default GPU for all models (potentially the fastest one with higher memory)
2. we could select specific model per specific GPU to use small models into small VRAM GPU and use fastest/highest_VRAM card for other large models.
Repository: vscode
Issue: Code Highlighting
Labels: info-needed

ADD ISSUE DESCRIPTION HERE
all of my code is white rather than different aspects of the code being highlighted

Version: 1.96.3
Commit: 91fbdddc47bc9c09064bf7acf133d22631cbf083
User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/128.0.0.0 Safari/537.36
Embedder: codespaces

<!-- generated by web issue reporter -->
Repository: electron
Issue: If nativeTheme.themeSource is set to “dark” on Windows, a white line is drawn under the menu bar.
Labels: platform/windows,bug :beetle:,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?

Windows

### Operating System Version

Windows11 24H2

### What arch are you using?

x64

### Last Known Working Electron version

33.3.1

### Expected Behavior

![Image](https://github.com/user-attachments/assets/e89bbf55-c3e7-413c-bb30-b54d78baa0e0)

### Actual Behavior

![Image](https://github.com/user-attachments/assets/3ef601fe-b5d0-41e5-bc61-0ee879109dfa)

### Testcase Gist URL

[https://gist.github.com/df43514921aa3386c054acc8721790be](https://gist.github.com/df43514921aa3386c054acc8721790be)

### Additional Information

_No response_
Repository: pytorch
Issue: [dynamo] Do not always skip code objects unconditionally
Labels: triaged,oncall: pt2,module: dynamo

Currently, when Dynamo determines that a frame should be skipped, we will also skip tracing all future calls to the same code object. This can cause issues when skipping a frame is dependent on inputs to the function:

```python
import torch

@torch.compile(dynamic=False)
def fn(x, n):
    if n == 0:
        try:
            # causes frame to be skipped
            torch._dynamo.graph_break()
        finally:
            pass
    if torch.compiler.is_compiling():
        return x + 1
    return x - 1

print(fn(torch.ones(3), 0)) # skipped
print(fn(torch.ones(3), 1)) # skipped

import torch._dynamo
torch._dynamo.reset()

print(fn(torch.ones(3), 1)) # compiled!
print(fn(torch.ones(3), 0)) # skipped

# Output:
# tensor([0., 0., 0.])
# tensor([0., 0., 0.])
# tensor([2., 2., 2.])
# tensor([0., 0., 0.])
```

We see that whether `fn(torch.ones(3), 1)` gets compiled is dependent on calling order! This makes it more difficult to understand the PT2 programming model. Thus, when skipping a frame is condition-dependent, we shouldn't skip the code object unconditionally - we should instead just skip the current frame and use guards to check if a future call should also skip/fall back to eager.

cc @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @amjames
Repository: rust
Issue: attempting to build on NetBSD/amd64 9.99.81 causes boootstrap/debug/rustc to crash with a SIGSEGV
Labels: I-crash,T-compiler,O-netbsd,T-bootstrap,C-bug,E-needs-investigation

I've been attempting to build rust from a clone done today (HEAD is 3736b85779d1db4c215b910004d7efcd7aff8408) on NetBSD/amd64 9.99.81 and I'm seeing boootstrap/debug/rustc crash with a SIGSEGV while "Building stage1 library artifacts".

```sh
./configure --set install.prefix=/usr/local --set install.sysconfdir=/usr/local/etc
```

Then because I didn't want to build LLVM I added the following line to the `[llvm]` section of the generated `./config.toml`:

```
download-ci-llvm = true
```

Running `./x.py build` results in:

```
   Compiling llvm-bitcode-linker v0.0.1 (/work/woods/m-rust/src/tools/llvm-bitcode-linker)
    Finished `release` profile [optimized] target(s) in 26.06s
Building stage1 library artifacts (x86_64-unknown-netbsd)
error: failed to run `rustc` to learn about target-specific information

Caused by:
  process didn't exit successfully: `/work/woods/m-rust/build/bootstrap/debug/rustc /work/woods/m-rust/build/bootstrap/debug/rustc - --crate-name ___ --print=file-names -Csymbol-mangling-version=legacy '--check-cfg=cfg(feature,values(any()))' -Zunstable-options '--check-cfg=cfg(bootstrap)' -Zmacro-backtrace -Csplit-debuginfo=off -Cprefer-dynamic -Zinline-mir -Zinline-mir-preserve-debug -Zmir_strip_debuginfo=locals-in-tiny-functions -Clink-args=-Wl,-z,origin '-Clink-args=-Wl,-rpath,$ORIGIN/../lib' -Cembed-bitcode=yes -Cforce-frame-pointers=yes '-Zcrate-attr=doc(html_root_url="https://doc.rust-lang.org/nightly/")' --target x86_64-unknown-netbsd --crate-type bin --crate-type rlib --crate-type dylib --crate-type cdylib --crate-type staticlib --crate-type proc-macro --print=sysroot --print=split-debuginfo --print=crate-name --print=cfg` (exit status: 254)
  --- stderr
  rustc exited with signal: 11 (SIGSEGV) (core dumped)
Build completed unsuccessfully in 0:18:05
```

GDB 11.0 can't find any symbols to give a reasonable stack backtrace from the resulting core (despite `file` reporting that the binary is "not stripped").