sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: 9 Dynamo test are failing with "Failed running call_function <function interpolate at 0xDEADBEEF".
Labels: low priority,triaged,oncall: pt2,module: dynamo

9 Dynamo test are failing with "Failed running call_function <function interpolate at 0xDEADBEEF".

## Repro

`PYTORCH_TEST_WITH_DYNAMO=1 pytest test_nn.py -v -k test_interpolate`

You will need to remove the skip or expectedFailure before running the repro command.
This may be just removing a line in
[dynamo_test_failures.py](https://github.com/pytorch/pytorch/blob/main/torch/testing/_internal/dynamo_test_failures.py)

## Failing tests

Here's a comprehensive list of tests that fail (as of this issue) with the above message:
<details>
<summary>Click me</summary>
```
test_nn.py::TestNN.test_interpolate
test_nn.py::TestNN.test_interpolate_buffer_overflow
test_nn.py::TestNN.test_upsamplingLinear1d
test_nn.py::TestNNDeviceTypeCPU.test_upsamplingTrilinear3d_align_corners_False_memory_format0_cpu
test_nn.py::TestNNDeviceTypeCPU.test_upsamplingTrilinear3d_align_corners_False_memory_format1_cpu
test_nn.py::TestNNDeviceTypeCPU.test_upsamplingTrilinear3d_align_corners_True_memory_format0_cpu
test_nn.py::TestNNDeviceTypeCPU.test_upsamplingTrilinear3d_align_corners_True_memory_format1_cpu
test_torch.py::TestTorch.test_upsample_nearest1d_meta
test_nn.py::TestNN.test_upsampling_bfloat16
```
</details>

cc @ezyang @anijain2305 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @msaroufim @bdhirsh @aakhundov
Repository: pytorch
Issue: 6 Dynamo test are failing with "torch.utils.checkpoint: trying to save more tensors during recomputation than during the original forward pass.".
Labels: triaged,oncall: pt2,module: dynamo

6 Dynamo test are failing with "torch.utils.checkpoint: trying to save more tensors during recomputation than during the original forward pass.".

## Repro

`PYTORCH_TEST_WITH_DYNAMO=1 pytest test_autograd.py -v -k test_nested_checkpoint_early_stop_False`

You will need to remove the skip or expectedFailure before running the repro command.
This may be just removing a line in
[dynamo_test_failures.py](https://github.com/pytorch/pytorch/blob/main/torch/testing/_internal/dynamo_test_failures.py)

## Failing tests

Here's a comprehensive list of tests that fail (as of this issue) with the above message:
<details>
<summary>Click me</summary>
```
test_autograd.py::TestNestedCheckpoint.test_nested_checkpoint_early_stop_False
test_autograd.py::TestNestedCheckpoint.test_nested_checkpoint_kwargs_early_stop_False
test_autograd.py::TestNestedCheckpoint.test_nested_checkpoint_non_tensor_inputs_and_outputs_early_stop_False
test_autograd.py::TestNestedCheckpoint.test_nested_checkpoint_reentrant_backwards_early_stop_False
test_autograd.py::TestNestedCheckpoint.test_nested_checkpoint_same_graph_early_stop_False
test_autograd.py::TestNestedCheckpoint.test_nested_checkpoint_two_children_early_stop_False
```
</details>

cc @ezyang @anijain2305 @chauhang @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @msaroufim @bdhirsh @aakhundov
Repository: next.js
Issue: Styled components global styles not reloading with app router
Labels: bug

### Link to the code that reproduces this issue

https://github.com/j2is/next-js-styled-components

### To Reproduce

Start the application, go to components/styles/GlobalStyles and change the background color to something else.
```
'use client';

import { createGlobalStyle, css } from "styled-components";

const styles = css`
  *{
    background: red; /* changing this value doesn't reload page */
  }
`;

const GlobalStyles = createGlobalStyle`
  ${styles}
`;

export default GlobalStyles;
```

### Current vs. Expected behavior

You should be able to see the updated css in the browser without manually reloading the browser

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: x64
  Version: Darwin Kernel Version 23.1.0: Mon Oct  9 21:27:27 PDT 2023; root:xnu-10002.41.9~6/RELEASE_X86_64
Binaries:
  Node: 18.17.0
  npm: 9.6.7
  Yarn: 1.22.19
  pnpm: N/A
Relevant Packages:
  next: 14.1.1-canary.51 // Latest available version is detected (14.1.1-canary.51).
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

App Router

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

next dev (local)

### Additional context

_No response_
Repository: pytorch
Issue: [c10d] Support NCCL group abort
Labels: triaged,module: nccl

### 🚀 The feature, motivation and pitch

https://github.com/NVIDIA/nccl/issues/1013 describes a case where two PGs both hang in their respective collective due to a rank's early exit. Calling abort on the two PGs one by one is not going to help because `ncclCommAbort` may incur a device-wise sync, which can be blocked by the hanging collective in the other PG. 

NCCL team's solution is to use the following semantic:
```
ncclGroupStart();
ncclCommAbort(comm1);
ncclCommAbort(comm2);
ncclGroupEnd();
```
i.e. using group semantic to abort the two comms simultaneously, see https://github.com/NVIDIA/nccl/issues/1013#issuecomment-1894576994

This semantic is experimental in a side branch for the moment:
https://github.com/NVIDIA/nccl/tree/github-abort-hang-fix

To support this semantic, PyTorch would need to add an abort API that's cross-PGs (as compared to the per-PG abort API today). Something like:
```
def abort_all_process_groups():
    _start_coalescing()
    for name, pg in pg_map.items():
        pg.abort()
    _end_coalescing()
```

### Alternatives

Use `ncclCommSplit` with `splitShare=1` flag to create multiple communicators:
https://github.com/NVIDIA/nccl/issues/1013#issuecomment-1876042348
But `splitShare=1` would serialize operations of those communicators.


Cc: @wconstab @shuqiangzhang @acphile @KaimingOuyang
Repository: flutter
Issue: popup_menu PopupMenuItem incorrect calculation of width step when spacing is used
Labels: f: material design,has reproducible steps,P2,team-design,triaged-design,found in release: 3.16,found in release: 3.20

### Steps to reproduce

use PopupMenuItem with spacing inside

### Expected results

size is enlarged
(Width of the menu is expanding in steps of 56 depending on the width of its children).

### Actual results

size is not enlarged sometimes depending on text length and content is overflowing to a second line.
(calculation of the size from its children to select the right step does not work when spacing is used (see example), if i replace spacing with SizedBox of the same width, expanding to the next step is working).

### Code sample

```
PopupMenuButton<MenuItem>(
     itemBuilder: (context) => [
             PopupMenuItem<MenuItem>(
                 height: 48,
                 value: MenuItem.deleteMessagesAll,
                 child: Wrap(spacing: 8, children: [
                   Icon(Icons.delete, color: colors.app_bar_text, size: 25),
                   Text("Delete message history",
                       style: const TextStyle(color: Colors.white, fontWeight: FontWeight.normal))
                 ])),
    ])
```

### Screenshots or Video

![screenshot_popup_issue](https://github.com/flutter/flutter/assets/21581993/e6183f35-1de5-4507-8ba7-f5113a11b20b)


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[✓] Flutter (Channel stable, 3.16.9, on Ubuntu Noble Numbat (development branch) 6.6.0-14-generic, locale en_DE.UTF-8)
    • Flutter version 3.16.9 on channel stable at /home/bwahlen/snap/flutter/common/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 41456452f2 (3 weeks ago), 2024-01-25 10:06:23 -0800
    • Engine revision f40e976bed
    • Dart version 3.2.6
    • DevTools version 2.28.5

[✓] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    • Android SDK at /home/bwahlen/android-sdk-linux
    • Platform android-34, build-tools 34.0.0
    • ANDROID_HOME = /home/bwahlen/android-sdk-linux
    • Java binary at: /usr/lib/jvm/temurin-17-jdk-amd64/bin/java
    • Java version OpenJDK Runtime Environment Temurin-17.0.10+7 (build 17.0.10+7)
    • All Android licenses accepted.

[✓] Chrome - develop for the web
    • Chrome at google-chrome

[✓] Android Studio (version 2023.1)
    • Android Studio at /home/bwahlen/android-studio
    • Flutter plugin version 77.2.1
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version openjdk version "17.0.7" 2023-04-18

[✓] Connected device (2 available)
    • sdk gphone64 x86 64 (mobile) • emulator-5554 • android-x64    • Android 14 (API 34) (emulator)
    • Chrome (web)                 • chrome        • web-javascript • Google Chrome 121.0.6167.184

[✓] Network resources
    • All expected network resources are available.

```

</details>
Repository: flutter
Issue: Unclear documentation on running a test on an emulator in `flutter/engine`
Labels: team-infra,P2,triaged-infra

As-per @keyonghan, I tried to reference our Wiki when iterating on https://github.com/flutter/engine/pull/50583 (in short, I want to run an existing test-script with Android emulator v28 instead of the usual v34). I wasn't able to find what I expected.

Here is what I tried referencing:

* [`org:flutter emulator` type=wikis](https://github.com/search?q=org%3Aflutter+emulator&type=wikis)
* ... led me to [`Testing Android Changes in the Devicelab on an Emulator`](https://github.com/flutter/flutter/wiki/Testing-Android-Changes-in-the-Devicelab-on-an-Emulator)

However, I'm not really sure if my current test cases ([`ci.yaml`](https://github.com/flutter/engine/blob/fc500b284b58534708b7bef1a63d9c49f3e84df6/.ci.yaml#L50-L67), [`ci/builders/linux_android_emulator.json`](https://github.com/flutter/engine/blob/main/ci/builders/linux_android_emulator.json) run on the Devicelab? At the minimum the documentation seems different than what I see, leading me to believe the engine tests are not running on the Devicelab.

<details>

<summary>Wiki Instructions I read </summary>

![image](https://github.com/flutter/flutter/assets/168174/de30f638-2c62-421e-bfa8-51fbbc65c8bd)

</details>

I also checked the [`Flutter Self Service Index`](https://github.com/flutter/flutter/wiki/Flutter-Self-Service-Index), but the section on `Emulators support` just points to the same page as above.

The only other reference I found was in the `.ci.yaml` itself, which reads:

```yaml
# The current android emulator config names can be found here:
# https://chromium.googlesource.com/chromium/src.git/+/HEAD/tools/android/avd/proto
# You may use those names for the android_virtual_device version.
```

... this comment was confusing, because I think the name we're referring to actually [lives in the JSON file](https://github.com/flutter/engine/blob/fc500b284b58534708b7bef1a63d9c49f3e84df6/ci/builders/linux_android_emulator.json#L59-L80):

```json
"test_dependencies": [
    {
        "dependency": "android_virtual_device",
        "version": "android_34_google_apis_x64.textpb"
    },
    {
        "dependency": "avd_cipd_version",
        "version": "build_id:8759428741582061553"
    }
]
```

... leading me to try replacing the "version" key:

```diff
-        "version": "android_34_google_apis_x64.textpb"
+        "version": "android_28_google_apis_x86.textpb"
```

... which appears to be what I need to do, but none of that was covered in the Wiki.
Repository: flutter
Issue: Incrementally introduce platform view changes for Windows to engine and framework
Labels: platform-windows,a: platform-views,a: desktop,P3,team-windows,triaged-windows

The current progress on Windows platform views has been split between planned changes to the engine and framework, which must communicate with each other over platform method channels. In order to avoid breakages and consistently ensure new and passing tests, these changes will need to be merged in steps.
Repository: flutter
Issue: `impellerc`'s file I/O (via `fml`) is lacking
Labels: engine,P3,c: tech-debt,team-engine,triaged-engine

When working on https://github.com/flutter/flutter/issues/143330, the "right" thing to do is delete intermediates:

```diff
static fml::UniqueFD CreateIntermediatesDirectory() {
  auto test_name = flutter::testing::GetCurrentTestName();
  std::replace(test_name.begin(), test_name.end(), '/', '_');
  std::replace(test_name.begin(), test_name.end(), '.', '_');
  return fml::OpenDirectory(flutter::testing::OpenFixturesDirectory(),
                            test_name.c_str(),
                            true,  // create if necessary
                            fml::FilePermission::kReadWrite);
}

CompilerTest::CompilerTest()
    : intermediates_directory_(CreateIntermediatesDirectory()) {
  FML_CHECK(intermediates_directory_.is_valid());
}

- CompilerTest::~CompilerTest() = default;
+ CompilerTest::~CompilerTest() {
+   fml::DeleteDirectory(flutter::testing::OpenFixturesDirectory(),
+                            test_name.c_str());
+ }
```

However, `fml::DeleteDirectory` does not exist. I looked into the `fml::<File I/O>` related methods, and they are very minimal, and from what I heard, are not consistent across platforms (i.e. the `WriteAtomically` method is not actually atomic on Windows).

One suggestion from @jonahwilliams was, in the future, we move the File I/O and effectively "`main()`" of `impellerc` to Dart, and just use `dart:io`.
Repository: next.js
Issue: Debugger not binding breakpoints in VSCode in server components, using official Next.js debugger setup
Labels: bug

### Link to the code that reproduces this issue

https://github.com/andrewmartin/nextjs-example

### To Reproduce

1. Open the code in `VSCode`
2. Add a breakpoint in any server side files
3. Open the "Run and Debug" panel
4. Select "Next.js: debug full stack" and press "F5" or the play button
5. Note that breakpoints don't land when requests are made in either scenario.

Breakpoints set in server components that aren't attached (sorry the screencaps below didn't show my mouse hover so here's a gif):

![Zight Recording 2024-02-13 at 09 45 03 AM](https://github.com/vercel/next.js/assets/273842/41de6e84-8b08-44f9-9459-bb3d84f7179e)

![page tsx — tmp2 2024-02-13 at 9 36 58 AM](https://github.com/vercel/next.js/assets/273842/6436dd61-01d9-4810-afaf-3f323cf6fc58)
![route ts — tmp2 2024-02-13 at 9 38 08 AM](https://github.com/vercel/next.js/assets/273842/b3e1ae98-2c18-41a5-8f38-e5286c6a6b76)

Debug diagnostics:

![Debug Diagnostics — tmp2 2024-02-13 at 9 39 02 AM](https://github.com/vercel/next.js/assets/273842/f3f95513-7d14-40f5-bb80-206a295702f1)

Some of the sources loaded (I can provide more if needed):

![Debug Diagnostics — tmp2 2024-02-13 at 9 39 53 AM](https://github.com/vercel/next.js/assets/273842/dba083ee-3d48-4ebd-9bbe-a66ae34ca33b)



### Current vs. Expected behavior

Hi everyone! The code repo shared is a brand new, blank `create-next-app` using Typescript, Next `14`, and the `app` directory. I only added the debugging setup from the official docs and a single basic API endpoint at `/api/health` and that's it. For some reason I cannot for the life of me get my breakpoints to attach.

Well, that's partially true, The only breakpoints that seem to be mapped with my codebase are those in the Browser / client side components. I have tried SO many things to get this to work and have read probably about 30 posts about trying to fix this. 

I'd love to know if anyone has any ideas why a vanilla Next.js project might not find my sources. Thanks in advance for your help!

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000
Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: 1.22.21
  pnpm: N/A
Relevant Packages:
  next: 14.1.0
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

I have tried:

- Using blank (vanilla) VSCode insiders
- Using alternative node versions (node 18, other minor node 20)
- Tried mucking around with the launch config a bit, like adjusting `sourceMapPathOverrides` etc

Some of my colleagues have had luck seeing them, others have not.
Repository: vscode
Issue: Git - "Discard Changes" and "Stage Changes" don't work for submodules
Labels: bug,git

<!-- ⚠️⚠️ 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: 1.86.1 (system setup)
- OS Version: Windows 11 (Windows_NT x64 10.0.22631)

Steps to Reproduce:
1. Open a folder that has a git submodule (`git clone https://github.com/mayraamaral/submodule-father --recursive`)
2. In the submodule, checkout to a different commit (`cd submodule-father/submodule-child && git checkout 5e40a1b` or edit a file in the submodule)
3. Open the project in VS Code
4. Open the Source Control sidebar
5. Close the submodule-child submodule (Right Click > Close Repository)
6. Click the "Discard Changes" or "Stage Changes" button and the expected outcome doesn't happen

Screenshot of the broken buttons:
![screenshot of the broken buttons](https://github.com/microsoft/vscode/assets/22121365/a4b20968-877c-41bb-98ee-2a0cae5a059f)

I can replicate the issue in my normal installation with all extensions disabled. On the latest insiders build, mostly not customized, I don't see the issue. I don't see any non-default settings that would be causing this.
Repository: pytorch
Issue: FSDP checkpoint saving raises internal deprecation warnings
Labels: oncall: distributed,triaged,module: distributed_checkpoint

### 🐛 Describe the bug

The messages are:

```python
/home/carlos/nightly-env/lib/python3.10/site-packages/torch/distributed/_shard/sharded_tensor/api.py:1132: UserWarning: Please use DTensor instead and we are deprecating ShardedTensor.
  warnings.warn(DEPRECATE_MSG)

/home/carlos/nightly-env/lib/python3.10/site-packages/torch/distributed/checkpoint/filesystem.py:148: UserWarning: TypedStorage is deprecated. It will be removed in the future and UntypedStorage will be the only storage class. This should only matter to you if you are using storages directly.  To access UntypedStorage directly, use tensor.untyped_storage() instead of tensor.storage()
  if tensor.storage().size() != tensor.numel():
```

Minimal repro:

```python
import os
import torch.cuda
import torch.nn as nn
import torch.distributed as dist
import torch.multiprocessing as mp
from torch.distributed.fsdp import FullyShardedDataParallel

def get_sharded_state_dict_context(module):
    from torch.distributed.fsdp.api import ShardedOptimStateDictConfig, ShardedStateDictConfig, StateDictType

    state_dict_config = ShardedStateDictConfig(offload_to_cpu=True)
    optim_state_dict_config = ShardedOptimStateDictConfig(offload_to_cpu=True)
    state_dict_type_context = FullyShardedDataParallel.state_dict_type(
        module=module,
        state_dict_type=StateDictType.SHARDED_STATE_DICT,
        state_dict_config=state_dict_config,
        optim_state_dict_config=optim_state_dict_config,
    )
    return state_dict_type_context  # type: ignore[return-value]

def work(rank):
    os.environ["MASTER_ADDR"] = "127.0.0.1"
    os.environ["MASTER_PORT"] = "1234"
    dist.init_process_group("nccl", world_size=2, rank=rank)
    torch.cuda.set_device(rank)
    device = torch.device("cuda", rank)

    model = nn.Linear(100, 50).to(device)
    model = FullyShardedDataParallel(model)
    x = torch.rand(2, 100, device=device)

    y = model(x)

    from torch.distributed.checkpoint import save
    with get_sharded_state_dict_context(model):
        state = {"model": model.state_dict()}
    save(state, checkpoint_id="fsdp_model.pt")

def run():
    mp.spawn(work, nprocs=2)

if __name__ == "__main__":
    run()
```

First reported in https://github.com/Lightning-AI/pytorch-lightning/issues/19462#issuecomment-1941811092

### Versions

2.3.0.dev20240212+cu121

cc @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @H-Huang @kwen2501 @awgu @penguinwu @fegin @XilunWu @wanchaol @fduwjj @wz337 @tianyu-l @wconstab @yf225 @LucasLLC
Repository: next.js
Issue: `pastDelay` option for `next/dynamic#loading` is always `true` in app router
Labels: bug,Lazy Loading

### Link to the code that reproduces this issue

https://github.com/stefanprobst/issue-next-dynamic-past-delay

### To Reproduce

1. clone [repo](https://github.com/stefanprobst/issue-next-dynamic-past-delay) and run `pnpm install`
2. `pnpm run dev`
3. open http://localhost:3000 and see `{"isLoading":true,"pastDelay":true,"error":null}` being logged to the server console

### Current vs. Expected behavior

i would expect `pastDelay` to be false initially

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #38~22.04.1-Ubuntu SMP PREEMPT_DYNAMIC Thu Nov  2 18:01:13 UTC 2
Binaries:
  Node: 20.11.0
  npm: 10.2.4
  Yarn: 1.22.19
  pnpm: 8.15.1
Relevant Packages:
  next: 14.1.1-canary.51 // Latest available version is detected (14.1.1-canary.51).
  eslint-config-next: N/A
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

App Router, Dynamic imports (next/dynamic)

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

next dev (local), next build (local)

### Additional context

_No response_