sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Add "send backwards" and / or "send to back" in the windows context menus that have 'minimize' and 'maximise'
Labels: Idea-Enhancement,Product-Window Manager,Needs-Triage

### Description of the new feature / enhancement

Like moving objects on a Powerpoint slide.  You have many windows open on a screen, possibly many e.g. web browsers from the same app and there isn't a great way to restore to view the one you were just looking it.

The one you were just looking at might not have had focus, so would not necessarily be the first in alt-tab, might be hard to distinguish by app in win-tab, and isn't clear by location with hover over the app-icon in the taskbar.  After clicking on another window that covers the one you want, there is not a great way to restore to foreground the newly-hidden window.

Being able to send the foreground window 'back' in the stack of windows on that screen (and desktop) - but without minimising it - allows you to see both windows.

**Alternatives**:
- current built-in: minimise the foreground window; find the revealed window on the taskbar; find the minimised window on the taskbar and restore it; then bring the hidden window to the foreground from the taskbar.
- current with PowerToys: minimise the foreground window; make the newly-revealed window 'always on top'; find the minimised window on the taskbar; restore that window; un'always-on-top' the foreground window
- possible: allow window selection with a mouse-box on screen
- possible: show window-thumbnails relative to their on-screen position during win-tab | during hover on taskbar app icon.

I expect that send-to-back is easier to implement otherwise you have to filter for windows on the right screen on the right desktop, possibly filtering for 'covered-by-the-selected-window'.

Happy to assist.

### Scenario when this would be used?

Many windows from many apps [on many screens with many desktops].

### Supporting information

_No response_
Repository: deno
Issue: Not possible to debug worker
Labels: feat,debugger

It seems the debugger in VSCode and Chrome never stops at breakpoints in worker code.

Are there any variables, specific Deno command line flags or worker options I have to use to be able to debug worker code?
Repository: godot
Issue: CollisionShape2D shape property is not being updated, visually and functionally
Labels: bug,topic:physics,topic:2d

### Godot version

3.4 stable

### System information

Windows 11

### Issue description

Hi all, 

I have an Area2D node, that contains a CollisionShape2D node. Within the latter, I am trying to swap out the shapes with saved resources, in order to test specific collisions. For some reason, the shapes are not getting updated when I cycle through them. 

If I try to do this via an AnimationPlayer, the shape property gets updated. 

I'm changing them fairly quickly, multiple times in each physics_update. Could this be the issue? How can I circumvent this?

### Steps to reproduce

In a node 2D, add an Area2D, along with a CollisionShape2D. 

Attach a script to the node2D, add in the physics_process function for the node2D, loop through some predefined shape2Ds, and insert them into the shape property of the CollisionShape2D node. 

You will notice that the area2D does not reflect the different shapes as you loop through. 

### Minimal reproduction project

_No response_
Repository: rust
Issue: Automatic type coercion fails when implementing a trait for multiple types.
Labels: A-trait-system,T-compiler,C-bug,T-types

If I define the following trait, with a single implementation for `&str`, then this code compiles just fine.
```rust
trait Trait<T> {
    fn function(self, t: T);
}

impl Trait<&str> for () {
    fn function(self, t: &str) {}
}

fn main() {
    // this is what gives the error
    ().function(&"test".to_string());

    // also an error
    <() as Trait<_>>::function((), &"test".to_string());
     
    // this is fine
    <() as Trait<&str>>::function((), &"test".to_string());

    // also fine
    ().function(&"test".to_string() as &str);
}

// uncommenting this gives an error
// impl Trait<()> for () {
//    fn function(self, t: ()) {}
// }
```

However when uncommenting the last block, the following error is returned:
```
the trait bound `(): Trait<&String>` is not satisfied
the following implementations were found:
  <() as Trait<&str>>
  <() as Trait<()>>
```

My interpretation is that the &String gets coerced automatically to &str if there is a single Trait implementation to choose from. However once more than on Trait implementation is available, automatic coercion stops working, and manual coercion is necessary. This is even the case if there is only one valid type to coerce to as can be seen in this example (`&String` can never be coerced to `()`).


