sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react
Issue: Bug: React 19 Build Error Report
Labels: Status: Unconfirmed

# React 19 Build Error Report

## React version
I'm using React 19 

## Steps To Reproduce

1. First, I cloned the React 19 source code from its official repository using the standard git clone command.

2. After that, I navigated to the cloned directory in the terminal and ran the yarn install command to install all the necessary dependencies for the project.

3. Then, I executed the yarn run build command to start the build process of the React 19 source code.
However, during the build process, an error occurred. The detailed error message is as follows:

<img width="1099" alt="image" src="https://github.com/user-attachments/assets/16ef52c3-286e-45f0-9aad-75ce7e4582a7" />


## Link to code example
Since it's the React 19 source code itself that I'm building, I'm unable to provide a separate external code example link at the moment. The error occurs during the standard build process of the cloned React 19 source code following the steps mentioned above.

## The current behavior
When running the yarn run build command after cloning the code and installing dependencies, the build process fails with the SyntaxError shown above. Specifically, the rollup-plugin-flow-remove-types plugin encounters an issue while parsing the react-dom-client.development.js file, deeming an expression at line 68, column 5 as invalid. This halts the entire build process for React 19, preventing the successful generation of the expected build output.

## The expected behavior
The expected behavior is that when I follow these steps (cloning the code, installing dependencies, and running yarn run build), the build process for React 19 should complete without any errors. The rollup-plugin-flow-remove-types plugin should be able to correctly parse the react-dom-client.development.js file and perform its intended operations smoothly, allowing the build to finish successfully and produce the necessary files for React 19 as intended.
Repository: opencv
Issue: Null pointer dereference
Labels: category: g-api / gapi

Hi all,
This is Qianxin CodeSafe Team, we found a suspicious issue,
Suppose 'd' < 'n_detections',then entry into circulation at
https://github.com/opencv/opencv/blob/6a0affdbcea8c0048fd82264086678acb0907c40/modules/gapi/src/3rdparty/vasot/src/components/ot/mtt/objects_associator.cpp#L138
Suppose't' < 'n_tracklets',then entry into circulation at
https://github.com/opencv/opencv/blob/6a0affdbcea8c0048fd82264086678acb0907c40/modules/gapi/src/3rdparty/vasot/src/components/ot/mtt/objects_associator.cpp#L140
Assume that the value of tracking_per_class_ is false at 
https://github.com/opencv/opencv/blob/6a0affdbcea8c0048fd82264086678acb0907c40/modules/gapi/src/3rdparty/vasot/src/components/ot/mtt/objects_associator.cpp#L141
Dereference null pointer "(tracklets[t]->GetRgbFeatures())" at
https://github.com/opencv/opencv/blob/6a0affdbcea8c0048fd82264086678acb0907c40/modules/gapi/src/3rdparty/vasot/src/components/ot/mtt/objects_associator.cpp#L146
which GetRgbFeatures() is defined at \opencv-4.9.0\modules\gapi\src\3rdparty\vasot\src\components\ot\mtt
https://github.com/opencv/opencv/blob/6a0affdbcea8c0048fd82264086678acb0907c40/modules/gapi/src/3rdparty/vasot/src/components/ot/tracklet.cpp#L100
https://github.com/opencv/opencv/blob/6a0affdbcea8c0048fd82264086678acb0907c40/modules/gapi/src/3rdparty/vasot/src/components/ot/tracklet.cpp#L101
Therefore,this results in a null point dereference
Repository: tauri
Issue: [feat] Add `TAURI_SIGNING_PUBLIC_KEY` environment variable
Labels: type: feature request

### Describe the problem

Currently, I cannot specify my public signing key from an environment variable, and I have to hard-code it in `tauri.conf.json`.

### Describe the solution you'd like

I would like to set the public signing key via a `TAURI_SIGNING_PUBLIC_KEY` environment variable.

### Alternatives considered

I have considered dynamically generating a custom `tauri.conf.json` during build, but that seems unnecessarily excessive.

