sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: vscode
Issue: Allow disabling of breadcrumbs on a per language basis
Labels: feature-request,polish,breadcrumbs

I want to do this:

```json
  "[markdown]": {
    "breadcrumbs.enabled": false
  }
```
Repository: rust
Issue: 1.27.1 many tests fail on s390x
Labels: C-bug,O-SystemZ

See https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=s390x&ver=1.27.1%2Bdfsg1-1%7Eexp1&stamp=1531882985&raw=0 at the bottom.

You can ignore the stdsimd/coresimd failures they were fixed as part of https://github.com/rust-lang-nursery/stdsimd/pull/466 but I have no clue what the other failures are.
Repository: TypeScript
Issue: Formatter should convert object literal to multiple lines / one line
Labels: Suggestion,Help Wanted,Domain: Formatter

**TypeScript Version:**  3.1.0-dev.20180717

**Code**

```ts
const o = { a: 0, b: 1, c: 2 };
```

**Expected behavior:**

A refactor exists to convert to:
```ts
const o = {
    a: 0,
    b: 1,
    c: 2,
};
```
and back.

**Actual behavior:**

No such refactor. I have to do a lot of manual editing of whitespace.
Repository: rust
Issue: 1.27.1 powerpc64/powerpc64le ui/target-feature-{gate,wrong} failing
Labels: O-PowerPC,C-bug

- Debian log https://buildd.debian.org/status/fetch.php?pkg=rustc&arch=ppc64el&ver=1.27.1%2Bdfsg1-1%7Eexp1&stamp=1531883902&raw=0
- Fedora log https://kojipkgs.fedoraproject.org//packages/rust/1.27.1/3.fc29/data/logs/ppc64le/build.log

Since the files already have `// ignore-arm` for now I will go ahead and add `// ignore-powerpc64{,le}` to the Debian patches.

However `target-feature-gate.rs` also has `gate-test-powerpc_target_feature` so I wonder if `ignore-powerpc64` is the best approach.
Repository: go
Issue: x/mobile: support vendored asset package on Android
Labels: OS-Android,mobile

Please answer these questions before submitting your issue. Thanks!


### What version of Go are you using (`go version`)?
go version devel +2acae87416 Mon Jul 9 23:04:30 2018 +0000 windows/amd64

go/mobile version is also latest from master

### Does this issue reproduce with the latest release?
This is on latest master/built from source (to resolve other gomobile problem).

### What operating system and processor architecture are you using (`go env`)?
This may be the same as https://github.com/golang/go/issues/25255

Note my build environment is windows; i have reproduced the problem using a linux
build environment; target environment is android

go env
set GOARCH=amd64
set GOBIN=
set GOCACHE=C:\Users\db\AppData\Local\go-build
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=d:\dev\go
set GOPROXY=
set GORACE=
set GOROOT=c:\devtools\go1.11.devel
set GOTMPDIR=
set GOTOOLDIR=c:\devtools\go1.11.devel\pkg\tool\windows_amd64
set GCCGO=gccgo
set CC=gcc
set CXX=g++
set CGO_ENABLED=1
set CGO_CFLAGS=-g -O2
set CGO_CPPFLAGS=
set CGO_CXXFLAGS=-g -O2
set CGO_FFLAGS=-g -O2
set CGO_LDFLAGS=-g -O2
set PKG_CONFIG=pkg-config
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\db\AppData\Local\Temp\go-build567116882=/tmp/go-build -gno-record-gcc-switches
set VGOMODROOT=

### What did you do?

I have an android app that creates a service.  The service is built linking to a library
created with `gomobile bind`

### What did you expect to see?
Everything works

### What did you see instead?
When the service starts, it immediately crashes with 
I/GoLog   (18112): asset: no current JVM
I/Zygote  (  195): Process 18112 exited cleanly (1)

The first thing the service does is attempt to load an asset (which is present in the .apk)
Repository: flutter
Issue: NetworkImageWithRetry should support HTTP headers for parity with NetworkImage
Labels: c: new feature,framework,package,team-ecosystem,P2,triaged-ecosystem

Just like the "usual" `NetworkImage` does. In my case I need to add an `Authorization` header and I think this is not unlikely.
Repository: vue
Issue: Error thrown when using transition-group with conditionally rendered children
Labels: transition

### Version
2.5.16

