sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: pytorch
Issue: 【Train issue with caffe2 detectron】Aborted at 1523501813 (unix time) try "date -d @1523501813" if you are using GNU date *** PC: @     0x7fa35103733a (unknown)
Labels: caffe2

I try to run resnet50_trainer.py to build my model by using 100 images, but I get the following error messages. My train method is drawn on the following web, https://github.com/royhuang9/Detectron. How to fix the error and run correctly using Caffe2? I am not sure if this is a Caffe2 issue. 

Train command:
python2 tools/train_net.py --cfg experiments/e2e_faster_rcnn_resnet-50-FPN_pascal2007.yaml  OUTPUT_DIR experiments/output  

Error meassage:
json_stats: {"accuracy_cls": 1.000000, "eta": "1:59:55", "iter": 26200, "loss": 0.000865, "loss_bbox": 0.000183, "loss_cls": 0.000680, "loss_rpn_bbox_fpn2": 0.000000, "loss_rpn_bbox_fpn3": 0.000000, "loss_rpn_bbox_fpn4": 0.000003, "loss_rpn_bbox_fpn5": 0.000003, "loss_rpn_bbox_fpn6": 0.000000, "loss_rpn_cls_fpn2": 0.000000, "loss_rpn_cls_fpn3": 0.000005, "loss_rpn_cls_fpn4": 0.000004, "loss_rpn_cls_fpn5": 0.000002, "loss_rpn_cls_fpn6": 0.000000, "lr": 0.002500, "mb_qsize": 64, "mem": 2451, "time": 0.212877}
*** Aborted at 1523501813 (unix time) try "date -d @1523501813" if you are using GNU date ***
PC: @     0x7fa35103733a (unknown)
*** SIGSEGV (@0x0) received by PID 6778 (TID 0x7fa2edffb700) from PID 0; stack trace: ***
    @     0x7fa351390390 (unknown)
    @     0x7fa35103733a (unknown)
    @     0x7fa351039184 __libc_malloc
    @     0x7fa348101c51 (unknown)
    @     0x7fa348164232 (unknown)
    @     0x7fa3481642ea (unknown)
    @     0x7fa3481f29d4 (unknown)
    @     0x7fa3481f2da0 (unknown)
    @           0x4c195b PyEval_EvalFrameEx
    @           0x4c136f PyEval_EvalFrameEx
    @           0x4b9ab6 PyEval_EvalCodeEx
    @           0x4d54b9 (unknown)
    @           0x4eebee (unknown)
    @           0x4a577e PyObject_Call
    @           0x4c5e10 PyEval_CallObjectWithKeywords
    @     0x7fa33adca3d0 pybind11::detail::object_api<>::operator()<>()
    @     0x7fa33adcbb51 caffe2::python::PythonOpBase<>::RunOnDevice()
    @     0x7fa33ad932cb caffe2::Operator<>::Run()
    @     0x7fa33addce3a _ZN6caffe213GPUFallbackOpINS_6python8PythonOpINS_10CPUContextELb0EEENS_11SkipIndicesIJEEEE11RunOnDeviceEv
    @     0x7fa33add95d5 caffe2::Operator<>::Run()
    @     0x7fa336bcef0a caffe2::DAGNet::RunAt()
    @     0x7fa336bcdbbe caffe2::DAGNetBase::WorkerFunction()
    @     0x7fa34a5cbc80 (unknown)
    @     0x7fa3513866ba start_thread
    @     0x7fa3510bc41d clone
    @                0x0 (unknown)
Repository: rust
Issue: one_time_diagnostics and --teach doesn't work with incremental compilation
Labels: A-lints,T-compiler,A-incr-comp,C-bug

Both `one_time_diagnostics` and `--teach` suppresses diagnostic information if it was already emitted. However with incremental compilation if cause of the other diagnostic is removed without affecting the cause of other such diagnostics, the information will not be emitted at all.
Repository: TypeScript
Issue: JSDOC inconsistance casting behavior
Labels: Bug,Domain: JavaScript

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨 -->
<!--
Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker.

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the CONTRIBUTING guidelines: https://github.com/Microsoft/TypeScript/blob/master/CONTRIBUTING.md
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ
-->

<!-- If you have a QUESTION:
   THIS IS NOT A FORUM FOR QUESTIONS.
   Ask questions at http://stackoverflow.com/questions/tagged/typescript
    or https://gitter.im/Microsoft/TypeScript