### Additional context

_No response_
Repository: transformers
Issue: Any plans to add AIMv2 in the model?
Labels: New model

### Model description

Is there a plan to add AIMv2 https://huggingface.co/collections/apple/aimv2-6720fe1558d94c7805f7688c as part of Huggingface Model? AIMv2 showed better performance than SigLIP. I think it will be helpful for the community to have AIMv2 in Huggingface Model.



### Open source status

- [X] The model implementation is available
- [X] The model weights are available

### Provide useful links for the implementation

Model implementation: https://github.com/apple/ml-aim
Model weights: https://huggingface.co/collections/apple/aimv2-6720fe1558d94c7805f7688c
Repository: PowerToys
Issue: [File Management :: Peek] change the DEFAULT activation short cut.
Labels: Needs-Triage

### Description of the new feature / enhancement

`Ctrl-space` is widely used as switching IME (input method) (particularly on Windows), apps should never use such shortcut as default.

Making `Ctrl-space` as the default is unthoughtful and ignorant.


### Scenario when this would be used?

always

### Supporting information

At least let user decide if he/she like to keep the `Ctrl-space` assignment, or detect the current setting for IME and use a fallback shortcut.

If you are going to implement this, please also aware that some user are used to `ctrl-space` and don't want it being changed. A better solution is change the default for new installations, and ask existing users if they want keep the 'ctrl-space' assignment.

Also, developers may prevent user from setting `ctrl-space`, if they read IME settings (from registry or somewhere it is stored) and find a conflict.
Repository: PowerToys
Issue: Progress bar disappears
Labels: Issue-Bug,Product-Settings,Needs-Triage

### Microsoft PowerToys version

0.0.0

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

General

### Steps to reproduce


