sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Shortcut is unavailable when focusing any other apps
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

0.85.1

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

General

### Steps to reproduce

1. Enable shortcut in powertoys.
2. shortcut is available when focusing powertoys.
3. shortcut in unavailable when focusing any other apps, such as calculator.

> The issue appears and disappears and does not reproduce consistently

### ✔️ Expected Behavior

shortcut is available in anywhere

### ❌ Actual Behavior

shortcut in unavailable when focusing any other apps, such as calculator

### Other Software

_No response_
Repository: Python
Issue: Use list instead of string in rot13.py
Labels: enhancement

### Feature description

### SUGGESTED IMPROVEMENTS

**Minor Efficiency Improvements:**
The code is efficient for its purpose, but using a list to accumulate characters instead of concatenating strings directly within the loop improves performance slightly, especially for longer strings.

**Redundant n Argument in dencrypt Function:**
Since the ROT13 cipher is designed to shift characters by 13 positions, the n parameter is unnecessary for this particular implementation. Using a fixed 13-shift simplifies the code and makes it clear that it’s a ROT13 encryption.

**Reversible Encryption Test Assumptions:**
The doctest section’s example assumes that dencrypt will return the exact input message upon re-encryption with n=13. However, because n is modifiable, this behavior could break if n is set to a different value. Fixing n=13 would make the encryption/decryption consistent.

**Testing for Errors and Assertions:**
The function doesn’t include any assertions to validate inputs. Adding checks, especially for invalid inputs, would improve its robustness.
Repository: godot
Issue: Path(3D) initial position of zero does not immediately update
Labels: bug,regression,topic:3d

