sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: angular
Issue: Inconsistency between "Accessing query parameters and fragments" headline and provided example
Labels: area: docs

### Describe the problem that you experienced

The current documentation under the headline "Accessing query parameters and fragments" does not actually demonstrate how to handle query parameters or fragments. Instead, it focuses on accessing a route (path) parameter and navigating to a route with a path parameter.

For example, the text states:

"Sometimes, a feature of your application requires accessing a part of a route, such as a query parameter or a fragment."
However, the example and code snippets only show how to retrieve a path parameter (e.g., hero/:id) and do not include any instructions or examples related to query parameters (?key=value) or URL fragments (#fragment).


I think, accessing all 3 kind of parameters is important and should be explained on the "Common Routing Tasks" page.

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

https://angular.dev/guide/routing/common-router-tasks#accessing-query-parameters-and-fragments

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

I was into the guide, how the docs use Path Params, Query Params and Fragments. 
Especially, because the `ActivatedRoute` has a `queryParamMap` and a `paramMap` (and not a pathParamMap).


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

its the default.

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

I think, accessing all 3 kind of parameters is important and should be explained on the "Common Routing Tasks" page.

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

_No response_

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

```true

```

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

```true

```

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

```true

```
Repository: vscode
Issue: VSCode launch failed (code 43) (conflict with MacType?)
Labels: bug,freeze-slow-crash-leak,windows,sandbox,mitigated

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.96?
- OS Version: Windows 11

Steps to Reproduce:

1. Ensure there are no VS Code running
2. Try to open VS Code "indirectly", e.g. via GitHub Desktop "Open in Visual Studio Code" or via command line `code`
3. Immediately see error; this error holds for a short while, and then the entire window disappears

Directly opening VS Code from e.g. the start menu works, but that defeats the entire purpose of being able to start VS Code from other places. If somehow there is already a VS Code window running, then the above error doesn't occur.

Example error window:
![Image](https://github.com/user-attachments/assets/a8f0376e-b246-419b-8992-7b6b8c43d334)

Normally, even `code --crash-reporter-directory` as mentioned in https://github.com/microsoft/vscode/wiki/Native-Crash-Issues#creating-a-crash-report can result in the same error, and this will NOT result in crash dumps (???), but I am lucky enough that it sometimes passes through, and now I have a crash dump for this error.

**Crash dump**:
[20241212_vscode_dump.zip](https://github.com/user-attachments/files/18114765/20241212_vscode_dump.zip)

For further context, my Windows 11 has OneDrive cloud backup enabled. I notice this cloud backup may somehow hold file locks that it should not (especially when it has completed the backup), which can sometimes block other apps eg Office Word from saving the Word file because the file is "in use" by OneDrive. Not sure if this is relevant in this problem.
Repository: ollama
Issue: Windows NUMA 4 socket, 144 core system, default thread count causes very poor performance
Labels: bug,performance,windows

### What is the issue?

A 135M-parameter model only yielded 4 words after running for 3.5 hours on one 36-core CPU @ 100% load.

A 3.8B model yielded only 10 words after 10.5 hours on the same machine.

Prompt in both cases: "Introduce yourself."

Windows Server 2016 OS (direct install, no Docker).

Ollama 0.5.1 on 4 Xeon Gold 6140 CPUs (144 logical cores in total) and 768 GB of system RAM (6-channel, NUMA architecture).

No GPU.

Tried two small LMMs for starters, namely smollm:135m and phi3.5 (3.8B).

The correct runner for that CPU type was loaded (cpu_avx2).

smollm:135m was saying (after 3.5 h): "I'm thrilled to introduce..."

phi3.5 (3.8B) was saying (after 10.5 h): "Hello! I am Phi, an artificial intelligence designed to interact..."

I have run larger LLMs with Q4 and FP16 quantizations on a much older server machine running Windows 10 with dual Xeons 5600 (intel Westmere, no AVX), 288 GB of RAM (and no GPU), and the "cpu" runner worked fine. Indeed, a 30B, Q4 model runs very slow (~one word/second), but nothing like one word/hour!!!

On the newer machine (Win Server 2016), Ollama seems to run 288 parallel threads on one of four 36-core (logical) CPU; here's an excerpt from the server.log:

time=2024-12-12T16:47:26.192+01:00 level=INFO source=runner.go:942 msg=system info="AVX = 1 | AVX_VNNI = 0 | AVX2 = 1 | AVX512 = 0 | AVX512_VBMI = 0 | AVX512_VNNI = 0 | AVX512_BF16 = 0 | FMA = 1 | NEON = 0 | SVE = 0 | ARM_FMA = 0 | F16C = 1 | FP16_VA = 0 | RISCV_VECT = 0 | WASM_SIMD = 0 | BLAS = 0 | SSE3 = 1 | SSSE3 = 1 | VSX = 0 | MATMUL_INT8 = 0 | LLAMAFILE = 1 | cgo(clang)" threads=288

On the older machine (Win 10 Pro x64), Ollama used both CPUs and the load peaked at ~60%. RAM is DDR3 @ 1333 MHz, 3 channels/CPU (6 channels for DDR4 @ 2666 MHz on the newer machine).

### OS

Windows

### GPU

Other

### CPU

Intel

### Ollama version

0.5.1
Repository: rust
Issue: Detect different borrowing in different sub-expressions the same expression and suggest borrowing when applicable
Labels: A-diagnostics,P-low,T-compiler,A-suggestion-diagnostics,D-terse

```
error[E0308]: mismatched types
    --> compiler/rustc_middle/src/ty/context.rs:3212:73
     |
3210 |         match expr.kind {
     |               --------- this expression has type `rustc_hir::ExprKind<'_>`
3211 |             hir::ExprKind::Path(qpath)
     |                                 ----- first introduced with type `rustc_hir::QPath<'_>` here
3212 |             | hir::ExprKind::Call(hir::Expr { kind: hir::ExprKind::Path(qpath), .. }, []) => {
     |                                                                         ^^^^^ expected `QPath<'_>`, found `&QPath<'_>`
     |
     = note: in the same arm, a binding must have the same type in all alternatives
```

The above should suggest `match &expr.kind`.
Repository: terminal
Issue: GitHub Copilot on Terminal Chat might be adding some shortcut hotkey
Labels: Issue-Feature,Product-Terminal,Needs-Tag-Fix,Priority-3,Area-Chat

### Description of the new feature

The `Clear the message history` might be able to bind a hotkey on it. For example, `Ctrl-L`.

![Image](https://github.com/user-attachments/assets/c7a150e3-2198-4258-8ada-4df8c4d3242b)


### Proposed technical implementation details

_No response_
Repository: react
Issue: [Compiler Bug]: Handle TSInstantiationExpression expressions
Labels: Type: Bug,Status: Unconfirmed,Component: Optimizing Compiler

### What kind of issue is this?

- [ ] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhHCA7MAXABABwEMYwFcBeXAHgCUAaXAQQD4AKAN0IBsoFkmAlPxoVmuYAB0MuXAHpZBYqVwAzKBjjYAlplwB3LdgAWuSAFsyZwgHMtcXFqxaAJggB0HqTJgJssaZw8CFIAvlJSCAAe+BAweGoa2roAKgg4AMIQZvhaXAgwrALiXrjoWHjWvgAihNiEFLiForgACjBZWqRuPpBc7AisANoAugLh0nIAVLjJRp2lWTl5YKqOZJOyJWU4uM619ZSV2DV1hW7GCBisRCQIYxglstOz88bteiuE0vntMLgbjwU2zwezqDSOJ0IZwuVxupCoOBgjmsI2Y9xKPj8MGkVEYGAgFxgmWymEueECvHIwFBhBCcmYoSkIBCQA

### Repro steps

Basically, just use typescript's instantiation expressions inside a component

### How often does this bug happen?

Every time

### What version of React are you using?

19

### What version of React Compiler are you using?

19.0.0-beta-37ed2a7-20241206
Repository: kubernetes
Issue: Failed to get rootfs info if the host machine uses bcachefs raid array
Labels: kind/bug,priority/backlog,sig/node,triage/accepted

### What happened?

If you create a host machine with bcachefs file system with multiple drives:

```bash
❯ bcachefs format /dev/nvme0n1p2 /dev/nvme1n1p2 --replicas=2
❯ mount -t bcachefs /dev/nvme0n1p2:/dev/nvme1n1p2 /mnt
```

The filesystem device is in every linux tool defined as `/dev/nvme0n1p2:/dev/nvme1n1p2`.

```bash
❯ mount
/dev/nvme0n1p2:/dev/nvme1n1p2 on / type bcachefs (rw,relatime,metadata_replicas=2,data_replicas=2,compression=lz4,background_compression=lz4,nopromote_whole_extents,fix_errors=yes,nojournal_transaction_names)

❯ df /
Filesystem                     1K-blocks       Used  Available Use% Mounted on
/dev/nvme0n1p2:/dev/nvme1n1p2 3593522709 1260627309 2297004701  36% /
```

As you might know, docker displays this file system label if you add any unnamed volumes to your container. And this brings us to the k8s issue. If you create a cluster e.g. with kind or minikube, it starts a kubelet service in the container. Kubelet tries to read all mounts, and fails to parse the bcachefs filesystem:

```
kubelet.go:1566] "Failed to start ContainerManager" err="failed to get rootfs info: failed to get mount point for device \"/dev/nvme0n1p2:/dev/nvme1n1p2\": no partition info for device \"/dev/nvme0n1p2:/dev/nvme1n1p2\""
```

What you _can_ do is to just take the first partition from the list and use that. But here we have kubelet just crashing, rendering systems such as kind or minikube not working.

### What did you expect to happen?

Kubelet should just not care the filesystem name format. The system should start even when using bcachefs.

### How can we reproduce it (as minimally and precisely as possible)?

Spin up a virtual machine with two disks. It's probably easiest to run on NixOS:

https://nixos.wiki/wiki/Bcachefs

Create the root volume with

```bash
❯ bcachefs format /dev/nvme0n1p2 /dev/nvme1n1p2 --replicas=2
❯ mount -t bcachefs /dev/nvme0n1p2:/dev/nvme1n1p2 /mnt
```

Continue the installation as instructed.

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
Client Version: v1.31.0
Kustomize Version: v5.4.2
```

</details>


### Cloud provider

<details>
Local machine.
</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 12 (bookworm)"
NAME="Debian GNU/Linux"
VERSION_ID="12"
VERSION="12 (bookworm)"
VERSION_CODENAME=bookworm
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"
$ uname -a
# paste output here
Linux docker-container 6.12.3-cachyos #1-NixOS SMP PREEMPT_DYNAMIC Fri Dec  6 06:20:46 UTC 2024 x86_64 GNU/Linux
```

</details>


### Install tools

_No response_

### Container runtime (CRI) and version (if applicable)

_No response_

### Related plugins (CNI, CSI, ...) and versions (if applicable)

_No response_
Repository: terminal
Issue: Make sure foo.ico,0 works as an icon specifier
Labels: Issue-Bug,Area-UserInterface,Product-Terminal,Needs-Tag-Fix,Priority-3

### Windows Terminal version

1.21.3231.0

### Windows build number

10.0.19045.5198

### Other Software

_No response_

### Steps to reproduce

Change default PNG resource with any std Windows ICO resource and you get one behavior. Add ",0" at the end for another behavior. Both together would be correct as a whole. Individually, both are wrong.

[Screenshots](https://postimg.cc/gallery/pP9SHw6)

### Expected Behavior

Correct usage of the icon resource for the given place it's supposed to be displayed.

### Actual Behavior

Wrong or no icon displayed in taskbar jump list or in app.
Repository: go
Issue: x/vulndb/internal/worker/log: TestGoogleCloudHandler failures
Labels: NeedsInvestigation,vulncheck or vulndb

```
#!watchflakes
default <- pkg == "golang.org/x/vulndb/internal/worker/log" && test == "TestGoogleCloudHandler"
```

Issue created automatically to collect these failures.

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

    === RUN   TestGoogleCloudHandler
        log_test.go:28: 
            got  {"time":"2024-12-11T16:30:47-08:00","severity":"INFO","message":"hello","logging.googleapis.com/trace":"tid","foo":"bar","count":17}
            
            want {"time":"2024-12-11T16:30:46-08:00","severity":"INFO","message":"hello","logging.googleapis.com/trace":"tid","foo":"bar","count":17}
    --- FAIL: TestGoogleCloudHandler (0.00s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: PowerToys
Issue: Add greater than to the possible key remapping
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Priority-2

### Description of the new feature / enhancement

Hi,
in **Powertoys Keyboard Manager** remaping the  "<" key is straghtforward but ">" must be done by using SHIFT+ combination for "<". (not very intuitive)

I am writing this from a laptop keyboard that (for some strange reason) does not have "<" nor ">" but i have seen  some keyboards where the combination is exactly AltGr +z for "<" and AltGr+x for ">".

For ease of use ">" should be added to the possible key mappings, this way people could map AltGr +z for "<" and AltGr+x for ">" and possibly use stickers to show the mappings on the keyboard. 


PS:Congrats on the powertoys tools.

### Scenario when this would be used?

"<" and ">" are keys that need to be easily acessible for coding, math formulas, teaching...

This change would make it possible to use keyboard stykers in the usual place reserved for the AltGr combination and visually help users find the keys.

### Supporting information

Seen numerous post on this subject missing "<" and ">" on keyboard many people seem to never even find the SHIFT "trick" in powertoys to get the ">" sign.

Other tools seem to offer this possibility but if anything is altering keyboard related, i think Microsoft should be the (safest) way.
Repository: go
Issue: proposal: slices: MutableValues iterator
Labels: Proposal

### Proposal Details

It's a common task to iterate over a slice and modify its elements. For the following structure:

```go
type element struct {
	field int
}

var (
	elements = []element{
		{field: 1},
		{field: 2},
		{field: 3},
	}

	doubledElements = []element{
		{field: 2},
		{field: 4},
		{field: 6},
	}
)

```
we have to use one of:
```go
func TestDoubleWithRangeAndIndex(t *testing.T) {
	// change base elements without MutableValues
	// using indexing
	for i, e := range elements {
		e.field *= 2
		elements[i] = e
	}

	if !slices.Equal(elements, doubledElements) {
		t.Fail()
	}
}
```
or
```go
func TestDoubleWithRangeAndPointer(t *testing.T) {
	// change base elements without MutableValues
	// using pointer to element (useful in case of neested loops
	// or operations on more than one field)
	for i := range elements {
		e := &elements[i]
		e.field *= 2
	}

	if !slices.Equal(elements, doubledElements) {
		t.Fail()
	}
}
```

The proposal is to add `MutableValues` iterator to `slices` package:
```go
func MutableValues[Slice ~[]E, E any](s Slice) iter.Seq[*E] {
	return func(yield func(*E) bool) {
		for i := range s {
			if !yield(&s[i]) {
				return
			}
		}
	}
}
```
Mutating of all elements of the slice can looks like:
```go
func TestDoubleWithMutableValuesIterator(t *testing.T) {
	// values in elements will be changed
	for e := range slices.MutableValues(elements) {
		// we can directly change element via pointer
		e.field *= 2
	}

	if !slices.Equal(elements, doubledElements) {
		t.Fail()
	}
}
```
Repository: vscode
Issue: Use unique sounds for code action triggered and applied
Labels: feature-request,accessibility

ATM, we're re-using sounds, it would be better to have unique ones to reduce confusion.

cc @jooyoungseo, @afre100
Repository: vscode
Issue: Expose syntactic or semantic tokens with styles to extensions
Labels: feature-request,api,semantic-tokens

<!-- ⚠️⚠️ 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. -->
While VSCode has for a while supported the "text/html" clipboard format[^1], it doesn't expose this in a way that extensions could use. The [Clipboard](https://code.visualstudio.com/api/references/vscode-api#Clipboard) API only allows you to get plain text - can't specify a format - and I can find nothing attached to or "under" `window` or on `Selection`, `TextEditor`, `TextDocument`, etc.

To facilitate extension that could, for example, render SVG (or an image) a la [Carbon](https://carbon.now.sh)[^2], extensions would need to get these tokens and, ideally, the styles currently associated with them based on the current theme. A more robust API not requiring the user to change the current theme would instead provide those tokens - based on TextMate grammars or any token provider, if registered - and a list of themes returning maps of tokens to styles (this would also be a new API it seems).

Even just extending the clipboard API to allow us to pass an optional clipboard format and returning either a `UInt8Array` or just limiting us to raw text e.g., the raw HTML text of the "text/html" clipboard format would be useful, but still require extra steps for the user to copy the text first since it appears there are no APIs to copy the current selection to the clipboard - only to get the plain text of a selection(s) and place it in the clipboard as plain text yourself.

[^1]: Which seems to be inconsistent on Windows vs. macOS: macOS 18.2 does not contain the "application/vnd.code.copymetadata" or "vscode-editor-data" - or perhaps Safari is suppressing it - nor does it seem to use the full HTML clipboard recommendation of using fragments.
[^2]: Carbon doesn't export SVGs in a way that most apps I've used can correctly consume. It'd also save a lot of time just to be able to export an SVG or rendered image to use in presentations, social media, etc., perhaps with adornments like window chrome similar to what Carbon does.
Repository: rust
Issue: alloc_error_handler can be an `unsafe fn` which is then unsoundly invoked
Labels: T-compiler,I-unsound,C-bug,requires-nightly

This code currently compiles:
```rust
#![feature(alloc_error_handler)]
#![no_std]

extern crate alloc;

#[alloc_error_handler]
unsafe fn f(_: alloc::alloc::Layout) -> ! {
    core::hint::unreachable_unchecked();
}
```

This is unsound if the alloc error handler ever gets invoked.

The alloc_error_handler feature is still unstable, tracking issue: https://github.com/rust-lang/rust/issues/51540
Repository: rust
Issue: bootstrap/compiletest: msys2 msys `--skip` filter behaves strangely
Labels: E-hard,C-enhancement,T-bootstrap,A-compiletest,A-test-infra

>  As I suspected (unfortunately), inside MSYS2 MSYS, the `--skip` on the exact path does not work (I suspect this is a compiletest problem, not bootstrap). However, MSYS2 MSYS also has several other `./x test`-related issues, so this is not worth blocking on MSYS2 problems IMO.

```bash
$ ./x test tests/ui/traits/fn-pointer/bare-fn-no-impl-fn-ptr-99875.rs --stage 1 --skip tests/ui/traits/fn-pointer/bare-fn-no-impl-fn-ptr-99875.rs

running 1 tests
.

test result: ok. 1 passed; 0 failed; 0 ignored; 0 measured; 18066 filtered out; finished in 97.23ms
```

_Originally posted by @jieyouxu in https://github.com/rust-lang/rust/issues/134209#issuecomment-2539760846_
Repository: terminal
Issue: SUI Nullable Colors & Icon control Follow-ups
Labels: Product-Terminal,Issue-Task,Needs-Tag-Fix,Area-SettingsUI

Follow-ups from #17870:
- [x] [A11y] Screen readers don't read expander's preview text
   - Tracked in https://github.com/microsoft/microsoft-ui-xaml/issues/10282
   - ~Hmm... it might be better to just directly set the `AutomationProperty.Name`~
   - PR #18418
- [ ] Add Tab Color to settings UI
- [ ] Update CursorColor preview to display #FFFFFF as "invert"
- [ ] Use Leonard's font picker UI, with the Segoe icon picker, so that you can filter the list
- [ ] [High contrast] we should probably add borders to the color chip previews

### From Bug bash 1/21
- [ ] [Windows 10] Conflicting Windows & app theme causes this:
![Image](https://github.com/user-attachments/assets/15bfaf58-930d-438a-98f6-14224ce2a3f5)

- [ ] [Windows 10] Checkmark icon is missing!
![Image](https://github.com/user-attachments/assets/8e8649fa-51ec-441e-8ecd-3f8e751f90e1)

- [ ] Narrow window = cut off
![Image](https://github.com/user-attachments/assets/f44ea36a-31ff-44e4-9501-ca2e492d72a9)

- [ ] When using an emoji for the Profile icon, I run into this while using certain emojis (shield) though that might just be an issue with the emoji itself (not our problem?)

![Image](https://github.com/user-attachments/assets/707f73a0-6beb-41f7-a8bf-4a8bf30c4314)
Repository: storybook
Issue: [Bug]: At the end of a test run, the description briefly flashes "Not run"
Labels: bug,ui,sev:S3,addon: test

When running tests, the description goes through these phases:

1. _"Starting..."_
1. _"Testing... X/Y"_
1. _"Not run"_ 👈 **Bug**
1. Empty, causing the UI to jump for a frame or two 👈 **Bug**
2. _"Ran X tests Y seconds ago"_

(The video is slowed down x0.5)

https://github.com/user-attachments/assets/e00ee708-0fbb-47e3-a231-d97c35a5d04e
Repository: ui
Issue: [bug]: Missing tailwind config for borderRadius xl
Labels: bug

### Describe the bug

Affects components that use `rounded-xl`. eg. the `<Card />` component.

See discussion:
https://github.com/shadcn-ui/ui/discussions/4902

### Affected component/components

Card

### How to reproduce

1. Change your global css ---radius to 0rem
2. You'll see ever component except for `<Card />` be affected by this change.


### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Firefox, Mac
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues