sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: API: buffer updates: merge result of visual operation
Labels: enhancement,api

<!-- Before reporting: search existing issues and check the FAQ. -->

- `nvim --version`: v0.3.1
- Vim (version: ) behaves differently? neovim only
- Operating system/version: Max
- Terminal name/version:  iTerm2
- `$TERM`: xterm-256color

### Steps to reproduce using `nvim -u NORC`

Create a file at `$NVIM_CONFIG/rplugin/node` with:

``` js

async function setup(nvim) {
  let id = await nvim.channelId
  let buffer = await nvim.buffer
  let lines = await buffer.lines
  buffer.listen('lines', (buf, tick, firstline, lastline, linedata, more) => {
    console.error(firstline)
    console.error(lastline)
    console.error(linedata.length)
  })
}

module.exports = (plugin) => {
  let {nvim} = plugin
  plugin.registerCommand('LiveListen', setup.bind(null, nvim), {sync: false})
}
```
Run `:UpdateRemotePlugins`

Open a file and run `:LiveListen` and have virtual selection like:

<img width="115" alt="screen shot 2018-06-20 at 1 34 11 am" src="https://user-images.githubusercontent.com/251450/41614154-49757cdc-742a-11e8-9909-2e2c42b638f1.png">

And delete the selection by type `d`

### Actual behaviour

The result would be `firstline: 1, lastline: 2, linedata: []`

### Expected behaviour

The result should be `firstline: 0, lastline: 2, linedata: ['a']`

The change of first line is not calculated.
Repository: vscode
Issue: Issue Reporter is unstable when number of duplicates change
Labels: bug,polish,issue-reporter

Issue Type: <b>Bug</b>

See the following recording. When editing the description the text input filed jumps up and down. It should be stable.

VS Code version: Code - Insiders 1.25.0-insider (b4a18da6e78f95295ea6538f5ae8dd0c9f0869a9, 2018-06-19T07:38:09.923Z)
OS version: Darwin x64 16.7.0

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz (8 x 2500)|
|GPU Status|2d_canvas: enabled<br>checker_imaging: disabled_off<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>native_gpu_memory_buffers: enabled<br>rasterization: enabled<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|2, 2, 2|
|Memory (System)|16.00GB (3.53GB free)|
|Process Argv|/Users/kmaetzel/Applications/Visual Studio Code - Insiders.app/Contents/MacOS/Electron -psn_0_14822946|
|Screen Reader|no|
|VM|0%|

</details><details><summary>Extensions (25)</summary>

Extension|Author (truncated)|Version
---|---|---
solargraph|cas|0.17.4
npm-intellisense|chr|1.3.0
regex|chr|0.2.0
githistory|don|0.4.1
gitlens|eam|8.4.1
tslint|eg2|1.0.32
vscode-npm-script|eg2|0.3.4
vsc-material-theme|Equ|2.1.0
git-project-manager|fel|1.6.1
crazy|kie|0.0.2
svgpreview|kis|0.2.0
vscode-azurestorage|ms-|0.3.1
mssql|ms-|1.3.1
python|ms-|2018.5.0
azure-account|ms-|0.4.0
azurecli|ms-|0.4.2
Go|ms-|0.6.83
vsliveshare|ms-|0.3.295
printcode|nob|2.3.0
vscode-docker|Pet|0.0.27
material-icon-theme|PKi|3.5.0
Ruby|reb|0.18.0
kustovscode|sea|0.0.1
php-syntax-visualizer|vsc|0.0.1
vscode-open-in-github|ziy|1.3.3

(3 theme extensions excluded)

</details>
<!-- generated by issue reporter -->

