sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: tauri
Issue: [bug] Desktop file entry in deb package is not good according to spec
Labels: type: bug,platform: Linux,status: needs triage

### Describe the bug

desktop file entry in deb package is not good according to spec.

According to [spec](https://specifications.freedesktop.org/desktop-entry-spec/latest/file-naming.html), desktop file name should be DBus well-known name which is reverse DNS convention.

However, in deb package, '{product_name}.desktop' is included. I think it should be "{identifier}.desktop" or some other configurable name

### Reproduction

just building deb package is enough.
I think rpm package will also have same problem but not tested yet.

### Expected behavior

_No response_

### Full `tauri info` output

```text
[✔] Environment
    - OS: Mac OS 15.0.1 arm64 (X64)
    ✔ Xcode Command Line Tools: installed
    ✔ rustc: 1.81.0-beta.7 (4a765c0b8 2024-08-28)
    ✔ cargo: 1.81.0-beta.7 (2dbb1af80 2024-08-20)
    ✔ rustup: 1.27.1 (54dd3d00f 2024-04-24)
    ✔ Rust toolchain: beta-aarch64-apple-darwin (default)
    - node: 22.6.0
    - pnpm: 8.15.4
    - npm: 10.8.2

[-] Packages
    - tauri 🦀: 2.0.1
    - tauri-build 🦀: 2.0.1
    - wry 🦀: 0.44.1
    - tao 🦀: 0.30.3
    - tauri-cli 🦀: 2.0.0-rc.3
    - @tauri-apps/api : 2.0.1 (outdated, latest: 2.0.2)
    - @tauri-apps/cli : 2.0.1 (outdated, latest: 2.0.2)

[-] Plugins
    - tauri-plugin-single-instance 🦀: 2.0.1
    - @tauri-apps/plugin-single-instance : not installed!
    - tauri-plugin-updater 🦀: 2.0.2
    - @tauri-apps/plugin-updater : not installed!
    - tauri-plugin-fs 🦀: 2.0.1
    - @tauri-apps/plugin-fs : not installed!
    - tauri-plugin-dialog 🦀: 2.0.1
    - @tauri-apps/plugin-dialog : not installed!

[-] App
    - build-type: bundle
    - CSP: unset
    - frontendDist: out
    - devUrl: http://localhost:3030/
    - framework: React (Next.js)
    - bundler: Webpack
```


### Stack trace

_No response_

### Additional context

The tauri info is running on development environment, which is on macOS.

vrc-get/vrc-get#1594
Repository: excalidraw
Issue: Optimization Issues with Pencil Tool Strokes on Page Zoom
Labels: bug,freedraw

Appreciate the fantastic software crafted by the development team. I've come across an issue while using it and would like to report it here. I hope you can consider further enhancements to the handwriting feature.

When the page is enlarged, there can be issues with writing using the pencil tool, often resulting in overly smooth strokes. This might be due to the visual effects seen in videos. Is there any plan to address this? If not, could you advise on how to adjust the length of the "guide line" at the pen tip in the video? Thanks!

Also, would it be possible to include a feature to disable pressure sensitivity? I'm concerned that this might be causing severe lag during writing after a while. Thanks!
Repository: storybook
Issue: Name is not defined for the Combo boxes present on the page in Windows.
Labels: bug,accessibility,argtypes

### Describe the bug

**Title:** Name is not defined for the Combo boxes present on the page in Windows.

**Pre-Requisite:**
Press F12 key to open developer tool.

**Test Environment:** 
OS: Windows 11 Version 24H2 OS build 26100.1742
Browser: Microsoft New Edge Version129.0.2792.52(Official build) (64-bit)
Tool: Developer Tool

**Actual Result:** 
Name is not defined for the 'Size' combo box present on the page in Windows. Screen reader is announcing as '16 combo box collapsed has pop up'.

Refer Attachment: 

https://github.com/user-attachments/assets/f963edd6-8843-4237-aaa5-c628cf087399

![Image](https://github.com/user-attachments/assets/73efa55a-99b4-4790-adec-23db70436496)


**Expected Result:** 
Name should be defined for the 'Size' combo box present on the page in Windows. Screen reader should announce as '16 size combo box collapsed has pop up'.

### Reproduction link

React Web Component Wrappers / Fluent Wrappers / Avatar - Docs ⋅ Storybook (ambitious-cliff-0c8148010.2.azurestaticapps.net) 

### Reproduction steps

**Repro Steps:**
Open URL: [React Web Component Wrappers / Fluent Wrappers / Avatar - Docs ⋅ Storybook (ambitious-cliff-0c8148010.2.azurestaticapps.net)](https://ambitious-cliff-0c8148010.2.azurestaticapps.net/?path=/docs/reactwrappers_react-web-component-wrappers-fluent-wrappers-avatar--docs) in latest Edge browser.
Story book page will open.
Press tab key from top of the page to reach the 'Size' combo box.
Press F12 to open developer tool.
Verify in developer tool whether name is defined for the 'Size' combo box or not.


### System

OS: Windows 11 Version 24H2 OS build 26100.1742
Browser: Microsoft New Edge Version129.0.2792.52(Official build) (64-bit)

### Additional context

_No response_
Repository: rust
Issue: Tracking Issue for minicore (core prelude stubs test auxiliary)
Labels: T-compiler,T-bootstrap,C-tracking-issue,A-test-infra

### Context

We have a bunch of `#![no_core]` ui/codegen/assembly tests that roll their own `core` prelude stubs because they need to build (but not run) on a cross-compiled target. But this means:

- A bunch of duplicated implementations of `core` prelude stubs scattered in different tests.
- A heavy burden on a contributor of possibly having to update *many* tests if a new *required* lang item wants to be added.
- Prelude stubs can obfuscate the intent of the test (more things that the reader has to read and mentally filter out).

Instead of continuing to add more copies of `core` prelude stubs, let's centralize such `core` prelude stubs into a shared test auxiliary called `minicore`. `minicore` is for `core` prelude stubs specifically. `std` prelude which can include `liballoc` items and such is beyond the scope of `minicore`, because `core` is usable by more tests. This does not preclude adding another `ministd` or `minialloc` for stubs of `std`/`liballoc` respectively.

See https://github.com/rust-lang/rust/issues/130375 for more discussions.

### Steps

- [x] 1. Open an MCP to add `minicore` test auxiliary.
    - MCP is accepted: https://github.com/rust-lang/compiler-team/issues/786
    - Note that the MCP title specified std/core prelude stubs, but we revised the scope to `core` stubs only.
- [x] 2. Implement initial test infra support for `minicore`.
    - https://github.com/rust-lang/rust/pull/130693 
- [x] 3. Adjust rustc-dev-guide docs.
    - https://github.com/rust-lang/rustc-dev-guide/pull/2097 
- [x] 4. ~~Figure out the logistics on how to absorb `core` stubs into `minicore`, then use `minicore` to simplify existing `#![no_core]` tests.~~
    - Currently, I think it's better to just have the infra in place to allow newer and changed tests to use `minicore.rs`, it seems like unnecessary churn to also force existing tests to use `minicore.rs` atm.

### Unresolved questions

- What do we do with existing `#![no_core]` tests that could benefit from `minicore`?
Repository: rust
Issue: false positive: variable does not need to be mutable
Labels: A-lints,C-bug,S-needs-repro

### Summary

I had a false positive `unused_mut`, after fixing it - re-running `cargo clippy` still threw the warning. Seems it could have some sort of cache issue as after doing `cargo clean`, the lint no longer threw the warning. 

![Image](https://github.com/user-attachments/assets/e2bdc712-99be-4eed-af69-9e1988c7af49)


### Lint Name

unused_mut

### Reproducer

I haven't managed to reproduce this since, but just a simple:


1. `let (tx, mut rx) = mpsc::unbounded_channel();`
2. run `cargo clippy`
3. remove the `mut`
4. lint still remained
5. `cargo clean`
6. lint now no longer warned

### Version

rustc 1.81.0 (eeb90cda1 2024-09-04)
binary: rustc
commit-hash: eeb90cda1969383f56a2637cbd3037bdf598841c
commit-date: 2024-09-04
host: x86_64-unknown-linux-gnu
release: 1.81.0
LLVM version: 18.1.7


### Additional Labels

_No response_
Repository: fastapi
Issue: Question about "Required, can be None" parameter
Labels: docs

### Discussed in https://github.com/fastapi/fastapi/discussions/12418

<div type='discussions-op-text'>

<sup>Originally posted by **bowenerchen** October 10, 2024</sup>
### First Check

- [X] I added a very descriptive title here.
- [X] I used the GitHub search to find a similar question and didn't find it.
- [X] I searched the FastAPI documentation, with the integrated search.
- [X] I already searched in Google "How to X in FastAPI" and didn't find any information.
- [X] I already read and followed all the tutorial in the docs and didn't find an answer.
- [X] I already checked if it is not related to FastAPI but to [Pydantic](https://github.com/pydantic/pydantic).
- [X] I already checked if it is not related to FastAPI but to [Swagger UI](https://github.com/swagger-api/swagger-ui).
- [X] I already checked if it is not related to FastAPI but to [ReDoc](https://github.com/Redocly/redoc).

### Commit to Help

- [X] I commit to help with one of those options 👆

### Example Code

```python
from typing import Annotated

from fastapi import FastAPI, Query

app = FastAPI()


@app.get("/items/")
async def read_items(q: Annotated[str | None, Query(min_length=3)] = ...):
    results = {"items": [{"item_id": "Foo"}, {"item_id": "Bar"}]}
    if q:
        results.update({"q": q})
    return results
```


### Description

https://fastapi.tiangolo.com/tutorial/query-params-str-validations/#required-can-be-none
![QQ_1728534861112](https://github.com/user-attachments/assets/95e967aa-ea9f-46c1-80c8-f13dc7c52e6c)
how to pass a None value to the required query parameter q?

### Operating System

macOS

### Operating System Details

Sonoma 14.7 M2 Max

### FastAPI Version

0.115.0

### Pydantic Version

2.5.3

### Python Version

Python 3.12.4

### Additional Context

_No response_</div>
Repository: PowerToys
Issue: Windows keyboard manager doesn't start when I first boot up my computer.
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Windows keyboard manager doesn't start when I first boot up my computer.

### ✔️ Expected Behavior

Every time, I have to manually run PowerToys.KeyboardManagerEngine.exe.
This needs to be fixed.

### ❌ Actual Behavior

Windows keyboard manager doesn't start when I first boot up my computer.

### Other Software

_No response_
Repository: godot
Issue: CameraAttribute exposure does not consider ambient light, and incorrectly exposes Background
Labels: bug,topic:rendering,confirmed,topic:3d

### Tested versions

4.3.stable

### System information

Windows 11 - Godot v4.3.stable - Vulkan (Forward+) - dedicated NVIDIA GPU

### Issue description

So, there are two problems, both related to the CameraAttribute exposure.

1. Ambient Light Color/Energy does not consider CameraAttribute exposure, Tonemap Exposure works fine.
There is a related [issue](https://github.com/godotengine/godot/issues/74899), but it is about SDFGI.
In the picture below, the ambient light color is set to magenta. The first line uses CameraAttribute and the second line uses Tonemap.
![screenshot_0](https://github.com/user-attachments/assets/0223a2d2-9c49-427a-9024-8fe52fec5698)
3. CameraAttribute expose Background "faster" than objects.
Ambient Light Energy is set to 0 here, and the color of Plane in the scene has been matched with Background to better observe the difference.
![screenshot_1](https://github.com/user-attachments/assets/7e954650-207d-4f8a-9ab0-c1a958ed8358)

These two problems make it more difficult to get consistent ambient light from Ambient Light Color when using CameraAttribute for exposure.

### Steps to reproduce

1. Create a scene, add WorldEnvironment, directional light and objects.
2. Select any mode in the Environment Background.
3. Select "Color" or "Sky" in Environment Ambient Light Source.
4. Adjust Exposure Multiplier of CameraAttribute and compare with Tonemap Exposure.

### Minimal reproduction project (MRP)

[exposure-test.zip](https://github.com/user-attachments/files/17323608/exposure-test.zip)
Repository: ant-design
Issue: table组件在配置virtual +行合并 + 合并行内容超出当前行高度时，表现出文字重叠的现象
Labels: Inactive,unconfirmed

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-vpvsjb?file=demo.tsx)

### Steps to reproduce

1. antd-table-[虚拟列表demo](https://ant.design/components/table-cn#table-demo-virtual-list)
2. 修改Group渲染字段内容字数
3. 修改行合并逻辑


### What is expected?

行合并后的内容高度可以自适应高度 带有边距

### What is actually happening?

行合并后的内容高度没有自适应高度

| Environment | Info |
| --- | --- |
| antd | 5.21.3 |
| React | 18.3.1 |
| System | macOS: 15.0 |
| Browser |  129.0.6668.60 (正式版本) (arm64) |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: ant-design
Issue: Table 开启 virtual 后，格子无法滚动
Labels: 🐛 Bug,Inactive

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-v48dwg?file=demo.tsx)

### Steps to reproduce

滚动有滚动条的格子

### What is expected?

格子可以滚动

### What is actually happening?

格子无法滚动

| Environment | Info |
| --- | --- |
| antd | 5.21.3 |
| React | latest |
| System | mac |
| Browser | chrome |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: next.js
Issue: Metadata function does not work as expected in intercepting routes.
Labels: bug,Metadata,Parallel & Intercepting Routes

### Link to the code that reproduces this issue

https://github.com/sato-kazuma-kun/nextjs-intercepting-routes-bug

### To Reproduce

1. Start the application (bun or npm suggested).
2. Navigate to `/` and press the "Login" button.
3. Watch that the title of the document does not change.
4. Check the code in `app/@modal/(.)login/page.tsx` (It exports a metadata function with a title).

### Current vs. Expected behavior

Following the steps I expect the title of the page to change to "Login - Bug" but it remains same to the page prior to opening the modal.

### Provide environment information

```bash
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Home Single Language
  Available memory (MB): 5990
  Available CPU cores: 8
Binaries:
  Node: 20.10.0
  npm: N/A
  Yarn: N/A
  pnpm: N/A
Relevant Packages:
  next: 14.2.4 // There is a newer version (14.2.15) available, upgrade recommended!
  eslint-config-next: 14.2.1
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.0.4
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Metadata, Parallel & Intercepting Routes

### Which stage(s) are affected? (Select all that apply)

next dev (local), next start (local)

### Additional context

_No response_
Repository: deno
Issue: Npm OpenPgp is not working on server side in Fresh.js
Labels: bug,node compat,crypto

Version: Deno 1.46.3
npm:openpgp its not working on server side in freshJs for data encryption 
**getting this error :** ` invalid utf-8 sequence of 1 bytes from index 1` whenever createMessage method call after reading the publicKey.
Repository: ollama
Issue: nomic-embed-vision-v1.5
Labels: model request

is-it possible to add nomic-ai/nomic-embed-vision-v1.5
to completing with nomic-embed-text-v1.5
Repository: rust
Issue: Implementation of trait "not general enough" in nightly, works fine on stable
Labels: P-high,regression-from-stable-to-stable,C-bug,T-types

<!--
Thank you for filing a regression report! 🐛 A regression is something that changed between versions of Rust but was not supposed to.

Please provide a short summary of the regression, along with any information you feel is relevant to replicate it.
-->

### Code

I tried this (reduced) code:

```rust
use tokio::sync::mpsc::{unbounded_channel,UnboundedSender};

pub trait Role: 'static + Sync + Send {
    type Return : Send;
}

pub trait BasicRole: 'static + Send + Sync {}
impl Role for dyn BasicRole + '_ {
    type Return = ();
}

pub struct ReturnEnvelope<R: Role + ?Sized> {
	pub return_path: Option<R::Return>,
}

pub fn start() {
    let (_basic_role_input, mut basic_role_output): (UnboundedSender<ReturnEnvelope<dyn BasicRole>>, _) = unbounded_channel();

    let event_loop = async move {
        let _ = basic_role_output.recv().await;
    };
    let _ = ::tokio::task::spawn(event_loop);
}
```
([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=37be08010838c0fec37bb6889fd69b1e))

I expected to see this happen: successful compile.

Instead, this happened: I received this error: 
```
error: implementation of `Role` is not general enough
  --> src/lib.rs:22:13
   |
22 |     let _ = ::tokio::task::spawn(event_loop);
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ implementation of `Role` is not general enough
   |
   = note: `Role` would have to be implemented for the type `(dyn BasicRole + '0)`, for any lifetime `'0`...
   = note: ...but `Role` is actually implemented for the type `(dyn BasicRole + '1)`, for some specific lifetime `'1`
```
This can also be seen on the playground configured to use nightly.

I am aware that handling this construct correctly seems to be an outstanding issue, I'm specifically reporting the inconsistency that it does work on stable and not nightly. 

### Version it worked on
It most recently worked on: 1.81.0 stable (most recent)

### Version with regression

`rustc --version --verbose`:
```
rustc 1.83.0-nightly (eb4e23467 2024-10-09)
binary: rustc
commit-hash: eb4e2346748e1760f74fcaa27b42431e0b95f8f3
commit-date: 2024-10-09
host: x86_64-pc-windows-msvc
release: 1.83.0-nightly
LLVM version: 19.1.1
```

However, this has been an issue since at least the 2024-08-17 nightly (feeba198f)

<!--
If you know when this regression occurred, please add a line like below, replacing `{channel}` with one of stable, beta, or nightly.
-->
@rustbot modify labels: +regression-from-stable-to-nightly -regression-untriaged
Repository: next.js
Issue: Image Component flicker when refresh the page
Labels: bug,Image (next/image)

### Link to the code that reproduces this issue

https://github.com/jizhi0v0/background-image-flash.git

### To Reproduce

1.Start the application in development (next dev)
2.refresh the page
3.image flash

### Current vs. Expected behavior


https://github.com/user-attachments/assets/a6098447-ed5a-4530-ad2b-1dd4aa7e7581



### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 24.1.0: Mon Sep 30 00:10:38 PDT 2024; root:xnu-11215.40.63~39/RELEASE_ARM64_T6031
  Available memory (MB): 36864
  Available CPU cores: 14
Binaries:
  Node: 22.3.0
  npm: 10.8.1
  Yarn: 1.22.22
  pnpm: 9.6.0
Relevant Packages:
  next: 14.2.15 // Latest available version is detected (14.2.15).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Image (next/image)

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

Also exist in latest canary version.
Repository: next.js
Issue: URLSearchParams does not survive serialization/deserialization when passed from a client to a Server Action
Labels: bug

### Link to the code that reproduces this issue

https://codesandbox.io/p/devbox/exciting-meitner-zrdlrs

### To Reproduce

1. Write a Server Action that takes URLSearchParams
2. Try to call it from a client component

### Current vs. Expected behavior

When calling `URLSearchParams#toString()` in a Server Action, it yields a malformed output (`foo,bar,next,js`), instead of actual query/search params (`foo=bar&next=js`).

### 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.0-canary.182 // Latest available version is detected (15.0.0-canary.182).
  eslint-config-next: N/A
  react: 19.0.0-rc-2d16326d-20240930
  react-dom: 19.0.0-rc-2d16326d-20240930
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Not sure

### Which stage(s) are affected? (Select all that apply)

next dev (local), next build (local), next start (local)

### Additional context

_No response_
Repository: rust
Issue: RPITIT causes incorrect "dropped while still borrowed" error in some cases
Labels: C-bug,F-return_position_impl_trait_in_trait

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

From [this SO question](https://stackoverflow.com/q/79073414/501250), the following code does not compile:

```rust
trait Iterable {
    fn owned_iter(&self) -> impl Iterator<Item = usize> + 'static;
}

struct B<T> {
    x: T,
}

impl<T: Iterable + Clone> Iterable for B<T> {
    fn owned_iter(&self) -> impl Iterator<Item = usize> + 'static {
        let y = self.x.clone();
        y.owned_iter() // error[E0597]: `y` does not live long enough
    }
}
```

However, boxing the iterator as a trait object allows it to compile:

```rust
trait Iterable {
    fn owned_iter(&self) -> impl Iterator<Item = usize> + 'static;
}

struct B<T> {
    x: T,
}

impl<T: Iterable + Clone> Iterable for B<T> {
    fn owned_iter(&self) -> impl Iterator<Item = usize> + 'static {
        let y = self.x.clone();
        let b: Box<dyn Iterator<Item = usize>> = Box::new(y.owned_iter());
        b
    }
}
```

Notably, not cloning `self.x` and simply returning `self.x.owned_iter()` also works.

I don't see any reason why the first code block shouldn't compile, especially while the boxed version and the non-cloning version do.

### 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.
-->

`rustc --version --verbose`:
```
rustc 1.81.0 (eeb90cda1 2024-09-04)
binary: rustc
commit-hash: eeb90cda1969383f56a2637cbd3037bdf598841c
commit-date: 2024-09-04
host: x86_64-unknown-linux-gnu
release: 1.81.0
LLVM version: 18.1.7
```

It also fails to compile on 1.83.0-nightly (2024-10-09 eb4e2346748e1760f74f).
Repository: deno
Issue: Support sloppy imports in `deno compile`
Labels: feat,compile

Version: Deno 2.0.0
I tried to play around with deno 2.0 by compiling my nest js project with deno. I thought maybe if i can compile the project into one executable binary that would be cool. Its pretty complex project. But i found that deno cannot compile if my import has no `.ts` on it. Maybe its obvious, but that would take a tedious task to add `.ts` in almost every imports

this is the error message
```bash
deno compile -R src/main.ts --unstable-sloppy-imports
error: Module not found "file:///project-dir/src/sentry". Maybe add a '.ts' extension or run with --unstable-sloppy-imports
    at file:///project-dir/src/main.ts:1:8
```
Repository: deno
Issue: Node HTTPS Server Requests
Labels: bug,node compat,node:http

Using this code to create a node https server:
<img width="1071" alt="image" src="https://github.com/user-attachments/assets/bac84538-bef8-42b1-bd7a-22c24417d44f">

Chrome shows the connection to the server as H2
<img width="1047" alt="image" src="https://github.com/user-attachments/assets/d0178e89-f2e2-4891-af75-40bc9a7b127b">

But Deno request (IncomingMessageForServer) http version is 1.1 and there is no **host** or **:authority** header in the request and requested domain can't be found anywhere in the request:
<img width="304" alt="image" src="https://github.com/user-attachments/assets/d3244336-ab44-4f27-bc83-11997b264bc7">