sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Trait bound order-dependent type errors using non_lifetime_binders
Labels: A-trait-system,T-compiler,C-bug,S-has-mcve,F-non_lifetime_binders

<!--
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:

```rs
#![feature(non_lifetime_binders)]

pub trait Trait1 {
    type Target;
    type This<T>: for<U> Trait1<This<U> = Self::This<U>> + Trait1<This<Self::Target> = Self>;
    
    fn cast<T>(self) -> Self::This<T>;
}

pub trait Trait2 {
    type Target;
    type This<T>: Trait2<This<Self::Target> = Self> + for<U> Trait2<This<U> = Self::This<U>>;
    
    fn cast<T>(self) -> Self::This<T>;
}

fn use1<T: Trait1>(val: T) -> T {
    val.cast::<()>().cast::<T::Target>()
}

fn use2<T: Trait2>(val: T) -> T {
    val.cast::<()>().cast::<T::Target>()
}
```
[playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=5508dab7e0468ebe37bd1974b2cec86b)

I expected to see this happen: Both versions of the trait to behave the same

Instead, this happened: One version works as expected, succeeding, but the other has a Mismatched Type error

Other details: When using `-Znext-solver`, *both* code blocks error out with the same message:
```
error[E0284]: type annotations needed: cannot satisfy `<<T as Trait2>::This<()> as Trait2>::This<<T as Trait2>::Target> == T`
  --> src\lib.rs:22:5
   |
22 |     val.cast::<()>().cast::<T::Target>()
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ cannot satisfy `<<T as Trait2>::This<()> as Trait2>::This<<T as Trait2>::Target> == T`
```

### 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.80.0-nightly (98489f248 2024-06-06)
binary: rustc
commit-hash: 98489f2487465f3765e5dd28d7305ebfd40f0865
commit-date: 2024-06-06
host: x86_64-pc-windows-msvc
release: 1.80.0-nightly
LLVM version: 18.1.7
```
Repository: tauri
Issue: [bug] backdrop blur not working when enable window transparent. 
Labels: type: bug,status: needs triage

### Describe the bug

https://github.com/tauri-apps/tauri/assets/45007226/4deeb391-4dfe-4d31-935b-99faad4c69d8

Mica effect depends on the window transparent feature. 


### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Windows 10.0.22631 X64
    ✔ WebView2: 125.0.2535.92
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.76.0 (07dca489a 2024-02-04)
    ✔ cargo: 1.76.0 (c84b36747 2024-01-18)
    ✔ rustup: 1.27.0 (bbb9276d2 2024-03-08)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (overridden by 'C:\Users\Han\Desktop\Publish\publish\rust-toolchain.toml')
    - node: 20.11.1
    - yarn: 4.2.2
    - npm: 10.2.4
    - bun: 1.1.0

[-] Packages
    - tauri [RUST]: 2.0.0-beta.20
    - tauri-build [RUST]: 2.0.0-beta.16
    - wry [RUST]: 0.40.0
    - tao [RUST]: 0.28.0
    - @tauri-apps/api : 2.0.0-beta.12
    - @tauri-apps/cli [NPM]: 2.0.0-beta.18

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../../packages/desktop/dist
    - devUrl: https://localhost:3000/
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: PowerToys
Issue: File Explorer preview cdr files
Labels: Idea-Enhancement,Product-File Explorer

### Description of the new feature / enhancement

To bee able to see cdr files without opening them

### Scenario when this would be used?

I have a lot of files in this format and it is time consuming to open one and one

### Supporting information

![image](https://github.com/microsoft/PowerToys/assets/7733677/8af14bbc-cd86-4acb-bc5f-8910dc1b443b)
Repository: react-native
Issue: `maxLength` of TextInput does not work when value is changed after state update
Labels: Component: TextInput,Needs: Triage :mag:

### Description

`maxLength` of Text Input is not working when value is changed after state update. It works as expected when input is given with keyboard.
`<TextInput
style={styles.textInput}
value={description}
maxLength={10}
onChangeText={text => setDescription(text)}
        />`

### Steps to reproduce

1. Set `maxLength` of TextInput to any non zero number
2. Store any text in state
3. Use text stored in state as value in TextInput
4. Update the state with text length greater than `maxLength`
5. TextInput will have text which has length greater than given `maxLength`

### React Native Version

0.74.2

### Affected Platforms

Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 13.5.1
  CPU: (10) arm64 Apple M1 Max
  Memory: 73.36 MB / 32.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.12.0
    path: ~/.nvm/versions/node/v18.12.0/bin/node
  Yarn:
    version: 3.6.4
    path: /opt/homebrew/bin/yarn
  npm:
    version: 8.19.2
    path: ~/.nvm/versions/node/v18.12.0/bin/npm
  Watchman: Not Found
Managers:
  CocoaPods:
    version: 1.14.3
    path: /Users/kunal.chavhan/.rvm/gems/ruby-3.2.2/bin/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: Jellyfish 2023.3.1 Patch 2 Jellyfish 2023.3.1 Patch 2
  Xcode:
    version: 15.0/15A240d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.10
    path: /usr/bin/javac
  Ruby:
    version: 3.2.2
    path: /Users/kunal.chavhan/.rvm/rubies/ruby-3.2.2/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.2.0
    wanted: 18.2.0
  react-native:
    installed: 0.74.2
    wanted: 0.74.2
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: true
  newArchEnabled: false
```


