sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: hang/slowdown in `rustc_middle::traits::ObligationCauseCode`
Labels: A-trait-system,C-bug,I-hang

<!--
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.
-->

see also https://github.com/rust-lang/rust/issues/90180

````rust
pub struct B0;
pub struct B1;
use std::ops::Shl;
use std::ops::Sub;
pub type Shleft<A, B> = <A as Shl<B>>::Output;
pub type Sub1<A> = <A as Sub<B1>>::Output;
pub struct UInt<U, B> {
    pub(crate) msb: U,
    pub(crate) lsb: B,
}
impl<U, B, Ur, Br> Shl<UInt<Ur, Br>> for UInt<U, B>
where
    UInt<Ur, Br>: Sub<Br>,
    UInt<UInt<B, U>, B0>: Shl<Self::Output>,
{
    type Output = Shleft<UInt<UInt<U, B>, B0>, Sub1<UInt<Ur, Br>>>;
    fn shl(self, rhs: UInt<Ur, Br>) -> Sub1<UInt<Ur, B1>> {
        unimplemented!()
    }
}
````
`rustc --crate-type lib -Ztime-passes hang.rs`

````
time:   0.018; rss:   37MB ->   39MB (   +2MB)	parse_crate
time:   0.011; rss:   42MB ->   57MB (  +15MB)	expand_crate
time:   0.011; rss:   42MB ->   57MB (  +15MB)	macro_expand_crate
time:   0.000; rss:   57MB ->   59MB (   +2MB)	finalize_macro_resolutions
time:   0.001; rss:   59MB ->   62MB (   +3MB)	late_resolve_crate
time:   0.002; rss:   57MB ->   62MB (   +5MB)	resolve_crate
time:   0.013; rss:   39MB ->   62MB (  +23MB)	configure_and_expand
time:   0.001; rss:   62MB ->   65MB (   +3MB)	looking_for_derive_registrar
time:   0.001; rss:   62MB ->   65MB (   +3MB)	misc_checking_1
time:   0.001; rss:   65MB ->   69MB (   +4MB)	type_collecting
time:   0.001; rss:   69MB ->   71MB (   +3MB)	coherence_checking
<freeze>
````

perf top shows a lot of processing in ` <rustc_middle::traits::ObligationCauseCode as core::cmp::PartialEq>::eq`
Repository: godot
Issue: Game window freezes when going to desktop and won't tab back in (DisplayServer regression)
Labels: bug,topic:rendering,needs testing,regression

### Godot version

v4.0.beta6.mono.official [7f8ecffa5]

### System information

Windows 10

### Issue description

Sometimes if I go to my desktop my game's window just freezes, I can't tab back into it.

### Steps to reproduce

Go to your desktop using a graphical button or a keyboard shortcut (depends on your OS/DE), usually `Win+D`/`Super+D`.
Try to tab back in, it won't work. The game window will not tab back in and reappear.

This isn't very consistent though, it only happens about 75% of the time.
This has been reproduced by @lewiji using Linux w/ Nvidia, with a different project [(Godot Engine Discord)](https://discord.com/channels/212250894228652034/908062856459743262/1049060013123055786).

The `Process` monitor graph dips when this happens.
![`Process` monitor graph dip](https://media.discordapp.net/attachments/880162931243876404/1049042162458820748/image.png)

### Minimal reproduction project

N/A
Repository: PowerToys
Issue: Right-click "Report Bug" Feature
Labels: Issue-Docs,Needs-Triage

### Provide a description of requested docs changes

1) When a user right-clicks the PT tray icon, provide a short popup on mouse-over that tells the user what will be done (i.e. all log and settings files will be zipped up to a file and placed on the desktop for attachment to a support ticket). Possibly better is to give a simple modal dialog detailing what will be done and asking for Continue: Yes/No choice.

2) The first one is an important and useful nice-to-have. This one is very important: 

PLEASE add an item to: 

a) the main github Read Me

b) the github Wiki page

