sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: [Mouse Crosshairs] Implement "Gliding cursor" accessibility feature
Labels: Needs-Triage,Product-Mouse Utilities

### Description of the new feature / enhancement

A gliding cursor allows someone who can only operate a single switch (or few) to interact with Windows. As a minimum, a single switch (e.g. by using the Microsoft Adaptive Accessories) can be connected to a pc and by sequentially pressing that switch the user can select a target on the screen by combing a "X" and "Y" coordinate on the desktop. This is achieved by having two moving lines running across the desktop, one running left to right, the other top to bottom. To start, the user initiates a vertical line movement by clicking the switch associated with this feature. The line starts running left to right and when the desired position is reached the user clicks again to lock that position vertically. A second, horizonal, line starts running across the desktop top to bottom. When the desired position for that line is reached, the user clicks the switch once more to create an exact position on the desktop at which the feature will perform a selection (single/double mouse click).

The existing Crosshair functionality in the Mouse utilities already offers quite a lot of the required properties. The idea would be to implement this new tool as an extension of that "Mouse Pointer Crosshairs" feature. 

This is a very popular, existing feature in iOS. Hereby a video showing the feature in use:  
https://youtu.be/HBo2BZ-Zzwg?si=ctQXnRakhxv8HfTZ&t=115/

### Scenario when this would be used?

This scenario would be used by developers/(power) users that have a mobility related accessibility requirement.  

### Supporting information

See video for an already well-proven scenario in iOS. It's a reoccurring ask to have a way to control Windows with a single switch. In the future this feature could be further extended to support multiple switches in case the user is able to work with more than a single switch. However, the implementation described above provides a basic implementation.   

https://github.com/user-attachments/assets/7716cb34-7678-40a8-9803-0daeed229b24
Repository: vscode
Issue: Ability to associate esoteric extensions with existing file types
Labels: triage-needed

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

It would be nice if there was an ability to “map” extensions with an existing file type, similarly the way you can map extensions to a language using the `files.associations` configuration option.

For example, I like to do some retro programming of PlayStation 1 games. The PlayStation 1 had its own native file formats, such as:

* `STR` for streaming data (videos)
* `TIM` for textured images
* `VB`/`VH` for audio samples

Given these are highly specific, they just show a default “text file” icon in the Explorer. It would nice if we could get a configuration option to indicate what type of files they are, though. Something like:

```json
"files.types": {
    "str": "video",
    "tim": "image",
    "vb": "audio",
    "vh": "audio"
}
```

I did look into this, but it seems the current way to address this is to create a custom extension. This seems impractical, due to:

* The huge barrier to creating an extension in the first place.
* It’s only a small number of file extensions I’m interested in.
* I have to bundle an existing file icon theme’s icons into _my_ extension, which is inefficient for less than half a dozen file types.

I’m not asking for these file types to be _supported_ by the Visual Studio Code editor, but just think it would be a nice quality of life improvement to be able to tell Code what type of files they are so they get an appropriate icon. For example, the Explorer shows a speaker icon for `*.mp3` files and a play icon for `*.mp4` files in the Explorer, despite Code not being able to open and play MP3 and MP4 files out of the box.
Repository: storybook
Issue: [Bug]: Global CSS bleeds between preloaded stories
Labels: bug

### Describe the bug

Storybook’s preloading mechanism currently preloads the first story in a story file when the Storybook instance is initialized. Additionally, hovering over other stories triggers their preloading. However, this functionality has introduced an issue where global CSS (non-modularized styles) from preloaded stories persists and bleeds into the current story, leading to unintended style conflicts.

