sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ui
Issue: [bug]: Type Error in DropdownMenu Component: "checked" Property Assignment Issue
Labels: bug

### Describe the bug

When using the `DropdownMenu` component, I encounter a type error related to the `checked` property. The error message suggests that there is an incompatibility when `checked` is set to `CheckedState | undefined`.

### Affected component/components

DropdownMenu

### How to reproduce

1. npx shadcn-ui@latest add dropdown-menu
2. see error in the generated file

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
"next": "^14.0.0"
"react": "^18.2.0"
"typescript": "^5.1.6"
"node": "20.x"
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: flutter
Issue: HardwareKeyboard.instance.isControlPressed not working for right control key on macOS
Labels: a: text input,platform-mac,a: desktop,has reproducible steps,P2,fyi-text-input,found in release: 3.22,team-macos,triaged-macos

### Steps to reproduce

I'm using a MacBook Air with an external keyboard attached. The MacBook only has a left control key, the external keyboard has both a left and a right control key.

When trying to refactor my source code from using the old RawKeyEvent to the new KeyEvent, I noticed that the right control key doesn't work with the new HardwareKeyboard class. There's no onKeyEvent for the right control key and HardwareKeyboard.instance.isControlPressed also returns false when the right control key is pressed.

### Expected results

onKeyEvent and onKey both should react the same way, when the control modifier is pressed

### Actual results

onKey correctly recognizes the left and the right control key. onKeyEvent only recognizes the left control key. The onKeyEvent isn't fired when the right control key is pressed.

### Code sample

<details open><summary>Code sample</summary>

```dart
TextField(
  focusNode: FocusNode(
    onKeyEvent: (node, event) { log("isControlPressedNew: ${HardwareKeyboard.instance.isControlPressed}"); return KeyEventResult.ignored; },
    onKey: (node, event) { log("isControlPressed: ${event.isControlPressed}"); return KeyEventResult.ignored; },
  ),
)
```

</details>


### Screenshots or Video

_No response_

### Logs

<details open><summary>Logs (for pressing Ctrl+a in the TextField)</summary>

```console
[log] isControlPressed: true // When ctrl was pressed
[log] isControlPressedNew: false // When "a" was pressed
[log] isControlPressed: true // When "a" was pressed
```

</details>

### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[✓] Flutter (Channel stable, 3.22.0, on macOS 14.4.1 23E224 darwin-arm64, locale
    de-DE)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2023.1)
[✓] VS Code (version 1.89.1)
[✓] Connected device (3 available)
[✓] Network resources

• No issues found!
```

</details>
Repository: rust
Issue: Warn for `cfg!(target_* = "whatever")` usage in build scripts
Labels: A-diagnostics,T-compiler,T-cargo

### Code

```Rust
if cfg!(target_feature = "sse2") {
    // …
}
```


### Current output

```Shell
No warning
```


### Desired output

```Shell
A warning pointing at `cfg!(target_feature = "sse2")` stating that this will be likely wrong for the target system if you cross compile
```


### Rationale and extra context

I would expect a warning that explains that `cfg!(target_*)` will be evaluated in the context of the host system that compiles the build script and not in the context of the target system. It seems to be a common mistake for crate authors writing build scripts to use `cfg!` and not `std::env` in combination with the environment variables set by cargo. The warning should suggest that the later variant is the correct solution there.

### Other cases

_No response_

### Rust Version

```Shell
rustc 1.78.0 (9b00956e5 2024-04-29)
binary: rustc
commit-hash: 9b00956e56009bab2aa15d7bff10916599e3d6d6
commit-date: 2024-04-29
host: x86_64-unknown-linux-gnu
release: 1.78.0
LLVM version: 18.1.2
```


### Anything else?

_No response_
Repository: vscode
Issue: Keybindings editor should use pills for tags such as `@command` and `+when`
Labels: feature-request,keybindings-editor



![Image](https://github.com/microsoft/vscode/assets/16353531/9500f2f2-f897-4b4d-af93-cc8d4d580fa4)

^ this is a bit incomprehensible

---

Maybe also squeeze the when clause to `...` with possibility to expand on click
Repository: deno
Issue: Got UnexpectedEof when reading from a TlsConn
Labels: bug,tls

Version: deno 1.43.6 (release, x86_64-unknown-linux-gnu)
The following code throws UnexpectedEof after all html was printed to stdout.
```js
import { writeAll } from "jsr:@std/io";

