sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: [joy-ui][Button] Make the loading button inclusive
Labels: accessibility,component: button,package: joy-ui,RFC

### What's the problem?

While "loading", the `Button` is completely disabled. This presents an accessibility issue for keyboard and screen-reader users.

### What are the requirements?

The button element should remain enabled, and critically **focusable**. In addition to the progress spinner there should be some feedback offered to non-sighted users.

### What are our options?

RFC might not be the right format 🤔 maybe this ought to be a feature request? LMK and I'll convert the issue.

### Proposed solution

Rather than applying `disabled` while "loading":
- the button element should be attributed with `aria-disabled` 
- the click handler (and perhaps other handlers) should be omitted or prevented
- the button element should be attributed with an `aria-label`, like "loading" or "pending"—this would likely need to be configurable for i18n. alternatively, the loading spinner could receive the `aria-label` and the button would be `aria-labelledby` the appropriate ID.

### Resources and benchmarks

Some information about "aria-disabled":
- https://a11y-101.com/development/aria-disabled
- https://css-tricks.com/making-disabled-buttons-more-inclusive/

**Search keywords**: a11y, accessibility, loading, pending
Repository: three.js
Issue: WebGPURenderer: Camera nodes are broken in compute shaders
Labels: WebGPU,Nodes,WebGL Backend

### Description

Since the camera is never provided in the compute context the use of camera nodes such as `cameraPosition` won't work.

Should we add a second parameter `camera` when calling `compute()` such as `compute(computeShader, camera)` to fix this? /cc @sunag 


### Code

```js
const computeShader = tslFn = (() => {
    const cameraPos = cameraPosition;
} )(1)
```

### Version

r160
Repository: next.js
Issue: Navigation from not-found.tsx is not always working
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/app-router-not-found-routing-issue-nmd6v3

### To Reproduce

The small example application renders a `publication` query parameter or `None` if it is not defined. If the query parameter is `1544`, it will call `notFound()` from `next/navigation`, which will display the `not-found.tsx`.

1. Add to the URL `publication=138508`
2. See that `138508` is displayed in the page
3. Change query parameter to `publication=1544`
4. See that a `Go Back` link is displayed from the `not-found.tsx` page
5. Click the `Go Back` link
6. Note that the URL changes, but the `not-found` page is still displayed with the `Go Back` link

### Current vs. Expected behavior

Given the behavior shown above, when redirecting via a `<Link>` component or via the nextJS `router` from the `not-found` page, I would expect the UI to refresh accordingly.

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.2.0: Wed Nov 15 21:55:06 PST 2023; root:xnu-10002.61.3~2/RELEASE_ARM64_T6020
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 4.0.2
  pnpm: N/A
Relevant Packages:
  next: 14.0.3
  eslint-config-next: 14.0.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

App Router, Routing (next/router, next/navigation, next/link)

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

next dev (local), next start (local)

### Additional context

I have tested against versions 14.0.3, 14.0.4 and canary (14.0.5) and the same issue exists in all of them. This happens locally both with `dev` and after `build` and `start`.

