sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: godot
Issue: Discrepancy between physics joints behavior and editor gizmo
Labels: bug,topic:editor,topic:physics

**Godot version:**
stable 3.2.2
Also reproduced in master cf03f90fa8d8e0fadcf22741ab75220665578371

**OS/device including version:**
Windows 10

**Issue description:**
Hinge and Cone joint editor gizmos don't show reliably how the joints behave in physics, which makes them extremely difficult to setup.

PhysicalBone joints also have similar issues.

**Steps to reproduce:**
See minimal repro projects below. The following steps refer to the different test case scenarios from these projects.
Run the scene to compare the joints behavior with the gizmos in the editor.

Case 1: Hinge at origin (red color)
The gizmo doesn't show up at all in the editor when the joint is at the same position as its child rigid body.

Case 2: Rotated Hinge with limits (green color)
The gizmo shows 180° of freedom at the back, the child rigid body rotates in a 180° range on the right side instead.
(can be reproduced with both Bullet and GodotPhysics)

Case 3: ConeTwist at origin with swing 45° & twist 180° (blue color)
The gizmo shows only a vertical line, but the child rigid body can rotate with 180° range around X axis (swing axis).
(can be reproduced with both Bullet and GodotPhysics)

Case 4: ConeTwist with swing 20° & twist 180° (yellow color)
The gizmo shows a cone with twist on Y axis and swing on X/Z axes according to the settings, but the child rigid body can swing with 180° range around X axis and the twist seems limited on Y axis (looks like axes are inverted).
(can be reproduced with both Bullet and GodotPhysics)

Case 3 & 4: In both cases, the child rigid body is fixed to (0, 0, 0) instead of using the offset from the joint when using Bullet (can't reproduce with GodotPhysics).

**Minimal reproduction project:**
3.2:
[joint-gizmo-3.2.zip](https://github.com/godotengine/godot/files/5001677/joint-gizmo-3.2.zip)

4.0:
[joint-gizmo.zip](https://github.com/godotengine/godot/files/5001679/joint-gizmo.zip)
Repository: pytorch
Issue: Not able to run quantized model on android
Labels: oncall: mobile

I have a quantized model which works on intel cpu and can be traced but fails to be run on android. Float32 model works fine on mobile though. Unfortunately, I cannot share the model. I get the following error:

`java.lang.IllegalArgumentException: at::Tensor scalar type is not supported on java side`


## Environment

PyTorch version: 1.7.0.dev20200727
Is debug build: No
CUDA used to build PyTorch: 10.2

OS: Ubuntu 20.04 LTS
GCC version: (Ubuntu 8.4.0-3ubuntu2) 8.4.0
CMake version: version 3.16.3

Python version: 3.7
Is CUDA available: Yes
CUDA runtime version: 10.2.89
GPU models and configuration: GPU 0: GeForce GTX 1070
Nvidia driver version: 440.100
cuDNN version: Could not collect

Versions of relevant libraries:
[pip3] numpy==1.19.0
[pip3] torch==1.7.0.dev20200727
[pip3] torchvision==0.8.0.dev20200727
[conda] Could not collect

cc @jerryzh168 @jianyuh @dzhulgakov @raghuramank100 @jamesr66a @vkuzo
Repository: youtube-dl
Issue: Add support for RCN as MSO
Labels: 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 2020.07.28. 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 **2020.07.28**
- [x] I've searched the bugtracker for similar feature requests including closed ones


## 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.
-->

Currently youtube-dl does not support RCN as a MSO -- the nature of the authentication pass through looks similar to some of the other username/pw MSOs, although I have been unable to figure out the code to get it to work on my own machine. According to wikipedia, RCN is the 11th largest cable provider, and it is the one I use.
Repository: youtube-dl
Issue: Support get thumbnail for Weibo 
Labels: 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 2020.07.28. 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])
-->

- [ ] I'm reporting a feature request
- [ ] I've verified that I'm running youtube-dl version **2020.07.28**

## 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.
-->

I tried to download video from https://weibo.com/1878335471/Jd7tqEund
The video downloaded successfully. However, it does not return the thumbnail.
I also try `youtube-dl --get-thumbnail https://weibo.com/1878335471/Jd7tqEund` but it doesn't return anything. 
Please consider supporting thumbnail for weibo video. Thank you
Repository: godot
Issue: Instancing of a scene does not instance a new ConcavePolygonShape in a collision shape
Labels: topic:core,documentation

**Godot version:**
3.2.2.stable

**OS/device including version:**
ubuntu 18.04

**Issue description:**
If you use a scene to procedurally generate static bodies using the SurfaceTool and the `shape.set_faces()` function, then it comes as a surprise to learn that each time you instance a new one it over-writes the triangles that are assigned to the concave collision shape

This is a very difficult bug to discover, particularly when your procedural shapes are reasonably similar and there's something about the physics that doesn't look right.  

The work-around is easy.  Put `$CollisionShape.shape = ConcavePolygonShape.new()` in the `_ready()` function of the static body.  The current behavior of not applying the deep-copy to this Collision object when the scene is instanced is not functionally useful.  This might be a special case, however.  Maybe the other pre-configured shapes (box, cylinder) are sufficiently constrained that they can be shared, because it is not their purpose to have procedural geometry inserted into them.

Animated gif shows two procedurally generated ramp static bodies with cubes rolling down them, where the collision shape of the steeper ramp has overwritten the collision shape of the shallow ramp.
![out](https://user-images.githubusercontent.com/677254/88942434-2e254f80-d282-11ea-94ed-c2fd36a3a793.gif)

**Steps to reproduce:**
See below.

**Minimal reproduction project:**
[collisionclonebug.zip](https://github.com/godotengine/godot/files/5002231/collisionclonebug.zip)
Repository: flutter
Issue: [webview_flutter] Leaking FLTJavaScriptChannel objects on iOS
Labels: platform-ios,c: performance,p: webview,package,perf: memory,has reproducible steps,P2,found in release: 2.2,found in release: 2.5,team-ios,triaged-ios

In my app I have a view with a WebView widget powered by the webview_flutter package. This view gets popped onto and off of the Navigator based on user interaction with the app.

I have discovered that repeatedly pushing and popping this view causes FLTJavaScriptChannel objects to leak:

After pushing one web view on the stack: 
<img width="234" alt="image" src="https://user-images.githubusercontent.com/1566468/88944445-bdb70800-d25a-11ea-9cb0-640e3fcfa13d.png">

After pushing and popping the web view repeatedly:
<img width="257" alt="image" src="https://user-images.githubusercontent.com/1566468/88944738-1a1a2780-d25b-11ea-8fa2-2d2852224a1b.png">

Output of `flutter doctor -v`:

```
[✓] Flutter (Channel unknown, 1.19.0-4.3.pre, on Mac OS X 10.15.6 19G73, locale en-US)
    • Flutter version 1.19.0-4.3.pre at /Users/alex/Development/Flutter/flutter
    • Framework revision 8fe7655ed2 (4 weeks ago), 2020-07-01 14:31:18 -0700
    • Engine revision 9a28c3bcf4
    • Dart version 2.9.0 (build 2.9.0-14.1.beta)


[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    • Android SDK at /Users/alex/Library/Android/sdk
    • Platform android-29, build-tools 29.0.2
    • ANDROID_HOME = /Users/alex/Library/Android/sdk
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 11.6)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 11.6, Build version 11E708
    • CocoaPods version 1.8.4

[✓] Android Studio (version 4.0)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)

[✓] VS Code (version 1.47.3)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.12.2

[✓] Connected device (1 available)
    • iPhone SE (2nd generation) • 0DA65E22-4B6F-4724-B8F1-458ADC344A93 • ios • com.apple.CoreSimulator.SimRuntime.iOS-13-6 (simulator)

• No issues found!
```
Repository: pytorch
Issue: Proper testing of `nn.Module` loading backward compatibility
Labels: module: nn,module: tests,module: serialization,triaged

Even though we recommend against saving `nn.Module` and save only the state dict to avoid this kind of issues, we actually have code that make it (mostly) work.
This code should be tested.

A couple of things to keep in mind:
- We have multiple file formats that all should be tested
- How old should the "old model" be? 
- How do we actually test that? Should we do something based on the nightly build like the backward compatibility checks or should we bundle a saved model into the git repo to be able to test older models?

cc @albanD @mruberry @VitalyFedyunin
Repository: pytorch
Issue: Instance norm annotation is incorrect
Labels: high priority,triage review,oncall: jit,days

See #41361 for background

Fix instance norm annotation



cc @ezyang @gchanan @zou3519 @suo @gmagogsfm
Repository: go
Issue: x/tools/refactor/eg: test case claims it should be failing, but it isn't.
Labels: NeedsInvestigation,Tools,Refactoring

### What version of Go are you using (`go version`)?

1.14

### Does this issue reproduce with the latest release?

Sure.

### What did you do?

`go test`

### What did you expect to see?

A test failure.

### What did you see instead?

The test passed.

This might seem like it's not surprising, but:

```
	// Should be no match however currently matches due to:
	// https://golang.org/issue/8584
	// Will start failing when this is fixed then just change golden to
	// No match pointer indirect
	// a.Lock()
	a.Lock()
```

That issue has been fixed for a long time, but apparently it's still matching. I don't yet understand the code's design intent well enough to know whether this comment is wrong, or there's a new/different bug, or ???
Repository: vscode
Issue: Custom editor issues: save and undo
Labels: bug,custom-editors

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version: 1.47.3
- OS Version: Fedora 32

I've been experiencing some intermittent issues related to both save and undo operations on the custom editor that I'm working on.
I also managed to reproduce them on the Pawdraw sample. Please refer to the steps below.
Notice that, these issues do not occur 100% of the time but, eventually, they will if these steps are stressed enough.  

**Issue A - Save operation**
1. Open a pawDraw file: fileX
2. Open another pawDraw file: fileY
3. Go back to fileX and make an edit
4. Go to fileY and make an edit
5. Save fileY (ctrl+S)
_Notification Error: Failed to save 'fileY.pawDraw': Canceled_

**Issue B - Undo operation**
_Notification Info: Could not undo 'Stroke' because there is already an undo or redo operation running._
when executing similar steps as in Issue A, i.e., editing, undoing and going back and forth between 2 files.

Please let me know if you need any further information.

/cc @mjbvz
Repository: TypeScript
Issue: Checking union type where key is enum tricks compiler
Labels: Bug

<!-- 🚨 STOP 🚨 STOP 🚨 STOP 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!--
Please try to reproduce the issue with the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  3.9.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
enum refinement
checking interface enum

**Code**

```ts
// A *self-contained* demonstration of the problem follows...
// Test this by running `tsc` on the command-line, rather than through another build tool such as Gulp, Webpack, etc.
enum Fish {
    blue= 1,
    red= 2
}

enum Crab {
    purple= 2
}

interface IFish {
    type: Fish,
    name: string,
}

interface ICrab {
    type: Crab,
    shell: string
}

const crab = {type: Crab.purple, shell: "hard"}

function determineAnimal(animal: ICrab | IFish) {
    if (animal.type === Fish.red) {
        console.log("fish")
        console.log(animal.name)
    } else if (animal.type === Crab.purple) {
        console.log("crab")
        console.log(animal.shell)
    } else {
        console.log("fell through")
    }
}

determineAnimal(crab)
```

**Expected behavior:** The program does not typecheck because checking against the enum does not prove the animal is an IFish

**Actual behavior:** The program typechecks and incorrectly determines the type of the crab, logging undefined.

**Playground Link:** [link](https://www.typescriptlang.org/play/?ssl=1&ssc=1&pln=34&pc=22#code/KYOwrgtgBAYglgZwBZQN4CgpagIwDZjAC8UAjADSbYBOwAJiQEzoC+66okUAwtQIY40VLAAcw1EXmJRmbdHBAAXYNQBmfAMbAoASXjIh2KIoCeI4AC5YiJJSMg+ES1ASLqCgOaU5C5Ws3aOrwChtim5lbBOHbYyMB4eFau7iAerOwaAPYgrlAa-IIkqOHOUQB0YhJS5C5I8YlQAERIfNR0jXKqYCAainDZUHTAfhAKwACCIHAQfHgAFHxTMw1BBVAAPrr6SACUoVhwqlALS7NlJVBEV9bIZbR0exhGRlk5mVJleJkec42qNo0dsJnq8EO9gJ9vidpmcHE4gUYWFB4ghtIdjosYXhzmZtFcSOVKpJgI9gS9smCPl8fo18gJAWTsKDwZCfpjlmU4gkEdgkSjtE9nlhmVSoX96sYkNRMmAPEgGYj0ughiMxpMsXM6TgdkA) 

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: flutter
Issue: [Windows] ☂️  Add support for Arm64 as a target
Labels: c: new feature,framework,engine,platform-windows,a: desktop,P3,platform-target-arm,team-windows,triaged-windows

https://github.com/flutter/flutter/issues/53120 tracks supporting Windows arm64 as a development environment; this is for being able to build Flutter Windows applications that run on arm64.

This would require:
* [x] https://github.com/flutter/flutter/issues/129649
* [x] Dart support for Windows arm64: https://github.com/dart-lang/sdk/issues/47824
* [ ] Dart support for cross-compiling Windows arm64 from x64 (since there are few Windows arm64 devices, requiring one for building would be problematic; for initial test purposes support without cross-compiling would be useful though)
* [x] Engine build support for arm64: https://github.com/flutter/engine/pull/35962
* [x] CI and uploaded artifacts: https://github.com/flutter/engine/pull/38739, https://flutter-review.googlesource.com/c/recipes/+/38132)
* [x] https://github.com/flutter/flutter/issues/129804
* [x] https://github.com/flutter/flutter/issues/129805
* [x] https://github.com/flutter/flutter/issues/129806
    * [ ] https://github.com/flutter/flutter/issues/134083, to allow promoting Windows Arm64 tests out of `bringup`
    * [ ] https://github.com/flutter/flutter/issues/136378
    * [ ] https://github.com/flutter/flutter/issues/141986, to allow pre-submit Windows Arm64 tests
* [ ] https://github.com/flutter/flutter/issues/129813
* [ ] https://github.com/flutter/flutter/issues/137161
* [ ] https://github.com/flutter/flutter/issues/129807
* [ ] https://github.com/flutter/flutter/issues/129808
* [ ] https://github.com/flutter/flutter/issues/136417
* [ ] https://github.com/flutter/flutter/issues/139949
Repository: PowerToys
Issue: Fix SA0001 violations
Labels: Issue-Bug

From stylecop enabling, SA0001 can be fixed by reading the docs :)

https://github.com/DotNetAnalyzers/StyleCopAnalyzers/blob/master/documentation/SA0001.md
Repository: opencv
Issue: Extendible parameters in OpenCV functions
Labels: evolution

The discussion thread for https://github.com/opencv/opencv/wiki/OE-34.-Named-Parameters
Repository: pytorch
Issue: RuntimeError: ProcessGroupNCCL does not support recv (torch-nightly)
Labels: oncall: distributed,feature,triaged,module: nccl

## 🐛 Bug

pytorch recently upgraded the nccl version to 2.7.3 https://github.com/pytorch/pytorch/pull/40622, which has support for point-to-point communication such as send and recv. However, I encounter `RuntimeError: ProcessGroupNCCL does not support recv` when using a nccl backend for send and recv. `torch.cuda.nccl.version()` returns `273`.

## Stack trace

```
  File "/private/home/sijun/projects/CrypTen/crypten/mpc/provider/ttp_provider.py", line 75, in generate_binary_triple
    c = TTPClient.get().ttp_request("binary", device, size0, size1)
  File "/private/home/sijun/projects/CrypTen/crypten/mpc/provider/ttp_provider.py", line 203, in ttp_request
    comm.get().recv(result, ttp_rank, self.comm_group)
  File "/private/home/sijun/projects/CrypTen/crypten/communicator/communicator.py", line 223, in logging_wrapper
    return func(self, *args, **kwargs)
  File "/private/home/sijun/projects/CrypTen/crypten/communicator/distributed_communicator.py", line 123, in recv
    dist.recv(result.data, src=src, group=group)
  File "/private/home/sijun/.conda/envs/torch_preview/lib/python3.8/site-packages/torch/distributed/distributed_c10d.py", line 751, in recv
    pg.recv([tensor], group_src_rank, tag).wait()
RuntimeError: ProcessGroupNCCL does not support recv
```
<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

## Environment

 - PyTorch Version (e.g., 1.0): torch-nightly (1.7.0)
 - OS (e.g., Linux): Linux
 - How you installed PyTorch (`conda`, `pip`, source): conda
 - Build command you used (if compiling from source): 
 - Python version: 3.8.3
 - CUDA/cuDNN version: 10.1
 - GPU models and configuration:
 - Any other relevant information:

## Additional context

<!-- Add any other context about the problem here. -->


cc @ngimel @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @xush6528 @osalpekar @jiayisuse @agolynski
Repository: go
Issue: x/pkgsite: various UI cleanups due to new fixed header on details page
Labels: NeedsFix,pkgsite

+ [x] The version string in the sticky header is all uppercase, which renders as `GO1.14.6` on standard library packages. This should preserve the original casing
+ [x] The `:target` selector in stylesheet.css (and in sidenav.css) that’s used to ensure that anchor targets aren’t scrolled below the sticky headers isn’t needed for pages that don’t have them (and need to be adjusted for the new sticky header on the details pages)
+ [x] Should the homepage should have smart quotes around example searches? (unrelated to header but just noticed it)
+ [x] `overflow: auto` on the html and body elements (used to fix an iOS focus bug) is causing  other focus issues and the fixed header to appear over scrollbars
+ [x] Search text is shown on mobile when the search input is collapsed
+ [x] Ensure sidenav height is properly calculated
+ [ ] The IntersectionObserver logic to show the sticky header will trigger it if the inline nav is below the fold. Ensure it only shows if it is off the top of the screen
+ [ ] The search bar in the primary header looks a bit off re: spacing on iOS
+ [ ] Determine whether to keep uppercase “Package”, “Command”, etc.
+ [ ] Adjust IntersectionObserver margin on fixed header to have it show earlier
+ [ ] Fixed header hack to fix focus bug on iOS Safari breaks tap-to-top behavior

/cc @julieqiu @jamalc
Repository: node
Issue: Buffer created from Buffer.from gives wrong length
Labels: buffer

<!--
Thank you for reporting an issue.

This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help


Please fill in as much of the template below as you're able.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name
-->

* **Version**:  v12.12.0
* **Platform**: Darwin DANMAC.local 18.7.0 Darwin Kernel Version 18.7.0: Tue Aug 20 16:57:14 PDT 2019; root:xnu-4903.271.2~2/RELEASE_X86_64 x86_64
* **Subsystem**: buffer

### What steps will reproduce the bug?

let a=new Uint8Array(10);
let b=Buffer.from(a,0,5);
console.log(a.length); (prints 10)
console.log(b.length); (prints 10, expected 5)

If a.buffer is passed in, the correct result is given.   

Either the expected result should occur (5), or a TypeError should be thrown since otherwise a very counter-intuitive result is given.

<!--
Enter details about your bug, preferably a simple code snippet that can be
run using `node` directly without installing third-party dependencies.
-->

### How often does it reproduce? Is there a required condition?

### What is the expected behavior?

<!--
If possible please provide textual output instead of screenshots.
-->

### What do you see instead?

<!--
If possible please provide textual output instead of screenshots.
-->

### Additional information

<!--
Tell us anything else you think we should know.
-->