sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ant-design
Issue: Support for `Arrays` as the `value` of the `Option` used for `CheckboxGroup`
Labels: unconfirmed

### What problem does this feature solve?

The interface `Option` is defined currently as : 
```
interface Option {
  label: string;
  value: string;
  disabled?: boolean;
}
```
where `value` is meant to be a `string` only, although it looks like passing `array` can work.
The requested feature is to officially support `arrays` and test if they work without causing any issues.

### What does the proposed API look like?

The proposed API would add support for arrays to the `value` prop, something like : 
```
interface Option {
  label: string;
  value: string | string[];
  disabled?: boolean;
}
```

An example usage of this could be : 

```
import React, { useState } from "react";
import { Checkbox, Divider } from "antd";

const options = [
  {
    label: "Good Fruits",
    value: ["Banana", "Apple", "Strawberry"],
  },
  {
    label: "Bad Fruits",
    value: ["Kiwi", "Apricot", "Guava"],
  },
];
const App = () => {
  const [value, setValue] = useState([["Banana", "Apple", "Strawberry"]]);
  const handleChange = (checkedValues) => setValue(checkedValues);
  return (
    <>
      <Checkbox.Group
        options={options}
        defaultValue={[["Banana", "Apple", "Strawberry"]]}
        onChange={console.log}
      />
      <Divider />
      <Checkbox.Group options={options} value={value} onChange={handleChange} />
    </>
  );
};

export default App;
```

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: opencv
Issue: Adding new functionality to cv::warpPolar
Labels: feature

### Describe the feature and motivation

`cv::warpPolar` pays too much attention to the central region and ignores information about the edges of the image when mapping the image from Cartesian space to polar coordinate space.

I introduced a new radial non-uniform sampling method, i.e., I introduced new macro definitions WARP_POLAR_EXP and WARP_POLAR_SQUARE to compensate for the loss of edge information. A [pull request](https://github.com/opencv/opencv/pull/26681) has been submitted, please merge the contents.

For case examples, see [example](https://github.com/shuaikaishi/RRE).

### Additional context

_No response_
Repository: create-react-app
Issue: Create react issue(script problem from my system) ho
Labels: needs triage

I having an issue creating a react app due to running script disabled on my system... How do I solve it
![1735828948749787895579439052525](https://github.com/user-attachments/assets/ad4c47d7-f47d-4660-ab81-693fe57623e2)
Repository: godot
Issue: RayCast3D collision detection issue in simple demo scene
Labels: documentation,topic:physics,topic:3d

### Tested versions

Reproducible in Godot 4.3.stable.official, 77dcf97d8

### System information

Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated Quadro T2000 - Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz (12 Threads)

### Issue description

This simple scene demonstrates using a RayCast3D on a "turret" to test for obstructions/line-of-sight to players (entire script and scene pictured below + attached) . Ray casting fails after the player's position has been modified, despite the player position and raycast target_position matching. If this is expected behavior, it will at least be nice to document and explain why this is happening, so that others can learn from it (possible related issue [here](https://github.com/godotengine/godot/issues/95359))...

![Image](https://github.com/user-attachments/assets/19246781-f076-4caf-9103-7ae36cac1d03)


### Steps to reproduce

Run the scene, look at the console output and confirm collision detection failures in part (B).

### Minimal reproduction project (MRP)

Project attached (simple 1-script demo scene started from a blank project).

[raycasttest.zip](https://github.com/user-attachments/files/18291688/raycasttest.zip)
Repository: ant-design
Issue: 'Alert.ErrorBoundary' cannot be used as a JSX component.
Labels: help wanted

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-jyh2k9)

### Steps to reproduce

使用最新的vite react-ts模板（node 22.12.0）
安装antd，放入<Alert.ErrorBoundary/>组件
运行tsc -b

### What is expected?

返回0

### What is actually happening?

```
src/App.tsx:7:8 - error TS2786: 'Alert.ErrorBoundary' cannot be used as a JSX component.
  Its type 'typeof ErrorBoundary' is not a valid JSX element type.
    Type 'typeof ErrorBoundary' is not assignable to type 'new (props: any, deprecatedLegacyContext?: any) => Component<any, any, any>'.
      Construct signature return types 'ErrorBoundary' and 'Component<any, any, any>' are incompatible.
        The types returned by 'render()' are incompatible between these types.
          Type 'string | number | bigint | boolean | Element | Iterable<ReactNode> | Promise<string | number | bigint | boolean | ReactPortal | Iterable<ReactNode> | ReactElement<...> | null | undefined> | null | undefined' is not assignable to type 'ReactNode'.
            Type 'bigint' is not assignable to type 'ReactNode'.

7       <Alert.ErrorBoundary/>
         ~~~~~~~~~~~~~~~~~~~


Found 1 error.
```

| Environment | Info |
| --- | --- |
| antd | 5.22.7 |
| React | 18.3.1 |
| System | Windows 11 |
| Browser | 无 |

---
package.json
```
"dependencies": {
    "antd": "^5.22.7",
    "react": "^18.3.1",
    "react-dom": "^18.3.1"
  },
  "devDependencies": {
    "@eslint/js": "^9.17.0",
    "@types/react": "^18.3.18",
    "@types/react-dom": "^18.3.5",
    "@vitejs/plugin-react": "^4.3.4",
    "eslint": "^9.17.0",
    "eslint-plugin-react-hooks": "^5.0.0",
    "eslint-plugin-react-refresh": "^0.4.16",
    "globals": "^15.14.0",
    "typescript": "~5.6.2",
    "typescript-eslint": "^8.18.2",
    "vite": "^6.0.5"
  }
```

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: PowerToys
Issue: Workspaces - slack fails to launch
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response,Product-Workspaces

### Microsoft PowerToys version

0.87.1

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Workspaces

### Steps to reproduce

slack doesn't launch

Create/edit a workspace.
In my case, I have 3 apps split evenly in the screen (gmail running as a PWA app, onenote, and slack).  
When I launch the workspace, slack fails to launch.

I have tried running powertoys as admin. 
i have tried running the shortcut as admin.
no change in behavior



### ✔️ Expected Behavior

Expecting slack to be launched and placed correctly, as captured by the workspaces layout editor.

### ❌ Actual Behavior

2 apps correctly launch and are layed out.
the slack app does not launch at all.

![Image](https://github.com/user-attachments/assets/756de052-9648-4bcb-aaa6-2fe79fed8a30)


### Other Software

_No response_
Repository: go
Issue: proposal: crypto/webauthn: webauthn signature verification API
Labels: Proposal,Proposal-Crypto

### Proposal Details

Passkey Authentication is seeing wide-spread industry adoption for authenticating users on websites and is implemented through the https://w3c.github.io/webauthn specification.

It would be great if Golang would support this authentication mechanism out of the box.

As a first step towards this path, I would like to propose introducing WebAuthn signature verification to Golang. The verification algorithm should follow the steps outlined in https://w3c.github.io/webauthn/#sctn-verifying-assertion 

WebAuthn registration is a lot more specific to people's usecases  (e.g. need to think about attestation and whatnot) so I would leave it out of scope for the first draft.

Related proposals:

WebAuthn is also used for the `ecdsa-sk` keytype in SSH and somebody asked for support for that here: https://github.com/golang/go/issues/69999 . In order to implement that we need this proposal.


## Initial design

### Interface

```golang

type CoseAlgorithmIdentifier int64

const (
	EdDSA CoseAlgorithmIdentifier = -8
	ES256 CoseAlgorithmIdentifier = -7
	ES384 CoseAlgorithmIdentifier = -35
	ES512 CoseAlgorithmIdentifier = -36
	PS256 CoseAlgorithmIdentifier = -37
	RS256 CoseAlgorithmIdentifier = -257
)

type OriginInfo struct {
	Origin      string
	CrossOrigin bool
	TopOrigin   string
}
type OriginPolicy func(OriginInfo) error

func OriginWhitelist(origins ...string) OriginPolicy

type AuthenticatorFlags uint8

const (
	FlagUserPresent AuthenticatorFlags = 1 << iota
	_
	FlagUserVerified
	FlagBackupEligibility
	FlagBackupState
	_
	FlagAttestedCredentialData
	FlagExtensionData
)

type AuthenticatorAssertionResponse struct {
	ClientDataJson []byte
	AuthenticatorData []byte
	Signature         []byte
}

type AuthenticatorData struct {
	RpIdHash [32]byte
	Flags    AuthenticatorFlags
	Count    uint32
	// NOTE: Contains variable length AttestedCredentialData if FlagAttestedCredentialData is set
	// Because we only do assertion, this field is currently always nil
	AttestedCredentialData []byte

	// NOTE: Contains variable length ExtensionData if FlagExtensionData is set
	ExtensionData []byte
}

type VerifyOptions struct {
	RpId                     string
	OriginPolicy             OriginPolicy
	UserVerificationRequired bool
	UserPresenceRequired     bool
}

// Verify verifies the signature of the assertion response and returns the
// parsed authenticator data which can be processed further by the caller.
func (r *AuthenticatorAssertionResponse) Verify(challenge []byte, key crypto.PublicKey, alg CoseAlgorithmIdentifier, opts VerifyOptions) (*AuthenticatorData, error)

```


### Example implementation

https://github.com/golang/crypto/compare/master...arianvp:crypto:webauthn
Repository: tauri
Issue: [bug] open app from deep link will break accessory activation policy
Labels: type: bug,platform: macOS,status: needs triage

### Describe the bug

I am building a tray app and use `set_activation_policy(tauri::ActivationPolicy::Accessory)` to hide icon from dock.
Recently I am adding deep link feature to my app, and I found that open app from deep link will make dock icon show again.

I also have a tray menu item to toggle window show/hide and it works just fine. Only when accessing from deep link will cause dock icon appear.

rust: 
```rust
#[tauri::command]
fn show_window(app_handle: tauri::AppHandle) {
    let window = app_handle.get_webview_window("main");
    if window.is_none() {
        return;
    }
    let w = window.unwrap();
    if !w.is_visible().expect("get is_visible error") {
        let _ = w.show();
        let _ = w.set_focus();
    }
}
```

js:
```js
onOpenUrl((urls) => {
    invoke("show_window");
});
```

Currently, my workaround is call `set_activation_policy` again when open url is triggered. But it won't prevent dock icon showing but only hide it quickly after it reappears, so there still is a moment that the icon showing.

### Reproduction

_No response_

### Expected behavior

Dock icon won't show.

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 15.1.1 arm64 (X64)
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.83.0 (90b35a623 2024-11-26)
    ✔ cargo: 1.83.0 (5ffbef321 2024-10-29)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: stable-aarch64-apple-darwin (default)
    - node: 22.11.0
    - npm: 10.9.0
    - bun: 1.1.36

[-] Packages
    - tauri 🦀: 2.1.1
    - tauri-build 🦀: 2.0.3
    - wry 🦀: 0.47.2
    - tao 🦀: 0.30.8
    - @tauri-apps/api : 2.1.1
    - @tauri-apps/cli : 2.1.0

[-] Plugins
    - tauri-plugin-shell 🦀: 2.2.0
    - @tauri-apps/plugin-shell : 2.2.0
    - tauri-plugin-updater 🦀: 2.3.0
    - @tauri-apps/plugin-updater : 2.3.0
    - tauri-plugin-autostart 🦀: 2.2.0
    - @tauri-apps/plugin-autostart : 2.2.0
    - tauri-plugin-single-instance 🦀: 2.2.0
    - @tauri-apps/plugin-single-instance : not installed!
    - tauri-plugin-os 🦀: 2.2.0
    - @tauri-apps/plugin-os : 2.2.0
    - tauri-plugin-log 🦀: 2.2.0
    - @tauri-apps/plugin-log : 2.2.0
    - tauri-plugin-deep-link 🦀: 2.2.0
    - @tauri-apps/plugin-deep-link : 2.2.0
    - tauri-plugin-store 🦀: 2.2.0
    - @tauri-apps/plugin-store : 2.2.0
    - tauri-plugin-window-state 🦀: 2.2.0
    - @tauri-apps/plugin-window-state : 2.2.0

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../build
    - devUrl: http://localhost:1420/
    - framework: Svelte
    - bundler: Rollup
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: PowerToys
Issue: Keyboard inputs are ingored or lathced randomly when in games.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.83.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

When in games, especially Source 2 games (cs 2, Deadlock) key inputs are sometimes ignored or latched, needing another press to unlatch. For ex in cs2 jumpping (space) is frequently ignored while in Deadlock i am getting WASD keys latched forcing movement in other direction. I tried different keyboards and disabled all the overlays. Only when powerToys is fully closed inputs are picked up correctly, also seems to not be related to Keyboard Manager as i tried with it off and also had the same behaviour[PowerToysReport_2025-01-02-18-13-16.zip](https://github.com/user-attachments/files/18292444/PowerToysReport_2025-01-02-18-13-16.zip)


### ✔️ Expected Behavior

Correct inputs are picked up in game

### ❌ Actual Behavior

Sometimes keys are ignored, sometimes they latch. Probably somehow the key press (when ingored) or unpress (when it remains latched) event is picked up by PowerToys and consumed but not forwarded. 

### Other Software

Counter Strike 2
Deadlock
Repository: godot
Issue: .ghsaderinc files with filenames that match included macro name cause macro argument errors
Labels: bug,topic:shaders

### Tested versions

- Reproducible in 4.1, 4.2.1, 4.3, new build based on master dated 2025/01/02
- Other versions not tested

### System information

Godot v4.3.stable - Windows 10.0.22631 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3060 Ti (NVIDIA; 32.0.15.6614) - 11th Gen Intel(R) Core(TM) i7-11700F @ 2.50GHz (16 Threads)

### Issue description

This is a weird one, didn't quite believe it was an issue myself at first, but taken all else away the issue persists. Here goes:

If you have a .gdshaderinc file that defines a macro with the same name as the file, the line below in `#include` directive will throw a "Invalid macro argument" error.
My guess would be it somehow tries to parse the macro name in the filename as invoking the macro.

### Steps to reproduce

1. Create a testmacro.gdshaderinc, and define a macro function with the same name:

```glsl
#define testmacro(value) clamp(value, 0.0, 1.0)
```

2. Create a shader file, that includes the shaderinclude mentioned above:```glsl
shader_type spatial;

```glsl
#include "testmacro.gdshaderinc"
void fragment() {
	ALBEDO = vec3(1.0, 0.5, testmacro(2.0));
}
```

![Image](https://github.com/user-attachments/assets/13073a35-f8ec-4604-aac6-eb460d9a09b5)


### Minimal reproduction project (MRP)

(Note the project below uses `saturate.gdshaderinc` instead of `testmacro`, as I initially thought `saturate` would be some reserved term. Any term works, though).

[shaderinctest.zip](https://github.com/user-attachments/files/18292493/shaderinctest.zip)
Repository: PowerToys
Issue: The PowerToys Run interface is black, and the content is not visible clearly.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.87.1

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

The PowerToys Run interface is black, and the content is not visible clearly.

![Image](https://github.com/user-attachments/assets/fa6456b6-f245-4287-bdb9-66da7a1d483a)



### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: godot
Issue: Animation Editor Filter Of Showing Tracks From Selected Node In Tree Focus Problem When Starting To Edit A Key
Labels: bug,topic:editor,topic:animation

### Tested versions

Reproducible in Godot v4.4.dev7.official [46c8f8c5c]

### System information

Godot v4.4.dev7 - Ubuntu 24.04.1 LTS 24.04 on X11 - X11 display driver, Multi-window, 1 monitor - Vulkan (Mobile) - dedicated NVIDIA GeForce RTX 4060 Laptop GPU - 13th Gen Intel(R) Core(TM) i7-13700H (20 threads)

### Issue description

As you can see in attached video, in Animation editor when enabling filter icon that shows tracks from selected node In tree and when clicking on a key to work on it, the tracks disappearing and forcing me again disable filtering command and working within all tracks showing in editor.
[See This Video Of This Issue](https://github.com/user-attachments/assets/9a61a08c-98fb-486e-b088-7c85a7c73782)


### Steps to reproduce

As you can see in attached video, in the attached project:
1- select animation editor 
2- click on filter icon
3- select one on sprites in the scene tree
4- in the animation editor click on a key 
5- the track on animation disappears

### Minimal reproduction project (MRP)

[animationfilterissue.zip](https://github.com/user-attachments/files/18292711/animationfilterissue.zip)
Repository: rust
Issue: run-make-support: `assert_dirs_are_equal` traverses symlinks
Labels: T-compiler,T-bootstrap,C-bug,A-run-make

`assert_dirs_are_equal` will try to read the file content behind symlinks, which is not necessarily the desired behavior. Either we should make it configurable, or avoid traversing symlinks.
Repository: rust
Issue: cleanup: use full `strip` cli args in cg_ssa
Labels: C-cleanup,T-compiler

> Suggestion [DISCARD-ALL 1/2]: can we spell out the full flag for this as well? `llvm-objcopy` docs say that `-x` is
>
> > --discard-all, -x
> >
> >   Remove most local symbols from the output. Different file formats may limit this to a subset of the local symbols. For example, file and section symbols in ELF objects will not be discarded. Additionally, remove all debug sections.
>
> This happens to align with `llvm-strip`, unlike `-S` or no-flag.
>
> - https://llvm.org/docs/CommandGuide/llvm-strip.html#cmdoption-llvm-strip-discard-all
> - https://llvm.org/docs/CommandGuide/llvm-objcopy.html#cmdoption-llvm-objcopy-discard-all

_Originally posted by @jieyouxu in https://github.com/rust-lang/rust/pull/135034#discussion_r1901062326_
Repository: kubernetes
Issue: Support for ignoring bad response from mutating admissions webhook
Labels: sig/api-machinery,kind/feature,needs-triage

### What would you like to be added?

Currently, you can configure the kubernetes control plane to ignore errors when calling a mutating admission webhook

> webhooks.failurePolicy (string)
>
> FailurePolicy defines how unrecognized errors from the admission endpoint are handled - allowed values are Ignore or Fail. > Defaults to Fail.

~ https://kubernetes.io/docs/reference/kubernetes-api/extend-resources/mutating-webhook-configuration-v1/

This is great, as some webhooks are 'nice to have' rather than critical and I do not want their failure to block resource creation. 

However, it seems as though `failurePolicy` only applies to errors calling the webhook, and not from handeling the response. For example, I created an (intentionally faulty) webhook that returns an invalid patch under certain conditions (specifically it tries to add an entry to `/metadata/annotations` even if it does not exist). When I tried to create an appropriate pod, I got an error response, even though I had set this webhook to have an `Ignore` failure policy. e.g.

```
% kubectl create -f dummy-pod.yaml
 Error from server (InternalError): error when creating "dummy-pod.yaml": Internal error occurred: add operation does  
 not apply: doc is missing path: "/metadata/annotations/webhook-test": missing value
```

I had a look through the source and I *think* this might be where the decision is being made about which errors to fail open for.

https://github.com/kubernetes/kubernetes/blob/35f584187a6d1250191aa24b0dcf735350f57508/staging/src/k8s.io/apiserver/pkg/admission/plugin/webhook/mutating/dispatcher.go#L204-L214

---

It would be great if there was some way to tell kubernetes to ignore invalid responses (as well as errors calling the webhook). Of course, if there is already a way to do this, please do let me know!

### Why is this needed?

This would increase the safety of using a webhook.
Repository: electron
Issue: Registering globalShortcut F14 fails on Linux on X11
Labels: platform/linux,bug :beetle:,component/globalShortcut,x11,33-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

33.2.1

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

Other Linux

### Operating System Version

TUXEDO OS (Ubuntu 24.04 based)

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

Using the minimal example for registering a globalShortcut https://www.electronjs.org/docs/latest/api/global-shortcut/ one can register the whole range of shortcuts listed in "accelerator -> Available key codes" https://www.electronjs.org/docs/latest/api/accelerator#available-key-codes.

### Actual Behavior

Running Linux with the X11 display server registering F14 as a shortcut fails. In the example above the `console.log('registration failed')` message is triggered.

In Wayland everything works as expected.

### Testcase Gist URL

_No response_

### Additional Information

I have a Notebook at hand with an extra key that is actually just a physical F14 key.

By default on Linux F13-F24 are not actually bound to F13-F24, but (from /usr/share/X11/xkb/symbols/inet):

```
key <FK13>   {      [ XF86Tools         ]       };
key <FK14>   {      [ XF86Launch5       ]       };
key <FK15>   {      [ XF86Launch6       ]       };
key <FK16>   {      [ XF86Launch7       ]       };
key <FK17>   {      [ XF86Launch8       ]       };
key <FK18>   {      [ XF86Launch9       ]       };
key <FK20>   {      [ XF86AudioMicMute      ]       };
key <FK21>   {      [ XF86TouchpadToggle    ]       };
key <FK22>   {      [ XF86TouchpadOn        ]       };
key <FK23>   {      [ XF86TouchpadOff       ]       };
```

And F19 and F24 not bound at all.

I suspect the issues affects the whole range of F13-F24. There is this older issue where overwriting the default X11 config fixed the issue, but this can not be contained in an electron package: https://github.com/electron/electron/issues/40086