sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ui
Issue: [bug]: Tooltip on Themes page doesn't inherit theme
Labels: bug

### Describe the bug

On the Themes page:

https://ui.shadcn.com/themes

When hovering over the new message button in the ChatDemo, the Tooltip portals in on the body, which is outside the .theme-red selector so the tooltip doesn't inherit the theme.

I think one potential solution could be to change the tooltip.tsx component to portal the tooltip content in relative to the tooltip root vs. on document.body.

### Affected component/components

Documentation, Tooltip

### How to reproduce

1.  Go to https://ui.shadcn.com/themes
2. Hover on new message button in ChatDemo
3. Notice tooltip is black, when it should be red if the red theme is selected.

### Codesandbox/StackBlitz link

https://ui.shadcn.com/themes

### Logs

_No response_

### System Info

```bash
Mac, Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: PowerToys
Issue: Cannot launch UI elements: faulting module Microsoft.UI.Xaml.dll
Labels: Issue-Bug,Resolution-Fix Committed

### Microsoft PowerToys version

0.86.0

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

General, Settings, Advanced Paste, PowerToys Run

### Steps to reproduce

Installed 0.86.0 (machine-wide) from GitHub on W11 23H2 22631 (multiple machines), both manually and through SCCM.

I get the following error when trying to launch any UI part of PowerToys:

```
Faulting application name: PowerToys.PowerLauncher.exe, version: 0.86.0.0, time stamp: 0x66e80000
Faulting module name: KERNELBASE.dll, version: 10.0.22621.4391, time stamp: 0x7433a115
Exception code: 0xe0434352
Fault offset: 0x000000000005fa4c
Faulting process ID: 0x0xbb0
Faulting application start time: 0x0x1db3b83c903a38c
Faulting application path: C:\Program Files\PowerToys\PowerToys.PowerLauncher.exe
Faulting module path: C:\WINDOWS\System32\KERNELBASE.dll
```

```
Faulting application name: PowerToys.Settings.exe, version: 0.86.0.0, time stamp: 0x66e80000
Faulting module name: Microsoft.UI.Xaml.dll, version: 3.1.6.0, time stamp: 0x0caad657
Exception code: 0xc000027b
Fault offset: 0x0000000000009125
Faulting process ID: 0x0xf24
Faulting application start time: 0x0x1db3b83caefa763
Faulting application path: C:\Program Files\PowerToys\WinUI3Apps\PowerToys.Settings.exe
Faulting module path: C:\Program Files\PowerToys\WinUI3Apps\Microsoft.UI.Xaml.dll
```

```
Faulting application name: PowerToys.Peek.UI.exe, version: 0.86.0.0, time stamp: 0x66e80000
Faulting module name: Microsoft.UI.Xaml.dll, version: 3.1.6.0, time stamp: 0x0caad657
Exception code: 0xc000027b
Fault offset: 0x0000000000009125
Faulting process ID: 0x0x1b20
Faulting application start time: 0x0x1db3b84ec20d9a2
Faulting application path: C:\Program Files\PowerToys\WinUI3Apps\PowerToys.Peek.UI.exe
Faulting module path: C:\Program Files\PowerToys\WinUI3Apps\Microsoft.UI.Xaml.dll
```

---

Trying to generate a debug report results in (likely because diagnostics is disabled through GPO):

```
Application: PowerToys.PowerLauncher.exe
CoreCLR Version: 8.0.1024.46610
.NET Version: 8.0.10
Description: The process was terminated due to an unhandled exception.
Exception Info: System.InvalidCastException: Unable to cast object of type 'System.Byte[]' to type 'System.Int32'.
   at Microsoft.PowerToys.Telemetry.DataDiagnosticsSettings.GetEnabledValue()
   at Microsoft.PowerToys.Telemetry.ETWTrace..ctor()
   at PowerLauncher.App..ctor()
   at PowerLauncher.App.Main()
