sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Fancy Zones Fullscreen
Labels: Needs-Triage

### Description of the new feature / enhancement

Make a window Fullscreen, instead of resizing a windows to the whole screen

### Scenario when this would be used?

It could be used as an alternative to double clicking the top bar of the window.

### Supporting information

A few programs differentiate between windowed and fullscreen. It would be nice to have it as an option to turn this behavior on or off.
Repository: vscode
Issue: Go To Line Behavior - Jump to line only on enter. 
Labels: feature-request,editor-core

<!-- ⚠️⚠️ 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. -->

Current Behavior: 
    Current go to line behavior jumps the courser to the inputted line on every insert. 
Feature Request: 
    Only jump the courser after the user has hit "enter"

Rationale:
    It is visually unpleasant and difficult to track when jumping to a line.
    IE If I'm on line 300, and I want to go to 305. Ctrl-G (goto line) will jump my page all the way to line '3', then to '30', then to '305'. Then I need to readjust and refocus my eyes to find the courser as my original positioning on my page is completely lost. 
      
Other standards to compare to:
    Big VisualStudio. Dialogue requesting goto-line only jumps after pressing enter.
    Vim: ':' and goto only jumps to line after pressing enter.
    Vim (VsCode plugin) follows the same implementation of Vim. 
     
     
Update:
Willing to make this PR myself if given some pointers to the relevant files/classes
Repository: pytorch
Issue: ProcessPoolExecutor resets all Tensors on the cuda device when using a cuda tensor
Labels: module: windows,module: multiprocessing,module: cuda,triaged

### 🐛 Describe the bug

If the `ProcessPoolExecutor` gets a cuda tensor, during the start of the new process, all values of all cuda tensors, are set to 0.

In the following example, all `untouched` tensors and the `touched` tensor are reset to 0. This happens only with cuda tensors.

```py
from concurrent.futures import ProcessPoolExecutor, wait, ALL_COMPLETED

import torch


def func(tensor):
    print(f"func: {tensor}")

def run():
    pool1 = ProcessPoolExecutor(1)

    untouched = torch.randperm(20, device=torch.device('cuda'))
    print(f"untouched - before: {untouched}")
    touched = torch.randperm(20, device=torch.device('cuda'))

    futures = [pool1.submit(func, touched)]

    untouched_2 = torch.randperm(20, device=torch.device('cuda'))
    print(f"untouched - started: {untouched}")
    print(f"untouched_2 - started: {untouched_2}")

    wait(futures, return_when=ALL_COMPLETED)

    print(f"untouched - finished: {untouched}")
    print(f"untouched_2 - finished: {untouched_2}")

if __name__ == '__main__':
    untouched_3 = torch.randperm(20, device=torch.device('cuda'))

    print(f"untouched_3 - before run: {untouched_3}")
    run()
    print(f"untouched_3 - after run: {untouched_3}")
```

### 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 10 Pro
GCC version: (x86_64-posix-seh-rev2, Built by MinGW-W64 project) 12.2.0
Clang version: Could not collect
CMake version: version 3.29.2
Libc version: N/A

Python version: 3.11.1 (tags/v3.11.1:a7a450f, Dec  6 2022, 19:58:39) [MSC v.1934 64 bit (AMD64)] (64-bit runtime)
Python platform: Windows-10-10.0.19045-SP0
Is CUDA available: True
CUDA runtime version: 12.1.66
CUDA_MODULE_LOADING set to: LAZY
GPU models and configuration: GPU 0: NVIDIA GeForce RTX 3080
Nvidia driver version: 551.78
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: True

CPU:
Architecture=9
CurrentClockSpeed=3701
DeviceID=CPU0
Family=107
L2CacheSize=6144
L2CacheSpeed=
Manufacturer=AuthenticAMD
MaxClockSpeed=3701
Name=AMD Ryzen 9 5900X 12-Core Processor
ProcessorType=3
Revision=8450

Versions of relevant libraries:
[pip3] mypy==1.9.0
[pip3] mypy-extensions==1.0.0
[pip3] numpy==1.26.4
[pip3] onnx==1.16.0
[pip3] onnxscript==0.1.0.dev20240330
[pip3] torch==2.4.1+cu124
[pip3] torchvision==0.19.1+cu124
[conda] Could not collect