c) the official documentation on the MS Learn website

... that clearly states what the Report Bug zip file will contain. Any security/privacy conscious individual will not desire to send a zip file created by some app on their computer to others - especially to a PUBLIC repository - without knowing what is in it. Don't make them have to dig through the many folders and files to ensure what this file contains is acceptable to promulgate.
Repository: three.js
Issue: From InstancedMesh to more generic Instances
Labels: Suggestion

<!-- Ignoring this template may result in your feature request getting deleted -->

**Is your feature request related to a problem? Please describe.**

Three.js has `InstancedMesh` API to allow easy GPU instancing handling.

It extends `Mesh` and the constructor takes `geometry`, `material`, and `count`.

Because of this design, it has limiation. It is hard to make the use of GPU instancing with non-regular `Mesh`, eg. `SkinnedMesh`, `Line`, or `Points`.

**Describe the solution you'd like**

We support more generic GPU instancing API. 

Perhaps `Instances( Mesh|SkinnedMesh|Line|Points (or whatever), count )`.

It would be more flexible.

**Describe alternatives you've considered**

1. Make `Instanced` API for each object type. eg. `InstancedSkinnedMesh`, `InstancedLine`, `InstancedPoints`. But I don't think it's a good idea because of complexity.
2. Three.js already has `InstancedBufferGeometry/Attribute` and they can be used for non-regular `Mesh`es (?). But it may be harder to use for generic users.

**Additional context**

The idea is from

* https://github.com/mrdoob/three.js/pull/23835#discussion_r844829963
* https://twitter.com/superhoge/status/1599509848995299329 (This may be the first issue originally raised from AI?)
Repository: TypeScript
Issue: API request: allow ignoring ts-(expect-error|ignore) in getPreEmitDiagnostics
Labels: Suggestion,In Discussion

# Suggestion

## 🔍 Search Terms

ignore comment directives ts-expect-error ts-ignore

## ✅ Viability Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).

## ⭐ Suggestion

