sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: neovim
Issue: :execute "?search" with 'nostartofline' does not change cursor column
Labels: bug-vim,core

- `nvim --version`: 

```
NVIM v0.5.0-dev
Build type: RelWithDebInfo
Lua 5.1
Compilation: /usr/bin/cc -g -O2 -fdebug-prefix-map=/build/neovim-vP8h0G/neovim-0.5.0+ubuntu1+git201912060004-ed42465-00e710e=. -fstack-protector-strong -Wformat -Werror=format-security -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -DMIN_LOG_LEVEL=3 -I/build/neovim-vP8h0G/neovim-0.5.0+ubuntu1+git201912060004-ed42465-00e710e/build/config -I/build/neovim-vP8h0G/neovim-0.5.0+ubuntu1+git201912060004-ed42465-00e710e/src -I/build/neovim-vP8h0G/neovim-0.5.0+ubuntu1+git201912060004-ed42465-00e710e/.deps/usr/include -I/usr/include -I/build/neovim-vP8h0G/neovim-0.5.0+ubuntu1+git201912060004-ed42465-00e710e/build/src/nvim/auto -I/build/neovim-vP8h0G/neovim-0.5.0+ubuntu1+git201912060004-ed42465-00e710e/build/include
Compiled by buildd@lgw01-amd64-018

Features: +acl +iconv +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

Run :checkhealth for more info
```

- `vim -u DEFAULTS` (version: ) behaves differently? Yes it does
- Operating system/version: Ubuntu 18.04
- Terminal name/version: xfce4-terminal
- `$TERM`: screen-256color (within tmux)

### Steps to reproduce using `nvim -u NORC`


```
printf "foobar\nbarfoo\nbazfoo\nbarbar\n" > test.txt; nvim -u NONE test.txt
# Inside vim : 
# Place yourself at the end of the document, end of the line
G$
# Reverse search for baz. (Within execute because this is executed within say a plugin)
:execute "?baz"
```

### Actual behaviour

