sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: E0700 does not point to where the captured lifetime is
Labels: C-enhancement,A-diagnostics,T-compiler,A-async-await,AsyncAwait-Triaged,D-papercut,S-has-mcve

The error message 

```rust
error[E0700]: hidden type for `impl Trait` captures lifetime that does not appear in bounds
```

does not point to where in the block the captured lifetime is (which makes debugging it difficult).

It does, however, point to the scope:

```rust
note: hidden type `impl futures::Future` captures the scope of call-site for function at 48:40
  --> rs/agent-updater/src/fetcher.rs:48:40
   |
48 |       ) -> Result<PathBuf, FetcherError> {
   |  ________________________________________^
49 | |         let checksum = m.get_valid_checksum()?;
51 | |
...  |
72 | |         Ok(folder)
73 | |     }
   | |_____^
```
Repository: TypeScript
Issue: @template is lost when importing method
Labels: Needs Investigation

<!-- 🚨 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.6.3

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
template

**Code**

```ts
const $indicatrix = require('./indicatrix')

/**
 * Will print the loading text and refresh the CLI line to show the ellipsis while the promise is loading.
 * @param {string} text The text to display in the CLI.
 * @param {!Promise<T>|function(...*): !Promise<T>} promise The promise or an async function that returns the promise.
 * @return {Promise<T>}
 * @template T
 */
function indicatrix(text, promise, options) {
  return $indicatrix(text, promise, options)
}

module.exports = indicatrix
```

import this from another file

```js
/**
 * @type {_indicatrix.indicatrix}
 */
async function $indicatrix(text, promise, options = {}) {
  // implementation ...
}

/**
 * @suppress {nonStandardJsDocs}
 * @typedef {import('..')} _indicatrix.indicatrix
 */
```

**Expected behavior:**

supposed to be like in the original location