API consumers such as [typescript-eslint](https://typescript-eslint.io) would benefit from being able to get the diagnostics in a file that _would_ be emitted were it not for a `// @ts-expect-error` or `// @ts-ignore`. Can we add in an options parameter to `program.getPreEmitDiagnostics` to allow consumers to stop those comment directives from suppressing errors?

I threw together a rough draft of how this could look in the TypeScript source here: https://github.com/JoshuaKGoldberg/TypeScript/compare/a7c07ff...JoshuaKGoldberg:TypeScript:get-diagnostics-options. Just in case it's helpful.

## 📃 Motivating Example

https://github.com/JoshuaKGoldberg/eslint-plugin-expect-type/issues/65: we'd like to make lint rules that assert on the error message matching what's expected, as a userland solution to #19139 not being accepted.

## 💻 Use Cases

Here's how we could change what [`eslint-plugin-expect-type` does today](https://github.com/JoshuaKGoldberg/eslint-plugin-expect-type/blob/312aa1e768472b2546d0cd3786d2e5ff01ec74f5/src/rules/expect.ts#L92-L93):

```diff
- const diagnostics = ts.getPreEmitDiagnostics(program, sourceFile);
+ const diagnostics = ts.getPreEmitDiagnostics(program, sourceFile, { skipCommentDirectiveErrorSuppressions: true });
```

Without this API, users either:
* Can't both suppress type errors _and_ lint that the suppressions match up with TypeScript
* Need to have lint rules & similar rewrite files to remove the comments - essentially parsing & type checking them twice
Repository: stable-diffusion-webui
Issue: [Feature Request]: img2img does not remember size setting between pictures
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 ?

If the user sets img2img resize to 1024x1024, for example, and wants to send a number of pictures to it, after every picture sent from the main screen, the img2img reverts back to 512x512. 

This means that every time the user needs to set it manually back to 512.

img2img should just remember the resize setting as it does with all other settings.  If the user changed it, then it shouldn't be automatically reverted.  The current auto-reversion back to 512 just slows down workflows.

### Proposed workflow

1. Create image in main screen
2. Send it to img2img
3. Set img2img resize to 1024x1024
4. Create img2img batch
5. Go back to main screen, generate a new image
6. Send it to img2img, which should retain its last size setting (1024x1024)


### Additional information

_No response_
Repository: rust
Issue: incompatible types when using re-exports of the same crate from different crates (different paths)
Labels: A-diagnostics,T-compiler,C-bug,D-crate-version-mismatch,S-needs-repro

I tried this code:

```rust
let item = sickle_builder::types::time::Date::from_calendar_date(
    2020,
    sickle_builder::types::time::Month::January,
    1,
)?;
let y: i32 = item.year();
let m: tiberius::time::time::Month = item.month();
let d: u8 = item.day();
let date: tiberius::time::Date = tiberius::time::time::Date::from_calendar_date(y, m, d)?;
```

I expected to see this happen: No error

Instead, this happened: 
```
error[E0308]: `?` operator has incompatible types
  --> sickle-query/src/mssql_queryable.rs:53:21
   |
53 |                     tiberius::time::time::Date::from_calendar_date(y, m, d)?
   |                     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ expected struct `tiberius::time::Date`, found struct `sickle_builder::types::time::Date`
   |
   = note: `?` operator cannot convert from `sickle_builder::types::time::Date` to `tiberius::time::Date`
```

`sickle_query::types::time` and `tiberius::time` are re-exports of the `time` crate. For multiple reasons, these may be different versions with different features and _are not be assumed to be the same_. However, it seems that rustc is detecting that they are the same crate, and then "forgets" the path or assumes the wrong path on line 53. But though the path is explicitly given on both the left and right hand sides of the assignment, so there is no ambiguity.

Confirmed this for nightly with `cargo +nightly build --workspace --all-targets --all-features`

Note: This seems different than https://github.com/rust-lang/rust/issues/102882, because I am explicitly stating the paths of which re-export to use, and am not making assumptions that they are the same. rustc seems to arbitrarily pick/unify/dedup a different re-export than what is explicitly stated on one side of the assignment, then fails to do the same with the other side.

### 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.65.0 (897e37553 2022-11-02)
binary: rustc
commit-hash: 897e37553bba8b42751c67658967889d11ecd120
commit-date: 2022-11-02
host: x86_64-unknown-linux-gnu
release: 1.65.0
LLVM version: 15.0.0
```

<!--
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>

No backtrace; it doesn't build.

</p>
</details>
Repository: next.js
Issue: With Next.js13 app-directory, Fetch API cause error when optional argument set for edge runtime
Labels: Runtime

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

 Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Enterprise
    Binaries:
      Node: 18.12.1
      npm: N/A
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.0.4
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

### Which area(s) of Next.js are affected? (leave empty if unsure)

Middleware / Edge (API routes, runtime)

### Link to reproduction - Issues with a link to complete (but minimal) reproduction code will be addressed faster

https://github.com/cloudflare/next-on-pages/issues/36

### To Reproduce

N/A

### Describe the Bug

This was reported on cloudflare issue but i think it belongs here, see https://github.com/cloudflare/next-on-pages/issues/36

When using the edge runtime then reactfetch will fail when trying to cache due to Request do not have those property implemented that is used for the key, mode, integrity, credentials
https://github.com/facebook/react/blob/main/packages/react/src/ReactFetch.js#L77


### Expected Behavior

N/A

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: rust
Issue: Codegen backends should validate their assumed encodings of e.g. rustc layouts.
Labels: A-LLVM,A-codegen,T-compiler

Specifically the thing that came to mind is that `rustc_codegen_llvm` could assert `LLVMSizeOf` matches the `rustc` `Layout` every time it builds a LLVM type from a layout.
<sub>(and this should hopefully be cheap enough that we could always have it enabled)
<sup>(I generally dislike debug asserts as they can't be relied upon to enforce soundness...)</sup></sub>

The motivating example is a discussion around a `#[repr(simd)] struct i32x3([i32; 3]);` type having size 12:
* https://github.com/rust-lang/portable-simd/issues/319#issuecomment-1336482215
* but as I note in the comment linked above, LLVM's `<3 x i32>` is 16 bytes, so that would be illegal
  * (16 bytes at least in "stride", which LLVM doesn't seem to name as such - it doesn't read/write 16 bytes on load/store, so it definitely seems to have more than once concept of "size" even for primitives)
  * (and no, `#[repr(packed)]` doesn't seem to do anything today, in combination with `#[repr(simd)]`, so you couldn't get the 12-byte layout without changing e.g. the `vector_align` algorithm in the compiler)

I'm unsure about the GCC backend but presumably it should also be able to do this? (cc @antoyo)

cc @rust-lang/wg-llvm @bjorn3
Repository: stable-diffusion-webui
Issue: [Bug]: Batch preview of individual images doesn't show image you clicked on in extra large preview.
Labels: bug-report

### Is there an existing issue for this?

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

### What happened?

When you generate a batch of images and then click the batch grid image shown in the interface you can see the individual images along the bottom of the batch. You can then click those small images, the image above them will change, but when you click on that far a larger preview it shows the next image in the batch. Then when closing that large preview you can see it has switched to that image on the main screen.

### Steps to reproduce the problem

1. Create a batch
2. Click the batch grid image to display the small images of individual generations on the bottom
3. Click the larger preview above that image to show the extra large preview and notice that it switches to the next image in the batch, not the one you clicked.

### What should have happened?

It should show the image you clicked in the extra large preview

### Commit where the problem happens

44c46f0

### What platforms do you use to access UI ?

Windows

### What browsers do you use to access the UI ?

Mozilla Firefox

### Command Line Arguments

```Shell
--listen --theme dark --enable-insecure-extension-access --xformers
```


### Additional information, context and logs

_No response_
Repository: PowerToys
Issue: create folder from selection
Labels: Idea-New PowerToy,Product-File Explorer

### Description of the new feature / enhancement

Right click and there be a "create folder from selection"

### Scenario when this would be used?

I would really like to be able to select a bunch of files, right click and there be a "create folder from selection" option. The ability to create a new folder from a selection of files without having to take multiple steps.... life would be so much better this way.

### Supporting information

_No response_
Repository: rust
Issue: `!` cannot be used as `impl Trait` when `!` implements `Trait`
Labels: T-compiler,C-bug,F-never_type,requires-nightly

<!--
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 ([playground link](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=c3993160a858f7133c2f66ce1209f03e)):

```rust
#![feature(never_type)]
#![allow(unreachable_code)]

pub trait Trait {}
impl Trait for ! {}

pub fn test() -> impl Trait {
    let x: ! = panic!();
    x
}
```

I expected to see this happen: The code should compile. Because `!` implements `Trait`, `!` should be a valid return type for `fn test` (and no fallback should occur).

Instead, this happened: The code does not compile. `x` "falls back" to `()`, (which does not implement `Trait`), so the function does not typecheck, giving the following error message:

```rs
error[E0277]: the trait bound `(): Trait` is not satisfied
 --> src/lib.rs:7:18
  |
7 | pub fn test() -> impl Trait {
  |                  ^^^^^^^^^^ the trait `Trait` is not implemented for `()`
  |
  = help: the trait `Trait` is implemented for `!`

For more information about this error, try `rustc --explain E0277`.
error: could not compile `playground` due to previous error
```

---

### See also:

* Tracking issue for making `!` a type: #35121. (I looked through the tracking issue and did not see this issue mentioned.)
* This is different from #55022, which concerned an `impl Trait` where `!` did not implement `Trait`.

### 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 +nightly --version --verbose`:
```
rustc 1.67.0-nightly (32e613bba 2022-12-02)
binary: rustc
commit-hash: 32e613bbaafee1bcabba48a2257b838f8d1c03d3
commit-date: 2022-12-02
host: x86_64-unknown-linux-gnu
release: 1.67.0-nightly
LLVM version: 15.0.4
```

<!--
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>

```
<backtrace>
```

</p>
</details>
Repository: PowerToys
Issue: [Peek] Minimize memory usage
Labels: Product-Peek

Cleanup resources:

- Disposal of bitmap images
- Unloading of UI controls
- Evaluation of WebView2 memory footprint (consider only loading WebView2 if users opt-in file type previewer that uses it)
Repository: PowerToys
Issue: [Peek] ImagePreviewer - Optimize thumbnail loading
Labels: Product-Peek

- Thumbnail quality is higher on subsequent request (OS caching), consider implementing re-try pattern if fast enough
- Consider forcing small quality thumbnail as first initial load, to speed up preview
Repository: PowerToys
Issue: [PowerToys Run] can't find running applications
Labels: Issue-Bug,Product-PowerToys Run,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.64.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

can't find running applicaitons
1. [TIM](https://tim.qq.com/)
2. [zerotier](https://my.zerotier.com/)

### ✔️ Expected Behavior

I can get  applications like `TIM` back to the current window.

### ❌ Actual Behavior

I could only create new process for `TIM` or `zeriter-one`.

### Other Software

_No response_
Repository: next.js
Issue: Next.js 13 SVG images imported with SVG components
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

    Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 21.4.0: Mon Feb 21 20:36:53 PST 2022; root:xnu-8020.101.4~2/RELEASE_ARM64_T8101
    Binaries:
      Node: 14.18.2
      npm: 6.14.15
      Yarn: 1.22.15
      pnpm: 6.11.0
    Relevant packages:
      next: 13.0.6
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0

### Which area(s) of Next.js are affected? (leave empty if unsure)

Image optimization (next/image, next/legacy/image)

### Link to reproduction - Issues with a link to complete (but minimal) reproduction code will be addressed faster

https://github.com/ShaySong99/next-examples-svg-components

### To Reproduce

In github repo

### Describe the Bug

```
import Cat from "&/svgs/cat.svg?icon";
import cat from "&/svgs/cat.svg";
import styles from "&/styles/index.module.css";

export default function Home() {
  return (
    <div className={styles.container}>
      <h2>Svg as components</h2>
      <Cat />
      <h2>Svg as image</h2>
      <img src={cat.src} alt="cat" />
    </div>
  );
}
```
```
webpack(config) {
    config.module.rules.push({
        test: /\.svg$/i,
        issuer: /\.[jt]sx?$/,
        resourceQuery: /icon/,
        use: ['@svgr/webpack'],
    });
    config.module.rules.push({
        test: /\.svg$/i,
        issuer: /\.[jt]sx?$/,
        resourceQuery: { not: [/icon/] },
        loader: 'next-image-loader',
        options: { assetPrefix: '' },
    });
    return config;
}
```

![image](https://user-images.githubusercontent.com/90174719/205582168-01e1a768-2f39-448a-9f34-352d3c3fa88f.png)


When import svg as components with @svgr/webpack, i use resourceQuery to resolve between different case. But it seems the svg imported by image is not bundled. It is correct when not using rule. 
And the using case is correctly presented in Next.js 12.

### Expected Behavior

Svg could be imported as components and images correctly.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: flutter
Issue: Overlay overlapps the popup menu created by `PopupMenuButton`
Labels: framework,f: material design,has reproducible steps,P2,found in release: 3.3,found in release: 3.7,team-design,triaged-design

I have a bug with menu overlapping. If `OverlayEntry`'s widget is active and I activate popup menu with `PopupMenuButton` it is draw **under** the overlay which is bug for me.

P.S. Unfortunately I will not be able to present the code sample, only this video.

https://user-images.githubusercontent.com/45417992/205594093-2929af05-6a67-43e5-ad35-991dcc78348f.mp4