sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: yt-dlp
Issue: `--compat-options format-sort` broken
Labels: bug,regression

### DO NOT REMOVE OR SKIP THE ISSUE TEMPLATE

- [X] I understand that I will be **blocked** if I *intentionally* remove or skip any mandatory\* field

### Checklist

- [X] I'm asking a question and **not** reporting a bug or requesting a feature
- [X] I've looked through the [README](https://github.com/yt-dlp/yt-dlp#readme)
- [X] I've verified that I'm running yt-dlp version **2023.03.04** ([update instructions](https://github.com/yt-dlp/yt-dlp#update)) or later (specify commit)
- [X] I've searched [known issues](https://github.com/yt-dlp/yt-dlp/issues/3766) and the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar questions **including closed ones**. DO NOT post duplicates
- [X] I've read the [guidelines for opening an issue](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#opening-an-issue)

### Please make sure the question is worded well enough to be understood

I was using "compat-options format-sort" this to download using the original way that youtube-dl would choose the highest bitrate version, and it was working good. But now, when I use that command, it downloads the exact same format and size as when I remove that command (same as yt-dlp). Why is it not working anymore?

### Provide verbose output that clearly demonstrates the problem

- [X] Run **your** yt-dlp command with **-vU** flag added (`yt-dlp -vU <your command line>`)
- [X] If using API, add `'verbose': True` to `YoutubeDL` params instead
- [X] Copy the WHOLE output (starting with `[debug] Command-line config`) and insert it below

### Complete Verbose Output

```shell
yt-dlp --newline -i --hls-prefer-native --cookies C:/Users/mike/Desktop/Tartube DLs/cookies.txt --windows-filenames --output C:/Users/mike/Desktop/Tartube DLs/%(title)s.%(ext)s https://www.youtube.com/watch?v=OwbKkAvL_wE&t=2s
[youtube] Extracting URL: https://www.youtube.com/watch?v=OwbKkAvL_wE&t=2s
[youtube] OwbKkAvL_wE: Downloading webpage
[youtube] OwbKkAvL_wE: Downloading android player API JSON
[youtube] OwbKkAvL_wE: Downloading MPD manifest
[info] OwbKkAvL_wE: Downloading 1 format(s): 244+251
[dashsegments] Total fragments: 858
[download] Destination: C:/Users/mike/Desktop/Tartube DLs/The Original Meet the Parents (Full Length Feature Film).f244.webm
[download] 100% of  167.67MiB in 00:02:41 at 1.04MiB/s
[dashsegments] Total fragments: 7
[download] Destination: C:/Users/mike/Desktop/Tartube DLs/The Original Meet the Parents (Full Length Feature Film).f251.webm
[download] 100% of   61.70MiB in 00:00:21 at 2.85MiB/s
[Merger] Merging formats into "C:/Users/mike/Desktop/Tartube DLs/The Original Meet the Parents (Full Length Feature Film).webm"
Deleting original file C:/Users/mike/Desktop/Tartube DLs/The Original Meet the Parents (Full Length Feature Film).f251.webm (pass -k to keep)
Deleting original file C:/Users/mike/Desktop/Tartube DLs/The Original Meet the Parents (Full Length Feature Film).f244.webm (pass -k to keep)
```
Repository: flutter
Issue: [camera_windows] preview aspect ratio doesn't match the camera/recorded video has black bars
Labels: platform-windows,p: camera,package,a: desktop,P2,team-windows,triaged-windows

HI,

When opening my USB webcam using the built-in Windows camera app I see a reasonably high quality 1920 x 1080 (16:9) image. 

When accessing the same webcam using the camera_windows plugin the preview reports a size of 320 x 240 (4:3). When recording a video the video has a resolution of 1920 x 1080 but there are black bars on the left and right sides of the video.

Thanks for your help!
Repository: rust
Issue: Tracking Issue for const `array::from_fn`
Labels: T-libs-api,C-tracking-issue

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(const_array_from_fn)]`

This is a tracking issue for using `array::from_fn` in const contexts

<!--
Include a short description of the feature.
-->

### Public API

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

```rust
// core::array

pub const fn from_fn<T, const N: usize, F>(cb: F) -> [T; N]
where
    F: ~const FnMut(usize) -> T + ~const Destruct,
    T: ~const Destruct;
   
pub const fn try_from_fn<R, const N: usize, F>(cb: F) -> ChangeOutputType<R, [R::Output; N]>
where
    F: ~const FnMut(usize) -> R + ~const Destruct,
    R: ~const Try,
    R::Residual: ~const Residual<[R::Output; N]>,
    R::Output: ~const Destruct;
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [ ] Implementation: #109122
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilzation PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- None yet.

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: rust
Issue: Tracking Issue for const `ptr::drop_in_place`
Labels: T-libs-api,C-tracking-issue

<!--
Thank you for creating a tracking issue!

Tracking issues are for tracking a feature from implementation to stabilization.

Make sure to include the relevant RFC for the feature if it has one.

If the new feature is small, it may be fine to skip the RFC process. In that
case, you can use use `issue = "none"` in your initial implementation PR. The
reviewer will ask you to open a tracking issue if they agree your feature can be
added without an RFC.
-->

Feature gate: `#![feature(const_drop_in_place)]`

This is a tracking issue for using `drop_in_place` in const contexts

<!--
Include a short description of the feature.
-->

### Public API

<!--
For most library features, it'd be useful to include a summarized version of the public API.
(E.g. just the public function signatures without their doc comments or implementation.)
-->

```rust
// core::ptr

pub const unsafe fn drop_in_place<T: ?Sized + ~const Destruct>(to_drop: *mut T);
```

### Steps / History

<!--
For larger features, more steps might be involved.
If the feature is changed later, please add those PRs here as well.
-->

- [ ] Implementation: #109122
- [ ] Final comment period (FCP)[^1]
- [ ] Stabilization PR

<!--
Once the feature has gone through a few release cycles and there are no
unresolved questions left, the feature might be ready for stabilization.

If this feature didn't go through the RFC process, a final comment period
(FCP) is always needed before stabilization. This works as follows:

A library API team member can kick off the stabilization process, at which point
the rfcbot will ask all the team members to verify they agree with
stabilization. Once enough members agree and there are no concerns, the final
comment period begins: this issue will be marked as such and will be listed
in the next This Week in Rust newsletter. If no blocking concerns are raised in
that period of 10 days, a stabilzation PR can be opened by anyone.
-->

### Unresolved Questions

<!--
Include any open questions that need to be answered before the feature can be
stabilised. If multiple (unrelated) big questions come up, it can be a good idea
to open a separate issue for each, to make it easier to keep track of the
discussions.

It's useful to link any relevant discussions and conclusions (whether on GitHub,
Zulip, or the internals forum) here.
-->