### Stacktrace or Logs

```text
NA
```


### Reproducer

https://github.com/kunalchavhan/rn-textinput-maxlength-reproducer

### Screenshots and Videos


https://github.com/facebook/react-native/assets/61144478/4a377ec3-e60a-46ad-b54d-c6362ebd8622
Repository: godot
Issue: "ERROR: snd_rawmidi_read error: No such device" When disconnecting midi device
Labels: bug,platform:linuxbsd,topic:audio

### Tested versions

Reproducible all the way back to Godot_v3.1-stable_x11, when the MIDIDriver was added in [this commit](https://github.com/godotengine/godot/commit/7a5f9fc08ea4f25cd20e743a9a1ef5566246cf2c#diff-4f2d6538b8ef51480a1adb209eb416ced72e3b4917abd8417e13010beaef0888)

Bug only effects Linux system where Godot uses the ALSA midi driver 

### System information

Godot v4.2.2.stable unknown - EndeavourOS #1 SMP PREEMPT_DYNAMIC Wed, 12 Jun 2024 20:17:17 +0000 - X11 - GLES3 (Compatibility) - NVIDIA GeForce RTX 3060 (nvidia; 550.90.07) - Intel(R) Xeon(R) CPU E3-1271 v3 @ 3.60GHz (8 Threads)

### Issue description

After opening midi ports using ```OS.open_midi_inputs()``` then disconnecting a midi device, the following error will be spammed in the terminal and editor debugger tab

```
ERROR: snd_rawmidi_read error: No such device
   at: read_in (drivers/alsamidi/midi_driver_alsamidi.cpp:147)
```


Also tested on ```Godot v4.2.2.stable - macOS 11.7.10 - GLES3 (Compatibility) - Intel Iris OpenGL Engine - Intel(R) Core(TM) i5-4278U CPU @ 2.60GHz (4 Threads)```
With no issue, so this appears to only affect the ALSA midi driver

### Steps to reproduce

Run the project below, or use the code:
```gdscript
func _ready() -> void:
	OS.open_midi_inputs()
```
Then disconnect a midi device from you system



### Minimal reproduction project (MRP)

v4.2.2.stable: [Midi Device Disconnect Error.zip](https://github.com/user-attachments/files/15845983/Midi.Device.Disconnect.Error.zip)
Repository: PowerToys
Issue: Key map🗺️ on display 💻️for multiple languages🔠 inputs⌨️
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

I use multiple methods to input text onto my PC. I must memorise which key to push to input a certain letter or character. However, memorising keymaps is really difficult for me. 

I would like a feature that shows a keymap for the input method when I am typing.

For example, when I am using a Greek keyboard, I want the first image below to be shown on the display.
When I am using Korean keyboard, I want the second image below to be shown on the display.

![b53ea55a-3d5b-443a-b651-bbefe637b34e](https://github.com/microsoft/PowerToys/assets/38034251/446ba2eb-126c-4157-a571-9fc3a3c7afdb)
![ab8e65d2-59e8-454b-b5f0-643d5b51a165](https://github.com/microsoft/PowerToys/assets/38034251/2cbc8f94-75c9-4caa-8b2e-02c091e5dbe9)
![image](https://github.com/microsoft/PowerToys/assets/38034251/39962d64-4811-401e-acba-7bf2ebaca81a)




### Scenario when this would be used?

When I am using a Greek keyboard, I want the first image below to be shown on the display.
When I am using a Chinese Cangjie keyboard, I want the second image below to be shown on the display.
When I am using a Korean keyboard, I want the third image below to be shown on the display.

![b53ea55a-3d5b-443a-b651-bbefe637b34e](https://github.com/microsoft/PowerToys/assets/38034251/446ba2eb-126c-4157-a571-9fc3a3c7afdb)
![ab8e65d2-59e8-454b-b5f0-643d5b51a165](https://github.com/microsoft/PowerToys/assets/38034251/2cbc8f94-75c9-4caa-8b2e-02c091e5dbe9)
![image](https://github.com/microsoft/PowerToys/assets/38034251/39962d64-4811-401e-acba-7bf2ebaca81a)



### Supporting information

_No response_
Repository: PowerToys
Issue: Fancy Zones, while dragging a window, Quick Zone select with numbers 1-9
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

While dragging a window and fancy zones with numbers are displayed, pressing the appropriate number key will automatically snap the window to the desired zone. i.e. drag and press 2 to immediately snap window to fancy zone 2

### Scenario when this would be used?

window resizing for MATLAB or other applications that open multiple windows.

### Supporting information

_No response_
Repository: PowerToys
Issue: 建议将键盘管理的重新调整界面，以方便用户选择
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager,Needs-Triage

### Description of the new feature / enhancement

将图中这个
![image](https://github.com/microsoft/PowerToys/assets/87689396/12cbe1c0-e93c-424e-a128-dfd9ff949d30)
修改成点击之后单独一个页面选择，因为上下选择实在太多了

### Scenario when this would be used?

将选择改成一个单独的页面，并归类，方便用户查找

### Supporting information

_No response_
Repository: PowerToys
Issue: Mouse without border, drag drop text between PCs.
Labels: Idea-Enhancement,Product-Mouse Without Borders

### Description of the new feature / enhancement

Select a text, try to drag to other PC. It won't appear. I have to copy paste it.
I am using MWB. not the power toys one, as I have Windows 7.

### Scenario when this would be used?

Saves seconds of work.

### Supporting information

I'd also like to learn about the working of MWB. How it works. Source. So that I may help too.
```[tasklist]
### Tasks
```
Repository: rust
Issue: Regression between nightlies with `-Zpolonius`
Labels: A-borrow-checker,T-compiler,C-bug,NLL-polonius,requires-nightly,T-types

<!--
Thank you for filing a regression report! 🐛 A regression is something that changed between versions of Rust but was not supposed to.

Please provide a short summary of the regression, along with any information you feel is relevant to replicate it.
-->

### Code

I tried this code:

```rust
// GAT hack taken from https://docs.rs/lending-iterator/latest/lending_iterator.
pub trait LendingIterator: Sized
where
    Self: for<'item> LendingIteratorItem<'item>,
{
    fn next(&mut self) -> Option<<Self as LendingIteratorItem>::Item>;
}

/// Hack to express a GAT without GATs.
pub trait LendingIteratorItem<'item> {
    type Item;
}

pub struct Wrapper<I> {
    wrapped: Option<I>,
}

impl<'item, I> LendingIteratorItem<'item> for Wrapper<I>
where
    I: LendingIteratorItem<'item>,
{
    type Item = I::Item;
}

impl<I> LendingIterator for Wrapper<I>
where
    I: LendingIterator,
{
    fn next(&mut self) -> Option<<I as LendingIteratorItem>::Item> {
        if let Some(first) = &mut self.wrapped {
            if let Some(next) = first.next() {
                return Some(next);
            } else {
                self.wrapped = None;
            }
        }
        None
    }
}
```

When running this with `-Zpolonius`, this worked with nightly-2024-05-31. With nightly-2024-06-01, I get this error message:
```
error[E0506]: cannot assign to `self.wrapped` because it is borrowed
  --> src/lib.rs:34:17
   |
29 |     fn next(&mut self) -> Option<<I as LendingIteratorItem>::Item> {
   |             - let's call the lifetime of this reference `'1`
30 |         if let Some(first) = &mut self.wrapped {
   |                              ----------------- `self.wrapped` is borrowed here
31 |             if let Some(next) = first.next() {
32 |                 return Some(next);
   |                        ---------- returning this value requires that `self.wrapped` is borrowed for `'1`
33 |             } else {
34 |                 self.wrapped = None;
   |                 ^^^^^^^^^^^^ `self.wrapped` is assigned to here but it was already borrowed
```

# Bisection

searched nightlies: from nightly-2024-05-31 to nightly-2024-06-01
regressed nightly: nightly-2024-06-01
searched commit range: https://github.com/rust-lang/rust/compare/6f3df08aadf71e8d4bf7e49f5dc10dfa6f254cb4...ada5e2c7b5427a591e30baeeee2698a5eb6db0bd
regressed commit: https://github.com/rust-lang/rust/commit/ada5e2c7b5427a591e30baeeee2698a5eb6db0bd

<details>
<summary>bisected with <a href='https://github.com/rust-lang/cargo-bisect-rustc'>cargo-bisect-rustc</a> v0.6.8</summary>

Host triple: x86_64-unknown-linux-gnu
Reproduce with:
```bash
cargo bisect-rustc --start=2024-05-31 --end=2024-06-01
```
</details>

This is likely caused by https://github.com/rust-lang/rust/pull/125652, cc @amandasystems.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"amandasystems"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: godot
Issue: Godot Removes script_type from resource when loading on Windows for the first time
Labels: topic:core,needs testing,topic:dotnet

### Tested versions

- Reproducable in Godot Version 4.2.2

### System information

Godot v4.2.2.stable.mono - Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1070 Ti (NVIDIA; 31.0.15.5222) - Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz (12 Threads)

### Issue description

I have a resource which is a type of script object called a "RenderLayer" when opening on Mac this works fine and the resource is not modified, it looks like this:
```
[gd_resource type="Resource" script_class="RenderLayer" load_steps=13 format=3 uid="uid://csgcsd2sidnas"]
```

However when I load it for the first time on Windows after pulling it from a shared repo it converts to this:
```
[gd_resource type="Resource" load_steps=13 format=3 uid="uid://csgcsd2sidnas"]
```

This then causes problems as I have techinically modfied this item just by opening it and it loses the script reference if the .improt number changes causing and error on build. It also breaks Mac builds if it is accidentally commited.

### Steps to reproduce

On MacOS:
- Create a C# script defining a new type
- Create a new resource of that scriptable type
- Save project


On Windows:
- Load Project
- Select resource in Godot editor
- Check git changes and see resource has been modified as reported

### Minimal reproduction project (MRP)

Due to the nature of the bug creating a MRP project would not be applicable as I am not on MacOS and so cannot reproduce this on my own.
Repository: go
Issue: runtime: concurrent map iter+write fatal doesn't respect GOTRACEBACK
Labels: NeedsInvestigation,compiler/runtime

### Go version

go version go1.22.4 linux/amd64

### What did you do?

* Introduce a data race on a map (repro: https://go.dev/play/p/rQ1QQ7PMZ86)
* Don't have sufficient test coverage that runs concurrently to catch it in CI
* Ship it to prod
* Have over a million goroutines
* Wait an hour....  


### What did you see happen?

... we hit the race on the map in prod after an hour and 💣 

The Go runtime then did its `fatal`:

```
fatal error: concurrent map iteration and map write
```

But then we got 3 GB of GOTRACEBACK stacks from the Go runtime for 1M+ stacks, about 3 GB more than we needed to find the bug, overwhelming our logging system in the process, causing a secondary outage. 

GOTRACEBACK docs say:

> The failure prints stack traces for all goroutines if there is no current goroutine or the failure is internal to the run-time.

And arguably a map race is internal to the run-time insofar as maps are implemented in the runtime.

But the Go runtime know it's the user's fault; note the "but is used when user code is expected to be at fault for the failure" bit here:

```go
// fatal triggers a fatal error that dumps a stack trace and exits.
//
// fatal is equivalent to throw, but is used when user code is expected to be
// at fault for the failure, such as racing map writes.
//
// fatal does not include runtime frames, system goroutines, or frame metadata
// (fp, sp, pc) in the stack trace unless GOTRACEBACK=system or higher.
//
//go:nosplit
func fatal(s string) {
        // Everything fatal does should be recursively nosplit so it
        // can be called even when it's unsafe to grow the stack.
        systemstack(func() {
                print("fatal error: ")
                printindented(s) // logically printpanicval(s), but avoids convTstring write barrier
                print("\n")
        })

        fatalthrow(throwTypeUser)
}
```

### What did you expect to see?

I'd expect `fatalthrow(throwTypeUser)` to be treated as a normal panic with `GOTRACEBACK=single` respected.

Currently it's ignored:

```
bradfitz@book1pro ~ % GOTRACEBACK=single go run maprace.go 2>&1 | wc -l
     618
bradfitz@book1pro ~ % GOTRACEBACK=none go run maprace.go 2>&1 | wc -l
       2
bradfitz@book1pro ~ % GOTRACEBACK=system go run maprace.go 2>&1 | wc -l
    1684
```

(At least `none` works, but that's too quiet, hiding the actual problem).
Repository: ollama
Issue: ollama-cuda: Incoherent responses using llama2-7b-chat/llama3:instruct after first rest request
Labels: bug

### What is the issue?

I am using Manjaro Linux. A few days ago, I received a new update to `ollama-cuda-0.1.41-1-x86_64.pkg.tar.zst` version.
I noticed that when making a request to ollama API using `llama2-7b-chat` or `llama3:instruct` models, the initial 
response is valid with a response time of 8 seconds. However, when I repeat the request multiple times, the 
responses start to degrade to the point of becoming incoherent. However, the response time is significantly shorter that first time.

I solve this issue making a downgrade to `ollama-cuda-0.1.38-1-x86_6.pkg.tar.zst`. The responses became coherent again.

### OS

Linux

### GPU

Nvidia

### CPU

AMD

### Ollama version

0.1.41
Repository: rust
Issue: "rustc-LLVM ERROR: underestimated function size" on thumbv6m-none-eabi
Labels: I-crash,A-LLVM,O-Arm,T-compiler,C-bug,S-has-mcve

## REPRO

1. git clone https://codeberg.org/sbechet/xmrs , check out commit `0b64aadb55aa8`.
2. `rustup target add thumbv6m-none-eabi`
3. `cargo build --target=thumbv6m-none-eabi --no-default-features --features libm`

This is a [published crate](https://crates.io/crates/xmrs) and we are intending to publish this exact version soon.

If you run this, you will get:

```
$ cargo build --target=thumbv6m-none-eabi --no-default-features --features libm
warning: unused manifest key: examples
   Compiling xmrs v0.6.0 (/home/mcc/work/r/v/test/h/xmrs)
rustc-LLVM ERROR: underestimated function size
error: could not compile `xmrs` (lib)
```

We have tested this on 
1. (My machine) rustc 1.78.0 (9b00956e5 2024-04-29)
2. (Both [sbechet's machine](https://codeberg.org/sbechet/xmrs/pulls/3#issuecomment-2023122) and my machine) rustc 1.79.0 (129f3b996 2024-06-10)
3. (My machine) 1.80.0-nightly (b92758a9a 2024-05-20)
4. (My machine) 1.81.0-nightly (f8e566053 2024-06-14)

The error is identical on all.

We do **NOT** see the problem on x86_64.

I have tested in the same configuration (no_std, libm or micromath) on riscv32imafdc with 1.80.0-nightly, and I do **NOT** see the problem there either.

The meaning of `--no-default-features --features libm` is "do not rely on std, and import libm so that you can do floating point math". If instead you say `--no-default-features --features micromath` (excludes libm, uses a fast approximations library) you DO get the "underestimated function size" error.

Because the error is so undescriptive, it is difficult for us to make a more minimal repro than this. I can gather more information if it helps but you will have to tell me what to gather.

We do not have a specific need to ship on thumbv6m-none-eabi. Currently our goal is to port the above crate to no-std, and thumbv6m-none-eabi was the platform sbechet settled on to test no-std. So this is only blocking us insofar as sbechet cannot test no-std locally. (I test no-std with riscv32imafdc.) However, if it is failing here it may be failing on other ARMs.

### EXTRA

"Include a backtrace in the code block by setting `RUST_BACKTRACE=1` in your environment."

This does not alter the error output.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Add turbo sampler to the new version of webui🙏🏼
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Forge's DPM++ 2m SDE turbo sampler only needs 8 steps to produce the same quality as the DPM++ 2M Karras 20 step, and it takes half the time. It can be used regardless of whether it is a turbo model or not. FP8 has already improved VRAM consumption, so it should be the same There must also be speed improvement of A1111 (the branch with speed improvement cannot use FP8)
Thank you so much

### Proposed workflow

1. The Forge project will no longer be updated (or leave the branch of A1111)
2. Add Turbo sampler when launching new version of webui

### Additional information

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Update Intel Extension for PyTorch to v2.1.30
Labels: enhancement

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Fix issues the current version has and increases performance.

### Proposed workflow

Just update from 2.0.10 to https://github.com/intel/intel-extension-for-pytorch/releases/tag/v2.1.30%2Bxpu 

### Additional information

_No response_