sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Rprop Optimizer: UnboundLocalError: local variable 'step_size_min' referenced before assignment
Labels: module: optimizer,triaged,actionable

### 🐛 Describe the bug

When using the optimiser's step method, I get an error regarding step minimums. I believe this value should default to 1e-6 if not explicitly set via params.

```
model = Net(feature_number=2, hidden_number=6, output_number=1)
search_method = torch.optim.Rprop(model.parameters(), lr=0.02)
## ommitted
def local_search(weights, network, loss_function, search_method , iterations, x_train, y_train, approach=LEARNING_METHOD):
    """ Perform local search for a given number of iterations """
    weights_into_network(network, weights)
    for i in range(iterations):
        output = network(x_train)
        loss = loss_function(output, y_train)
        search_method .zero_grad()
        loss.backward()
        search_method .step() #<--- here thrown
        learned_loss = loss.item() 
## ommitted
```

```
  File "C:\Users\user\nn_ga\main.py", line 381, in local_search
    search_method.step()
  File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\torch\optim\optimizer.py", line 88, in wrapper
    return func(*args, **kwargs)
  File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\torch\autograd\grad_mode.py", line 28, in decorate_context
    return func(*args, **kwargs)
  File "C:\Users\user\AppData\Local\Programs\Python\Python39\lib\site-packages\torch\optim\rprop.py", line 109, in step
    step_size_min=step_size_min,
UnboundLocalError: local variable 'step_size_min' referenced before assignment
```


### Versions

Versions of relevant libraries:
[pip3] numpy==1.21.1
[pip3] torch==1.10.1+cu102
[pip3] torchaudio==0.10.1+cu102
[pip3] torchvision==0.11.2+cu102

cc @vincentqb @jbschlosser @albanD
Repository: create-react-app
Issue: How to execute timers cleanup before HMR will refresh the page
Labels: needs triage

I have a react application this with some setTimeOut's inside. And after each save HMR react and refreshes the application, but timeouts still going and executing their code.

So question is, do we have some hook (like beforeRefresh), so that I can cleanup timers in it.
Repository: godot
Issue: Large number of CanvasItems in the scene slow down input
Labels: needs testing,topic:input,topic:gui,topic:2d,performance

### Godot version

3.4.2 stable official

### System information

Linux Mint 20.2 Cinnamon, Kernel 5.11, GLES3, AMD Athlon II X4, AMD Radeon Rx 570X, Mesa 21.3

### Issue description

Mouse movement cripples performance massively if many (~10.000) CanvasItems (Control or Node2D) are in the scene.
It's specially bad if `Input.set_use_accumulated_input()` is `false`, but is also noticeable if `true`.



### Steps to reproduce

Place many CanvasItems in the scene, about 10.000 and move the mouse around.

### Minimal reproduction project

[rep_manyLines.zip](https://github.com/godotengine/godot/files/7770595/rep_manyLines.zip)
Repository: next.js
Issue: experimentalDecorators support incomplete
Labels: SWC

### What version of Next.js are you using?

12.0.8-canary.13

### What version of Node.js are you using?

v14

### What browser are you using?

n/a

### What operating system are you using?

macOS

### How are you deploying your application?

other

### Describe the Bug

After removing the babelrc and setting experimentalDecorators to true in compiler options, the build fails with error..

"Error: error: Using the export keyword between a decorator and a class is not allowed. Please use `export @dec class` instead."

Granted, maybe should begin refactoring our legacy decorators anyway, but this should work right?

old .bablerc has..
```json
"plugins": [["@babel/plugin-proposal-decorators", {"legacy": true}]]
```
jsconfig.json has..
```json
{
    "compilerOptions" {
        "experimentalDecorators": true
    }
}
```


### Expected Behavior

Project builds. Currently the build fails with above error.

### To Reproduce

```js
function wrapComponent(Component) {
    return (props) => <Component {...props} imDecorated />
}



@wrapComponent
export default class MyComponent extends Component {
    render() { return <div />; }
}
```
Repository: angular
Issue: Support for AsyncIterable within AsyncPipe
Labels: feature,area: core,feature: under consideration

*Note from the Angular team*: we're treating this issue as a feature request for `AsyncIterable` support in `AsyncPipe`.

### Description

Angular can render native `Iterable` within its `ngFor` directive, but not `AsyncIterable`, complaining when we add `| async` filter to such a type.

### Proposed solution

`AsyncIterable` should be supported with `| async` filter, the same as for any `Observable`.

### Alternatives considered

Wrapping native `AsyncIterable` into RXJS observable just to make it usable within HTML-rendering engine - isn't great, and it creates an unnecessary overhead for a native type, which adds a subscription logic (`AsyncIterable` is simpler, and it doesn't need any subscription logic)

