sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [caffe2] Fails to build with fbgemm enabled
Labels: caffe2

## 🐛 Bug

Caffe2 git master fails to build with fbgemm enabled (`USE_FBGEMM:BOOL='ON'`), giving the following error:
```
[ 45%] Building CXX object caffe2/quantization/server/CMakeFiles/caffe2_dnnlowp_avx2_ops.dir/elementwise_sum_dnnlowp_op_avx2.cc.o
In file included from /storage/linux/abs/caffe2-git/src/pytorch/caffe2/quantization/server/dnnlowp.h:11,
                 from /storage/linux/abs/caffe2-git/src/pytorch/caffe2/quantization/server/caffe2_dnnlowp_utils.h:4,
                 from /storage/linux/abs/caffe2-git/src/pytorch/caffe2/quantization/server/utility_dnnlowp_ops.h:4,
                 from /storage/linux/abs/caffe2-git/src/pytorch/caffe2/quantization/server/elementwise_sum_dnnlowp_op_avx2.cc:1:
/storage/linux/abs/caffe2-git/src/pytorch/third_party/fbgemm/include/fbgemm/QuantUtils.h:9:10: fatal error: cpuinfo.h: No such file or directory
 #include <cpuinfo.h>
          ^~~~~~~~~~~
compilation terminated.
make[2]: *** [caffe2/quantization/server/CMakeFiles/caffe2_dnnlowp_avx2_ops.dir/build.make:63: caffe2/quantization/server/CMakeFiles/caffe2_dnnlowp_avx2_ops.dir/elementwise_sum_dnnlowp_op_avx2.cc.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:4460: caffe2/quantization/server/CMakeFiles/caffe2_dnnlowp_avx2_ops.dir/all] Error 2
make: *** [Makefile:141: all] Error 2
```
This error seems to be caused by the recent commit https://github.com/pytorch/pytorch/commit/fb8c3d62feacf5c3d39f6fb034db944a89a0bcf4. It was building fine some commits before it.

## To Reproduce

Steps to reproduce the behavior:

