sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Advanced Paste - History Access via Keyboard
Labels: Needs-Triage

### Description of the new feature / enhancement

I recently switched from Ditto to Powertoys Advanced Clipboard. Prior to that I used Alfred on macOS to do clipboard history.

PowerToys Advanced Paste departs from the behavior of the vast majority of clipboard viewers in that I can not use ONLY the keyboard to navigate.

As a user of PowerToys who is inside of a document with both hands on my keyboard, when I need to paste, I use Ctl-V and Ctl-X etc frequently.

When I need to paste from the Advanced Paste tool (with AI enabled, no idea if that changes the behavior) it auto focuses on the prompt box. In order to access an item on the clipboard history that is 5 from the top, I have to hit the following key combinations:

1. Ctl-Shift-V (my activator key shortcut)
2. Tab
3. Tab
4. Enter
5. Arrow key to the correct item
6. Enter
7. Ctl-V

Conversely, in Ditto and Alfred (and most clipboard history tools)... 

1. Activator keyboard shortcut
2. Down arrow to the one you want
3. Enter to paste

Candidly, it's kind of a pain in the butt to use the clipboard history because of that. This is a power user tool, but this interface feels anything but power.

### Scenario when this would be used?

Every day all day when I need to paste clipboard history. Probably 50 times a day.

### Supporting information

I have proof as a user of the product that it is cumbersome to get to the clipboard history.
Repository: react
Issue: [Compiler Bug]: Error when calling `React.createElement(..., { ref })`
Labels: Type: Bug,Component: Optimizing Compiler

### What kind of issue is this?

- [X] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEMCaAkpgBI4C2ANgKL0K0KY4AUAlEcADrEicQmBwkyRALxEoYBACUynTFHr1uAbkFEJOWMSUBDXADo4pIzgTNW7LvxBwjmAG5GwjgDR8JaIgC+WoIBIAFAA

### Repro steps

