sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [compile / strict export] torch._dynamo.exc.Unsupported: CollectiveFunctionRewriteVariable can't support async_op=True for <function all_reduce at 0x7f40be5724d0>
Labels: oncall: pt2,export-triaged,oncall: export

### 🐛 Describe the bug

Ran into this problem when trying all reduce with async op 

```
import logging
import os

import torch
import torch.distributed as dist
import torch.multiprocessing as mp
from torch.export import export

def run(rank, size):
    mod = Foo()
    inps = (torch.randn(4, 4),)
    mod(*inps)
    # comment torch.compile to check export 
    torch.compile(mod, fullgraph=True)(*inps)
    if rank == 0:
        ep = export(mod, inps)
        print(ep)


def init_process(rank, size, fn, backend="gloo"):
    """Initialize the distributed environment."""
    os.environ["MASTER_ADDR"] = "127.0.0.1"
    os.environ["MASTER_PORT"] = "29500"
    torch.cuda.set_device(rank)
    dist.init_process_group(backend, rank=rank, world_size=size)
    fn(rank, size)


class Foo(torch.nn.Module):
    def __init__(self):
        super().__init__()
        self.linear = torch.nn.Linear(4, 3)

    def forward(self, x):
        y = self.linear(x).abs().clamp(max=1.0) * 2
        work = dist.all_reduce(y, async_op=True)
        work.wait()
        return y


def main() -> None:
    world_size = 2
    processes = []
    mp.set_start_method("spawn")
    for rank in range(world_size):
        p = mp.Process(target=init_process, args=(rank, world_size, run))
        p.start()
        processes.append(p)
    for p in processes:
        p.join()


if __name__ == "__main__":
    main()
```

Thanks @pianpwk for his example. 

### Versions

trunk

cc @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4
Repository: node
Issue: Intl.DateTimeFormat.format() output for fi locale no longer matches chrome or latest ICU data (v22)
Labels: v8 engine

### Version

22.13

### Platform

```text
MacOS, Windows, and Linux
```

### Subsystem

_No response_

### What steps will reproduce the bug?

v22 sandbox (incorrect month format): https://codesandbox.io/p/devbox/node22-finnish-datetimeformat-bug-vt3jx6
```sh
en: Jan 24
fi: 24.1.
```

v20 sandbox (correct):  https://codesandbox.io/p/devbox/node22-finnish-datetimeformat-bug-v20-f8zvvg

```sh
en: Jan 24
fi: 24. tammik.
```

### How often does it reproduce? Is there a required condition?

Consistently

### What is the expected behavior? Why is that the expected behavior?

FI `short` month format should match ICU data.  Finnish month in `short` format should be the abbreviated version of the month (e.g. `tammik.`)

### What do you see instead?

It currently is outputting the same as `numeric` format.  e.g. `1.`


### Additional information

I noticed that the ICU data did change in the November update for the Finnish locale, but not in this way.  This only seems to be impacting Finnish from what I can tell, and only the `short` month format.  Furthermore, this is working fine in v20.  It only presented this regression after updating to v22.

