sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: TUI: system(), systemlist(), :! in same process-group
Labels: compatibility,job-control,tui,system

#8217 and #8450 describe some casualties of the change in #8107: since #8107, all processes spawned by Nvim are created in their own session (by calling `setsid()` in the child). Using `setsid()`  avoids serious bugs like #6530 (orphaned processes). It's a good thing to do, and is essentially what Vim's `job_start()` does as well.

However, the terminal version (at least) of Vim doesn't do that for `system()`, `systemlist()` and `:!`.

"Fixing" this as attempted in https://github.com/neovim/neovim/pull/8389 would regress https://github.com/neovim/neovim/pull/8107 for `system()`, `systemlist()`, and `:!`. For example, CTRL-C during this command would leave orphan processes:

    :echo system('sleep 30|sleep 30|sleep 30')

Vim's approach for `system()`, `systemlist()`, and `:!` is:

1. Block signals
2. `fork()`
3. Unblock signals in the child
4. On CTRL-C, send SIGINT to the process-group id
5. The parent (`vim`) ignores the signal. The child and its descendants do _not_, so sending the signal to the group kills everything except `vim` itself.

To do this in Nvim will (I think) require adding a case in `process_spawn()` to work without using libuv. This could be implemented like how `src/nvim/os/pty_process_unix.c` implements `ProcessType.kProcessTypePty`:  add `ProcessType.kProcessTypeUnix` and special-case it.

The work will be in implementing `src/nvim/os/unix_process.c` (again as mentioned, `src/nvim/os/pty_process_unix.c` would be a good starting point).
Repository: pytorch
Issue: [caffe2] Drop connections
Labels: caffe2

Hi,

Is there a way to implement a drop connection layer in caffe2? I'm not talking of dropout.
https://stats.stackexchange.com/questions/201569/difference-between-dropout-and-dropconnect


Thanks.
Repository: rust
Issue: edition lint: migrating `extern crate` with `#[macro_use]`
Labels: C-enhancement,A-lints,T-compiler,L-macro_use_extern_crate,A-edition-2018

The migration issue is that `#[macro_use] extern crate foo;` beings macros into scope from `foo` and `extern crate` is unidiomatic in the 2018 edition. `local_inner_macros ` is the current solution but as discussed in #50911, we're not 100% that works.
Repository: rust
Issue: edition lint: declarations obviated by in-band lifetimes
Labels: A-lints,T-lang,A-edition-2018

cc https://github.com/rust-lang/rust/issues/44524

e.g., in `fn two_args<'b>(arg1: &Foo, arg2: &'b Bar) -> &'b Baz`, suggest that `<'b>` is not necessary.
Repository: TypeScript
Issue: Set TypeScript compiler's base/working directory
Labels: Suggestion,In Discussion

It looks like TypeScript compiler resolves files relative to the location of the `tsconfig.json` file (however, I couldn't find anything about paths resolution in the official documentation).

Is there a way to specify an alternative base/working directory, which will be used for relative paths resolution?

I want to use a generic `tsconfig.json` file to compile multiple projects in various directories (one at a time).

P/S: I've [created a question](https://stackoverflow.com/q/51158989/1056679) on StackOverflow first, but haven't received any attention there, so I've decided to ask here directly.
Repository: pytorch
Issue: nvcc fatal : A single input file is required for a non-link phase when an outputfile is specified
Labels: awaiting response (this tag is deprecated),caffe2

nvcc fatal   : A single input file is required for a non-link phase when an outputfile is specified
CMake Error at gloo_cuda_generated_nccl.cu.o.Release.cmake:203 (message):
  Error generating
  /home/lty/caffe2/build/third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir/nccl/./gloo_cuda_generated_nccl.cu.o


nvcc fatal   : A single input file is required for a non-link phase when an outputfile is specified
third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir/build.make:77: recipe for target 'third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir/nccl/gloo_cuda_generated_nccl.cu.o' failed
make[2]: *** [third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir/nccl/gloo_cuda_generated_nccl.cu.o] Error 1
nvcc fatal   : A single input file is required for a non-link phase when an outputfile is specified
make[2]: *** 正在等待未完成的任务....
CMake Error at gloo_cuda_generated_cuda.cu.o.Release.cmake:203 (message):
  Error generating
  /home/lty/caffe2/build/third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir//./gloo_cuda_generated_cuda.cu.o


CMake Error at gloo_cuda_generated_cuda_private.cu.o.Release.cmake:203 (message):
  Error generating
  /home/lty/caffe2/build/third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir//./gloo_cuda_generated_cuda_private.cu.o


third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir/build.make:63: recipe for target 'third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir/gloo_cuda_generated_cuda.cu.o' failed
make[2]: *** [third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir/gloo_cuda_generated_cuda.cu.o] Error 1
third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir/build.make:70: recipe for target 'third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir/gloo_cuda_generated_cuda_private.cu.o' failed
make[2]: *** [third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir/gloo_cuda_generated_cuda_private.cu.o] Error 1
CMakeFiles/Makefile2:626: recipe for target 'third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir/all' failed
make[1]: *** [third_party/gloo/gloo/CMakeFiles/gloo_cuda.dir/all] Error 2
make[1]: *** 正在等待未完成的任务....
[ 54%] Built target caffe2
[ 54%] Built target python_copy_files
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2


This is the output when make -j8 install.
I really have no idea and could not find any answer about this.
Can anyone help me?
Repository: node
Issue: Embedding: static nodejs variables are not set to default
Labels: help wanted,c++,embedding

* **Version**: v8.x (maybe any)
* **Platform**: MS Windows 7
* **Subsystem**: embedding

<!-- Enter your issue details below this comment. -->
I use nodejs to run javascript code in my application. And I have found that after running script from code, script from file will not run. It is caused by unpredicted value of `eval_string` static variable, that was not set to nullptr at previous run, and bootstrap tries to run code instead of file. Also I think, some other static variables can interrupt running scripts too.
Repository: vscode
Issue: Editor/terminal only anti aliasing
Labels: feature-request,font-rendering

So would love to have a working anti aliasing. Right now it's all or nothing with workbench setting - so either my editor fonts are blurry or, if I turn off AA then the menu fonts (which I can't appear to change) get all crappy due to them using a font that doesnt work well with AA. 