const conn = await Deno.connectTls({ hostname: "www.google.com", port: 443 });
await writeAll(conn, new TextEncoder().encode("GET / HTTP/1.0\r\n\r\n"));
await conn.readable.pipeTo(Deno.stdout.writable);
```
The callstack is:
```
error: Uncaught (in promise) UnexpectedEof: unexpected end of file
    at Object.pull (ext:deno_web/06_streams.js:996:30)
    at Module.invokeCallbackFunction (ext:deno_webidl/00_webidl.js:946:16)
    at ReadableByteStreamController.pullAlgorithm (ext:deno_web/06_streams.js:3563:14)
    at readableByteStreamControllerCallPullIfNeeded (ext:deno_web/06_streams.js:1242:49)
    at ReadableByteStreamController.[[[PullSteps]]] (ext:deno_web/06_streams.js:5983:5)
    at readableStreamDefaultReaderRead (ext:deno_web/06_streams.js:2513:36)
    at ext:deno_web/06_streams.js:2742:9
    at new Promise (<anonymous>)
    at ext:deno_web/06_streams.js:2741:14
    at eventLoopTick (ext:core/01_core.js:168:7)
```

The problem doesn't exist when working with normal Tcp socket.
The following code works fine.
```js
import { writeAll } from "jsr:@std/io";

const conn = await Deno.connect({ hostname: "www.google.com", port: 80 });
await writeAll(conn, new TextEncoder().encode("GET / HTTP/1.0\r\n\r\n"));
await conn.readable.pipeTo(Deno.stdout.writable);
```
Repository: ant-design
Issue: Cascader.Panel 在 DatePicker 的panelRender 里清空值不会清空 Cascader 的值
Labels: Inactive,unconfirmed

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-ulihsa?file=demo.tsx)

### Steps to reproduce

1. 点击日期选择年月
2. 点击清空，清空日期的值
3. 再次点击日期，月份没有清空选中状态

### What is expected?

月份清空选中状态

### What is actually happening?

月份未清空选中状态

| Environment | Info |
| --- | --- |
| antd | 5.17.3 |
| React | latest |
| System | mac |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: next.js
Issue: Buffer polyfill not work on ios lower then 14
Labels: bug,Webpack

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/floral-snowflake-cyrx5f

### To Reproduce

Add something with Buffer on client side
Try open page on IOS lower then 14
Console report the error:
![image](https://github.com/vercel/next.js/assets/17552716/6c7b4b77-3c57-4c4f-a397-5d1a0f3696cb)


### Current vs. Expected behavior

The polyfill should work on versions supported by Next.js.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Fri Apr 2 22:23:49 UTC 2021
  Available memory (MB): 15701
  Available CPU cores: 8
Binaries:
  Node: 20.13.1
  npm: 10.5.2
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: 14.2.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


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

Not sure, Webpack

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

next dev (local), next build (local), next start (local)

### Additional context

_No response_
Repository: next.js
Issue: Custom page extension + own sitemap/robots route bug - route source code returned instead of Response
Labels: bug,Middleware,Navigation,Module Resolution,Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://github.com/Git-I985/next-custom-page-extension-custom-sitemap-route-bug

### To Reproduce

1. Create blank next project
2. Configure custom page extension, lets say `["x.ts", "x.tsx"]`
3. Create `sitemap.xml` directory in `src/app`
4. Create file `route.x.ts` with content 
```
export const GET = () => new Response('It will return file content because route starts with "sitemap"')
```
4. run `npm run dev` in terminal
5. Open `http://localhost:3000/sitemap.xml`
6. You will see `export const GET = () => new Response('It will return file content because route starts with "sitemap"')` instead of response text (`It will return file content because route starts with "sitemap"`)


