sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: svelte
Issue: css_nesting_selector_invalid_placement false positive using tailwind 4 import reference
Labels: css

### Describe the bug

Have style block like this
```svelte
<style>
	@import '../../app.css' reference;
</style>
```
using new tailwind 4 syntax, [see](https://github.com/tailwindlabs/tailwindcss/pull/15228)
Svelte diagnostic emits top level warning `Nesting selectors can only be used inside a rule or as the first selector inside a lone ':global(...)'`

### Reproduction

n/a

### Logs

_No response_

### System Info

```shell
npmPackages:
    svelte: ^5.6.2 => 5.6.2
```


### Severity

annoyance
Repository: storybook
Issue: [Bug]: expect.any(String) always fails
Labels: bug,sev:S2,test utilities

### Describe the bug

`expect.any` is modified due to `@storybook/instrumenter` so it's asymmetric matching capabilities are broken.

```ts
import { expect} from '@storybook/test';
expect('hi').toEqual(expect.any(String)) // throws an error
```

running the above line using expect from `vitest` passes as expected.

### Reproduction link

https://stackblitz.com/edit/github-uhys1k?file=src%2Fstories%2FButton.stories.ts

### Reproduction steps

1. Go to above link.
2. Open Button -> Primary story
3. View "Instrumentation" add-on
4. See error

### System

```bash
Storybook Environment Info:

  System:
    OS: macOS 14.6.1
    CPU: (12) arm64 Apple M2 Max
    Shell: 5.9 - /bin/zsh
  Binaries:
    Node: 20.15.1 - ~/.nodenv/versions/20.15.1/bin/node
    Yarn: 3.2.4 - ~/.nodenv/versions/20.15.1/bin/yarn <----- active
    npm: 10.7.0 - ~/.nodenv/versions/20.15.1/bin/npm
  Browsers:
    Chrome: 131.0.6778.109
    Safari: 17.6
  npmPackages:
    chromatic: ^11.5.1 => 11.5.1
```

### Additional context

_No response_
Repository: go
Issue: internal/coverage/cfile: TestCoverageApis/emitToNonexistentDir failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "internal/coverage/cfile" && test == "TestCoverageApis/emitToNonexistentDir"
```

Issue created automatically to collect these failures.

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

    === RUN   TestCoverageApis/emitToNonexistentDir
    === PAUSE TestCoverageApis/emitToNonexistentDir
    === CONT  TestCoverageApis/emitToNonexistentDir
        emitdata_test.go:166: running: /home/swarming/.swarming/w/ir/x/t/TestCoverageApis2155603058/001/build1/harness.exe -tp emitToNonexistentDir -o /home/swarming/.swarming/w/ir/x/t/TestCoverageApis2155603058/001/emitToNonexistentDir-edir-y with rdir=/home/swarming/.swarming/w/ir/x/t/TestCoverageApis2155603058/001/emitToNonexistentDir-rdir-y and GOCOVERDIR=false
        emitdata_test.go:166: running: /home/swarming/.swarming/w/ir/x/t/TestCoverageApis2155603058/001/build1/harness.exe -tp emitToNonexistentDir -o /home/swarming/.swarming/w/ir/x/t/TestCoverageApis2155603058/001/emitToNonexistentDir-edir-x with rdir=/home/swarming/.swarming/w/ir/x/t/TestCoverageApis2155603058/001/emitToNonexistentDir-rdir-x and GOCOVERDIR=true
        emitdata_test.go:293: I run last.
            
            internal error in coverage meta-data tracking:
            encountered bad pkgID: 0  at slot: 3420  fnID: 6  numCtrs: 1
            list of hard-coded runtime package IDs needs revising.
    ...
            fatal error: exit hook invoked panic
            
            goroutine 1 gp=0xc000004380 m=0 mp=0x70e140 [running]:
            runtime.throw({0x5b98cd?, 0xc000004380?})
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/panic.go:1099 +0x92 fp=0xc0000768c0 sp=0xc000076890 pc=0x4e4e72
            internal/runtime/exithook.Run.func1()
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/internal/runtime/exithook/hooks.go:69 +0x55 fp=0xc0000768e0 sp=0xc0000768c0 pc=0x503795
            panic({0x5ab3e0?, 0xc0001d0030?})
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/panic.go:787 +0x202 fp=0xc000076990 sp=0xc0000768e0 pc=0x4e48c2
            runtime.goPanicSliceAcap(0x10000623d, 0x6c42)
    ...
            runtime.gopark(0x0?, 0x0?, 0x0?, 0x0?, 0x0?)
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/proc.go:435 +0x24a fp=0xc00005e630 sp=0xc00005e610 pc=0x4e518a
            runtime.runfinq()
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/mfinal.go:196 +0x3ce fp=0xc00005e7e0 sp=0xc00005e630 pc=0x4288ee
            runtime.goexit({})
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/asm_amd64.s:1700 +0x1 fp=0xc00005e7e8 sp=0xc00005e7e0 pc=0x4eee01
            created by runtime.createfing in goroutine 1
            	/home/swarming/.swarming/w/ir/x/w/goroot/src/runtime/mfinal.go:166 +0x86
        emitdata_test.go:294: running 'harness -tp emitToNonexistentDir': exit status 2
    --- FAIL: TestCoverageApis/emitToNonexistentDir (0.05s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: ollama
Issue: KV Cache quants run into issues every couple of messages.
Labels: bug

### What is the issue?

This is the error message I run into when running my scripts with KV cache q4_0 or q8_0. These are the models:

```
gemma2:27b-instruct-q4_0 (will be switching to q4_K_S)
minicpm-v-2.6-8b-q8_0
```

```
Traceback (most recent call last):

File "C:\Users\user\PycharmProjects\vector_companion\vector_companion\main.py", line 564, in <module>

config.asyncio.run(main())

File "C:\Users\user\.conda\envs\vector_companion\lib\asyncio\runners.py", line 44, in run

return loop.run_until_complete(main)

File "C:\Users\user\.conda\envs\vector_companion\lib\asyncio\base_events.py", line 647, in run_until_complete

return future.result()

File "C:\Users\user\PycharmProjects\vector_companion\vector_companion\main.py", line 520, in main

await queue_agent_responses(

File "C:\Users\user\PycharmProjects\vector_companion\vector_companion\main.py", line 178, in queue_agent_responses

await config.asyncio.gather(process_sentences(), play_audio_queue())

File "C:\Users\user\PycharmProjects\vector_companion\vector_companion\main.py", line 157, in process_sentences

async for sentence in sentence_generator:

File "C:\Users\user\PycharmProjects\vector_companion\vector_companion\config\config.py", line 109, in fetch_stream

for chunk in stream:

File "C:\Users\user\.conda\envs\vector_companion\lib\site-packages\ollama\_client.py", line 90, in _stream

raise ResponseError(e)

ollama._types.ResponseError: an error was encountered while running the model: read tcp 127.0.0.1:34105->127.0.0.1:34102: wsarecv: An existing connection was forcibly closed by the remote host.

```

So when I look at the server log I see this:

```
C:\a\ollama\ollama\llama\ggml-cuda\cpy.cu:531: ggml_cuda_cpy: unsupported type combination (q4_0 to f32)

time=2024-12-04T19:38:14.673-05:00 level=DEBUG source=server.go:1092 msg="stopping llama server"
[GIN] 2024/12/04 - 19:38:14 | 200 |     5.073219s |       127.0.0.1 | POST     "/api/chat"
time=2024-12-04T19:38:14.674-05:00 level=DEBUG source=sched.go:407 msg="context for request finished"
time=2024-12-04T19:38:14.674-05:00 level=DEBUG source=sched.go:339 msg="runner with non-zero duration has gone idle, adding timer" modelPath=C:\Users\carlo\.ollama\models\blobs\sha256-d7e4b00a7d7a8d03d4eed9b0f3f61a427e9f0fc5dea6aeb414e41dee23dc8ecc duration=2562047h47m16.854775807s
time=2024-12-04T19:38:14.674-05:00 level=DEBUG source=sched.go:357 msg="after processing request finished event" modelPath=C:\Users\carlo\.ollama\models\blobs\sha256-d7e4b00a7d7a8d03d4eed9b0f3f61a427e9f0fc5dea6aeb414e41dee23dc8ecc refCount=0
```
This is per the RC uploaded today.

### OS

Windows

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.4.8 RC
Repository: pytorch
Issue: torch.distributed.new_group got stuck when use backend=mpi
Labels: oncall: distributed,module: mpi

### 🐛 Describe the bug

```python
# test.py
import torch
import os
rank = int(os.getenv("LOCAL_RANK"))
torch.distributed.init_process_group('mpi')
g = torch.distributed.new_group(ranks=[0])
torch.distributed.barrier()
print("Done!")
```

### Description

The problem same with #134314 , but I run them with `backend=mpi`. And I test on torch2.5.1, but cannot be solved.

Please help me to solve this problem, thanks !

cc @H-Huang @awgu @kwen2501 @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o
Repository: terminal
Issue: Snippets pane doesn't include snippets from .wt.json
Labels: Issue-Bug,Area-Settings,Product-Terminal,Needs-Discussion

It probably should.
Repository: ollama
Issue: Mini-CPM-V-2.6-q8_0 produces incoherent responses after applying KV Cache q4_0 or q8_0.
Labels: bug

### What is the issue?

This happens when running ollama `/generate` via the python API. The output looks like the model is having a seizure. It seems to be able to see the images but its output is so random and erratic I can't make out anything from the text. I didn't change any other parameter about the model.

### OS

Windows

### GPU

Nvidia

### CPU

Intel

### Ollama version

0.4.8 RC
Repository: node
Issue: `.pipeTo(Writable.toWeb(process.stdout))` returns a never-settling Promise
Labels: web streams

### Version

- v22.9.0
- v22.12.0
- v23.3.0

### Platform

```text
Linux a54ff73afbfe 5.15.153.1-microsoft-standard-WSL2 #1 SMP Fri Mar 29 23:14:13 UTC 2024 x86_64 GNU/Linux
```
```text
Linux SURFACE9PRO 5.15.153.1-microsoft-standard-WSL2 #1 SMP Fri Mar 29 23:14:13 UTC 2024 x86_64 x86_64 x86_64 GNU/Linux
```

### Subsystem

node:stream

### What steps will reproduce the bug?

create file `test.mjs`

```javascript
import { Readable, Writable } from 'node:stream'

await Readable.toWeb(process.stdin).pipeTo(Writable.toWeb(process.stdout))
```

run

```terminal
echo test | node test.mjs 
test
Warning: Detected unsettled top-level await at file:///workspace/test.mjs:2
await Readable.toWeb(process.stdin).pipeTo(Writable.toWeb(process.stdout))
^
```

### How often does it reproduce? Is there a required condition?

always

### What is the expected behavior? Why is that the expected behavior?

no warning, `await` to work as expected

### What do you see instead?

warning about unsettled top-level await is shown

### Additional information

_No response_
Repository: PowerToys
Issue: Activity Modes
Labels: Idea-New PowerToy,Needs-Triage,Needs-Team-Response

### Description of the new feature / enhancement

I very often need to adjust the screen saver timeout, display off timeout, and sleep settings of windows. These settings are related, but the dialogs to change them are all over the place and difficult to open.  It would be nice to be able to configure and save various modes with different values for these settings, then have a WIN+SHIFT hotkey to cycle through modes to choose an active one. In addition, it would be nice to have WIN+SHIFT shortcuts to immediately activate one of them, like put the pc to sleep now or turn off the monitor now or start the screensaver now.


### Scenario when this would be used?

I use Chrome Remote Desktop to remote into PCs, which cannot wake them. I'm constantly turning sleep off or on, depending on my need to remote into the PC later.

I might normally have aggressive timeouts for screensaver at 10 min, display turn off at 15 min, sleep at 30 min. However, when I am researching or doing something without using the mouse for long periods, I need a less conservative mode. I might set the screensaver to 235 min, display turn off to 240 min, and sleep to never.

Some keyboards have a dedicated sleep button, which is great for immediately activating sleep. For pcs that have them, I can leave sleep off and just hit that button when I am done working. However, I usually have to resort to making desktop shortcuts to turn on a screensaver or fumble around looking for the power button to turn off monitors. It would be nice to just have consistent keyboard shortcuts across devices to do these very basic tasks.

### Supporting information

It's so difficult to find these dialogs in the new interactive settings app and old control panel dialogs that I find myself leaving them open 24/7 to be able to change and apply new settings. It's extremely cumbersome. 

Forgetting to increase timeouts during a session can force you to have to authenticate every few minutes, often involving finding your phone and responding to 2FA popups.

Forgetting to disable sleep can make it impossible to "chromote" in later.
Repository: rust
Issue: Likely unintentionally stabilized support for inhabitedness checks to permeate `Pin`
Labels: T-lang,T-compiler,C-bug

```rs
use std::pin::Pin;

enum Void {}
fn demo(x: Pin<Void>) {
    match x {}
}
```
this compiles successfully since 1.82

The issue with this is that generally, the check does *not* look through private implementation details. However, the field of `Pin` is technically public (only hidden and unstable) in order to support the `pin!` macro.

I would have expected the above code to still fail compiling. It’s quite unlikely that anyone depends on this behavior already, because `Pin` isn’t supposed to be used with non-pointers anyway.

This could be fixed by changing the inhabitedness check to treat unstable fields like private fields.

Alternatively, if kept as-is, we should add a test case for this so we at least notice the breakage if `Pin` is ever re-structured to no longer using a public field.

cc @Nadrieril, I guess
Repository: ollama
Issue: model requires more system memory than is available when useMmap 
Labels: bug

### What is the issue?

When I use continue vscode extension to call ollama config like
```
    {
      "model": "qwen2.5-coder:14b",
      "title": "qwen2.5-coder:14b",
      "provider": "ollama",
      "completionOptions": {
        "keepAlive": 9999999,
        "useMmap": true
      }
    },
```
It still checks system memory disregard the `"useMmap": true` option.  And return 500 internal error like:
```
{"error":"model requires more system memory (17.7 GiB) than is available (13.6 GiB)"}
```


### OS

Windows

### GPU

_No response_

### CPU

Other

### Ollama version

0.4.7
Repository: deno
Issue: [Feature Request] Workspace task with --env-file 
Labels: suggestion,task runner

In my project we have the same env variables on all our workspace. It would be nice to have `--env-file` on task so that we would only set env on RootDir deno.json file
```json
{
  "tasks" {
    "build": "deno task --recursive build",
    "build:dev": "deno task --env-file=.env.dev build",
    "build:prod": "deno task --env-file=.env.prod build"
  }
}
```
Repository: rust
Issue: rustdoc: support #![cfg(feature)] that disables doc tests
Labels: T-rustdoc,C-feature-request,A-doctests,A-cfg

Code in doc comments may require specific Cargo features or platforms, but currently the syntax for disabling doctests is non-obvious, verbose, and by mixing languages and syntaxes, it doesn't play well with Markdown syntax highlighting:

````rust
#![cfg_attr(feature = "alloc", doc = " ```")]
#![cfg_attr(not(feature = "alloc"), doc = " ```ignore")]
//! code
//! ```

````

I suggest supporting `#![cfg(…)]` inside doctests, injected into the test code in a way that disables a block of code containing the test. Currently `#![cfg(feature = …)]` doesn't work at all in doctests, because it gets hoisted to be a real crate attribute, and ends up disabling entire the test module.

````rust
//! ```rust
//! #![cfg(feature = "alloc")] // proposed syntax
//! code
//! ```
````

In the implementation I think it would require wrapping "everything_else" code in extra `{ }`, and keeping `#![cfg(feature = …)]` attrs in the code, instead of extracting them and hoisting them to the top level of the doctest crate.
Repository: neovim
Issue: LSP: need a strategy for handling stateful data
Labels: enhancement,lsp,architecture

### Problem

Some LSP request responses need to be retained after processing the results, such as:

- `textDocument/foldingRange` needs to retain state for closing a specific `foldingRangeKind`. For neovim, folding information must be cached.
- `textDocument/inlayHint` and `textDocument/codeLens` require maintaining state for subsequent requests like `resolve`.
- `textDocument/documentHighlight` could retain state to enable forward/backward navigation.

### Expected behavior

Implement an internal-only module dedicated to handling these stateful data, by:

- Creating `bufstate` and corresponding callback functions when a buffer has a client that supports the relevant methods.
- Destroying `bufstate` and corresponding callback functions when no clients in the buffer support the relevant methods.

Use this module for the methods mentioned above to avoid relying on nil-checks (which might mask bugs) and automatically creating tables via metatable methods (which can be difficult to debug).

The `bufstate` should only contain results directly obtained from the server (e.g., `lsp.foldingRange[]`, `lsp.InlayHint[]`) and derived information (e.g.,  computed caches or whether they are applied). It should not store user-managed settings (e.g., `enabled`).
Repository: pytorch
Issue: [compiled autograd] Does compiled autograd under torch 2.4 support using selective checkpoint?
Labels: triaged,oncall: pt2,module: compiled autograd

### 🐛 Describe the bug

While implementing selective checkpointing in compiled autograd, we encountered the following error:
```
torch._dynamo.exc.Unsupported: 'inline in skipfiles: CheckpointFunction.backward | backward /.../site-packages/torch/utils/checkpoint.py, 
skipped according to trace_rules.lookup SKIP_DIRS'
```
The error is thrown here:
```python
def call_backward(backward_c_function, saved_tensors, *args):
    fake = FakeBackwardCFunction(backward_c_function, saved_tensors)
    # error throw point
    grads = fake._forward_cls.backward(fake, *args)  # type: ignore[attr-defined]

    # in eager, we wrap in a tuple when there's only one grad output
    if type(grads) is not tuple:
        grads = (grads,)

    return grads
```
Is it accurate to say that torch 2.4 still does not support selective checkpointing in compiled autograd?"

### Versions

[pip3] numpy==1.24.4
[pip3] onnx==1.16.2
[pip3] torch==2.4.0
[pip3] torchaudio==2.4.0+cu124
[pip3] torchlibrosa==0.1.0
[pip3] torchvision==0.19.0+cu124
[pip3] triton==3.0.0
[conda] Could not collect

cc @chauhang @penguinwu @xmfan @yf225
Repository: PowerToys
Issue: Desktop Background Manager
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

Windows 11 has decent multi-monitor support for desktop backgrounds. You can use a random or alphabetical slideshow of images from a specified folder and make the backgrounds unique or mirrored across monitors. If you right-click the background, you can cycle to the next image in the slideshow, but it only changes one monitor and not necessarily the one you wanted to change. 

It would be nice to have a Power Toys module that gave further control. I would love to have a WIN+SHIFT shortcut to cycle images, like the right-click shortcut. It would be nice to have a shortcut to pause the timer cycling to keep them fixed for a while, perhaps to make a set of consistent screenshots. It would be nice to have a keyboard shortcut (and/or a right-click shortcut) to cycle a specific monitor's image. It would be nice to configure preset images per monitor, maybe even including random or alphabetical for some monitors and fixed images on other monitors or even a different set of slideshow folders for each monitor, then allow shortcuts to activate or cycle those presets.

You could get even crazier with ai, allowing filtering of the slideshow images with a description, like "green palette" or "cars" or "2024" or "anime". Using it to find images of people or particular things, like "my car" or "my pet", would probably require defining those things with a selected image that it could use to find similar ones. I won't be paying monthly fees for any ai service though, so unless there is a free way to implement ai features, like Microsoft Copilot, I'm not interested.

### Scenario when this would be used?

This would be useful in any multiple monitor configuration. It would save a lot of time when you want to change a background image. It would allow you to make presets that would be useful for taking consistent screenshots. It would allow you to set a simple background image and pause the background slideshow when "chromoting" into a pc with limited bandwidth. The possibilities are endless.

### Supporting information

If I want to change a background from a slideshow when I have 3 monitors, I currently have to right click the desktop and click "next desktop background" up to 3 times, which is extremely cumbersome. If I only want to change one of the three, there is no way to reliably do this.
Repository: transformers
Issue: Is there a way to find the earliest version of transformers that has a certain model?
Labels: Feature request

### Feature request

Is there a way to find the earliest version of transformers that has a certain model? For example, I want to use CLIP into my project, but the existing transformers version is old, I want to upgrade transformers to a lowest version that can use CLIP, so that other parts of my code do not change.

### Motivation

There are situations where I need to use a new model in the existing codebase. But when updating transformers, there could be some parts of the code out of date, and need to be modified. 

### Your contribution

I don't know, but I will try to help.
Repository: angular
Issue: UMD version of Zone.js is incorrectly transpiled
Labels: area: zones

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

zone.js

### Is this a regression?

No

### Description

The implementation of ZoneAwarePromise.allWithCallback uses a `for(... of ...)` loop. This is expected and correct, as [Promise.all](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/Promise/all) expects an iterable.

However, the latest published [UMD version](https://unpkg.com/zone.js@0.15.0/bundles/zone.umd.js) of zone.js transpiles that down to `for (var _i = 0, values_3 = values; _i < values_3.length; _i++) {`, which will only work with Arrays (or ArrayLike) values.

This fails when Promise.all is used with Iterables

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

[JSFiddle showing bug when umd version of zone is installed](https://jsfiddle.net/32o5ydsj/4/)

[JSFiddle showing correct behaviour without zone.js](https://jsfiddle.net/32o5ydsj/3/)

### Please provide the exception or error you saw

```true
N/A
```

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

```true
N/A
```

### Anything else?

_No response_
Repository: ant-design
Issue: Feature to identify the exact reason of triggering event
Labels: 🗣 Discussion,Inactive

### What problem does this feature solve?

This feature solves the ambiguity in handling the onChange event in the Ant Design AutoComplete component by allowing developers to identify whether the event was triggered by user typing, selecting an option, or clearing the input. This enhances event handling precision and reduces the need for workaround logic.

### What does the proposed API look like?

The proposed API introduces an additional parameter to the onChange event handler in the Ant Design AutoComplete component. This parameter specifies the reason for the onChange event being triggered.

onChange={(value, reason) => {
    console.log('Value:', value, 'Reason:', reason);
}}

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->