sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: Unable to build: subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--target', 'install', '--config', 'Release', '--', '-j', '4']' returned non-zero exit status 1.
Labels: module: build,triaged

## 🐛 Bug

Trying to build on Mac OSX from source, build terminated with:
subprocess.CalledProcessError: Command '['cmake', '--build', '.', '--target', 'install', '--config', 'Release', '--', '-j', '4']' returned non-zero exit status 1.

## To Reproduce

Steps to reproduce the behavior:

1.  Install dependencies as documented on web page
2.  git clone --recursive https://github.com/pytorch/pytorch
3. cd to pytorch directory
4.  git submodule update --init --recursive 
5. export CMAKE_PREFIX_PATH=${CONDA_PREFIX:-"$(dirname $(which conda))/../"}
MACOSX_DEPLOYMENT_TARGET=10.9 CC=clang CXX=clang++ python setup.py install 2>&1 | tee build_new.txt

<!-- If you have a code sample, error messages, stack traces, please provide it here as well -->

log of output after additional context below

<!-- A clear and concise description of what you expected to happen. -->

Clean build of caffe2 (logged messages 



## Environment

Please copy and paste the output from our
[environment collection script](https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py)
(or fill out the checklist below manually).

You can get the script and run it with:
```
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py
PyTorch version: N/A
Is debug build: N/A
CUDA used to build PyTorch: N/A
ROCM used to build PyTorch: N/A

OS: macOS 10.15.6 (x86_64)
GCC version: Could not collect
Clang version: 12.0.0 (clang-1200.0.32.29)
CMake version: version 3.19.0

Python version: 3.8 (64-bit runtime)
Is CUDA available: N/A
CUDA runtime version: Could not collect
GPU models and configuration: Could not collect
Nvidia driver version: Could not collect
cuDNN version: Could not collect
HIP runtime version: N/A
MIOpen runtime version: N/A

Versions of relevant libraries:
[pip3] numpy==1.19.5
[conda] mkl                       2020.2                      260
[conda] mkl-include               2020.2                      260
[conda] numpy                     1.19.2           py38h63973fd_0
[conda] numpy-base                1.19.2           py38h68fea81_0
```

 - PyTorch Version (e.g., 1.0):
 - OS (e.g., Linux):
 - How you installed PyTorch (`conda`, `pip`, source):
 - Build command you used (if compiling from source):
 - Python version:
 - CUDA/cuDNN version:
 - GPU models and configuration:
 - Any other relevant information:

## Additional context

<!-- Add any other context about the problem here. -->

[build_new.txt](https://github.com/pytorch/pytorch/files/5961572/build_new.txt)


cc @malfet @seemethere @walterddr
Repository: flutter
Issue: [webview_flutter] NavigationDelegate blocks Js redirects
Labels: platform-android,p: webview,package,has reproducible steps,P2,found in release: 2.2,found in release: 2.5,team-android,triaged-android

I'm new to flutter. I'm doing a project with Webview. I need to check urls. I'm checking with navigationDelegate but NavigationDecision.navigate is blocking js redirects white page appears. If I remove the navigationDelegate part, it works fine. Is there any other way for me to check url? or how to fix this problem


<details>
<summary>code sample</summary>

```dart
              WebView(
                javascriptMode: JavascriptMode.unrestricted,
                onWebViewCreated: (WebViewController c) {
                  c.loadUrl('https://www.doyurunbeni.com/',
                      headers: {'Cookie': 'test=testcookie');
                  _controllerCompleter.future
                      .then((value) => controller = value);
                  _controllerCompleter.complete(c);
                },
                navigationDelegate: (NavigationRequest request) {
                  if (request.url.startsWith('tel:')) {
                    printError('This is an error.');
                    launch(request.url);
                    return NavigationDecision.prevent;
                  }
                  if (request.url.startsWith('mailto:')) {
                    printError('This is an error.');
                    launch(request.url);
                    return NavigationDecision.prevent;
                  }
                  if (request.url.startsWith('https://wa.me/905442854486')) {
                    printError('This is an error.');
                    print('blocking navigation to $request}');
                    return NavigationDecision.prevent;
                  }
                  printError('url' + request.url);
                  return NavigationDecision.navigate;
                },
                gestureNavigationEnabled: true,
              ),
```
</details>
Repository: rust
Issue: Detect intended out argument on mutability and lifetime errors involving fn args
Labels: A-diagnostics,A-lifetimes,T-compiler,A-suggestion-diagnostics,D-newcomer-roadblock

Given code like:

```rust
fn foo(x: &String) {
    let y = "asdf".to_string();
    x = &y;
}
```

we [currently emit](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=dd257a6e7529f899a57540fe9fec3462):

```
error[E0384]: cannot assign to immutable argument `x`
 --> src/main.rs:3:5
  |
1 | fn foo(x: &String) {
  |        - help: make this binding mutable: `mut x`
2 |     let y = "asdf".to_string();
3 |     x = &y;
  |     ^^^^^^ cannot assign to immutable argument

error[E0597]: `y` does not live long enough
 --> src/main.rs:3:9
  |
1 | fn foo(x: &String) {
  |           - let's call the lifetime of this reference `'1`
2 |     let y = "asdf".to_string();
3 |     x = &y;
  |     ----^^
  |     |   |
  |     |   borrowed value does not live long enough
  |     assignment requires that `y` is borrowed for `'1`
4 | }
  | - `y` dropped here while still borrowed
```

We should detect cases like these and instead [suggest making `x: &mut String`](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=94c05485c82d5668d6edc7b422fcd646) which is the more likely desire:

```rust
fn foo(x: &mut String) {
    let y = "asdf".to_string();
    *x = y;
}
```
Repository: rust
Issue: rustdoc: Show generic parameters for item being documented
Labels: T-rustdoc,C-feature-request

Currently, rustdoc does not display generic parameters for the item being documented:

![image](https://user-images.githubusercontent.com/37223377/107578979-4ec35000-6ba9-11eb-9ccc-a1b206278c5c.png)

This can be confusing because you will see generic parameters used that are never documented themselves. This is especially common with enums. As you can see in the image above, the variants section for `std::option::Option` shows the `Some(T)` variant — but where did the `T` come from?

It might be nice to show something like this instead (the difference is the `<T>` added after `std::option::Option` in the header):

![image](https://user-images.githubusercontent.com/37223377/107579144-8df1a100-6ba9-11eb-8e18-3ae241617170.png)
Repository: rust
Issue: rustdoc does not warn when linking to an item with no generated docs
Labels: T-rustdoc,C-bug,A-intra-doc-links

I tried this code:

```rust
//! Link to [S]

#[doc(no_inline)]
pub use inner::S;

mod inner {
    pub struct S;
}
```

I expected to see this happen: Rustdoc warns that the links will all be broken

Instead, this happened: Rustdoc gives no warning and generates HTML that looks bad: 
![image](https://user-images.githubusercontent.com/23638587/107592146-361f5e00-6bda-11eb-9a58-4670becc2e79.png)


### 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.
-->

`rustdoc --version`: rustdoc 1.52.0-nightly (9778068cb 2021-02-07)
Repository: flutter
Issue: Support for ARMv7 (Linux)
Labels: c: new feature,engine,e: embedder,c: proposal,P3,team-engine,triaged-engine

## Use case

There is still plenty of use of 32bit ARM device around, for example the [STM32MP1](https://www.st.com/en/evaluation-tools/stm32mp157c-dk2.html). This device should be very capable of running flutter on top of OpenEmbedded/Yocto Linux.

## Proposal

The flutter engine should compile for running on ARMv7, and be a cross-compile target CPU for Linux.

Flutter was previously able to compile and run for ARMv7, but successive changes including some introduced as part of this [PR](https://github.com/flutter/flutter/pull/61221) have either caused problems in the build process, or caused compilation errors.

Other related issues:
- https://github.com/flutter/flutter/issues/74322
- [maintainer of meta-flutter for yocto, used with stm32mp1](https://github.com/flutter/flutter/issues/56213)
- [flutter-rs engine builds needed to be disabled](https://github.com/flutter-rs/engine-builds)
- [article where ARM was used, no-longer working](https://blog.basyskom.com/2020/how-to-run-flutter-on-an-embedded-device/)
Repository: go
Issue: x/website: workflow documentation for managing transitive deps
Labels: Documentation,NeedsInvestigation,FeatureRequest,modules,website

@stevetraut, @bcmills said I should ping you on this :)

The new [workflow doc](https://golang.org/doc/modules/managing-dependencies) is great, but I had suggestions for workflows to support/document that aren't currently directly covered by any existing docs. The high level questions are:
- How do I unequivocally, permanently exclude a vulnerable version of a module (and all prior versions) from my transitive set, (probably due to a CVE), when the upstream has released a fixed version?
- What is the supported method of generating a complete transitive set of deps, for the purposes of feeding scanning tools that expect to see that? [NexusIQ documents a method](https://help.sonatype.com/iqserver/analysis/go-application-analysis#GoApplicationAnalysis-Whatissupported) (the `go.list` path) but it's not clear that's an intended workflow.


Thanks!
Repository: rust
Issue: Better support for common const generic errors in item definition
Labels: A-diagnostics,T-compiler,A-suggestion-diagnostics,A-const-generics,D-newcomer-roadblock

Given

```rust
struct A<const N: u8>;
impl<N> Display for A<N> {}
```

[we currently emit](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=601e51cff8fc9e780c74d829f7f63f13)

```
error[E0747]: type provided when a constant was expected
 --> src/lib.rs:4:23
  |
4 | impl<N> Display for A<N> {}
  |                       ^
  |
help: if this generic argument was intended as a const parameter, try surrounding it with braces:
  |
4 | impl<N> Display for A<{ N }> {}
  |                       ^   ^
```

[if we follow the suggestion, it will emit](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=8dd7dbc09e6b3879bca992c432c550c4):

```
error[E0423]: expected value, found type parameter `N`
 --> src/lib.rs:4:25
  |
2 | struct A<const N: u8>;
  | ---------------------- similarly named unit struct `A` defined here
3 | 
4 | impl<N> Display for A<{ N }> {}
  |                         ^ help: a unit struct with a similar name exists: `A`

error[E0207]: the type parameter `N` is not constrained by the impl trait, self type, or predicates
 --> src/lib.rs:4:6
  |
4 | impl<N> Display for A<{ N }> {}
  |      ^ unconstrained type parameter
```

The [correct code would have been](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=3ac28a8898599a280c327bcf2bdf57da):

```rust
struct A<const N: u8>;

impl<const N: u8> Display for A<N> {
```

[Another potential mistake is](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=4543a8156e2bc20d265afd384a6279aa)

```rust
impl Display for A<N> {
```
```
error[E0412]: cannot find type `N` in this scope
 --> src/lib.rs:4:20
  |
2 | struct A<const N: u8>;
  | ---------------------- similarly named struct `A` defined here
3 | 
4 | impl Display for A<N> {
  |                    ^ help: a struct with a similar name exists: `A`

error[E0747]: type provided when a constant was expected
 --> src/lib.rs:4:20
  |
4 | impl Display for A<N> {
  |                    ^
  |
help: if this generic argument was intended as a const parameter, try surrounding it with braces:
  |
4 | impl Display for A<{ N }> {
  |                    ^   ^
```

We should handle at least these three cases and actually suggest the right code.

<!-- TRIAGEBOT_START -->

<!-- TRIAGEBOT_ASSIGN_START -->

<!-- TRIAGEBOT_ASSIGN_DATA_START$${"user":"henryboisdequin"}$$TRIAGEBOT_ASSIGN_DATA_END -->

<!-- TRIAGEBOT_ASSIGN_END -->
<!-- TRIAGEBOT_END -->
Repository: ant-design
Issue: Useful Form instance modifications
Labels: Inactive

- [x] I have searched the [issues](https://github.com/ant-design/ant-design/issues) of this repository and believe that this is not a duplicate.

### What problem does this feature solve?
This issue will cover four topics.
1) Adding `getAllFieldNames` prop to useForm (form instance). [priority low]
2) Modifying `isFieldTouched` and `isFieldsTouched` [priority high]
3) Adding `isFieldVisited` and `isFieldsVisited` props. [priority high]
4) Adding `isFieldValidated` and `isFieldsValidated` props [priority high]

Some more advanced (and useful) features could be implemented with the form instance.

1) Adding `getAllFieldNames` prop to useForm (form instance).
var listOfFieldNames = formInstance.getAllFieldNames();
This would help reduce hard-coded attempts to build a list of field names. A list of field names is required for the majority of the form instance props. If a field is changed within the form, we usually face having to modify a hard-coded list if we use any of the form instance props. This might not be as important of a problem to address, but would drastically improve usability of the form instance. This would be a modification to [rc/field-form](https://github.com/react-component/field-form) I believe.
2) Modifying `isFieldTouched` and `isFieldsTouched` 
While experimenting with the usage of the isFieldTouched and isFieldsTouched, I found that 'touched' in this context really means 'modified'. For example, if I tab through all of the fields on a form, isFieldsTouched will be false. I suggest that `isFieldTouched` and `isFieldsTouched` should be renamed to `isFieldModified` and `isFieldsModified` respectively. This makes more semantic sense when referencing functionality of this feature, which leads me to number 3.
3) Adding `isFieldVisited` and `isFieldsVisited` props.
Currently, there is no way to tell if a field has been visited (which is originally what I thought `isFieldTouched` did). Adding this prop to form instance would allow full semantic coverage of what was confusing about `isFieldTouched`. This prop would perhaps keep track of the blur event of each field and if it has fired (not if it has been modified or not).
4) Adding `isFieldValidated` and `isFieldsValidated` props [priority high]
This would allow a check if a field has been previously validated already.

### What does the proposed API look like?
The API would be similar to how the form instance props work, just modifying functionality of `isFieldTouched` and `isFieldsTouched` as well as adding a `getAllFieldNames`, `isFieldVisited`, `isFieldsVisited`, `isFieldValidated`, and `isFieldsValidated` props.


<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: flutter
Issue: Font weight light (anything < 400) does not render correctly in Flutter Web
Labels: c: regression,engine,a: typography,platform-web,c: rendering,e: web_canvaskit,has reproducible steps,P2,found in release: 2.10,found in release: 2.13,team-web,triaged-web

### Steps to reproduce
1. Create a Flutter project
2. Add a Text Widget with font weight < 400 (e.g. w300)
3. Compile it for Flutter Web and view it in Chrome

### Actual Behaviour
The Text Widget is rendered with font weight normal

### Expected Behaviour
The Text Widget is rendered with a light font weight (< 400).




When running the same application on Android, the font weight is rendered correctly.

```
❯ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, 1.27.0-2.0.pre.43, on Linux, locale en_US.UTF-8)
[✓] Android toolchain - develop for Android devices (Android SDK version 30.0.2)
[✓] Chrome - develop for the web
[✓] Android Studio
[✓] Connected device (1 available)

• No issues found!
```
```
❯ flutter --version
Flutter 1.27.0-2.0.pre.43 • channel master • https://github.com/flutter/flutter.git
Framework • revision 16af4aa7eb (25 hours ago) • 2021-02-10 17:01:04 +0800
Engine • revision b3a18f5182
Tools • Dart 2.13.0 (build 2.13.0-15.0.dev)
```


Thanks in advance!
Best regards

Julian
Repository: transformers
Issue: Text to Speech Generalized End-To-End Loss for Speaker Verification, Real Time Voice Cloning
Labels: New model,Feature request

# 🌟 New model addition

## Model description
Generalized End-To-End Loss for Speaker Verification implements Real time voice cloning, a way to generate a Text-To-Speech model adapted to a certain speaker with a short audio sample. The model implements the following paper.
https://arxiv.org/pdf/1806.04558.pdf and the code is available on github.

https://github.com/CorentinJ/Real-Time-Voice-Cloning

<!-- Important information -->

## Open source status

* [ ] the model implementation is available: (give details)
https://colab.research.google.com/drive/1SUq5RLOI0TIMkrBzMHMms01aaVNgkO7c?usp=sharing

The model can be run through Colaboratory. Here is an example of a generated voice.
https://soundcloud.com/birger-mo-ll/generated-voice

* [ ] the model weights are available: (give details)
Here are the model weights that are used.

encoder.load_model(project_name / Path("encoder/saved_models/pretrained.pt"))
synthesizer = Synthesizer(project_name / Path("synthesizer/saved_models/logs-pretrained/taco_pretrained"))
vocoder.load_model(project_name / Path("vocoder/saved_models/pretrained/pretrained.pt"))

* [ ] who are the authors: @CorentinJ
The author is not currently working on the repo, but since it is a fairly popular repo (25.000 stars) it might be reasonable to take the time to explore how to recreate / adapt the model to work with Huggingface transformer.
Repository: node
Issue: big-string will cause heap out of memory
Labels: memory

* **Version**:tested on bth v16.0.0-pre. and v12.18.2
* **Platform**:linux
* **Subsystem**:ubuntu

### What steps will reproduce the bug?

just use a big-string,  each string-chunk is about 30M 
the string only contains  [0-9]+

### How often does it reproduce? Is there a required condition?

always

### What is the expected behavior?

I dont know, just want to known if this is a limitation

### What do you see instead?

```
big-string will cause heap out of memory

each string-chunk is about 30M,such as 28091184 , the string only contains  [0-9]+


==== JS stack trace =========================================

    0: ExitFrame [pc: 0x13c5b79]
Security context: 0x2ef9089008d1 <JSObject>
    1: _next [0x5b7c2c01391] [repl:~1] [pc=0x7d4c348ebf4](this=0x33fba72801e9 <JSGlobal Object>,0x1827ee180119 <Very long string[28091184]>)
    2: gen [0x5b7c2c102c1] [repl:8] [bytecode=0x9937cfe4441 offset=134](this=0x33fba72801e9 <JSGlobal Object>,0x0ae7e62c4149 <String[#1]: 1>)
    3: next [0x2ef908923139](this=0x33fba72b3bb9 <JSGenerator>)
    4: /* anonymou...

```


### Additional information
Repository: pytorch
Issue: Build using Py_LIMITED_API and then build wheels with the stable ABI abi3 tag
Labels: module: binaries,module: performance,oncall: releng,triaged

## 🚀 Feature
Pytorch could build python c-extension modules with `#define Py_LIMITED_API`, which would allow using the stable ABI `abi3` tag, so that one c-extension module (and wheel) would work on multiple CPython versions.
## Motivation
Limit the number of wheels needed for each release

## Pitch

PyTorch wheels are very large, straining the PyPI infrastructure as well as requiring significant resources on a user' machine. Providing a more universal wheel would ease that burden

## Alternatives



## Additional context

The [1.7.1 release](https://pypi.org/project/torch/#files) has 12 wheels: 3 for each python version 3.6, 3.7, 3.8, 3.9. If sucessful, this enhancement would reduce that to 3 wheels.

cc @ezyang @seemethere @malfet @walterddr @VitalyFedyunin @ngimel
Repository: vscode
Issue: find not working correctly for regular expression containing asterisk wildcard
Labels: feature-request,editor-find

I am trying to find with regex "[^\t]*" in a tab delimited file

paste the following contents in vs code in untitled buffer where fields are delimited by tabs
f1	f2
f3	f4
f5	f6

then try to find in regex mode with regular expression "[^\t]*"
observe that it finds only f1,f3 and f5 and completely ignores fields in second column. *  means it should match zero of more characters, so it should match fields in second column.

if I try to find with regex "[^\t]+" it works correctly and does find fields in second column.

details about the VS code build I am using:
Version: 1.53.1
Commit: 5d424b828ada08e1eb9f95d6cb41120234ef57c7
Date: 2021-02-08T23:35:15.302Z (2 days ago)
Electron: 11.2.1
Chrome: 87.0.4280.141
Node.js: 12.18.3
V8: 8.7.220.31-electron.0
OS: Darwin x64 19.6.0
Repository: vscode
Issue: Find widget focus movement could be improved
Labels: feature-request,accessibility,polish,editor-find

I am looking into improving the tab focus navigation across the workbench such that each ActionBar is one tab, and inside it you would have to user arrow navigation to move focus.
I have run across the find widget and there I see we do quite some custom solutions. So wanted to first create this issue to show what currently does not work (independent of changes which I would like to do).

1. Open find widget
2. You can not focus onto `Find In Selection` button 🐛 
3. You can use `left` / `right` arrow navigation inside the find input, but not for the find widget buttons on the right 🐛