sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: rustc doesn't infer that the future of a recursive `async fn` is `Send`.
Labels: C-bug,T-types

(Note: this bug is *not* about recursion in asynchronous functions being limited because futures of async functions cannot contain a copy of themselves.)

I would expect this code to compile successfully:

```rust
use std::future::Future;

pub async fn recur(depth: usize) {
    if depth == 0 {
        return;
    }
    spawn(recur(depth - 1));
}

pub fn spawn(_future: impl Future + Send + 'static) { }
```

Instead, rustc complains:

```
error[E0283]: type annotations needed: cannot satisfy `impl Future<Output = ()>: Send`
  --> recursive/src/lib.rs:7:5
   |
7  |     spawn(recur(depth - 1));
   |     ^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: cannot satisfy `impl Future<Output = ()>: Send`
note: required by a bound in `spawn`
  --> recursive/src/lib.rs:10:37
   |
10 | pub fn spawn(_future: impl Future + Send + 'static) { }
   |                                     ^^^^ required by this bound in `spawn`

For more information about this error, try `rustc --explain E0283`.
error: could not compile `recursive` (lib) due to 1 previous error
```

The program compiles fine if I pass `RUSTFLAGS=-Znext-solver` to nightly rustc. I wasn't able to find any existing issues that seemed similar.

### Meta

`rustc +nightly --version --verbose`:
```
rustc 1.85.0-nightly (9c707a8b7 2024-12-07)
binary: rustc
commit-hash: 9c707a8b769523bb6768bf58e74fa2c39cc24844
commit-date: 2024-12-07
host: x86_64-unknown-linux-gnu
release: 1.85.0-nightly
LLVM version: 19.1.5
```
Repository: PowerToys
Issue: Problem with Image Resizer
Labels: Issue-Bug,Product-Image Resizer,Needs-Triage,Area-Context Menu

### Microsoft PowerToys version

0.86.0

### Installation method

GitHub, Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

Image Resizer

### Steps to reproduce

It is impossible to have image resizer in the Windows context menu. I have no problem with other tools like PowerRename.

