sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: yt-dlp
Issue: Extract audio from audio.onet.pl
Labels: site-bug

### Checklist

- [X] I'm reporting a site feature request
- [X] I've verified that I'm running yt-dlp version **2022.05.18** ([update instructions](https://github.com/yt-dlp/yt-dlp#update)) or later (specify commit)
- [X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
- [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

_No response_

### Example URLs

[onet.pl video](https://www.onet.pl/video/programy/86-dzien-wojny-wstrzasajace-nagranie-z-mariupola/6vszsg0,6c2ea0e6) extraction works. 

[audio.onet.pl](https://audio.onet.pl/show/autoswiatwstereo/samochd-kontra-rower-czy-mona-to-jako-pogodzi) extraction fails (debug log below).

### Description

Currently onet.pl extracto only extracts video. It fails for audio (podcast) extraction. 

### Verbose log

```shell
[debug] Command-line config: ['-vU', 'https://audio.onet.pl/show/autoswiatwstereo/samochd-kontra-rower-czy-mona-to-jako-pogodzi']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.05.18 [b14d52355]
[debug] Python version 3.10.4 (CPython 64bit) - macOS-12.3.1-x86_64-i386-64bit
[debug] Checking exe version: ffprobe -bsfs
[debug] Checking exe version: ffmpeg -bsfs
[debug] exe versions: ffmpeg 5.0.1 (setts), ffprobe 5.0.1, rtmpdump 2.4
[debug] Optional libraries: Cryptodome-3.14.1, brotli-1.0.9, certifi-2021.10.08, mutagen-1.45.1, sqlite3-2.6.0, websockets-10.3
[debug] Proxy map: {}
Latest version: 2022.05.18, Current version: 2022.05.18
yt-dlp is up to date (2022.05.18)
[debug] [onet.pl] Extracting URL: https://audio.onet.pl/show/autoswiatwstereo/samochd-kontra-rower-czy-mona-to-jako-pogodzi
[onet.pl] samochd: Downloading webpage
ERROR: [onet.pl] samochd: Unable to extract pulsembed url; please report this issue on  https://github.com/yt-dlp/yt-dlp/issues?q= , filling out the appropriate issue template. Confirm you are on the latest version using  yt-dlp -U
  File "/usr/local/Cellar/yt-dlp/2022.5.18/libexec/lib/python3.10/site-packages/yt_dlp/extractor/common.py", line 642, in extract
    ie_result = self._real_extract(url)
  File "/usr/local/Cellar/yt-dlp/2022.5.18/libexec/lib/python3.10/site-packages/yt_dlp/extractor/onet.py", line 252, in _real_extract
    pulsembed_url = self._search_regex(
  File "/usr/local/Cellar/yt-dlp/2022.5.18/libexec/lib/python3.10/site-packages/yt_dlp/extractor/common.py", line 1226, in _search_regex
    raise RegexNotFoundError('Unable to extract %s' % _name)
```
Repository: create-react-app
Issue: Allow Proxy to be set by environment variables
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..."
-->

Currently, we are using the proxy for create-react-app to proxy requests to a staging server and it works great. We have several environments hosted for development and production (e.g. staging, testing, prod, BSEs, and occasionally long-lived feature branches). If we want to change what server we are proxying to we need to change the field in package.json and remember to revert this change before committing. This frustrates me because I very frequently forget and commit this change. 

### Describe the solution you'd like

<!--
  Provide a clear and concise description of what you want to happen.
-->

I'd like to be able to set the proxy via environment variables so that it is configurable without having to change tracked files. This would allow us to add environment variables in the shell and not have to change tracked files to change the proxy. I'd like to append `|| proccess.env.PROXY` to line [111 of react-scripts/scripts/start.js](https://github.com/facebook/create-react-app/blob/3880ba6cfd98d9f2843217fd9061e385274b452f/packages/react-scripts/scripts/start.js#L111) 

### Describe alternatives you've considered

<!--
  Let us know about other solutions you've tried or researched.
-->

We looked into using 'http-proxy-middleware' to setup a custom proxy that will proxy off environment variables. We are currently not prefixing our endpoints and setting up 'http-proxy-middleware' for a custom proxy to work on environment variables would require some refactoring of the application and how we are integrating with third party software we are using for authorization and processing payments.

### Additional context

<!--
  Is there anything else you can add about the proposal?
  You might want to link to related issues here, if you haven't already.
-->

(Write your answer here.)
Repository: go
Issue: crypto/cipher: easy optimisations to xorBytes
Labels: Performance,NeedsInvestigation

The function `crypto/cipher.xorBytes` implements the XOR operations between slices of bytes, and is heavily used by encryption in CTR mode.  The version in the stdlib has seen a significant amount of optimisation, but some easy optimisations are missing:

1. The variable `supportUnaligned` in xor_generic.go should be set for GOARCH equal to `arm64`.
2. Said variable sohould be set for GOARCH equal to ARM and GOARM equal to 6 or 7 (but not 5).
3. When `supportsUnaligned` is not set, the fast version should still be called when both src and dst are multiples of wordSize (this actually happens fairly often, e.g. when encrypting a freshly allocated slice);
4. When `supportsUnaligned` is not set, and src and dst are equal modulo wordSize, then the initial bytes should be xored and then the fast version called on the rest of the array;
5. Ideally, there should be a NEON implementation for ARMv7.

Points 1 through 3 are fairly trivial, and would bring a significant part of the benefit.  This is related to #53021.
Repository: godot
Issue: Crash in 3.5 rc1 on MacBook when opening specific game
Labels: bug,platform:macos,topic:core,crash

### Godot version

3.5 RC1

### System information

MacBook M1 Max, macOS 12.3.1

### Issue description

I was previously using 3.5 beta1 without any issues. Today I installed 3.5 beta 5, followed by 3.5 rc1, both of which crash when I try to edit a specific game.

I did some further testing with other versions, starting back at 3.5 beta1. I found that the crash happens starting at 3.5 beta3.

I don't know if the system crash report helps, but I can add it if it does.


### Steps to reproduce

I don't know how to reproduce this because it only happens with one game that I am working on. Other games open without crashing.

### Minimal reproduction project

_No response_
Repository: material-ui
Issue: Support Material Symbols (Icon v2)
Labels: new feature,design: material,waiting for 👍,priority: important,package: icons

### Summary 💡

Google has recently introduced a new major iteration on their icon system: Material Symbols: https://material.io/blog/introducing-symbols. This is an awesome new iteration on their icon system, and more importantly, they have made it the default! Proof https://fonts.google.com/icons. This new iteration seems much better.

<img width="253" alt="Screenshot 2022-05-21 at 17 00 35" src="https://user-images.githubusercontent.com/3165635/169657301-fd979b27-bea7-4652-83e5-4f8a454e8ef9.png">

For SVGs, we might be able to implement the weight with the `stroke-width` attribute, see: https://feathericons.com/ but we might have to build these SVGs ourselves: https://github.com/google/material-design-icons/issues/1360.

### Examples 🌈

- https://developers.google.com/fonts/docs/material_symbols
- https://github.com/angular/components/issues/24845
- https://github.com/google/material-design-icons

### Motivation 🔦

We will need to update our icons to reflect this change, both for font and SVG icons. It's an important step forward in terms of icon
Repository: godot
Issue: Access Requests to MacOS Document/Desktop Folders
Labels: platform:macos,topic:editor,topic:porting

### Godot version

4.0 dev alpha 8

### System information

MacOS 12.3.1 Arm64 

### Issue description

My Godot 4.app has full access to my drive in my Security and Privacy settings.  Yet if my Godot project is located in my Desktop or Documents folder, when I start Godot, it prompts me for access to the folder.  When I run the project, it prompts me multiple times before it will start.  Even if I choose OK, it continues to prompt me every time.

If I move the project to a normal folder location, then it works fine.

### Steps to reproduce

Create a new project in your Documents folder.
Save the new scene with Node2D as the root.
Run the scene.


### Minimal reproduction project

_No response_
Repository: PowerToys
Issue: 取消“始终置顶”后，边框残留
Labels: Issue-Bug,Product-Always On Top

### Microsoft PowerToys version

0.58.0

### Running as admin

- [ ] Yes

### Area(s) with issue?

Always on Top

### Steps to reproduce

![Uploading Quicker_20220521_234201.png…]()
[PowerToysReport_2022-05-21-23-41-05.zip](https://github.com/microsoft/PowerToys/files/8747899/PowerToysReport_2022-05-21-23-41-05.zip)
取消“始终置顶”后，窗体的蓝色边框残留无法消去，重启后恢复正常，但偶尔还是会出现。


### ✔️ Expected Behavior

不要边框残留

### ❌ Actual Behavior

_No response_

### Other Software

_No response_
Repository: rust
Issue: [NLL] "so that ... will meet its required lifetime bounds" should point to RPIT, not statement
Labels: A-diagnostics,T-compiler,A-NLL,NLL-diagnostics

In [src/test/ui/impl-trait/type_parameters_captured.rs](src/test/ui/impl-trait/type_parameters_captured.rs) (and similarly in [src/test/ui/impl-trait/must_outlive_least_region_or_bound.rs](src/test/ui/impl-trait/must_outlive_least_region_or_bound.rs)) the suggestion goes from

```
error[E0310]: the parameter type `T` may not live long enough
  --> $DIR/type_parameters_captured.rs:11:20
   |
LL | fn foo<T>(x: T) -> impl Any + 'static {
   |                    ^^^^^^^^^^^^^^^^^^ ...so that the type `T` will meet its required lifetime bounds
   |
help: consider adding an explicit lifetime bound...
```
to

```
error[E0310]: the parameter type `T` may not live long enough
  --> $DIR/type_parameters_captured.rs:13:5
   |
LL |     x
   |     ^ ...so that the type `T` will meet its required lifetime bounds
   |
help: consider adding an explicit lifetime bound...
```
Repository: rust
Issue: [NLL] "that is required by this bound" note missing
Labels: A-diagnostics,T-compiler,A-NLL,NLL-diagnostics,D-terse

In [src/test/ui/nll/ty-outlives/projection-where-clause-env-wrong-lifetime.rs](src/test/ui/nll/ty-outlives/projection-where-clause-env-wrong-lifetime.rs) and [src/test/ui/nll/ty-outlives/projection-where-clause-env-wrong-bound.rs](src/test/ui/nll/ty-outlives/projection-where-clause-env-wrong-bound.rs) we lose a note:

before
```
error[E0309]: the associated type `<T as MyTrait<'a>>::Output` may not live long enough
  --> $DIR/projection-where-clause-env-wrong-lifetime.rs:14:5
   |
LL |     bar::<<T as MyTrait<'a>>::Output>()
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = help: consider adding an explicit lifetime bound `<T as MyTrait<'a>>::Output: 'a`...
   = note: ...so that the type `<T as MyTrait<'a>>::Output` will meet its required lifetime bounds...
note: ...that is required by this bound
  --> $DIR/projection-where-clause-env-wrong-lifetime.rs:20:8
   |
LL |     T: 'a,
   |        ^^
```
after
```
error[E0309]: the associated type `<T as MyTrait<'_>>::Output` may not live long enough
  --> $DIR/projection-where-clause-env-wrong-lifetime.rs:14:5
   |
LL |     bar::<<T as MyTrait<'a>>::Output>()
   |     ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = help: consider adding an explicit lifetime bound `<T as MyTrait<'_>>::Output: 'a`...
   = note: ...so that the type `<T as MyTrait<'_>>::Output` will meet its required lifetime bounds
```

Probably related, but the error used `'_` instead of `'a`
Repository: angular
Issue: Deprecated `@angular/core/testing`'s `inject()`
Labels: area: testing,P3

### Which @angular/* package(s) are relevant/related to the feature request?

core

### Description


Hey 👋 !

There are currently two `inject()` functions that have two completely distinct purposes and signatures: `@angular/core`s and `@angular/core/testing`'s.

This can be misleading and harm the Developer eXperience. (I already had some trouble with IDEs preferring to automatically import `@angular/core/testing` instead of `@angular/core`.)

🤔 This reminds me of `async` => `waitForAsync` renaming

### Proposed solution

IMO, `@angular/core/testing`'s `inject()` is not widely used and we could simply deprecate before we remove it in a future version. We could also ship a migration schematic that "simply" replaces:

```typescript
inject([A, B], (a, b) => {...})
```

with

```typescript
(a = inject(A), b = inject(B)) => {...}
```



### Alternatives considered

Rename `@angular/core/testing`'s `inject()` to something else... maybe `nostalgicInject()`
Repository: rust
Issue: [NLL] "`'static` requirement introduced here" note missing
Labels: A-diagnostics,T-compiler,A-NLL,NLL-diagnostics

In the various revisions of [src/test/ui/associated-types/cache/project-fn-ret-invariant.rs](src/test/ui/associated-types/cache/project-fn-ret-invariant.rs), we go from

```
error[E0759]: `x` has lifetime `'a` but it needs to satisfy a `'static` lifetime requirement
  --> $DIR/project-fn-ret-invariant.rs:55:9
   |
LL | fn baz<'a, 'b>(x: Type<'a>) -> Type<'static> {
   |                   -------- this data with lifetime `'a`...
...
LL |     bar(foo, x)
   |         ^^^  - ...is used and required to live as long as `'static` here
   |
note: `'static` lifetime requirement introduced by the return type
  --> $DIR/project-fn-ret-invariant.rs:51:37
   |
LL | fn baz<'a, 'b>(x: Type<'a>) -> Type<'static> {
   |                                     ^^^^^^^ `'static` requirement introduced here
...
LL |     bar(foo, x)
   |     ----------- because of this returned expression
```
to
```
error: lifetime may not live long enough
  --> $DIR/project-fn-ret-invariant-nll.rs:56:5
   |
LL | fn baz<'a, 'b>(x: Type<'a>) -> Type<'static> {
   |        -- lifetime `'a` defined here
...
LL |     bar(foo, x)
   |     ^^^^^^^^^^^ returning this value requires that `'a` must outlive `'static`
   |
   = note: requirement occurs because of the type `Type<'_>`, which makes the generic argument `'_` invariant
   = note: the struct `Type<'a>` is invariant over the parameter `'a`
   = help: see <https://doc.rust-lang.org/nomicon/subtyping.html> for more information about variance
```

We lose the note, particularly the bit pointing to the return type (it's sort of in the note, but not exactly)
Repository: rust
Issue: Provide better diagnostics upon encountering an infinite cyclic type
Labels: A-diagnostics,T-compiler

<!--
Thank you for filing a bug report! 🐛 Please provide a short summary of the bug,
along with any information you feel relevant to replicating the bug.

If you cannot produce a minimal reproduction case (something that would work in
isolation), please provide the steps or even link to a repository that causes
the problematic output to occur.
-->

Given the following code:

```rust
use nom::{branch::alt, bytes::complete::is_a, sequence::pair, IResult};

fn foo(input: &str) -> IResult<&str, &str> {
    alt((is_a(""), pair(is_a(""), is_a(""))))(input)
}
```

The current output is:

```
error[E0271]: type mismatch resolving `<impl FnMut(_)-> Result<(_, (_, _)), nom::Err<_>> as FnOnce<(_,)>>::Output == Result<(_, _), nom::Err<_>>`
  --> src/main.rs:4:9
   |
4  |     alt((is_a(""), pair(is_a(""), is_a(""))))(input)
   |     --- ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ cyclic type of infinite size
   |     |
   |     required by a bound introduced by this call
   |
   = note: required because of the requirements on the impl of `Parser<_, _, _>` for `impl FnMut(_)-> Result<(_, (_, _)), nom::Err<_>>`
   = note: required because of the requirements on the impl of `nom::branch::Alt<_, _, _>` for `(impl Fn(_)-> Result<(_, _), nom::Err<_>>, impl FnMut(_)-> Result<(_, (_, _)), nom::Err<_>>)`
note: required by a bound in `alt`
  --> /.../nom-7.1.1/src/branch/mod.rs:71:49
   |
71 | pub fn alt<I: Clone, O, E: ParseError<I>, List: Alt<I, O, E>>(
   |                                                 ^^^^^^^^^^^^ required by this bound in `alt`
```

Ideally the output should look something like a mismatched type error.

Also see #35978.

<!--
If the problem is not self-explanatory, please provide a rationale for the
change.
-->

<!--
If dramatically different output is caused by small changes, consider also
adding them here.

If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions. The output might also be
different depending on the Edition.
-->
Repository: PowerToys
Issue: Feature Request: powerToys run, Selected text appearing in the search box without the need for a copy and paste
Labels: Idea-Enhancement,Product-PowerToys Run,Needs-Triage

### Description of the new feature / enhancement

When text is selected and pressed ALT + SPACE appears directly in the search box

### Scenario when this would be used?

When you're working on some files word, PDF, and even you're chatting on telegram then you want to do a quick search on Google rather than copy the  select text  then pressed "alt+ space" then paste it,  you need to select the text, and it's appearing in the search box 

### Supporting information

_No response_
Repository: godot
Issue: RichTextLabel `text` property doesn't return actual text
Labels: bug,documentation,topic:gui

### Godot version

4ce4840

### System information

Windows 10 x64

### Issue description

When you append text to RichTextLabel and it has BBCode enabled, the `text` property will be empty.

If this is intended (and I assume it is), it should be mentioned in the docs. You can use `get_parsed_text()` to get the text without BB codes, but if you append using the push methods, you can't get the full text including bbcodes.

### Steps to reproduce

1. `rich_text_label.append_text("[color=red]test[/color]")`
2. `print(rich_text_label.text)` # nothing

### Minimal reproduction project

_No response_
Repository: PowerToys
Issue: Bind Mouse To Window/Monitor
Labels: Idea-New PowerToy,Needs-Triage

### Description of the new feature / enhancement

Some games, such as Paradox's Stellaris, do not properly bind the mouse cursor to the game window. On systems with 2+ monitors this means that the mouse cursor will move out of the game window and onto another display based on configuration. PowerToys Mouse Utilities could add a configurable hotkey to bind the mouse cursor either to a specific window and/or monitor to help work around these issues.

### Scenario when this would be used?

Playing games where the developer does not properly bind the mouse cursor, but could also be useful in cases where a second (or third) monitor is used purely for displaying status updates and the user does not want the mouse cursor to leave the primary monitor where all interactions will take place. 

### Supporting information

_No response_
Repository: pytorch
Issue: toleranceOverride should override atol and rtol even when explicitly specified in a test
Labels: module: tests,triaged,module: primTorch

This would allow a test's default atol/rtol to be set tighter but still allow operators to set the atol/rtol manually.

In primTorch this would let us set tighter atol and rtol for the reference consistency tests.

cc @mruberry @ezyang @ngimel
Repository: react
Issue: Bug: renderToPipeableStream and renderToStaticNodeStream render inconsistency
Labels: Type: Bug,Component: Server Rendering,React 18

the output html file include unexpected `<!-- --> ` in the `<title>` element when there are both variable and plain text together in `Html.js` react component.
The step is about `renderToPipeableStream` function, and in my project,  i notice similar inconsistent behavior in `renderToStaticNodeStream` as well.

**altho following steps is using v18.0. v18.1 have same results**

React version: 18.1.0

## Steps To Reproduce

If you find this steps too much, **I've already created a fork and attached link to the folk**, ***error is in html title element***

1. go to [ssr example sandbox](https://codesandbox.io/s/kind-sammet-j56ro?file=/server/render.js:1054-1614), i got this link from here https://github.com/reactwg/react-18/discussions/22
2. after entering codesandbox page, go to `src/Html.js` file
3. in line 17, replace `<title>{title}</title>` with `<title>{title} 321</title>`
4. save the file. (you may automatically fork this project after saving)
5. after rebuild, in the browser window on the right hand side, there are three buttons on the right side of url box. click `Open In New Window`
6. check new Window title

Link to code example:

https://codesandbox.io/s/agitated-night-oowlsi?file=/src/Html.js

## The current behavior

the page title and text in html <title> element are both `Hello<!-- --> 321<!-- -->`

## The expected behavior

the page title and value in html <title> element are supposed to be `Hello 321`

![Screen Shot 2022-05-21 at 11 03 26 PM](https://user-images.githubusercontent.com/5487482/169676832-7fba3617-de41-443b-af41-697fa4c067ee.png)
Repository: rust
Issue: [NLL] No "expected ..., found ..." in diagnostics
Labels: A-diagnostics,T-compiler,A-NLL,NLL-diagnostics

This happens in a lot of tests, but from [src/test/ui/traits/trait-upcasting/type-checking-test-4.rs](src/test/ui/traits/trait-upcasting/type-checking-test-4.rs):

before
```
error[E0308]: mismatched types
  --> $DIR/type-checking-test-4.rs:20:13
   |
LL |     let _ = x as &dyn Bar<'static, 'a>; // Error
   |             ^ lifetime mismatch
   |
   = note: expected trait object `dyn Bar<'static, 'a>`
              found trait object `dyn Bar<'static, 'static>`
note: the lifetime `'a` as defined here...
  --> $DIR/type-checking-test-4.rs:19:16
   |
LL | fn test_wrong1<'a>(x: &dyn Foo<'static>, y: &'a u32) {
   |                ^^
   = note: ...does not necessarily outlive the static lifetime
```
after
```
error: lifetime may not live long enough
  --> $DIR/type-checking-test-4.rs:20:13
   |
LL | fn test_wrong1<'a>(x: &dyn Foo<'static>, y: &'a u32) {
   |                -- lifetime `'a` defined here
LL |     let _ = x as &dyn Bar<'static, 'a>; // Error
   |             ^^^^^^^^^^^^^^^^^^^^^^^^^^ type annotation requires that `'a` must outlive `'static`
```

Being able to compare the expected and found types in full make it clear what's wrong.