sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [Impeller] libImpeller: Find default font files on Android.
Labels: P2,e: impeller,team-engine,triaged-engine,e: libimpeller

Today, the font files need to be explicitly specified. The mechanism exists but needs to be wired up.
Repository: rust
Issue: Misleading error messages when using the wrong macro fragment specifiers
Labels: A-diagnostics,A-macros,D-confusing

Issue:

```rust
#[rustfmt::skip]
mod issue {
    struct SomeType<T>(std::marker::PhantomData<T>);

    macro_rules! test {
        ($ty:ty) => {
            impl<$ty,> SomeType<$ty> {}
        };
    }

    // Works fine
    impl<T,> SomeType<T> {}
    //   error: expected one of `>` or `as`, found `,`
    //   --> src\lib.rs:7:21
    //    |
    // 7  |             impl<$ty,> SomeType<$ty> {}
    //    |                     ^ expected one of `>` or `as`
    // ...
    // 12 |     test!(T);
    //    |     -------- in this macro invocation
    test!(T);

    macro_rules! test2 {
        ($ty:ty) => {
            impl<$ty> SomeType<$ty> {}
        };
    }

    // Works fine
    impl<T> SomeType<T> {}
    // error: expected `::`, found `SomeType`
    //   --> src\lib.rs:17:23
    //    |
    // 17 |             impl<$ty> SomeType<$ty> {}
    //    |                       ^^^^^^^^ expected `::`
    // ...
    // 22 |     test2!(T);
    //    |     --------- in this macro invocation
    test2!(T);
}
```

The macro should behave exactly like its manual expansion would; I've inlined the reported problems into the code.

### Meta
The error happens in both stable and nightly toolchains, on linux and windows

`rustc --version --verbose`:
```
rustc 1.82.0 (f6e511eec 2024-10-15)
binary: rustc
commit-hash: f6e511eec7342f59a25f7c0534f1dbea00d01b14
commit-date: 2024-10-15
host: x86_64-pc-windows-msvc
release: 1.82.0
LLVM version: 19.1.1
```
Repository: flutter
Issue: Make `ErrorWidget`'s text selectable
Labels: c: new feature,framework,c: proposal,P3,team-framework,triaged-framework

# Problem

When an assertion is triggered, it is displayed using the `ErrorWidget`.

Unfortunately, its text is unselectable - I cannot copy it to search the internet for help.

# Solution

Ideas:

1. Make the `ErrorWidget`'s text selectable
2. Add a link to Google that searches for the error

# Example scenario

This app has a bad container that provides both a `color` and a `decoration` in a `Container`:

```dart
import 'package:flutter/material.dart';

void main() => runApp(MyApp());

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Container(
      color: Colors.blue,
      decoration: BoxDecoration(
        color: Colors.blue,
      ),
    );
  }
}
```

Result:

