sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: CupertinoSlidingSegmentedControl should support multiple selected segments
Labels: c: new feature,framework,f: cupertino,c: proposal,P3,team-design,triaged-design

### Use case

Per Apple's HIG best practices, a segmented control can have a [single selection or multiple selected segments](https://developer.apple.com/design/human-interface-guidelines/segmented-controls#Best-practices). As the API currently stands, CupertinoSlidingSegmentedControl can only support 1 selected segment. 


### Proposal

Instead of a single `groupValue` of type `T`, replicate Material's [SegmentedButton](https://api.flutter.dev/flutter/material/SegmentedButton-class.html) API which takes a `selected` parameter of `Set<T>`, allowing for multiple selected segments. 

Likely related to #43826
Repository: react
Issue: [React 19] Incorrect infered response type in server actions with React 19
Labels: React 19

## Summary

Server actions in Next.js return `Promise<void>` instead of the infered response type.

This is most likely a issue in react 19 or @types/react 19 since it works as exepected with both Next.js 14 and Next.js 15 and can only be reproduced when upgrading from React 18 to 19.

Example action:
https://github.com/alexanderalmstrom/next-15-server-actions/blob/main/src/app/actions.ts

`main` branch with React 19:
https://github.com/alexanderalmstrom/next-15-server-actions/tree/main

<img width="1057" alt="Skärmavbild 2024-12-14 kl  23 49 34" src="https://github.com/user-attachments/assets/4f82ecd0-6352-44c9-89d7-8d4e5f54b035" />

`react-18` branch with React 18.3.1 where the response is infered correctly with `Promise<{ message: string }>`
https://github.com/alexanderalmstrom/next-15-server-actions/tree/react-18

<img width="1062" alt="Skärmavbild 2024-12-14 kl  23 42 07" src="https://github.com/user-attachments/assets/bf68c072-c2cf-4993-b381-598bd17a746a" />

Both branches uses the same Next version 15.1.0 and the same server action.

I'm aware of the `useActionState` (previously called `useFormState`)...

```
"use client";

import { type ComponentProps, useActionState } from "react";
import { exampleFormActionState } from "../actions";

export default function FormWithActionState(props: ComponentProps<"form">) {
  const [state, action] = useActionState(exampleFormActionState, {
    message: "",
  });

  return (
    <form action={action} {...props}>
      <input type="text" name="name" />
      <button type="submit">Submit</button>
      {state.message && <p>{state.message}</p>}
    </form>
  );
}

```

but is it expected that the action should return `Promise<void>`?

<img width="1055" alt="Skärmavbild 2024-12-15 kl  00 20 04" src="https://github.com/user-attachments/assets/99a7ffc3-ac39-4818-afad-1e850caeb21b" />

and we have to type the state like this, instead of having the types infered automatically for us in typescript?

```
type FormState = {
  message: string;
};

export async function exampleFormActionState(
  prevState: FormState,
  formData: FormData
) {
  const name = formData.get("name");

  if (!name || typeof name !== "string") {
    return { message: "VALIDATION_ERROR" };
  }

  return { message: `Hello, ${name}!` };
}
```

The thing is, what if I don't want to use `useActionState`? Lets say that we pass the action as prop to the form element, and then use a`useFormStatus `and a pending state for the button. Then that's not possible because of this error.
Repository: PowerToys
Issue: Feature request - Save queries with name, Load the saved queries
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

User can save queries up to 5 with name as description and can load the saved queries when needed.

### Scenario when this would be used?

Currently the tool keeps the last query but it is replaced when new query runs. The additonal feature allows the user to save favorite query with value for replacement with some description as its name, and load to reuse. Probably the query is regular expression in most cases. 

### Supporting information

_No response_
Repository: PowerToys
Issue: "Remap a shortcut" not working
Labels: Issue-Bug,Product-Keyboard Shortcut Manager,Needs-Triage

### Microsoft PowerToys version

0.86.0

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

