sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: ui
Issue: [bug]: `globals.css` contains default NextJS CSS variables that interfere with the theme
Labels: bug

### Describe the bug

**Issue:** After running `npx shadcn@latest init -d`, the resulting `globals.css` contains both the default NextJS setup as well as the themed css variables. These variables overlap and cause issues with the tailwind setup created via the shadcn command.

As a concrete example, the `tailwind.config.ts` background looks like this: `background: "hsl(var(--background))"` (note that it expects `--background` to be a hsl value. The problem is that the default NextJS setup uses hex for the themed colors. These override the ones specified by the shadcn theme and effectively corrupt the theme. The resulting style given to the browser looks like:
```css
.bg-background {
    background-color: hsl(#ffffff);
}
```

Note that it is trying to use a hex value as an hsl value.

Since the value passed to the browser is not valid, it renders the background color as transparent which messes with all of the components that rely on this background theming (read: practically all of them).

I noticed this initially on the slider component as the thumb was entirely transparent.

**Expected:** The resulting `globals.css` file should not contain the default NextJS setup.

**Workaround:** If others face this issue and notice that their components look a little funny, simply remove the default NextJS theming (first `:root` block through to the first `@layer utilities` block

See the first part of the resulting `globals.css` file below:

```css
@tailwind base;
@tailwind components;
@tailwind utilities;

:root {
  --background: #ffffff;
  --foreground: #171717;
}

@media (prefers-color-scheme: dark) {
  :root {
    --background: #0a0a0a;
    --foreground: #ededed;
  }
}

body {
  color: var(--foreground);
  background: var(--background);
  font-family: Arial, Helvetica, sans-serif;
}

@layer utilities {
  .text-balance {
    text-wrap: balance;
  }
}


@layer base {
  :root {
    --background: 0 0% 100%;
    --foreground: 0 0% 3.9%;
    
...
```

### Affected component/components

All

### How to reproduce

1. Run `npx shadcn@latest init -d`
2. Install slider `npx shadcn@latest add slider`
3. Add slider to component and observe transparent slider thumb.

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Shadcn: 2.0.6
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: transformers
Issue: Clarify what kwargs can be accepted by "AutoModelForCausalLM.from_pretrained()" 
Labels: Feature request

### Feature request

i saw in the doc saying:If a configuration is not provided, kwargs will be first passed to the configuration class initialization function ([from_pretrained()](https://huggingface.co/docs/transformers/main/en/main_classes/configuration#transformers.PretrainedConfig.from_pretrained)). Each key of kwargs that corresponds to a configuration attribute will be used to override said attribute with the supplied kwargs value. Remaining keys that do not correspond to any configuration attribute will be passed to the underlying model’s __init__ function.

but I can't seem to find the __init__(I found 3 lines with __init__, but no useful info). 

I saw some one added "use_cache:Ture" but don't know how this got handled and set,maybe it's discarded. 

### Motivation

i checked the doc and source code but still confused. 

### Your contribution

I'll keep looking
Repository: kubernetes
Issue: Possible dereferencing a nil pointer in pkg/registry/generic/registry/store.go
Labels: sig/api-machinery,triage/accepted

Hello, colleagues!
After having been compared to a _nil value_ at store.go:1398,1402,1408, pointer 'options' is dereferenced at store.go:1412.
https://github.com/kubernetes/kubernetes/blob/f0f7ff989a948389247e628c4c5a43e915f51daa/staging/src/k8s.io/apiserver/pkg/registry/generic/registry/store.go#L1398

https://github.com/kubernetes/kubernetes/blob/f0f7ff989a948389247e628c4c5a43e915f51daa/staging/src/k8s.io/apiserver/pkg/registry/generic/registry/store.go#L1402

https://github.com/kubernetes/kubernetes/blob/f0f7ff989a948389247e628c4c5a43e915f51daa/staging/src/k8s.io/apiserver/pkg/registry/generic/registry/store.go#L1408

It seems you've just missed add a "nill-deref check" here when make this [commit](https://github.com/kubernetes/kubernetes/commit/e1537fc41b9eecb0e5026bfc72b27e4a07d771ba).

https://github.com/kubernetes/kubernetes/blob/f0f7ff989a948389247e628c4c5a43e915f51daa/staging/src/k8s.io/apiserver/pkg/registry/generic/registry/store.go#L1412-L1412

Found by Linux Verification Center (portal.linuxtesting.ru) with SVACE.

Author E. Bykhanova ([e.bykhanova@fobos-nt.ru](mailto:e.bykhanova@fobos-nt.ru)).
Repository: pytorch
Issue: torch._dynamo.exc.Unsupported: builtin: bool [<class 'torch._dynamo.variables.tensor.SymNodeVariable'>] False
Labels: good first issue,triaged,oncall: pt2,module: dynamic shapes,module: dynamo

### 🐛 Describe the bug

```
import torch
from torch.export import export
import torch._functorch.config

class Foo(torch.nn.Module):
    def forward(self, x):
        return bool(x.eq(0.1).any().item())

model = Foo()
inputs = (torch.randn(64),)
with torch._functorch.config.patch(fake_tensor_propagate_real_tensors=True):
    ep = export(model, inputs, strict=True)
```

WAR is to convert to int first before bool lol. Maybe it shouldn't spec though...

### Versions

main

cc @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @chenyang78 @kadeng @chauhang @amjames @rec
Repository: ant-design
Issue: Tabs控件依赖的resize-observer-polyfill里面有一个动态代码执行 导致NextJS 14编译npm run build报告动态代码执行错误  Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime
Labels: Inactive,🧶 Low Priority

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/antd-reproduce-5x-1iybka?file=demo.tsx)

### Steps to reproduce

  /*

  Antd的Tabs空间依赖的resize-observer-polyfill的文件
  node_modules\resize-observer-polyfill\dist\ResizeObserver.es.js

  里面有一段动态执行的代码，导致nextjs npm run build 报错

  报错信息如下：
  ./node_modules\resize-observer-polyfill\dist\ResizeObserver.es.js
Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime
Learn More: https://nextjs.org/docs/messages/edge-dynamic-code-evaluation  


那个ResizeObserver.es.js文件出错的地方在这里

var global$1 = (function () {
    if (typeof global !== 'undefined' && global.Math === Math) {
        return global;
    }
    if (typeof self !== 'undefined' && self.Math === Math) {
        return self;
    }
    if (typeof window !== 'undefined' && window.Math === Math) {
        return window;
    }
    // eslint-disable-next-line no-new-func
    return Function('return this')();  <----- 【【【【【这个出错】】】】】
})();

  */

### What is expected?

nextjs越来越火，应该兼容nextjs

### What is actually happening?

nextjs越来越火，应该兼容nextjs

| Environment | Info |
| --- | --- |
| antd | 5.20.5 |
| React | 18 |
| System | nodejs 20 |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: rust
Issue: Tracking Issue for `abort_unwind`
Labels: T-libs-api,C-tracking-issue

Feature gate: `#![feature(abort_unwind)]`

This is a tracking issue for `core::panic::abort_unwind`.

`abort_unwind` is similar to `catch_unwind`, except that it aborts the process if it unwinds instead of catching the unwind. Prior to the abort, the panic hook is called in the same way that it is for other functions that cannot unwind (e.g. `extern "C" fn`).

### Public API

```rust
// in core::panic (and std::panic)

fn abort_unwind<F: FnOnce() -> R, R>(f: F) -> R;
```

### 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: https://github.com/rust-lang/libs-team/issues/441
- [x] Implementation: https://github.com/rust-lang/rust/pull/130339
- [ ] Final naming (`abort_on_unwind`)?
- [ ] Improve documentation (add example)?
- [ ] Expose a better `fn abort() -> !` in `core`?
- [ ] 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: deno
Issue: TypeError: Failed to execute 'writeBuffer' on 'GPUQueue': Argument 3 is a view on a SharedArrayBuffer, which is not allowed
Labels: bug,webgpu

Version: Deno 1.46.3

in [spce](https://www.w3.org/TR/webgpu/#dom-gpuqueue-writebuffer) ,  it should be ok to use sharedArrayBuffer in device.queue.writeBuffer.

## Reproduce

main.ts:
```ts
const worker = new Worker(import.meta.resolve("./worker.ts"), {
  type: "module",
});
worker.postMessage({ buffer: new SharedArrayBuffer(64) });

```
worker.ts:
```ts
const adapter = await navigator.gpu.requestAdapter();
const device = await adapter!.requestDevice();

const gpuBuffer = device.createBuffer({
  size: 32,
  usage: GPUBufferUsage.STORAGE | GPUBufferUsage.COPY_SRC,
});

self.addEventListener("message", (event) => {
  const data = (event as any).data;
  const view = new DataView(data.buffer);
  device.queue.writeBuffer(gpuBuffer, 0, view, 0, 4);
});

```
run `deno run --unstable-webgpu main.ts` then get error:

<img width="1134" alt="截屏2024-09-14 13 40 10" src="https://github.com/user-attachments/assets/15d41ceb-4fb9-4e60-9460-2d7c46000168">
Repository: ant-design
Issue: Datepicker.Range 如何单面板选择范围？
Labels: 💡 Feature Request,Inactive

### What problem does this feature solve?

在一些业务场景下，客户希望在一个面板里面通过左右移动年月来选择范围

### What does the proposed API look like?

<DatePicker.Range multiplePanel="single" />

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: go
Issue: crypto/x509: no support for BitString
Labels: NeedsInvestigation

### Go version

1.23.1

### Output of `go env` in your module/workspace:

```shell
-
```


### What did you do?

Read x509 cert containing a BitString

### What did you see happen?

unsupported string type: 3 BitString

### What did you expect to see?

Support for bitstring https://go.dev/src/crypto/x509/parser.go line 60
Repository: ant-design
Issue: Spin嵌套使用下，当内层spin没有children导致外层Spin children被遮挡
Labels: Inactive,improvement

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-4nut3m?file=demo.tsx)

### Steps to reproduce

直接可以发现页面上的hello按钮被遮挡了，无法点击

### What is expected?

期望可以正常点击

### What is actually happening?

无法点击

| Environment | Info |
| --- | --- |
| antd | 5.20.6 |
| React | 与react版本无关 |
| System | 系统无关 |
| Browser | 浏览器版本无关 |

---
我查找了一下原因和阅读了一下源码，这个BUG产生原因是由于这个样式 &-nested-loading > div > .@{spin-prefix-cls}。而当Spin没有children渲染成 ：
const spinElement: React.ReactNode = (
    <div
      {...restProps}
      style={mergedStyle}
      className={spinClassName}
      aria-live="polite"
      aria-busy={spinning}
    >
      <Indicator prefixCls={prefixCls} indicator={mergedIndicator} percent={mergedPercent} />
      {tip && (isNestedPattern || fullscreen) ? (
        <div className={`${prefixCls}-text`}>{tip}</div>
      ) : null}
    </div>
  );
而不是 null 的原因我猜测是为了这样写 <Spin spinning={true}></Spin> 可以实现 loading 效果。
这个BUG我目前知道了原因，希望可以试试。

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: TypeScript
Issue: JSDoc typed function comments inside functions
Labels: Suggestion,Awaiting More Feedback

### 🔍 Search Terms

"JSDoc inside functions", "JSDoc comments inside", "typed function comments"

### ✅ Viability Checklist

- [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
- [X] This wouldn't change the runtime behavior of existing JavaScript code
- [X] This could be implemented without emitting different JS based on the types of the expressions
- [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, new syntax sugar for JS, etc.)
- [X] This isn't a request to add a new utility type: https://github.com/microsoft/TypeScript/wiki/No-New-Utility-Types
- [X] This feature would agree with the rest of our Design Goals: https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals

### ⭐ Suggestion

Are we able add support for adding JSDoc typed function comments inside functions, either natively or by a setting?

### 📃 Motivating Example

Personally, I find it easier to read JSDoc typed function comments when they are indented nicely inside functions, similar to Python, which would also pair really well with code folding.

```js
function arrayMove(index) {
  /**
   * @param {Number} index
   * @return {Array}
   */
  // ...
}
```
I enquired about [this](https://stackoverflow.com/questions/75955461/how-can-i-add-jsdoc-comments-inside-functions) on Stackoverflow last year

### 💻 Use Cases

.
Repository: PowerToys
Issue: 希望添加修改窗口透明度的功能
Labels: Needs-Triage

### Description of the new feature / enhancement

可以通过快捷键调整当前窗口的透明度以看到窗口下面的内容

### Scenario when this would be used?

学习中边看题目边写代码，工作时对照材料写文档等。

### Supporting information

_No response_
Repository: TypeScript
Issue: Error when accessing CSS property value using kebab case in `CSSStyleDeclaration` object
Labels: Bug,Help Wanted,Domain: lib.d.ts

### 🔎 Search Terms

"CSS property value kebab case dash", "CSSStyleDeclaration", "getComputedStyle", "getPropertyValue"

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about "CSSStyleDeclaration", "getComputedStyle"

### ⏯ Playground Link

https://www.typescriptlang.org/play/?ts=5.7.0-dev.20240914#code/OYUwLgwg9gtgDgVzCAJgZTATwDYgBQpQDGCMIAdmAHQBGUKmAlANoDkNAhkQNbABOUBORQBaIlGxQ+rALpA

### 💻 Code

```ts
getComputedStyle(document.body)['background-color']
```

### 🙁 Actual behavior

TypeScript reports following error:

>    Element implicitly has an 'any' type because index expression is not of type 'number'.

### 🙂 Expected behavior

TypeScript should not report any error.

### Additional information about the issue

If I update the file `node_modules/typescript/lib/lib.dom.d.ts` to include `background-color` as follows:

```ts
interface CSSStyleDeclaration {
  // ...
  'background-color': string;
  // ...
}
```

the error does not occur for `background-color` property.
Repository: electron
Issue: [Feature Request]: Turn off Efficiency Mode in win11
Labels: enhancement :sparkles:,platform/windows,32-x-y

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

32.1.0

### What operating system(s) are you using?

Windows

### Operating System Version

23H2

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

Don't enable Efficiency Mode!

### Actual Behavior

Efficiency Mode is on, but I want my software to run at high priority.

### Testcase Gist URL

_No response_

### Additional Information

https://devblogs.microsoft.com/performance-diagnostics/reduce-process-interference-with-task-manager-efficiency-mode/

_No response_
Repository: PowerToys
Issue: CAPTURAR JANELA
Labels: Issue-Bug,Needs-Triage,Product-Workspaces

### Microsoft PowerToys version

Release v0.84.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Workspaces

### Steps to reproduce

IN PT-BR, TRANSLATE PLS OK ( A NOVIDADE DO WORKSPACES NÃO CAPTURA, MESMO COM O POWERTOYS EM ADMIN, A JANELA DO CLIENTE DO LEAGUE OF LEGENDS E DO GS AUTO CLICKER 3.1.4) 

### ✔️ Expected Behavior

IN PT-BR, TRANSLATE PLS OK ( A NOVIDADE DO WORKSPACES NÃO CAPTURA, MESMO COM O POWERTOYS EM ADMIN, A JANELA DO CLIENTE DO LEAGUE OF LEGENDS E DO GS AUTO CLICKER 3.1.4) 

### ❌ Actual Behavior

IN PT-BR, TRANSLATE PLS OK ( A NOVIDADE DO WORKSPACES NÃO CAPTURA, MESMO COM O POWERTOYS EM ADMIN, A JANELA DO CLIENTE DO LEAGUE OF LEGENDS E DO GS AUTO CLICKER 3.1.4) 

### Other Software

IN PT-BR, TRANSLATE PLS OK ( A NOVIDADE DO WORKSPACES NÃO CAPTURA, MESMO COM O POWERTOYS EM ADMIN, A JANELA DO CLIENTE DO LEAGUE OF LEGENDS E DO GS AUTO CLICKER 3.1.4)
Repository: neovim
Issue: ":read :cmd" reads :cmd output into a buffer
Labels: enhancement,complexity:low,editor

### Problem

Vims' internal pager 'more' sucks: can't search when neovim opens output in it.

### Expected behavior

ability to search when paging with neovims internal pager 'more'
Repository: angular
Issue: Add "delay" parameter to the "idle" trigger
Labels: area: core,core: defer

### Which @angular/* package(s) are relevant/related to the feature request?

compiler

### Description

Please add the "delay" parameter to the "idle" trigger.
We could use it like this:
```
@defer (on hover(container); on idle(2000)) {
  <heavy-component/>
}
```
or this:
```
@defer (on idle({delay: 2000})) {
  <heavy-component/>
}
```
That would load the HeavyComponent either on hover or after a 2s delay after “idle”.

There are just components that are far enough from the user’s path, and heavy enough to load them not on just “idle”, but with a small delay - because more important components will take a chance to be loaded on “idle”.

### Proposed solution

Please add the "delay" parameter to the "idle" trigger.

### Alternatives considered

We can do this, but it is [considered a bad practice by Angular.dev](https://angular.dev/guide/templates/defer#avoid-cascading-loads-with-nested-defer-blocks):
```
@defer (on idle) {
  @defer(on timer(2000)) {
    <heavy-component/>
  }
}
```
Also, this way we can't combine triggers with "or" logic.
Repository: godot
Issue: Building with Visual Studio does not work if Scons is not on the path
Labels: discussion,topic:buildsystem

### Tested versions

74de05a01c8716a42d4e3427f607d7bea76b35e5

### System information

Windows 11

### Issue description

The solution generated with `scons platform=windows vsproj=yes dev_build=yes` will not build unless `scons` is available on the path. I am using conda environments with python as is recommended. I only have scons installed in one of the virtual environments. Building normally with scons this way works fine, however if I generate an sln file and try to build it using Visual Studio the build fails because it can't find scons. Adding scons to the path solves the issue but that is more a workaround than an actual solution.

### Steps to reproduce

- run `scons platform=windows vsproj=yes dev_build=yes` in a conda venv
- try to build

### Minimal reproduction project (MRP)

-
Repository: PowerToys
Issue: Reach out to devs of software that enhances / fixes Windows 10/11 issues to join the PowerToys project
Labels: Needs-Triage

### Description of the new feature / enhancement

For many users, certain software is essential when installing Windows 10 in order to restore missing / lacking functionality. The software includes:
* [7+ Taskbar Tweaker](https://ramensoftware.com/7-taskbar-tweaker) - fixes multiple lack of features within the taskbar; requires additional mods to work with Windows 11 ([see this blog post by the dev](https://ramensoftware.com/7-taskbar-tweaker-on-windows-11-with-windows-10s-taskbar)
* [PersistentWindows](https://github.com/kangyu-california/PersistentWindows) - fixes a long-standing issue with Windows 10/11 where program windows don't remember their location when using multiple monitors
* [StartIsBack](https://www.startisback.com/) - gives users full control over their start bar, allowing them to have it however they want; dev may not want to contribute without compensation though, as it's not freeware
* Search [Everything](https://www.voidtools.com/) - is **SO** much faster and better than any search functionality built into Windows 10/11
* [TagSpaces Lite](https://github.com/tagspaces/tagspaces) - allows much easier tagging of files in Windows and searching for them far better than Windows can
* [OldNewExplorer](https://msfn.org/board/topic/170375-oldnewexplorer-119/) - restores missing functionality that should never have been taken away after Windows 7

This is my personal OldNewExplorer setup, and is absolutely essential for me, along with having the "Preview pane" off.
![image](https://github.com/user-attachments/assets/f91e43c3-2f52-4b02-828d-4b37ca22bc8f)


### Scenario when this would be used?

Pretty much all the time. All of this software is because Microsoft changed user interfaces, removed functionality, or newer incorporated it into Windows in the first place. Many pro users are neurodivergent, especially autistic, ADHD, or both (AuDHD), so this kind of stuff really, really, irritates us to the core. Literally to the point where users will look for **any** workarounds to add in missing functionality. These are all Quality Of Life (QOL) issues that should at least be incorporated into PowerToys where possible, even if Microsoft won't allow them to be incorporated fully into Windows 10, 11, or whatever version comes next. (I was about to make a joke about it being Windows 365, but just found out that's an actual thing that exists!!!)

### Supporting information

I can't think of anything else to add here, other than linking you to [Embrace Autism](https://embrace-autism.com/), which explains a lot about neurodivergence in general. You should probably also be aware that a lot of programmers (even ones coding for Microsoft environments) fall somewhere under the trans umbrella (which is how the meme about "programmer socks" got started), so maybe link some of your colleagues to the [GDB](https://genderdysphoria.fyi/), just in case you've got a few programmers whose eggs haven't cracked yet. (If it's not obvious from my profile, yes, I'm a trans woman.)