sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: mewatch unable to download video; Unable to download JSON metadata
Labels: broken-IE,patch-available

<!--

######################################################################
  WARNING!
  IGNORING THE FOLLOWING TEMPLATE WILL RESULT IN ISSUE CLOSED AS INCOMPLETE
######################################################################

-->


## Checklist

<!--
Carefully read and work through this check list in order to prevent the most common mistakes and misuse of youtube-dl:
- First of, make sure you are using the latest version of youtube-dl. Run `youtube-dl --version` and ensure your version is 2021.12.17. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that all URLs and arguments with special characters are properly quoted or escaped as explained in http://yt-dl.org/escape.
- Search the bugtracker for similar issues: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Read bugs section in FAQ: http://yt-dl.org/reporting
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a broken site support issue
- [x] I've verified that I'm running youtube-dl version **2021.12.17**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
- [x] I've searched the bugtracker for similar bug reports including closed ones
- [x] I've read bugs section in FAQ


## Verbose log

<!--
Provide the complete verbose output of youtube-dl that clearly demonstrates the problem.
Add the `-v` flag to your command line you run youtube-dl with (`youtube-dl -v <your command line>`), copy the WHOLE output and insert it below. It should look similar to this:
 [debug] System config: []
 [debug] User config: []
 [debug] Command-line args: [u'-v', u'http://www.youtube.com/watch?v=BaW_jenozKcj']
 [debug] Encodings: locale cp1251, fs mbcs, out cp866, pref cp1251
 [debug] youtube-dl version 2021.12.17
 [debug] Python version 2.7.11 - Windows-2003Server-5.2.3790-SP2
 [debug] exe versions: ffmpeg N-75573-g1d0487f, ffprobe N-75573-g1d0487f, rtmpdump 2.4
 [debug] Proxy map: {}
 <more lines>
-->

```
PASTE VERBOSE LOG HERE
```


## Description

<!--
Provide an explanation of your issue in an arbitrary form. Please make sure the description is worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient. Provide any additional information, suggested solution and as much context and examples as possible.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

WRITE DESCRIPTION HERE

Hi, I am unable to download any video from mewatch recently, i have been receiving this error while trying to download the videos.
![image](https://user-images.githubusercontent.com/37041596/232090350-8a967c2a-dd86-45e8-b97f-4d7b294554e0.png)
Repository: PowerToys
Issue: Windows closes automatically after running Shell commands
Labels: Idea-Enhancement,Needs-Triage

### Microsoft PowerToys version

0.69.1

### Installation method

Microsoft Store

### Running as admin

Yes

### Area(s) with issue?

PowerToys Run

### Steps to reproduce

When I try to run a command with Run like "ping" or "tracert" it opens a new window, do the command but the windows closes before displaying the result.

### ✔️ Expected Behavior

That terminal windows should remain open.

### ❌ Actual Behavior

It closes before displaying the result of the command. 

### Other Software

_No response_
Repository: flutter
Issue: TabBar add new 'onTabChanging' and 'onTabChanged' events
Labels: c: new feature,framework,f: material design,c: proposal,P3,team-design,triaged-design

**Use case**

I am trying to build a complex form in Flutter where a large number of input controls are spread across multiple tab views.
Currently, there is no way to know when the current tab view is changing or has changed.
This gap blocks any attempt to validate the data input on the current view 

**Proposal**

Add two new events to the 'TabBar' widget...

a). on TabChanging
This event would be called as a preliminary step to a request to change the current tab.   
It would allow logic to be inserted to check on data from controls in the old tab.

```
onTabChanging:  (int oldTabIndex, int newTabIndex) {
  // a return value of 'true' would enable the tab change,  
  // a return value of 'false' would intercept and block the tab change
}

```
b). onTabChanged
This event would be called once the current tab had been changed to a new index

```
onTabChanged: (int oldTabIndex, int newTabIndex) {
}
```
Repository: neovim
Issue: detach the current TUI (nvim continues headlessly)
Labels: enhancement,ui,tui,channels-rpc,server,ui-extensibility,remote

### Problem

When connected to a remote ui executing `:q` will close the remote server, I guess this makes sense in the way that the command is being run by the backend and not the UI, but it's not intuitive or desired, I wish to quit without killing the backend

### Steps to reproduce

