sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Overflow evaluating the requirement with a where clause on associated type
Labels: A-associated-items,GATs-triaged,S-bug-has-test,A-GATs

I tried this code ([playground](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=f807d82c1774e0e747237c3815b45542)):

```rust
#![feature(generic_associated_types)]

use std::fmt::Debug;

trait Foo {
    type Ass where Self::Ass: Debug;
}

#[derive(Debug)]
struct Bar;

impl Foo for Bar {
    type Ass = Bar;
}
```

Note that while it doesn't use GATs, it requires `feature(generic_associated_types)` for the `where` clause on the associated type to be allowed.

I expected to see this happen: this should build without errors.

Instead, this happened:

```
error[E0275]: overflow evaluating the requirement `<Bar as Foo>::Ass == _`
  --> src/lib.rs:12:5
   |
12 |     type Ass = Bar;
   |     ^^^^^^^^^^^^^^^

For more information about this error, try `rustc --explain E0275`.
```

[Error E0275 explanation](https://doc.rust-lang.org/nightly/error-index.html#E0275) uses this example:

```rust
trait Foo {}

struct Bar<T>(T);

impl<T> Foo for T where Bar<T>: Foo {}
```

where indeed there's a recursive requirement that can't be checked in a small number of steps. Not so in my example: there's no recursion; `Bar` clearly implements `Debug` (and `Foo`).

@rustbot modify labels: +A-associated-items +F-generic_associated_types
Repository: rust
Issue: Stall from overflow caused by `for<'a> F: FnOnce(Self::Gat<'a>)`
Labels: GATs-triaged,A-GATs

<!--
This code causes `rustc` completely stall on my local machine.

-->

I tried this code:

```rust
#![feature(generic_associated_types)]

pub struct Structure<F> {
    f: F,
}

pub trait Trait {
    type Gat<'a>;
}

impl<F> Trait for Structure<F>
where
    for<'a> F: FnOnce(Self::Gat<'a>),
{
    type Gat<'a> = String;
}
```

https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=fbd726c1f1bd90e514358a91016581ec

Given that 
https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=f889ed7bfeffb6a6f3179bf6d94f438c
causes an `overflow evaluating the requirement Structure<F>: Trait` I would expect the problem code to give a similar message.

Instead, `rustc` stalls indefinitely.

### Meta

`rustc --version --verbose`:
```
rustc 1.56.0-nightly (a6ece5615 2021-08-03)
```

<details><summary>Backtrace</summary>
<p>

No backtrace produced due to stall.

</p>
</details>
Repository: youtube-dl
Issue: Handling url expiration in a queue of direct links
Labels: question

<!--

######################################################################
  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:
- Look through the README (http://yt-dl.org/readme) and FAQ (http://yt-dl.org/faq) for similar questions
- Search the bugtracker for similar questions: http://yt-dl.org/search-issues
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm asking a question
- [x] I've looked through the README and FAQ for similar questions
- [x] I've searched the bugtracker for similar questions including closed ones


## Question

<!--
Ask your question in an arbitrary form. Please make sure it's worded well enough to be understood, see https://github.com/ytdl-org/youtube-dl#is-the-description-of-the-issue-itself-sufficient.
-->

I'm trying to build a telegram bot that streams from audio links given by YoutubeDl using ffmpeg and directly sending the raw bytes to a library. The problem is that I've just remembered that the direct urls given by YoutubeDl might expire after a certain time so when the script reaches a queue index the url might not be usable again.

I'm trying to build some kind of cache thing around this that if the url has expired the script will fetch the url again but I need to know a few things before proceeding.

Does YoutubeDl has some kind of cache implemented that when I use `extract_info()` will not make another request to the server (either YouTube or any other supported services)?

Is there any hint indicating where the link might expire? Either a header, dictionary attribute or something else without me having to parse the url?

What are other options I can explore when fetching something using YoutubeDl?
Repository: create-react-app
Issue: react-scripts 4.0.0 not working
Labels: priority: low (ignored issue template),priority: low (needs more information),issue: needs investigation,issue: bug report

In my react app I use react-scripts 4.0.0. When I run my react app with `npm start`, react-scripts fails to start my react app. When I downgrade react-scripts to 3.0.0 and run `npm start`, the app successfully runs. Please fix this problem in react-scripts 4.0.0.
Repository: vscode
Issue: Git - Commit does not work if there are git hooks from husky and lint-staged
Labels: bug,git

<!-- ⚠️⚠️ 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: 1.58.2

```
code --version    
1.58.2
c3f126316369cd610563c75b1b1725e0679adfb3
x64
```

- OS Version: Ubuntu 20.04

Steps to Reproduce:

1. configure husky and lint-staged
2. check that commiting from CLI works
3. try commiting from VSCode 
4. get error "Git: Failed to execute git"
5. see following in git log in Output:

```
> git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file -
> git config --get-all user.name
> git config --get-all user.email
```
Repository: godot
Issue: rotref_posscale_decomposition() error when scaling a skeleton with physical bone children
Labels: bug,topic:core,topic:3d

### Godot version

3.3.2

### System information

Windows 10 Intel 4690k GTX 1060 6gb

### Issue description

E 0:00:00.550   rotref_posscale_decomposition: Condition "!m.is_diagonal()" is true. Returned: Vector3()
  <C++ Source>  core/math/basis.cpp:300 @ rotref_posscale_decomposition()
Error is thrown when scaling a skeleton with physical bone children(Specifically when using those created by Godot's ragdoll system)

### Steps to reproduce

1. Create a skeleton
2. Create a ragdoll
3. Child the ragdoll to the skeleton
4. Scale the skeleton
5. Run the scene with the skeleton

### Minimal reproduction project

[Ragdoll Bug.zip](https://github.com/godotengine/godot/files/6931769/Ragdoll.Bug.zip)

Run the scene and there will be an error. Scale the root node back down to 1, and the error disappears.
Repository: storybook
Issue: Storybook is firing DOMContentLoaded twice on hard refresh
Labels: bug,has workaround,core,needs triage

**Describe the bug**
Also seems to be happening on hot reload too.

**To Reproduce**
```js
    window.addEventListener('DOMContentLoaded', () => {
      console.log('fired')
    });
```
Then refresh the page using F5.

This is due to storybook simulating page reload for hot-reload changes here:

```js
export function simulateDOMContentLoaded() {
  var DOMContentLoadedEvent = document.createEvent('Event');
  DOMContentLoadedEvent.initEvent('DOMContentLoaded', true, true);
  document.dispatchEvent(DOMContentLoadedEvent);
}
```

However it should not fire the above function on a hard refresh of the page because the browser fires it automatically.

Here's current workaround:

preview.js

```js
let domContentAlreadyLoaded = false;

document.addEventListener('DOMContentLoaded', (e) => {
  if (domContentAlreadyLoaded) {
    e.stopPropagation();
  }

  domContentAlreadyLoaded = true;
});
```

Hot reload doesn't work but it's better than bugs.
Repository: godot
Issue: Changing Viewport size after scene initialization causes render offset
Labels: bug,topic:rendering,confirmed

### Godot version

3.3.stable

### System information

Windows 10, gles3

### Issue description

When changing the size of a Viewport node during runtime (after _ready()), the resulting ViewportTexture will render the contents at an offset equal to half the difference between old size and new size. Interestingly, this doesn't seem to occur during initialization of the scene, so you can change the size all you want during _ready() unless you use a delay (such as a yield timer). Additionally, the ViewportTexture seems to correct itself if you change the window size in any way.

### Steps to reproduce

I've included a minimal reproduction project, by default it will wait 1 second then change the size of the viewport resulting in the sprite being rendered at an offset. You can change the delay and new viewport size in the "Main" node's inspector. Different sizes will result in different offsets, which may result in the sprite going off-screen.

### Minimal reproduction project

[Viewport Bug Test.zip](https://github.com/godotengine/godot/files/6931925/Viewport.Bug.Test.zip)
Repository: neovim
Issue: NetrwSettings() error
Labels: bug-vim,needs:vim-patch,netrw

### Neovim Version

NVIM v0.5.0

### Operating system/version:

archlinux 5.13.7-arch1-1

### Terminal name/version:

alacritty 0.8.0 (a1b13e68)

### TERM environment variable

tmux-256color

### Installation

pacman -S neovim

### Steps to reproduce

with nvim -u NORC

:NetrwSettings<CR>

### Vim

with a new vim install (pacman -S vim; version: VIM - Vi IMproved 8.2, Included patches: 1-2891) this error is shown:

```
Error detected while processing function netrwSettings#NetrwSettings:
line    2:
E117: Unknown function: netrw#SavePosn
"Netrw Settings" [Not edited] --No lines in buffer--
line  130:
E121: Undefined variable: g:netrw_localrmdir
Press ENTER or type command to continue
```

### Expected behavior

settings are shown without any errors

### Actual behavior

```
Error detected while processing function netrwSettings#NetrwSettings:
line    2:
E117: Unknown function: netrw#SavePosn
line  130:
E121: Undefined variable: g:netrw_localrmdir
E15: Invalid expression:  'let g:netrw_localrmdir        = '.g:netrw_localrmdir
Press ENTER or type command to continue
```

after hitting enter the settings are shown
Repository: go
Issue: x/exp/cmd/gorelease: cannot verify consistency of existing tag
Labels: NeedsInvestigation,modules,Tools

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.16.6 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

Yes

### What did you do?

I use `gorelease` locally, it's a great tool to automatically apply semver rules and suggest new version numbers.

### What did you expect to see?

In addition to that, I would like to use it on CI (specifically: every time a new `v*` tag is pushed) in order to verify that this tag is consistent with the semantic versioning rules. This would allow us to catch cases where contributors forgot to run `gorelease` before tagging a new release, and quickly act to avoid breaking downstream users when we used the wrong version number.

### What did you see instead?

There's no way to verify an existing version using `gorelease`. Running `gorelease` on the most recent tag (`v0.x.y`) will just return `v0.x.y+1`, running it using the `-base=v0.x.y-1` results in the error message "Can only suggest a release version when compared against the most recent version of this major: v0.x.y".
Repository: go
Issue: x/crypto/ssh/agent: keyring does not honor "ConfirmBeforeUse"
Labels: Documentation,NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

I was using the newest release of <https://github.com/buptczq/WinCryptSSHAgent>

### Does this issue reproduce with the latest release?

As far as my code analysis goes: yes

### What operating system and processor architecture are you using (`go env`)?

Windows 10, x64

### What did you do?

TL;DR: realizing, the ``-c``-flag of ``ssh-add`` is ignored by <https://github.com/buptczq/WinCryptSSHAgent>, while ``-t`` isn't.

for more details, please see https://github.com/buptczq/WinCryptSSHAgent/issues/55

After opening the issue there, I further investigated and understood, the problem is in the library. Especially in the keyring-implementation of the ssh agent: https://github.com/golang/crypto/blob/a769d52b0f97a420f3dcafc17f8b3384217859a2/ssh/agent/keyring.go.

While https://github.com/golang/crypto/blob/a769d52b0f97a420f3dcafc17f8b3384217859a2/ssh/agent/keyring.go#L147-L148 says "Note that any constraints given are ignored.", the time constraint really isn't, as appropriate handling was added in https://github.com/golang/crypto/commit/8e06e8ddd9629eb88639aba897641bff8031f1d3. However, the claim "and will ask the user to confirm a signing operation if ConfirmBeforeUse is set." in the commit description is not true: as far as I understand the code, no sch handling was/is included in the file.

### What did you expect to see?

I expected, that either both flags are ignored/not supported (as common on windows in Pageant as well as Microsoft OpenSSH) or both flags are supported. At best of course the latest.

### What did you see instead?

As described above: ``ssh-add -t`` is handled correctly, while ``ssh-add -c`` isn't.
Repository: vscode
Issue: Line numbers are not restored if active window when exiting Zen mode is not a file.
Labels: bug,workbench-zen,confirmed

<!-- ⚠️⚠️ 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: 1.58.2
- OS Version: Windows_NT x64 10.0.19043

Steps to Reproduce:

1. Open a file.
2. Enter Zen Mode.
3. Open your Command Palette.
4. Select "Preferences: Open User Settings".
5. Exit Zen Mode.
6. Switch back to the original file.

You will see that your line numbers were not restored if your active window was not a file when exiting Zen mode.
Repository: rust
Issue: Tracking issue for organizing the standard library's #![feature]s
Labels: C-cleanup,T-libs,A-technical-debt

The standard libraries use a lot of `#![feature]`s. We should organize them a bit and make sure it's acceptable for all of them to be used in the way they are.

It'd be nice to split them in language and library features. For the language features, we should check with the relevant team(s) if it's okay that we're using the feature in the library, and document with which of them we need to be extra careful and what their pitfalls are.

There's also a few features enabled that are no longer in use. We should remove those attributes.

- [ ] Categorize and clean up features
    - [x] `core`: https://github.com/rust-lang/rust/pull/87768
    - [x] `alloc`: https://github.com/rust-lang/rust/pull/87769
    - [ ] `std`
    - [ ] other libraries
- [ ] Make an overview of used language features
- [ ] Discuss those language features and their uses with the relevant team(s)
- [ ] Document stuff for future contributors and reviewers
Repository: storybook
Issue: Allow addon authors to opt-out of URL syncing for certain globals
Labels: feature request,args

**Is your feature request related to a problem? Please describe**
See discussion on https://github.com/storybookjs/storybook/pull/15056

**Describe the solution you'd like**

When setting a global from an addon, allow it to opt-out from URL syncing (writing to it, not reading from it).

**Describe alternatives you've considered**
We could add a separate API to define globals to exclude from syncing (incl. ones that aren't set in the addon itself). Allowing control of other addons' behavior seems wrong though.
Repository: PowerToys
Issue: Replace the gif encoder in ImageResizer
Labels: Product-Image Resizer,Cost-Large

### Description of the new feature / enhancement

Currently, ImageResizer uses the .net GifBitmapEncoder, which doesn't support gif features such as global metadata and frame metadata.
The gif encoder should be replaced to one that is able to handle this metadata, as currently the gif resizer can destroy the animation on some gif images after resizing.

Ref: https://github.com/microsoft/PowerToys/issues/12487

### Scenario when this would be used?

When resizing gif images that contain global metadata and frame metadata.

### Supporting information

_No response_
Repository: storybook
Issue: Preview build failing with component display name containing space after 6.3.x
Labels: bug,has workaround,core

**Describe the bug**
The preview build is failing when any components have a `displayName` containing a space after upgrading from [`v6.2.9`](https://github.com/storybookjs/storybook/releases/tag/v6.2.9) to [`v6.3.0`](https://github.com/storybookjs/storybook/releases/tag/v6.3.0).

The reason seems to be due to the following:
```
HTMLButtonElement.displayName = 'HTML Button Element';
```
transpiles to
```
HTML Button Element.displayName = 'HTML Button Element';
```

**To Reproduce**
`yarn storybook` (error in console) or `yarn build-storybook` (error in terminal) on https://github.com/mvargeson/storybook-display-name-build-failure-repro

**System**
```
Environment Info:

  System:
    OS: macOS 11.5.1
    CPU: (8) x64 Intel(R) Core(TM) i7-6920HQ CPU @ 2.90GHz
  Binaries:
    Node: 14.17.3 - /usr/local/bin/node
    Yarn: 1.22.10 - /usr/local/bin/yarn
    npm: 6.14.13 - /usr/local/bin/npm
  Browsers:
    Chrome: 92.0.4515.131
    Firefox: 53.0.3
    Safari: 14.1.2
  npmPackages:
    @storybook/addon-actions: ^6.3.6 => 6.3.6
    @storybook/addon-essentials: ^6.3.6 => 6.3.6
    @storybook/addon-links: ^6.3.6 => 6.3.6
    @storybook/builder-webpack5: ^6.3.6 => 6.3.6
    @storybook/components: ^6.3.6 => 6.3.6
    @storybook/core-events: ^6.3.6 => 6.3.6
    @storybook/manager-webpack5: ^6.3.6 => 6.3.6
    @storybook/react: ^6.3.6 => 6.3.6
    @storybook/theming: ^6.3.6 => 6.3.6
```

**Additional context**
I realize this is likely not an issue specifically with Storybook (probably Babel, etc). I had significant trouble tracking this down in a large codebase (with only a single component guilty of having a space in the display name) after doing the version bump so my hope is that filing this will help somebody else discover the problem in their own codebase.

An example of how this would show up in error output:
```
Error: bundle.js from Terser
ERR!       Unexpected token: name (...)
```

I've also seen this show up with the significantly more helpful:
```
ERR! => Failed to build the preview
ERR! Unexpected token (15:9)
ERR! | try {
ERR! |     // @ts-ignore
ERR! |     HTML Button Element.displayName = "HTML Button Element";
ERR! |     // @ts-ignore
ERR! |     HTML Button Element.__docgenInfo = { "description": "Primary UI component for user interaction", "displayName": "HTML Button Element", "props": {} };
```

**Workaround**
Find the space(s). Remove the space(s). 🤷
Repository: PowerToys
Issue: PowerToys Run and Ease of Access
Labels: Issue-Bug,Product-PowerToys Run,Priority-2,Area-Accessibility

PowerToys Run window should retain focus when "Activate a window by hovering over it with mouse" is enabled, unless ESC is hit or search has been completed.
Repository: pytorch
Issue: Add a way to edit CI env variables from PRs
Labels: low priority,triaged,better-engineering

When looking over #62686 I was thinking it'd be nice to be able to toggle this behavior (something hidden behind an environment variable) without changing any code. Right now to do something like this we have to ghstack together a change that flips the flag + the actual change. Setting these from the PR itself could obviate the need for this and make iteration easier. This could look something like this section in the PR body:

````
```environment
MY_ENV_VAR=some_new_value
```
````


I don't think this would be easy/clean to implement today in a generic way though. We could add a check that reads `${{ github.event.pull_request.body }}` and sets things accordingly before running the tests, but this doesn't cover many of our other build scripts that read envs. For those we'd need to edit the env of the shell so there'd have to be some kind of wrapper (maybe [using a custom `shell:` parameter](https://docs.github.com/en/actions/reference/workflow-syntax-for-github-actions#custom-shell) could simplify this)

cc @pytorch/pytorch-dev-infra
Repository: PowerToys
Issue: FancyZones Grid, specify rows and columns separately
Labels: Idea-Enhancement,FancyZones-Editor,Product-FancyZones

### Description of the new feature / enhancement

When defining a "Grid" type layout, allow specifying rows and columns separately

### Scenario when this would be used?

I have a 43" 4K TV running at 100% scale, and would like to create a layout with 8 columns and 4 rows for that monitor. Defining this by hand as a custom layout is way too fiddly.

### Supporting information

_No response_