-->

<!-- If you have a SUGGESTION:
  Most suggestion reports are duplicates, please search extra hard before logging a new suggestion.
  See https://github.com/Microsoft/TypeScript-wiki/blob/master/Writing-Good-Design-Proposals.md
-->

<!-- If you have a BUG:
  Please fill in the *entire* template below.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  2.8.1

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** 
jsdoc, casting

**Code**

utils.d.ts
```typescript
declare namespace utils {
   export type PartialTypeGuard<T, U extends T> = (value: T) => value is U;
   export type TypeGuard<T> = PartialTypeGuard<any, T>;
}
```

test.js
```javascript
// @ts-check
/// <reference path="./utils.d.ts" />

/**
 * @type {utils.TypeGuard<string>}
 */
let pass = ((a)=>typeof a === 'string');

/**
 * @type {utils.TypeGuard<string>}
 */
let fail = (a)=>typeof a === 'string';
```

**Expected behavior:**
They both throw error due to casting between item with incompatible signature without explicit casting

**Actual behavior:**
The first one pass for unknown reason , the second one failed as expect

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior --> 

**Related Issues:**
Repository: rust
Issue: unsized generic field not allowed in repr(packed) struct
Labels: A-type-system,C-enhancement,T-types,A-repr-packed

For some reason, using a generic `T: ?Sized` does not work in a `repr(packed)` struct, while a non-generic unsized type is OK.

```
#[repr(packed)]
struct Bar([u8]); // ok

#[repr(packed)]
struct Foo<T: ?Sized>(T): // err
```

An non-`packed` is also OK:
```struct Foo<T: ?Sized>(T); // ok```

The full error:
```
error[E0277]: the trait bound `T: std::marker::Sized` is not satisfied
  |
5 | struct Foo<T: ?Sized>(T); // err
  |                       ^^ `T` does not have a constant size known at compile-time
  |
  = help: the trait `std::marker::Sized` is not implemented for `T`
  = help: consider adding a `where T: std::marker::Sized` bound
  = note: only the last field of a struct may have a dynamically sized type
```

This may be related to #47068?

## Meta

```
$ rust --version --verbose
rustc 1.25.0 (84203cac6 2018-03-25)
binary: rustc
commit-hash: 84203cac67e65ca8640b8392348411098c856985
commit-date: 2018-03-25
host: x86_64-unknown-linux-gnu
release: 1.25.0
LLVM version: 6.0
```
Repository: javascript
Issue: separate event handler functions for an event attached to different inputs or one event handler function with lot of if statements/ switch statement?
Labels: question

separate event handler functions for an event attached to different inputs or one event handler function with lot of if statements/ switch statement?

```js
// event handler 1
function validateEmail() {
	// validate email here
}

// event handler 2
function validatePassword() {
	//validate password here
}

// or

// generic event handler
function validateFields() {
	/*
	if(is email){
		validate email
	}

	if(is password) {
		validate password
	}
	*/
}
```
Repository: pytorch
Issue: caffe2/cuda_rtc can throw during the destructor
Labels: caffe2

Note that this line throws in the destructor:
https://github.com/pytorch/pytorch/blob/master/caffe2/cuda_rtc/common_rtc.h#L27

We saw those cases happening in TC so we rewrote our logic to unload first before destroying.
You may wan to consider the same.
Repository: go
Issue: net/http: TestServerDuplicateBackgroundRead crashes netbsd-arm builder
Labels: Testing,OS-NetBSD,NeedsFix

One of the net/http tests, `TestServerDuplicateBackgroundRead`, has crashed the netbsd-arm-bsiegert builder machine several times. When this happens, the machine locks up, accepting no input on the console, and the CPU gets hot.

02328153520b10d6252064ef18d5eeb214f55824 marks this test as skipped.

This issue is tracked upstream in NetBSD as http://gnats.netbsd.org/53173.

//cc @zoulasc @bradfitz @tklauser
Repository: You-Dont-Know-JS
Issue: this & Object Prototypes - Chapter 3 : 'in' operator 
Labels: for second edition

There's a paragraph related to the **in** operator that goes like this : 

