sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: "q." command (history of dot-repeatable actions)
Labels: enhancement,core,multicursor

### Actual behaviour
I like the functionality of `q /` and `q :` where it will display a list of past executed searches/commands. There are many times where I am doing some edits and would like to repeat that action with `.` later in normal mode somewhere else, however often times I end up performing some other edit action so `.` would no longer be relevant but if I could type `q .` then retrieve a list of most recently used editing actions then I would have at my fingertips all past actions and it would be awesome to use anyone at my command

### Expected behaviour
Typing `q .` would bring up a list of past editing actions that I can press enter to execute immediately just like how `q /` would bring up a list of past searches or `q :` would bring up a list of past executed commands.
Repository: go
Issue: crypto/tls: improve server-side (lack of) renegotiation docs and error message
Labels: Documentation,help wanted,NeedsFix

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.5 linux/amd64
</pre>

### Does this issue reproduce with the latest release?

yes

### What operating system and processor architecture are you using (`go env`)?
`amd64/linux`

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->

I am unable to renegotiate successfully using TLS 1.2 to a Go server I wrote. https://play.golang.org/p/Q39eh8PVAOP. After starting the server, I connect using openssl:
 `openssl s_client -connect 172.16.28.75:10000 -tls1_2`. Following a successful handshake, and some test messages going through, I start a renegotiation by sending `R` in the openssl client session. The renegotiation fails because the Go server expects a `helloRequestMessage` as the first message in the renegotiation while the`openssl` client sends a `clientHelloMessage` as the first message in the renegotiation.


### What did you expect to see?

A successful renegotiation as demonstrated when running the same server using `openssl s_server -key /home/vagrant/easy-rsa/easyrsa3/pki/private/server.key -cert /home/vagrant/easy-rsa/easyrsa3/pki/issued/server.crt -accept 10000`.

And output from renegotiation on the client: 
```
R
RENEGOTIATING
depth=0 CN = server
verify error:num=20:unable to get local issuer certificate
verify return:1
depth=0 CN = server
verify error:num=21:unable to verify the first certificate
verify return:1
```

### What did you see instead?

On the server: 
```
$ go run test.go
2019/12/26 15:30:25 New connection
2019/12/26 15:30:26 tls: received unexpected handshake message of type *tls.clientHelloMsg when waiting for *tls.helloRequestMsg
exit status 1
```

On the client: 
```
---
R
RENEGOTIATING
4684979820:error:140043F2:SSL routines:CONNECT_CR_SRVR_HELLO:sslv3 alert unexpected message:/BuildRoot/Library/Caches/com.apple.xbs/Sources/libressl/libressl-47.11.1/libressl-2.8/ssl/ssl_pkt.c:1200:SSL alert number 10
4684979820:error:140040E5:SSL routines:CONNECT_CR_SRVR_HELLO:ssl handshake failure:/BuildRoot/Library/Caches/com.apple.xbs/Sources/libressl/libressl-47.11.1/libressl-2.8/ssl/ssl_pkt.c:585:
```
Repository: vscode
Issue: Auto save & new line prevents undo from working
Labels: bug,undo-redo

- Version: 1.41.0
- Commit: 9579eda04fdb3a9bba2750f15193e5fafe16b959
- Date: 2019-12-11T17:58:38.338Z
- Electron: 6.1.5
- Chrome: 76.0.3809.146
- Node.js: 12.4.0
- V8: 7.6.303.31-electron.0
- OS: Darwin x64 19.2.0

Steps to Reproduce:

1. set `"files.trimFinalNewlines": true` and `"files.autoSave": "afterDelay"`; _edit: instead set `"files.insertFinalNewline": true` to follow POSIX conventions_
2. move the caret to the very end of the file
3. insert a string at the very end of a file
4. a new line is automatically added
5. try to undo step 3 will remove the new line, which is then added again

Does this issue occur when all extensions are disabled?: Yes
Repository: rust
Issue: panic=abort testing / subprocess testing
Labels: T-libs-api,C-tracking-issue,Libs-Tracked

