sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react-native
Issue: [iOS] VoiceOver reads the placeholder in TextInput
Labels: Platform: iOS,Issue: Author Provided Repro,Component: TextInput,Needs: Attention,Needs: Version Info

### Description

When setting a `placeholder` in the `TextInput` field, VoiceOver reads the placeholder text. This causes problems when an accessibilityLabel is also provided.

Expected behaviour: Placeholder should not be read by a screen reader as it is just a visual component.

### Steps to reproduce

Try this sample code:

```
import React from 'react';
import {SafeAreaView, StyleSheet, TextInput} from 'react-native';

const TextInputExample = () => {
  const [text, onChangeText] = React.useState('');

  return (
    <SafeAreaView>
      <TextInput
      placeholder="text input"
      accessibilityLabel="text input"
        style={styles.input}
        onChangeText={onChangeText}
        value={text}
      />
    </SafeAreaView>
  );
};

const styles = StyleSheet.create({
  input: {
    height: 40,
    margin: 12,
    borderWidth: 1,
    padding: 10,
  },
});

export default TextInputExample;
```

### React Native Version

0.74.0

### Affected Platforms

Runtime - iOS

### Output of `npx react-native info`

```text
n/a
```


### Stacktrace or Logs

```text
n/a
```


### Reproducer

https://snack.expo.dev/eiduCgHeg-d8A6PLexqp2

### Screenshots and Videos