> There's (currently) no built-in way to get a list of all properties which is equivalent to what the in operator test would consult (traversing all properties on the entire [[Prototype]] chain, as explained in Chapter 5). You could approximate such a utility by recursively traversing the [[Prototype]] chain of an object, and for each level, capturing the list from **Object.keys(..)** -- only enumerable properties.

Why do we need to capture only the **enumerable** properties. The **in** operator also checks for **non-enumerable** properties as well. So instead of using Object.keys(), shouldn't we use Object.getOwnPropertyNames() to build the utility?
Repository: pytorch
Issue: [Caffe2] - Run on different Cuda streams
Labels: caffe2

Hi,

I loaded the model once on the GPU, and would like to run the network on different cuda streams, meaning having two videos running simultaneously using same model. I managed to implement this, but can't find where I need to change the cuda stream, for the Workspace to run on.

Maybe it will be more helpful for OpenCV I'm passing cv::cuda::Stream, is there a way that I can do the same with caffe2, while sharing the data or running the network? Also I'm using the C++ version not Python.

Thanks very much
Repository: go
Issue: x/build/cmd/gerritbot: auto-wrap description
Labels: help wanted,Builders,NeedsFix

Per https://go-review.googlesource.com/c/vgo/+/105335/9//COMMIT_MSG#9 it would be good/nice to have gerritbot auto-wrap the first comment to save people having to do this by hand (which in a webpage text box is painful)

cc @andybons
Repository: vscode
Issue: Select editor text via touch
Labels: feature-request,editor-core,touch/pointer

Issue Type: <b>Feature Request</b>

When using a touch screen, I want to be able to interact with VSCode in an intuitive manner.

When I touch and drag on text, I expect it to do something. I think the most intuitive option would be to select text.

When I touch and drag on empty space (space with no characters in the buffer), I expect the editor to scroll with my finger.

VS Code version: Code 1.22.1 (950b8b0d37a9b7061b6f0d291837ccc4015f5ecd, 2018-04-06T02:26:57.615Z)
OS version: Windows_NT x64 10.0.16299


<!-- generated by issue reporter -->
Repository: TypeScript
Issue: Review preserving internal trivia in code fixes
Labels: Bug,Domain: Quick Fixes

**TypeScript Version:**  master

**Code**

```ts
exports.x = () /*comment*/ => f;
```

Run code fix to convert to an ES6 module.

**Expected behavior:**

```ts
export function x() /*comment*/ { return f; }
```

**Actual behavior:**

```ts
export function x() { return f; }
```
Repository: flutter
Issue: Document the accuracy of native memory leak instrumentations
Labels: team,engine,dependency: dart,d: api docs,P2,team-engine,triaged-engine

