sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: electron
Issue: [Bug]: resizable=false window feature makes windows not resizable though that's not in the spec anymore
Labels: platform/windows,bug :beetle:

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/main/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/main/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a bug report that matches the one I want to file, without success.

### Electron Version

32

### What operating system(s) are you using?

Windows

### Operating System Version

Windows 11

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

`window.open(url, name, "resizable=false")` should create a resizable window


### Actual Behavior

`window.open(url, name, "resizable=false")` creates a window that isn't resizable

### Testcase Gist URL

_No response_

### Additional Information

The modern [spec](https://html.spec.whatwg.org/multipage/nav-history-apis.html#dom-open-dev) doesn't mention this feature besides saying it controls whether a page opens in a popup (vs in a tab).

[This comment](https://github.com/whatwg/html/issues/2464#issuecomment-289168412) says:
>Many of the other window features that Chrome used to check (resizable, menubar, status, scrollbars) are things that aren't configurable anymore: popups are always resizable

I think this used to be a supported feature and then got removed, so Electron should probably stop respecting it.

(can observe this in the default Fiddle by opening devtools and running `window.open("https://example.com", "", "resizable=false");`)
Repository: pytorch
Issue: [export] is_fx_tracing evaluates to true when exporting non-strict
Labels: triaged,oncall: pt2,oncall: export

### 🐛 Describe the bug

Symbolic trace's `is_fx_tracing` flag evaluates to `True` when tracing with non-strict export, which causes some errors when tracing NJT. The actual code which is causing issues is [here](https://github.com/pytorch/pytorch/blob/058a69d91a38f0efaf64c8b964b275dc7e1c65d0/torch/nested/__init__.py#L389-L394), but here's a simple repro:

```
    def test_is_fx_tracing(self):
        from torch.fx._symbolic_trace import is_fx_tracing
        class M(torch.nn.Module):
            def forward(self, x):
                if is_fx_tracing():
                    raise RuntimeError("moo")
                else:
                    return x + x
        
        ep = torch.export.export(M(), (torch.ones(3),), strict=False)  # RuntimeError raised
```

A simple fix is to replace the `if is_fx_tracing()` with `if not torch.compiler.is_compiling() and is_fx_tracing()`, since the `not torch.compiler.is_compiling()` will evaluate to `False`, but I find it weird that `is_fx_tracing()` evaluates to `True`.

cc @ezyang @chauhang @penguinwu @avikchaudhuri @gmagogsfm @zhxchen17 @tugsbayasgalan @suo @ydwu4 @YuqingJ 

### Versions

main
Repository: godot
Issue: Dictionary.duplicate(true) still does not make a recursive deep copy
Labels: discussion,topic:core,documentation

### Tested versions

Personal experience: 4.3
I have also seen [documentation of this bug from over 4 years ago](https://github.com/godotengine/godot/issues/37162), as well as some [more recent reports](https://github.com/mphe/SmartShape2D/issues/32).

### System information

Windows 11

### Issue description

The documentation for the Dictionary class states "If deep is true, inner Dictionary and [Array](https://docs.godotengine.org/en/stable/classes/class_array.html#class-array) keys and values are also copied, **recursively**." for the duplicate method. However, the objects in dictionaries created via the Dictionary.duplicate(true) function still act as references to those in the duplicated dictionary, implying either that a shallow copy or a non-recursive deep copy was made, instead of the recursive deep copy proscribed by the documentation. 

### Steps to reproduce

Create a dictionary. Put an array of objects passed by reference into the dictionary. Call duplicate(true) on the dictionary. Alter an object in the array in the result of the duplicate function. Print or otherwise display the object it corresponds to in the original dictionary. It will appear as if a shallow copy had been made, despite described behavior specifying a deep copy.

### Minimal reproduction project (MRP)

I do not currently have access to a Godot editor to make a MRP. I hope the issue is simple enough fort my description to be sufficient.
Repository: flutter
Issue: Text Duplication Issue with Microsoft Translate Keyboard in Flutter Text Fields
Labels: a: text input,platform-android,a: internationalization,has reproducible steps,P2,team-text-input,triaged-text-input,found in release: 3.24,found in release: 3.25

### Steps to reproduce

1.Create a basic Flutter app with a text field.
2.On a device with the Microsoft Translate keyboard installed, set it as the active keyboard.
3.Focus on the text field in the Flutter app.
4.Type any word or phrase using the Microsoft Translate keyboard.
5.Observe that the entered text appears twice in the text field.

### Expected results

The text should appear only once in the text field, as entered.

### Actual results

The text is duplicated, with each word or phrase appearing twice.

### Code sample

```dart
import 'package:flutter/material.dart';

void main() {
  runApp(MyApp());
}

class MyApp extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        appBar: AppBar(
          title: Text('Text Field Example'),
        ),
        body: Center(
          child: Padding(
            padding: EdgeInsets.all(20.0),
            child: TextField(
              decoration: InputDecoration(
                hintText: 'Enter text here',
                border: OutlineInputBorder(),
              ),
            ),
          ),
        ),
      ),
    );
  }
}
```
### Screenshots or Video

video: 

https://github.com/user-attachments/assets/004c5ff4-ebf7-450a-818b-4882c777451f

In this video, I'm using a subtitle editor app. When I want to translate text to any language using the Microsoft Translator keyboard, I encounter an issue. After selecting the text and clicking on translate, the translated text appears twice.

For example, this issue occurs when I translate from English to Kurdish Central, English to Arabic, or any other language combination.

Steps to reproduce:
1. Open the any app created in flutter have Text Field
2. Select a piece of text
3. Use the Microsoft Translator keyboard to translate the selected text
4. Observe that the translated text appears twice in the text field

This issue consistently occurs regardless of the source or target language.

### Logs

<details open><summary>Logs</summary>

```console
[Paste your logs here]
```

</details>


### Flutter Doctor output

[√] Flutter (Channel stable, 3.24.1, on Microsoft Windows [Version 10.0.19045.3570], locale en-US)
    • Flutter version 3.24.1 on channel stable at C:\src\flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5874a72aa4 (2 weeks ago), 2024-08-20 16:46:00 -0500
    • Engine revision c9b9d5780d
    • Dart version 3.5.1
    • DevTools version 2.37.2
Repository: pytorch
Issue: [Distributed] Non-0 ranks creating CUDA contexts on device 0
Labels: high priority,triage review,oncall: distributed

### 🐛 Describe the bug

Symptom:
![image](https://github.com/user-attachments/assets/ca41c0f1-9896-47b8-a3d5-962d10c5f71a)

Each non-0 rank is occupying ~ 1GB memory on GPU 0.

### Versions

Simple repro:
`torchrun --standalone --nproc-per-node 4 repro.py`

```
import torch
import os
import torch.distributed.distributed_c10d as c10d

def repro(rank, world_size):
    device = torch.device("cuda:%d" % rank)
    #torch.cuda.set_device(device)
    c10d.init_process_group(
        backend="nccl", rank=rank, world_size=world_size, device_id=device,
    )
    
    x = torch.ones((10,), device=device)
    c10d.all_reduce(x)
    c10d.destroy_process_group()
    print("clean exit")

if __name__ == "__main__":
    repro(int(os.environ["RANK"]), int(os.environ["WORLD_SIZE"]))

```

Note:
The issue can be avoided if user uncomments the `torch.cuda.set_device(device)` line. But this is not / has not been a requirement of distributed.

cc @ezyang @gchanan @zou3519 @kadeng @msaroufim @XilunWu @H-Huang @awgu @wanchaol @fegin @fduwjj @wz337 @wconstab @d4l3k @c-p-i-o
Repository: PowerToys
Issue: Bug keyboard manager - Please help me
Labels: Issue-Bug,Needs-Triage

### Microsoft PowerToys version

v084.0

### Installation method

GitHub

### Running as admin

No

### Area(s) with issue?

Keyboard Manager

### Steps to reproduce

Hi, I have a problem and I really need help.

I recently changed my keyboard settings using the PowerToys keyboard manager on my Dell notebook (Windows 11). I changed the number keys on the right of the keyboard because I wanted to make it easier to play a game. I changed the Numpad 1, Numpad 2, Numpad 3 and Numpad 4 keys to the left, down, right and up keys, respectively. I did this because my direction pads are very small and I wanted greater comfort in gameplay. However, when I went to remove this remapping, the keys no longer returned, even though I deleted the settings, restarted my notebook, deleted PowerToy and installed it again, and nothing returned to normal, the keys did not return. What can I do? Please, help me.

### ✔️ Expected Behavior

_No response_

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: vscode
Issue: `@builtin @enabled` doesn't work
Labels: feature-request,extensions

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: 1.93.0
- OS Version: Windows 11

Steps to Reproduce:

1. goto to extensions view
2. type `@builtin @enabled`

Expected:
All _enabled_ builtin extensions to show up

Actual:
nothing

![image](https://github.com/user-attachments/assets/0a442097-c0f6-4aa9-9a84-781108eba492)

the same is also true for `@builtin @disabled` etc
Repository: rust
Issue: `#[cfg(...)]` attribute is incorrectly removed from a function parameter inside of the derive macro
Labels: A-macros,T-compiler,C-bug,A-proc-macros,A-cfg

I tried this code:

```rust
// my_macro proc-macro crate
use use proc_macro::TokenStream;

#[proc_macro_derive(Derive)]
pub fn derive(input: TokenStream) -> TokenStream {
    eprintln!("{input}");
    TokenStream::default()
}

// lib.rs
#[derive(my_macro::Derive)]
enum Enum {
    X = {
        fn foo(#[cfg(any())] arg1: (), arg2: ()) {}
        0
    },
}
```

I'm not sure what exactly I expected to see in the `stderr` output when I compile the crate. Maybe this with the `#[cfg(...)]` attribute left intact on the function
```rust
enum Enum { X = { fn foo(#[cfg(any())] arg1: (), arg2: ()) {} 0 }, }
```
or this with the `#[cfg(...)]` attribute completely removed togther with the syntax it was placed on:
```rust
enum Enum { X = { fn foo(arg2: ()) {} 0 }, }
```

Instead, the output is invalid rust code:

```rust
enum Enum { X = { fn foo(, arg2: ()) {} 0 }, }
```
Notice that the `#[cfg(...)]` was removed, but... the coma after the function parameter was not removed. This output results in an invalid token tree not parsable by `syn`

### Meta
`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
```

## Context

Why would I ever write such code? I'd like to support conditional compilation with my proc macro that generates a builder from a function called [`bon`](https://github.com/elastio/bon). But... since it's a proc macro attribute, the `#[cfg(...)]` and `#[cfg_attr(...)]` attributes aren't automatically removed when the macro runs. 

So I thought I'd workaround it by delegating to a derive macro that accepts the function item in the expression position as the first item of the block for the default value of the enum's variant. This is because derive macros benefit from automatic expansion of `#[cfg(...)/cfg_attr(...)]` attributes before they run. Thus, by using a derive macro wrapper I could get the results of cfg evaluation this way.

I could work around that by passing the item as an argument to the proc-macro derive... But IDEs and Rust Analyzer don't work this way. They somehow mess up span information.
Repository: PowerToys
Issue: [Workspaces] Saving and loading File Explorer with tabs
Labels: Needs-Triage,Tracker,Product-Workspaces

### Description of the new feature / enhancement

All tabs in the File Explorer should be saved and opened when launching the workspace.

### Scenario when this would be used?

Currently, Workspace is able to open multiple File Explorer instances. However, adding a feature to allow saving/loading File Explorer with (the user saved) tabs would be nice for organization or small screen setups.

### Supporting information

_No response_
Repository: puppeteer
Issue: [Bug]: BrowserWebSocketTrasnport errors are ignored
Labels: bug,confirmed,P3

### Minimal, reproducible example

```TypeScript
// websocket of connected chrome instance receives error as result of message
```


### Background

Working with `@cloudflare/puppeteer` I got a WebSocket error when attempting to capture a screenshot that was beyond the size limit for a workerd WebSocket message (see https://github.com/cloudflare/workerd/issues/2667)

The resulting error was ignored by puppeteer, meaning my automation was left in a hanging state (could not cleanup browser connection of capture error).

After some digging through Puppeteer, this comment seems to indicate the problem: https://github.com/puppeteer/puppeteer/blob/main/packages/puppeteer-core/src/common/BrowserWebSocketTransport.ts#L39

My naive solution was to call `onmessage` with something non-protocol like that could be caught in `Connection`, which would subsequently call `#callbacks.clear()`. Would you be open to a pull request along those lines are am I completely missing the complexity of such a change :)

### Expectation

Transport errors should probably result in a TargetClose error?

### Reality

Transport errors result in unresolved promises and hanging automations.

### Puppeteer configuration file (if used)

_No response_

### Puppeteer version

@cloudflare/puppeteer@0.0.14

### Node version

20.10.0

### Package manager

npm

### Package manager version

10.2.3

### Operating system

macOS
Repository: TypeScript
Issue: False positive for "Unreachable code detected" for code following `switch`/`case` with `allowUnreachableCode: false`
Labels: Suggestion,Awaiting More Feedback

### 🔎 Search Terms

"false positive allowUnreachableCode"
"allowUnreachableCode case statement"
"Unreachable code detected case statement"

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about `switch`/`case`

### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/C4TwDgpgBAYg9nKBeKAiARgQwE6qgHzSwC9UAoMgYzgDsBnYKAMxuSgAoA3TAGwFcIALlgIAlMJp8AtugjZkAPigBvMlHVQ6AdwCWwSgAsuvAaJVqNlypjrQMOVIIuWXUbBGB9srAIwBuZxdrWyJMUidXV3dPbygAJgDLAF8KS2ivVhtbbGAAOQhOOXZUGjhIAEJUUQCUqloGZho4tmN+IRE4cShJGTlFc0ttPUNW0wHI4LssXAjItI8MqH9AqxspsMcVyPTYhK31ABMIJkw+HmBZufUdzLpsvIKikrKISurAlNrqekYWAGYWtw2sJ4J0JNJZPIkEpVJYdExRtAkMjQrgzLDtgtYstklAIDwQvCOECBMgUfZSOj9m4saw9slAoEblAsnIHoVsMVShUqjUKEw+DRKMAdLQWXc2fkOewpBA7pgAOYQAD8wgY2B0NAVXRoj3kGOABmwcC03QgpoAothjZzZfKlVBlcq0AAVAw6OhQahHKBaGx4gAekGFEAOUGAiFkUEF7kwhkw6B4EAAdLyyLUWMUEGA6Hh-aDRGQWHEs2Vc+KOoX-qWc3nPQWyEA

### 💻 Code

```ts
type Foo = "bar" | "baz"

const fn = (value: Foo): number => {
    switch(value) {
        case "bar":
            return 1;
        case "baz":
            return 2;
    }

    return assertNever("nope!");
}
```


### 🙁 Actual behavior

```ts
return assertNever("nope!");
```
is highlighted as "Unreachable code detected". The [docs](https://www.typescriptlang.org/tsconfig/#allowUnreachableCode), however, state:
> This does not affect errors on the basis of code which appears to be unreachable due to type analysis.

### 🙂 Expected behavior

No error. This should be the same as the other case form, the if form, and various similar constructs where even though it's _allegedly_ exhaustive, that's just based off of type information (I would like to have a runtime assertion in this case).

### Additional information about the issue

Possibly related to: https://github.com/microsoft/TypeScript/issues/18882
Repository: pytorch
Issue: DISABLED test_profiler_mark_wrapper_call_dynamic_shapes_cpu (__main__.DynamicShapesCpuTests)
Labels: triaged,module: flaky-tests,skipped,oncall: pt2,module: inductor

Platforms: linux

This test was disabled because it is failing in CI. See [recent examples](https://hud.pytorch.org/flakytest?name=test_profiler_mark_wrapper_call_dynamic_shapes_cpu&suite=DynamicShapesCpuTests&limit=100) and the most recent trunk [workflow logs](https://github.com/pytorch/pytorch/runs/29751966360).

Over the past 3 hours, it has been determined flaky in 10 workflow(s) with 30 failures and 10 successes.

**Debugging instructions (after clicking on the recent samples link):**
DO NOT ASSUME THINGS ARE OKAY IF THE CI IS GREEN. We now shield flaky tests from developers so CI will thus be green but it will be harder to parse the logs.
To find relevant log snippets:
1. Click on the workflow logs linked above
2. Click on the Test step of the job so that it is expanded. Otherwise, the grepping will not work.
3. Grep for `test_profiler_mark_wrapper_call_dynamic_shapes_cpu`
4. There should be several instances run (as flaky tests are rerun in CI) from which you can study the logs.



<details><summary>Sample error message</summary>

```
Traceback (most recent call last):
  File "/var/lib/jenkins/workspace/test/inductor/test_torchinductor.py", line 9497, in test_profiler_mark_wrapper_call
    with profile() as prof:
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/profiler/profiler.py", line 744, in __enter__
    self.start()
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/profiler/profiler.py", line 754, in start
    self._transit_action(ProfilerAction.NONE, self.current_action)
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/profiler/profiler.py", line 793, in _transit_action
    action()
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/profiler/profiler.py", line 174, in start_trace
    self.profiler._start_trace()
  File "/opt/conda/envs/py_3.10/lib/python3.10/site-packages/torch/autograd/profiler.py", line 339, in _start_trace
    _enable_profiler(self.config(), self.kineto_activities)
MemoryError: std::bad_alloc

To execute this test, run the following from the base repo dir:
    python test/inductor/test_torchinductor_dynamic_shapes.py DynamicShapesCpuTests.test_profiler_mark_wrapper_call_dynamic_shapes_cpu

This message can be suppressed by setting PYTORCH_PRINT_REPRO_ON_FAILURE=0
```

</details>


Test file path: `inductor/test_torchinductor_dynamic_shapes.py`

cc @clee2000 @ezyang @chauhang @penguinwu @voznesenskym @EikanWang @jgong5 @Guobing-Chen @XiaobingSuper @zhuhaozhe @blzheng @wenzhe-nrv @jiayisunx @ipiszy @yf225 @chenyang78 @kadeng @muchulee8 @ColinPeppler @amjames @desertfire
Repository: godot
Issue: `GLES3` shadeless colors are incorrect compared to `Vulkan`  [3D]
Labels: bug,discussion,topic:rendering,needs testing

### Tested versions

4.3 stable

### System information

Windows 10

### Issue description

Left side is a SubViewport contains a `MeshInstance3D` plane.
Right side is a `Sprite2D`

GLES3:
![GLES3](https://github.com/user-attachments/assets/90bc537a-0d92-40e9-af3e-82e9b4daaea6)

Vulkan:
![vulkan](https://github.com/user-attachments/assets/e1b22a10-13f8-4cc9-b70d-6fbc5de81864)


### Steps to reproduce

N/A

### Minimal reproduction project (MRP)

[minimal_reproduction_project.zip](https://github.com/user-attachments/files/16901561/test.zip)
Repository: flutter
Issue: [video_player_android] Incorrect orientation when previewing captured videos
Labels: platform-android,p: video_player,package,has reproducible steps,P1,team-android,triaged-android,found in release: 3.24,found in release: 3.25

### Workaround

**Pin `video_player_android` to 2.7.1.**

### Steps to reproduce

#### With the official example

1. Run the example of `camera`
2. Select a camera and record for a few seconds in portrait up.
3. See the preview video being orientated incorrectly.

#### With other Flutter packages

Run the example of `package:wechat_camera_picker`.

### Expected results

The video preview should have a correct rotation.

### Actual results

The video preview shows an incorrect rotation. This is likely affected by https://github.com/flutter/packages/pull/6456, and we also have similar problems with `camera_android_camerax`: https://github.com/flutter/flutter/issues/149177, and `camera_android`: https://github.com/flutter/flutter/issues/150549.

### Code sample

https://github.com/flutter/packages/tree/main/packages/camera/camera/example

### Screenshots or Video

<details open>
<summary>Screenshots / Video demonstration</summary>

https://github.com/user-attachments/assets/8b0f6067-31ca-47f8-a945-84b6ed34cc6e

</details>


### Logs

N/A

### Flutter Doctor output

<details open><summary>Doctor output</summary>

```console
[✓] Flutter (Channel master, 3.25.0-1.0.pre.270, on Microsoft Windows [Version 10.0.22631.4037], locale en-US)
    • Flutter version 3.25.0-1.0.pre.270 on channel master at X:\SDK\flutter-master
    • Upstream repository https://github.com/flutter/flutter
    • Framework revision a7cd788d80 (16 hours ago), 2024-09-05 05:57:40 -0400
    • Engine revision 34b61eb53b
    • Dart version 3.6.0 (build 3.6.0-216.0.dev)
    • DevTools version 2.39.0
    • Pub download mirror https://pub.flutter-io.cn
    • Flutter download mirror https://storage.flutter-io.cn

[✓] Windows Version (Installed version of Windows is version 10 or higher)

[✓] Android toolchain - develop for Android devices (Android SDK version 35.0.0)
    • Android SDK at X:\Android\SDK
    • Platform android-35, build-tools 35.0.0
    • ANDROID_HOME = X:\Android\SDK
    • ANDROID_SDK_ROOT = X:\Android\SDK
    • Java binary at: X:\IDEs\AndroidStudio\jbr\bin\java
    • Java version OpenJDK Runtime Environment (build 17.0.11+0--11852314)
    • All Android licenses accepted.
```

</details>