sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Option for 'Alt + Tab' cycling only through applications in the focused display
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

Basically, while using multiple monitors, would be nice to have an option limiting the Alt + Tab cycle to applications present in the currently active/in focus monitor . The pop up would be shown in the designated display with only the available windows in it.

### Scenario when this would be used?

Having multiple applications distributed in different monitors can make cycling through Alt + Tab overwhelming, especially in case the circumstance calls for switching between only windows in the same display. 
Since, a lot of the time, secondary displays during certain workflows hold just the apps that will have little to none interaction and are simply acting as visual aid for something else; grouping them in this manner would (probably) reduce time and amount of required interaction spent in the task.
Multiple windows of the same program (a browser, for example) can create a lot of visual noise, music players and docs/pdfs can just, lay there, static. 
So, by having this separation of concerns, things can be a lot easier while hopping between anything in the focused display.

### Supporting information

- This exact behavior is currently possible through the 'Win + Tab' shortcut, although, due to how it works (having focus in virtual desktops and history activity), its much slower (both in performance and user experience) and more dependent of mouse input.  
**'Alt + Tab'** holds up much better even to this day, snappier and objective, with no screen overlay and unnecessary functions.

- Windows 10 multitasking settings covers only options for including/excluding Edge tabs from results and how it should behave between different virtual desktops.