cc @peterjc123 @mszhanyi @skyline75489 @nbcsm @iremyux @Blackhex @VitalyFedyunin @ptrblck @msaroufim
Repository: vscode
Issue: "go back" (Ctrl+Alt+-) goes berserk after search
Labels: bug,editor-find

<!-- ⚠️⚠️ 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

<!-- 🪓 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.1
- OS Version: Manjaro Linux

Steps to Reproduce:

1. Move around in the code
2. Hit Ctrl+F and search for a string that has occurrences in the code
3. Click somewhere in the code near to some of the results that were found
4. (Optional) Ctrl+click on some function call so as to navigate to somewhere else
5. Hit "Ctrl+Alt+-" to go back, and then again and again

Expected behavior: should go back to where you were before, and then where you were before that, etc

Observed: Starts going to completely random places that have nothing to do with my history of navigating through code, and selecting random portions of text.
Repository: PowerToys
Issue: Monitor input control/layout
Labels: Needs-Triage

### Description of the new feature / enhancement

New Feature
--
* Switch monitor between two inputs (HDMI to DP or DP1 to DP2 etc.) 
* When switching, remember and restore screen position of programs

### Scenario when this would be used?

This feature would complement "Mouse Without Borders," allowing people with multiple monitors (but perhaps one primary screen) to move their primary monitor between computers. As a computer programmer, this is something I do many times each day. I'm currently accomplishing this using a Rube Goldberg contraption consisting of ControlMyMonitor.exe, AHK, and RainMeter, but programs still get moved around in ways I don't expect.

### Supporting information

https://www.nirsoft.net/utils/control_my_monitor.html
Repository: ui
Issue: [bug]: CLI cannot detect electron.vite.config.ts
Labels: bug

### Describe the bug

I use electron-vite framework to develop electron application, and the generated vite configuration file is named election.vite.config.ts, which leads to the following error `could not detect a supported framework`