### Current vs. Expected behavior

I expect `route.x.ts` return me actual response instead of page with route source code 

### 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
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 21.5.0
  npm: 10.2.4
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.2.3 // Latest available version is detected (14.2.3).
  eslint-config-next: 14.2.3
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.4.5
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Middleware, Module Resolution, Navigation, Parallel & Intercepting Routes

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local)

### Additional context

It reproduced only if there is word `sitemap` in the begining of the route name, also same issue reproduced with the name `robots`

_No response_
Repository: TypeScript
Issue: Nullish coalescing operator but for conditional types
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

nullish coalescing operator
conditional types

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

Add syntactic sugar to allow this:

```ts
type T = A extends B ?? C
```

to be shorthand of:

```ts
type T = A extends B ? A : C
```

### 📃 Motivating Example

When working with large complicated types, it is often that you need to check that a type extends another type before passing it as a type argument to another type.

For example, ensuring it is an array before passing it to something that requires it to be an array:

```ts
type Foo<T> = Bar<
    Some<Really<Deep<Complex<Type<Utility<T>>>>>> extends readonly unknown[]
        ? Some<Really<Deep<Complex<Type<Utility<T>>>>>>
        : never
>;

type Bar<T extends readonly unknown[]> = ...;
```

The more complex the type you need to check, the more you need to repeat yourself to pass the same type in again.

This proposal aims to address that.

```ts
type Foo<T> = Bar<
    Some<Really<Deep<Complex<Type<Utility<T>>>>>> extends readonly unknown[] ?? never
>;
```

### 💻 Use Cases

1. What do you want to use this for?

Making my type code more readable and easier to maintain.

2. What shortcomings exist with current approaches?

The need to repeat yourself. Updates to the type need to be make in two places.

3. What workarounds are you using in the meantime?

