sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ui
Issue: [bug]: Primary colors used in New York style tooltips
Labels: bug

### Describe the bug

Here's the tooltip in NewYork Style:

```
"use client";

import * as React from "react";
import * as TooltipPrimitive from "@radix-ui/react-tooltip";

import { cn } from "@/lib/utils";

const TooltipProvider = TooltipPrimitive.Provider;

const Tooltip = TooltipPrimitive.Root;

const TooltipTrigger = TooltipPrimitive.Trigger;

const TooltipContent = React.forwardRef<
  React.ElementRef<typeof TooltipPrimitive.Content>,
  React.ComponentPropsWithoutRef<typeof TooltipPrimitive.Content>
>(({ className, sideOffset = 4, ...props }, ref) => (
  <TooltipPrimitive.Portal>
    <TooltipPrimitive.Content
      ref={ref}
      sideOffset={sideOffset}
      className={cn(
        "z-50 overflow-hidden rounded-md bg-primary px-3 py-1.5 text-xs text-primary-foreground animate-in fade-in-0 zoom-in-95 data-[state=closed]:animate-out data-[state=closed]:fade-out-0 data-[state=closed]:zoom-out-95 data-[side=bottom]:slide-in-from-top-2 data-[side=left]:slide-in-from-right-2 data-[side=right]:slide-in-from-left-2 data-[side=top]:slide-in-from-bottom-2",
        className
      )}
      {...props}
    />
  </TooltipPrimitive.Portal>
));
TooltipContent.displayName = TooltipPrimitive.Content.displayName;

export { Tooltip, TooltipTrigger, TooltipContent, TooltipProvider };
```

If you notice it uses primary colors. So if I switch the theme to blue or some other colorful theme, the tooltip background also changes to blue which looks pretty odd.

Under default theme it uses popover colors which still looks decent. Am I missing something?

### Affected component/components

tooltip

### How to reproduce

Check the code of tooltip component

### Codesandbox/StackBlitz link

https://ui.shadcn.com/docs/components/tooltip

### Logs

_No response_

### System Info

```bash
Chrome
MacOS
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: TypeScript
Issue: Computed property name is not escaped in declaration emit
Labels: Bug

### 🔎 Search Terms

computed property symbol declaration emit

### 🕗 Version & Regression Information

- This changed between versions 3.7 and 3.8


### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=3.7.5#code/MYGwhgzhAEAq0G8BQ1XQgFzBglsaATgKZgAmA9gHYgCe0A2gEQA6GjAugFzQCulOARx5F0NALYAjciADcSAL5IQRDNAAe0ALyIUaerCasOXaAEYFMoA

### 💻 Code

```ts
class T {
    static readonly ["\t"]: unique symbol;
}
let x = {
    [T["\t"]]: 1
};
```


### 🙁 Actual behavior

The type of `x` is emitted as `{  [T["\t"]]: number; }` in declaration files, making the file invalid since the property does not exist on `T`

### 🙂 Expected behavior

The escape should be preserved in the property name.

### Additional information about the issue

Was introduced by https://github.com/microsoft/TypeScript/pull/18860/commits/8bb7230729f43f1c134f895a535e73c4cd58af3e
Repository: three.js
Issue: Replacing an attribute of a geometry instanced by another new attribute with a superior length break the renderer
Labels: Bug

### Description

On previous version of Three.JS, ( r162 havnt tested between then and now ) ,we were able to replace an entire instancedgeometry attribute with a new length and set the instanceCount to a superior value

This is a valuable feature for performances if you play with huge dynamic instanced geometry that increments count over time and allows to first allocate a smaller buffer then grow with a safe multiple to limit the size of the buffer 

But this also limits flexibility of building geometries by a lot

In both WebGL and WebGPU back end it now breaks the renderer : 


<img width="523" alt="Screenshot 2024-12-19 at 15 02 09" src="https://github.com/user-attachments/assets/450d9260-3e84-41e3-9708-52bdd25a13be" />



Look at the switchArray function 

[Live example](https://jsfiddle.net/ar6kdvzp/)
Repository: deno
Issue: ext/node: Do not expose `fs.promises.fstat`
Labels: bug,node compat

We currently expose `fs.promises.fstat` from `node:fs`, but that doesn't seem an public API of Node https://nodejs.org/api/fs.html

(`fs.promises` namespace generally doesn't expose `f` prefixed APIs)
Repository: flutter
Issue: define `ThemeExtension` outside of material, with static `.of` and an `InheritedWidget` or `InheritedModel`
Labels: c: new feature,c: proposal,P3,team-design,triaged-design,f: theming

### Use case

I am building a design system outside of material. I don't desire to use `MaterialApp` or `Theme` widget to define the UI. I would like the ability to use `ThemeExtension`s without depending on `material`'s `Theme[Data]`.

### Proposal

I would like 
- `ThemeExtension` to be defined and exported from `package:flutter/widgets.dart`
- a new encapsulation of ThemeExtensions in an InheritedWidget or InheritedModel
- a new `.of` static method that "feels" some where between `ThemeData.extension` and in a typical style of `InheritedWidget.of`
- the ability to introduce ThemeExtensions in a `WidgetsApp` (and thus available in `CupertinoApp`) if not in it's own InheritedWidget


example:

```dart
import 'package:flutter/widgets.dart';

