sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Cannot use PowerToys Run, occasional errors on login, clicking on error produces another error window
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run, General

### Steps to reproduce

[2024-10-11.txt](https://github.com/user-attachments/files/17399950/2024-10-11.txt)
[2024-10-12.txt](https://github.com/user-attachments/files/17399953/2024-10-12.txt)
[2024-10-14.txt](https://github.com/user-attachments/files/17399951/2024-10-14.txt)
[2024-10-15.txt](https://github.com/user-attachments/files/17399954/2024-10-15.txt)
[2024-10-16.txt](https://github.com/user-attachments/files/17399952/2024-10-16.txt)

Just logging into Windows 11 like usual, and also, pressing Alt+Spacebar generates an error window. Clicking on the error window generates another error (example screenshot attached).  [PowerToysReport_2024-10-16-18-59-04.zip](https://github.com/user-attachments/files/17399965/PowerToysReport_2024-10-16-18-59-04.zip)

![Image](https://github.com/user-attachments/assets/2281c2ae-5ff9-4aa6-b57e-8f6ec407d99e)

PC Specifications:
Asus TUF A17 FA706IU
AMD Ryzen 7 4800H
Nvidia GTX 1660 Ti
16 GB DDR4 RAM
256 GB WD SN520 NVMe SSD (Windows Boot Drive)
1 TB SanDisk SSD Plus SATA SSD


### ✔️ Expected Behavior

I was expecting the Powertoys Run searchbox to open without any issues whatsoever.

### ❌ Actual Behavior

An error window was generated, as shown in the example screenshot, and clicking on that error window also generates another error window.

### Other Software

_No response_
Repository: react
Issue: Bug: On mobile devices, clicking checkboxes in a list of 2 or more checkboxes will toggle the wrong one.
Labels: Status: Unconfirmed

When rendering a list of checkboxes, clicking checkboxes in sequence will sometimes trigger the wrong checkbox to be toggled. Behavior seems to be that sometimes previously clicked checkbox gets toggled instead of currently clicked checkbox.

This issue only seems to be on mobile or possibly touch devices. Could possibly be an issue with touch event listener.
This issue seems to have been introduced in React 17.0.0 as version 16.14.0 seems to work correctly.

Reopening of: #27475 

React version: 18.3.1

## Steps To Reproduce

View app on a mobile device (I'm using iPhone 15 Pro with Safari, Orion, and Firefox)
Click multiple checkboxes in sequence
Expect that correct checkbox always gets toggled, however often the previous checkbox gets toggled.

Link to code example:

Sandbox with working behavior (React 16.14.0)
https://codesandbox.io/s/react-16-checkboxes-xzzl96
https://xzzl96.csb.app/

Sandbox with broken behavior (React 18.2.0)
https://codesandbox.io/s/react-18-checkboxes-zrhpfp
https://zrhpfp.csb.app/

## The current behavior

When clicking multiple checkboxes in sequence, often the wrong checkboxes gets toggled.

## The expected behavior

The correct checkbox should be toggled when clicked.
Repository: rust
Issue: Unreachable post-monomorphization error triggered by `-C link-dead-code`
Labels: I-monomorphization,link-dead-code

I have the following code:

```rust
#![allow(dead_code)]

trait Foo {
    fn baz() {
        const { panic!() }
    }
}

impl Foo for () {}
```

If I build normally (using `cargo build`), it succeeds. If I build passing `RUSTFLAGS='-C link-dead-code'`, Rust attempts to monomorphize `Foo::baz` and fails despite `Foo::baz` never being used:

```text
error[E0080]: evaluation of `<() as Foo>::baz::{constant#0}` failed
 --> src/lib.rs:5:17
  |
5 |         const { panic!() }
  |                 ^^^^^^^^ the evaluated program panicked at 'explicit panic', src/lib.rs:5:17
  |
  = note: this error originates in the macro `$crate::panic::panic_2021` which comes from the expansion of the macro `panic` (in Nightly builds, run with -Z macro-backtrace for more info)

note: erroneous constant encountered
 --> src/lib.rs:5:9
  |
5 |         const { panic!() }
  |         ^^^^^^^^^^^^^^^^^^

note: the above error was encountered while instantiating `fn <() as Foo>::baz`
```

Post-monomorphization errors (PMEs) are often used to detect error conditions at compile time that cannot be encoded in the type system proper. We do this in zerocopy 0.8 in certain APIs to ban dynamically-sized types whose trailing element type is zero-sized.

`cargo fuzz` builds using `-C link-dead-code`, and so it has been [causing build failures for our users](https://github.com/google/zerocopy/issues/1867). In our specific case, it's possible to work around this because (for entirely coincidental reasons) the issue is only triggered by deprecated APIs that we can likely just remove. However, it's only luck that this hasn't caused more serious breakage for us.

I'm not sure what the right thing to do here is. From *our* perspective, having `-C link-dead-code` be more permissive would be good, but I understand why that might not be desirable for other users.

### Miscellaneous

Cargo version 1.81.0.
Repository: godot
Issue: `vkCmdCopyImageToBuffer` called with zero image extent on Godot XR template
Labels: bug,topic:rendering,topic:xr

### Tested versions

- Reproducible in: v4.3.stable.official.77dcf97d8

### System information

Vulkan 1.3.296 - Forward Mobile - Using Device #0: Qualcomm - Turnip Adreno (TM) 750

### Issue description

Godot when launched with the [XR template](https://github.com/GodotVR/godot-xr-template) having no modifications, ends up calling [`vkCmdCopyImageToBuffer`](https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/vkCmdCopyImageToBuffer.html) with one of the [`VkBufferImageCopy`](https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VkBufferImageCopy.html)s having an `imageExtent.width` of `0` (height/depth are both 1) which breaks [`VUID-VkBufferImageCopy-imageExtent-06659`](https://registry.khronos.org/vulkan/specs/1.3-extensions/man/html/VkBufferImageCopy.html#VUID-VkBufferImageCopy-imageExtent-06659) ("imageExtent.width must not be 0"). These problematic copies should be dropped on the Godot's end since as far as VK drivers are concerned, this is UB.

Additional Context: I'm a developer of Mesa3D Turnip (FOSS VK driver for QCOM Adreno GPUs), breaking the VK specification causes a crash on our driver and since this is an application bug it isn't something we would fix.

### Steps to reproduce

1. Download Godot XR Template v4.1.0 from Asset Store.
2. Load it up.

### Minimal reproduction project (MRP)

[Godot XR Template v4.1.0](https://godotengine.org/asset-library/asset/2280)
Repository: react-native
Issue: Inconsistent text wrap behavior when opening/closing accordion rows
Labels: Needs: Attention

### Description

We've seen instances where text wrapping will sometimes overflow the View boundary in accordion rows. The issue only occurs when specific rows are opened and closing/opening previous rows will sometimes make the issue go away.

I tried to reproduce this in a standalone RN application (v0.75) and while I haven't been able to reproduce the overflow issue, I did notice some strange behavior with text wrap changing based on accordion rows being opened/closed.



### Steps to reproduce

Build steps:
1. `git clone git@github.com:omniphx/reproduce-text-wrap.git`
2. `cd reproduce-text-wrap`
3. `bundle install`
4. `bundle exec pod install`
5. `yarn start`
6. `yarn ios`

Simulator steps:
1. Open all accordions until you get to the one labeled "this will shift text wrap"
2. Toggling this accordion will cause text wrap from previous rows to change

### React Native Version

0.75.4

### Affected Platforms

Runtime - Android, Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 14.4
  CPU: (10) arm64 Apple M2 Pro
  Memory: 662.86 MB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.11.0
    path: ~/.nvm/versions/node/v20.11.0/bin/node
  Yarn:
    version: 3.6.4
    path: ~/.nvm/versions/node/v20.11.0/bin/yarn
  npm:
    version: 10.2.4
    path: ~/.nvm/versions/node/v20.11.0/bin/npm
  Watchman:
    version: 2024.06.10.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/MITCHMX20/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.5
      - iOS 17.5
      - macOS 14.5
      - tvOS 17.5
      - visionOS 1.2
      - watchOS 10.5
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.3 AI-223.8836.35.2231.10671973
  Xcode:
    version: 15.4/15F31d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.10
    path: /usr/bin/javac
  Ruby:
    version: 2.7.6
    path: /Users/MITCHMX20/.rbenv/shims/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
```
```


### Stacktrace or Logs

```text
n/a
```


### Reproducer

https://github.com/omniphx/reproduce-text-wrap

### Screenshots and Videos

Reproduced issue:

https://github.com/user-attachments/assets/47689cd5-ffda-415c-97af-824de8e6ac39
Repository: godot
Issue: GDScript suggests closing curly brace when comma is missing in dictionary
Labels: discussion,topic:gdscript

### Tested versions

Reproducible in 4.3.stable.arch_linux

### System information

Arch Linux, Vulkan 1.3.280 - Forward+, NVIDIA GeForce GTX 1080 Ti

### Issue description

When forgetting to add a comma after a dictionary entry, the engine will give an error saying: 
> "Expected closing "}" after dictionary elements."

It wrongfully presumes the developer forgot to add a closing bracket, while the developer actually forgot to add a comma.

### Steps to reproduce

Just create a dictionary with atleast 2 entries and don't add a trailing comma after an entry. Using GDScript.

```gdscript
var ExampleDictionary = {
        "Key1": "Value1" # <- There should be a comma here
        "Key2": "Value2" # <- Here as well
}
```

### Minimal reproduction project (MRP)

Just a new project.
Repository: flutter
Issue: Codesigning failing for 3.27 beta
Labels: team-release

[engine commit](https://flutter.googlesource.com/mirrors/engine/+/d63244175cfeba9ac15dd0af1d1ba3369218f046)
[build](https://ci.chromium.org/ui/p/dart-internal/builders/flutter/Mac%20Production%20Engine%20Drone/14363/infra)
[logs](https://logs.chromium.org/logs/dart-internal/buildbucket/cr-buildbucket/8733911943888945617/+/u/Global_generators/Codesign__Volumes_Work_s_w_ir_cache_builder_src_out_debug_framework_unsigned_framework.zip/codesign_Apple_engine_binaries/stdout)

```
[INFO] codesign: Executing: /usr/bin/codesign --keychain build.keychain -f -s Developer ID Application: FLUTTER.IO LLC (S8QB4VV633) /Volumes/Work/s/w/ir/x/t/conductor_codesignBmgvmt/single_artifact/FlutterMacOS.xcframework/macos-arm64_x86_64/FlutterMacOS.framework --timestamp --options=runtime

Unhandled exception:
Exception: Failed to codesign binary or bundle at /Volumes/Work/s/w/ir/x/t/conductor_codesignBmgvmt/single_artifact/FlutterMacOS.xcframework/macos-arm64_x86_64/FlutterMacOS.framework with args: /usr/bin/codesign --keychain build.keychain -f -s Developer ID Application: FLUTTER.IO LLC (S8QB4VV633) /Volumes/Work/s/w/ir/x/t/conductor_codesignBmgvmt/single_artifact/FlutterMacOS.xcframework/macos-arm64_x86_64/FlutterMacOS.framework --timestamp --options=runtime
stdout:
stderr:
/Volumes/Work/s/w/ir/x/t/conductor_codesignBmgvmt/single_artifact/FlutterMacOS.xcframework/macos-arm64_x86_64/FlutterMacOS.framework: replacing existing signature
/Volumes/Work/s/w/ir/x/t/conductor_codesignBmgvmt/single_artifact/FlutterMacOS.xcframework/macos-arm64_x86_64/FlutterMacOS.framework: unsealed contents present in the root directory of an embedded framework
#0      FileCodesignVisitor.codesignAtPath.<anonymous closure> (package:codesign/src/file_codesign_visitor.dart:388)
<asynchronous suspension>
#1      RetryOptions.retry (package:retry/retry.dart:131)
<asynchronous suspension>
#2      FileCodesignVisitor.codesignAtPath (package:codesign/src/file_codesign_visitor.dart:381)
<asynchronous suspension>
#3      FileCodesignVisitor.visitDirectory (package:codesign/src/file_codesign_visitor.dart:289)
<asynchronous suspension>
#4      FileCodesignVisitor.visitDirectory (package:codesign/src/file_codesign_visitor.dart:264)
<asynchronous suspension>
#5      FileCodesignVisitor.visitDirectory (package:codesign/src/file_codesign_visitor.dart:264)
<asynchronous suspension>
#6      FileCodesignVisitor.visitDirectory (package:codesign/src/file_codesign_visitor.dart:264)
<asynchronous suspension>
#7      FileCodesignVisitor.processRemoteZip (package:codesign/src/file_codesign_visitor.dart:221)
<asynchronous suspension>
#8      FileCodesignVisitor.validateAll (package:codesign/src/file_codesign_visitor.dart:182)
<asynchronous suspension>

```
Repository: kubernetes
Issue: Mutating Admission Policy work tracking
Labels: sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

The KEP of Mutating Admission Policy is in:
https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/3962-mutating-admission-policies

The first alpha of Mutating Admission Policy is expected to be merged in 1.32. And we plan to have a second alpha before promoting to beta. The expected work for the second alpha would include:

* [in alpha1]New resources API added together with storage, serving, validation, etc
* [in alpha1]Feature gate added
* [in alpha1]Admission plugin
* [in alpha1]applyconfiguration support with CEL
* [in alpha1]jsonPatch support 
* [in alpha1]reinvocation with random ordering
* [in alpha1]FailurePolicy, matchCondition, variables, CEL variables(object, oldObject, request, params, authorizer, etc) support same as VAP
* [in alpha1]integration test
* Type checking
* Remove values support in applyConfiguration
* Metrics
* Validation checking by reapply object
* Shared binding(Needs more discussion on if strong use cases exists/worth doing)
* E2E test

 

### Why is this needed?

/sig api-machinery
/triage accepted
Repository: rust
Issue: Figure out which target features are required/incompatible for which ABI
Labels: T-compiler,C-tracking-issue,A-floating-point,A-ABI,A-target-feature

The context for this is https://github.com/rust-lang/rust/issues/116344: some target features change the way floats are passed between functions. Changing those target features is unsound as code compiled for the same target may now use different ABIs.

In https://github.com/rust-lang/rust/pull/134794, I am adding the infrastructure to have the compiler recognize this. But this infrastructure needs to be fed with information about which ABIs exist (e.g. softfloat/hardfloat), and which target features they require or are incompatible with. This will have to be done for each architecture we support.

- [x] x86 (32bit and 64bit):
  - `soft-float` can be set to swap the ABI; if unset, a hardfloat ABI is used
  -  32bit: uses float registers if `!soft-float && x87` (see [here](https://github.com/rust-lang/rust/issues/116344#issuecomment-2380834799)). IOW, hardfloat ABI requires `x87`.
      - except `f16` uses SSE registers so that's extra fun, see https://github.com/rust-lang/rust/issues/131819
  - 64bit: floats are passed via SSE registers, so likely `!soft-float && sse` is the relevant check -- IOW, hardfloat ABI requires `sse`/`sse2`.
- [x] arm
  - `soft-float` can be set to swap the ABI; if unset, a hardfloat ABI is used
  -  uses float registers if `!soft-float && fpregs` (see [here](https://github.com/rust-lang/rust/issues/116344#issuecomment-2380834799)), so hardfloat ABI requires `fpregs`
- [x] aarch64
  - doesn't really have a notion of a softfloat ABI, but we offer a softfloat target anyway...
  -  uses float registers if `fp-armv8` ; Rust makes `-neon` imply `-fp-armv8` so we have to forbid both -- but `neon` is stable! See https://github.com/rust-lang/rust/issues/131058
- [x] riscv
  - "RISC-V has a similar ABI split. -F/-D/-Q is your softfloat/nofloat, but it also comes with the Zfinx/Zdinx/Zqinx variants where floating-point values are carried in the regular registers and the floating-point register file is deleted. Your float-function-features would be +F,-Zfinx, +D,-Zdinx for riscv64gc-unknown-linux (linux does not permit finx). Although I don't think this is as much of a problem because the platform states that +F,+Zfinx is illegal?" (from [here](https://github.com/rust-lang/rust/issues/116344#issuecomment-1793256519))
  - For RISC-V targets, the float ABI can be specified by the llvm_abiname target option. As long as this happens, [f/d can be enabled without changing the ABI](https://godbolt.org/z/jTv7W6Wdc) (LLVM doesn't support q yet). Disabling target features required by the requested ABI [will cause LLVM to ignore the ABI](https://godbolt.org/z/x7Y53KP8d). The zfinx/zdinx features don't affect the ABI.
  - Also see https://github.com/rust-lang/rust/issues/132618
- [ ] powerpc
- [ ] wasm
- [ ] loongarch
- [ ] s390x
- [ ] sparc
- [ ] bpf
- [ ] csky
- [ ] hexagon
- [ ] mips
- [ ] m68k
- [ ] more?
Repository: next.js
Issue: Error on browsers like chrome 83
Labels: create-next-app,bug,Pages Router,Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://github.com/ViniciusLeviVL/next-catalogo-digital-debug2

### To Reproduce

Steps to reproduce:
Just init a next project with create-next-app@latest, deploy and see using a emulator like appetize.io (need to be deployed in web first) or insomnia (can reproduce in development environment)

https://appetize.io/demo?device=galaxytabs7&osVersion=11.0&record=true&debug=true&proxy=intercept&enableAdb=true

### Current vs. Expected behavior

I have a project with next.js and this month some old browsers is getting error on load, i tryed init a new project with the default template of next and it's getting error too, did not next support browsers like chrome 83 ?

I deployed my project on vercel to make sure that's not my server, but still getting these errors

https://next-catalogo-digital.vercel.app

Images:

[Error stack in my globar-error.tsx](https://i.sstatic.net/jtEVjV6F.png)

[Browser version of emulator](https://i.sstatic.net/wjCSrVsY.png)



### Provide environment information

```bash
Versions: 

Node: 20.16.0
Browser: Chrome 83 ...
Next: 14.2.15
```

My package.json:
```
{
  "name": "next-example",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint"
  },
  "dependencies": {
    "react": "^18",
    "react-dom": "^18",
    "next": "14.2.15"
  },
  "devDependencies": {
    "typescript": "^5",
    "@types/node": "^20",
    "@types/react": "^18",
    "@types/react-dom": "^18",
    "postcss": "^8",
    "tailwindcss": "^3.4.1",
    "eslint": "^8",
    "eslint-config-next": "14.2.15"
  }
}
```
```


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

create-next-app, Pages Router, Parallel & Intercepting Routes

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

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

### Additional context

I tested in next 13, 14 and 15
Repository: PowerToys
Issue: Power Toys will NOT open
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

Settings, General

### Steps to reproduce

When I try to open PowerToys, either from the system tray or the start menu or the .exe.

### ✔️ Expected Behavior

The application window where you can change settings to open.

### ❌ Actual Behavior

I get a notification saying "A new powertoys version has been installed,. Please restart the computer, when possible, to fully reload File Explorer extensions." and the normal settings/application window does not open.

### Other Software

_No response_
Repository: rust
Issue: We have two independent checks for "is this attribute unsafe"
Labels: C-cleanup,A-attributes,T-compiler

Turns out https://github.com/rust-lang/rust/issues/123757 was implemented by duplicating existing information previously added for https://github.com/rust-lang/rust/issues/82499:
- Attributes are marked as unsafe here:

https://github.com/rust-lang/rust/blob/624c071b997f3bab0ef086af24f59ebc95f37c59/compiler/rustc_feature/src/builtin_attrs.rs#L431-L433

- But separately, the unsafety checker has a list of unsafe attributes here:

https://github.com/rust-lang/rust/blob/c682aa162b0d41e21cc6748f4fecfe01efb69d1f/compiler/rustc_lint/src/builtin.rs#L293-L303

and here:

https://github.com/rust-lang/rust/blob/c682aa162b0d41e21cc6748f4fecfe01efb69d1f/compiler/rustc_lint/src/builtin.rs#L307-L317

and here:

https://github.com/rust-lang/rust/blob/c682aa162b0d41e21cc6748f4fecfe01efb69d1f/compiler/rustc_lint/src/builtin.rs#L336-L341

This should be cleaned up into a single source of truth for which attributes are unsafe.
Repository: tauri
Issue: [feat] Receive mouse events on inactive window (macOS)
Labels: type: feature request

### Describe the problem

Currently we can't receive mouse events when the window is inactive. This causes a couple of quirks in an always on top / picture-in-picture situation: 
- clicking the window to activate it when it's already on top is counterintuitive 
- it's not possible to react to window mouse enter/exit events to change the UI

Examples where this is working: Spotlight, Raycast, Zoom, Apple Music mini-player - button hover states still work even when the app is not active / focused. 

### Describe the solution you'd like

Add window mouse events (enter, exit, move) for `on_window_event` when the window is inactive. 

### Alternatives considered

_No response_

### Additional context

_No response_
Repository: deno
Issue: Deno npm:node-firebird won't work 
Labels: bug,node compat

Version: Deno 2.0.0
```js
import * as Firebird from "npm:node-firebird";

let options = {};
options.host = "server.ip";
options.port = 3050;
options.database = "aDatabase";
options.user = "SYSDBA";
options.password = "password";

Firebird.attach(options, function (err, db) {
  console.log("in callback");
});
```

callbacks are never called! 

with node.js or bun it works fine
Repository: deno
Issue: yaml/yml fmt - Indentless arrays as an option
Labels: suggestion,deno fmt

To directly quote https://github.com/prettier/prettier/issues/12385#issue-1156771175,

> I am a Kubernetes engineer (aka YAML engineer), do you support customization of the autoformat style of the YAML file? I prefer not adding indent for the array in YAML.
> 
> ![image](https://user-images.githubusercontent.com/49930785/156323702-3228ba8f-2c18-41c7-8a8d-11734fb7404a.png)

This could inflict `fmt` configuration option creep, but curious to know how the Deno team feels about it!