sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: test_wishart_log_prob fails locally for me
Labels: module: distributions,module: tests,triaged

### 🐛 Describe the bug

```
======================================================================
ERROR: test_wishart_log_prob (__main__.TestDistributions)
----------------------------------------------------------------------
Traceback (most recent call last):
  File "/data/users/ezyang/pytorch-tmp/test/distributions/test_distributions.py", line 2309, in test_wishart_log_prob
    expected = ref_dist.logpdf(x.transpose(0, 2).numpy())
  File "/home/ezyang/local/pytorch-tmp-env/lib/python3.9/site-packages/scipy/stats/_multivariate.py", line 2258, in logpdf
    out = self._dist._logpdf(x, self.dim, self.df, self.scale,
  File "/home/ezyang/local/pytorch-tmp-env/lib/python3.9/site-packages/scipy/stats/_multivariate.py", line 1851, in _logpdf
    _, log_det_x[i] = self._cholesky_logdet(x[:, :, i])
  File "/home/ezyang/local/pytorch-tmp-env/lib/python3.9/site-packages/scipy/stats/_multivariate.py", line 2221, in _cholesky_logdet
    c_decomp = scipy.linalg.cholesky(scale, lower=True)
  File "/home/ezyang/local/pytorch-tmp-env/lib/python3.9/site-packages/scipy/linalg/_decomp_cholesky.py", line 88, in cholesky
    c, lower = _cholesky(a, lower=lower, overwrite_a=overwrite_a, clean=True,
  File "/home/ezyang/local/pytorch-tmp-env/lib/python3.9/site-packages/scipy/linalg/_decomp_cholesky.py", line 37, in _cholesky
    raise LinAlgError("%d-th leading minor of the array is not positive "
numpy.linalg.LinAlgError: 3-th leading minor of the array is not positive definite

----------------------------------------------------------------------
```

I have scipy                    1.8.0 installed

### Versions

master

cc @fritzo @neerajprad @alicanb @nikitaved @mruberry @jianyuh @pearu @walterddr @IvanYashchuk @xwang233 @Lezcano
Repository: youtube-dl
Issue: ARTE (France) HTTP Error 500 since 2 days
Labels: broken-IE,pending-fixes

hello :)

 report: multiple links on ARTE.fr show the same error: I report one below
```
# youtube-dl --verbose https://www.arte.tv/fr/videos/107231-000-A/bresil-le-retour-de-la-faim/
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://www.arte.tv/fr/videos/107231-000-A/bresil-le-retour-de-la-faim/']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, pref UTF-8
[debug] youtube-dl version 2021.12.17
[debug] Python version 3.8.2 (CPython) - Linux-5.6.18-x86_64-with-glibc2.2.5
[debug] exe versions: none
[debug] Proxy map: {}
[ArteTV] 107231-000-A: Downloading JSON metadata
ERROR: Unable to download JSON metadata: HTTP Error 500: Internal Server Error (caused by <HTTPError 500: 'Internal Server Error'>); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; see  https://yt-dl.org/update  on how to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
  File "/usr/lib/python3.8/site-packages/youtube_dl/extractor/common.py", line 634, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/usr/lib/python3.8/site-packages/youtube_dl/YoutubeDL.py", line 2288, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/usr/lib/python3.8/urllib/request.py", line 531, in open
    response = meth(req, response)
  File "/usr/lib/python3.8/urllib/request.py", line 640, in http_response
    response = self.parent.error(
  File "/usr/lib/python3.8/urllib/request.py", line 569, in error
    return self._call_chain(*args)
  File "/usr/lib/python3.8/urllib/request.py", line 502, in _call_chain
    result = func(*args)
  File "/usr/lib/python3.8/urllib/request.py", line 649, in http_error_default
    raise HTTPError(req.full_url, code, msg, hdrs, fp)
```
Repository: flutter
Issue: [Image_picker] Add support for picking multiple videos
Labels: c: new feature,customer: mulligan (g3),p: image_picker,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

Please add this feature or give me a quick fix so I can select multi_video like multi_image. Thank you.
Repository: rust
Issue: [NLL] Many errors generated instead of one with many notes
Labels: A-diagnostics,T-compiler,A-NLL,NLL-diagnostics

