sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: material-ui
Issue: Accordion's bottom outline disappears when expanded (only in safari)
Labels: component: accordion,browser: Safari

### Steps to reproduce

Link to live example: https://stackblitz.com/~/github.com/vaughn18/mui-accordion-bug

Using the live example will be redundant as it requires you to use different browser. So you must clone this [repo](https://github.com/vaughn18/mui-accordion-bug) 

Steps:
1. Clone the [repo](https://github.com/vaughn18/mui-accordion-bug)
2. install vite if not yet installed e.g. `npm install -D vite`
3. start the app with `vite` in terminal
4. Open the app in Safari (I am currently on version 17.5) it should be on localhost:5173
5. Expand Accordion 2




### Current behavior

Bottom outline is gone
<img width="1222" alt="Screenshot 2024-08-13 at 4 23 05 PM" src="https://github.com/user-attachments/assets/6c75746c-7d1d-4626-b87e-e0ff5e56ceac">


### Expected behavior

Bottom outline is there (opened in chrome)
<img width="1366" alt="Screenshot 2024-08-13 at 4 22 55 PM" src="https://github.com/user-attachments/assets/ba300051-3e99-49e6-a5ba-1a26157f01c1">


### Context

I am a developer for a health software company and we happen to use React MUI for our App. It is part of our standards that we should comply to support Safari. We found this bug from testing and can confirm that it only happens on Safari, we haven't tested on any other versions aside from the one mentioned (17.5). We currently have a workaround to fix this issue which is to expand the height of the Grid container by hardcoding a specific value but it is not quite up to par with our coding conventions as we try to not to hardcode values on low level components.

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```
  System:
    OS: macOS 14.5
  Binaries:
    Node: 20.12.2 - ~/.nvm/versions/node/v20.12.2/bin/node
    npm: 10.5.0 - ~/.nvm/versions/node/v20.12.2/bin/npm
    pnpm: 9.7.0 - ~/.nvm/versions/node/v20.12.2/bin/pnpm
  Browsers:
    Chrome: 127.0.6533.100
    Edge: 127.0.2651.98
    Safari: 17.5
  npmPackages:
    @emotion/react: ^11.13.0 => 11.13.0 
    @emotion/styled: ^11.13.0 => 11.13.0 
    @mui/core-downloads-tracker:  5.16.7 
    @mui/icons-material: ^5.16.7 => 5.16.7 
    @mui/material: ^5.16.7 => 5.16.7 
    @mui/private-theming:  5.16.6 
    @mui/styled-engine:  5.16.6 
    @mui/system:  5.16.7 
    @mui/types:  7.2.15 
    @mui/utils:  5.16.6 
    @types/react: ^18.3.3 => 18.3.3 
    react: ^18.3.1 => 18.3.1 
    react-dom: ^18.3.1 => 18.3.1 
```



**Search keywords**: accordion bottom outline safari glitch disappears
Repository: rust
Issue: `impl PartialOrd<[U]> for [T]`
Labels: T-libs-api,C-tracking-issue

This has an [accepted ACP][ACP], but I'm going to file a separate issue here since I was having issues implementing it and don't want to forget about it. (Like I have for the past year.)

Essentially, the primary issue is the way we go about specializing `PartialOrd` for slices, which is not symmetric with the way we go about specializing `PartialEq` for slices. 

Right now, `PartialEq<[U]> for [T]` relies on a corresponding `SlicePartialEq<U> for [T]`, and there's no issue.

However, because `Ord` doesn't have a generic parameter, `SlicePartialOrd` also doesn't, and this means that we can't actually specialize `PartialOrd<[U]> for [T]`. And I don't really know how to fix things without breaking the existing optimizations in the standard library, which is why I haven't touched this yet.

All the relevant code is in `library/core/src/slice/cmp.rs`:

```rust
impl<T, U> PartialEq<[U]> for [T]
where
    T: PartialEq<U>,
{
    fn eq(&self, other: &[U]) -> bool {
        SlicePartialEq::equal(self, other)
    }

    fn ne(&self, other: &[U]) -> bool {
        SlicePartialEq::not_equal(self, other)
    }
}

trait SlicePartialEq<B> {
    fn equal(&self, other: &[B]) -> bool;

    fn not_equal(&self, other: &[B]) -> bool {
        !self.equal(other)
    }
}

impl<T: PartialOrd> PartialOrd for [T] {
    fn partial_cmp(&self, other: &[T]) -> Option<Ordering> {
        SlicePartialOrd::partial_compare(self, other)
    }
}

trait SlicePartialOrd: Sized {
    fn partial_compare(left: &[Self], right: &[Self]) -> Option<Ordering>;
}
```

The main issue is this impl here:

```rust
trait AlwaysApplicableOrd: SliceOrd + Ord {}
impl<A: AlwaysApplicableOrd> SlicePartialOrd for A {
    fn partial_compare(left: &[A], right: &[A]) -> Option<Ordering> {
        Some(SliceOrd::compare(left, right))
    }
}
```

Which essentially *requires* that `SlicePartialOrd` not have a generic parameter, since `SliceOrd` and `Ord` don't.

[ACP]: https://github.com/rust-lang/libs-team/issues/285
Repository: material-ui
Issue: [Typography] text color not working in v6 + Pigment CSS
Labels: docs,component: Typography,package: material-ui,v6.x,package: pigment-css

### Steps to reproduce

Link to live example: (required)

Steps:
Use pigmentcss
1. ` <Typography color="text.secondary">Hello!!!</Typography>`


### Current behavior

No secondary text color

### Expected behavior

Secondary text color

### Context

Also same issue with ListItemText and secondary prop because it uses typography

### Your environment

<details>
  <summary><code>npx @mui/envinfo</code></summary>

```

  System:
    OS: macOS 14.3.1
  Binaries:
    Node: 22.5.1 - /opt/homebrew/bin/node
    npm: 10.8.2 - /opt/homebrew/bin/npm
    pnpm: 9.6.0 - /opt/homebrew/bin/pnpm
  Browsers:
    Chrome: 127.0.6533.100
    Edge: Not Found
    Safari: 17.3.1
  npmPackages:
    @emotion/react:  11.13.0 
    @emotion/styled:  11.13.0 
    @mui/core-downloads-tracker:  6.0.0-dev.240424162023-9968b4889d 
    @mui/icons-material: next => 6.0.0-beta.5 
    @mui/material: next => 6.0.0-beta.5 
    @mui/material-pigment-css: next => 6.0.0-beta.5-dev.20240809-114550-93cb3d65e7 
    @mui/private-theming:  6.0.0-beta.5-dev.20240809-114550-93cb3d65e7 
    @mui/styled-engine:  6.0.0-beta.5 
    @mui/system:  6.0.0-beta.5-dev.20240809-114550-93cb3d65e7 
    @mui/types:  7.2.15 
    @mui/utils:  6.0.0-beta.5-dev.20240809-114550-93cb3d65e7 
    @types/react: ^18 => 18.3.3 
    react: ^18 => 18.3.1 
    react-dom: ^18 => 18.3.1 
    typescript: ^5 => 5.5.4 

```
</details>


**Search keywords**: Typography text color not working
Repository: godot
Issue: Autoload breaks upon migrating project from Windows 7 to Windows 11
Labels: bug,topic:editor,needs testing

### Tested versions

- Reproducible in: Godot 3.5.3-Stable, Godot 3.6-beta5

### System information

Windows 11 Home Edition (Ver. 23H2, Build 22631.3880)
CPU: Intel Core i5 1155G7
SSD: Wodposit NVMe SSD (M.2, 512 GB)
Video: Intel Iris Xe graphics (Integrated)

### Issue description

I'm migrating from Windows 7 to Windows 11.

When I trying to run my project what I developed on Windows 7, I'm catching an error:

_**"Parser Error: The identifier "AutoloadScriptName" isn't declared in the current scope."**_

It catched from other script with autoload call. Upon search (and enabling **verbose_stdout** setting in project), I've found out what problematic script really loaded BEFORE needed autoload.

Screenshot:
![Screenshot](https://github.com/user-attachments/assets/9c6d026d-8c29-405a-9f40-a406156e7ccd)
[(also full output log in txt file)](https://github.com/user-attachments/files/16595118/debug_output.txt)

Any way to fix what? Because my project is heavily-depended on autoloads and cannot be easily rewritten for other way.
Reattaching autoload script (even with project reloading) won't helping with this issue. On Win 7 it opens and runs fine.

P.S. Maybe it helps, I'm also always catching this error in output upon opening any project (no difference between new on Win 11 or old from Win 7):
**_"platform/windows/os_windows.cpp:3671 - Condition "res != ((HRESULT)0x00000000)" is true. Returned: String()"_**

### Steps to reproduce

I'm not sure HOW I should reproduce this. Because too many autoloads (12)? Project structure (many classes in GDScript, what inherits from one another)? Or I just don't have some C++ Redistributables what old PC has? Or all of them at once?

### Minimal reproduction project (MRP)

Same as in steps. I can only give my full project what I'm working on.
Repository: next.js
Issue: Top Suspence fallback not work in chrome or android
Labels: bug,Lazy Loading,Performance,Parallel & Intercepting Routes,Partial Prerendering (PPR)

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/priceless-tristan-scjvs6?file=%2Fapp%2Fpage.tsx%3A12%2C32

### To Reproduce

1. open preview link in chrome new tab
2. refresh some times
3. responce body has loading dom but not show

### Current vs. Expected behavior

Current: Normal in safari and Firefox, but abnormal in chrome and Android, sometimes flashes

Expected behavior: fallback should always show

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 15.0.0-canary.112 // Latest available version is detected (15.0.0-canary.112).
  eslint-config-next: N/A
  react: 19.0.0-rc-187dd6a7-20240806
  react-dom: 19.0.0-rc-187dd6a7-20240806
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Lazy Loading, Parallel & Intercepting Routes, Partial Prerendering (PPR), Performance

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local)

### Additional context

_No response_
Repository: PowerToys
Issue: Please add a desktop organization function, this is really useful
Labels: Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

Windows users can easily throw files everywhere on the desktop, there are some small software that can classify them according to type, tags and other dimensions, place, which can greatly improve the user's experience and work efficiency, but to install a small piece of software, in fact, it is not very user-friendly, please try to add such a function

### Scenario when this would be used?

It greatly improves the user's experience and productivity, and reduces the number of small pieces of software that users can install, which may also be insecure

### Supporting information

_No response_
Repository: rust
Issue: Tracking Issue for `const_vec_string_slice`
Labels: T-libs-api,final-comment-period,C-tracking-issue,disposition-merge,A-str

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(const_vec_string_slice)]`

This is a tracking issue for making a bunch of `String` and `Vec` methods `const`.

### Public API

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

The following methods are now `const`:

```rust
impl String {
    pub const fn into_bytes(self) -> Vec<u8>
    pub const fn as_str(&self) -> &str
    pub const fn capacity(&self) -> usize
    pub const fn as_bytes(&self) -> &[u8]
    pub const fn len(&self) -> usize
    pub const fn is_empty(&self) -> bool
}

impl Vec<T> {
    pub const fn capacity(&self) -> usize
    pub const fn as_slice(&self) -> &[T]
    pub const fn as_ptr(&self) -> *const T
    pub const fn len(&self) -> usize
    pub const fn is_empty(&self) -> bool
}
```

### Steps / History

- [x] Implementation: #128399
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html

@rustbot label A-str
Repository: stable-diffusion-webui
Issue: [Feature Request]: Please add support for the FLUX model, thank you!
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 ?

The FLUX model's hand processing and prompt accuracy are incredibly powerful, and it's been super popular recently!

### Proposed workflow

1. thank you!
2. thank you!
3. thank you!


### Additional information

_No response_
Repository: godot
Issue: Text is selected unexpectedly in script editor when left clicking after opening a context menu
Labels: bug,topic:editor,topic:input

### Tested versions

v4.3.rc3.official [03afb92ef]

### System information

w10 64

### Issue description

Watch the video, I select a line (left click), I open the context menu (right click), then I select another line (left click) and the text was selected, something I did not do.


https://github.com/user-attachments/assets/ff640a92-b069-4058-8f06-654b0b9a9049



### Steps to reproduce

read the description and see the video

### Minimal reproduction project (MRP)

...
Repository: godot
Issue: Every time I start a new project, a warning is printed about an unavailable file (due to it being referenced in `editor_layout.cfg`)
Labels: bug,topic:editor,usability

### Tested versions

v4.3.rc3.official [03afb92ef]
But I had it happening since 4.1 or so

### System information

Mac Mini M1 with newest MacOS

### Issue description

Every time I start a new project an error is printed in the console:
![image](https://github.com/user-attachments/assets/8a775036-51fa-40d4-a440-96db1a9a6ebc)

Again, this is when starting a completely empty project. The file Godot is looking for was indeed used in one of my old projects and it exists somewhere in some other folder and I don't see why would it be invoked. The file Godot is looking for is nothing special, it's just a special effect that is drawn on screen when the player character uses a weapon (basically a Sprite2D with maybe an audio component or something similar).

The projects work normally after I save them the first time (at least I haven't noticed anything strange) and the error message goes away after a while without me doing anything special.

This doesn't really block my work or anything but it's really annoying and slightly worrying.

### Steps to reproduce

I open a new project and get the error message. I assume it's specific to something on my end.

### Minimal reproduction project (MRP)

Godot project manager -> New project
Repository: godot
Issue: Dragging a meshlibrary file hangs the editor for several seconds. 
Labels: topic:editor,topic:3d,performance

### Tested versions

- Reproductible in v4.3.rc3.mono.official [03afb92ef]
- Reproductible in v4.2.2.stable.mono.official [15073afe3]

### System information

Windows 10 - Vulkan (forward+) - dedicated

### Issue description

Trying to drag a meshlibrary file into a gridmap file makes the editor hang for several seconds depending on the size of the file.
It also repeats the hang everytime you mouseover the slot dropbox.

If the file is small 30Mb~ it is manageble. Just feels clunky.


https://github.com/user-attachments/assets/d725e86c-c1be-43de-aaf9-16fdbd4f2425



Big it becomes unusable if the file is bigger than around 80MB


https://github.com/user-attachments/assets/62941182-9196-469e-b4c5-8db5628b9be4


---

**I'm also not sure if the mesh library size is a bug itself.**
A mesh library of kenny platformer kit (**142 files** totalling **2 MB glb files**) --> **Meshlibrary of 9 MB**
But then using KayKit halloween bits (**63 files** totalling **1.47 MB**) ----> **Meshlibrary of 88 MB**
Both saved as .meshlib format.

It feels like a bug but it might also be the mesh library is horribly optimized for specific cases.
From the size reduction of **130 MB to 5 MB with a simple .zip** with the MRP, the Meshlibrary itself doesn't seem to use much
compression to it, even using .meshlib or .res files. 


### Steps to reproduce

From the MRP:
- Open world.tscn
- Drag & drop "mesh_really_bad.meshlib"
Result: Editor hands for several seconds
- Drag & Drop "mesh_bad.meshlib"
Result: Lags and hands for a few miliseconds each time mouse over gridmap slot while holding file.

From a blank project:
- Save a scene file with lots of glb scenes children.
- Select export as meshlibrary.
- Add a gridmap to a new scene
- Try Drag and drop a meshlibrary file into the gridmap slot ( lags if file is 30MB, unusable at 80MB)


### Minimal reproduction project (MRP)

Minimal project.
[bug-meshlibrary-drag.zip](https://github.com/user-attachments/files/16596839/bug-meshlibrary-drag.zip)
Repository: rust
Issue: Inconsistency between tuples and struct-tuples with `min-exhaustive-patterns`
Labels: A-diagnostics,T-lang,T-compiler,C-discussion,F-min_exhaustive_patterns

I tried this code:

```rust
#![feature(min_exhaustive_patterns)]
#![feature(never_type)]

use std::marker::PhantomData;

pub fn foo<B>(x: (!, PhantomData<B>)) -> ! {
    match x {}
}

pub struct Bar<B>(!, PhantomData<B>);
impl<B> Bar<B> {
    pub fn bar(&self) -> ! {
        match *self {}
    }
}
```

I expected to see this happen: No errors (because `Bar<B>` is empty the same way `foo`'s parameter is).

Instead, this happened: `non-exhaustive patterns: type Bar<B> is non-empty`.

Note that the tracking issue #119612 mentions "a struct with a _visible_ field of empty type", so I also tried to make the first field `pub !` to see, but it's the same behavior. Note that I consider the field visible in the scope it is used, which matches with the fact that adding `pub` did not fix the issue. The issue seems thus to be a difference between struct-tuple and tuple.

### Meta

`rustc --version --verbose`:
```
rustc 1.82.0-nightly (f8060d282 2024-07-30)
binary: rustc
commit-hash: f8060d282d42770fadd73905e3eefb85660d3278
commit-date: 2024-07-30
host: x86_64-unknown-linux-gnu
release: 1.82.0-nightly
LLVM version: 18.1.7
```
Repository: ollama
Issue: AMD Discrete GPU Version info not found - Radeon RX Vega56 - gfx900
Labels: feature request,amd

### What is the issue?

## What happened
Every time I start the ollama,it always shows these:
```
https://www.amd.com/en/support/linux-drivers" error="amdgpu version file missing: /sys/module/amdgpu/version stat /sys/module/amdgpu/version: no such file or directory"
time=2024-08-13T16:46:10.463+08:00 level=INFO source=amd_linux.go:348 msg="skipping rocm gfx compatibility check" HSA_OVERRIDE_GFX_VERSION=9.0.0
time=2024-08-13T16:46:10.463+08:00 level=INFO source=types.go:105 msg="inference compute" id=0 library=rocm compute=gfx900 driver=0.0 name=1002:687f total="8.0 GiB" available="7.1 GiB"
```
I am using Arch Linux system and i sure that i installed my drivers correctly
My GPU: _Radeon RX Vega56 8GB_

ROCm version:
_rocm-core 6.0.2-2_

## What I expect
I can use GPU Support
Without this,i can only use my CPU.

### OS

Linux

### GPU

AMD

### CPU

Intel

### Ollama version

0.3.3
Repository: rust
Issue: Confusing errors with *dyn pointers
Labels: A-diagnostics,T-compiler,D-confusing

### Code

```Rust
trait MyTrait {
    fn f(&self) -> bool;
}

struct MyStruct(pub u32);

impl MyTrait for MyStruct {
    fn f(&self) -> bool {
        self.0 != 0
    }
}

pub fn inner(_p: *mut dyn MyTrait) {}

pub fn outer(p: &mut dyn MyTrait) {
    let q = p as *mut _;
    inner(q)
}

pub fn main() {
    let mut s = MyStruct(42);
    outer(&mut s);
}
```


### Current output

```Shell
error: lifetime may not live long enough
  --> main.rs:16:13
   |
15 | pub fn outer(p: &mut dyn MyTrait) {
   |                 - let's call the lifetime of this reference `'1`
16 |     let q = p as *mut _;
   |             ^ cast requires that `'1` must outlive `'static`

error: aborting due to 1 previous error
```


### Desired output

_No response_

### Rationale and extra context

The fact that a cast to a **raw pointer** checks lifetimes is confusing by itself. Even more confusing is the fact it talks about the reference lifetime while it’s the referenced type lifetime what matters, i.e. `&mut (dyn MyTrait + 'static)` is what the compiler wants. Though I’m not sure whether it should check that either, it’s a raw pointer after all.

Also sometimes, the error is shown not on the cast but where the result is used, like:
```
43 | pub fn some_function<R>(parameter: &mut dyn SomeTrait, f: impl FnOnce() -> R) -> R {
   |                                    - let's call the lifetime of this reference `'1`
44 |     let pp = std::ptr::from_mut(parameter);
45 |     let obj = SomeOtherObj::new(pp);
   |                                 ^^ cast requires that `'1` must outlive `'static`
```
I’m not sure how to reproduce *that* however.

Related: #95242.

### Other cases

_No response_

### Rust Version

```Shell
rustc 1.80.1 (3f5fd8dd4 2024-08-06)
binary: rustc
commit-hash: 3f5fd8dd41153bc5fdca9427e9e05be2c767ba23
commit-date: 2024-08-06
host: x86_64-unknown-linux-gnu
release: 1.80.1
LLVM version: 18.1.7
```


### Anything else?

_No response_