sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: svelte
Issue: append_styles(...) --> Cannot read properties of null (reading 'querySelector')
Labels: awaiting submitter

### Describe the bug

I get some random `Cannot read properties of null (reading 'querySelector')` pointing to the function `apend_styles(anchor, css)` in `css.js`.

```
css.js:20 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
    at Array.<anonymous> (￼css.js:20:15)
    at run_all (￼utils.js:44:8)
    at process_micro_tasks (￼task.js:21:2)
```

### Reproduction

I am afraid I did not manage to reproduce this outside my app, and the part it occurs in is something rather special (recursive and dynamic components). But it seems to occur if the `svelte:component` changes to another component.

### Logs

```shell
css.js:20 Uncaught TypeError: Cannot read properties of null (reading 'querySelector')
    at Array.<anonymous> (css.js:20:15)
    at run_all (utils.js:44:8)
    at process_micro_tasks (task.js:21:2)
(anonymous)	@	css.js:20
run_all	@	utils.js:44
process_micro_tasks	@	task.js:21
```


### System Info

```shell
System:
    OS: Linux 6.12 Void
    CPU: (12) x64 AMD Ryzen 5 3600X 6-Core Processor
    Memory: 47.80 GB / 62.73 GB
    Container: Yes
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.16.0 - /usr/bin/node
    Yarn: 1.22.19 - /usr/bin/yarn
    npm: 10.8.1 - /usr/bin/npm
    pnpm: 9.14.2 - /usr/bin/pnpm
  Browsers:
    Brave Browser: 121.1.62.153
    Chromium: 131.0.6778.85
  npmPackages:
    svelte: ^5.10.1 => 5.17.1
```


### Severity

Prevents upgrade to Svelte 5
Repository: vscode
Issue: Close running code tabs through a single place / button
Labels: feature-request,workbench-tabs

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

### Close button which closes the running tabs through a single location

- Why do we need it? sometime the tab size is different and we opened for ex 17 tabs
- so for closing them we frustratedly click on the close button expecting all tabs will be closed.
- but no, here the anger issue raises.
- if there is a button separately to close all tabs one after another when that same button clicked, then it will be a awesome feature
- please add this feature  😟😞

### here how it is looks like

https://github.com/user-attachments/assets/e5a56b3d-4508-45a9-b3ce-51548314766e

### here how it should be from notepad++

https://github.com/user-attachments/assets/b78906b7-66ea-43de-a361-ec0452603d13
Repository: vscode
Issue: Quick input - explore changes to border/shadow/backdrop/overlay
Labels: quick-pick,under-discussion

Here is a screenshot where it is difficult to "focus visually" on the quick input. Things that we could explore:
1. Tweak the border/shadow of the widget so that it stands out
2. Use a backdrop/overlay to dim the workbench behind the input

<img width="1826" alt="Image" src="https://github.com/user-attachments/assets/51728468-ee9b-42c1-bfc9-ab96de6f853a" />
Repository: vscode
Issue: Language model not available
Labels: triage-needed,stale


Type: <b>Bug</b>

I just subscribed to Copilot but cannot use it in VS Code. It just says "language model not available"

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

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

|Item|Value|
|---|---|
|CPUs|11th Gen Intel(R) Core(TM) i5-1145G7 @ 2.60GHz (8 x 1498)|
|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.73GB (2.79GB free)|
|Process Argv|--crash-reporter-id 604e9176-5864-4f53-a1d6-01b94bcdd7f0|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (14)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-openapi|42C|4.31.0
pascal-formatter|ale|2.9.0
ng-template|Ang|19.0.3
pascal-language-basics|Ans|0.1.12
vscode-intelephense-client|bme|1.12.6
openedge-abl|chr|1.3.0
xml|Dot|2.5.1
framework7|ETT|0.0.3
vscode-docker|ms-|1.29.3
csharp|ms-|2.55.29
vscode-dotnet-runtime|ms-|2.2.3
remote-containers|ms-|0.394.0
remote-wsl|ms-|0.88.5
vscode-yaml|red|1.15.0