This is the tracking issue for `-Zpanic-abort-tests` and related functionality.

Specifically, this flag switches the default test strategy of (loosely) a thread per test to a process per test, and implements the associated functionality of collecting process failures and treating that as passing/failing the test. It also includes a currently unstable option in test binaries, `--force-run-in-process`.

This was originally added in https://github.com/rust-lang/rust/pull/64158 and Cargo support landed in https://github.com/rust-lang/cargo/pull/7460.
Repository: flutter
Issue: Remove "dartpad" mode in snippet generator, and just put dartpad for all snippets
Labels: team,framework,d: api docs,P2,team-framework,triaged-framework

cc @RedBrogdon @gspencergoog 

While we're at it, we should probably rename "snippet" and "sample" to be more intuitive. I always think of "snippet" as being something too small to compile, and "sample" as being an example that can be tested, which is the opposite of reality as far as I can tell.
Repository: godot
Issue: Addon zipped with windows 10 unable to load because of required ZIP version
Labels: bug,topic:core,topic:editor,confirmed,topic:thirdparty

**Godot version:**
Godot_v3.1.1-stable_win64

**OS/device including version:**
WIn10

**Issue description:**
 editor/editor_asset_installer.cpp:175 - Condition ' !dir_map.has(ppath) ' is true. Continuing..:

**Steps to reproduce:**
1. create addon
2. use right click -> send to -> Compressed (zipped) folder
3. AssetLib -> Import

**Minimal reproduction project:**
[test.zip](https://github.com/godotengine/godot/files/4004017/test.zip)

Related Issue: the imported addon will be added to the root project folder
1. download addon
https://godotengine.org/asset-library/asset/457
https://github.com/samdze/godot-modifiers-plugin/archive/4e88b9812c26d35673d6c12198aeb2f8cb2d9425.zip
2. import addon
Repository: godot
Issue: Transparent + no culling + deep parallax depth crashes editor
Labels: bug,topic:rendering,confirmed,crash

**Godot version:**
Godot 3.2 beta 4

**OS/device including version:**
Windows 10

**Issue description:**
Transparent + no culling + deep parallax depth combination in SpatialMaterial crashes editor. I *think* it displays correctly in editor's main viewport and runtime, but if you try to see mesh preview (not material preview) in inspector, editor crashes without any error message.

**Steps to reproduce:**
- Add SpatialMaterial to a mesh
- Set transparent `true`, select cull mode `disable`
- Enable depth, and enable Deep Parallax and add depth texture
- Try to see mesh preview in the inspector panel

**Minimal reproduction project:**
[SpatialCrash.zip](https://github.com/godotengine/godot/files/4004441/SpatialCrash.zip)
Repository: youtube-dl
Issue: https://study.com/
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 2019.12.25. 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])
-->

- [ ] I'm reporting a new site support request
- [ ] I've verified that I'm running youtube-dl version **2019.12.25**
- [ ] I've checked that all provided URLs are alive and playable in a browser
- [ ] I've checked that none of provided URLs violate any copyrights
- [ ] 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://study.com/academy/topic/the-evolution-of-organizational-behavior.html 
- Single video: https://study.com/academy/topic/the-evolution-of-organizational-behavior.html
- Playlist: https://study.com/academy/course/anatomy-physiology-course.html


## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

WRITE DESCRIPTION HERE
Repository: pytorch
Issue: update embedding at indices, other than those passed as input, in the case of sparse tensors
Labels: module: sparse,module: nn,triaged,enhancement

