sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Multiple Monitor Setup Tools Request
Labels: Idea-New PowerToy,Product-Display management,Needs-Triage

### Description of the new feature / enhancement

I would love to see multi-monitor tools in PowerToys. Specifically, the ability to lock your mouse to a specific monitor and have a shortcut to unlock it and drag it to another screen. Currently, it's cumbersome when the cursor moves past the indented edge onto another monitor. Love PowerToys! Thank you!

### Scenario when this would be used?

My current display setup is two stacked monitors. The top monitor is used for entertainment (podcasts, YouTube, Tidal, etc), and the bottom main monitor for freelance work. When I drag the mouse cursor too quickly onto the top toolbar in my design software (Photoshop, Premiere, Illustrator, etc) it jumps to the top monitor. I would love to lock the cursor on my main screen and activate the cursor jump with a keyboard shortcut whenever I need to access the second display.

### Supporting information

Sample software:

DisplayFusion
https://www.displayfusion.com

Dual Monitor Tools
https://sourceforge.net/projects/dualmonitortool/
Repository: deno
Issue: Improve command line help docs to have more information about permission flags
Labels: docs

When I run `deno run --help` I get a list of all the flags, but the docs are lack luster. There's an opportunity to provide examples and explanation under each of these. While the docs should be terse, it doesn't need to be limited to 5 words.

```
      --allow-read[=<allow-read>...]
          Allow file system read access

      --allow-write[=<allow-write>...]
          Allow file system write access

      --allow-net[=<allow-net>...]
          Allow network access

      --allow-env[=<allow-env>...]
          Allow environment access

      --allow-sys[=<allow-sys>...]
          Allow access to system info

      --allow-run[=<allow-run>...]
          Allow running subprocesses

      --allow-ffi[=<allow-ffi>...]
          Allow loading dynamic libraries

      --allow-hrtime
          Allow high resolution time measurement
```
Repository: pytorch
Issue: Issue on building from source: Remove -mfpu=neon option on MacOS with Apple silicon
Labels: module: build,triaged

### 🐛 Describe the bug

Get pytorch:
```
git clone -b v2.0.0 --recursive https://github.com/pytorch/pytorch
```

Install dependencies as said in Readme.

I tried compiling with bot gcc(real gcc, not alias for clang) and clang, they all told me about -mfpu=neon option.

GCC: 
```
gcc-12: error: unrecognized command-line option '-mfpu=neon'
```

Clang:
```
clang: warning: argument unused during compilation: '-mfpu=neon' [-Wunused-command-line-argument]
```

This option seems to be useless in this situation.
 

### Versions

pytorch 2.0.0

cc @malfet @seemethere
Repository: vscode
Issue: "Accept all Current/Incoming" does not work when selecting multiple files (in Source Control Tab)
Labels: bug,merge-conflict

Type: <b>Bug</b>

Same as issue #63621: When a merge conflict occurs in git, select multiple changed file in the "Source Control" panel, right-click on any of them and select "Accept all Incoming" or "Accept all Current". I would expect it to accept all changes in all of the selected files, not just the one I right-clicked on, as this is also how staging and reverting files works in VSCode.