Can we please have an option to use anti aliasing in the editor and terminal only?  Seems like a pretty standard thing that all other editors support.  I realize there is a lot of discussions but all the issues have been closed with no real working resolution a far as I am concerned.
Repository: node
Issue: doc: troubleshooting FAQ?
Labels: help wanted,doc,meta

We have some frequently emerged issues mostly concerned Node.js installation. Just two classic examples:

1. Windows issue with antivirus and "Performance counters" / "Event tracing" options: https://github.com/nodejs/node/issues/20538

2. Global `npm` installation issue: https://github.com/nodejs/node/issues/21661

Should we create some troubleshooting FAQ doc and link to it from the main `nodejs/node` GitHub page and from the nodejs.org site?
Repository: rust
Issue: It would be nice if JoinHandle<T> were must-use for T != ()
Labels: A-diagnostics,T-libs-api,T-compiler,C-feature-request

One IRC today, someone had code not working because they were doing

```rust
thread::spawn(|| mylib::my_function);
```

Which of course returns the function rather than running it.

Arguably it's almost always mistake to not keep the JoinHandle if the thread is going to return a non-unit value, since if you didn't care the closure could just be `-> ()`, so this should lint, but AFAIK `#[must_use]` on the function or type would warn for `JoinHandle<()>` too today.

Repro link: https://play.rust-lang.org/?gist=fd8973579bf0bf474a7e2b9e135ff946&version=nightly
Repository: vscode
Issue: Shared properties in launch.json 
Labels: feature-request,debug

## Search Terms

launch.json, configuration, url

## Suggestion

The ability to specify shared properties among launch configurations.

Allowing properties to be inherited or specified in some common way while allowing overrides in individual entries would ease this situation greatly.

## Use Cases

For example, I have many launch configurations that are identical except the URL. Management of changes then has to be propagated to each and every entry. Often a single launch.json can contain dozens of entries, and changing something simple but common like browser or other option must be done by search and replace. SNR itself is easy, but the repeated entries clutter up the launch.json and make spotting the actual differences when they exist other than URL more difficult.

I fully understand this is a corner case and not relevant to a large audience, however it would be extremely helpful for those who do need it, and the implementation is small in scope.

## Examples

Not too picky about actual implementation, but a possible idea is below. Multiple shared configs accessed by name would be even better to allow multiple default settings.

```json
{
    "version": "0.2.0",
    "defaultConfiguration": [
            "preLaunchTask": "build",
            "request": "launch",
            "sourceMaps": true,
            "port": 9222,
            "smartStep": true,
            "breakOnLoad": true,
            "webRoot": "${workspaceRoot}"
     ],
    "configurations": [
        {
            "name": "Demo1 (Chrome)",
            "type": "chrome",
            "url": "http://127.0.0.1:8888/demo1/",
        },
        {
            "name": "Demo1 (Firefox)",
            "type": "firefox",
            "url": "http://127.0.0.1:8888/demo1/",
        },
        {
            "name": "Demo2 (Chrome)",
            "type": "chrome",
            "url": "http://127.0.0.1:8888/demo2/",
        },
    ]
```
Repository: pytorch
Issue: [Caffe2] build_ios.sh => 'is only available on iOS 11 or newer'
Labels: caffe2

