sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: CUDA error: an illegal memory access was encountered (laugh_kernel at ...../cuda/CUDALoops.cuh:112)
Labels: module: cuda,triaged,module: cublas

## ❓ Questions and Help

### Please note that this issue tracker is not a help form and this issue will be closed.

We have a set of [listed resources available on the website](https://pytorch.org/resources). Our primary means of support is our discussion forum:

I got two errors and I have no idea to fix it. I need your help and I will appreciate it very much.
**ERROR 1**
Traceback (most recent call last):
  File "F:/CODE/BHC/main.py", line 175, in <module>
    p, r, f1 = main(configs, fold_id)
  File "F:/CODE/BHC/main.py", line 73, in main
    loss.backward()
  File "F:\Common_V\lib\site-packages\torch\tensor.py", line 198, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph)
  File "F:\Common_V\lib\site-packages\torch\autograd\__init__.py", line 100, in backward
    allow_unreachable=True)  # allow_unreachable flag
RuntimeError: CUDA error: CUBLAS_STATUS_EXECUTION_FAILED when calling `cublasSgemm( handle, opa, opb, m, n, k, &alpha, a, lda, b, ldb, &beta, c, ldc)` (gemm at ..\aten\src\ATen\cuda\CUDABlas.cpp:165)
(no backtrace available)

**ERROR 2**
File "F:/CODE/BHC/main.py", line 175, in <module>
    p, r, f1 = main(configs, fold_id)
  File "F:/CODE/BHC/main.py", line 73, in main
    loss.backward()
  File "F:\Common_V\lib\site-packages\torch\tensor.py", line 198, in backward
    torch.autograd.backward(self, gradient, retain_graph, create_graph)
  File "F:\Common_V\lib\site-packages\torch\autograd\__init__.py", line 100, in backward
    allow_unreachable=True)  # allow_unreachable flag
RuntimeError: CUDA error: an illegal memory access was encountered (launch_kernel at C:/w/b/windows/pytorch/aten/src\ATen/native/cuda/CUDALoops.cuh:217)
(no backtrace available)

The two errors occur when I run the program,  sometimes the ERROR 1 occurs and sometimes the ERROR 2 occurs. 
I explicitly set my device according related issue, but it does not work.  The errors occur when model computes gradients,  but i don't know how to check the problem.