1. mkdir build
1. cd build
1. [cmake options](https://bpaste.net/show/ca5a7eb99368)
1. make -j1

## Expected behavior

A succesful build with fbgemm enabled.

## Environment

 - **PyTorch Version:** git master (currently at https://github.com/pytorch/pytorch/commit/f79fb58744ba70970de652e46ea039b03e9ce9ff)
 - **OS:** Arch Linux x86_64
 - **How you installed PyTorch:** source
 - **Build command you used (if compiling from source):** already shown above
 - **Python version:** 3.7.1
 - **CUDA/cuDNN version:** not enabled in this example
 - **GPU models and configuration:** not enabled in this example
 - **Compiler:** gcc 8.2.1
 - **Any other relevant information:** the same error occurs when enabling cuda and using gcc 7.3.1

## Additional context

It builds fine when disabling fbgemm (`USE_FBGEMM:BOOL='OFF'`).
Repository: flutter
Issue: AndroidView is offsetted and clipped on some Xiaomi devices with a notch
Labels: e: device-specific,platform-android,engine,a: platform-views,P3,team-android,triaged-android

When running the [webview_flutter](https://github.com/flutter/plugins/tree/master/packages/webview_flutter) example on a device with a notch, a blank bar apears on the top of the native view, below the app bar. The platform view responds to touches with a vertical offset (one must touch above the point). #19030 

![screenshot_2018-11-22-15-39-43-001_com example webviewtest](https://user-images.githubusercontent.com/367621/48907384-ea086780-ee6f-11e8-9d05-63580a8d90de.png)
Repository: TypeScript
Issue: ts error should better explain that import is a reserved keyword for a function name
Labels: Suggestion,Effort: Moderate,Domain: Error Messages,Experience Enhancement

<!-- 🚨 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 `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.1.6

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
import
import keyword
keyword
**Code**

given the following code with a function named `import` :disappointed: :    
```ts
export function	import(pad_id: number, config: Config, csvRows: string[][], externalCallback: (err?: Error | null, data?: string[]) => void) {
...
```

![image](https://user-images.githubusercontent.com/7466144/48909948-f7712200-ee6e-11e8-895b-09281ba0f0da.png)


**Expected behavior:**

A clear error message explaining that import is a reserved keyword

**Actual behavior:**

A cryptic error message telling that there's a missing semicolumn :  

![image](https://user-images.githubusercontent.com/7466144/48910022-2d160b00-ee6f-11e8-89be-c644ec992da0.png)


**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->

**Related Issues:** <!-- Did you find other bugs that looked similar? -->

didn't found any
Repository: rust
Issue: Tracking issue for HashMap::raw_entry
Labels: A-collections,T-libs-api,B-unstable,C-tracking-issue,finished-final-comment-period,disposition-close,Libs-Tracked,S-tracking-design-concerns

Added in #54043.

----

As of 6ecad338381cc3b8d56e2df22e5971a598eddd6c / 2019-01-09, this feature covers:

```rust
impl<K, V, S> HashMap<K, V, S>
    where K: Eq + Hash,
          S: BuildHasher
{
    pub fn raw_entry(&self) -> RawEntryBuilder<K, V, S> {…}
    pub fn raw_entry_mut(&mut self) -> RawEntryBuilderMut<K, V, S> {…}
}

pub struct RawEntryBuilder<'a, K: 'a, V: 'a, S: 'a> {…} // Methods return Option<(&'a K, &'a V)>
pub struct RawEntryBuilderMut<'a, K: 'a, V: 'a, S: 'a> {…} // Methods return RawEntryMut<'a, K, V, S>
pub enum RawEntryMut<'a, K: 'a, V: 'a, S: 'a> {
    Occupied(RawOccupiedEntryMut<'a, K, V>),
    Vacant(RawVacantEntryMut<'a, K, V, S>),
}
pub struct RawOccupiedEntryMut<'a, K: 'a, V: 'a> {…}
pub struct RawVacantEntryMut<'a, K: 'a, V: 'a, S: 'a> {…}
```

… as well as `Debug` impls for each 5 new types, and their inherent methods.
Repository: vscode
Issue: Centered editor layout: top and bottom padding
Labels: feature-request,workbench-zen

I don't like Zen mode taking full screen. I want some padding on top and bottom. Here's what I get in Vim with https://github.com/junegunn/goyo.vim:

<img width="946" alt="image" src="https://user-images.githubusercontent.com/4033249/48916946-41d7ac00-ee39-11e8-9cc9-c51a87e69653.png">
Repository: ant-design
Issue: Form: 为 onFieldsChange() 提供一个无 nested 版本
Labels: Inactive,IssueHuntFest

- [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?
有这么一个需求：

在表单任意表单域控件的 onChange 且 newValue **通过 validator** 后, 收集到最新的数据变更
（且此时我并不知道有哪些 field）

研究了一下 API 后, 我觉得 使用 `onFieldChange` 这个方法最能符合这个需求

但是目前的 form 内部会将符合 nested 规则的 field name nested 化, `onFieldChange` 方法返回的 changedValue 和 allValue 也都是 nested 化的, 这导致我无法通过一个很直接的方法来判断 changedValue 这个对象的每一个 property 的 value 是 Field 对象还是一个 nested object

### What does the proposed API look like?
（想到的一个做法：）新增加一个函数, 相比目前的 `onFieldsChange` 函数, 其返回的 field 全部是未经 nested 的, 来允许用户方便的获取所有 value

（或者 antd 的 Form 如果暴露出 rc-form/createFormField.js 的 `isFormField` 方法的话, 似乎也可以用）

### BTW 这个函数的文档有问题

看了下 rc-form 的代码， 其 `onFieldsChange`函数的参数与文档中介绍的参数、 `Form.tsx` 的对应 interface 声明的参数都是不一致的
rc-form 的代码有三个参数：
`onFieldsChange(this.props, changedFields, this.fieldsStore.getNestedAllFields());`
( https://github.com/react-component/form/blob/master/src/createBaseForm.js#L286 )
而 ant.design 对应的文档只有两个参数：
https://github.com/ant-design/ant-design/blob/master/components/form/index.zh-CN.md#formcreateoptions
而 `Form.tsx` 中的接口定义有四个参数：
https://github.com/ant-design/ant-design/blob/master/components/form/Form.tsx#L22 

<!-- generated by ant-design-issue-helper. DO NOT REMOVE -->
Repository: javascript-algorithms
Issue: detect-cycle-algorithms detect just one cycle
Labels: enhancement

The detect-cycle-algorithms detect just one cycle.
It would be great if the algorithms can recognize more cycles than one, in case there are several.
Repository: angular
Issue: Animations: animateChild() fails to run child transitions when using state() with '*' star style
Labels: type: bug/fix,area: animations,freq2: medium,P3


# 🐞 bug report

### Affected Package
@angular/animations

### Description

When an animation uses states to/from the '*' star style, animateChild() fail to run the transition to the  "starred" state and jumps to the final state instead (or run the transition from the final state to the same). 

## 🔬 Minimal Reproduction
Take a look here:
https://stackblitz.com/edit/wizdm-animatechild-toggler?file=src%2Fapp%2Fmat-toggler%2Fmat-toggler-animations.ts

## 🌍  Your Environment

**Angular Version:**
Angular CLI: 7.0.5
Node: 9.11.1
OS: darwin x64
Angular: 7.0.3
... animations, cdk, common, compiler, compiler-cli, core, forms
... http, language-service, material, material-moment-adapter
... platform-browser, platform-browser-dynamic, router

Package                            Version
------------------------------------------------------------
@angular-devkit/architect          0.8.6
@angular-devkit/build-angular      0.10.2
@angular-devkit/build-ng-packagr   0.8.6
@angular-devkit/build-optimizer    0.10.2
@angular-devkit/build-webpack      0.10.2
@angular-devkit/core               0.8.6
@angular-devkit/schematics         7.0.5
@angular/cli                       7.0.5
@angular/fire                      5.1.0
@angular/flex-layout               7.0.0-beta.19
@ngtools/json-schema               1.1.0
@ngtools/webpack                   7.0.2
@schematics/angular                7.0.5
@schematics/update                 0.10.5
ng-packagr                         4.4.0
rxjs                               6.3.3
typescript                         3.1.6
webpack                            4.19.1

**Anything else relevant?**
building on macOS, running on both Chrome & Safari.

Thanks,
Repository: node
Issue: Does `autoDestroy` make sense for http2 streams?
Labels: question,http2

<!--
Thank you for reporting an issue.

This issue tracker is for bugs and issues found within Node.js core.
If you require more general support please file an issue on our help
repo. https://github.com/nodejs/help


Please fill in as much of the template below as you're able.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify affected core module name

If possible, please provide code that demonstrates the problem, keeping it as
simple and free of external dependencies as you are able.
-->

* **Subsystem**: http2

Now that we have `autoDestroy` support in the streams implementation, I think we would like to move streams towards using that option if possible. I have a hard time figuring out if this makes sense for HTTP/2 streams? (i.e., should we destroy streams once both readable and writable side are finished?)

I have a hard time understanding HTTP/2 stream’s lifecycle behaviour, to be honest, and I’d appreciate any explanations about it :)

/cc @nodejs/http2 @mcollina
Repository: nvm
Issue: `nvm install-latest-npm`: unknown issue
Labels: installing node,needs followup

<!-- 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:

- `nvm debug` output:
<details>
<!-- do not delete the following blank line -->

```sh

```
</details>

- `nvm ls` output:
<details>
<!-- do not delete the following blank line -->

```sh

```
</details>

- How did you install `nvm`? (e.g. install script in readme, Homebrew):

- What steps did you perform?

- What happened?

- What did you expect to happen?

- Is there anything in any of your profile files (`.bashrc`, `.bash_profile`, `.zshrc`, etc) that modifies the `PATH`?

<!-- if this does not apply, please delete this section -->
- 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: opencv
Issue: Inclusion of JABCode and HiQ
Labels: feature,category: objdetect,GSoC,evolution,effort: few weeks

# Introduction
JABCode is a color barcode used by the German government (Federal Office of Information Security) for tagging items. Currently there is no easy-to-use solutions available for the public to test and experiment.

HiQ is a color barcode based on QR code, created by the students Hong Kong Chinese University (the top University of Hong Kong).

# Proposed Solution
1. The inclusion of JABCode and HiQ into OpenCV
2. The allowance of Python, JS and Java APIs in their respective package repos for ease of use

# Impact on existing code
## For JABCode
There is no compatibility problem for JABCode inclusion, as this is written in C (moving to C++ should be easy), and the code for JABCode is licensed under LGPL.
## For HiQ
For HiQ the source code is written in Java, uses ZXing, and the license is  Apache 2.0. It would be great if the code is rewritten in C/C++. Also HiQ

# References
## For JABCode
* Repo https://github.com/jabcode/jabcode
* Website https://jabcode.org/
* Standard https://www.bsi.bund.de/EN/Publications/TechnicalGuidelines/TR03137/TechnicalGuidelines_03137_node.html
## For HiQ
* Repo https://github.com/ouyangzhibo/HiQ-Robust-and-Fast-Decoding-of-High-Capacity-Color-QR-Codes
* Website http://authpaper.net/
Repository: pytorch
Issue: [jit][script] support slicing with tensor literals
Labels: oncall: jit

See #14311 for context.
```py
@torch.jit.script
def foo():
    a = torch.rand(3, 4, 5, 6)
    a[[0, 2], :, [3, 1]] = 1
    # and
    a[[0, 2], 1:3, [3, 1]] = 1
    return a
```
Gets tripped up, interpreting tensor literals as `int[]`.
Repository: rust
Issue: Expose Windows VolumeSerialNumber and FileIndex/FileId in std::os::windows::fs::MetadataExt
Labels: O-windows,T-libs-api,A-io

Currently, using `std::os::unix::fs::MetadataExt` and `std::os::linux::fs::MetadataExt` it is possible to get the inode number of a file. This can be useful in determining whether two files are the same. There's a similar concept in Windows, consisting of a few parts:

`VolumeSerialNumber`: The serial number of the volume that contains the file.
`FileIndex`: A 64 bit unique (within a volume) identifier that is associated with a file.
`FileId`: A 128 bit unique (within a volume) identifier that is associated with a file (this is the "evolution" of the above, according to the docs currently only used by ReFS).

Sources: [_BY_HANDLE_FILE_INFORMATION](https://docs.microsoft.com/en-us/windows/desktop/api/fileapi/ns-fileapi-_by_handle_file_information) [_FILE_ID_INFO](https://docs.microsoft.com/en-us/windows/desktop/api/winbase/ns-winbase-_file_id_info)

Combining the `VolumeSerialNumber` and `FileIndex`/`FileId` of a file is thus a unique identifier of a file on a single machine (at a given time; unique IDs may be reused).

I would like these to get added to `std::os::windows::fs::MetadataExt`. The changes needed would be fairly tiny (literally just exposing already available data in case of `VolumeSerialNumber` and `FileIndex` [here](https://github.com/rust-lang/rust/blob/6a2d1b4e15d5de90f8c36181b1d429da658adfd2/src/libstd/sys/windows/fs.rs#L299-L309) but an additional function call for `FileId`), and it wouldn't introduce any breaking changes as far as I can see, it would only add 2/3 methods. Would this require an RFC?

I see that the RFCs README lists "Additions to std." as an as example, but on the other hand I wouldn't say this is a "substantial" change.
Repository: go
Issue: net/http: logic error in http2ConfigureServer?
Labels: NeedsInvestigation

Reported against tip, 649b89377e91ad6dbe710784f9e662082d31a1ff

https://github.com/golang/go/blob/649b89377e91ad6dbe710784f9e662082d31a1ff/src/net/http/h2_bundle.go#L4021

the logic of this line is error(ValidCipher, BadCipher,BadCipher will go through), it should be 
```go
if http2isBadCipher(cs) {
    sawBad = true
} 
if sawBad {
    return fmt.Errorf("http2: TLSConfig.CipherSuites index %d contains an HTTP/2-approved cipher suite (%#04x), but it comes after unapproved cipher suites. With this configuration, clients that don't support previous, approved cipher suites may be given an unapproved one and reject the connection.", i, cs)
}
```
Repository: go
Issue: x/image/font: wrong rendering of intersecting paths
Labels: NeedsInvestigation

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.11.1 windows/amd64
</pre>

### What did you do?
Parse APL386 true type font with github.com/golang/freetype/truetype and render U+2262 with golang.org/x/image/font Drawer.DrawString.

I'll update with a link to example code and images shortly.

### What did you expect to see?
A rendering of the rune, that has intersecting paths. The intersecting regions should be filled (with black color).

### What did you see instead?
Intersecting regions are not filled, they are left white.
Repository: rust
Issue: Enhance `match` implied borrow
Labels: C-enhancement,A-borrow-checker,T-compiler

```rust
struct Foo {
    bar: Option<String>
}

fn f(foo: &Foo) -> i32 {
    match &foo.bar {
        None => 1,
        Some(s) => 2,
    }
}
```

The above works because of the implied borrow introduced in v1.26

However, if we don't put `&` before `foo.bar`, the `ref` is mandatory.

```rust
fn f(foo: &Foo) -> i32 {
    match foo.bar {
        None => 1,
        Some(ref s) => 2,
    }
```

Is it a good idea in this case that the compiler also implicitly adds `ref` for us, since we cannot move `foo.bar` anyway.
Repository: pytorch
Issue: Caffe2 C++ tutorial is not working
Labels: caffe2

## 📚 Documentation

<!-- A clear and concise description of what content in https://pytorch.org/docs is an issue. If this has to do with the general https://pytorch.org website, please file an issue at https://github.com/pytorch/pytorch.github.io/issues/new/choose instead. If this has to do with https://pytorch.org/tutorials, please file an issue at https://github.com/pytorch/tutorials/issues/new -->

The steps explained in https://caffe2.ai/docs/cplusplus_tutorial.html are not working to build C++ code with Caffe2. 
The first issue is to generate .cc files from .proto files. After trying different command line combination from https://github.com/protocolbuffers/protobuf/issues/3028 I was able to generate it.

Then I created a VS solution following described steps and add the include directories. I got this error:
```
"fatal error C1083: Cannot open include file: 'c10/macros/cmake_macros.h': No such file or directory"
```
This is due the following piece of code in Macros.h:
```
#ifndef C10_USING_CUSTOM_GENERATED_MACROS
#include "c10/macros/cmake_macros.h"
#endif // C10_USING_CUSTOM_GENERATED_MACROS
```
So I defined C10_USING_CUSTOM_GENERATED_MACROS to 1. Then I started getting this error:
```
"Cannot open include file: 'ATen/core/blob.h': No such file or directory"
```
So I added the ATen/core to include directories and now I'm receiving a lot o errors.

Is the Caffe2 still supported with C++ building in Windows ??
Repository: rust
Issue: warning for UB `!` exprs is too light
Labels: A-type-system,C-enhancement,A-lints,A-diagnostics,E-needs-test,T-lang,T-compiler,T-types

So this code produces a warning about the `&*input` expression being unreachable:

```rust
enum Void { };

fn process(input: *const Void) {
   let _input = &*input;
}
```

```
warning: unreachable expression
```

I can imagine this needs to "only" be a warning so someone can write some really janky macro code that very carefully ensures the expression isn't ever evaluated. Even if that's the case, I would appreciate that this get its own error-code, or just stronger language to indicate to the user that they are doing something Very Bad. In particular I believe evaluating this expr is Undefined Behaviour.
Repository: nvm
Issue: [Bug] Install scripts do not create ~/.nvm
Labels: needs followup,installing nvm: profile detection,shell: zsh: oh-my-zsh

(Deleted the template since it is for post-installation bugs)

OS: Ubuntu 18.10
Shell: zsh (oh-my-zsh)

When installing with either `wget` or `curl` in the README, I get the following error:
```
You have $NVM_DIR set to "/home/kuech/.nvm", but that directory does not exist. Check your profile files and environment.
```

Creating `~/.nvm` prior to running the scripts solves the issue
Repository: rust
Issue: Implement `CoerceUnsized` and `DispatchFromDyn` for `ManuallyDrop`
Labels: T-lang

Add the following impls:

```rust
impl<T: ?Sized, U: ?Sized> CoerceUnsized<ManuallyDrop<T>> for ManuallyDrop<U>
where
    T: CoerceUnsized<U>,
{}

impl<T: ?Sized, U: ?Sized> DispatchFromDyn<ManuallyDrop<T>> for ManuallyDrop<U>
where
    T: DispatchFromDyn<U>,
{}
```

And add a test case that is allowed by these impls.

This will allow `ManuallyDrop<Box<T>>` to be unsized to `ManuallyDrop<Box<dyn Trait>>`, and allow `ManuallyDrop<Box<Self>>` to be used as a trait-object-safe method receiver with the `arbitrary_self_types` feature. And similarly for other pointer types besides `Box`.

Example test case:

```rust
trait Trait {
    fn foo(self: ManuallyDrop<Box<Self>>) -> i32;
}

impl Trait for i32 {
    fn foo(self: ManuallyDrop<Box<Self>>) -> i32 {
        self
    }
}

fn main() {
    let x = ManuallyDrop::new(Box::new(5i32)) as ManuallyDrop<Box<dyn Trait>>;
    assert_eq!(x.foo(), 5);
}
```

This affects stable code, by allowing unsize coercions that were not previously allowed (e.g. from `ManuallyDrop<Box<T>` to `ManuallyDrop<Box<U>>` where `T: Unsize<U>`), so I guess it requires an FCP.
Repository: kubernetes
Issue: Kubelet does not restart or reregister in response to removed Node API object
Labels: kind/bug,sig/node,sig/cluster-lifecycle,priority/important-longterm,lifecycle/frozen,triage/accepted

Once a kubelet has started up, if its Node API object is removed, the kubelet perpetually attempts and fails to update the status on the now-missing Node object.

I would have expected it to do one of the following:
* exit after a period of time or number of retries
* re-register the Node object

/kind bug
/sig node