[PowerToysReport_2024-12-10-00-37-23.zip](https://github.com/user-attachments/files/18069535/PowerToysReport_2024-12-10-00-37-23.zip)
![Image](https://github.com/user-attachments/assets/af658429-a67a-4309-aa1e-979d08070c37)


### ✔️ Expected Behavior

A solution !

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: ollama
Issue: Nancy finds security vulnerabilities
Labels: bug

### What is the issue?

It finds:
* [CVE-2024-8063](https://ossindex.sonatype.org/vulnerability/CVE-2024-8063?component-type=golang&component-name=github.com%2Follama%2Follama&utm_source=nancy-client&utm_medium=integration&utm_content=1.0.46) CWE-369: Divide By Zero
* [CVE-2024-39719](https://ossindex.sonatype.org/vulnerability/CVE-2024-39719?component-type=golang&component-name=github.com%2Follama%2Follama&utm_source=nancy-client&utm_medium=integration&utm_content=1.0.46) CWE-209: Information Exposure Through an Error Message

The latest stable Ollama version does not fix them, so I am opening an issue to track that.

### OS

Linux

### GPU

Intel

### CPU

Intel

### Ollama version

0.5.1
Repository: next.js
Issue: Clicking on a <Link> to the current page focuses the first page.tsx element, not the first layout.tsx element
Labels: bug,Navigation

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/vigilant-orla-2snw6p

### To Reproduce

1. Put a link in the root `layout.tsx` file that takes you to `/`
2. Click that link, notice how `document.activeElement` is now the first element from the `page.tsx`, and not `layout.tsx`

### Current vs. Expected behavior

I would expect this line to find the first element on the page, but instead it finds the first element from the `page.tsx`, causing the page to scroll down when clicking on a link to itself:

https://github.com/vercel/next.js/blob/657c2cbd72ebf8f9a58edb4a7393c596246e3161/packages/next/src/client/components/layout-router.tsx#L209

This is causing issues on our site as it scrolls the user down every time they visit the home page, because we have a large shared navigation bar that is on every page.

### Provide environment information

```bash
Operating System:
  Platform: linux
  Arch: x64
  Version: #1 SMP PREEMPT_DYNAMIC Sun Aug  6 20:05:33 UTC 2023
  Available memory (MB): 4102
  Available CPU cores: 2
Binaries:
  Node: 20.9.0
  npm: 9.8.1
  Yarn: 1.22.19
  pnpm: 8.10.2
Relevant Packages:
  next: 15.0.4-canary.49 // Latest available version is detected (15.0.4-canary.49).
  eslint-config-next: N/A
  react: 19.0.0
  react-dom: 19.0.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Navigation

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local), Vercel (Deployed), Other (Deployed)

### Additional context

Related: #49427
Repository: rust
Issue: Crater testing
Labels: S-waiting-on-review

Just testing some crater runs, please ignore.
Repository: deno
Issue: localStorage constructor name is not 'Storage' an instead 'bound Storage'
Labels: bug,web

Hello,

The result of `globalThis.localStorage.constructor.name` is "bound Storage".

It was formerly just "Storage", as it is in Chrome &etc.

Best,
R

Version: Deno 2.1.3

```
$ deno
Deno 2.1.3
> globalThis.localStorage.constructor.name
"bound Storage"
>
$
```
Repository: deno
Issue: compile - ability to exclude modules or files
Labels: suggestion,compile

It would be useful to have a flag for excluding files or modules (ex. exclude some statically analyzable dynamic import or files in the node_modules directory that aren't necessary).
Repository: go
Issue: cmd/link/internal/ld: TestRISCVTrampolines failures
Labels: NeedsInvestigation

```
#!watchflakes
default <- pkg == "cmd/link/internal/ld" && test == "TestRISCVTrampolines"
```

Issue created automatically to collect these failures.

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

    === RUN   TestRISCVTrampolines
    === PAUSE TestRISCVTrampolines
    === CONT  TestRISCVTrampolines
        ld_test.go:425: Build failed: exit status 1, output: go: error obtaining buildID for go tool link: fork/exec /home/swarming/.swarming/w/ir/x/w/goroot/pkg/tool/netbsd_arm/link: bad file descriptor
    --- FAIL: TestRISCVTrampolines (224.01s)


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: godot
Issue: UIDs reported as missing on editor load, yet associated errors disappear after running project
Labels: bug,topic:core,topic:gdscript

### Tested versions

Godot 4.3 stable [77dcf97d8]

### System information

Windows 10, Debian 12

### Issue description

In one of my active gdscript files, I preload some Resources via UID, as shown below:

```gdscript
var mat : StandardMaterial3D = preload("uid://7ykjq67rxmbx")
```

This works as intended and without error when running the project. However upon closing the editor and reloading the project, on startup I get a stream of cascading errors up the chain of dependency from the initial resource-loading script, such as the following:

```
  core/io/resource_uid.cpp:132 - Condition "!unique_ids.has(p_id)" is true. Returning: String()
  res://scripts/components/shadow.gd:33 - Parse Error: Preload file "uid://7ykjq67rxmbx" does not exist.
  res://entities/isochan/isochan.gd:-1 - Compile Error: 
  res://scripts/room_manager.gd:-1 - Compile Error: 
  res://autoload/save_manager.gd:-1 - Compile Error: 
  modules/gdscript/gdscript.cpp:2936 - Failed to load script "res://autoload/save_manager.gd" with error "Parse error". (User)
```

Thing is, the reported UID in question _does_ in fact exist; if I right-click the resource in question in the editor and hit >Copy UID, the pasted string is exactly the same. This is further reinforced by simply running the project, in which the resource loads as intended without error or warning, and the initial editor load errors are cleared. The project is seemingly without issue until I close and reload the editor, and the same error consistently shows itself on editor startup thereon out.

### Steps to reproduce

I could not get the same error to happen in a separate MRP when when trying to manufacture the same conditions, so unfortunately I'm lost on how to reproduce this. My best guess is that whatever tracks the UIDs in this particular project has had _something_ screwy happen to it, but as far as I'm aware I cannot pin it down a singular cause, nor do I have any way of knowing what the state of the UIDs in my project is. Additionally it is unclear under what exact conditions the error starts to pop up. In the two times I've ran into it, the only way to mitigate the issue was to revert back to an earlier commit, and manually redo whatever changes I had made since. On the first occurrence of doing this, the errors, inexplicably, disappeared. Just recently I started getting the same error on a completely different set of resources. Most notably I have other resources in the project loaded in the exact same way as above, yet those ones have not given me issue.

### Minimal reproduction project (MRP)

As stated above, unfortunately I cannot seem to replicate this in an MRP. It seems to be specific to the active project I'm working on, or perhaps something that affects bigger projects with a number of existing resources, though the exact catalyst is unknown. That said, I'm more than willing to take question and try out suggestions in order to help narrow this down.
Repository: godot
Issue: set(property_string, property_value) works inconsistently with typed dictionaries
Labels: discussion,topic:core,topic:gdscript,documentation

### Tested versions

Reproduced in: v4.4.dev5

### System information

Windows 10

### Issue description

Assigning typed dictionary to another typed dictionary does not cast Variants to target typing. 
If that's intended, I'd expect the editor to spew an error of some kind, or output a warning. Instead the assignment is just skipped silently.

### Steps to reproduce

```
extends Node2D

class_name TestBug

var test_dict1: Dictionary[String, Variant] = {"Works": "false"}
var test_dict2: Dictionary[Variant, Variant] = {"Works": "true"}

func _ready() -> void:
    var target_dict: Dictionary[Variant, Variant] = {"Test": "Test"}
    set("test_dict1", target_dict.duplicate(true))
    set("test_dict2", target_dict.duplicate(true))
    print(test_dict1)
    print(test_dict2)
```
I would expect this to print
`
{ "Test": "Test" }
{ "Test": "Test" }
`
But instead, I got
`
{ "Works": "false" }
{ "Test": "Test" }
`



### Minimal reproduction project (MRP)

Here's the project zip:
[dictbug.zip](https://github.com/user-attachments/files/18071694/dictbug.zip)


### Edit:
I was able to get around this issue by simply doing
```
get(dictionary_name).clear()
for key in result_dict.keys():
    get(dictionary_name)[key] = result_dict[key]
```
The target dictionary is typed while `result_dict `isn't. The fact that set() doesn't work but this does feels inconsistent.
Repository: vscode
Issue: Chat Widget does not follow display language changes correctly
Labels: bug,chat

<!-- ⚠️⚠️ 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.95.3 (Universal)
- OS Version: macOS 15.1.1 (24B91)

Steps to Reproduce:

1. Open the Copilot Chat side panel.
2. Change VSCode language via `Configure Display Language` command. Confirm `Restart` button.
3. VScode restarts and successfully switches to new language. Copilot Chat still displaying with old language.
4. Reload VSCode via `Developer: Reload Window` command. (This step must be performed after Copilot Chat has finished initializing.)
5. Copilot Chat switches to new language successfully.

P.S. `renderWelcomeViewContentIfNeeded` cache is likely the culprit. It is called before `viewModel` exists.

https://github.com/microsoft/vscode/blob/05fd1308240072efb09749954fd478221fd01d55/src/vs/workbench/contrib/chat/browser/chatWidget.ts#L563-L582
Repository: pytorch
Issue: Using DeviceMesh Slicing with torch.compile()
Labels: oncall: distributed,triaged,module: DeviceMesh

### 🚀 The feature, motivation and pitch

This is a follow-up issue for https://github.com/pytorch/pytorch/pull/142287. Some questions from the reviewers:

* the internal tensor usage- is it always a CPU tensor regardless of the device used for training/communication
* the internal tensor should not be visible to anyone, other than indirectly (by calling other device-mesh APIs)
* how does device mesh behave under torch.compile and faketensor-trace? does a 'device-mesh' become an input to a graph? or does it get 'desugared' into primitive components, like ProcessGroup does when it gets traced?

We need to have clarities on how these work and add the supports if any features missing. Or we just need to explicitly add checks to forbid users from using DeviceMesh slicing with torch.compile() and document the limitation.

### Alternatives

_No response_

### Additional context

_No response_

cc @H-Huang @awgu @kwen2501 @wanchaol @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o
Repository: PowerToys
Issue: Upscaled Image Previews in File Explorer
Labels: Product-File Explorer,Needs-Triage

### Description of the new feature / enhancement

### **Problem:**
Windows File Explorer currently displays image previews scaled to **_at most_** 100%, even when using "Large icons" or "Extra large icons." This makes small images, such as 16x16 pixel art PNGs, difficult to see. Users often need to open these images in an external editor to zoom in, which is time-consuming.

### **Proposed Solution:**
Introduce an addon for PowerToys that:
1. Upscales small image previews to fill the entire preview container in File Explorer.
2. Offers customizable scaling methods, such as Nearest Neighbor (for crisp pixel art) or Bicubic (for smooth interpolation).
3. Includes options to ignore specific file types (e.g., `.jpg`) or directories (e.g., `C:/MyFolder`).


### Scenario when this would be used?

This feature would benefit anyone working with pixel art or low-resolution graphics, such as game developers, graphic designers, or hobbyists. It streamlines workflows by eliminating the need to open files in an editor just to inspect them.

![Image](https://github.com/user-attachments/assets/9e9df0bb-b74d-4150-8bb3-1dd56b331f46)

### Supporting information

Some specialized applications, like [Aseprite](https://www.aseprite.org/), already provide this functionality for their proprietary file types. Adding similar support for standard image files in File Explorer would be invaluable for users handling low-resolution assets.

![Image](https://github.com/user-attachments/assets/815a4796-1b16-4137-bab7-3aebcf4c48d8)
Repository: next.js
Issue: Empty URL search params are swallowed when rewriting via middleware on Vercel
Labels: bug,Middleware

### Link to the code that reproduces this issue

https://github.com/migueloller/vercel-middleware-search-params-bug-repro

### To Reproduce

Deploy the application to Vercel. The easiest way is using the Vercel CLI. I have a deployed version that can be used to test [here](https://search-params-drab.vercel.app/?foo=bar).

Visit the path `/?foo=` and then visit `/?foo=bar`. Note that while the search params are there for `/?foo=bar`, they are not there for `/?foo=`.

### Current vs. Expected behavior

The expectation is that URL search params are there even if the value is an empty string. Note, this is only happening because of the rewrite in the middleware. If the `middleware.ts` file is deleted, then the expected behavior occurs.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:13:04 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6020
  Available memory (MB): 16384
  Available CPU cores: 10
Binaries:
  Node: 18.19.0
  npm: 10.2.3
  Yarn: 1.22.21
  pnpm: 8.15.6
Relevant Packages:
  next: 15.0.3 // There is a newer version (15.0.4) available, upgrade recommended! 
  eslint-config-next: 15.0.3
  react: 19.0.0-rc-66855b96-20241106
  react-dom: 19.0.0-rc-66855b96-20241106
  typescript: 5.7.2
Next.js Config:
  output: N/A
 ⚠ There is a newer version (15.0.4) available, upgrade recommended! 
   Please try the latest canary version (`npm install next@canary`) to confirm the issue still exists before creating a new issue.
   Read more - https://nextjs.org/docs/messages/opening-an-issue
```


### Which area(s) are affected? (Select all that apply)

Middleware

### Which stage(s) are affected? (Select all that apply)

Vercel (Deployed)

### Additional context

The issue only happens when deploying to Vercel, it does not reproduce during local development. This is likely due to differences in the runtime middleware runs on in Vercel vs local dev.
Repository: angular
Issue: some diagrams are hard to read in dark mode
Labels: help wanted,good first issue,area: docs

### Describe the problem that you experienced

Many of the diagrams don't work well in dark mode. For example:

Light mode:
![Image](https://github.com/user-attachments/assets/dcb8b240-388d-453c-8332-af0c7b89ee63)

Dark mode:
![Image](https://github.com/user-attachments/assets/596ae229-e271-4b39-8ad9-d9df63514c6a)

The "User" label on the start node uses white text on a very bright yellow background, making it almost impossible to read.

The other nodes, while readable, contrast _very_ harshly with the black background, making the entire diagram unpleasant to look at.

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

https://angular.dev/guide/forms#data-flow-in-reactive-forms

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

_No response_

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

_No response_

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

_No response_

### 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
Doesn't seem to be browser specific, looks identical on Firefox, Chrome and Edge.
```
Repository: kubernetes
Issue: NodeResourcesBalancedAllocation cause too many pods scheduled to the same node
Labels: kind/bug,sig/scheduling,needs-triage

### What happened?

NodeResourcesBalancedAllocation will return different score if pod request is empty.

```
I1210 06:42:54.701779       1 resource_allocation.go:70] "Listing internal info for allocatable resources, requested resources and score" pod="tuyaco-k8s/task-worker-9" node="10.20.96.50" resourceAllocationScorer="NodeResourcesBalancedAllocation" allocatableResource=map[cpu:15600 memory:28727588291] requestedResource=map[cpu:14580 memory:24593301504] resourceScore=96
I1210 06:42:54.701793       1 resource_allocation.go:70] "Listing internal info for allocatable resources, requested resources and score" pod="tuyaco-k8s/task-worker-9" node="10.20.96.8" resourceAllocationScorer="NodeResourcesBalancedAllocation" allocatableResource=map[cpu:15600 memory:28727600579] requestedResource=map[cpu:15350 memory:24235737088] resourceScore=92
I1210 06:42:54.701807       1 resource_allocation.go:70] "Listing internal info for allocatable resources, requested resources and score" pod="tuyaco-k8s/task-worker-9" node="10.20.96.9" resourceAllocationScorer="NodeResourcesBalancedAllocation" allocatableResource=map[cpu:15600 memory:28727600579] requestedResource=map[cpu:13480 memory:19474153472] resourceScore=90
```


### What did you expect to happen?

NodeResourcesBalancedAllocation score should return zero if podRequest is zero. 

https://github.com/kubernetes/kubernetes/blob/a499facee693a1a83daadb82d88f7b51d324ffc5/pkg/scheduler/framework/plugins/noderesources/resource_allocation.go#L85-L114

The code below use `IsPrefixedNativeResource`, which ignore `cpu` and `memory`. 
https://github.com/kubernetes/kubernetes/blob/a499facee693a1a83daadb82d88f7b51d324ffc5/pkg/scheduler/util/utils.go#L158-L162

I think we should use below function.

https://github.com/kubernetes/kubernetes/blob/a499facee693a1a83daadb82d88f7b51d324ffc5/pkg/apis/core/v1/helper/helpers.go#L54-L60

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

create pod whcih request is empty and enable NodeResourcesBalancedAllocation.

scheduler config:
```yaml
- name: NodeResourcesBalancedAllocation
  args:
    resources:
      - name: cpu
      - name: memory
```

### Anything else we need to know?

_No response_

### Kubernetes version

<details>

```console
$ kubectl version
# paste output here
Server Version: v1.24.15
```

</details>


### Cloud provider

<details>
vanilla
</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: next.js
Issue: Failed to build with the error occurred in `next/font`
Labels: bug,Font (next/font)

### Link to the code that reproduces this issue

https://stackblitz.com/edit/stackblitz-starters-yqm1pksx?file=package.json

### To Reproduce

1. Install next.js v14.2.20
2. Exec `npm run build` 

### Current vs. Expected behavior

**Current**

Failed to build with errors shown below

```
> next build

  ▲ Next.js 14.2.20
  - Environments: .env.local

   Creating an optimized production build ...
Failed to compile.

src/app/layout.tsx
An error occurred in `next/font`.

Error: Cannot find module '$HOME/node_modules/@jridgewell/gen-mapping/dist/gen-mapping.umd.js'
```

**Expected**

Passing to build with no errors.

### Provide environment information

```bash
Operating System:
  Platform: Darwin
  Arch: arm64
  Version: 22.6.0
Binaries:
  Node: 20.16.0
  npm: 10.5.1
Relevant Packages:
  next: 14.2.20
Next.js Config:
  output: standalone
```


### Which area(s) are affected? (Select all that apply)

Font (next/font)

### Which stage(s) are affected? (Select all that apply)

next build (local)

### Additional context

I think this error is related with https://github.com/jridgewell/gen-mapping/issues/14
Repository: react
Issue: [eslint-plugin-react-hooks] v5.1.0 was released without any changes in github
Labels: Status: Unconfirmed

The newer version is released https://www.npmjs.com/package/eslint-plugin-react-hooks/v/5.1.0

However, there aren't any changes in the package dir here as of the time of posting the issue.
https://github.com/facebook/react/tree/372ec00c0384cd2089651154ea7c67693ee3f2a5/packages/eslint-plugin-react-hooks

This is concerning because it could indicate that someone published on behalf of the react team.