sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: File sorting/filtering
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

The ability to automate the moving of files based on sorting/filtering rules that employ regular expressions to only affect certain files by name or extension.

### Scenario when this would be used?

Say you have hundres of files with names like "Expense Report - John Smith.pdf" or "Art by Jane Doe.jpg", where being able to select just the files with "Expense Report" in their names via regex and then move them to a designated folder would be helpful.  Or just selecting files by a specific artist and doing specific tasks on them such as placing all artwork in a zip archive, moving or deleting them that sort of thing.

Basically choosing files based on file name, file extension, tags, dimensions, GPS location, etc and then moving them where I want to store them.  Of course, it needs to versatile and fast, so the power user can easily handle hundreds, thousands or even several tens of thousands of files quickly. (e.g. a Wedding Photographer, Web Developer or just someone who likes to download lots of images from various websites.)

The ability to export rules on one computer and then import them on another machine would also be helpful.

### Supporting information

Programs that do something similar but have certain failings, such as being to slow, having a poor interface design or not using regular expressions on files properties:

- http://davidevitelaru.com/index.php?page=software
- https://www.filejuggler.com/features/
- http://www.dropitproject.com/
Repository: material-ui
Issue: Improve the styling DX to quickly find a specific component using browser dev tools
Labels: package: system,dx

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Summary 💡

This StackOverflow question (that I wrote) explains the problem clearly:

https://stackoverflow.com/questions/71152038/in-mui-v5-how-do-you-debug-find-a-specific-element-style-class-in-the-dev-tools

Quick recap:

In MUI v4, it was very easy to locate a specific component and it's style block (`HelloWorld-main`) using the browser dev tools:

<img src="https://i.stack.imgur.com/jDVvI.png" width="400" />

In MUI v5, the dev tools `Mui-root css-1lekm29` does not indicate the componnt/style block in the React code:

<img src="https://i.stack.imgur.com/ruuLH.png" width="400" />