---

**Afterthought:** It should work not just with `ngFor`, but everywhere where `| async` filter is applicable.
Repository: youtube-dl
Issue: wanted crossclip extractor
Labels: request,site-support-request

<!--

######################################################################
  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.
- Search the bugtracker for similar feature requests: http://yt-dl.org/search-issues. DO NOT post duplicates.
- Finally, put x into all relevant boxes (like this [x])
-->

- [x] I'm reporting a feature request
- [x] I've verified that I'm running youtube-dl version **2021.12.17**
- [ ] I've searched the bugtracker for similar feature requests including closed ones

- [x] I'm reporting a new site support request
- [x] I've checked that all provided URLs are alive and playable in a browser
- [ ] I've checked that none of provided URLs violate any copyrights


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single video: https://crossclip.com/clips/352865904939376640

## 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.
-->

1. [Crossclip](https://crossclip.com/) 
2. In addition, wanted to save the clip name via `-o` username-clipname.file . Basically same as the youtube extractor, When on youtube it take titile+ vid by default, IMO on crossclip username-clip-title.extension would be the best.

Feel free to give input / start a PR if you have a similar goal. Happy December :)
Repository: rust
Issue: rustdoc: the pointer docs currently render no less than four separate types in a single main "Methods" list
Labels: T-rustdoc,C-enhancement

[See here.](https://doc.rust-lang.org/nightly/core/primitive.pointer.html)

This was frankly always somewhat confusing even when it amounted to solely the sometimes-identically-named `*const T` and `*mut T` methods, but has recently become IMO borderline unnavigable due to the further addition of the methods from `*const [T]` and `*mut [T]`.

If at all possible, it seems like it would ultimately be good overall to get rustdoc rendering "primitives" in the same separate manner that it does user-defined structs.
Repository: vscode
Issue: file://// URL not recognised
Labels: under-discussion,uri

Issue Type: <b>Bug</b>

1. Control-Press `file:////proc/sys/fs/inotify/max_user_instances` in a text editor.

VS Code version: Code 1.63.2 (899d46d82c4c95423fb7e10e68eba52050e30ba3, 2021-12-15T09:39:46.686Z)
OS version: Linux x64 5.15.8-1-default
Restricted Mode: No

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM)2 Quad CPU    Q6600  @ 2.40GHz (4 x 2379)|
|GPU Status|2d_canvas: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>oop_rasterization: disabled_off<br>opengl: enabled_on<br>rasterization: disabled_software<br>skia_renderer: enabled_on<br>video_decode: disabled_software<br>vulkan: disabled_off<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|1, 1, 1|
|Memory (System)|5.66GB (0.14GB free)|
|Process Argv|--unity-launch --crash-reporter-id 2a03cb52-9f4b-48bf-93d3-5c0537d534ee|
|Screen Reader|no|
|VM|0%|
|DESKTOP_SESSION|/usr/share/xsessions/plasma5|
|XDG_CURRENT_DESKTOP|KDE|
|XDG_SESSION_DESKTOP|KDE|
|XDG_SESSION_TYPE|x11|
</details><details><summary>Extensions (26)</summary>

Extension|Author (truncated)|Version
---|---|---
doxdocgen|csc|1.3.2
vscode-resx-editor|Dom|0.0.5
vscode-pull-request-github|Git|0.34.2
Ionide-fsharp|Ion|5.10.2
better-cpp-syntax|jef|1.15.10
vscode-language-pack-pl|MS-|1.63.3
csharp|ms-|1.23.17
dotnet-interactive-vscode|ms-|1.0.2606010
vscode-dotnet-pack|ms-|1.0.4
python|ms-|2021.12.1559732655
vscode-pylance|ms-|2021.12.2
jupyter|ms-|2021.11.1001550889
jupyter-keymap|ms-|1.0.0
jupyter-renderers|ms-|1.0.4
remote-containers|ms-|0.209.6
remote-ssh|ms-|0.70.0
remote-ssh-edit|ms-|0.70.0
remote-wsl|ms-|0.63.13
cmake-tools|ms-|1.9.2
cpptools|ms-|1.7.1
cpptools-extension-pack|ms-|1.1.0
powershell|ms-|2021.12.0
vscode-markdown-notebook|ms-|0.0.26
vsliveshare|ms-|1.0.5200
vsliveshare-audio|ms-|0.1.91
cmake|twx|0.0.17

(1 theme extensions excluded)

</details><details>
<summary>A/B Experiments</summary>

```
vsliv368:30146709
vsreu685:30147344
python383:30185418
vspor879:30202332
vspor708:30202333
vspor363:30204092
pythontb:30283811
pythonvspyt551cf:30345471
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
pythonvspyt200:30340761
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
vsaa593cf:30376535
pythonvs932:30410667
vscop804cf:30404767
vscop940:30404999
vsrem710:30416614

```

</details>

<!-- generated by issue reporter -->
Repository: godot
Issue: SceneTree dock option menu needs changes
Labels: discussion,topic:editor,usability

### Godot version

9d02cfa

### System information

W10

### Issue description

After #51413, the scene tree has a new menu button for misc options:
![image](https://user-images.githubusercontent.com/2223172/147293504-1450d694-fe00-4e29-8847-fd07ad01bc1e.png)
There are two problems with that:
- We have a menu with a single item (Expand/Collapse All was moved mistakenly, this is being fixed in #55569)
- The menu button takes space from the search field, which is now very small

Both problems are rather minor, especially the first one, but this is something that could be handled better.

For the first problem, we could just move/add more options to the menu. The menu is supposed to contain options that affect the whole tree and are not tied to specific node (unlike the RMB menu). It's rather unlikely that we have some option that could be moved out from RMB menu, but maybe there are some editor settings that could fit there for quick access? Or we could just add some new features 😏 idk

For the second problem, we can do something with Add/Instance Child buttons. They can't be moved/removed, because some people seem to use it often (see discussion in #55569). Right now I can think of two solutions: a) move them to another row
![image](https://user-images.githubusercontent.com/2223172/147293946-aca4be03-7ca4-4efe-9fb2-5869b4e3d82d.png)
This makes the filter box super big, which is nice.
b) hide them when the filter box is focused (probably meh)

### Steps to reproduce

1. Open Godot 4
2. Look at the top of scene tree
3. Kinda meh

### Minimal reproduction project

_No response_
Repository: flutter
Issue: We should have tests for the initial Dart SDK download
Labels: a: tests,tool,P3,c: tech-debt,team-tool,triaged-tool

We currently don't really test the initial Dart SDK download much (except for verifying that it basically works in our test infrastructure).
We should have tests that verify:

- [ ] That it works with various versions of `curl` on various platforms
- [ ] That it works with various versions of `bash` and other shells
- [ ] That it works with various proxy servers (e.g. including those that fail to correctly implement range requests)
- [ ] That it handles transient network errors correctly
- [ ] That it handles data corruption in the download
- [ ] That it works from many different regions
- [ ] That it works in China in particular
Repository: TypeScript
Issue: Generic extending union type inference error
Labels: Bug

# Bug Report

I am not sure this is intentional or not.

### 🔎 Search Terms

TS2322  generic union 

### 🕗 Version & Regression Information

4.5.4

### ⏯ Playground Link

https://www.typescriptlang.org/play?#code/C4TwDgpgBAGlC8UDeUAeAuKA7ArgWwCMIAnAbigF8AoUSKATQWShE10JPOtuhkcTgAfBqSo1w0AOIAeACpQIqYBCwATAM6x6APiZIqUKAHM2+ImSoUoAMiizRVAGY4sAY2ABLAPZYozt3IKSioaWtoAFACUzFAGUK4+6sBomPqGhiZQAAxxVrYwooYJWElorMhxGZg5hnlQ4UIMkYXxicnAqZXG1bk2dg5FbcYA+gDuHsAAFsMYUDJ8uoioLQD0K1AA8gDSccWlRmMT06jl8zpMJ6vr27tDB+NTwx1z0gtMwFd2AMoATADMPx+liAA

### 💻 Code

<!-- Please post the relevant code sample here as well-->
```ts
type X = { x: number; }
type Y = { y: number; }
type XY = X | Y;

type G<T extends XY> = {
  g: number;
} & T;

function func<T extends XY>() {  
  const x: {
    g: 0
  } & X;
  const xy: {
    g: 0
  } & (X | Y);
  const t: {
    g: 0
  } & T;

  const g_with_x: G<XY> = x;
  // OK
  const g_with_xy: G<XY> = xy;
  // OK
  const g_with_t: G<XY> = t;
  // TS2322
}
```

### 🙁 Actual behavior

TS2322 occurs

### 🙂 Expected behavior

It should not, maybe?
Repository: TypeScript
Issue: Confusing error for missing { in JSX attribute initializer object
Labels: Suggestion,Experience Enhancement

# Bug Report

<!--
  Please fill in each section completely. Thank you!
-->

### 🔎 Search Terms

jsx attribute expression initializer double brace bracket object cannot find name

### 🕗 Version & Regression Information

- This is the behavior in every version I tried, and I reviewed the FAQ for entries about JSX

### ⏯ Playground Link

<!--
  A link to a TypeScript Playground "Share" link which shows this behavior

  The TypeScript Workbench can be used for more complex setups, try
  https://www.typescriptlang.org/dev/bug-workbench/

  As a last resort, you can link to a repo, but these will be slower for us to investigate.
-->
[Playground link with relevant code](https://www.typescriptlang.org/play?jsx=1#code/CYUwxgNghgTiAEYD2A7AzgF3gWQJ4GEkBbAB1RBQwC54oVcBuAKCYB49DTzKn55goGKAF4A3rz7w0xEADUoEAK4gaGGMoA0EgL5MA9AD4GQA)

### 💻 Code

```tsx
declare const MyComponent: any;

<MyComponent
  data={ someValue: true }
/>;
```

### 🙁 Actual behavior

```tsx
  data={ someValue: true }
//       ~~~~~~~~~ Error: Cannot find name 'someValue'.
```

Anecdotally, this is a pretty common mistake and I make & see it fairly often. [[example Discord question](https://discord.com/channels/508357248330760243/740273703119618089/923809131528339487)]

### 🙂 Expected behavior

This error message is unrelated to the actual issue, that the contents inside the JSX attribute initializer need to have double `{` around them. 

```tsx
  data={{ someValue: true }}
```

How about adding a suggestion like `Did you mean to add '{}' brackets around the attribute value`, ideally with an auto-fixer?
Repository: storybook
Issue: Tsconfig paths is override when lib is shared between apps
Labels: bug,needs triage

**Describe the bug**
If 2 tsconfig file exist, and everyone defines paths config, seems like the extended one will override the base one.

**To Reproduce**
Create a lib named '@lib/utils', which will create paths in tsconfig.base.json
Then create an app, which extends tsconfig.base.json and defines its own paths in tsconfig.json
When start app, when paths inside tsconfig.base.json will be override and then throw '@lib/utils' is not defined.

```
  // tsconfig.base.json
  "paths": {
    "@stock-web/utils": ["libs/utils/src/index.ts"]
  }

  // tsconfig.json in app

 "extends": "../../tsconfig.base.json",
  "compilerOptions": {
   ...
    "baseUrl": ".",
    "paths": {
      "@/*": ["src/*"],
      "@ajax": ["src/utils/ajax"]
    }
  },
```

Error: @stock-web/utils is not defined.

**Additional context**
Repository: neovim
Issue: :terminal closes file descriptors under 25
Labels: bug,job-control,io,has:repro

### Neovim version (nvim -v)

0.6.0

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

n/a part of :terminal

### Operating system/version

Linux/Archlinux

### Terminal name/version

kitty 0.23.1

### $TERM environment variable

xterm-kitty

### Installation

system package manager (pacman)

### How to reproduce the issue

nvim --clean 24</etc/hosts
:!ls /dev/fd 
:terminal 
i
cat /dev/fd/24
<C-d>
q
:!ls /dev/fd


### Expected behavior

Inside the terminal, file descriptor 24 should still be available, and `cat </dev/fd/24` should output the contents of /etc/hosts

If closing of file descriptors is intended behavior, then it should be better document (and I'd like a feature to override that). 

### Actual behavior

As soon as the `:terminal` is run, the file descriptor for 24 is closed. And the cat command prints that `/dev/fd/24` does not exist. The second `:!ls /dev/fd` command also no longer includes the 24 file descriptor (although the first one does). 

Interestingly, if higher numbered file descriptors are used (for example 63) it does work as expected. From experimentation, on my system the threshold appears to be 27.
Repository: terminal
Issue: [Terminal]: Extra info which only appear on Tooltip is not announced by Screen Reader for some controls throughout Terminal app.
Labels: Issue-Bug,Area-Accessibility,Product-Terminal,HCL-E+D,A11yWCAG,A11yUsable,HCL-WindowsTerminal,A11yCO

### Windows Terminal version

1.12.3472.0

### Windows build number

10.0.22504.1010

### Other Software

**Test Environment:**
OS: Windows 11 Version Dev (OS Build 22504.1010)
App: Windows Terminal Preview
Screen Reader: Narrator
Tool: Accessibility Insights for Windows Version 1.1.1741.1

### Steps to reproduce

**Repro Steps:**
1. Open Windows Terminal.
2. Open Settings page using 'Ctr+,'.
3. Open Narrator using 'Win + Ctrl + Enter' keys.
4. Then navigate to all controls whose have tooltip like 'Open JSON file' and observe the issue.

**User Experience:**
Screen Reader users UX will not be good if they will miss some important info which only appear on tooltips.

**Attachments:**
[Extra info which only appear on Tooltip is not announced by Screen Reader for some controls throughout Terminal app..zip](https://github.com/microsoft/terminal/files/7773131/Extra.info.which.only.appear.on.Tooltip.is.not.announced.by.Screen.Reader.for.some.controls.throughout.Terminal.app.zip)

### Expected Behavior

Extra info which only appears on Tooltip should be announced by Screen Reader for all controls throughout Terminal app.
i.e. For 'Open JSON file', Tooltip is 'Open your Settings.json file, Alt+ Click to open defaults.json file' and Screen Reader should announce something like this 'Open your Settings.json file, Alt+ Click to open defaults.json file 1 of 1'

### Actual Behavior

Extra info which only appears on Tooltip is not announced by Screen Reader for some controls throughout Terminal app.
i.e. For 'Open JSON file', Tooltip is 'Open your Settings.json file, Alt+ Click to open defaults.json file' and Screen Reader is only announcing 'Open JSON file 12 of 12'

**Observation:** 
Issue repro with NVDA Screen Reader
Narrator users have option to read tooltips using shortcut key 'Caps lock + 0' keys.
Repository: flutter
Issue: MaterialPageRoute incorrectly applies CupertinoPageRoute’s transition animation on iOS
Labels: platform-ios,framework,a: animation,f: material design,a: fidelity,f: cupertino,f: routes,team-design,triaged-design

If you use `MaterialPageRoute`, Flutter automatically adapts the transition animation depending on the platform: on Android it uses a transition from  `MaterialPageRoute`, and on iOS from `CupertinoPageRoute`. It's a good idea, but the implementation needs to be improved.

Although `MaterialPageRoute` adapts the transition animation depending on the platform, it uses the wrong animation speed for transition from `CupertinoPageRoute`: instead of 400 ms animation speed required for `CupertinoPageRoute`, it uses 300 ms animation speed which is only suitable for `MaterialPageRoute`. It seems to be no big deal, but this makes CupertinoPageRoute's behavior feel completely different than it should. It doesn't feel like a native transition animation.

I have a question: is it normal `MaterialPageRoute` behavior on iOS or is it a bug? What was the point of using a transition animation from `CupertinoPageRoute` in `MaterialPageRoute` on iOS? 

By the way, in one of the next releases there will be an improvement `CupertinoPageRoute`’s transition animation. Issue: #95511, PR: #95537. Briefly, the `CupertinoPageRoute` transition animation will have a new `barrierColor` like in native iOS. With the current implementation of how the transition animation works depending on platform, I guess those developers who are using `MaterialPageRoute` for both platforms won't be able to notice these improvements.
Repository: terminal
Issue: [Settings> Save]: Shortcut key should be defined for 'Save' and 'Discard Changes' control inside Settings page. 
Labels: Issue-Bug,Area-Accessibility,Product-Terminal,HCL-E+D,A11yUsable,HCL-WindowsTerminal,A11yCO

### Windows Terminal version

1.12.3472.0

### Windows build number

10.0.22504.1010

### Other Software

**Test Environment:**
OS: Windows 11 Version Dev (OS Build 22504.1010)
App: Windows Terminal Preview
Screen Reader: Narrator
Tool: Accessibility Insights for Windows Version 1.1.1741.1

### Steps to reproduce

**Repro Steps:**
1. Open Windows Terminal.
2. Open Settings page using 'Ctr+,'.
3. Make some changes inside given tabs.
4. Verify that whether shortcuts is given to save or discard changes.

**User Experience:**
UX will not be good if Users like Keyboard only, Screen Reader users are not able Save or Discard changes fast.

**Attachments:**
[Shortcut key should be defined for 'Save' and 'Discard Changes' control inside Settings page..zip](https://github.com/microsoft/terminal/files/7773208/Shortcut.key.should.be.defined.for.Save.and.Discard.Changes.control.inside.Settings.page.zip)


### Expected Behavior

Shortcut keys should be defined for 'Save' and 'Discard Changes' control inside Settings page. Shortcut keys should also be included with 'Save' or Discard' button Accessible Name & Tooltip. 
i.e. 'Ctrl+ S' to Save Changes and 'Ctrl + D' to Discard changes.

### Actual Behavior

Shortcut key is not defined for 'Save' and 'Discard Changes' control inside Settings page. Users have to navigate to Save or Discard button in order to save or discard changes.