1: ![Image](https://github.com/user-attachments/assets/a6534c3b-3e2f-4985-a9b6-94f14cce7c1c)

2: ![Image](https://github.com/user-attachments/assets/533bc6ab-f699-4e97-b861-d6036aa171f8)

3: ![Image](https://github.com/user-attachments/assets/90101d01-dfce-461c-8dd7-d4a92ab0b851)

### ✔️ Expected Behavior

The update status should not be reset (the progress bar should always be visible after it appears while the update is being downloaded) after switching to any other tab.

### ❌ Actual Behavior

The update status is reset (the progress bar disappears) after the download starts and then you switch to any other tab.

### Other Software

_No response_
Repository: vscode
Issue: Formatting changes ending on \r result in an extra new line
Labels: info-needed

<!-- ⚠️⚠️ 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. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 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.96
- OS Version: Windows 10

Steps to Reproduce:

1. Install the clangd extension 
2. Follow the steps from https://github.com/clangd/vscode-clangd/issues/759 :

Config:
````
IncludeBlocks: Regroup
SortIncludes: 'true'
````
The code:
````
#include "a.h"
#include "c.h"
#include "b.h"

using namespace NS;
````
Each time you format using clangd, a new line is added before the using namespace. I checked if I can remove the \r from the replacement in the formatting code, though it breaks other stuff while doing so. (clang-format.exe now reformats as it tries to remove the \r)

According to the maintainers of the clangd extension it is VS Code that applies these changes to the source.
Repository: flutter
Issue: [CI] LUCI `butlr` timeout on successful build 
Labels: team-infra,P2,triaged-infra

### Type of Request

bug

### Infrastructure Environment

LUCI, engine builds.

### What is happening?

1. https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20mac_ios_engine/38769/overview hangs for 4 hours.
2. https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20linux_host_engine/39846/overview `collect builds|collect|wait` takes 20 minutes
3. https://ci.chromium.org/ui/p/flutter/builders/try/Linux%20linux_host_engine/39844/overview `collect builds|collect|wait` takes 20 minutes.
4. https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20mac_ios_engine/38775/overview `collect builds|collect|wait` takes 12 minutes.
5. https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20mac_ios_engine/38772/overview `collect builds|collect|wait` takes 10 minutes.
6. https://ci.chromium.org/ui/p/flutter/builders/try/Windows%20windows_host_engine/37454/overview `collect builds|collect|wait` takes 32 minutes.
4. https://ci.chromium.org/ui/p/flutter/builders/try/Mac%20mac_host_engine/39375/overview `collect builds|collect|wait` takes 44 minutes and failed.

![image](https://github.com/user-attachments/assets/c20408ae-83de-49c7-b22e-433b60ba9c0f)

### Expected results

Maybe not waiting for so long?
Repository: vscode
Issue: Snippets Snippets
Labels: feature-request,snippets

Currently snippets files don't have snippets for snippets syntax

Actual:
![Image](https://github.com/user-attachments/assets/3e5b06c3-0a8a-4d3c-afb0-016f8914227b)


Expected:
![Image](https://github.com/user-attachments/assets/12e196e9-5103-4307-bb32-3480d245a437)

https://code.visualstudio.com/docs/editor/userdefinedsnippets#_snippet-syntax

PR https://github.com/microsoft/vscode/pull/236675
Repository: next.js
Issue: Next.js+ React 19 incompatible with the code that was precompiled using react compiler
Labels: Runtime,linear: next

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/frosty-bird-xx8pz9

### To Reproduce

Import components from packages precompiled using the babel-plugin-react-compiler targeting React 19.
Build and run a Next.js project using the app directory and the precompiled dependencies.

<img width="784" alt="Screenshot 2024-12-20 at 16 54 52" src="https://github.com/user-attachments/assets/64809865-ec7a-4715-b72d-793df39c52f0" />


### Current vs. Expected behavior

#### Expected

* Next js works well with libraries precompiled with compiler
* The Next.js project builds and runs without errors during prerendering or runtime.

#### Current behavior

* Build errors during prerendering in the Next.js project.
* Runtime errors in react-compiler-runtime.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Thu Oct 10 21:02:26 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T8122
  Available memory (MB): 24576
  Available CPU cores: 8
Binaries:
  Node: 23.3.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: 9.15.0
Relevant Packages:
  next: 15.1.2
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.2
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)

### Additional context

I believe it's because nextjs isn't really using stable react build.
Repository: transformers
Issue: Default value for mean_resizing in resize_token_embeddings should be False
Labels: bug

### System Info

transformers>=4.46

### Who can help?

@Arthur

### Information

- [ ] The official example scripts
- [ ] My own modified scripts

### Tasks

- [ ] An officially supported task in the `examples` folder (such as GLUE/SQuAD, ...)
- [ ] My own task or dataset (give details below)

### Reproduction

When running resize_token_embeddings with additional tokens

### Expected behavior

It is much slower to run resize_token_embeddings with mean_resizing=True.
Maybe it's because nowadays token embedding size became much larger than before (like gemma2, qwen2, ...).

So I think the default value for mean_resizing in resize_token_embeddings should be False now,
or implementation has to be fix to keep resizing speed as before.

Note: Maybe it happens if I'm using deepspeed stage3, but I didn't thoroughly investigate that.
Repository: godot
Issue: [TextServer] Some texts are shaped accidently when use system font
Labels: bug,topic:gui

### Tested versions

- Reproducible in: v4.3.stable, v4.4.dev.mono.custom_build [89001f91d] 

### System information

Godot v4.4.dev.mono (89001f91d) - Windows 11 (build 22631) - System Locale: `zh_CN`

### Issue description

Input Chinese texts `工具系统，` and `经济系统，` and see shaped text in editor and runtime:

| Expected, Editor | Unexpected, Runtime |
|--------|--------|
| ![Image](https://github.com/user-attachments/assets/a7a2c5db-0e27-4de0-8637-c9be6b5f0cc3) | ![Image](https://github.com/user-attachments/assets/75e46d37-f05b-48e2-abb4-fa1fa88bd5d2) |

1. When the characters `济` and `系` are combined, `系` is accidentally distorted.
2. It also affects the comma at the end (which should be at the bottom left).
3. It only happens at runtime and with fallback system fonts. Behaves normally in the editor or when specifying custom fonts.

### Steps to reproduce

N/A

### Minimal reproduction project (MRP)

[TextShapeIssue.zip](https://github.com/user-attachments/files/18209174/TextShapeIssue.zip)

Note: This may not be consistent due to differences in system region or language.
Repository: godot
Issue: Buttons in tree jiggles when scrolling horizontally
Labels: bug,topic:gui

### Tested versions

Godot v4.4.dev7

### System information

Fedora Linux 40 (KDE Plasma) on Wayland - X11 display driver, Multi-window

### Issue description

Buttons in tree jiggles when scrolling horizontally 

https://github.com/user-attachments/assets/7f4627bc-dc0d-4d1b-8a48-023a32606e7e


### Steps to reproduce

Scroll horizontally in scene tree

### Minimal reproduction project (MRP)

[jiggle.zip](https://github.com/user-attachments/files/18209281/jiggle.zip)
Repository: godot
Issue: Shader editing window issues, vanishing boxes and blinking windows
Labels: bug,topic:editor,topic:shaders

### Tested versions

was having issues with it in 4.3 and thought maybe updating to 4.4 would fix, it did not

### System information

Godot v4.4.dev7 - Windows 10 (build 19044) - Multi-window, 1 monitor - OpenGL 3 (Compatibility) - Intel(R) HD Graphics 620 (Intel Corporation; 24.20.100.6025) - Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4 threads)

### Issue description

Godot v4.4.dev7 - Windows 10 (build 19044) - Multi-window, 1 monitor - OpenGL 3 (Compatibility) - Intel(R) HD Graphics 620 (Intel Corporation; 24.20.100.6025) - Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4 threads)

### Steps to reproduce

I am new to this so please be patient with my lack of CS lingo
-gpu particles 3d node
-process material -new particle process material
-drawpass prism mesh
-accelerations gravity -0.1
-set to single particle
-geometry new shader material
-shader: new shader
-visual shader
-flags enable unshaded
-new node on shader edit, particle color
-connect particle color to albedo

result:![Image](https://github.com/user-attachments/assets/72d3c11e-508b-4bbd-9ac9-626025141f1d)



### Minimal reproduction project (MRP)

I tried to reproduce this in a fresh project following identical steps, and it didn't recreate. The project included doesn't have many files in it, but I don't know which ones are causing the issue. I am sorry if i did something wrong in the bug reporting process

[bug.zip](https://github.com/user-attachments/files/18209496/bug.zip)
Repository: godot
Issue: Transparent + always on top + maximised = freeze browsers like chrome, firefox, opera
Labels: bug,platform:web

### Tested versions

- Reproducible with 4.3.stable and 4.4.dev6


Tested with:
- Firefox 133.0
- Chrome 131.0.6778.109
- Brave v1.73.101
- Opera

Not tested on:
Linux / macOS / safari

### System information

Windows 10.0.22631 - Godot 4.3.stable - Forward+/mobile/compatibility - Intel Iris Xe Graphics

### Issue description

I'm working on a widget-like game, meaning transparent + always on top + maximised. The goal is to be able to allow using other softwares while the game runs on top.
For most softwares, everything is working perfectly. Godot works like a charm, windows no problem, I can drag windows, reduce, maximise, type etc...
But when opening a browser, the content of the browser window freezes, and does not get updated, except by system signals, like moving the window around. The "OS" part of the window is fine (minimize, maximise, close, drag window), but what is displayed in the browser does not get updated
![Image](https://github.com/user-attachments/assets/5868f143-9a24-46fe-92fa-099276188b0d)

Notes: 
- there is no issue with microsoft edge
- there is no issue when changing to "windowed" mode

### Steps to reproduce

- create a project, with transparent + always on top + maximised settings
- in the main scene script, use DisplayServer.window_set_mouse_passthrough to allow clicking on programs on the background
- open a browser
- try and fail clicking on buttons, scrolling
- move the window around, see the image being updated

### Minimal reproduction project (MRP)

[issue_with_transparent_app.zip](https://github.com/user-attachments/files/18209493/issue_with_transparent_app.zip)
Repository: three.js
Issue: 3MF Production Extension support
Labels: Loaders

### Description

The 3MF loader does not currently load models that use the [3MF production extension](https://github.com/3MFConsortium/spec_production/blob/master/3MF%20Production%20Extension.md).

### Solution

When a 3MF file using the extension is loaded, It would be great to be able to successfully load and display them, even if all the production features were ignored. Currently nothing is loaded. 

### Alternatives

No alternatives that I can think of, other than asking users to save files without the extension, but that's not ideal in my application, which is based around 3d print models.

### Additional context

I need to look into it a bit to see exactly *how* it fails, and I might be able to spend some time on this soon, but I'm opening this in case anyone has already done it, is planning to, or already knows how to.
Repository: PowerToys
Issue: Shortcut of PT Run stops working
Labels: Issue-Bug,Product-PowerToys Run,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.87.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

After the upgrade when I try to launch any application as Admin (example Visual Studio), it doesn't launch it, and subsequent call to PT Run won't work, either by shortcut or even in the PT button for the effect.

![Image](https://github.com/user-attachments/assets/aa8a8328-07f5-4e0f-912a-ffdedc2aaac2)


### ✔️ Expected Behavior

PT Run to work as expected

### ❌ Actual Behavior

PT Run fails lauching app's in Admin mode, and after the first attempt, PT Run also fails to run and search does not open.

### Other Software

_No response_
Repository: rust
Issue: Polonius fails to infer lifetimes of borrows
Labels: C-bug,NLL-polonius,T-types

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code:

```rust
struct Foo([u8; 10]);

impl Foo {
    fn read_non_empty<'c, P>(&'c mut self) -> P
    where
        P: serde::Deserialize<'c> + std::string::ToString,
    {
        loop {
            let b: P = self.read();
            if !b.to_string().is_empty() {
                return b;
            }
        }
    }

    fn read<'c, P>(&'c mut self) -> P
    where
        P: serde::Deserialize<'c>,
    {
        unimplemented!();
    }
}
```

I expected to see this happen: Compilation to succeed.

Instead, this happened: Got an error:

```rust
❯  RUSTFLAGS='-Zpolonius' cargo +nightly c --tests
    Checking tmp-scdnga v0.1.0 (/home/zeenix/.cache/cargo-temp/tmp-sCDnga)

error[E0499]: cannot borrow `*self` as mutable more than once at a time
 --> src/main.rs:9:24
  |
4 |     fn read_non_empty<'c, P>(&'c mut self) -> P
  |                       -- lifetime `'c` defined here
...
9 |             let b: P = self.read();
  |                        ^^^^-------
  |                        |
  |                        `*self` was mutably borrowed here in the previous iteration of the loop
  |                        argument requires that `*self` is borrowed for `'c`

For more information about this error, try `rustc --explain E0499`.
error: could not compile `tmp-scdnga` (bin "tmp-scdnga" test) due to 1 previous error
```

If I modify the code to not use a loop, I still get the same:

```rust
    fn read_non_empty<'c, P>(&'c mut self) -> P
    where
        P: serde::Deserialize<'c> + std::string::ToString,
    {
        {
            let b: P = self.read();
            if !b.to_string().is_empty() {
                return b;
            }
        }

        {
            let b: P = self.read();
            if !b.to_string().is_empty() {
                return b;
            }
        }

        unimplemented!();
    }
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.85.0-nightly (9e136a30a 2024-12-19)
binary: rustc
commit-hash: 9e136a30a965bf4e63f03095c57df7257bf96fd6
commit-date: 2024-12-19
host: x86_64-unknown-linux-gnu
release: 1.85.0-nightly
LLVM version: 19.1.6
```