[Playground link](https://playground.react.dev/#N4Igzg9grgTgxgUxALhAMygOzgFwJYSYAEMCaAkpgBI4C2ANgKL0K0KY4AUAlEcADrEicQmBwkyRALxEoYBACUynTFHr1uAbkFEJOWMSUBDXADo4pIzgTNW7LvxBwjmAG5GwjgDR8JaIgC+WoIBIAFAA)

This code:

```js
function refInHtmlElement() {
  const ref = useRef(null);
  return React.createElement("canvas", { ref });
}
```

Has this error:

> InvalidReact: Ref values (the `current` property) may not be accessed during render. (https://react.dev/reference/react/useRef) (3:3)

Even though we're using a ref in the way it's meant to be used. If we rewrite it in JSX, the error goes away:

```jsx
function refInHtmlElement() {
  const ref = useRef(null);
  return <canvas ref={ref} />;
}
```

I find this behavior surprising, because I always thought that JSX desugared down to `React.createElement` anyway....

### How often does this bug happen?

Every time

### What version of React are you using?

Playground

### What version of React Compiler are you using?

Playground
Repository: PowerToys
Issue: Peek view plantuml
Labels: Needs-Triage

### Description of the new feature / enhancement

Add plantuml preview in peek.

### Scenario when this would be used?

When I want to view a diagram without opening an entire IDE or uploading the file on a web app.

### Supporting information

_No response_
Repository: flutter
Issue: `flutter test test/integration.shard` fails locally
Labels: tool,P2,c: tech-debt,team-tool,triaged-tool

This is in a clean build locally with no changes.

```sh
flutter_tools % flutter-dev test test/integration.shard
```

The actual failures are not always the same, and sometimes pass when ran locally one at a time.
Repository: deno
Issue: HTTP server does not validate `Host` header is present
Labels: bug

Version: Deno 2.0.0

I made a quick and simple standards test and found that Deno does not properly check for Content-Length vs. Transfer-Encoding. It must close the connection with error if both headers are present.

Also, the Host header is not checked.

![Screenshot 2024-10-25 222602](https://github.com/user-attachments/assets/664cd6c8-35d8-4950-aa43-1a4c293ae24d)
Repository: flutter
Issue: Chromium Mac Bots become unresponsive and Xcode commands hang
Labels: team-infra,P0,triaged-infra

From https://chromium-swarm.appspot.com/bot?id=build806-m9

<img width="1436" alt="Screenshot 2024-10-25 at 13 25 01" src="https://github.com/user-attachments/assets/1278a76d-2d1b-4c01-92f1-bcae102e62b3">

XCode installs are failing due to data corruption as in:

https://logs.chromium.org/logs/flutter/buildbucket/cr-buildbucket/8733087603218910657/+/u/install_xcode/install_xcode_from_cipd/stdout

There are other failure modes as well. I suspect a bad disk or bad memory. The automatic reboots on task failure don't seem to be helping.

I put up this CL to remove it from the prod pool, but I'm wondering if this is the right thing to do? https://chrome-internal-review.googlesource.com/c/infradata/config/+/7775927

cc @christopherfujino I'm wondering if bad machines like this are the underlying cause of https://github.com/flutter/flutter/issues/156614 ?
Repository: flutter
Issue: Windows tool integration tests are flaky: "Java heap space"
Labels: platform-windows,P1,c: flake,team-tool,triaged-tool

One [example failure](https://ci.chromium.org/ui/p/flutter/builders/try/Windows%20tool_integration_tests_7_9/683/overview):

```txt
20:00 +25 -1: test/integration.shard/isolated/native_assets_test.dart: flutter build apk succeeds without libraries [E]
  Exception: flutter build failed: 1
  
  FAILURE: Build failed with an exception.
  
  * What went wrong:
  Execution failed for task ':app:compressDebugAssets'.
  > A failure occurred while executing com.android.build.gradle.internal.tasks.CompressAssetsWorkAction
     > Java heap space
  
  * Try:
  > Run with --stacktrace option to get the stack trace.
  > Run with --info or --debug option to get more log output.
  > Run with --scan to get full insights.
  > Get more help at https://help.gradle.org/.
  
  BUILD FAILED in 42s
  Gradle task assembleDebug failed with exit code 1
  
  
  Running Gradle task 'assembleDebug'...                          
  Running Gradle task 'assembleDebug'...                             43.9s
  
  test\integration.shard\isolated\native_assets_test.dart 240:11  main.<fn>.<fn>
  ===== asynchronous gap ===========================
  test\integration.shard\isolated\native_assets_test.dart 803:5   inTempDir
  ===== asynchronous gap ===========================
  test\integration.shard\isolated\native_assets_test.dart 226:7   main.<fn>
```

Looking at the try-bots, these [don't seem particularly healthy](https://ci.chromium.org/ui/p/flutter/builders/try/Windows%20tool_integration_tests_7_9):

![image](https://github.com/user-attachments/assets/0698d293-f0d6-436f-bf9a-66058a911ef9)
Repository: neovim
Issue: snippets: wrong indentation when snippet contains `^`
Labels: bug,snippet

### Problem

```lua
vim.snippet.expand([[
a^  b$1
c$1
d$1
e]])
```

```
a^  b
^  c
^  ^  d
^  ^  ^  e
```

Whitespace after `^` (circumflex) is detected as indent and added multiple times. Relates to #29658.


######  [My comment](https://github.com/neovim/neovim/pull/29670#issuecomment-2416708675) with a possible explanation.

### Steps to reproduce

Execute the above Lua code.

### Expected behavior

```
a^  b
c
d
e
```

### Nvim version (nvim -v)

v0.10.2

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

n/a

### Operating system/version

Arch

### Terminal name/version

Alacritty

### $TERM environment variable

alacritty

### Installation

system package manager
Repository: ui
Issue: [bug]: Select component doesn't work with useFormStatus() pending
Labels: bug

### Describe the bug

I recently upgraded to NextJS 15 and I have noticed that react-dom's useFormStatus is no longer working when the `Select` component is included in the form.

I'm not sure if this is a shadcn/ui issue, a radix issue, or a react-dom issue.

Please see the repository where I have a trimmed down form that reproduces the problem.

I'm also not sure if this affects other shadcn/ui components.

### Affected component/components

Select

### How to reproduce

1. Clone https://github.com/samstr/shadcn-formstatus-demo
2. npm install
3. npm run dev
4. Go to http://localhost:3000
5. Click the submit button on the form with an Input (pending state works)
6. Click the submit button on the form with a Select (pending state does not work)

### Codesandbox/StackBlitz link

https://github.com/samstr/shadcn-formstatus-demo


https://github.com/user-attachments/assets/03baa682-b540-43d5-967b-9d237fa08e3b



### Logs

_No response_

### System Info

```bash
Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/130.0.0.0 Safari/537.36

See package.json
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: pytorch
Issue: Libtorch torch::Tensor default constructor does not initialize on CPU like in python
Labels: module: cpp,triaged

### 🐛 Describe the bug

Working in python:

```py
import torch

t = torch.Tensor()
x = torch.cat([t, t, t], 1)
x
```
output:
```
tensor([])
```

not working in c++
```cpp
#include <torch/torch.h>

int main()
{
	torch::Tensor t{};
	auto x = torch::cat({ t, t, t }, 1);
	std::cout << x << std::endl;

	return 0;
}
```
Throws a c10::Error
```
tensor does not have a device
```



### Versions

PyTorch version: 2.4.1+cu124
Is debug build: False
CUDA used to build PyTorch: 12.4
ROCM used to build PyTorch: N/A

OS: Microsoft Windows 11 Pro (10.0.22631 64-bit)
GCC version: Could not collect
Clang version: Could not collect
CMake version: version 3.25.1
Libc version: N/A

Python version: 3.10.5 (tags/v3.10.5:f377153, Jun  6 2022, 16:14:13) [MSC v.1929 64 bit (AMD64)] (64-bit runtime)
Python platform: Windows-10-10.0.22631-SP0
Is CUDA available: True
CUDA runtime version: 12.6.77
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 4090
Nvidia driver version: 565.90
cuDNN version: C:\Program Files\NVIDIA GPU Computing Toolkit\CUDA\v12.6\bin\cudnn_ops64_9.dll
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Name: 13th Gen Intel(R) Core(TM) i9-13900K
Manufacturer: GenuineIntel
Family: 207
Architecture: 9
ProcessorType: 3
DeviceID: CPU0
CurrentClockSpeed: 3000
MaxClockSpeed: 3000
L2CacheSize: 32768
L2CacheSpeed: None
Revision: None

Versions of relevant libraries:
[pip3] numpy==1.24.1
[pip3] torch==2.4.1+cu124
[pip3] torchaudio==2.4.1+cu124
[pip3] torchvision==0.19.1+cu124
[conda] Could not collect


For C++:
libtorch-win-shared-with-deps-debug-2.4.1+cu124
Microsoft (R) C/C++ Optimizing Compiler Version 19.32.31332 for x64
CUDA 12.6.77 C++ Compiler

cc @jbschlosser
Repository: godot
Issue: TileMap editor background visibility issues RELOADED
Labels: enhancement,topic:editor,usability,topic:2d

### Tested versions

- Reproducible in 4.4.dev3

### System information

Linux

### Issue description

Reopen of this issue -> https://github.com/godotengine/godot/issues/84192 that was closed due to the author "ban".
You can't see shit if tilemap has, for example, transparent background.
![image](https://github.com/user-attachments/assets/84330c84-34f9-4b42-a5bc-a5ade628f224)


### Steps to reproduce

None

### Minimal reproduction project (MRP)

None
Repository: react
Issue: Bug: Checkbox change event is incorrect when parent state is updated using `flushSync`
Labels: Status: Unconfirmed

<!--
  Please provide a clear and concise description of what the bug is. Include
  screenshots if needed. Please test using the latest version of the relevant
  React packages to make sure your issue has not already been fixed.
-->

React version: `18.3.1`

## Steps To Reproduce

It is a very specific case best described by a code sample. I have checkbox inside a div.  When the checkbox is clicked, it should select the checkbox and the div. Notice the `checkbox` does not get selected. If I remove `flushSync` then it works as expected 

```
export default function App() {
  const [isDivSelected, setIsDivSelected] = useState(false);
  const [isCheckboxSelected, setIsCheckboxSelected] = useState(false);

  return (
    <>
      <div
        className="container"
        style={{
          borderColor: isDivSelected ? "blue" : "red",
        }}
        onClick={() => {
          flushSync(() => {
            setIsDivSelected(true);
          });
        }}
      >
        <input
          type="checkbox"
          checked={isCheckboxSelected}
          onChange={(e) => {
            setIsCheckboxSelected(e.target.checked);
          }}
        />
        Click to checkbox to select cell
      </div>
      <button
        type="button"
        onClick={() => {
          setIsDivSelected(false);
          setIsCheckboxSelected(false);
        }}
      >
        Reset
      </button>
    </>
  );
}
```

<!--
  Your bug will get fixed much faster if we can run your code and it doesn't
  have dependencies other than React. Issues without reproduction steps or
  code examples may be immediately closed as not actionable.
-->

Link to code example:
https://codesandbox.io/p/sandbox/flamboyant-ace-ngqjfg?workspaceId=bc172196-5c2d-4f29-a12b-3906e64cfab1

<!--
  Please provide a CodeSandbox (https://codesandbox.io/s/new), a link to a
  repository on GitHub, or provide a minimal code example that reproduces the
  problem. You may provide a screenshot of the application if you think it is
  relevant to your bug report. Here are some tips for providing a minimal
  example: https://stackoverflow.com/help/mcve.
-->

## The current behavior
`event.target.checked` is `false`


## The expected behavior
`event.target.checked` should be `true`
Repository: pytorch
Issue: [Feature request] Flag to prevent certain parameters from being typecast by nn.module.to()
Labels: module: nn,triaged,needs design

### 🚀 The feature, motivation and pitch

 I work with a lot of models that are mostly bf16 but have a couple parameters that I need to have stay in fp32. The most common ones are loss scaling parameters used for fp32 loss calculations that require grad updates.

A flag similar to ```requires_grad``` but for preventing casting would be very handy.
I.e. something similar to:
```
self.p = nn.Parameter(t)
self.p.dynamic_dtype = False
```


### Alternatives

There are workarounds (i.e. saving and restoring the parameter) but they tend to be quite error prone, especially when working with training libraires that cast the nn.module. You always have to be on the lookout whenever you're loading or training that a cast doesn't slip by.

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki
Repository: flutter
Issue: make currentSystemFrameTimeStamp more reliable/expose _lastRawTimeStamp
Labels: framework,c: proposal,P3,team-framework,triaged-framework

### Use case

I sometimes I need to access the current frame time during an event handler (ie, `SchedulerBinding.instance.currentFrameTimeStamp`), to record when an animation started.

### Proposal

`currentFrameTimeStamp` doesn't allow this, as it asserts when accessed outside of the render(?) phase. `currentSystemFrameTimeStamp` looks like it will work, but the documentation says "On most platforms, this is a more or less arbitrary value, and should generally be ignored." Is that correct? It doesn't seem like this should be the case, as [the code](https://github.com/flutter/flutter/blob/9b84dbed06a173617a70d9c760775984296d90fb/packages/flutter/lib/src/scheduler/binding.dart#L1130) just returns `_lastRawTimeStamp`, which seems close enough to the behavior I want.

But I guess the ideal thing would be if we had a timestamp with time dilation(?) outside of the render phase as well?
Repository: react
Issue: [Compiler Bug]: `===` is not a sufficient equality check
Labels: Component: Optimizing Compiler

### What kind of issue is this?

- [X] React Compiler core (the JS output is incorrect, or your app works incorrectly after optimization)
- [ ] babel-plugin-react-compiler (build issue installing or using the Babel plugin)
- [ ] eslint-plugin-react-compiler (build issue installing or using the eslint plugin)
- [ ] react-compiler-healthcheck (build issue installing or using the healthcheck script)

### Link to repro

https://playground.react.dev/#N4Igzg9grgTgxgUxALhASwLYAcIwC4AEwBUYCAyngIZ4IEC+BAZjBBgQDogwJVx5cA3BwB2ohAA8c+AgBMETKlAA2hJlBH80EEQQBaCVgAoAlEVEECcHWEIBtAF6GIAGgJk8B1gF0CAXhIyShoEIwAGE2FdKxtCWxh-AgB5ACMAKwR+ADo0MCMnVjcIggB+ThAwrgJkcoBaSpAoyx48WF0AHhSoPDwdAh0AYWU0OABrP2BTfwA+dwRPZyNagogTemngePp2gHounp1pqPpREHogA

### Repro steps

1. Click the rendered button repeatedly

**Expected result:**

On each click, the text should toggle between `0` and `-0`.

**Actual result:**

Initially, the text `0` is rendered. After the first click, `-0` is rendered. Subsequent clicks don't do anything.

### How often does this bug happen?

Every time

### What version of React are you using?

18.3.1

### What version of React Compiler are you using?

19.0.0-beta-8a03594-20241020

---

React Compiler currently uses the `===` operator to check whether to memoize. The `===` operator isn't sufficient to check whether two values are identical. The two edge cases missed by `===` but handled handled by `Object.is()`:

- `0`/`-0`: React Compiler being unable to detect a difference between these values causes this bug.
- `NaN`: React Compiler incorrectly _always_ detects a difference despite one not existing, causes code to not be memoized, but is otherwise correct.

I imagine that changing `===` to `Object.is()` in the output might be bad for performance. In case this bug is a _wontfix_, you should document this limitation somewhere.
Repository: flutter
Issue: Annotation or enums for preferred constant values
Labels: framework,c: proposal,P3,team-framework,triaged-framework

### Use case

As part of work around the Flutter Property Editor (https://github.com/flutter/devtools/issues/1948), we would like to be able to support Flutter properties like [strokeAlign](https://api.flutter.dev/flutter/painting/BorderSide/strokeAlign.html). Although it's a double, there are three constants defined by Flutter that are preferred (strokeAlignInside, strokeAlignCenter, and strokeAlignOutside). Ideally we would like to find a way to support this in the Property Editor without having to hardcode rules for these special cases. 

There are likely other cases similar to `strokeAlign` that should be modified to best support the Flutter Property Editor. 

### Proposal

A couple options to solve this:

1. By creating an annotation (e.g., `@knownValues`) 

```
BorderSide({
    Color color = const Color(0xFF000000),
    double width = 1.0,
    BorderStyle style = BorderStyle.solid,
    @knownValues([BorderSide.strokeAlignInside, BorderSide.strokeAlignCenter, BorderSide.strokeAlignOutside])
    double strokeAlign = strokeAlignInside})
```

2. Switch to an enum 
 
Another option would be to use an enhanced enum with `double` members. However, in the case of `strokeAlign`, because other values besides -1.0. 0.0. and 1.0 can be used, this is likely not the best solution.
Repository: deno
Issue: "module is not defined" cjs suggestion should not occur for mjs/mts modules
Labels: bug,good first issue

```
> cat main.mjs
import * as a from "./a.cjs";

console.log(a.add(1, 2));

module.isPreloading = true;
> deno run main.mjs
3                                                                                                                                                                                                                                                                                                                
error: Uncaught (in promise) ReferenceError: module is not defined                                                                                                                                                                                                                                                             
module.isPreloading = true;                                                                                                                                                                                                                                                                                                    
^
    at file:///V:/scratch/main.mjs:5:1

    info: Deno supports CommonJS modules in .cjs files, or when there's a package.json
          with "type": "commonjs" option and --unstable-detect-cjs flag is used.
    hint: Rewrite this module to ESM,
          or change the file extension to .cjs,
          or add package.json next to the file with "type": "commonjs" option
          and pass --unstable-detect-cjs flag.
    docs: https://docs.deno.com/go/commonjs
```

This suggestion doesn't make sense.

Node for example:

```
> node main.mjs
3
file:///V:/scratch/main.mjs:5
module.isPreloading = true;
^

ReferenceError: module is not defined in ES module scope
    at file:///V:/scratch/main.mjs:5:1
    at ModuleJob.run (node:internal/modules/esm/module_job:262:25)
    at async ModuleLoader.import (node:internal/modules/esm/loader:474:24)
    at async asyncRunEntryPointWithESMLoader (node:internal/modules/run_main:109:5)

Node.js v22.3.0
```
Repository: rust
Issue: Diagnostic doesn't mention cfg'ed out items if the unresolved path is simple (i.e., a single identifier)
Labels: A-diagnostics,A-resolve,T-compiler,D-terse,A-cfg

Given the following code, I would've expected rustc to mention the cfg'ed out item `Struct`:

```rs
#[cfg(flag)]
struct Struct;

fn main() { let _ = Struct; } //~ ERROR cannot find type `Struct` in this scope
```

but it doesn't:

```
error[E0425]: cannot find value `Struct` in this scope
 --> file.rs:4:21
  |
4 | fn main() { let _ = Struct; }
  |                     ^^^^^^ not found in this scope
```

Only if you slightly tweak the input by replacing the simple path `Struct` with a complex one like `self::Struct` or `crate::Struct`, the note "found an item that was configured out" will show up:

```rs
#[cfg(flag)]
struct Struct;

fn main() { let _ = self::Struct; }
```

```
error[E0425]: cannot find value `Struct` in module `self`
 --> file.rs:4:27
  |
4 | fn main() { let _ = self::Struct; }
  |                           ^^^^^^ not found in `self`
  |
note: found an item that was configured out
 --> file.rs:2:8
  |
2 | struct Struct;
  |        ^^^^^^
note: the item is gated here
 --> file.rs:1:1
  |
1 | #[cfg(flag)]
  | ^^^^^^^^^^^^
```

CC #109005. I don't know if that's intentional or not.