![r7a3p884ra](https://user-images.githubusercontent.com/4674940/41616631-4372a82c-73b3-11e8-8ed2-10c00617e161.gif)
Repository: vue
Issue: Dynamic input field type renders invalid code in IE11
Labels: improvement

### Version
2.5.17-beta.0

### Reproduction link
[https://github.com/nirazul/vue-loader-bug-repro](https://github.com/nirazul/vue-loader-bug-repro)

### Steps to reproduce
1. `npm install`
2. `npm run build`
3. `npm run watch`
4. Open `./public/index.html`
5. Inspect `main.bundle.js` in dev tools
6. On line 9044 you will find a duplicated key `value`

### What is expected?
A valid output from vue-template-compiler without duplicated value props, or at least a warning that the usage of dynamic input field types is prohibited in certain cases.

### What is actually happening?
In IE11 a blank page is rendered

---
I'm using a centralized component for both radio and checkbox input fields as the markup is 90% the same.
As we switched from webpack 3 to webpack 4, we had to also upgrade the vue-loader version from 12 to 13 or 14, which introduced this bug. 
Prior to version 13, vue-template-renderer was not enforcing strict mode on all of its rendered templates. This is now the case, introducing this critical bug.


References:
https://vuejs.org/v2/guide/forms.html#Radio-1
https://github.com/vuejs/vue/issues/7048
https://github.com/vuejs/vue/issues/6917

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: go
Issue: x/build: add misc-compile-mobile TryBots for Android/iOS
Labels: Builders,NeedsInvestigation,FeatureRequest,new-builder

https://storage.googleapis.com/go-build-log/21200cf2/misc-compile-mobile_0b3b3144.log

```
/workdir/go/pkg/tool/linux_amd64/link: running gcc failed: exit status 1
/tmp/go-link-391904482/go.o:(.data+0x0): undefined reference to `x_cgo_init'
/tmp/go-link-391904482/go.o:(.data+0x4): undefined reference to `x_cgo_notify_runtime_init_done'
/tmp/go-link-391904482/go.o:(.data+0x8): undefined reference to `x_cgo_thread_start'
/tmp/go-link-391904482/go.o:(.data+0x14): undefined reference to `x_cgo_setenv'
/tmp/go-link-391904482/go.o:(.data+0x18): undefined reference to `x_cgo_unsetenv'
/tmp/go-link-391904482/go.o:(.data+0x1c): undefined reference to `_cgo_yield'
collect2: error: ld returned 1 exit status
```

If this is caused by my change (https://go-review.googlesource.com/c/go/+/109697) I can't see it.

/cc @bradfitz
Repository: neovim
Issue: :q, :qa shouldn't quietly kill terminal buffers
Labels: terminal

<!-- Before reporting: search existing issues and check the FAQ. -->

- `nvim --version`: v0.3.1-dev
- Vim (version: ) behaves differently? 8.1.89. Yes. Depending on `'confirm'`, fails or opens dialog
- Operating system/version: Ubuntu 18.04
- Terminal name/version: gnome-terminal 3.28.1
- `$TERM`: tmux-256color

### Steps to reproduce using `nvim -u NORC`

```
nvim -u NORC
Open a terminal buffer with `:terminal`.
Type `:q` or `:qa` to quit.
```

### Actual behaviour

Neovim quits, killing the terminal buffer silently.

### Expected behaviour

- If `'confirm'` is not set, `:q` (or `:qa`) should fail.
- If `'confirm'` is set, `:q` (or `:qa`) should open a Yes/No/Cancel dialog, offering to kill each open terminal buffer, just as it does for each changed file buffer.
Repository: TypeScript
Issue: Enum keys not accepted as computed properties if their name is not a valid identifier
Labels: Bug,Good First Issue

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  2.9.2

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** computed property name

**Code**

```ts
enum Type {
  Foo = 'foo',
  '3x14' = '3x14'
}

type TypeMap = {
  [Type.Foo]: any
  [Type['3x14']]: any
}
```

**Expected behavior:**
`Type['3x14']` to be usable as a computed key in a type definition.

**Actual behavior:**
`A computed property name in a type literal must refer to an expression whose type is a literal type or a 'unique symbol' type.`

This is the case even for `Type.Foo` if it's written as `Type['Foo']` instead; so it seems there is some early bailout when the bracket operator is involved. For certain key names it may not be possible to write them without resorting to brackets, like a name that starts with a digit.

**Playground Link:** [Link](https://www.typescriptlang.org/play/#src=enum%20Type%20%7B%0A%20%20Foo%20%3D%20'foo'%2C%0A%20%20'3x14'%20%3D%20'3.14'%0A%7D%0A%0Atype%20TypeMap%20%3D%20%7B%0A%20%20%5BType.Foo%5D%3A%20any%0A%20%20%5BType%5B'3x14'%5D%5D%3A%20any%0A%7D%0A)
Repository: godot
Issue: PoolColorArray.set doesn't work
Labels: topic:gdscript,documentation

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:** 3.0.3
<!-- Specify commit hash if non-official. -->


**OS/device including version:** Linux x64 (SolusOS 3.9999 Gnome 3.28.2)
<!-- Specify GPU model and drivers if graphics-related. -->


**Issue description:**
<!-- What happened, and what was expected. -->
I'm trying to use `Polygon2D.vertex_color.set(0, color)` and this approach doesn't do nothing, while `vertex_colors[0] = color` works, the below doesn't:

```GDScript
func _ready():
	var color = Color(1, 1, 1, 1)
	print(color)
	vertex_colors.set(0, color)
	print(vertex_colors[0])
```
the print returns:

```
1,1,1,1
1,0.701961,0.501961,1
```

While `Polygon2D.vertex_color` by creating another `PoolColorArray`:

```GDScript
var white = Color(1, 1, 1, 1)
	var colors = [white, white, white, white]
	print(colors[0])
	vertex_colors = colors
	print(vertex_colors[0])
```

the print returns:

```
1,1,1,1
1,1,1,1
```
Both are reflected in the actual game (first one doesn't modify the Polygon2D vertex colors, second approach does)

Also, during some tests I realized that unfortunately we have a `not true` statement on latest post about the [Animation System](https://godotengine.org/article/godot-gets-brand-new-animation-editor-cinematic-support).

I tried to `Tween.interpolate_property` and `Tween.interpolate_method` both trying to interpolate the `Polygon2D.vertex_color` and I got this error:

```
0:00:00:0209 - Invalid param type, except(int/real/vector2/vector/matrix/matrix32/quat/aabb/transform/color)
----------
Type:Error
Description: 
Time: 0:00:00:0209
C Error: Invalid param type, except(int/real/vector2/vector/matrix/matrix32/quat/aabb/transform/color)
C Source: scene/animation/tween.cpp:991
C Function: _calc_delta_val
```

So it seems like:

> any property from any object can be animated or tweened

Is not true, unfortunately :(

**Steps to reproduce:**
1. Create a Polygon2D
2. On its `vertex_colors` property create the desired array
3. Try to `PoolColorArray.set(index, color)`

---

1.Create 2 PoolColorArray
2. Try to `Tween.interpolate_property` using them as `initial_value` and `final_value`

**Minimal reproduction project:**
<!-- Recommended as it greatly speeds up debugging. Drag and drop a zip archive to upload it. -->

[Polygon2D.zip](https://github.com/godotengine/godot/files/2119646/Polygon2D.zip)
Repository: flutter
Issue: ShadowBox inset attribute? Inner shadow
Labels: c: new feature,framework,customer: crowd,P3,team-framework,triaged-framework

I didn't find any trace of inner shadow for box.
Like in CSS using box-shadow: inset there is a option to achieve the same effect?
Repository: puppeteer
Issue: Disable crash reporting by default
Labels: bug,feature,upstream,chromium,confirmed,P3

Win CI usually fails to cleanup userDataDir folder in some tests. Example: [appveyour build](https://ci.appveyor.com/project/aslushnikov/puppeteer/build/1.0.1672/job/j2bllv92su3uajye)

It turns out that on Windows:
- crash pad  is launched in a separate process
- crash pad writes a few files into userDataDir
- crash pad process doesn’t necessarily shutdown when we close browser.

As a result, we fail to remove temporary user data directory.

We need to disable crash reporting by default. Somehow chrome headless ignores the `--disable-breakpad` flag and launches crashpad anyway; this requires investigation and fixing upstream.
Repository: rust
Issue: 1.27.0 Compiler Options: no-redzone option (Is the explanation backwards?)
Labels: C-enhancement,P-medium,T-compiler,A-docs

In the 1.27.0 release of the "Rustc Book", the command-line option "no-redzone" is described as follows:

no-redzone

This flag allows you to disable the red zone. This flag can be passed many options:

    To enable the red zone: y, yes or on.

    To disable it: n, no, or off.

This sounds backwards. Should it be "no-redzone=yes" would disable the RedZone and "no-redzone=no" would enable the "RedZone"? If not, it seems like the command-line option is misnamed and should be "redzone" rather than "no-redzone".
Repository: go
Issue: cmd/go: get fails to provide sensible error message for private vcs repos
Labels: NeedsFix,GoCommand,modules

#### What did you do?
I have a project that imports a private git repository. When setting it up with `vgo get` or similar commands, the resolving process will stop abruptly, not writing anything to the disk.

The command succeeds if git credentials are properly set up (*_ASKPASS, global config or the repo is already cloned with the right config, etc.).

#### What did you expect to see?
An error message, or some indication of what went wrong

#### What did you see instead?
No error message, just an exit code 1.

#### System details

```
go version go1.10.3 linux/amd64 vgo:2018-02-20.1
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/exploser/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/exploser/go"
GORACE=""
GOROOT="/usr/lib/go"
GOTMPDIR=""
GOTOOLDIR="/usr/lib/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
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 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build534162883=/tmp/go-build -gno-record-gcc-switches"
GOROOT/bin/go version: go version go1.10.3 linux/amd64
GOROOT/bin/go tool compile -V: compile version go1.10.3
uname -sr: Linux 4.16.14-2-MANJARO
LSB Version:	n/a
Distributor ID:	ManjaroLinux
Description:	Manjaro Linux
Release:	17.1.10
Codename:	Hakoila
/usr/lib/libc.so.6: GNU C Library (GNU libc) stable release version 2.27.
gdb --version: GNU gdb (GDB) 8.1
```
Repository: rust
Issue: #[macro_use] use path; produces unhelpful diagnostics
Labels: C-enhancement,A-diagnostics,T-compiler,A-suggestion-diagnostics

```rust

mod a {
    macro_rules! foo { () => {}; }
}

mod b {
    #[macro_use]
    use a;
    
    foo!();
}

fn main() {}
```

```
   Compiling playground v0.0.1 (file:///playground)
error: cannot find macro `foo!` in this scope
  --> src/main.rs:10:5
   |
10 |     foo!();
   |     ^^^
   |
   = help: have you added the `#[macro_use]` on the module/import?
```

The error message even seems to suggest that this is what you're supposed to write, by using the phrase "on the module/**import**"
Repository: puppeteer
Issue: Support Network requests in Workers
Labels: feature,upstream,chromium

WebWorkers can `fetch` data; we should surface traffic from web workers in puppeteer.

This is blocked on #2548 since nested targets are broken with request interception. See https://github.com/GoogleChrome/puppeteer/pull/2717#issuecomment-398899616 for details.
Repository: flutter
Issue: Reduce duplication in RenderOpacity and RenderAnimatedOpacity
Labels: team,framework,P3,team-framework,triaged-framework

RenderOpacity and RenderAnimatedOpacity contain quite a bit of duplicated code.  

This duplication even resulted in a recent nuanced bug that showed itself when a RenderOpacity was changed to a RenderAnimatedOpacity and broke a golden image test.  

The duplication between these two classes should be reduced to avoid future discrepancies.
Repository: godot
Issue: Nested viewports don't work correctly with get_local_mouse_position()
Labels: bug,topic:core,confirmed

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:**
3.0.2


**OS/device including version:**
Windows 10


**Issue description:**
When nesting viewports (viewportcontainer/viewport/viewportcontainer/viewport), the mouse input is always scaled from the root viewport instead of the parent.


**Steps to reproduce:**
Make 4 nodes with the following hierarchy:
viewportcontainer/viewport/viewportcontainer2/viewport2
scale viewportcontainer, and call get_local_mouse_position() on viewportcontainer2. It will pass the local position as if it was not a child of viewportcontainer.

<!--**Minimal reproduction project:**
 Recommended as it greatly speeds up debugging. Drag and drop a zip archive to upload it. -->
Repository: pytorch
Issue: [caffe2] AffineChannelOp
Labels: caffe2

Hi,

If I use a SpatialBN (spatial batch normalization), when using the net in production, do I need to put a AffineChannelOp or is setting the flag is_test to true enough?

What do you advise? If I need to use an AffinChannelOp, how to do this?

Thanks a lot for anybody helping me.
Repository: neovim
Issue: Project concept
Labels: enhancement,core

# Problem

With large projects with multiple directories, files like Session.vim, tags files, and other similar "project files" could be anywhere within the project.

# Expected behavior

With a "project" feature, commands like `:vimgrep`, `:make`, `nvim -S Session.vim`, etc., load files from the project directory.

I was thinking of having 4 options:

- ~~`project: boolean` (default 0 for compatibility) When this option is set to true, neovim sets the 'projectdir' and looks for makefiles, cscope dbs, etc, inside the cwd, then inside 'projectdir'. When set to false, neovim acts as usual When 'autochdir' is set, neovim changes the directory to the project directory~~
    - *(2024 justinmk)* Doesn't seem necessary; instead, always do the right thing based on the presence of `&l:rootdir` or `.nvim.lua` ?
- `projectfunc: string` (default: empty) Decides the project directory by a custom function. If nil, the project directory is determined by searching parent directories for the projectfiles
    - *(2024 justinmk)* related: https://github.com/neovim/neovim/pull/31630
- `projectdir: string` (default: empty) Set by projectfunc or projectfiles.  The directory of the project
    - *(2024 justinmk)* I assume this is buffer-local option? Alternative names: `rootdir`, `workdir`
- `projectfiles: list` (default: ".git,src,etc") Files/directories to search for in parent directories.  Searches from left to right eg. search for .git, then src, etc
    - *(2024 justinmk)* In `vim.lsp.config` we named this `root_markers`.
Repository: pytorch
Issue: [Feature Request] Add to() method for optimizers/schedulers
Labels: todo,module: optimizer,triaged

I think the optimizers and schedulers could use some extra work.  
The main thing I would love, is for optimizers and schedulers to have a `to()` method so we can send their parameters to a certain device. This would allow us to save the parameters and reload them at a later stage without any problems.

Right now, the following script crashes with an error that the optimizer expects a `torch.FloatTensor` but got a `torch.cuda.FloatTensor`. I am not quite sure why, as I specifically load the data to CPU?

```python
# Note: This is not my actual script, but rather a representation of the steps and in what order I perform them
network = ... # Creating a network based of torch.nn.Module
optim = torch.optim.SGD(network.parameters(), ...)

state = torch.load('file_path', lambda storage, loc: storage)  # Send all tensors to CPU

network.load_state_dict(state['network'])
optim.load_state_dict(state['optim'])

network.to(torch.device('cuda'))
#optim.to(torch.device('cuda'))   # Would this solve my problems? 
```

The same could be said about schedulers.
Repository: go
Issue: cmd/go: document exit codes of a process executing `go test`
Labels: Documentation,NeedsInvestigation

Please answer these questions before submitting your issue. Thanks!

### What version of Go are you using (`go version`)?

1.10.3

### Does this issue reproduce with the latest release?

Yes.

### What operating system and processor architecture are you using (`go env`)?

```
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/user/.cache/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOOS="linux"
GOPATH="/home/user/devel/go"
GORACE=""
GOROOT="/home/user/devel/golang1.10"
GOTMPDIR=""
GOTOOLDIR="/home/user/devel/golang1.10/pkg/tool/linux_amd64"
GCCGO="gccgo"
CC="gcc"
CXX="g++"
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 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build141686204=/tmp/go-build -gno-record-gcc-switches"
```

### What did you do?

I run `go help test` and try to search for keywords "return", "exit", "code" in the output.

### What did you expect to see?

I expect the possible exit codes for running `go test` be documented
in order to make sensible decisions about running this command in scripts
(and from Makefiles, by a CI system etc).

### What did you see instead?

No menton of the return/exit code.

----

I'd expect the following cases to be documented *if implemented:*

- Successful run—all tests compiled and passed OK—exit code 0.
- Failed run—the compilation of at least one package failed or at least a single test failed—a non-zero exit code.
- Invalid parameters passed and/or one of the listed packages wasn't found—a non-zero exit code,
different from that of the former case.

I'd also think that the cached results should effectively "memorize" the exit codeused ATM the results were generated (and cached).

See also #23716.
Repository: go
Issue: spec: legal conversions from string constant to byte slice are not covered by convertability rules
Labels: Documentation,NeedsFix

According to [Conversions](https://golang.org/ref/spec#Conversions) (as of 21.06.2018), the following programs should be illegal, but it compiles without errors:
```
package main

func main() {
	_ = []byte("s") // no compile time error
}
```
Here we have constant value `"s"` converted to `[]byte`. According to spec, `"s"` must be [Representable](https://golang.org/ref/spec#Representability) by `[]byte`. The only way to explain the absence of error is to suppose that `"s"` is in the set of values determined by `[]byte`.

The assumption above contradicts with [Assignability](https://golang.org/ref/spec#Assignability) rules. Consider the following program that fails to compile:
```
package main

func main() {
	var b []byte
	b = "s" // compile time error
}
```
So, `"s"` is not assignable to `[]byte`. As a consequence, `"s"` is not representable by `[]byte` and `"s"` is **not** in the set of values determined by `[]byte`.
Repository: go
Issue: cmd/compile: record and use per-function optimization data
Labels: Performance,NeedsInvestigation,compiler/runtime

This is an open-ended performance idea to explore.

We have per-function compiler-specific export data (see method funcExt in iexport.go). We could do some analysis in package ssa of return values, add that to the export data, and use it on import. This might help with function calls that cannot be inlined.

For example, we could record whether a return value is known to be non-nil. Or a known limited range for a return value. Or a concrete type for a function that returns an interface.

Related: #25862. If we pursue this idea, the mechanism for using info about the return values could be re-used with some annotation for #25862. And possibly also to generalize and simplify the ssa rule "don't nilcheck the return value of newobject".

We could also return things like the ratio of Nodes to instructions, which we might want to use to improve downstream inlining decisions.

One weird thing about doing this is that calling functions from imported packages might optimize further than calling functions from within the same packages. (A similar problem arises for some of the ideas mooted in #17566.) Still probably worth exploring.

cc @randall77 @martisch @dr2chase @cherrymui
Repository: pytorch
Issue: [JIT] Add peephole to delete unnecessary type_as.
Labels: oncall: jit

Context: #8687

This peephole should be probably be run on specialized graphs (in an unspecialized graph, it is hard to tell if a type_as is unnecessary).