### Tested versions

 Reproducible in 4.4 dev3
 4.3 still has non immediate bug [issue 95612](https://github.com/godotengine/godot/issues/95612)

### System information

Godot v4.4.dev3 - Windows 10.0.19045 - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated Radeon RX 5500 XT - AMD Ryzen 7 5800X 8-Core Processor (16 threads)

### Issue description

Similar to [95612](https://github.com/godotengine/godot/issues/95612)
possibly caused by [96140](https://github.com/godotengine/godot/pull/96140)

After updating to 4.3 I also experienced the delayed update affecting path transforms.
I copy transforms manually (for many reasons) so I currently can't use 4.3, I tested in 4.4 dev3 and I don't get the jumping to a new position for one frame problem, however unless I set the path.position(_ratio) to a very small non-zero value the starting position is incorrect.
It appears the immediate update might be skipped if the value is zero

### Steps to reproduce

Place an instance somewhere in the scene that manually copies transforms, before the progress_ratio is non zero, the instance starts at a different position, as soon as the path position is non zero it behaves as expected (MRP provided)

I think maybe one of the checks added skips zero values, resulting in a lack of immediate transform when the progress value is set but the value is zero

Maybe p_immediate just needs to be exposed as a check box, so users doing custom pathing can get the immediate behaviour as per previous versions? Maybe the default state needs to be how it was in 4.2, or whatever state most users expect it to be?

### Minimal reproduction project (MRP)

[44d3_path3d_immediate_mrp.zip](https://github.com/user-attachments/files/17537509/44d3_path3d_immediate_mrp.zip)

(While making this I also found that the string passing UI bug for very small numbers (more than 4 decimal places) still exists, I also found that if all control node values are zero on the start or end point, an unexpected rotation is applied, I'll have a look for similar reports and pop ones in if needed)
Repository: opencv
Issue: The new dnn engine does not support async inference
Labels: bug,category: dnn

### System Information

Platform: Any
References: 
- https://github.com/opencv/opencv/pull/26208
- https://github.com/opencv/opencv/pull/26056

### Detailed description

-

### Steps to reproduce

-

### Issue submission checklist

- [X] I report the issue, it's not a question
- [ ] I checked the problem with documentation, FAQ, open issues, forum.opencv.org, Stack Overflow, etc and have not found any solution
- [ ] I updated to the latest OpenCV version and the issue is still there
- [ ] There is reproducer code and related data files (videos, images, onnx, etc)
Repository: vscode
Issue: Scroll Beyond First Line in Visual Studio Code
Labels: feature-request,editor-scrollbar

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
With the [workaround](https://github.com/microsoft/vscode/issues/108548) of using "[padding top](https://github.com/microsoft/vscode/issues/49027)", the feature of scrolling beyond the first line remains a **low-priority** request for now. 

However, it's important to highlight a key distinction between the existing functionality of `editor.scrollBeyondLastLine` and the workaround of using `editor.padding.top`.

The `scrollBeyondLastLine` feature dynamically calculates the height, allowing users to scroll down until only one line is visible. 
In contrast, the padding approach has a fixed limit of 1000 pixels, which may suffice for most users but can be restrictive for those with vertical screens. Such users may find themselves unable to scroll as freely as they would prefer.

Therefore, while padding top works for the moment, implementing a `scrollBeyondFirstLine` feature would enhance usability by offering the same dynamic scrolling experience upwards, allowing for a more comfortable reading of the code.

Thank you for considering this enhancement!
Repository: rust
Issue: Suboptimal codegen for integer slice matching without `|` in inner elements
Labels: T-compiler,A-patterns,C-optimization

In maching without `|`, this is not optimized as slice compare:
```rust
let s: &[u8];
match s {
    &[b'a', b'b', ... , ..] => ...
    _ => ...,
}
```
Slice compare:
```rust
let s: &[u8];
let target = b"...";
if s.len() >= target.len() && &s[..target.len()] == target {
 ...
} else {
 ...
}
```
Integer: https://godbolt.org/z/csxf5zeYs
`&str`: https://godbolt.org/z/3Yr5nac3r
~~Not sure if this shoud be integer only.~~
Repository: angular
Issue: `withComponentInputBinding` allow binding to Route's `title` property
Labels: area: router

### Which @angular/* package(s) are relevant/related to the feature request?

router

### Description

It would be nice if `withComponentInputBinding` supports binding to the current route's `title` property via an `input`. 

### Proposed solution

Allow binding to the route's `title` property, similar to other supported properties.

```ts
readonly title = input.required<string>();
```

### Alternatives considered

The current approach is by accessing the `title` property via the Route's snapshot.

```ts
readonly title = this.activedRoute.snapshot.title;
```
Repository: react-native
Issue: [Bug] 0.76 with new arch off - border-radius with non-integer values causes faded bottom padding
Labels: Issue: Author Provided Repro,Needs: Attention,Type: Old Architecture,0.76

### Description

I have just updated to RN 0.76 and seeing some weird behavior with non integer values when applying corner radius. It creates a bottom padding that has a faded color.

### Steps to reproduce

Create a simple view and apply the following values:

```
  return (
    <View className="h-full bg-indigo-900 p-4">
      <View
        style={{
          marginVertical: 400,
          borderTopLeftRadius: 10,
          borderTopRightRadius: 10,
          backgroundColor: 'white',
          padding: 14,
        }}
      />
    </View>
```

The output should look like this:

![OSP 000480](https://github.com/user-attachments/assets/01671065-ea97-4899-9ab9-66e4cf6ff015)

But instead it looks like this:

![OSP 000479](https://github.com/user-attachments/assets/34a5110c-5ccd-47d4-b6dc-ce4ace002f1a)




### React Native Version

0.76.0

### Affected Platforms

Runtime - iOS

### Output of `npx react-native info`

```text
System:
  OS: macOS 15.0.1
  CPU: (11) arm64 Apple M3 Pro
  Memory: 223.63 MB / 36.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 20.13.1
    path: ~/.local/share/mise/installs/node/20/bin/node
  Yarn:
    version: 4.5.1
    path: ~/.local/share/mise/installs/node/20/bin/yarn
  npm:
    version: 10.5.2
    path: ~/.local/share/mise/installs/node/20/bin/npm
  Watchman:
    version: 2024.10.21.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.15.2
    path: /Users/osp/.local/share/mise/installs/ruby/3/bin/pod
SDKs:
  iOS SDK:
    Platforms:
      - DriverKit 24.0
      - iOS 18.0
      - macOS 15.0
      - tvOS 18.0
      - visionOS 2.0
      - watchOS 11.0
  Android SDK:
    API Levels:
      - "33"
      - "34"
      - "35"
    Build Tools:
      - 30.0.3
      - 33.0.0
      - 33.0.1
      - 34.0.0
      - 35.0.0
      - 35.0.0
    System Images:
      - android-33 | Google Play ARM 64 v8a
    Android NDK: 26.1.10909125
IDEs:
  Android Studio: 2024.2 AI-242.23339.11.2421.12483815
  Xcode:
    version: 16.0/16A242d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 21.0.3
    path: /usr/bin/javac
  Ruby:
    version: 3.3.1
    path: /Users/osp/.local/share/mise/installs/ruby/3/bin/ruby
npmPackages:
  "@react-native-community/cli":
    installed: 15.0.0
    wanted: ^15.0.0
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.76.0
    wanted: 0.76.0
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: false
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: Not found
```


### Stacktrace or Logs

```text
*
```


### Reproducer

https://github.com/ospfranco/border-radius-bug

### Screenshots and Videos

_No response_
Repository: ant-design
Issue: Modal Header & Footer Color Issue
Labels: Inactive,improvement

### Reproduction link

[https://ant.design/theme-editor](https://ant.design/theme-editor)

### Steps to reproduce

1. Navigate to: Component > Modal.
2. Attempt to change contentBg, footerBg, or headerBg color.

### What is expected?

The entire header background color should change without any padding.

### What is actually happening?

The header is wrapped inside the content, affecting the color change.


| Environment | Info |
| --- | --- |
| antd | 5.21.5 |
| React | react |
| System | Sequoia Version 15.0.1 |
| Browser | Google Chrome Version 130.0.6723.70 |

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: next.js
Issue: Turbopack: `resourceQuery` is empty for import URLs that are remapped in TypeScript
Labels: bug,Turbopack,linear: turbopack

### Link to the code that reproduces this issue

https://codesandbox.io/p/github/kdy1/repro-next-69502/csb-pl26sn/draft/modest-bassi

### To Reproduce

1. Have Turbopack configured to load `*.mdx` file with a custom loader
2. Created a file in the root folder: `/assets/test.mdx`
3. Update tsconfig.json's `compilerOptions.paths` to add `"assets/*": ["./assets/*"]`
4. Import the mdx file in a component: 
```typescript
import { v } from "assets/test.mdx?test";
```
5. Inside the custom loader, `this.resourceQuery` is empty

### Current vs. Expected behavior

**Current:**

`this.resourceQuery` is empty

**Expected:**

`this.resourceQuery` should be `?test`.

### 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.12.0
  npm: 10.5.0
  Yarn: 1.22.19
  pnpm: 8.15.6
Relevant Packages:
  next: 15.0.2-canary.9 // Latest available version is detected (15.0.2-canary.9).
  eslint-config-next: 14.1.0
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.3.3
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Turbopack

### Which stage(s) are affected? (Select all that apply)

next dev (local)

### Additional context

Disable Turbopack and use the identical Webpack configuration, `this.resourceQuery` gives the correct result of `?test`.

Related issue: https://github.com/vercel/next.js/issues/69502
Related PR: https://github.com/vercel/next.js/pull/69703
Repository: rust
Issue: Tracking issue for release notes of #118833: Add lint against function pointer comparisons
Labels: T-lang,relnotes,relnotes-tracking-issue


This issue tracks the release notes text for #118833.

### Steps

- [X] Proposed text is drafted by PR author (or team) making the noteworthy change.
- [ ] Issue is nominated for release team review of clarity for wider audience.
- [ ] Release team includes text in release notes/blog posts.

### Release notes text

The responsible team for the underlying change should edit this section to replace the automatically generated link with a succinct description of what changed, drawing upon text proposed by the author (either in discussion or through direct editing).

````markdown
# Language
- [Add `unpredictable_function_pointer_comparisons` lint to warn against function pointer comparisons](https://github.com/rust-lang/rust/pull/118833)
````

> [!TIP]
> Use the [previous releases](https://doc.rust-lang.org/nightly/releases.html) categories to help choose which one(s) to use.
> The category will be de-duplicated with all the other ones by the release team.
>
> *More than one section can be included if needed.*

### Release blog section

If the change is notable enough for inclusion in the blog post, the responsible team should add content to this section.
*Otherwise leave it empty.*

````markdown
````

cc @Urgau, @cjgillot -- origin issue/PR authors and assignees for starting to draft text
Repository: node
Issue: [Proposal] - Thead Safe data structures
Labels: feature request,worker

### What is the problem this feature will solve?

What I'd like to achieve is an implementation of shared (between worker threads) and thread safe data structures.
I want something easier to work with when doing multithread nodejs. Sharing data between threads using SharedArrayBuffer can be hard sometimes.


### What is the feature you are proposing to solve the problem?

I'll show you an example of what the API usage could look like for a data structure like LRU Cache:

This is the code in the main thread
```js
// main 
import {LRUCache} from "shared-ds"
import {Worker} from "worker_threads"

const cache = new LRUCache();

cache.set("test", { p1: "property1", p2: "property2" })

const worker = new Worker("./worker.js", {
    workerData: {
          lruCache: cache
    }
}

```
this is the worker code:

```js
import { workerData } from "worker_threads";
import { LRUCache } from "shared-ds";


const cache = LruCache.fromWorkerData(workerData.lruCache);

const testValue = cache.get("test");
console.log(testValue); // this outputs { p1: "property1", p2: "property2" }
```
I started working into an implementation that uses extensively SharedArrayBuffer and Atomics to reach thread safety but there are lots of problems to take into consideration like:

- Serialization of data into SharedArrayBuffer
- atomics operations ( I still did not figure out how I can read multiple 'bytes atomically' avoiding multiple Atomic.load calls)

Do you guys think it's a useful feature and worth implementing or taking it into consideration?

### What alternatives have you considered?

_No response_
Repository: next.js
Issue: Babel TypeScript transformer does not support satisfies operator in v13
Labels: bug

### Link to the code that reproduces this issue

https://stackblitz.com/edit/vercel-next-js-elkp8u?file=pages%2Findex.tsx

### To Reproduce

When using satisfies in the Next v13, incorrect syntax errors are thrown out as v13 is packaged with older versions of babel that do not have satisfies support.

### Current vs. Expected behavior

With the latest (or higher than current) babel version, satisfies would work correctly.

### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.3.0: Wed Dec 20 21:30:44 PST 2023; root:xnu-10002.81.5~7/RELEASE_ARM64_T6000
Binaries:
  Node: 20.17.0
  npm: 10.8.2
  Yarn: N/A
  pnpm: 8.6.1
Relevant Packages:
  next: 13.5.7
  eslint-config-next: 13.5.7
  react: 18.2.0
  react-dom: 18.2.0
  typescript: 5.6.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 build (local)

### Additional context

There was an issue long ago about this [here](https://github.com/vercel/next.js/issues/43799) which was closed by a PR [here](https://github.com/vercel/next.js/pull/51962), which made it into canary versions of 1.5.6 but somehow never to the full version.
Repository: godot
Issue: Godot UI unresponsive when extending primary monitor with secondary.
Labels: bug,needs testing,topic:gui

### Tested versions

Tested: 
Godot 4.0
Godot 4.3
Godot 4.4 dev3

### System information

Godot v4.4.dev3 - Windows 10.0.19045 - Multi-window, 1 monitor - Vulkan (Forward+) - dedicated NVIDIA GeForce RTX 3070 Laptop GPU (NVIDIA; 32.0.15.6081) - 11th Gen Intel(R) Core(TM) i7-11800H @ 2.30GHz (16 threads)

### Issue description

When Godot is opened on my primary (laptop) 4k display and I attach a secondary monitor to it that 'extends' that display. Where the second monitor has a different resolution, I tested with HD and 2K. Then after the desktop is extended, Godot's UI is unresponsive. 
It still reacts to key strokes although the main window won't update. 
(Scene Debug Editor Help) Buttons also still work, and open their associated pop ups.
Pop generally open. 

This does not happen if e.g. Godot is opened with the extended second monitor. Then the second monitor is disconnected and reconnected. In this case everything keeps working. 

### Steps to reproduce

Open Godot Project on primary 4k screen. 
Attach HDMI cable to display port
Wait until extended desktop is loaded.
Try clicking buttons in the UI

### Minimal reproduction project (MRP)

N/A
Repository: node
Issue: [Question] The difference between Buffer and ArrayBuffer
Labels: question,buffer,doc

### Affected URL(s)

_No response_

### Description of the problem

 I'd like to confirm: Does `ArrayBuffer` in node allocate shared heap memory for objects, and is `Buffer` a separate chunk from the heap memory?

If that's the case, isn't the size theoretically allocated by ArrayBuffer equivalent to the size of the heap memory(Maybe 1.7G?), and isn't the theoretical size of buffer [max_length](https://nodejs.org/api/buffer.html#bufferconstantsmax_length)?

According to #3012 , there was a related description a long time ago, but now there is no related description in the document.
Repository: vscode
Issue: Soft Assertion Failed
Labels: error-telemetry,diff-editor

```javascript
Error: Soft Assertion Failed
at But in src/vs/base/common/assert.ts:43:21
at $od in src/vs/editor/browser/widget/diffEditor/diffEditorViewModel.ts:527:3
at <anonymous> in src/vs/editor/browser/widget/diffEditor/diffEditorViewModel.ts:178:15
at Array.map (<anonymous>)
at o in src/vs/editor/browser/widget/diffEditor/diffEditorViewModel.ts:175:8
at updateUnchangedRegions in src/vs/editor/browser/widget/diffEditor/diffEditorViewModel.ts:312:5
at fn in src/vs/base/common/observableInternal/base.ts:303:3
at $ge in src/vs/editor/browser/widget/diffEditor/diffEditorViewModel.ts:310:4
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=384ff7382de624fb94dbaf6da11977bba1ecd427&bH=778c84e8-9419-da02-5c86-4ad67795bc9c)
Repository: ui
Issue: [bug]: The `ContextMenu` `onContextMenu` event propagating to the parent `ContextMenu` on `long-press`!
Labels: bug

### Describe the bug

I am building [r-cloud](https://r-cloud.vercel.app), a cloud storage provider progressive web application (PWA). I'm trying to make users feel as though they are interacting with an average `file-explorer`, thus using the `context menu` for some interactions

![Screenshot 2024-10-28 at 10 11 02](https://github.com/user-attachments/assets/999aef05-ff6d-4787-a5db-8913e4406a47)

![Screenshot 2024-10-28 at 10 13 15](https://github.com/user-attachments/assets/7477cc82-cf3d-4169-a325-a1b465ac2367)

Based on the path next to the R-cloud logo at the upper left side of these images, you can see that I'm in the `portfolio` sub directory, which is then our `current-folder`.

As you must've guessed already, the `current folder`'s card is wrapped with its own context menu, and each `file-card` & `folder-card` in this portfolio directory is also wrapped with its own context menu.

On desktop, when I `right-click` on a file-card or folder-card (file/folder) to trigger the context menu, the `event propagation` is fine, as the event is not caught by the parent (current folder's) context menu.

The problem is when I inspect or open the web app on a mobile phone (which I now have to use a `long-press` instead), The `contextmenu` event of the file/folder, is propagated to the parent context menu, opening both menus (both for the file/folder and that of the current-folder. In this case the portfolio folder) and giving this UI effect

![Screenshot 2024-10-28 at 10 30 51](https://github.com/user-attachments/assets/647bb904-359a-4591-ab5f-226301f41642)

### I tried the following

1 Added context menu even to the immediate divs of the `files/folders` with `addEventListerner` and stopping the `propagation` on the `capture` phase of the event to no avail

2 Repeating `step 1` but on the `body` tag instead but didn't solve it 

### Affected component/components

ContextMenu

### How to reproduce

1 Sign in/up to [r-cloud](https://r-cloud.vercel.app) 😁
2 Either create a new `folder` or upload a new `file`
3 Either Inspect on your desktop browser or just do steps `1 & 2` on a mobile phone
4 Try opening the `context-menu` of the file or folder you created by`long-pressing` on it
5 You will have reproduced the `bug` and have 2 context menus open

### Codesandbox/StackBlitz link

_No response_

### Logs

_No response_

### System Info

```bash
Chrome, Firefox
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: vscode
Issue: Tool "copilot_vscodeAPI" was not contributed.
Labels: error-telemetry

```javascript
Error: Tool "copilot_vscodeAPI" was not contributed.
at Ize.registerToolImplementation in out-vscode/vs/workbench/contrib/chat/browser/vs/workbench/contrib/chat/browser/languageModelToolsService.ts:82:10
at mFt.$registerTool in src/vs/workbench/api/browser/mainThreadLanguageModelTools.ts:51:54
at Pht.S in src/vs/workbench/services/extensions/common/rpcProtocol.ts:458:17
at Pht.Q in src/vs/workbench/services/extensions/common/rpcProtocol.ts:443:32
at Pht.M in src/vs/workbench/services/extensions/common/rpcProtocol.ts:373:19
at Pht.L in src/vs/workbench/services/extensions/common/rpcProtocol.ts:299:10
at vZ.value in src/vs/workbench/services/extensions/common/rpcProtocol.ts:161:57
at x.B in src/vs/base/common/event.ts:1243:13
at x.fire in src/vs/base/common/event.ts:1274:9
at D6.fire in src/vs/base/parts/ipc/common/ipc.net.ts:652:19
```
[Go to Errors Site](https://errors.code.visualstudio.com/card?ch=360bf09ae640d0faff2972106bfafa0dee7364bf&bH=280add4c-683f-6657-3ea3-c74c3d2dd307)