Navigation from the `not-found` page *does* work if the navigation causes the URL `pathname` to change (for example from `/fishy` to `/en-US/fishy`, but if the `pathname` remains the same, and (for instance), just a query parameter is removed, then the URL is modified, but the application does not refresh.
Repository: flutter
Issue: [iOS] Crash in Production with `EXC_BAD_ACCESS  SkNVRefCnt<T>::SkNVRefCnt`
Labels: c: crash,e: device-specific,platform-ios,engine,a: production,P2,needs repro info,team-engine,triaged-engine

### Steps to reproduce

Sentry find

### Expected results

no crash

### Actual results

Crash with EXC_BAD_ACCESS 
SkNVRefCnt<T>::SkNVRefCnt
[d1d7f3a4228341b5ba6d126d49226b1d-symbolicated.txt](https://github.com/flutter/flutter/files/13947952/d1d7f3a4228341b5ba6d126d49226b1d-symbolicated.txt)


see attached stack trace file

### Code sample

<details open><summary>Code sample</summary>

```dart
[Paste your code here]
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[√] Flutter (Channel stable, 3.16.5, on Microsoft Windows [Version 10.0.19045.3930], locale de-DE)
[√] Windows Version (Installed version of Windows is version 10 or higher)
[√] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[√] Chrome - develop for the web
[√] Visual Studio - develop Windows apps (Visual Studio Community 2022 17.7.3)
[√] Android Studio (version 2022.3)
[√] VS Code (version 1.85.1)
[√] Connected device (3 available)
[√] Network resources
```

</details>
Repository: PowerToys
Issue: [Mouse Without Borders] Keyboard focus not switching to remote machine when using shortcut
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response,Product-Mouse Without Borders

### Microsoft PowerToys version

0.77.0

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

Mouse Without Borders

### Steps to reproduce

Windows 10.
Use keyboard shortcut to switch to remote machine (default Ctrl+Alt+[1,2,3,4]).
Without using the mouse, subsequent keyboard input is not transmitted to the remote machine.
A mouse move will successfully move keyboard focus to the remote machine.

### ✔️ Expected Behavior

My primary reason for using the keyboard shortcut to switch machines, is to avoid using the mouse.  I would expect the keyboard shortcut to move keyboard focus .

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: material-ui
Issue: [docs-infra] Use `text-wrap: pretty`
Labels: design,scope: docs-infra

From https://www.youtube.com/watch?v=cCAtD_BAHNw, `text-wrap: pretty` seems to make sense https://developer.chrome.com/blog/css-text-wrap-pretty? The performance might be good enough https://docs.google.com/document/d/1jJFD8nAUuiUX6ArFZQqQo8yTsvg8IuAq7oFrNQxPeqI/edit#heading=h.2djo7125fihp.

Should test in the PR that performances are not impacted by the modification

**Search keywords**:


https://github.com/mui/material-ui/assets/3165635/4698e290-4267-4d03-8bd7-1912cb1c1ecd
Repository: next.js
Issue: Can't import dynamic client component to server component
Labels: bug,Lazy Loading

### Link to the code that reproduces this issue

https://codesandbox.io/p/github/minazukie/next-dynamic-import-issue/main

### To Reproduce

1. Define a client component called `Hello`, the file path is `app/hello.tsx`.
```jsx
"use client"

export function Hello() {
  return <p>Hello!</p>
}
```
2. Import the client component using `dynamic` function in a server component, such as `app/page.tsx`.
```jsx
import dynamic from 'next/dynamic'
 
const ClientComponent = dynamic(() =>
  import('./hello').then((mod) => mod.Hello)
)
```
3. Add `<ClientComponent />` to the server component.
```jsx
import dynamic from "next/dynamic"

const DynamicComponent = dynamic(() =>
  import("./hello").then((mod) => mod.Hello)
);

export default function Home() {
  return (
    <div>
      <DynamicComponent />
    </div>
  );
}
```


### Current vs. Expected behavior

It will throw an error:
<img width="1029" alt="image" src="https://github.com/vercel/next.js/assets/19151914/beaa21e8-bcc9-4eca-a8ca-12d52c06111a">


### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.0.0: Thu Aug 17 21:23:05 PDT 2023; root:xnu-10002.1.11~3/RELEASE_ARM64_T6000
Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: 1.22.17
  pnpm: 8.6.12
Relevant Packages:
  next: 14.0.5-canary.59
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.1.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

App Router, Dynamic imports (next/dynamic)

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

https://nextjs.org/docs/app/building-your-application/optimizing/lazy-loading#importing-named-exports

_No response_
Repository: PowerToys
Issue: Powertoys key remapping not working on remote desktop (microsoft devbox) which uses windows 11
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage,Needs-Team-Response


![Uploading key_remapping_bug.png…]()
### Microsoft PowerToys version

0.77.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Create a dev box from devbox.microsoft.com (uses windows 11)

Login via remote desktop

install powertoys

restore the profile from the physical machine (which uses windows 10) 

Verify the exact same key remappings are present

The keys and shortcuts work on the physical machine but not on the remote machine

### ✔️ Expected Behavior

key remappings should have worked exactly similarly on both physical and remote machines

### ❌ Actual Behavior

The keys and shortcuts work on the physical machine but not on the remote machine

### Other Software

NA
Repository: material-ui
Issue: [test] Multiple tests failing with React Canary
Labels: bug 🐛,package: material-ui,package: joy-ui

Running tests with the canary version of React causes multiple of them to fail.

Reproduction steps:
1. Update package.json to reference React Canary: `node ./scripts/useReactVersion next`
2. Install the packages: `pnpm i`
3. Run tests: `pnpm test:unit`

**Search keywords**:
Repository: ant-design
Issue: Antd Input: To use with react-number-format customInput feature.
Labels: help wanted,Inactive,🚌 External Dependency

### Reproduction link

https://stackblitz.com/edit/react-m9nrou

### Steps to reproduce

In the example, it will be seen that the Input field does not work properly when numeric values are entered."

### What is expected?

I can't determine for sure if this problem is caused by Antd Input. However, this problem is not encountered when using the Input of another library.

### What is actually happening?

What I expect is that the values entered in the Input field work properly.

| Environment | Info |
| --- | --- |
| antd | 5.13.3 |
| React | 18 |
| System | Windows 11 |
| Browser | Chrome, Mozilla, Opera. |

---
I'm not sure if this problem is caused by Antd Input or react-number-format, I just wanted to open this issue because I saw that it worked correctly when I used another framework Input.
**Note: It works smoothly in version 5.10.3**

A sample of the material is also available, you can also examine it.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: Rules around call resolution on `fn_traits` are confusing
Labels: T-compiler,requires-nightly,F-unboxed_closures,C-discussion

I tried this code:

```rust
#![feature(fn_traits, unboxed_closures)]

pub struct Foo<F>(F); // a simple newtype over closure object, nothing more

impl<F: FnOnce(A) -> B, A, B> FnOnce<(A,)> for Foo<F> {
    type Output = B;

    extern "rust-call" fn call_once(self, (a,): (A,)) -> B {
        (self.0)(a)
    }
}

impl<F: FnMut(A) -> B, A, B> FnMut<(A,)> for Foo<F> {
    extern "rust-call" fn call_mut(&mut self, (a,): (A,)) -> B {
        (&mut self.0)(a)
    }
}

impl<F: Fn(A) -> B, A, B> Fn<(A,)> for Foo<F> {
    extern "rust-call" fn call(&self, (a,): (A,)) -> B {
        (&self.0)(a)
    }
}

fn main() {
    let mut s = String::new();
    
    // This works
    {
        let mut closure = |()| s.push_str("");
        (move |x| closure(x))(());
    }
    
    // This doesn't!
    {
        let closure = |()| s.push_str("");
        (Foo(closure))(());
    }
}
```
([playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=59a0a18a24169dc93a8bd544b6d6c987))

I expected to see this happen: `FnMut` gets picked up as the next candidate fitting for closure call, code compiles succesfully.

Instead, this happened: the closest candidate in method resolution should be `Self`, if anything, but, evidently, `&Self` is preferred instead. It would be justifiable for closures specifically if the code could be compiled. It doesn't seem to align with anything known so far about either closures or method call expressions. Removing Fn impl makes the code compile successfully, but it shouldn't be considered at all due to unsatisfied `F: Fn` bound.

### Meta

rustc version: `1.76.0 nightly`

Main tracking issue: #29625
Repository: kubernetes
Issue: StructuredAuthentication - remove the hard limit on JWTAuthenticators
Labels: priority/awaiting-more-evidence,kind/feature,sig/auth,needs-triage

### What would you like to be added?

Hi folks,

I was recently reading through the [Structured Authentication KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/3331-structured-authentication-configuration) and I find it very exiting. I was wondering how many authenticators could be configured and my first guess would have been that there would be no in code limitation. I found out that there is [a comment](https://github.com/aramase/kubernetes/blob/0712728ee9caab4d04ec0a751855aca8c891b690/staging/src/k8s.io/apiserver/pkg/apis/apiserver/validation/validation.go#L59-L61) in the code that says that this number will be 64 for some future release of Kubernetes. The reasoning behind this comment seems to be [another comment](https://github.com/kubernetes/kubernetes/pull/118984#discussion_r1263760016) made during PR review. That comment references the [Structured Authorization KEP](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/3221-structured-authorization-configuration) and the limit of 64 that is applied to lists, however in the KEP the limit is only mentioned for the number of `matchConditions` which I think makes sense. Also in the current version of the validation for AuthorizationConfiguration there seems to be [no limit](https://github.com/aramase/kubernetes/blob/0712728ee9caab4d04ec0a751855aca8c891b690/staging/src/k8s.io/apiserver/pkg/apis/apiserver/validation/validation.go#L224) for the number of authorizers.

Would you reconsider not enforcing the hard limit of 64 for the number of JWTAuthenticatiors?

kind ping @aramase as author and @enj as reviewer of the mentioned PR

### Why is this needed?

I understand that having > 64 authenticators is probably not the most common use case, however there are scenarios in which this is useful, i.e. a single kubernetes cluster is accessed by multiple external systems (ex. CI systems, other k8s clusters, etc) and this access is granted because that central k8s cluster has all of these external systems trusted via JWTAuthenticator configurations.
Repository: go
Issue: cmd/cgo/internal/test: TestCallbackCallersSEH failures
Labels: OS-Windows,NeedsFix,compiler/runtime

### Go version

go version devel go1.22-e9b3ff15f4 Wed Jan 10 17:35:49 2024 +0000 windows/amd64

### Output of `go env` in your module/workspace:

```shell
set GO111MODULE=
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\aaa\AppData\Local\go-build
set GOENV=C:\Users\aaa\AppData\Roaming\go\env
set GOEXE=.exe
set GOEXPERIMENT=
set GOFLAGS=
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOINSECURE=
set GOMODCACHE=C:\Users\aaa\go\pkg\mod
set GONOPROXY=
set GONOSUMDB=
set GOOS=windows
set GOPATH=C:\Users\aaa\go
set GOPRIVATE=
set GOPROXY=https://proxy.golang.org,direct
set GOROOT=C:\Users\aaa\code\golang-go
set GOSUMDB=sum.golang.org
set GOTMPDIR=
set GOTOOLCHAIN=auto
set GOTOOLDIR=C:\Users\aaa\code\golang-go\pkg\tool\windows_amd64
set GOVCS=
set GOVERSION=devel go1.22-e9b3ff15f4 Wed Jan 10 17:35:49 2024 +0000
set GCCGO=gccgo
set GOAMD64=v1
set AR=ar
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set GOMOD=C:\Users\aaa\code\golang-go\src\cmd\go.mod
set GOWORK=
set CGO_CFLAGS=-O2 -g
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-O2 -g
set CGO_FFLAGS=-O2 -g
set CGO_LDFLAGS=-O2 -g
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -Wl,--no-gc-sections -fmessage-length=0 -ffile-prefix-map=C:\Users\aaa\AppData\Local\Temp\go-build998051253=/tmp/go-build -gno-record-gcc-switches
```


### What did you do?

go test --ldflags=-linkmode=internal -run=TestCallbackCallersSEH ./cmd/cgo/internal/test

### What did you see happen?

```cmd
--- FAIL: TestCallbackCallersSEH (0.00s)
    callback_windows.go:107: incorrect backtrace:
        want:   [test._Cfunc_backtrace test.testCallbackCallersSEH.func1.1 test.testCallbackCallersSEH.func1 test.goCallback test._Cfunc_callback test.nestedCall.func1 test.nestedCall test.testCallbackCallersSEH test.TestCallbackCallersSEH]
        got:    []
FAIL
FAIL    cmd/cgo/internal/test   2.527s
FAIL
```

### What did you expect to see?

```cmd
=== RUN   TestCallbackCallersSEH
--- PASS: TestCallbackCallersSEH (0.00s)
PASS
ok      cmd/cgo/internal/test   2.286s
```

Some more context:

- Only reproduces when using the Go internal linker.
- The test fails only with certain gcc versions. I've reproduced the failure with:

```cmd
>gcc --version
gcc (x86_64-posix-seh-rev2, Built by MinGW-W64 project) 12.2.0
Copyright (C) 2022 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```
Repository: godot
Issue: ACES tonemapper uses incorrect gamma curve
Labels: topic:rendering,needs testing,topic:3d

### Tested versions

Godot v4.2.stable
Godot v4.2.1.stable

### System information

Godot v4.2.1.stable - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 (NVIDIA; 31.0.15.3742) - Intel(R) Core(TM) i5-8600K CPU @ 3.60GHz (6 Threads)

### Issue description

Scenes displayed with the ACES tonemapper show extremely dark mids, with overblown contrast and saturation in the highlights.

linear:
![image](https://github.com/godotengine/godot/assets/156802459/6012aa82-a77c-481b-b480-8b405e28e7c1)

Reinhard:
![image](https://github.com/godotengine/godot/assets/156802459/13cb784d-3c97-4148-b944-2d6236f09b62)

filmic:
![image](https://github.com/godotengine/godot/assets/156802459/af815e08-c2c0-4efb-bba6-f7dfd2f473b1)

ACES:
![image](https://github.com/godotengine/godot/assets/156802459/a28d5a5e-c17e-4f09-b7b8-7d9d347f162b)

It appears that the tonecurve is assuming an encoding gamma, while the data is in fact linear. To demonstrate, here is the screenshot in a color managed After Effects project using the ACES/rec709 display transform:

![image](https://github.com/godotengine/godot/assets/156802459/ed5067f6-1888-4283-b76f-62e1deca1513)
Still very dark (no exposure compensation), but much more realistic and manageable. This is what I would expect.

Here is the same but using After Effect's ACES/sRGB display transform:

![image](https://github.com/godotengine/godot/assets/156802459/6748dcb1-26b1-4319-9823-da9adc78ba44)
This is behaving similarly to Godot's tonemapper, accounting for the 1.8f exposure bias in Godot's tonemap code making it darker. sRGB and rec709 use the same gamut but have different gamma curves.

To emphasise, the issue is not that the scene is too dark. It's a dark scene and I would expect to have to compensate somehow when using ACES anyway. the issue is unmanageably high contrast and oversaturated colors between highlights and midtones, indicative of overcorrected gamma. Here is the scene in Godot's ACES tonemapper with brighter lights and higher exposure respectively:

![image](https://github.com/godotengine/godot/assets/156802459/789810f2-2670-41b4-9551-1025fae414ae)
![image](https://github.com/godotengine/godot/assets/156802459/f0256c0f-365f-4728-8b05-9fa8c84e91a9)
The contrast is way too high, highlights are way too blown out, high mids are way too saturated. As it stands the tonemapper is neither ACES compliant nor useable aesthetically.

### Steps to reproduce

- Apply ACES tonemapper to any 3d scene

### Minimal reproduction project (MRP)

[ACES tonemap gamma mrp.zip](https://github.com/godotengine/godot/files/13953767/ACES.tonemap.gamma.mrp.zip)
Repository: flutter
Issue: ListView does not trigger a sound when scrolling while using VoiceOver on iOS
Labels: platform-ios,framework,a: accessibility,f: scrolling,has reproducible steps,P2,team-ios,triaged-ios,found in release: 3.16,found in release: 3.19

### Steps to reproduce

1. Within the iOS settings app `Accessibility > VoiceOver > Audio > Sounds & Haptics > Scrolled Page` and enable both (they should be enabled by default)
2. Within the iOS settings app `Accessibility > VoiceOver`, enable VoiceOver
3. Run the linked demo app (or any other app that has a `ListView`)
4. Using 3 fingers scroll down the generated list view

### Expected results

There is an audible sound made each time you scroll down.

### Actual results

There is no sound or feedback to the user letting them know they have scrolled.

### Code sample

https://github.com/jeremynorman89/flutter_listview_accessibility_bug_demo

(There is nothing particularly special about this, it's just a ListView with 500 items in it)

### Screenshots or Video

_No response_

### Logs

_No response_

### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[✓] Flutter (Channel stable, 3.16.5, on macOS 14.2.1 23C71 darwin-arm64, locale en-GB)
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for more details.
[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.2)
[✓] VS Code (version 1.85.1)
[✓] Connected device (4 available)
[✓] Network resources

! Doctor found issues in 1 category.

```

</details>