This issue is similar to the [following](https://github.com/rust-lang/rust/issues/92178) issue created by @compiler-errors. I have also talked with him on Zulip before posting it here.
Repository: next.js
Issue: `next build` failed to import web workers from pure esm packages
Labels: bug,Webpack

### Run `next info` (available from version 12.0.8 and up)

```
'yarn' is not recognized as an internal or external command,
operable program or batch file.
'pnpm' is not recognized as an internal or external command,
operable program or batch file.

    Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 16.13.1
      npm: 8.1.2
      Yarn: N/A
      pnpm: N/A
    Relevant packages:
      next: 12.0.11-canary.1
      react: 17.0.2
      react-dom: 17.0.2
```

### What version of Next.js are you using?

12.0.11-canary.1

### What version of Node.js are you using?

v16.13.1

### What browser are you using?

Unrelated

### What operating system are you using?

Windows 11

### How are you deploying your application?

Unrelated

### Describe the Bug

When a dependency package has `"type": "module"` in package.json, and uses `new Worker(new URL("./worker.js", import.meta.url))` to create a web worker, `next build` failed with

```
Module not found: ESM packages (./worker.js) need to be imported. Use 'import' to reference the package instead. https://nextjs.org/docs/messages/import-esm-externals
```

While `next dev` and a barebone webpack configuration all works.

---

This issue originated near here:

https://github.com/vercel/next.js/blob/5365f417853e11fb000ad95729d9f9b68d2a3e42/packages/next/build/webpack-config.ts#L849-L851

`dependencyType` is `"worker"` in this case.

### Expected Behavior

`next build` successfully create a build.

### To Reproduce

```
git clone https://github.com/yume-chan/next-repro-33914
cd next-import-worker
npm i
cd packages/next-app
next build
```

The `webpack-app` folder is a barebone webpack configuration, which can correctly import and bundle the worker.
Repository: react
Issue: [DevTools Bug] Cannot add node "1" because a node with that id is already in the Store.
Labels: Type: Bug,Resolution: Needs More Information,Component: Developer Tools

### Repro steps

  
  "react": "17.0.2",
  "react-native": "0.66.3",
  "react-devtools": "^4.22.0",
  "@react-navigation/devtools": "^6.0.5",
  "@react-navigation/bottom-tabs": "^6.1.0",
  "@react-navigation/core": "^6.1.1",
  "@react-navigation/elements": "^1.3.0",
  "@react-navigation/native": "^6.0.7",
  "@react-navigation/native-stack": "^6.3.0",
  "@react-navigation/routers": "^6.1.0",
  "@react-navigation/stack": "^6.1.0",

### How often does this bug happen?

Every time

### DevTools package (automated)

react-devtools-core

### DevTools version (automated)

4.14.0-d0ec283819

### Error message (automated)

Cannot add node "1" because a node with that id is already in the Store.

### Error call stack (automated)

```text
at /Applications/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:48:140545
    at c.emit (/Applications/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:48:89515)
    at /Applications/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:48:90986
    at /Applications/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:48:347787
    at Array.forEach (<anonymous>)
    at S.Gc.e.onmessage (/Applications/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:48:347771)
    at S.n (/Applications/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:40:3009)
    at S.emit (events.js:315:20)
    at e.exports.P (/Applications/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:8:9318)
    at e.exports.emit (events.js:315:20)
    at e.exports.dataMessage (/Applications/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:8:15409)
    at e.exports.getData (/Applications/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:8:14651)
    at e.exports.startLoop (/Applications/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:8:12066)
    at e.exports._write (/Applications/React Native Debugger.app/Contents/Resources/app.asar/node_modules/react-devtools-core/dist/standalone.js:8:11421)
    at doWrite (_stream_writable.js:403:12)
    at writeOrBuffer (_stream_writable.js:387:5)
```


### Error component stack (automated)

_No response_

### GitHub query string (automated)

```text
https://api.github.com/search/issues?q=Cannot add node  because a node with that id is already in the Store. in:title is:issue is:open is:public label:"Component: Developer Tools" repo:facebook/react
```
Repository: pytorch
Issue: test_sampled_addmm_zero_sized causes CUDA memory exception
Labels: module: sparse,module: crash,module: cuda,triaged

### 🐛 Describe the bug

Discovered while running https://github.com/pytorch/pytorch/pull/72016 that adds explicit error even if CUDA memory exception caused early termination

See this runlog for example: https://github.com/pytorch/pytorch/runs/5029465594?check_suite_focus=true

### Versions

N/A

cc @nikitaved @pearu @cpuhrsch @ngimel
Repository: excalidraw
Issue: Drawing issue with pen mode.
Labels: mobile

Drawing with spen or pen doesn't work as expected.
Please see video for reference.

Device: Samsung S7 Plus
Android 
Tested on excalidraw.com 

https://user-images.githubusercontent.com/4208015/152185790-a8726182-0213-4e50-a8b9-b05768473f7a.mp4
Repository: TypeScript
Issue: `tsc` should halt on a wrong config file instead of start checking
Labels: Suggestion,Awaiting More Feedback

# Bug Report

I have a simple test case. I make an intentional error in `tsconfig.json` by providing 
- a fake path to the `extends` 
- or passing a wrong `compilerOptions` option. 

But instead of expected halt with an appropriate error message, `tsc` is simply continuing to work! Rendering its output useless and confusing. 

Without being properly configured, lots of includes obviously just stop working and produce dozens of errors which TSC displays BEFORE it alerts about your incorrect `tsconfig.json` — its primary source of instructions on how to operate.

I can't think about a single scenario when one would agree to get informed about some **root** problem on an N-th page among other (usually derived) errors. This must not work this way.

### 🔎 Search Terms

`halt tsconfig error`

### 🕗 Version & Regression Information

4.5.5

### 🙁 Actual behavior

`tsc` neither clearly complains nor halts on errors in `tsconfig.json` 

### 🙂 Expected behavior

`tsc` must not proceed at all if `tsconfig.json` is wrong.
Repository: PowerToys
Issue: Extend Zone Sticker Beyond Monitor While in Monitor-Mode (No Span Mode)
Labels: Idea-Enhancement,Help Wanted,Product-FancyZones

### Description of the new feature / enhancement

- Zone stickers should be allowed to extend beyond the monitor while in Monitor-Mode (no Span Mode). There will be some overlap between zones on different monitors but this will be great for screen real estate. The "when multiple zones overlap" will be useful for this.

### Scenario when this would be used?

- When wanting to fit a window to a zone so that certain useless parts of the window remain hidden (like the menu bar, window outline, etc.). **This will maximize screen real estate and help focus on the important parts of a window.**

### Supporting information

_No response_
Repository: create-react-app
Issue: Error while running create-react-app command on windows 11 using WSL
Labels: needs triage,issue: bug report

### Describe the bug

I have setup Ubuntu 20.04 LTS version on Windows 11 system using WSL2 feature. 
Every time I am trying to run the command `npx create-react-app`, it is throwing error as shown in the screenshot.
I also tried installing the package globally using this command `npm install -g create-react-app` which works fine but after that running `npx create-react-app` still throws error.

![WindowsTerminal_WNABFhdERY](https://user-images.githubusercontent.com/171670/152189658-e38c6da9-0978-472c-8250-39086286fd86.png)
Repository: pytorch
Issue: Mechanism for Tensor subclasses to "disable autograd"
Labels: feature,module: autograd,triaged,actionable,module: __torch_dispatch__

### 🚀 The feature, motivation and pitch

## Motivation
Some Tensor Subclasses (I'm looking at functorch) want to selectively disable calling certain autograd APIs on them. For example, calling requires_grad_() or retain_grad() on functorch's GradTrackingTensor will produce silently incorrect results most of the time, but they are indeed necessary at other times.

## Feature
We should design some sort of API to selectively disable autograd APIs that Tensor Subclasses can opt-into.

## Pitch

There's a lot to consider here:
- how do we report a nice error message?
- do we disable all autograd APIs at a thread-local level or at a global level?
- do we only want this to disable these APIs for a Tensor subclass?
- what are the autograd APIs to disable? Do people ever want to use some autograd APIs but not others?
- How to get the API to report a nice error message other than "Autograd is disabled"?


### Alternatives

Have the Autograd API go through the PyTorch dispatcher. This gives Tensor Subclasses free reign over everything.

### Additional context

_No response_

cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: rust
Issue: Unstable fingerprint after incremental recompilation
Labels: I-ICE,T-compiler,A-incr-comp,C-bug

Recompiling (incrementally) openethereum after some modifications results in the error below:

```
thread 'rustc' panicked at 'Found unstable fingerprints for hir_module_items(ethcore[cfff]::tx_filter::transact_acl::functions): ModuleItems { submodules: [DefId(0:18987 ~ ethcore[cfff]::tx_filter::transact_acl::functions::contract_version), DefId(0:19004 ~ethcore[cfff]::tx_filter::transact_acl::functions::contract_name_hash), DefId(0:19022 ~ ethcore[cfff]::tx_filter::transact_acl::functions::contract_name), DefId(0:19039 ~ ethcore[cfff]::tx_filter::transact_acl::functions::allowed_tx_types)], items: [ItemId { def_id: DefId(0:18984 ~ ethcore[cfff]::tx_filter::transact_acl::functions::{misc#0}) }, ItemId { def_id: DefId(0:18987 ~ ethcore[cfff]::tx_filter::transact_acl::functions::contract_version) }, ItemId { def_id: DefId(0:19004 ~ ethcore[cfff]::tx_filter::transact_acl::functions::contract_name_hash) }, ItemId { def_id: DefId(0:19022 ~ ethcore[cfff]::tx_filter::transact_acl::functions::contract_name) }, ItemId { def_id: DefId(0:19039 ~ ethcore[cfff]::tx_filter::transact_acl::functions::allowed_tx_types) }], trait_items: [], impl_items: [], foreign_items: [] }', compiler/rustc_query_system/src/query/plumbing.rs:675:9
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

error: internal compiler error: unexpected panic

note: the compiler unexpectedly panicked. this is a bug.
```

rustc 1.58.1 (db9d1b20b 2022-01-20) running on x86_64-unknown-linux-gnu

compiler flags: -C opt-level=3 -C embed-bitcode=no -C debuginfo=2 -C debug-assertions=on -C incremental

query stack during panic:
```
#0 [hir_module_items] HIR module items in `tx_filter::transact_acl::functions`
#1 [analysis] running analysis passes on this crate
end of query stack
```

## Steps to reproduce
```bash
git clone https://github.com/openethereum/openethereum.git
cd openethereum/crates/ethcore
cargo build
# edit some files
cargo build # fails
```
Repository: go
Issue: test: issue46234.go failures with "command exceeded time limit"
Labels: NeedsInvestigation

`greplogs --dashboard -md -l -e 'command exceeded time limit' --since=2021-01-01`

[2022-02-01T18:15:07-125c5a3/solaris-amd64-oraclerel](https://build.golang.org/log/4fb8380e5b03c29bd64e74c65580a6ce91638e6c)
[2021-07-01T17:07:36-eb437ba/linux-riscv64-jsing](https://build.golang.org/log/e76fb9b20bb1a187543688b8565a0af73230226c)

This test was added in [CL 320913](https://go.dev/cl/320913) for #46234 (CC @thanm @cherrymui @mdempsky). The test runs with an apparently-arbitrary timeout to “[e]nsure that runtime traceback does not infinite loop”, but a 30-second timeout is decidedly shorter than infinity, especially when an entire program must be compiled and linked. 😅

As far as I can tell, there are [only two tests](https://cs.opensource.google/search?q=%22buildrun%20-t%22&ss=go%2Fgo) that use `buildrun -t` today: `issue46234.go` and `issue10958.go`. And of those, the latter is [disabled by default](https://cs.opensource.google/go/go/+/master:test/fixedbugs/issue10958.go;l=8-13;drc=e3c684777a05ca5a4f9bb59983e07c4e6a7a5e15).

A good first step might be to separate the “build” and “run” steps in `buildrun -t`, so that the timeout only applies to the "run" portion rather than also the “build”. Or, perhaps we should increase the timeout, and probably also apply `GO_TEST_TIMEOUT_SCALE` from the builder environment.

If the timeouts persist, we should probably consider terminating the program with a more appropriate signal (#50436) to obtain a core dump for investigation.
Repository: flutter
Issue: [A11y] Add support to currency string attribute
Labels: c: new feature,framework,a: accessibility,customer: money (g3),P3,team-framework,triaged-framework

b/216712711
```dart
import 'package:flutter/material.dart';

void main() => runApp(const MyApp());

class MyApp extends StatelessWidget {
  const MyApp({Key? key}) : super(key: key);

  static const String _title = 'Flutter Code Sample';

  @override
  Widget build(BuildContext context) {
    return MaterialApp(
        title: _title,
        home: Scaffold(
         appBar: AppBar(title: Text(_title)),
         body: Text('₹8,56,000'),
       ),
    );
  }
}
```
focus the text using talkback

expect:
pronounce 856000 ruby

actual

8 ruby 56000



For android we can use https://developer.android.com/reference/android/text/style/TtsSpan#TYPE_MONEY
For iOS we can use https://developer.apple.com/documentation/foundation/nsnumberformatter?language=objc
Repository: pytorch
Issue:  test_fn_fwgrad_bwgrad_special_ndtr_cuda_float64 fails
Labels: module: crash,module: cuda,triaged,ZeroTensor

### 🐛 Describe the bug

Discovered while running #72016 that adds explicit error even if CUDA memory exception caused early termination
See this runlog for example: https://github.com/pytorch/pytorch/runs/5039413269?check_suite_focus=true

### Versions

N/A

cc @ngimel
Repository: godot
Issue: Resource leak in GDNative
Labels: bug,topic:gdextension

### Godot version

3.4.2 stable

### System information

OS: Arch Linux, CPU: Ryzen 5, GUP: RX 480

### Issue description

Calling `get_script()` on an instance with a GDScript in GDNative causes the script to leak at the end of the program.

### Steps to reproduce

Create a node with a native script as the scene's root and add a child with a script.
In _ready() method of the root (nativescript) call get_child(0).get_script() (don't store the reference).
The script leaks at the end.

### Minimal reproduction project

_No response_
Repository: three.js
Issue: USDZExporter animations
Labels: Enhancement

**Is your feature request related to a problem? Please describe.**

I'm building a dynamic scene in ThreeJS, and I need a fallback for webXR (AR, specifically), for devices that don't support it. One solution is to use Apple's [Quick Look](https://developer.apple.com/documentation/quicklook) app, but it requires USDZ format. I'm using the [USDZExporter](https://github.com/mrdoob/three.js/blob/b47c97dde78da84975b910c37fff5231154197d5/examples/jsm/exporters/USDZExporter.js) to export the file, but it loses the keyframe animations. 

**Describe the solution you'd like**
I'd like the USDZExporter to pull the animation clip from my loaded model.

Here are some useful links for the USD animation schema:
https://graphics.pixar.com/usd/release/tut_xforms.html
https://developer.apple.com/documentation/arkit/usdz_schemas_for_ar/autoplay


**Describe alternatives you've considered**

I could build some kind of cloud function docker thing that [converts from GLTF to USD](https://github.com/google/usd_from_gltf) since the [GLTFExporter](https://github.com/mrdoob/three.js/blob/master/examples/jsm/exporters/GLTFExporter.js) supports animations. It's not an ideal solution.


**Additional context**

https://github.com/mrdoob/three.js/issues/14219
Repository: pytorch
Issue: test_fn_fwgrad_bwgrad_[trapezoid|trapz]_cuda_complex128 causes CUDA memory exception
Labels: module: crash,module: cuda,module: ci,triaged,ZeroTensor

### 🐛 Describe the bug

Discovered while running #72016 that adds explicit error even if CUDA memory exception caused early termination
See this runlog for trapezoid failure: https://github.com/pytorch/pytorch/runs/5040778523?check_suite_focus=true
And this one for trapz: https://github.com/pytorch/pytorch/runs/5041795069?check_suite_focus=true

### Versions

N/A

cc @ngimel @seemethere @malfet @pytorch/pytorch-dev-infra
Repository: PowerToys
Issue: [Power Toys Run] Option to bring front already open window when app selected on PT Run
Labels: Idea-Enhancement,Product-PowerToys Run,Run-Plugin

### Description of the new feature / enhancement

Let's say that Visual Studio is open but there are an other app in front of it, like a browser.
When i find and open Visual Studio on PT Run,
Then the already open window of Visual Studio, is bringed to front.

### Scenario when this would be used?

- For hard users that are avoiding to use the mouse
- For laptop users
- For users that are moving to windows from other platforms that have this default behaviour
- For times that you have too much windows and just want to bring the already open instance

### Supporting information

_No response_