- Confirm that things such as `dyn Trait` works with this as well

[^1]: https://std-dev-guide.rust-lang.org/feature-lifecycle/stabilization.html
Repository: stable-diffusion-webui
Issue: [Feature Request]: add blip2 model to "Preprocess images".
Labels: enhancement,extension-request

### Is there an existing issue for this?

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

### What would your feature do ?

It will use blip2 models for text desc of images 
![222902203-a53ef1b7-d9c3-4445-a0fe-751d3624943f](https://user-images.githubusercontent.com/123314104/226162207-b3252d39-8cb2-4314-9112-e79def9c9929.jpeg)


### Proposed workflow

1. Go to Train
2. Press Preprocess images
3. Chose Use BLIP for caption.
4. Add here Use BLIP2 for caption.


### Additional information

_No response_
Repository: go
Issue: cmd/compile: implement more optimizations on loong64
Labels: Performance,NeedsFix,arch-loong64,compiler/runtime

This issue is mainly for tracking the implementation progress of various low-hanging fruits regarding `loong64` optimizations.

There are many missed optimization chances on `loong64`. A quick survey on SSA intrinsics uncovers:

* [ ] `runtime.publicationBarrier`
    - `dmb st` on `arm64`
    - `dbar 0` on LA64 v1.00
    - `dbar <TBD>` on next revision of LA64 (finer-grained barriers are to be supported)
* [x] `runtime.Bswap{32,64}`
    - `revb.{2w,d}` on LA64 v1.00: [CL 483357](https://go.dev/cl/483357)
* [ ] `runtime/internal/sys.Prefetch{,Streamed}`
    - `preld` on LA64 v1.00
* [x] `runtime/internal/atomic.{And,Or}`
    - `am{and,or}.d` on LA64 v1.00: [CL 482756](https://go.dev/cl/482756)
* [x] :exclamation: ~~`math.{Trunc,Ceil,Floor,RoundToEven}`~~ not possible with LA64 v1.00
    - LA64 v1.00 `frint.[sd]` is not orthogonal: no fixed rounding mode variants (unlike e.g. `ftintr{m,p,z,ne}`).
* [ ] :question: `math.Round`
    - `frint.[sd]` on LA64 v1.00 -- have to check if the rounding mode behavior is tolerable
* [ ] `math.Abs`
    - `fabs.[sd]` on LA64 v1.00
* [ ] `math.Copysign`
    - `fcopysign.[sd]` on LA64 v1.00
* [x] `math.FMA`
    - `f{,n}m{add,sub}.[sd]` on LA64 v1.00: [CL 483355](https://go.dev/cl/483355)
* [x] `math/bits.TrailingZeros{64,32}` (`ssa.OpCtz{64,32}`)
    - `ctz.[wd]` on LA64 v1.00: [CL 479498](https://go.dev/cl/479498)
* [x] `math/bits.Len{64,32,}` (`ssa.OpBitLen{64,32}`)
    - `clz.[wd]` on LA64 v1.00: [CL  483356](https://go.dev/cl/483356)
    - ~~significant performance regression across the board, needs investigation~~ confirmed to be micro-architecture quirk, alleviated somewhat by various alignment tricks
* [x] `math/bits.Reverse{64,32,8}` (`ssa.OpBitRev{64,32,8}`)
    - `bitrev.{d,w,4b}` on LA64 v1.00: [CL 483656](https://go.dev/cl/483656)

We may want to implement (and preferably benchmark) all of the above.

cc @golang/loong64
Repository: create-react-app
Issue: Add banner on plan for CRA to docs
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

There seems to still be confusion regarding the plan for CRA (for example: https://github.com/facebook/create-react-app/issues/13072), as CRA's readme and docs don't mention the plan Dan Abramov has recently discussed on Twitter, GitHub, and Reddit: 

> [Our current plan is to make it a launcher for the recommended solutions. See https://github.com/reactjs/reactjs.org/pull/5487#issuecomment-1409720741 for (a lot of) context.](https://www.reddit.com/r/reactjs/comments/11u1r3w/comment/jcmimez/?context=3)

Additionally, many beginners are trying to find best practices on search engines, and since "create a react app" looks very similar to "create react app", search engines are still listing these docs on the first page of results (some still have it as the first result).

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

I'd suggest a simple banner in the docs, similar to the previous BLM and current Ukraine banners, making it clear that CRA isn't currently recommended now and linking to the team's plan, for example:

> Create React App isn't recommended for new apps. [Installation](https://react.dev/learn/installation) [Plan for Create React App](https://github.com/reactjs/react.dev/pull/5487#issuecomment-1409720741)

### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

This may not be seen by all users, especially if they're using an older third party resource. If the `create-react-app` or `react-scripts` packages are not going to be used in the [plan for CRA](https://github.com/reactjs/react.dev/pull/5487#issuecomment-1409720741), I'd recommend deprecating them. Otherwise, it would probably be a good idea to add a similar message to the logs of the CLI

Additionally, it may help to add migration guides. [Vite](https://vitejs.dev/) is the most straightforward replacement for CRA currently. If a similar tooling setup to CRA is desired, I also have an open source [Vite + React + Testing template](https://github.com/nickmccurdy/vite-react-testing).
Repository: go
Issue: proposal: os/user: include shell in user lookup
Labels: Proposal

On unix systems, `user.Lookup` returns most passwd fields, but not shell:

https://github.com/golang/go/blob/20e9b7f1b53d49fd66e0344b1d0d42d3cf5e47b6/src/os/user/lookup_unix.go#L162-L168

It can be desired to look up a user's shell in some cases, and it should be a small non-intrusive change:

- Add a `Shell string` field to `user.User`.
- For the Cgo case, read `pw_shell` from the passwd struct
- For the non-Cgo case, read `parts[6]`
- Leave the field blank on Windows systems
Repository: PowerToys
Issue: 2 Shifts switchs CapsLock 
Labels: Idea-Enhancement,Product-Keyboard Shortcut Manager,Needs-Triage

### Description of the new feature / enhancement


PowerToys-KeyboardManager-RemapKey: (Left Shift + RightShift) -> CapsLock 

### Scenario when this would be used?

To switch caps lock, I want to press both shifts simultaneously. I used "power toy - keyboard manager - remap a key" to reassign these keys (CapsLock -> Esc, Alts -> Crtls, Wins -> Alts, Esc->CapsLock) for gvim text editor. Everything works fine except reaching for esc with my pinky finger to toggle caps lock is inconvenient. Pressing both shifts once should enable the upper layout and pressing again should disable it. However, keyboard manager only lets me add one key such as shift and not two shift keys together for escape.

### Supporting information

_No response_
Repository: vscode
Issue: French keyboard "backtick symbol" is converted to the "lower than sign" in the native menus
Labels: upstream,macos,keyboard-layout,upstream-issue-linked

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->
- VS Code Version: Version: 1.76.2 (Universal)
- OS Version: MacOS Ventura 13.2.1

Steps to Reproduce:

1. Download VSCode on a MacBook having an Apple Silicon chip with a French numerical keyboard configuration
2. Try to use the default shortcut to create a new terminal and you'll see that the "backtick symbol" is converted to the "lower than sign" key.

See by yourself, MacOS which determines the keyboard shortcut displays a different binding than VSCode does.
<img width="1121" alt="image" src="https://user-images.githubusercontent.com/35221325/226168223-dd956b8c-bf3e-4c2f-b076-d94a5d043a06.png">
Repository: godot
Issue: Godot 4 Could not load file or assembly Microsoft.AspNetCore
Labels: bug,topic:editor,topic:dotnet

### Godot version

4.0-stable

### System information

Windows 11

### Issue description

Hello!
I'm trying to use the AspNetCore API in a Godot C# script to make a gRPC server, but at runtime it throws an error:
`ERROR: 'System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.AspNetCore, Version=7.0.0.0, Culture=neutral, PublicKeyToken=adb9793829ddae60'. The system cannot find the file specified.'`

I have installed all required dependencies:
```
dotnet --list-runtimes
Microsoft.AspNetCore.App 7.0.4 [C:\Program Files\dotnet\shared\Microsoft.AspNetCore.App]
Microsoft.NETCore.App 7.0.4 [C:\Program Files\dotnet\shared\Microsoft.NETCore.App]
```

To enable AspNetCore, I followed steps from [docs](https://learn.microsoft.com/en-us/aspnet/core/fundamentals/target-aspnetcore?view=aspnetcore-7.0&tabs=visual-studio#use-the-aspnet-core-shared-framework).

### Steps to reproduce

VSCode: Set the `GODOT4` environment variable to the path to the godot executable, or replace it in the `launch.json` file with the path to the godot executable.
Select `Launch` as the debug configuration and run debugging.

### Minimal reproduction project

[godot_asp_net.zip](https://github.com/godotengine/godot/files/11010645/godot_asp_net.zip)
Repository: stable-diffusion-webui
Issue: [Feature Request]: Make Extra Networks ignore "empty" folders
Labels: enhancement

### Is there an existing issue for this?

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

### What would your feature do ?

I have a lot of models (same happens for LoRa, TI, etc) and am using <https://github.com/CurtisDS/sd-model-preview-xd/> to store multiple previews of them.
Consequently for each model I have one folder holding multiple pictures + 1 text file and nothing else. Which makes "Extra Networks" add a lot of empty folders on top of my checkpoint cards.
I'd like for Extra Networks to add a "Folder button" only if there's some actual model/LoRa/Ti in there. If not possible, an option to turn off those directory altogether :/ would be helpful too.
![image](https://user-images.githubusercontent.com/4246001/226169786-40c588a8-9703-4406-9060-7ee82455ce97.png)


### Proposed workflow

For solution 1 : nothing to do on the user end
For solution 2 : Settings->Extra Networks->Hide Folders : On/Off

### Additional information

_No response_
Repository: PowerToys
Issue: 希望能增加字典功能
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

在日常生活中，很多时候都会用到字典，希望能添加该功能，拥有基本的字典查询翻译功能

### Scenario when this would be used?

日常搜索

### Supporting information

_No response_
Repository: flutter
Issue: GoRouter ShellRoute wrong official example and transition bug
Labels: package,has reproducible steps,P2,p: go_router,found in release: 3.7,found in release: 3.9,team-go_router,triaged-go_router

Hi,

There is an en error on this official documentation (or maybe I am wrong): https://github.com/flutter/packages/blob/main/packages/go_router/example/lib/shell_route.dart

As you can see on the code, each Screen widget, starts with a "Scaffold". But they parent with BottomNavigation have also a Scaffold which duplicates the usage of Scaffold and in the widget tree we have 2 Scaffold.

On the flutter documentation we have this : https://api.flutter.dev/flutter/material/Scaffold-class.html#:~:text=It%20is%20typically,updates%20the%20AppBar

> It is typically not necessary to nest Scaffolds.

On my app, I wanted to use only 1 shared Scaffold, but it cause a bug during transition. To replicate it, you can use this code: https://github.com/flutter/packages/blob/main/packages/go_router/example/lib/shell_route.dart

And just change the ScreenB widget content to this (just removing the Scaffold parent):
```dart
/// The second screen in the bottom navigation bar.
class ScreenB extends StatelessWidget {
  /// Constructs a [ScreenB] widget.
  const ScreenB({super.key});

  @override
  Widget build(BuildContext context) {
    return Center(
      child: Column(
        mainAxisSize: MainAxisSize.min,
        children: <Widget>[
          const Text('Screen B'),
          TextButton(
            onPressed: () {
              GoRouter.of(context).go('/b/details');
            },
            child: const Text('View B details'),
          ),
        ],
      ),
    );
  }
}
```

Or see the real preview here: https://flutlab.io/editor/46151d54-95e1-49cf-9fe0-ad0afc469c76

Then, if you try to go from A Screen, to B Screen, you will the that there is a transition bug from the view A to B. Like this: (https://user-images.githubusercontent.com/13520683/226175787-7ccc910f-11b5-446c-a106-0f0ba1d79c22.webm) 
<video src="https://user-images.githubusercontent.com/13520683/226175787-7ccc910f-11b5-446c-a106-0f0ba1d79c22.webm" width="500" height="950">

As you can see, there is no problem to go From A to C, because the A and C have their own Scaffold so duplicated Scaffolds with BottomNavigationBar. But as I removed the Scaffold from the Screen B to keep only 1 scaffold, there is a transition bug from A to B, C to B etc. But no problem from B to A, or C.
Repository: pytorch
Issue: "Adaptive pool MPS: input sizes must be divisible by output sizes", I keep getting this error even when I try to adjust for size
Labels: module: crash,triaged,module: mps

### 🐛 Describe the bug

I am running a facet-pytorch library for facial recognition. I initialised the mtcnn class and passed on MPS as the device so I can run the program on that GPU for faster results. 

'''
device = torch.device("mps")
mtcnn1 = MTCNN(image_size=(160,160) device=device)
'''

The problem starts when I try to iterate though an image folder and pass it in the mtcnn i.e.
for imge, index in dataLoader:
    face, prob = mtcnn0(image, return_prob=True) 

it keeps coming up with this error:

RuntimeError: Adaptive pool MPS: input sizes must be divisible by output sizes

Can someone help please?

### Versions

wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py

cc @kulinseth @albanD @malfet @DenisVieriu97 @jhavukainen @razarmehr @abhudev