sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: [caffe2] Implement Gather for any value of `axis`
Labels: caffe2

Fix this: https://github.com/pytorch/pytorch/blob/master/caffe2/onnx/backend.cc#L629 which is because the implementation of Gather does not support axes other than 1
Repository: pytorch
Issue: Where could I see all of the caffe2 operators and their arguments in python API?
Labels: caffe2

Thanks for publishing the caffe2 and it is an excellent deep learning framework. I am wondering that how could I see all of the caffe2 operators. I see the caffe2 operators catalog https://caffe2.ai/docs/operators-catalogue.html but it might not cover all of the operators. For example, I could apply an operator called 'SmoothL1Loss' by model.net.SmoothL1Loss() but it is not in the website. 
In addition, how could I know all of the arguments of these operators in python API? For example, I can apply convolutional layer by model.Conv(input, output, 3, 64, 3), how could I know other arguments' name?

Thank you very much!
Repository: opencv
Issue: The parameter types for cv::solvePnP() is misleading
Labels: bug,category: calib3d

<!--
If you have a question rather than reporting a bug please go to http://answers.opencv.org where you get much faster responses.
If you need further assistance please read [How To Contribute](https://github.com/opencv/opencv/wiki/How_to_contribute).

Please:

* Read the documentation to test with the latest developer build.
* Check if other person has already created the same issue to avoid duplicates. You can comment on it if there already is an issue.
* Try to be as detailed as possible in your report.
* Report only one problem per created issue.


This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library.
-->

##### System information (version)
<!-- Example
- OpenCV => 3.1
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2015
-->

- OpenCV => master


##### Detailed description
See the code
https://github.com/opencv/opencv/blob/ee1e1ce377aa61ddea47a6c2114f99951153bb4f/modules/calib3d/include/opencv2/calib3d.hpp#L692-L695

`rvec` and `tvec` are of type `OutputArray` indicating that they are used only for ouput.

But the code
https://github.com/opencv/opencv/blob/ee1e1ce377aa61ddea47a6c2114f99951153bb4f/modules/calib3d/src/solvepnp.cpp#L58
https://github.com/opencv/opencv/blob/ee1e1ce377aa61ddea47a6c2114f99951153bb4f/modules/calib3d/src/solvepnp.cpp#L71-L79
treats them as input when `useExtrinsicGuess==true`.
<!-- your description -->

##### Suggestions
The prototype should be decalared as `InputOutputArray`.

<!-- to add code example fence it with triple backticks and optional file extension
    ```.cpp
    // C++ code example
    ```
 or attach as .txt or .zip file
-->
Repository: vscode
Issue: [html] Support SCSS in HTML with <style type="text/scss">
Labels: feature-request,html

I'm using a framework that lets me write SCSS code in HTML files, by marking them in a block with `<style type="text/scss">`. While VS Code seems to be perfectly fine with SCSS, it doesn't seem to support it inside a HTML file. As such, I get errors from the CSS parsers when using SCSS features, IntelliSense isn't working, etc.
Repository: pytorch
Issue: [Caffe2] [Question] How to disable the bias parameter?
Labels: caffe2

Is there any way to disable the bias parameter for a specific layer, e.g., for convolution layer? Is there something like **bias_term=[true or false] from Caffe**?
Repository: pytorch
Issue: Error when building 
Labels: caffe2

Hello, 
when I build , there is an error after "FULL_CAFFE2=1 python setup.py install".
/usr/local/lib/libopencv_imgcodecs.so.3.3: undefined reference to `TIFFReadEncodedStrip@LIBTIFF_4.0'
/usr/local/lib/libopencv_imgcodecs.so.3.3: undefined reference to `TIFFSetField@LIBTIFF_4.0'
/usr/local/lib/libopencv_imgcodecs.so.3.3: undefined reference to `TIFFSetWarningHandler@LIBTIFF_4.0'
/usr/local/lib/libopencv_imgcodecs.so.3.3: undefined reference to `TIFFSetErrorHandler@LIBTIFF_4.0'
/home/xuran/Detectron/pytorch/build/lib/libcaffe2.so: undefined reference to `leveldb::Status::ToString() const'
/home/xuran/anaconda3/lib/libleveldb.so.1: undefined reference to `std::__cxx11::basic_string<char, std::char_traits<char>, std::allocator<char> >::_M_create(unsigned long&, unsigned long)@GLIBCXX_3.4.21'
collect2: error: ld returned 1 exit status
make[2]: *** [bin/stream_test] Error 1
make[1]: *** [caffe2/CMakeFiles/stream_test.dir/all] Error 2
make: *** [all] Error 2
Failed to run 'bash ../tools/build_pytorch_libs.sh --use-cuda --use-nnpack --full-caffe2 caffe2 libshm gloo THD c10d'
Can you help me ? Thank you .
Repository: vue
Issue: An anti-pattern in computed property may cause performance issue
Labels: has PR

### Version
2.5.17

### Reproduction link
[https://codesandbox.io/s/140202wlq](https://codesandbox.io/s/140202wlq)





### Steps to reproduce
Open the code sandbox link and click the button to use the computed property 'filteredEntities', and you will find it cost a lot of time.

After check the call tree, I found this is because the code calls the getter of 'entities'  many times which will then call the `dependArray` function.

The code leading to this is:
```js
const len = this.entities.length;
for (let i = 0; i < len; i++) {
  const e = this.entities[i];
  // do something with e
}
```
If this.entities has a length of n, its getter will be called n + 1 times. And every time when the getter was called, it will call dependArray on the value of this.entities, which is the array with length n.
Since dependArray will iterate the value, the depend function will be called **(n + 1)^2** times totally.

I found this code when I'm reviewing someone's PR, and the original code use `for (let i = 0; i < this.entities.length; i++) ` and make another n times call to the getter.

It was easy to avoid this problem, such as using some array methods like `filter` to only call getter once.
Even cache the value of entities by `const cache = this.entities` can solve it.

Although it was easy to avoid of this pattern, I still think it is dangerous because the original code was not an obvious anti-pattern.
And this will not show any performance issue when the array is small, but may cause serious performance issue when the array is large in some production environment.

### What is expected?
I've read the related source code and I think this is the expected result of the observer system.

Then I read some chapter of the guide again to ensure there is no mention about this, so I'm not sure whether we need to add this as a NOT TODO in the computed property chapter.

### What is actually happening?
Described.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: vscode
Issue: Git - Linux ssh-agent/ssh-askpass problem
Labels: bug,git

<!-- Please search existing issues to avoid creating duplicates. --> 
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

As already reported in #33814, #32097, #52137 the bug isn't fixed for me and the workarounds don't work either

<!-- Use Help > Report Issue to prefill these. -->
```
VSCode Version: 1.26.1
OS Version: Ubuntu 16.04
Date: 2018-08-16T18:34:20.517Z
Electron: 2.0.5
Chrome: 61.0.3163.100
Node.js: 8.9.3
V8: 6.1.534.41
Architecture: x64
Shell: zsh
```

Steps to Reproduce:

1. Open a Git repo folder
2. Call a Git action like sync, push etc

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes



I'm using ssh-agent to keep all my keys opened and enter the passwords after I boot (`ssh-add ~/.ssh/id_rsa`). I can use git from the terminal without any problems, but "use the terminal then" is not a valid workaround for me when a whole feature doesn't work.
I've set some configs in my ~/.ssh/config file as well
```
Host *
  ServerAliveInterval 60
  AddKeysToAgent yes
  IdentityFile ~/.ssh/id_rsa
Host gitlab.com
  HostName gitlab.com
  User git
Host github.com
  HostName github.com
  User git
```

But it still get this error when using a feature that calls a remote git action:
```
> git pull --tags origin master
ssh_askpass: exec(/usr/bin/ssh-askpass): No such file or directory
Permission denied (publickey).
fatal: Could not read from remote repository.

Please make sure you have the correct access rights
and the repository exists
```

I already tried installing ssh-askpass with `sudo apt-get install ssh-askpass-gnome ssh-askpass` but he asks me every single time for a password, so the ssh-agent is ignored
Repository: flutter
Issue: Ink reaction of IconButtons in AppBar is too big
Labels: framework,f: material design,a: fidelity,has reproducible steps,P2,found in release: 3.3,found in release: 3.7,team-design,triaged-design

Compared to native Android apps and the material spec, `IconButton`s in `AppBar`s should have a smaller ink reaction when pressed.

<img src="https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F0B9msDEx00QXmRVVQQlZBRnRGd2M%2Fpressed-04.png">
(Tile 1)

Not sure if that applies to all `IconButton`s. I also found this image

<img src="https://storage.googleapis.com/spec-host-backup/mio-design%2Fassets%2F0B9msDEx00QXmc0xTUGhCU2tQWE0%2Fpressed-03.png">
(Tile 1)

Source: https://material.io/design/interaction/states.html#pressed

For reference, also see:

https://material-components.github.io/material-components-web-catalog/#/component/icon-button
https://material-components.github.io/material-components-web-catalog/#/component/top-app-bar
Repository: flutter
Issue: `flutter attach --machine` should report `Waiting for a connection` in JSON for editors to report progress
Labels: c: new feature,tool,P3,team-tool,triaged-tool

Currently this status is just written to stdout so the editor can't display a nicer representation (eg. a progress notification):

```
[12:32:30 GMT+0100 (BST)] [FlutterRun] [Info] <== [{"event":"daemon.connected","params":{"version":"0.4.1","pid":13567}}]
[12:32:30 GMT+0100 (BST)] [FlutterRun] [Info] <== Waiting for a connection from Flutter on Android SDK built for x86...
```
Repository: pytorch
Issue: Multiprocess Deadlock when using np.transpose and torch.stack 
Labels: module: multiprocessing,triaged

Environment: 
Ubuntu 16.04.4 LTS
Python 3.5.2
pytorch 0.4.0
numpy 1.14.5
Or just use horovod image `uber/horovod:0.13.10-tf1.9.0-torch0.4.0-py3.5`

I run np.transpose and torch.stack first in parent process,  then run np.transpose and torch.stack in the subprocess, then subprocess hangs at torch.stack.
When I comment any np.transpose or torch.stack in parent process or subprocess, it run normally.
The minimal code to reproduce is 
```
import torch.multiprocessing as t_mp
import time
import numpy as np
import torch


if __name__ == '__main__':
    # hangs at stack tensor in subprocess，each of Method1-4 can run normally
    # Python3.5 torch0.4.0
    start = time.time()
    print("Some ops in main process")
    batch = np.random.rand(300, 300, 300)
    # Method1: Common following one line
    batch = batch.transpose((2, 0, 1))
    batch = [torch.from_numpy(b) for b in batch]
    # Method2: Common following one line
    batch = torch.stack(batch, 0)
    print("batch type ", type(batch))

    print("Multiprocessing with 1 workers")
    def _read_worker():
        batch = np.random.rand(300, 300, 300)
        print("transpose")
        # Method3: Common following one line
        batch = batch.transpose((2, 0, 1))
        print("numpy to tensor")
        batch = [torch.from_numpy(b) for b in batch]
        print("torch stack tensor")
        # Method4: Common following one line
        batch = torch.stack(batch, 0)
        print("batch type in worker", type(batch))

    w = t_mp.Process(
        target=_read_worker,
    )
    w.daemon = True  # ensure that the worker exits on process exit
    w.start()
    w.join()
    print("done")
```

It really confused me. I didn't even know how to debug it. Can anyone shed a light?
Repository: react
Issue: Relax ToString consistency guarantees
Labels: Type: Enhancement,Component: DOM,React Core Team

We recently chatted about https://github.com/facebook/react/pull/13367 and related work (e.g. https://github.com/facebook/react/pull/13394) with @sebmarkbage, and he raised a good point.

It seems like overall treating them consistently is adding significant overhead in the implementation readability. And there’s undoubtedly runtime overhead to it too. There are two separate issues here:

* **warning** for invalid values
* ensuring that the output for invalid values is **consistent** (e.g. functions are always skipped)

The conclusion we came to is that we should keep **warning** for bad values, but **as long as we warn, consistency is not necessary**. It's fine if we sometimes stringify a function, and sometimes skip it, as long as we always warn for those cases

**Our guiding principle for invalid inputs should be that we handle them with the least amount of overhead** (both at runtime, and in terms of code size), not that they’re always handled the same way.

One exception to this is probably Symbols because they throw when stringified. So it seems like skipping them is actually desirable — unless we're okay with errors.
Repository: go
Issue: runtime: use parent goroutine's stack for new goroutines
Labels: Performance,NeedsInvestigation,compiler/runtime

This is a speculative idea from discussion with @aclements. Jotting it down so it doesn't get lost and to open discussion.

Spinning off many goroutines that grow their stack and then exit can be a source of performance pain. See e.g. #18138. One approach to fixing this is [tracking and using statistics about stack growth behavior per spawn site](https://github.com/golang/go/issues/18138#issuecomment-264228318).

Another possible approach is to:

* switch immediately in the scheduler from parent goroutine to spawned goroutine
* use the (free part of) the parent's stack as the spawn's stack
* relocate the spawn's stack as needed

The idea here is that the parent goroutine's stack is likely to have plenty of free space, so if the spawn is short-lived, we can avoid doing any stack allocation for it at all, much less multiple stack growths.

If the spawn lives long enough that the parent goroutine starts running again, then this is worse. So it might be worth tracking some basic statistics on the fly to decide whether to do this.
Repository: rust
Issue: Rustc does not warn about `use` with paths incompatible with `uniform_paths` for edition 2018
Labels: A-lints,T-compiler,C-future-incompatibility,C-bug,A-edition-2018

## Updated Description:

[This code generates no warnings when compiled with the 2015 edition](https://play.rust-lang.org/?version=beta&mode=debug&edition=2015):

```rust
#![deny(rust_2018_compatibility)]
#![allow(unused_imports)]

extern crate rayon;

mod foo {
    mod rayon {}
    
    use rayon::Scope;
}
```

but [when compiled with the 2018 edition fails to compile](https://play.rust-lang.org/?version=beta&mode=debug&edition=2018&gist=37c27a00bd5b5e5d06e1218be5860d7e): 

```
error[E0432]: unresolved import `rayon::Scope`
 --> src/lib.rs:9:9
  |
9 |     use rayon::Scope;
  |         ^^^^^^^^^^^^ no `Scope` in `foo::rayon`

error[E0659]: `rayon` is ambiguous (name vs any other name during import resolution)
 --> src/lib.rs:9:9
  |
9 |     use rayon::Scope;
  |         ^^^^^ ambiguous name
  |
note: `rayon` could refer to the module defined here
 --> src/lib.rs:7:5
  |
7 |     mod rayon {}
  |     ^^^^^^^^^^^^
  = help: use `self::rayon` to refer to this module unambiguously
note: `rayon` could also refer to the extern crate imported here
 --> src/lib.rs:4:1
  |
4 | extern crate rayon;
  | ^^^^^^^^^^^^^^^^^^^
  = help: use `::rayon` to refer to this extern crate unambiguously

error: aborting due to 2 previous errors

Some errors occurred: E0432, E0659.
For more information about an error, try `rustc --explain E0432`.
```

## Old Description

Rustc does not warn about `use` with paths incompatible with `uniform_paths` for edition 2018.  This means that rustfix it will not fix your code for edition 2018.

To reproduce create the following project:

`Cargo.toml`: 
```toml
[package]
name = "foobar"
version = "0.0.0"
authors = ["Foo <example@example.com>"]

[dependencies]
criterion = "0.2"
```

`src/lib.rs`:
```rust
#![allow(unused)]
#![feature(rust_2018_preview, uniform_paths)]
extern crate criterion;
use criterion::Criterion;
```

If you run `cargo +nightly check` you will not get any warning, which means that when you run `cargo +nightly fix --edition` nothing will change, but the code is not compilable in rust 2018.  Change `Cargo.toml` to enable edition 2018 (by adding `cargo-features = ["edition"]` and `package.edition = "2018"`) and run `cargo +nightly build`:

```text
$ cargo +nightly build
[...]
error: `criterion` import is ambiguous
 --> src/lib.rs:4:5
  |
3 | extern crate criterion;
  | ----------------------- can refer to `self::criterion`
4 | use criterion::Criterion;
  |     ^^^^^^^^^ can refer to external crate `::criterion`
  |
  = help: write `::criterion` or `self::criterion` explicitly instead
  = note: relative `use` paths enabled by `#![feature(uniform_paths)]`
[...]
```

`cargo +nightly fix --edition` should have changed line 4 to `use ::criterion::Criterion`.

Ref: Bug in cargo: rust-lang/cargo#5905
Repository: go
Issue: cmd/go: allow verifying vendored code
Labels: NeedsInvestigation,FeatureRequest,modules

`go mod verify` is extremely useful for validating the integrity of modules in the local cache.

It would be great if projects that choose to vendor their modules (then presumably building with `go build -mod vendor ...`) had a similar command to verify the integrity of modules in that directory.

This would satisfy a major requirement that many projects need to account for in their CI process-- ensuring that vendored code hasn't been tampered with.
Repository: deno
Issue: Don't assume paths are always valid UTF8
Labels: suggestion,chore

This is a longer term goal. 

* Don't use String/str for paths on the rust side (we should start doing this today).
* Use flatbuffer byte vectors instead of strings to encode paths in messages.
* On the javascript side have an *optional, low-level API* that reports paths are typed arrays and not strings.

This was an issue in Node: https://github.com/nodejs/node-v0.x-archive/issues/2387
Repository: TypeScript
Issue: In JS, assignment to property of class has no contextual type
Labels: Bug,Domain: JSDoc,checkJs,Domain: JavaScript

**TypeScript Version:** 3.1.0-dev.20180829

**Code**

```ts
class C {
    /**
     * @param {number} n
     * @return {number}
     */
    m = n => n * 2;
}

const c = new C();
c.m = n => n * 3;
```

**Expected behavior:**

No error.

**Actual behavior:**

`src/a.js:10:7 - error TS7006: Parameter 'n' implicitly has an 'any' type.`

There is no error for the equivalent TypeScript code (using `m = (n: number): number => n * 2;`).

**Related Issues:**

#25926
Repository: flutter
Issue: Discussion: Separate Scaffold and DrawerLayout
Labels: framework,f: material design,c: proposal,P2,team-design,triaged-design

Is there any reason why the `Scaffold` is responsible for the page itself (app bars, floating action button...) and the drawers? It seems like there is no unidirectional connection between the drawer rendering and the page itself.

It would be handy if there was a `DrawerLayout` widget that is only responsible for rendering drawers.

Developers could place the `DrawerLayout` above the `Navigator` so that it does not disappear when the route changes.
Repository: kubernetes
Issue: Scarce Resource Bin Packing Priority Function 
Labels: sig/scheduling,kind/feature,lifecycle/frozen

/kind feature
/sig scheduling

**What happened**:
Consider a 3 node cluster with following resources availability
  
*Node 1*  extended-resource = intel.com/foo : 4
*Node 2*  extended-resource = intel.com/foo : 4
*Node 3*  extended-resource = intel.com/foo : 2

Run Job spec with following requests for extended resources 

*Job 1*  extended-resource-requests = intel.com/foo : 2
*Job 2*  extended-resource-requests = intel.com/foo : 4
*Job 2*  extended-resource-requests = intel.com/foo : 4

Default scheduler 

Job 1 ---> Node 1
Job 2 ---> Node 2
Job 3 ---> Pending state (Not scheduled due to resource fragmentation)

**What you expected to happen**:

Job 1 ---> Node 3
Job 2 ---> Node 1 or 2
Job 3 ---> Node 1 or 2

**How to reproduce it (as minimally and precisely as possible)**:

Patch Nodes as follows 

For Node 1 and 2

```sh
curl --header "Content-Type: application/json-patch+json" \
--request PATCH \
--data '[{"op": "add", "path": "/status/capacity/intel.com~1foo”, "value": "4"}]' \
http://localhost:8001/api/v1/nodes/<node-name>/status
```

For Node 3

```sh
curl --header "Content-Type: application/json-patch+json" \
--request PATCH \
--data '[{"op": "add", "path": "/status/capacity/intel.com~1foo”, "value": "2"}]' \
http://localhost:8001/api/v1/nodes/<node -name>/status
```

Run Following Pod Spec

```yaml
apiVersion: v1
kind: Pod
metadata:
  name: test-pod-1
spec:
  containers:
  - name: nginx
    image: nginx
    resources:
      limits:
        intel.com/foo: 2
---
apiVersion: v1
kind: Pod
metadata:
  name: test-pod-2
spec:
  containers:
  - name: nginx
    image: nginx
    resources:
      limits:
        intel.com/foo: 4
---
apiVersion: v1
kind: Pod
metadata:
  name: test-pod-3
spec:
  containers:
  - name: nginx
    image: nginx
    resources:
      limits:
        intel.com/foo: 4
```