![screen shot 2018-04-12 at 12 32 40 pm](https://user-images.githubusercontent.com/156888/38699715-a7e3255c-3e4d-11e8-836c-9ab13861132f.png)

There are some Dart memory management related stacks that show up as leaks in Xcode Instruments when playing around with the Gallery.

We should document whether users that see these are legitimate concerns or just red herrings that are artifacts of our garbage collection mechanism. 

cc @sethladd @cbracken @sivachandra
Repository: pytorch
Issue: [Feature Request] Optimization with constraint (L-BFGS-B)
Labels: proposal accepted,todo,triaged

Is there an agenda for implementing bounded optimization method like L-BFGS-B?
Scipy already has a functional method here scipy.optimize.fmin_l_bfgs_b.
Repository: rust
Issue: "File name too long" error when compiling files with long names
Labels: C-enhancement,T-bootstrap

```
could not write output to /home/russell/code/rust/rust/build/x86_64-unknown-linux-gnu/test/ui/nll/closure-requirements/region-lbr1-does-outlive-lbr2-because-implied-bound.region_lbr1_does_outlive_lbr2_because_implied_bound0-317d481089b8c8fe83113de504472633.rs.rcgu.o: File name too long
```

Can the test runner avoid trying to write file with names this long? I've moved my rust installation to a higher level directory to work around it.
Repository: flutter
Issue: Potential customers run Flutter in Instruments and perceive it as leaking
Labels: platform-ios,engine,P3,team-ios,triaged-ios

My understanding is this occurs for two reasons.

1. Running Flutter in --debug, and see something (presumably tracing/observatory) taking up increasing memory over time.  This occurred for customer:gold early in their initial eval.

2.  Running flutter and loading lots of images and hitting: https://github.com/flutter/flutter/issues/13606.  Customers see what looks like Flutter leaking memory every time an image is loaded.
Repository: vscode
Issue: Command - Undo Replace All
Labels: feature-request,search-replace,undo-redo

In Search Panel should be button "Undo Replace All", whitch undo all "replaced" changes in all files.
Should to be work like standard undo function, but only for files whitch "Replace All" made a changes.

It looks something simple to introduce. Am I right?
Repository: flutter
Issue: Add a per directory structure README.md to the engine repo
Labels: team,engine,d: api docs,P2,team-engine,triaged-engine

Add a directory map README.md at the root similar to https://fuchsia.googlesource.com/docs/+/master/development/source_code/layers.md or https://fuchsia.googlesource.com/docs/+/master/map.md describing what should go where or a README.md like https://github.com/chinmaygarde/flutter_engine/blob/02c1f084cbe6a4f4c7a99a9278e11c9b41d657ec/content_handler/README.md per directory describing the role of the directory.

cc @cbracken @chinmaygarde
Repository: go
Issue: x/build: finish, document Gerrit hashtags for managing open CLs
Labels: Documentation,Builders,NeedsFix

In chat with @andybons @FiloSottile @bcmills and @ianlancetaylor yesterday, I proposed we start using Gerrit's "hashtags" support, now that our hosted Gerrit supports it (notedb support is active for us) and PolyGerrit (the new web UI) supports it.

After discussion, we settled on using tags:

```
so, how about: "wait-author", "wait-release", "wait-issue", "wait-$PERSON"
where $PERSON is some substring of a name/email in the reviewer set.
and if somebody is named "Issue Release" and their email is issue@release.com, then you have to use their full email in $PERSON
we can mass remove the "wait-release" labels when tree opens
```

While triaging today, I found we should also add support for:

```
wait-cl-NNNNN -- this CL is blocked until NNN is resolved
```

I started looking into adding hashtag support to maintner and gopherbot.

Tracking that work here, then documenting all this on the wiki.
Repository: go
Issue: x/build/cmd/gerritbot: impersonate reviewer accounts
Labels: Builders,NeedsInvestigation

The experience of only receiving messages from @gopherbot can be a bit impersonal and confusing. When migrating from Google Code we had gopherbot impersonate accounts. We could do the same for comments on PRs.

It would be opt-in but as long as the main reviewers are covered, I think it would achieve its goal.

/cc @andybons
Repository: terminal
Issue: Conhost Properties Dialog → "Find out more about new console features" leads to outdated documentation
Labels: Product-Conhost,Issue-Docs,Area-UserInterface

* Setup:
    * System 1:
        * Windows 10 Pro Fall Creator's Update, Version 1709 (16299.371)
        * Release ring: Semi-Annual Channel (targeted)
        * Locale: English (United States) (en-US)
    * System 2:
        * Windows 10 Home Insider Preview, Version 1803 (17113.73)
        * Release ring: Release Preview
        * Locale: English (United States) (en-US)

* Steps to Reproduce:
    * Via command prompt:
        1. Launch `cmd` from the run dialog
        2. Right click the title of the new window
        3. Select `Properties`
        4. Click the link in `Find out more about new console features`
    * Via Powershell
        1. Launch `powershell` from the run dialog
        2. Right click the title of the new window
        3. Select `Properties`
        4. Click the link in `Find out more about new console features`

* What happens:
    * Browser opens a link a technet page: https://go.microsoft.com/fwlink/?LinkId=507549 (https://technet.microsoft.com/en-us/library/mt427362.aspx)
    * Inside the page: 
        `What's New in the Windows Console in Windows Server 2016 Technical Preview` 
        and 
        `Applies To: Windows Server Technical Preview`

* What I expected:
    * Inside the page: 
        `What's New in the Windows Console in Windows 10 Fall Creator's Update and  Windows Server 2016 version 1709` (or it's appropriate Windows Support wording)
        and
`Applies To: Windows 10 version 1709, Windows Server 2016 version 1709`

* Severity: Very low/cosmetic/documentation (for english speaking users)
    * Documentation is otherwise correct except for the above two issues
    * Other languages require automatic translations to use the page

* Possible solutions:
    * Link to: https://blogs.msdn.microsoft.com/commandline/2017/10/11/whats-new-in-windows-console-in-windows-10-fall-creators-update/ instead
        * Issues:
            * Is not a technet/windows support page/is a blog post
            * Is only available in english
    * Update: https://go.microsoft.com/fwlink/?LinkId=507549 (https://technet.microsoft.com/en-us/library/mt427362.aspx)
        * Issues:
            * Might retroactively change existing preview documentation
            * Is also only available in english(?) (there are no french/german/spanish/chinese/etc translations of the page at the moment)
    * Migrate doc to https://docs.microsoft.com/en-us/windows/console
        * Issues:
            * Requires an update of cmd.exe if a new LinkId is desired, if retroactively changing the existing LinkId is not desired
            * Technet pages seem more consistent with under the hood/administrative tool pages
Repository: node
Issue: Flexible stdios for IPC
Labels: child_process,stdio

* **Version**: master
* **Platform**: all
* **Subsystem**: child_process

A noted problem pattern is broken data flow when i) spawning OS commands that predate Node.js and that do not expect their stdios to be non-blocking. ii) Composite IPC that involves more than one Node process in the process chain.