Maybe, the issue could be solved by having this other suggestion implemented: ( #58  ), but it does look much more complex and doesn't seem to have gained increased interest this days.

In the end, it may be a very welcome addition even without certainty of how many people are interested by the idea. It's one of those things people don't realize they've been missing, until running into it by chance.

Or it's niche, I guess.  .-.

-----

**Relevant Link:**

[Alt + Tab Handler](https://www.displayfusion.com/Features/AltTab/) is a paid tool (not tested), that seems to offer what is being asked/suggested here and plus some other options.
Repository: godot
Issue: RigidBody with CylinderShape jiggles by itself on Plane
Labels: bug,topic:physics,topic:3d

### Godot version

v4.0.dev.calinou [729461b2a]

### System information

Mx Linux (Debian Based)

### Issue description

When having a RigidBody with CylinderShape over a plane, it jiggles and never goes to sleep. It also happen if I stack the Cylinder on top on another.

### Steps to reproduce

Use the Main.tscn of the Minimal reproduction project.

Material is assign to the cylinder on process. Red means awake, blue sleep.

### Minimal reproduction project

[CylinderPhysics.zip](https://github.com/godotengine/godot/files/7145442/CylinderPhysics.zip)
Repository: go
Issue: x/text/language: Wrong language is selected
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.17 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes (via play.golang.org)

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
</pre></details>

### What did you do?

I have a set of strings in Norwegian and Danish. The user requests content via Accept-Language header of `nb-no` (Norwegian). Example:

https://play.golang.org/p/rfr4sjGVHkk

### What did you expect to see?

I expected to get an exact match to the Norwegian language tag.

### What did you see instead?

`Match()` picks Danish instead.
Repository: next.js
Issue: Unable to disable locale routing
Labels: bug,Internationalization (i18n)

### What version of Next.js are you using?

11.1.2

### What version of Node.js are you using?

15.14.0

### What browser are you using?

Chrome

### What operating system are you using?

Ubuntu

### How are you deploying your application?

local using next dev

### Describe the Bug

I do not want to use locale based routing in my next app. Here's my next.config.js

```
/** @type {import('next').NextConfig} */
module.exports = {
  reactStrictMode: true,
  i18n: {
    locales: ["en"],
    defaultLocale: "en",
    localeDetection: false,
  },
  async redirects() {
    return [
      {
        source: "/",
        destination: "/test",
        permanent: false,
        locale: false,
      },
    ];
  },
};
```

Although `localeDetection` has been set to `false` the page is getting redirected from `/` to `/en/test`. Moreover, after adding `locale: false` to my redirect, the redirection is no longer happening.

### Expected Behavior

Expecting redirects to work fine without sub path routing.

### To Reproduce

Can visit this repo - https://github.com/lalitindoria/next-router-locale-bug
Repository: flutter
Issue: Catch and log exceptions in ObjC (and Swift) plugin registrants
Labels: platform-ios,tool,platform-mac,P2,a: plugins,team-ios,triaged-ios

The Java registrant was recently updated to catch and log exceptions during plugin registration, to address the fact that the behavior for an Android plugin throwing was extremely confusing (it and all plugins after it alphabetically just didn't work).

We just had a spate of bugs where a popular plugin shipped a completely-broken-on-iOS version that threw an exception during registration, and the effect was that the app crashed (see https://github.com/flutter/flutter/issues/89859 for an example). If you don't know what to look for, it's not super obvious that the culprit is the plugin, not Flutter. If we catch it we can:
- clearly log the problem, including the plugin's name (in this particular case the exception message has the name of the plugin in the class name, but there's no reason for that to always be true)
- not crash, so that the behavior is "the broken plugin doesn't work" not "the whole app crashes"

/cc @jmagman
Repository: rust
Issue: Suggest a deref when calling `<T as From<&X>::from` when `impl From<X> for T` exists
Labels: A-diagnostics,T-compiler

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

Given the following code: <!-- Please provide a link to play.rust-lang.org -->

```rust
struct T(bool);
impl From<bool> for T {
    fn from(val: bool) -> Self {
        Self(val)
    }
}

fn main() {
    let x = true;
    let y = &x;
    let x = T::from(y);
}
```

The current output is:

```
error[E0277]: the trait bound `T: From<&bool>` is not satisfied
   --> src/main.rs:11:13
    |
11  |     let x = T::from(y);
    |             ^^^^^^^ the trait `From<&bool>` is not implemented for `T`
    |
    = help: the following implementations were found:
              <T as From<bool>>
note: required by `from`
```

<!-- The following is not always necessary. -->
I was thinking we could do the thing we do for [function calls](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=8318d2dfe1ca544341645181baeb3364) and suggest a deref:

```
error[E0277]: the trait bound `T: From<&bool>` is not satisfied
   --> src/main.rs:11:13
    |
11  |     let x = T::from(y);
    |             ^^^^^^^ the trait `From<&bool>` is not implemented for `T`
    |
    = help: there is an implementation of `From<bool>` for `T`
    = help: consider dereferencing the borrow: `*y`

```

or, in the case of a direct call (`T::from(&true)`) suggest removing the borrow:

```
error[E0277]: the trait bound `T: From<&bool>` is not satisfied
   --> src/main.rs:11:13
    |
11  |     let x = T::from(&true);
    |             ^^^^^^^ the trait `From<&bool>` is not implemented for `T`
    |
    = help: there is an implementation of `From<bool>` for `T`
    = help: consider removing the borrow: `true`
```


This is especially helpful when, like in the real-world case where I ran into this, `T` has a *lot* of `From` impls - enough that it'd turn into the "and <x> others" and not necessarily even show the relevant impl for the deref'ed version of the argument.
Repository: create-react-app
Issue: I keep having to rm node_modules/.cache/.eslintcache
Labels: needs triage,issue: bug report

Somewhat frequently, I save and have some eslint errors, I fix them, save again, but it's still showing the eslint errors in browser and in console

restarting the dev server (`react-scripts start`) won't help

I have to delete eslint cache running `rm node_modules/.cache/.eslintcache` and restart the server to get it working again

config:
```
$ node -v
v16.9.0
$ npm -v
7.21.1
$ npm ls react-scripts
└── react-scripts@4.0.3
```
using sublime text and ESLint Formatter package to format on save using eslint_d if that matters, but I remember having that with vscode and the standard LSP formatter
Repository: pytorch
Issue: Track Reliability of Test Reporting and Uploading
Labels: triaged

We handle test reports in different ways:
1. We send them to S3 in their raw form [here](https://github.com/pytorch/pytorch/blob/master/.github/templates/linux_ci_workflow.yml.j2#L351-L377)
2. We send them to S3 (a different bucket) in a parsed form in print_test_stats.py 
3. We use the raw form for PR HUD, like https://hud.pytorch.org/commit/f767cf668395baf29ca7c9f1fa80f0abed8c53c7
4. We use parsed form for test categorization like with slow tests and sharding and target det tests.

When steps 1 or 2 fail, they can affect 3 and 4, which affect developer experience. We would like to detect this failures early on rather than later down the line. We also want to be able to log these processes for ease of debugging.

@suo @pytorch/pytorch-dev-infra
Repository: flutter
Issue: Errors from starting intent on Android are not caught and cause "flutter run" to hang
Labels: platform-android,tool,a: quality,P2,team-android,triaged-android

I had an app installed in my "work" profile on my Android phone, and tried to `flutter run --profile` the app to that phone. It failed with the following (captured later with `--verbose`) and just hung:

```
[  +47 ms] Starting: Intent { act=android.intent.action.RUN flg=0x20000000 cmp=com.example.iosjank/.MainActivity (has extras) }

           Error type 3
           Error: Activity class {com.example.iosjank/com.example.iosjank.MainActivity} does not exist.
```
Repository: pytorch
Issue: Base parallelism on CPU count available to process rather than system total
Labels: triaged,module: multithreading

## 🚀 Feature

Currently when running models on CPU, then PyTorch uses as many parallel threads as it detects cores on the machine. This should instead use the number of cores that the operating system will allow the process to use, for example by checking the CPU affinity.

## Motivation

PyTorch users are used to automatically taking advantage of the full parallelism of the machine they run on. However, when moving to running on other resources (for example, an HPC centre), where there may be multiple concurrent processes running, each with a certain subset of the available CPU cores allocated, then unless manual steps are taken to check or hardcode the number of parallel threads to use, then the process will thrash, and perform far worse than it should.

## Pitch

Rather than assuming all cores on the machine are available to PyTorch, PyTorch should check the CPU affinity of the process and set the number of threads accordingly. This should have zero impact on PyTorch users not running on shared facilities, but will remove a class of issue where PyTorch users starting to run on HPC clusters see their jobs massively underperforming compared to expectations calibrated on their personal machines, due to thrashing.

## Alternatives

The current workaround is to manually call `torch.set_num_threads()`, with the argument either taken from `os.get_schedaffinity(0)` or `psutil.Process().cpu_affinity()`, or by looking for a relevant environment variable such as `SLURM_CPUS_PER_TASK`. Maintaining a list of environment variables used for this purpose by different job schedulers seems out of scope for the PyTorch project, so checking the CPU affinity seems the easier option here. Leaving the configuration to the user means that many users will either be surprised when their job runs slowly and then has to be manually adjusted, or never notice that it is running slowly but waste computing resources.

## Additional context

Since there is no `psutil.Process.cpu_affinity()` on e.g. macOS, then this feature would need to fall back to a reasonable default behaviour (e.g. the current behaviour) if a function for checking affinity is not present.
Repository: pytorch
Issue: CMake outputs lots of warnings in CI
Labels: module: ci,triaged

There are a bunch of warnings, see build here for an example: https://hud.pytorch.org/pr/64600. We should fix / suppress these so cmake runs cleanly (this is just regarding CMake warnings, not anything we see while actually building)

<details>

```
CMake Warning at caffe2/CMakeLists.txt:1729 (add_executable):
  Cannot generate a safe runtime search path for target distributed_test
  because files in some directories may conflict with libraries in implicit
  directories:

    runtime library [libgomp.so.1] in /usr/lib/gcc/x86_64-linux-gnu/5 may be hidden by files in:
      /opt/conda/lib

  Some of these libraries may not be found correctly.


CMake Warning at caffe2/CMakeLists.txt:1729 (add_executable):
  Cannot generate a safe runtime search path for target cpuid_test because
  files in some directories may conflict with libraries in implicit
  directories:

    runtime library [libgomp.so.1] in /usr/lib/gcc/x86_64-linux-gnu/5 may be hidden by files in:
      /opt/conda/lib

  Some of these libraries may not be found correctly.


CMake Warning at modules/detectron/CMakeLists.txt:36 (add_library):
  Cannot generate a safe runtime search path for target caffe2_detectron_ops
  because files in some directories may conflict with libraries in implicit
  directories:

    runtime library [libgomp.so.1] in /usr/lib/gcc/x86_64-linux-gnu/5 may be hidden by files in:
      /opt/conda/lib

  Some of these libraries may not be found correctly.
```

</details>

cc @ezyang @seemethere @malfet @lg20987 @pytorch/pytorch-dev-infra
Repository: rust
Issue: Visualization for str is broken in the latest Windows SDK
Labels: A-debuginfo,T-compiler,O-windows-msvc,C-bug

The update to the latest version of the Windows SDK broke the `str` visualization. 

Related to #88796
Repository: pytorch
Issue: I am unable to detect torch.Tensor._version change during __torch_dispatch__ call
Labels: triaged,module: __torch_dispatch__

## 🐛 Bug

I am unable to detect a version change using __torch_dispatch__ alone with a python subclassed torch.Tensor. Is there another hook/function after dispatch that would reflect the new updated version?

## To Reproduce

SCRIPT:

```py
import torch
from torch.utils._pytree import tree_map

class DirtyTensorTracker(torch.Tensor):
    cpu_elem: torch.Tensor

    def __init__(self, cpu_elem: torch.Tensor):
        self.cpu_elem = cpu_elem
        self.is_dirty = False

    @staticmethod
    def __new__(cls, cpu_elem):
        r = torch.Tensor._make_subclass(cls, cpu_elem.to('cpu'), cpu_elem.requires_grad)
        return r

    #__torch_function__ = torch._C._disabled_torch_function_impl

    @classmethod
    def __torch_dispatch__(cls, func, types, args=(), kwargs=None):
        possibly_dirty = []
        def unwrap(e):
            if isinstance(e, DirtyTensorTracker):
                possibly_dirty.append((e, e.cpu_elem._version))
                return e.cpu_elem
            else:
                return e

        # need to test if tensor is modified

        r = func(*tree_map(unwrap, args), **tree_map(unwrap, kwargs))

        for e, saved_version in possibly_dirty:
            if saved_version != e.cpu_elem._version:
                print("detected dirty")
                e.is_dirty = True
        return r

x = DirtyTensorTracker(torch.randn((2, 2)))
x_old_version = x._version
x_cpu_elem_old_version = x.cpu_elem._version
# should be marked as dirty
x.add_(2)
x_new_version = x._version
x_cpu_elem_new_version = x.cpu_elem._version
print(f"x: old: {x_old_version} new: {x_new_version}")
print(f"x.cpu_elem: old: {x_cpu_elem_old_version} new: {x_cpu_elem_new_version}")
```

OUTPUT:
```
x: old: 0 new: 1
x.cpu_elem: old: 0 new: 1
is x dirty: False
```

## Expected behavior

OUTPUT:
```
x: old: 0 new: 1
x.cpu_elem: old: 0 new: 1
is x dirty: True
```
<!-- A clear and concise description of what you expected to happen. -->

## Environment

 - PyTorch Version (e.g., 1.0): 1.10.0a0+git15eec8e
 - OS (e.g., Linux): Linux
 - How you installed PyTorch (`conda`, `pip`, source): source into conda env
 - Build command you used (if compiling from source): 
 - Python version: 3.9.6
 - CUDA/cuDNN version: N/A
 - GPU models and configuration:N/A
 - Any other relevant information:N/A

## Additional context
This was discussed in a conversation with @ezyang about creating an OffloadTensor that could automatically move a tensor from disk to CPU for the execution of a function, then (if the tensor became dirty) write it back out to disk.
Repository: godot
Issue: Weird spotlight shadow behaviour when cast_shadow = double-sided or cull mode = disabled
Labels: topic:rendering,needs testing,topic:3d

### Godot version

3.3.stable

### System information

Windows 10, GLES3, RTX 2070

### Issue description

Weird "all or nothing" behaviour with the spotlight when the mesh is cast_shadow is set to double-sided or when the material is cull_disabled.
(plus weird shadow popping on the door spaces closed with precisely sized boxes)

cast_shadow = on
![image](https://user-images.githubusercontent.com/106078/132935826-1f94df60-676f-4035-84bf-81a917fed877.png)

cast_shadow = double-side
![image](https://user-images.githubusercontent.com/106078/132935835-4b405499-4f01-48ba-bacb-a273e5088985.png)


### Steps to reproduce

Explained in the description.

### Minimal reproduction project

[Shadowbug.zip](https://github.com/godotengine/godot/files/7147197/Shadowbug.zip)

Press F4 to switch shadow modes on meshes.
Repository: godot
Issue: Add a `use_hdr` property to CurveTexture to complement GradientTexture's recent changes
Labels: enhancement,topic:core

### Godot version

3.3.3.stable

### System information

Windows 10

### Issue description

The CurveTexture only draws a gradient when the value is between 0 and 1, regardless if the max_value property is set to higher than 1. 

Example when max_value is 1
![image](https://user-images.githubusercontent.com/18707771/132935937-20d1ceb4-e4c8-4bf6-b2d9-b08b3a870fae.png)

Example when max_value is 2
![image](https://user-images.githubusercontent.com/18707771/132935952-0f0e706c-070a-4a17-9be4-e7dbdef522c1.png)


### Steps to reproduce

Add a script to a TextureRect node
```
extends TextureRect

export(CurveTexture) var tex

func _ready() -> void:
	texture = tex
```

Modify the exported tex property, set the curve's max_value over 1


### Minimal reproduction project

_No response_
Repository: vscode
Issue: Add telemetry for extension host is detached
Labels: feature-request,extension-host

<!-- ⚠️⚠️ 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. -->
Add telemetry for extension host disconnect runner status.
Add telemetry when the renderer disconnected.
Add telemetry when the extension host socket is closed.
Add telemetry when extension host is ready.
Add telemetry for extension host reduced grace time.
Add telemetry for extension host unhandled errors and termination.
Repository: vscode
Issue: Add telemetry to track reasons for disconnects
Labels: feature-request,remote-connection

<!-- ⚠️⚠️ 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. -->
Add telemetry for disconnects to help with debugging.
Repository: material-ui
Issue: There is an unexpected space when using typography inside grid item - Material v4.12
Labels: discussion,component: Grid

There is an unexpected space between last item and second item. 

My workaround is just use normal text instead of Typography

<img width="1004" alt="qE0gN" src="https://user-images.githubusercontent.com/19651144/132937637-fb3c515a-cb99-417c-ab98-11ebc0d19578.png">

## Steps to Reproduce 🕹

Here is my code

```
<Grid container direction="column" spacing={2}>
      <Grid item>
        <Typography variant="h1">Test</Typography>
      </Grid>
      <Grid item>
        <Grid container alignItems="center" style={{ border: '1px solid red' }}>
          <Grid item xs={2}>
            <Typography variant="body1">Testing Column 1</Typography>
          </Grid>
          <Grid item xs={4}>
            <Typography variant="body1">Testing Column 1</Typography>
          </Grid>
          <Grid item xs={6}>
            <Typography variant="body1">Testing Column 1</Typography>
          </Grid>
        </Grid>
      </Grid>
      <Grid item>Issue Here</Grid>
    </Grid>
```

I would appreciate if you could look into this.
Repository: pytorch
Issue: Add support for GPU based data loading and transformation
Labels: module: dataloader,triaged

## 🚀 Feature
<!-- A clear and concise description of the feature proposal -->
Can pytorch support GPU-based dataloading? 
## Motivation
[RTX IO](https://www.nvidia.com/en-us/geforce/news/rtx-io-gpu-accelerated-storage-technology//) Enable faster texture loading for games. It would be nice if we can have GPU-based dataset loading, saving some precious bandwidth as well as enabling faster data loading. 
<!-- Please outline the motivation for the proposal. Is your feature request related to a problem? e.g., I'm always frustrated when [...]. If this is related to another GitHub issue, please link here too -->


cc @SsnL @VitalyFedyunin @ejguan