sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rustdesk
Issue: After clicking on some menus, the menu disappears when you move the mouse away, and you cannot click on the options in the menu
Labels: bug

### Bug Description

When using iPad to control Windows 11, after clicking on some menus, the menu disappears when you move the mouse away, and you cannot click on the options in the menu. This is basically a bug that will inevitably occur.

### How to Reproduce

1. Control a win11 PC on ipad through Rustdesk with a mouse.
2. Click on the icon in picture below and move the mouse to the options. Please check the attached screenshots gif.
3. You will find the options disappear.



### Expected Behavior

The options should not disappear.

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

iPad OS 18.2 -> windows 11 23H2

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

1.3.6 -> 1.3.2

### Screenshots

![PixPin_2025-01-04_14-19-30](https://github.com/user-attachments/assets/a1755af6-c613-44c0-8824-89f5da61380b)


### Additional Context

_No response_
Repository: godot
Issue: [3.x] Scaling in windowed mode can crash the Linux Operating System
Labels: bug,platform:linuxbsd,crash

### Tested versions

Reproducible in the Godot 3.6.0 release, other versions untested.

### System information

OS: Linux Mint 22 Cinnamon GPU: Intel Corporation Alder Lake-UP3 GT2 [UHD Graphics] CPU: 12th Gen Intel© Core™ i5-1235U × 10

### Issue description

Viewports can cause the OS to slow down under certain circumstances, eventually freezing and/or crashing the entire OS and potentially corrupting the open project as a result.

I have not tested this on other operating systems or hardware, nor have I tested to see if there are other steps that can be taken to reproduce the issue.

### Steps to reproduce

1. Create an AspectRatioContainer with a typical 3D Viewport setup as its child.
2. Set AspectRatioContainer.ratio to 1.7778 and AspectRatioContainer.stretch mode to STRETCH_COVER (or anything besides STRETCH_FIT).
3. Set "display/window/stretch/mode" to 2d and "display/window/stretch/aspect" to Expand.
4. Launch the project in windowed mode, then scale the window as thin as you can and start moving it around. After a few seconds of slowing down the computer (most obvious when listening to audio) it will begin to freeze and then crash after about 5-10 seconds.

You can skip to step 4 when using the MRP.

### Minimal reproduction project (MRP)

[Viewport Crash.zip](https://github.com/user-attachments/files/18305837/Viewport.Crash.zip)
Repository: rust
Issue: Nested recursive enum with ManuallyDrop causes thread 'rustc' to overflow its stack
Labels: I-crash,A-debuginfo,T-compiler,C-bug,S-has-mcve

There seemed to be an issue with the type Composition<Conditional<T>> adding drop-check rules, so I added ManuallyDrop to get the program to compile. I also added the unpin impl as there was also an error regarding its implementation.

I tried this code:

```rust
use std::mem::ManuallyDrop;

pub enum Composition<T> {
    Conditional(ManuallyDrop<Conditional<T>>),
    Item(T),
}

impl <T> Unpin for Composition<T> {}

#[derive(Default)]
pub struct Conditional<T> {
    _condition: Vec<Composition<Condition<T>>>,
    _warrant: Vec<Composition<T>>,
}

pub enum Condition<T> {
    T(T),
}

fn main() {
    let _ = Conditional::<()>::default();
}
```


I expected wither for the program to run, or for the compiler to give the a similar error to when ManuallyDrop is removed: "overflow while adding drop-check rules for `Vec<Composition<T>>`"

Instead, the rustc thread overflowed its stack.

### Meta

`rustc --version --verbose`:
```
rustc 1.86.0-nightly (3f43b1a63 2025-01-03)
binary: rustc
commit-hash: 3f43b1a636738f41c48df073c5bcb97a97bf8459
commit-date: 2025-01-03
host: aarch64-apple-darwin
release: 1.86.0-nightly
LLVM version: 19.1.6
```

<!--
Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your
environment. E.g. `RUST_BACKTRACE=1 cargo build`.
-->
<details><summary>Backtrace</summary>
<p>

```
   Compiling overflow-issue v0.1.0 (/Users/wutter/dev/overflow-issue)

thread 'rustc' has overflowed its stack
fatal runtime error: stack overflow
error: could not compile `overflow-issue` (bin "overflow-issue")

Caused by:
  process didn't exit successfully: `/Users/wutter/.rustup/toolchains/nightly-aarch64-apple-darwin/bin/rustc --crate-name overflow_issue --edition=2024 src/main.rs --error-format=json --json=diagnostic-rendered-ansi,artifacts,future-incompat --diagnostic-width=80 --crate-type bin --emit=dep-info,link -C embed-bitcode=no -C debuginfo=2 -C split-debuginfo=unpacked --check-cfg 'cfg(docsrs,test)' --check-cfg 'cfg(feature, values())' -C metadata=2a6ba930726f09c1 -C extra-filename=-15d023de81aec2c9 --out-dir /Users/wutter/dev/overflow-issue/target/debug/deps -C incremental=/Users/wutter/dev/overflow-issue/target/debug/incremental -L dependency=/Users/wutter/dev/overflow-issue/target/debug/deps` (signal: 6, SIGABRT: process abort signal)```
```

</p>
</details>
Repository: transformers
Issue: Memory Access out of bounds in mra/cuda_kernel.cu::index_max_cuda_kernel()
Labels: bug

### System Info

* OS: Linux ubuntu 22.04 LTS
* Device: A100-80GB
* docker: nvidia/pytorch:24.04-py3
* transformers: latest, 4.47.0

### Who can help?

_No response_

### 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

## Reproduction
1. pip install the latest transformers
2. prepare the UT test enviroments by `pip install -e .[testing]`
3. `pytest tests/models/mra/test_modeling_mra.py`

## Analysis
There might be some memory access out-of-bound behaviours in CUDA kernel `index_max_cuda_kernel()`
https://github.com/huggingface/transformers/blob/main/src/transformers/kernels/mra/cuda_kernel.cu#L6C1-L58C2

Note that `max_buffer` in this kernel is `extern __shared__ float` type, which means `max_buffer` would be stored in shared memory.
According to https://github.com/huggingface/transformers/blob/main/src/transformers/kernels/mra/cuda_launch.cu#L24-L35, CUDA would launch this kernel with 
* gird size: `batch_size`
* block size: 256
* shared memory size: `A_num_block * 32 * sizeof(float)`

In case that `A_num_block` < 4, the for statement below might accidentally locate the memory out of `A_num_block * 32`, since num_thread here is 256, and threadIdx.x is [0, 255].
```
for (int idx_start = 0; idx_start < 32 * num_block; idx_start = idx_start + num_thread) {
```

Therefore, when threadblocks of threads try to access `max_buffer`, it would be wiser and more careful to always add `if` statements before to avoid memory access out of bounds.

So We suggest to add `if` statements in two places:
![捕获](https://github.com/user-attachments/assets/172271ec-31d8-4e4d-8827-0cc66fbdd9be)




### Expected behavior

UT tests should all pass!
Repository: godot
Issue: [3.x] Mono HTML5 exports can't use System.Net.Http due to missing dependency WebAssembly.Net.Http
Labels: bug,platform:web,topic:dotnet

### Tested versions

- Reproducible in: v3.6.stable.mono.official [de2f0f1]

### System information

Windows 11 64-bit, Chrome 131.0.6778.205

### Issue description

Many C# libraries have `System.Net.Http` as a dependency, most notably Firebase. On Web exports, C# uses a different implementation, provided via package `WebAssembly.Net.Http`, since browsers only allow requests via the `fetch` API rather than opening a raw socket.

However, exporting a web C# project which uses `System.Net.Http` as a dependency or sub-dependency crashes and logs the following messages to the console:
```
The following assembly referenced from .mono/assemblies/Debug/System.Net.Http.dll could not be loaded:
Assembly:   WebAssembly.Net.Http    (assemblyref_index=2)
Version:    1.0.0.0
Public Key: cc7b13ffcd2ddd51

The assembly was not found in the Global Assembly Cache, a path listed in the MONO_PATH environment variable, or in the location of the executing assembly (/.mono/assemblies/Debug/).

System.IO.FileNotFoundException: Could not load file or assembly 'WebAssembly.Net.Http, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51' or one of its dependencies.
File name: 'WebAssembly.Net.Http, Version=1.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'
   at System.Net.Http.HttpClient..ctor () <0x3986018 + 0x00002> in <filename unknown>:0
```

This issue is present since at least 2021, evident by these forum posts:
* [Missing dependency after HTML5 export](https://forum.godotengine.org/t/missing-dependency-after-html5-export/9929)
* [Created HTML5 can not be run, as WebAssembly cannot find System.Net.Http.HttpClient](https://forum.godotengine.org/t/created-html5-can-not-be-run-as-webassembly-cannot-find-system-net-http-httpclient/12404)


### Steps to reproduce

1. Export the attached Minimal Reproduction Project to the web
2. Run and observe the browser console (F12)

### Minimal reproduction project (MRP)

[GodotHTTPIssue.zip](https://github.com/user-attachments/files/18306077/GodotHTTPIssue.zip)
Repository: transformers
Issue: Reload Transformers imports
Labels: Good Second Issue,Feature request

### Feature request

It would be nice to have a transformers.clear_import_cache() or any other way to reset the dynamic imports of transformers.

### Motivation

Some people are having bugs after hacking on transformers [1](https://github.com/unslothai/unsloth/issues/1410), [2](https://github.com/unslothai/unsloth/issues/1499). Hacking on transformers [seems to be supported](https://huggingface.co/docs/transformers/how_to_hack_models)

### Your contribution

given some amount of guidance, I am willing to write a PR.
Repository: godot
Issue: [3.x] ViewportContainer + Viewport is distorted.
Labels: bug,topic:rendering

### Tested versions

Reproducable in Godot 3.6, not tested in any other version.

### System information

OS: Linux Mint 22 Cinnamon GPU: Intel Corporation Alder Lake-UP3 GT2 [UHD Graphics]

### Issue description

Viewports render a distorted image. The distortion is grid-like and most obvious with ViewportTexture filtering off.
Sorry for the sparse description, it's a very simple issue.
![Image](https://github.com/user-attachments/assets/508e3015-ed5b-431a-a484-0b573c3aac99)

### Steps to reproduce

1. Open MRP
2. Launch the project and scale the window. Notice how the distortion increases as you make it smaller or change the aspect ratio.

### Minimal reproduction project (MRP)

[Viewport Distortion.zip](https://github.com/user-attachments/files/18306154/Viewport.Distortion.zip)
Repository: godot
Issue: Having free() in a script in the scene tree will throw an error in exported game
Labels: bug,topic:gdscript

### Tested versions

Reproducible in 4.3 stable and 4.2.2 stable

### System information

Windows 11, macOS Ventura

### Issue description

If a script has free() anywhere in it (test.gd in this case) and is loaded into the scene tree via a node, the log will show the following error.

USER SCRIPT ERROR: Parse Error: Function "free()" not found in base self.
   at: GDScript::reload (res://test.gd:20)
ERROR: Failed to load script "res://test.gd" with error "Parse error".
   at: load (modules/gdscript/gdscript.cpp:2936)

It won't crash the exported game, but any node that has this and is added to the scene tree will just be added and not function. In the Editor, this runs normally with no issues or errors.

However, using free() in an unsafe line such as part of a "for loop" doesn't throw this error in the exported game. Example below:

```
for child in $SomeNode.get_children():
    child.free()
```

### Steps to reproduce

1. Create a new script for any Node
2. Put the free() method to be called anywhere in the script
3. Have a function that will add this node to the scene tree (it can even be in the main scene script itself)
4. Export the game and run it (be sure to have file logging on)
5. Check the logs to see the parse error

### Minimal reproduction project (MRP)

MRP can be recreated easily using the steps above.
Repository: flutter
Issue: Linux OnScreen keyboard don't always show up
Labels: a: text input,engine,a: accessibility,platform-linux,has reproducible steps,team-linux,found in release: 3.27,found in release: 3.28

### Steps to reproduce

In the Linux environment, the full screen is applied, and only the input box is required in the application. When I typed the first few times, the on-screen keyboard popped up normally, but after a flash, the on-screen keyboard never popped up again

### Expected results

Each time input box input, the on-screen keyboard can pop up normally

### Actual results

After an on-screen keyboard does not pop up normally, the on-screen keyboard will not appear again

### Code sample

await windowManager.ensureInitialized();
    const windowOptions = WindowOptions(
      center: true,
      fullScreen: true,
    );
    windowManager.waitUntilReadyToShow(windowOptions, () async {
      await windowManager.show();
    });

### Screenshots or Video

![企业微信截图_89af754a-67a0-42a2-881f-d78d90432086](https://github.com/user-attachments/assets/7e3ff4d0-5b2a-4c3c-b570-11a506d5ab33)
Looks like the on-screen keyboard went under my app

### Logs

_No response_

### Flutter Doctor output

Doctor summary (to see all details, run flutter doctor -v):
[!] Flutter (Channel stable, 3.19.6, on Ubuntu 20.04 LTS 5.4.0-204-generic, locale en_US.UTF-8)
    ! Upstream repository https://github.com/flutter/flutter.git is not the same as FLUTTER_GIT_URL
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, please use
      `flutter config --android-sdk` to update to that location.

[✗] Chrome - develop for the web (Cannot find Chrome executable at google-chrome)
    ! Cannot find Chrome. Try setting CHROME_EXECUTABLE to a Chrome executable.
[✓] Linux toolchain - develop for Linux desktop
[!] Android Studio (not installed)
[✓] VS Code (version 1.78.2)
[✓] Connected device (1 available)
[✓] Network resources

! Doctor found issues in 4 categories.
Repository: transformers
Issue: When gradient checkpointing is enabled, flash_attn_kwargs cannot be passed into the decoder_layer
Labels: bug

### System Info

transformers 4.47.1

### Who can help?

@ArthurZucker 

### 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

https://github.com/huggingface/transformers/blob/241c04d36867259cdf11dbb4e9d9a60f9cb65ebc/src/transformers/models/llama/modeling_llama.py#L896C1-L931C54
```python
for decoder_layer in self.layers[: self.config.num_hidden_layers]:
    if output_hidden_states:
        all_hidden_states += (hidden_states,)


    if self.gradient_checkpointing and self.training:
        layer_outputs = self._gradient_checkpointing_func(
            decoder_layer.__call__,
            hidden_states,
            causal_mask,
            position_ids,
            past_key_values,
            output_attentions,
            use_cache,
            cache_position,
            position_embeddings,
        )
    else:
        layer_outputs = decoder_layer(
            hidden_states,
            attention_mask=causal_mask,
            position_ids=position_ids,
            past_key_value=past_key_values,
            output_attentions=output_attentions,
            use_cache=use_cache,
            cache_position=cache_position,
            position_embeddings=position_embeddings,
            **flash_attn_kwargs,
        )
```

### Expected behavior

x
Repository: material-ui
Issue: [Collapse] Horizontal Collapse is twitching
Labels: bug 🐛,component: Collapse

### Steps to reproduce

Steps:
1. Open this link to live example: https://codesandbox.io/p/sandbox/transition-group-with-horizontal-collapse-2frjrp
2. Click on the "Add" button several times

### Current behavior

In some instances a strange twitching happens. This event stretches the page, hence why there is a scrollbar for a brief moment. The card has a full width for a split second, and then it goes back to 0 width and expands slowly.

### Expected behavior

The animation is smooth. There is no twitching, it starts from 0 width and expands as expected.

### Context

I'm trying to achieve [this](https://mui.com/material-ui/transitions/?srsltid=AfmBOoqGwt8xSCgjV5fzpeMoWXfPlto6YrORkAeJ208b9a4EiKS3S-jF#transitiongroup) exact scenario from the documentation but in a horizontal manner.

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>


**Search keywords**: horizontal, collapse, twitching, transition-group
Repository: ollama
Issue: Speed ten times slower than llamafile
Labels: bug

### What is the issue?

Llamafile is much faster on cpu than ollama, what takes ollama 33 minutes takes llamafile 3 minutes with the same model.
llamafile crashes unfortunately after reusing it and spins its wheels staying at 100% CPU for hours.

I'd rather use a stable ollama, but you must work on speed on CPU

### OS

Linux

### CPU

Intel
Repository: deno
Issue: Add support for arrays in OTEL attributes
Labels: bug,otel

Right now we support strings, bools, numbers, and bigints. We should also support homegeneous arrays of each of those types.
Repository: rust
Issue: List of trait implementations should be version-sorted
Labels: A-diagnostics,T-compiler,D-papercut

### Code

```Rust
// tests/ui/suggestions/issue-71394-no-from-impl.rs
```

### Current output

```Shell
error[E0277]: the trait bound `&[i8]: From<&[u8]>` is not satisfied
  --> $DIR/issue-71394-no-from-impl.rs:8:25
   |
LL |     let _: &[i8] = data.into();
   |                         ^^^^ the trait `From<&[u8]>` is not implemented for `&[i8]`
   |
   = help: the following other types implement trait `From<T>`:
             `[T; 10]` implements `From<(T, T, T, T, T, T, T, T, T, T)>`
             `[T; 11]` implements `From<(T, T, T, T, T, T, T, T, T, T, T)>`
             `[T; 12]` implements `From<(T, T, T, T, T, T, T, T, T, T, T, T)>`
             `[T; 1]` implements `From<(T,)>`
             `[T; 2]` implements `From<(T, T)>`
             `[T; 3]` implements `From<(T, T, T)>`
[...]
```

### Desired output

```Shell
error[E0277]: the trait bound `&[i8]: From<&[u8]>` is not satisfied
  --> $DIR/issue-71394-no-from-impl.rs:8:25
   |
LL |     let _: &[i8] = data.into();
   |                         ^^^^ the trait `From<&[u8]>` is not implemented for `&[i8]`
   |
   = help: the following other types implement trait `From<T>`:
             `[T; 1]` implements `From<(T,)>`
             `[T; 2]` implements `From<(T, T)>`
             `[T; 3]` implements `From<(T, T, T)>`
[...]
             `[T; 10]` implements `From<(T, T, T, T, T, T, T, T, T, T)>`
             `[T; 11]` implements `From<(T, T, T, T, T, T, T, T, T, T, T)>`
             `[T; 12]` implements `From<(T, T, T, T, T, T, T, T, T, T, T, T)>`
[...]
```

### Rationale and extra context

The existing sorting displays 10, 11, 12, before it displays 1, 2, 3. Lower numbers should be sorted before higher numbers. In addition to sorting in a more semantically correct fashion, this would also present the user with less complex possibilities first.

### Other cases

```Rust

```

### Rust Version

```Shell
Git commit 7349f6b50359fd1f11738765b8deec5ee02d8710
```

### Anything else?

_No response_
Repository: flutter
Issue: Need a Sliver Variant of `DragTarget`
Labels: c: new feature,framework,f: scrolling,c: proposal,P3,team-framework,triaged-framework

### Use case

A sliver variant of `DragTarget` would make it easier to implement advanced drag-and-drop workflows in scrollable, sliver-based layouts. This would simplify development for UIs that involve dynamic, interactive lists or grids within `CustomScrollView`.

eg:
```dart
CustomScrollView(
  slivers: [
    // ...
    SliverList.builder(...),

    DragTarget<String>(     // Does not work
      builder: (context, candidateData, rejectedData) {
        return SliverList.builder(
          itemCount: items.length,
          itemBuilder: (context, index) {
            return Text(items[index].name);
          },
        );
      },
    ),

    SliverList.builder(...),
    // ...
  ],
)
```

I asked this question on Stack Overflow but did not find a solution. You can view the question here: https://stackoverflow.com/questions/79304188/how-to-make-a-sliverlist-a-dragtarget-in-flutter

### Proposal

Introduce a  `SliverDragTarget` widget that can seamlessly integrate with `CustomScrollView` and other sliver-based layouts, allowing developers to apply drag-and-drop functionality to slivers directly
Repository: deno
Issue: Emphasize user code in stack traces
Labels: suggestion,testing

Creating a new issue after discussion in [#24002](https://github.com/denoland/deno/issues/24002#issuecomment-2561927997).

I’d like to propose a feature to improve readability when working with stack traces. Currently, assertion errors generate a verbose stack trace that includes both user code and internal library or runtime code. It can be challenging to quickly locate the lines relevant to my own logic amidst calls from the Deno standard library or third-party modules.

Failed assertions would be a good start for this feature, given stack traces are gnarly enough that a [flag was created to hide them](https://github.com/denoland/deno/issues/24002).

```
error: AssertionError: Values are not strictly equal.


    [Diff] Actual / Expected


-   5
+   3

  throw new AssertionError(message);
        ^
    at assertStrictEquals (https://jsr.io/@std/assert/1.0.10/strict_equals.ts:66:9)
    at toBe (https://jsr.io/@std/expect/1.0.10/_matchers.ts:29:5)
    at applyMatcher (https://jsr.io/@std/expect/1.0.10/expect.ts:223:13)
    at Proxy.<anonymous> (https://jsr.io/@std/expect/1.0.10/expect.ts:233:13)
    at checkQueueAndResults (file:///home/dandv/project/tests/common.ts:187:39) ⬅️
    at Object.runMicrotasks (ext:core/01_core.js:683:26)
    at processTicksAndRejections (ext:deno_node/_next_tick.ts:59:10)
    at runNextTicks (ext:deno_node/_next_tick.ts:76:3)
    at eventLoopTick (ext:core/01_core.js:182:21)
    at async Object.<anonymous> (file:///home/dandv/project/tests/unit.test.ts:349:7) ⬅️
```

# Proposal

– Highlight or visually distinguish user code in the stack trace, for example with a marker like ⬅️ (since bold and colors are already used)

– Either hide references to the Deno and library calls, or de-emphasize them (greyed out?) so they don’t obscure the code paths I’m actively debugging.
Repository: next.js
Issue: Page crashes and "Error: Connection closed." in  log
Labels: Navigation,Runtime

### Link to the code that reproduces this issue

https://github.com/Abhii5496/store-thing

### To Reproduce

visit : https://store-thing.netlify.app/products

just select any product , im using  Link tag 

https://store-thing.netlify.app/products/1
when i hard refresh at same url it works

### Current vs. Expected behavior

visit : https://store-thing.netlify.app/products

just select any product , im using  Link tag 

https://store-thing.netlify.app/products/1
when i hard refresh at same url it works

### Provide environment information

```bash
"next": "15.1.3",
    "react": "^19.0.0",
    "react-dom": "^19.0.0",
```


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

Navigation, Runtime

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

Vercel (Deployed)

### Additional context

next 15.1.3 version