when we use,
```
x = nn.Embedding(10, 5, sparse=True)
```
then, only the embeddings at indices that are passed as input get updated, for example,
```
y = x(torch.LongTensor([0])).sum()
y.backward()
for param in x.parameters():
  print(param.grad)
```
gives
```
tensor(indices=tensor([[0]]),
       values=tensor([[1., 1., 1., 1., 1.]]),
       size=(10, 5), nnz=1, layout=torch.sparse_coo)
```
but if we want to update embedding of words in our vocabulary that our model predicted, then there is no way to do that, or changing requires_grad for a word that is not passed as input is also not possible, that is doing something like,
```
x.index[1].requires_grad = True
x.index[8].requires_grad = True
```
cannot be done, and only embedding of indices that are passed as input to this sparse tensor get updated.
there is no way to update embedding of a word that is not passed as input when using sparse embedding, and if we set sparse=False, then it will update all word embedding.

cc @vincentqb
Repository: flutter
Issue: Allow specifying --user-data-dir for chrome launch
Labels: c: new feature,tool,platform-web,P3,team-web,triaged-web

i want to use --user-data-dir save my user data ,how to do ?

like this

`
flutter run -d chrome --web-port=8686 --user-data-dir=~/Documents/chrome
`
Repository: pytorch
Issue: pytorch out of memory when calculation squared difference of unfold
Labels: module: memory usage,triaged

## 🐛 Bug

> RuntimeError: CUDA out of memory. Tried to allocate 90.73 GiB (GPU 0; 1.96 GiB total capacity; 12.11 MiB already allocated; 1.13 GiB free; 1.89 MiB cached)

## To Reproduce

Steps to reproduce the behavior:
```

import torch

x = torch.rand(1,3,1000,1000).cuda()
print(x.shape)
t = torch.rand(1,3,100,100).cuda()
print(t.shape)

y = x.unfold(dimension=2, size=t.shape[2], step=1).unfold(dimension=3, size=t.shape[3], step=1)
print(y.shape)

ssd = torch.einsum('xcijkl,xckl->xcij', y, t)
ssd *= - 2
ssd += torch.einsum('xcijkl, xcijkl->xcij', y, y)
ssd += torch.einsum('xcij, xcij', t, t)
```


## Environment

> Collecting environment information...
> PyTorch version: 1.2.0
> Is debug build: No
> CUDA used to build PyTorch: 10.0.130
> 
> OS: Ubuntu 19.10
> GCC version: (Ubuntu 9.2.1-9ubuntu2) 9.2.1 20191008
> CMake version: Could not collect
> 
> Python version: 3.7
> Is CUDA available: Yes
> CUDA runtime version: Could not collect
> GPU models and configuration: GPU 0: GeForce 940MX
> Nvidia driver version: 435.21
> cuDNN version: Could not collect
> 
> Versions of relevant libraries:
> [pip3] numpy==1.16.3
> [pip3] pytorch-ignite==0.1.2
> [pip3] torch==1.2.0
> [pip3] torchsummary==1.5.1
> [pip3] torchvision==0.4.0
> [conda] Could not collect

When I try to calculate the sum of squared difference between an image and a template I get the error out of memory. Even on cpu its not working.

> RuntimeError: [enforce fail at CPUAllocator.cpp:64] . DefaultCPUAllocator: can't allocate memory: you tried to allocate 97416120000 bytes. Error code 12 (Cannot allocate memory)

I can do the same thing with opencv with no problems.

```
import numpy as np
import cv2

x = np.random.uniform(size=(1000,1000,3))
x = np.array(x*255., dtype=np.uint8)
print(x.shape)
t = np.random.uniform(size=(100,100,3))
t = np.array(t*255., dtype=np.uint8)
print(t.shape)


ssd = cv2.matchTemplate(x, t, cv2.TM_SQDIFF)
print(ssd.shape)
```

cc @fmassa
Repository: pytorch
Issue: Use of Sequence collections for abstract classes in Dataset
Labels: feature,module: dataloader,triaged

## 🚀 Feature
Using the sequence (or any other similar Python abstract class) for the `Dataset` class in order to tackle the note in lines 30-32 of `torch.utils.data.dataset`:

```python
    # No `def __len__(self)` default?
    # See NOTE [ Lack of Default `__len__` in Python Abstract Base Classes ]
    # in pytorch/torch/utils/data/sampler.py
```