```

### ✔️ Expected Behavior

Any UI element of PowerToys opens as expected.

### ❌ Actual Behavior

Nothing opens (the icon is visible in the system tray), and occasionally, the system hangs (especially when trying to do something with advanced paste).

Interestingly, Always On Top works perfectly. Running the application as an administrator also works perfectly (no GPO enforced).


### Other Software

_No response_
Repository: react
Issue: [React 19] Regression when using `createPortal` with DOM element created by `dangerouslySetInnerHTML`
Labels: React 19

In React 18, it was possible to use `createPortal` with a DOM element created by `dangerouslySetInnerHTML`.

Example (adapted from [this Stack Overflow answer](https://stackoverflow.com/questions/62300569/add-react-component-in-html-set-by-dangerouslysetinnerhtml/77099814#77099814)):

```tsx
import { useCallback, useState } from "react";
import { createPortal } from "react-dom";

export default function App() {
  const htmlFromElsewhere = `foo <span class="portal-container"></span> bar`;

  return <InnerHtmlWithPortals html={htmlFromElsewhere} />
}

function InnerHtmlWithPortals({ html }: { html: string }) {
  const [portalContainer, setPortalContainer] = useState<Element | null>(null)

  const refCallback = useCallback((el: HTMLDivElement) => {
    setPortalContainer(el?.querySelector(".portal-container"))
  })

  return <>
    <div ref={refCallback} dangerouslySetInnerHTML={{ __html: html }} />
    {portalContainer && createPortal(<Cake />, portalContainer)}
  </>
}

function Cake() {
  return <strong>cake</strong>
}
```

React 18 CodeSandbox: https://codesandbox.io/p/sandbox/optimistic-kowalevski-73sk5w

In React 19, this no longer works.  React appears to be re-rendering the inner HTML after calling `refCallback`.  Thus, `createPortal` succeeds, but the `portalContainer` element that it uses is no longer part of the DOM.

React 19 CodeSandbox: https://codesandbox.io/p/sandbox/vibrant-cloud-gd8yzr

It is possible to work around the issue by setting `innerHTML` directly instead of using `dangerouslySetInnerHTML`:

```diff
   const [portalContainer, setPortalContainer] = useState<Element | null>(null)

   const refCallback = useCallback((el: HTMLDivElement) => {
+    if (el) el.innerHTML = html
     setPortalContainer(el?.querySelector(".portal-container"))
-  })
+  }, [html])

   return <>
-    <div ref={refCallback} dangerouslySetInnerHTML={{ __html: html }} />
+    <div ref={refCallback} />
     {portalContainer && createPortal(<Cake />, portalContainer)}
   </>
```

But I'm not sure whether that is a reliable solution.
Repository: go
Issue: proposal: hash: standardize the hash function
Labels: Proposal

**Background**: Issue https://github.com/golang/go/issues/69420 proposes a `types.Hash` function that provides a hash operator for `types.Type` values that is consistent with the equivalence relation for types defined by `types.Identical`. The only real question in that proposal is: what is to be Go's future convention for the signature of a custom hash function?

The naive answer is `func(T) uint64`, where T stands for `types.Type`. However, hash tables with only a single hash function are vulnerable to a "hash flooding" denial-of-service attack, in which an adversary provides many inputs that all hash to the same value, causing the table to degenerate into a linked list. The defense is for each process (or particular hash table) to select a different hash function at random so that the values cannot be predicted. The `hash/maphash` package embodies this approach: a random Seed value determines the hash functions (`Hash.Strings` and `Hash.Bytes`), which depend on the seed's opaque random value. (maphash does not provide a Seed-dependent way to hash integers.)

So, perhaps custom hash functions should accept a `maphash.Seed` parameter. And perhaps Seed should also provide methods for hashing integers.

**Proposal:** In the hash package, define function types HashFunc and EqFunc that document the conventions for Go hash tables.

Here is the minimal answer, without Seeds:

```go
package hash

