sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: terminal
Issue: [Settings>Actions] : Focus is not visible properly on 'Shortcut' edit field.
Labels: Issue-Docs,Area-Accessibility,Product-Terminal,Priority-3,HCL-E+D,A11yWCAG,HCL-WindowsTerminal,A11yCO,A11ySev3

### Windows Terminal version

1.12.3472.0

### Windows build number

22509.1011

### Other Software

**Test Environment: **
OS: Windows 11 Version Dev (OS Build 22509.1011)
App: Windows Terminal Preview
Screen Reader: Narrator

### Steps to reproduce

**Repro Steps: **

1.Open Windows Terminal.
2.Open Settings page using 'Ctr+,'
3.Navigate to 'actions' list-item via 'Up/down' arrow keys & press enter.
4.Now Navigate to Actions present in the right pane via down arrow key.
5.Navigate to 'Edit' button present for any 'Action' via tab key & press enter.
6.A pop-up will gets open & navigate to 'Shortcut' edit field via tab key.
7.Verify whether focus is visible properly on 'Shortcut' edit field or not.

**User Experience: **
Users who rely on keyboard will get impacted here & may fail to track the currently focused element, if focus is not visible properly on 'Shortcut' edit field.

**Guideline Reference: **
https://www.w3.org/TR/WCAG21/#focus-visible