## Issue description

I can't install build_ios.sh for caffe2 ios.

`aligned allocation function of tyle    ...   is only available on iOS 11 or newer`


My ipad version is higher than iOS 11.
Macbook Pro version is macOS High Sierra 10.13.5
Xcode version is 9.4.1
Python3


How can I fix the problem?!?
Thank you


iOS installing Error with below log
`[ 35%] Building CXX object caffe2/CMakeFiles/caffe2.dir/utils/threadpool/ThreadPool.cc.o
In file included from /Users/pulse9_mac/iOS/pytorch/caffe2/utils/threadpool/ThreadPool.cc:2:
In file included from /Users/pulse9_mac/iOS/pytorch/caffe2/utils/threadpool/WorkersPool.h:6:
/Users/pulse9_mac/iOS/pytorch/caffe2/core/common.h:172:29: error: aligned allocation function of
      type 'void *(std::size_t, std::align_val_t)' is only available on iOS 11 or newer
      [-Waligned-allocation-unavailable]
  return std::unique_ptr<T>(new T(std::forward<Args>(args)...));
                            ^
/Users/pulse9_mac/iOS/pytorch/caffe2/utils/threadpool/ThreadPool.cc:80:18: note: in
      instantiation of function template specialization 'caffe2::make_unique<caffe2::ThreadPool,
      int &>' requested here
  return caffe2::make_unique<ThreadPool>(numThreads);
                 ^
/Users/pulse9_mac/iOS/pytorch/caffe2/core/common.h:172:29: note: if you supply your own aligned
      allocation functions, use -Wno-aligned-allocation-unavailable to silence this diagnostic
  return std::unique_ptr<T>(new T(std::forward<Args>(args)...));
                            ^
/Users/pulse9_mac/iOS/pytorch/caffe2/core/common.h:172:29: error: aligned deallocation function
      of type 'void (void *, std::align_val_t) noexcept' is only available on iOS 11 or newer
      [-Waligned-allocation-unavailable]
  return std::unique_ptr<T>(new T(std::forward<Args>(args)...));
                            ^
/Users/pulse9_mac/iOS/pytorch/caffe2/core/common.h:172:29: note: if you supply your own aligned
      allocation functions, use -Wno-aligned-allocation-unavailable to silence this diagnostic
2 errors generated.
make[2]: *** [caffe2/CMakeFiles/caffe2.dir/utils/threadpool/ThreadPool.cc.o] Error 1
make[1]: *** [caffe2/CMakeFiles/caffe2.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....`
Repository: go
Issue: cmd/go: check for import path collision in go build
Labels: Proposal,Proposal-Accepted,NeedsFix,GoCommand

### What version of Go are you using (`go version`)?
go version go1.10.3 linux/amd64

### Does this issue reproduce with the latest release?
Yes

**Proposal:** Raise a warning or an error at compile time if the import path of a local package matches the import path of package from the standard library.
This is prevents a fairly niche problem, namely collisions, but in practice the compile error that they produce remind of a declaration/syntax/code organization error so it's pretty hard to guess what went wrong.
Repository: rust
Issue: coercions do not reach into aggregates - converging coercions
Labels: C-enhancement,T-lang,A-coercions

