sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: "uncorrectable NVLink error" making the tests fail
Labels: oncall: distributed,module: cuda,triaged,module: nccl

## 🐛 Bug

Trying to build PyTorch 1.8.1 on our latest A100 cluster fails during the tests. The failing tests are

- test_nccl_errors_blocking_abort
- test_nccl_errors_blocking_nonzero_exit
- test_nccl_errors_blocking_sigkill
- test_nccl_errors_blocking_sigterm
- test_nccl_blocking_wait_with_barrier
- test_nccl_errors_blocking_clean_exit
- test_nccl_timeout

Those failures look related, so I'd guess they have the same cause. Also those are the only failures from this test file

Errors look like:
```
test_nccl_blocking_wait_with_barrier (__main__.NcclErrorHandlingTest) ... terminate called after throwing an instance of 'c10::Error'
  what():  CUDA error: uncorrectable NVLink error detected during the execution
```

and 

```
test_nccl_errors_blocking_abort (__main__.NcclErrorHandlingTest) ... ERROR:root:Caught exception: 
RuntimeError: NCCL error in: ../torch/lib/c10d/../c10d/NCCLUtils.hpp:155, unhandled cuda error, NCCL version 2.8.3
ncclUnhandledCudaError: Call to CUDA function failed.
```

See this gist for more details: https://gist.github.com/Flamefire/2cef97c9ae73e1ee206ac7e2fa0f62fb

## To Reproduce

Steps to reproduce the behavior:

1. Build and run tests: `run_test.py -i distributed/test_c10d`

## Environment

 - PyTorch Version (e.g., 1.0): 1.8.1
 - OS (e.g., Linux): CentOS 7
 - How you installed PyTorch (`conda`, `pip`, source): source
 - Build command you used (if compiling from source): `USE_CUPTI_SO=1 PYTORCH_BUILD_VERSION=1.8.1 PYTORCH_BUILD_NUMBER=1 MAX_JOBS=96 BLAS=Eigen USE_FFMPEG=1 BUILD_CUSTOM_PROTOBUF=0 USE_IBVERBS=1 USE_CUDA=1 CUDNN_LIB_DIR=/sw/installed/cuDNN/8.0.4.30-CUDA-11.1.1/lib64 CUDNN_INCLUDE_DIR=/sw/installed/cuDNN/8.0.4.30-CUDA-11.1.1/include USE_SYSTEM_NCCL=1 NCCL_INCLUDE_DIR=/sw/installed/NCCL/2.8.3-CUDA-11.1.1/include USE_METAL=0   /scratch/ws/1/s3248973-EasyBuild/easybuild-rome/software/Python/3.8.6-GCCcore-10.2.0/bin/python setup.py build`
 - Python version: 3.8.6
 - CUDA/cuDNN version: 11.1.1, NCCL 2.8.3
 - GPU models and configuration: 8xA100

## Additional context

From what I heard NCCL has non-fatal errors which shouldn't terminate the application. I'd guess this is one of them and PyTorch likely needs to handle those.


cc @ngimel @pietern @mrshenli @pritamdamania87 @zhaojuanmao @satgera @rohan-varma @gqchen @aazzolini @osalpekar @jiayisuse @agolynski @SciPioneer @H-Huang @mrzzd @cbalioglu @gcramer23
Repository: flutter
Issue: [Macos][Desktop][Feature Request]: Add FlutterViewController's initWithEngine method
Labels: c: new feature,engine,platform-mac,c: proposal,a: desktop,P2,team-macos,triaged-macos

try upgrade flutter
try change channel to dev
deleted flutter/bin/cache/...FlutterMacOS and redownload 

the same...
Repository: pytorch
Issue: Allow `Union` as a `Dict` key
Labels: triaged,TSRootCause:TypeRefinement

## 🚀 Feature
If we have `Union[T1, T2, ... TN]` where each internal type `TK` is an allowable dict key, then we should also allow that Union as a dict key. If one or more of the types in the Union is not an allowable Dict key, we shouldn't allow that Union as a dict key.

The difficulty here comes from making schema matching work. I think that this could be both a follow-up to `Union` as well as part of a larger upgrade in our schema-matching algorithm

cc @gmagogsfm
Repository: PowerToys
Issue: Toggle on old Photoviewer
Labels: Idea-New PowerToy,Product-Tweak UI Design

I really miss the old Photviewer from Windows past. I know I can use it with a manual registry entry on Windows 10, but it would be so much nicer if it was just a resident Powertoy and be able to toggle it on with a simple push of a button.
Repository: node
Issue: Stream finished does not always work with http incoming message
Labels: stream

* **Version**: v15.12.0
* **Platform**: Darwin Kernel Version 20.3.0
* **Subsystem**: http

### What steps will reproduce the bug?

The `stream.finished` never resolves or rejects when applied onto a destroyed incoming message like in example below. It finishes for example when applied on a destroyed file stream. Also it finishes when the line with `await new Promise(r => setTimeout(r, 1000));` is commented. This looks really inconsistent.

``` js
let http = require("http");
let { finished } = require("stream/promises");

let server = http.createServer(async function(req, res)
{
	for await (let chunk of req) break;
	await new Promise(r => setTimeout(r, 1000));
	console.log("waiting");
	await finished(req);
	console.log("sending");
	res.end();
});

(async function()
{
	await new Promise(resolve => server.listen(resolve));
	let req = http.request({ port: server.address().port, method: "post" }).end("abc");
	try
	{
		let res = await new Promise((resolve, reject) => req.on("response", resolve).on("error", reject));
		await finished(res.resume());
	}
	catch(e)
	{
		console.log(e);
	}
}());
```

### How often does it reproduce? Is there a required condition?

Always.

### What is the expected behavior?

```
Error: socket hang up
waiting
sending
```

### What do you see instead?

```
Error: socket hang up
waiting
```

### Additional information
Repository: pytorch
Issue: torch.split_with_sizes is not documented
Labels: module: docs,triaged

![Screenshot from 2021-05-13 01-35-59](https://user-images.githubusercontent.com/19503980/118037551-a1b8c900-b38b-11eb-8515-83f74946a3f2.png)

The function is available and tested. Also the name does not start with a leading underscore so I assume it is meant to be public. Looks like this was just a miss.
https://github.com/pytorch/pytorch/blob/c9eb381aac886ea39efa4ad042fa126102974905/torch/testing/_internal/common_methods_invocations.py#L6382-L6384

cc @brianjo @mruberry
Repository: vscode
Issue: Git conflict resolution Accept Current Change "ignores" addition of a single empty line
Labels: bug,merge-conflict

<!-- ⚠️⚠️ Do Not Delete This! bug_report_template ⚠️⚠️ -->
<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- 🕮 Read our guide about submitting issues: https://github.com/microsoft/vscode/wiki/Submitting-Bugs-and-Suggestions -->
<!-- 🔎 Search existing issues to avoid creating duplicates. -->
<!-- 🧪 Test using the latest Insiders build to see if your issue has already been fixed: https://code.visualstudio.com/insiders/ -->
<!-- 💡 Instead of creating your report here, use 'Report Issue' from the 'Help' menu in VS Code to pre-fill useful information. -->
- VS Code Version: 1.55.2
- OS Version: macOS 10.15.7

I'm resolving a merge conflict where the last diff is the following (I had already resolved a couple successfully earlier in the file):

_Current Change_ ↔ _Incoming Changes_
```
154:  same line in file  |  154:  same line in file
155:                     |
156:  another same line  |  155:  another same line
```
Basically, **just an empty line** inserted by the **current** change.

Add I see this in the merge interface:
```
154:  same line in file
     Accept Current Change | Accept Incoming Change | Accept Both Changes | Compare Changes
155: <<<<<<< HEAD (Current Change)
156:
157: =======
158: >>>>>>> master (Incoming Change)
159:  another same line
```

If I click on **Accept _Current_ Change**, the **empty line was not preserved**—in fact, if I undo and click **Accept _Incoming_ Change** instead, the result is the same!

<!-- 🔧 Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: _not tested_

<!-- 🪓 If you answered No above, use 'Help: Start Extension Bisect' from Command Palette to try to identify the cause. -->
<!-- 📣 Issues caused by an extension need to be reported directly to the extension publisher. The 'Help > Report Issue' dialog can assist with this. -->

_Originally reported under and possibly related to: https://github.com/microsoft/vscode/issues/107821#issuecomment-831657432_
Repository: flutter
Issue: implement flutter precache --dry-run
Labels: team,P3,team-tool,triaged-tool

When passed the flag `--dry-run`, instead of downloading remote artifacts, the tool would just print out the remote path it would have downloaded, and perhaps the relative path in the cache it would have downloaded to (maybe support `--machine` so this could be structured JSON)

This would assist release tooling that needs to account for all remote artifacts depended on by the tool.
Repository: terminal
Issue: Add settings import to command line
Labels: Issue-Feature,Needs-Tag-Fix,Area-Commandline

<!-- 
🚨🚨🚨🚨🚨🚨🚨🚨🚨🚨

I ACKNOWLEDGE THE FOLLOWING BEFORE PROCEEDING:
1. If I delete this entire template and go my own path, the core team may close my issue without further explanation or engagement.
2. If I list multiple bugs/concerns in this one issue, the core team may close my issue without further explanation or engagement.
3. If I write an issue that has many duplicates, the core team may close my issue without further explanation or engagement (and without necessarily spending time to find the exact duplicate ID number).
4. If I leave the title incomplete when filing the issue, the core team may close my issue without further explanation or engagement.
5. If I file something completely blank in the body, the core team may close my issue without further explanation or engagement.

All good? Then proceed!
-->

# Description of the new feature/enhancement

Command line argument allowing the import of new settings files.

This would make scripting of environment setup a bit less fiddly.

Something like

```console
> wt import mySettings.json
Settings imported successfully
```

Potentially could validate settings during import to prevent overwriting existing settings with invalid ones

```console
> wt import myDodgySettings.json
Settings not valid, import failed.
Ln # 8: "HoopyFrood" is not a valid setting
Ln # 9: "KnowsWhereHisTowelIs" is an unknown value for setting "ArthurDent"
    Acceptable values are "Confused", "Bewildered", or "JustWantsANiceCupOfTea".
````

If getting really fancy, the command could update valid but older settings to newer schemas

```console
> wt import myValidButOldSettings.json
Whoa, there Magrathean, those settings look a little stale!
Settings updated to new schema
Settings imported successfully
```
Repository: pytorch
Issue: [FX] record_function tracing in FX
Labels: triaged,module: fx

```
import torch
import torch.fx

class Foo(torch.nn.Module):
    def forward(self, x):
        with torch.profiler.record_function('my_op'):
            return torch.relu(x)

traced = torch.fx.symbolic_trace(Foo())
print(traced.code)
"""
def forward(self, x):
    relu = torch.relu(x);  x = None
    return relu
"""
```

A user may want their `record_function` ranges to be preserved in the FX-traced code. The initial conception of this was to support context managers, however I don't think it's worth it to do that since the value prop of FX is to have a flat DAG of operations without confusing nested scopes. Instead, we could record the underlying `torch.ops.profiler._record_function_enter` and `torch.ops.profiler._record_function_exit` calls in the graph. This would preserve the behavior, however it would not invoke `_record_function_exit` on propagating an exception. This is probably a fine trade-off

cc @ezyang @SherlockNoMad
Repository: neovim
Issue: vim.list_extend vs. vim.tbl_extend
Labels: enhancement,lua

`vim.list_extend` and `vim.tbl_extend` are inconsistent -- the latter returns a copy, while the former mutates its argument.

Is it too late to "fix" / change that? I'd love a `list_extend` that returns a copy instead, it seems to be a common need for me when writing Lua code, and then if versions with mutation are desirable presumably some second mutating API for both?

As usual feel free to close if this is a ridiculous idea.
Repository: PowerToys
Issue: Monitor file changes in Markdown preview, update when file is changed.
Labels: Idea-Enhancement,Product-File Explorer

### Microsoft PowerToys version

0.37.0

### Running as admin

- [X] Yes

### Area(s) with issue?

MD Preview

### Steps to reproduce

1. Open Windows File Explorer.
2. Click on Markdown file and view it in the preview pane.
3. Open the Markdown file in VSCode.
4. Edit the Markdown file in VSCode.
5. Save the Markdown file in VSCode.
6. Activate the open Windows File Explorer
7. The Markdown file is not updated in the preview pane.

### ✔️ Expected Behavior

Expected the Markdown preview pane in Windows File Explorer to show the edited changes.

### ❌ Actual Behavior

The Markdown preview pane in Windows File Explorer to showed the original document.

* When selecting something else in Windows File Explorer and re-selecting the Markdown document, then the changes to the Markdown document are shown.
* Suspect this behavior may apply to other document previewers too.

### Other Software

OS Name	Microsoft Windows 10 Pro
Version	10.0.19043 Build 19043
System Model	OMEN Laptop 15-en0xxx
System Type	x64-based PC
System SKU	2V927UA#ABA
Processor	AMD Ryzen 7 4800H with Radeon Graphics, 2900 Mhz, 8 Core(s), 16 Logical Processor(s)
BIOS Version/Date	AMI F.13, 03/04/2021
Installed Physical Memory (RAM)	16.0 GB
Total Physical Memory	15.4 GB
Available Physical Memory	6.92 GB
Total Virtual Memory	19.9 GB
Available Virtual Memory	5.03 GB
Page File Space	4.50 GB
Repository: rust
Issue: Doc example with feature dependency does not compile
Labels: T-rustdoc,A-doctests,C-discussion

A doc example which depends on a feature does not compile if the entire example is conditionally excluded.

Having the example conditionally compiled with a feature does not work if the feature is not enabled:

```rust
/// ```
/// #![cfg(feature = "foo")]
/// assert_eq!(1, 1);
/// ```
pub struct Foo;
```

Fails with:

> error[E0601]: `main` function not found in crate `rust_out`
> --> src/lib.rs:8:1
>   |
> 1 | / #![allow(unused)]
> 2 | | #![cfg(feature = "foo")]
> 3 | | fn main() { #[allow(non_snake_case)] fn _doctest_main_src_lib_rs_9_0() {
> 4 | | assert_eq!(1, 1);
> 5 | | } _doctest_main_src_lib_rs_9_0() }
>   | |__________________________________^ consider adding a `main` function at the crate level

Adding a `main()` as suggested also does not work:

```rust
/// ```
/// #![cfg(feature = "foo")]
/// fn main() {
/// assert_eq!(1, 1);
/// }
/// ```
pub struct Foo;
```

> Couldn't compile the test.
> ---- src/lib.rs - Foo (line 1) stdout ----
> error[E0601]: `main` function not found in crate `rust_out`
>  --> src/lib.rs:1:1
>   |
> 1 | / #![allow(unused)]
> 2 | | #![cfg(feature = "foo")]
> 3 | | fn main() {
> 4 | | assert_eq!(1, 1);
> 5 | | }
>   | |_^ consider adding a `main` function at the crate level

I expected the example to compile like an empty example, which does work:

```rust
/// ```
/// ```
pub struct Baz;
```

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

Affects stable and nightly:

`rustc --version --verbose`:
```
rustc 1.52.1 (9bc8c42bb 2021-05-09)
binary: rustc
commit-hash: 9bc8c42bb2f19e745a63f3445f1ac248fb015e53
commit-date: 2021-05-09
host: x86_64-unknown-linux-gnu
release: 1.52.1
LLVM version: 12.0.0
```
```
rustc 1.54.0-nightly (5c0292654 2021-05-11)
binary: rustc
commit-hash: 5c029265465301fe9cb3960ce2a5da6c99b8dcf2
commit-date: 2021-05-11
host: x86_64-unknown-linux-gnu
release: 1.54.0-nightly
LLVM version: 12.0.1
```
Repository: flutter
Issue: [in_app_purchase] iOS Always prompting for authentication on every purchase in sandbox mode
Labels: platform-ios,a: quality,p: in_app_purchase,package,has reproducible steps,P2,found in release: 2.0,team-ios,triaged-ios

On IOS only after every purchase it prompts the user for their apple id and password. This behavior exists after deploying to test flight as well. 

i am doing  to make the purchase. The purchase works its just asking me for my apple id and password its doing the same for all my beta testers as well.


```dart
     ProductDetails prod = _products.where((item) => item.id == productId).first;
      final PurchaseParam purchaseParam = PurchaseParam(productDetails: prod);
      await _iap.buyConsumable(purchaseParam: purchaseParam);
      
      ...
      ...
     await _iap.completePurchase(purchaseDetails);
```



<img height="450" alt="Screen Shot 2021-05-12 at 9 12 27 PM" src="https://user-images.githubusercontent.com/17206638/118063276-c3538980-b366-11eb-848b-b3444348b2c3.png">
Repository: tensorflow
Issue: Compilation fails on Ubuntu 20.04 when using TensorRT 8. 
Labels: stat:awaiting tensorflower,type:bug,subtype: ubuntu/linux,comp:gpu:tensorrt,TF 2.5

**System information**
- OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 20.04
- Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
- TensorFlow installed from (source or binary): binary
- TensorFlow version: 2.4.1, 2.5, etc
- Python version: 3.8
- Installed using virtualenv? pip? conda?: no, built from source
- Bazel version (if compiling from source): 3.1 (for TF 2.4.1), 3.7.2 (for TF 2.5.0-rcx)
- GCC/Compiler version (if compiling from source): gcc (Ubuntu 9.3.0-17ubuntu1~20.04) 9.3.0
- CUDA/cuDNN version: Cuda 11.1, cudnn8 (8.0.5.39-1+cuda11.1) or Cuda-11-2, libcudnn 8.1.1, 8.2, 
- GPU model and memory: GTX-1080ti
- TensorRT (crucial): 8.0.0-1+cuda11.0, or 8.0.0-1+cuda11.3

**Describe the problem**
When compiling with support for TensorRT 8 (via libnvinfer8), compilation fails (log is below). 

**Provide the exact sequence of commands / steps that you executed before running into the problem**
When configuring the build, make sure you build with TensorRT support, and make sure TensorRT version 8 is selected. Build TF as usual. Compilation will fail. 

If you install  TensorRT version 7 manually (from debs available for Ubuntu 18.04), compilation will complete just fine.

**Any other info / logs**
Relevant error: 
`C++ compilation of rule '//tensorflow/compiler/tf2tensorrt:tensorrt_stub' failed (Exit 1): crosstool_wrapper_driver_is_not_gcc failed: error executing command`

`In file included from bazel-out/k8-opt/bin/external/local_config_tensorrt/_virtual_includes/tensorrt_headers/third_party/tensorrt/NvInfer.h:54,
                 from tensorflow/compiler/tf2tensorrt/stub/nvinfer_stub.cc:17:
bazel-out/k8-opt/bin/external/local_config_tensorrt/_virtual_includes/tensorrt_headers/third_party/tensorrt/NvInferRuntime.h:2264:51: note: from previous declaration 'nvinfer1::IPluginRegistry* getPluginRegistry() noexcept'
 2264 | extern "C" TENSORRTAPI nvinfer1::IPluginRegistry* getPluginRegistry() noexcept;`

Full log here: 
[gesdm-tf2.5.0rc3-error.txt](https://github.com/tensorflow/tensorflow/files/6469944/gesdm-tf2.5.0rc3-error.txt)
Repository: youtube-dl
Issue: loco.gg
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 2021.04.26. 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])
-->

- [x] I'm reporting a new site support request
- [x] I've verified that I'm running youtube-dl version **2021.04.26**
- [x] I've checked that all provided URLs are alive and playable in a browser
- [x] I've checked that none of provided URLs violate any copyrights
- [x] 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 stream: https://loco.gg/stream/8bf55013-84cb-491f-b186-e1dc5ef26abb
- Single video: https://loco.gg/stream/f162bf6d-8265-46db-a0a4-186e604e7245
- get other streams link from https://loco.gg/live-streams


## Description

<!--
Provide any additional information.
If work on your issue requires account credentials please provide them or explain how one can obtain them.
-->

Watch India's top streamers playing and live streaming all your favorite games like Free Fire, CODM, PUBG, Valorant, GTA V and many more!
Repository: rust
Issue: Stack overflow/infinite recursion in `rustc_middle::ty::fold::TypeFoldable::fold_with`
Labels: A-type-system,I-crash,P-medium,T-compiler,C-bug,T-types

https://gitlab.com/veloren/veloren/-/commit/a8b267387cf4fdc0d537668defa20e1eeecf701e is the version of Veloren's codebase that triggers the bug.
It initially manifested as a SIGSEGV, looking at it under gdb seems to indicate that it's infinite recursion.

Rustc/cargo versions:
```
$ cargo --version
cargo 1.52.0-nightly (90691f2bf 2021-03-16)
$ rustc --version
rustc 1.53.0-nightly (f82664191 2021-03-21)
```

Related issues:
Searching for "TypeFoldable::fold_with" in the issue tracker seems to bring up a few ICEs, but no SIGSEGVs before this one.

[Excerpted GDB transcript](https://github.com/rust-lang/rust/files/6469977/rustc_crash_20210512.txt)
Repository: tauri
Issue: Feature request: JS API throws Error objects instead of strings
Labels: scope: core,type: feature request,priority: 3 low,type: breaking change

**Is your feature request related to a problem? Please describe.**
As a web developer who works primarily in with HTML/CSS/JS, all of my app code is currently JS which calls the tauri APIs via its JS bindings when appropriate. When an expected exception occurs (for example, trying to read a file that doesn't exist), I'd like to catch it and do something depending on the type of the exception. The JS bindings currently always throw string error messages instead of objects that extend Error, meaning that code for handling different kinds of exceptions involves messily parsing the error string or creating custom commands in Rust.

**Describe the solution you'd like**
I would like JS API calls to raise error objects that are associated with the expected kind of exception. They would provide access to the error message string plus any extra data relevant to that specific kind of exception. It would reduce the friction of implementing good exception handling as app developers wouldn't need to come up with custom exception parsing/wrapping solutions.

**Describe alternatives you've considered**
If it were not part of the API, somebody would likely create a separate library to do it at some point. It'd be better if it were just part of the API contract itself though.