The cursor is placed on the right line (line 3), but the column has not changed
![Selection_001](https://user-images.githubusercontent.com/2071336/70315863-c1ed6b80-181a-11ea-9008-175a61124e95.png)


### Expected behaviour

The cursor should be placed on the right line, and on column 1 : 

![Selection_002](https://user-images.githubusercontent.com/2071336/70315883-ca45a680-181a-11ea-988b-a5dbab29f816.png)

The behavior is correct for `vim`, and also when using `?baz` directly, without execute.
Repository: pytorch
Issue: save model definition file
Labels: feature,module: serialization,triaged

## 🚀 Feature
I noticed that torch.save() has already saved the model definition file. However, a model still needs to be defined in advance when loading. It is inconvenient to the user-defined  model structure. Since the relative paths must be consistent.

## Motivation
I always keep model in one place and often loaded failed.

## Pitch
torch.load can save forward process.

## Alternatives

<!-- A clear and concise description of any alternative solutions or features you've considered, if any. -->

## Additional context

<!-- Add any other context or screenshots about the feature request here. -->
Repository: vscode
Issue: Trailing comma-aware move line up/down
Labels: feature-request,json,editor-autoindent

Some files like JSON or pre-ES6 JavaScript files don't allow trailing commas, so moving last line in a block up or moving other line to the bottom causes these files to be corrupted and in a need of manual editing.

```json5
{
  "someProperty": 1,
  "otherProperty": 2,
  "anotherProperty": 3 /* <-- My cursor is in this line */
}
```

Now, I press <kbd>option</kbd>+<kbd>↑</kbd> and...

## Current behavior

```json5
{
  "someProperty": 1,
  "anotherProperty": 3
  "otherProperty": 2,
}
```

...oh no! two errors! 

* Expected comma json(514) [4, 3]
* Trailing comma json(519) [4, 20]

## Expected behavior

```json5
{
  "someProperty": 1,
  "anotherProperty": 3,
  "otherProperty": 2
}
```

Everything good!
Repository: gin
Issue: time_format tag not work with ShouldBindJSON?
Labels: bug

## Description

I have the param struct like this:

```
type Param1 struct {
	Timestamp time.Time `json:"Timestamp" binding:"required" time_format:"2006-01-02 15:04:05"`
}

type Param2 struct {
	Timestamp time.Time `json:"Timestamp" binding:"required" time_format:"unix"`
}
```

request json for Param1:
```
{
    "Timestamp": "2001-11-11 11:11:11"
}
```

response error:
```
parsing time \"\"2001-11-11 11:11:11\"\" as \"\"2006-01-02T15:04:05Z07:00\"\": cannot parse \" 11:11:11\"\" as \"T\"]
```

request json for Param2:
```
{
     "Timestamp": 1575528300
}
```

response error:
```
parsing time \"1575528300\" as \"\"2006-01-02T15:04:05Z07:00\"\": cannot parse \"1575528300\" as \"\"\"]
```

## Environment

- go version: 1.13
- gin version (or commit ref): 1.5.0
- operating system: macOS
Repository: TypeScript
Issue: JSDoc @type annotation ignored in chained variable declaration
Labels: Suggestion,Awaiting More Feedback

I'm not sure whether this is a bug or a feature request:

**TypeScript Version:**  Version 3.8.0-dev.20191206
also confirmed in 3.7.2

**Search Terms:** type ignored

**Code**

```javascript
var 
/** @type {string} */
str1,
/** @type {number} */
num1;

/** @type {string} */
var str2;
/** @type {number} */
var num2;



str1 = "Hello";
num1 = "World"; // TSC does not complain => not OK

str2 = "Hello";
num2 = "World"; // TSC complains => OK
```

**Expected behavior:**
```
test.js:15:1 - error TS2322: Type '"World"' is not assignable to type 'number'.

15 num1 = "World";

test.js:18:1 - error TS2322: Type '"World"' is not assignable to type 'number'.

18 num2 = "World";
```


**Actual behavior:**
```
test.js:18:1 - error TS2322: Type '"World"' is not assignable to type 'number'.

18 num2 = "World";
```
**Playground Link:** Unable to reproduce any type related warning in JS PlayGround, please test locally

**Related Issues:** #22434, #13371 (somewhat related)

The official JSDoc documentation says nothing about mixing types within one `var` statement, but I guess that if the TS notation works, the behavior for JS might be the same.
```ts
var str1: string,
num1: number;
```
Repository: create-react-app
Issue: Suggestion: Add one line in CRA-originated index.html that disable Chrome's automatic translation
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

A deployed CRA-originated app ran into crashes. The error text:
> react-dom.production.min.js:4260 DOMException: Failed to execute 'removeChild' on 'Node': The node to be removed is not a child of this node.

This is caused by Chrome's automatic translation feature. It seems it can modify a DOM node such that React's rendering process then fails. It is probably a fairly unusual error, but tricky to diagnose.

### Describe the solution you'd like

The suggestion is to add
<meta name=“google” content=“notranslate” />

which according to Googles support pages (and in practice) then disables the automatic translation feature, and in turn React's rendering does not crash.

### Describe alternatives you've considered

It is likely that React already tries at least somewhat to handle effects of browser plugins that change the DOM under the renderer process' feet, but maybe the Chrome translation is able to hide or somehow surprise any such protections. So there might be more interesting ways to solve this.

Other alternatives is to educate all users on how to disable this translation feature.

### Additional context

Only Chrome has been specifically investigated. There are likely other browsers that offer automatic translation that can cause similar issues.
Repository: godot
Issue: Empty scene handling inconsistentcy
Labels: enhancement,discussion,topic:editor

**Godot version:** v3.1.2.stable.official & v3.2.beta.custom_build.0aea0d0b3

**OS/device including version:** macOS Catalina 10.15.1

**Issue description:**

If there are two or more scenes open (whether empty or not), empty scenes are treated just like "normal" non-empty scenes, nothing special.

If the only open scene is an empty scene:
* Some commands (e.g. "New Scene") treat the empty scene as a normal scene
* Some other commands (e.g. "Open Scene") treat the empty scene as a placeholder: the newly opened scene will replace the empty scene; closing an empty scene does nothing...

I think this behavior is strange.
* If an empty scene is just a placeholder, then there should not be two of them open at the same time. Create a New Scene over an empty scene should do nothing.
* "Open Scene" over an empty scene behave differently when the only open scene is an empty scene, and when there are two scenes open.

IMHO, some clearer ways may be:
* Don't special treat empty scenes at all
* Treat empty scene as a placeholder: only one empty scene allowed, no matter how many scenes are currently open
Repository: flutter
Issue: Rendering order inside Grid/ListView
Labels: c: new feature,framework,f: scrolling,P3,team-framework,triaged-framework

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill our the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

I'd like to be able to change the drawing order of children in a GridView.  Right now they are drawn in the order they appear in the children list.  If they overlap there is no way to control how they overlap.

<!--
     Please tell us the problem you are running into that led to you wanting
     a new feature.

     Is your feature request related to a problem? Please give a clear and
     concise description of what the problem is.

     Describe alternative solutions you've considered. Is there a package
     on pub.dev/flutter that already solves this?
-->

## Proposal
Add rendering order for child indexes, something like CSS's "z-index".
<!--
     Briefly but precisely describe what you would like Flutter to be able to do.

     Consider attaching images showing what you are imagining.

     Does this have to be provided by Flutter directly, or can it be provided
     by a package on pub.dev/flutter? If so, maybe consider implementing and
     publishing such a package rather than filing a bug.
-->
## Video
![ezgif com-video-to-gif](https://user-images.githubusercontent.com/6845754/70332313-5e7f3000-1852-11ea-98a9-036d48fea653.gif)
Repository: go
Issue: cmd/compile: -d=checkptr doesn't detect invalid pointer fields in converted pointers-to-structs
Labels: help wanted,NeedsInvestigation,compiler/runtime

<!-- Please answer these questions before submitting your issue. Thanks! -->

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version devel +0915a19a11 Fri Dec 6 05:12:15 2019 +0000 linux/amd64
</pre>

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE="on"
GOARCH="amd64"
GOBIN=""
GOCACHE="~/.cache/go-build"
GOENV="~/.config/go/env"
GOEXE=""
GOFLAGS=" -mod="
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="~/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="~/projects/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="~/projects/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
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-build392569888=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?

```golang
package tmp

import (
	"testing"
	"unsafe"
)

func TestUnsafeCast(t *testing.T) {
	var x uint32 = 0
	p := (*uint64)(unsafe.Pointer(&x))
	t.Log(*p)
}

func TestUnsafeStructCast(t *testing.T) {
	var x uint32 = 0

	type A struct {
		p *uint32
	}
	type B struct {
		p *uint64
	}

	v := &A{ptr:&x}
	p := (*B)(unsafe.Pointer(v))
	t.Log(*p.p)
}
```

### What did you expect to see?

Both `TestUnsafeCast` and `TestUnsafeStructCast` fail with `go test -gcflags=-d=checkptr`, since both use invalid `unsafe.Pointer` casts.

### What did you see instead?

Only the `TestUnsafeCast` fails. Pointer fields are not verified properly.
Repository: pytorch
Issue: ReduceLROnPlateau detects a plateau during a steady decrease after a spike
Labels: module: optimizer,triaged

I'm not sure if this is best described as a bug report, feature request, or even documentation clarification. I'm describing an unintuitive and undesired behaviour, but not necessarily a wrong behaviour.

The name and documentation of `ReduceLROnPlateau` suggests that it will step the LR when the loss is no longer decreasing, but that's not how it behaves. It actually steps the LR when the loss is not below the best it has ever achieved. This causes problems if the loss spikes up during training then continues decreasing from that spike.

Here's a loss graph where this happens:
![image](https://user-images.githubusercontent.com/19550501/70337933-e01b9180-1843-11ea-976a-422172e2a739.png)

Everything after step ~250 is treated as a plateau by `ReduceLROnPlateau` because it's not below the lowest point, despite the fact that it's clearly trending down and not a plateau in the conventional sense of the word. In this example, this stalls the training because the LR is repeatedly decimated and it never gets a chance to get back below the lowest point. With the scheduler disabled, it keeps decreasing rapidly and quickly gets below the previous lowest point with no further spikes.

The documentation states:
> Reduce learning rate when a metric has stopped improving. Models often benefit from reducing the learning rate by a factor of 2-10 once learning stagnates. This scheduler reads a metrics quantity and if no improvement is seen for a ‘patience’ number of epochs, the learning rate is reduced.

I don't think the behaviour and the description match. The loss is clearly improving at the point when the LR is being reduced.

I'd like the plateau detection to be more sensible about not triggering when there's a downward trend. That's tricky, because a cycle of spike, gentle decrease, spike, gentle decrease should be detected as a plateau, but a one off case shouldn't. Perhaps one way to approach this would be to give `best` a maximum age, so that it's only ever looking at the most recent `n` steps. I wonder if `patience` would be a good default value of `n`?

cc @vincentqb
Repository: flutter
Issue: Focus can be stolen from the current ModalRoute
Labels: framework,f: routes,f: focus,has reproducible steps,P2,found in release: 3.0,found in release: 3.1,team-framework,triaged-framework

This involves dialogs or any modal routes that maintain their state. If an event happens and they spawn an auto-focusing FocusNode, the route will steal focus from the rest of the application, sometimes even invisibly.

Example app:
```dart
import 'dart:async';

import 'package:flutter/foundation.dart';
import 'package:flutter/material.dart';

void main() {
  // If testing on desktop:
  debugDefaultTargetPlatformOverride = TargetPlatform.fuchsia;
  runApp(MaterialApp(
    home: HomePage(),
  ));
}

class HomePage extends StatefulWidget {
  @override
  _HomePageState createState() => _HomePageState();
}

class _HomePageState extends State<HomePage> {
  Timer _timer;

  void _stealSoon() {
    setState(() {
      _timer = Timer(Duration(seconds: 5), () {
        setState(() {});
      });
    });
  }

  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Padding(
        padding: const EdgeInsets.all(24.0),
        child: SizedBox(
          width: double.infinity,
          child: Column(
            children: <Widget>[

              RaisedButton(
                child: Text('Open dialog'),
                onPressed: () {
                  showDialog(
                    context: context,
                    child: AlertDialog(
                      title: Text('Hi!'),
                      actions: <Widget>[
                        FlatButton(
                          autofocus: true,
                          child: Text('OK'),
                          onPressed: () {
                            Navigator.of(context).pop();
                          },
                        ),
                      ],
                    ),
                  );
                },
              ),
              RaisedButton(
                child: Text('Steal focus soon'),
                onPressed: _timer == null ? _stealSoon : null,
              ),
              if (_timer != null && !_timer.isActive)
                TextField(
                  autofocus: true,
                ),
            ],
          ),
        ),
      ),
    );
  }
}
```

Clicking "Steal focus soon" and then "Open dialog" will show this issue. The topmost modal route should be the only thing that can request and maintain focus.

This can happen in an actual application. e.g. a dialog shows up, and the route below goes to a username+password login page because credentials expired. If the username field has autofocus, this will steal focus from the dialog. Worse, this can happen with an opaque route if another opaque route is on top of it, assuming the previous route has maintainState set.

cc @gspencergoog
Repository: flutter
Issue: Text and icons do not render correctly in CanvasKit on older Android devices
Labels: c: regression,framework,dependency: skia,a: typography,platform-web,e: OS-version specific,e: web_canvaskit,has reproducible steps,P2,found in release: 3.3,found in release: 3.4,team-web,triaged-web

On older Android devices, with the latest Chrome browser installed, text and icons either do not render correctly, or not at all, when built with CanvasKit support:

Consider the test web app at http://mjohnsullivan.github.io/flutter_web_test

On a Pixel 2, it renders correctly:

![Screenshot_20191206-095242](https://user-images.githubusercontent.com/102488/70344462-aaa88100-180e-11ea-8d1b-8d1b67e7dc8f.png)

On a Nexus 6, the text and icons do not render:

![Screenshot_20191206-095306](https://user-images.githubusercontent.com/102488/70344490-b7c57000-180e-11ea-8184-fdd29aabb682.png)

Here's the details on the Nexus 6:

Device: Nexus 6
OS: Android 7.1.1
Chrome version: 78.0.3904.108
Flutter: Channel master, v1.12.17-pre.80, on Mac OS X 10.14.6 18G1012, locale en-US
Repository: create-react-app
Issue: no-unused-expressions warning for optional chaining
Labels: tag: underlying tools,issue: bug report

<!--
    Please note that your issue will be fixed much faster if you spend about
    half an hour preparing it, including the exact reproduction steps and a demo.

    If you're in a hurry or don't feel confident, it's fine to report bugs with
    less details, but this makes it less likely they'll get fixed soon.

    In either case, please use this template and fill in as many fields below as you can.

    Note that we don't provide help for webpack questions after ejecting.
    You can find webpack docs at https://webpack.js.org/.
-->

### Describe the bug

I just upgrade `react-scripts` to 3.3.0. I am able to use nullish coalescing, but when I attempt to use optional chaining, I can't compile as I get this error: 
```
./src/components/Select/Select.tsx
  Line 141:5:  Expected an assignment or function call and instead saw an expression  no-unused-expressions

Search for the keywords to learn more about each error.
```

The line in question is:
```ts
    this.props.onChange?.(resultingValue);
```

### Did you try recovering your dependencies?

No, I don't have time at the moment. If this might help I'll try it.

### Which terms did you search for in User Guide?

I searched for optional chaining, no-unused-expressions, eslint optional chaining.

### Environment
```
npx: installed 91 in 30.467s

Environment Info:

  System:
    OS: Windows 10 10.0.17134
    CPU: (8) x64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
  Binaries:
    Node: 12.2.0 - C:\Program Files\nodejs\node.EXE
    Yarn: Not Found
    npm: 6.9.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: 42.17134.1098.0
    Internet Explorer: 11.0.17134.1
  npmPackages:
    react: ^16.12.0 => 16.12.0
    react-dom: ^16.12.0 => 16.12.0
    react-scripts: 3.3.0 => 3.3.0
  npmGlobalPackages:
    create-react-app: Not Found
```
### Steps to reproduce

1. Use optional chaining.
2. Attempt to run `npm start`.

### Expected behavior

I expected the app to compile and for the code to function like:
```
    this.props.onChange !== undefined && this.props.onChange(resultingValue);
```

### Actual behavior

The app failed to compile and gave the above message.
Repository: PowerToys
Issue: [PowerRename] Allow Copy instead of Rename
Labels: Idea-Enhancement,Help Wanted,Product-PowerRename

In PowerRename, how about add a checkbox option to "Copy file instead of renaming"

Without the option being checked, the file is renamed:
file.txt is renamed to SomethingElse.txt and file.txt no longer exists

With the option checked, the file is copied:
file.txt is copied to SomethingElse.txt and and file.txt still exists.

Every other aspect of PowerRename works in the same exact manner.
Repository: rust
Issue: [rustc_codegen_ssa] Let function calls and definitions use OperandValue or custom enum instead of Bx::Value
Labels: C-enhancement,A-codegen,T-compiler,A-cranelift

>> For example `Bx::Value` is assumed to be able to contain a pair
>
> I know this is offtopic but I just wanted to note that pair creation is intentionally funnelled through methods with "immediate_or_packed_pair" in their name, and they're limited to function inputs/outputs, for both calls and definitions (including e.g returns).
The solution there is to have an enum (or reuse `OperandValue`) which is used for e.g. `call`, `invoke`, `ret` and function params, but nothing else.

_Originally posted by @eddyb in https://github.com/rust-lang/rust/pull/65881#issuecomment-562678719_

This is necessary to use cg_ssa with backends which can't represent pairs in `Bx::Value`.
Repository: vscode
Issue: [scss] references for all SASS functions/at-rules
Labels: feature-request,css-less-scss

Ref: https://github.com/microsoft/vscode/issues/85981
Related: https://github.com/microsoft/vscode/issues/86187

I want to link all of them to official sass documentation.
Make this data loaded from a JSON file and add `references` to all of them, so they show up in completion. With #86187 references would show up in hover as well.