### Reproduction link
[https://codepen.io/riophae/pen/EpgWdZ](https://codepen.io/riophae/pen/EpgWdZ)

### Steps to reproduce
1. Open the pen and it shows 1, 3, 5
2. Click the button

### What is expected?
It should show 3, 5

### What is actually happening?
Got this error in console:

```
[Vue warn]: Error in render: "TypeError: c$1.elm.getBoundingClientRect is not a function"

found in

---> <TransitionGroup>
       <Root>

TypeError: c$1.elm.getBoundingClientRect is not a function
   at Proxy.render (VM643 vue.js:8383)
   at VueComponent.Vue._render (VM643 vue.js:4535)
   at VueComponent.updateComponent (VM643 vue.js:2788)
   at Watcher.get (VM643 vue.js:3140)
   at Watcher.run (VM643 vue.js:3217)
   at flushSchedulerQueue (VM643 vue.js:2981)
   at Array.<anonymous> (VM643 vue.js:1839)
   at MessagePort.flushCallbacks (VM643 vue.js:1760)
```

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: pytorch
Issue: [feature request] Rename `Subset` -> `Resample` to reflect wider use
Labels: todo,module: dataloader,triaged

Very minor but I believe `torch.utils.data.dataset.Subset` might better be named `Resample` (or something similar), since it's possible to use for oversampling via duplicated indices.  This is a common use case for e.g. imbalanced data, and I had actually made my own before realizing that `Subset` was exactly the same indices-array method I implemented.

The switch would make it clear (a) that it can be used like this, and (b) that it *is* being used like this, so that it doesn't get broken in some future update.

Thanks.

cc @SsnL @VitalyFedyunin @ejguan
Repository: pytorch
Issue: Incorrect term in _LRScheduler.
Labels: todo,module: optimizer,triaged

So, _LRScheduler use 'epoch' (last_epoch etc.) as a term which describe step of learning rate. But epoch is an artifical term, more commonly we operate in terms of steps. And I think that rename of 'last_epoch' to 'last_step' will be more correct.

cc @vincentqb
Repository: go
Issue: x/image/tiff: implement a generic tiff parser
Labels: NeedsInvestigation,FeatureRequest

Hi,

I am currently working on a project handling tiff based content (proprietary raw from Canon and Nikon, as well as Exif).

There is a library handling my needs regarding [Exif](https://github.com/rwcarlsen/goexif) but this one re-implements the [tiff parser](https://github.com/rwcarlsen/goexif/blob/go1/tiff/tiff.go) in order to access fields.

I am wondering it could not be interesting to expose a tiff parser in the `x/image/tiff` package that developers could use to handle content in a TIFF container.

Happy to help if you think this is an interesting idea.
Repository: vscode
Issue: Rectangle commands for large file editing
Labels: feature-request,editor-multicursor

### Problem
It is difficult to modify large files (more than 10k lines) efficiently, as we are limited in cursors, as showed in the following gif.

![Cursor](https://i.imgur.com/fc78CRp.gif)

While i do understand the possible problem to have more than 10k active cursors at the same time, i still think it would be nice to be able to edit large file.

### Solution and request 
I think emacs has a interesting solution for file editing without using multiple cursors: the [rectangle commands](https://www.gnu.org/software/emacs/manual/html_node/emacs/Rectangles.html).
Maybe using this "marking" solution could enable vscode to modify larger file.
Thanks.
Repository: flutter
Issue: Update flutter_test documentation to highlight gotchas of inherent fake async usage
Labels: team,tool,d: api docs,P3,team-tool,triaged-tool

Not sure if this is expected but I just noticed that calling any async method from `dart:io`, for instance `File.exists()` does not work when executed in tests. However `File.existsSync()` still works.

To reproduce simply `flutter create` a new project and modify existing test to include something like this:

```dart
    final dir = Directory.systemTemp;
    final res = await dir.exists();
    print(res);
```

The test will fail with timeout.

```
$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v0.5.8-pre.62, on Mac OS X 10.13.5 17F77, locale en-BY)
[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 9.4.1)
[✓] Android Studio (version 3.1)
[✓] IntelliJ IDEA Community Edition (version 2018.1.6)
[!] VS Code (version 1.24.1)
[!] Connected devices
    ! No devices available

! Doctor found issues in 2 categories.
```
Repository: pytorch
Issue: [feature request] More options for Fractional Max Pooling
Labels: triaged,module: pooling

Two things from the Fractional Max Pooling paper (https://arxiv.org/pdf/1412.6071.pdf) are not currently implemented: 
- what is called random increments in the paper (in contrast with what is called pseudorandom increments, which seems to be the only possible kind of increments in the current implementation);
- what is called disjoint regions in the paper (in contrast with overlapping regions, which seems to be the only possible kind of regions in the current implementation).

Thanks
Repository: TypeScript
Issue: Bring back typedef property expansion
Labels: Suggestion,In Discussion

_From @zavr-1 on July 18, 2018 20:25_

In the newer version, I can only see the type of an argument which is an object, compared to how it was expanded in the previous versions.

![test3](https://user-images.githubusercontent.com/21156791/42904849-3f94249c-8ace-11e8-91bb-8a09063e9d30.png)

It was actually very useful to see all properties on hover which served as a documentation. 

![test4](https://user-images.githubusercontent.com/21156791/42905747-d387673e-8ad0-11e8-92c8-ddf31e9d7f92.png)

I think if you hide the details of the type, you should also provide means to expand its properties via a UI, or provide a setting for it. 

_Copied from original issue: Microsoft/vscode#54609_
Repository: go
Issue: cmd/go: get downgrade of excluded last version fails
Labels: NeedsDecision,modules

Bryan points out that this fails because the go.mod is inconsistent:

	go get rsc.io/sampler@<v1.99
	
	-- go.mod --
	module x
	require rsc.io/sampler@v1.99.99
	exclude rsc.io/sampler@v1.99.99

It's unclear how to make it succeed, and it's fine for most other commands like go build etc to fail, but running that go get is an obvious way to attempt to dig out of that hole and it doesn't work.

It would be nice to do something here, but it's not entirely clear what.

From https://go-review.googlesource.com/c/vgo/+/122396/6#302.
Repository: rust
Issue: rustdoc discussion: collapsing sections by default
Labels: T-rustdoc,C-discussion,A-rustdoc-ui

IIUC, Rustdoc collapses all trait impls and the type declaration (cc https://github.com/rust-lang/rust/pull/49412) by default. But leaves other sections expanded.

This seems good in many cases, but in others. We might want to adjust exactly how things are collapsed.

Some thoughts:

* When collapsing the type decl, it would be nice to still see a minimal part of the signature, e.g., for [Iterator](https://doc.rust-lang.org/std/iter/trait.Iterator.html) there is good reason to not show all the methods, but it would be nice to show `pub trait Iterator { ... }` and maybe the `Item` assoc type. I realise all the information is there on the page, but it just looks incomplete without something there.
* It is often useful to have type decl as a 'contents' page for the docs, especially if the intro text is very long. OTOH, it might be nice to actually have a contents (e.g., just the names of fields/methods) so that impl methods are included.
* For trait impls, it would be nice to include the signatures of methods, but not the text descriptions (i.e., the trait impl is expanded, but each method is collapsed). The reasoning here is that often wants to know the names or signatures of methods in an impl, but not the descriptions (where I agree with the reasoning that it is not the most useful).
* For traits, it would be good to further collapse the list of impls, see for example [IntoIterator](https://doc.rust-lang.org/std/iter/trait.IntoIterator.html#implementors), it might be nice to have just a list of the types (rather than the signatures) with a click through to see the sig, or to keep the current style but collapse the whole list by default.
Repository: rust
Issue: SystemTime conversions invite programmer error
Labels: C-enhancement,T-libs-api,A-docs

Yesterday, I found and reported a [panic bug in `serde_json`](https://github.com/serde-rs/json/issues/464) which traces its origins to the mechanism for extracting usable information from `SystemTime`.

Specifically, using the best method they believed to be available, it would panic when I tried to serialize metadata for files with negative `mtime` values. (I have one file with an mtime of `-1` and another with an mtime so far in the future that it overflows into a large negative number if the Rust code is compiled for the `i686-unknown-linux-musl` target.

The current design of the API encourages users to assume that sources of `SystemTime` values use unsigned values internally (ie. that modifications to the system clock are the only source of `Err` with valid input), and, further more, in the bug I reported for `serde_json`, it led @lambda to the incorrect conclusion that there is currently no way to losslessly serialize and deserialize `SystemTime` values.

If nothing else, the documentation should be improved in the following ways:

1. The documentation for both `UNIX_EPOCH` definitions should explicitly mention that the underlying OS may return valid `SystemTime` values prior to the epoch and code should be prepared for such an eventuality. (Perhaps with the concrete example of `ext3` filesystems allowing negative `mtime` values to be stored)

2. The documentation for `SystemTime::duration_since` should use "may return `SystemTimeError`" rather than "may fail" to avoid the connotation that an `Err` result is erroneous in any sense other than being an "until" rather than a "since".

    That is, "failure" connotes a response that should prompt either retry or error-propagation, while it is not necessary to re-run the operation with the arguments reversed in order to extract the `Duration` and, depending on the input, nothing may be wrong at all. (ie. the `Result` discriminant is semantically equivalent to a sign bit in this case.)

3. "and the error contains how far from self the time is" is too easy to overlook, given how important it is for robust software to handle this eventuality. It should explicitly mention `SystemTimeError::duration` to make it more eye-catching.

    Perhaps "Returns an Err if `earlier` is later than `self`. A `Duration` representing how far `self` is before `earlier` can be retrieved via the `duration()` function on the resulting `SystemTimeError`.

There are probably other ways to better tune the writing to guard against human error, but I don't want to be here all night trying to perfect this when you might think of the same improvements immediately, simply by virtue of having a different perspective.
Repository: godot
Issue: GodotSharp(?): detect if Solution is a C# or C++ project first before attempting to build it
Labels: enhancement,topic:dotnet

**Godot version:** 3.0.5 stable mono win64

**Issue description:** GodotSharp will blindly try to build an .sln, obviously failing when it's a C++ solution. Had to drag the .sln out of the folder in order to run the project.

Not an urgent issue at all, as I can just download the non-mono release of Godot and use that instead, but its nice to have :P

Maybe parsing the .sln, and skip building if it has vcxproj(s) in it?

**Steps to reproduce:** Build a project with a Visual Studio C++ solution inside.
Repository: vscode
Issue: [folding] Add keyboard shortcut to jump between #region and #endregion
Labels: feature-request,editor-folding

How difficult would it be to add a keyboard shortcut to jump between `#region` and `#endregion`, the same way you can jump between opening and closing brackets `[]`, braces `{}`, and parentheses `()`? I would prefer the same keyboard shortcut, so just adding this to `editor.action.jumpToBracket` would be perfect. However, I can imagine that some might prefer it to be a separate command, or it may be better to do that from an implementation standpoint.

I apologize if I'm missing an existing shortcut, but I couldn't find anything in the current keybindings.
Repository: vscode
Issue: [scss] Add "Go to or peek defintion" for imported mixins and variables for SCSS files
Labels: feature-request,css-less-scss

Has this been discussed before? 
I couldn't find an issue, but I can't imagine other people not needing this.
Repository: go
Issue: testing: examples with trailing whitespace in multiple lines of output can be confusing
Labels: NeedsInvestigation

Below example fails. Even if I copy the output of `go test` to the output section, it still fails.
```
func ExampleTrailingSpace() {
	fmt.Println("abc ")
	fmt.Println("cde")
	// Output:
	//abc
	//cde
}
```

However, if I remove the second print, it succeeds.
```
func ExampleTrailingSpace() {
	fmt.Println("abc ")
	// Output:
	//abc
}
```

Why? Because `testing/example.go` trims leading and trailing spaces of the whole output, but not every line. Code formatting tools, including `gofmt`, trims the space of each comment line.

I suggest trimming each line before comparing the output.
Repository: opencv
Issue: isContinuous() fails for large images in OpenCV
Labels: category: core,RFC

<!--
If you have a question rather than reporting a bug please go to http://answers.opencv.org where you get much faster responses.
If you need further assistance please read [How To Contribute](https://github.com/opencv/opencv/wiki/How_to_contribute).

This is a template helping you to create an issue which can be processed as quickly as possible. This is the bug reporting section for the OpenCV library.
-->

##### System information (version)
<!-- Example
- OpenCV => 3.1
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2015
-->

- OpenCV => 3.4.2
- Operating System / Platform => Ubuntu 18.04
- Compiler => gcc 8

##### Detailed description

Hi, I have the following in OpenCV 3.4.2

    cv::Mat3b a(cv::Size(30511, 26060)); 
    cout << a.isContinuous() << endl;
    cv::Mat3b b = a.clone();
    cout << b.isContinuous() << endl;


and the result is 0 (false) in both cases, which I think is not correct. At least for `cv::Mat3b b` the docs say "The original step[] is not taken into account. So, the array copy is a continuous array occupying total()*elemSize() bytes.".
Repository: go
Issue: cmd/link: short tests are not short enough
Labels: Testing,NeedsInvestigation,compiler/runtime

Running all.bash (which does go test -short std cmd), my target is usually that individual tests should run in under 1 second.
	
The cmd/link test takes 3.4s on my system. Can we make it take less time?

cmd/link is implicitly tested by pretty much every other test in the system, so it's hard to believe it needs to do a ton in the -short test.

/cc @aclements
Repository: go
Issue: build: all.bash takes too long
Labels: Testing,help wanted,NeedsFix

My target for all.bash is to keep it around 3-4 minutes. Usually when it gets to 5 minutes I spend some time trimming it back down. Maybe 3-4 minutes is no longer attainable, but right now we're at 7 minutes, which is much longer than I'd hope.

I filed a few bugs to try to help: #26469, #26472, #26470, #26471.

Speeding all.bash may also help speed the trybots, which also take longer than I'd hope.
Repository: go
Issue: cmd/go: module update should drop unused indirect dependencies?
Labels: NeedsInvestigation,modules

### What version of Go are you using (`go version`)?
Latest go devel: `go version devel +d278f09333 Thu Jul 19 05:40:37 2018 +0000 darwin/amd64`

### Does this issue reproduce with the latest release?
Yes

### What operating system and processor architecture are you using (`go env`)?
```
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/ikorolev/Library/Caches/go-build"
GOEXE=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOOS="darwin"
GOPATH="/Users/ikorolev/.gvm/pkgsets/go1.11beta1/global:/Users/ikorolev/dev/go"
GOPROXY=""
GORACE=""
GOROOT="/Users/ikorolev/.gvm/gos/go1.11beta1"
GOTMPDIR=""
GOTOOLDIR="/Users/ikorolev/.gvm/gos/go1.11beta1/pkg/tool/darwin_amd64"
GCCGO="gccgo"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -fno-caret-diagnostics -Qunused-arguments -fmessage-length=0 -fdebug-prefix-map=/var/folders/_b/d1934m9s587_8t_6ngv3hnc00000gp/T/go-build301560759=/tmp/go-build -gno-record-gcc-switches -fno-common"
```

### What did you do?

Sorry, can't give you a standalone reproduction - bug is produced only with downloading updated dependencies.

Consider the following flow:

A(v0.0.1) uses B(v0.0.1):
```
module github.com/mwf/vgo-modules/a

require github.com/mwf/vgo-modules/b v0.0.1
```

Then A(v0.1.0) drops the dependency.

Here we got a project `main` which uses A(v0.0.1) and we want to upgrade A to v0.1.0

```
cd `mktemp -d`
git clone https://github.com/mwf/vgo-modules .
echo "\n$(cat go.mod)"
echo "\n$(cat go.sum)"
go get github.com/mwf/vgo-modules/a@v0.1.0
echo "\n$(cat go.mod)"
```

We get an unexpected indirect dependency `github.com/mwf/vgo-modules/b v0.0.1 // indirect` in `go.mod`, it seems to be taken from go.sum as a side-effect.


### What did you expect to see?
`go.mod` should contain updated `a` dependency
```
module github.com/mwf/vgo-modules

require github.com/mwf/vgo-modules/a v0.1.0
```

### What did you see instead?

We get an unexpected indirect dependency from `b` in `go.mod`, it seems to be taken from `go.sum` as a side-effect.

```
module github.com/mwf/vgo-modules

require (
    github.com/mwf/vgo-modules/a v0.1.0
    github.com/mwf/vgo-modules/b v0.0.1 // indirect
)
```
Repository: rust
Issue: Set up CI for local rebuilds using the actual rustc-src tarball
Labels: T-infra,C-feature-request

By that I mean the whole end-to-end process of `./x.py {build,test,install}` and then using this installed version to build itself again.

Would help to prevent things like #52541, this has happened quite a few times now.
Repository: flutter
Issue: [image_picker plugin] FEATURE REQUEST: get most recent image/video
Labels: c: new feature,p: image_picker,package,c: proposal,team-ecosystem,P3,has partial patch,triaged-ecosystem

I'm working on an app that accesses the user's image/video gallery. I want the button that opens the image picker to be a thumbnail of the most recent image/video in the user's gallery. It would be great if I could get this from the image_picker package directly!