sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ui
Issue: [bug]: Installation fails with Next.js 15 and/or React 19
Labels: bug

### Describe the bug

While initializing a new Next.js project with shadcn-ui using `npx shadcn@latest init`, the installation fails when attempting to install dependencies. The error occurs because @radix-ui/react-icons has a peer dependency requirement for "react@^16.x || ^17.x || ^18.x", but the project is using React 19.0.0-rc-69d4b800-20241021.

Error message:
npm error ERESOLVE unable to resolve dependency tree
npm error Found: react@19.0.0-rc-69d4b800-20241021
npm error Could not resolve dependency:
npm error peer react@"^16.x || ^17.x || ^18.x" from @radix-ui/react-icons@1.3.0

Current environment:
- Next.js 15
- React 19.0.0-rc-69d4b800-20241021
- npm (latest version)
- shadcn-ui (latest version)

The installation works fine with React 18, suggesting that @radix-ui/react-icons needs to be updated to support React 19 release candidates.

Potential solutions:
1. Update @radix-ui/react-icons peer dependencies to include React 19
2. Add a note in the documentation about React 19 compatibility
3. Add a version check in the CLI to warn users about React 19 compatibility issues

### Affected component/components

shadcn-ui installation fails

### How to reproduce

```
Steps to reproduce:

1. Create a new Next.js project with experimental features:
   ```bash
   npx create-next-app@latest my-app --typescript --tailwind --app
   ```

2. During the setup, select 'yes' for App Router and other default options

3. Navigate to the project directory:
bash
   cd my-app


4. Try to initialize shadcn-ui:
bash
   npx shadcn@latest init


5. Select configuration options:
   - Style: New York
   - Base color: Neutral
   - CSS variables: Yes

6. The installation will fail during the dependency installation step with the following error:

   npm error ERESOLVE unable to resolve dependency tree
   npm error Found: react@19.0.0-rc-69d4b800-20241021
   npm error Could not resolve dependency:
   npm error peer react@"^16.x || ^17.x || ^18.x" from @radix-ui/react-icons@1.3.0


You can verify the React version in your package.json: 
{
  "dependencies": {
    "react": "19.0.0-rc-69d4b800-20241021",
    "react-dom": "19.0.0-rc-69d4b800-20241021"
  }
}


### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
System Information:

Operating System:
- Windows 8
- Working in Command Prompt

Node Environment:
- Node.js version: v20.17.0
- npm version: v10.9.0

Project Dependencies:
- Next.js: 15
- React: 19.0.0-rc-69d4b800-20241021
- React DOM: 19.0.0-rc-69d4b800-20241021
- Typescript: ^5
- Tailwind CSS: ^3.4.1

CLI Versions:
- create-next-app: latest
- shadcn-ui CLI: latest (@shadcn/ui)

Additional Context:
- Fresh installation with default configurations
- Using App Router
- Project created with TypeScript and Tailwind CSS enabled
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Devcontainer setup ad-hoc parsing fails on Rocky 8.5
Labels: bug,linux,good first issue,remote

<!-- ⚠️⚠️ 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.92.0 (Commit: b1c0a14de1414fcdaa400695b4db1c0799bc3124)
- OS Version: Rocky Linux 8.5

The `check-requirements-linux.sh` script that runs as part of a devcontainer setup wants to parse the OS version from `/etc/os-release`.
That file "is a newline-separated list of environment-like shell-compatible variable assignments" (see `man os-relase` on Linux).
The script tries to parse the value it wants [here](https://github.com/microsoft/vscode/blob/main/resources/server/bin/helpers/check-requirements-linux.sh#L34), by running:

```
OS_ID="$(cat /etc/os-release | grep -Eo 'ID=([^"]+)' | sed -n '1s/ID=//p')"
```

This looks for a key-value pair of the form `ID=value` and strips out the `ID=` part.
It assumes the pair is not of the form `ID="value"`, which appears to be permitted by the file format, and appears in the wild in Rocky 8.5 where the relevant line reads:

```
ID="rocky"
```

In that case the `grep` command will fail to match the line and the value of `OS_ID` will be empty, resulting in a non-zero exit code of 1.

This could be fixed by changing the variable assignment to:

```
OS_ID=$(source /etc/os-release && echo $ID)
```

This will run a subshell in which the values in the file get assigned to environment variables, which removes any surrounding `"` marks.
Since this runs in a subshell the current shell's environment will not pick up these variables.