</details>
<!-- generated by issue reporter -->
Repository: PowerToys
Issue: could you add slope calculation in ruler section?
Labels: Needs-Triage

### Description of the new feature / enhancement

could you add slope calculation in ruler section?

### Scenario when this would be used?

na

### Supporting information

na
Repository: ui
Issue: [bug]: Disabled Slider is Not Styled or Supported by Label Properly
Labels: bug

### Describe the bug

The `Slider` Component carries incorrect TailwindCSS classes to support the @radix-ui/react-slider implementation, because the implementation (correctly) doesn't utilize a `disabled` attribute (those are only available to INPUTs, not SPANs, as implemented).

The Slider generator currently uses `disabled:` TailwindoCSS classes which fail to match because the disabled attribute isn't utilized. Rather, it should be using `aria-disabled:` classes on the `SliderPrimitive.Root`, as the root element is flagged with `aria-disabled="true"`. If the Slider handle is intended to be targeted (`disabled:pointer-events-none`), the `SliderPrimitive.Thumb` should instead carry the `data-[disabled]:pointer-events-none` TailwindCSS class, as that element uses `data-disabled`.

Additionally, the `Label` Component fails to recognize and visually represent the disabled state of Slider, because of the lack of `disabled` attribute. I don't have a great suggestion here. Ideally, the `Label` would be extended to included a `peer-aria-disabled`, but that becomes based on DOM positioning and the Slider carrying a `peer` class which cannot be assumed. 🫤

### Affected component/components

Slider

### How to reproduce

1. Generate a new Slider component
2. Add the Slider component to a page
3. Disable the Slider component
4. Note there is no visual differentiation between disabled or enabled, the cursor doesn't change, and pointer events still trigger.

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
N/A
```


### System Info

```bash
N/A
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: react-native
Issue: Archive broken on Xcode 16 for React Native 0.75
Labels: Needs: Author Feedback,Needs: Repro

### Description

I have a production app built with react native that has the iOS Archive broken after an upgrade. This is a bare React Native project (not an expo project). I upgraded the following:

    react-native version to 0.75.4
    Xcode to v16

So I'm not really sure which of those upgrades are causing the problem.

Running the app in debug mode works ok, however when archiving (in order to publish a new version of the app) it throws the error: 'EMFILE too many files open' and looking the full logs I see that comes from Metro. That confuses me because as far as I know metro should not be running as part of the archive process, but this is fired from the react native scripts.

Any ideas?

I have tried to fix that Metro error by removing the line -reset-cache from react-native-xcode.sh and now it breaks in a different place. But I don't think touching the react native scripts is the way to go


### Steps to reproduce

1. build archive
2.install ipa on iphone
3. app is crashing on launchscreen

### React Native Version

0.75.4

### Affected Platforms

Runtime - iOS, Build - MacOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 15.1.1
  CPU: (8) arm64 Apple M2
  Memory: 104.44 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 21.7.1
    path: /usr/local/bin/node
  Yarn: Not Found
  npm:
    version: 10.8.1
    path: /usr/local/bin/npm
  Watchman:
    version: 2024.03.25.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/raghunaik/.rubies/ruby-2.6.10/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.1
      - iOS 18.1
      - macOS 15.1
      - tvOS 18.1
      - visionOS 2.1
      - watchOS 11.1
  Android SDK: Not Found
IDEs:
  Android Studio: 2024.2 AI-242.23339.11.2421.12550806
  Xcode:
    version: 16.1/16B40
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.10
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /Users/raghunaik/.rubies/ruby-2.6.10/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.4
    wanted: 0.75.4
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false
```
Repository: deno
Issue: Deno allow-read doesn't work for / (root directory) if a deny-read parameter is set.
Labels: bug,node compat

Version: Deno 2.1.5 (also tested on 1.44.4, 1.46.4, 2.1.2)
OS: MacOS 15.2 (also tested on linux)

When allow-read is used in combination with deny-read, it doesn't allow access to the root directory.

## Test file

```ts
import * as fs from "node:fs";