![Image](https://github.com/user-attachments/assets/807206d7-1864-4a85-b8aa-867593a0079e)


### ✔️ Expected Behavior

shortcuts of new letters to be entered when buttons pressed

### ❌ Actual Behavior

not working

### Other Software

_No response_
Repository: vscode
Issue: Incorrect indentation for TypeScript opening curly brace
Labels: bug,editor-autoindent

Does this issue occur when all extensions are disabled?: Yes

- VS Code Version: 1.96.0 and 1.97-0-insider
- OS Version: Windows 11 Pro 24H2 26100.2605

Steps to Reproduce:

In a TypeScript file, put your cursor immediately before an opening (left) curly brace and press Enter.  The curly brace will be indented, which is incorrect behavior.

![Image](https://github.com/user-attachments/assets/cf51ce02-70ee-4457-9f83-a641e36f180b)

![Image](https://github.com/user-attachments/assets/cadefdbf-91de-437f-a701-b71bd20538f9)

![Image](https://github.com/user-attachments/assets/d58e9bde-8f83-496f-a72c-4fe4a2d180c5)


This bug is similar to https://github.com/microsoft/vscode/issues/216737 but not the same; that issue has been fixed, as you can see below:

![Image](https://github.com/user-attachments/assets/544071fd-2341-4d42-a70e-e515ae159221)
Repository: vscode
Issue: Profiles broke in recent VSCode WSL
Labels: info-needed

<!-- ⚠️⚠️ 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.0 and earlier
- OS Version: Windows_NT x64 10.0.22635

In recent VSCode versions, profiles no longer work correctly when connected to WSL.

* Primary Side Panel does not save which view tab is currently open (can’t quite reproduce)
* Steps to Reproduce:
  1. Connect VSCode to WSL
  2. Use profile editor UI to copy the Default profile
     * ❎ the Editor cannot save
Repository: PowerToys
Issue: The Mouser Highlighter appears to be of different sizes on monitors with varying DPI settings.
Labels: Issue-Bug,Needs-Triage,Product-Mouse Utilities

### Microsoft PowerToys version

v0.86.0

### Installation method

PowerToys auto-update

### Running as admin

None

### Area(s) with issue?

Mouse Utilities

### Steps to reproduce

used the Mouser Highlighter  feature

### ✔️ Expected Behavior

I hope that they will actually look the same size visually.


### ❌ Actual Behavior

I'm currently using two monitors with different DPI settings and have encountered an issue where a circle with a radius set to 50px appears visually different on each display. While it may not be a bug, the inconsistency is less than ideal.
Thanks.![Image](https://github.com/user-attachments/assets/5b05cb1b-d15e-4ad8-aebc-816d2728a008)
![Image](https://github.com/user-attachments/assets/6b061f5b-6dc9-42f4-b49d-3d9c96f095bc)

### Other Software

win11
Repository: ollama
Issue: Digest mismatch for llama3.3
Labels: bug

### What is the issue?

I've tried this several times - same result every time:

~ took 43s ❯ ollama run llama3.3
pulling manifest
pulling 4824460d29f2... 100% ▕████████████████████████████████████▏  42 GB
pulling 948af2743fc7... 100% ▕████████████████████████████████████▏ 1.5 KB
pulling bc371a43ce90... 100% ▕████████████████████████████████████▏ 7.6 KB
pulling 53a87df39647... 100% ▕████████████████████████████████████▏ 5.6 KB
pulling 56bb8bd477a5... 100% ▕████████████████████████████████████▏   96 B
pulling c7091aa45e9b... 100% ▕████████████████████████████████████▏  562 B
verifying sha256 digest
Error: digest mismatch, file must be downloaded again: want sha256:4824460d29f2058aaf6e1118a63a7a197a09bed509f0e7d4e2efb1ee273b447d, got sha256:4e7ab3e3f5fba9ba2d72787c3e5a8e0d4931059bae000821f1278753855af7ac


### OS

Linux

### GPU

Nvidia

### CPU

AMD

### Ollama version

0.5.1
Repository: vscode
Issue: Confirm window before close setting: separate window vs app
Labels: feature-request,workbench-window

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->

I'd like to have two separate "confirm before close" settings for Window close (Cmd+Shift+W) **and** App close (Cmd+Q). Right now the current setting (`"window.confirmBeforeClose": "keyboardOnly"`) sets the behavior for both.

I like this confirmation dialog for accidental "Cmd+Q"s but not for "Cmd+Shift+W"s. I usually have several VSCode windows open and I very rarely want to close them all at the same time. So confirm dialog is useful in this case.

However I often close/reopen instances quite often. And confirmation dialog gets in the way.
Repository: ollama
Issue: version set incorrectly on local build without primary repo remote and tags - results in pull failure for newer models
Labels: bug,build

### What is the issue?

Following the [docs](https://github.com/ollama/ollama/blob/main/docs/development.md#macos) to build Ollama from source, then trying to pull llama3.1 results in a refusal stating the Ollama version is too old.

```shell
$ git checkout feature/my-feature-in-development
$ make -j $(expr $(nproc) / 2)
...
$ ollama pull llama3.1:8b-instruct-q6_K

pulling manifest
Error: pull model manifest: 412:

The model you are attempting to pull requires a newer version of Ollama.

Please download the latest version at:

	https://ollama.com/download

$ ollama -v
ollama version is 4d52e5d-dirty
```

### OS

Linux, macOS

### GPU

Nvidia, Apple

### CPU

AMD, Apple

### Ollama version

4d52e5d-dirty
Repository: rust
Issue: Confusing suggestion from self import
Labels: A-diagnostics,T-compiler

### Code

```Rust
mod foo {
    use self::Bar;

    pub struct Bar;
}

fn main() {}
```

### Current output

```Shell
error[E0255]: the name `Bar` is defined multiple times
 --> src/main.rs:4:5
  |
2 |     use self::Bar;
  |         --------- previous import of the type `Bar` here
3 |
4 |     pub struct Bar;
  |     ^^^^^^^^^^^^^^^ `Bar` redefined here
  |
  = note: `Bar` must be defined only once in the type namespace of this module
help: you can use `as` to change the binding name of the import
  |
2 |     use self::Bar as OtherBar;
  |                   +++++++++++
```

### Desired output

```Shell
error[E0255]: the name `Bar` is defined multiple times
 --> src/main.rs:4:5
  |
2 |     use self::Bar;
  |         --------- previous import of the type `Bar` here
3 |
4 |     pub struct Bar;
  |     ^^^^^^^^^^^^^^^ `Bar` redefined here
  |
  = note: `Bar` must be defined only once in the type namespace of this module
help: Remove redundant recursive import
  |
2 |   - use self::Bar
  |
```

### Rationale and extra context

if you are doing a self import it is most likely that you made a change in your code that made it redundant

### Other cases

```Rust

```

### Rust Version

```Shell
rustc 1.83.0 (90b35a623 2024-11-26)
binary: rustc
commit-hash: 90b35a6239c3d8bdabc530a6a0816f7ff89a0aaf
commit-date: 2024-11-26
host: x86_64-unknown-linux-gnu
release: 1.83.0
LLVM version: 19.1.1
```

### Anything else?

_No response_
Repository: PowerToys
Issue: Preview Pane to show additional file information
Labels: Idea-Enhancement,Product-File Explorer,Needs-Triage

### Description of the new feature / enhancement

The preview pane before Windows 10 was a pleasure to use. I am still used to it being at the bottom of the Explorer window, not on the right as it is currently. I wish we still had the option to change it from the right side to the bottom. 

Lately, you guys have added additional file types for preview, which is helpful. However, one important feature I'm still missing is the ability to view additional file information and properties. This was particularly useful when flipping through files or clips, as it allowed me to see the dimensions and resolution of photos, the video resolution and frames per second, and the file size. Additionally, information such as the camera model and settings (ISO, aperture, etc.) would be displayed. Having all this data in one place was incredibly useful, and I sorely miss it. 

My question is whether there is a possibility of adding all the file information and properties to the preview pane, and perhaps, as a bonus, adding the option to move it to the bottom of the window.

### Scenario when this would be used?

It's extremely useful

### Supporting information

If you have ever used the preview pane before Windows 10, you would understand it for yourself.
Repository: rust
Issue: Tracking Issue for m68k_target_feature
Labels: C-tracking-issue,O-motorola68k,A-target-feature

<!--
NOTE: For library features, please use the "Library Tracking Issue" template instead.

Thank you for creating a tracking issue! 📜 Tracking issues are for tracking a
feature from implementation to stabilisation. Make sure to include the relevant
RFC for the feature if it has one. Otherwise provide a short summary of the
feature and link any relevant PRs or issues, and remove any sections that are
not relevant to the feature.

Remember to add team labels to the tracking issue.
For a language team feature, this would e.g., be `T-lang`.
Such a feature should also be labeled with e.g., `F-my_feature`.
This label is used to associate issues (e.g., bugs and design questions) to the feature.
-->

This is a tracking issue for M68k architecture specific part of https://github.com/rust-lang/rust/issues/44839 (RFC 2045 (rust-lang/rfcs#2045)).
The feature gate for the issue is `#![feature(m68k_target_feature)]`.

### About tracking issues

Tracking issues are used to record the overall progress of implementation.
They are also used as hubs connecting to other relevant issues, e.g., bugs or open design questions.
A tracking issue is however *not* meant for large scale discussion, questions, or bug reports about a feature.
Instead, open a dedicated issue for the specific matter and add the relevant feature gate label.
Discussion comments will get marked as off-topic or deleted.
Repeated discussions on the tracking issue may lead to the tracking issue getting locked.

### Steps
<!--
Include each step required to complete the feature. Typically this is a PR
implementing a feature, followed by a PR that stabilises the feature. However
for larger features an implementation could be broken up into multiple PRs.
-->

- [ ] Implementation https://github.com/rust-lang/rust/pull/134329
- [ ] Stabilization PR ([see instructions on rustc-dev-guide][stabilization-guide])

[stabilization-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#stabilization-pr
[doc-guide]: https://rustc-dev-guide.rust-lang.org/stabilization_guide.html#documentation-prs
[nightly-style-procedure]: https://github.com/rust-lang/style-team/blob/main/nightly-style-procedure.md 
[Style Guide]: https://github.com/rust-lang/rust/tree/master/src/doc/style-guide

### Unresolved Questions
<!--
Include any open questions that need to be answered before the feature can be
stabilised.
-->

- `isa-68000` is baseline of this architecture, so it may not actually need to be expressed as a target feature.

### Implementation history

<!--
Include a list of all the PRs that were involved in implementing the feature.
-->

- `isa-*`: https://github.com/rust-lang/rust/pull/134329

@rustbot label +O-motorola68k +A-target-feature
Repository: flutter
Issue: [pigeon][swift] Make `PigeonError` Class Conform to `Sendable`
Labels: package,c: proposal,team-ecosystem,p: pigeon,P2,triaged-ecosystem

Related Issues:  
- https://github.com/flutter/flutter/issues/140439  
- https://github.com/flutter/flutter/issues/147283

### Use case

`Sendable` was introduced in Swift 5.5 to ensure thread-safe interactions in concurrent code. With the `Swift 6` language mode in Swift 6.0 (Xcode 16), stricter conditions for `Sendable` conformance are enforced. Although newer Swift compiler can compile in `Swift 5` mode, many developers prefer the stricter safety guarantees of `Swift 6`.

Pigeon, a code generator for Dart and native platform communication, enables seamless cross-platform development. However, the `PigeonError` class currently does not conform to `Sendable`, leading to compilation errors in `Swift 6` mode and blocking developers from adopting the latest Swift concurrency features.

Example error:
```
Stored property 'details' of 'Sendable'-conforming class 'PigeonError' has non-sendable type 'Any?'
```

### Proposal

The current `PigeonError` class is a simple implementation of the `Error` protocol:

```swift
/// Error class for passing custom error details to the Dart side.
final class PigeonError: Error {
  let code: String
  let message: String?
  let details: Any?

  init(code: String, message: String?, details: Any?) {
    self.code = code
    self.message = message
    self.details = details
  }

  var localizedDescription: String {
    return "PigeonError(code: \(code), message: \(message ?? "<nil>"), details: \(details ?? "<nil>"))"
  }
}
```

To make the class compatible with `Swift 6.0` mode, I propose changing the `details` property type from `Any?` to `Sendable?`. This ensures the class conforms to `Sendable` since:
- The `Error` protocol already conforms to `Sendable`.
- All other properties (`String` and `Optional`) are `Sendable`.

This change introduces backward incompatibility because of the `details` type change. However, most existing use cases of `PigeonError` involve small, well-defined payloads, so migration should be straightforward. Developers can update their code by ensuring objects passed to `details` conform to `Sendable`.
Repository: vscode
Issue: When the hover is focused, keyboard shortcut to autofix (ctrl + .) does not work
Labels: polish,editor-hover

<!-- ⚠️⚠️ 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. -->
When the hover is focused with pressing `ctrl + k ctrl + I` twice, the autofix shortcut no longer works. Maybe this is because when the hover is focused, the problem is no longer being focused. However, this behavior does not follow intuition and it would be nice to still be able to use the autofix shortcut key after the hover is focused.

vscode version: 1.96.0
Repository: deno
Issue: NPM compat: cannot use `npm:@grotto/logysia`
Labels: bug,types

Version: Deno 2.1.4

## Reproduction 

```ts
import { Elysia, t } from "npm:elysia"
import { swagger } from "npm:@elysiajs/swagger"
import { logger } from "npm:@grotto/logysia"

const app = new Elysia()
  .use(logger()) // comment this out to make ID type check
  .use(swagger())
  .get("/user/:id", ({ params: { id } }) => id, {
    params: t.Object({
      id: t.Numeric(),
    }),
  })

export default app
```

## `deno run main.ts`
```ts
$ deno run main.ts                                                                                                        844ms  2024년 12월 15일 (일) 오후 05시 23분 56초error: TypeScript files are not supported in npm packages: file:///home/scarf/.cache/deno/npm/registry.npmjs.org/@grotto/logysia/0.1.6/src/index.ts
```

TypeScript files are not supported in npm package.

## `deno check main.ts`

```sh
deno check main.ts                                                                                                              2024년 12월 15일 (일) 오후 05시 22분 20초Check file:///home/scarf/repo/etc/elysia/main.ts
error: TS7031 [ERROR]: Binding element 'id' implicitly has an 'any' type.
  .get("/user/:id", ({ params: { id } }) => id, {
                                 ~~
    at file:///home/scarf/repo/etc/elysia/main.ts:8:34
```

type of `id` is correctly resolved as number on node, but `any` in deno.
Repository: deno
Issue: Using `Buffer` no longer works after upgrading to Deno v2
Labels: needs info,compile,node compat

Version: Deno 2+

Hello, after upgrading to Deno v2, our use of Buffer no longer works. We get the following error:

```sh
error: TS2576 [ERROR]: Property 'from' does not exist on type 'Buffer'. Did you mean to access the static member 'Buffer.from' instead?
    Buffer.from(data, 'base64').toString('utf-8')
```
We are importing with 
```ts
import { Buffer } from 'buffer';
```
```json
{
  "imports": {
    "buffer": "node:buffer",
  }
}
```
If also tried `https://deno.land/std/io/buffer.ts`  and `@std/io/buffer`
Repository: vscode
Issue: Web VSCode can't load audio files for preview in Safari
Labels: bug,help wanted,web,safari

<!-- ⚠️⚠️ 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: vscode.dev 1.96.0 (138f619c86f1199955d53b4166bef66ef252935c)
- OS Version:  macOS 15.2 with Safari 18.2 (Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.2 Safari/605.1.15)

Steps to Reproduce:

1. Use vscode.dev to connect to a remote tunnel in Safari
2. Open a .wav file for preview
3. This error shows in the preview window
<img width="375" alt="Image" src="https://github.com/user-attachments/assets/f81214fb-4f00-454d-9bf7-9f4fe80c478b" />

This issue is Safari specific. It doesn't occur in Chrome.
Repository: go
Issue: govulncheck-action: Support using a later patch than go directive patch version in go.mod
Labels: NeedsInvestigation,vulncheck or vulndb

### Go version

n/a

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

```shell
n/a
```


### What did you do?

want to use later golang than go.mod but compatible with go.mod

Support using a later patch release than what's in go.mod

Please ensure the action inherits https://github.com/actions/setup-go/issues/481 when implemented.

### What did you see happen?

1.22.0 go.mod results in 1.22.0 being used and no option to use later 1.22

### What did you expect to see?

1.22.0 go.mod should use 1.22.7+ or latest available compatible with 1.22.0