![IMG_F51B7AE11582-1](https://github.com/facebook/react-native/assets/35132816/cc977c4d-793d-4ae9-9d67-466931cd6f6c)
Repository: next.js
Issue: Next JS app built using output: 'export' not rendered properly
Labels: create-next-app,bug

### Link to the code that reproduces this issue

https://github.com/tusharvelingkar/static-export-bug

### To Reproduce

1. Create new nextjs app
2. Update next config to output as static site
3. Open the outputted page from out folder

### Current vs. Expected behavior

Current Output
![image](https://github.com/vercel/next.js/assets/154614065/ccb172f0-20c9-43e4-bf3b-77dea0181a0a)



Expected Output
![image](https://github.com/vercel/next.js/assets/154614065/6e1e70cd-e4f9-4302-8721-b93d2e104bfe)
Above output is when app run using dev mode

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP Thu Mar 14 14:20:09 EDT 2024
  Available memory (MB): 31893
  Available CPU cores: 8
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.12.1
Relevant Packages:
  next: 14.2.2 // Latest available version is detected (14.2.2).
  eslint-config-next: 14.2.2
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.5
Next.js Config:
  output: export
```


### Which area(s) are affected? (Select all that apply)

create-next-app

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

_No response_
Repository: tauri
Issue: [bug] Tauri builds but the app can't be installed
Labels: type: bug,platform: Linux,status: needs triage

### Describe the bug

After doing a `npm run tauri build`, I try to install the .deb file and it doesn't work. 
I've tried to build with the `create-tauri-app` project, without modifying anything except the `identifier`, and I've got the same error when trying to install the .deb file : 
```
dpkg-deb: error: file '/home/cledez@celad2.celad.com/Documents/tuto/test_tauri/src-tauri/target/release/bundle/deb/test-tauri_0.0.0_amd64.deb' is corrupt - bad archive header magic
dpkg: error processing archive /home/cledez@celad2.celad.com/Documents/tuto/test_tauri/src-tauri/target/release/bundle/deb/test-tauri_0.0.0_amd64.deb (--install):
 dpkg-deb --control subprocess returned error exit status 2
Errors were encountered while processing:
 /home/cledez@celad2.celad.com/Documents/tuto/test_tauri/src-tauri/target/release/bundle/deb/test-tauri_0.0.0_amd64.deb
```

For my project, executing the AppImage reads "files not found", but with the `create-tauri-app` example, the AppImage is working.

### Reproduction

`sh <(curl https://create.tauri.app/sh)`
```
✔ Project name · test_tauri
✔ Choose which language to use for your frontend · TypeScript / JavaScript - (pnpm, yarn, npm, bun)
✔ Choose your package manager · npm
✔ Choose your UI template · Angular - (https://angular.dev/)
```
`npm install`
`npm run tauri build`

### Expected behavior

After `npm run tauri build`, the .deb file would be installed with `sudo dpkg -i <path>`. 

### Full `tauri info` output

```text
[✔] Environment
    - OS: Ubuntu 22.04 X64
    ✔ webkit2gtk-4.0: 2.44.0
    ✔ rsvg2: 2.52.5
    ✔ rustc: 1.77.2 (25ef9e3d8 2024-04-09)
    ✔ cargo: 1.77.2 (e52e36006 2024-03-26)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-unknown-linux-gnu (default)
    - node: 20.12.0
    - npm: 10.5.2

[-] Packages
    - tauri [RUST]: 1.6.2
    - tauri-build [RUST]: 1.5.1
    - wry [RUST]: 0.24.8
    - tao [RUST]: 0.16.9
    - tauri-cli [RUST]: 1.5.12
    - @tauri-apps/api [NPM]: 1.5.4
    - @tauri-apps/cli [NPM]: 1.5.11

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist/test_tauri/browser
    - devPath: http://localhost:1420/
    - framework: Angular
    - bundler: Webpack
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: deno
Issue: Bug: Missing stdio pipes with `node:child_process` on Windows
Labels: bug,node compat

**Update:** This issue is now resolved on unix platforms (macOS and linux), but is not yet fixed on Windows.

---

Tried the current state of running `playwright` in Deno (see https://github.com/denoland/deno/issues/16899) and ran into an issue regarding the pipes set up for `node:child_process.spawn()`. The launcher code can be found here https://github.com/microsoft/playwright/blob/main/packages/playwright-core/src/utils/processLauncher.ts#L133

They expect to receive 5 streams to be set up, but we only set up the first three. I created a minimal reproduction out of that:

## Steps to reproduce

1. Create file `main.mjs` with these contents
  ```js
  import cp from "node:child_process";
  import process from "node:process";

  if (import.meta.url.endsWith("main.mjs")) {
    const child = cp.spawn(process.execPath, [import.meta.url], {
      stdio: ["ignore", "pipe", "pipe", "pipe", "pipe"],
    });

    console.assert(
      child.stdio.length === 5,
      `Expected stdio length to equal 5 but got ${child.stdio.length}`
    );
  }
  ```
2. Run `DENO_FUTURE=1 deno run -A main.mjs`

Can also be run in Node for comparison `node main.mjs`

Version: Deno 1.42.4 (git https://github.com/denoland/deno/commit/5294885a5a411e6b2e9674ce9d8f951c9c011988 2024-04-24)
Repository: next.js
Issue: redirects in next config different from version before and produce endless redirect loops
Labels: bug,Runtime

### Link to the code that reproduces this issue

https://codesandbox.io/p/sandbox/cocky-frost-dsd496

### To Reproduce

1. add this to config
async redirects() { return [ { source: '/app', destination: '/app/', permanent: false, }, ] } 

2. open /app and see your browser freeze or stop at some point do to endless redirects.


### Current vs. Expected behavior

Above example should redirect normally from /app to /app/, bur redirect loop happens instead

Redirect loop happens in redirect in new Version > 13.4.19. without our code changes from previous versions



### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Fri Mar 15 00:12:49 PDT 2024; root:xnu-10063.101.17~1/RELEASE_ARM64_T6020
  Available memory (MB): 32768
  Available CPU cores: 12
Binaries:
  Node: 21.7.3
  npm: 10.5.0
  Yarn: 1.22.22
  pnpm: N/A
Relevant Packages:
  next: 14.2.2 // Latest available version is detected (14.2.2).
  eslint-config-next: 14.2.2
  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)

Runtime

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

next dev (local), next build (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

I tested with the latest canary and still happens
Repository: deno
Issue: Bug: `glob no matches found` error with `deno task` and `npm-run-all`
Labels: node compat

Tried running the `build` command of the [Preact repository](https://github.com/preactjs/preact) and ran into this error.

## Steps to reproduce

1. Create a `package.json` file with these contents:
  ```json
  {
    "scripts": {
      "all": "npm-run-all foo:*",
      "foo:a": "echo 'a'",
      "foo:b": "echo 'b'"
    },
    "dependencies": {
      "npm-run-all": "^4.1.5"
    }
  }
  ```
2. Run `npm i`
3. Run `DENO_FUTURE=1 deno task all`

## Error

Deno:

```sh
$ deno task all 
Task all npm-run-all foo:*
glob: no matches found '/Users/marvinh/dev/test/deno-run-all/foo:*'
```

Node:

```sh
$ npm run all

> all
> npm-run-all foo:*


> foo:a
> echo 'a'

a

> foo:b
> echo 'b'

b
```

Version: Deno 1.42.4 (git https://github.com/denoland/deno/commit/5294885a5a411e6b2e9674ce9d8f951c9c011988 2024-04-24)
Repository: rust
Issue: Clean up implicit const promotion behavior
Labels: C-enhancement,T-lang,T-compiler,A-maybe-future-edition,A-const-prop,WG-const-eval

In https://github.com/rust-lang/rust/issues/80619 we tamed promotion to no longer cause fundamental problems around whether and when const-evaluation is allowed to fail. All our promoteds are now either infallible, or in guaranteed-live code.

However, as part of this, the rules for what we promote when became "a bit" obscure:
- `&(1/1)` gets promoted, but `&(1/(1+0))` does not. This is because when the RHS of the division is not a constant, it *may* be 0, and computing the promoted value would fail, so we can't promote this.
- Inside the initializer expression of a const/static, `&myfunction()` gets promoted *only if* the control flow graph of the initializer is a straight line until it reaches this point. (See [here](https://github.com/rust-lang/rust/pull/121557) for examples.) This is to ensure that we do not promote function calls in dead code.
- `&Enum::Variant` gets promoted even if other enum variants contain `UnsafeCell`, which is [borderline unsound](https://github.com/rust-lang/unsafe-code-guidelines/issues/493).

We should probably clean that up, by not promoting function calls or division/modulo ever (requiring a const block instead), and also not doing value-based reasoning for interior mutability during promotion. I assume this requires an edition transition. ([Here](https://github.com/rust-lang/rust/pull/122819) is a crater run that just tried to not promote function calls ever. Cargo itself doesn't even build any more so we did not get numbers.) Edition transitions for promotions are non-trivial; they would have to work something like this:
- Do not promote these things.
- Run borrowck.
- If that fails, try promoting them and see if that makes borrowck pass. If yes, issue a forward-compat lint.

That's non-trivial but would also help clean up a very organically grown (and hence confusingly-shaped) part of the language, and resolve some cases that are at least borderline unsound.

FWIW, for division/modulo, there is in theory an alternative -- we could treat them similar to what we do with overflows in add/sub/mul. This requires having a version of these operators that always succeeds. Then we can promote `&(a/b)` to using that kind of division, and additionally include a runtime check (outside the promoted) for division-by-0 (and for overflow due to division-by-int-min).

Cc @rust-lang/wg-const-eval
Repository: excalidraw
Issue: Prevent default for Ctrl+Z when inside WYSIWYG
Labels: bug,UX/UI,history

While in WYSIWYG, Ctrl+Z with an intention to undo in certain situations triggers default browser behavior - reopening the last closed tab.
Repository: excalidraw
Issue: Use Esc to cancel and capture currect selections
Labels: UX/UI,history

```[tasklist]
### Tasks
- [ ] Cancel of currently selected elements on ESC.
- [ ] Capture this change by the store so it could be undone/redone through the history.
```
Repository: excalidraw
Issue: Capture increments when moving element with arrows
Labels: UX/UI,history

```[tasklist]
### Tasks
- [ ] Similar to drag, capture changes in elements' position while moving them with arrows (debounced).
```
Repository: excalidraw
Issue: Unify `selectedElementIds` and `selectedLinearElement`
Labels: refactor,store

We are keeping these in sync and doing some workarounds inside and outside `Store`, it would be better if both would be unified under one property or in theory synced automatically (as a dependency).
Repository: node
Issue: Cross-compilation bug when compiling for ARM64 on a non-ARM64 host with Windows
Labels: windows,build

### Version

v21.7.3

### Platform

Microsoft Windows NT 10.0.20348.0 x64

### What steps will reproduce the bug?

Cross-compiling for  Windows ARM64 on a Windows x86_64 machine.

### What is the expected behavior? Why is that the expected behavior?

Should compile.

### What do you see instead?

Here's the log:
```
--snip--

  NodeWorker.cpp

  NodeTracing.cpp

  NodeRuntime.cpp

     Creating library out\Release\libnode.lib and object out\Release\libnode.exp

  libnode.vcxproj -> out\Release\\libnode.dll

  generate_node_def_action

  '"out\Release\gen_node_def_host.exe"' is not recognized as an internal or external command,
  operable program or batch file.

C:\Program Files\Microsoft Visual Studio\2022\Enterprise\MSBuild\Microsoft\VC\v170\Microsoft.CppCommon.targets(254,5): error MSB8066: Custom build for 'out\Release\\libnode.dll' exited with code 1. [D:\a\github\node\generate_node_def.vcxproj]
````

### Additional information

Compiling as a shared library with:
```batch
.\vcbuild.bat arm64 dll 
```
Repository: excalidraw
Issue: Revisit undo/redo with different `actionFinalize` cases
Labels: UX/UI,store,history

At the moment `actionFinalize` takes care of too many use cases (linear element, invisibly small elements, freedraw, etc.), resulting in subpar experience on some history actions (empty undos, dissappearring linear element handles due to `selectedElementId`, etc.).

```[tasklist]
### Tasks
- [ ] Revisit all the cases `actionFinalize` is doing
- [ ] Considering handling each case separetely with it's own `storeAction`
- [ ] Especially for invisibly small elements, consider if related cases are handled well by the store
```
Repository: PowerToys
Issue: [Github] AI duplicate issues bot: Issues missing in their comment
Labels: Issue-Bug,Needs-Triage,Area-GitHub workflow

### Microsoft PowerToys version

-

### Installation method

Other (please specify in "Steps to Reproduce")

### Running as admin

None

### Area(s) with issue?

General

### Steps to reproduce

The bot comments missing open issues that are very old.

For example issue #32600: The issue we deduplicate against is #26. But it is not listed in the bot comment.

I saw this behavior on other issues too.

### ✔️ Expected Behavior

The open issue is listed

### ❌ Actual Behavior

The open issue we dedup against is not listed.

### Other Software

_No response_
Repository: deno
Issue: Bug: `ERROR: Bad resource ID` running eslint in preact repo
Labels: bug,node compat

## Steps to reproduce

1. Clone https://github.com/preactjs/preact
2. Run `npm i`
3. Run `DENO_FUTURE=1 deno task lint`

## Error

```sh
DENO_FUTURE=1 deno-git task lint
Task lint run-s eslint tsc

> preact@10.20.2 eslint
> eslint src test debug compat hooks test-utils

Warning: React version not specified in eslint-plugin-react settings. See https://github.com/yannickcr/eslint-plugin-react#configuration .
ERROR: Bad resource ID
```

The React error message is expected, but the last one `ERROR: Bad resource ID` is not.

Version: Deno 1.42.4 (git https://github.com/denoland/deno/commit/5294885a5a411e6b2e9674ce9d8f951c9c011988 2024-04-24)
Repository: flutter
Issue: Support for YUV textures in fragment shader / Texture widget.
Labels: c: new feature,engine,P3,team-engine,triaged-engine

### Steps to reproduce

if I need commit nv12 raw data, I do not know how make a image from nv12

example C/C++, I can use GL_LUMINANCE for inner format.
```
shader.setImageSampler(0, image);
image ?= [NV12]
```

### Actual results

Can Flutter achieve this now?

### Logs

<details open>
<summary>Logs</summary>

```console

<!-- Paste your logs here -->

```

</details>


### Flutter Doctor output

<details open>
<summary>Doctor output</summary>

```console

<!-- Paste your output here -->

```

</details>
Repository: excalidraw
Issue: Refactor `Ordered` type away
Labels: refactor

`Ordered` type was introduced as part of the #7359 to distinguish between elements with a fractional index and those without. Based on the index we could perform reconciliation and order elements within the history actions.

But, in the ideal world, all elements within the scene should be ordered. The elements on the boundaries (to be inserted into the `Scene`) might or might not be ordered - locally inserted through the `updateScene`, remotely received elements, etc.

1. Try to refactor it away, and let the `ExcalidrawElement` be already ordered.
2. Ensure to emit element arrays with valid indices through the editor APIs, such as `onChange`, `restoreElements`, `getSceneElements*` etc.
3. Don't force the host apps to pass ordered elements inside the editor (i.e. within `updateScene`, `convertToExcalidrawElements`, etc.) as fractional indices are internal behavior (also due to non-breaking changes policy).
4. Consider adding `NonRestoredExcalidrawElement` for yet unrestored elements (note that it does not cover all cases of elements on the boundaries)
Repository: excalidraw
Issue: Introduce internal transaction-like API for element mutations
Labels: refactor

Within a certain action, we should have UoW-like possibilities for doing everything (in a transaction) or doing nothing (rollback to the previous state), so that we don't end up in an inconsistent state in between mutations.

1. Either perform all mutations or none (perform a rollback)
2. Don't allow mutating one element multiple times within the same transaction (~limit unnecessary version bumps)

The first step towards mimicking such behavior was done in #7348 as part of the `applyTo` logic, where either all increments are applied or none (while rolling back to `prevElements`). Check the details inside: https://github.com/excalidraw/excalidraw/blob/c1a3b89856acc0480e9a51f9943329857293fff3/packages/excalidraw/change.ts#L1069
Repository: flutter
Issue: Run devicelab_drone recipes with presubmit engine/monorepo artifacts
Labels: a: tests,team-infra,P3,triaged-infra

Dart wants to run devicelab performance tests on presubmit engine artifacts. Either running performance tests needs to be moved off of the devicelab_drone recipe, or the devicelab_drone recipe needs to understance engine/monorepo commit hash and builder_id input properties, and construct the correct artifact URLs and engine.version to use in framework when running tests.

Devicelab_drone currently supports LOCAL_ENGINE environment variable settings, for the same Dart presubmit testing discussed here. That support could be dropped once we support presubmit engine/monorepo artifact URLs.

This issue is for adding the required support to devicelab_drone, but if the plan is to move the performance testing to engine_v2/tester or engine_v2/tester_engine, an issue can be filed for that instead.
Repository: excalidraw
Issue: Introduce performance related tests
Labels: performance ⚡️

Introduce performance measures, so that we can keep pushing forward and ensure no regression in the future, especially in the hot paths. 

```[tasklist]
### Tasks
- [ ] Establish benchmarking infrastructure for unit/integration tests
- [ ] Analyse options on how to measure and detect complexity for certain hot paths
- [ ] Analyse options for testing on large data sets for certain hot paths
- [ ] Analyse options of fuzz testing for certain how paths
- [ ] Gradually unify performance across various user actions to keep as stable FPS as possible
```
Repository: godot
Issue: Black Flickering on Editor Axes
Labels: bug,topic:editor,confirmed,regression,topic:3d

### Tested versions

- Reproducible in 4.2.2
- Not Reproducible in 4.2.1

### System information

Godot v4.2.2.stable - macOS 14.1.1 - GLES3 (Compatibility) - Apple M1 - Apple M1 (8 Threads)

### Issue description

Certain actions (right-clicking, creating new resources in exports and adding nodes) cause the axes in the editor to flicker black.

### Steps to reproduce

- Create a new project
- Right-click on a node.

### Minimal reproduction project (MRP)

N/A
Repository: opencv
Issue: Inconsistent shape for ConcatLayer in function 'getMemoryShapes' while reading onnx model
Labels: bug,category: dnn (onnx)

### System Information

Python 3.10.10
General configuration for OpenCV 4.6, 4.x and 5.x  =====================================
 
Platform:
Host: Linux (Ubuntu 22.04) x86_64
CMake: 3.22.1
Configuration: Debug Release

### Detailed description

Detailed description

Issue came up while adding a new onnx model [dexiened](https://github.com/axinc-ai/ailia-models/tree/master/line_segment_detection/dexined) for edge detection sample in dnn

onnx model can be downloaded from [here](https://storage.googleapis.com/ailia-models/dexined/model.onnx)

Model works perfectly when inferred with onnx and opencv==4.6.0

I get the following error with opencv==4.9.0-dev and opencv==5.x during model loading:

```
ERROR:0@1.272] global onnx_importer.cpp:1032 handleNode DNN/ONNX: ERROR during processing node with 6 inputs and 1 outputs: [Concat]:(onnx_node!Concat_146) from domain='ai.onnx'
terminate called after throwing an instance of 'cv::Exception'
  what():  OpenCV(4.9.0-dev) opencv/modules/dnn/src/onnx/onnx_importer.cpp:1054: error: (-2:Unspecified error) in function 'handleNode'
> Node [Concat@ai.onnx]:(onnx_node!Concat_146) parse error: OpenCV(4.9.0-dev) opencv/modules/dnn/src/layers/concat_layer.cpp:108: error: (-201:Incorrect size of input array) Inconsistent shape for ConcatLayer in function 'getMemoryShapes'
```

Similar issues: https://github.com/opencv/opencv/issues/24030 , https://github.com/opencv/opencv/issues/19416

### Steps to reproduce

Here is the inference snippet: 
```python
        session = cv.dnn.readNetFromONNX(args.onnxmodel)
        # Load and process the image using DexiNed model
        orig_img = cv.imread(cv.samples.findFile(args.input))
        # Prepocess the image
        img = preprocess(orig_img)
        
        inp = cv.dnn.blobFromImage(img, swapRB=False, crop=False)
    
        session.setInput(inp)

        out = session.forward()
```


### Issue submission checklist

- [X] I report the issue, it's not a question
- [X] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [X] I updated to the latest OpenCV version and the issue is still there
- [X] There is reproducer code and related data files (videos, images, onnx, etc)