sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: react-native
Issue: autoComplete='off' does not disables the autocomplete in Android
Labels: Platform: Android,Impact: Bug

### Description

According to doc it says
> Specifies autocomplete hints for the system, so it can provide autofill. On Android, the system will always attempt to offer autofill by using heuristics to identify the type of content. To disable autocomplete, set autoComplete to off.

However with following code snippet, in Android we still get the autocomplete Hint.

``` jsx
<TextInput autoComplete='off' />
```

Output
![image](https://github.com/user-attachments/assets/2e05f290-cead-4d20-9b8e-ef85e0ec3cd4)



### Steps to reproduce

1. Open [Snack](https://snack.expo.dev/@endo-ngima/reproducer-rn-textinput-autocomplete-off)
2. Run it in Android
3. Start typing
4. You can see autocomplete suggestion

### React Native Version

0.75.3

### Affected Platforms

Runtime - Android

### Output of `npx react-native info`

```text
info Fetching system and libraries information...
System:
  OS: macOS 15.0
  CPU: (12) arm64 Apple M2 Pro
  Memory: 158.14 MB / 16.00 GB
  Shell:
    version: "5.9"
    path: /bin/zsh
Binaries:
  Node:
    version: 18.17.0
    path: ~/.nvm/versions/node/v18.17.0/bin/node
  Yarn:
    version: 3.6.4
    path: /opt/local/bin/yarn
  npm:
    version: 9.6.7
    path: ~/.nvm/versions/node/v18.17.0/bin/npm
  Watchman:
    version: 2024.09.16.00
    path: /opt/homebrew/bin/watchman
Managers:
  CocoaPods:
    version: 1.13.0
    path: /usr/local/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:
      - "31"
      - "33"
      - "34"
    Build Tools:
      - 30.0.3
      - 33.0.0
      - 33.0.1
      - 34.0.0
    System Images:
      - android-22 | Google APIs ARM 64 v8a
      - android-34 | Google APIs ARM 64 v8a
    Android NDK: Not Found
IDEs:
  Android Studio: 2024.1 AI-241.18034.62.2411.12071903
  Xcode:
    version: 16.0/16A242d
    path: /usr/bin/xcodebuild
Languages:
  Java:
    version: 17.0.11
    path: /usr/bin/javac
  Ruby:
    version: 2.6.10
    path: /usr/bin/ruby
npmPackages:
  "@react-native-community/cli": Not Found
  react:
    installed: 18.3.1
    wanted: 18.3.1
  react-native:
    installed: 0.75.3
    wanted: 0.75.3
  react-native-macos: Not Found
npmGlobalPackages:
  "*react-native*": Not Found
Android:
  hermesEnabled: true
  newArchEnabled: false
iOS:
  hermesEnabled: Not found
  newArchEnabled: false
```


### Stacktrace or Logs

```text
-
```


### Reproducer

https://snack.expo.dev/@endo-ngima/reproducer-rn-textinput-autocomplete-off

### Screenshots and Videos

_No response_
Repository: pytorch
Issue: `empty_like` with NJT on a different device fails because the offsets are not cast appropriately
Labels: triaged,module: nestedtensor,module: tensor creation

### 🐛 Describe the bug

This snippet fails
```python
import torch
device = torch.device("cuda:0")
a = torch.nested.nested_tensor_from_jagged(values=torch.randn(10), lengths=torch.tensor([2, 3, 5]))
torch.empty_like(a, device=device)
```
with
```
     86 assert offsets.ndim == 1
     87 assert not isinstance(values, NestedTensor)
---> 88 assert values.device == offsets.device
     90 # Query cache for the symint associated with offsets or lengths
     91 # (create a new one if needed).
     92 ragged_source = offsets if lengths is None else lengths

AssertionError: 
```

Not entirely sure how to work around that in the generic case - sending offsets to device separately will incur some extra cost and assumptions. For instance, it'll need to by done with `non_blocking=True` meaning that we'll have a cuda sync where users may not be expecting it.

The goal here is to do
```
torch.empty_like(x, device=device).set_(
                untyped_storage,
                size=x.shape,
                stride=stride,
                storage_offset=storage_offset,
            )
```
to create a view of a storage on a given device (ie, move a consolidated TD from host to device by moving the storage and rebuilding the tensors after that).
Casting the offsets separately on device doesn't really make sense, because we are moving them as part of the consolidated storage already.

I can find a workaround in tensordict, but we should think of how we want to handle this with NJT with a minimum of underlying H2D transfers.

cc @cpuhrsch @jbschlosser @bhosmer @drisspg @soulitzer @davidberard98 @YuqingJ @gchanan @mruberry

### Versions

latest nightlies
Repository: godot
Issue: Stuttering when mouse moves from one control to another in editor
Labels: bug,topic:editor,needs testing,performance

### Tested versions

- Godot 4.3

### System information

Windows 10 - RTX 3070 - Forward+ renderer - latest Nvidia drivers installed

### Issue description

This issue seems to only happen using Forward+ and the single/multi window option has no effect on it.
I noticed that when I move my mouse over a lot of UI elements, the editor starts to stutter, which makes it harder to efficiently aim with the mouse.
Somehow hovering over only a few elements in a short time doesn't seem to have any effect, but it feels like there is some "threshold" that suddenly create micro freezes when reached. It seems to be totally independent of the project's content, even an empty causes the issues.
Occasionally, that stutter results in an occasional single frame being rendered "dimmer" or even entirely black.

I tried to record the stutter in a video, but somehow the act of recording my screen magically makes the issue go away, and it comes back the moment I stop.

It feels like a typical rendering issue related to GPU drivers and such, but so far only Godot displays this kind of behavior on my computer.

Note that I can't see any spike in CPU or GPU usage when having this issue.

### Steps to reproduce

- Create an empty project with Forward+ renderer
- Open the project in editor
- Quickly move the mouse back and forth between several UI elements. (moving between a major part of the UI, like main screen and inspector, seems to make the effect even worse)

### Minimal reproduction project (MRP)

-
Repository: PowerToys
Issue: Using Snip tool to capture a window when mouse crosshairs is enabled captures the entire screen
Labels: Issue-Bug,Needs-Triage,Area-App Compat,Product-Mouse Utilities

### Microsoft PowerToys version

0.85.0

### Installation method

PowerToys auto-update

### Running as admin

No

### Area(s) with issue?

Mouse Utilities

### Steps to reproduce

- enable mouse crosshairs
- open snipping tool
- set snip tool to capture window
- create new snip
- snip tool doesn't track windows
- click to capture and entire screen(s) is captured

### ✔️ Expected Behavior

Expecting to be able to select the window & capture just that.

### ❌ Actual Behavior

The entire screen/screens is captured.

### Other Software

Snipping tool 11.2407.3.0
Repository: PowerToys
Issue: Brouwser tabs in workspace utility
Labels: Needs-Triage

### Description of the new feature / enhancement

I want the workspace utility to open the browser with specific tabs open on a specific profile.

### Scenario when this would be used?

I have a workflow where I need to have 20 tabs open in the browser (let's say chrome) on my work profile.

### Supporting information

By opening all the tabs in my work profile, I don't need to open all the tabs manually.
Repository: Web-Dev-For-Beginners
Issue: typinggame_solution_index.js
Labels: no-issue-activity

Issues found:
Child node selection issue: The code is using quoteElement.childNodes[0] and quoteElement.childNodes[wordIndex]. The childNodes property includes all nodes, such as text nodes, which can interfere with the correct selection of elements.

Solution: Use children instead of childNodes, as children only selects element nodes and excludes text nodes.

Handling case when the last word is typed correctly: In the current implementation, after the last word is typed, the code does not reset for a new round or disable further input to prevent errors.

UI elements might not exist: There's no check to ensure that the quoteElement, messageElement, and typedValueElement exist in the DOM before trying to manipulate them. If these elements are missing, it could cause runtime errors.

Unnecessary word space in spans: There's an extra space (" " after each word in the span element generation), which may lead to display issues when highlighting words.
Repository: deno
Issue: Custom (private) JSR registry support
Labels: suggestion,jsr

Similar to https://github.com/denoland/deno/issues/16105
I think Deno should support custom jsr repositories that can be used at the same time as jsr.io.
Repository: vscode
Issue: Editor: cannot Ctrl+click to goto definition in a link with a method name included
Labels: bug,editor-core

For example in this case:

https://github.com/microsoft/vscode-bisect/blob/379f271eb92182890a1969e0ab55a79c1834576f/src/builds.ts#L297-L299

I cannot goto definition to the method call, it always opens the link.

---
Edit from @hediet:
```js
console.log(`https://example.com/${foobar()}`); // Do Ctrl+Click on foobar -> opens link and goes to definition!

function foobar() {
}
```
Repository: node
Issue: Stack traces broken for static methods with --enable-source-maps
Labels: source maps

### Version

22.9.0

### Platform

```text
Microsoft Windows NT 10.0.22631.0 x64
```


### Subsystem

_No response_

### What steps will reproduce the bug?

With
```
class JSClass {
  static async foo() {
    throw new Error("JSClass");
  }
}
```

the stack trace without `--enable-source-maps` is
```
Error: JSClass
    at JSClass.foo (file:///C:/Users/mfischer/src/videmo/test/node-bug-enable-source-maps/index.mjs:3:15)
```
but with `--enable-source-maps` it becomes:
```
Error: JSClass
    at Function.foo (C:\Users\mfischer\src\videmo\test\node-bug-enable-source-maps\index.mts:3:11)
```

The class name is lost somewhere.

I also noticed that the class name is missing even without using `--enable-source-maps` when using prototype based inheritance instead of classes and also for napi classes created with `napi_define_class` (not included in repro below).

See detailed repro at https://github.com/mika-fischer/node-bug-enable-source-maps

So maybe the issue is not really with enable-source-map-support but that the standard `CallSite` serialization accesses some magic property that only works for real JS classes and is missing when using prototype based inheritance or `napi_define_class`. And enable-source-maps just uses the public accessors of `CallSite`, which don't seem to expose/use this property...

In any case I'm interested in both:
- `--enable-source-map` should retain the class names
- Static methods of classes defined with `napi_define_class` (and preferable also "classes" defined using protoype inheritance) should have the class name (with or without `--enable-source-maps`)



### How often does it reproduce? Is there a required condition?

Always

### What is the expected behavior? Why is that the expected behavior?

the stack trace should be
```
Error: JSClass
    at JSClass.foo (C:\Users\mfischer\src\videmo\test\node-bug-enable-source-maps\index.mts:3:11)
```

### What do you see instead?

the stack trace is
```
Error: JSClass
    at Function.foo (C:\Users\mfischer\src\videmo\test\node-bug-enable-source-maps\index.mts:3:11)
```

### Additional information

_No response_
Repository: kubernetes
Issue: Support takeover for devicemanager/device-plugin
Labels: priority/backlog,sig/node,kind/feature,triage/accepted

### What would you like to be added?

Add support for seamless takeover by a new device-plugin for a resource without deregistering the resource.

In other words, a new device-plugin can be started and registering the resource before the old device-plugin is stopped. In this case, devicemanager should not change the values of allocatable/total count for this resource.

### Why is this needed?

Currently, devicemanager only works with one device-plugin instance for every resource. In other words, if two device-plugin are running, devicemanager may have unexpected behaviors. 

For example, when two device-plugin are running, they are both registered for the same resource. However, if one of them stops, the resource is marked as deregistered and resource counts reset to 0.

We need this support to have seamless deployment of device-plugin. After this is supported, new device-plugin can be started while the old device-plugin is also running, and devicemanager should notice the new device-plugin, as it registers more recently, to be the new takeover and gracefully deregister/disconnect the old device-plugin. With this, there will be no downtime for resources in device-plugin updates.
Repository: PowerToys
Issue: Custom URL Opening in PowerToys Run
Labels: Needs-Triage

### Description of the new feature / enhancement

I would like to request the implementation of a "Custom URL Opening" feature in PowerToys Run, similar to the "Web Search" feature in Listary. This functionality would allow users to create custom URL shortcuts that dynamically insert queries, enabling quick access to web searches or internal systems.

For example, users could configure:

- Keyword: g
- Title: Google
- URL: http://www.google.com/search?q={query}

Typing "g PowerToys" in PowerToys Run would then open the default browser and search for "PowerToys" on Google (https://www.google.com/search?q=PowerToys).

This feature would allow great customization, enabling users to create shortcuts to various services, websites, and internal systems, enhancing productivity.

### Scenario when this would be used?

This feature would be useful in scenarios where users need quick access to specific web searches or internal systems using predefined URLs with dynamic query parameters. For example:

- Searching Google or other search engines with a keyword like "g."
- Accessing internal issue trackers like Redmine by typing something like "# 123" to open issue #123.
- Searching specific resources in shared drives by configuring a keyword like "f" to search a particular folder in Google Drive.

It would be especially beneficial for people working in environments with custom systems or shared resources, allowing them to quickly access these resources without opening the browser and typing the URL manually.

### Supporting information

This feature is already available in a similar tool called Listary, under the name "Web Search." It supports dynamic URL queries and is highly customizable. Implementing this in PowerToys Run would make it a more versatile tool, potentially attracting more users who need such flexibility.

Ref: https://www.listary.com/
Repository: pytorch
Issue: `batch_first` argument of `nn.Transformer()` should be `True` by default because it's not convenient to get a warning with the default settings
Labels: module: nn,triaged

### 🐛 Describe the bug

[nn.Transformer()](https://pytorch.org/docs/stable/generated/torch.nn.Transformer.html) with the default settings gets the warning as shown below because `batch_first` argument is `False` by default:

```python
from torch import nn

tran = nn.Transformer() # Warning
```

> UserWarning: enable_nested_tensor is True, but self.use_nested_tensor is False because encoder_layer.self_attn.batch_first was not True(use batch_first for better inference performance)
  warnings.warn(f"enable_nested_tensor is True, but self.use_nested_tensor is False because {why_not_sparsity_fast_path}")

So `nn.Transformer()` with `batch_first=True` doesn't get the warning as shown below:

```python
from torch import nn

tran = nn.Transformer(batch_first=True) # No warning
```

My suggestion is `batch_first` should be `True` by default because it's not convenient to get the warning with the default settings.

### Versions

```python
import torch

torch.__version__ # Error
```

cc @albanD @mruberry @jbschlosser @walterddr @mikaylagawarecki @bhosmer @cpuhrsch @erichan1 @drisspg
Repository: PowerToys
Issue: Color picker Functionality for formulae in custom color formats
Labels: Needs-Triage

### Description of the new feature / enhancement

Proposal for adding functionality to use calculated values in the color picker's custom color formats.
For example, multiplying the saturation with the HSV value to get a 'vividness' score.

If we call this new color format HSV Viv (hue, saturation, value, saturation*value), the _formula_ might be **HSV Viv(%Hu, %Sb, %Va, %Sb * %Va * 0.01)**
<img width="377" alt="CustomFormulaColorFormat" src="https://github.com/user-attachments/assets/9734786f-1d60-4b0e-9cc9-86bacb1f2120">

Of course, one should consider escaping the math operators in case users want to have math symbols written in their color picker readings.

### Scenario when this would be used?

Whenever users want to implement their own custom color formats.
Or when users want to have additional information shown that are calculated values based on the built-in values.

Also some Issues and Feature Requests could be directed towards 'the tool has the capabilities, there you can implement _xyz_ format', freeing up some time for urgent requests.

### Supporting information

_No response_
Repository: godot
Issue: @export_range's "radians_as_degrees" changes behaviour based on the default value in code
Labels: bug,topic:editor,usability

### Tested versions

Reproduced in v4.3.stable.official [77dcf97d8]

### System information

Godot v4.3.stable - Garuda Linux #1 ZEN SMP PREEMPT_DYNAMIC Thu, 12 Sep 2024 17:17:51 +0000 - X11 - GLES3 (Compatibility) - Mesa Intel(R) HD Graphics 630 (KBL GT2) - Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz (8 Threads)

### Issue description

When using `"radians"` or `"radians_as_degrees"` hints in `@export_range`, the behaviour changes based on the default value within the code:
- If the default values in the code are numbers, values inputted in the inspector field as degrees **will not** be converted to radians and will remain as degrees. (90deg in the inspector will result in the value of the variable being equal to 90)
- If the default values in the code are numbers multiplied by PI, values inputted in the inspector field as degrees **will** be converted to radians. (90deg in the inspector will result in the value of the variable being equal to 1.5708)

I believe this is unintuitive, as even a 0 as a default value will end up in degrees in the inspector not being converted to radians. In my specific case I was making a turret base class, with export variables used to adjust possible vertical/horizontal spread. Having set default values to 0, it was unclear why a +-5deg spread value set in the inspector resulted in shots fired in whatever direction possible ( `rotation.y = randi_range(-h_spread, h_spread)` does very different things if `h_spread` is in degrees vs radians. 

### Steps to reproduce

Create an empty project with an empty Node3D and add the following script to it. Then, in the inspector, set all export fields created by this script to any value in degrees. Run the scene and observe the output printed.

```
extends Node3D

@export_range(0,360, 1, "radians") var R_deg = 1
@export_range(0,360, 1, "radians") var R_rad = 1*PI
@export_range(0,360, 1, "radians_as_degrees") var RaD_deg = 1
@export_range(0,360, 1, "radians_as_degrees") var RaD_rad = 1*PI

func _ready() -> void:
	# comments after each line below represent the values printed if all inspector export values are set to 90
	print("Marked 'radians', default code value is 1: " + str(R_deg)) #90
	print("Marked 'radians', default code value is 1*PI: " + str(R_rad)) #1.5708
	print("Marked 'radians_as_degrees', default code value is 1: " + str(RaD_deg)) #90
	print("Marked 'radians_as_degrees', default code value is 1*PI: " + str(RaD_rad)) #1.5708

```

### Minimal reproduction project (MRP)

N/A
Repository: next.js
Issue: TypeError: Cannot read properties of undefined (reading 'call')
Labels: bug,Webpack,Navigation,Runtime

### Link to the code that reproduces this issue

https://github.com/JClackett/next-server-actions

### To Reproduce

Getting this consistently in production only and only for certain users

```
TypeError: Cannot read properties of undefined (reading 'call')

message: Cannot read properties of undefined (reading 'call'),
name: TypeError,
stack: TypeError: Cannot read properties of undefined (reading 'call') at l
(<url>/_next/static/chunks/webpack-0062ff542f3d788d.js?
```

I posted an issue a while back and am still struggling to get a repro, but it's consistently happening. I can see its happening on certain actions but when I test those in production it doesnt error, so im assuming its something to do with a user's browser maybe?

https://github.com/vercel/next.js/issues/67208

Looking into the sources there's one webpack file generated and there are 2 references to .call

```
try {
            f[e].call(n.exports, n, n.exports, l),
            r = !1
        } finally {
            r && delete d[e]
        }
```
and 
```
   l.o = function(e, t) {
        return Object.prototype.hasOwnProperty.call(e, t)
    },
```

I can see from the session replays that the server action isnt even being called, it throws an error on the client straight away as soon as the form is submitted.


### Current vs. Expected behavior

Server actions dont throw exceptions


### Provide environment information

```bash
Operating System:
  Platform: darwin
  Arch: arm64
  Version: Darwin Kernel Version 23.6.0: Mon Jul 29 21:14:30 PDT 2024; root:xnu-10063.141.2~1/RELEASE_ARM64_T6000
  Available memory (MB): 32768
  Available CPU cores: 8
Binaries:
  Node: 18.20.4
  npm: 10.7.0
  Yarn: 1.22.19
  pnpm: 8.15.7
Relevant Packages:
  next: 14.2.14 // Latest available version is detected (14.2.14).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.2
Next.js Config:
  output: N/A
```


### Which area(s) are affected? (Select all that apply)

Navigation, Runtime, Webpack

### Which stage(s) are affected? (Select all that apply)

Vercel (Deployed)

### Additional context

Deployed on vercel, production only.
Repository: PowerToys
Issue: CapsLock turns on when pressing combination Win+Ctrl with mapping of CapsLock->Ctrl
Labels: Issue-Bug,Needs-Triage,Needs-Team-Response

### Microsoft PowerToys version

0.85.0

### Installation method

PowerToys auto-update

### Running as admin

Yes

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

I have mapped left Ctrl to CapsLock which means that in place of CapsLock have left Ctrl and left Ctrl is left in place.

When using mappings connected to virtual desktops Win+Ctrl+<something> sometimes CapsLock (although it is mapped out to oblivion) turn on. But I effectively don't have Caps Lock so I have to manually turn off Keyboard Manager Toy, use CapsLock to turn it off and turn on Keyboard Manager.

### ✔️ Expected Behavior

Don't turn on Caps Lock when it is mapped out of keyboard.

### ❌ Actual Behavior

_No response_

### Other Software

_No response_