![screenshot of finnish data delta](https://github.com/user-attachments/assets/b894fda5-18fa-483d-a4a1-44f1bf854394)
Repository: flutter
Issue: Flutter Web: Text <input> form elements that collect information about the user require the autocomplete attribute (Accessibility)
Labels: a: text input,c: new feature,a: accessibility,platform-web,c: proposal,customer: castaway,team-accessibility

### Use case

Text `<input>` form elements that collect information about the user require the autocomplete attribute. The `autocomplete` attribute allows the browser to do a pattern match against a list of values locally stored with the browser, and supplies the appropriate corresponding value when the input is programmatically tagged.

### Proposal

Add all values for the `autocomplete` attribute. A full list can be found at [HTML autocomplete attribute specification](https://html.spec.whatwg.org/multipage/form-control-infrastructure.html#autofilling-form-controls:-the-autocomplete-attribute).
Repository: flutter
Issue: Flutter Web: Radio buttons require proper keyboard interactions (Accessibility)
Labels: a: text input,c: new feature,framework,a: accessibility,platform-web,c: proposal,customer: castaway,team-accessibility

### Use case

Radio buttons (contained in a radiogroup) do not have the expected keyboard interactions.

### Proposal

Add the following keyboard interactions for radio buttons contained inside of a radiogroup:

- **Tab** and **Shift + Tab**: Move focus into and out of the radio group. When focus moves into a radio group:
-- If a radio button is checked, focus is set on the checked button.
-- If none of the radio buttons are checked, focus is set on the first radio button in the group.
- **Space**: checks the focused radio button if it is not already checked.
- **Right Arrow** and **Down Arrow**: move focus to the next radio button in the group, uncheck the previously focused button, and check the newly focused button. If focus is on the last button, focus moves to the first button.
- **Left Arrow** and **Up Arrow**: move focus to the previous radio button in the group, uncheck the previously focused button, and check the newly focused button. If focus is on the first button, focus moves to the last button.
Repository: ollama
Issue: Please separate deepseek-r1 from deepseek-r1-Distill!
Labels: model request

Please separate deepseek-r1 from deepseek-r1-Distill!
This is not the same model and the architecture is different!
The model on the ollama official website is a perfect obfuscation!
Repository: PowerToys
Issue: Copilot and PowerToys Run have the same keyboard shortcut, so maybe add Copilot as a plugin
Labels: Needs-Triage

### Description of the new feature / enhancement

I noticed that Copilot and PowerToys Run both have the same keyboard shortcut, Alt + Space, and so it makes sense to add Copilot as a plugin so that for example anything you type after '.' keyword becomes a copilot prompt, this way both can be used with the same hotkey

### Scenario when this would be used?

If the user enables the option to use Alt + Space hotkey for Copilot, then it will override PowerToys Run, so this would enable both to be used

### Supporting information

_No response_
Repository: ui
Issue: [bug]: PostCSS and Tailwind new configuration: components no longer work / Outdated documentation
Labels: bug,tailwind

### Describe the bug

The documentation no longer works, I believe it has to do with the new version of tailwind, or it might just be some error with the documentation. I tried multiple times, and followed tutorials to see if I am messing something up, but in fact the documentation needs some update because of how tailwind works with postcss:
plugin:vite:css] [postcss] It looks like you're trying to use tailwindcss directly as a PostCSS plugin. The PostCSS plugin has moved to a separate package, so to continue using Tailwind CSS with PostCSS you'll need to install @tailwindcss/postcss and update your PostCSS configuration

### Affected component/components

General function of PostCSS with Tailwind

### How to reproduce

Follow Vite's documentation to run shadCN, and it will say the following error: 
plugin:vite:css] [postcss] It looks like you're trying to use tailwindcss directly as a PostCSS plugin. The PostCSS plugin has moved to a separate package, so to continue using Tailwind CSS with PostCSS you'll need to install @tailwindcss/postcss and update your PostCSS configuration

### Codesandbox/StackBlitz link

Can't reproduce in Codesandbox because it doesn't let me use the terminal

### Logs

```bash

```

### System Info

```bash
Browser: Opera, using vscode,
```

### Before submitting

- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues
Repository: flutter
Issue: Flutter Web: Landmark roles are required to identify regions of a page (Accessibility)
Labels: c: new feature,a: accessibility,platform-web,c: proposal,customer: castaway,team-accessibility

### Use case

WAI-ARIA landmark roles provide a powerful way to identify the organization and structure of a web page. By classifying and labelling sections of a page, they enable structural information that is conveyed visually through layout to be represented programmatically. Screen readers exploit landmark roles to provide keyboard navigation to important sections of a page. Landmark regions can also be used as targets for "skip links" and by browser extensions to enhanced keyboard navigation.

### Proposal

Add the following landmark roles to the the available semantics roles in existing widget libraries:

- `banner` (when in context of the `body` element)
- `complementary`
- `contentinfo` (when in context of the `body` element)
- `main`
- `navigation`
- `region` (when it has an accessible name using `aria-labelledby` or `aria-label`)
Repository: tailwindcss
Issue: Variant doesn't expand when inside a media query
Labels: bug,v4

**What version of Tailwind CSS are you using?**

