sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react-native
Issue: useWindowDimensions + translucent system ui returns incorrect dimensions on android
Labels: Issue: Author Provided Repro,Platform: Android,API: Dimensions,Needs: Triage :mag:

### Description

The window height doesn't include the navigation bar height when it's displayed as "translucent". This also occurs if you enable edge-to-edge mode, which similarly shows the app UI under the system UI.


### Steps to reproduce

Install and run the reproducer project

### React Native Version

0.73.0

### Affected Platforms

Runtime - Android

### Output of `npx react-native info`

```text
System:
  OS: macOS 13.6
  CPU: (8) arm64 Apple M1 Pro
  Memory: 86.08 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.17.1
    path: ~/.nvm/versions/node/v18.17.1/bin/node
  Yarn:
    version: 1.22.19
    path: ~/.nvm/versions/node/v18.17.1/bin/yarn
  npm:
    version: 9.6.7
    path: ~/.nvm/versions/node/v18.17.1/bin/npm
  Watchman:
    version: 2023.09.04.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.11.3
    path: /Users/joeporpeglia/.rbenv/shims/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 23.0
      - iOS 17.0
      - macOS 14.0
      - tvOS 17.0
      - watchOS 10.0
  Android SDK: Not Found
IDEs:
  Android Studio: 2022.2 AI-222.4459.24.2221.10121639
  Xcode:
    version: 15.0/15A240d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 11.0.17
    path: /Users/joeporpeglia/.sdkman/candidates/java/current/bin/javac
  Ruby:
    version: 2.7.5
    path: /Users/joeporpeglia/.rbenv/shims/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.73.0
    wanted: 0.73.0
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: false
```


### Stacktrace or Logs

```text
n/a
```


### Reproducer

https://github.com/joeporpeglia/rn-android-window-dimensions-reproducer

### Screenshots and Videos

In the screenshots below the height of the blue view is set to `useWindowDimensions().height`.

### Navigation bar height is excluded on all android devices I tested

<img width="50%" src="https://github.com/facebook/react-native/assets/1399969/d2faf3f2-d7cb-4259-9ff4-77b80179525a" />

### Status bar height is excluded on Pixel 5 device

<img width="50%" src="https://github.com/facebook/react-native/assets/1399969/27ce2fca-3ae2-41a0-bfbc-fdd6eec87343" />
Repository: rust
Issue: Tracking Issue for `for await` loops
Labels: T-lang,B-unstable,C-tracking-issue,WG-async,F-async_for_loop,B-experimental

<!--
NOTE: For library features, please use the "Library Tracking Issue" template instead.

Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a
feature from implementation to stabilisation. Make sure to include the relevant
RFC for the feature if it has one. Otherwise provide a short summary of the
feature and link any relevant PRs or issues, and remove any sections that are
not relevant to the feature.

Remember to add team labels to the tracking issue.
For a language team feature, this would e.g., be `T-lang`.
Such a feature should also be labeled with e.g., `F-my_feature`.
This label is used to associate issues (e.g., bugs and design questions) to the feature.
-->

This is a tracking issue for a `for await` loop variant that makes it easier to work with async iterators (#79024).
The feature gate for the issue is `#![feature(async_for_loop)]`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [ ] Get consensus on design, and if we even want this feature
- [ ] Implement the feature
- [ ] Adjust documentation ([see instructions on rustc-dev-guide][doc-guide])
- [ ] Formatting for new syntax has been added to the [Style Guide] ([nightly-style-procedure])
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[nightly-style-procedure]: https://github.com/rust-lang/style-team/blob/master/nightly-style-procedure.md 
[Style Guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide

### Dependencies

- #79024 
  - The design for `AsyncIterator` still doesn't have consensus, and naturally the desugaring of `for await` will depend on this. Fortunately, the desugaring is an implementation detail so we aren't necessarily blocked on experimentation by that design.

### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->

This is an early experimental feature, so basically every question is still unresolved.

### Implementation history

<!--
Include a list of all the PRs that were involved in implementing the feature.
-->

- #118847
Repository: vscode
Issue: Float exact matches to the top in the Command Palette
Labels: bug,quick-open

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
<img width="851" alt="image" src="https://github.com/microsoft/vscode-copilot/assets/323878/02a69d8d-40fd-4df1-b2c2-9227c56ab5ce">

This happens because the `recently used` section of the Command Palette is sorted by "last used". Reproing this bug is easy:
* Run `Preferences: Color Theme`
* Run `Preferences: Browse Color Themes in Marketplace`
* Get Copilot Chat `@vscode` agent to suggest running the former

If we float exact matches to the top, the user can have a nicer experience when using `@vscode` in Chat & if they happen to type in an exact match.
Repository: deno
Issue: proposal: convert `-1n` to `0xffffffffffffffffn` internally in KV interface
Labels: suggestion,ext/kv

One of the bigger toe-stubs that I've seen people have with the KV sum mutation API is that they expect negative numbers to just work. I think this is reasonable. Currently, we have an error message, but one that is really not useful. If people come to discord, they may be able to find the `0xffffffffffffffffn` hack but almost everyone who discovers it is confused about why it works.

I see a few paths forward:
1. Do nothing
2. Make docs + error message better ("oh I saw you were trying to increment by `-1n`, use `0xffffffffffffffffn` instead)
3. Internally convert negative numbers to the positive number equivalent

I'm personally in favor of number 3. Curious to hear what people think.
Repository: rust
Issue: `SelectionContext::evaluate_predicate_recursively` ignores type paramters in outlive predicates
Labels: C-bug,T-types

I believe this is missing another special case for `pred.0.has_params()` as well as `has_placeholders()`:
https://github.com/rust-lang/rust/blob/3340d49d22b1aba425779767278c40781826c2f5/compiler/rustc_trait_selection/src/traits/select/mod.rs#L798-L808
Repository: rust
Issue: `InferCtxt::region_constraints_added_in_snapshot` ignores type outlives obligations
Labels: T-compiler,A-inference,T-types

This function should also consider region obligations added in `InferCtxtInner::region_obligations`

https://github.com/rust-lang/rust/blob/3340d49d22b1aba425779767278c40781826c2f5/compiler/rustc_infer/src/infer/mod.rs#L920-L927
Repository: vscode
Issue: Selecting "Visible After Execute" for the "Show Cell Status Bar" setting leads to layout glitches
Labels: bug,notebook-statusbar

### Applies To

- [X] Notebooks (.ipynb files)
- [ ] Interactive Window and\/or Cell Scripts (.py files with \#%% markers)

### What happened?

Selecting the "VisibleAfterExecute" option for the "Show Cell Status Bar" setting and executing cells one by one leads to the following layout glitches:

- [Margins between cells disappear.](https://ibb.co/qmzYwnW)
- [The size of some cells is reduced and is back to normal only after the cell is executed.](https://ibb.co/Hn1vnLy)

### VS Code Version

1.76.0

### Jupyter Extension Version

v2023.2.1000592019

### Jupyter logs

_No response_

### Coding Language and Runtime Version

Python 3.10.9

### Language Extension Version (if applicable)

_No response_

### Anaconda Version (if applicable)

_No response_

### Running Jupyter locally or remotely?

Local
Repository: next.js
Issue: Intercepting Routes + Dynamic Routes cause incorrect page routing
Labels: bug,Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://github.com/Tim0401/nextjs-intercepting-dynamic-routes

### To Reproduce

1. Start the application in development (npm run dev)
2. Access http://localhost:3000/parent
3. Click `/parent/new`
4. `params.id: new` is displayed

### Current vs. Expected behavior

I expected to display `new`, but got `params.id: new`.
In other words, when I accessed `/parent/new`, I expected it to be routed to `app/[parentId]/(.)new/page.tsx`, but it was routed to `app/[parentId]/(.)[id]/page.tsx`.

### 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.1.0: Mon Oct  9 21:28:45 PDT 2023; root:xnu-10002.41.9~6/RELEASE_ARM64_T6020
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.0.5-canary.9
  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, Routing (next/router, next/navigation, next/link)

### Additional context

This problem seems to reproduce only under nested Dynamic Routes.
Repository: ant-design
Issue: upload 组件上传图片时支持粘贴功能
Labels: help wanted,💡 Feature Request,Inactive

### What problem does this feature solve?

https://ant-design.antgroup.com/components/upload-cn 希望upload组件实现粘贴图片上传
![image](https://github.com/ant-design/ant-design/assets/1331211/35c70774-ef7a-4a6c-9baf-5601e226b508)

### What does the proposed API look like?

当鼠标移动到drag drop区域时，可以粘贴之前复制的图片，自动上传

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: material-ui
Issue: [material-ui][Alert] Potential accessibility issues
Labels: accessibility,waiting for 👍,package: material-ui,component: alert,enhancement

Hi, 
I was looking at the Alert component and I noticed it added an ARIA alert role to the component. This component may potentially not exist on page load and might be displayed dynamically.

In your [accessibility notes for the alert component ](https://mui.com/material-ui/react-alert/#accessibility) you say:

> When the component is dynamically displayed, the content is automatically announced by most screen readers. At this time, screen readers do not inform users of alerts that are present when the page loads.

The content is not always automatically announced by some screen readers though. Scott O'Hara talks about this in a post called [are we live](https://www.scottohara.me/blog/2022/02/05/are-we-live.html).

> Dynamically injecting a live region node or changing an existing live region from display: none to display: block are effectively the same. In both cases (being absent or set to display: none) the live region does not exist in the a11y tree. Rather, as the following test cases show, ensuring an empty live region exists in your DOM, and injecting content into it when necessary, proves to be the most robust way to ensure a live region will be announced.

#### Severity of Alerts

Some people might not consider a success message an alert, and depending on context, info and warning might not be either.  You are appending role="alert" to the component for all variants. I really think this should be revisited. At the very least mentioned in the documentation. I don't think pointing to the WAI-ARIA Authoring Practices helps here.

Thanks.
Repository: flutter
Issue: TextField: The container does not disappear from autocorrection
Labels: a: text input,platform-ios,engine,has reproducible steps,P2,team-ios,triaged-ios,found in release: 3.16,found in release: 3.18,fyi-text-input

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Steps to reproduce

1. write a word in the input field to call up the auto-correction rectangle
2. hide app
3. open the application
4. hide keyboard

### Expected results

--

### Actual results


https://github.com/flutter/flutter/assets/38835822/0eb9b3e9-ead6-4247-b841-e90d8a91013e



### Code sample

<details><summary>Code sample</summary>

```dart
import 'package:flutter/material.dart';
import 'package:flutter/services.dart';
import 'package:path/path.dart' as path;

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Playground',
      home: AutoCorrectTest(),
    );
  }
}

class AutoCorrectTest extends StatefulWidget {
  @override
  _AutoCorrectTestState createState() => _AutoCorrectTestState();
}

class _AutoCorrectTestState extends State<AutoCorrectTest> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(
        title: Text('TextField example'),
      ),
      body: Padding(
          padding: EdgeInsets.all(16.0),
          child: Column(
            children: [
              TextField(
              ),
              ElevatedButton(onPressed: () {
                FocusScope.of(context).requestFocus(FocusNode());
              }, child: const Text('Hide keyboard')),
              ElevatedButton(onPressed: () {
                Navigator.of(context).push(MaterialPageRoute(builder: (context) => Scaffold(appBar: AppBar(),body: Text('new page'),)));
              }, child: const Text('Go to nextPage'))
            ],
          )
      ),
    );
  }
}```

</details>


### Screenshots or Video

<details>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.13.8, on macOS 14.0 23A344 darwin-arm64, locale ru-RU)
[✓] Android toolchain - develop for Android devices (Android SDK version 33.0.2)
[✓] Xcode - develop for iOS and macOS (Xcode 15.0.1)
[✓] Chrome - develop for the web
[✓] Android Studio (version 2022.2)
[✓] Android Studio (version 2021.2)
[✓] Connected device (4 available)
[✓] Network resources

• No issues found!
```

</details>
Repository: TypeScript
Issue: Functions with fewer parameters NOT assignable to functions with more parameters defined as tuples union
Labels: Bug,Help Wanted

### 🔎 Search Terms

"tuple union" "tuple spread"

### 🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about

### ⏯ Playground Link

[Playground Link](https://www.typescriptlang.org/play?ts=5.4.0-dev.20231213#code/C4TwDgpgBAcgrgWwEYQE4GcoF4oG0CGAXFAHaIqoA0USxZyaAugNwBQokUAysKgJYkA5phwFi6XgMHVaUCfyEtW7cNAAqcMABsIAQVTDsUABQA6c-gPpi8BhgCU2AHxQAbgHs+AEzYBjdyQSUABmAIzEGtp6VkbG+I5YLv6B7jqmWu6CcfbMUAD0eVCAvBuAMjvKHNBcfIIk+MBwqBAA8q5oGfheRgDeJuamlsI25Gjo9sQe3rlmFlbEPArCY26ePlAAviqcAGKBAJIkwCMQvsB8AbHT-bOwww7Oy96OAGQmlwPW3JJCo-cTXjmbdSaHToACqJDOJH0hhwb2utgomAAPp8Fj9Eg8fMpkkFggAmObVWr1RotNruDqxeL3HGpCDpTLZXIFYplHHAEIAZmIO3Q+0OGGOp3OsOpGNpaQyWXizMKpVY7JCABYIsCIGCIQFoSITGKkgF0HSGdKcvlCoAZcmUeQAVNbWFBrVA1KooAByOLiL6CKAo+gUBIuP6uqB8TAkdwc-DodBE-BIHRQYDuRMu12REHgyHa12me2OqBO1SYdzBKBgSz4BAQAWYV34YP4EidOtWBuNEMkfwIcuneP0vMFwfOziuhEjH2oqToYOh0gRqBRmM1OMJpMpkdiOReid+pg5geDoepscYGdh+eL2N9xPJipuzfyKQ726MfcOw8frjuBq+aAACyjKA8SgCAdCrA5jB+JA4A5YABmrBctAyAB3YsSC0EAoFCUxjDxTk8Txew8zyZQgA)

### 💻 Code

```ts
type Numbers = [a: number, b: number];
type Strings = [a: string, b: string];

type TupleArgs = (...args: Numbers) => void;
const f1: TupleArgs = (a) => console.log(a); // 👌

type SignatureOverload = { (...args: Numbers): void; (...args: Strings): void; }
type FnsIntersection = ((...args: Numbers) => void) & ((...args: Strings) => void);
type TuplesUnionArgs = (...args: Numbers | Strings) => void;

const f2: SignatureOverload = (a) => console.log(a); // 👌
const f3: FnsIntersection = (a) => console.log(a); // 👌
const f4: TuplesUnionArgs = (a) => console.log(a); // ❌

/**
 * Type '(a: string | number) => void' is not assignable to type 'TuplesUnionArgs'.
 *   Types of parameters 'a' and 'args' are incompatible.
 *     Type 'Numbers | Strings' is not assignable to type '[a: string | number]'.
 *       Type 'Numbers' is not assignable to type '[a: string | number]'.
 *         Source has 2 element(s) but target allows only 1.(2322)
 */
```


### 🙁 Actual behavior

```
Type '(a: string | number) => void' is not assignable to type 'TuplesUnionArgs'.
  Types of parameters 'a' and 'args' are incompatible.
    Type 'Numbers | Strings' is not assignable to type '[a: string | number]'.
      Type 'Numbers' is not assignable to type '[a: string | number]'.
        Source has 2 element(s) but target allows only 1. (2322)
```

### 🙂 Expected behavior

`(a: string | number) => void` should be assignable to `(...args: [a: number, b: number] | [a: string, b: string]) => void`

### Additional information about the issue

Since this issue has 2 pretty clean workarounds (signature overload, functions intersection), it is not critical. 
But it is an instance of inconsistent behaviour (which is annoying).
Repository: godot
Issue: Windows/editor: mouse hit test appears to be broken
Labels: bug,topic:gui

### Tested versions

- Reproducible in v3.5.3.stable.official [6c814135b]

### System information

Windows version 10.0.19045.3693 - x64

### Issue description

Mouse hit testing in the Godot UI (menu items, buttons, etc...) appear to be slightly off: for example, moving the mouse over a menu item with a submenu will highlight the menu as expected but the submenu won't open until the mouse is moved outside the menu item:


https://github.com/godotengine/godot/assets/199648/ae362ed7-7b9f-4e4f-90c7-23c3534eb9bb



Not sure this is related, but I am using a Surface Book which has an HDPI screen (Windows 10 scaling is set to `200%`).

### Steps to reproduce

- start godot
- open or create a new project
- move the mouse over the `Project > Tools` menu item

### Minimal reproduction project (MRP)

It is not specific to a project: creating a new project is enough.
Repository: next.js
Issue: `params` in catchall doesn't return empty array
Labels: bug

### Link to the code that reproduces this issue

https://github.com/tobiaslins/catchall-params-bug/blob/main/src/app/%5B%5B...slug%5D%5D/page.tsx

### To Reproduce

- Create `/src/[[...slug]]/page.tsx`
- Log `params` from props
- Visit localhost:3000

### Current vs. Expected behavior

I'd expect for the root to get `{ params: { slug: [] }` but it returns `{params: {} }`

### 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: Fri Sep 15 14:41:43 PDT 2023; root:xnu-10002.1.13~1/RELEASE_ARM64_T6000
Binaries:
  Node: 18.17.1
  npm: 9.6.7
  Yarn: 1.22.19
  pnpm: 7.14.2
Relevant Packages:
  next: 14.0.4
  eslint-config-next: N/A
  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

### Additional context

We need the info that it was catched by catchall route. When having `slug: []` we can resolve the `route` from that + pathname
Repository: vscode
Issue: Improve clarity of a search view toggle button tooltip
Labels: search,polish,confirmed

Type: <b>Feature Request</b>

"Use Exclude Settings and Ignore Files"

![image](https://github.com/microsoft/vscode/assets/6726799/0a79571f-cd1a-4f5f-9335-a3428e7a0186)

This could be understood to mean either:

1. all files will be ignored (ignore is a verb)

or:

2.  any `.gitignore` and `.ignore` files will be consulted to determine what will be ignored (ignore is a noun)

The answer is 2, but I think we could easily help the reader by using hyphenation:

"Use Exclude Settings and Ignore-Files"

VS Code version: Code - Insiders 1.86.0-insider (f87fb292c3af22e51a7f5c628496cd8d6fd9ecd5, 2023-12-13T08:07:18.340Z)
OS version: Windows_NT x64 10.0.22621
Modes:


<!-- generated by issue reporter -->