I guess this is a logical judgment problem of cli when detecting the framework, because I found the relevant code [getProjectInfo](https://github.com/shadcn-ui/ui/blob/078dfe66072c4ca780bbc99d4ad4b13b1f44fe7e/packages/shadcn/src/utils/get-project-info.ts#L97-L108)


### Affected component/components

CLI

### How to reproduce

1. go to  [electron-vite](https://electron-vite.org/guide/#scaffolding-your-first-electron-vite-project) to build a electron-vite project
2. run `pnpm dlx shadcn@latest init`

### Codesandbox/StackBlitz link

[link](https://github.com/JinJieBeWater/Noark/tree/issue_CLI-cannot-detect-electron.vite.config.ts)

### Logs

```bash
We could not detect a supported framework at D:\JinJieBeWater\Noark\Noark.
Visit https://ui.shadcn.com/docs/installation/manual to manually configure your project.
Once configured, you can use the cli to add components.
```


### System Info

```bash
We could not detect a supported framework at D:\JinJieBeWater\Noark\Noark.
Visit https://ui.shadcn.com/docs/installation/manual to manually configure your project.
Once configured, you can use the cli to add components.
```


### Before submitting

- [X] I've made research efforts and searched the documentation
- [X] I've searched for existing issues
Repository: go
Issue: proposal: encoding/xml: add flag for stricter XML char parsing
Labels: Proposal

### Proposal Details

## Background
As reported by @DemiMarie 

The encoding/xml package does not properly validate that the characters within comments, processing instructions, or directives are properly within the CharData range as defined by the XML specification.

## Proposal
Add a godebug flag, `xmlvalidatechars=1`, which enables more strict validation of characters within comments, processing instructions, and directives. It is my understanding that changing XML behavior can sometimes lead to unexpected behavior/breaking changes, but I have tested what would happen if this flag were enabled by default internally and ran into zero issues.
Repository: TypeScript
Issue: Cannot access protected field but private field inside nested class
Labels: Bug,Help Wanted

### 🔎 Search Terms

private, protected

### 🕗 Version & Regression Information

Version 5.6.2


### ⏯ Playground Link

https://www.typescriptlang.org/play/?#code/KYDwDg9gTgLgBAYwDYEMDOa4DEITgbwChC5S4woIZgFqATOGACwEs0BJNABUutuAYBeOAEYA3CTIUWANxTVGrDtyiz5wOMPHEycAEYooACgCUALhx4iu3QggA7NPGbzNithJtlJXqMBgArlD2cPbAAO6IqBhwoNT2dJiWBDpeNmgQALb+rPYA5qYpacVwfoHBivIAdMxsnDxqCgDUlTA1SvW8NPSeJaQAvj42g7qD-UA

### 💻 Code

```ts
export class Foo {

    protected thisIsProtected = 1;
    private thisIsPrivate = 1;

    bar():Foo {
        const that = this;
        
        return new class extends Foo {

            something() {
                return that.thisIsPrivate + that.thisIsProtected;
            }
        }
    }
}
```


### 🙁 Actual behavior

I get a compile error for `that.thisIsProtected`, but not for `that.thisIsPrivate`

### 🙂 Expected behavior

I can access the protected field, like the private

### Additional information about the issue

_No response_
Repository: angular
Issue: Canonical: Components cannot be fully initialized before `ApplicationRef.tick` with ZoneJS and `TestBed.createComponent`
Labels: area: testing,area: core,canonical

### Which @angular/* package(s) are the source of the bug?

core, zone.js

### Is this a regression?

Yes

### Description

TL;DR: Calling `TestBed.createComponent` will cause automatic application synchronization before the tester has an opportunity to fully initialize the component state.

`TestBed.createComponent` wraps the [component creation in an `NgZone.run`](https://github.com/angular/angular/blob/4231e8f28ffe8f55dddc2af0647b5b04fa8445d7/packages/core/testing/src/test_bed.ts#L701). When this closure exits, `NgZone` checks if the zone is stable, and if so, [emits `onMicrotaskEmpty`](https://github.com/angular/angular/blob/4231e8f28ffe8f55dddc2af0647b5b04fa8445d7/packages/core/src/zone/ng_zone.ts#L364-L367). This will cause automatic [application synchronization](https://github.com/angular/angular/blob/4231e8f28ffe8f55dddc2af0647b5b04fa8445d7/packages/core/src/change_detection/scheduling/ng_zone_scheduling.ts#L48-L58) before the tester has a chance to fully initialize the component (i.e. set inputs, run change detection before `afterNextRender` hooks run if they're defined in constructors, etc.). 

One workaround that developers can use today is to wrap all of their setup logic in an `NgZone.run` of their own, i.e.

```
const fixture = TestBed.inject(NgZone).run(() => {
  const fixture = TestBed.createComponent(MyComp);
  fixture.componentRef.setInput('requiredInput', 'initialValue');
  return fixture;
});
```

Related issues:

* https://github.com/angular/angular/issues/57313
* https://github.com/angular/angular/issues/57767
* https://github.com/angular/angular/issues/57856

### Please provide a link to a minimal reproduction of the bug

_No response_

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

_No response_

### Anything else?

_No response_
Repository: rust
Issue: AtomicU128/AtomicI128 not shown in std docs on rust-lang.org
Labels: A-docs,T-libs,A-atomic,A-target-feature

### Location

https://doc.rust-lang.org/nightly/std/?search=AtomicU128

### Summary

AtomicU128/AtomicI128 are hidden when the docs for std are built for the rust-lang website, I'm guessing this is likely because the website's docs are for x86_64-unknown-linux-gnu, which doesn't have 128-bit atomics due to not having the cmpxchg16b target feature enabled by default.

see also #99069
Repository: godot
Issue: `clip_children` not working with new WebKit
Labels: bug,platform:web,platform:ios,platform:macos,needs testing,topic:2d

### Tested versions

tested with 4.3.stable and 4.4-dev2

### System information

M1 MacOS 15.0 (Safari 18.0), iOS 18.1. Tested with Forward+ and Compatibility

### Issue description

![2024-09-17 19 48 10](https://github.com/user-attachments/assets/7b1b346e-3068-49ff-b9f6-9e3af6a1b77d)

WebKit (Safari on MacOS and all browsers on iOS) does not show the node when the clip_children value is set to anything other than Disabled.

But it seems like old WebKit doesn't have this issue:

![oldmac](https://github.com/user-attachments/assets/9af921cb-6ed3-42e8-82f4-a994afbb9093)
air 2017
safari 16.4.1
mac os monterey 12.7.1

![se](https://github.com/user-attachments/assets/2ef09f6d-7646-4c77-97d7-f2f78b0194ed)
Iphone SE
iOS 15.8.2


### Steps to reproduce

- Create Node
- Set clip_children to "Clip Only" or "Clip + Draw"
- Run in Browser
- Open in Safari

### Minimal reproduction project (MRP)

Demo project: https://github.com/TABmk/godot4-webkit-mask-bug

Demo build: https://tabmk.github.io/godot4-webkit-mask-bug/webkit-mask-bug.html
Repository: vscode
Issue: Many output bugs when printing to both STDOUT and STDERR; "There are more than 500 outputs"
Labels: bug,notebook-output

Type: <b>Bug</b>

I've long noticed that when using both `print` (STDOUT) and `logging.warn` (STDERR), there are issues with cell outputs and the way they collapse or don't collapse. I saw cases where multiple independent cell output windows were created. And recently I even saw a case where the outputs stopped completely with a message "There are more than 500 outputs".

Reproducing the issue is trivial - just use `print` and `logging.warning` or stderr in the same cell in a loop. Examples:
```
import time
for i in range(2000):
    for i in range(10):
        print("out")
    for i in range(5):
        print("err", file=sys.stderr)
    time.sleep(0.01)
```

This is very easy to trigger with tqdm as well:
```
import time
import tqdm
for i in tqdm.tqdm(range(2000)):
    for i in range(10):
        print("out")
    time.sleep(0.01)
```

Expected behavior: The output cell should behave the same (single, not verty long, partially hidden text) whether or not STDOUT is mixed with STDERR or not.

Extension version: 2024.7.0
VS Code version: Code 1.92.2 (fee1edb8d6d72a0ddff41e5f71a671c23ed924b9, 2024-08-14T17:29:30.058Z)
OS version: Windows_NT x64 10.0.19045
Modes:

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|AMD Ryzen 9 5950X 16-Core Processor             (32 x 3394)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: enabled_on<br>direct_rendering_display_compositor: disabled_off_ok<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>opengl: enabled_on<br>rasterization: enabled<br>raw_draw: disabled_off_ok<br>skia_graphite: disabled_off<br>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled<br>webnn: disabled_off|
|Load (avg)|undefined|
|Memory (System)|127.93GB (72.74GB free)|
|Process Argv|--crash-reporter-id 4c472b0d-1b85-4f57-b29c-3c522acbd317|
|Screen Reader|no|
|VM|0%|
</details><details>
<summary>A/B Experiments</summary>

```
vsliv368cf:30146710
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805:30301674
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
962ge761:30959799
pythongtdpath:30769146
welcomedialog:30910333
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
accentitlementsc:30995553
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
dsvsc021:30996838
724cj586:31013169
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupyter:31046869
2f103344:31071589
impr_priority:31102340
refactort:31108082
pythonrstrctxt:31112756
flighttreat:31119336
wkspc-onlycs-t:31111718
fje88620:31121564

```

</details>

<!-- generated by issue reporter -->
Repository: vscode
Issue: Jupyter notebook text editor output displays json
Labels: bug,notebook-output

### Applies To

- [X] Notebooks (.ipynb files)
- [ ] Interactive Window and\/or Cell Scripts (.py files with \#%% markers)

### What happened?

If I run a piece of code that prints say a very large piece of text, then I click "open in a text editor", then I run the code again to print a different also long piece of text, the text editor will then display this JSON:
```json
[
	{
		"metadata": {
			"outputType": "stream"
		},
		"outputItems": [
```

It is quite annoying as I want to be able to open large text blobs in a side window and then open another blob using the same cell without having to click "open in a text editor" again.

### VS Code Version

Version: 1.93.1 (user setup) Commit: 38c31bc77e0dd6ae88a4e9cc93428cc27a56ba40 Date: 2024-09-11T17:20:05.685Z Electron: 30.4.0 ElectronBuildId: 10073054 Chromium: 124.0.6367.243 Node.js: 20.15.1 V8: 12.4.254.20-electron.0 OS: Windows_NT x64 10.0.22631

### Jupyter Extension Version

v2024.8.1

### Jupyter logs

_No response_

### Coding Language and Runtime Version

_No response_

### Language Extension Version (if applicable)

_No response_

### Anaconda Version (if applicable)

_No response_

### Running Jupyter locally or remotely?

Local
Repository: godot
Issue: ItemList truncation does not show ellipsis (...) with new script editor list minimum width
Labels: bug,topic:editor,regression

### Tested versions
Appears in editor in 4.4 since https://github.com/godotengine/godot/pull/96909
Not visible in editor in 4.3, but the underlying behavior in ItemList is observable in 4.3

### System information

Windows 10

### Issue description

In an ItemList, names are truncated if they are too wide for the list. Usually this is done with an ellipsis `...`, but when the width is small enough, no ellipsis is used. I think this is good intended behavior, otherwise only an ellipsis would be shown at very low widths.

Since https://github.com/godotengine/godot/pull/96909 set the minimum width of the script list to 100, the width is small enough that many script names are now truncated with no ellipsis. This happens *right around* a script list width of 100. For `new_script.gd`, the threshold for the behavior happens at 101px wide, so it was easily noticeable when testing.

I believe this is *existing behavior* of the ItemList truncation, but since the preview editor script list minimum was above the threshold, it was not visible to godot editor users. The MRP is created and tested in 4.3, and replicates the same behavior if the width is low enough.

Observed behavior in the https://github.com/godotengine/godot/pull/96909 artifact:

https://github.com/user-attachments/assets/17179298-3a6d-4d83-b0af-7be34a7d144e

Observed behavior in the MRP (created and tested in 4.3). 

https://github.com/user-attachments/assets/bd7a7570-f944-4e00-a27c-fe37b4597373

Possible resolutions:
- Tweak the truncation limits so that an ellipsis is still used at the minimum script width of 100.
- Tweak the minimum script width to 105 or 110, to barely avoid this behavior.
- Do nothing, as this *is* intended behavior, just an edge case that usually doesn't come up in the editor. In this case the user is knowingly making their editor UI crowded in exchange for extra script editor space, and minor "problems" like this may be expected. (It's me. I'm user. 😃)

CC @aXu-AP

### Steps to reproduce

Open the MRP. 
Adjust the HSplitContainer left and right. You can test with and without 16x16 icons.

### Minimal reproduction project (MRP)

[mrp-truncation.zip](https://github.com/user-attachments/files/17032862/mrp-truncation.zip)
Repository: deno
Issue: Absolute imports do not work correctly
Labels: question,needs info

Version: Deno 1.46.3

I'm getting this error , when importing a file using dynamic import
```
TypeError: Relative import path "react" not prefixed with / or ./ or ../
```

How to reproduce:
let's say I have folder A which is a deno project and has a deno.json file
and then I have project B which also have a deno.json file

Now in project A in some file I'm using a dynamic import  I'm trying to import a file from project B and that file in project B has (import react from 'react') inside

Now I have in both projects in deno.json in imports section this "react": "npm:react@18.3.5"
But even that doesn't help and I get the error that it is a relative import and react needs to be prefixed

But why is that if both projects have the dependency in the imports?

Is that I'm using a dynamic import with a absolte path in it?
like that 
```
const a = await import(absolutePathToFile)
```
And the in that absolutePathToFile in that file I have (import react)
Repository: electron
Issue: [Bug]: Electron ignores XCompose settings when running natively on Wayland
Labels: platform/linux,bug :beetle:,has-repro-gist,30-x-y

### 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

33.2.0

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

Other Linux

### Operating System Version

NixOS 24.05

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

Compose sequences defined in `~/.XCompose` can be typed.

### Actual Behavior

When running natively on Wayland, user-defined compose sequences are unrecognized; only the system default compose sequences can be typed.

### Testcase Gist URL

_No response_

### Additional Information

Re https://github.com/electron/electron/issues/39957#issuecomment-1785932393