The long-form syntax.
Repository: node
Issue: undefined reference to `v8::internal::trap_handler::RegisterDefaultTrapHandler()'
Labels: riscv64

```console
/usr/lib64/gcc/riscv64-suse-linux/13/../../../../riscv64-suse-linux/bin/ld: /home/abuild/rpmbuild/BUILD/node-v22.2.0/out/Release/obj.target/v8_base_without_compiler/deps/v8/src/api/api.o: in function `v8::TryHandleWebAssemblyTrapPosix(int, siginfo_t*, void*)':
/home/abuild/rpmbuild/BUILD/node-v22.2.0/out/../deps/v8/src/api/api.cc:6403:(.text._ZN2v829TryHandleWebAssemblyTrapPosixEiP9siginfo_tPv+0xa): undefined reference to `v8::internal::trap_handler::TryHandleSignal(int, siginfo_t*, void*)'
/usr/lib64/gcc/riscv64-suse-linux/13/../../../../riscv64-suse-linux/bin/ld: /home/abuild/rpmbuild/BUILD/node-v22.2.0/out/Release/obj.target/v8_base_without_compiler/deps/v8/src/trap-handler/handler-outside.o: in function `v8::internal::trap_handler::EnableTrapHandler(bool)':
/home/abuild/rpmbuild/BUILD/node-v22.2.0/out/../deps/v8/src/trap-handler/handler-outside.cc:265:(.text._ZN2v88internal12trap_handler17EnableTrapHandlerEb+0x54): undefined reference to `v8::internal::trap_handler::RegisterDefaultTrapHandler()'
collect2: error: ld returned 1 exit status
make[1]: *** [tools/v8_gypfiles/mksnapshot.target.mk:228: /home/abuild/rpmbuild/BUILD/node-v22.2.0/out/Release/mksnapshot] Error 1
```
Repository: storybook
Issue: [Bug]: Storybook cant handle imported types in components, svelte
Labels: bug,help wanted,typescript,svelte

### Describe the bug

am tryin to have standartised options as type definition in my storybook. but even i not use this types in the stories, storybook has a problem when types are imported in the component.

tryin also full path imports and all types have the export flag

### Reproduction link

localhost

### Reproduction steps

see my additional content

### System

```bash
Archlinux, Storybook 8.0.9 -> cant update to 8.1.2 because of my cli issue (see the other ticket:https://github.com/storybookjs/storybook/issues/27236)
```


### Additional context

## Komponent
```<script lang="ts">
    import {headerClassType, headerType} from "../types";
    export let header: headerType = 2
    export let headerClass: headerClassType = "h"+header
    export let classes: string = ""
    export let overrideClasses: string = ""
    export let value: string
</script>

    <h1 class="atom-typography-title {headerClass} {classes} {overrideClasses}">{value}</h1>
```

## Story
```import AtomTypographyTitle from "./AtomTypographyTitle.svelte";
import type { Meta, StoryObj } from "@storybook/svelte";
import {headerClassTypeArr,headerTypeArr} from "../types";

const meta = {
    // @ts-ignore
    component: AtomTypographyTitle,
    title: "Atoms/Typography/Title",
    argTypes: {
        // @ts-ignore
        value: { control: "text" },
        classes: { control: "text"},
        overrideClasses: { control: "text"},
        header: {
            options: headerTypeArr,
            control: "select",
        },
        headerClass: {
            options: headerClassTypeArr,
            control: "select" ,
        },

    },
} satisfies Meta<typeof AtomTypographyTitle>;

export default meta;
type Story = StoryObj<typeof meta>

export const H1: Story = {
    args: {
        header: 1,
        headerClass: "h1",
        value: "This is a Title"
    },
}, H2: Story = {
    args: {
        ...H1.args,
        header: 2,
        headerClass: "h2"
    },
}, H3: Story = {
    args: {
        ...H1.args,
        header: 3,
        headerClass: "h3"
    },
}, H4: Story = {
    args: {
        ...H1.args,
        header: 4,
        headerClass: "h4"
    },
}, H5: Story = {
    args: {
        ...H1.args,
        header: 5,
        headerClass: "h5"
    },
}, H6: Story = {
    args: {
        ...H1.args,
        header: 6,
        headerClass: "h6"
    },
};
```

## Types one folder up:
```
export type headerType = 1 | 2 | 3 | 4 | 5 | 6
export type headerClassType = "h1" | "h2" | "h3" | "h4" | "h5" |"h6" 
export const headerTypeArr: headerType[] = [1, 2, 3, 4, 5, 6];
export const headerClassTypeArr: headerClassType[] = ["h1", "h2", "h3", "h4", "h5", "h6"];
```

Error:
```The requested module 'http://localhost:6006/src/components/types.ts' doesn't provide an export named: `'headerClassType'` ```
Repository: PowerToys
Issue: The program search module in PowerToys Run is unable to search for programs that do not have a desktop shortcut created.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.80.0

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

When I install an application in the.exe format and generate a shortcut on the desktop, it can be viewed in the program search. When I delete the shortcut, I can no longer search for it.
1. ctrl + space
2. input '?zomm'


result: not found!

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

22631.3593
Repository: vscode
Issue: Very thin hollow/transparent gap/background between mini-map and scrollbar (on split editor)
Labels: upstream,zoom

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->

On Zoom level = -1, there is a tiny gap between mini-map and scrollbar where underlying text is visible, causing distraction. An screenshot attached.

<img width="225" alt="Screenshot 2024-05-23 at 3 18 43 PM" src="https://github.com/microsoft/vscode/assets/110830958/33b7003b-deca-4d2b-88ff-1666a624e266">

Does this issue occur when all extensions are disabled?: Yes/No

YES

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.89.1
- OS Version: macOS Sonoma 14.5

Steps to Reproduce:

1. Set zoom level to -1
2. Open split editor
Repository: ant-design
Issue: Select组件在支持搜索的状态下使用onCompositionStart、onCompositionEnd中文输入没有处理，而Input组件处理了
Labels: Inactive,unconfirmed

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/antd-reproduction-template-forked-3w5zfm)

### Steps to reproduce

```js
import { Select } from 'antd'
import { useRef } from 'react'

const { Option } = Select

function SelectTest() {
  const inputCompositionStatus = useRef('end')

  function handleComposition(e) {
    console.log(e.type)
    if (e.type === 'compositionend') {
      inputCompositionStatus.current = 'end'
    } else if (e.type === 'compositionstart') {
      inputCompositionStatus.current = 'start'
    } else if (e.type === 'compositionupdate') {
      inputCompositionStatus.current = 'update'
    } else {
      inputCompositionStatus.current = 'end'
    }
  }

  return (
    <div style={{ margin: 50 }}>
      <Select
        mode="multiple"
        placeholder="Select a option"
        style={{ width: 800 }}
        dropdownStyle={{ width: 800 }}
        onCompositionStart={handleComposition}
        onCompositionUpdate={handleComposition}
        onCompositionEnd={handleComposition}
      >
        <Option value="option1">Option 1Option</Option>
        <Option value="option2">Option 2</Option>
        <Option value="option3">Option 3</Option>
      </Select>
    </div>
  )
}

export default SelectTest
```
这个传下去的onCompositionStart、onCompositionUpdate、onCompositionEnd的方法Select组件没有接收处理，不能让我在Select组件中搜索的时候处理中文输入

### What is expected?

期待的结果是当我在Select组件中进入中文输入搜索的时候，等我在输入法中将文字输入完成了才进行搜索

### What is actually happening?

实际的结果是我在Select组件中进行中文输入搜索时，在输入法中输入第一个字母就已经开始进行了搜索，立即显示暂无数据

| Environment | Info |
| --- | --- |
| antd | 5.17.3 |
| React | 18.2.0 |
| System | 谷歌浏览器 |
| Browser | 124.0.6367.210 |

---
这个问题的原因是Select组件在源码中没有对onCompositionStart和onCompositionEnd进行接收处理，而antd源码依赖的rc-select库是接收了onCompositionStart和onCompositionEnd方法的，所以需要在antd的Select组件源码中加上对onCompositionStart和onCompositionEnd方法的接收处理，可以参考antd的Input组件源码

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: [local_auth][iOS] Plugin throw NotAvailable exception in cases of No Permission, Lockout, and Face not recognized 
Labels: platform-ios,p: local_auth,package,P2,team-ios,triaged-ios,:hourglass_flowing_sand:

### Steps to reproduce

Code:
```dart
try {
      return await auth.authenticate(
        localizedReason: 'Please authenticate to continue',
        options: const AuthenticationOptions(
          biometricOnly: true,
          useErrorDialogs: false,
        ),
      );
    } on PlatformException catch (e) {
//I get NotAvailable here
}
```

### Expected results

it should throw with different error codes.

### Actual results

It throw NotAvailable in the following cases.
No Permission case: when I disable face id permission for my app in the device setting.

Lockout case: when i do too many wrong attempt for face id,

Face not recognized case: do auth with wrong face, ios will show a dialog giving you two options 1) Enter Password, 2) Cancel. When tap Cancel, it throw NotAvailable.

### Code sample

<details open><summary>Code sample</summary>

```dart
//please run above code snippet
```

</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
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.19.0, on macOS 14.3.1 23D60 darwin-arm64, locale
    en-MM)
[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
[✓] Xcode - develop for iOS and macOS (Xcode 15.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.3)
[✓] IntelliJ IDEA Community Edition (version 2023.3.2)
[✓] VS Code (version 1.89.1)
[✓] Connected device (3 available)            
[✓] Network resources

• No issues found!
```

</details>