sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: youtube-dl
Issue: Downloading 5 simultaneous Chaturbate livestreams results in lag/ stuttering
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.
-->

WRITE QUESTION HERE
Hi, I have a quick question. I regularly download livestream webcam shows from chaturbate (5 at a time/ simultaneously) but when I play the video files when they finish downloading, there is almost always lag at some parts of most of the videos. There seems to ALWAYS be a 3-10 second pause/ lag at about the 3 second mark when opening a video. I am on a 4g LTE wifi connection. Is my wifi speed the limiting factor here? Are there ANY useful flags/ commands that I can include with each download to make the downloads smoother (maybe something to make sure youtube-dl takes it time to download a livestream smoothly and forgo speed). Is there even such a thing? I see livestreams ALL OVER the internet and NONE of them seem to suffer from the stuttering/ lagging that I get with my videos. You guys are the Pros. What can I do?
Repository: opencv
Issue: The time spent on seamlessClone is seriously affected by the size of the input image.
Labels: question (invalid tracker),category: photo,incomplete,needs reproducer

I found a bug about the run time of seamlessClone.

This is my code：
	cv::resize(inImage, inImage,Size(936,936));  //Set the size of the input image

	hconcat(inImage, inImage, SplicingImage);
	vconcat(SplicingImage, SplicingImage, SplicingImage);
	Mat mask = 255 * Mat::ones(inImage.rows, inImage.cols, inImage.depth());
	Point centerPt = Point(SplicingImage.cols / 2, SplicingImage.rows / 2);
	seamlessClone(inImage, SplicingImage, mask, centerPt, SplicingImage, NORMAL_CLONE);

When I set the size of the input image to 937x937, it took about 5s. But when I set the input image size to 936x936, it took only 1.5s.In most cases, when I set my resolution to odd, it takes several times more time than setting it to even.Sometimes the opposite happens.I used three different pictures for the test.

opencv 4.2
Ubuntu 20.04.1 TLS
Repository: ant-design
Issue: Dropdown下拉菜单hover移动到菜单稍快，菜单会立即消失 |  Dropdown menu disappear
Labels: 🐛 Bug,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://ant.design/components/dropdown-cn/](https://ant.design/components/dropdown-cn/)

### Steps to reproduce
代码演示的第一个从Hover me菜单hover后稍快移动到菜单，菜单则消失
The first code demonstration 
Moves from the Hoverme button, menu disappears  quickly after hover

### What is expected?
菜单不消失
The menu does not disappear

### What is actually happening?
菜单消失
 the menu disappears

| Environment | Info |
|---|---|
| antd | 4.13.0 |
| React | React：v17.0.1 |
| System | window10 |
| Browser | 谷歌v 88.0.4324.190 |


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: create-react-app
Issue: After creating a React app with yarn dlx create-react-app, the first time I press yarn start to start it, I get an error.
Labels: needs triage,issue: bug report

## Use yarn 2 (yarnpkg/berry)
* in terminal
```
% yarn set version berry
% yarn dlx create-react-app apple
% cd apple
% yarn start
```
*  in browser
```
Failed to compile
Failed to load config "react-app" to extend from.
Referenced from: D:\Projects\apple\package.json
This error occurred during the build time and cannot be dismissed.
```

How do I solve this problem?

ps. yarn dlx create-next-app works fine.  only have a problem with the CRA
Repository: opencv
Issue: Temp file creation on Windows name conflict/race condition
Labels: bug,category: core,affected: 3.4,platform: win32

- OpenCV => 2.4.3 and later
- Operating System / Platform => Windows 
- Compiler => any

##### Detailed description

For context see [core/src/system.cpp](https://github.com/opencv/opencv/blob/f70e80a6bacec67842757ffbed7b9a643488388d/modules/core/src/system.cpp#L982)

The function cv::tempfile() uses [::GetTempFileNameA](https://docs.microsoft.com/en-us/windows/win32/api/fileapi/nf-fileapi-gettempfilenamea) to create a temp file. It immediately deletes it (see next line) instead of reserving it and only returns the filename. Other OpenCV process at the same time can create a temp file with the same name resulting in a name collision.

MS recommends in the remarks of using a GUID when many temp files are required.

Proposed solution: Use the already implemented [GetFileNameWinRT](https://github.com/opencv/opencv/blob/f70e80a6bacec67842757ffbed7b9a643488388d/modules/core/src/system.cpp#L198) on line 198, system.cpp
Repository: TypeScript
Issue: Incorrect ts(7053) error when updating json file
Labels: Needs Investigation

# Bug Report

I have strings stored in a json file. 
I did set  "resolveJsonModule": true, in the tsconfig.
I import the strings as follows:
import * as strings from '../languages/en.json';

Works perfectly.

When I add a string in the json file and I then try to use that new string, intellisense always gives me the ts(7053) error.

Everything builds and works but the code remains underlined as a problem.

The only workaround I found to get rid of the incorrect report is to close VSCode and reopen it.

Broken in TypeScript  v4.1.5
Works in TypeScript v4.0.5

VS Code
Version: 1.53.2
Commit: 622cb03f7e070a9670c94bae1a45d78d7181fbd4
Date: 2021-02-11T11:45:54.515Z
Electron: 11.2.1
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Darwin x64 20.3.0
Repository: rust
Issue: Associated types specified using equality are still ambiguous.
Labels: A-associated-items,T-compiler,C-bug

<!--
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.
-->

I tried this code:

```rust
pub trait A {
    type Foo;
}

pub trait B: A<Foo = <Self as B>::Foo> {
    type Foo;
    
    fn foo() -> Self::Foo;
}
```

The return type `Self::Foo` of `foo` should not be ambiguous, since `<Self as B>::Foo` is equal to `<Self as A>::Foo`. However, this code can't compile, and the error message is:

```plaintext
error[E0221]: ambiguous associated type `Foo` in bounds of `Self`
 --> src/main.rs:8:17
  |
2 |     type Foo;
  |     --------- ambiguous `Foo` from `A`
...
6 |     type Foo;
  |     --------- ambiguous `Foo` from `B`
7 |     
8 |     fn foo() -> Self::Foo;
  |                 ^^^^^^^^^ ambiguous associated type `Foo`
  |
help: use fully qualified syntax to disambiguate
  |
8 |     fn foo() -> <Self as B>::Foo;
  |                 ^^^^^^^^^^^^^^^^
help: use fully qualified syntax to disambiguate
  |
8 |     fn foo() -> <Self as A>::Foo;
  |                 ^^^^^^^^^^^^^^^^
```

### Meta
<!--
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.
-->

`rustc --version --verbose`:
```
rustc 1.50.0 (cb75ad5db 2021-02-10)
binary: rustc
commit-hash: cb75ad5db02783e8b0222fee363c5f63f7e2cf5b
commit-date: 2021-02-10
host: x86_64-apple-darwin
release: 1.50.0
```
Repository: godot
Issue: world_to_map() returns inconsistent values when using raycast
Labels: bug,confirmed,topic:physics

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:** 
<!-- Specify commit hash if using non-official build. -->
3.2.3-stable_x11.64 (Also tested in 3.1.2-stable_x11.64)

**OS/device including version:** 
<!-- Specify GPU model, drivers, and the backend (GLES2, GLES3, Vulkan) if graphics-related. -->
Manjaro 20.2.1 Nibia

**Issue description:**
<!-- What happened, and what was expected. -->
The `world_to_map()` sometimes return inconsistent values when using the `intersect_ray()` method. See the output from the image below:

![1](https://user-images.githubusercontent.com/9718665/109702413-f6152080-7b72-11eb-8326-a14de8c0e489.png)
![2](https://user-images.githubusercontent.com/9718665/109702419-f7dee400-7b72-11eb-941f-64d9d43eb7c2.png)

Looking the z axis from output you will see an inconsistent values between the first and second image.
I also tried to reproduce the `world_to_map` method, dividing the `result.position` by the `cell_size` and then using the ` floor()` method, but in both cases I get the same inconsistent value.

```phyton
	var space_state = get_world().direct_space_state
	var start = camera.project_ray_origin(crosshair.position)
	var end = start + camera.project_ray_normal(crosshair.position) * ray_length
        var cell_size = 2
	
	var result = space_state.intersect_ray(start, end, [self.get_rid()])
	if result and Input.is_action_just_pressed("ui_accept"):
		print(str(result.position) + " # WORLD SPACE")
		print(str(result.position / cell_size) + " # CELL COORDS")
		print(str((result.position / cell_size).floor()) + " # CELL COORDS with floor()s")
		print(str(grid_map.world_to_map(result.position)) + " # world_to_map()")
		print("====================")
```

**Steps to reproduce:**

- Create a GridMap with a basic box as a tile.
- Use the raycast to hit any face of the box.
- Get the `result` from the ray.
- Pass the `result.position` to the `world_to_map()`.
- Print the value.
- Repeat the process in another point in the box until you see an inconsistent value.

**Minimal reproduction project:**
<!-- A small Godot project which reproduces the issue. Drag and drop a zip archive to upload it. -->
[GridMapRaycastBug.zip](https://github.com/godotengine/godot/files/6062314/GridMapRaycastBug.zip)
Repository: flutter
Issue: EventChannel is not working when app is in background
Labels: platform-android,d: api docs,has reproducible steps,P2,team-android,triaged-android,found in release: 3.19,found in release: 3.22

I'm working on a Flutter plugin. Is it possible to use EventChannel in the background? Despite calling success on EventSink instance, on dart-side StreamBuilder is not able to receive the data. I'm not using an isolate in dart-side but I've created a Foreground Service in my plugin on the native side. eventSink's success method is getting called when app is in background, but [receiveBroadcastStream](https://api.flutter.dev/flutter/services/EventChannel/receiveBroadcastStream.html) is not receiving any data.

I'm using the latest stable release.
Repository: godot
Issue: Apple TV Guideline Problem
Labels: platform:ios,topic:porting

Hi,

Im trying publish my game on Apple TV but Apple is rejecting it because of this:

```
Guideline 4.0 - Design


We noticed your Apple TV app does not satisfy the requirements outlined in the Apple TV Human Interface Guidelines.

Specifically, pressing and holding the Menu button on the Siri remote does not take the user back to the Home screen.

Next Steps

To resolve this issue, please revise your app to ensure that it complies with the guides, specifications, and templates provided in the Apple TV Human Interface Guidelines.
```

Basically because of:

```
Specifically, pressing and holding the Menu button on the Siri remote does not take the user back to the Home screen.
```

Can anyone help me how can i do it using gdscript?
Repository: pytorch
Issue: [TorchScript Usability] Optional type does not support `x != None`
Labels: oncall: jit

## 🐛 Bug

Test case: [test-optional-none.py](https://github.com/penguinwu/hodgepodge/blob/master/TorchScriptStudy/bad-examples/test-optional-none.py)

TS issues the following errors:
```
The original call is:
  File "test-optional-none.py", line 5
def fn(a: Optional[int], val: int):
    if a != None:
       ~~~~~~~~~ <--- HERE
        return a+val
    else:
```

It seems to support `a == None` or `a is not None` (when `a` is of Optional type), but not `a != None`. This asymmetry is unintuitive to users.

## Desired behavior

`a != None` should be handled like `a is not None`.

Related to #50444

cc @gmagogsfm
Repository: pytorch
Issue: [TorchScript Usability] Instance attribute annotation does not seem to take effect
Labels: oncall: jit

## 🐛 Bug

Test case: [test-instance-attr-annotation.py](https://github.com/penguinwu/hodgepodge/blob/master/TorchScriptStudy/bad-examples/test-instance-attr-annotation.py)

In this example, instance attribute `x` is annotated to be `Optional[int]` at the class level, but the compiler does not seem to know that fact and produces the following error:
```
Wrong type for attribute assignment. Expected None but got int:
  File "test-instance-attr-annotation.py", line 11
        self.x = None
        if x > 0:
            self.x = x
            ~~~~~~~~~~ <--- HERE
```

Related to #50444

cc @gmagogsfm
Repository: ant-design
Issue: sustainable time for <Spin />
Labels: help wanted,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.

### What problem does this feature solve?
In many cases, we need a spinning icon to imply the refresh/reload action (which is what <Spin /> does). However, when refresh/reload time is too short to be noticed, we want to specify a minimum spinning time.

### What does the proposed API look like?
Specifies a minimum time in milliseconds for loading state (prevent blink)
```javascript
<Spin sustain={500}/>
```


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: pytorch
Issue: [codegen] Make it easier to codegen call to API
Labels: triaged,enhancement,module: codegen

Right now, the logic for how to call into ATen (e.g., a true `at::view` call, or a call to `at::redispatch`) is spattered throughout the codebase. For example, here is how autograd figures out how to make a redispatch call:

```
CALL_REDISPATCH = CodeTemplate("""\
at::redispatch::${api_name}(${unpacked_args})""")

...

            dispatch_key_set = 'ks & c10::after_autograd_keyset'
            call = CALL_REDISPATCH.substitute(
                api_name=cpp.name(
                    f.func,
                    faithful_name_for_out_overloads=True,
                ),
                unpacked_args=[dispatch_key_set] + list(unpacked_args))
```

there is a similar bit of logic in tracing type

```
    dispatcher_sig = DispatcherSignature.from_schema(f.func)
    dispatcher_exprs = dispatcher_sig.exprs()
    
    # code-generated tracing kernels plumb and recompute dispatch keys directly through the kernel for performance.
    # See Note [Plumbing Keys Through The Dispatcher] for details.
    dispatch_key_set = 'ks & c10::DispatchKeySet(c10::DispatchKeySet::FULL_AFTER, c10::DispatchKey::Tracer)'
    redispatch_args = ', '.join([dispatch_key_set] + [a.expr for a in dispatcher_exprs])
    
    assign_return_values = f'{tie_return_values(f)} = ' \
                           if f.func.kind() == SchemaKind.functional and f.func.returns else ''
    
    # Note that this calls the slow, dispatching variants of manual_cpp_binding ops.
    # We could probably work harder to ensure that the fast variants are called instead, but the perf benefit would be minimal.
    sig_group = CppSignatureGroup.from_native_function(f, method=False, fallback_binding=f.manual_cpp_binding)
    if sig_group.faithful_signature is not None:
        api_name = sig_group.faithful_signature.name()
    else:
        api_name = sig_group.signature.name()
    
    trace_body.append(TRACE_DISPATCH.substitute(
        assign_return_values=assign_return_values,
        api_name=api_name,
        unpacked_args=redispatch_args,
    ))

```

The logic is not *too* long, but it would be much better if there was a very short (maybe even one line) way to say "generate a call to redispatch given some bindings in scope). 

cc @bdhirsh @bhosmer @smessmer
Repository: pytorch
Issue: Ensure that nn.MHA and functional multi-head attention is supported by FX graph mode quantization
Labels: oncall: quantization,low priority,triaged,module: fx

Ensure that nn.MHA is supported by FX graph mode quantization.  Since this is a complex nn module, special handling might be required.



cc @jerryzh168 @jianyuh @jamesr66a @vkuzo @jgong5 @Xia-Weiwen @leslie-fang-intel @ezyang @SherlockNoMad @EikanWang @wenzhe-nrv @raghuramank100 @dzhulgakov
Repository: rust
Issue: Incorrect HashMap visualization in WinDbg
Labels: A-debuginfo,C-bug,S-blocked

I tried to debug this program in WinDbg.

```rust
use std::fmt;

#[derive(PartialEq, Eq, Hash)]
struct Student {
    name: String,
    country: String,
}

impl fmt::Display for Student {
    fn fmt(&self, f: &mut fmt::Formatter<'_>) -> fmt::Result {
        write!(f, "({}, {})", self.name, self.country)
    }
}

fn main() {
    use std::collections::HashMap;
    let mut map = HashMap::new();
    let s1 = Student { name: String::from("Tom"), country: String::from("UK") };
    let s2 = Student { name: String::from("Alex"), country: String::from("US")};
    map.insert(s1, 10);
    map.insert(s2, 8);
    for (k,v) in map.iter() {
        println!("{}, {}", k, v);
    }
}
```

When examining the variable ```map``` in WinDbg, I got this visualization:
![image](https://user-images.githubusercontent.com/74681961/109536734-f4643380-7a72-11eb-9f29-e90dfcc0128a.png)

The screenshot illustrates two problems:
+ The ```Name``` column displays meaningless numeric values (0x0, 0x1) instead of the keys.
+ The ```Value``` column displays error messages instead of the values.

These two problems are filed under the same bug report since I've discovered that they can both be tied to the same cause - WinDbg's failure to perform the casting of ```base.table.ctrl.pointer``` to ```tuple&lt;$T1, $T2&gt;*``` in HashMap's natvis entry.
```rust
<Item Name="{((tuple&lt;$T1, $T2&gt;*)base.table.ctrl.pointer)[-(i + 1)].__0}">((tuple&lt;$T1, $T2&gt;*)base.table.ctrl.pointer)[-(i + 1)].__1</Item>
```

### Meta
This bug is discovered on ```rustc 1.52.0-dev``` and  WinDbg debugger engine version: 10.0.21306.10
Repository: go
Issue: x/tools/go/packages: error position paths are relative to Config.Dir, should be absolute
Labels: NeedsInvestigation,Tools

The go command reports errors relative to its working directory. go/packages passes them on as packages.Errors, e.g. in https://github.com/golang/tools/blob/7a079fcd7976efee71404a62f2b2be0bbc34f3a5/go/packages/golist.go#L706.

In packages.Package, all paths are absolute, so it's surprising to get relative paths in the errors. I think they should be absolute too.

@matloob
Repository: rust
Issue: Track Windows 7 vs. delete-on-close fixes
Labels: A-LLVM,O-windows,T-compiler,C-bug,O-windows-7

Rust #82605 reverted LLVM [D81803](https://reviews.llvm.org/D81803), "Avoid setting the delete-on-close bit if a TempFile doesn't reside on a local drive," because that regressed Windows 7 in #81051.

That change was meant to fix [LLVM PR42623](https://bugs.llvm.org/show_bug.cgi?id=42623), which also references Rust #54216. It would be nice if some Windows user could verify if that was fixed on a nightly where we still had the change, roughly 2021-01-13 through 2021-02-28. But since it left Windows 7 unable to create _any_ archives, we decided that regression was worse than the fix.

[LLVM 48378](https://bugs.llvm.org/show_bug.cgi?id=48378) also reported a Windows 7 regression that seems to be the same root cause. Perhaps there will be a new update that makes it all work for Windows 7, so we can have the best of both. Another possibility suggested in a [compiler meeting](https://zulip-archive.rust-lang.org/238009tcompilermeetings/76458weeklymeeting2021021854818.html#226830050) was to use runtime platform detection, skipping D81803's code on Windows 7, but letting us still have the bug fix on newer Windows.

Alternatively, when Rust eventually decides to stop supporting Windows 7, we can just drop the revert / reapply D81803.
Repository: godot
Issue: Crash after setting probe data
Labels: bug,topic:rendering,crash

**Godot version:**
3.2.4.rc.custom_build. 8385a0d8a

**Issue description:**
After setting probe data, Godot crash with this backtrace
```
[1] /lib/x86_64-linux-gnu/libc.so.6(+0x46210) [0x7fac21f38210] (??:0)
[2] VisualServerScene::_gi_probe_fill_local_data(int, int, int, int, int, VisualServerScene::GIProbeDataCell const*, VisualServerScene::GIProbeDataHeader const*, VisualServerScene::InstanceGIProbeData::LocalData*, Vector<unsigned int>*) (/mnt/Miecz/godot3.2/servers/visual/visual_server_scene.cpp:2461)
[3] VisualServerScene::_setup_gi_probe(VisualServerScene::Instance*) (/mnt/Miecz/godot3.2/servers/visual/visual_server_scene.cpp:2529 (discriminator 1))
[4] VisualServerScene::render_probes() (/mnt/Miecz/godot3.2/servers/visual/visual_server_scene.cpp:3391)
[5] VisualServerRaster::draw(bool, double) (/mnt/Miecz/godot3.2/servers/visual/visual_server_raster.cpp:110 (discriminator 1))
[6] VisualServerWrapMT::draw(bool, double) (/mnt/Miecz/godot3.2/servers/visual/visual_server_wrap_mt.cpp:104)
[7] Main::iteration() (/mnt/Miecz/godot3.2/main/main.cpp:2131)
[8] OS_X11::run() (/mnt/Miecz/godot3.2/platform/x11/os_x11.cpp:3628)
[9] /usr/bin/godot(main+0x125) [0x16ff90b] (/mnt/Miecz/godot3.2/platform/x11/godot_x11.cpp:57)
[10] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xf3) [0x7fac21f190b3] (??:0)
[11] /usr/bin/godot(_start+0x2e) [0x16ff72e] (??:?)
```
**Steps to reproduce:**
Run project

**Minimal reproduction project:**
[GDScript.zip](https://github.com/godotengine/godot/files/6064089/GDScript.zip)
Repository: go
Issue: x/pkgsite: add directories to "Jump to" list
Labels: NeedsInvestigation,pkgsite,UX

For modules with many packages/directories like the standard library It would be helpful if directories were listed in the "Jump to" dialog.

### Example use case

Visit https://pkg.go.dev/std
Press "f"
Type "template", and the "Jump to" dialog would list:
- html/template
- text/template
- text/template/parse