Attachments:
[Focus is not visible properly on shortcut edit field.zip](https://github.com/microsoft/terminal/files/7726819/Focus.is.not.visible.properly.on.shortcut.listeners.edit.field.zip)


### Expected Behavior

Focus should be visible properly on 'Shortcut' edit field. Focus indicator should be provided as outline for better visibility.

### Actual Behavior

'Inline' focus is provided for 'Shortcut' edit field, due to this user is unable to recognize that edit field is focused when focus is on 'Shortcut' edit field.
Repository: godot
Issue: Meshes saved in binary format do not persist materials
Labels: topic:core,needs testing

### Godot version

3.4 stable

### System information

Ubuntu 21.10 

### Issue description

- In one project I am saving a mesh which has a material with texture using `ResourceSaver` to import in another project
- I am then dragging the obtained `.tscn` file into the editor in another blank project.
  - When using `.tscn` format everything works as expected - I get my mesh with it's materials and textures exactly imported in a blank project
  - but when I wan't to save some space using the binary format `.scn` the textures do not transfer to a blank project with import
  - `ResourceLoader` works with the same quirk - only mesh loads, without material

### Steps to reproduce

Works:
```
var scn = PackedScene.new()
scn.pack($Mesh24212)
ResourceSaver.save("/home/user/Downloads/mesh-comp.tscn", scn, ResourceSaver.FLAG_BUNDLE_RESOURCES)
```

Does not work (only mesh gets loaded, the material is not loaded)
```
var scn = PackedScene.new()
scn.pack($Mesh24212)
ResourceSaver.save("/home/user/Downloads/mesh-comp.scn", scn, ResourceSaver.FLAG_BUNDLE_RESOURCES)
```

Note the only difference is using text/binary format `.tscn/.scn`

### Minimal reproduction project

Attached
[Issue55989.zip](https://github.com/godotengine/godot/files/8381540/Issue55989.zip)

https://user-images.githubusercontent.com/394662/160863632-9b7e2075-bd86-4e19-bbad-2e62ab088541.mp4
Repository: rust
Issue: If-else value followed by operator parsing error provided only for some operators
Labels: A-frontend,A-diagnostics,A-parser,T-compiler,D-terse

When an if-else block produces a value and this is followed by an operator and this all happens inside a block, this is apparently a parsing error.

When the operator is `+`, the parsing error is pointed out. When the operator is `&`, the parsing error is not pointed out.

Please provide the parsing error for all operators.

Given the following code: https://play.rust-lang.org/?edition=2021&gist=55a7b19b44fc6010a33338774bef3b11

```rust
fn main() {
    { if true { 0 } else { 0 } & 0 };
}
```

The current output is:

```
   Compiling playground v0.0.1 (/playground)
error[E0308]: mismatched types
 --> src/main.rs:2:17
  |
2 |     { if true { 0 } else { 0 } & 0 };
  |       ----------^-------------
  |       |         |
  |       |         expected `()`, found integer
  |       expected this to be `()`

error[E0308]: mismatched types
 --> src/main.rs:2:28
  |
2 |     { if true { 0 } else { 0 } & 0 };
  |       ---------------------^--
  |       |                    |
  |       |                    expected `()`, found integer
  |       expected this to be `()`

For more information about this error, try `rustc --explain E0308`.
error: could not compile `playground` due to 2 previous errors
```

Ideally the output should look like the output when `+` is used instead of `&`:

```
   Compiling playground v0.0.1 (/playground)
error: leading `+` is not supported
 --> src/main.rs:2:32
  |
2 |     { if true { 0 } else { 0 } + 0 };
  |                                ^ unexpected `+`
  |
help: parentheses are required to parse this as an expression
  |
2 |     { (if true { 0 } else { 0 }) + 0 };
  |       +                        +

error[E0308]: mismatched types
 --> src/main.rs:2:17
  |
2 |     { if true { 0 } else { 0 } + 0 };
  |       ----------^-------------
  |       |         |
  |       |         expected `()`, found integer
  |       expected this to be `()`

error[E0308]: mismatched types
 --> src/main.rs:2:28
  |
2 |     { if true { 0 } else { 0 } + 0 };
  |       ---------------------^--
  |       |                    |
  |       |                    expected `()`, found integer
  |       expected this to be `()`

For more information about this error, try `rustc --explain E0308`.
error: could not compile `playground` due to 3 previous errors
```

Note the added help line: `parentheses are required to parse this as an expression`

This explanation should be included for all operators.

Nightly has the same problem.

**Stable**: rustc 1.57.0 (f1edd0429 2021-11-29)                                       
**Nightly**: rustc 1.59.0-nightly (c5ecc1570 2021-12-15) (from rustc 1.59.0-nightly (404c8471a 2021-12-14))
Repository: pytorch
Issue: Error in `torch.cdist` documentation
Labels: module: docs,triaged,module: distance functions

### 📚 The doc issue

The documentation says that `torch.cdist` == `scipy.spatial.distance.cdist(input,’minkowski’, p=p)` when `p` in (0, inf). However, `scipy.spatial.distance.cdist` with ’minkowski’ only supports `p >= 1`. So this sentence is an error.

```python
import torch
x= torch.rand(torch.Size([1, 2]))
y = torch.rand(torch.Size([1, 2]))
p = 0.5
res1 = torch.cdist(x, y, p=p)
import scipy.spatial
res2 = scipy.spatial.distance.cdist(x, y, 'minkowski', p=p)
# ValueError: p must be at least 1
```

### Suggest a potential alternative/fix

It should be corrected to `torch.cdist` == `scipy.spatial.distance.cdist(input,’minkowski’, p=p)` when `p` in [1, inf)

cc @brianjo @mruberry
Repository: godot
Issue: RichTextLabel alignment not working properly
Labels: bug,topic:gui

### Godot version

v3.5.beta.custom_build.102f102f7

### System information

Arch Linux 5.15.7-zen1-1-zen, GLES3, NVIDIA GeForce GTX 1660 SUPER/PCIe/SSE2

### Issue description

Text rendered in a RichTextLabel using BBCode shows alignment issues, or to put it simply, an extra space, when a newline is forced to make the text fit inside the node's size right after a word enclosed in a tag like `[i]` or `[b]`. This does not occur when the new line starts after an unformatted word, and the user would expect this not to happen regardless.

https://user-images.githubusercontent.com/13611953/146369707-1399b4b6-5d6e-4d9c-aada-2d31d651f44f.mp4




### Steps to reproduce

Use a RichTextLabel with BBCode enabled, write some text using BBCode tags.

### Minimal reproduction project

[RTLabel_BBCodeAlign_Issue.zip](https://github.com/godotengine/godot/files/7727132/RTLabel_BBCodeAlign_Issue.zip)
Repository: flutter
Issue: `RenderFlex` computes `intrinsic sizing` and `dryLayout` incorrectly in some cases. 
Labels: framework,f: material design,has reproducible steps,found in release: 2.8,found in release: 2.9,team-design,triaged-design

As we know,`RenderBox` objects must implement intrinsic sizing and `computeDryLayout`.In some cases a `RenderBox` can't calculate `computeDryLayout` or intrinsic sizing without doing a full layout.For example, the size may depend on the baseline of a child (which is not available without doing a full layout).

`RenderFlex` uses `crossAxisAlignment` to place its children along the cross axis.If `crossAxisAlignment` be `CrossAxisAlignment.baseline`,then `RenderFlex` places its children along the cross axis such that their baselines match.But in this case If the main axis is vertical, then this value is treated like `CrossAxisAlignment.start`.

Therefore if `crossAxisAlignment` be `CrossAxisAlignment.baseline` and main axis be horizontal,then  `RenderFlex` can't calculate `computeDryLayout` or intrinsic sizing because that needs a full layout. But if `crossAxisAlignment` be `CrossAxisAlignment.baseline` and main axis be vertical, then `RenderFlex` can calculate `computeDryLayout` or intrinsic sizing.

But `RenderFlex` just checks `crossAxisAlignment` for this purpose and doesn't check main axis.

<details><summary>The source code of RenderFlex:</summary>

```dart
bool get _canComputeIntrinsics => crossAxisAlignment != CrossAxisAlignment.baseline;

 @override
  Size computeDryLayout(BoxConstraints constraints) {
    if (!_canComputeIntrinsics) {
      assert(debugCannotComputeDryLayout(
        reason: 'Dry layout cannot be computed for CrossAxisAlignment.baseline, which requires a full layout.',
      ));
      return Size.zero;
    }
    FlutterError? constraintsError;
    assert(() {
      constraintsError = _debugCheckConstraints(
        constraints: constraints,
        reportParentConstraints: false,
      );
      return true;
    }());
    if (constraintsError != null) {
      assert(debugCannotComputeDryLayout(error: constraintsError));
      return Size.zero;
    }

    final _LayoutSizes sizes = _computeSizes(
      layoutChild: ChildLayoutHelper.dryLayoutChild,
      constraints: constraints,
    );

    switch (_direction) {
      case Axis.horizontal:
        return constraints.constrain(Size(sizes.mainSize, sizes.crossSize));
      case Axis.vertical:
        return constraints.constrain(Size(sizes.crossSize, sizes.mainSize));
    }
  }
```
</details>

For a more accurate result we can add a few more checks.
Repository: yt-dlp
Issue: [BRIGHTEON] Please add support for downloading channels as playlists
Labels: site-request

### Checklist

- [X] I'm reporting a site feature request
- [X] I've verified that I'm running yt-dlp version **2021.12.01**. ([update instructions](https://github.com/yt-dlp/yt-dlp#update))
- [X] I've checked that all provided URLs are alive and playable in a browser
- [X] I've searched the [bugtracker](https://github.com/yt-dlp/yt-dlp/issues?q=) for similar issues 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)
- [X] I've read about [sharing account credentials](https://github.com/yt-dlp/yt-dlp/blob/master/CONTRIBUTING.md#are-you-willing-to-share-account-details-if-needed) and I'm willing to share it if required

### Region

Norway

### Example URLs

https://www.brighteon.com/channels/hrreport

### Description

```
$ yt-dlp --dateafter 20211020 --datebefore 20211031 -f best https://www.brighteon.com/channels/hrreport
[generic] hrreport: Requesting header
WARNING: [generic] Falling back on generic information extractor.
[generic] hrreport: Downloading webpage
[generic] hrreport: Extracting information
ERROR: Unsupported URL: https://www.brighteon.com/channels/hrreport

```
Repository: create-react-app
Issue: UnhandledPromiseRejectionWarning: TypeError: match.loader.options.plugins is not a function
Labels: issue: question

### package.json
`{

    "name": "client",
    "version": "0.1.0",
    "private": true,
    "dependencies": {
        "@craco/craco": "^6.4.3",
        "@emotion/react": "^11.7.0",
        "@emotion/styled": "^11.6.0",
        "@mui/icons-material": "^5.2.0",
        "@mui/material": "^5.2.1",
        "@testing-library/jest-dom": "^5.15.1",
        "@testing-library/react": "^11.2.7",
        "@testing-library/user-event": "^12.8.3",
        "axios": "^0.24.0",
        "dotenv": "^10.0.0",
        "eslint": "^7.32.0",
        "firebase": "^9.5.0",
        "history": "^5.1.0",
        "moment": "^2.29.1",
        "react": "^17.0.2",
        "react-dom": "^17.0.2",
        "react-router": "^6.0.2",
        "react-router-dom": "^6.0.2",
        "react-scripts": "^5.0.0",
        "react-toastify": "^8.1.0",
        "stream-chat": "^4.4.3",
        "stream-chat-react": "^6.12.0",
        "typescript": "^4.5.4",
        "universal-cookie": "^4.0.4",
        "web-vitals": "^1.1.2"
    },
    "scripts": {
        "start": "craco start",
        "build": "craco build",
        "test": "craco test",
        "eject": "react-scripts eject",
        "lint": "eslint ./src --ext .js",
        "lint:fix": "npm run lint -- --fix",
        "prettier:format": "prettier --write \"**/*.+(js|jsx|ts|tsx|json|scss|md)\"",
        "pre:commit": "npm run lint && npm run prettier:format"
    },
    "eslintConfig": {
        "extends": [
            "react-app",
            "react-app/jest"
        ]
    },
    "browserslist": {
        "production": [
            ">0.2%",
            "not dead",
            "not op_mini all"
        ],
        "development": [
            "last 1 chrome version",
            "last 1 firefox version",
            "last 1 safari version"
        ]
    },
    "devDependencies": {
        "autoprefixer": "^9.8.8",
        "eslint-config-prettier": "^8.3.0",
        "eslint-plugin-import": "^2.25.3",
        "eslint-plugin-jsx-a11y": "^6.5.1",
        "eslint-plugin-prettier": "^4.0.0",
        "eslint-plugin-react": "^7.27.1",
        "eslint-plugin-react-hooks": "^4.3.0",
        "postcss": "^7.0.39",
        "prettier": "^2.5.1",
        "tailwindcss": "npm:@tailwindcss/postcss7-compat@^2.2.17"
    }
}
`

### craco.config.js

`module.exports = {

    style: {
        postcss: {
            plugins: [require('tailwindcss'), require('autoprefixer')],
        },
    },

};`

I have just shifted to react scripts 5.0.0 for in order to get rid of [this](https://github.com/facebook/create-react-app/issues/11771) issue and now im getting an error in vs code console while doing npm start, which goes like **UnhandledPromiseRejectionWarning: TypeError: match.loader.options.plugins is not a function** and i don't know what is causing this error can someone please help out with this
Repository: terminal
Issue: [Settings] : Tooltip is not appearing for 'Close/Open' Navigation button, when user jump to Settings page using "Ctrl + ," keys.
Labels: Issue-Bug,Area-Accessibility,Product-Terminal,HCL-E+D,A11yUsable,HCL-WindowsTerminal,A11yCO

### Windows Terminal version

1.12.3472.0

### Windows build number

22509.1011

### Other Software

**Test Environment: **
OS: Windows 11 Version Dev (OS Build 22509.1011)
App: Windows Terminal Preview

### Steps to reproduce

**Repro Steps: **

1.Open Windows Terminal.
2.Open Settings page using 'Ctr+,'
3.Focus will land on 'Close/open' Navigation button.
4.Verify whether Tooltip is appearing for 'Close/Open' Navigation button or not.

**User Experience: **
Users who rely on keyboard will get impacted here & may not know the exact purpose of the control, if Tooltip not appears for 'Close/Open' Navigation button, when user jump to Settings page using "Ctrl + ," keys.

Attachment :
[Tooltip is not appearing for 'Close or Open' Navigation button, when user jump to Settings page using Ctrl + , keys..zip](https://github.com/microsoft/terminal/files/7727596/Tooltip.is.not.appearing.for.CloseOpen.Navigation.button.when.user.jump.to.Settings.page.using.Ctrl.%2B.keys.zip)


### Expected Behavior

Tooltip should appear for 'Close/Open' Navigation button, when user jump to Settings page using "Ctrl + ," keys.

### Actual Behavior

Tooltip is not appearing for 'Close/Open' Navigation button, when user jump to Settings page using "Ctrl + ," keys.
-->On opening 'settings' using 'Ctrl + ,' keys, focus is landing on 'Close/Open' Navigation button & Tooltip is not appearing for 'Close/Open' Navigation button.

Observation : 
Issue do not repro, while navigating in the opened 'Settings' window.
Repository: terminal
Issue: [Settings] : Screen Reader is not announcing as 'Saved' and 'Changes Discarded', when user activates 'Save' and 'Discard changes' button.
Labels: Issue-Bug,Area-Accessibility,Product-Terminal,Priority-3,HCL-E+D,A11yWCAG,HCL-WindowsTerminal,A11yCO,A11ySev3

### Windows Terminal version

1.12.3472.0

### Windows build number

22509.1011

### Other Software

**Test Environment: **
OS: Windows 11 Version Dev (OS Build 22509.1011)
App: Windows Terminal Preview
Screen Reader : Narrator



### Steps to reproduce

**Repro Steps: **

1.Open Windows Terminal.
2.Open Settings page using 'Ctr+,'
3.Select any 'list-item' from left pane.
4.Now Navigate in the 'Right pane' via tab key & make any changes.
5.Now activate 'Save' or 'Discard changes' button.
6.Observe the issue.

**User Experience: **
Users who rely on screen reader will get impacted here & may not know whether the changes are discarded or saved successfully on activating respective buttons, if Screen Reader do not announces 'Saved' and 'Changes Discarded' when user activate 'Save' and 'Discard changes' button.

Guideline reference
EN 301 549 V3.2.1: 11.5.2.15 Change notification

Attachment : 
[Screen Reader is not announcing as 'Saved' and 'Changes Discarded'.zip](https://github.com/microsoft/terminal/files/7727877/Screen.Reader.is.not.announcing.as.Saved.and.Changes.Discarded.zip)


### Expected Behavior

Screen Reader should narrate as 'Saved' and 'Changes Discarded' as a confirmation message, when user activates 'Save' and 'Discard changes' button.

### Actual Behavior

Screen Reader is not announcing as 'Saved' and 'Changes Discarded', when user activates 'Save' and 'Discard changes' button.
Repository: flutter
Issue: Missing refund functionality for iOS In App Purchase (IAP)
Labels: c: new feature,platform-ios,p: in_app_purchase,package,c: proposal,P2,team-ios,triaged-ios

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill out the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case
iOS In App Purchase [Human Guidelines](https://developer.apple.com/design/human-interface-guidelines/in-app-purchase/overview/introduction/) are updated. Apple requires to launch the refund flow from within the app now by using [`beginRefundRequest(in:)`](https://developer.apple.com/documentation/storekit/transaction/3803220-beginrefundrequest). It will open the Native Refund flow. Apple can raise issue if developer do not full fill these human guidelines.
<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe the alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal
Please add functionality in [in_app_purchase ](https://pub.dev/packages/in_app_purchase) to launch the flow of refund in iOS. 
<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching something showing what you are imagining:
      * images
      * videos
      * code samples

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->
Repository: terminal
Issue: [Settings>Color schemes] : Screen reader is not narrating any confirmation message, when user activate 'Add New', 'Accept rename' and 'Yes, Delete color Scheme' button.
Labels: Issue-Bug,Area-Accessibility,Product-Terminal,Priority-3,HCL-E+D,A11yWCAG,HCL-WindowsTerminal,A11yCO,A11ySev3

### Windows Terminal version

1.12.3472.0

### Windows build number

22509.1011

### Other Software

**Test Environment: **
OS: Windows 11 Version Dev (OS Build 22509.1011)
App: Windows Terminal Preview
Screen Reader : Narrator



### Steps to reproduce

**Repro Steps: **

1.Open Windows Terminal.
2.Open Settings page using 'Ctr+,'
3.Navigate to 'Color schemes' list-item from left pane via tab key & press enter.
4.Now Navigate in the right pane via tab key & 'add', 'Replace' & 'Delete' the color scheme by activating respective buttons.
5.Observe the issue.

**User Experience: **
Users who rely on screen reader will get impacted here & may not know any confirmation on 'adding', 'Replacing' & 'Deleting' the color scheme by activating respective buttons, if Screen reader do not narrates any confirmation message, when user activate 'Add New',  'accept rename' and 'Yes, Delete color Scheme' button.

Guideline reference
EN 301 549 V3.2.1: 11.5.2.15 Change notification

Attachment
[Screen reader is not narrating any confirmation message, when user activate 'Add New', 'Accept rename' and 'Yes, Delete color Scheme' button..zip](https://github.com/microsoft/terminal/files/7728112/Screen.reader.is.not.narrating.any.confirmation.message.when.user.activate.Add.New.Accept.rename.and.Yes.Delete.color.Scheme.button.zip)


### Expected Behavior

Screen Reader should narrate as  Ex : 'Color Scheme12 added', 'Color Schemes 12 renamed to Hello' and 'Color Scheme 12 Deleted' when user activate 'Add New', 'Accept rename' and 'Yes, Delete color Scheme' button.

### Actual Behavior

Screen reader is staying silent & not narrating any confirmation message, on 'adding', 'Replacing' & 'Deleting' the color scheme by activating 'Add New', 'Accept rename' and 'Yes, Delete color Scheme' button respectively.