sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ui
Issue: [bug]: component at https://ui.shadcn.com/r/colors/Gray.json was not found.
Labels: bug

### Describe the bug



The component at https://ui.shadcn.com/r/colors/Gray.json was not found.
It may not exist at the registry. Please make sure it is a valid component.

### Affected component/components

Drawer

### How to reproduce

1. Go to Docs on Shadcn
2. Click on Drawer
3. follow the installation steps

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Terminal
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: angular
Issue: adev: Dropdown design issue on Firefox
Labels: area: docs-infra

### Describe the problem that you experienced

Not sure if all dropdowns are affected, but the dropdown on the [Angular Update page](https://angular.dev/update-guide) has two issues on Firefox:
- There is some horizontal scrolling (which starts all the way right, making it impossible to read what it says without scrolling left).
- The scrollbar background is translucent.

### Enter the URL of the topic with the problem

https://angular.dev/update-guide

### Describe what you were looking for in the documentation

_No response_

### Describe the actions that led you to experience the problem

_No response_

### Describe what you want to experience that would fix the problem

_No response_

### Add a screenshot if that helps illustrate the problem

Firefox:
![Image](https://github.com/user-attachments/assets/2edb27f7-7652-41f4-b939-dcb194039e8b)

Chrome:
![Image](https://github.com/user-attachments/assets/e132b3fe-7ed0-4925-81a3-5ee5f9a5174b)



### If this problem caused an exception or error, please paste it here

```true

```

### If the problem is browser-specific, please specify the device, OS, browser, and version

```true
Firefox 132 (on Windows 10, not sure if relevant)
```

### Provide any additional information here in as much as detail as you can

```true

```
Repository: material-ui
Issue: [docs] Convert the "all components" images to CSS
Labels: docs,design

### Summary

The [Material UI](https://mui.com/material-ui/all-components/), [Base UI](https://mui.com/base-ui/all-components/), and [Charts](https://mui.com/x/react-charts/#all-mui-x-charts-components) docs have an "all components" page with illustrated cards for each component. These illustrations are currently done on Figma and added to the cards as png. That's not entirely ideal because:

1. Maintaining them on Figma is an additional tool to manage
2. Compressing images and then needing to download them is cumbersome and not efficient performance-wise
3. We can't add micro animations

So, the idea is to, at some point, tackle all of these points by converting them into CSS. 
This issue tracks the effort for the Base UI images.

**Search keywords**: component images css

**Search keywords**:
Repository: flutter
Issue: Build linux failed by INSTALL not found "native_assets/linux" 
Labels: platform-linux,a: desktop,P2,team-linux,triaged-linux

### Steps to reproduce

'flutter build linux' will trigger this bug. I've tried 'flutter clean' or create a sample project but this bug still occurred.

### Expected results

build successfully just as 'flutter build apk' does.

### Actual results

```
CMake Error at cmake_install.cmake:112 (file):
  file INSTALL cannot find "/home/....../build/native_assets/linux": No such
  file or directory.
```

### Code sample

<details open><summary>Code sample</summary>

```dart
[Paste your code here]
```

</details>


### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

[Upload media here]

</details>


### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, 3.24.5, on Arch Linux 6.11.9-zen1-1-zen, locale en_US.UTF-8)
[!] Android toolchain - develop for Android devices (Android SDK version 34.0.0)
    ! Some Android licenses not accepted. To resolve this, run: flutter doctor --android-licenses
[✓] Chrome - develop for the web
[✓] Linux toolchain - develop for Linux desktop
[!] Android Studio (not installed)
[✓] IntelliJ IDEA Ultimate Edition (version 2024.3)
[✓] Connected device (2 available)
[✓] Network resources

```

</details>
Repository: material-ui
Issue: [Autocomplete][docs] The Tailwind code demo doesn't include item focus styles
Labels: bug 🐛,docs,component: autocomplete

### Related page

https://mui.com/base-ui/react-autocomplete/

### Kind of issue

Missing information

### Issue description

The Tailwind autocomplete demo has visible focus on selected items, i.e. if you hover an item or used the up/down keys, items are visibly focused.

However, if you copy the code from the code sample into a project, or if you open the [linked codesandbox](https://codesandbox.io/s/myqs2l?file=/src/Demo.tsx), those visible focus states don't work and there's no visible feedback about which item is focused.

From the devtools, it looks like there are some extra css rules applied to the in-page demo that aren't in the code sample.

### Context

I'm trying to use the base-ui autocomplete component with Tailwind in the way demonstrated on the page.

**Search keywords**: tailwind focus autocomplete base-ui

**Search keywords**:
Repository: ant-design
Issue: [BUG] Select with search requires double enter hit to trigger the onChange event
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/antd-reproduce-5x-qe3zcq?file=demo.tsx)

### Steps to reproduce

1. Choose 'Edoardo' user shown into the Select by click
2. Re-open the Select and fill the text with 'Brugola', then hit 'Enter' (one hit the search works)
3. Re-open the Select and fill the text with 'Pistoni', then hit 'Enter' (not work at the first hit. Hit 'Enter' again and it works)

### What is expected?

Hit the 'Enter' button only once time.

### What is actually happening?

After the first search by text (that works as expected), the Select requires two hit by 'Enter' button to perform the onChange event.

| Environment | Info |
| --- | --- |
| antd | 5.22.1 |
| React | 18.3.1 |
| System | nodeJS latest |
| Browser | Chrome latest |

---
This is happened with React state and REDUX also.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: vscode
Issue: Horizontal scroll position resets in file when seek peek definition called
Labels: feature-request,ux,polish,editor-symbols

<!-- ⚠️⚠️ 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.2
- OS Version: linux mint mate 21.3

Version: 1.95.2
Commit: e8653663e8840adaf45af01eab5c627a5af81807
Date: 2024-11-07T11:07:22.054Z
Electron: 32.2.1
ElectronBuildId: 10427718
Chromium: 128.0.6613.186
Node.js: 20.18.0
V8: 12.8.374.38-electron.0
OS: Linux x64 5.15.0-126-generic

__Issue:__
With long lines in a code file and horizontally scrolled to bring the remaining part of the line into view
In this scroll position, when tried to seek peek definition 
the seek peek definition shows inline,
but the original code file horizontally scrolls back to start position


Steps to Reproduce:
1.  Identify long code line in a file and horizontally move to bring a symbol to view
2.  select seek peek definition for this symbol

sample images - 
![Image](https://github.com/user-attachments/assets/2de853df-32de-4585-b0f1-f1d17b704b00)

![Image](https://github.com/user-attachments/assets/41d014a1-9bb8-4351-ab4d-5c2c9e1e8e56)
( note the horizontal scroll position has come to start position )
and have scroll back to see symbol in code.

__Expected behaviour:__
horizontal scroll position to be retained during seek peek definition
as in sample image below

![Image](https://github.com/user-attachments/assets/fb1a4243-2c09-4203-a031-03acfc608e38)
Repository: rustdesk
Issue: Keyboard German to German Raspberry PI4 not working
Labels: bug

### Bug Description

Hello,

If i connect with Rustdesk to a Raspberry PI4 local Language German: 
![image](https://github.com/user-attachments/assets/829a2e66-7f81-4932-a27d-4a0138f4e0d2)
The Keys are not forwarded correctly. For example instead of * i get }.  Do you have a Idea how to fix this?

Thanks

### How to Reproduce

Install Rustdesk under Raspbian and connect.

### Expected Behavior

Correct keys.

### Operating system(s) on local (controlling) side and remote (controlled) side

Windows 10 -> Raspbian

### RustDesk Version(s) on local (controlling) side and remote (controlled) side

1.3.1 - > 1.2.7

### Screenshots

![image](https://github.com/user-attachments/assets/6cafb1af-a945-4be2-b9b8-258ed8f57995)


### Additional Context

_No response_
Repository: vscode
Issue: Enable highlighting scroll in copilot chat window
Labels: chat

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

In the Github Copilot chat window it can sometimes give very long answers, rewriting entire files/scripts, when only a portion of that code is actually changing. Currently, when I try to highlight a longer section of code but don't want all of it, I need to click the start of where I want to copy, scroll down manually, and click the end with shift held to highlight everything. Instead it would be easier if I could highlight and have the scrollbar move with the highlighted section as it hits the top/bottom of the currently visible window. This type of feature is implemented in most other programs with scroll text boxes.
Repository: node
Issue: FATAL ERROR: v8::ToLocalChecked Empty MaybeLocal
Labels: confirmed-bug,child_process

### Version

v22.11.0

### Platform

```text
Darwin 23.6.0 Darwin Kernel Version 23.6.0 

I also tested it on Linux machine.
```


### Subsystem

_No response_

### What steps will reproduce the bug?

Hi, 

I want to report a node bug. It can reproduced by running the following PoC, node.js gives a FATAL error.

```javascript
const {spawn} = require('child_process');
Object.defineProperty(Array.prototype, "0", {
  set(){
    console.log(123);
  } 
});
spawn("ls");
```

Please note that this bug differs from the reported [here](https://github.com/nodejs/node/issues/54186). 

AH. 

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

By just running the given code, node runtime gives node crash.

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

Not a crash, by looking at the stack trace, it is connected to `v8::ToLocalChecked Empty MaybeLocal`.

### What do you see instead?

FATAL ERROR: v8::ToLocalChecked Empty MaybeLocal

FATAL ERROR: v8::ToLocalChecked Empty MaybeLocal
----- Native stack trace -----

 1: 0x10bdd2277 node::OnFatalError(char const*, char const*)
 2: 0x10c025171 v8::Utils::ReportApiFailure(char const*, char const*)
 3: 0x10bef84cc node::(anonymous namespace)::ProcessWrap::Spawn(v8::FunctionCallbackInfo<v8::Value> const&) 
 4: 0x10cb21a62 Builtins_CallApiCallbackGeneric [~/node/v22.11.0/bin/node]

----- JavaScript stack trace -----

1: ChildProcess.spawn (node:internal/child_process:395:28)
2: spawn (node:child_process:759:9)
3: ${PATH_TO_POC}
4: node:internal/modules/cjs/loader:1546:14
5: node:internal/modules/cjs/loader:1689:10
6: node:internal/modules/cjs/loader:1318:32
7: node:internal/modules/cjs/loader:1128:12
8: traceSync (node:diagnostics_channel:315:14)
9: wrapModuleLoad (node:internal/modules/cjs/loader:218:24)
10: executeUserEntryPoint (node:internal/modules/run_main:170:5)

### Additional information

_No response_
Repository: TypeScript
Issue: MIDIMessageEvent data is incorrectly typed
Labels: Bug,Help Wanted,Domain: lib.d.ts

### 🔎 Search Terms

In https://github.com/microsoft/TypeScript/pull/57027 `MIDIMessageEvent.data` was changed from `Uint8Array` to `Uint8Array | null` (see https://github.com/microsoft/TypeScript/pull/57027/files#diff-dc0eab937d15e62545da3ed7b4f40ad6b24f15dd88fbc6ceda2bfb4ed8356eb0L14670). 

According to https://developer.mozilla.org/en-US/docs/Web/API/MIDIMessageEvent/data data the value will always be an Uint8Array.

### 🕗 Version & Regression Information

This changed in #57027 


### ⏯ Playground Link

_No response_

### 💻 Code




### 🙁 Actual behavior

`'event.data' is possibly 'null'.ts(18047)`

### 🙂 Expected behavior

No warning about data property possibly being null.

### Additional information about the issue

_No response_
Repository: react
Issue: [React 19] useOptimistic - Add option to disable rollback
Labels: React 19

## Summary

`useOptimistic` automatically rolls back upon error. Can we make this optional?

Use case: I would like to keep the optimistic data displaying upon error, and display a "Try again" button next to it. (yes, I could do this without useOptimistic, but I suspect this will be a common use case).

Also, the current rollback on error behavior [isn't documented here](https://react.dev/reference/react/useOptimistic), so suggest adding before release.

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->
Repository: godot
Issue: Performance drop in 3D scenes with DirectionalLight in Godot 3.6 compared to 3.5
Labels: bug,topic:rendering,regression,topic:3d,performance

### Tested versions

- Godot 3.5.3
- Godot 3.6

### System information

Linux Ubuntu 22.04, Intel Core 2 Duo 2.8 Ghz, Geforce 9500 GT 3Gb VRAM, 4 Gb RAM 800 Mhz

### Issue description

Performance is considerably worse in Godot 3.6, compared to 3.5

Godot 3.5.3, with 33 FPS:
![Image](https://github.com/user-attachments/assets/ccd9f534-edcf-4dea-bfc7-8df4e8986413)

Same exact scene in Godot 3.6 with 27 FPS:
![Image](https://github.com/user-attachments/assets/208af5b8-22c9-4a17-bb06-24b79ca2bf14)

A drop of 20% in performance can be observed.

### Steps to reproduce

Run a project in Godot 3.5.3, make note of the FPS
Run the same project in Godot 3.6 and observe the drop in performance.

### Minimal reproduction project (MRP)

The truck town demo can be used to attest the performance change.
https://github.com/godotengine/godot-demo-projects/releases/download/3.5-9e68af3/3d_truck_town.zip
Repository: ollama
Issue: Ollama on AMD CPU iGPU Windows Hack
Labels: feature request

Followed this tutorial https://github.com/ollama/ollama/pull/5059 
and got Ollama running on windows on AMD CPU,

any tips on how I get it to use iGPU what commands can i try to hack?

Thanks
Repository: rust
Issue: Tracking Issue for `vec_deque_iter_as_slices`
Labels: T-libs-api,C-tracking-issue

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

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

This is a tracking issue for:

 - `alloc::collections::vec_deque::Iter::as_slices`
 - `alloc::collections::vec_deque::IterMut::into_slices`
 - `alloc::collections::vec_deque::IterMut::as_slices`
 - `alloc::collections::vec_deque::IterMut::as_mut_slices`

<!--
Include a short description of the feature.
-->

Each of these functions obtains a pair of slices from a `VecDeque` iterator, similar to `VecDeque::as_slices`.

### Public API

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

```rust
use std::collections::vec_deque::{Iter, IterMut};

impl<'a, T> Iter<'a, T> {
    pub fn as_slices(&self) -> (&'a [T], &'a [T]) { ... }
}

impl<'a, T> IterMut<'a, T> {
    pub fn into_slices(self) -> (&'a mut [T], &'a mut [T]) { ... }
    pub fn as_slices(&self) -> (&[T], &[T]) { ... }
    pub fn as_mut_slices(&mut self) -> (&mut [T], &mut [T]) { ... }
}
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [x] Implementation: #123947
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilization PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: excalidraw
Issue: Increase text element padding in rectangle
Labels: good first issue,UX/UI

As of now, the text padding inside the rectangle is way too small, so it's often necessary to manually add the spaces to achieve a more pleasant look.

Instead, we shall increase the padding, so that no manual "alignment" is not necessary.

Things to keep in mind:
- it might be a regression -> double-check
- do not create a breaking change for existing diagrams (after a manual redraw, like entering wysiwyg, it's likely fine)
- don't forget about padding while editing (wysiwyg)
- test different sizes & zoom levels

![Image](https://github.com/user-attachments/assets/e98c94a9-a8da-4a0f-ae3c-b3a8347d93de)
Repository: tensorflow
Issue: The documentation in `data_performance.ipynb` uses `py_function()` without an explanation
Labels: type:docs-bug,type:bug

### Issue type

Documentation Bug

### Have you reproduced the bug with TensorFlow Nightly?

Yes

### Source

source

### TensorFlow version

TF 2.18

### Custom code

No

### OS platform and distribution

_No response_

### Mobile device

_No response_

### Python version

_No response_

### Bazel version

_No response_

### GCC/compiler version

_No response_

### CUDA/cuDNN version

_No response_

### GPU model and memory

_No response_

### Current behavior?

In the ["Better performance with the tf.data API" guide](https://www.tensorflow.org/guide/data_performance), `tf.py_function()` is used several times in the mapping function. There are various performance boosts demonstrated by the guide with said mapping functions. However, there does not seem to be any practical reason why `tf.py_function()` is used inside the mapping functions. In fact, if you remove those, the behavior is the same; in other words, there doesn't seem to be a need for them at all.

Curiously, if you remove them from the examples and then perform the time measurements, the speedup goes away. For example, consider the following mapping function from [the guide](https://github.com/tensorflow/docs/blob/bbc0b9c70fc0bd4411793d1b0bcc56ef1dbc2405/site/en/guide/data_performance.ipynb#L447-L450):

```python
def mapped_function(s):
    # Do some hard pre-processing
    tf.py_function(lambda: time.sleep(0.03), [], ())
    return s
```

In the sequential case, it is shown that the following mapping code results in a time measurement of 0.49222556600034295:

```python
benchmark(
    ArtificialDataset()
    .map(mapped_function)
)
```

And, the optimized (parallel) version as follows results in a time measurement of 0.36392719900049997:

```python
benchmark(
    ArtificialDataset()
    .map(
        mapped_function,
        num_parallel_calls=tf.data.AUTOTUNE
    )
)
```

But, if I remove the `tf.py_function()` from the mapping function, I get comparable measurements from both examples, namely, 0.22448736599994845 and 0.2266392660001202:

```python
def mapped_function(s):
    # Do some hard pre-processing
    lambda: time.sleep(0.03), [], ()
    return s
```

In fact, that measurement is even better, which makes me believe that this example is contrived to show a performance benefit by using `num_parallel_calls` when in fact TF is already optimizing the code without it. Frivolously wrapping the function in `tf.py_function()` is most likely  causing TensorFlow *not* to optimize the function. Thus, is `num_parallel_calls` even needed to achieve better performance?

### Standalone code to reproduce the issue

```shell
Mentioned in the above description.
```


### Relevant log output

_No response_
Repository: terminal
Issue: Rendering with tcell under WSL is slow for the first 65s
Labels: Product-Conpty,Issue-Bug,Product-Terminal,Needs-Tag-Fix,Priority-2

### Windows Terminal version

1.23.3231.0

### Windows build number

10.0.26100.0

### Other Software

_No response_

### Steps to reproduce

Under WSL run this: https://github.com/gdamore/tcell/blob/main/_demos/stress.go

### Expected Behavior

_No response_

### Actual Behavior

Initially the application runs super slow. After 65 seconds it suddenly becomes extremely fast (= the expected performance). Here you can see the transition between the two:

https://github.com/user-attachments/assets/765f5cbe-88b2-4c7e-a21c-bbdefb555687
Repository: kubernetes
Issue: Adopting new libraries from cel-go
Labels: sig/api-machinery,kind/feature,triage/accepted

### What would you like to be added?

CEL is general used in Kubernetes now. We wanna keep up with new libraries added into cel-go. cel recently released the [new release](https://github.com/google/cel-go/releases/tag/v0.22.0) which has some feature we love to include in Kubernetes. This issue is to track the adoption of cel-go@0.22.0.

More info: cel introduced versioning for newly added libraries. Kubernetes would love to keep up with supporting the libraries in versions.

### Why is this needed?

/sig api-machinery
/triage accepted