sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: go
Issue: encoding/asn1: Unmarshalling implicitly tagged GeneralizedTime unmarshalls as UTCTime
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.2 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/chris/.cache/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/chris/Git/gorims"
GOPROXY=""
GORACE=""
GOROOT="/usr/lib/go"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build216350556=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?
Add an implicitly tagged field to a struct of type time.Time and tagged it with "generalized".  Marshalled the struct and then unmarshalled it.  Unmarshalling failed because it parses the time as a UTCTime.

https://play.golang.org/p/XOKSctdaYl5


### What did you expect to see?
Unmarshalling observe the "generalized" attribute tag and parse the time as a Generalized Time


### What did you see instead?
Unmarshalling parsed the time as a UTCTime which failed and produced the zero val for the time.

Looking at the current test suite, it appears that the implementation of the "generalized" attribute tag is incomplete:
```
func TestImplicitTaggedTime(t *testing.T) {
	// An implicitly tagged time value, that happens to have an implicit
	// tag equal to a GENERALIZEDTIME, should still be parsed as a UTCTime.
	// (There's no "timeType" in fieldParameters to determine what type of
	// time should be expected when implicitly tagged.)
	der := []byte{0x30, 0x0f, 0x80 | 24, 0xd, '9', '1', '0', '5', '0', '6', '1', '6', '4', '5', '4', '0', 'Z'}
	var result implicitTaggedTimeTest
	if _, err := Unmarshal(der, &result); err != nil {
		t.Fatalf("Error while parsing: %s", err)
	}
	if expected := time.Date(1991, 05, 06, 16, 45, 40, 0, time.UTC); !result.Time.Equal(expected) {
		t.Errorf("Wrong result. Got %v, want %v", result.Time, expected)
	}
}
```
But there IS a timeType set by the use of the "generalized" tag.
Repository: go
Issue: net/v2: meta bug for v2 changes
Labels: v2

This is a meta/index bug for things we might change in a possible future `net/v2` (~ *"Go 2"*) package, including both links to other issues, or just comments with API problems/cleanups that are too little to warrant their own bugs.

(This is **not** about `net/http`, `net/mail`, `net/rpc`, `net/smtp`, `net/nextproto`, or `net/url`. Those should have their own bugs if/when needed.)
Repository: vscode
Issue: [snippets] Support for global or project-level variables
Labels: feature-request,snippets

I originally posted in #59557, but I realized the OP was asking for a variable *defined within the snippet*.

## This request is for adding support for user-overridable variables defined *outside* of the snippet code, perhaps in:

1. A global/project-level config file
2. Environment variables

NOTE: # 2 [has a precedent in TextMate](https://macromates.com/manual/en/environment_variables).

# JavaScript Use Cases

## Use Case 1: `let` vs `const`

ES2015 introduced `let` and `const`. This comes down to a personal preference for many users.

This could be accommodated by allowing the user to set a variable like `${VARIABLE_DECL_KIND}` to either `const` or `let`.

## Use Case 2: `;`

Ending statements with `;` is also a stylistic preference for most JavaScript code.

This could be accommodated using a `${STATEMENT_TERMINATOR}` that could be defined as either `;` or an empty string.

I know many similar requests are being closed in favor of #10561, but I'm wondering if short of that, this could be implemented by adding another `VariableResolver` implemention, e.g.: `EnvironmentVariableResolver` or `ConfigFileVariableResolver`?
Repository: flutter
Issue: RouteAware.didPushNext documentation is incorrect
Labels: framework,customer: mulligan (g3),d: api docs,f: routes,P2,team-framework,triaged-framework

Internal: b/292548580

"Called when a new route has been pushed, and the current route is no longer visible."

It's called before the route transition is finished; therefore, the current route is still visible, just obscured. This is an important distinction in some scenarios like one I ran into today where I wanted to do something as soon as the route containing the current widget was no longer visible whatsoever.
Repository: opencv
Issue: dnn: PROTOBUF_USE_DLLS
Labels: priority: low,category: build/install,category: dnn

I'm on Win7 x64, Visual Studio 2015, trying to build opencv v4.0.0.

Since I haven't managed to build opencv's dnn module with whatever protobuf comes with it, I've built libprotobuf (and protoc) standalone. it seems cmake automatically configures that build for shared libraries (dlls).