v4.0.0

**What build tool (or framework if it abstracts the build tool) are you using?**

Astro 5.1.9
@tailwindcss/vite 4.0.0

**What version of Node.js are you using?**

v23.4.0

**What browser are you using?**

Chrome

**What operating system are you using?**

Windows

**Reproduction URL**

https://play.tailwindcss.com/11WjRHqAY2?file=css

**Describe your issue**

`@variant dark` will expand if it wraps `@media`, but not if it's inside it.

I'd expect this

```css
@media (prefers-reduced-motion: reduce) {
  @variant dark {
    a {
      color: red;
    }
  }
}
```

to become this

```css
@media (prefers-reduced-motion: reduce) {
  &:where(.dark, .dark *) {
    a {
      color: red;
    }
  }
}
```

but `@variant dark` remains in the output css.
Repository: vscode
Issue: Inline Color Picker should be enabled/disabled depends on context (file type)
Labels: editor-color-picker

Similar Issues:
#233193
#235479

A `#XXXXXX` annotation does not always mean an html color, as obviously `#` just means number or id in natural languages, and in programming it can refer to an issue id or line number.

When not in an web development context, displaying such inline color pickers can be quite annoying - not only because it shows a color block, but also because it makes cursor/selection unintuitive. But it can be still helpful when a user happens to need to hack on some web stuff.

So we need a feature to **enable/disable it depends on context, an easy way to guess the context is file type**. For example:

- html/css/php, you may always want this feature.
- js: **_likely_** web development but maybe not interested in colors, and also there're node.js context which is not web development.
- csharp/python/java/go: they **can** be used in web development
- c/c++/...: unlikely but possible
- scm/changelogs: no matter whether it's web development, a `#XXXXXX` likely does not mean an html color here.

It's kind of complex to design a more intelligent way to guess the probability of _whether a `#XXXXXX` means an html color_, but at least one thing that satisfies user needs more is:
**Disable** Inline Color Picker **globally** and enable it on html/css/php/... file types (and let user add the file types).
Repository: flutter
Issue: Flutter Web: aria-required must be an available property on form inputs (Accessibility)
Labels: c: new feature,a: accessibility,platform-web,c: proposal,customer: castaway,team-accessibility

### Use case

The WAI-ARIA property `aria-required` must be available on all Flutter form input elements types/widgets when user input is required on the element before a form may be submitted.

### Proposal

Add the WAI-ARIA property `aria-required` to the list of semantics flags on the following element types/widgets. Its value is either `true` or `false`.

- `<input>` (all types)
- `checkbox`
- `combobox`
- `gridcell`
- `listbox`
- `radiogroup`
- `spinbutton`
- `textbox`
- `tree`
Repository: flutter
Issue: Flutter Web: aria-describedby must be an available property on all component types (Accessibility)
Labels: c: new feature,a: accessibility,platform-web,c: proposal,customer: castaway,team-accessibility

### Use case

The WAI-ARIA property `aria-describedby` must be available on all Flutter component types/widgets to provide more information about an element that the user might need.

### Proposal

Add the WAI-ARIA property `aria-describedby` to the list of semantics flags on all Flutter component types/widgets. Its value must only be the ID of another text string element on the page (text strings are not a valid value for `aria-describedby`). Multiple ID's can be listed (each separated by a single space) in order to form a single accessible description.

Examples:
```
aria-describedby="text1"
aria-describedby="text1 text2 text3"
```
Repository: flutter
Issue: Flutter Web: aria-expanded must be an available property on elements that toggle visibility of content (Accessibility)
Labels: c: new feature,a: accessibility,platform-web,c: proposal,customer: castaway,team-accessibility

### Use case

The `aria-expanded` attribute is applied to a focusable, interactive element that toggles visibility of content in another element. For example, show/hide or "accordion" elements, `combobox` elements, `listbox` elements, and more.

### Proposal

Add the WAI-ARIA property `aria-expanded` to the list of semantics flags on the following element types/widgets. Its value is `true` when the content is expanded/visible, and `false` when the content is collapsed/not visible.

- `application`
- `button`
- `checkbox`
- `combobox`
- `gridecell`
- `link`
- `listbox`
- `menuitem`
- `row`
- `rowheader`
- `tab`
- `treeitem`
Repository: flutter
Issue: Flutter Web: aria-invalid must be an available property on form inputs (Accessibility)
Labels: c: new feature,a: accessibility,platform-web,c: proposal,customer: castaway,team-accessibility

### Use case

The WAI-ARIA property `aria-invalid` must be available on all Flutter form input elements types/widgets when the value is computed to be invalid or out-of-range.

### Proposal

Add the WAI-ARIA property `aria-invalid` to the list of semantics flags on the following element types/widgets. Its value is `true` when the entered value is invalid, and `false` when the entered value is valid.

- `<input>` (all types)
- `application`
- `checkbox`
- `combobox`
- `gridecell`
- `listbox`
- `radiogroup`
- `slider`
- `spinbutton`
- `textbox`
- `tree`
Repository: ui
Issue: [bug]: ShadCn Ui Not Working :tailwind css not installing using vite after update of tailwind v3 to v4
Labels: bug,tailwind

### Describe the bug

tailwind css not installing using vite after update of tailwind v3 to v4 ...
i tried Many time from yesterday but it is not working i think code and installation should code have to update
error occuring in npx tailwindcss init -p
it is not working 

### Affected component/components

installation

### How to reproduce

any suggestions

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash

```

### System Info

```bash
System Information:

Operating System:
- Windows 11
```

### Before submitting

- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues
Repository: rust
Issue: Tracking Issue for `Vec::push_mut`
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(push_mut)]`