[This (playground):](https://play.rust-lang.org/?gist=c95124c2c3f228927fb6632c7f6e1137&version=stable&mode=debug&edition=2015)

```rust
fn foo() {}
fn bar() {}
fn main() {
    let _ = [(foo), (bar)]; // OK
    let _ = [(foo,), (bar,)]; // FAILS
}
```

fails to compile with the following error:

```
error[E0308]: mismatched types
 --> src/main.rs:5:23
  |
5 |     let _ = [(foo,), (bar,)]; // FAILS
  |                       ^^^ expected fn item, found a different fn item
  |
  = note: expected type `fn() {foo}`
             found type `fn() {bar}`
```
Repository: pytorch
Issue: [pytorch] Make dtype second positional argument of tensor factory methods
Labels: triaged,module: numpy,module: pybind,module: ux

NumPy lets the user pass dtype without kwarg, as the second positional argument: `np.zeros((3, 4), np.float32)`

In PyTorch `torch.zeros((3,4), torch.float32)` results in: `TypeError: zeros(): argument 'out' (position 2) must be Tensor, not torch.dtype`

I'd suggest the `out` argument is more exotic than `dtype`, and is a better candidate for later positional args, or as keyword-only.

cc @mruberry @rgommers @heitorschueroff
Repository: TypeScript
Issue: Poor type inference for `reduce`
Labels: Suggestion,Needs Proposal,Domain: lib.d.ts

**TypeScript Version:**  3.0.0-dev.20180705

**Code**

```ts
function toStrings(arr: ReadonlyArray<object>): string[] {
	return arr.reduce((acc, obj) => {
		acc.push(obj.toString());
		return acc;
	}, [] as string[]);
}
```

**Expected behavior:**

No error.

**Actual behavior:**

```
src/a.ts:2:2 - error TS2322: Type 'object' is not assignable to type 'string[]'.
  Property 'length' is missing in type '{}'.

2  return arr.reduce((acc, obj) => {
   ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
3  	acc.push(obj.toString());
  ~~~~~~~~~~~~~~~~~~~~~~~~~~~
4  	return acc;
  ~~~~~~~~~~~~~
5  }, [] as string[]);
  ~~~~~~~~~~~~~~~~~~~~

src/a.ts:3:7 - error TS2339: Property 'push' does not exist on type 'object'.

3  	acc.push(obj.toString());
```

No error if `arr` is `ReadonlyArray<number>` or some other non-`object` type.
No error if I explicitly specify `arr.reduce<string[]>`.
No error if I remove the first two overloads to `reduce`, which are non-generic.
Repository: flutter
Issue: add setTag to flutter_google_maps plugin
Labels: c: new feature,p: maps,customer: google,package,c: proposal,team-ecosystem,P2,triaged-ecosystem

Hi,

currently its not possible to associate any custom data to a marker on the Map which is a big disadvantage.
As the native API  offers a setTag method https://developers.google.com/maps/documentation/android-sdk/marker#marker-data

It would be great if that could be added to the `MarkerOptions` and returned by the tap handler.

Thanks for your awesome work!
Repository: go
Issue: cmd/vet: reported typecheck errors not sorted by file position
Labels: NeedsInvestigation,Analysis

Compare gc and vet typecheck errors:

```
$ go test
# golang.org/x/vgo2/vendor/cmd/go/internal/modfetch [golang.org/x/vgo2/vendor/cmd/go/internal/modfetch.test]
./coderepo.go:279:70: undefined: file2
./coderepo.go:294:8: no new variables on left side of :=
./coderepo.go:294:30: undefined: gomod
# golang.org/x/vgo2/vendor/cmd/go/internal/modfetch
./coderepo.go:294:30: undeclared name: gomod
./coderepo.go:294:8: no new variables on left side of :=
./coderepo.go:279:70: undeclared name: file2
vet: typecheck failures
```

(go test printing both sets at all is a different issue, but it is nice for seeing how they compare.)

It's weird that the errors from vet come out not sorted in file line order. They should.
Repository: vue
Issue: Error thrown when using transition-group with component v-bind:is directive
Labels: transition

### Version
2.5.16

### Reproduction link
[https://jsfiddle.net/50wL7mdz/451168/](https://jsfiddle.net/50wL7mdz/451168/)

### Steps to reproduce
Render a `component` (not just any component, but the build-in one: https://vuejs.org/v2/api/#component), with the `v-bind:is` directive set to `"transition-group"` (or simply `is="transition-group"`):

```
<component is="transition-group"></component>
```

### What is expected?
I expect no errors to be thrown.

### What is actually happening?
This component appears to work as expected but throws the following error in the console:

```
vue.js:597 [Vue warn]: Unknown custom element: <component> - did you register the component correctly? For recursive components, make sure to provide the "name" option.

found in

---> <TransitionGroup>
       <TransitionWrapper>
         <Root>
```

No error is thrown if `transition` is used instead of `transition-group`.

---
I came across this bug because I was building a re-usable animation component that looks like this:

```
<template>
  <component
    :is="group ? 'transition-group' : 'transition'"
    @enter="velocityEnter"
    @leave="velocityLeave"
  >
    <slot/>
  </component>
</template>
```

The component actually seems to work as expected, but the error described above is thrown.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: vscode
Issue: Use code editor for rename input box
Labels: feature-request,rename

Release 1.25.0 just introduced sub-word navigation –thank you!- yet it is not available on the `F2` _Rename Symbol_ input prompt box.

Ideally it should be possible to navigate in it as well. It'd be specially useful on camel-cased methods renaming.
Repository: go
Issue: net/http/cookiejar: escaped path matching
Labels: NeedsInvestigation

Some servers and software return cookies with paths encoded

eg. `/path/contains%20some%20spaces`

Go's default cookiejar can't match those when we make calls back no matter how we make them

There are some characters in RFC6265 which should be encoded/escaped, but space isn't one of the ones listed. This might be a side effect of go being really nice with urls and making it so we rarely have to deal with escaped paths in code.

### What version of Go are you using (`go version`)?
```
go version go1.10.3 darwin/amd64
```

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/user/Library/Caches/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/shannon/go"
GORACE=""
GOROOT="/usr/local/go"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
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/08/9qf64r3d209cvmgznzj49zg40000gn/T/go-build088227774=/tmp/go-build -gno-record-gcc-switches -fno-common"
```

### What did you do?

https://play.golang.org/p/_3MyXdTJbm-

nb. The cookie set in that example is forced escaping to emulate what the software I'm calling is doing.

### What did you expect to see?

all is well

### What did you see instead?

cookie not found
cookie not found

### How did you work around it

I copied cookiejar, modified jar.go to attempt to unescape the path, there might be a better option, but it worked for this instance.

```
@@ -369,6 +369,10 @@
 	if i == 0 {
 		return "/" // Path has the form "/abc".
 	}
+
+	if s, err := url.PathUnescape(path[:i]); err == nil {
+		return s
+	}
 	return path[:i] // Path is either of form "/abc/xyz" or "/abc/xyz/".
 }

@@ -386,6 +390,8 @@

 	if c.Path == "" || c.Path[0] != '/' {
 		e.Path = defPath
+	} else if path, err := url.PathUnescape(c.Path); err == nil {
+		e.Path = path
 	} else {
 		e.Path = c.Path
 	}
```
Repository: pytorch
Issue: Where is the include and lib path for caffe2?
Labels: caffe2

i installed pytorch with caffe2 from source by using 'python setup_caffe2.py install' command.
Can anyone tell that where is the default include and lib path for caffe2?
Repository: pytorch
Issue: [Caffe2] compiling error with gcc-6
Labels: caffe2

If you have a question or would like help and support, please ask at our
[forums](https://discuss.pytorch.org/).

If you are submitting a feature request, please preface the title with [feature request].
If you are submitting a bug report, please fill in the following details.

## Issue description
When compiling caffe2, the following error occurs

[ 72%] Linking CXX shared library ../lib/libcaffe2.so
[ 72%] Built target caffe2
[ 72%] Building NVCC (Device) object caffe2/CMakeFiles/caffe2_gpu.dir/sgd/caffe2_gpu_generated_yellowfin_op_gpu.cu.o
gcc-6: error: unrecognized command line option ‘-faligned-new’; did you mean ‘-falign-jumps’?
CMake Error at caffe2_gpu_generated_yellowfin_op_gpu.cu.o.Release.cmake:219 (message):
  Error generating
  /home/mburon/pytorch/build/caffe2/CMakeFiles/caffe2_gpu.dir/sgd/./caffe2_gpu_generated_yellowfin_op_gpu.cu.o


caffe2/CMakeFiles/caffe2_gpu.dir/build.make:917: recipe for target 'caffe2/CMakeFiles/caffe2_gpu.dir/sgd/caffe2_gpu_generated_yellowfin_op_gpu.cu.o' failed
make[2]: *** [caffe2/CMakeFiles/caffe2_gpu.dir/sgd/caffe2_gpu_generated_yellowfin_op_gpu.cu.o] Error 1
CMakeFiles/Makefile2:1442: recipe for target 'caffe2/CMakeFiles/caffe2_gpu.dir/all' failed
make[1]: *** [caffe2/CMakeFiles/caffe2_gpu.dir/all] Error 2
Makefile:140: recipe for target 'all' failed
make: *** [all] Error 2

Provide a short description.

## Code example

Please try to provide a minimal example to repro the bug.
Error messages and stack traces are also helpful.

## System Info
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 or Caffe2: Caffe2
- How you installed PyTorch (conda, pip, source): cmake of caffe2
- Build command you used (if compiling from source): sudo make install
- OS: Ubuntu 18
- PyTorch version: 
- Python version: 2.7
- CUDA/cuDNN version: 9.0 / 7.0.5
- GPU models and configuration: GTX 1070
- GCC version (if compiling from source): gcc-6
- CMake version: 3.10.2
- Versions of any other relevant libraries: