sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: PowerToys
Issue: Sound Profiles - Saving Playback Device + Microphone Combinations
Labels: Idea-New PowerToy

### Description of the new feature / enhancement

It's very common now to have numerous devices for both Audio Output Devices such as a headset, speakers, digital audio devices, microphones, etc.  And when we're doing various activities, we have to select among all these devices depending on our activity.  So if I'm using TEAMS for a conference call, I have to select a headset and microphone when I don't want to disturb others that may be working around me, or I want the PC's speakers and my Elgato microphone when my call is for a group.  It's a PITA. Now add the complexity of using not just TEAMS, but ZOOM, WEBEX, CHIME, etc.  Different settings for different use cases.  How about GAMING, and changing settings when various game scenarios are needed.

So the new feature here is to simply create a Sound Profile that activates the devices needed for the use case, and save those profiles so they can be quickly accessed and enabled in one click, or as a keyboard shortcut.

### Scenario when this would be used?

It's very common now to have numerous devices for both Audio Output Devices such as a headset, speakers, digital audio devices, microphones, etc.  And when we're doing various activities, we have to select among all these devices depending on our activity.  So if I'm using TEAMS for a conference call, I have to select a headset and microphone when I don't want to disturb others that may be working around me, or I want the PC's speakers and my Elgato microphone when my call is for a group.  It's a PITA. Now add the complexity of using not just TEAMS, but ZOOM, WEBEX, CHIME, etc.  Different settings for different use cases.  How about GAMING, and changing settings when various game scenarios are needed.

### Supporting information

_No response_
Repository: svelte
Issue: background video no auto play on loaded in firefox on mobile device like smartphone and tablet
Labels: media elements

### Describe the bug

I have a background video on a webpage, the video is `av1` inside `mp4` container and supported by `firefox`
Only poster image is displayed, video never starts playing 

this is the code

```
<script lang="ts">
  import vi from './assets/videofile.mp4'
  import posterimg from './assets/PosterImage.png'
</script>

<main>
  <video
  autoplay 
  muted 
  loop
  Playsinline
  src={vi}
  poster={posterimg}>
  </video>
</main>

<style>
video 
{
  width: 100%;
  -moz-user-select: none;
  -webkit-user-select: none;
  user-select: none;
  pointer-events: none;
}
</style>
```

### Reproduction

Unable to reproduce the issue while development in `responsive design mode` in firefox.

You can create a `svelte app` using `vite`, with simple video playing in background.

`built` it and host it on `github pages` once for free and access it from a `mobile device` like `smartphone` or `tablet` from `firefox` check it

The issue only on `firefox` when opened on mobile device, works fine `Chrome` & `Opera` on both computer and mobile device.

### Logs

```shell
firefox browser log details from android browser


Media resource https://mywebsite.com/assets/videofile.87f84cd1.mp4 could not be decoded. mywebsite.com
Some cookies are misusing the recommended “SameSite“ attribute 2
Cookie “_ga” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:35:486
Cookie “_gid” will be soon rejected because it has the “SameSite” attribute set to “None” or an invalid value, without the “secure” attribute. To know more about the “SameSite“ attribute, read https://developer.mozilla.org/docs/Web/HTTP/Headers/Set-Cookie/SameSite analytics.js:35:486
Media resource https://mywebsite.com/assets/videofile.87f84cd1.mp4 could not be decoded, error: Error Code: NS_ERROR_DOM_MEDIA_METADATA_ERR (0x806e0006)
```
```


### System Info

```shell
$ npx envinfo --system --npmPackages svelte,rollup,webpack --binaries --browsers

  System:
    OS: Linux 5.4 Ubuntu 20.04.3 LTS (Focal Fossa)
    CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz
    Memory: 406.05 MB / 3.72 GB
    Container: Yes
    Shell: 5.0.17 - /bin/bash
  Binaries:
    Node: 17.4.0 - /usr/local/bin/node
    Yarn: 1.22.17 - /usr/bin/yarn
    npm: 8.3.1 - /usr/local/bin/npm
  Browsers:
    Firefox: 96.0


```
```


### Severity

