sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Use MIME Types Rather Than File Extensions to Choose Peek Preview Handler
Labels: Needs-Triage

### Description of the new feature / enhancement

When Peek is used to preview a file with no extension, rather than display the standard Peek window shown when no preview can be displayed, use the MIME type to determine if the file can in fact be displayed.

### Scenario when this would be used?

It is not uncommon for a user to have at least some files on their drive with no extension.  Currently, such files cannot be previewed in Peek (or Explorer's preview pane) without some (probably ill-advised) tweaking of the registry. (I believe) it is currently only possible by change the value of `PerceivedType` to`text/plain` for the registry key `HKCR\*`.  Then, I encountered [this](https://github.com/LRN/mimerun) GitHub project, called `mimerun` which presents an interested idea.

### Supporting information

Here is the README Description of the **`mimerun`** Project: 

<div align=justify>

Mimerun installs itself as a shell hook (shell hooks are supported in all versions of Windows since Windows XP, although they are disabled in Vista and later by default).

Whenever something (Windows Explorer, Windows command line shell, or any Windows program) calls **`ShellExecute()`** or **`ShellExecuteEx()`**, Mimerun catches that and, if target is a file, uses **`libmagic`** (the supporting library of the UNIX file(1) utility) to guess the type of target. Then it compares the result of type guessing with a set of Mimerun rules (written by user, stored in the registry) and, if a match is found, executes the command specified in the matching rule. Once a matching rule is found and its handler is executed successfully, Mimerun signals the caller of that success, stopping the shell from trying to handle the target. If no rules match, or the target is not a file, or if there were errors during the computation, Mimerun signals a failure and lets the shell find other ways to handle the target.

#### Shebang Support

Mimerun also supports shebangs, being able to use them exclusively to run scripts with correct interpreters, or supplementing a handler with them.

Commandline bridge is used to force the shell to pass any unknown files (files that do not match any of the shell's own file associations) to Mimerun. This allows Mimerun to process files that were double-clicked in Windows Explorer and were not handled by the shell.

Adding "." to `PATHEXT` environment variable allows files without extensions to be handled correctly.

</div>
Repository: PowerToys
Issue: shortcut key conflict
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.84.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

While powertoys is running in the background, holding down the shift key and a number key will not enter the character above the number, and holding down the shift key and an alphabet key will not enter a capital letter. After closing powertoys, everything returns to normal.

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: pytorch
Issue: The error message of `nn.RNN()` for the input tensor should say ValueError: the dtype of the `input` tensor and `RNN()` must be the same but got `...` and `...` respectively
Labels: module: nn,module: rnn,triaged

### 🐛 Describe the bug

Setting a `float64` tensor to [nn.RNN()](https://pytorch.org/docs/stable/generated/torch.nn.RNN.html) gets the error message as shown below:

```python
import torch
from torch import nn

my_tensor = torch.tensor([[8., -3., 5.]], dtype=torch.float64) # float64

torch.manual_seed(42)

rnn = nn.RNN(input_size=3, hidden_size=2)

rnn(input=my_tensor) # Error
```

> ValueError: input must have the type torch.float32, got type torch.float64

And, setting a `complex64` tensor to `nn.RNN()` gets the error message as shown below:

```python
import torch
from torch import nn

my_tensor = torch.tensor([[8.+0.j, -3.+0.j, 5.+0.j]]) # complex64

torch.manual_seed(42)

rnn = nn.RNN(input_size=3, hidden_size=2)

rnn(input=my_tensor) # Error
```

> ValueError: input must have the type torch.float32, got type torch.complex64

But setting a `float64` tensor or `complex64` tensor to `nn.RNN()` with `dtype=torch.float64` or `dtype=torch.complex64` respectively works as shown below:

```python
import torch
from torch import nn

my_tensor = torch.tensor([[8., -3., 5.]], dtype=torch.float64) # float64

torch.manual_seed(42)
                                        # ↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓
rnn = nn.RNN(input_size=3, hidden_size=2, dtype=torch.float64)

rnn(input=my_tensor)
# (tensor([[-1.0000, -0.9999]], dtype=torch.float64, grad_fn=<SqueezeBackward1>),
#  tensor([[-1.0000, -0.9999]], dtype=torch.float64, grad_fn=<SqueezeBackward1>))

my_tensor = torch.tensor([[8.+0.j, -3.+0.j, 5.+0.j]]) # complex64

torch.manual_seed(42)
                                        # ↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓ ↓
rnn = nn.RNN(input_size=3, hidden_size=2, dtype=torch.complex64)

rnn(input=my_tensor)
# (tensor([[ 0.9965-0.0006j, -0.9936-0.0332j]], grad_fn=<SqueezeBackward1>),
#  tensor([[ 0.9965-0.0006j, -0.9936-0.0332j]], grad_fn=<SqueezeBackward1>))
```

I think the error messages should be something like as shown below:

> ValueError: the dtype of the `input` tensor and `RNN()` must be the same but got `float64` and `float32` respectively

> ValueError: the dtype of the `input` tensor and `RNN()` must be the same but got `complex64` and `float32` respectively

### Versions

```python
import torch

torch.__version__ # '2.3.0'
```

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: storybook
Issue: [Bug]: Storybook v8.1.6 Deployment Error: JSyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSON  正文 Describe the bugAfter deploying our Storybook  v8.1.6, we're encountering issues that don't appear in our local environment. we use vite +ts
Labels: bug,needs triage

### Describe the bug

1. JSON Syntax ErrorUpon accessing the deployed Storybook in production, the 'View error' button reports the following error:SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSONThis suggests an issue with resource loading, possibly an attempt to load an HTML document where a JSON file was expected.
![lQLPKGvY1q8SYG_NARXNBLOw3fKJUKq65eEG4I_KLBRCAA_1203_277](https://github.com/user-attachments/assets/29443b9c-7fb8-47a2-8360-e49c29a926b9)


### Reproduction link

test

### Reproduction steps

_No response_

### System

```bash
1. JSON Syntax ErrorUpon accessing the deployed Storybook in production, the 'View error' button reports the following error:SyntaxError: Unexpected token '<', "<!DOCTYPE "... is not valid JSONThis suggests an issue with resource loading, possibly an attempt to load an HTML document where a JSON file was expected.
![lQLPKGvY1q8SYG_NARXNBLOw3fKJUKq65eEG4I_KLBRCAA_1203_277](https://github.com/user-attachments/assets/29443b9c-7fb8-47a2-8360-e49c29a926b9)
```


### Additional context

_No response_
Repository: pytorch
Issue: `input_size` argument of `nn.RNN()` gets indirect error messages
Labels: module: nn,module: rnn,triaged

### 🐛 Describe the bug

Setting the float value `3.` to `input_size` of [nn.RNN()](https://pytorch.org/docs/stable/generated/torch.nn.RNN.html) gets the indirect error message as shown below:

```python
import torch
from torch import nn

my_tensor = torch.tensor([[8., -3., 5.]])

torch.manual_seed(42)
                      # ↓↓
rnn = nn.RNN(input_size=3., hidden_size=2) # Error

rnn(input=my_tensor)
```

> TypeError: empty(): argument 'size' failed to unpack the object at pos 2 with error "type must be tuple of ints,but got float"

And, setting the boolean value `True` to `input_size` of `nn.RNN()` gets the indirect error message as shown below:

```python
import torch
from torch import nn

my_tensor = torch.tensor([[8., -3., 5.]])

torch.manual_seed(42)
                      # ↓↓↓↓
rnn = nn.RNN(input_size=True, hidden_size=2)

rnn(input=my_tensor) # Error
```

> RuntimeError: input.size(-1) must be equal to input_size. Expected True, got 3

So, the error messages should be something direct like as shown below:

> TypeError: `input_size` argument must be `int` but got `float`

> TypeError: `input_size` argument must be `int` but got `bool`

### Versions

```python
import torch

torch.__version__ # '2.3.0'
```




























































cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: pytorch
Issue: Setting the boolean value `True` to `hidden_size` argument of `nn.RNN()` gets a indirect error message
Labels: module: nn,module: rnn,triaged

### 🐛 Describe the bug

Setting the boolean value `True` to `hidden_size` argument of [nn.RNN()](https://pytorch.org/docs/stable/generated/torch.nn.RNN.html) gets the indirect error message as shown bleow:

```python
import torch
from torch import nn

my_tensor = torch.tensor([[8., -3., 5.]])

torch.manual_seed(42)
                                     # ↓↓↓↓
rnn = nn.RNN(input_size=3, hidden_size=True) # Error
```

```
TypeError: empty() received an invalid combination of arguments - got (tuple, dtype=NoneType, device=NoneType), but expected one of:
 * (tuple of ints size, *, tuple of names names, torch.memory_format memory_format, torch.dtype dtype, torch.layout layout, torch.device device, bool pin_memory, bool requires_grad)
 * (tuple of ints size, *, torch.memory_format memory_format, Tensor out, torch.dtype dtype, torch.layout layout, torch.device device, bool pin_memory, bool requires_grad)
```

While setting the float value `1.` to `hidden_size` argument of `nn.RNN()` gets the correct error message as shown bleow:

```python
import torch
from torch import nn

my_tensor = torch.tensor([[8., -3., 5.]])

torch.manual_seed(42)
                                     # ↓↓
rnn = nn.RNN(input_size=3, hidden_size=1.) # Error
```

> TypeError: hidden_size should be of type int, got: float

So, the wrong error message should be corrected as shown below:

> TypeError: hidden_size should be of type int, got: bool


### Versions

```python
import torch

torch.__version__ # '2.3.0'
```

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: electron
Issue: restore upstream `CHECK_EQ(IsGuest()...)` test
Labels: component/webcontents,upgrade-follow-up,stale

[This Chromium roll](https://github.com/electron/electron/pull/43948) removes a new  upstream `CHECK_EQ()` in `WebContentsImpl::CreateNewWindow()`:

```diff
-  // While some guest types do not have a guest SiteInstance, the ones that
-  // don't all override WebContents creation above.
-  CHECK_EQ(source_site_instance->IsGuest(), IsGuest());
   bool is_guest = IsGuest();
```

That check is failing in Electron, both in CI runs and in manual testing.

I tried injecting just that one `CHECK_EQ()` line into `main` on its own (in 27d2a8f9e28715c3da6e8570bbc12d89cfa88178) and it fails there, too. So whatever's going on is not new to this roll; some pre-existing condition in Electron is causing `IsGuest()` and `source_site_instance->IsGuest()` to have different values.

This ticket's TODO is to understand why and figure out if it can be solved in Electron's code instead of in a patch.
Repository: deno
Issue: /etc/hosts seems to be ignored
Labels: bug,node compat

Version: Deno 1.46.3 and 2.0.0-rc.7
OS: Macos Sequoia

Hello

I am trying to use this code:

```ts
import dns from "node:dns";

dns.lookup("mongo-1", (err, address, family) => {
  console.error(err);
  console.log("address: %j family: IPv%s", address, family);
});
```

I also have the issue with the `mongodb` package from NPM.

It prints:

```bash
Error: getaddrinfo ENOTFOUND mongo-1
    at __node_internal_captureLargerStackTrace (ext:deno_node/internal/errors.ts:93:9)
    at __node_internal_ (ext:deno_node/internal/errors.ts:246:10)
    at GetAddrInfoReqWrap.onlookup [as oncomplete] (node:dns:37:26)
    at ext:deno_node/internal_binding/cares_wrap.ts:78:9
    at eventLoopTick (ext:core/01_core.js:175:7) {
  errno: -3007,
  code: "ENOTFOUND",
  syscall: "getaddrinfo",
  hostname: "mongo-1"
}
address: %j family: IPvundefined undefined
```

`/etc/hosts`

```txt
127.0.0.1 mongo-1
```

I tested using bash (netcat) and mongoDB Compass and the name `mongo-1` works as expected.

I tried this command as well: `sudo dscacheutil -flushcache; sudo killall -HUP mDNSResponder` without success.

Thank you.
Repository: pytorch
Issue: Setting wrong values to `num_layers` of `nn.RNN()` gets indirect error messages
Labels: module: nn,module: rnn,triaged

### 🐛 Describe the bug

Setting a float value to `num_layers` of [nn.RNN()](https://pytorch.org/docs/stable/generated/torch.nn.RNN.html) gets the indirect error message as shown below:

```python
import torch
from torch import nn

my_tensor = torch.tensor([[8., -3., 5.]])
                                                   # ↓↓
rnn = nn.RNN(input_size=3, hidden_size=1, num_layers=1.) # Error

rnn(input=my_tensor)
```

> TypeError: 'float' object cannot be interpreted as an integer

And, setting a complex value to `num_layers` of `nn.RNN()` also gets the indirect error message as shown below:

```python
import torch
from torch import nn

my_tensor = torch.tensor([[8., -3., 5.]])
                                                   # ↓↓↓↓↓↓
rnn = nn.RNN(input_size=3, hidden_size=1, num_layers=1.+0.j) # Error

rnn(input=my_tensor)
```

> TypeError: '<=' not supported between instances of 'complex' and 'int'

And, setting a bool value to `num_layers` of `nn.RNN()` also gets the indirect error message as shown below:

```python
import torch
from torch import nn

my_tensor = torch.tensor([[8., -3., 5.]])
                                                   # ↓↓↓↓
rnn = nn.RNN(input_size=3, hidden_size=1, num_layers=True)

rnn(input=my_tensor) # Error
```

```
TypeError: rnn_tanh() received an invalid combination of arguments - got (Tensor, Tensor, list, bool, bool, float, bool, bool, bool), but expected one of:
 * (Tensor data, Tensor batch_sizes, Tensor hx, tuple of Tensors params, bool has_biases, int num_layers, float dropout, bool train, bool bidirectional)
      didn't match because some of the arguments have invalid types: (Tensor, Tensor, !list of [Parameter, Parameter, Parameter, Parameter]!, !bool!, bool, !float!, !bool!, bool, bool)
 * (Tensor input, Tensor hx, tuple of Tensors params, bool has_biases, int num_layers, float dropout, bool train, bool bidirectional, bool batch_first)
      didn't match because some of the arguments have invalid types: (Tensor, Tensor, !list of [Parameter, Parameter, Parameter, Parameter]!, bool, !bool!, float, bool, bool, bool)
```

So, they should be something direct like as shown below:

> TypeError: num_layers argument must be int but got float

> TypeError: num_layers argument must be int but got complex

> TypeError: num_layers argument must be int but got bool

### Versions

```python
import torch

torch.__version__ # '2.3.0'
```

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: opencv
Issue: Allow use of system flatbuffers
Labels: feature,category: build/install,category: dnn

### Describe the feature and motivation

Currently, OpenCV only supports use of bundled 3rdparty flatbuffers. Adding an option like Protobuf to decide whether finding or building is much better.

### Additional context

https://github.com/opencv/opencv/blob/4.x/cmake/OpenCVDetectFlatbuffers.cmake
Repository: deno
Issue: Failed to get cpu info crash on aarch64
Labels: needs investigation,node compat

The latest Deno 2 release candidate crashes inside the Node compatibility function `os.cpus()` when run on an Android device under Termux. To reproduce:

```
$ curl -O https://dl.deno.land/release/v2.0.0-rc.7/deno-aarch64-unknown-linux-gnu.zip
$ unzip deno-aarch64-unknown-linux-gnu.zip
$ apt install glibc-repo
$ apt install glibc-runner
$ grun ./deno eval 'console.log("success")'
success
$ echo 'import {cpus} from "node:os";' >cpus.js
$ echo 'console.log(cpus());' >>cpus.js
$ grun ./deno --allow-sys=cpus cpus.js
error: Uncaught (in promise) TypeError: Failed to get cpu info
  at cpus (node:os:63:10)
  at file:///data/data/com.termux/files/home/cpus.js:2:13
```

I don't have another ARM device handy, but I'm curious whether this affects all aarch64 machines or just the Termux glibc wrapper script.

Version: Deno 2.0.0-rc.7
Repository: rust
Issue: Can we avoid the heap allocation in macOS Mutex/Condvar?
Labels: O-macos,T-libs,A-atomic

This was brought up over [here](https://github.com/rust-lang/rust/issues/93740#issuecomment-1992275013): our current macOS implementation for `Mutex` and `Condvar` use heap allocations. That's unfortunate because it can lead to OOM, and also seems like a slight efficiency hit.

Heap allocations are required because we are using the pthread API on macOS, and pthread Mutexes are not movable. AFAIK, @joboet has been working on alternative implementations that avoid the pthread API (https://github.com/rust-lang/rust/pull/122408). The alternative, suggested by @daira , is to get Apple to guarantee that their pthread mutexes are movable under certain conditions. Given the black box that Apple is, I have no idea if that's even remotely realistic. But anyway it seems worth tracking this somewhere so here we go. :)
Repository: opencv
Issue: Use universal intrinsics in imgwarp.cpp
Labels: feature

### Describe the feature and motivation

Currently, there are a lot of `CV_SIMD128` in https://github.com/opencv/opencv/blob/4.x/modules/imgproc/src/imgwarp.cpp and some SSE4_1, AVX2, LASX SIMD implementation. I suggest using universal intrinsics instead.

This is a following issue of https://github.com/opencv/opencv/issues/26185

### Additional context

_No response_
Repository: PowerToys
Issue: PowerToys Run does not work
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.84.1

### Installation method

WinGet

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

in my laptop with Windows 11 power toys run as expected, but in job pc with windows 10 power toys not working, can anyone help with that? 

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: fastapi
Issue: Required with Ellipsis may not work
Labels: docs,confirmed

### Privileged issue

- [ ] I'm @tiangolo or he asked me directly to create an issue here.

### Issue Content

https://fastapi.tiangolo.com/tutorial/query-params-str-validations/#required-parameters
![QQ_1727594279276](https://github.com/user-attachments/assets/86d8893a-4c3f-45cb-8fc3-7f97cad6ac00)
python interpreter:3.12.4
fastapi version:0.115.0

my codes:
```
from __future__ import annotations
from typing import Annotated
import uvicorn
from fastapi import FastAPI, Query
app = FastAPI()
@app.get("/items/")
async def read_items(q: Annotated[str, Query(min_length = 3)] = ...):
    """
    curl -X 'GET' 'http://127.0.0.1:18081/items/' -H 'accept: application/json'
    ValueError: [TypeError("'ellipsis' object is not iterable"), TypeError('vars() argument must have __dict__ attribute')]
    """
    results = {"items": [{"item_id": "Foo"}, {"item_id": "Bar"}]}
    if q:
        results.update({"q": q})
    return results


if __name__ == '__main__':
    uvicorn.run(app, host = '127.0.0.1', port = 18081)
```
swagger docs:
![QQ_1727594546393](https://github.com/user-attachments/assets/c1b94031-5145-4f27-981a-6d35f6cc2fe2)

![QQ_1727594603897](https://github.com/user-attachments/assets/4d370afd-5642-4948-8521-65483a460514)

ValueError: [TypeError("'ellipsis' object is not iterable"), TypeError('vars() argument must have __dict__ attribute')]
Repository: PowerToys
Issue: shortcuts with pressed Alt don't work when keymap is changed
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.84.1

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

I'm using Keyboard Manager with Microsoft Japanese IME. I've defined some shortcuts to input polish letters and everything works fine, until I change the keymap. After the change (to Polish (Programmers) or US International), keyboard with pressed Alt doesn't work as expected.

- set Polish (Programmers) and Japanese IME keymap.
- define shortcut mapping to send polish letters, e.g. Alt (Right) + A -> ą; Alt (Right) + c -> ć
- keep right Alt pressed and press ac
- change the keymap
- keep right Alt pressed and press ac

### ✔️ Expected Behavior

Remapping works with constantly pressed right Alt key. I.e. ąć

### ❌ Actual Behavior

After changing the keymap when right Alt is continuously pressed only the first shortcut send proper text. I.e. ąc

### Other Software

_No response_
Repository: rust
Issue: wasm32_wasip1_threads's llvm_target is mistake
Labels: A-linkage,T-compiler,O-wasm,C-bug

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

about /compiler/rustc_target/src/spec/targets/wasm32_wasip1_threads.rs
https://github.com/rust-lang/rust/blob/master/compiler/rustc_target/src/spec/targets/wasm32_wasip1_threads.rs#L61
now:
```rust:
llvm_target: "wasm32-wasi".into(),
```
I think:
```rust:
llvm_target: "wasm32-wasi-threads".into(),
```
--target wasm32-wasi: After this argument, the linked .o files are treated as wasm32-wasi.
```
= note: wasm-ld: error: --shared-memory is disallowed by dlmalloc.o because it was not compiled with the 'atomics' or 'bulk-memory' features.
```

If you change it, it will be linkable.

### 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
```
Repository: ant-design
Issue: RangePicker the triangle sign was not positioned correctly in some cases
Labels: 🐛 Bug,help wanted,Inactive

### Reproduction link

[![Edit on StackBlitz](https://developer.stackblitz.com/img/open_in_stackblitz.svg)](https://stackblitz.com/edit/react-2hs74j?file=demo.tsx)

### Steps to reproduce

click any RangePicker component

### What is expected?

the triangle mark should be in the correct position

### What is actually happening?

the triangle sign always seems to be on the left

| Environment | Info |
| --- | --- |
| antd | 5.21.1 |
| React | 18.3.1 |
| System | Windows 11 |
| Browser | Version 129.0.6668.60 (Official Build) (64-bit) |

To reproduce, I changed the demo to a `flex-end` layout. Normally, when a search form is used and the `datepicker` component is the last element in a row
![image](https://github.com/user-attachments/assets/868957ee-e661-4278-be1e-3eb28a3ca8dd)


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->