sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: SkeletonIK bone snapping near full chain extension - max_iterations and min_distance seem to have no effect
Labels: bug,topic:core,topic:animation,topic:3d

### Godot version

3.3.2.stable, 3.2.stable

### System information

Windows 10, GLES 3

### Issue description

In a simple 3 bone chain (example: top leg, bot leg, foot), moving the target slowly from full extension to contraction (and vice versa) will display clear snapping artifacts, as seen below. This happens both in editor and in a running game. It happens with magnet disabled too, but it's a bit different, I will focus on the issue when magnet is enabled as this is Godot's pole target for IK and very common to use.

The properties 'max_iterations' and 'min_distance' seem to have no effect in the solver, not just regarding the snapping, they seem to do nothing at all, at least nothing visible. I see no difference between 'max_iterations = 0' or 'max_iterations = 500', same thing with 'min_distance'.


### Steps to reproduce

For this example I'm using the 3D IK Demo's model. All I've done is add a SkeletonIK node and a target node, and set the properties.

Open ik_issue.tscn, enable IK after selecting the SkeletonIK, then slowly move the target up and down, passing through the point of full extension of the chain.

### Minimal reproduction project

[IK snapping issue.zip](https://github.com/godotengine/godot/files/6620027/IK.snapping.issue.zip)

Tree:
![tree](https://user-images.githubusercontent.com/79580741/121268179-5d9ae480-c8b5-11eb-9e66-c2af31faf5b3.PNG)

Properties:
![properties](https://user-images.githubusercontent.com/79580741/121268172-58d63080-c8b5-11eb-8bc6-f43b7b574101.PNG)

Demonstration of issue - notice the bones fast movement/snapping several times before smoothing out:
https://user-images.githubusercontent.com/79580741/121268502-021d2680-c8b6-11eb-9057-6d33e336ca8e.mp4
Repository: youtube-dl
Issue: Tango.me live stream support
Labels: 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.06.06. If it's not, see https://yt-dl.org/update on how to update. Issues with outdated version will be REJECTED.
- Make sure that all provided video/audio/playlist URLs (if any) are alive and playable in a browser.
- Make sure that site you are requesting is not dedicated to copyright infringement, see https://yt-dl.org/copyright-infringement. youtube-dl does not support such sites. In order for site support request to be accepted all provided example URLs should not violate any copyrights.
- Search the bugtracker for similar site support 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 new site support request
- [x] I've verified that I'm running youtube-dl version **2021.06.06**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] I've searched the bugtracker for similar site support requests including closed ones


## Example URLs

<!--
Provide all kinds of example URLs support for which should be included. Replace following example URLs by yours.
-->

- Single video: https://www.tango.me/live/nearby (just choose any livestream)



## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

Please can you make it save tango.me livestreams...
Repository: godot
Issue: Grid moves along a selected object in the 2D editor under certain conditions
Labels: discussion,topic:editor,topic:2d

### Godot version

3.3.2.stable.official

### System information

Windows 10 GLES 3 GTX1060

### Issue description

In 2D view. 
1/ When "View" > "Always Show Grid" option is ticked **and** "Use Grid Snap" is **not** selected, if the user enters "Select Mode" ,"Move Mode" , "Rotate Mode" or "Scale Mode" and tries to move, rotate or scale, an object on the grid, the grid moves along the object. 

2/When "View" > "Always Show Grid" option is ticked **and** "Use Grid Snap" **is**  selected, if the user enters "Rotate Mode" or "Scale Mode" and tries rotate or scale, an object on the grid, the grid moves along the object. 

The grid should never follow the object, it is very confusing because and it is not how it works in classic 2D editors.

### Steps to reproduce

Please see issue description.

### Minimal reproduction project

_No response_
Repository: pytorch
Issue: Add a lint rule to recommend TORCH_CHECK(false) over throw std::runtime_error
Labels: triaged,better-engineering

## 🚀 Feature
When throwing exceptions in the C++ codebase, we should prefer to use TORCH_CHECK(false, "foo") over throw std::runtime_error("foo") since the former can provide a detailed C++ stacktrace when `TORCH_SHOW_CPP_STACKTRACES=1` is enabled, but the latter will not as it does not go through c10's exception handling logic here: https://github.com/pytorch/pytorch/blob/master/torch/csrc/Exceptions.h#L51. Thus we could have a lint rule that enforces this at code review time.

## Motivation
Using `TORCH_CHECK` with `TORCH_SHOW_CPP_STACKTRACES=1` helps investigate crashes with detailed logs, but this is quite easy to overlook in code review and it is natural for developers to instead use `throw std::runtime_error` especially if they are newer to the PyTorch codebase. Having a lint rule/recommendation would be helpful for encouraging this practice in the codebase.
Repository: ant-design
Issue: Tree 组件 设置 titleRender dragable 拖拽后属性 每次拖拽 都会发出N次 titleRender 执行
Labels: help wanted,Inactive

- [ ] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[https://github.com/ant-design/ant-design](https://github.com/ant-design/ant-design)

### Steps to reproduce
看了下rc-tree 组件源码 拖拽over 监听时间中 没有加节流 导致疯狂setState 触发render N次  导致 titleRender 爆炸 卡顿问题   请优化下

### What is expected?
 每次拖拽 直接setState 这个问题那么明显 居然还不修复

### What is actually happening?
拖拽事件里的执行setState加入节流

| Environment | Info |
|---|---|
| antd | undefined |
| React | 16.8.6 |
| System | macOS |
| Browser | chrome |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: TypeScript
Issue: super reference in private method throws 
Labels: Bug,Rescheduled

# Bug Report



### 🔎 Search Terms

private, super

### 🕗 Version & Regression Information

v4.3.2, also tested with nightly in playground

works with ESNext setting (which just strips out the types), Babel, V8


### ⏯ Playground Link

https://www.typescriptlang.org/play?ts=4.3.2#code/MYGwhgzhAECC3QN4CgEIC4FMLoBQEolU0SAnTdAV1IDtoByLHe4hAX2Q+VEhgCFomAB5YaAExjwUJAMQAzAPYKCREmQrU6ESgAdMpAHRM8+VtC4kARmFIrpahOSq1o6ABYBLCAflKCZji5gBRocaEtoAF5oGkwAd2g+AgNrW1NuEIgFEEwDEAUAc1xLfCA

### 💻 Code

```ts
class A  {
    test() {
        return 'test'
    }
}

class B extends A {
    #foo() {
        return super.test()
    }

    bar() {
        return this.#foo()
    }
}

const b = new B().bar()

console.log(b)

// [ERR]: "Executed JavaScript Failed:" 
// [ERR]: 'super' keyword unexpected here 
```

### 🙁 Actual behavior

throws error

### 🙂 Expected behavior

prints 'test'
Repository: material-ui
Issue: [TimePicker] ClockNumber has weird focus outline on Safari
Labels: new feature,component: time picker

When open a TimePicker, Safari renders weird focus outline.

I think this behavior was introduced by #26400.

- [x] The issue is present in the latest release.
- [x] I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

## Workaround 

https://github.com/mui-org/material-ui/blob/a533d062df191a95478a663a9f926de4f94b3046/packages/material-ui-lab/src/ClockPicker/Clock.tsx#L270-L279

```css
div[role="listbox"] {
  outline: none;
}
```

## Current Behavior 😯

### Chrome/Firefox

<img width="333" alt="current: chrome/firefox" src="https://user-images.githubusercontent.com/199728/121294143-d9357980-c927-11eb-93ad-a3e52df02596.png">

### Safari

<img width="334" alt="current: safari" src="https://user-images.githubusercontent.com/199728/121294418-552fc180-c928-11eb-993b-bbebdc62130c.png">

## Expected Behavior 🤔

### Chrome/Firefox/Safari

<img width="333" alt="expected" src="https://user-images.githubusercontent.com/199728/121294143-d9357980-c927-11eb-93ad-a3e52df02596.png">

## Steps to Reproduce 🕹

<!--
  Provide a link to a live example (you can use codesandbox.io) and an unambiguous set of steps to reproduce this bug.
  Include code to reproduce, if relevant (which it most likely is).

  You should use the official codesandbox template as a starting point: https://material-ui.com/r/issue-template-next

  If you have an issue concerning TypeScript please start from this TypeScript playground: https://material-ui.com/r/ts-issue-template

  Issues without some form of live example have a longer response time.
-->

Steps:

1. Open https://next.material-ui.com/components/time-picker/#basic-usage.
2. Open TimePicker.
3. (If you are using Safari) Some weird focus outline appears.


## Your Environment 🌎

- Safari 14.1.1 (16611.2.7.1.4)
- Mobile Safari (iPadOS 14.5.1)
Repository: flutter
Issue: [Windows] Constant "update_windows: InvalidatedReasonKind.inputChanged..." due to flutter checked out with CR-LF line-endings, instead of LF
Labels: tool,platform-windows,a: desktop,has reproducible steps,P3,found in release: 2.3,team-windows,triaged-windows

<!--  Thank you for contributing to Flutter!

      If you are filing a bug, please add the steps to reproduce, expected and actual results.

      If you are filing a feature request, please describe the use case and a proposal.

      If you are requesting a small infra task with P0 or P1 priority, please add it to the
      "Infra Ticket Queue" project with "New" column, explain why the task is needed and what
      actions need to perform (if you happen to know). No need to set an assignee; the infra oncall
      will triage and process the infra ticket queue.
-->

Roughly 3-4 secs (and maybe more due to it's effect) are lost in:

```
[+2796 ms]   [+2796 ms] unpack_windows: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated contents: d:\p\flu\flutter\packages\flutter_tools\lib\src\build_system\targets\windows.dart,D:\p\wicked_gpu\windows\flutter\ephemeral\flutter_windows.dll,D:\p\wicked_gpu\windows\flutter\ephemeral\flutter_windows.dll.exp,D:\p\wicked_gpu\windows\flutter\ephemeral\flutter_windows.dll.pdb}
[ +957 ms]   [ +957 ms] kernel_snapshot: Starting due to {InvalidatedReasonKind.inputChanged: The following inputs have updated contents: d:\p\flu\flutter\packages\flutter_tools\lib\src\build_system\targets\common.dart,d:\p\flu\flutter\bin\internal\engine.version,d:\p\flu\flutter\bin\internal\engine.version,d:\p\flu\flutter\bin\internal\engine.version}
```

Once I've changed my flutter installation (d:\p\flu\flutter) do be LF, instead of CR-LF the issue went away.

Logs before: 
[log.txt](https://github.com/flutter/flutter/files/6621339/log.txt)

Logs after:
[log3.txt](https://github.com/flutter/flutter/files/6621341/log3.txt)

(in addition I've removed the `_phony_` target from the CMakeFile.txt to speed up further, but that maybe questionable practice for now. I'm trying to speed up certain development on the C/C++ side).
Repository: ant-design
Issue: Form.List rules disables deeply nested Form.Item rules
Labels: Inactive

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### Reproduction link
[![Edit on CodeSandbox](https://codesandbox.io/static/img/play-codesandbox.svg)](https://codesandbox.io/s/antd-reproduction-template-forked-vq2ou)

### Steps to reproduce
- First press Submit and see that "No Letter A" and "No Letter Z" boxes are validated. Console outputs 4 errors from 2 "No Letter Z" from different list items, and 2 "No Letter A" from the same list item but on different deeper nested page.
- Enable the switch up top to add `rules` to the outer `Form.List`.
- Press Submit again and this time "No Letter A" rules are **not activated**. Console output 3 errors (4 + 1 - 2) instead of expected 5 errors. (4 + 1)

### What is expected?
Expected the state after switch on the `Form.List` `rules` to add one more rule to count list items, console should output 5 errors. 

### What is actually happening?
Instead this rule also disables deeply nested `Form.Item` `rules`, "No Letter A" rule is no longer active. Console only outputs 3 errors.

| Environment | Info |
|---|---|
| antd | 4.16.2 |
| React | 17.0.2 |
| System | MacOS |
| Browser | Edge |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: neovim
Issue: treesitter incredible slow with single line big json due to hotspot in nvim_buf_set_extmark
Labels: bug,performance,treesitter

<!-- Before reporting: search existing issues and check the FAQ. -->

- `nvim --version`:   
v0.5.0-dev+1357-g192f89ea1
                               Build type: RelWithDebInfo
                                                         LuaJIT 2.1.0-beta3

- Operating system/version:
archlinux x64
- Terminal name/version:
xterm(also happened when using nvim-qt)

[ ] `vim -u DEFAULTS` (version: ) behaves differently (not tried)

### Steps to reproduce using `nvim -u NORC`
only happen if using with nvim-treesitter, while using nvim -u NORC, nvim highlight head parts of json and not hang.

### Actual behaviour

while using with tree-sitter, nvim incredible slow when opening very big json file(in one line),  profile shows nvim_buf_set_extmark consume most of CPU time. after a while, even after file is highlighted, cursor move still very slow, especially when cursor hit object start '{'

### Expected behaviour

tree-sitter highlight should be responsive.

minimal config:
```
set nocompatible
filetype off


call plug#begin('~/.vim/bundle')

"vim-scripts

Plug 'nvim-treesitter/nvim-treesitter', {'do': ':TSUpdate'}
call plug#end()


lua << EOF


require'nvim-treesitter.configs'.setup {
    ensure_installed = "maintained",
    highlight = {
        enable = true
    },
    indent = {
        enable = true
    }
}

EOF

```


while nvim hanging, I've run profiler attached, profile result shows that nvim_buf_set_extmark consume 96% cpu time.
source code shows that src/nvim/api/buffer.c 1497 and 1687 each consume about 50% cpu time.
```
  1492   size_t len = 0;
  1493   if (line < 0 || line > buf->b_ml.ml_line_count) {
  1494     api_set_error(err, kErrorTypeValidation, "line value outside range");
  1495     return 0;
  1496   } else if (line < buf->b_ml.ml_line_count) {
  1497     len = STRLEN(ml_get_buf(buf, (linenr_T)line+1, false));             <------------------------ hotspot1
  1498   }



  1685  if (col2 >= 0) {
  1686     if (line2 >= 0 && line2 < buf->b_ml.ml_line_count) {
  1687       len = STRLEN(ml_get_buf(buf, (linenr_T)line2 + 1, false));          <--------------------------hotspot2
  1688     } else if (line2 == buf->b_ml.ml_line_count) {
  1689       // We are trying to add an extmark past final newline
  1690       len = 0;
  1691     } else {
  1692       // reuse len from before
  1693       line2 = (int)line;
  1694     }


```
Repository: vscode
Issue: Please enable emmet.action.updateImageSize in pug.
Labels: feature-request,emmet

<!-- ⚠️⚠️ Do Not Delete This! feature_request_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->

<!-- Describe the feature you'd like. -->
Repository: excalidraw
Issue: Allow the host to customise the keyboard shortcuts
Labels: discussion,package:excalidraw
Repository: pytorch
Issue: cuda streams run sequentially, expected to run parallel
Labels: module: performance,module: cuda,triaged

I'v read the official tutorial here: https://pytorch.org/docs/stable/notes/cuda.html#cuda-streams
and try to use multiple streams to make submodules of my model run in parallel, here is a simplified example:

```python
import torch
import torch.nn as nn
import torch.cuda as cuda
from torch.autograd.profiler import profile


def run():
    device = torch.device(0)

    s1 = cuda.Stream(device=device)
    s2 = cuda.Stream(device=device)

    x = torch.rand(size=(100, 100)).to(device)
    w1 = torch.rand(size=(100, 100)).to(device)
    w2 = torch.rand(size=(100, 100)).to(device)
    
    cuda.synchronize()

    with cuda.stream(s1):
        out1 = x.matmul(w1)

    with cuda.stream(s2):
        out2 = x.matmul(w2)
    
with profile() as prof:
    run()

prof.export_chrome_trace('./prof_streams.json')
```
It is expected that code under context `s1` and `s2` should run parallel, but my profiling shows that is run sequentially:

![Screen Shot 2021-06-09 at 3 57 40 PM](https://user-images.githubusercontent.com/17561508/121315993-71892980-c93b-11eb-9721-f302ff9838fc.png)







cc @ngimel @VitalyFedyunin
Repository: PowerToys
Issue: [Run-Plugin] [Windows Settings] Add unit tests
Labels: Help Wanted,Area-Tests,Run-Plugin

### Provide a description of the new feature / enhancement

We decided to do unit tests as separate pr into master
Repository: go
Issue: x/tools/gopls: code action to extracting an interface for usage
Labels: FeatureRequest,gopls,Tools,Refactoring

Consider the following program:

```
type bar struct {}
func (b *bar) x() {}
func (b *bar) y() {}
type Foo struct {
    bar *bar
}
func (f *Foo) baz() {
    f.b.y()
}
```

Now assume we would like to test `foo` and for this we'd want to mock `bar`. The recommended way of doing this is to extract the way that `bar` is used into an interface and use that in lieu of `bar` in `foo`.

```
type bar struct {}
func (b *bar) x() {}
func (b *bar) y() {}

type barI interface {
    y()
}
type Foo struct {
    bar barI
}
func (f *Foo) baz() {
    f.b.y()
}
```

Note that only `y()` was extracted.
Supporting such a code action in gopls would make life a lot easier for devs who write unit tests.
This is at least viable to implement for unexported members, as no new methods can be added in other packages which access this member.
Repository: node
Issue: Rare crashes in inspect mode
Labels: inspector

* **Version**: v16.3.0
* **Platform**: Linux inspiron-7577 4.15.0-142-generic #146~16.04.1-Ubuntu SMP x86_64 x86_64 x86_64 GNU/Linux

### What steps will reproduce the bug?
Start an app using inspect mode. After some time the app crashes occasionally.
I used rawkit but I don't think it matters.

### How often does it reproduce? Is there a required condition?
Rarely. It happened twice using 16.2 and once with 16.3 out of many restarts.

### What is the expected behavior?
The app should not crash in inspect mode

### What do you see instead?

```
#
# Fatal error in , line 0
# Check failed: !regexp_stack_->is_in_use().
#
#
#
#FailureMessage Object: 0x7ffdcdfd0440
 1: 0xb831a1  [node]
 2: 0x1c1e754 V8_Fatal(char const*, ...) [node]
 3: 0x12016c1 v8::internal::RegExpStackScope::RegExpStackScope(v8::internal::Isolate*) [node]
 4: 0x11f4e71 v8::internal::NativeRegExpMacroAssembler::Execute(v8::internal::String, int, unsigned char const*, unsigned char const*, int*, int, v8::internal::Isolate*, v8::internal::JSRegExp) [node]
 5: 0x11f4ff2 v8::internal::NativeRegExpMacroAssembler::Match(v8::internal::Handle<v8::internal::JSRegExp>, v8::internal::Handle<v8::internal::String>, int*, int, int, v8::internal::Isolate*) [node]
 6: 0x1205098 v8::internal::RegExpImpl::IrregexpExecRaw(v8::internal::Isolate*, v8::internal::Handle<v8::internal::JSRegExp>, v8::internal::Handle<v8::internal::String>, int, int*, int) [node]
 7: 0x120558f v8::internal::RegExpImpl::IrregexpExec(v8::internal::Isolate*, v8::internal::Handle<v8::internal::JSRegExp>, v8::internal::Handle<v8::internal::String>, int, v8::internal::Handle<v8::internal::RegExpMatchInfo>, v8::internal::RegExp::ExecQuirks) [node]
 8: 0x125b705 v8::internal::Runtime_RegExpExec(int, unsigned long*, v8::internal::Isolate*) [node]
 9: 0x16147d9  [node]
Illegal instruction (core dumped)
```

### Additional information
Didn't experience this issue prior to Node v16
Repository: excalidraw
Issue: Add F2 keyboard shortcut to edit text boxes
Labels: enhancement,discussion

Hi! It would be really practical to implement the F2 keyboard shortcut for when one grabs a text box and wants to edit it. It is a very common shortcut and avoids changing to the mouse for the double click already available. Very happy with Excalidraw, great tool!
Repository: electron
Issue: [Bug]: `BrowserWindow.getBounds()` cannot be restored as they were in this case with multiple monitors and differing scale levels
Labels: bug :beetle:,component/BrowserWindow,has-repro-gist,12-x-y,stale

### Preflight Checklist

- [X] I have read the [Contributing Guidelines](https://github.com/electron/electron/blob/master/CONTRIBUTING.md) for this project.
- [X] I agree to follow the [Code of Conduct](https://github.com/electron/electron/blob/master/CODE_OF_CONDUCT.md) that this project adheres to.
- [X] I have searched the [issue tracker](https://www.github.com/electron/electron/issues) for a feature request that matches the one I want to file, without success.

### Electron Version

12.0.10

### What operating system are you using?

Windows

### Operating System Version

Windows 10, version 19043

### What arch are you using?

x64

### Last Known Working Electron version

_No response_

### Expected Behavior

A window can be asked for `getBounds` and be restored with these values when restarting to preserve the location on screen. 

### Actual Behavior

The window restores wrongly.

### Testcase Gist URL

https://github.com/electron/electron/files/6624616/Archive.zip

### Additional Information

**Steps:**
* attach a laptop with screen resolution 2560x1440 and 150% scale to an external monitor with 2560x1440 resolution and 100% scale
* configure displays to extend and not copy the desktop (primary monitor is laptop left and secondary monitor is external right)
* run a simple hello world fiddle to opens a window
* instrument the code to `console.log(mainWindow.getBounds())` e.g. from a `setInterval`
* move the window to the second monitor right corner so that it snaps and split in half of the screen size
* close the window
* note the `x`, `y`, `width` and `height` values printed
* start the fiddle again, this time setting `x`, `y`, `width` and `height` values in the creation options

=> 🐛  the window does not appear as it was before

This does not reproduce when the 150% scaling is turned off on the laptop so it seems to be related to the fact that one display has scaling turned on while the other does not.