sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: [Release] Update release documentation
Labels: team-release

As part of regular release engineering maintenance we need to ensure release documentation is accurate and up-to-date. This issue tracks the verification and updating of these documents.

Once a document is verified and updated, please check the corresponding box.  If a change is made, please reference the PR.

- [ ] [Bad-Builds.md](https://github.com/flutter/flutter/blob/master/docs/releases/Bad-Builds.md)
- [ ] [Flutter-Cherrypick-Process.md](https://github.com/flutter/flutter/blob/master/docs/releases/Flutter-Cherrypick-Process.md)
- [ ] [Flutter-build-release-channels.md](https://github.com/flutter/flutter/blob/master/docs/releases/Flutter-build-release-channels.md)
- [ ] https://github.com/flutter/flutter/blob/master/docs/releases/Hotfix-Documentation-Best-Practices.md
- [ ] https://github.com/flutter/flutter/blob/master/docs/releases/Quality-Assurance.md
- [ ] [Release-process.md](https://github.com/flutter/flutter/blob/master/docs/releases/Release-process.md)
- [ ] [Release-versioning.md](https://github.com/flutter/flutter/blob/master/docs/releases/Release-versioning.md)
- [ ] [Where's-my-commit.md](https://github.com/flutter/flutter/blob/master/docs/releases/Where's-my-commit.md)
Repository: ollama
Issue: Pulling models from private OCI Registries
Labels: feature request

According to #2388 it should be possible to push and pull models to a Docker/OCI registry (without authentication). 

Even though it's an unsupported feature, I find it very useful and would like to contribute a short description how to do this.

Potential use cases are

- organisation-internal registries for orgs that limit internet access,
- serving private models, 
- running Ollama on air gapped systems, and
- saving bandwidth and download time at edge locations.

I've tried it with a local docker registry: Pushing seems to work, pulling of the manifest works, as well, but pulling the blobs apparently did not work. Here is what I've tried:

Run a local docker registry v2:

```bash
docker run -d -p 5000:5000 --restart=always --name registry registry:2
```

Copy a model and push it to the registry:

```bash
ollama cp phi localhost:5000/mitja/phi
ollama push localhost:5000/mitja/phi --insecure
```

Remove the copied model and pull it, again (that works, I believe because the blobs from the original phi model are still there):

```bash
ollama rm localhost:5000/mitja/phi
ollama pull localhost:5000/mitja/phi --insecure
```

Remove both the copied and the original model, then pull the model from the private registry, again (does not work):

```bash
ollama rm phi
ollama rm localhost:5000/mitja/phi
ollama pull localhost:5000/mitja/phi --insecure
```

Runs into `Error: http: no Location header in response`

Pull the original model, then the copied model (works):

```bash
ollama pull phi
ollama pull localhost:5000/mitja/phi --insecure
ollama run localhost:5000/mitja/phi
```

Remove the registry container to clean up:

```bash
docker stop /registry
docker rm /registry
```

Did I miss a step or did I make a mistake, or is pushing/pulling the blobs not yet possible?
Repository: excalidraw
Issue: text not synced if pasted into wysiwyg
Labels: bug,collaboration

in collab (affects E+ too):

1. enter wysiwyg editor
2. paste text that's in font and code range that aren't currently already rendered on canvas
3. the text element is not synced to other client (even after confirmation)

/cc @Mrazator
Repository: godot
Issue: Tileset collision polygon does not appear when clicking away after drawing the polygon
Labels: bug,topic:editor,topic:2d

### Tested versions

- Reproduce in v4.3.stable.official [77dcf97d8]

### System information

Godot v4.3.stable - Windows 10.0.22631 - GLES3 (Compatibility) - AMD Radeon RX 6750 XT (Advanced Micro Devices, Inc.; 32.0.12011.1036) - 12th Gen Intel(R) Core(TM) i5-12600KF (16 Threads)

### Issue description

When clicking away after drawing the collision polygon, it will not show up on the tile in the tileset. If you click the square surrounding the tile in the drawing area it will show the polygon in the tileset over that tile.

Note: Here I've been using Compatibility but this also happens in Forward+.

https://github.com/user-attachments/assets/1e9ce277-1a7b-445c-ab8b-3ef06a35eb6b



### Steps to reproduce

1. Create a tileset
2. Add a Physics Layer
3. Press the "Add polygon tool" and start drawing the polygon
4. Click outside the drawing area after enclosing the polygon - Polygon is missing
5. Click the gray (or whatever it's color is on your system) area surrounding the tile in the drawing area - Polygon is present

### Minimal reproduction project (MRP)

[tileset_collision_polygon_bug.zip](https://github.com/user-attachments/files/17421413/tileset_collision_polygon_bug.zip)
Repository: kubernetes
Issue: `kubeapiservertesting.StartTestServer` mutates global state and prevents parallel tests within the same package
Labels: sig/api-machinery,triage/accepted

The following recent changes make it hard to run parallel integration tests from within the same package (the `utilruntime.Must` call will occasionally `panic`):

https://github.com/kubernetes/kubernetes/blob/632ed16e002d87fa7166a8f4ca1dc48d4f0a9725/cmd/kube-apiserver/app/testing/testserver.go#L196-L208

This can be hacked around but adding locks (though I suspect that does not cover all cases):

https://github.com/kubernetes/kubernetes/blob/632ed16e002d87fa7166a8f4ca1dc48d4f0a9725/test/integration/controlplane/transformation/transformation_test.go#L151-L158

Note that while many integration tests cannot be run in parallel because the test logic itself mutates global state, the base `kubeapiservertesting.StartTestServer` should support running parallel tests for the cases in which the test logic itself does not need to mutate global state.

cc @deads2k @jpbetz @liggitt 

/sig api-machinery
/triage accepted
Repository: svelte
Issue: Feat: [Types] Improves "svelte/element" with directive-free types, and a configurable children
Labels: types / typescript

### Describe the problem

The module "svelte/elements" provides the definitions of HTML attributes that can be used to declare props to spread in a component that "wrap" a HTML element.

For example for a component `Button`, using directly the type `HTMLButtonAttributes`
```svelte
<script lang="ts">
    import type { HTMLButtonAttributes } from 'svelte/elements';

    let { children, ...rest } : HTMLButtonAttributes = $props();
</script>

<button {...rest}>
    {@render children?.()}
</button>
```

Or via the equivalent using `SvelteHTMLElements `
```svelte
<script lang="ts">
    import type { SvelteHTMLElements } from 'svelte/elements';

    let { children, ...rest } : SvelteHTMLElements['button'] = $props();
</script>

<button {...rest}>
    {@render children?.()}
</button>
```

But there are 2 flaws : 
* This include the definition of `bind:` and `on:` directives, which are therefore proposed by autocompletion
* The children is defined with zero parameter, and this cannot be changed easily.

In order to remove the `bind:`/`on:` directives, II need to write something like that : 
```ts
    let { children, ...rest } : Omit<HTMLButtonAttributes, `bind:${string}` | `on:${string}`> = $props();
```

And if I need to specify a parameter for the children snippet, I have to write : 
```ts
    let { children, ...rest } : Omit<HTMLButtonAttributes, `bind:${string}` | `on:${string}` | 'children'>
        & { children?: Snippet<[number]> } = $props();
```



### Describe the proposed solution

It would be nice if Svelte 5 had an official type to handle this in "svelte/elements".

Something like this might work :
```ts
export type SvelteHTMLProps<TagName extends string, Parameters extends unknown[] = []> = {
	children?: import('svelte').Snippet<Parameters>;
} & Omit<SvelteHTMLElements[TagName], `bind:${string}` | `on:${string}` | `children`>;
```

So we can use `SvelteHTMLProps<'button'>`in order to define our Button component : 
```svelte
<script lang="ts">
    import type { SvelteHTMLProps } from 'svelte/elements';

    let { children, ...rest } : SvelteHTMLProps<'button'> = $props();
</script>

<button {...rest}>
    {@render children?.()}
</button>
```

Or `SvelteHTMLProps<'button', [number]>`to define the children parameter type : 
```svelte
<script lang="ts">
    import type { SvelteHTMLProps } from 'svelte/elements';

    let { children, onclick, ...rest } : SvelteHTMLProps<'button', [number]> = $props();

    let count = $state(0);

    function countClick(evt) {
        count++;
        onclick?.(evt);
    }
</script>

<button onclick={countClick} {...rest}>
    {@render children?.(count)}
</button> 
```

### Importance

nice to have
Repository: kubernetes
Issue: Race when scheduling statefulset pods with local PV, resulting in pods pending forever
Labels: kind/bug,sig/scheduling,lifecycle/stale,needs-triage

### What happened?

A statefulset has a volumeclaimtemplate which uses a local PV storage class. The PVs created by this storage class are tightly bound to a single node.

In this example lets say that ordinal 0 of the statefulset is running on node A with a PVC which is bound to a PV on node A as well.

1. delete the PVC for ordinal 0
2. immediately after, delete the pod for ordinal 0
3. the new pod for ordinal 0 gets scheduled on node A
4. the new PVC/PV for ordinal 0 gets bound to node B
5. the new pod is stuck in Pending state forever since the new PVC is only available on node B

I believe the issue is that the scheduler when scheduling the new pod is looking at the OLD PVC object which is the progress of being deleted. Since PVCs are referenced by name and statefulsets use consistent naming for PVCs, the scheduler can use the old PVC definition when doing Filter decisions.
This can happen if the pod informer/watcher in the scheduler is ahead of the pvc informer/watcher.

### What did you expect to happen?

The scheduler should not place pods using local PVs in an unschedulable state.

### How can we reproduce it (as minimally and precisely as possible)?

Create a statefulset with a local PVC claimref. Delete the pod and pvc for an ordinal at the same time. Retry until the pod is stuck in Pending state.

### Anything else we need to know?

Thinking about possible solutions:
1. in the scheduler, do not use deleting PVCs/PVs when placing the pod. this does not fix the race but it most likely reduces the frequency
2. in the scheduler, form a consistent snapshot where all objects used in scheduling decisions are from the same ETCD revision (I tried to see if there is anything in the k8s project that does this but I couldn't find anything)
3. in the statefulset controller, create an owner reference on PVCs to owning pod. during scheduling, if the PVC is not owned by the pod being scheduled, backoff.

### Kubernetes version

<details>

```console
$ kubectl version
1.29.9
```

</details>


### Cloud provider

<details>

</details>


### OS version

<details>

```console
# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here
```

</details>


### Install tools

<details>

</details>


### Container runtime (CRI) and version (if applicable)

<details>

</details>


### Related plugins (CNI, CSI, ...) and versions (if applicable)

<details>

</details>
Repository: excalidraw
Issue: Failure to Automatically Read and Save to Existing Excalidraw Canvas File After Reload
Labels: bug

When saving an Excalidraw canvas file and reloading the webpage, the app fails to automatically read from the previously saved file. 

After reloading, users cannot save changes to the existing file. Instead, they must save to a new file or manually reopen the existing one to continue working
Repository: pytorch
Issue: Adam optimizer without first moment estimate, for less vram
Labels: module: optimizer,triaged,actionable

### 🚀 The feature, motivation and pitch

Many GANs like StyleGan use the Adam optimizer with betas=(0.0, 0.999), this means that the first moment estimate is disabled but it still uses a lot of vram for it, is it possible to add an option to stop this from happening and reduce vram usage?

### Alternatives

_No response_

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @vincentqb @janeyx99 @crcrpar
Repository: ui
Issue: [bug]: breaking changes for calendar using react-day-picker 9.1.4
Labels: bug

### Describe the bug

As it is, the calendar component breaks, if you update react-day-picker to `9.1.4`.
I discovered this while I initially wanted to try out the new timeZone feature.

More details on what may be affected are provided in the docs:
https://daypicker.dev/upgrading

Styles & custom components are affected.

Example Quote from the migration guide
```
//Broken
IconLeft: ({ ...props }) => <ChevronLeft className="h-4 w-4" />,
IconRight: ({ ...props }) => <ChevronRight className="h-4 w-4" />,

//Fix
Chevron(props) {
  if (props.orientation === 'left') {
    return <ChevronLeft className="h-4 w-4" />;
  }
  return <ChevronRight className="h-4 w-4" />;
},
  }}
  />
```

Please let me know if you need additional information.

### Affected component/components

calendar

### How to reproduce

Update react-day-picker from `8.10.1` to `9.1.4`

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Windows/Chrome
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: PowerToys
Issue: PowerToys Settings not showing window properly
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.85.1

### Installation method

Microsoft Store

### Running as admin

No

### Area(s) with issue?

Welcome / PowerToys Tour window

### Steps to reproduce

I've installed noramlly by Winget at first when i got this error, then I removed all files and unistalled all, to try the install by MS-Store, but I'm getting the same issue all the ways i tried

### ✔️ Expected Behavior

The settings window sshould show all the stuff

### ❌ Actual Behavior

Nothing is being showed, just the whell icon a little on top, the image above is the settings "opened"
![Image](https://github.com/user-attachments/assets/458d812c-68e8-4113-b6b4-501e65ee9ab0)


### Other Software

_No response_
Repository: rust
Issue: LUB coercions can't combine unsafe fn item with safe fn item or pointer
Labels: C-bug,A-coercions,T-types

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.
-->

I tried this code: [playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=e3e838d025de542f3773ff98ab7e4488)

```rust
fn safe_fn() {}
unsafe fn unsafe_fn() {}

fn lub() {
    // safe fn item + unsafe fn item
    // doesn't work
    let _ = if true { safe_fn } else { unsafe_fn };

    // safe fn ptr + unsafe fn item
    // doesn't work
    let _ = if true { safe_fn as fn() } else { unsafe_fn };

    // safe fn item + unsafe fn ptr
    // works
    let _ = if true { safe_fn } else { unsafe_fn as unsafe fn() };

    // closure + unsafe fn item
    // works
    let _ = if true { || {} } else { unsafe_fn };
}
```

I expected to see this happen: I expected the safe fn item and unsafe fn item to combine to an unsafe fn ptr, especially since the closure and unsafe fn item do combine to an unsafe fn ptr.

Instead, this happened:

```
error[E0308]: `if` and `else` have incompatible types
 --> src/lib.rs:7:40
  |
7 |     let _ = if true { safe_fn } else { unsafe_fn };
  |                       -------          ^^^^^^^^^ expected safe fn, found unsafe fn
  |                       |
  |                       expected because of this
  |
  = note: expected fn item `fn() {safe_fn}`
             found fn item `unsafe fn() {unsafe_fn}`

error[E0308]: `if` and `else` have incompatible types
  --> src/lib.rs:11:48
   |
11 |     let _ = if true { safe_fn as fn() } else { unsafe_fn };
   |                       ---------------          ^^^^^^^^^ expected safe fn, found unsafe fn
   |                       |
   |                       expected because of this
   |
   = note: expected fn pointer `fn()`
                 found fn item `unsafe fn() {unsafe_fn}`
   = note: unsafe functions cannot be coerced into safe function pointers
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

playground nightly
```
Build using the Nightly version: 1.84.0-nightly

(2024-10-16 798fb83f7d24e31b16ac)
```

@rustbot label A-coercions T-types
Repository: vscode
Issue: Have a setting to always delete untitled workspaces on close
Labels: feature-request,workbench-multiroot

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

Version: 1.94.2 (user setup)
Commit: 384ff7382de624fb94dbaf6da11977bba1ecd427
Date: 2024-10-09T16:08:44.566Z
Electron: 30.5.1
ElectronBuildId: 10262041
Chromium: 124.0.6367.243
Node.js: 20.16.0
V8: 12.4.254.20-electron.0
OS: Windows_NT x64 10.0.19045


Steps to Reproduce:

1. Close all VSCode windows
2. Open folder in VSCode via Windows context menu ("Open with Code")
3. Add another folder to the workspace to create an untitled workspace
4. Close VSCode
5. Open the same folder in VSCode via Windows context menu ("Open with Code")

You will now have two windows open. No matter if you have the "Confirm Save Untitled Workspace" setting enabled or not.



With those two windows open, what you do next affects how VSCode functions:

Scenario A> If you close the window with the untitled workspace FIRST, it will ask you if you want to save the workspace. If you check the box to "Always discard untitled workspaces without asking" then you will not get this window anymore, but steps 1 through 5 still produce the same result.

Scenario B> If you close the single folder window first, and then close the untitled workspace window, you will not get a popup asking you if you want to save the workspace. Opening another folder in VSCode will open two windows again.


Result:
If the window with the untitled workspace is the LAST window to close, it will never ask you if you want to save the untitled workspace and will ALWAYS save it no matter what the setting is.

If the window with the untitled workspace is NOT the last window to close, it will ask you if you want to discard the workspace if the setting is not enabled to always discard untitled workspaces, or it will properly discard the workspace if the setting is enabled.


This is a bug. The functionality of VSCode changes depending on whether the untitled workspace window is closed last or not and it ignores the setting unless there are other windows open.
Repository: neovim
Issue: windows: `nvim.exe` exits with code -1073741819 immediately after startup
Labels: bug,platform:windows,bug-crash,startup

### Problem

when run `nvim`, cmd is cleared and only a new prompt at the end of the cmd screen, pressing more enter key will cause the cmd to crash (dev version will directly crash cmd when press enter or run echo %ERRORLEVEL% after run nvim)
both 0.10.2 and dev version have this issue

in the picture, the next ran command of `echo %ERRORLEVEL%` also is suppressed by this issue but only outputted its result `-1073741819`

![Image](https://github.com/user-attachments/assets/bd22a156-906c-409f-ae89-c4c1ef0fe788)


### Steps to reproduce

open a brand new cmd window,
run nvim.exe

### Expected behavior

nvim starts to run 

### Nvim version (nvim -v)

0.10.2 and dev

### Vim (not Nvim) behaves the same?

no,  vim 8.2.227

### Operating system/version

win10 1803

### Terminal name/version

cmd

### $TERM environment variable

na

### Installation

zip
Repository: deno
Issue: Feat: Configure permission profiles to shorten task commands, like `deno run --permission-profile main-script main.ts`
Labels: suggestion,task runner

Task commands for a simple application look like this:

```json
{
  "tasks": {
    "start": "deno run --allow-env --allow-read --allow-run npm:concurrently 'deno run server' 'deno run bundle'",
    "bundle": "deno run --allow-env --allow-read --allow-run npm:esbuild src/main.ts --watch --bundle --outfile=public/main.bundle.js",
    "serve": "deno serve --allow-env --allow-sys --allow-net --allow-read --watch src/server.ts"
  }
}
```

As I'm sure others have noted, this is quite verbose and it's difficult to read or edit the end of the command, which is what I usually care about. 

I'm proposing a new configuration section and a new CLI flag for `deno run` and `deno serve`, `--permission-profile` or `-P`, to define permission profiles for improved readability and reduced repetition:

```json
{
  "tasks": {
    "start": "deno run -P tool npm:concurrently 'deno run server' 'deno run bundle'",
    "bundle": "deno run -P tool npm:esbuild src/main.ts --watch --bundle --outfile=public/main.bundle.js",
    "serve": "deno serve -P server --watch src/server.ts"
  },
  "permissionProfiles": {
    "tool": "--allow-env --allow-read --allow-run",
    "server": "--allow-env --allow-sys --allow-net --allow-read"
  }
}

```
Repository: flutter
Issue: [Flutter GPU] Use unsigned Dart FFI types where appropriate.
Labels: engine,c: proposal,P2,team-engine,triaged-engine,flutter-gpu

Dart FFI supports unsigned types like Uint32. So we should use those instead of int types when passing things like enums to the engine.
Repository: PowerToys
Issue: PowerToys tray icon missing after upgrade to Windows 11 Home 24H2.
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.85.1

### Installation method

GitHub

### Running as admin

Yes

### Area(s) with issue?

System tray interaction

### Steps to reproduce

Update Windows 11 Home 23H PC to Windows 11 Home 24H2. (Without NPU).
(Optionally: uninstall PowerToys usings winget, and install it system wide using installed from GitHub)
Restart computer

### ✔️ Expected Behavior

PowerToys tray icon is displaying.

### ❌ Actual Behavior

PowerToys tray icon is not displaying.
![Image](https://github.com/user-attachments/assets/85a9548f-0a85-49d2-bf07-a39fdd449826)


### Other Software

After every boot, I get a windows update screen with the message: to have a moment of patience.
All PowerToys features are working.