sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ui
Issue: [bug]: Difficulties Encountered During SHADCN Installation on Next.js 15
Labels: bug

### Describe the bug

Problem:
![Screenshot 2024-11-07 190817](https://github.com/user-attachments/assets/dcaa4643-9116-487d-ae4a-0f6a50570d7d)


### Affected component/components

Installation

### How to reproduce

1. Support `@radix-ui/react-icons` peer dependencies to React 19
2. Documentation regarding next.js 15 installation

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
npx shadcn@latest init  
✔ Preflight checks.
✔ Verifying framework. Found Next.js.
✔ Validating Tailwind CSS.
✔ Validating import alias.
√ Which style would you like to use? » Default
√ Which color would you like to use as the base color? » Gray
√ Would you like to use CSS variables for theming? ... no / yes
✔ Writing components.json.
✔ Checking registry.
✔ Updating tailwind.config.js
✔ Updating app\globals.css
  Installing dependencies.

It looks like you are using React 19.
Some packages may fail to install due to peer dependency issues in npm (see https://ui.shadcn.com/react-19).

√ How would you like to proceed? » Use --force
⠴ Installing dependencies.
Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

Command failed with exit code 1: npm install --force tailwindcss-animate class-variance-authority lucide-react clsx tailwind-merge
Unknown command: "install$1$1"


Did you mean this?
  npm install # Install a package
To see a list of supported npm commands, run:
  npm help
```


### System Info

```bash
Windows 11, Git Bash, Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: go
Issue: cmd/internal/testdir: Test/typeparam/chans.go failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/internal/testdir" && test == "Test/typeparam/chans.go"
```

Issue created automatically to collect these failures.

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

    === RUN   Test/typeparam/chans.go
    === PAUSE Test/typeparam/chans.go
    === CONT  Test/typeparam/chans.go
        testdir_test.go:147: exit status 2
            panic: _Ranger Send should have failed, but timed out
            
            goroutine 1 gp=0x40000021c0 m=4 mp=0x4000080008 [running]:
            panic({0xb95e0?, 0xfa808?})
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/panic.go:806 +0x154 fp=0x40000a0ea0 sp=0x40000a0df0 pc=0x73914
            main.TestRanger()
    ...
            runtime.gcBgMarkWorker(0x4000180000)
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/mgc.go:1363 +0xdc fp=0x4000189fb0 sp=0x4000189f10 pc=0x257ec
            runtime.gcBgMarkStartWorkers.gowrap1()
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/mgc.go:1279 +0x28 fp=0x4000189fd0 sp=0x4000189fb0 pc=0x256d8
            runtime.goexit({})
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/asm_arm64.s:1260 +0x4 fp=0x4000189fd0 sp=0x4000189fd0 pc=0x79ac4
            created by runtime.gcBgMarkStartWorkers in goroutine 1
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/mgc.go:1279 +0x140
            
    --- FAIL: Test/typeparam/chans.go (60.52s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: angular
Issue: Signal effect for an input signal gets triggered after writeValue in custom form component (control value accessor)
Labels: area: core,area: forms,cross-cutting: signals

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

core, forms

### Is this a regression?

No

### Description

for a component that is implementing ControlValueAccessor interface, writeValue is being called **before** an effect for an input signal. This is inconsistent with the older way of using input setter or ngOnChanges to trigger some side effect at component initialisation.


### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/stackblitz-starters-xhlf3j?file=test.component.ts

### Please provide the exception or error you saw

There is no error, just inconsistency with input setters/ngOnChanges which should be replaced by signals.

### Please provide the environment you discovered this bug in (run `ng version`)

Angular CLI: 19.0.0-rc.1
Node: 18.20.3
Package Manager: npm 10.2.3
OS: linux x64

Angular: 19.0.0-rc.1
... animations, cli, common, compiler, compiler-cli, core, forms
... platform-browser, router

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1900.0-rc.1
@angular-devkit/build-angular   19.0.0-rc.1
@angular-devkit/core            19.0.0-rc.1
@angular-devkit/schematics      19.0.0-rc.1
@schematics/angular             19.0.0-rc.1
rxjs                            7.8.1
typescript                      5.5.4
zone.js                         0.15.0

### Anything else?

**Use case why it would make sense:**
I am defining an empty form record. When the input is initialised with list of items: 

1. **effect** is triggered to populate the form record with form controls reflecting the items
2. **writeValue** updates the form record value


Please note that I encountered this bug on version 18.2.10. Then I thought it might be fixed already with this [PR](https://github.com/angular/angular/pull/57874) so I tested it again with 19.0.0-rc.1

Angular CLI: 18.2.10
Node: 20.12.2
Package Manager: npm 10.5.0
OS: darwin x64

Angular: 18.2.9
... animations, cdk, common, compiler, compiler-cli, core, forms
... language-service, localize, material, platform-browser
... platform-browser-dynamic, platform-server, router
... service-worker

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1802.10
@angular-devkit/build-angular   18.2.9
@angular-devkit/core            18.2.9
@angular-devkit/schematics      18.2.9
@angular/cli                    18.2.10
@schematics/angular             18.2.9
rxjs                            7.8.1
typescript                      5.5.4
zone.js                         0.14.10
Repository: langchain
Issue: Unable to stream structured output with ChatBedrock
Labels: investigate

### Checked other resources

- [X] I added a very descriptive title to this issue.
- [X] I searched the LangChain documentation with the integrated search.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I am sure that this is a bug in LangChain rather than my code.
- [X] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

### Example Code

```python
class Joke(TypedDict):
    """Joke to tell user."""

    setup: Annotated[str, ..., "The setup of the joke"]
    punchline: Annotated[str, ..., "The punchline of the joke"]
    rating: Annotated[Optional[int], None, "How funny the joke is, from 1 to 10"]

async def llm_stream(topic: str):
    llm = ChatBedrock(
        model=config.BEDROCK_LLM_MODEL_ID,
        model_kwargs=dict(temperature=0.05, top_k=100, top_p=0.95),
        provider="anthropic",
    )
    structured_llm = llm.with_structured_output(Joke)
    
    async for chunk in structured_llm.astream(f"Tell me a really long joke story about {topic}"):
        print(chunk)
```

### Error Message and Stack Trace (if applicable)

_No response_

### Description

Seems like there is something going wrong if you want to stream with structured output using ChatBedrock. Using ChatOpenAI works with the same code but ChatBedrock doesn't. Even I use `astream` or `stream` method, it just gives the output in one chunk and behaves like synchronous invocation.

The same code works for ChatOpenAI. Also tried to switch to json_schema, but doesn't help. If you remove structured_output, streaming works.

I guess for now, as a workaround, I can do some prompt engineering to get a json output.

### System Info

System Information
------------------
> OS:  Darwin
> OS Version:  Darwin Kernel Version 24.1.0: Thu Oct 10 21:03:11 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6020
> Python Version:  3.11.2 (main, Jul 19 2024, 17:09:07) [Clang 15.0.0 (clang-1500.3.9.4)]

Package Information
-------------------
> langchain_core: 0.3.12
> langchain: 0.3.4
> langsmith: 0.1.136
> langchain_aws: 0.2.2
> langchain_text_splitters: 0.3.0
> langchain_weaviate: 0.0.3

Optional packages not installed
-------------------------------
> langgraph
> langserve

Other Dependencies
------------------
> aiohttp: 3.10.10
> async-timeout: Installed. No version info available.
> boto3: 1.35.36
> httpx: 0.27.0
> jsonpatch: 1.33
> numpy: 1.26.4
> orjson: 3.10.9
> packaging: 24.1
> pydantic: 2.9.2
> PyYAML: 6.0.2
> requests: 2.32.3
> requests-toolbelt: 1.0.0
> simsimd: 3.7.7
> SQLAlchemy: 2.0.36
> tenacity: 8.5.0
> typing-extensions: 4.12.2
> weaviate-client: 4.9.0
Repository: PowerToys
Issue: ctrl + alt + '=(+)' shortcut not work
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Ctrl + Alt + '=(used together with +)' does not work
Ctrl + Alt + 'any other key' works.
Upon further inspection, it appears that the Ctrl + Alt keys are recognized, but pressing the =(+) key while in this state is not recognized. It seems to occur consistently, not just in specific programs.

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: svelte
Issue: Slide transition throws a "Invalid keyframe value for property height" warning since Svelte 5
Labels: transition/animation

### Describe the bug

Using Svelte 4 and before, this REPL custom Accordion with a slide effect was working perfectly. Since Svelte 5, it throws a warning:
> Invalid keyframe value for property height: NaNpx

I like the approach of this accordion using `{#key isOpen}` as it re-runs the transition and also keeps the content in the DOM,  only playing with CSS to hide the content when closed.

I haven't made this REPL but adapted it to a similar component in my codebase.

### Reproduction

REPL with Svelte 5 (and the warning): https://svelte.dev/playground/a904286e5a4c497daa9e6f9351b3f3a9?version=5
REPL with Svelte 4 (and no warning): https://svelte.dev/playground/a904286e5a4c497daa9e6f9351b3f3a9?version=4

### Logs

```shell
> Invalid keyframe value for property height: NaNpx
```


### System Info

```shell
System:
    OS: macOS 15.1
    CPU: (12) arm64 Apple M2 Max
    Memory: 258.97 MB / 32.00 GB
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.18.0 - ~/.local/state/fnm_multishells/32005_1720871078955/bin/node
    Yarn: 1.22.19 - ~/.local/state/fnm_multishells/32005_1720871078955/bin/yarn
    npm: 10.9.0 - ~/.local/state/fnm_multishells/32005_1720871078955/bin/npm
    pnpm: 8.5.0 - ~/.local/state/fnm_multishells/32005_1720871078955/bin/pnpm
    bun: 1.1.34 - ~/.bun/bin/bun
  Browsers:
    Brave Browser: 130.1.71.118
    Safari: 18.1
```


### Severity

annoyance
Repository: terminal
Issue: AtlasEngine: Incorrectly broken up MapCharacters runs should be joined before text shaping
Labels: Area-Rendering,Issue-Bug,Product-Terminal,Priority-3,Area-AtlasEngine

### Windows Terminal version

1.21.2911.0

### Windows build number

10.0.19045.0

### Other Software

_No response_

### Steps to reproduce

Print https://unicode.org/Public/emoji/latest/emoji-test.txt under Windows 10.

### Expected Behavior

All of the emojis work.

### Actual Behavior

All emojis with a U+200D joiner are broken. This is because DirectWrite's `MapCharacters()` is kinda bad and breaks them up. We then pass the broken runs to text shaping which are unable to see that the emoji consists of multiple parts joined together. This causes them to look incorrectly. We need to join the broken runs first and then pass the result to text shaping.
Repository: ui
Issue: [bug]: Unknown command: "install$1$1" when initializing on existing Next.js 14 project
Labels: bug

### Describe the bug

I have an existing Next.js 14 project I'd like to add shadcn to. But whenever I try to initialize it with `npx shadcn@latest init`, it has this error: `Unknown command: "install$1$1"`. I tried to do the [Manual Installation](https://ui.shadcn.com/docs/installation/manual), but when I try to add a component using the CLI, it still yields the same error.

### Affected component/components

All

### How to reproduce

1. Run the command `npx shadcn@latest init` on an existing project, or `npx shadcn@latest add <component>` after doing a manual install.
2. Follow on-screen instructions. (I selected Default-Gray-Yes)
3. Error will occur after `Installing dependencies`

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash
PS C:\Users\hikari\Desktop\Project\myProgram> npx shadcn@latest init
✔ Preflight checks.
✔ Verifying framework. Found Next.js.
✔ Validating Tailwind CSS.
✔ Validating import alias.
√ Which style would you like to use? » Default
√ Which color would you like to use as the base color? » Gray
√ Would you like to use CSS variables for theming? ... no / yes
✔ Writing components.json.
✔ Checking registry.
✔ Updating tailwind.config.js
✔ Updating src\app\globals.css
⠧ Installing dependencies.
Something went wrong. Please check the error below for more details.
If the problem persists, please open an issue on GitHub.

Command failed with exit code 1: npm install tailwindcss-animate class-variance-authority lucide-react clsx tailwind-merge
Unknown command: "install$1$1"


Did you mean this?
  npm install # Install a package
To see a list of supported npm commands, run:
  npm help
```


### System Info

```bash
Windows 11 64-bit
Node version: v22.6.0
npm version: 10.9.0
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: pytorch
Issue: Default value for get_num_threads
Labels: triaged,module: multithreading

### 📚 The doc issue

Hello.
I was taking a look at the document about CPU threading that torch internal uses, referring the link : https://pytorch.org/docs/stable/notes/cpu_threading_torchscript_inference.html

Here, at the "Runtime API" tab, it says for both intra-op and inter-op parallelism, the default number of threads is set to the number of CPU cores.

![Screenshot from 2024-11-07 23-39-36](https://github.com/user-attachments/assets/ed0e8915-bad1-4891-bab2-09bad26d6177)

However, if I run the **at::get_num_threads** command in libtorch and **get_num_threads** in pytorch, it shows different results. The scripts are below

![Screenshot from 2024-11-07 23-41-38](https://github.com/user-attachments/assets/fd15a9c0-ac69-4b70-badd-efcdf67766c8)

![Screenshot from 2024-11-07 23-42-17](https://github.com/user-attachments/assets/97a86896-648a-425e-8202-71ea9b7e912a)

Above python usage reports 20 threads, but libtorch reports 40 threads. My machine has 20 CPU cores, and I expect that libtorch somehow reported the total number of hyperthreads, as my machine has 2 hyperthreads per core.

Below is my setups 
- python 3.10.14
- pytorch 2.3.1.+cu121
- libtorch cxx11ABI version 
- g++ 10.5.0 


Thanks


### Suggest a potential alternative/fix

Update related part of the document

cc @albanD
Repository: rust
Issue: Add a regression test for #132587
Labels: A-parser,E-needs-test,T-compiler,E-medium,C-bug,A-proc-macros

#132587 partially reverted #129346 because that caused a test failure in cfg_eval, but the revert PR didn't come with a test because it involved proc-macros and was hard to minimize. We should still add a regression test.

@rustbot label +E-needs-test

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"yegeunyang"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: flutter
Issue: DateTimePicker date buttons fail touch target size accessibility checks
Labels: framework,f: material design,a: accessibility,f: date/time picker,has reproducible steps,P2,team-accessibility,triaged-accessibility,found in release: 3.27

### Steps to reproduce

Internal bug b/377876657

1. Write some UI that invokes `showDatePicker`
2. Use an accessibility checker on the resulting UI, such as 
    ```dart
    await expectLater(
      tester,
      meetsGuideline(androidTapTargetGuideline),
    );
    ```


### Expected results

All user-interactable elements should have a minimum touch target size of at least 48dp x 48dp, as described at https://support.google.com/accessibility/android/answer/7101858.

### Actual results

The size of the individual day buttons is less than 48x48


### Code sample

<details open><summary>Code sample</summary>

App code:

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      title: 'Flutter Demo',
      theme: ThemeData.light(useMaterial3: true),
      home: MyHomePage(title: 'Flutter Demo Home Page'),
    );
  }
}

class MyHomePage extends StatefulWidget {
  MyHomePage({Key? key, required this.title}) : super(key: key);

  final String title;

  @override
  _MyHomePageState createState() => _MyHomePageState();
}

class _MyHomePageState extends State<MyHomePage> {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      appBar: AppBar(title: Text(widget.title)),
      body: Center(child: Text('Body')),
      floatingActionButton: FloatingActionButton(
        onPressed: () {
          showDatePicker(
            context: context,
            initialDate: DateTime.now(),
            firstDate: DateTime(2024),
            lastDate: DateTime(2026),
          );
        },
        tooltip: 'Increment',
      ),
    );
  }
}
```

Test code:

```dart
import 'package:flutter/material.dart';
import 'package:flutter_test/flutter_test.dart';
// Import for file above
import 'package:hello_flutter.app/main.dart';

void main() {
  testWidgets('test', (WidgetTester tester) async {
    await tester.pumpWidget(MyApp());

    final button = find.byType(FloatingActionButton);

    await tester.tap(button);

    await tester.pumpAndSettle();

    expect(find.byType(DatePickerDialog), findsOneWidget);
    await expectLater(
      tester,
      meetsGuideline(androidTapTargetGuideline),
    );
  });
}
```

</details>


### Screenshots or Video

Screenshots / Video demonstration: N/A

### Logs

Logs: N/A


### Flutter Doctor output

<details open><summary>Doctor output</summary>

N/A, Google internal client

</details>
Repository: vscode
Issue: Copilot Inline chat hunks don't disappear when rejected
Labels: bug,inline-chat

<!-- ⚠️⚠️ 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?: No

<!-- 🪓 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: Linux

Steps to Reproduce:

1. Open the inline chat (ctrl +I) and sent a prompt that generates edits in multiple hunks
2. Discard one of the hunks

Instead of undoing the previous hunk edit when discarding it, the hunk is still visible and decorated as a diff, see screenshot:

![Image](https://github.com/user-attachments/assets/4b427aa9-dce6-4c7d-82ec-76f446774745)
Repository: excalidraw
Issue: Vertical text with upright direction
Labels: enhancement,Text rendering,text wrapping

It seems all excalidraw's text is horizontal.

Is it possible to support change text orientation to vertical + upright?

For example:

![Image](https://github.com/user-attachments/assets/afc525d9-34c1-44b0-9045-686a963cd78d)
Repository: vscode
Issue: Debt: Cleanup Tree Find (`FindController`, `FindFilter` and toggles)
Labels: debt,tree-widget

`AsyncFindController` has a weird dependency on `FindController`. Some functionality should be moved down to `AbstractFindController` so that `AsyncFindController` does not need to extend `FindController`. 

Also need to look into toggles. Maybe the toggles should be given from the start to the filter and then the filter should listen on event from it...

related [#232964](https://github.com/microsoft/vscode/pull/232964)
Repository: godot
Issue: Attenuation model of AudioStreamPlayer3D breaks when using AnimationPlayer with web build 
Labels: bug,platform:web,topic:audio

### Tested versions

- Reproducible v4.3.stable.official [77dcf97d8]

### System information

Windows 10 - v4.3.stable.official [77dcf97d8]

### Issue description

Attenuation model emits sound globally with max_distance setting only on the web build

### Steps to reproduce

1) Create AudioStreamPlayer3D, AnimationPlayer
2) Add Audio Playback track to animation and play animation with AnimationPlayer
3) Configure moving camera to check if max_distance and attenuation model works properly
4) Build for web, sound is emitted globally for some reason.

Compare Web build to debug play, you will see that's only web build issue

### Minimal reproduction project (MRP)

[TestAudioStream3D.zip](https://github.com/user-attachments/files/17664232/TestAudioStream3D.zip)
Repository: rust
Issue: Nightly `rustc-dev` can't be used in cross-compilation
Labels: A-cross,T-infra,C-bug

## Bug

I've made a minimal reproducible repo: https://github.com/tombh/nightly_cross_minimal_repro

Pasting `main.rs`:
```rs
#![feature(rustc_private)]

extern crate rustc_ast;
extern crate rustc_driver;
extern crate rustc_macros;

fn main() {
    println!("{}", rustc_ast::node_id::CRATE_NODE_ID)
}
```

The build commands are here: https://github.com/tombh/nightly_cross_minimal_repro/blob/main/.github/workflows/ci.yml

Pasting the most relevant part:
```sh
rustup toolchain install nightly-2024-09-30
rustup default nightly-2023-09-30
rustup target add aarch64-unknown-linux-gnu
rustup component add rust-src rustc-dev-aarch64-unknown-linux-gnu llvm-tools
...
cargo -v build --locked --release --target aarch64-unknown-linux-gnu
```

And here is the failing build: https://github.com/tombh/nightly_cross_minimal_repro/actions/runs/11463471346/job/31897390824#step:5:9

Also, just out of interest, here is a failing build with a more recent nightly (`nightly-2024-10-21`), it fails differently, it can't find `derive_where`: https://github.com/tombh/nightly_cross_minimal_repro/actions/runs/11463505291/job/31897508604#step:5:9

## Relevant Issues

- The bug is being discussed in a `rustup` issue: https://github.com/rust-lang/rustup/issues/3255. That is where it was suggested that this is rather a `rust` or `cargo` issue.
- #62447
- #70838