// HashFunc defines a hash function for values of type T.
// A conformant HashFunc and EqFunc pair (hash, eq) must observe the invariant
// that eq(x, y) => hash(x) == hash(y).
type HashFunc[T any] func(T) uint64

// EqFunc defines an equivalence relation for values of type T.
type EqFunc[T any] func(x, y T) bool
```

@ianlancetaylor @griesemer
Repository: pytorch
Issue: Dynamo should reorder warnings (and other logging) by default if they don't involve tensor values
Labels: triaged,oncall: pt2,module: dynamo,empathy-day

The thing I ran into is https://gist.github.com/zou3519/4c45db951c17845a598f4e9d9f433ba9 (instancenorm warns if an input looks wrong). One can also run into this via deprecation warnings.

cc @voznesenskym @penguinwu @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @chauhang @amjames
Repository: rust
Issue: Tracking Issue for OsString::truncate
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(os_string_truncate)]`

This is a tracking issue for the 

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

### 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
// std::ffi::os_str

impl OsString {
    pub fn truncate(&mut self, new_len: usize);
}
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->
- [x] ACP Approved: https://github.com/rust-lang/libs-team/issues/486
- [ ] Implementation:
- [ ] 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: flutter
Issue: Revisit inline vs out-of-line implementations of methods in Impeller geometry classes
Labels: engine,P3,e: impeller,team-engine,triaged-engine

Currently many of the Impeller geometry classes are templates and so they must implement all of their methods inline, but some of them (for instance `Matrix`) are regular classes and so the methods could be implemented in their associated `.cc` file. We've been shifting the code to more cases of moving implementations to the `.cc` file and so we should revisit the various geometry classes to determine what's best for them.
Repository: next.js
Issue: URL's search params get encoded on page load.
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://github.com/wkd-kapsule/next-router-demo

### To Reproduce