console.log(fs.statSync("/tmp").mtime);
console.log(fs.statSync("/").mtime);
```

## Expected output
`$ deno run --allow-read access.ts`

```
2025-01-10T03:19:51.822Z
2024-12-07T08:11:55.000Z
```

## Output with bug

`$ deno run --allow-read --deny-read=/mnt access.ts`

```
2025-01-10T03:19:51.822Z
error: Uncaught (in promise) NotCapable: Requires read access to "/", run again with the --allow-read flag
console.log(fs.statSync("/").mtime);
               ^
    at Object.statSync (ext:deno_fs/30_fs.js:415:3)
    at Module.statSync (ext:deno_node/_fs/_fs_stat.ts:163:25)
    at file:///Users/matheusgr/access.ts:4:16
```

Setting allow-read to root directory also fails.

---

We caught this issue due to the last browserslist update (4.24.4) . It may stat the root directory and fail due to some deny-read configuration that we use.
Repository: kubernetes
Issue: vishvananda Netlink breaking changes in 1.2.1
Labels: priority/important-soon,sig/network,triage/accepted

The vishvananda netlink library had a behavior change in 1.2.1 , see https://github.com/vishvananda/netlink/pull/1018 for more details

> Before https://github.com/vishvananda/netlink/pull/925 (in v1.2.1), the flag was ignored and results were returned without an error. With that change, response handling is aborted, results are discarded, and unix.EINTR is returned.

We are impacted by that change https://github.com/kubernetes/kubernetes/blob/fc7520b32f1287b867377aaee89412482199d14a/go.mod#L63 

In order to recover the previous behavior and being more resilient to partial results we should adopt a similar solution to the one adopted by moby developers, wrapping the library to retry a few times

We need to implement something like https://github.com/moby/moby/pull/48407/commits/00bf437d84ac1aec5ce24ffc5f1b7dbb6309263b#diff-28da2a9c14d97c7755152d3ad995389ceda8cc7655c8e03e2874b6d44f977ec1

We also should have some way of linting to avoid adding new netlink calls that are susceptible to get interrupted without the wrapper

/sig network
/priority important-soon
Repository: flutter
Issue: [Proposal] TableView: add  jump to/scroll to a specified item
Labels: c: new feature,f: scrolling,package,c: proposal,P3,team-framework,triaged-framework,p: two_dimensional_scrollables

### Use case

Can the tableView be enhanced with a feature that allows it to jump to/scroll to a specified row and column when given the row index and column index?

### Proposal

jump to/scroll to
Repository: PowerToys
Issue: Advanced Past causes issues with larger clipboard content on remote desktop
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Advanced Paste

### Steps to reproduce

- Having advanced paste active on host machine
- Open remote desktop session (e.g. AVD)
- Use the snipping tool to copy a larger area of the desktop into the clipboard (probably any other way to have some larger content in the clipboard would work as well)
- try to type using the keyboard

### ✔️ Expected Behavior

Keyboard input to work normally.

### ❌ Actual Behavior

Keyboard input is extremely erratic, almost doesn't work anymore until clipboard is cleaned again.

### Other Software

_No response_
Repository: godot
Issue: Baking LightmapGI with shadowmasks can crash Godot after transparency support was added
Labels: bug,topic:rendering,crash,regression,topic:3d

### Tested versions

-Reproducible in latest master v4.4.dev.gh [24d74510e]

### System information

Windows 10 - Godot 4.4dev - Vulkan (Foward+) - Nvidea 1070

### Issue description

Trying to bake the LightmapGI with shadowmasks can get stuck and crash Godot in some circunstances.

Using the latest master (v4.4.dev.gh [24d74510e]) and trying to bake the lightmapGI using the testproject from (https://github.com/godotengine/godot/pull/85653#issuecomment-2447529657) crashes Godot.
With a lot of "Couldn't map PC to fn name" errors.

https://github.com/user-attachments/assets/852e65f9-1f42-476e-928f-f004ba76c92c

Here is the start of the crash:
(On Windows 10, Foward+, Nvidea 1070)

![shadowmask](https://github.com/user-attachments/assets/62311593-d235-4e54-86a3-1cfcd4b08b4e)

It appears this started happening since adding transparency support to the lightmapGI (https://github.com/godotengine/godot/pull/99538)

As found out by https://github.com/godotengine/godot/pull/85653#issuecomment-2581660852
> @Geometror EDIT: Tested some some PR's and is crashing since #99538 (Transparency PR). Something broke between Dec 12 and Dec 19.
> 
> EDIT2: It seems like if I insist and try again it manage to bake, but taking double the time and the computer becomes unresponsive in the process.



### Steps to reproduce

I didn't figure out the MRP yet, but you can 
use the test project from https://github.com/godotengine/godot/pull/85653#issuecomment-2447529657
(Used to work until the transparency to GI was added)
([direct download link](https://github.com/user-attachments/files/17580558/shadowmask_test_2.zip))

- Try to bake the LIghtmapGI

Expected: LightmapGI baked
Results: Goes until about 50% then Godot gets stuck and crashes.

### Minimal reproduction project (MRP)

Use the test project from https://github.com/godotengine/godot/pull/85653#issuecomment-2447529657
([direct download link](https://github.com/user-attachments/files/17580558/shadowmask_test_2.zip))
Repository: flutter
Issue: [google_maps_flutter][web] Support clickableIcons flag
Labels: c: new feature,p: maps,platform-web,package,c: proposal,team-web

### Use case

As a developer I want to hide the default info window which appears when clicking on a POI


<img width="660" alt="Screenshot 2025-01-10 at 15 13 38" src="https://github.com/user-attachments/assets/fb396db0-510a-4890-b804-093a35f7443f" />


### Proposal

While going through the source files of google_maps_flutter_web I can see that the extension type MapOptions includes this boolean clickableIcons which is used by the JS API for the purpose of hiding this info windows.

```dart
extension type MapOptions._(JSObject _) implements JSObject {
  external MapOptions({
    String? backgroundColor,
    bool? cameraControl,
    CameraControlOptions? cameraControlOptions,
    LatLngOrLatLngLiteral? center,
    bool? clickableIcons,
    JSAny? /*(ColorScheme|string)?*/ colorScheme,
    num? controlSize,
    bool? disableDefaultUI,
    bool? disableDoubleClickZoom, ...) }
```  

But there is no way to set this option via the GoogleMap widget. I think it would be nice to have an extra variable for this purpose. Something like: 

```dart
GoogleMap(clickableIcons: false, ...)
```
Repository: vscode
Issue: Add keybindings to chat edit actions, help dialog
Labels: feature-request,accessibility

The following should have default keybindings to aid screen reader users and keyboard only users and be included in the a11y help dialog:

- Undo Last Edit (proposed `ctrlCmd+z`)
- Redo Last Edit (proposed `ctrlCmd+shift+z`)
- Clear Working Set (proposed `ctrlCmd+k`)
- Save All (proposed `alt+ctrlCmd+s`)
- View All Edits (proposed `ctrlCmd+e`)
- Add files (proposed `ctrlCmd+a`)
- Switch to Chat (already has keybinding)
- New Edit Session (already has keybinding)

cc @joyceerhl, @jrieken, @jooyoungseo, @rperez030 for feedback
Repository: next.js
Issue: CSS Module Hot Reloading Issue in Next.js Dev Mode
Labels: CSS

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/unruffled-rui-xqj4ys
### Issue Description:
I encountered an issue with CSS modules in my Next.js project when working in development mode. When I modify CSS properties in a CSS module and save the file, the styles do not update as expected in the browser. Instead, the following error is thrown in the console:
```
Error: No link element found for chunk static/chunks/src_components_fb4138._.css
    at http://localhost:3000/_next/static/chunks/_d95469._.js:1595:28
    ...

```
### To Reproduce 

1- Create a component that imports a CSS module:
`import styles from './drawingcanvas.module.css';
`
2- Modify any CSS property in the CSS module while running the Next.js app in development mode (next dev).
3- Observe that the styles do not update in the browser, and the following error appears in the console:
`Error: No link element found for chunk static/chunks/[...].css
`
4- Manually reload the page to apply the changes.


### Current vs. Expected behavior

Expected Behavior:
CSS modules should hot reload, and the updated styles should be reflected in the browser without requiring a manual page reload.

Actual Behavior:
CSS changes in the module do not take effect, and the browser throws an error until the page is manually reloaded.

Workaround:
I resolved this issue by moving the CSS module import from the child component (Canvas component) to its parent component. I then passed the styles object as a prop to the child component. Example:

Parent Component:
```
import styles from './drawingcanvas.module.css';

export default function ParentComponent() {
  return <CanvasComponent styles={styles} />;
}
```

Child Component:
```
export default function CanvasComponent({ styles }) {
  return <div className={styles.canvasContainer}>Canvas</div>;
}

```
This workaround fixed the issue, and the CSS changes hot-reloaded correctly in development mode. However, this introduces extra coupling between components and may not be an ideal solution.


### Provide environment information

```bash
Next.js version: 15.1.4
Node.js version: 20.17.0.
Browser: arc browser version 1.36.1 with chromium engine 131.0.6778.265
OS: windows 11 21h2 build 22000.556
```


### Which area(s) are affected? (Select all that apply)

Not sure, Developer Experience

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_
Repository: PowerToys
Issue: Move AltGR functions to Left Alt key
Labels: Needs-Triage

### Description of the new feature / enhancement

Example: To write the @ character I need to hold AltGR and press 2 on my Nordic ISO keyboard. I would rather hold <Left Alt> and press 2, but it doesn't work. 

### Scenario when this would be used?

Everyday use for characters like @£$€{[]}\ 

It would also free up a key that I can assign to something else on.

### Supporting information

_No response_
Repository: PowerToys
Issue: Snap new windows when started
Labels: Needs-Triage

### Description of the new feature / enhancement

As soon as a new app window is launched, snap it to a zone in the active screen/monitor, following where the mouse cursor is.

### Scenario when this would be used?

Today we have the ability to "remember" the last position of an app when re-launched. The idea is to be capable to keep windows organized for any new launched app window, at list the main app window, to avoid having to organize manually.

### Supporting information

_No response_
Repository: terminal
Issue: WT causes the whole Windows animation to be super laggy (after RDP?), until all the WT processes are terminated
Labels: Issue-Bug,Needs-Triage,Needs-Attention

### Windows Terminal version

1.21.3231.0

### Windows build number

10.0.19045.5247

### Other Software

Command line

### Steps to reproduce

There are no concrete steps to reproduce, as the issue occurs randomly. However, I’ve noticed two recurring patterns:

1. Using RDP to access this computer often triggers the bug later when I use the computer locally (though *not always immediately*).
2. Having multiple Windows Terminal (WT) windows open for an extended period.



### Expected Behavior

It shouldn't cause Windows animation lagging issue.

### Actual Behavior

I briefly mentioned this performance issue [[in another ticket](https://github.com/microsoft/terminal/issues/17414#issuecomment-2539085553)](https://github.com/microsoft/terminal/issues/17414#issuecomment-2539085553), but I believe it deserves its own standalone discussion.

When the bug occurs, the entire Windows desktop UI becomes extremely laggy (e.g., dragging and switching windows), with performance dropping to what feels like less than 20 FPS. 3D applications like full-screen games are *not* affected; only the desktop UI.

To resolve the issue, I must close all open Windows Terminal windows (I typically keep 2–3 open at any given time). Doing so immediately restores normal performance.

The issue is not tied to any specific tab—I’ve tested this by opening a new window and then closing all existing windows, but the problem persists. 

Here’s what the processes related to WT look like before I terminate them (and fix the issue):

![Image](https://github.com/user-attachments/assets/38bebb02-6a4a-4af9-b054-387796da75a5)