Steps to Reproduce:

1. Start a devcontainer built from Rocky 8.5.
Repository: deno
Issue: Documentation missing: where does `deno task` look for commands?
Labels: question

Version: Deno 2.0.1

### How does `deno task` find commands?

If a dependency defines a command in (`bin` in `package.json`), how does `deno task` find that command?   

Is there a way to run those commands outside of `deno task`?   What's deno's equivilant of `npx`?

### Concrete example

see: https://github.com/smoofra/lambdazoo

`deno task generate` runs a script called `ohm` which is defined by `@ohm-js/cli`.    How does that happen?

If i run `npx ohm` in that project it seems to work too, but that populates `node_modules`, and runs a script in `node_modules/.bin/ohm` that actually runs `node` not `deno`.     `deno task generate` does not.    How can you run `ohm` 
`deno`, not `node`?.
Repository: go
Issue: proposal: x/sys/unix: add methods to covert between time.Time and unix.PtpClockTime on Linux
Labels: Proposal

### Proposal Details

Recently we have exposed the syscalls and types related to PTP (IEEE 1588) on Linux in the `unix` package.
Amongs those is a struct representing time in PTP calls, [`unix.PtpClockTime`](https://pkg.go.dev/golang.org/x/sys/unix@master#PtpClockTime). Semantically it is very similar to Unix time, differing in underlying type for the nanoseconds field and having a placeholder for future extentions.

The proposal is to add the convenience methods to carry conversion between *unix.PtpClockTime* and *time.Time*:

```
package unix

func TimeToPtpClockTime(t time.Time) PtpClockTime
func (t *PtpClockTime) Time() time.Time
func (t *PtpClockTime) Unix() (sec int64, nsec int64)
```

This shall allow to use the maths of the standard time package while avoiding
the boilerplate: write `ptpt.Time()` instead of `time.Unix(ptpt.Sec, int64(ptpt.Nsec))`,
and `unix.TimeToPtpClockTime(t)` instead of `unix.PtpClockTime{Sec: t.Unix(), Nsec: uint32(t.Nanosecond())}`.

As an example of what the boilerplate looks like in real-world code, please see facebook/time#418.

golang/sys#230 implements the proposal.

Thank you for consideration.
Repository: pytorch
Issue: Add mean and var operation for Nested Tensors
Labels: triaged,module: nestedtensor

### 🚀 The feature, motivation and pitch

For torch.Tesnor it is easy to compute mean and var, but I can not find ways to compute mean and var for Nested Tensors. Nested Tensors support layer_norm operation which include mean and var operation. Is there any ways to compute mean fo Nested Tensors?
```
x = torch.randn(1, 192)
y = torch.randn(10, 192)
nested = torch.nested.nested_tensor([x, y])
nested.mean(dim=-1)#Don't support
layer_norm(nested)#support
```

### Alternatives

_No response_

### Additional context

_No response_

cc @cpuhrsch @jbschlosser @bhosmer @drisspg @soulitzer @davidberard98 @YuqingJ
Repository: flutter
Issue: Flutter-web text field iframed with semantics disabled refuses to let go of focus
Labels: a: text input,engine,a: accessibility,platform-web,f: focus,P2,customer: samehere,team-web,triaged-web

### Steps to reproduce

See also https://github.com/flutter/flutter/issues/157387 which requires the same conditions (iframed, semantics disabled).

1. Requisites
    a. Accessibility (semantics tree) must not be enabled, and
    b. Flutter-web app must be iframed.
2. Click on one of the text field widgets within the Flutter-web app.
3. Attempt to click out to the iframe host.

### Expected results

Focus should move to the iframe host (whatever you clicked).

### Actual results

The Flutter-web iframe keeps stealing the focus back as soon as it loses it, preventing interacting with the iframe host.

Workarounds:
* Click within the Flutter-web iframe out of the text field so that it loses focus. Then you're able to focus into the iframe host.
* Enabling Flutter semantics seems to resolve this issue, interestingly.

### Code sample

<details open><summary>Code sample</summary>

https://dartpad.dev/?id=074d8b35285e25643fcffbdf8f9a3b1b

1. Run this.
2. Click into the Flutter-web text field. Optionally also type some stuff in to make the focus stealing obvious.
3. Then try to click back to the DartPad code. Notice how the Flutter-web text field steals focus and selects-all its content.
4. Now, click in the Flutter-web area outside of the text field so that it loses focus.
5. Then try to click back to the DardPad code and see that it succeeds now.

```dart
import 'package:flutter/material.dart';
import 'package:flutter/rendering.dart';

void main() async {
  runApp(
    MaterialApp(
      title: 'Test',
      home: Scaffold(
        body: Row(
          children: [
            Text('Text field: '),
            SizedBox(
              height: 50,
              width: 400,
              child: Semantics(container: true, child: const TextField()),
            ),
          ],
        ),
      ),
    ),
  );

  // Uncomment this line to enable the Semantics tree, which makes it work properly.
  //SemanticsBinding.instance.ensureSemantics();
}
```
</details>
Repository: pytorch
Issue: [PTD][RPC] Verify RPC Tutorials contents and scripts
Labels: oncall: distributed,module: docs,triaged

### 📚 The doc issue

It has been a while these tutorials have been updated. Since there are not active developments on these, we should verify the scripts in the tutorials are still working as expected. 

Getting Started with Distributed RPC Framework - https://pytorch.org/tutorials/intermediate/rpc_tutorial.html  - ?
Implementing a Parameter Server Using Distributed RPC Framework - https://pytorch.org/tutorials/intermediate/rpc_param_server_tutorial.html -? 
Implementing Batch RPC Processing Using Asynchronous Executions - https://pytorch.org/tutorials/intermediate/rpc_async_execution.html  - ? 
Combining Distributed DataParallel with Distributed RPC Framework - https://pytorch.org/tutorials/advanced/rpc_ddp_tutorial.html - ?

### Suggest a potential alternative/fix

_No response_

cc. @c-p-i-o 

cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wconstab @d4l3k @c-p-i-o @svekars @brycebortree @sekyondaMeta @AlannaBurke
Repository: flutter
Issue: Deprecate support for ia32
Labels: P1,team-tool,triaged-tool

Dart is considering dropping support for ia32, please see https://github.com/dart-lang/sdk/issues/49969 for more context.

This issue is to ensure Flutter goes through a deprecation process before removing support for ia32.

List of items to consider

- [x] remove support for jit release mode which is tracked here https://github.com/flutter/flutter/issues/151610
- [x] make an announcement to external developers about the intent to drop support for ia32, this could be done by having Flutter tools issue a warning whenever the x86 emulator is used (Please see https://github.com/flutter/flutter/issues/158953)
- [ ] switch Flutter tools to use x86_64 by default (switch to use a different ABI, apparently  AS: 31 and above ABI uses x86_64)
- [ ] After one beta cycle of issuing the warning, remove support for ia32 in flutter tools

//cc @bkonyi
Repository: flutter
Issue: Test runner appears to run `test/cupertino/tab_scaffold_test.dart` 14K times
Labels: tool,c: tech-debt,team-tool

Example log:
https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8733174319067180289/+/u/read_logs/tmpfg_tnxrl

In the middle of the run, you can see the following:
```txt
unhandled error during finalization of test:
/Volumes/Work/s/w/ir/x/w/flutter/packages/flutter/test/cupertino/tab_scaffold_test.dart
TestDeviceException(Shell subprocess crashed with segmentation fault.)
#0      FlutterTesterTestDevice.finished (package:flutter_tools/src/test/flutter_tester_device.dart:251:5)
<asynchronous suspension>
#1      FlutterTesterTestDevice.kill (package:flutter_tools/src/test/flutter_tester_device.dart:233:5)
<asynchronous suspension>
#2      FlutterPlatform._startTest.<anonymous closure> (package:flutter_tools/src/test/flutter_platform.dart:555:9)
<asynchronous suspension>
#3      FlutterPlatform._startTest (package:flutter_tools/src/test/flutter_platform.dart:617:11)
<asynchronous suspension>
```

I am guessing due to this crash state, the test runner gets into a bad state which causes thousands of misattributed lines.

Filing against `tool` (I don't believe this is specific to our own test infrastructure).
Repository: flutter
Issue: Make `flutter analyze --suggestions` agnostic to patch versions
Labels: platform-android,P1,team-android,triaged-android

Context https://github.com/flutter/flutter/pull/156502#discussion_r1803810604

Our Gradle/Java/AGP compat checking code includes max known and supported Gradle and AGP versions. We should probably make the code that handles these versions agnostic to patch versions, in my opinion.
Repository: svelte
Issue: Flash of content if a `fly` in-transition started immediately after out-transition
Labels: bug,transition/animation

### Describe the bug

Most of the time if the element is shown immediately after it's out-transition ended it momentarily flashes in its final state in DOM before the in-transition kicks in.

Doesn't matter if the element is shown in `onoutroend`, or in [$effect teardown in use](https://svelte.dev/docs/svelte/use)

Spamming `await tick()` everywhere doesn't help at all, but wrapping the code that starts the in-transition in `setTimeout(..., 0)` does. Makes me think about task queue starvation by microtask queue, but I don't understand JS at the level that deep.

Bug reproduced on Brave Browser: 129.1.70.126, desktop Safari 16.6.1 and mobile Safari. The same code on Svelte v4 works correctly.


### Reproduction
[REPL link @5.2.3](https://svelte.dev/playground/87db0d4896204488a5e490d29e9a3437?version=5.2.3)

Same code [works fine on 4.2.19](https://svelte.dev/playground/eb2e676081f6449e9116fe801a4e5cf1?version=4.2.19)

### Logs

_No response_

### System Info

```shell
System:
    OS: macOS 11.7.10
    CPU: (4) x64 Intel(R) Core(TM) i7-4650U CPU @ 1.70GHz
    Memory: 274.89 MB / 8.00 GB
    Shell: 3.6.1 - /usr/local/bin/fish
  Binaries:
    Node: 22.7.0 - ~/.local/share/nvm/v22.7.0/bin/node
    Yarn: 1.22.19 - /usr/local/bin/yarn
    npm: 10.8.2 - ~/.local/share/nvm/v22.7.0/bin/npm
  Browsers:
    Brave Browser: 129.1.70.126
    Chrome: 126.0.6478.63
    Safari: 16.6.1
  npmPackages:
    svelte: ^5.0.0 => 5.0.5
```


### Severity

annoyance
Repository: PowerToys
Issue: awake not observing the powertoys setting of keep awake indefinitely
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.85.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Awake

### Steps to reproduce

[PowerToysReport_2024-10-24-14-11-09.zip](https://github.com/user-attachments/files/17511188/PowerToysReport_2024-10-24-14-11-09.zip)
enable awake
select keep awake indefinitely
enable keep screen on

### ✔️ Expected Behavior

screen should not sleep

### ❌ Actual Behavior

screen sleeps

### Other Software

_No response_
Repository: go
Issue: proposal: strings, bytes: Add JoinSeq
Labels: Proposal

### Proposal Details

#61901 added SplitSeq and friends to bytes, but nothing for joining. Right now you have to do slices.Collect first or use a bytes.Buffer/strings.Builder, which feels unfortunate. I propose to add `strings.JoinSeq(seq iter.Seq[string], sep string) string` and the bytes equivalent as well.
Repository: react
Issue: [React 19] Inconsistent hoisting behavior between links created with  `preload()` and manually inserted ones
Labels: Resolution: Stale,React 19

## Summary

When trying to preload the `srcset` of an image with a `link` tag.  I found an unexpected behavior.

### Examples

#### Preloading srcset with `preload()`

``` js
preload('https://sample.com/foo', {
  as: 'image',
  imageSrcSet: 'https://sample.com/foo 1x',
});
```
##### Results (As expected)

``` html
<html>
  <head>
    <link rel="preload" as="image" imagesrcset="https://sample.com/foo 1x" />
  </head>
  <body></body>
</html>
```
#### Preloading srcset with `<link >`

``` html
<link
  rel="preload"
  as="image"
  imageSrcSet="https://sample.com/foo 1x"
/>
```
##### Expected

``` html
<html>
  <head>
    <link rel="preload" as="image" imagesrcset="https://sample.com/foo 1x" />
  </head>
  <body></body>
</html>
```
##### Current

``` html
<html>
  <head></head>
  <body>
    <link rel="preload"  as="image" imagesrcset="https://sample.com/foo 1x" />
  </body>
</html>
```

#### Preloading src with `preload()`

``` js
preload('https://sample.com/foo', {
  as: 'image',
});
```
##### Results (As expected)

``` html
<html>
  <head>
    <link rel="preload" as="image" href="https://sample.com/foo" />
  </head>
  <body></body>
</html>
```

#### Preloading src with `<link >`

``` html
<link
  rel="preload"
  as="image"
  href="https://sample.com/foo"
/>
```
##### Results (As expected)

``` html
<html>
  <head>
    <link rel="preload" as="image" href="https://sample.com/foo" />
  </head>
  <body></body>
</html>
```

#### Rendering `<img /> with srcset`

``` html

<img src="https://sample.com/bar" srcSet="https://sample.com/bar 1x" />
```
##### Results (As expected)

``` html
<html>
  <head>
    <link rel="preload" as="image" imagesrcset="https://sample.com/foo 1x" />
  </head>
  <body>
    <img src="https://sample.com/bar" srcset="https://sample.com/bar 1x" />
  </body>
</html>
```

Is this intended? Why links created with `preload()` end up hoisted to the head, while manually inserted links without the `href` attribute do not?
Repository: next.js
Issue: Next.JS does NOT support Docker Swarm.
Labels: bug,Output (export/standalone)

### Link to the code that reproduces this issue

https://github.com/SanderCokart/sandercokart.com/tree/development

### To Reproduce

`docker service create` and `docker stack deploy` both do launch the nodes and services but going to localhost:3000 results in nothing.

### Current vs. Expected behavior

Going to localhost:3000 results in nothing.

**Expected behavior:** webpage shows up

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 65268
  Available CPU cores: 16
Binaries:
  Node: 20.17.0
  npm: N/A
  Yarn: N/A
  pnpm: 9.11.0
Relevant Packages:
  next: 14.2.11 // An outdated version detected (latest is 15.0.1), upgrade is highly recommended!
  eslint-config-next: 14.2.11
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.2
Next.js Config:
  output: standalone
```


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

Output (export/standalone)

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

Other (Deployed)

### Additional context

After a `docker swarm init` you can run `docker service create -p 80:80 --replicas 1 --name nginx nginx` and then visit localhost:80 (make sure to disable apache in wsl running `sudo systemctl stop apache2.service` in wsl terminal) you can see the nginx welcome page.

Using curl to go to localhost:3000 you get this:
```
curl: (52) Empty reply from server
```
Repository: next.js
Issue: Example Dockerfile does not copy .npmc / .yarnrc files
Labels: examples

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 32566
  Available CPU cores: 16
Binaries:
  Node: 20.12.2
  npm: N/A
  Yarn: N/A
  pnpm: 9.10.0
Relevant Packages:
  next: 14.2.10 // An outdated version detected (latest is 15.0.1), upgrade is highly recommended!
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.5.4
Next.js Config:
  output: standalone
```


### Which example does this report relate to?

with-docker

### What browser are you using? (if relevant)

_No response_

### How are you deploying your application? (if relevant)

_No response_

### Describe the Bug

Currently example `Dockerfile` does not try to copy `.npmrc` / `.yarnrc` files which can lead to issues when installing packages

### Expected Behavior

Example `Dockerfile` should attempt to copy those configuration files just like it attempts to copy the lock files

### To Reproduce

1. Add a package from a private registry to your NextJS project
2. Copy the example `Dockerfile` into your project
3. Attempt to build the docker image
Repository: ollama
Issue: RFC: multi-template models
Labels: feature request

Some models are being released with multiple chat_templates, eg [Aya-Expanse 32B & 8B](https://huggingface.co/CohereForAI/aya-expanse-8b/blob/b9848575c8731981dfcf2e1f3bfbcb917a2e585d/tokenizer_config.json#L304) which has a default template but also templates tuned for RAG and Tool use.

There's a few ways these could be supported.
1. Mash all of the templates together and add a new option to the API request that the golang template can access.
```go
{{- if eq .TemplateSelector "rag" }}{{ system_message = 'Decide which of the retrieved documents are relevant to the user" }}
{{- else if eq .TemplateSelector "tool_use" }}{{ system_message = "You can use the following tools" }}
{{- else system_message =  "You are Aya, a brilliant, sophisticated, multilingual AI-assistant" }}
{{- end }}
<BOS_TOKEN>
...
```
2. Give the API the ability to supply a template.  This currently works for `/api/generate` but not `/api/chat`, and requires some surgery to make it work.
3. Create different versions of the model with the same GGUF with different TEMPLATE statements.  This is easiest but requires loading the same model multiple times.
4. Modifying TEMPLATE processing to support TEMPLATE[].  Also requires metadata in the API call to choose the appropriate template.

Is there any appetite for supporting multi-template models?