now, when I try to configure opencv with cmake, it detects all the paths, but when building, I get about half a dozen linker errors ("unresolved external symbol", LNK2001) right when opencv_dnn400 is linked.

I can only resolve them by doing what [they did](https://github.com/Microsoft/vcpkg/issues/1353): add `PROTOBUF_USE_DLLS`. strangely, simply defining this as a cmake variable within cmake-gui didn't work (for me). I actually have to edit the corresponding CMakeLists.txt.

Maybe this could gain some auto-detection or be resolved some other way? at the very least, I hope to leave this breadcrumb for others who run into this problem.
Repository: vue-element-admin
Issue: 面包屑导航实现子路由之间的跳转无需新打开tagViews
Labels: enhancement :star:,feature

 // 活动管理
  {
    path: '/activity',
    redirect: '/activity/index',
    component: Layout,
    children: [{
      path: 'index',
      component: () => import('@/views/activity/index'),
      name: 'activityIndex',
      meta: {
        title: '活动管理',
        icon: 'dashboard',
        noCache: true
      }
    }]
  },
  {
    path: '/activity',
    component: Layout,
    redirect: '/activity/index',
    name: 'activity',
    hidden: true,
    meta: {
      title: '活动管理',
      icon: 'dashboard',
      noCache: true
    },
    children: [{
        path: 'add',
        component: () => import('@/views/activity/components/add'),
        name: 'activityAdd',
        meta: {
          title: '活动添加',
          noCache: true
        }
      },
      {
        path: 'edit/:id(\\d+)',
        component: () => import('@/views/activity/components/edit'),
        name: 'activityEdit',
        meta: {
          title: '活动修改',
          noCache: true
        },
        hidden: true
      },
      //详情页面
      {
        path: 'detail/:id(\\d+)',
        hidden: true,
        component: () => import('@/views/activity/components/detail'),
        name: 'activityDetail',
        meta: {
          title: '活动详情',
          icon: 'star',
          noCache: true
        }
      }
    ]
  }
侧边导航只会显示一个，右侧不同子路由的切换，不会新增新的tagViews,实现了 “首页/父路由/子路由1”到“首页/父路由/子路由2”的切换，切换的同时关闭子路由1，有没有可能实现模拟浏览器的后退按钮，后退就直接返回上次的路由
Repository: pytorch
Issue: [Caffe2] How can I use detectron with pytorch?
Labels: caffe2

Hi guys :sweat_smile:  :sweat_smile:  I have a question but I don't know if this is the right place to ask or not.   

I am using pytorch and I wanted to use detectron and they are saying that I have to install caffe2 first and I did so but when type `from caffe2.python import core`, I see this   

`WARNING:root:This caffe2 python run does not have GPU support. Will run in CPU only mode.
CRITICAL:root:Cannot load caffe2.python. Error: /lib64/libc.so.6: version 'GLIBC_2.14' not found (required by /home/qwe123/data/conda_packages/lib/python3.6/site-packages/caffe2/python/caffe2_pybind11_state.cpython-36m-x86_64-linux-gnu.so)`    

I tried other solutions I found on here but I could not get this to work. I only installed caffe2 because I wanted to use detectron, Can I use it with pytorch without the need of caffe2? My version of pytorch of 4.0, Should I download pytorch version 1.0 to use detectron with it?
Repository: flutter
Issue: Implement empty table rendering
Labels: c: new feature,framework,a: fidelity,f: cupertino,P2,team-design,triaged-design

Implement empty table rendering. Includes dividers that fill viewport.
Repository: rust
Issue: Type mismatch reporting is slow when `gtk` crate is present
Labels: A-type-system,C-enhancement,A-diagnostics,I-compiletime,T-compiler,T-types

This code takes a long time (3-4 seconds) in item-bodies checking before reporting the type mismatch:

```rust
extern crate gtk;

fn bar(param: ()) {}

fn main() {
    bar(true);
}
```

It compiles (or fails to compile) nearly instantly when the `extern crate` is removed or the `true` is replaced with the proper type `()`.

One of the reasons this could be slow is because `gtk` contains a *lot* of traits (at least 189, in fact).

I understand that optimizing error paths isn't that important, but 3-4 seconds on this tiny piece of code did seem a bit excessive, so I thought I'd open an issue anyway.

Tested on the current nightly (`rustc 1.32.0-nightly (f1e2fa8f0 2018-11-20)`) and stable 1.30.1
Repository: pytorch
Issue: Provide Protobuf library if libtorch was built with included version
Labels: module: build,module: protobuf,module: cpp,triaged

When building pytorch and libtorch with ``python setup.py build``, an internal version of protobuf is used. Our C++ app also uses Protobuf but finds an incompatible version with the one used by libtorch. Would it be possible to add to the install a ProtobufConfig.cmake so that we can link against the same protobuf?

cc @yf225
Repository: TypeScript
Issue: Inconsistency of mapped type and `Parameters<T>` between TS and JS
Labels: Bug

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.1.4

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** mapped type parameters js

**Code**

```ts
// TypeScript
const Foo = Object.freeze({
  a: (arg1: string) => arg1,
  b: (arg1: string, arg2: boolean) => arg2,
});
// typeof Foo = Readonly<{
//    a: (arg1: string) => string;
//    b: (arg1: string, arg2: boolean) => boolean;
//}>

type Bar = {[K in keyof typeof Foo]: (...args: Parameters<(typeof Foo)[K]>) => void}
// typeof Bar = { 
//     readonly a: (arg1: string) => void; 
//     readonly b: (arg1: string, arg2: boolean) => void;
// }
```

```js
// JavaScript
const Foo = Object.freeze({
	a: (/** @type {string} */arg1) => arg1,
	b: (/** @type {string} */arg1, /** @type {boolean} */arg2) => arg2,
});
// typeof Foo = Readonly<{
//    a: (arg1: string) => string;
//    b: (arg1: string, arg2: boolean) => boolean;
//}>
// ^ is identical to TS

/** @typedef {{[K in keyof typeof Foo]: (...args: Parameters<(typeof Foo)[K]>) => void}} Bar */
// typeof Bar = {
//     readonly a: (arg1?: string) => void;
//     readonly b: (arg1?: string, arg2?: boolean) => void;
// }
// ^ why optional??
```
**Expected behavior:**
`Bar.{a,b}` having the same signatures in TS and JS

**Actual behavior:**
`Bar.{a,b}` have only optional parameters in JS.
Repository: flutter
Issue: Transform.rotate is super slow
Labels: engine,c: performance,has reproducible steps,P2,team-engine,triaged-engine,found in release: 3.19,found in release: 3.22

I'm implementing a card swiping tinder like ui. Cards are being moved during onPanUpdate (within GestureDetector). 
When applying just regular Transform.translate it is super smooth, but with when I apply also Transform.rotate it is missing a lot of frames (even on iPhone X).

This is the sample code:
```dart
class MemberCard extends StatelessWidget {
  final double width;
  final double height;
  final String photo;
  final double rotation;
  final Offset offset;
  final double scale;
  final bool dropShadow;

  MemberCard({
    this.width,
    this.height,
    this.photo,
    this.rotation = 0.0,
    this.offset = const Offset(0.0, 0.0),
    this.scale = 1.0,
    this.dropShadow = false,
  });

  @override
  Widget build(BuildContext context) {
    double angle = rotation * (math.pi / 180.0);
    var matrix = Matrix4.translationValues(offset.dx, offset.dy, 0.0);
    if (scale != 1.0) {
      matrix..scale(scale);
    }
    if (rotation != 0.0) {
      matrix.rotateZ(angle);
    }

    return Transform(
      alignment: Alignment.center,
      transform: matrix,
      child: Stack(
        children: <Widget>[
          RepaintBoundary(
            child: Container(
              width: width,
              height: height,
              decoration: BoxDecoration(
                boxShadow: dropShadow
                    ? [
                        BoxShadow(
                            color: Colors.black.withOpacity(0.4),
                            blurRadius: 5.0,
                            offset: Offset(0.0, 1.0))
                      ]
                    : [],
                borderRadius: BorderRadius.all(Radius.circular(10.0)),
                color: Colors.white,
                // image: DecorationImage(
                //   image: NetworkImage(photo),
                //   fit: BoxFit.cover,
                // ),
              ),
              child: ClipRRect(
                borderRadius: BorderRadius.circular(10.0),
                child: Image.network(
                  photo,
                  fit: BoxFit.cover,
                  filterQuality: FilterQuality.none,
                ),
              ),
            ),
          ),
        ],
      ),
    );
  }
}

```
Repository: go
Issue: encoding/pem: fix #bytes lineBreaker.Write returns
Labels: NeedsDecision

<!-- 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.2 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?
yes


### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/santhosh/Library/Caches/go-build"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/santhosh/go"
GOPROXY=""
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/xy/4qx1s2zn5qn82yzpx8xhbplr0000gn/T/go-build703305017=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

<!--
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
-->
```go
const sixtyFourCharString = "0123456789012345678901234567890123456789012345678901234567890123"
var breaker lineBreaker
breaker.out = new(bytes.Buffer)
n, err := breaker.Write([]byte(test.in))
fmt.Println(n,err)
```

### What did you expect to see?
should print `64 nil`


### What did you see instead?

this prints `0 nil`

as this api is not exported, it will not be visible to end user. but still the io.Writer contract is broken
Repository: pytorch
Issue: [Caffe2] Cannot get repeated argument in custom operator in CUDA context
Labels: caffe2

## 🐛 Bug

I am trying to build own custom operator for caffe2. My operator has some arguments. Some of them are repeated (vectors of numbers). In operator constructor I get the arguments, however, when I run my operator in CPU context I am able to get all arguments, when I run in CUDA context all repeated arguments are empty. 

## To Reproduce

Operator constructor
```
template <typename T,class Context>
class YoloOp final:public Operator<Context> {
public:
    USE_OPERATOR_CONTEXT_FUNCTIONS;
    YoloOp(const OperatorDef& operator_def, Workspace* ws)
        : Operator<Context>(operator_def, ws),
          anchor_mask_(this->template GetRepeatedArgument<int>("anchor_mask")),
          anchors_(OperatorBase::GetRepeatedArgument<int>("anchors")),
          numclass_(OperatorBase::GetSingleArgument<int>("numclass",80)),
...
std::cout << "YOLO num_classes: " << this->numclass_ << std::endl;
std::cout << "Anchors: " << this->anchors_ << std::endl;
```

Example of running operation:
```
    caffe2::DeviceOption deviceOptionCPU;
    deviceOptionCPU.set_device_type(PROTO_CPU);
    caffe2::OperatorDef op = caffe2::CreateOperatorDef("Yolo","MyYolo",vector<string>{"inputYOLO_"+idx_str},
                                                       vector<string>{"out_"+idx_str,"tx_"+idx_str,"ty_"+idx_str,"tw_"+idx_str,"th_"+idx_str,"det_conf_"+idx_str,"class_prob_"+idx_str,"tmp"+idx_str},
                                                       deviceOptionCPU);

    caffe2::AddArgument("numclass",60, &op);

    std::vector<int> anchors({ 10,13,  16,30,  33,23,  30,61,  62,45,  59,119,  116,90,  156,198,  373,326});
    caffe2::AddArgument("anchors",anchors, &op);
```


## Expected behavior

When I run my operator in CPU context I get the following output:
```
YOLO num_classes: 60
Anchors: 10 13 16 30 33 23 30 61 62 45 59 119 116 90 156 198 373 326
```
When I run my operator in GPU context it just output empty anchors:
```
YOLO num_classes: 60
Anchors: 
```

## Environment

```
Collecting environment information...
PyTorch version: 1.0.0a0+ff608a9
Is debug build: No
CUDA used to build PyTorch: 9.0.176

OS: Ubuntu 16.04.5 LTS
GCC version: (Ubuntu 5.4.0-6ubuntu1~16.04.10) 5.4.0 20160609
CMake version: version 3.12.2

Python version: 3.6
Is CUDA available: Yes
CUDA runtime version: 9.0.176
GPU models and configuration: GPU 0: GeForce GTX 1050 Ti
Nvidia driver version: 384.130
cuDNN version: Probably one of the following:
/usr/lib/x86_64-linux-gnu/libcudnn.so.6.0.21
/usr/lib/x86_64-linux-gnu/libcudnn.so.7.2.1
/usr/lib/x86_64-linux-gnu/libcudnn_static_v7.a

Versions of relevant libraries:
[pip] Could not collect
[conda] torch                     1.0.0a0+ff608a9           <pip>
```

## Additional context

<!-- Add any other context about the problem here. -->
Repository: rust
Issue:  no_std panic=abort dev builds require `rust_eh_personality`
Labels: A-linkage,T-compiler

```
$ cat Cargo.toml 
[package]
name = "foo"
version = "0.1.0"
authors = ["Mike Hommey <mh@glandium.org>"]

[lib]
crate-type = ["cdylib"]

[profile.dev]
panic = "abort"

[profile.release]
panic = "abort"
```

```
$ cat src/lib.rs
#![no_std]

use core::alloc::Layout;
use core::ffi::c_void;
use core::ptr;

const CHUNK_SIZE: usize = 1 << 20;

#[panic_handler]
#[no_mangle]
pub fn panic_impl(_: &core::panic::PanicInfo) -> ! {
    loop {}
}

#[derive(Clone, Copy, Debug)]
pub(crate) struct ChunkLayout(Layout);

#[derive(Debug)]
pub(crate) struct ChunkLayoutErr;

impl ChunkLayout {
    fn from_size_align(size: usize, align: usize) -> Result<Self, ChunkLayoutErr> {
        if align < CHUNK_SIZE || (size & (CHUNK_SIZE - 1) != 0) {
            return Err(ChunkLayoutErr);
        }
        Layout::from_size_align(size, align).map(ChunkLayout).map_err(|_| ChunkLayoutErr)
    }
}

#[no_mangle]
pub unsafe extern "C" fn chunk_alloc_mmap(size: usize, align: usize) -> *mut c_void {
    if let Ok(_layout) = ChunkLayout::from_size_align(size, align) {
        ptr::null_mut()
    } else {
        ptr::null_mut()
    }
}
```

```
$ cargo build
   Compiling foo v0.1.0 (/tmp/foo)
    Finished dev [unoptimized + debuginfo] target(s) in 0.24s
$ objdump -T target/debug/libfoo.so | grep rust_eh_personality
0000000000000000      D  *UND*	0000000000000000 rust_eh_personality
```

Practically speaking, this means the resulting library (cdylib) can't be loaded because the symbol can't be resolved.

This doesn't happen with `--release` (there is no undefined reference to `rust_eh_personality`). And this doesn't happen when the body of `chunk_alloc_mmap` is further reduced to only `ptr::null_mut()`.

If I add -Wl,-Map,map to the linker arguments, the output `map` file says the symbol reference comes from:
```
 .data.DW.ref.rust_eh_personality
                0x0000000000004008        0x8 /tmp/foo/target/debug/deps/foo.3sp59mzlmyqssn40.rcgu.o
                0x0000000000004008                DW.ref.rust_eh_personality
```

So rust actively creates a pointer to `rust_eh_personality` in `.data`. DW suggests this would have something to do with DWARF, so I tried enabling debug info on the release profile, but that still didn't make it happen with `--release`.

Cc: @japaric, @alexcrichton
Repository: opencv
Issue: Python bindings build fails when source directory named "opencv2"
Labels: bug,category: python bindings,category: build/install



##### System information (version)
- OpenCV => master
- Operating System / Platform => Ubuntu 18
- Compiler => default

##### Detailed description

When source directory is named `opecnv2` python bindings can not be built:
```
FAILED: <compiling> /work/opencv2/modules/python/src2/cv2.cpp
In file included from /work/opencv2/modules/python/src2/cv2.cpp:109:0:
modules/python_bindings_generator/pyopencv_generated_include.h:14:10: fatal error: opencv2/modules/core/misc/python/shadow_umat.hpp: No such file or directory
 #include "opencv2/modules/core/misc/python/shadow_umat.hpp"
          ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
compilation terminated.
```
Directory names `opencv` and `opencv3` works well.

##### Steps to reproduce

```
git clone https://github.com/opencv/opencv opencv2
git -C opencv2 checkout master
mkdir build && pushd build
cmake -GNinja ../opencv2
ninja
```
Repository: pytorch
Issue: No code example for AdaptiveLogSoftmaxWithLoss
Labels: module: docs,triaged

## 📚 Documentation
There are no code examples for `torch.nn.AdaptiveLogSoftmaxWithLoss`, and so it is not trivial how to go about using it as a layer, and how to use the methods `predict` and `log_prob`.
<!-- 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 -->