The underlying issue is the mixed mode I/O in a number of variations based on number of parent-child combo that is possible.

While many of these can be mitigated by studying the I/O characteristics of parent and child and crafting a suitable IPC that works, inability to (programatically) control the blocking behavior (flow mode) of the stdio channel causes usability issues.


Proposals:

Node parent -> non-Node child
Node parent - Node child
 - exec family functions to receive option to control the blocking behavior of child stdios (new option)
 - adjust the child stdios accordingly, while retaining parent side of pipes non-blocking 
 - convert stdout and stderr to nonblocking prior to exit to help drain the buffered chunks (revisit #6773)

Node parent - non-Node child -> Node grand child
Node parent - non-Node child -> non-Node grand child
 - restore stdio characteristics on exit (already being worked upon in #17737)
 - convert stdout and stderr to nonblocking prior to exit to help drain the buffered chunks 

references: 
truncated stdout on porcess exit: #19218 #784 #6456 #6379
pre-fabricated duplex streams for IPC: #16553 #15714 #13542 
inconsistent IPC with process chain: #9413
unexpected flow mode for stdio: #14752 #18446 #19838
Repository: rust
Issue: Type inference fails to infer lifetimes.
Labels: C-enhancement,A-diagnostics,A-lifetimes,A-closures,T-compiler,A-inference

## Short summary

When I partially specify the `&mut` type of a `Fn` trait argument, my code compiles. If I let the compiler find it out, it fails. I cannot see a single, language-wise, reason why it should fail.

## Details

If I try the following code:
```
fn set(t : &mut usize) {}
fn reset(t : &mut usize) {}

fn main() {
    let vec : Vec<&Fn(_)> = vec![&set, &reset];
    let mut t = 0;
    for f in vec {
        f(&mut t);
    }
}
```

Then it fails to compile with the message:
```
error[E0597]: `t` does not live long enough
  --> src/main.rs:14:16
   |
14 |         f(&mut t);
   |                ^ borrowed value doeerror[E0597]: `t` does not live long enough
15 |     }
16 | }
   | - `t` dropped here while still borrowed
   |
   = note: values in a scope are dropped in the opposite order they are created
```

However, if I replace the underscore with `&mut _`, everything works fine.

I assumed that, in functions, an underscore should be strictly better for type interference than everything else, especially in this case where the borrow checker can just insert `&mut` itself. Apparently this is not the case, and I have no idea why. 

## Meta

```
$ rustc --version --verbose
rustc 1.25.0 (84203cac6 2018-03-25)
binary: rustc
commit-hash: 84203cac67e65ca8640b8392348411098c856985
commit-date: 2018-03-25
host: x86_64-unknown-linux-gnu
release: 1.25.0
LLVM version: 6.0
```
Repository: vscode
Issue: Use fresh environment block on new terminals in Windows
Labels: feature-request,windows,terminal-process

At the moment, if any environment variables change, or new "apps" are installed while VS Code is running, in order for those changes to be recognized VS Code needs to be closed and re-open. 

For instance, when running `npm i -g <something>` or `choco install <package>` in another prompt or powershell window, those new commands are not recognized until the app is rebooted.

It would be great if adding a new terminal instance with `+` would load these new variables/apps/notsurewhatterminologytouse.