![image](https://github.com/user-attachments/assets/4f9fe6a3-df38-4d3c-a0e7-b667b556a17a)
Repository: angular
Issue: Invalid check in router/url_tree/parseParens
Labels: area: router,router: aux routes

### Which @angular/* package(s) are the source of the bug?

router

### Is this a regression?

No

### Description

The `parseParens` method in url_tree.ts has a sanity check that checks if segment group is properly closed or not.
https://github.com/angular/angular/blob/c22b5accdd083f3bdc4141431cece196f0e33112/packages/router/src/url_tree.ts#L711-L718

This check does not pass when the segment group is defining an outlet with a path and children. For example:
```
/Home(app:Welcome//dock:left(1:One;pinned//2:Two;below=1//3:Three;pinned;above=2//4:Four))
```
In this case, after matching the outlet and its segments (`dock:left`), the next character is a `(` to specify the children.

### 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`)

_No response_

### Anything else?

_No response_
Repository: next.js
Issue: tsconfigPath is not supported by Turbopack
Labels: bug,Turbopack,linear: turbopack

### Link to the code that reproduces this issue

https://github.com/seanparmelee/nextjs-tsconfigpath

### To Reproduce

1. Run `npm run dev:turbo`
2. Navigate to http://localhost:3000/
3. You should see the error `Module not found: Can't resolve '@/components/Hello'`
4. Stop the server
5. Run `npm run dev`
6. Navigate to http://localhost:3000/
7. Confirm the page renders successfully

### Current vs. Expected behavior

When using Turbopack (`npm run dev:turbo`), modules referenced via the configured path alias cannot be found; presumably because Turbopack doesn't support the `typescript.tsconfigPath` Next.js config option.

When not using Turbopack (`npm run dev`), the aliased modules are resolved successfully.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Wed Jul 31 20:49:39 PDT 2024; root:xnu-10063.141.1.700.5~1/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 10
Binaries:
  Node: 22.11.0
  npm: 10.9.0
  Yarn: N/A
  pnpm: 8.15.2
Relevant Packages:
  next: 15.0.3-canary.6 // Latest available version is detected (15.0.3-canary.6).
  eslint-config-next: N/A
  react: 19.0.0-rc-7c8e5e7a-20241101
  react-dom: 19.0.0-rc-7c8e5e7a-20241101
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Turbopack

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

_No response_
Repository: vscode
Issue: Add support for adding `svg` as attachments
Labels: feature-request,panel-chat

![Image](https://github.com/user-attachments/assets/8f281f87-e6c8-4664-bf4d-780a96b644ca)
Repository: flutter
Issue: Feature Request: Add Parameter to Control Tooltip Dismissal Behavior
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

### Use case

**Description:** I would like to propose an enhancement to the existing Tooltip widget in Flutter to provide developers with the ability to control the dismissal behavior of tooltips more effectively.

**Current Behavior:** The default behavior of the Tooltip widget is that it remains visible even when the mouse hovers over the tooltip itself. This can lead to situations where the tooltip persists longer than desired, especially when the user moves the cursor from the target widget directly to the tooltip.

### Proposal

**Proposed Enhancement:** Add a parameter to the Tooltip widget that allows developers to specify whether the tooltip should dismiss immediately when the mouse leaves the target widget, even if the mouse enters the tooltip. This could be achieved by introducing a boolean parameter such as dismissOnHoverExit:

```dart
Tooltip(
  message: 'This is a tooltip',
  dismissOnHoverExit: true, // New parameter to control dismissal behavior
)
```
**Use Case:** This enhancement would be particularly useful for applications where tooltips are used for short instructions or contextual help, improving user experience by avoiding unnecessary delays in tooltip dismissal.

**Example Scenario:** When the user hovers over a button with a tooltip, the tooltip appears as expected. However, if the user then moves the mouse away from the button and onto the tooltip, the tooltip should disappear immediately rather than remaining visible.

**Conclusion:** I believe that this enhancement would provide developers with greater flexibility in how tooltips are used within their applications, ultimately leading to a better user experience. Thank you for considering this feature request!
Repository: terminal
Issue: Copilot chat loses input when dismissed and reloaded
Labels: Issue-Bug,Product-Terminal,Needs-Tag-Fix,Area-Chat

### Windows Terminal version

1.23.3091.0

### Windows build number

10.0.26100.0

### Other Software

_No response_

### Steps to reproduce

@DHowett told me to bind copilot chat to <kbd>shift</kbd>+<kbd>/</kbd> which I thought was an alright idea.

That is... until I tried to type a question mark at the end of my query for Copilot to answer... which rightfully dismissed the input box.

However, when I brought it back up again.... everything I typed was gone.



### Expected Behavior

I would have expected the box to preserve and keep my input through to reopening the dialog.

### Actual Behavior

The input on Copilot chat is empty on every launch, even if it was dismissed with content inside it.
Repository: godot
Issue: Script sidepanel toggle is permanent with ctrl + \ but only temporary with the bottom left arrow
Labels: bug,topic:editor

### Tested versions

v4.4.dev3.official [f4af8201b]

### System information

Godot v4.4.dev3 - Windows 10.0.19045 - Multi-window, 9 monitors - OpenGL 3 (Compatibility) - NVIDIA GeForce RTX 3070 (NVIDIA; 32.0.15.6590) - 11th Gen Intel(R) Core(TM) i9-11900K @ 3.50GHz (16 threads)

### Issue description

Using ctrl + \ to toggle the script panel or right clicking to toggle/hide it is a permanent state change upon reloads.
The bottom left arrow to show or hide the panel is a temporary change across reloads.

### Steps to reproduce

Click bottom left arrow to hide panel, reload the project, it will be visible again
Ctrl + \ to hide the panel, reload the project, and it will stay hidden


https://github.com/user-attachments/assets/e3eb7c2d-8078-4992-b1b4-a77fbd6c7d3b



### Minimal reproduction project (MRP)

[mrp_script_sidepanel_state.zip](https://github.com/user-attachments/files/17637369/mrp_script_sidepanel_state.zip)
Repository: flutter
Issue: Give a non-nullable context to ContextAction's invoke()
Labels: c: new feature,framework,d: api docs,c: proposal,P3,team-framework,triaged-framework

### Use case

The Actions API introduced `ContextAction` a few years ago: https://docs.google.com/document/d/1A9yald55O_C6Weqp4tOtyMisfOC1ZC0UMq7Yc-pNfVQ/edit?tab=t.0

The API is:

```
  @override
  bool isEnabled(T intent, [BuildContext? context]) => super.isEnabled(intent);

  @protected
  @override
  Object? invoke(T intent, [BuildContext? context]);
```

There are three possible cases for the usage of a context in an action:

1. An `Action` doesn't use a `BuildContext`, (and can subclass `Action` if this is the case)
2. An `Action` requires a `BuildContext` to do its function
3. An `Action` may use a `BuildContext` but can fall back somehow without it

In practice case 3 seems rare, but the ergonomics of the common case 2 are hampered by needing to work around the nullable `BuildContext` when the `BuildContext` is required for the action to do its primary function. Implementations need an out-of-band error handling mechanism. It appears that a `BuildContext` is always provided, but it isn't clear if it's safe to assume that or if rare bugs could be introduced. 

We could introduce a convention of marking the action as disabled when the context is null, then use '!' on the context argument, but this isn't ideal.



### Proposal

* Make clear in API docs if and when a context can actually be missing
* Introduce a new API something like `RequiredContextAction` which has a non-nullable Context and make it impossible to invoke those actions without one (and/or schedule a breaking API change to update `ContextAction`)
Repository: TypeScript
Issue: VSCode auto-import ignores typescript.preferences.importModuleSpecifierEnding when using a path from the package.json imports
Labels: Needs More Info

<!-- ⚠️⚠️ 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.95.1
- OS Version: MacOS 14.7

---------

I have these settings in VSCode:
```
{
   "javascript.preferences.importModuleSpecifierEnding": "minimal",
   "typescript.preferences.importModuleSpecifierEnding": "minimal"
}
```

I have these setting in my package.json:
```
"imports": {
    "#src": ["./src/index.ts", "./src/index/tsx"],
    "#src/*": [
      "./src/*",
      "./src/*.ts",
      "./src/*.tsx",
      "./src/*/index.ts",
      "./src/*/index.tsx"
    ]
  },
```

I have these settings in my tsconfig.json
```
"target": "esnext",
"module": "esnext",
"moduleResolution": "bundler",
```

However, when I auto-import something that starts with `#src/`, it automatically appends a `.js` to the import (or a `.ts` if I have `allowImportingTsExtensions` on. This is ignoring my settings to use the minimum module specifier ending I set in VSCode.

It looks like the addition of the `.ts` functionality was added in this bugfix: https://github.com/microsoft/TypeScript/issues/52167. I'm not sure why it wasn't set to respect the vscode settings.
Repository: go
Issue: compress/flate: TestBestSpeed failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "compress/flate" && test == "TestBestSpeed"
```

Issue created automatically to collect these failures.

Example ([log](https://ci.chromium.org/b/8732086649999571185)):

    === RUN   TestBestSpeed
    === PAUSE TestBestSpeed
    === CONT  TestBestSpeed


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: go
Issue: x/tools/gopls: recognize templ user agent in telemetry
Labels: gopls,Tools

Templ language server uses gopls to process go syntax.
Currently, gopls spawned by Templ language server is not distinguishable from gopls editors manage directly.

As Templ is getting popular, I think it is beneficial for both gopls and templ teams to track templ's gopls usage more closely. Hopefully, this information can help when we need to track the protocol compatibility and minimize accidental breakages like in https://github.com/golang/vscode-go/issues/3435#issuecomment-2192862723. 

In https://github.com/a-h/templ/pull/966 I am proposing to adjust the client info so we can record the chain of lsp participants. I use `;` but I am open to other characters. Or even other fields if there are. 

Whatever format is chosen, we also need to adjust gopls side to process this format. For example,

https://github.com/golang/tools/blob/f1f7c26696be8f94198beafd05b36843515ac2ba/gopls/internal/cache/snapshot.go#L950 
and telemetry.
Repository: pytorch
Issue: compiling "input mutation" followed by "input mutation + aliasing" does not properly recompile
Labels: high priority,triaged,oncall: pt2,module: guards

Noticed this after some discussion from https://github.com/pytorch/pytorch/pull/139555#discussion_r1828455360. Here is a small repro:
```
import torch


def f(x, y):
    x.mul_(2)
    return x + y


x1 = torch.ones(4)
y1 = torch.ones(4)

f_compiled = torch.compile(f, backend="aot_eager")
out1 = f_compiled(x1, y1)

base = torch.ones(8)
x2 = base[:4]
y2 = base[2:6]
# None of the inputs alias
out2 = f_compiled(x2, y2)

base_ref = torch.ones(8)
x2_ref = base_ref[:4]
y2_ref = base_ref[2:6]
# This should re-compile, since inputs now alias!
# But it does not
out2_ref = f(x2_ref, y2_ref)

print(out2_ref)
print(out2)
```

The problem is that on the second invocation, we have two inputs that alias each other, and are also mutated. We have some special logic in AOTAutograd to handle this case, by generating a "shared base" graph input, and regenerating the views inside of the graph so we can functionalize the mutations properly.

The problem though, is that we end up re-using the first graph (which does not have any aliasing), when we should be recompiling.

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @chauhang @penguinwu
Repository: ui
Issue: [bug]: `init`/`add` commands break `tailwind.config.js`
Labels: bug

### Describe the bug

```
      fontFamily: {
        sans: [
          'Work Sans',
          'sans-serif',
          'Calibri',
          'Candara',
          'Segoe',
          'Segoe UI',
          'Optima',
          'Arial',
        ],
      },
```
Becomes

```
  		fontFamily: {
  			sans: [\n          'Work Sans',\n          'sans-serif',\n          'Calibri',\n          'Candara',\n          'Segoe',\n          'Segoe UI',\n          'Optima',\n          'Arial',\n        ]
  		},
```

### Affected component/components

CLI

### How to reproduce

Have multiple lines in your tw config and use the CLI
```
      fontFamily: {
        sans: [
          // This breaks
          'Work Sans',
        ],
      },
```

```
      fontFamily: {
        sans: [
          'Work Sans',
          'Or this',
        ],
      },
```

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
next 14/15
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: ui
Issue: [bug]: CLI breaks tailwind.config.ts
Labels: bug

### Describe the bug

```
      fontFamily: {
        sans: [
          'Work Sans',
          'sans-serif',
          'Calibri',
          'Candara',
          'Segoe',
          'Segoe UI',
          'Optima',
          'Arial',
        ],
      },
```
Becomes

```
  		fontFamily: {
  			sans: [\n          'Work Sans',\n          'sans-serif',\n          'Calibri',\n          'Candara',\n          'Segoe',\n          'Segoe UI',\n          'Optima',\n          'Arial',\n        ]
  		},
```

### Affected component/components

CLI

### How to reproduce

Have multiple lines in your tw config and use the CLI
```
      fontFamily: {
        sans: [
          // This breaks
          'Work Sans',
        ],
      },
```

```
      fontFamily: {
        sans: [
          'Work Sans',
          'Or this',
        ],
      },
```

### Affected component/components

CLI

### How to reproduce

Have multiple lines in your tw config and use the CLI
```
      fontFamily: {
        sans: [
          // This breaks
          'Work Sans',
        ],
      },
```

```
      fontFamily: {
        sans: [
          'Work Sans',
          'Or this',
        ],
      },
```

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Next 14/15
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: pytorch
Issue: Speed up `DataLoader` worker start time for large datasets
Labels: module: dataloader,triaged

### 🚀 The feature, motivation and pitch

Startup time for `DataLoader` workers can be very slow when using a `Dataset` object of even moderate size. The reason is that each worker process is started serially in a loop, and for each worker we have to:
1. pickle the dataset
2. wait while we pipe the data to the worker

I've found we can greatly improve both of these issues by:
1. pre-pickling the dataset once before starting the workers
2. create all the worker processes first, then start them in threads, because `Process.start` is non-blocking

### Alternatives

(2) seems quite safe, (1) I haven't thought through the implications of incorporating this into the `DataLoader` itself, and is not that hard to implement on your own `Dataset` class with a manual method and `__setstate__`.

### Additional context

My use case is handling geospatial data (`pip install xarray dask zarr`):

```python
import pickle
import time
import xarray as xr
import torch
from torch.utils.data import Dataset, DataLoader


class XarrayDataset(Dataset):
    def __init__(self, data):
        self.data = data
        self._len = data.time.size

    def __len__(self):
        return self._len

    def __getitem__(self, idx):
        sample = self.data.isel(time=idx)
        temperature = torch.tensor(sample["2m_temperature"].values)
        return temperature


if __name__ == "__main__":
    ds = xr.open_zarr("gs://gcp-public-data-arco-era5/ar/1959-2022-6h-1440x721.zarr")

    dataset = XarrayDataset(ds)
    loader = DataLoader(
        dataset,
        multiprocessing_context="spawn",
        num_workers=16,
    )
    start = time.time()
    iterator = loader._get_iterator()
    print(f"Time to start DataLoader: {time.time() - start:.2f}")
```

The pickled representation of the `xarray.Dataset` here is about 13MB, almost all of it in the `dask` graph representing the arrays.

On `main`, this takes **38s to start 16 workers**, but I've seen much worse with more complex dask graphs.

If we modify the dataloader to pickle the data once up front and then unpickle in each worker, this goes down to **20s**.

If we modify the dataloader to start the workers in separate threads, I get this down to **7s** without pre-pickling the data, and **3.5s** with it.


cc @andrewkho @divyanshk @SsnL @VitalyFedyunin @dzhulgakov
Repository: next.js
Issue: redirect does not work when using multiple root layouts 
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/llipengda/next-redirect-bug

### To Reproduce

1. next dev
2. click `/test-a`
3. click `redirect to /`
4. the page is navigated to /
5. click `/test-b`
6. click `redirect to /`
7. this does not work

### Current vs. Expected behavior

current: when clicking `redirect to /` in `/test-b`, `redirect` does not work.
expected: redirect to /

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home China
  Available memory (MB): 16164
  Available CPU cores: 16
Binaries:
  Node: 20.18.0
  npm: 10.8.3
  Yarn: 1.22.22
  pnpm: 9.12.2
Relevant Packages:
  next: 15.0.3-canary.6 // Latest available version is detected (15.0.3-canary.6).
  eslint-config-next: N/A
  react: 19.0.0-rc-7c8e5e7a-20241101
  react-dom: 19.0.0-rc-7c8e5e7a-20241101
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


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

Navigation

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

next dev (local), next start (local)

### Additional context

_No response_