sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: next.js
Issue: 15X Build Slowdown in the Latest NextJS Version
Labels: bug,Lazy Loading

### Link to the code that reproduces this issue

https://github.com/MartinXPN/next-slow-build-reproduction

### To Reproduce

```shell
# You can run `yarn build` instead to see the execution time
npm run build     # (~500s) This will build the app with the latest Next.js version
npm uninstall next && npm install next@13.4.19 && rm -rf .next
npm run build     # (~35s) This will build the app with the previous Next.js version
```

### Current vs. Expected behavior

It currently takes ~15x longer to build a project with a large client-side component compared to the previous NextJS version. This **REALLY** hurts the developer experience!
It should take way quicker to build the whole project and produce the production build.

For this small project, it took ~500s to build with the latest Next.js version, while it used to take only ~40 with the 13.4.9 version.

Using the latest version of NextJS actually resulted in a 20x build slowdown on one of my actual projects (not the reproduction above) making each build ~40 minutes instead of 2. Imagine how terrible it is to wait for 40 minutes for every minor change to hit production!

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.4.0: Wed Feb 21 21:45:49 PST 2024; root:xnu-10063.101.15~2/RELEASE_ARM64_T6020
Binaries:
  Node: 20.10.0
  npm: 10.2.3
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.1.3
  eslint-config-next: 14.0.3
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.4.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure, App Router, Dynamic imports (next/dynamic)

### Which stage(s) are affected? (Select all that apply)

next build (local), Vercel (Deployed)

### Additional context

I've also reproduced this with a large form using `react-hook-form` and `zod`.

There was a [recent fix](https://github.com/vercel/next.js/pull/60859) that was supposed to fix this issue but actually had no effect on my projects.

<img width="712" alt="Screenshot 2024-03-15 at 1 13 18 PM" src="https://github.com/vercel/next.js/assets/16335716/cde8f3c9-2731-4607-9857-be5ff637847d">
<img width="711" alt="Screenshot 2024-03-15 at 1 13 38 PM" src="https://github.com/vercel/next.js/assets/16335716/2030157b-95e6-4c2c-adba-b1bab2f6623a">

This is the same project with the same dependencies (NextJS latest version VS `13.4.9`).
Imagine the pain of waiting 40 minutes every time you push to production (while it used to take only 2 minutes).
Repository: vscode
Issue: SCM - Hidden local changes indicator "*" in "source control repositories" view
Labels: bug,ux,scm,papercut :drop_of_blood:

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 
Version: 1.87.1 (system setup)
Commit: 1e790d77f81672c49be070e04474901747115651
Date: 2024-03-06T00:21:36.258Z
Electron: 27.3.2
ElectronBuildId: 26836302
Chromium: 118.0.5993.159
Node.js: 18.17.1
V8: 11.8.172.18-electron.0
OS: Windows_NT x64 10.0.19045
- OS Version: Versión 22H2 (compilación de SO 19045.3086)

Steps to Reproduce:

1. Have a repo with local changes -> an "*" is added at the right of the branch name
2. Reduce the panel size (positioned at the right side) so that the branch name is clipped at the right (worsened with long names)
3. The "*" is no longer visible, losing the indication of existing local changes. This happens whenever the repo is not selected and its changes not shown in the source control view.

![2024-03-15_(095048)_Code](https://github.com/microsoft/vscode/assets/26868611/e35b1c26-0104-44e3-9019-ba53ced4b48b)

Potential solutions:
* Move the "*" to the left
* Make it not clippable
* Itegrate it with the sync button instead of appending it to the name, new icon? or could just be it
* Repos with changes could also be colored differently

Best regards!
Repository: vscode
Issue: [FR] Add option to disable icon bouncing in macOS's dock - 2
Labels: macos

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

I would like to re-request this feature: https://github.com/microsoft/vscode/issues/104365 
Not sure how to turn off the setting, and I don't think it should be an undocumented thing. 

Every time I'm watching a movie on my Mac, this dock icon starts jumping just cause I lost an SSH connection and it's so annoying.
Repository: PowerToys
Issue: always on top边框大小问题
Labels: Issue-Bug,Product-Always On Top,Needs-Triage

### Microsoft PowerToys version

v0.79.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Always on Top

### Steps to reproduce


<img width="277" alt="9aa7905834b478b13473cfade14dbf4" src="https://github.com/microsoft/PowerToys/assets/102527585/8f389a64-5433-494d-8605-486eb1903e45">
<img width="277" alt="9aa7905834b478b13473cfade14dbf4" src="https://github.com/microsoft/PowerToys/assets/102527585/15bae240-2ee1-473e-bfc2-9c436e9dc0e8">
打开任意窗口，使用always on top，会发现周围边框与窗口大小不符，并且红色边框内的区域无法点击。


### ✔️ Expected Behavior

边框大小与窗口大小符合

### ❌ Actual Behavior

边框大小与窗口大小不符合

### Other Software

_No response_
Repository: tauri
Issue: [bug] how to use sidecar in mobile?
Labels: type: bug,status: needs triage

### Describe the bug

how use sidecar in mobile?

### Reproduction

_No response_

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 14.3.0 X64
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.75.0 (82e1608df 2023-12-21)
    ✔ cargo: 1.75.0 (1d8b05cdd 2023-11-20)
    ✔ rustup: 1.26.0 (5af9b9484 2023-04-05)
    ✔ Rust toolchain: stable-x86_64-apple-darwin (default)
    - node: 18.14.0
    - pnpm: 8.15.1
    - npm: 9.3.1

[-] Packages
    - tauri [RUST]: 2.0.0-beta.8
    - tauri-build [RUST]: 2.0.0-beta.6
    - wry [RUST]: 0.37.0
    - tao [RUST]: 0.26.1
    - @tauri-apps/api [NPM]: 2.0.0-beta.0
    - @tauri-apps/cli [NPM]: 2.0.0-beta.1

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: ../dist
    - devUrl: http://localhost:1420/
    - framework: Vue.js
    - bundler: Vite
```


### Stack trace

_No response_

### Additional context

_No response_
Repository: ollama
Issue: Please add the memory requirement estimate if run with cpu and vram request for run with GPU for each model in model list. 
Labels: feature request

### What are you trying to do?

I want to know if my computer can support the model or not, but currently no one can tell me.

### How should we solve this?

Add the memory needed for each model tag if run on cpu.
Add the vram needed for each model tag if run on GPU.

### What is the impact of not solving this?

All users had to download each model and test, this will be a big waste of resources.

### Anything else?

_No response_
Repository: TypeScript
Issue: Reverse mapped type inference fails to infer from annotated parameters in partially-inferrable object types
Labels: Help Wanted,Possible Improvement

### 🔎 Search Terms

reverse mapped inference annotated parameters partially inferrable noninferrable object context sensitive

### 🕗 Version & Regression Information

- This is the behavior in every version I tried

### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=5.5.0-dev.20240315#code/CYUwxgNghgTiAEAzArgOzAFwJYHtXwGcQNkAHAHgBUBxZWYAgPgAoB9ALngG8AoeeAOZ0YDTr378A2gGl4WfAGsQATxyJ4NYQwC6nZpgAenNAtQ4A7qgA08UrCgBbAp030CM7QEp4AXkbwAIxwcCBAoVABuPngAXyiYzxdaNyieMDwCDEEtAl9CYjJmcWy3MWj+KD1vP3gMGGQQK3LAvVYbOxhHAmr-OoamiXgwVvb7J05UZAcAkBge2vrG6JimhNShNx4Aei34AD0AfiA

### 💻 Code

```ts
declare function setup<TGuards>(_: {
  guards: {
    [K in keyof TGuards]: (ctx: unknown, params: TGuards[K]) => boolean;
  };
}): TGuards;

const guards = setup({
  guards: {
    a: () => true,
    b: (_, params) => true,
    c: (_, params: number) => true,
  },
});

guards
// ^? const guards: { a: unknown; b: unknown; c: unknown; }
```


### 🙁 Actual behavior

It infers `{ a: unknown; b: unknown; c: unknown; }`

### 🙂 Expected behavior

I'd expect `{ a: unknown; b: unknown; c: number; }` to get inferred here

### Additional information about the issue

_No response_
Repository: node
Issue: Missing content-security-policy header in response using http2 client
Labels: regression,http2

### Version

18.13.0

### Platform

Darwin XXX 22.5.0 Darwin Kernel Version 22.5.0: Thu Jun  8 22:22:20 PDT 2023; root:xnu-8796.121.3~7/RELEASE_ARM64_T6000 arm64 arm Darwin

(it also happens on Ubuntu 22.04)

### Subsystem

http2

### What steps will reproduce the bug?

Create a http2 client and perform a request to an endpoint that sets a `content-security-policy` HTTP header.

```js
const http2 = require("node:http2");

const session = http2.connect("https://plantview.i.mercedes-benz.com");

session.on("error", console.error);

const req = session.request({ ":path": "/" });
req.end();

req.on("response", (headers) => {
  // should display true
  console.log(Object.keys(headers).includes("content-security-policy"));
});

req.on("data", (data) => {});

req.on("end", () => {
  session.close();
});
```

### How often does it reproduce? Is there a required condition?

It happens consistently.

### What is the expected behavior? Why is that the expected behavior?

The `content-security-policy` header should be present in the headers of the `response` event.

### What do you see instead?

The `content-security-policy` header is missing.

### Additional information

The header is visible on `Node.js 18.12.1` and missing as of [Node.js 18.13.0](https://github.com/nodejs/node/blob/main/doc/changelogs/CHANGELOG_V18.md#2023-01-05-version-18130-hydrogen-lts-danielleadams).

It works fine using `node:https`:

<details>

<summary>Reproduction example</summary>

```js
const https = require("node:https");

const req2 = https.request("https://plantview.i.mercedes-benz.com");
req2.end();

req2.on("response", (req) => {
  console.log(
    "https",
    Object.keys(req.headers).includes("content-security-policy")
  );
});

req2.on("data", (data) => {});

req2.on("end", () => {
  session.close();
});
```

</details>
Repository: electron
Issue: [Bug]: Confirm/Alert popups break focus
Labels: bug :beetle:,has-repro-gist,29-x-y

### Preflight Checklist

- [x] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

29.1.4

### What operating system are you using?

Windows

### Operating System Version

Edition:	Windows 10 Home | Version:	22H2 | OS build:	19045.4170 | Experience:	Windows Feature Experience Pack 1000.19054.1000.0

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

Using a popup (alert or confirm) then trying to focus an input element shouldn't cause issues.

### Actual Behavior

When the application is launched, there are no problems interacting with an input element.

After clicking on a popup from `confirm` or `alert`, trying to focus the window that just caused the popup (namely an input element) will no longer work.

Focusing on another window and refocusing the window repairs the issue.

### Testcase Gist URL

https://gist.github.com/LqdBcnAtWork/9af23d4faa33e74874cd08ffbc8e4ed6

### Additional Information

I've noticed this issue for a while, but didn't catch onto the issue being caused by popups. I thought it was random and was caused by some strange interaction with focus that I was causing on my end. Having diagnosed the problem's cause, creating a Fiddle that could replicate it took seconds.

I mention this because it means the issue has existed for many major versions of Electron. How far back is unknown to me. But it goes at least as far back as version 21. I tried version 12.2.3 for fun with Fiddle and the problem persists.

I believe this is caused by the popup taking focus, but the window doesn't recognise that it gets focus _back_ when the popup is closed. I also think this issue might be on Chromium's end. But I'm unsure since neither Chrome or Edge (the only other Chromium apps I have available to me) use the same kind of popup for `alert` and `confirm` or display this issue.
Repository: PowerToys
Issue: The shortcut mapping configuration in keyboard Manager becomes invalid the next day
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage

### Microsoft PowerToys version

0.79.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

![image](https://github.com/microsoft/PowerToys/assets/153173018/a82989ee-ba00-4956-994f-0976b1b330c8)


### ✔️ Expected Behavior

Normally, you should map Alt+C to Ctrl+C


### ❌ Actual Behavior

No replication actually takes place


### Other Software

_No response_
Repository: godot
Issue: `Camera2D` disrupts low processor mode
Labels: needs testing,topic:2d

### Tested versions

Godot 4.2, 4.3

### System information

Windows 10 - AMD Radeon R7 Graphics, OpenGL3 angle and Vulkan

### Issue description

The `Camera2D` disrupts low processor mode in GUI projects like GodSVG or Pixelorama, which use (or used to use) it for dynamic viewports. It causes high GPU usage on idle.

Note: this was not reproducible by other people on Linux or other hardware for some reason. It could also be that my hardware is so underpowered that it's just more noticeable on it.

### Steps to reproduce

Add a `Camera2D` to a project that uses low processor mode and observe the GPU usage staying high on idle.

### Minimal reproduction project (MRP)

-

### Temporary solution

The `Camera2D` can be replaced with a custom implementation using the `Viewport` `canvas_transform` property.
Repository: stable-diffusion-webui
Issue: [Feature Request]: Support python 3.12 -> Upgrade torch to 2.2
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 ?

From the documentation [here](https://github.com/AUTOMATIC1111/stable-diffusion-webui?tab=readme-ov-file#automatic-installation-on-windows), Python 3.10.6 is the latest version compatible with torch. 

This seems to have changed according to the closing of [this issue](https://github.com/pytorch/pytorch/issues/110436), as torch 2.2.0 now supports Python 3.12.

Thus, upgrading the torch dependancy would allow us to use a newer version of python.

One potential caveat is that torch.compile is not yet supported as you can see [here](https://github.com/pytorch/pytorch/issues/120233).

As I [searched the code base](https://github.com/search?q=repo%3AAUTOMATIC1111%2Fstable-diffusion-webui+torch.compile&type=code) I found no direct usage of torch.compile, but I did find something about SwinIR. Not sure if this is enough to block the upgrade?

I also do not know if any code would need to be updated as torch is upgraded, but perhaps this issue/thread can be used as ground for discussion.

### Proposed workflow

1. Upgrade torch dependency to v2.2.x
2. ???
3. Profit (newer python version compatibility)

### Additional information

_No response_
Repository: pytorch
Issue: [RFC] Use CUDA graphs by default on torch.compile
Labels: triaged,oncall: pt2,module: inductor

### 🐛 Describe the bug

I keep seeing comparisons between JAX / TF / Keras vs `torch.compile` where they benchmark the "default XLA settings vs. the default `torch.compile`" to find that XLA frontends are x3-x4 faster than `torch.compile`.
The last one I found is the newly posted Keras 3 benchmarks
https://keras.io/getting_started/benchmarks/ 
but I have seen these skewed comparisons over and over again.

The only thing stopping us from compiling with CUDA graphs on is that these sometimes have a higher mem footprint. Would it be reasonable to turn these on by default so that people get speed by default, and then catch a potential OOM and re-raise it indicating that using CUDA-graphs off to potentialy mitigate the OOM?

cc @ezyang @msaroufim @bdhirsh @anijain2305 @zou3519 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @peterbell10 @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @aakhundov @ColinPeppler @amjames @desertfire @jansel @albanD @eellison @Chillee 

### Versions

master
Repository: opencv
Issue: Improve FileStorage documentation
Labels: feature,category: documentation

### Describe the doc issue

Hello everyone,
I wanted to try to use FileStorage to upload an XML file and couldn't do it. 
So I created a post on the OpenCV forum and one on Stackoverflow

https://forum.opencv.org/t/using-opencv-filestorage-to-read-a-xml-file/16812/5

https://stackoverflow.com/questions/78161034/using-opencv-filestorage-to-read-a-xml-file?noredirect=1#comment137802795_78161034

(Sorry for the crosspost)

What I didn't realize is that I can't just load any file.
My proposal is to explain the situation better on the documentation.
One could take a cue from @crackwitz 's answer 

### Fix suggestion

OpenCV does not read arbitrary XML/YAML/JSON. For that purpose you need to use a generic XML/YAML/JSON library.
cv::FileStorage is made specifically to store and read OpenCV types (e.g. cv::Mat). 
It assumes a specific structure to the file. This is specific to cv::FileStorage. For example in the case of a XML file one requirement is that all the data is contained in a <opencv_storage> tag.
Repository: pytorch
Issue: which Pythorch suports "TORCH_USE_CUDA_DSA=1" from the shell environment?
Labels: module: docs,triaged

Hi,

I would like to know what version or build has been tested and works with "TORCH_USE_CUDA_DSA=1"?

Thanks.

cc @svekars @brycebortree
Repository: rust
Issue: GCC builds are taking 30 min in PR CI
Labels: T-infra

Looking at the logs for the "PR - x86_64-gnu-llvm-16" and "PR - x86_64-gnu-tools" CI jobs, both of them seem to be spending 30 minutes building GCC. Excerpt from the [llvm-16 logs](https://productionresultssa18.blob.core.windows.net/actions-results/c10258ff-5f9f-4d44-b3c5-24cdd6da327a/workflow-job-run-a64ed217-e4bb-5680-9c18-8f3ddeed4bfc/logs/job/job-logs.txt?rsct=text%2Fplain&se=2024-03-15T14%3A13%3A59Z&sig=m4vnLi0yHWT9ONq1b%2FR6bDynBc2cL47AeQSQGKvcmig%3D&sp=r&spr=https&sr=b&st=2024-03-15T14%3A03%3A54Z&sv=2021-12-02):
```
2024-03-14T20:31:31.0313582Z #13 [8/8] RUN sh /scripts/build-gccjit.sh /scripts
2024-03-14T20:31:31.1420705Z #13 0.262 + cd /scripts
2024-03-14T20:31:31.1421386Z #13 0.262 + git clone https://github.com/antoyo/gcc gcc-src
[...]
2024-03-14T21:02:52.4850388Z #13 1881.6 + ln -s /scripts/gcc-install/lib/libgccjit.so /usr/lib/x86_64-linux-gnu/libgccjit.so
2024-03-14T21:02:52.6362274Z #13 1881.6 + ln -s /scripts/gcc-install/lib/libgccjit.so /usr/lib/x86_64-linux-gnu/libgccjit.so.0
2024-03-14T21:02:53.0817083Z #13 DONE 1882.2s
```
Notice the timestamps and the time printed at the end (that's from Docker, I think).

Not sure if these should be cached, but something seems to be going wrong here. Note that this happens before rustc tests are run, so this increase the latency for ui test failures by 30min (or by 50% above the baseline of not running GCC).

This probably regressed in https://github.com/rust-lang/rust/pull/122042. (The build-gccjit.sh script did not exist before that PR.)

Cc @antoyo @GuillaumeGomez  @Mark-Simulacrum
Repository: godot
Issue: Caching scene groups can take a long time while the editor is unresponsive
Labels: bug,topic:editor,usability,performance

### Tested versions

4.3 after #60965

### System information

Windows 10.0.19045 - Vulkan (Forward+) - dedicated NVIDIA GeForce GTX 1060 (NVIDIA; 31.0.15.4633) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)

### Issue description

When a project doesn't have `scene_groups_cache.cfg`, the editor will crawl every scene and fetch node groups. During this process the editor is unresponsive and it may take a looooong time if the scenes are heavy and there is many of them.

- [x] We should add some progress bar for this action, so the user knows that something is happening.
- [ ] It would be nice if fetching groups did not involve fully loading the scene, because if it references some heavy resources, they are being repeatedly loaded and unloaded, which is just wasteful. You don't need to do that to know groups.

### Steps to reproduce

1. Have a big project
2. Don't have `scene_groups_cache.cfg` in your `.godot` folder
3. Open the project
4. ⏳⏳⏳💀

### Minimal reproduction project (MRP)

[LongGroups.zip](https://github.com/godotengine/godot/files/14616584/LongGroups.zip)
Can be used to test both raised points.
Repository: vscode
Issue: Link package.json properties that expect a when clause to the definition of the language
Labels: debt

What is Condition?

![Code_-_Insiders_rlm1v7tltN](https://github.com/microsoft/vscode/assets/2931520/6943c87e-56f8-4d69-8919-166e60e80d9f)