This is a tracking issue for `Vec::push_mut`, as discussed in the comments of [this ACP](https://github.com/rust-lang/libs-team/issues/465). This adds a way to get a reference to the just-pushed value, which can eliminate having to `.unwrap()` or access the back of the list twice.

### Public API

```rust
#[must_use = "if you don't need a reference to the value, use Vec::push")]
pub fn push_mut(&mut self, value: T) -> &mut T { /* ... */ }
```

### Steps / History

- [x] Implementation: #135975 
- [ ] Final comment period (FCP)
- [ ] Stabilization PR

### Unresolved Questions

- None yet
Repository: godot
Issue: ColorRect not scaling to entire viewport under BackBufferCopy with anchor preset set to full rect (& expand)
Labels: documentation,topic:2d

### Tested versions

- Reproducible in: 4.3-stable (commit 77dcf97d82cbfe4e4615475fa52ca03da645dbd8)
Compiled for double precision floats

### System information

6.12.9 (NixOS) 4.3-stable-77dcf97d82cbfe4e4615475fa52ca03da645dbd8 (Mobile preset)

### Issue description

A simple ColorRect won't scale to the window, even though its' parent (BackBufferCopy) copy mode is set to Viewport.

![Image](https://github.com/user-attachments/assets/b389cc2b-c0a4-486a-a7c1-00ab52e32580)

Reparenting said ColorRect to be directly under a Control node allows it to be @ fullscreen

![Image](https://github.com/user-attachments/assets/b70739a1-d637-44b1-aca8-a919cf4bcfab)

### Steps to reproduce

Add anything that should scale to the entire viewport under a BackBufferCopy. It won't scale unless you do hacks to work around it.

### Minimal reproduction project (MRP)

If it scales correctly, everything should be white and you won't see the low-poly sphere.

[Godot issue.zip](https://github.com/user-attachments/files/18531088/Godot.issue.zip)
Repository: ui
Issue: [bug]: Animation stuttering on Sheet component after update tailwind v3 to v4
Labels: bug,tailwind

### Describe the bug

Sheet component somehow looses the smooth animation.
Idk if updating tailwind v3 to v4 is related to the problem, but i tryed one version before the update and the sheet component opened smoothly without any problem.

### Bad opening
https://github.com/user-attachments/assets/ca326b72-fadd-4ab4-b45d-030af7e20b4c

### Expected opening
https://github.com/user-attachments/assets/7e145edb-f31a-441b-9c83-71307227b99e

### Affected component/components

Sheet

### How to reproduce

1. Install Sheet component
2. Build the component
3. Test
4. Update Tailwind v3 to v4
5. Click in the trigger component

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash

```

### System Info

```bash
Fedora 41, Firefox-Aurora, NextJs 15.1.4, Tailwindcss 4.0.0, @tailwindcss/postcss ^4.0.0
```

### Before submitting

- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues
Repository: pytorch
Issue: _pickle.UnpicklingError: invalid load key, ''.
Labels: oncall: distributed

### 🐛 Describe the bug

`import pickle
import torch
import io

_pickler = pickle.Pickler
_unpickler = pickle.Unpickler


tensor = torch.tensor([126, 188, 133, 30,  60, 138, 188], dtype=torch.uint8)
buf = tensor.numpy().tobytes()[:3]

_unpickler(io.BytesIO(buf)).load()`


tobytes is error:

[rank14]: File "/usr/local/lib/python3.10/site-packages/torch/distributed/distributed_c10d.py", line 2362, in _tensor_to_object
[rank14]: return _unpickler(io.BytesIO(buf)).load()
[rank14]: _pickle.UnpicklingError: invalid load key, '~'.

# need to modify:
tensor.numpy().tobytes()
to
pickle.dumps(tensor.numpy())

### Versions

python3.10
torch2.3.0
ubuntu20.04

cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o
Repository: puppeteer
Issue: [Feature]: Convert Puppeteer Response object into Response object of Fetch API
Labels: feature,P3

### Feature description

`Page.goto` method returns `HTTP Response`:
https://pptr.dev/api/puppeteer.httpresponse

In my project, I'm encapsulating puppeteer. I make an interface like

```ts
export type IPage = {
  goto(
    url: string,
    options?: { timeout: number }
  ): Promise<Response | null>;

```

Not to unaware of puppeteer, I'd be happy if I could convert Puppeteer HTTP Response class into Response class of Fetch API shown below
https://developer.mozilla.org/en-US/docs/Web/API/Response

Thank you.
Repository: vscode
Issue: Python file is not running
Labels: info-needed


Type: <b>Bug</b>

print("adithya"+"ranjit")

VS Code version: Code 1.96.4 (cd4ee3b1c348a13bafd8f9ad8060705f6d4b9cba, 2025-01-16T00:16:19.038Z)
OS version: Windows_NT x64 10.0.19045
Modes:

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

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 3 3250U with Radeon Graphics          (4 x 2595)|
|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: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|5.94GB (0.88GB free)|
|Process Argv|--crash-reporter-id 27a663b3-1774-456e-a8d4-f79d63956c8a|
|Screen Reader|no|
|VM|0%|
</details><details><summary>Extensions (20)</summary>

Extension|Author (truncated)|Version
---|---|---
auto-save-toggler|Bac|1.0.6
debugpy|ms-|2024.14.0
python|ms-|2024.22.2
vscode-pylance|ms-|2024.12.1
jupyter|ms-|2024.11.0
jupyter-keymap|ms-|1.1.2
jupyter-renderers|ms-|1.0.21
vscode-jupyter-cell-tags|ms-|0.1.9
vscode-jupyter-slideshow|ms-|0.1.6
java|red|1.39.0
LiveServer|rit|5.7.9
pdf|tom|1.2.2
intellicode-api-usage-examples|Vis|0.2.9
vscodeintellicode|Vis|1.3.2
vscode-gradle|vsc|3.16.4
vscode-java-debug|vsc|0.58.1
vscode-java-dependency|vsc|0.24.1
vscode-java-pack|vsc|0.29.0
vscode-java-test|vsc|0.43.0
vscode-maven|vsc|0.44.0

(1 theme extensions excluded)

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

```
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythonnoceb:30805159
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
dvdeprecation:31068756
dwnewjupyter:31046869
nativerepl2:31139839
pythonrstrctxt:31112756
nativeloc1:31192215
cf971741:31144450
iacca1:31171482
notype1:31157159
5fd0e150:31155592
dwcopilot:31170013
stablechunks:31184530
6074i472:31201624
dwoutputs:31217127
9064b325:31222308
copilot_t_ci:31222730

```

</details>

<!-- generated by issue reporter -->