**Runtime Environment**
python:3.7.7
torch:1.5.0+cu101
cuda: 10.1
cudnn:7.4.2
- [Discussion Forum](https://discuss.pytorch.org/)


cc @csarofeen @ptrblck @ngimel
Repository: create-react-app
Issue: create-react-app public, src,and scripts folder not created
Labels: priority: low (needs more information),stale,issue: install problem

Need Help
----------------------
use : `npx create-react-app react-app-test`

![image](https://user-images.githubusercontent.com/68770683/90751915-f0579c00-e300-11ea-861a-1fdbff20f5f4.png)
![image](https://user-images.githubusercontent.com/68770683/90752311-6c51e400-e301-11ea-84c7-bf9f49e01708.png)



Not installing src folder 
-------------------------------
Node v14.8.0
npm v6.14.8
Repository: opencv
Issue: Add colmap txt and bin importer
Labels: feature,future

COLMAP is one of the most popular open source SfM 3D reconstruction Tool with state of the art contributions from top researchers.

I think it would be nice if OpenCV would have the capabilities of importing a 3d reconstruction consisting of 3d map points, 2d-3d correspondences, intrinsics of the different cameras and camera poses. This would allow for building applications or refinements on top of the colmap results. Maybe this would be great for OpenCV 5?
Repository: TypeScript
Issue: Support generics on first class functions
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->
first class function generics

## Suggestion

<!-- A summary of what you'd like to see added or changed -->
I think first class functions are one of the most useful and important advantages that JavaScript has over other modern programming languages. While TypeScript's inference generally works pretty well on first class function arguments, it seems like changing generic arguments on a first class function (without wrapper functions) is not possible the way the generic argument syntax is parsed.

## Use Cases

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->
Any case where custom arguments don't need to be passed to a first class function, but generic type arguments do need to be passed. Currently, you have to either pass a first class function without generics or wrap a new function literal to use generics, otherwise you get `Argument of type 'T' is not assignable to parameter of type 'F'.(2345)`, `Expected X arguments, but got 0.`, and `An argument for 'T' was not provided.`.

## Examples

<!-- Show how this would be used and what the behavior would be -->
Desired syntax with type error: https://www.typescriptlang.org/play?#code/GYVwdgxgLglg9mABBAhgGzQdRlAFgHgBUAaRAJQD4AKFAJwHMAuRExUSZmh5wgSkQC8FcvwDeAWABQiRLQCmUELSTsIXerykBfKbsmrYCWQqVgAggGci1Ok0TgA1mDgB3MLx6IJ044uWJbAIsWbT1UDGw8KgAiOQAPFABbAAc0OWjSeT9zKwsoWhgwegpeIA

Workaround without type errors: https://www.typescriptlang.org/play?#code/GYVwdgxgLglg9mABBAhgGzQdRlAFgHgBUAaRAJQD4AKFAJwHMAuRExUSZmh5wgSkQC8FcvwDeAWABQiRLQCmUELSTsIXerykBfKbsmrYCWQqVgAggGci1Ok0TgA1mDgB3MLx6IJ044uWJbAIsWbT1UDGw8KgAiOQAPFABbAAc0OWjSdX4hX1NLfAsoWhgwehsGXl4gA

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: TypeScript
Issue: [Request] Warn on void && Short circuit
Labels: Suggestion,Awaiting More Feedback

## Suggestion

Typescript should warn that `expr` will never be evaluated in the following 

```ts
void [condition] && [expr]
```

## Example

```ts
const bar = () => void condition && foo();
```
Repository: flutter
Issue: Debugger: the stop button does not stop the app
Labels: e: device-specific,platform-android,tool,P2,team-android,triaged-android

## Steps to Reproduce

1. Start-debug any flutter app in Android Studio
2. Click the stop button

**Expected results:** IDE stops debugging and the app terminates

**Actual results:** IDE stops debugging but the app keeps working on the device

Command line `flutter run` and then 'q' works so it has to be an IDE/plugin issue.

<details>

Device: LG H873

  <summary>Logs</summary>

<!-- Finally, paste the output of running `flutter doctor -v` here. -->

```
C:\dev\pss-mobile-android>flutter doctor -v
[√] Flutter (Channel stable-logcat-fix, v1.17.0-4.0.pre.6, on Microsoft Windows [Version 10.0.18362.959], locale ru-UA)
    • Flutter version 1.17.0-4.0.pre.6 at C:\dev\flutter
    • Framework revision bffffb8cd7 (3 months ago), 2020-06-04 11:58:54 +0300
    • Engine revision b851c71829
    • Dart version 2.8.3


[√] Android toolchain - develop for Android devices (Android SDK version 29.0.3)
    • Android SDK at c:\tools\Android-SDK
    • Platform android-29, build-tools 29.0.3
    • ANDROID_HOME = c:\tools\Android-SDK
    • Java binary at: C:\tools\android-studio\jre\bin\java
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)
    • All Android licenses accepted.

[√] Android Studio (version 4.0)
    • Android Studio at C:\tools\android-studio
    • Flutter plugin version 47.1.2
    • Dart plugin version 193.7361
    • Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b01)

[√] VS Code, 32-bit edition (version 1.48.0)
    • VS Code at C:\Program Files (x86)\Microsoft VS Code
    • Flutter extension version 3.13.2

[√] Connected device (1 available)
    • LG H873 • LGH8736bb28167 • android-arm64 • Android 8.0.0 (API 26)

• No issues found!
```

</details>
Repository: TypeScript
Issue: Service worker types for service worker event listener
Labels: Bug,Help Wanted,Domain: lib.d.ts,PursuitFellowship

<!-- 🚨 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.7

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

serviceworker listener
serviceworker statechange
serviceworker onstatechange

**Code**

```ts
const updateServiceWorker = () => {
    const registrationWaiting = serviceWorkerRegistration?.waiting;

    if (registrationWaiting) {
      registrationWaiting.postMessage({ type: "SKIP_WAITING" });

      registrationWaiting.addEventListener("statechange", (e) => {
        if (e.target.state === "activated") {
          window.location.reload(true);
        }
      });
    }
  };
```

**Expected behaviour:**

Above event.target is` ServiceWorker` type

**Actual behaviour:**

Above event.target is `EventTarget` type
Repository: opencv
Issue: ONNX loader : does not support "ones_like"
Labels: feature,priority: low,category: dnn,category: dnn (onnx)

##### System information (version)
- OpenCV => 4.4
- Operating System / Platform => Ubuntu 18.04
- Compiler => gcc/g++ 8.4.0

##### Detailed description

Trying to load an onnx model and i get the stack trace:
```
opencv-4.4.0/modules/dnn/src/dnn.cpp:604: error: (-2:Unspecified error) Can't create layer "ones_like:0" of type "Tile" in function 'getLayerInstance'
```
Repository: rust
Issue: Unused `format!()`s are not optimised away
Labels: I-slow,T-compiler,A-mir-opt

I was slightly surprised to see that code like this:

```
pub fn foo() {
    format!("Hello {}", 4);
}
```

does not get optimised to a nop. It still calls `format!()`. This is surprising from a user point of view - you're calling a function, but it seems like it has no side effects and I don't use the result, so surely it should be removed?

I presume the reason it doesn't is that it allocates a `String` and heap allocation is considered to be a side effect? Whatever the reason I think that it would be nice if it was optimised.

If you're wondering about motivation, consider a debug trait with a default implementation that does nothing. You could call `debug.write(&format!(...))` and it would be fully optimised away for the default implementation.
Repository: react-native
Issue: .measure returns undefined on Android unless collapsable=false or onLayout are specified
Labels: Platform: Android,Needs: Triage :mag:,Needs: Repro

## Description
If you call `.measure` on a ref to a `View` on Android but you don't also have `onLayout` or `collapsable={false}` specified then `.measure` will call its success callback with `undefined`.

This issue got closed but it was never fixed https://github.com/facebook/react-native/issues/3282 
Seems it got reported again and was also closed without a fix https://github.com/facebook/react-native/issues/19103

The issue here is identical, a 5 year old bug! I suspect it's due to android removing "unnecessary" views when it shouldn't. If there's a `ref` the `view` should essentially have `collapsable={false}` automatically.

## React Native version:
```
System:
    OS: Windows 10 10.0.20190
    CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor
    Memory: 33.48 GB / 63.93 GB
  Binaries:
    Node: 10.18.1 - C:\dev\tools\nodejs\node.EXE
    Yarn: 1.22.4 - C:\dev\tools\nodejs\yarn.CMD
    npm: 6.14.7 - C:\dev\TaskHero\node_modules\.bin\npm.CMD
    Watchman: 4.9.4 - C:\dev\tools\watchman\watchman.EXE
  SDKs:
    Android SDK:
      API Levels: 28, 29
      Build Tools: 28.0.3, 29.0.3, 30.0.1
      System Images: android-24 | Google Play Intel x86 Atom, android-25 | Google APIs ARM EABI v7a, android-25 | Google APIs Intel x86 Atom_64, android-28 | Google Play Intel x86 Atom_64, android-29 | Google Play Intel x86 Atom_64, android-30 | Google APIs Intel x86 Atom_64, androi
d-R | Google Play Intel x86 Atom_64
      Android NDK: 21.0.6113669
  IDEs:
    Android Studio: Not Found
  Languages:
    Java: 12.0.2
    Python: 3.8.4
  npmPackages:
    @react-native-community/cli: ^4.10.1 => 4.10.1
    react: 16.13.1 => 16.13.1
    react-native: 0.63.2 => 0.63.2
  npmGlobalPackages:
    *react-native*: Not Found

```

## Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

1. Add a ref to a view on Android
2. Call .measure on that ref, values returned are undefined

## Expected Results
It should return the measurement results

## Snack, code example, screenshot, or link to a repository:
Not needed, can be reproduced immediately on any react native android project of any version
Repository: godot
Issue: Go to the defination shows wrong doc with the same identifier in diffrent bases. 
Labels: bug,topic:gdscript,topic:editor

**Godot version:** 3.2.2

**OS/device including version:** Linux

**Issue description:**   As the title says if I ctrl+click on `print` identifier in any base it always goes to `@GDScript.print`. It seems that this only happens with the global scope. 

**Steps to reproduce:**
1. Copy the script below and ctrl+click on `print`.

```gdscript
class One:
	static func print():
		pass

func _init():
	One.print() # Goes to @GDScript.print
	JSON.print(1) # Also goes to @GDScript.print
```
Repository: go
Issue: x/tools/gopls: consider moving methods inside its type in outline view
Labels: Thinking,FeatureRequest,gopls,Tools

It would be nice if we could look at some type in outline view and see all of the methods declared on that type in one place.

At the moment type and its methods separated

![Screenshot from 2020-08-18 10-26-29](https://user-images.githubusercontent.com/6453537/90483910-24369400-e13e-11ea-9acd-e935749eb440.png)
Repository: godot
Issue: RigidBody box collision shape failing collision detection through convex and concave shapes when impulse is applied, on Bullet
Labels: bug,confirmed,topic:physics

**Godot version:**
3.2.2-stable_win64; 3.2.3-beta1_win64; 3.2.3-rc3_win64;


**OS/device including version:**
Windows 10, 64bit


**Issue description:**
When applying a moderate to strong impulse to a RigidBody (BoxShape), the body will very often go through both ConvexPolygonShape and ConcavePolygonShape (created with Trimesh Collision Sibling and Single Convex Collision Sibling). This has been tested only on Bullet, for some reason impulse isn't being applied on GodotPhysics.
'continuous_cd' and 'can_sleep' have seemingly no effect, the issue happens regardless these being ticked or not.

To be clear, this issue doesn't happen if the collision shape it collides against is a BoxShape, even on very high impulse forces.


**Steps to reproduce:**
Press right a couple times in the attached project. You can press left and right, it will quickly go through the floor with visible jitter.

**Minimal reproduction project:**
[Coll bug.zip](https://github.com/godotengine/godot/files/5104508/Coll.bug.zip)

There are a few other issues with physics and collision but I couldn't find something describing this specifically, hopefully it's not a duplicate.

![coll_bug](https://user-images.githubusercontent.com/68266227/90821768-59eca000-e32b-11ea-9edf-b09b6a6cdf35.gif)
Repository: pytorch
Issue: backward for dense+sparse does not work
Labels: module: sparse,module: autograd,triaged

## 🐛 Bug


## To Reproduce
```
a=torch.randn(2,3).to_sparse().requires_grad_(True)
c=torch.randn(2,3)
sum2=c+a
loss=sum2.sum()
loss.backward()
```
results in 
```
Function AddBackward0 returned an invalid gradient at index 1 - expected type TensorOptions(dtype=float, device=cpu, layout=Sparse, requires_grad=false (default), pinned_memory=false (default), memory_format=(nullopt)) but got TensorOptions(dtype=float, device=cpu, layout=Strided, requires_grad=false (default), pinned_memory=false (default), memory_format=(nullopt))
Exception raised from validate_outputs at caffe2/torch/csrc/autograd/engine.cpp:622 (most recent call first):
frame #0: c10::Error::Error(c10::SourceLocation, std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >) + 0x7b (0x7fb71562896b in /mnt/xarfuse/uid-202799/443637f6-seed-nspid4026531836-ns-4026531840/libomnibus.so)
frame #1: torch::autograd::validate_outputs(std::vector<torch::autograd::Edge, std::allocator<torch::autograd::Edge> > const&, std::vector<at::Tensor, std::allocator<at::Tensor> >&, std::function<std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > (std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> > const&)> const&) + 0x13db (0x7fb705c28cdb in /mnt/xarfuse/uid-202799/443637f6-seed-nspid4026531836-ns-4026531840/libomnibus.so)
frame #2: <unknown function> + 0x7d8eb186 (0x7fb705c2a186 in /mnt/xarfuse/uid-202799/443637f6-seed-nspid4026531836-ns-4026531840/libomnibus.so)
```


cc @ezyang @SsnL @albanD @zou3519 @gqchen @vincentqb @aocsa
Repository: godot
Issue: Vulkan: Viewport's `keep_3d_linear` property not reimplemented yet
Labels: topic:rendering,topic:3d

**Godot version:** Git 4e52c75a981f3704a01f702ffd14cc626ea32ec7

**OS/device including version:** Fedora 31, GeForce GTX 1080 (NVIDIA 440.100)

**Issue description:** Viewport's `keep_3d_linear` property hasn't been reimplemented yet in the Vulkan renderer. That property is available in 3.2.2.

**Steps to reproduce:** Search for `keep_3d_linear` in the editor help.

**Minimal reproduction project:** N/A
Repository: flutter
Issue: The method 'getElementForInheritedWidgetOfExactType' was called on null
Labels: a: text input,framework,customer: money (g3),f: focus,P2,c: fatal crash,team-framework,triaged-framework

Internal: b/165559233

Stacktrace:

Thread 0 main thread CRASHED

```
NoSuchMethodError: The method 'getElementForInheritedWidgetOfExactType' was called on null.
Receiver: null

Tried calling: getElementForInheritedWidgetOfExactType()
at Actions._visitActionsAncestors	(actions.dart:457)
at Actions.invoke	(actions.dart:608)
at ShortcutManager.handleKeypress	(shortcuts.dart:330)
at _ShortcutsState._handleOnKey	(shortcuts.dart:472)
at FocusManager._handleRawKeyEvent	(focus_manager.dart:1625)
at RawKeyboard._handleKeyEvent	(raw_keyboard.dart:594)
at BasicMessageChannel.setMessageHandler.<anonymous closure>	(platform_channel.dart:75)
at BasicMessageChannel.setMessageHandler.<anonymous closure>	(platform_channel.dart:74)
at _DefaultBinaryMessenger.handlePlatformMessage	(binding.dart:283)
at _invoke3.<anonymous closure>	(hooks.dart:282)
at _rootRun	(zone.dart:1190)
at _CustomZone.run	(zone.dart:1093)
at _CustomZone.runGuarded	(zone.dart:997)
at _invoke3	(hooks.dart:281)
at _dispatchPlatformMessage	(hooks.dart:156)
```
Repository: pytorch
Issue: Remove warning, and update documentation.
Labels: module: docs,module: optimizer,triaged

As mentioned [here](https://github.com/pytorch/pytorch/pull/31125#issuecomment-673654283), the warning in LambdaLR should be removed and replaced by a simple note in the load/save state_dict documentation.

cc @jlin27 @vincentqb @gchanan
Repository: TypeScript
Issue: Show constructor jsdoc when constructing a class
Labels: Bug,Help Wanted,Domain: Quick Info,PursuitFellowship

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ, especially the "Common Feature Requests" section: https://github.com/Microsoft/TypeScript/wiki/FAQ

-->

## Search Terms

- jsdoc class
- tsdoc class
- tsdoc instances

## Suggestion

> apologize if this is a duplicate! 

I am not sure if this is new behavior or if I just somehow have not noticed it until now, but I noticed that the documentation (in vscode insiders) is not showing the class documentation when you use `new` to create the instance.  It does show if you add a `constructor` call and add docs to that, but it seems that it should show the actual class docs regardless. 

So my personal thought would be:

1. Always show the documentation for the class itself when the class name is referenced.
2. If `constructor` has documentation, also add that as well -- similar to how some other cases are handled when there are multiple levels of documentation (parameter docs for functions as example).

## Use Cases

- Better documentation as it makes sense you would always want to see the wider class documentation when you are using it throughout.  
- Less duplication - keep it DRY!

## Examples

```typescript
/**
 * The specified market was not found
 *
 * @extends NotFoundError
 * @statusCode 404
 */
export class MARKET_NOT_FOUND extends NotFoundError {
  public message = 'Market not found';

  public code = this.constructor.name;

  public name = this.code;

  public body = {
    code: this.code,
    message: this.message,
  };
}
```

So in the above case, the docs will show up when I do not preface with `new`:

![image](https://user-images.githubusercontent.com/15365418/90824134-ea63ba00-e304-11ea-9923-bdfc1e84de98.png)

but it is not shown when actually using the error:

![image](https://user-images.githubusercontent.com/15365418/90824162-f485b880-e304-11ea-9c53-b51e73745efc.png)

If I add in the following:

```typescript
/**
   * The constructor docs
   */
  constructor() {
    super();
  }
```

then it will show those docs...

![image](https://user-images.githubusercontent.com/15365418/90824231-154e0e00-e305-11ea-96dc-22179ca412e0.png)



## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [x] This wouldn't change the runtime behavior of existing JavaScript code
* [x] This could be implemented without emitting different JS based on the types of the expressions
* [x] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [x] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: excalidraw
Issue: Allow setting shouldForceLoadScene from url parameter
Labels: enhancement

I'd like to be able to force an iframe to load a new scene. It would be nice to be able to add a hash parameter to have it not pop up the warning.