sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: deno
Issue: authentication within @kubernetes/client-node is not working as expected
Labels: bug,node compat

Version: Deno 2.0.1

i tried to use the library: @kubernetes/client-node with deno and i wasnt able to authenticate with the provided examples here:
[@kubernetes/client-node](https://github.com/kubernetes-client/javascript/blob/master/README.md)

i switched back with the same code and configs to nodejs and it was working as expected
Repository: material-ui
Issue: [Radio] Radio's `ButtonBase` has `role="button"` when using styled-components
Labels: external dependency,component: radio,component: ButtonBase,package: styled-engine-sc

### Steps to reproduce

Link to live example: https://codesandbox.io/p/devbox/nervous-oskar-xx7s2l

Steps:
1. Use mui together with styled-components (i.e. aliasing `@mui/styled-engine` with `@mui/styled-engine-sc`)
2. Use a `<Radio />` component


### Current behavior

The radio's ButtonBase has a `role="button"`. This leads to an accessibility violation since there is a radio inside of a button.
The HTML basically looks like this:

```html
<span 
  class="MuiButtonBase-root MuiRadio-root [...]" 
  role="button">
    <input class="sc-egkSDF jccrsl PrivateSwitchBase-input" type="radio">
    <span class="sc-fAUdSK cyWAma">
      <svg>[...]</svg>
    </span>
    <span class="MuiTouchRipple-root-hfoSaC iZusHU MuiTouchRipple-root"></span>
</span>
```

Note that there is a `role="button"` on the outermost `<span>`. This should not be there and is in fact not there if you use the "regular" emotion adapter for `@mui/styled-engine`.

### Expected behavior

There is no `role="button"` on the `ButtonBase` for a `<Radio />`.

### Context

I think the problem is that `<SwitchBase />` passes `role={undefined}` to the `<SwitchBaseRoot />` (which is a styled `<ButtonBase />`) here: https://github.com/mui/material-ui/blob/master/packages/mui-material/src/internal/SwitchBase.js#L177
And I guess that styled-components just swallows properties with `undefined` values (since version 6?).
It used to work with mui v5 and styled-components v5.

This bug also affects other components that use `<SwitchBase />` (like `<Checkbox />` or `<Switch />`).

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: Linux 6.1 Debian GNU/Linux 11 (bullseye) 11 (bullseye)
  Binaries:
    Node: 20.11.0 - /usr/local/bin/node
    npm: 10.2.4 - /usr/local/bin/npm
    pnpm: 8.15.1 - /usr/local/share/npm-global/bin/pnpm
  Browsers:
    Chrome: Not Found
  npmPackages:
    @mui/core-downloads-tracker:  6.1.5 
    @mui/envinfo: 2.0.28 => 2.0.28 
    @mui/material: ^6.1.5 => 6.1.5 
    @mui/private-theming:  6.1.5 
    @mui/styled-engine:  6.1.5 
    @mui/styled-engine-sc: ^6.1.5 => 6.1.5 
    @mui/system:  6.1.5 
    @mui/types:  7.2.18 
    @mui/utils:  6.1.5 
    @types/react: 18.3.11 => 18.3.11 
    react: 18.3.1 => 18.3.1 
    react-dom: 18.3.1 => 18.3.1 
    styled-components: ^6.1.13 => 6.1.13 
```
</details>


**Search keywords**: radio styled-components button
Repository: vscode
Issue: Let's consider to use a concrete type for `toolInvocationToken`
Labels: feature-request,api

I have seen @isidorn pass a cancellation token as `toolInvocationToken` when calling `invoke`. I guess this is because of "looks like a token must be a token" thinking. We could rename the field or (my favourite) use a concrete type (class with private ctor) for this so that using a cancellation token or anything else yields a compile error
Repository: godot
Issue: Tree dropdown buttons disappear when Base Spacing is low
Labels: bug,topic:gui

### Tested versions

4.3 stable

### System information

Godot v4.3.stable - Windows 10.0.19045 - GLES3 (Compatibility) - Radeon RX 560 Series (Advanced Micro Devices, Inc.; 31.0.14001.45012) - Intel(R) Core(TM) i5-4570 CPU @ 3.20GHz (4 Threads)

### Issue description

If you change the Base Spacing value to <2 in the editor settings in the Theme section, the buttons that open the Tree on the left side disappear. This does not happen with the right side.

Base Spacing = 4
![2](https://github.com/user-attachments/assets/9b70d7e9-c950-45c1-92f8-e80f7b1ff363)

Base Spacing = 0
![1](https://github.com/user-attachments/assets/56ce4be7-c29f-42f8-b4a2-a9ec0ba69fce)


### Steps to reproduce

1. Open the editor settings and go to the Theme section
2. change the Base Spacing value to 0 or 1

### Minimal reproduction project (MRP)

N/A
Repository: ant-design
Issue: Add a prop for disabling click propagation for the Popover / Tooltip when the trigger is "click"
Labels: Inactive

### What problem does this feature solve?

Currently whenever a Popover component is opened using `trigger="click"`, a user can click outside of the popover component to close the component. However, some users don't consider the fact that if they click outside of the popover component it might trigger the event for the element they did click on. For example if a Popover component is rendered inside of a Modal. Clicking on the outside mask of the modal while the popover is open, will close both the Popover and the modal. 
See this in action on this [codesandbox](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-w7k5lj)



### What does the proposed API look like?

Preferably I would like to have a prop for the Tooltip / Popover component that would stop the propagation of this event like 
```ts
stopOutsideClickPropagation: boolean
```
Else adding in the clickEvent to the `onOpenChange` function like: 
```ts
(open: boolean, event: React.MouseEvent<HTMLElement>) => void
```

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: transformers
Issue: speed up whisper compile time
Labels: Feature request

### Feature request


after torch compiling the whisper.text_decoder model, the inference time is crazy low !. Thank you for the work !
however the warm up time is very long since it needs to go through all logits (at a maximum of 448)

how can reduce this time ?
(i have looked into storing the compiled model with pytorch but it does not seem supported)
(i have tried compiling torch_tensorrt but i have the error EncoderDecoderCache encountered in the dynamo_compile input parsing)

### Motivation

the start up time of the model can take around 10m for a large model

### Your contribution

happy to do a pr but need guidance
Repository: ui
Issue: [bug]: The CSS variable `--sidebar-width-mobile` is not being used
Labels: bug

### Describe the bug

The documentations says:

<img width="746" alt="Screenshot 2024-10-22 at 11 15 54" src="https://github.com/user-attachments/assets/ea089b2e-8599-470c-bb41-c692281b011b">

Link: https://ui.shadcn.com/docs/components/sidebar#width

But the CSS variable `--sidebar-width-mobile` is not being used anywhere in the code. So, changing it doesn't cause any effects.

### Affected component/components

Sidebar

### How to reproduce

Try to do this and see if the sidebar changed its width in mobile:

```
<SidebarProvider
  style={{
    "--sidebar-width": "20rem",
    "--sidebar-width-mobile": "2rem", // Very small sidebar
  }}
>
  <Sidebar />
</SidebarProvider>
```

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
macOS Sonoma 14.5 (23F79)
Arc Browser Version 1.65.0 (54911)
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: create-react-app
Issue: error that occur in vs code that i cann't run program:
Labels: needs triage,issue: bug report


PS C:\Users\Hp\Documents\New react project> npm start
npm error Missing script: "start"
npm error
npm error Did you mean one of these?
npm error   npm star # Mark your favorite packages
npm error   npm stars # View packages marked as favorites
npm error
npm error To see a list of scripts, run:
npm error   npm run
npm error A complete log of this run can be found in: C:\Users\Hp\AppData\Local\npm-cache\_logs\2024-10-22T14_14_21_973Z-debug-0.log
![image](https://github.com/user-attachments/assets/590f5118-068b-4a93-8579-bc9c073eb780)
Repository: rustdesk
Issue: Privacy Mode 1: Failed to get hwnd after started
Labels: bug,Fund

### Bug Description

On some of our devices running Windows 10, we cannot enable Privacy Mode 1 (the gray screen one), as it fails with one of the following errors:
- "No privacy window created"
- "Failed to get hwnd after started"

Unclear if there are any error logs that we can provide.
Also, we're using RustDesk Server Pro.


### How to Reproduce

1. Connect to a device running Windows 10
1. Enable Privacy Mode 1

### Expected Behavior

Privacy Mode is enabled successfully and hides the sensitive tasks we have to perform.

### Operating system(s) on local side and remote side

Windows 11 -> Windows 10

### RustDesk Version(s) on local side and remote side

1.3.1 -> 1.3.1 (Custom Client)

### Screenshots

![rustdesk_cA1pmYxLNF](https://github.com/user-attachments/assets/c9e65827-c5c6-41c4-82c5-eec1b720f54f)


### Additional Context

We can consistently reproduce this issue on some machines running Windows 10, but not all.

Is there any hardware / windows version requirements for using Privacy Mode?

<!-- POLAR PLEDGE BADGE START -->
## Upvote & Fund

- We're using [Polar.sh](https://polar.sh/rustdesk) so you can upvote and help fund this issue.
- We receive the funding once the issue is completed & confirmed by you.
- Thank you in advance for helping prioritize & fund our backlog.

<a href="https://polar.sh/rustdesk/rustdesk/issues/9720">
<picture>
  <source media="(prefers-color-scheme: dark)" srcset="https://polar.sh/api/github/rustdesk/rustdesk/issues/9720/pledge.svg?darkmode=1">
  <img alt="Fund with Polar" src="https://polar.sh/api/github/rustdesk/rustdesk/issues/9720/pledge.svg">
</picture>
</a>
<!-- POLAR PLEDGE BADGE END -->
Repository: stable-diffusion-webui
Issue: [Feature Request]: folder subpath in config rather than command line for reverse proxy
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

It would be nice if you could configure a subpath in the config for reverse proxy, even if it required a restart for the underlying engine.

I use a docker host (adbarho) and it would be nice if this didn't require command line overrides.

Something like the following:
![image](https://github.com/user-attachments/assets/ac91d2d0-bcef-4ede-a358-e8172a191f54)


### Proposed workflow

1. Go to settings
2. Press configure 'reverse proxy'
3. enter details


### Additional information

_No response_
Repository: TypeScript
Issue: Mixin with abstract class infers wrong type for super
Labels: Bug,Help Wanted

### 🔎 Search Terms

"mixin abstract super", "mixin abstract super type", "mixin abstract constructor super", "mixin abstract constructor super type", "mixin Abstract method cannot be accessed via super expression"

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about "super"


### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.7.0-dev.20241022#code/IYIwzgLgTsDGEAJYBthjAgsgTwILmjggGFV0EBvAKAQQAcBXEZAS1gVEhngQHMBTCADlgAW34AKAJQAuBFxYA7XgG4qAXypUAZg0XwWAe0UJRLAB5KA6iwgALfFyKk0YADwAVAEJp+CfuYQ-IoAJhiK-ADuCBIAdPHAULxgcsCK2ADaALpSCAC8AHxYeATcJGRgBRIA+iC+ct6+udQ0SBVYFkou5AFBoRi1vpRatLSMzGx8giLi0nIKysOjo1CCDFAmYAx0-FCxAsJiklIqCAD0ZwgAolBQhlByAESOhDzi9oYhCADkBzP83wQSjarh+OBeZW6YEBsDSikMiBAfjgsH46H4XwAbixgPJtrt-OY6Kt0EZFLFHq1aJpqSMEKsIOsTJhOoooWpNFoqEoglBtHA-DgAJKKXn81FLKaHWayeTQJSqDRaXT6CBk0ysmz2EVigWeHxgPy9YJhBARaJxBJJFIcdLZXKFYo63bi-hVQaGhoG-jNOkoUEsyxs9rG-oID1+FrLcasdh-I5zOVQBWS5YMpl4nZ7eMy04XBCRe4AazAVIQNPLdPTGw6QfZGiAA

### 💻 Code

```ts
abstract class MyAbstractClass {
  public abstract getName(): string;
}

function mixinWithAbstractClass<TBase extends new (...args: any[]) => MyAbstractClass>(_base: TBase) {

  class MixinClass extends _base {
    public getName(): string {
      return super.getName(); // Error: "Abstract method 'getName' in class 'MyAbstractClass' cannot be accessed via super expression."
    }
  }

  return MixinClass;
}



interface MyInterface {
  getName(): string;
}

function mixinWithInterface<TBase extends new (...args: any[]) => MyInterface>(_base: TBase) {

  class MixinClass extends _base {

    public getName(): string {
      return super.getName(); // works as expected
    }
  }

  return MixinClass;
}
```


### 🙁 Actual behavior

`mixinWithAbstractClass` fails because the compiler infers that `super` is of the exact type `class MyAbstractClass`.

### 🙂 Expected behavior

I expected `mixinWithAbstractClass` to compile like `mixinWithInterface` does. The constraint `TBase extends new (...args: any[]) => MyAbstractClass` specifies that `TBase` extends a concrete constructor, which returns instances that conform to `MyAbstractClass`. Since the constructor is concrete, we can infer that `TBase` (the superclass) already implements the abstract methods.

### Additional information about the issue

_No response_
Repository: angular
Issue: @angular/elements uses (internal) property name for custom element properties, but template name for attributes
Labels: area: elements,P3,bug,cross-cutting: signals

## Angular edit

Angular elements defines (`Object.defineProperty`) a property for each input of an element's component, as well as an HTML attribute which feeds into each property. Each input is thus represented by a property/attribute pair, as in the real DOM.

However, the way we name these things differs. `createCustomElement` uses the template name of the input for the attribute API, but the property name of the input for the DOM/property API. This was likely done intentionally as it makes _some_ sense - property name for properties - but it doesn't consider that the property name is meant to be an implementation detail of a component and shouldn't end up on its public API.

Fixing this would be a breaking change.

## Original Issue

When declaring an input with alias inside of a component and use `createCustomElement` of that component.
ex.

```
readonly name = input<string>(
    'name',
    { alias: 'customName' },
  );
```

On the actual web-component there are no such attribute as `customName`, only `name` will exist and work.


Looks  like that `ComponentFactory`  at method `resolveComponentFactory` which returns `inputs` array with `propName` of each input is not actually aliased name.

https://github.com/angular/angular/blob/main/packages/elements/src/component-factory-strategy.ts#L46
Repository: pytorch
Issue: Diffusers import change breaking newly built (non-cached) test-infra dockers.
Labels: module: ci,triaged,module: docker

> NOTE: Remember to label this issue with "`ci: sev`"

 <!-- uncomment the below line if you don't want this SEV to block merges -->
 <!--  **MERGE BLOCKING** -->

## Current Status
*Status could be: preemptive, ongoing, mitigated, closed. Also tell people if they need to take action to fix it (i.e. rebase)*.
* When trying to update dockers, diffusers inductor tests start breaking due to an import change between diffusers and hf hub. I can't figure out where diffusers / hf_hub versions are pinned.

## Error looks like
*Provide some way users can tell that this SEV is causing their issue.*
* Building new dockers / updating docker-ci requirements seem to cause stable diffustion tests to start failing
```
 from huggingface_hub import HfFolder, cached_download, hf_hub_download, model_info
ImportError: cannot import name 'cached_download' from 'huggingface_hub' (/opt/conda/envs/py_3.10/lib/python3.10/site-packages/huggingface_hub/__init__.py)
```

## Incident timeline (all times pacific)
*Include when the incident began, when it was detected, mitigated, root caused, and finally closed.*
* Atleast since yesterday

## User impact
*How does this affect users of PyTorch CI?*
* Can't update docker requirements without breaking tests

## Root cause
*What was the root cause of this issue?*
* Import change from diffusers _ hf_hub
## Mitigation
*How did we mitigate the issue?*
* Better pin dependencies for inductor tests perhaps? Discovered in upgrade here: https://github.com/pytorch/pytorch/pull/133814

## Prevention/followups
*How do we prevent issues like this in the future?*


cc @seemethere @malfet @osalpekar @atalman @pytorch/pytorch-dev-infra
Repository: svelte
Issue: docs: FAQ section "does svelte scale" is outdated
Labels: documentation

### Describe the bug

The svelte docs section "FAQ" has the same "[Does svelte scale](https://svelte.dev/docs/svelte/faq#Does-Svelte-scale)" section as the version for svelte 4 has. But, as mentioned in #2546 , this is no longer up to date with svelte 5.

### Severity

annoyance
Repository: angular
Issue: Allow reactive values for the disabled state of FormControls
Labels: feature,area: forms,forms: disabling controls

### Which @angular/* package(s) are relevant/related to the feature request?

forms

### Description

When initializing new FormControls, we currently can only pass a value and an optional disabled state.

However, when the disabled state depends on other reactive flows, we need to manually implement a change listener, like this:

```typescript
  someControl = new FormControl({ value: '', disabled: false });

  constructor() {
    this.shouldBeDisabled$.pipe(takeUntilDestroyed()).subscribe((disabled) => {
      if(disabled){
        this.someControl.disable();
      }else{
        this.someControl.enable();
      }
    });
  }
```

While this approach is valid, it feels a bit clunky nowadays—especially with the introduction of newer reactive concepts like signals.

It would feel more intuitive if the disabled state could also accept a signal or observable of type `boolean`, allowing it to automatically re-evaluate whenever the value changes. While I'm unsure if observables would be as intuitive in this context, I believe using signals would be much more readable.

For example, we could write something like this:

```typescript
  someControl = new FormControl({ value: '', disabled: toSignal(this.shouldBeDisabled$) });
```

This approach would also synergize well with template-driven forms, where we can already pass a signal to the disabled state of a form control. Having the same capability in reactive forms would create a more consistent developer experience for both form implementation approaches, template-driven and reactive.

### Proposed solution

allow disabled property to accept signals and/or observables

### Alternatives considered

Manually subscriptions
Repository: TypeScript
Issue: JSDoc `@import` no longer works correctly with default exports
Labels: Needs More Info,Needs Investigation

### 🔎 Search Terms

jsdoc import @import

### 🕗 Version & Regression Information

This changed between versions 5.5.4 and 5.6.3.

### ⏯ Playground Link

_No response_

### 💻 Code

```js
/** @import Foo from "my-app/foo" */

/** @return {Foo} */
function getFoo() {
  return myFoo;
}
```

`tsconfig.json` excerpt:

```json
{
 "compilerOptions": {
    "baseUrl": ".",
    "paths": {
      "my-app/*": ["src/*"]
    }
  }
}

```

### 🙁 Actual behavior

In TypeScript 5.5 the above worked correctly with `getFoo` returning `Foo`. As of TypeScript 5.6 this now returns an `any`. This workaround resolves the problem but feels like it is not what is intended.

```js
/** @import { default as Foo } from "my-app/foo" */

/** @return {Foo} */
function getFoo() {
  return myFoo;
}
```


### 🙂 Expected behavior

I expected default exports to work with `@import` in JSDoc.

### Additional information about the issue

_No response_
Repository: TypeScript
Issue: bug: error message says 0n is truthy
Labels: Bug

### 🔎 Search Terms

falsey, truthy, bigint, PseudoBigInt, TS Error 2872, TS Error 2873, unnecessary condition, constant condition

### 🕗 Version & Regression Information

- This changed between versions 5.5.4 and 5.6.3,
- https://github.com/microsoft/TypeScript/pull/59217 ([playground](https://www.typescriptlang.org/play/?target=99&ts=5.6.0-pr-59217-23#code/JYMwBAFADAdglGA3mFAoAvkA))

### ⏯ Playground Link

https://www.typescriptlang.org/play/?target=99&ts=5.7.0-dev.20241022#code/JYMwBAFADAdglGA3mFAoAvkA

### 💻 Code

`0n` is falsy.

```ts
if (0n) {
  // won't happen
}
```

### 🙁 Actual behavior

TS 2872: This kind of expression is always truthy.

### 🙂 Expected behavior

TS 2873: This kind of expression is always falsy.

### Additional information about the issue

I am presuming that this is due to this function, which always reports `BigIntLiteral` as `PredicateSemantics.Always`, rather than checking for `0n`.

https://github.com/microsoft/TypeScript/blob/c07da583afbfbb68930448b781832c74b3f713e6/src/compiler/checker.ts#L44498-L44532

Looks like this has been present since the always-truthy/always-falsey check was initially created: https://github.com/microsoft/TypeScript/pull/59217/files#diff-d9ab6589e714c71e657f601cf30ff51dfc607fc98419bf72e04f6b0fa92cc4b8R44293

I'd be happy to drop a PR if this is accepted and that's the issue.
Repository: PowerToys
Issue: Unable to remap CAPS, strange behavior
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Issue 1
Remap CAPS to Ctrl+C

Issue 2
Remap CAPS to Alt+Shift

### ✔️ Expected Behavior

Issue 1
Remap and work perfectly, with CAPSLOCK completely disabled

Issue 2
Allow me to remap CAPS to Alt+Shift

### ❌ Actual Behavior

Issue 1
When press CAPS, it causes lag and trigger CAPS, and sometimes it also trigger Ctrl+C
 
Issue 2
It suggest a third key in combo. But Alt+Shift itself is already language change shortcut

### Other Software

![Image](https://github.com/user-attachments/assets/b7c2406d-ed21-48d7-84fe-fe8238768f6d)
Repository: vscode
Issue: "Experimental" setting hover takes a surprisingly long time to show up
Labels: bug,settings-editor,confirmation-pending

Testing #231887

I don't recall seeing a hover take as long as this one does to show up. I have not configured the default hover delay, are we using something custom here?