By using the `Sequence` abstract classes, we can see in the official Python documentation that they have the exact abstract methods that the `Dataset` class expects, i.e. `__getitem__` and `__len__`.

## Motivation

My motivation is three-fold: (1) tackling the note mentioned above left by the PyTorch contributors, (2) let the code be auto-documented—since accessing this code states explicitly that you need to define those two methods and, (3) using Python abstract classes instead of inheritting from object (which is a rather deprecated practice for when Python did not have abstract classes capabilities).

## Pitch

Implement the Dataset class using new Python abstract classes capabilities, or at least discuss about it.

## Alternatives

I currently do not have alternative proposals.

## Additional context

`None`.


cc @SsnL
Repository: pytorch
Issue: Cuda error 59 : device-side assert triggered
Labels: needs reproduction,module: cuda,triaged

Hello,

I'm using an PyTorch implementation of Yolo for a deep learning model, running on AWS EC2 instance (g3s.xlarge with Tesla M60 GPU).

I have an issue when the training process: 8 classes with around 7000 images (for the moment to estimate the results), batch size = 64 (128 also possible), the error is: **Cuda error 59 : Runtime Error: device-side assert triggered**

I found a lot of subject on the same error, but no one answer really clear to the issue.
- I try to increase the number of images (in case the error is because there is not enought targets)
- I try to decrease the batch size
- I decrease the number of classes (a try with 2 classes, same number of images and try with 2 classes and around 2k images)
- I try to change PyTorch and Torchvision versions (using torch==1.0.1.post2 and torchvision==0.2.2.post3)
- I also try to restart all the process on fresh install of my instance

I attach a screenshoot of the error using the CUDA_LAUNCH_BLOCKING=1 to get more accuracy stacktrace, in case it can help

