sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: DISABLED test_cache_load_function_device_cuda_float32_dynamic_False_bundle_triton_True_grad_False (__main__.TestFxGraphCache)
Labels: module: rocm,triaged,module: flaky-tests,skipped,oncall: pt2,module: inductor

Platforms: rocm

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

Over the past 3 hours, it has been determined flaky in 4 workflow(s) with 5 failures and 4 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_cache_load_function_device_cuda_float32_dynamic_False_bundle_triton_True_grad_False`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/pytorch/test/inductor/test_codecache.py", line 146, in test_cache_load_function
    self.assertEqual(
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 4028, in assertEqual
    raise error_metas.pop()[0].to_error(  # type: ignore[index]
AssertionError: Scalars are not equal!

Expected 7 but got 14.
Absolute difference: 7
Relative difference: 1.0

To execute this test, run the following from the base repo dir:
    PYTORCH_TEST_WITH_ROCM=1 python test/inductor/test_codecache.py TestFxGraphCache.test_cache_load_function_device_cuda_float32_dynamic_False_bundle_triton_True_grad_False

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `inductor/test_codecache.py`

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd @clee2000 @wdvr @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang @aakhundov
Repository: pytorch
Issue: DISABLED test_cache_hot_load_device_cuda_bfloat16_dynamic_False (__main__.TestFxGraphCache)
Labels: module: rocm,triaged,module: flaky-tests,skipped,oncall: pt2,module: inductor

Platforms: rocm

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

Over the past 3 hours, it has been determined flaky in 4 workflow(s) with 4 failures and 4 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_cache_hot_load_device_cuda_bfloat16_dynamic_False`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/pytorch/test/inductor/test_codecache.py", line 363, in test_cache_hot_load
    self.assertEqual(counters["inductor"]["fxgraph_cache_miss"], 2)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/testing/_internal/common_utils.py", line 4028, in assertEqual
    raise error_metas.pop()[0].to_error(  # type: ignore[index]
AssertionError: Scalars are not equal!

Expected 2 but got 3.
Absolute difference: 1
Relative difference: 0.5

To execute this test, run the following from the base repo dir:
    PYTORCH_TEST_WITH_ROCM=1 python test/inductor/test_codecache.py TestFxGraphCache.test_cache_hot_load_device_cuda_bfloat16_dynamic_False

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `inductor/test_codecache.py`

cc @jeffdaily @sunway513 @jithunnair-amd @pruthvistony @ROCmSupport @dllehr-amd @jataylo @hongxiayang @naromero77amd @clee2000 @wdvr @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @chauhang @aakhundov
Repository: rust
Issue: Tracking issue for release notes of #118159: Implementation of `fmt::FormattingOptions`
Labels: relnotes,T-libs,needs-triage,relnotes-tracking-issue


This issue tracks the release notes text for #118159.

### Steps

- [ ] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Category (e.g. Language, Compiler, Libraries, Compatibility notes, ...)
- [Implementation of `fmt::FormattingOptions`](https://github.com/rust-lang/rust/pull/118159)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @EliasHolzmann, @m-ou-se -- origin issue/PR authors and assignees for starting to draft text
Repository: vscode
Issue: Provide the originating conversion in the MappedEdits
Labels: chat

> We never used the conversation in our mapper code. It turned out that the code block with just the markdown before the block as well as the input file works well. 
> 
> 
> 
> Would it be good enough to add the `ChatResult` from the response that contained the block?
> 
> Maybe lets open a new feature request so we can discuss this. 

 _Originally posted by @aeschli in [4f2c166](https://github.com/microsoft/vscode/commit/4f2c166752c938b98b14244acb4003126536278f#r151621031)_
Repository: storybook
Issue: [Bug]: Storybook not accessible from local hostname after Vite 6 upgrade
Labels: bug,good first issue,help wanted,compatibility with other tools,has workaround,core,builder-vite

### Describe the bug

After upgrading from Vite 5 to Vite 6, Storybook is no longer accessible via local hostname (e.g., timon-work.local) configured in macOS System Settings > Sharing. Despite setting the `--host` flag to `0.0.0.0` in the dev script, accessing Storybook through the local hostname results in 403 Forbidden errors:

![Image](https://github.com/user-attachments/assets/ba5ddb6f-a57e-4f9a-b580-f97e140c5794)

Setting `allowedHosts` in `vite.config.ts` doesn't resolve the issue. However, configuring it in `.storybook/main.ts` within the `viteFinal` function does work:

```ts
const config: StorybookConfig = {
  // ... snip
  viteFinal: (config) => {
    config.server ??= {};
    console.log(config.server);
    // Allow Storybook to be accessed from any host in development mode
    // config.server.allowedHosts = process.env.NODE_ENV === 'development' ? true : config.server.allowedHosts;
    return config;
  },
};
```

I've managed to reproduce this with a clean Storybook setup (`npx storybook@latest init`).

### Reproduction link

https://github.com/TimonVS/storybook-hostname-reproduction

### Reproduction steps

1. Create a Storybook project (`npx storybook@latest init`)
2. Setup a local hostname on macOS (System Settings > Sharing)
3. Add `--host 0.0.0.0` flag to `storybook` script

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 15.1
    CPU: (12) arm64 Apple M3 Pro
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 22.6.0 - ~/.local/share/mise/installs/node/22/bin/node
    npm: 10.8.2 - ~/.local/share/mise/installs/node/22/bin/npm
    pnpm: 9.15.0 - ~/Library/pnpm/pnpm <----- active
  Browsers:
    Chrome: 131.0.6778.265
    Safari: 18.1
```

### Additional context

_No response_
Repository: next.js
Issue: Turbopack fails to load valid .mjs module with UTF-8 error
Labels: please add a complete reproduction,Turbopack

### Link to the code that reproduces this issue

https://github.com/utsuboco/r3f-perf/blob/752adc19edbcabc43fc917519c5366718fa0b9d0/src/components/TextsHighHZ.tsx#L10

### To Reproduce



### Description
Turbopack is failing to load a valid .mjs module that exports a base64 string. The module is from [r3f-perf](https://github.com/utsuboco/r3f-perf)  package and contains a valid JavaScript file that exports a base64-encoded font string.


### Error Message

```sh
Module not found: Can't resolve '../roboto.woff.mjs'
8 | import as THREE from "three";
9 | import { useEvent } from "@utsubo/events";
> 10 | import localFont from "../roboto.woff.mjs";
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
11 | import { getPerf } from "../store.mjs";
failed to convert rope into string
Caused by:
invalid utf-8 sequence of 1 bytes from index 11
```

### Current vs. Expected behavior

### Expected Behavior
The file should load successfully as it's a valid ES module that simply exports a string:

```js
javascript
// Content of roboto.woff.mjs
const localFont = "data:font/woff;base64,..."
export { localFont as default };
```


### Actual Behavior
Turbopack appears to be attempting UTF-8 validation before module parsing, causing it to fail on what should be a valid JavaScript file. The same file loads correctly when using webpack.

Their package is Typescript and builds for CJS and ESM. I tried aliasing and it failed.


### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
  Available memory (MB): 40638
  Available CPU cores: 16
Binaries:
  Node: 20.9.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.23 // An outdated version detected (latest is 15.1.5), upgrade is highly recommended!
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.7.2
Next.js Config:
  output: N/A
```

### Which area(s) are affected? (Select all that apply)

Webpack, Turbopack, Developer Experience

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

### Additional context


- This worked in Next.js 14.1 with Turbopack
- Still works with webpack in Next.js 14.2
- The file is a valid ES module exporting a base64 string
- Attempted to use resolveAlias in turbo config but it's ignored
- Package affected: r3f-perf

Link to issue in other library : https://github.com/utsuboco/r3f-perf/issues/59

### Impact
This prevents using Turbopack with packages that use this pattern for asset loading, requiring fallback to webpack development server.
Repository: flutter
Issue: Linux web_canvaskit_tests_5 is 2.11% flaky
Labels: P0,c: flake,team-web

<!-- meta-tags: To be used by the automation script only, DO NOT MODIFY.
{
  "name": "Linux web_canvaskit_tests_5"
}
-->

The post-submit test builder `Linux web_canvaskit_tests_5` had a flaky ratio 2.11% for the past (up to) 100 commits, which is above our 2.00% threshold.

One recent flaky example for a same commit: https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20web_canvaskit_tests_5/17575
Commit: https://github.com/flutter/flutter/commit/da080e6976acd5c9f281f227f7df634ccfa84fae

Flaky builds:
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20web_canvaskit_tests_5/17575
https://ci.chromium.org/ui/p/flutter/builders/prod/Linux%20web_canvaskit_tests_5/17514

Recent test runs:
https://flutter-dashboard.appspot.com/#/build?taskFilter=Linux%20web_canvaskit_tests_5

Please follow https://github.com/flutter/flutter/blob/master/docs/infra/Reducing-Test-Flakiness.md#fixing-flaky-tests to fix the flakiness and enable the test back after validating the fix (internal dashboard to validate: go/flutter_test_flakiness).
Repository: next.js
Issue: Tree shaking in middleware doesn't work
Labels: Middleware,linear: next

### Link to the code that reproduces this issue

https://github.com/amannn/nextjs-bug-repro-middleware/commit/6c442b025f45b0f777fda6f32fc355e58bef1fb9

### To Reproduce

1. Run `pnpm i && pnpm build`
2. See console output and analyzer output


### Current vs. Expected behavior

**Console output:**

```
ƒ Middleware                             1.07 MB
```

I'd expect `getMessages` to not be bundled into the middleware as it's not used there.

See also the analyzer output:

![Image](https://github.com/user-attachments/assets/a1dd03f8-c9ff-49a8-b199-4c3c0ef930a0)

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:00 PDT 2024; root:xnu-10063.141.2~1/RELEASE_X86_64
  Available memory (MB): 16384
  Available CPU cores: 12
Binaries:
  Node: 20.11.1
  npm: 10.2.4
  Yarn: 1.22.22
  pnpm: 9.15.4
Relevant Packages:
  next: 15.1.5 // Latest available version is detected (15.1.5).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.7.3
Next.js Config:
  output: N/A
```

### Which area(s) are affected? (Select all that apply)

Middleware

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

_No response_
Repository: next.js
Issue: Lazy loaded component CSS doesn't contain assetPrefix
Labels: Lazy Loading,linear: next,Module Resolution,CSS

### Link to the code that reproduces this issue

https://github.com/GeorgeHulpoi/lazy-loaded-component-asset-prefix

### To Reproduce

1. Verify in development mode the behavior.
2. Build the project with `NEXT_PUBLIC_ASSET_PREFIX` (it will be ussed in `next.config.ts` / `assetPrefix`. 
3. Move the `_next/static` to the cdn / server / whatever (I used an S3 + CloudFront for this reproduction).
4. Start the server in production (everything should work fine).
5. Press on `Load lazy`.
6. You will see that the JS has loaded with `assetPrefix`:

![Image](https://github.com/user-attachments/assets/42bdd451-93bc-443a-a0d6-0f111ee15c3b)

Nonetheless, the CSS doesn't have the `assetPrefix`

![Image](https://github.com/user-attachments/assets/e3a22ba6-6a7a-4b3d-b7db-2a09e1712870)



### Current vs. Expected behavior

Within development environment, clicking on `Load lazy` will show the following:

![Image](https://github.com/user-attachments/assets/defdc7fa-6828-41d2-9279-071ec68b7bb6)

In production with the `assetPrefix` set, the CSS fails to load:

![Image](https://github.com/user-attachments/assets/d0afb3c6-6647-4ee6-9261-e86f9792bd7d)


### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 10 Pro
  Available memory (MB): 14189
  Available CPU cores: 16
Binaries:
  Node: 20.9.0
  npm: 10.1.0
  Yarn: 1.22.21
  pnpm: 9.15.0
Relevant Packages:
  next: 15.1.5 // Latest available version is detected (15.1.5).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: N/A
Next.js Config:
  output: N/A
```

### Which area(s) are affected? (Select all that apply)

Module Resolution, Lazy Loading

### Which stage(s) are affected? (Select all that apply)

next start (local)

### Additional context

_No response_
Repository: vscode
Issue: Wrong text expected
Labels: triage-needed


Type: <b>Bug</b>

I'm using VSCode Insider, with EVKey - A Vietnamese Keyboard, when i wrote "taij", it should be "tại" but the result was "taiại"

Update: VSCode resolves the problem

VS Code version: Code - Insiders 1.97.0-insider (d226a2a497b928d78aa654f74c8af5317d3becfb, 2025-01-22T05:05:14.565Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Xeon(R) CPU E3-1225 v5 @ 3.30GHz (4 x 3312)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: unavailable_off<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: unavailable_off<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|19.93GB (12.00GB free)|
|Process Argv|--crash-reporter-id 2467a45c-82aa-484d-9f03-9e53c22b4e29|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (12)</summary>

Extension|Author (truncated)|Version
---|---|---
codesnap|adp|1.3.4
vsc-material-theme|Equ|34.7.9
vsc-material-theme-icons|equ|3.8.12
copilot|Git|1.257.1326
copilot-chat|Git|0.24.2025012201
discord-vscode|icr|5.8.0
ia-vscode|Lon|0.1.5
vsliveshare|ms-|1.0.5948
material-icon-theme|PKi|5.17.0
vscode-yaml|red|1.15.0
vscode-spotify|shy|3.2.1
catppuccin-theme|Sir|0.3.1


</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythonvspyt551:31179976
vscod805:30301674
vsaa593cf:30376535
py29gd2263:31024238
c4g48928:30535728
2i9eh265:30646982
962ge761:30841072
pythonnoceb:30776497
dsvsc014:30777825
dsvsc015:30821418
pythonmypyd1:30859725
h48ei257:31000450
pythontbext0:30879054
cppperfnew:30980852
pythonait:30973460
dvdeprecation:31040973
dwnewjupyter:31046869
nativerepl1:31134653
pythonrstrctxt:31093868
nativeloc1:31118317
cf971741:31144450
e80f6927:31120813
iacca1:31150324
notype1:31143044
dwcopilot:31158714
h409b430:31177054
c3hdf307:31184662
6074i472:31201624
dwoutputs:31217127
8did9651:31218798
hdaa2157:31222309
copilot_t_ci:31222730

```

</details>

<!-- generated by issue reporter -->
Repository: electron
Issue: [Windows 11] `new BrowserWindow(...)` bug it shows a white screen, and after waiting for a while, the software automatically closed
Labels: platform/windows,bug :beetle:,blocked/need-repro,33-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

33.3.1

### What operating system(s) are you using?

Windows

### Operating System Version

Windows 11 23H2 or 24H2

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

Source: https://github.com/wangliang181230/dev-sidecar/tree/v2.0.0-RC4.3
Release: https://github.com/wangliang181230/dev-sidecar/releases/tag/v2.0.0-RC4.3

Open `Dev-Sidecar-2.0.0-RC4.3` without error.

### Actual Behavior

Open `Dev-Sidecar-2.0.0-RC4.3` but it shows a white screen, and after waiting for a period of time, the software automatically closed.
And no logs were recorded.

![Image](https://github.com/user-attachments/assets/bd6de39d-4cda-4cb1-a93e-8ce733964f05)

### Testcase Gist URL

_No response_

### Additional Information

_No response_
Repository: material-ui
Issue: [TextField] Autocomplete does not allow the select to open when text field uses input slotProps (any of them)
Labels: support: question,component: text field,status: waiting for author

### Steps to reproduce

Steps:
1. Open this link to live example: https://stackblitz.com/edit/react-eomwegjs?file=Demo.tsx
2. Click on Autocomplete, select will not open.


### Current behavior

Clicking on Autocomplete when input is provided to TextField component does not open the list. 

### Expected behavior

When clicking on the TextField the list should open (in this case the movies example)

### Context

I need to have an auto complete with a custom text field containing end adornments. 

### Your environment

Forked on stackblitz from MUI autocomplete example. 


**Search keywords**: TextField, slotProps, AutoComplete
Repository: PowerToys
Issue: World Clock
Labels: Needs-Triage

### Description of the new feature / enhancement

You can add a plugin or add in world clock functionality to PowerToys run to easily check the time in different countries.

### Scenario when this would be used?

To check world times easily.

### Supporting information

_No response_
Repository: pytorch
Issue: The possible error in the pytorch documentation of RNN.
Labels: module: rnn,triaged

### 📚 The doc issue

### 1. Where is the documentation?
URL: https://pytorch.org/docs/stable/generated/torch.nn.RNN.html#rnn

### 2. What is the possible error?
The documentation provide a piece of code about " Efficient implementation equivalent to the following with bidirectional=False " which is shown below:
```python
# Efficient implementation equivalent to the following with bidirectional=False
def forward(x, h_0=None):
    if batch_first:
        x = x.transpose(0, 1)
    seq_len, batch_size, _ = x.size()
    if h_0 is None:
        h_0 = torch.zeros(num_layers, batch_size, hidden_size)
    h_t_minus_1 = h_0
    h_t = h_0
    output = []
    for t in range(seq_len):
        for layer in range(num_layers):
            h_t[layer] = torch.tanh(
                x[t] @ weight_ih[layer].T
                + bias_ih[layer]
                + h_t_minus_1[layer] @ weight_hh[layer].T
                + bias_hh[layer]
            )
        output.append(h_t[-1])
        h_t_minus_1 = h_t
    output = torch.stack(output)
    if batch_first:
        output = output.transpose(0, 1)
    return output, h_t
```
However, the piece of code **does not explain** the implementation of RNN correctly because it uses `x[t]`as the input data to compute the `h_t[layer]`**in each RNN layer** at the time `t`. 

To compute the `h_t[layer]` correctly, the input data in each RNN layer at the time `t` should be 'x[t]' when `layer == 0` and 'h_t[layer-1]' when `layer > 0` respectively. 

Thus, the correct interpretation of the RNN implementation can be:

### 3. The code of possible correct interpretation of the RNN implementation
```python
def forward(x, h_0=None):

    if batch_first:
        x = x.transpose(0, 1)
    seq_len, batch_size, _ = x.size()
    if h_0 is None:
        h_0 = torch.zeros(num_layers, batch_size, hidden_size)
    h_t_minus_1 = h_0
    h_t = h_0
    output = []
    for t in range(seq_len):
        
        input_t = x[t]
        for layer in range(num_layers):
            h_t[layer] = torch.tanh(
                input_t @ weight_ih[layer].T
                + bias_ih[layer]
                + h_t_minus_1[layer] @ weight_hh.T
                + bias_hh[layer]
            )
            input_t = h_t[layer]

        output.append(h_t[-1])
        h_t_minus_1 = h_t
    output = torch.stack(output)
    if batch_first:
        output = output.transpose(0, 1)
    return output, h_t
```

### Suggest a potential alternative/fix

_No response_

cc @mikaylagawarecki