After an email response from [Olivier Tassinari](https://www.linkedin.com/in/oliviertassinari/), he suggested I open this issue.

This is an excerpt from Olivier's email, specifically with his solution:

> Emotion has a babel plugin to link where the styles have been created https://emotion.sh/docs/@emotion/babel-plugin. The DX should feel like this https://user-images.githubusercontent.com/3468483/157389915-6f08dc9b-f3b2-47b3-b9cf-6768681f81fe.mp4.
> 
> I did a bit more exploration on the problem, I have found that because of our custom _document.tsx Next.js integration using [extractCriticalToChunks](https://github.com/emotion-js/emotion/blob/7d9e74f8f0d0e0ea60573a19965eded61dc41024/packages/server/src/create-instance/extract-critical-to-chunks.js), we don't provide the source map, breaking the source map. Without, it works :), proof:
>
> <img src="https://user-images.githubusercontent.com/1320083/182503997-42e173d3-c254-49ad-9fe4-5811201da000.png" width="400" />

Olivier ended the email with:

> Now, in our case, we are using the <Box>, the babel plugin only looks at the styled() calls, so it would likely need a custom Babel plugin to make it work.
> ...
> It could be a great opportunity to improve the styling DX. For example, when using Tailwind CSS, I believe that this problem is unsolved.




### Examples 🌈

https://user-images.githubusercontent.com/3468483/157389915-6f08dc9b-f3b2-47b3-b9cf-6768681f81fe.mp4



### Motivation 🔦

Given a very large React app, it's very easy to get lost in all of the components, so being able to quickly locate a specific component after inspecting the DOM in dev tools would be critical to the DX (as Olivier mentioned in his email).
Repository: material-ui
Issue: Container sx maxWidth being overwritten
Labels: component: Container

### Duplicates

- [X] I have searched the existing issues

### Latest version

- [X] I have tested the latest version

### Current behavior 😯

When using `maxWidth` inside `sx` prop it gets overwritten by `lg` breakpoint

see the bug here...

https://codesandbox.io/s/container-sx-maxwidth-bug-d3uy8r

this happens because of this line:

https://github.com/mui/material-ui/blob/master/packages/mui-system/src/Container/createContainer.tsx#L137


### Expected behavior 🤔

Container looks up sx `maxWidth` before defaulting to `lg`

### Steps to reproduce 🕹

Steps:

1. Open the code [sandbox](https://codesandbox.io/s/container-sx-maxwidth-bug-d3uy8r?file=/src/App.tsx)
2. Notice that I'm setting `sm` as the `maxWidth` inside `sx` (this is actually supported)
3. When the component renders, you can see the maxWidth is there but it is actually getting overwritten 


### Context 🔦

Since the `sx` prop is supported for container, it is important to let users set the maxWidth there similar to how it works with other components like Box.

### Your environment 🌎

```
System:
    OS: macOS 12.4
  Binaries:
    Node: 16.15.1 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 8.11.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 103.0.5060.134
    Edge: Not Found
    Firefox: Not Found
    Safari: 15.5
  npmPackages:
    @emotion/react: ^11.9.3 => 11.9.3 
    @emotion/styled: ^11.9.3 => 11.9.3 
    @mui/base:  5.0.0-alpha.92 
    @mui/codemod:  5.9.3 
    @mui/docs:  5.9.3 
    @mui/envinfo:  2.0.6 
    @mui/icons-material:  5.8.4 
    @mui/joy:  5.0.0-alpha.39 
    @mui/lab:  5.0.0-alpha.93 
    @mui/markdown:  5.0.0 
    @mui/material:  5.9.3 
    @mui/material-next:  6.0.0-alpha.47 
    @mui/private-theming:  5.9.3 
    @mui/styled-engine:  5.8.7 
    @mui/styled-engine-sc:  5.9.3 
    @mui/styles:  5.9.3 
    @mui/system:  5.9.3 
    @mui/types:  7.1.5 
    @mui/utils:  5.9.3 
    @mui/x-data-grid:  5.13.0 
    @mui/x-data-grid-generator:  5.13.0 
    @mui/x-data-grid-premium:  5.13.0 
    @mui/x-data-grid-pro:  5.13.0 
    @mui/x-date-pickers:  5.0.0-alpha.3 
    @mui/x-date-pickers-pro:  5.0.0-alpha.3 
    @mui/x-license-pro:  5.12.3 
    @types/react: ^18.0.14 => 18.0.14 
    react: ^18.2.0 => 18.2.0 
    react-dom: ^18.2.0 => 18.2.0 
    styled-components:  5.3.5 
    typescript: ^4.6.4 => 4.6.4 

```
Repository: rust
Issue: Non exhaustive match error presents incompletely with tuples and .unwrap()
Labels: A-diagnostics,T-compiler,C-bug

When matching against a tuple, if one of the values is an `Option<char>`, unwrapping it in the match statement itself provides a garbled error message from the compiler. 


previous_chr is of type `Option<char>`
current_chr if of type `char`


```
match ( (previous_chr.unwrap(), current_chr) ){
    ('\\', '"') => {
        self.is_within_literal = true; 
        self.previous_chr = Some(current_chr)
    }
} 
```

I would expect a typical error message stating that the None case for the optional value is not covered. Instead, this message is returned by the compiler:
```
   --> src\interpreter\helpers\mod.rs:147:23
    |
147 |                 match ((self.previous_chr.unwrap(),current_chr)){
    |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ patterns `('\0'..='[', _)`, `(']'..='\u{d
7ff}', _)` and `('\u{e000}'..='\u{10ffff}', _)` not covered
    |
    = note: the matched value is of type `(char, char)`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern, a match ar
m with multiple or-patterns as shown, or multiple match arms
152 +                     ('\0'..='[', _) | (']'..='\u{d7ff}', _) | ('\u{e000}'..='\u{10ffff}', _) => todo!()   
    |

```

Changing the code to the following...
```
match ( (previous_chr, current_chr) ){
    (Some('\\'), '"') => {
        self.is_within_literal = true; 
        self.previous_chr = Some(current_chr)
    }
} 
```

...produces the expected message:

```
   --> src\interpreter\helpers\mod.rs:147:23
    |
147 |                 match ((self.previous_chr,current_chr)){
    |                       ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ pattern `(None, _)` not covered
    |
    = note: the matched value is of type `(std::option::Option<char>, char)`
help: ensure that all possible cases are being handled by adding a match arm with a wildcard pattern or an expli
cit pattern as shown
    |
151 ~                     }
152 +                     (None, _) => todo!()
    |
```
rust version:

rustc 1.64.0-nightly (4493a0f47 2022-08-02)
binary: rustc
commit-hash: 4493a0f4724c0bae1436242d76cccc9c0a287b80
commit-date: 2022-08-02
host: x86_64-pc-windows-msvc
release: 1.64.0-nightly
LLVM version: 14.0.6


There is no panic and no backtrace is emitted.
Repository: TypeScript
Issue: Allow decorators to apply type guards to arguments of the method/function they decorate
Labels: Suggestion,Awaiting More Feedback

# Bug Report

### 🔎 Search Terms
decorators, type guards

### 🕗 Version & Regression Information
- This is the behavior in every version I tried, and I reviewed the FAQ for entries about decorators

### ⏯ Playground Link
[Playground link with relevant code](https://www.typescriptlang.org/play?#code/MYGwhgzhAEAyD2BzACgUwE4XgO2gbwFgAoaU6AAQEsIA5MAW1WXVQlWwBdizoQkAKAA4Ys2AFzQ0mHAEp83HmQD0S6MOnYAdNgapo1aIgCuYdGE6pUAE2gd40AEZ6w0CB3SVsiaFaN67FNR0jMys7Bw+qMDwZnboADTQAJ6oERjoMfowbpQgILYAFhkA7tgKioVBllYQUqLBqEIiONq6MuXQAL7E3UTEnhwYAGZgwHp1OPIkZDqMEm4eXtAAPtBG2FaoQ57WPcTEQ+vAHJSTQbqhbJz8HKaIqRLmSYmCGeocSQDSqEnz7p6IRKbCDADyCOISZjwd5JAAirFBlHBMTkhGmFWi2Dc0BilEQnjAIAAYkcTpMALyREFguKaABuhL8AG4OjxgYjkeh6Yy9JTDthjqdcPxUayKtBMdj1KJoJS7kZGJwIABtAAMAF0WX10eLSJQhtAmhpWoxZeTKdgjHkVqtpS1ZrzzWsNlsdlZ2jrdTwWBwjOhcJL4CBUJo+Ih+AAiCa4KzwVjYADkEQKYDpzmgDojMi1XrIYoqPr9uFx+J0xNJQs0YEEghASRuBWoiXlio4EGz+a6e21-MFkw4jdo1VqzWwDX4Dr+i0Qop1geDoYEAAMHVloAASPAOzpLj2dIA)

### 💻 Code
```ts
class LogPerson {
    @isNamePresent
    log(person: Person) {
        // person.name is guaranteed to be a string due to @isNamePresent decorator, yet error is still thrown
        thisNeedsPersonName(person.name)
    }
}

interface Person {
    name: string | undefined
}

function isNamePresent(target: any, propertyKey: string, descriptor: PropertyDescriptor) {
        const originalFunction = descriptor.value;
        descriptor.value = function () {
            const person = arguments[0];

            if (person.name === null || person.name === undefined)
                return console.log("Person doesn't have a name");
            
            return originalFunction.apply(this, arguments);
        }
}

function thisNeedsPersonName(name: string) {
    console.log(`name is ${name}`)
}
```

### 🙁 Actual behavior
TypeScript throws the error `Type 'undefined' is not assignable to type 'string'.` when person.name is used as a parameter to a method guarded by the `@isNamePresent` decorator

### 🙂 Expected behavior
TypeScript should see the decorator's type guard show the person.name field as only being a string, not `string | undefined`.
*This could be too closely related to function calls not resetting narrowing, in which case, just close this issue. Though I do think it is different enough where it might be possible to be fixed.*
Repository: godot
Issue: Directional shadow rendering breaks when using specific Camera frustum offset values
Labels: bug,topic:rendering,topic:3d

### Godot version

3.5.rc (f9db8fa70)

### System information

Fedora 36, GeForce GTX 1080 (NVIDIA 515.57)

### Issue description

Directional shadow rendering breaks when using specific Camera frustum offset values. This occurs both when using GLES3 and GLES2, and both with the Orthogonal and PSSM 4 Splits shadow rendering modes:

https://user-images.githubusercontent.com/180032/182549972-0a95ca02-67c7-40f2-a6ad-f18ac7a439bf.mp4

This does not occur on 4.0.alpha 1839cae8a. The angle at which the DirectionalLight is positioned doesn't seem to affect this issue: it'll always occur at the same camera frustum offset.

### Steps to reproduce

Download the MRP below, run the project and move the mouse around. (The MRP aims to simulate [Y-shearing](https://zdoom.org/wiki/Y-shearing), see https://github.com/godotengine/godot-proposals/issues/2713#issuecomment-1203565263.)

### Minimal reproduction project

[test_y_shearing_3.x.zip](https://github.com/godotengine/godot/files/9249004/test_y_shearing_3.x.zip)
Repository: PowerToys
Issue: Switch VDs with scrolling/ improved control 
Labels: Idea-New PowerToy,Product-Virtual Desktop

### Description of the new feature / enhancement

Hey, i would like to see an improved Expierence of  Virtuel Desktop, to make it more Like gnome in Fedora. That means an open of menu with the Windows Key and and fast Switch with the Mouse Wheel. This should improve the user expierence a lot.

### Scenario when this would be used?

Improved user expierence of the Virtuel Desktop in WIN 11.

### Supporting information

_No response_
Repository: react
Issue: ReactDevTools extension doesn't work in private Firefox windows [DevTools Bug]: 
Labels: Type: Bug,Status: Unconfirmed,Component: Developer Tools

### Website or app

reactjs.org

### Repro steps

1. Install the ReactDev tools extension for Firefox ( I am running Firefox Dev edition Version 104.0b5 on Debian-Linux)
2. Allow the extension to run in private WIndows by going to Add-ons and themes (Ctrl + Shift + A)
3.  Visit any website running a  development or production of React in Firefox(I have tested Firefox dev Edition and FirefoxESR) 
4. Open Firefoxdevtools and visit the components tab added by the Reactdevtools extenstion
5. I have tested a local dev build and a production build of React, and weirdly it works in non-private windows. But in Private windows, it doesn't see that the page uses React.
6. Below is a screenshot of what I see on both websites
7. ![reactdevtoolsbug](https://user-images.githubusercontent.com/97474001/182564648-ea35b0cf-0395-48b4-9c07-0220044d5422.png)




### How often does this bug happen?

Every time

### DevTools package (automated)

_No response_

### DevTools version (automated)

_No response_

### Error message (automated)

_No response_

### Error call stack (automated)

_No response_

### Error component stack (automated)

_No response_

### GitHub query string (automated)

_No response_
Repository: tensorflow
Issue: AttributeError: '_UserObject' object has no attribute 'add_slot'
Labels: stat:awaiting tensorflower,type:bug,comp:dist-strat,2.6.0

Issue Type: Bug
Source: binary
Tensorflow Version: 2.6
Custom Code: Yes


# Current Behaviour?

I have model, saved using `SavedModel` format. The model is trained on Kaggle TPU and saved in the following ways:

```python
# in kaggle tpu, it must be saved in the following way!
save_locally = tf.saved_model.SaveOptions(experimental_io_device='/job:localhost')
final_model.save('./final_model', options=save_locally)
 ```

Now, it seems like, if I try to load this model in the following way, 

```python
model = tf.saved_model.load("final_model")

---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
/tmp/ipykernel_17/3033429325.py in <module>
----> 1 model = tf.saved_model.load("final_model")
...
...
AttributeError: '_UserObject' object has no attribute 'add_slot'
```

But if I do as follows, it works.

```
model = tf.keras.models.load_model("final_model")
```

But for some reason, I need to make `tf.saved_model.load` API work instead `tf.keras.models.load_model` API. What approach should we take here?
Repository: rustdesk
Issue: Extra Mouse Button and left/right wheel issues (Linux not ready yet, because of flutter bug)
Labels: bug,help wanted

**Describe the bug you encountered:**

On a mouse with extra buttons:
- The scroll left and scroll right buttons are reversed.
- The back and forward mouse buttons are not supported at all.

**Scroll left/right:**
For example, on this page:
https://www.w3schools.com/howto/howto_css_menu_horizontal_scroll.asp

On the little example navigation area which has a horizontal scrollbar, in normal use (not using RustDesk) clicking the scroll right button (tiliting middle button to the right) will scroll to the right normally. However, when doing this on a remote machine using RustDesk, the behaviour of the scroll buttons are reversed - tilting the middle button to the right scrolls left, and tilting left scrolls right.

**Back and forward buttons:**
The back and forward buttons do not seem to be passed through to the remote machine at all (for example, these buttons are normally used to navigate back/forward in a web browser or through folders in Windows Explorer etc).

If it will help, according to what I have read online, the "back" button should be XBUTTON1 and "forward" should be XBUTTON2 [(source)](https://docs.microsoft.com/en-us/windows/apps/design/basics/navigation-history-and-backwards-navigation#handle-mouse-navigation-buttons).

https://docs.microsoft.com/en-us/windows/win32/inputdev/virtual-key-codes

For the right/left scroll, I'm unsure how they work whether it's as a button or maybe this - simply my guess.

https://docs.microsoft.com/en-us/windows/win32/inputdev/wm-mousehwheel

On my mouse, it clicks like a button but maybe it's technically a wheel. In any case, as stated above, it is currently implemented but in reverse.

...

**What did you expect to happen instead?**
Reverse the current scroll left/right behaviour to fix the scrolling issue. Scrolling right on the mouse should scroll right, and left should scroll left.

Implement passthrough for back and forward mouse buttons.

...

**How did you install `RustDesk`?**

Build from source (yesterday)

---

**RustDesk version and environment**

Client: Windows 10, Rustdesk built from source
Remote: Windows 7, Rustdesk 1.1.9 downloaded from website.
Repository: vscode
Issue: Ambiguous characters warn about box drawing \ but not / or |
Labels: bug,unicode-highlight

![image](https://user-images.githubusercontent.com/2193314/182579840-ccdfbf6e-06c8-4384-96a7-2609e2ac0066.png)

Seems like these should be warned as well:

- U+2572: \
- U+2502: |
- Maybe also: U+2503: |
Repository: pytorch
Issue: build fail when using lto with gcc
Labels: module: build,triaged

### 🐛 Describe the bug

The bug is reported to gentoo at https://bugs.gentoo.org/862672

During the build I get

_/var/tmp/portage/sci-libs/caffe2-1.12.0/work/pytorch-1.12.0/aten/src/ATen/native/cpu/moments_utils.h:76: error: type of ‘c_vecs’ does not match original declaration [-Werror=lto-type-mismatch]
   76 |     static std::array<Vec, kChunkSize> c_vecs = ([]() {
      | 
/usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/include/g++-v11/array:95: note: type name ‘std::array<at::vec::DEFAULT::Vectorized<c10::BFloat16>, 16ul>’ should match type name ‘std::array<at::vec::AVX2::Vectorized<c10::BFloat16>, 16ul>’
   95 |     struct array
      | 
/var/tmp/portage/sci-libs/caffe2-1.12.0/work/pytorch-1.12.0/aten/src/ATen/native/cpu/moments_utils.h:76: error: ‘c_vecs’ violates the C++ One Definition Rule [-Werror=odr]
   76 |     static std::array<Vec, kChunkSize> c_vecs = ([]() {
      | 
/usr/lib/gcc/x86_64-pc-linux-gnu/11.3.0/include/g++-v11/array:95: note: type name ‘std::array<at::vec::DEFAULT::Vectorized<c10::BFloat16>, 16ul>’ should match type name ‘std::array<at::vec::AVX512::Vectorized<c10::BFloat16>, 16ul>’
   95 |     struct array
      | 
/var/tmp/portage/sci-libs/caffe2-1.12.0/work/pytorch-1.12.0/aten/src/ATen/native/cpu/moments_utils.h:76: note: ‘c_vecs’ was previously declared here
   76 |     static std::array<Vec, kChunkSize> c_vecs = ([]() {
      | 
/var/tmp/portage/sci-libs/caffe2-1.12.0/work/pytorch-1.12.0/aten/src/ATen/native/cpu/moments_utils.h:76: note: code may be misoptimized unless ‘-fno-strict-aliasing’ is used_

my guess is that the compiler has problem (in lto mode) to distinguish the various static variable c_vecs created on different instance of the template

### Versions

version is 1.12.0

Collecting environment information...
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A

OS: Gentoo Base System release 2.8 (x86_64)
GCC version: (Gentoo 11.3.0 p4) 11.3.0
Clang version: 14.0.4
CMake version: version 3.22.4
Libc version: glibc-2.34

Python version: 3.10.5 (main, Jun 29 2022, 11:04:31) [GCC 11.3.0] (64-bit runtime)
Python platform: Linux-5.15.32-gentoo-r1-x86_64-x86_64-Intel-R-_Core-TM-_i5-4570_CPU_@_3.20GHz-with-glibc2.34
Is CUDA available: N/A
CUDA runtime version: Could not collect
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A
Is XNNPACK available: N/A

Versions of relevant libraries:
[pip3] numpy==1.22.3
[conda] Could not collect

cc @malfet @seemethere
Repository: flutter
Issue: [camera] White balance lock feature support.
Labels: c: new feature,p: camera,package,c: proposal,team-ecosystem,P3,triaged-ecosystem

## Use case
I would like to create a camera app that can locked exposure and white balance, but Flutter's camera plugin only have exposure setting function.

## Proposal

Both iOS and Android seem to provide a way to lock the white balance.

**iOS**
WhiteBalanceMode.locked

**Android**
CaptureRequest.CONTROL_AWB_MODE_OFF
Repository: neovim
Issue: Sinhala language/script causes artifacts unless XTERM is set to empty string
Labels: bug,tui,display,unicode  💩

### Neovim version (nvim -v)

v0.7.2

### Vim (not Nvim) behaves the same?

no, vim 8.1

### Operating system/version

Ubuntu 20.04.4 LTS

### Terminal name/version

GNOME Terminal 3.36.2

### $TERM environment variable

xterm-256color

### Installation

Neovim PPA

### How to reproduce the issue

1.  Open a text in Sinhala language/script.  I reproduced it with <https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/client/src/__locales/si-lk.json>.

2.  ```sh
    env XTERM='xterm-256color' nvim --clean ./client/src/__locales/si-lk.json
    ```

3.  Try to edit the file.

### Expected behavior

The file is shown and edited with no issues.

### Actual behavior

There are artifacts that prevent me from editing the file normally.  See screenshot:

![Screenshot from 2022-08-03 15-21-27](https://user-images.githubusercontent.com/4964986/182606460-05332733-2e7d-4a43-b216-cab148753647.png)

Additionally, using `XTERM=''` fixes the issue, so my theory is that it has something to do with colour.

Using or not using `tmux` doesn't seem to matter.
Repository: PowerToys
Issue: Unable to turn off "Always run as administrator
Labels: Issue-Bug,Area-Runner,Needs-Repro,Needs-Triage

### Microsoft PowerToys version

0.61.1

### Running as admin

- [X] Yes

### Area(s) with issue?

General

### Steps to reproduce

Turning off "Always Run as Administrator" doesn't work.  Requires admin login at every startup.

### ✔️ Expected Behavior

Unchecking "Always Run as administrator" would save the setting.  Restart of PowerToys would not require an admin login.

### ❌ Actual Behavior

PowerToys asks for admin login during next restart.  "Always run as administrator" is checked on again.

### Other Software

_No response_