![error_cuda_train](https://user-images.githubusercontent.com/13837778/71527760-10070380-28dd-11ea-903b-f0df75ed1d1b.png)

PS: The error come after the first epoch, before run the test function on images

Do you have any idea to fix this ?

Thanks for your help,

Regards,
Florian

cc @ngimel
Repository: TypeScript
Issue: commonjs export binding produces invalid code for increment/decrement in PrefixUnaryExpression
Labels: Bug,Help Wanted

<!-- 🚨 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.7.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** export increment decrement syntax error

**Code**

```ts
// @module: commonjs
let foo = 1;
export { foo };
while (!--foo) { }
```

**Expected behavior:**

```js
while (!(exports.foo = --foo)) { }
```

**Actual behavior:**

Because the module-transform uses `onSubstituteNode`, it doesn't use the auto-parenthesizing that's done by the factory API.

```js
while (!exports.foo = --foo) { } // SyntaxError: `!exports.foo` is no valid assignment target
```

**Playground Link:** https://www.typescriptlang.org/play/?target=99&module=1&ssl=3&ssc=19&pln=1&pc=1#code/DYUwLgBAZg9jEF4IEYDcAoEAPADjATpAN7RwQC+GA7gBYCWoEAFAIQC0bsMAlBCeUA

**Related Issues:** #33044
Repository: TypeScript
Issue: ObjectAssignmentRest causes "Property 'foo' does not exist on type '{}'"
Labels: Bug

<!-- 🚨 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.7.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** rest destructuring assignment does not exist on type

**Code**

```ts
let { foo = {}, ...rest } = {}; // no error in ObjectBindingPattern
({ foo = {} } = {}); // works in ObjectAssignmentPattern without rest property
({ foo = {}, ...rest } = {}); // error: Property 'foo' does not exist on type '{}'
```

**Expected behavior:**

all or none should have an error

**Actual behavior:**

Rest in ObjectAssignmentPattern causes error on unrelated property.

**Playground Link:** https://www.typescriptlang.org/play/?target=99&ssl=3&ssc=30&pln=1&pc=1#code/DYUwLgBA3hBmD28IF5oF8A0EB0uBOIAzpGiugNwBQAFDAkqlKaY2gJRW1yJlNa7YCxCC3QcgA
Repository: TypeScript
Issue: commonjs export binding not updated in ForInOrOfStatement
Labels: Bug

<!-- 🚨 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.7.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** commonjs export for of

**Code**

```ts
// @module: commonjs
// @target: esnext
let foo = '';
export { foo };
for (foo in {}) { }
for (foo of []) {}
for ({foo} of [{foo}]) {}
```

**Expected behavior:**

`for...in` and `for...of` should update the export binding.

```js
for (_a in {}) { 
  exports.foo = foo = _a;
}
for (_b of []) {
  exports.foo = foo = _b;
}
for (_c of [{foo}]) {
  exports.foo = foo = _c.foo;
}
```

**Actual behavior:**

Binding is not updated

**Playground Link:** https://www.typescriptlang.org/play/?target=99&module=1#code/DYUwLgBAZg9jEF4IHJkG4BQIAeAHGATpAN7RwQC+msBEAFLPAJYB2ExFAlO5RjfYwgwoEANoBdbhz6F6xRhSEjR8uBUnsKQA
Repository: godot
Issue: 3.x: Materials generated from .gltf file are too big in filesize
Labels: discussion,confirmed,documentation,topic:import,topic:3d

**Godot version:**
3.1.2

**OS/device including version:**
Windows 10 v1809

**Issue description:**
When you import fully textured .gltf scenes Godot automatically generates .material files for you. Unfortunately there's a flaw in it, because, for example - a door material is 13 mb in size while all the textures are barely 300kb in size. Also, the exported gltf is only 2,6 mb in size. Something's totally not right here.

**Steps to reproduce:**
Make a model in blender, make materials, export to gltf and finally import to godot.
**Minimal reproduction project:**

[material-bug.zip](https://github.com/godotengine/godot/files/4006125/material-bug.zip)

here's a screenshot of all of the wooden floor material files - they're only 718 kb in file size, while the material is 9,2 mb (!)
![Screenshot_6](https://user-images.githubusercontent.com/57419448/71530481-3d0de300-28ea-11ea-88ba-5d6c51d242b5.png)
Repository: TypeScript
Issue: import is cut after "transpileModule" compilation when object spread is used (TypeScript 3.7)
Labels: Bug,Help Wanted

**TypeScript Version:**  3.7.0-dev.20190820

**Search Terms:**

- transpileModule
- cut import
- object spread

**Code**

```ts
import { additionalInfo } from './additionalInfo';

async function getObject() {
	return {
		key: 'value',
	}
}

async function main() {
	const obj = await getObject();

	return {
		...obj,
		additionalInfo,
	};
}
```

**Expected behavior:**

import should stay in compiled version even when `transpileModule` is used.

**Actual behavior:**

import is cut from `transpileModule` compilation output. I met this behaviour during usage of [ts-loader](https://github.com/TypeStrong/ts-loader) with [`transpileOnly: true` option used](https://github.com/TypeStrong/ts-loader#transpileonly). It uses TS's `transpileModule` underneath.

Occurs also on Nightly version of `typescript` (3.8.0-dev.20191224 at the moment).

Error occurs first on 3.7.0-dev.20190820 version. No error on 3.7.0-dev.20190817

More specifically, error occurs after applying this PR - https://github.com/microsoft/TypeScript/pull/32969. So I'm guessing, `obj` somehow gets `unknown` type during compilation. Spreading is not allowed on it and import is cut off from the compilation output.

import will stay after compilation in these cases:

- manual unapplying of that PR on `typescript` source;
- writing return type of `getObject` function;
- manual wrapping of the object with `Promise.resolve()`;
- making `getObject` function not async;
- use normal `tsc` compilation;

**Playground Link:**

Sadly, not reproducible in Typescript Playground.

I constructed example in this repository: https://github.com/sorochanalex/typescript-bug

**Related Issues:**

I have found _something_ similar here - https://github.com/microsoft/TypeScript/issues/15469 - but this issue was resolved.