![Image](https://github.com/user-attachments/assets/ce391aee-351f-4421-a655-5631de73b306)

### Reproduction link

-

### Reproduction steps

1. Create a Storybook with two stories. The second one should import a css file with global CSS (e.g. background: red)
2. Visit the first story and now hover over the second one. -> CSS of the preloading bleeds into the first one

### System

```bash
-
```

### Additional context

_No response_
Repository: kubernetes
Issue: [Flaking Test] [sig-node] E2eNode Suite.[It] [sig-node] [NodeConformance] Containers Lifecycle when Running a pod with init containers and regular containers
Labels: sig/node,kind/flake,needs-triage

### Which jobs are flaking?

master-blocking
- ci-crio-cgroupv2-node-e2e-conformance

### Which tests are flaking?

E2eNode Suite.[It] [sig-node] [NodeConformance] Containers Lifecycle when Running a pod with init containers and regular containers, restartPolicy=Never when A regular container has a PreStop hook when A regular container fails a liveness probe when a pod is terminating because its liveness probe fails should continue running liveness probes for restartable init containers and restart them while in preStop [NodeConformance]
[prow](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv1-evented-pleg/1883458293720944640)
[triage](https://storage.googleapis.com/k8s-triage/index.html?test=Containers%20Lifecycle%20when%20Running%20a%20pod%20with%20init%20containers%20and%20regular%20containers%2C%20restartPolicy%3DNever%20when%20A%20regular%20container%20has%20a%20PreStop%20hook%20when%20A%20regular%20container%20fails%20a%20liveness%20probe%20when%20a%20pod%20is%20terminating%20because%20its%20liveness%20probe%20fails%20should%20continue%20running%20liveness%20probes%20for%20restartable%20init%20containers%20and%20restart%20them%20while%20in%20preStop&xjob=e2e-kops)

### Since when has it been flaking?

[1878741797895671808 1/13/2025, 6:52:56 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv1-evented-pleg/1878741797895671808)
[1879195290896961536 1/14/2025, 12:54:56 PM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv1-evented-pleg/1879195290896961536)
[1880873097419034624 1/19/2025, 4:01:58 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv1-evented-pleg/1880873097419034624)
[1881916482472906752 1/22/2025, 1:07:59 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv1-evented-pleg/1881916482472906752)
[1882868904884178944 1/24/2025, 4:12:44 PM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv1-evented-pleg/1882868904884178944)
[1883458293720944640 1/26/2025, 7:14:44 AM](https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/ci-crio-cgroupv1-evented-pleg/1883458293720944640)


### Testgrid link

https://testgrid.k8s.io/sig-release-master-blocking#ci-crio-cgroupv2-node-e2e-conformance

### Reason for failure (if possible)

```
{ failed [FAILED] Expected an error to have occurred.  Got:
    <nil>: nil
In [It] at: k8s.io/kubernetes/test/e2e_node/container_lifecycle_test.go:941 @ 01/26/25 10:32:58.877
}
```

### Anything else we need to know?

N/A

### Relevant SIG(s)

/sig node
cc: @kubernetes/release-team-release-signal
Repository: flutter
Issue: Flutter commands no longer work if a branch is cloned with `--single-branch`
Labels: team-infra,monorepo

### Steps to reproduce

I have a GitHub action for cloning Flutter to run tests. The test run on various different branches but to save time/space only the branch being tested is cloned (the other branches run in different jobs) using `--single-branch`.

This used to work fine, but recently has stopped working because Flutter assumes it can access `origin/master`.

To repro:

1. Run `git clone --single-branch --branch beta https://github.com/flutter/flutter` to clone the beta branch without all others
2. Run `./flutter_beta/bin/flutter doctor`

### Expected results

`flutter doctor` should run successfully.

### Actual results

```
PS D:\Temp> ./flutter_beta/bin/flutter doctor
fatal: Not a valid object name origin/master
Error: Unable to determine engine version...
```

### Code sample

N/A

### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

![Image](https://github.com/user-attachments/assets/3db2ea7f-5a48-42b5-80f6-455a1f2dbfd3)

</details>


### Logs

<details open><summary>Logs</summary>

Unable to get any verbose logs:

```console
PS D:\Temp> ./flutter_beta/bin/flutter doctor -v
fatal: Not a valid object name origin/master
Error: Unable to determine engine version...
```

</details>


### Flutter Doctor output

<details open><summary>Doctor output</summary>

Unable to run:

```console
PS D:\Temp> ./flutter_beta/bin/flutter doctor -v
fatal: Not a valid object name origin/master
Error: Unable to determine engine version...
```

</details>
Repository: godot
Issue: Tool Script get_string_size() Discrepancy for "♯" Between Editor Inspection and Scene Execution
Labels: topic:editor,needs testing,topic:gui

### Tested versions

Godot v4.4.beta1

### System information

Windows 11 (build 22631) - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 2050 (NVIDIA; 32.0.15.6109) - 12th Gen Intel(R) Core(TM) i5-12500H (16 threads)

### Issue description

When a `@tool` script calls get_theme_default_font().get_string_size("♯"), it returns correct metrics (16.0, 23.0) during editor inspection (with script actively running as a tool), but shows reduced width (7.0, 23.0) during scene execution (via Play Scene button or exported build). Regular characters (e.g., "A","C","B") remain consistent across both modes.

### Steps to reproduce

```gdscript
@tool
extends Control

func _process(delta: float) -> void:
	var special_char_size = get_theme_default_font().get_string_size("♯", HORIZONTAL_ALIGNMENT_CENTER)
	var regular_char_size = get_theme_default_font().get_string_size("ACB", HORIZONTAL_ALIGNMENT_CENTER)
	print("Font metrics - Special: %s %s | Regular: %s" % [
		get_theme_default_font().font_name,
		special_char_size,
		regular_char_size
	])
```
Editor (Output example: Open Sans SemiBold (16.0, 23.0) | (32.0, 23.0))
Runtime (Example: Open Sans SemiBold (7.0, 23.0) | (32.0, 23.0))

### Minimal reproduction project (MRP)

N/A
Repository: storybook
Issue: [Bug]: addon-storysource doesn't display the full source when using Vite
Labels: bug,needs triage

### Describe the bug

I am using storybook v8.5.1.  When using Vite as a framework and this addon - @storybook/addon-storysource I am not able to see the the full source code. 
This is similar to https://github.com/storybookjs/storybook/issues/29478, and the issue was fixed in https://github.com/storybookjs/storybook/pull/29669, but this only seems to have fixed it for webpack as framework and not Vite.

<p>Using Vite:</p>
<img src="https://github.com/user-attachments/assets/d52376fc-ad6c-492b-9ea3-f9a6b74dcf62" width="300" height="300" alt="Using Vite" title="Using Vite" />

<p>Using Webpack:</p>
<img src="https://github.com/user-attachments/assets/bcc42547-ed53-4476-94ef-e74e0711a3af" width="300" height="300" alt="Using Webpack" title="Using Webpack" /> 

Storybook Version : ^8.5.1

### Reproduction link

https://stackblitz.com/edit/github-h25xa6-fqssm5jb?file=package.json

### Reproduction steps

1. To see the results of using webpack, go to .storybook/main.ts
2. Uncomment the commented lines and remove "@storybook/react-vite" from the framework config.

### System

```bash
System:
    OS: Windows 11 10.0.26100
    CPU: (12) x64 Intel(R) Core(TM) 7 150U
  Binaries:
    Node: 20.12.1 - C:\Program Files\nodejs\node.EXE
    Yarn: 1.22.22 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 10.5.1 - C:\Program Files\nodejs\npm.CMD <----- active
    pnpm: 9.6.0 - ~\AppData\Roaming\npm\pnpm.CMD
  Browsers:
    Edge: Chromium (132.0.2957.115)
  npmPackages:
    @storybook/addon-essentials: ^8.5.1 => 8.5.1
    @storybook/addon-interactions: ^8.5.1 => 8.5.1
    @storybook/addon-onboarding: ^8.5.1 => 8.5.1
    @storybook/addon-storysource: ^8.5.1 => 8.5.1
    @storybook/addon-webpack5-compiler-swc: ^2.0.0 => 2.0.0
    @storybook/blocks: ^8.5.1 => 8.5.1
    @storybook/react: ^8.5.1 => 8.5.1
    @storybook/react-vite: ^8.5.1 => 8.5.1
    @storybook/react-webpack5: ^8.5.1 => 8.5.1
    @storybook/test: ^8.5.1 => 8.5.1
    eslint-plugin-storybook: ^0.11.2 => 0.11.2
    storybook: ^8.5.1 => 8.5.1
```

### Additional context

_No response_
Repository: rust
Issue: PowerPC linker warning: `bss-plt forced due to {name}.o`
Labels: T-compiler,O-PowerPC,C-bug,O-linux-gnu,A-linkers,L-linker_messages

Originally noted in https://github.com/rust-lang/rust/issues/136096#issuecomment-2615051447 when building `libc`, PowerPC can emit the following linker warning:

```text
 warning: linker stderr: /usr/lib/gcc-cross/powerpc-linux-gnu/13/../../../../powerpc-linux-gnu/bin/ld: bss-plt forced due to /checkout/target/powerpc-unknown-linux-gnu/debug/deps/const_fn-5906628da0f5d31e.2bjw3mlsf69tu9e94ehzuvs4u.rcgu.o
```

I also noticed this previously in `compiler_builtins` https://github.com/rust-lang/compiler-builtins/pull/667.

https://sourceware.org/binutils/docs/ld/PowerPC-ELF32.html says the following:

> --bss-plt
>    Current PowerPC GCC accepts a ‘-msecure-plt’ option that generates code capable of using a newer PLT and GOT layout that has the security advantage of no executable section ever needing to be writable and no writable section ever being executable. PowerPC ld will generate this layout, including stubs to access the PLT, if all input files (including startup and static libraries) were compiled with ‘-msecure-plt’. ‘--bss-plt’ forces the old BSS PLT (and GOT layout) which can give slightly better performance.
>
> --secure-plt
>    ld will use the new PLT and GOT layout if it is linking new ‘-fpic’ or ‘-fPIC’ code, but does not do so automatically when linking non-PIC code. This option requests the new PLT and GOT layout. A warning will be given if some object file requires the old style BSS PLT. 

It sounds like `secure-plt` is the default but something about our object files forces a fallback to `bss-plt`.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"taiki-e"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: go
Issue: google.golang.org/protobuf: TestIntegration/Go1.23.0/LazyDecoding failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "google.golang.org/protobuf" && test == "TestIntegration/Go1.23.0/LazyDecoding"
```

Issue created automatically to collect these failures.

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

    === RUN   TestIntegration/Go1.23.0/LazyDecoding
        integration_test.go:148: executing (go1.23.0 test ./proto -test_lazy_unmarshal): exit status 1
            --- FAIL: TestHasExtensionNoAlloc (0.00s)
                --- FAIL: TestHasExtensionNoAlloc/Eager (0.00s)
                    extension_test.go:157: proto.HasExtension should not allocate, but allocated 1.00x per run
            FAIL
            FAIL	google.golang.org/protobuf/proto	0.179s
            FAIL
    --- FAIL: TestIntegration/Go1.23.0/LazyDecoding (5.61s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: pytorch
Issue: [export] Fail fast on pytorch with `aoti_load_package`
Labels: oncall: pt2,export-triaged,oncall: export

### 🐛 Describe the bug

When we use 
`aoti_compile_and_package` for GPU and then on another instance we use `aoti_load_package` without GPU it is failing internally at:

https://github.com/triton-lang/triton/blob/main/python/triton/runtime/driver.py#L8

As the message is a bit ambiguous
`raise RuntimeError(f"{len(actives)} active drivers ({actives}). There should only be one.")`

Can we fast and safely  fail in pytorch with a more user friendly message instead of triton internals?

### Versions

nightly

cc @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @angelayi @suo @ydwu4
Repository: langchain
Issue: Assertions not executed in test_stream_error_callback
Labels: 🤖:bug

### Checked other resources

- [x] I added a very descriptive title to this issue.
- [x] I searched the LangChain documentation with the integrated search.
- [x] I used the GitHub search to find a similar question and didn't find it.
- [x] I am sure that this is a bug in LangChain rather than my code.
- [x] The bug is not resolved by updating to the latest stable version of LangChain (or the specific integration package).

### Example Code

N/A

### Error Message and Stack Trace (if applicable)

_No response_

### Description

`test_stream_error_callback` has test code which is not executed.

```python
async def test_stream_error_callback() -> None:
    message = "test"

    def eval_response(callback: BaseFakeCallbackHandler, i: int) -> None:
        assert callback.errors == 1
        assert len(callback.errors_args) == 1
        llm_result: LLMResult = callback.errors_args[0]["kwargs"]["response"]
        if i == 0:
            assert llm_result.generations == []
        else:
            assert llm_result.generations[0][0].text == message[:i]

    for i in range(2):
        llm = FakeListChatModel(
            responses=[message],
            error_on_chunk_number=i,
        )
        with pytest.raises(FakeListChatModelError):
            cb_async = FakeAsyncCallbackHandler()
            async for _ in llm.astream("Dummy message", callbacks=[cb_async]):
                pass
            # !!! The code below is not executed
            eval_response(cb_async, i)

            cb_sync = FakeCallbackHandler()
            for _ in llm.stream("Dumy message", callbacks=[cb_sync]):
                pass

            eval_response(cb_sync, i)
```
when `llm.astream` is called it raises `FakeListChatModelError` and exits the `with` section without executing `eval_response` and the sync test.
This was detected when applying ruff rule PT012. See https://github.com/langchain-ai/langchain/pull/29381.

### System Info

N/A
Repository: ui
Issue: [bug]: Shadcn not recognising tailwind.config.js file from React+Vite project
Labels: bug

### Describe the bug

![Image](https://github.com/user-attachments/assets/25a65cf6-e03f-4143-9d14-6e3faa02b2f1)

I have all configuration for tailwind and other stuff
and tailwind is working in my project still this error.

![Image](https://github.com/user-attachments/assets/a569a320-f9e1-4696-ae00-2df8ed8cf3ff)

### Affected component/components

Installation Problem

### How to reproduce

S D:\shop-manage-react\shop-manage> npx shadcn@latest init
✔ Preflight checks.
✔ Verifying framework. Found Vite.
✖ Validating Tailwind CSS.
✔ Validating import alias.

No Tailwind CSS configuration found at D:\shop-manage-react\shop-manage.
It is likely you do not have Tailwind CSS installed or have an invalid configuration.
Install Tailwind CSS then try again.
Visit https://tailwindcss.com/docs/guides/vite to get started.

### Codesandbox/StackBlitz link

_No response_

### Logs

```bash

```

### System Info

```bash
{
  "name": "shop-manage",
  "private": true,
  "version": "0.0.0",
  "type": "module",
  "scripts": {
    "dev": "vite",
    "build": "vite build",
    "lint": "eslint .",
    "preview": "vite preview"
  },
  "dependencies": {
    "@tailwindcss/vite": "^4.0.0",
    "axios": "^1.7.9",
    "js-cookie": "^3.0.5",
    "react": "^18.3.1",
    "react-dom": "^18.3.1",
    "react-router-dom": "^7.1.3"
  },
  "devDependencies": {
    "@eslint/js": "^9.17.0",
    "@types/node": "^22.10.10",
    "@types/react": "^18.3.18",
    "@types/react-dom": "^18.3.5",
    "@vitejs/plugin-react": "^4.3.4",
    "autoprefixer": "^10.4.20",
    "eslint": "^9.17.0",
    "eslint-plugin-react": "^7.37.2",
    "eslint-plugin-react-hooks": "^5.0.0",
    "eslint-plugin-react-refresh": "^0.4.16",
    "globals": "^15.14.0",
    "postcss": "^8.5.1",
    "tailwindcss": "^4.0.0",
    "vite": "^6.0.5"
  }
}
```

### Before submitting

- [x] I've made research efforts and searched the documentation
- [x] I've searched for existing issues
Repository: vscode
Issue: Test compound logs and filtering in Output view
Labels: testplan-item

Refs: #237974 #237829 #237432

- [x] Mac @Tyriar
- [x] Win @bpasero
- [ ] Linux @TylerLeonhardt

Complexity: 5


[Create Issue](https://github.com/microsoft/vscode/issues/new?body=Testing+%23238846%0A%0A&assignees=sandy081)

---

### Filtering

You can now filter the content in the Output view. 

- Open any output view say `Git`
- Test filtering the content in the output view and make sure it is working as expected
  - Filter by Log Level
  - Filter by Category - Category of the log line is defined after the log level in square brackets.
  - Filter by Text

### Compound Output View

You can now view multiple logs in a single compound output view. VS Code already has OOB some compound output views: Window, Shared & Telemetry. You can also create one by selecting existing.

- Open Window log in Output View and set log level to Trace from `gear` icon next to the dropdown
- Go to extensions view and run some searches to Marketplace
- Validate that the network logs appear in the Window output
- Validate that the filter dropdown shows Network category. Note that other categories available in the dropdown are logs composed into this view.
- Test filtering (follows steps from above) in the Window output view is working as expected
- Test creating a custom compound log using the action `Add Compound Log...` available in the overflow menu of the Output view. 
- Test that the created compound log view is showing the data from all the logs you selected
- Test that the filtering this compound log view is working as expected
- Test that you can open the compound log in an editor or in an aux window using the actions available in the overflow menu

### Export & Import

You can now export and import the logs using the actions available in the overflow menu of the Output view

- Test **Save Output As...** and **Export Logs...** actions in the overflow menu are working as expected
- Import these exported logs using **Import Log...** action and test the log is imported correctly.
  - Test that the filtering the imported log is working as expected