sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Tooltips lock the main editor window
Labels: bug,platform:linuxbsd,topic:porting,topic:gui

### Godot version

4+

### System information

Linux/BSD

### Issue description

when hovering, and an information box appears ... (and occasionally text boxes) ... it LOCKS.
i must kill godot and restart it.
if i move the main window the little information box stays exactly where it was ... .... hence i guess a popup.

this is ENTIRELY random ... sometimes it does it ... sometimes not ..... 
it cannot be "reproduced" except by random chance.

a small example is attached.

and it is ANY information box .. not just one ... i kill and restart FAR more than actually MAKING any game.

![Screenshot_2023-07-06_02-07-08](https://github.com/godotengine/godot/assets/127719264/164c43c6-f84a-4bba-94d1-efd3511cbab2)
![Screenshot_2023-07-06_06-21-35](https://github.com/godotengine/godot/assets/127719264/d66e428a-57c1-465c-b731-53383bad9829)


### Steps to reproduce

see "Issue description" with attachment.

### Minimal reproduction project

see "Issue description" with attachment.
Repository: tauri
Issue: [bug] NSIS and WIX fails when application larger than 2GB 
Labels: type: bug,platform: Windows,status: needs triage

### Describe the bug

Hello, I try to build software installer larger than 2GB but always get this compiler error indicating 2GB size limit. Similar error happens also when I use WIX. I know it is NSIS/WIX side issue but I still want to ask if there is an existing convient way from tauri side to fix this? That would save me a lot time. 

### Reproduction

1. create an app larger than 2GB
2. run `yarn tauri build --debug --verbose --bundles nsis`

### Expected behavior

`msi` / `exe` installer successfully created

### Platform and versions

```text
[✔] Environment
    - OS: Windows 10.0.22621 X64
    ✔ WebView2: 114.0.1823.67
    ✔ MSVC: Visual Studio Community 2022
    ✔ rustc: 1.67.1 (d5a82bbd2 2023-02-07)
    ✔ Cargo: 1.67.1 (8ecd4f20a 2023-01-10)
    ✔ rustup: 1.25.2 (17db695f1 2023-02-01)
    ✔ Rust toolchain: stable-x86_64-pc-windows-msvc (default)
    - node: 16.16.0
    - yarn: 1.22.19
    - npm: 8.11.0

[-] Packages
    - tauri [RUST]: 1.2.4
    - tauri-build [RUST]: 1.2.1
    - wry [RUST]: 0.23.4
    - tao [RUST]: 0.15.8
    - @tauri-apps/api [NPM]: 1.4.0
    - @tauri-apps/cli [NPM]: 1.4.0

[-] App
    - build-type: bundle
    - CSP: unset
    - distDir: ../dist
    - devPath: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

```text
MakeNSIS v3.08 - Copyright 1999-2021 Contributors
See the file COPYING for license details.
Credits can be found in the Users Manual.

Processing config: C:\Users\xxx\AppData\Local\tauri\NSIS\nsisconf.nsh
Processing script file: "C:\Users\xxx\src-tauri\target\debug\nsis\x64\installer.nsi" (UTF16LE)

Internal compiler error #12345: error mmapping file (2102998393, 33554432) is out of range.

Note: you may have one or two (large) stale temporary file(s) left in your temporary directory (Generally this only happens on Windows 9x).
```


### Additional context

_No response_
Repository: excalidraw
Issue: Open files in android Browsers partially not working
Labels: bug,mobile,filesystem

Opening saved files on android seems to only work in Firefox

on the other tested Browsers it opens the file explorer and lets you select a file
but it doesn't change the Canvas on Excalidraw

I've tested other common Browsers like:
- Chrome
- Brave
- Microsoft Edge

I used a Samsung Galaxy Tab S8 and Samsung Galaxy A52s to Test this.
Repository: storybook
Issue: [Bug](NextJS): Error: Google Fonts couldn't be loaded.
Labels: bug,needs triage

### Describe the bug

Seeing this error very often when deploying a NextJS app to Chromatic:  `Error: Google Fonts couldn't be loaded.`.

Rerun usually works, but it would be great if Storybook could do a few retries here, and make this more robust?

### To Reproduce

_No response_

### System

_No response_

### Additional context

_No response_
Repository: angular
Issue: FormControls are not usable in multiple formGroups
Labels: area: forms,forms: Controls API

### Which @angular/* package(s) are the source of the bug?

forms

### Is this a regression?

Yes

### Description

Right now using the same formControls in multiple formGroups is not possible. From the developer's point of view, I think it would be more intuitive in this case that the controls were synchronized. It seems that it only changes the value in the last formGroup that the controls are assigned to.

Example:

```
userControl = new FormControl('');
passControl = new FormControl('');

form1 = new FormGroup({
 user1: this.userControl,
 pass1: this.userControl
});

form2 = new FormGroup({
  user2: this.userControl,
  pass2: this.userControl
});

constructor(){
     this.form1.valueChanges.subscribe((res) => {
       // Never enter here:
       console. log('FORM1 Changes');
     });

     this.form2.valueChanges.subscribe((res) => {
       console. log('FORM2 Changes');
     });
}

```

In the HTML:

```
<form [formGroup]="form1">
     <!---- If you type here, the console prints 'FORM2 Changes' ------>
     <input type="text" matInput formControlName="user1" placeholder="user in form 1">
     <input type="text" matInput formControlName="pass1" placeholder="pass in form 1">
</form>


<form [formGroup]="form2">
     <input type="text" matInput formControlName="user2" placeholder="user in form 2">
     <input type="text" matInput formControlName="pass2" placeholder="pass in form 2">
</form>

```

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular CLI: 15.2.8
Node: 16.15.1
Package Manager: npm 8.14.0
OS: win32 x64

Angular: 15.2.9
... animations, cdk, common, compiler, compiler-cli, core, forms
... material, platform-browser, platform-browser-dynamic, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1502.8
@angular-devkit/build-angular   15.2.8
@angular-devkit/core            15.2.8
@angular-devkit/schematics      15.2.8
@angular/cli                    15.2.8
@schematics/angular             15.2.8
rxjs                            7.5.7
typescript                      4.8.4
```


### Anything else?

_No response_
Repository: create-react-app
Issue: Should react use ipv6 address for localhost by default in Node.js >=18.16 ?
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->
(Related issue: [#11302](https://github.com/facebook/create-react-app/issues/11302))

Node.js >=18.16, localhost will be resolved to ipv6 address [::1] by default, instead of 127.0.0.1. Some popular dev servers like Angular follow this feature. But React still resolves its default hostname "localhost" to ipv4.
See line 56 in "create-react-app\packages\react-scripts\scripts\start.js":
```
const HOST = process.env.HOST || '0.0.0.0';
```
This is sometimes a little unfriendly while users use some node.js based functions resolving localhost in a different way.

For example:
```
proxyApp.web(
      req,
      res,
      {
        target, // target is the url started by React, e.g. http://localhost:3000
        secure: false,
        toProxy: true,
      },
      onConnectionLost(req, res, target)
    );
```
In this case, the valid target is actually http://127.0.0.1:3000, while node base functions like proxyApp.web() resolve its host name to [::1]. This problem affects users who use Node.js >=18.16

So is it possible to change the default host to follow node 18?

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

For example, should line 56 in "create-react-app\packages\react-scripts\scripts\start.js" be changed to something like:
```
const HOST = process.env.HOST || localhost;
```
or
```
const HOST = process.env.HOST || "::";
```
Repository: PowerToys
Issue: Power toys run - Windows settings are sometimes shown first and do not respond to Global sort order score modifier
Labels: Issue-Bug,Product-PowerToys Run,Needs-Triage

### Microsoft PowerToys version

0.71.0

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

It happens with lots of searches, but for example: when searching for "webflow" I type "web" and the first result is always "Apps for Websites" no matter how much I use the Webflow app and dont use "Apps for Websites". Changing the Global sort order score modifier both on programs and on Windows settings seems to have no effect.

### ✔️ Expected Behavior

Show me "Webflow" before showing me "Apps for Websites".

### ❌ Actual Behavior

It shows me "Apps for Websites" and the Global sort order score modifier does not seem to be having any effect.

### Other Software

_No response_
Repository: pytorch
Issue: DISABLED test_cuda_memory_leak_detection (__main__.TestCudaMultiGPU)
Labels: module: cuda,triaged,module: flaky-tests,skipped

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_cuda_memory_leak_detection&suite=TestCudaMultiGPU) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/14816707226).

Over the past 3 hours, it has been determined flaky in 2 workflow(s) with 2 failures and 2 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_cuda_memory_leak_detection`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.


Test file path: `test_cuda_multigpu.py`

cc @ptrblck
Repository: next.js
Issue: Url which contain several locales have strange behaviour
Labels: bug,Navigation,Runtime

### Verify canary release

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

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 21:00:17 PST 2023; root:xnu-8796.101.5~3/RELEASE_X86_64
    Binaries:
      Node: 16.15.1
      npm: 8.11.0
      Yarn: 1.22.11
      pnpm: N/A
    Relevant packages:
      next: 13.2.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)

Internationalization (i18n), Middleware / Edge (API routes, runtime), Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/tender-shannon-ykkmm6?file=%2Fmiddleware.ts%3A4%2C1

### To Reproduce

1. Open /en/fr url
2. Check middleware log

### Describe the Bug

When /en/fr (or similar url with two locales) next resolve locale incorrect in middleware and 404 page shown incorrectly. I have a `Error: Invariant: The detected locale does not match the locale in the query. Expected to find 'fr' in '/en/fr' but found 'en'}` in my case, in CodeSendbox reproduction hard navigate error caused. Middleware logs "/en/fr" with "fr" locale.


### Expected Behavior

404 page should be shown with "en" locale (first part of the url) without errors
Middleware shoud log "/fr" pathname with "en" locale 

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

_No response_

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

_No response_
Repository: flutter
Issue: iOS build scheme's environment variables not being passed to xcodebuild
Labels: c: new feature,platform-ios,tool,t: xcode,c: proposal,P3,team-ios,triaged-ios

### Is there an existing issue for this?

- [X] I have searched the [existing issues](https://github.com/flutter/flutter/issues)
- [X] I have read the [guide to filing a bug](https://flutter.dev/docs/resources/bug-reports)

### Use case

Hi everyone. I'm building an android and iOS app and need to integrate the [google_maps_flutter](https://pub.dev/packages/google_maps_flutter) plugin. The package requires a specific platform configuration where an api key must be provided and the app I'm building supports multiple flavors. Also I need to specify a different api key for each app flavor.

On iOS platform, I have tried to specify the api key as a build scheme's environment variable.
I thought it was quite a straightforward way to accomplish such platform configuration on iOS, since flutter flavors rely on build schemes. But then I realise that the environment variable is available only if I build and run the iOS project from Xcode, otherwise it is completely ignored when building the project with flutter cli tools.


### Proposal

Should build scheme's environment variable being considered when building for iOS platform?
Repository: next.js
Issue: Redirect by middleware works incorrect for site navigation via Link (with locale change)
Labels: bug,Navigation

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 22.4.0: Mon Mar  6 21:00:17 PST 2023; root:xnu-8796.101.5~3/RELEASE_X86_64
    Binaries:
      Node: 16.15.1
      npm: 8.11.0
      Yarn: 1.22.11
      pnpm: N/A
    Relevant Packages:
      next: 13.4.9-canary.2
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 4.5.5
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Internationalization (i18n), Middleware / Edge (API routes, runtime), Routing (next/router, next/navigation, next/link)

### Link to the code that reproduces this issue or a replay of the bug

https://codesandbox.io/p/sandbox/laughing-northcutt-wmc65k?file=%2Fpages%2Findex.tsx%3A17%2C11

### To Reproduce

1. Open /fr locale
2. Click to the link "Open to the OnlyEnPage" (you should open a Link to the page which should be redirected)
3. Check middleware logs

### Describe the Bug

When you have a Link to the page which should be redirected, you can't use next redirects but you can use middleare to perform redirect.

In next 13.3+ versions if you navigate to a page with locale redirect redirect not happened correctly. In reproduction page will be show correctly (with correct locale) but an url will be incorrect - with wrong locale. Middleware logs a bad data - pathname is "/fr/en/only-en-page" with locale "en"

I have an ` Error: Invariant: The detected locale does not match the locale in the query. Expected to find 'en' in '/fr/en/only-en-page' but found 'fr'}` error in my case and url "/fr/en/only-en-page"
### Expected Behavior

1. Url should be shown correctly - "/en/only-en-page"
2. Middleware should have correct data - pathname should be "/only-en-page" and locale "fr" and "/only-en-page" with locale "fr" after redirect.


### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_
Repository: next.js
Issue: Static page generates two different pages, one for initial navigation and one for client side navigation
Labels: bug

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 19.6.0: Mon Aug 31 22:12:52 PDT 2020; root:xnu-6153.141.2~1/RELEASE_X86_64
    Binaries:
      Node: 16.20.1
      npm: 8.19.4
      Yarn: 3.6.0
      pnpm: 8.6.6
    Relevant Packages:
      next: 13.4.9-canary.2
      eslint-config-next: N/A
      react: 18.2.0
      react-dom: 18.2.0
      typescript: 5.1.6
    Next.js Config:
      output: N/A
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

App Router

### Link to the code that reproduces this issue or a replay of the bug

https://github.com/O4epegb/nextjs-page-duplicate

https://nextjs-page-duplicate-l2clkuj8y-danila.vercel.app/

### To Reproduce

https://nextjs-page-duplicate-l2clkuj8y-danila.vercel.app/

1) Go to index page, you will see page number and a link to `/test` page
2) Press `/test` page link, then press `/index` link to go back again to the index page
3) The page number will be different

### Describe the Bug

Both pages are completely static and use `use server` (implicitly), but after back and forth client side navigation we basically get a different page compared to what we've got on initial SSR navigation.

I'm not entirely sure that this is a bug, but it was little bit unexpected for me while migrating pages with `getStaticProps` function.



### Expected Behavior

I would expect the page to be generated just once so there is no difference between direct first time navigation to the page and client side navigation.

But I understand that I might be wrong here and to achieve the same behaviour as `getStaticProps` version I need to use some different way? I've tried to use React `cache()`, but it does not change anyhting.

I understand that the page uses `Math.random()`, but is was possible before to run it in `getStaticProps` to achieve consistency between SSR and CSR. I don't understand how to do it right now, but again, maybe I'm missing some crucial info.

### Which browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

Vercel
Repository: pytorch
Issue: [feature request] Specialized memory layouts and wide blocked/tiled dtypes for cublasLt (`CUBLASLT_ORDER_COL32`, `CUBLASLT_ORDER_COL4_4R2_8C`, `CUBLASLT_ORDER_COL32_2R_4R4`)/onednn: e.g. torch.float16x32 / torch.int8x32 / torch.bits1x512 (akin to torch.quint2x4)
Labels: feature,triaged,module: memory format

### 🚀 The feature, motivation and pitch

I found a blog post explaining how to get speedups by using int8 gemm kernels on CUDA: https://www.speechmatics.com/company/articles-and-news/fast-and-accurate-gpu-quantization-for-transformers

It mentions several specialized memory layouts to maximize perf of cublas gemm ops (found them documented in https://docs.nvidia.com/cuda/cublas/#cublasltorder-t):
- `CUBLASLT_ORDER_COL32` (mentioned as the most performant memory layout for cublasLt int8 gemms)
- `CUBLASLT_ORDER_COL4_4R2_8C`
- `CUBLASLT_ORDER_COL32_2R_4R4`

These memory formats/layouts seem important for max-perf cublasLt for int8, as evidenced by this blog post and FasterTransformer kernels. @vkuzo are these formats supported by `_int_mm` in https://github.com/pytorch/pytorch/pull/96685?

Is `CUBLASLT_ORDER_COL32` logically representable in PyTorch? Other formats?

For int8, I would understand this means as if there was dtype holding 32-sized tiles/tuples of `torch.int8`  (32 bytes = 256 bits), currently the widest dtype is `complex128` (supposed to hold a tuple of two float64 i.e. 16bytes = 128 bits). (and then these tuples are stored in column-major)

So IMO a minimal way to support it would be:
- introducing uninterpreted (except torch.to/torch.view/print) dtypes `torch.int8x32`, maybe `torch.float16x32` and so forth
  - https://github.com/pytorch/pytorch/pull/94992 introduced `torch.bits2x4` (there also exists torch.quint2x4`) and `torch.bits16`, so maybe at least `torch.bits2048` could be added?
- implementing int8_tensor.to(dtype = torch.int8x32) and maybe tensor.view(torch.int8x32)
- an alternative way might be to introduce separate `memory_format=` supporting conversions to these layouts via this avenue (especially for `CUBLASLT_ORDER_COL32_2R_4R4`?)

In that blog post they are fusing the quantization + conversion into a LayerNorm kernel, but I guess this can be introduced later (if needed at all).

Also, FasterTransformer has many COL32 kernels: https://github.com/NVIDIA/FasterTransformer/blob/main/src/fastertransformer/kernels/unfused_attention_int8_kernels.cu

It also appears that similar tiled/blocked memory formats dtypes are used for MKLDNN: https://oneapi-src.github.io/oneDNN/v1.0/dev_guide_understanding_memory_formats.html and are probably already supported by calling `.to_mkldnn()` / weight prepacking. I wonder if supporting such tupled-dtypes could be good and unify the layouts for cublasLt and MKLDNN (cc @jamesr66a @mingfeima)

For onednn it is:
- nChw16c
- nChw8c

@jerryzh168 @vkuzo @ngimel this is probably also related to int8 gemm code paths as we discussed in https://github.com/pytorch/pytorch/issues/69364

(256 bit AVX2's equivalent is float32x8, and for AVX512 it's float32x16
Repository: godot
Issue: Stretching Windows window too much with stretch mode set to viewport can cause it to go black.
Labels: bug,topic:rendering

### Godot version

v4.1.stable.official.970459615

### System information

Windows 10.0.19045 - Vulkan (Compatibility) - GeForce GT 540M () - Intel(R) Core(TM) i7-2670QM CPU @ 2.20GHz (8 Threads)

### Issue description

When stretch mode is set to viewport and stretch aspect to keep width, keep height or expand, stretching the game's window too much can cause it's content to disappear and turn black.

The bug happens for any type of node (node, node 2d, node 3d, control).

The disappearance is dependent on the aspect ratio of the window rather than its width/height alone, making the window higher when it is very wide can make its content be visible again.

The window width at which it happens depends on the set window width and height, with higher values making the window turn black at aspect ratios closer to 1:1. (To test the issue I also set window size overrides to make the window fit on screen)

When the bug happens, the project's debugger is spammed with warning messages:
```cmd
WARNING: Could not create render target, status: GL_FRAMEBUFFER_INCOMPLETE_ATTACHMENT
     at: _update_render_target (drivers/gles3/storage/texture_storage.cpp:1767)
```

I only tested it with the compatibility renderer, because the others don't work on my pc.

Please check out this video on which I reproduce the issue:

https://github.com/godotengine/godot/assets/84321760/ee9c6499-eaf2-497c-a74b-cddcbfe1d28d



### Steps to reproduce

0. Use the minimal reproduction project or:
1. Create a new project. (I used compatibility renderer).
2. Set stretch mode to viewport in project settings.
3. Set stretch aspect to keep width, keep height (hard to reproduce, the window needs to be very high for it) or expand.
4. Create any scene.
5. Run the project.
6. Stretch the window very wide and short at the same time.
7. Observe the content going black and a warning being printed.

### Minimal reproduction project

[BlackScreenOnWindowStretchTest4.1.zip](https://github.com/godotengine/godot/files/11968292/BlackScreenOnWindowStretchTest4.1.zip)