In tests like:
* [src/test/ui/regions/regions-addr-of-upvar-self.rs](https://github.com/rust-lang/rust/tree/master/src/test/ui/regions/regions-addr-of-upvar-self.rs)
* [src/test/ui/regions/regions-close-object-into-object-4.rs](https://github.com/rust-lang/rust/tree/master/src/test/ui/regions/regions-close-object-into-object-4.rs)

Under NLL we generate many errors for almost the same span instead of one error with many notes under migrate mode, which is more readable and easier to understand.

We should fix this.

@rustbot label +A-NLL +NLL-diagnostics
Repository: godot
Issue: random getornull error spammed in console
Labels: bug,topic:core,needs testing

### Godot version

3.4.4

### System information

windows 10

### Issue description

I've been getting a lot of 'getornull' errors lately.

I'm not sure what's causing them (seems random).
One thing that seems to trigger them sometimes, is adding a breakpoint.
I also got them with a faulty decision tree, and when trying to assign a non-existant animation to an animationplayer. I think these should give me different error messages, no ?

The only thing I can think of that might be causing this, is perhaps a high(er) vertex count ??? But the error doesn't happen all the time, so ... ?

### Steps to reproduce

random error spam

### Minimal reproduction project

_No response_
Repository: vscode
Issue: CompletionList.isIncomplete=true results in showing "stale" results when typing quickly due to cancelled requests
Labels: suggest,under-discussion

I'm trying to move my extension to using `isIncomplete=true` on Completion results to avoid preloading thousands of items in the first request. However, when I do this, the completion feels sluggish/doesn't update and I suspect it's due to how cancellations are handled.

I made a small completion provider that takes 40ms to return, and a test that types one character every 60ms (this means all requests complete without any cancellation). I include the offset of the request in the results to make it clear when updated results are shown. As expected, the completion list updates on every keystroke:

![Apr-21-2022 09-51-20](https://user-images.githubusercontent.com/1078012/164418014-eb2095d5-2f3e-4b23-ac40-f856fb06783a.gif)

However, if I increase the completion provider to take 80ms to return (slightly longer than the delay between keystrokes), the completion list doesn't update at all until the typing stops:

![Apr-21-2022 09-52-14](https://user-images.githubusercontent.com/1078012/164418136-160bdebb-90d3-4562-b316-4d516fd9f4ba.gif)

My understanding is that when you type a new character, VS Code cancels the previous (in-flight) request and sends a new one. This makes sense. However, if the server returns the results anyway (perhaps it had already computed them), I think it would be a much better experience if VS Code still used those results while waiting for the next one. Otherwise, using `isIncomplete=true` results in completion feeling sluggish when typing slightly faster than the server is responding (server response times may increase slightly if lots of requests are being sent/cancelled, as there could be synchronous work that means they don't _immediately_ handle the cancellation).
Repository: pytorch
Issue: at::real and at::imag as methods
Labels: triaged,module: complex

### 🚀 The feature, motivation and pitch

It'd make formulae easier to read, as you could read them left-to-right. E.g.
```c++
t.diagonal(0, -2, -1).real().mul_(0.5);
```
rather than
```c++
at::real(t.diagonal(0, -2, -1)).mul_(0.5);
```

I could submit a PR if people are fine with this.

### Alternatives

_No response_

### Additional context

_No response_

cc @ezyang @anjali411 @dylanbespalko @mruberry @Lezcano @nikitaved
Repository: terminal
Issue: White line at bottom when using "Automatically hide the taskbar"
Labels: Help Wanted,Issue-Bug,Product-Terminal,Area-Windowing

### Windows Terminal version

1.12.10982.0

### Windows build number

10.0.19044.1645

### Other Software

None

### Steps to reproduce

Run Windows Terminal with Focus Mode on

Toggle Fullscreen many tiems



### Expected Behavior

Fullscreen without white line at bottom

### Actual Behavior


https://user-images.githubusercontent.com/83569599/164424073-7f921327-66d4-4741-b8ea-07cf9b45b473.mp4

![1](https://user-images.githubusercontent.com/83569599/164424103-7403575a-72ff-4236-9fe1-2b3ba1d42189.png)

![2](https://user-images.githubusercontent.com/83569599/164424107-f4cebef0-6327-40a5-b0a9-4d6f6e15886b.png)

![3](https://user-images.githubusercontent.com/83569599/164424110-2ded30d3-44ed-4809-b573-4543f100f00f.png)
Repository: material-ui
Issue: [Select] Shows the first item to be selected when initial value is blank or null and the menu popover is not aligned properly with the Select
Labels: bug 🐛,component: select

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

![image](https://user-images.githubusercontent.com/86403873/164447375-2bb6d283-451d-4ade-a9bf-9eb349a8762a.png)

Trying to create a simple basic Select with no customization / or styling. 
Two issues observerd -- 

- As shown in picture, the first item 'Ten' is shown kind of selected gray background. However, I didn't hover or clicked inside the menu.
- The menu popover has incorrectly aligned left positions w.r.t Select.


Please help.
Below is the code snipped used --
```tsx
import * as React from 'react';
import MenuItem from '@mui/material/MenuItem';
import Select, { SelectChangeEvent } from '@mui/material/Select';

export default function SelectLabels() {
  const [age, setAge] = React.useState('');
  const handleChange = (event: SelectChangeEvent) => {
    setAge(event.target.value);
  };
  
  return (
    <div>
      <Select
        labelId="demo-simple-select-helper-label"
        id="demo-simple-select-helper"
        value={age}
        onChange={handleChange}
        sx={{ minWidth: 120 }}
      >
        <MenuItem value={10}>Ten</MenuItem>
        <MenuItem value={20}>Twenty</MenuItem>
        <MenuItem value={30}>Thirty</MenuItem>
      </Select>
    </div>
  );
}
```

### Expected behavior 🤔

_No response_

### Steps to reproduce 🕹

Steps:

1.
2.
3.
4.


### Context 🔦

_No response_

### Your environment 🌎

<details>
  <summary>`npx @mui/envinfo`</summary>

```
  Don't forget to mention which browser you used.
  Output from `npx @mui/envinfo` goes here.
```
</details>
Repository: puppeteer
Issue: Ability to exit a script while keeping browser running
Labels: feature,good first issue,confirmed

My java server need to convert some HTML pages to PDF.
Today I call a script who use process.launch().
All work fine except I take seconds to complete, and it is too slow.
After investigations, 1.5 to 3 seconds are needed just to launch() chromium and open newPage()...


### Bug description

To speed up this, I try to create a new script that use puppeteer to launch a headless chromium instance, save the browserWSEndpoint on the file system and exiting the script leaving the browser opened.

So, other puppeteer scripts can connect to this browserWSEndpoint later to speed up it.

```
const puppeteer = require("puppeteer");

(async () => {
       const browser = await puppeteer.launch({
		handleSIGINT : false, 
		handleSIGTERM : false, 
		handleSIGHUP : false,
	});

	try {
		const browserWSEndpoint = browser.wsEndpoint();
		console.log("Endpoint: " + browserWSEndpoint);
 
               // Save browserWSEndpoint to the file system
         } finally {
		browser.disconnect();
                process.exit(0);
	}
})();
```

My main problem is that the script hang without calling browser.close();

So I try with the 3 parameters: handleSIGINT : false,  handleSIGTERM : false,  handleSIGHUP : false
They seem to have no effect, pressing Ctrl+c kill the script and chromium too.
I try with adding process.kill(0); at the end of the script function to force exit, but the chromium is killed too.

Are-there another way to let the chromium process alive after script execution?

### Puppeteer version

13.4.0

### Node.js version

v16.14.2

### npm version

8.5.0

### What operating system are you seeing the problem on?

Windows

### Relevant log output

_No response_
Repository: angular
Issue: Webcomponents properties are undefined inside connectedCallback
Labels: area: core,cross-cutting: custom elements,P3,bug

### Which @angular/* package(s) are the source of the bug?

core

### Is this a regression?

No

### Description

We are using Webcompoents in our application. Currently inside of our Webcompoent`s connectedCallback we want to make few changes to our component based on some properties. However, when connectedCallback is executed all the properties are set to undefined. 
We further inspected this issue and found that, currently Angular sets properties of a Webcomponent after it is attached to the DOM. 
If you will look at the console in the below share stackblitz, you will observe that the setter of the property inside our webcomponent is called after the connectedCallback.

We even compared this with other framework such as React, where the behaviour seems more standard, as the properties are set before the component is being attached to the DOM. 
React: https://codesandbox.io/s/prod-sky-gw6qcz?file=/src/App.js:259-261

### Please provide a link to a minimal reproduction of the bug

https://stackblitz.com/edit/angular-ivy-rh2gzx?file=src/app/app.component.html

### Please provide the exception or error you saw

_No response_

### Please provide the environment you discovered this bug in (run `ng version`)

```true
Angular : 13.2.0
```
Repository: go
Issue: testing: respect -count when running fuzz corpus tests
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.18 linux/amd64

</pre>

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/e/.cache/go-build"
GOENV="/home/e/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/e/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/e/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/nix/store/h2w6bc9dpcfvr76cfz8ymv7l5llfjjsj-go-1.18/share/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/nix/store/h2w6bc9dpcfvr76cfz8ymv7l5llfjjsj-go-1.18/share/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.18"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/home/e/Downloads/fuzzcount/go.mod"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build1871101059=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

```
$ cat fuzzcount_test.go
package fuzzcount

import "testing"

func TestA(t *testing.T) {
	t.Logf("TestA: ran")
}

func FuzzA(f *testing.F) {
	f.Add([]byte("test"))
	f.Fuzz(func(t *testing.T, _ []byte) {
		t.Logf("FuzzA: ran")
	})
}
$ go mod init fuzzcount
$ go test -count 5 -v .
=== RUN   TestA
    fuzzcount_test.go:6: TestA: ran
--- PASS: TestA (0.00s)
=== RUN   TestA
    fuzzcount_test.go:6: TestA: ran
--- PASS: TestA (0.00s)
=== RUN   TestA
    fuzzcount_test.go:6: TestA: ran
--- PASS: TestA (0.00s)
=== RUN   TestA
    fuzzcount_test.go:6: TestA: ran
--- PASS: TestA (0.00s)
=== RUN   TestA
    fuzzcount_test.go:6: TestA: ran
--- PASS: TestA (0.00s)
=== RUN   FuzzA
=== RUN   FuzzA/seed#0
    fuzzcount_test.go:12: FuzzA: ran
--- PASS: FuzzA (0.00s)
    --- PASS: FuzzA/seed#0 (0.00s)
PASS
ok  	fuzzcount	0.001s
```
### What did you expect to see?

5 instances of `FuzzA: ran`.


### What did you see instead?

Only one instance of `FuzzA: ran`.

Specifying `-count XX` to `go test` is for repeating test runs XX times; I'd expect the same behaviour for tests implied by a fuzz target corpus.
Repository: TypeScript
Issue: Duplicate jsdoc tags from getters and setters
Labels: Bug,Needs Proposal

# Bug Report

### 🔎 Search Terms

getter, setter, jsdocs, duplicated tags

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about duplicate tags
- (Tested v4.0.5 + 4.6.2 + Nightly in https://www.typescriptlang.org/play)

### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=4.0.5&ssl=29&ssc=4&pln=28&pc=10#code/KYDwDg9gTgLgBAYwDYEMDOa4BVhvgbwChC44B6AKgpNIrgBEI40IBbYZmAVwDMe4AFsCgcUAOhpxqpKXAACaYKIB2ATzgQYQqHHZaIAEwkzpteQeBgRCFDGAHsAgJaYXnKCmUBzDnl49jWjJJH3gQAAoASgAudydvOCIZOBFuKGU4AHIQTIBuGgBfYlJKU1lGZjZfbj5BYQ4AI0CpSTo5MBQPVjgQRw5lYAB3OAA3FCQuYGa2xRV1TW1dYH0jVtbzS2tbe0c3NzwPb2r-aeDSRTDwkFiD+K9IxMlECGUWJCmkCC8ryPzSIpodjwUViIwgTgcSRkZDIz1eEHeYk+3y0LjEIF+T1RaHRcAAvFkcn84ACCkA
### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
export class Test {

  /**
   * Do some stuff here a.
   *
   * @see any other method.
   *
   * @deprecated This is strange stuff.
   */
   get x(): string {
    return 'x';
  }

  /**
   * Do some stuff here b.
   *
   * @param x The new value.
   * @see any other method.
   *
   * @deprecated This is strange stuff.
   */
  set x(x: string) {
    console.log(x);
  }

  test(): void {
    // console.log(this.x);
    this.x = 'a'; // Hover `x` to see the JsDocs
  }

}
```

### 🙁 Actual behavior

I see the jsdocs tags for both the getter and setter when hovering the property (usage) for them.

<details>
<summary><strong>VSCode (v1.66.2) (Click to expand)</strong></summary>

![grafik](https://user-images.githubusercontent.com/1579362/164467807-ce841a7a-b162-4398-921c-e19e16db4385.png)

</details>

<details>
<summary><strong>Stackblitz (TS-Sample) (Click to expand)</strong></summary>

![grafik](https://user-images.githubusercontent.com/1579362/164469423-7b571dd9-137f-4541-a378-995b0268923d.png)

</details>

### 🙂 Expected behavior

I expect to see only the jsdocs for either the getter or setter, or at least duplicate tags being filtered.

### See also

https://github.com/faker-js/faker/issues/855#issuecomment-1105218425

> @Shinigami92
> I assume yes, feel free to link:
> - https://github.com/microsoft/TypeScript/issues/37716
> - https://github.com/microsoft/TypeScript/issues/20966
> - https://github.com/microsoft/TypeScript/pull/37451
Repository: terminal
Issue: Opening Windows Terminal in current directory from right-click folder context menu (the `ubuntu.exe` bug)
Labels: Issue-Question,Resolution-External,Resolution-Answered,Area-Settings,Product-Terminal

# Description of the new feature/enhancement

I couldn't find a way to open up `wt.exe` in a linux profile (e.g. `Ubuntu`) via right-click in the context menu that pops up in explorer by setting the current working directory to whatever I was browsing before.

To rephrase: I added some `HKCR\Directory\Background\shell\wt\command` key with `wt.exe -d "%V"` so that I can Shift+RightClick in a folder in explorer.exe and have a `Open in Windows Terminal with Linux` item in the context menu. Windows Terminal opens but the starting directory, no matter what I set the profile `startingDirectory` field in the JSON to, is always set to my home directory. It would be nice if `wt.exe -d "C:\\"` or whatever actually opened, for the linux profile, in `/mnt/c` as starting directory.
Repository: pytorch
Issue: Many dispatch keys do not print to string correctly
Labels: triaged,module: dispatch

### 🐛 Describe the bug

I've been spending a lot of time with the "dispatch key implementation not found" error and I noticed that there are a lot of `UNKNOWN_TENSOR_TYPE_ID` in the output:

```
NotImplementedError: Could not run 'aten::_foreach_minimum.List' with arguments from the 'Meta' backend. This could be because the operator doesn't exist for this backend, or was omitted during the selective/custom build process (if using custom build). If you are a Facebook employee using PyTorch on mobile, please visit https://fburl.com/ptmfixes for possible resolutions. 'aten::_foreach_minimum.List' is only available for these backends: [Dense, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, SparseCPU, SparseCUDA, SparseHIP, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, SparseXPU, UNKNOWN_TENSOR_TYPE_ID, SparseVE, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, NestedTensorCPU, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID, UNKNOWN_TENSOR_TYPE_ID
```

cc @bdhirsh

### Versions

master
Repository: PowerToys
Issue: WindowGrid-like behavior for FancyZones - a few missing details
Labels: Idea-Enhancement,Product-FancyZones,Needs-Triage

### Description of the new feature / enhancement

The idea is completely and entirely _stolen_ from [WindowGrid](http://windowgrid.net/), which a) unfortunately seems to be dormant since at least 5 years and b) according to [recent comments](https://www.facebook.com/windowgrid.net/community/?ref=page_internal) doesn't work on Windows 11.

The idea behind WindowGrid is that you don't have a fixed layout (as in FancyZones) but instead have a grid of `n x m` spanning your monitor to which you can align and resize Windows.

The original page's intro GIF shows this quite well:

![WindowGrid in action GIF](http://windowgrid.net/public/images/WindowGrid.gif)

What's so amazing about this is that you **don't have to setup anything beforehand** and especially don't need to anticipate future zone needs you might have, but instead can just set a reasonable grid size once and whenever you need to arrange your windows snap them to the grid.

As of now, t's _almost_ possible to use FancyZones as a WindowGrid replacement but a few details are missing:

* **Define grid layouts (`rows x columns`) _per monitor_** (see: #12621)
  (WindowGrid allowed you to set an `n x m` grid and would just flip that for displays oriented in portrait)
* **Making dragging across multiple zones easier** - currently you have to press and hold <kbd>Ctrl</kbd> to resize a window to more than 2 zones. Easiest would probably be the following handling (like in WindowGrid):
  * Start dragging a window with left click (no grid displayed for now)
  * Click right once (while holding the drag) to activate grid
  * Drag to desired size and let go
* (Not essential: Provide an option to move a window within the grid without resizing it)

### Scenario when this would be used?

Arranging windows must be one of the core power user tasks 🙈 , but in all seriousness: a WindowGrid-like PowerToy would let you arrange windows very flexibly (and the community has also already provided great extension ideas in all the [BitBucket issues](https://bitbucket.org/joshua_wilding/windowgrid-binaries/issues)).

### Supporting information

See how people [share their love for WindowGrid on Facebook](https://www.facebook.com/windowgrid.net/community/?ref=page_internal) and if in doubt just install it (it runs as a portable app directly after download) and use it a few times - **it's addictive!**