The same bug has may have been fixed in the past (see #63621), but is once again active.

VS Code version: Code - Insiders 1.78.0-insider (c9df8ee8e8c316f38dcc75a894ba150024ce3718, 2023-04-13T05:25:44.823Z)
OS version: Windows_NT x64 10.0.19044
Modes:
Sandboxed: Yes

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz (12 x 2208)|
|GPU Status|2d_canvas: enabled<br>canvas_oop_rasterization: disabled_off<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>video_decode: enabled<br>video_encode: enabled<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled<br>webgpu: enabled|
|Load (avg)|undefined|
|Memory (System)|15.90GB (5.17GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|
</details>Extensions: none<details>
<summary>A/B Experiments</summary>

```
vsliv695:30137379
vsins829:30139715
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vswsl492:30256197
vslsvsres303:30308271
pythontb:30258533
pythonptprofiler:30281269
vshan820:30294714
pythondataviewer:30285072
vscod805cf:30301675
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593cf:30376535
pythonvs932:30404738
cppdebug:30492333
vsclangdf:30492506
c4g48928:30535728
dsvsc012:30540252
pynewext54:30618038
pylantcb52:30590116
nodejswelcome1:30587009
pyind779:30611226
pythonsymbol12:30651887
2i9eh265:30646982
showlangstatbar:30659908
pythonb192cf:30661257
functionswalk:30687959
pythonms35:30671666
f08j5886:30680471
24365598:30687740
pythonfmttextcf:30710680
pythonclientmv:30700173

```

</details>

<!-- generated by issue reporter -->
Repository: pytorch
Issue: AttributeError: type object 'torch._C._profiler.ProfilerActivity' has no attribute 'MPS'
Labels: triaged,OSS contribution wanted,oncall: profiler,module: mps

### 🚀 The feature, motivation and pitch

Add support for 'MPS' in Pytorch profiler

```
In [1]: import torch

In [2]: from torch.profiler import profile, record_function, ProfilerActivity
   ...: 

In [9]: with profile(activities=[ProfilerActivity.CPU, ProfilerActivity.MPS], re
   ...: cord_shapes=True) as prof:
   ...:     for epoch in range(num_epochs):
   ...:         i = i + 1

```

### Alternatives

_No response_

### Additional context

_No response_

cc @robieta @chaekit @aaronenyeshi @guotuofeng @guyang3532 @dzhulgakov @davidberard98 @briancoutinho @sraikund16 @sanrise @kulinseth @albanD @malfet @DenisVieriu97 @jhavukainen @ngimel @nbcsm @gaoteng-git @tiffzhaofb @razarmehr @abhudev
Repository: storybook
Issue: [Feature Request] Add option to hide toolbars for doc pages
Labels: feature request,good first issue,addon: toolbars

### Is your feature request related to a problem? Please describe

It's not currently possible to show toolbars for stories, but hide them for doc pages (see [thread](https://discord.com/channels/486522875931656193/1089890776210747522)). I have unattached doc pages with no stories as well as doc pages with stories.

### Describe the solution you'd like

I'd like to be able to hide the toolbar for unattached doc pages with no stories, where the toolbar options don't apply.

### Describe alternatives you've considered

I could look into hiding the individual toolbar options (I believe SB 6.5 did this), but I'd like to just be able to hide the toolbar.

### Are you able to assist to bring the feature to reality?

yes, I can

### Additional context

_No response_
Repository: stable-diffusion-webui
Issue: [Feature Request]: Consistency Models
Labels: enhancement,extension-request

### Is there an existing issue for this?

- [X] I have searched the existing issues and checked the recent builds/commits

### What would your feature do ?

Add Consistency Models support: https://github.com/openai/consistency_models

### Proposed workflow

Add Consistency Models support: https://github.com/openai/consistency_models

### Additional information

Add Consistency Models support: https://github.com/openai/consistency_models
Repository: rust
Issue: long types are written to a file as one looong line
Labels: A-diagnostics,T-compiler,D-diagnostic-infra

### Current output

With a long type in an error the compiler will write the type to a file rather than to the screen, and instead write this:
```Shell
note: the full type name has been written to '/target/wasm32-unknown-unknown/release/deps/x-8006b700d2e73017.long-type-6230284475292204263.txt'
```

### Desired output

It would be awesome if the type could be formatted to be multiple lines as it's a big type and we have a whole file to show the type's name in.

### Rationale and extra context

Could we pipe it through rustfmt or just use a # while printing the type to the file? It would just make life a little easier. (this could also be helpful if people happened to be using diff tools against these types to see what changed)
Repository: go
Issue: net/http: HTTP requests failing with 'Protocol not available' on wasm/js when running in browser
Labels: NeedsInvestigation,arch-wasm,OS-JS

### What version of Go are you using (`go version`)?

<pre>
$ go version
1.20.3
</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
wasm/js

Chrome version: Version 111.0.5563.146 (Official Build) (x86_64)

(also reproducible with various Chromium-based browsers)

</pre></details>

### What did you do?

When doing a simple HTTP GET in a Go library compiled for wasm/js, all versions Go 1.18 and later are failing when running inside Chrome with `dial tcp: lookup <some_domain>: Protocol not available`. 

When running on Go 1.17, this works fine. But Go 1.18 and later give the error above

The issue seems to be introduced by https://github.com/golang/go/commit/266626211e40d1f2c3a34fa4cd2023f5310cbd7d and possibly made worse by https://github.com/golang/go/commit/4c5d97990e4a39bd3e903f8e318b7234db3ba91f. These commits seem to try to "autodetect" a Node environment by checking the presence of certain browser settings. While that may have been valid at time of committing, it seems the assumptions on which they were based no longer hold for more recent browser versions. 

Perhaps a more direct/explicit way of checking whether we're running in a Node or browser environment would be more suitable? The methods above look a bit hacky
Repository: PowerToys
Issue: add more window buttons
Labels: Needs-Triage

### Description of the new feature / enhancement

- Always set the window above all windows
- separate button to mute a single window
- a button to disable Alt-F4 for accidents

### Scenario when this would be used?

Better window management



### Supporting information

_No response_
Repository: rust
Issue: random Empty/Tombstone LLVM assertion error on i686-msvc CI
Labels: A-LLVM,O-windows-msvc,A-spurious,O-x86_32,C-external-bug

There have been a few instances of the following error on i686-msvc on CI:

```
Assertion failed: !KeyInfoT::isEqual(Val, EmptyKey) && !KeyInfoT::isEqual(Val, TombstoneKey) && "Empty/Tombstone value shouldn't be inserted into map!", file C:\a\rust\rust\src\llvm-project\llvm\include\llvm/ADT/DenseMap.h, line 624
```

Examples:
* https://github.com/rust-lang/rust/pull/105575#issuecomment-1355535137
* https://github.com/rust-lang/rust/pull/108283#issuecomment-1506888154
Repository: godot
Issue: Editor ignores Ctrl + Shortcuts after saving with Ctrl + S
Labels: bug,platform:windows,topic:editor,confirmed,topic:input

### Godot version

v4.0.2.stable.official [7a0977ce2]

### System information

Win 64

### Issue description

After saving in the code editor using Ctrl + S, no shortcut keys using the Ctrl key work until the Ctrl key is released.

### Steps to reproduce

1. Open a GDScript file in the GDScript editor -- any file which is large enough to scroll around.
2. Press Ctrl + S, keeping Ctrl held down. The 'Saving Scene' window appears briefly, and disappears before returning focus to the GDScript editor.
3. With Ctrl still held down, press Ctrl + Down. This should scroll the window, but instead it moves the cursor.
4. With Ctrl still held down, press Ctrl + Shift + D. This should duplicate the current line, but instead has no effect.
5. With Ctrl still held down, press Ctrl + Shift + O. This should launch the "Quick Open Script..." window, but instead has no effect.
6. Release Ctrl and try the shortcuts again. All shortcuts work properly.

### Minimal reproduction project

N/A
Repository: next.js
Issue: When getServerSideProps takes longer than 700ms and you go to the site through an anchor tag with target=_blank, Chrome iOS renders the viewport with extra height 
Labels: bug,Pages Router

### Verify canary release

- [X] I verified that the issue exists in the latest Next.js canary release

### Provide environment information

```bash
Operating System:
      Platform: darwin
      Arch: x64
      Version: Darwin Kernel Version 21.6.0: Mon Dec 19 20:44:01 PST 2022; root:xnu-8020.240.18~2/RELEASE_X86_64
    Binaries:
      Node: 16.15.1
      npm: 8.19.2
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 13.3.1-canary.6
      eslint-config-next: 11.0.1
      react: 18.2.0
      react-dom: 18.2.0
```


### Which area(s) of Next.js are affected? (leave empty if unsure)

Data fetching (gS(S)P, getInitialProps)

### Link to the code that reproduces this issue

https://github.com/JiniHendrix/next-chrome-ios-bug

### To Reproduce

Replace the ip address in the href in line 46 of the index page with your own local network ip address

Go to the index page on an ios device on Chrome
Click the link to open the page in a new tab
Notice that the red bar that is fixed to the bottom of the page is not visible

Try switching back from landscape to portrait, or switching back and forth in the tab, or opening the keyboard.

Notice that the red bar is now visible at the bottom of the page.



### Describe the Bug

When getServerSideProps takes longer than 700ms and you open the page in a new tab through an anchor tag with target=_blank, the viewport renders with extra height.

When you change the timeout value to 500ms or less the bug isn't there.

### Expected Behavior

The page shouldn't be rendering with extra height no matter how long getServerSideProps takes.

### Which browser are you using? (if relevant)

112.0.5615.46

### How are you deploying your application? (if relevant)

next run dev, next start
Repository: PowerToys
Issue: Automatically size all columns to fit in Windows Explorer
Labels: Idea-New PowerToy,Product-Tweak UI Design,Product-File Explorer

### Description of the new feature / enhancement

When browsing in Windows Explorer with the Details view option as default, this feature would ensure that all columns (Filename, status, date modified, type, size, etc.,) are automatically resized so that all the information can be viewed.
 
There is currently a context menu option to "Size All Columns to Fit" in Windows Explorer, but this is a manual option. It's usefulness is limited because you need to do it manually for almost every folder when filenames can significantly vary in length.

The PowerToys feature would include some settings to tweak the behaviour, such as maximum/minimum widths, maximum number of columns to resize, columns to ignore, etc.

### Scenario when this would be used?

Whenever Windows Explorer is used with the Details view option as default (possibly other views that use columns).

### Supporting information

_No response_
Repository: flutter
Issue: ☂️ Align 1P plugin error handling with best practices
Labels: team,package,team-ecosystem,P2,triaged-ecosystem

Our wiki documents [our ideal error handling best practices](https://github.com/flutter/flutter/wiki/Contributing-to-Plugins-and-Packages#platform-exception-handling), where we have a structured error system that's clearly defined as part of the API, rather than just having all the errors be `PlatformExceptions` that come directly from the native side and are frequently inconsistent and/or undocumented. However, almost all of our 1P plugins are currently doing the later since the guidance is recent, and we treat significant changes to errors as breaking changes, so can't fix them incrementally.

This is an umbrella for auditing each plugin and determining what changes we should make, then filing sub-issues to track each specific plugin's tasks.

Subtasks that have been filed so far:
- [ ] [in_app_purchase](https://github.com/flutter/flutter/issues/140225)
- [ ] [url_launcher](https://github.com/flutter/flutter/issues/127665)
Repository: flutter
Issue: Hybrid composition wiki does not have a correct example
Labels: d: examples,d: wiki,team-ecosystem,P2,triaged-ecosystem

The [Hybrid composition](https://github.com/flutter/flutter/wiki/Hybrid-Composition) wiki does not provide a correct example (nothing about the controller, or the view type).

It would be better to have a fully-fledged example app for this, which the wiki refers to via code snippets.
Repository: go
Issue: x/pkgsite: kokoro presubmit test is flaky
Labels: NeedsInvestigation,pkgsite

observed during go.dev/cl/483757

https://source.cloud.google.com/results/invocations/c9abece0-cec4-4ca0-b03b-48e55f00b2ab/targets/golang%2Fpkgsite%2Fgcp_ubuntu%2Fpresubmit/log

> 2023/04/12 18:39:56 Critical: fetchFunc(ctx, f, "std", "v1.9.0"): FetchAndUpdateState("std", "v1.9.0", ""): fetchAndInsertModule("std", "v1.9.0"): FetchModule("std", "v1.9.0"): stdlib.ZipInfo("v1.9.0"): semanticVersion("v1.9.0"): stdlib.Versions(): remoteGoRepo.refs: Get "https://go.googlesource.com/go/info/refs?service=git-upload-pack": context deadline exceeded
> exit status 1

https://source.cloud.google.com/results/invocations/1e04a480-457f-4f52-a2cf-1167dd4ba62f/targets/golang%2Fpkgsite%2Fgcp_ubuntu%2Fpresubmit/log
Similar timeout issue during screentest.

https://source.cloud.google.com/results/invocations/766b4c7f-c19c-4ed2-8726-d37da0c27b61/targets/golang%2Fpkgsite%2Fgcp_ubuntu%2Fpresubmit/log

> 2023/04/12 19:22:10 Debug: test-1549 DROP TABLE IF EXISTS ser args=
> 2023/04/12 19:22:10 Error: {ID:test-1549 Query:DROP TABLE IF EXISTS ser Args:  DurationSeconds:9.443e-06 Error:DB running query test-1549: context deadline exceeded}
> --- FAIL: TestTransactSerializable (10.01s)
>    database_test.go:433: max retries: 0
Repository: flutter
Issue: Remove unconditional goma context entry in engine_v2 gn step
Labels: team-infra,P2,triaged-infra

Added in https://flutter-review.googlesource.com/c/recipes/+/41740.

Ideally, whether to enable goma for the gn step would be indicated by a flag in the `gn` section of the build config, e.g. here: https://github.com/flutter/engine/blob/main/ci/builders/mac_unopt.json#L21.

cc @godofredoc
Repository: go
Issue: all: failures on aix with `ld returned 12 exit status`
Labels: NeedsInvestigation,OS-AIX,compiler/runtime

```
#!watchflakes
post <- goos == "aix" && log ~ `ld returned 12 exit status`
```

Issue created automatically to collect these failures.

Example ([log](https://build.golang.org/log/f98f381f8a5b91ef47a8408d51531f049f7e317c)):

    --- FAIL: TestDisasmExtld (0.87s)
        objdump_test.go:159: Running [/ramdisk8GB/workdir-host-aix-ppc64-osuosl/go/bin/go build -o /ramdisk8GB/workdir-host-aix-ppc64-osuosl/tmp/TestDisasmExtld1998086750/001/hello-3da08facc82f2a8311a3360fd6024b47779b9e94b1e5cec8cd839c0e71b5402a.exe -ldflags=-linkmode=external fmthello.go]
        objdump_test.go:162: go build fmthello.go: exit status 1
            # command-line-arguments
            /ramdisk8GB/workdir-host-aix-ppc64-osuosl/go/pkg/tool/aix_ppc64/link: [gcc] -Wl,-V failed: exit status 1
            /usr/bin/ld: LD 7.2.2(5/18/17)
            ld: 0711-999 SEVERE ERROR: Unexpected system call error.
            	ld:open() No such file or directory
            ld: 0711-996 Error occurred while processing file: a.out
            collect2: error: ld returned 12 exit status


— [watchflakes](https://go.dev/wiki/Watchflakes)
Repository: flutter
Issue: ColorScheme.fromImageProvider violate framework style guide on avoiding timeouts
Labels: framework,P2,has partial patch,team-framework,triaged-framework

See: https://github.com/flutter/flutter/blob/62cb61d3f36674952a8345a54e723eb663d3cfdb/packages/flutter/lib/src/material/color_scheme.dart#L1163

We should not have this in here at all. Some other notes: this code should be using the built in image resizing functionality and not emulating it via canvas resizing.


cc @esouthren
Repository: rust
Issue: Unexpected Interpretation of Binary Operation starting with Unsafe
Labels: A-diagnostics,A-parser,D-newcomer-roadblock,D-terse

I just stumbled across a compiler error that does not really make sense to me. For some reason, the compiler does not accept an unsafe block expression followed by a binary operator under certain circumstances.

For some unsafe function `unsafe fn test() -> i32`, the following does not compile:
```rust
unsafe { test() } != 0;
```
<details>
<summary>Error message</summary>

```
error: expected expression, found `!=`
  --> src/main.rs:14:23
   |
14 |     unsafe { test() } != 0;
   |                       ^^ expected expression

error[[E0308]](https://doc.rust-lang.org/stable/error_codes/E0308.html): mismatched types
  --> src/main.rs:14:14
   |
14 |     unsafe { test() } != 0;
   |              ^^^^^^- help: consider using a semicolon here: `;`
   |              |
   |              expected `()`, found `i32`

For more information about this error, try `rustc --explain E0308`.
```
</details>


```rust
let _ = if true {
    unsafe { test() } != 0
} else {
    false
};
```
<details>
<summary>Error message</summary>

```
error: expected expression, found `!=`
  --> src/main.rs:18:27
   |
18 |         unsafe { test() } != 0
   |                           ^^ expected expression

error[[E0308]](https://doc.rust-lang.org/stable/error_codes/E0308.html): mismatched types
  --> src/main.rs:18:18
   |
17 |       let _ = if true {
   |  _____________-
18 | |         unsafe { test() } != 0
   | |                  ^^^^^^ expected `()`, found `i32`
19 | |     } else {
20 | |         false
21 | |     };
   | |_____- expected this to be `()`
   |
help: consider using a semicolon here
   |
18 |         unsafe { test(); } != 0
   |                        +
help: consider using a semicolon here
   |
21 |     };;
   |      +

For more information about this error, try `rustc --explain E0308`.
error: could not compile `playground` due to 2 previous errors
```
</details>

However, the following _does_ compile:
```rust
let _ = unsafe { test() } != 0;
```

```rust
0 != unsafe { test() };
```

```rust
if unsafe { test() } != 0 {
    unreachable!();
}
```

The playground example can be found [here](https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=ced8273db03cbb25d4bbd10a52908ffa).

I would have these examples expected to just work, since the unsafe block is just an expression.

### Meta

This behaviour seems to be the same on stable `1.68.2`, beta `1.69.0-beta.7`, and nightly `1.70.0-nightly`.
Repository: flutter
Issue: DlImageSkia does not use a Skia unref queue wrapper
Labels: engine,P2,team-engine,triaged-engine

DlImageSkia is one of the few objects left that holds an object that might need to be unref'd on a GPU thread, but it does not protect its GPU resource from those unrefs by using something like a SkiaGPUObject wrapper.

As a result, its queueing issues are promoted to affect any object that holds a DlImageSkia object and thus to any object that holds a DlImage object and thus ... to dozens of other objects that themselves don't hold any actual resources.

See https://github.com/flutter/flutter/issues/122634
See https://github.com/flutter/flutter/issues/33086