nvim --listen 127.0.0.1:8888 --headless
nvim --server 127.0.0.1:8888 --remote-ui
:q

### Expected behavior

The UI should disconnect from the server but not to kill it

### Neovim version (nvim -v)

0.10.x

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

no

### Operating system/version

macOS 13.2.1

### Terminal name/version

iTerm

### $TERM environment variable

xterm-256color

### Installation

homebrew
Repository: vscode
Issue: Deleting a Cloud Change sometimes doesn't remove Tree Item completely and keeps around a GUID
Labels: bug,cloud-changes

Title says it all... I had a few Cloud Changes and was deleting them one-by-one (without realizing the Delete All in the overflow)

![image](https://user-images.githubusercontent.com/2644648/232114591-84587ff5-a4df-4946-a280-0f71fa42cbfe.png)

It's usually like every other delete does this.
Repository: flutter
Issue: Consider making MediaQueryData track whether the device is unfolding or not.
Labels: platform-android,framework,P3,team-android,triaged-android

A customer is working for an app on an foldable device. This device letterboxes your app if you lock the orientation and it is unfolded.

They want to know whether the device is unfolding or not.

The `MediaQueryData.displayFeatures` gives you a snapshot-right-now of what the device is reporting, but testing is revealing that this is not always super reliable for the customer's use case.

I'm not really sure if this is a bug in the device, the Android embedding, or the Framework, but it seems like the framework could track things here. The following code seems to work more reliably to track whether the device is unfolding:

```dart
class FoldObserver extends WidgetsBindingObserver {
  bool unfolding = false;

  @override
  void didChangeMetrics() {
    super.didChangeMetrics();
    final view = ui.PlatformDispatcher.instance.implicitView!;
    final logicalSize = view.physicalSize / view.devicePixelRatio;

    // Make sure app doesn't get letterboxed.
    if (!unfolding) {
      unfolding = view.displayFeatures.any((ui.DisplayFeature feature) =>
          feature.state == ui.DisplayFeatureState.postureHalfOpened);
    } else {
      unfolding = !view.displayFeatures.any((ui.DisplayFeature feature) =>
          feature.state == ui.DisplayFeatureState.postureFlat);
    }

    if (unfolding || logicalSize.shortestSide >= 600) {
      SystemChrome.setPreferredOrientations([]);
    } else if (logicalSize.shortestSide < 600) {
      SystemChrome.setPreferredOrientations([DeviceOrientation.portraitUp]);
    }
  }
}
```

The _real_ fix for all of this is to get the physical screen size (https://github.com/flutter/flutter/issues/123307), but we don't support that yet and it will take a bit of work to do it in a cross platform manner.

I think the framework could consider tracking this state on the MediaQueryData.

@goderbauer @reidbaker fyi.
@TytaniumDev fyi
Repository: pytorch
Issue: Add Debug builds for python with pydebug
Labels: triaged,module: devx

Requested by @albanD:

## The Ask
We need to very seriously consider adding a pydebug CI build. We have major bugs like https://github.com/pytorch/pytorch/pull/91684#issuecomment-1504062950 that keep going unoticed. Dynamo is especially at risk and the cornerstone of PT2.

## pydebug
pydebug is a version of CPython with internal asserts basically. We rely on a lot of low level details in CPython. So we break these asserts regularly for very various reasons


## Installation
More details: https://devguide.python.org/getting-started/setup-building/#unix

Depending on the environment, maybe you will have a package for it. Otherwise you might need to build CPython from source (which we already do anyways) with an extra flag.

## Jobs added
Re the config that should be built, any one config would be file. `linux cpu-only` may be best since it's the cheapest

cc @kit1980 @huydhn @clee2000
Repository: rust
Issue: Rustdoc --show-coverage is wrong for reexported items
Labels: T-rustdoc,A-doc-coverage

**a/src/lib.rs**
```rust
pub use b::*;
```

**b/src/lib.rs**

```
/// Documented with example
///
/// ```
/// // The example
/// ```
pub struct B1;
/// Documented, no example
pub struct B2;
// Undocumented
pub struct B3;
```

In `b` 

```
b$ cargo +nightly rustdoc -- -Z unstable-options --show-coverage
 Documenting b v0.1.0 (/home/gh-aDotInTheVoid/tmp/b)
+-------------------------------------+------------+------------+------------+------------+
| File                                | Documented | Percentage |   Examples | Percentage |
+-------------------------------------+------------+------------+------------+------------+
| src/lib.rs                          |          2 |      50.0% |          1 |      25.0% |
+-------------------------------------+------------+------------+------------+------------+
| Total                               |          2 |      50.0% |          1 |      25.0% |
+-------------------------------------+------------+------------+------------+------------+
    Finished dev [unoptimized + debuginfo] target(s) in 0.32s
```

But In `a`:

```
a$ cargo +nightly rustdoc -- -Z unstable-options --show-coverage
 Documenting a v0.1.0 (/home/gh-aDotInTheVoid/tmp/a)
+-------------------------------------+------------+------------+------------+------------+
| File                                | Documented | Percentage |   Examples | Percentage |
+-------------------------------------+------------+------------+------------+------------+
| src/lib.rs                          |          0 |       0.0% |          0 |       0.0% |
+-------------------------------------+------------+------------+------------+------------+
| Total                               |          0 |       0.0% |          0 |       0.0% |
+-------------------------------------+------------+------------+------------+------------+
    Finished dev [unoptimized + debuginfo] target(s) in 0.11s
```

These outputs should be the same.

When writing tests for this, also add one with `--output-format json`, as that flag is overloaded between this and the json backend, and the json backend interacts in funny ways with inlining.

rustdoc 1.70.0-nightly (a41fc00ea 2023-04-13)
binary: rustdoc
commit-hash: unknown
commit-date: unknown
host: aarch64-unknown-linux-gnu
release: 1.70.0-nightly
LLVM version: 16.0.2
Repository: flutter
Issue: [flutter_tools] investigate whether tool should order Android Studio installations by dirname
Labels: tool,P3,team-tool,triaged-tool

If a flutter user has multiple Android Studio installations on their computer, we determine which is the "newest". The first way we order these is lexicographically comparing the directory names. This seems the wrong approach.

See discussion in https://github.com/flutter/flutter/pull/124771 for more context.
Repository: flutter
Issue: BottomNavigationBar -> NavigationBar needs migration guide and docs
Labels: framework,f: material design,c: API break,d: api docs,P2,team-design,triaged-design

Follow up to https://github.com/flutter/flutter/issues/88888

This is a rare and unfortunate case where we have created a new widget to replace an old one. This type of migration is most painful for developers, so we should provide better help.

Dart fix is not capable of helping here.

BottomNavigationBar is styled for M2 spec.
NavigationBar is style for M3 and the intended replacement for BottomNavigationBar.

To resolve this issue we should do these things:

- [ ] Document on useMaterial3 that it does not apply to BottomNavigationBar
- [x] Document on BottomNavigationBar that NavigationBar is the M3 counterpart and replacement.
  - There is a brief mention under `See also`, but there should be more. 
- [x] Create a migration guide for https://docs.flutter.dev/release/breaking-changes
- [x] Send a message to flutter-announce mentioning this and including a link to the migration guide
- [ ] (Eventually) deprecate BottomNavigationBar
  - This is not clear yet, are we going to maintain M2 and M3 spec after useMaterial3 is on by default?
Repository: godot
Issue: Inspector not working for read-only/write-only properties
Labels: bug,discussion,topic:gdscript,topic:editor

### Godot version

4.0-stable

### System information

Windows 10

### Issue description

From GDExtension, it's possible to register properties without either a setter or a getter (by providing a null pointer to `classdb_register_extension_class_property` arguments).

These are **read-only** and **write-only** properties, respectively.

---

## GDScript behavior

When trying to write read-only properties in GDScript, this error occurs:

![grafik](https://user-images.githubusercontent.com/708488/232136006-f7a45826-120b-45a2-8d7d-d70a1c8cdbae.png)

When reading a write-only property via `self.property`, `<null>` is returned. Possibly not the most intuitive; I'd also expect an error here. (I'm aware that write-only is rare, but if it's supported, then I'd consider this a bug).

---

## Inspector UI

In the editor, properties that are either read- or write-only have a very weird UI.

I try to move to the beginning of the text field, and then continuously type the character "x".
The result can be seen in the following videos:


Read-only:

https://user-images.githubusercontent.com/708488/232139322-02294868-ba2d-4fab-a06d-e5b98737f040.mp4

<br>

Write-only:
(here, I hooked the setter to a function that prints the passed value, which you see in the output)

https://user-images.githubusercontent.com/708488/232139348-0007b479-2c41-4231-b1a8-e4c7cabcaa87.mp4

<br>

I would expect the following:
1. UI: Read-only properties have a disabled text field ([`TextEdit.editable == false`](https://docs.godotengine.org/en/stable/classes/class_textedit.html#class-textedit-property-editable))
2. UI: Write-only properties may not display their current value, but at least let you complete an input before pressing enter.
3. GDScript: Reading write-only properties causes an error, similar to the one when writing read-only ones.
   * This one is less important, and if it conflicts with (2), then we should probably forget about it.

### Steps to reproduce

Register only getter or setter, then see videos above.

### Minimal reproduction project

N/A
Repository: flutter
Issue: Document the use of dimensions in .ci.yaml
Labels: team-infra,P2,triaged-infra

The use of dimensions on .ci yaml file has been implemented and validated, however the documentation has not been updated. This is a tracker bug to ensure a dimensions section is added to the .ci.yaml docs.
Repository: rust
Issue: `dead_code`: Inherent associated types are unconditionally considered dead
Labels: A-lints,C-bug,requires-nightly,F-inherent_associated_types,L-dead_code

On nightly, the following code triggers `dead_code` even though it should not.

```rust
#![feature(inherent_associated_types)]
#![allow(incomplete_features)]

fn main() {
    let _: Struct::Item = ();
}

struct Struct;
impl Struct { type Item = (); }
```

```
warning: associated type `Item` is never used
 --> min.rs:9:20
  |
9 | impl Struct { type Item = (); }
  | -----------        ^^^^
  | |
  | associated type in this implementation
  |
  = note: `#[warn(dead_code)]` on by default

warning: 1 warning emitted
```

Actually until recently, `dead_code` was never triggered at all for inherent associated types.
PR #110277 was just merged which started visiting more associated items exposing this bug.
The `dead_code` pass never considers IATs as *live symbols* (`live_symbols`) even in cases where they should be.

This feels like a regression but technically speaking it is not:
We switched from one extreme to the other. Thus not marking as such.

@rustbot label A-lint F-inherent_associated_types requires-nightly

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

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

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: PowerToys
Issue: PowerRename - Add ability to save queries and/or execute macros
Labels: Idea-Enhancement,Product-PowerRename,Issue-Feature

### Description of the new feature / enhancement

Hello! I've been a pretty frequent user of PowerRename and think it would be useful to have the ability to save queries and possibly even stage macros. The current history function is useable but it only applies to one box at a time and is a little inconvenient if you're switching between queries and folders often.

The macro feature would enable you to run multiple queries in sequence, which is often times more convenient than trying to format a single regex to match your desired result.  The "Renamed" column would always show the final result of a macro, rather than just one of the steps.

I was contemplating opening a branch for this so just checking this isn't already something being worked on.

### Scenario when this would be used?

This would be used in potentially all renaming situations. Say you want to change a date format and also move that date to the beginning of a file. Rather than writing a single wordy query, you can build discrete queries that may be reused and stage a macro if they're frequently used in the same sequence.

### Supporting information

_No response_
Repository: flutter
Issue: Engine android CI should verify VisibleForTests field are not used
Labels: team,platform-android,engine,P2,team-android,triaged-android

We had to send a revert in https://github.com/flutter/engine/pull/41211 as this failed analysis checks on Google Testing, but not the LUCI checks.

```
shell/platform/android/io/flutter/plugin/editing/TextInputPlugin.java:239: Error: This method should only be accessed from tests or within private scope [VisibleForTests]
      imeSyncCallback.remove();
```

My expectation is analysis checks like this should be caught in presubmit.
Repository: flutter
Issue: Flutter Framework size regression
Labels: c: regression,engine,platform-mac,a: desktop,P2,team-macos,triaged-macos

It appears a recent roll of the framework caused a size regression, about 500kb in flutter_framework_uncompressed_bytes in hello_world_macos__compile

Skia perf link:
https://flutter-flutter-perf.skia.org/e/?begin=1681270451&end=1681500982&keys=X4129c1b014a53ca2bc7747c174d61ea5&requestType=0&selected=commit%3D34371%26name%3D%252Carch%253Dintel%252Cbranch%253Dmaster%252Cconfig%253Ddefault%252Cdevice_type%253Dnone%252Cdevice_version%253Dnone%252Chost_type%253Dmac%252Csub_result%253Dflutter_framework_uncompressed_bytes%252Ctest%253Dhello_world_macos__compile%252C&xbaroffset=34370

Seems to have started with this engine roll: https://github.com/flutter/flutter/pull/124841
Repository: flutter
Issue: Add more info and a schema definition to the ci.yaml readme file for better self service for developers
Labels: team-infra,P3,c: tech-debt,triaged-infra

One of the pain points for developers is finding out which fields go where in the ci.yaml definitions. We should add some more information about the schema of the file and how it relates to the builds so developers can help themselves rather than going through infra when they have questions.
Repository: godot
Issue: When all selected node are descendants of one of them PopupMenu act as if one node is selected
Labels: discussion,topic:editor

### Godot version

4.1.dev (afca0b8fdd)

### System information

MacOS 13.3 M1 Pro

### Issue description

When selecting multiple nodes and one of them is the ancestors of all the other, the right click popup will show things that are normally shown only when one node is selected (Add child node, instantiate child scene, make scene root) and missing multi select ones (Batch Edit). 
I think this behaviour is here because we are selecting a branch and branch specific option (expand/collapse branch, save branch as scene) needs to be there.


### Steps to reproduce

1. first reproduce the following tree or open the minimal reproduction project
<img width="235" alt="Capture d’écran 2023-04-14 à 23 09 47" src="https://user-images.githubusercontent.com/66184050/232155382-da3f9e22-26fb-4e10-bdcb-07cb60c25ea1.png">
2. Select `Child2` and `GrandChild`. Then right click you should see these options 
<img width="369" alt="Capture d’écran 2023-04-14 à 18 16 36" src="https://user-images.githubusercontent.com/66184050/232155532-0208094e-0908-4e23-82e7-43d37a6b7bc9.png">
3. to see normal behaviour of multi select add `Child` to the selection and then right click the selection you should see these options (the right popup should be a mix of the current one and this one)
<img width="375" alt="Capture d’écran 2023-04-14 à 18 16 44" src="https://user-images.githubusercontent.com/66184050/232155764-1b5472be-ada2-46bc-b5d8-da65901bb49a.png">


### Minimal reproduction project
[test.zip](https://github.com/godotengine/godot/files/11237384/test.zip)
Repository: rust
Issue: Tracking issue for incorrect lifetime bound errors in async
Labels: T-compiler,A-coroutines,A-async-await,AsyncAwait-Triaged,WG-async,T-types

```[tasklist]
### Reported issues
- [ ] #71723
- [ ] #79648
- [ ] #82921
- [ ] #90696
- [ ] #64552
- [ ] #87425
- [ ] #92415
- [ ] #92096
- [ ] #102211
- [ ] #60658
- [ ] #64650
- [ ] #71671
- [ ] #110339
- [ ] #104382
- [ ] #111105
- [ ] https://github.com/rust-lang/rust/issues/114046
- [ ] https://github.com/rust-lang/rust/issues/124757
- [ ] https://github.com/rust-lang/rust/issues/126551
- [ ] https://github.com/rust-lang/rust/issues/126550
- [ ] https://github.com/rust-lang/rust/issues/89976
- [ ] https://github.com/rust-lang/rust/issues/126044
- [ ] https://github.com/rust-lang/rust/issues/126350
- [ ] https://github.com/rust-lang/rust/issues/114177
- [ ] https://github.com/rust-lang/rust/issues/130113
```

## Cause

We erase lifetime relations of types inside generators, making it impossible in some cases to prove bounds or normalize associated types.

See https://github.com/rust-lang/rust/issues/64552#issuecomment-533267241 for a more detailed explanation.

## Implementation history

- [x] #92449

## Notes

Please keep discussion in this thread at a "meta-level" and open new issues for code that does not compile.

These might not all have the same cause, though it seems plausible that they do. My primary motivation is to try to group all the related issues together so they're easier to keep track of. If we can split them into sub-groups, all the better.

Many of the issues in this list are cribbed from #92449, thanks to @compiler-errors for coming up with that list.