![image](https://user-images.githubusercontent.com/21156791/73294479-fed05000-4216-11ea-895f-5a817a6412d8.png)

**Actual behavior:**

the template bit is lost 

![image](https://user-images.githubusercontent.com/21156791/73294553-22939600-4217-11ea-8a34-eb4226be67d7.png)
Repository: rust
Issue: UnixDatagram: please support vectored send
Labels: T-libs-api,C-feature-request

The `UnixDatagram` type provides `send` and `send_to` methods, but does not provide a vectored send operation. Such an operation is particularly helpful for datagrams, where separate send operations result in separate datagrams; a vectored send allows sending data from multiple buffers in a single datagram.

Given that `UnixDatagram` only runs on UNIX, where `writev` works just fine on a socket, such an operation could use `writev`; alternatively, this could use `sendmsg`, which supports supplying an iovec. `sendmsg` would also allow a vectored `send_to` operation.
Repository: rust
Issue: UdpSocket: please support vectored send
Labels: T-libs-api,C-feature-request

The `UdpSocket` type provides `send` and `send_to` methods, but does not provide a vectored send operation. Such an operation is particularly helpful for datagrams, where separate send operations result in separate datagrams; a vectored send allows sending data from multiple buffers in a single datagram.

This would require calling `sendmsg`, which supports supplying an iovec. (This should work on Windows as well.)
Repository: godot
Issue: In an HBoxContainer a Viewport with size 0 in a stretch-enabled VIewportcontainer does not render until first resize
Labels: bug,confirmed,topic:gui

**Godot version:**

3.1.2

**OS/device including version:**

OpenSuse Tumbleweed

**Issue description:**

is related to https://github.com/godotengine/godot/issues/26187 and can be easily fixed setting the viewport size to something good in the first place but maybe this helps someone figure out https://github.com/godotengine/godot/issues/34805

**Steps to reproduce:**

make a 3d scene and a 2d scene, put a viewportcontainer in a hboxcontainer and make them resize and enable stretch,
put the viewport in the viewportcontainer and put the viewports size to 0,0, notice how it doesn't render on first frames,
resize the window to resize all the containers
notice how it now works :D 

**Minimal reproduction project:**

[testproject.zip](https://github.com/godotengine/godot/files/4124967/testproject.zip)
Repository: TypeScript
Issue: Documentation returned from constant type instead of from the constant itself 
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. 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.
-->

From https://github.com/microsoft/vscode/issues/89508

<!--
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.8.0-dev.20200128

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
- jsdoc
- quickinfo
- signatureHelp

**Code**
For the code:

```ts
/**
 * Interface!
 */
interface Handler<T> {
    /**
     * Call!
     */
    (): void;
}

/**
 * Instance!
 */
declare const catHandler: Handler<string>;


catHandler()
```

1. Hover over `catHandler()`

**Expected behavior:**
Documentation `Instance!` is returned

**Actual behavior:**
Documentation for `Call!` returned:

<img width="429" alt="Screen Shot 2020-01-28 at 2 47 01 PM" src="https://user-images.githubusercontent.com/12821956/73312221-0ffc6b00-41dd-11ea-93fc-39b212e0afa8.png">


/cc @Tyriar
Repository: rust
Issue: StorageLive (and even StorageDead) may be unnecessary in MIR.
Labels: C-cleanup,T-compiler,A-MIR

A while back I was discussing `Storage{Live,Dead}` and dominators, with @tmandry (in the context of generator layout optimizations), and came to the conclusion that `StorageLive` pretty much *has to* dominate all uses (I doubt we ever added a check that it does so, though).

More recently, I was trying to figure out what the simplest "`StorageLive` sinking" (i.e. moving the statement "later" in the CFG) optimization we could do was.

The conclusion I came to was that we might not need `StorageLive` at all, because there might be a deterministic "best placement" we could compute (assuming we need *exactly* one `llvm.lifetime.start` per `alloca`).

<hr/>

That best placement would be the *least (common) dominator* of all mentions of a MIR local.
Even indirect accesses require a direct borrow beforehand, so this should cover everything.

(Assuming that, given CFG points `x`, `y`, `z`, "`x` is a common dominator of `y` and `z`" means "`x` dominates both `y` and `z`", i.e. "to reach either `y` or `z` you must go through `x` first", and the "least" such `x` is the one not dominating other common dominators of `y` and `z`, i.e. it's "the closest to `y` and `z`")

This could be:
* just before the single assignment of that local
  * `let x = x + y;`
* at the end of a block branching into paths which all assign that local
  * `let x = if c { a } else { b };`
  * `let x; if c { x = a; } else { x = b; }` (roughly equivalent)

I am not sure about interactions with loops, though.

But this doesn't have to remain theoretical, we could compute this "ideal `StorageLive` position" and then compare it with the existing one (presumably one would dominate the other? not sure this would catch any loop issues though).

<hr/>

`StorageDead` could also be similar ("least (common) post-dominator"?).

However, it also has the effect of invalidating borrows, so we would need to keep an `InvalidateBorrows(x)` statement around, and consider it one of the mentions of `x`.

Then "`Storage{Live,Dead}` range shrinking" would simply boil down to hoisting `InvalidateBorrows(x)` up past statements which couldn't indirectly access `x`.

<hr/>

cc @nikomatsakis @ecstatic-morse @rust-lang/wg-mir-opt
Repository: terminal
Issue: Alternate console buffers of different sizes confuse ConPTY (and therefore Windows Terminal)
Labels: Help Wanted,Area-Rendering,Product-Conpty,Area-Output,Issue-Bug,Priority-2

<!--
This bug tracker is monitored by Windows Terminal development team and other technical folks.

**Important: When reporting BSODs or security issues, DO NOT attach memory dumps, logs, or traces to Github issues**.
Instead, send dumps/traces to secure@microsoft.com, referencing this GitHub issue.

If this is an application crash, please also provide a Feedback Hub submission link so we can find your diagnostic data on the backend. Use the category "Apps > Windows Terminal (Preview)" and choose "Share My Feedback" after submission to get the link.

Please use this form and describe your issue, concisely but precisely, with as much detail as possible.

-->

# Environment

```
Microsoft Windows [Version 10.0.18362.535]
Version: 0.8.10261.0
```

# Steps to reproduce

<!-- A description of how to trigger this bug. -->
1. Open a TUI application in Windows Terminal.
2. Resize the Terminal Window
3. Close the TUI application

The resulting terminal window acts like it is the original size before resizing, but the resized area remains visible.

For reference, the TUI application I was testing is a command line 2048 game: https://github.com/jwlodek/py_cui_2048
It can be installed with pip for python3:
```
pip install py_cui_2048
py2048
```

# Expected behavior

<!-- A description of what you're expecting, possibly containing screenshots or reference material. -->

When performing the same steps in `cmd` the terminal is resized back to its original size after resize and TUI application closed. This is also the case for a standalone `powershell` window.

# Actual behavior

<!-- What's actually happening? -->
The window does seem to internally resize, but the extra space is still drawn. Please see video below for visual example:


![TUIResizeBug](https://user-images.githubusercontent.com/29227305/73313018-1b10c480-41f8-11ea-82b0-d0d84d6e910d.gif)
Repository: material-ui
Issue: Slide recreates style object property
Labels: component: transitions

* [x]  The issue is present in the latest release.
* [x]  I have searched the [issues](https://github.com/mui-org/material-ui/issues) of this repository and believe that this is not a duplicate.

 ## Current Behavior 
Slide component always recreates children `style` object and sets its `visibility` field to `'hidden'` / `undefined`.
In such situation we cannot use neither `React.memo` (without compare function) nor `React.PureComponent`, cause function `shallowEquals` always returns `false`.

https://github.com/mui-org/material-ui/blob/5c84559ce012e403d01773112774de56d7e74723/packages/material-ui/src/Slide/Slide.js#L212-L222

 ## Expected Behavior 
Slide should try to use original style objects whenever it can.

Something like that, should be enough:
```js
// Trying to get children style without recreating style object
const getChildrenStyle = (state) => {
  const forwardedStyle = (() => {
    if (!style) {
      return children.props.style;
    }
    if (!children.props.style) {
      return style;
    }
    return {...style, ...children.props.style};
  })();

  if (state === 'exited' && !inProp) {
    return {visibility: "hidden", ...forwardedStyle}
  }
  return forwardedStyle;
};
```
 
 ## Steps to Reproduce 
https://codesandbox.io/s/serene-easley-ll4ut
 
 ## Your Environment 
Tech | Version
--- | ---
Material-UI | v4.9.0
React | latest
Browser | chrome
Repository: TypeScript
Issue: Private Fields: Code action for marking a field private
Labels: Suggestion,Awaiting More Feedback

Testing https://github.com/microsoft/vscode/issues/89387.

It would make sense to provide a code action / refactoring for turning a public field into a private field that also generates a getter if needed.
Repository: nvm
Issue: nvm changes user profile - must be "opt-in" rather than "opt-out"
Labels: installing nvm: profile detection

<!-- Thank you for being interested in nvm! Please help us by filling out the following form if you‘re having trouble. If you have a feature request, or some other question, please feel free to clear out the form. Thanks! -->

#### Operating system and version:

Linux.

#### `nvm debug` output:
Not relevant to this request.

#### `nvm ls` output:
<details>
$ nvm ls
->     v12.14.1
        v13.6.0
        v13.7.0
         system
default -> lts/* (-> v12.14.1)
node -> stable (-> v13.7.0) (default)
stable -> 13.7 (-> v13.7.0) (default)
iojs -> N/A (default)
unstable -> N/A (default)
lts/* -> lts/erbium (-> v12.14.1)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.18.1 (-> N/A)
lts/erbium -> v12.14.1


```sh

```
</details>

#### How did you install `nvm`?
Install script.

#### What steps did you perform?

```
wget -qO- https://raw.githubusercontent.com/nvm-sh/nvm/v0.35.2/install.sh | XDG_CONFIG_HOME=`pwd` bash
:
=> Appending nvm source string to /home/bryce/muggeridge/.bashrc
=> Appending bash_completion source string to /home/bryce/muggeridge/.bashrc
:
```

Modifying the user's profile is altogether unfriendly (and un-Linux).  It has resulted in some of our users' login session breaking, since it cannot find the NVM_DIR.  

This *has* to become an opt-in feature.

I know you can opt-out, by setting the environment variable PROFILE=/dev/null.  However, most users are unaware of that, and nor should they have to become aware.

#### What happened?

The user's profile is updated by default, without them requesting that to be updated.  Some users' login sessions were subsequently broken.  Dare I say, the current behaviour is virus-like, albeit well-intentioned as I understand what you were trying to achieve.

#### What did you expect to happen?

A user ought to opt-in to have their profile updated.  Currently, the default behaviour requires the user to opt-out.

#### Is there anything in any of your profile files that modifies the `PATH`?
<!--  (e.g. `.bashrc`, `.bash_profile`, `.zshrc`, etc) -->

<!-- Please remove the following section if it does not apply to you -->
#### If you are having installation issues, or getting "N/A", what does `curl -I --compressed -v https://nodejs.org/dist/` print out?
<details>
<!-- do not delete the following blank line -->

```sh

```
</details>
Repository: pytorch
Issue: PyTorch freezes on second call to scripted densenet model from torchvision
Labels: oncall: jit,triaged,module: vision

## 🐛 Bug

PyTorch freezes on second call to scripted densenet model from torchvision.

## To Reproduce

Steps to reproduce the behavior:

The script freezes after printing the first result.

```python
import torch
import torchvision

"""
Freezes on the second call to run the script model.
"""
model = torchvision.models.densenet121(pretrained=True)
x = torch.randn(2, 3, 224, 224, requires_grad=True)

script_model = torch.jit.script(model)
print('resuit:', script_model(x))

print('second result:', script_model(x))
```

## Environment

Both PyTorch and torchvision are nightly, installed by `conda install pytorch torchvision cpuonly -c pytorch-nightly`

PyTorch version: 1.5.0.dev20200128
Is debug build: No
CUDA used to build PyTorch: Could not collect

OS: Ubuntu 16.04.5 LTS
GCC version: (Ubuntu 5.4.0-6ubuntu1~16.04.12) 5.4.0 20160609
CMake version: version 3.5.1

Python version: 3.7
Is CUDA available: No
CUDA runtime version: Could not collect
GPU models and configuration: GPU 0: GeForce GTX 1070
Nvidia driver version: 410.78
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.7.4.1
/usr/local/cuda-10.0/lib64/libcudnn.so.7


cc @suo @fmassa
Repository: pytorch
Issue: RPC mock mode for unit tests.
Labels: triaged,module: rpc

## 🚀 Feature
I am building some distributed features that rely on RPC. For my unit test, once I need to test multiple workers, RPC will bring up a process group. As a developer that uses RPC api, launching communication layer feels too heavy for unit tests.  

It would be great to have a mock version of RPC that bypasses the communication layer (process group / gloo / etc ) and enables lightweight RPC API testing. 


cc @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @gqchen @aazzolini @rohan-varma @xush6528 @jjlilley @osalpekar
Repository: pytorch
Issue: JIT performance discrepancies
Labels: module: performance,oncall: jit,triaged

PyTorch Nightly (today)
Fedora 31
Anaconda Python 3.7
GPU: 970 (staying under 3.5 GB limit, last 0.5GB is lower quality memory)

Not completely confident it's a bug, if it isn't there should certainly be something mentioned in the documentation.

All result variance is ~0.01

```
import numpy as np
import torch
import time

data_type = torch.torch.cuda.DoubleTensor

cuda = torch.device('cuda')

points = torch.rand((2**22,3), dtype=torch.double, device=cuda, requires_grad=False).type(data_type)
points[:, 2] = 0.0

@torch.jit.script
def attractor_func(v):
	x, y, z = torch.chunk(v, 3, dim=1)

	#lorenz
	a = 10.0
	b = 28.0
	c = 8.0 / 3.0
	dx = a * (y - x)
	dy = x * (b - z) - y
	dz = x * y - c * z

	return torch.cat([dx, dy, dz], 1)

@torch.jit.script
def rk4(v):
	h = 0.001
	k1 = attractor_func(v)
	k2 = attractor_func(v + (h / 2.0) * k1)
	k3 = attractor_func(v + (h / 2.0) * k2)
	k4 = attractor_func(v + h * k3)
	return h * (k1 / 6.0 + k2 / 3.0 + k3 / 3.0 + k4 / 6.0)


rk4 = torch.jit.trace(rk4, example_inputs=points)


start = time.time()
for _ in range(1024):
	points += rk4(points)
end = time.time()
print(end - start)
```

output:
18.279905796051025

comment out the trace, output:
18.649290084838867

Why is the trace adding performance to JIT scripts?

Uncomment the trace and comment the script tags on both functions, output:
28.479955911636353

Why does the trace benefit greatly from JIT scripts?


Another example that may have more to do with wrong function choice or some minor inefficiency somewhere:

```
import numpy as np
import torch
import time

data_type = torch.torch.cuda.DoubleTensor

cuda = torch.device('cuda')

points = torch.rand((2**22,3), dtype=torch.double, device=cuda, requires_grad=False).type(data_type)
points[:, 2] = 0.0

def attractor_func(v):
	x, y, z = torch.chunk(v, 3, dim=1)

	#duffing
	a = 0.25
	b = 0.3
	c = 1.0
	dx = y
	dy = x - x**3 - a * y + b * torch.cos(c * z)
	dz = x - x + 1.0
	return torch.cat([dx, dy, dz], 1)

def rk4(v):
	h = 0.001
	k1 = attractor_func(v)
	k2 = attractor_func(v + (h / 2.0) * k1)
	k3 = attractor_func(v + (h / 2.0) * k2)
	k4 = attractor_func(v + h * k3)
	return h * (k1 / 6.0 + k2 / 3.0 + k3 / 3.0 + k4 / 6.0)


rk4 = torch.jit.trace(rk4, example_inputs=points)


start = time.time()
for _ in range(1024):
	points += rk4(points)
end = time.time()
print(end - start)
```


output:
46.12030529975891

change to `dz = x.clone().fill_(1.0)`

output:
65.20094799995422

change to `dz = torch.ones((2**22,1), dtype=torch.double, device=cuda, requires_grad=False).type(data_type)`

output:
46.92164850234985

change to `dz = x.new_ones((2**22,1))`

output:
46.9119393825531

Only the last two make sense. Though it seems like it’s precisely the last two that make the use of a script tag for the function impossible. In this case, unlike the previous one the script tags don't appear to do much.



cc @suo @VitalyFedyunin @ngimel
Repository: flutter
Issue: Add test to verify that loading code using dart:mirrors via IsolateMirror.loadURI does not regress.
Labels: a: tests,engine,e: embedder,P2,team-engine,triaged-engine

This is not supported in Flutter but an internal user depends on this functionality. Test must be added to ensure that this does not regress till they migrate away to an alternative. The entirety of the filesystem and package map handling code in Tonic is written to support this use case. Since this use case does not at first glance seem supported, attempts may be made by engineers to get rid of the same.

xref https://github.com/flutter/engine/pull/16157
Repository: scrcpy
Issue: Lagging on my Mobile(Poco f1)
Labels: performance,obs

hi first of all thanks for making this software.

now lets come to the problem I am using Xiaomi Poco f1 device and I am casting my screen to my pc(windows 10) for recording I am recording with OBS till now no problem everything is working fine but when I start to record with OBS somehow my device starts to lag the game especially PUBG Mobile I don't know why I think Poco f1 has good hardware(SD 845) and should not lag in this case.

if you have any setting which I can play around then please tell me. it would be appreciated.
Thanks.
Repository: flutter
Issue: Make the Cupertino Date Picker easier to driver with Flutter driver
Labels: framework,f: date/time picker,f: cupertino,c: proposal,P3,team-design,triaged-design

Similar to #49100 if would be great to make this widget easier to driver using Flutter driver by adding well known keys to the days, months, years, hours, minutes, seconds CupertinoPicker widgets within this control.  These picker could then be scrolled and tapped and thus any date and/ or time could be picked.

At the moment this widget is impossible to driver using the driver.

I'm happy to do a PR for this so let me know any thoughts or if I have missed something simple with driving this element with the driver.
Repository: godot
Issue: Bug that caused project to lose all files except for the default files
Labels: bug,topic:editor

**Godot version:**
v3.1.stable.official

**OS/device including version:**
Windows 10

**Issue description:**
The project that lost the files will be in like when it was first created with the default files

**Steps to reproduce:**
I encountered this bug when in a project then quit to project list then enter another project and quit again, then the project list will be empty, import your projects back and a project would be affected with the bug
Repository: flutter
Issue: DropDownButton looses selection when disabled
Labels: framework,f: material design,c: proposal,P3,team-design,triaged-design

A DropDownButtonhas no `enable` property. Instead, the `onChanged` property must be set to null. In this case, any selection will be replaced by `disabledHint` or `hint` which is inconsistent with other input widgets.

It would be much better to have

1. a property `enable` to enable / disable the widget (more clear to handle)
2. display the selected value (its widget) independent of enabled state
3. move hints to `InputDecoration` which should become a property `decoration` for the dropdown button.