void main() {
  return runApp(
    // new: some inherited model or widget for ThemeExtensions
    ThemeExtensions(
      child: WidgetsApp(home: Home(), ...),
      extensions: const [
        MyColor(brandColor: Color(0xFFE53935)),
      ],
    ),
  );
}

class Home extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    // new: lookup my extension MyColor with ".of"
    final myColor = ThemeExtension.of<MyColor>(context);
    return const ColoredBox(color: myColor.brandColor);
  }
}
```

some possibly related issues:
- https://github.com/flutter/flutter/issues/102993
- https://github.com/flutter/flutter/issues/154740
Repository: TypeScript
Issue: Bug: settings in `tsconfig.json#paths` and `package.json#imports` conflicts
Labels: Bug,Help Wanted

### 🔎 Search Terms

"package.json imports path"

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about this issue


### ⏯ Playground Link

_No response_

### 💻 Code

[My repository](https://github.com/KostyaTretyak/package-json-imports-bug) is intended to reproduce a bug that manifests when the following three settings are combined:

1. `"rootDir": "."` in the `tsconfig.json` file, which is required only for VS Code and `eslint.config.mjs`;
2. `paths` in the `tsconfig.json` file creates an alias for the path `#lib/*`, pointing to `./src/*`;
3. `imports` in the `package.json` file creates an alias for the path `#lib/*`, pointing to `./dist/*`.

In such cases, TypeScript suggestions merge content from both the `./dist/*` and `./src/*` directories:

---

![Image](https://github.com/user-attachments/assets/d3846bd0-18a3-48e4-8bbc-7e219145cbd8)

---


### 🙁 Actual behavior

As you can see, `file1.js`, `file2.js`, and `index.js` appear at the same level as the `src` and `test` folders, which is incorrect.

### 🙂 Expected behavior

1. The setting described in point 2 should take higher precedence for TypeScript over the setting in point 3.
2. In any case, the settings in points 2 and 3 should not be merged.

### Additional information about the issue

If in point 1 the setting is changed to `"rootDir": "src"`, the bug disappears. However, in this case, you cannot use `"include": ["test"]` in the `tsconfig.json` file, which is very inconvenient. Instead, it is more practical to use the `"rootDir": "src"` setting in the `tsconfig.build.json` file.
Repository: ui
Issue: [bug]: Can't find use-mobile hook in shadcn doc
Labels: bug

### Describe the bug

Because restricted firewall in my company, I can't use the cli for adding components because it point to external registry, so I'm using manual installation for sidebar component and adding requirement one by one. Until I want add the @/components/hooks/use-mobile but can't find the example

### Affected component/components

Sidebar

### How to reproduce

1. Go to shadcn website
2. Add Sidebar with Manual Installation 

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: flutter
Issue: [espresso] (feature request) doesNotExist assertion for widgets
Labels: c: new feature,platform-android,package,c: proposal,P3,p: espresso,team-android,triaged-android

### Use case

I'm trying to add an Android integration test to one of the packages, I use Espresso for it, like suggested in [Plugin-Tests.md](https://github.com/flutter/flutter/blob/master/docs/ecosystem/testing/Plugin-Tests.md). I need to check if a widget is not rendered on the screen, after that I'll perform an action, and then verify the existence of a widget again (this time it should be visible).

In native Espresso library we can do that with `ViewAssertions.doesNotExist`, but there's no equivalent in Espresso for Flutter - we only have `isExisting` here.

### Proposal

I'd suggest adding another static function (`doesNotExist`) to `FlutterMatchers` class. This function would return a proper matcher that would check if a given Flutter widget exists. If it does, it should throw an exception.

Example code:

```dart
WidgetInteraction playButton = onFlutterWidget(withValueKey("Play"));
playButton.check(matches(doesNotExist()));
```
Repository: vscode
Issue: Support collapsing/expanding notebook cell comments
Labels: feature-request,notebook

<!-- ⚠️⚠️ 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/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: macOS 15.1.1 (24B91)
- OS Version: 1.96.1

Steps to Reproduce:

1. Create a review comment on a notebook cell.
2.  Press the collapse button.

Expected:
Collapses the comment somehow.

Actual:
Nothing happens.

-----

Looks like this was never implemented for notebooks: https://github.com/microsoft/vscode/blob/8467007af3f3dca1e9653a476fba3c5536f8d0cc/src/vs/workbench/contrib/notebook/browser/view/cellParts/cellComments.ts#L74

I guess one challenge in implementing is coming up with a UX for collapsed comments and how to uncollapse them, given there is no line gutter icon which is used on text files for that. Maybe we could have a similar red icon in the bottom margin that also has the language picker on the far right. There is some space there, and it is relatively close to where the comments would be...

What do you think, @rebornix?
Repository: rust
Issue: compiletest: more granular `--nocapture` for `run-make` tests
Labels: T-compiler,T-bootstrap,C-bug,A-compiletest,A-run-make,A-test-infra

>  Would it be possible to add a way to revert back to the old behavior? For cg_clif this makes testing the rustc test suite very verbose. I have to use `--nocapture` to see any test failures in the first place as `panic=abort` means that without it compiletest aborts before it gets a chance to print the test failures, but I would like to not have my terminal getting spammed with the output of all passing tests.

_Originally posted by @bjorn3 in https://github.com/rust-lang/rust/issues/134111#issuecomment-2554625017_
Repository: vscode
Issue: [html] support `goto definition` on built-in symbols inside of `script` 
Labels: help wanted,feature-request,html

<!-- ⚠️⚠️ 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. -->
Version: 1.96.1 (user setup)
Commit: 42b266171e51a016313f47d0c48aca9295b9cbb2
OS: Windows_NT x64 10

Steps to Reproduce:

1. Create new file with `html` type
2. Put code
```html
<!DOCTYPE html>
<html lang="en">

<head>
    <meta charset="UTF-8">
    <meta name="viewport" content="width=device-width, initial-scale=1.0">
    <title>Document</title>
</head>

<body>
    <script>
        const b = new Blob([]);
    </script>
</body>

</html>
```
3. Press `ctrl` and hover cursor over `Blob` to see underline to go to definition
4. No underline below `Blob` and click on it doesnt do anything
Repository: TypeScript
Issue: if-statements allow multiple arguments and don't check for constant conditions after the first argument
Labels: Suggestion,Awaiting More Feedback

### 🔎 Search Terms

"if statement", "constant condition"

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about common bugs


### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/MYewdgzgLgBBIFsCmBhAFk4BrAlmA5gGICuYwUO4MAvDABQAOAhgE5MICMAXHFC3vgA0MZmwQAmHtH4FhIBhXBMANgAVW7AMw0YfYkgCUNAHwwA3gCgY1mAHpbMACYhexAGZurNlkijEWYLos+gDcFgC+Fhb2MCoA7kwAnhAwbioQSMI+EMTKsCBucIioGNgCJGSKgfFJKTj4YCA+jhY4bnTwyOiYuAQV5JRgdABEouwcw8KjGhLDBsJpyhlGljYwEVExjkgMSGDbYPmB2bn5hZ0lPeWkA+Ct7RfdZX03VSNjnJMw02LiX4vLFZeawRIA

### 💻 Code

```ts
const someCheckingFunction = (param1: string, param2: string, optionalParam3 = true) => {
    // do stuff
    return true;
}

// always false, result of someCheckingFunction always ignored
if(someCheckingFunction("param1", "param2"), false) {
    
}

// dependent on result of someCheckingFunction
if(someCheckingFunction("param1", "param2", false)) {
    
}
```


### 🙁 Actual behavior

Due to a mistake in my bracket placement as seen in the example, I accidentally learned that multiple arguments in an if statement are possible.

Currently that means:
1. only the last argument is used for the if statement check
2. even for constant conditions there is not error visible

### 🙂 Expected behavior

What I would expect:
1. don't allow multiple arguments, this only happens because someone made an error
2. at least show an error if there is a constant condition

### Additional information about the issue

_No response_
Repository: pytorch
Issue: [CI] XPU linux ci test has flaky error with sccache service
Labels: module: ci,triaged,module: infra,intel

Noticed that there are some torch xpu ci test failure with sccache caused by the S3 token permission expired, refer https://github.com/pytorch/pytorch/actions/runs/12374649660/job/34540161843#step:14:3461

```
sccache: error: Server startup failed: cache storage failed to read: Unexpected (permanent) at read => S3Error { code: "ExpiredToken", message: "The provided token has expired.", resource: "", request_id: "NMJ4H2V91GQ7S2BZ" }
```
The workflow is https://github.com/pytorch/pytorch/blob/main/.github/workflows/_xpu-test.yml runs on self-hosted runner `linux.idc.xpu` with docker containers

cc @seemethere @malfet @pytorch/pytorch-dev-infra @jgong5 @mingfeima @XiaobingSuper @sanchitintel @ashokei @jingxu10
Repository: vscode
Issue: Automatically adjust minimap scale according to display scale
Labels: bug,editor-minimap,under-discussion

<!-- ⚠️⚠️ 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. -->

I have a 27" 4K monitor as my main display and a 24" 1080p monitor as a secondary display. To make everything have consistent sizes between the two displays, I have set my main display to 175% scale. The majority of VS Code scales accordingly, but the minimap does not, which results in it being very small and difficult to use. I can change `editor.minimap.scale` to 2 to account for this on my main display, but then if I move a window over to my secondary display, the minimap is far too large.

I would like the minimap to automatically account for display scaling (or have a way to set a different scale per display) such that it is a consistent size on my two displays. This may require supporting non-integer scales (#84168), or it could round to the nearest integer (which may not be ideal for 150% scale).
Repository: flutter
Issue: [go_router] Support for Handling Action-Based Deep Links Without Navigation
Labels: c: new feature,package,c: proposal,P2,p: go_router,team-go_router,triaged-go_router

### Use case

**Problem**  
The `go_router` package provides a great mechanism for handling deep links through the `redirect` callback. However, there are scenarios where a deep link should trigger an action (e.g., saving a referral code, showing a snack bar) without navigating to any route or modifying the current screen.

Currently, the `redirect` function requires returning either `null` (to proceed to the intended route) or another string (to redirect to a different route). There is no clean way to "do nothing" while still handling the deep link logic.

**Use Case**  
An example is a referral link (`/referral?code=XYZ123`) that should:

1. Save the referral code locally.
2. Show a snack bar confirming the referral code was saved.
3. Prevent navigation, keeping the user on their current screen.

### Proposal

1. Introduce a separate `onDeepLink` callback that is triggered for every incoming deep link. This callback could be used to handle action-based links independently of routing.

   ```dart
   GoRouter(
     onDeepLink: (context, state) {
       if (state.uri.path == '/referral') {
         // Perform the action here
         return true; // Handled successfully
       }
       return false; // Continue with routing
     },
     // Other configurations...
   );
   ```

2. Provide a mechanism to block/prevent navigation dynamically based on deep link conditions.
   ```dart
   redirect: (context, state) {
     if (state.host.isNotEmpty && state.uri.path == '/referral') {
       // Perform the action and block navigation
     }
     return null;
   }
   ```
Repository: angular
Issue: output-migration Removes types from output
Labels: core: inputs / outputs,area: migrations

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

core

### Is this a regression?

No

### Description

When running a migration `ng generate @angular/core:output-migration`

My @outputs when migrating to output lose the type causing errors everywhere.

![Image](https://github.com/user-attachments/assets/47caa339-7178-44f0-a313-2b3f8c005554)

Instead of turning this
`@Output() EventMoveMovimientos: EventEmitter<resupuesta> = new EventEmitter();`
into
`readonly EventMoveMovimientos = output();`
 
It should be into this
`readonly EventMoveMovimientos = output<resupuesta>();`


By the way the event emit is this:
```
this.EventMoveMovimientos.emit({
  idInstrumento: nemo.idNemotecnico,
  idCuenta: nemo.idCuenta,
});
```

And the interface is this:
```
export interface resupuesta {
  idInstrumento: number;
  idCuenta: number;
}
```


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

_No response_

### Please provide the exception or error you saw

```true
X [ERROR] TS2345: Argument of type '{ idInstrumento: any; idCuenta: any; }' is not assignable to parameter of type 'void'. [plugin angular-compiler]

    src/app/modules/shared-module/tabla-instrumento/forward/forward.component.ts:97:35:
      97 │     this.EventMoveMovimientos.emit({
         ╵                                    ^
```

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

```true
_                      _                 ____ _     ___
    / \   _ __   __ _ _   _| | __ _ _ __     / ___| |   |_ _|
   / △ \ | '_ \ / _` | | | | |/ _` | '__|   | |   | |    | |
  / ___ \| | | | (_| | |_| | | (_| | |      | |___| |___ | |
 /_/   \_\_| |_|\__, |\__,_|_|\__,_|_|       \____|_____|___|
                |___/
    

Angular CLI: 19.0.6
Node: 20.13.1
Package Manager: npm 10.5.2
OS: win32 x64

Angular: 19.0.5
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... platform-server, router, service-worker

Package                         Version
---------------------------------------------------------
@angular-devkit/architect       0.1900.6
@angular-devkit/build-angular   19.0.6
@angular-devkit/core            19.0.6 (cli-only)
@angular-devkit/schematics      19.0.6
@angular/cdk                    19.0.4
@angular/cli                    19.0.6
@angular/flex-layout            15.0.0-beta.42
@angular/material               19.0.4
@schematics/angular             19.0.6
rxjs                            7.8.1
typescript                      5.5.3
zone.js                         0.15.0
```

### Anything else?

_No response_
Repository: vscode
Issue: theme-color is not updated when the PWA is inactive.
Labels: bug,titlebar,confirmed,web

- VS Code Version: 1.97.0-insider
- OS Version: PWA (Mac OS, but should apply to all)

Steps to Reproduce:

1. Set the colour `titleBar.inactiveBackground` to something significantly different to the `activeBackground` to easily distinguish the focused app.
2. Focus on any other app.

![Image](https://github.com/user-attachments/assets/77590a3f-b277-4fc2-bfe4-13d7258e58a8)

Notice that even when the PWA is inactive, it still takes the theme-color from the active titlebar background.

https://github.com/microsoft/vscode/blob/main/src/vs/workbench/browser/style.ts#L27-L41

I think that ideally the theme-color would match the titlebar colour, regardless of whether the app is active or not.
Repository: transformers
Issue: [`Mamba2`] Varlen implementation
Labels: Feature request

### Feature request

Use varlen implementations (cu_seq_lens) of mamba2 and conv1d when requirements are met, i.e. mostly version dependencies.

### Motivation

It's similar to how fa2 works with varlen and it should boost performance while guaranteeing correct performance on batches.

### Your contribution

I can make a PR, not sure when I'll get to it - prolly after xmas days.