annoyance
Repository: create-react-app
Issue: CRA 5 installs prettier-plugin-tailwindcss which changes prettier behavior to sort classNames (also it's unlicensed)
Labels: needs triage,issue: bug report

### Describe the bug

After installing CRA5, prettier started reporting errors for class names which aren't sorted. Upon inspection, I found this to be caused by the install of [prettier-plugin-tailwindcss](https://github.com/tailwindlabs/prettier-plugin-tailwindcss). This lib is undesirable as it alters the default Prettier config, and because it's installed as a plugin unconfigurable.

In addition, this library is unlicensed, so using it is suspicious legally.
In addition, this library is uglified, so its published code can hardly be reviewed and may be harmful.

### Did you try recovering your dependencies?

Yes

### Which terms did you search for in User Guide?

I searched the entire repo for mentions of the plugin, and did not find anything relevant.

### Environment

Environment Info:

  current version of create-react-app: 5.0.0
  running from /Users/martijnhols/.npm/_npx/c67e74de0542c87c/node_modules/create-react-app

  System:
    OS: macOS 11.6.2
    CPU: (16) x64 Intel(R) Core(TM) i9-9980HK CPU @ 2.40GHz
  Binaries:
    Node: 16.10.0 - ~/.nvm/versions/node/v16.10.0/bin/node
    Yarn: 1.22.17 - ~/.yarn/bin/yarn
    npm: 7.24.0 - ~/.nvm/versions/node/v16.10.0/bin/npm
  Browsers:
    Chrome: 98.0.4758.80
    Edge: Not Found
    Firefox: 88.0
    Safari: 15.2
  npmPackages:
    react: ^17.0.2 => 17.0.2 
    react-dom: ^17.0.2 => 17.0.2 
    react-scripts: ^5.0.0 => 5.0.0 
  npmGlobalPackages:
    create-react-app: Not Found

### Steps to reproduce

1. Install CRA 5
2. install `prettier`
3. Write any kind of code with classNames e.g. `table table-condensed` which is already sorted as desired
4. find prettier to complain about the className order while it works fine in CRA4 or any project with standard prettier

### Expected behavior

I would expect CRA5 not to alter default Prettier config.

### Actual behavior

The `prettier-plugin-tailwindcss` plugin is installed and alters Prettier config.
Repository: flutter
Issue: [PopUpMenuButton] [Proposal] Add the ability to customise Modal Barrier Behaviour
Labels: c: new feature,framework,f: material design,f: gestures,P3,team-design,triaged-design

## Introduction

As discussed in #90223 the PopUpMenuButton (and I also found that DropdownButton and DropdownButtonFormField) doesn't close when scrolling. The Material behavior seems to describe that any gesture would close it, but it's not. This is being fixed by this PR: #98191 

However, I also mentioned about a proposal to allow drag/scroll gestures to be passed down to the layer behind so the content behind the modal can be scrolled (possibly with the popUp content too).

## Proposal

Add some kind of behavior (given by an enum value) to the widgets that use a modal barrier. The possible behaviors are:
- closeOnAnyTap: this is the default Material behavior (after fixing the bug that the modal doesn't dismiss with drag/scroll) for everything (mobile, desktop, web)
- passThrough: allows drag gestures (not taps, taps close the modal) to be passed down to the widgets behind it, this allows some Desktop/Web behavior for pop up menus and dropdowns (an example is right here on GitHub where you can click the top right kebab menu ( **. . .** ) and then scroll the page (web desktop only, on mobile it closes immediately with any interaction) you'll notice that the menu keeps open, and it keeps scrolling alongside the origin of the menu with the page itself.


## Use case

When building large forms on Flutter web, this is basically a need, users might need to scroll to get some other fields visible while they have the popUp open to make a decision on what to pick.

When making desktop/web apps that have menus (like File, Edit, View, Insert, Format, etc for Docs on Google Docs) you can open a specific menu and then scroll the content of the page, some users do this on the same motivation as the previous one, to check some content before making a choice of the menu options (they just want to have the options visible while looking at the content they are working on)

## Proposal

The widgets using the modal barrier can look now something like this:

```dart
PopupMenuButton<int>(
  icon: const Icon(Icons.view_list_rounded),
  //closes the modal with any gesture (as soon as the cursor taps/clicks down) this is the default behavior
  //modalBehavior: ModalBehavior.closeOnAnyTap,
  modalBehavior: ModalBehavior.passThrough,  //lets the scrolling/dragging gestures be passed down
  onSelected: (_) {},
  itemBuilder: (context) => List.generate(
    100,
    (i) => PopupMenuItem(
      child: Text('Pop Up Menu Item $i'),
      value: i,
    ),
  ),
),
```

P.S: Don't take the naming I gave as solid, I'm the worst at naming things, so, make it something that makes sense in the context of flutter/menus/popups/modals/whatever you think is best :)
Repository: next.js
Issue: Docker container stops when Next/Image is used on DiskStation NAS (Intel Atom CPU)
Labels: bug,Image (next/image)

### Run `next info` (available from version 12.0.8 and up)

    Operating System:
      Platform: win32
      Arch: x64
      Version: Windows 10 Pro
    Binaries:
      Node: 17.4.0
      npm: 8.3.1
      Yarn: 1.22.17
      pnpm: N/A
    Relevant packages:
      next: 12.0.10
      react: 17.0.2
      react-dom: 17.0.2

For my local development environment

### What version of Next.js are you using?

12.0.10

### What version of Node.js are you using?

17.4.0

### What browser are you using?

Chrome 98.0.4758.82

### What operating system are you using?

DSM 6.2.4-25556 Update 3

### How are you deploying your application?

next dev

### Describe the Bug

When I open a page which contains a next/image element the browser connection for the image request terminates with:
`GET http://diskstation:3000/_next/image?url=%2Fdata%2Fdylan-taylor-RXaQgz7qTqI-unsplash.jpg&w=1920&q=75 net::ERR_CONNECTION_RESET`

The docker container output in `stdout` returns `error Command failed with signal "SIGILL".` After that, the docker container stops.

#### My analysis so far

I narrowed it down to the next/image component, but I'm not sure about the root cause yet. I landed at this [node.js issue](https://github.com/nodejs/build/issues/704) about CPU instruction sets and hashing algorithms (sha*). So I assume the CPU (Intel Atom) is missing some instruction sets? But I can't tell what next/image is even using.

Maybe I'm on the completely wrong track here...

I tried it with the productive image first, but ended up with `next dev` to receive better logs.

### Expected Behavior

The application is able to load images with the next/image component on the NAS too.

### To Reproduce

Run the docker image which contains the Next/Image component on an INTEL Atom D2700 like in the Synology Diskstation DS412+

* Tag with next/image, which doesn't work [0.0.16](https://registry.hub.docker.com/layers/solloc/picture-browser/0.0.16/images/sha256-c1bd651008f3aab9e530fe7e6c4ad3caeb0d55b2fd336cd75cfd890b40c26999?context=explore) / [repo](https://github.com/solloc/picture-browser/tree/a5cb7dfbb194ad9b6bc2b7718c40fd40e3355083)
* Tag with `<img>` which works [0.0.17](https://registry.hub.docker.com/layers/solloc/picture-browser/0.0.17/images/sha256-a2efad0584ca4fb3cf28d47115fa2c640074dcfb40cd73f5a799d45403787d4c?context=explore) / [repo](https://github.com/solloc/picture-browser/tree/fcc04d5c45166064d2337eee7f17bc3d3955a930)
Repository: pytorch
Issue: nn.functional No-batch-dim support should have OpInfo examples
Labels: module: nn,module: tests,triaged

### 🚀 The feature, motivation and pitch

Filing this so we can track the issue. @jbschlosser tells me that no-batch-dim (https://github.com/pytorch/pytorch/issues/60585) testing is done with ModuleInfo and not OpInfo. However, this means that subsystems that only use OpInfos to test their semantics may be unaware of the new changes. We should update OpInfos with no-batch-dim examples like how we added ModuleInfo testing for them.

### Alternatives

_No response_

### Additional context

_No response_

cc @albanD @mruberry @jbschlosser @walterddr @kshitij12345
Repository: godot
Issue: Cannot edit AtlasTexture in 2d array
Labels: bug,topic:editor,confirmed

### Godot version

3.4.2

### System information

Kubuntu 20.04 GLES3 Ryzan 7 5700G with Radeon Graphics

### Issue description

I can't open or edit a TextureAtlas when nested inside a 2d array
```
export (Array, Array, Texture) var selections      : Array
```
![image](https://user-images.githubusercontent.com/2453707/153496668-7604ed9f-8eb1-4104-bda1-084567383bd6.png)
This does seem to work with AnimatedTexture though

### Steps to reproduce

1. `export (Array, Array, Texture) var selections      : Array`
2. try to open it in inspector and edit the texture

### Minimal reproduction project

_No response_
Repository: rust
Issue: Confusing diagnostic from const eval when offsetting a pointer out of bounds
Labels: A-diagnostics,T-compiler,A-const-eval

Given the following code: [playground link](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2021&gist=57e2129e26c3f847391d9e9e0d35603c)

```rust
#![feature(const_ptr_offset)]
const fn demo() -> *const u8 {
    let x = 0u8;
    let ptr = &x as *const u8;
    unsafe { ptr.offset(3) }
}

const P: *const u8 = demo();

fn main() {}
```

The current output is:

```
error[E0080]: evaluation of constant value failed
   --> /home/ben/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/const_ptr.rs:295:18
    |
295 |         unsafe { intrinsics::offset(self, count) }
    |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |                  |
    |                  pointer arithmetic failed: alloc2 has size 1, so pointer to 3 bytes starting at offset 0 is out-of-bounds
    |                  inside `ptr::const_ptr::<impl *const u8>::offset` at /home/ben/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/const_ptr.rs:295:18
```

Ideally the output should look like:

```
error[E0080]: evaluation of constant value failed
   --> /home/ben/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/const_ptr.rs:295:18
    |
295 |         unsafe { intrinsics::offset(self, count) }
    |                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    |                  |
    |                  pointer arithmetic failed: alloc2 has size 1, so pointer to 1 byte starting at offset 3 is out-of-bounds
    |                  inside `ptr::const_ptr::<impl *const u8>::offset` at /home/ben/.rustup/toolchains/nightly-x86_64-unknown-linux-gnu/lib/rustlib/src/rust/library/core/src/ptr/const_ptr.rs:295:18
```

I originally found this through Miri, in https://github.com/huonw/primal/issues/35, though the diagnostic is generated by rustc so I'm opening an issue here. I spent a while in the original example trying to figure out how a `*const u8` became a pointer to 3 bytes. Reading over the code that implements this diagnostic, it almost looks like some generic pointer out-of-bounds code was repurposed to provide a diagnostic for invalid offsets. I'd implement an improvement myself but I really can't figure out how to get the size of the pointee type.
Repository: TypeScript
Issue: navto search scope seems incorrect
Labels: Needs Investigation

There are several different ways to invoke the `navto`[`-full`] command:

1. Scope to a single file
2. Provide neither a file nor a project, as VS Code does for `Go to symbol in workspace...`
3. Provide a project, but not a file, as VS does for `Go to Symbol`
4. Provide only a file
5. Provide both a file and a project

(4) & (5) aren't that well understood, since neither of the primary consumers use this pattern and the behavior isn't documented.  In practice, the scope appears to be the projects including the given file and projects downstream from there.  Personally, I think we should ignore the file if the request isn't file-scoped and then fall back to either (2) or (3).

(3) appears to be scoped to a single project and not trigger project loading.  This is in line with VS's requirements, since VS will make a separate request for each project and duplicating downstream searches would be bad.  Unfortunately, it does mean that it will never trigger project loading, possibly resulting in confusingly incomplete results.

(2) appears intended to search all discoverable projects (it calls `combineProjectOutputFromEveryProject`) but, anecdotally, it does not.  As far as I've been able to understand `loadAncestorProjectTree`, it will consider all loaded projects and any projects downstream from any of those (even if they have to be loaded).

To take a concrete example, if you open `src/compiler/core.ts` in VS Code, the only loaded project will be `src/compiler`, though `src` and everything upstream from it will have been discovered.  If you invoke navto, projects like `src/tsc` and `src/services` that depend on `src/compiler` will be loaded, as will the solution project, `src`, but not unrelated projects referenced by the solution project:

- `src/cancellationToken`
- `src/debug`
- `src/instrumenter`
- `src/shims`
- `src/tsserverlibrary`
- `src/typescriptServices`
- `src/watchGuard`

This seems incorrect, though it's certainly possible that we made this compromise consciously to improve responsiveness by loading fewer projects.
Repository: rust
Issue: lint against unexpectedly late drop for temporaries in match scrutinee expressions
Labels: A-lints,A-destructors,E-mentor,T-compiler,E-help-wanted,E-medium,C-feature-request

This came up recently on twitter: https://twitter.com/fasterthanlime/status/1491803585385877519

Where @fasterthanlime ran into an unexpected difference in behavior that caused a deadlock.

The following code works fine:

```rust
use parking_lot::Mutex;

struct State {}

impl State {
    fn foo(&self) -> bool {
        true
    }

    fn bar(&self) {}
}

fn main() {
    let mutex = Mutex::new(State {});

    let val = mutex.lock().foo();
    match val {
        true => {
            mutex.lock().bar();
        }
        false => {}
    };
    println!("All done!");
}
```

But when the mutex locking expression is inlined into the match scrutinee expression it causes deadlock:

```rust
    match mutex.lock().foo() {
        true => {
            mutex.lock().bar();
        }
        false => {}
    };
```

Link to playgrounds

* Working: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=cb6f3a378805e4bbff601cee783af7f4
* Deadlock: https://play.rust-lang.org/?version=stable&mode=debug&edition=2021&gist=09d0aed9879678812aea960bd87dc263

This deadlock occurs because temporaries created in a match scrutinee automatically have their lifetime extended for the duration of the match expression. This is done to allow match arms to borrow from the scrutinee expressions, but this surprised many of the users in the above twitter thread because `foo` returns a bool, so there is no borrow taken by any of the match arms. My understanding is that the current behavior was chosen because otherwise drop timing of match temporaries would depend on whether or not you create any borrows.

This issue has generated some discussion around the possibility of changing drop rules in an edition to more aggressively drop temporaries. In this issue I would like to avoid a discussion of that size and instead propose that we introduce a lint that warns when one could encounter potentially surprising drop behaviour. @oli-obk has volunteered to mentor this issue. He suggested that we produce a warning when a temporary with a Drop impl which isn't borrowed by any match arms has its lifetime extended.


<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"PrestonFrom"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: terminal
Issue:  PowerShell argument `WindowStyle -Hidden` is not respected when the default terminal application is Windows Terminal
Labels: Issue-Feature,Product-Terminal,Area-DefApp

### Windows Terminal version

1.12.10393.0

### Windows build number

Microsoft Windows NT 10.0.22549.0

### Other Software

|Software | Version| 
|---| --- |
| PowerShell.exe | Multiple Versions | 
| pwsh.exe | Multiple Versions | 



### Steps to reproduce

1. Set Windows Terminal as the default terminal application:
. 
![image](https://user-images.githubusercontent.com/6994498/153515763-9362bbc3-2c4f-4a8e-8927-804ec3b7c7af.png)

2. Make sure to save changes to Windows Terminal Settings, and then using Windows Run, run `pwsh -WindowStyle Hidden -Command Sleep 10`:
![image](https://user-images.githubusercontent.com/6994498/153516667-363724b3-1400-47ae-aa39-333a74b287d0.png)


### Expected Behavior

A new PowerShell process launches (Windows Terminal), and it isn't visible. The window _may_ flash for a second. PowerShell window shouldn't be displayed when it's launched with `WindowStyle -Hidden`.

### Actual Behavior

A new PowerShell process launches (on Windows Terminal), and it is visible and remains visible (and waits) for 10 seconds.

![image](https://user-images.githubusercontent.com/6994498/153516951-e0feb19c-7bf3-4660-a1ba-9195a8034540.png)

Note: There is no repro for this issue with `Windows Console Host` as the default terminal application.
Repository: godot
Issue: `cubic_interpolate()` and `cubic_slerp()` cause overshoot
Labels: enhancement,topic:animation,topic:3d

### Godot version

4.0.dev, 3.4

### System information

Any

### Issue description

#40592 split and resend. Current `cubic_interpolate()` causes overshoot; we should consider employing modified-akima interpolation.

References of modified-akima:
- https://slpr.sakura.ne.jp/qp/akima-interpolation/
- https://jp.mathworks.com/help/matlab/ref/makima.html


### Steps to reproduce

https://user-images.githubusercontent.com/61938263/153521705-b5c1c87b-c852-4457-8db5-511b5be78942.mov

### Minimal reproduction project

[cubic_interpolation_test.zip](https://github.com/godotengine/godot/files/8045276/cubic_interpolation_test.zip)