1. Go to the [production site.](https://next-router-demo-eight.vercel.app/)
2. Use a special character in the URL's search params, such as `/`. Whether by directly typing it or clicking the button on the page.
3. Watch the URL being encoded before your eyes as the page loads.


### Current vs. Expected behavior

### **_Current behavior:_** 
Directly typing a url or using `useRouter` will encode the URL's search params after page loading.

### **_Expected behavior:_** 
I'd like to be able to use characters such as `/` or `$` in a URL's search params.

### **_Context:_**
 I use URL seach params to store some state in my app. The thing is that it's a path, thus containing `/`. In dev mode, everything is fine but somehow in production, `/` gets encoded into `%2F` once the page has loaded. It does it whether I directly type the url and press Enter or click on button with `useRouter().push`.

I've reproduced this in a minimal repo but for some reason it works fine when using `useRouter().push`. The URL gets encoded only when you manually type it and press Enter. There is basically no difference in the way I use `useRouter().push()` in this repo and in my app, I can't grasp why both behaves differently.

**NOTE: I know that I can just decode it to get the original character but my issue is more visual than technical. Having encoded characters could discourage the users of my app to use the URL to navigate. Whereas this is exactly why I put that path in the URL, so the user can directly go where they need, without having to use the interface.**

Here's the [demo](https://next-router-demo-eight.vercel.app/)

https://github.com/user-attachments/assets/4d63d9d5-f00f-4c84-b6ef-19600627b2b3

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home
  Available memory (MB): 16272
  Available CPU cores: 8
Binaries:
  Node: 20.13.1
  npm: 10.8.1
  Yarn: N/A
  pnpm: 8.15.5
Relevant Packages:
  next: 15.0.4-canary.19 // There is a newer canary version (15.0.4-canary.20) available, please upgrade!
  eslint-config-next: 15.0.3
  react: 19.0.0-rc-69d4b800-20241021
  react-dom: 19.0.0-rc-69d4b800-20241021
  typescript: 5.6.2
Next.js Config:
  output: N/A
```


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

Navigation

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

Vercel (Deployed)

### Additional context

I couldn't pin which Next.js versions first caused the issue because it actually occured a while ago. I didn't report it at the time as being constantly on the latest canary version, I just imagined it would eventually get solved. Now that's been several months already so I thought I better report it.

Nonetheless, I can tell you that I'm using Google Chrome and that everything works as expected in Microsoft Edge.
Repository: ollama
Issue: Request: Nexa AI Omnivision
Labels: model request

Here is the link to Nexa AI's model. (I haven't checked over it to make sure it's super reputable though)
https://huggingface.co/NexaAIDev/omnivision-968M
Repository: ant-design
Issue: `RangePicker` breaks when using with date-fns via `dateFnsGenerateConfig`
Labels: help wanted,Inactive

### Reproduction link

[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/p/sandbox/datepicker-rangepicker-antd-v5-hr2rr9?file=%2Findex.tsx)

### Steps to reproduce

- Setup Antd DatePicker to use date-fns according the [official guide](https://ant.design/docs/react/use-custom-date-library#use-date-fns);
- Renders `RangePicker` using `format`, `picker` containing `"time"` value and `use12Hours` props;
- Click on the RangePicker to input values.

### What is expected?

The RangePicker should show the dropdown with the options so we can select a time range.

### What is actually happening?

The entire app breaks with an error "Format string contains an unescaped latin alphabet character `A`"

| Environment | Info |
| --- | --- |
| antd | 5.22.1 |
| React | ^18.0.0 |
| System | macOS Sequoia Version 15.0 (24A335) |
| Browser | Google Chrome Version 131.0.6778.86 |

---
I walked through the previous versions to find when this starts to break and I found the `v5.18.3` working but if we upgrade to `v5.19.0` or earlier, the error starts to happen.

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: ui
Issue: [bug]: GitHub link in site header is only clickable on icon
Labels: bug

### Describe the bug

The GitHub link in the site header is only clickable on the icon, if the button is clicked outside of the icon, the link doesn't work.

This is solved by using asChild as documented in https://ui.shadcn.com/docs/components/button

### Affected component/components

Button, Link

### How to reproduce

1. Go to https://ui.shadcn.com/
2. Click on the GitHub link in the site header, clicking outside of the icon
3. Doesn't work

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Any system
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: flutter
Issue: Removing the `Key` class
Labels: c: API break,a: first hour,c: tech-debt,design doc,:scroll:

### Document Link

[flutter.dev/go/unwrapping-widget-keys](https://docs.google.com/document/d/1Fc9ZYTTxlJUAfGeQzf83wXuV-wSiRZFHhMgwoUNukhI)

### What problem are you solving?

This is an effort to make widgets less complicated and more performant.
Repository: neovim
Issue: Windows WSL: osc52 data with CRLF lines gets Chinese chars
Labels: bug,platform:windows,clipboard,needs:repro,platform:wsl

### Problem

osc52 works for one line only. More than one line means bug (random chinese character etc.)

### Steps to reproduce

nvim --clean -u minimal.lua
write

deed
de

select previous text
press "y"
your clipboard now is chinese
敤摥搀e
note on my full config (not just the minimal.lua) copying a selection always copy only the first line instead of becoming chinese clipboard.
Also copying one line only always works flawlessly

minimal.lua
```lua
  vim.g.clipboard = {
    name = 'OSC 52',
    copy = {
      ['+'] = require('vim.ui.clipboard.osc52').copy('+'),
      ['*'] = require('vim.ui.clipboard.osc52').copy('*'),
    },
    paste = {
      ['+'] = require('vim.ui.clipboard.osc52').paste('+'),
      ['*'] = require('vim.ui.clipboard.osc52').paste('*'),
    },
  }
vim.cmd("set clipboard=unnamedplus")
```


### Expected behavior

Not chinese characters

### Nvim version (nvim -v)

0.10.2

### Vim (not Nvim) behaves the same?

vim no osc52 native AFAIK

### Operating system/version

windows wsl ubuntu

### Terminal name/version

windows terminal

### $TERM environment variable

on ssh xterm-256color

### Installation

appimage 0.10.2 github
Repository: node
Issue: Support `concurrency` when `--experimental-test-isolation` is set to `'none'`
Labels: feature request,test_runner

### What is the problem this feature will solve?

It would be nice to be able to run multiple "workers" when using the `none` test isolation mode.

Today, according to the docs, when `--experimental-test-isolation` is set to `'none'`, it implies 1 concurrency: https://github.com/nodejs/node/blob/f270462c09ddfd770291a7c8a2cd204b2c63d730/doc/api/cli.md#L2252-L2264

However, `mocha` another test runner that does not isolate tests, does accept a concurrency flag: https://mochajs.org/#parallel-tests

### What is the feature you are proposing to solve the problem?

We're looking to move off of `jest` because its test module isolation is extremely slow. We love the idea of using the node-native test runner with isolation disabled, instead of adopting another third-party framework like `mocha`.

However, we'd need to write some custom code (e.g., using [`parallel`](https://www.gnu.org/software/parallel/)) to spin up `n` concurrent, isolation-disabled tests to effectively utilize all the cores available on our CI machine.

The docs and other recent comments all indicate that when `--experimental-test-isolation` is set to `'none'`, concurrency must be `1`. However, I couldn't find the reasoning in [the original PR](https://github.com/nodejs/node/pull/53927) or [issue](https://github.com/nodejs/node/issues/51548).

There's probably a good reason for this but, as someone not intimately familiar with the implementation, it's not obvious to me why we wouldn't be able to run non-isolated tests concurrently, like in `mocha`.

### What alternatives have you considered?

I could probably use a tool like [`parallel`](https://www.gnu.org/software/parallel/) to spin up multiple calls to `node --test`. However, this would require me to also write code to split up all the test files between the parallel runs, etc.
Repository: pytorch
Issue: cudagraph_trees error message suggestion doesn't always work
Labels: triaged,module: cuda graphs,oncall: pt2,module: inductor,empathy-day

This came from running a user empathy model. Repro is:
```
import torch

class Mod(torch.nn.Module):
    def __init__(self):
        super().__init__()

    def forward(self, x):
        out = x * 2
        if not hasattr(self, "t"):
            self.t = torch.arange(x.shape[1], device='cuda')[None, None]
        elif self.t.shape[-1] < x.shape[1]:
            self.t = torch.arange(x.shape[1], device='cuda')[None, None]
        else:
            self.t = self.t[..., :x.shape[1]]
        return out

m = Mod()
m = torch.compile(m, mode='reduce-overhead')

x = torch.randn(8, 8, device='cuda')
with torch.no_grad():
    torch.compiler.cudagraph_mark_step_begin()
    m(x)
    torch.compiler.cudagraph_mark_step_begin()
    m(x)
    torch.compiler.cudagraph_mark_step_begin()
    m(x)
```

This gives the error:
```
  File "/home/hirsheybar/.conda/envs/pytorch_nightly/lib/python3.11/site-packages/torch/_inductor/cudagraph_trees.py", line 628, in get_non_cudagraph_inps
    and t.untyped_storage().data_ptr() not in existing_path_data_ptrs
        ^^^^^^^^^^^^^^^^^^^
RuntimeError: Error: accessing tensor output of CUDAGraphs that has been overwritten by a subsequent run. Stack trace: File "/data/users/hirsheybar/nightly/evo/tmp2.py", line 10, in forward
    self.t = torch.arange(x.shape[1], device='cuda')[None, None]. To prevent overwriting, clone the tensor outside of torch.compile() or call torch.compiler.cudagraph_mark_step_begin() before each model invocation.
```

cc @mcarilli @ezyang @eellison @penguinwu @chauhang @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire @aakhundov
Repository: excalidraw
Issue: [Feature Request] - Add a document to the canvas
Labels: enhancement

I think a very good addition to Excalidraw would be to add a "Document" feature.

Either the way Whimsical does it, where you can create documents separated from canvas, or the way Eraser does it, with a document attached to the canvas itself.