sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: current_exe() returns invalid path on linux when exe has been deleted
Labels: O-linux,T-libs-api,C-bug

Calling `current_exe()` on linux after the original executable has been deleted or replaced results in an invalid path being returned.

```rust
fn main() {
    // current_exe = /path/to/executable
    remove_file(current_exe().unwrap()).ok();
    println!("{:?}", current_exe());
}
```

### Output
`Ok("/path/to/executable (deleted)")`

### Desired behavior
While it is the correct behavior of the underlying `/proc/self/exe` to append the string ` (deleted)` to the original pathname the result is not a valid path and might even end up pointing to a completely different file.

I would either expect the docs to explicitly mention this behavior or classify it as an error and return `io::ErrorKind::NotFound` accordingly.

### Meta
<!--
If you're using the stable version of the compiler, you should also check if the
bug also exists in the beta or nightly versions.
-->

`rustc --version --verbose`:
```
rustc 1.41.0 (5e1a79984 2020-01-27)
binary: rustc
commit-hash: 5e1a799842ba6ed4a57e91f7ab9435947482f7d8
commit-date: 2020-01-27
host: x86_64-unknown-linux-gnu
release: 1.41.0
LLVM version: 9.0
```

I would gladly claim this issue if you agree to it.
Repository: godot
Issue: When an external editor is configured, script opens in the Godot script editor when double-clicking an error line
Labels: bug,topic:editor,confirmed,usability

**Godot version:**
3.2 stable mono

**OS/device including version:**
win10 64

**Issue description:**
When you double click on an error report that indicates the script file, the script opens in the Godot editor creating inconsistencies in the scene execution.
I have everything configured correctly, I use VSCode.
![GIF](https://user-images.githubusercontent.com/19652075/75022875-2671ab80-5497-11ea-8acc-d99a1b0b9064.gif)

**Steps to reproduce:**
1 - Cause an error like the one in the image.
2 - Double click on the line that informs the file that contains the script.
3 - Run the scene.
4 - A window will open automatically indicating something that does not apply, in the GIF casually did not appear.
5 - Note that the script was opened in the Godot code editor.

**Minimal reproduction project:**
[testPosicion.zip](https://github.com/godotengine/godot/files/4235326/testPosicion.zip)
Repository: PowerToys
Issue: Add option to turn ON/OFF Virtual Desktop zoneset inheritance from parent
Labels: Idea-Enhancement,FancyZones-Settings,Product-FancyZones,Cost-Small,FancyZones-VirtualDesktop

When a new Virtual Desktop is created, FancyZones applies to it the same zoneset of the parent desktop.
This behavior may not be ideal for some users.
We should consider adding an option to turn ON/OFF this feature.
Repository: opencv
Issue: dnn: mixed-precision inference and quantization
Labels: RFC,category: dnn

##### System information (version)
- OpenCV => 4.2.0

##### Detailed description

The CUDA backend can support mixed-precision inference with various types: FP32, FP16, INT32, (U)INT8 and possibly INT4 and INT1. It's fairly easy to implement as cuDNN already has convolution primitives for many of these types and the existing CUDA backend codebase is fully template-based.

Before this can be implemented, some issues need to be sorted out:
1. Is it required?
2. APIs to configure mixed-precision
    - APIs to allow the user to control the mixed-precision configuration
    - ability to import quantized models and use the quantized weights during inference

Other ideas:
1. Default Mixed-precision policies
    - example: fp16 for convolutions and fp32 for the rest?
2. Automatic Mixed-Precision
    - the user provides a representative dataset and the AMP system automatically figures out a good configuration
      - a similar thing would be required to implement in-house quantization

IE supports mixed-precision inference. A generic `cv::dnn` API for mixed-precision could be used for all the backends that support it.
Repository: flutter
Issue: Missing grid layout in flutter
Labels: c: new feature,framework,P3,team-framework,triaged-framework

Flutter needs grid layout similar or same to CSS grid. In most cases we probably will not need to use this layout but if you need it then replacing it with Rows and Columns is just crazy. I found a package **flutter_layout_grid** but I honestly think that this should comes with flutter especially in web development
Repository: flutter
Issue: testing very simple GridView.count fails
Labels: a: tests,framework,f: scrolling,has reproducible steps,P2,found in release: 3.3,found in release: 3.7,team-framework,triaged-framework


## Steps to Reproduce

This simple test fails
```dart
  testWidgets('GridView.count', (tester) async {
    await tester.pumpWidget(
      MaterialApp(
        home: GridView.count(
          crossAxisCount: 1,
          children: <Widget>[
            Text('1'),
            Text('2'),
            Text('3'),
            Text('4'),
          ],
        ),
      ),
    );

    expect(find.byType(Text), findsNWidgets(4));
  });
```

the error message:

══╡ EXCEPTION CAUGHT BY FLUTTER TEST FRAMEWORK ╞════════════════════════════════════════════════════
The following TestFailure object was thrown running a test:
  Expected: exactly 4 matching nodes in the widget tree
  Actual: _WidgetTypeFinder:<exactly one widget with type "Text" (ignoring offstage widgets):
Text("1", dependencies: [MediaQuery, DefaultTextStyle])>
   Which: is not enough


Flutter doctor :
[√] Flutter (Channel master, v1.14.7-pre.103, on Microsoft Windows [Version 10.0.18362.657], locale en-US)
 
[!] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
    X Android license status unknown.
      Try re-installing or updating your Android SDK Manager.
      See https://developer.android.com/studio/#downloads or visit https://flutter.dev/setup/#android-setup for
      detailed instructions.
[√] Chrome - develop for the web
[!] Android Studio (version 3.2)
    X Flutter plugin not installed; this adds Flutter specific functionality.
    X Dart plugin not installed; this adds Dart specific functionality.
[√] VS Code (version 1.42.0)
[√] Connected device (2 available)
Repository: flutter
Issue: Flutter MethodChannel handler memory semantics are potentially confusing
Labels: engine,c: performance,d: api docs,customer: dream (g3),perf: memory,P3,team-engine,triaged-engine

https://b.corp.google.com/issues/149979662.

cc @chinmaygarde
Repository: flutter
Issue: AnimatedIcon more_vert to arrow_back
Labels: c: new feature,framework,f: material design,a: fidelity,P3,team-text-input,triaged-text-input

The text selection overflow menu in native Android animates the icon transition between the 3 dot more_vert icon and arrow_back, so Flutter should do this too!  However, it seems that [AnimatedIcons](https://master-api.flutter.dev/flutter/material/AnimatedIcons-class.html) doesn't support this transition.  We should add it.

This is what native Android looks like:

<img width="250" src="https://user-images.githubusercontent.com/389558/62390332-dccf6c80-b516-11e9-80cb-22bb924ab070.gif" />

I noticed this when implementing the overflow menu in https://github.com/flutter/flutter/pull/49391.
Repository: rust
Issue: Occasional non-reproducibility when building rustc
Labels: T-compiler,C-bug,A-reproducibility

Over the past few days I have occasionally seen my builds of rustc be non-reproducible.  The differences most often seem to be in stage 1's libparking_log, librustc_parse, or librustc_driver.

A git bisect suggests that this was caused by 138c50f0af57e2631aa09092b826e2c3efd224d2, although due to the fact that this issue is itself difficult to reproduce this could potentially be incorrect.  But after many builds with and without that patch, I have only seen the error with it.  Assuming that is correct, I believe this issue might well be due to non-determinism in LLVM's `-O3`, but I'm not sure how to run just the LLVM portion on the compile so I'm not sure.

Note that this is a part of #34902.
Repository: TypeScript
Issue: Type completions in jsDoc @augments and @implements tags.
Labels: Needs Investigation

## Suggestion

Add code completions in jsDoc `@augments` and `@implements` clauses. 

## Use Cases
Anybody using the new `@implements` and `@augments` jsDoc tags will benefit from this. 

## Examples
Inside the `{}` triggering code completions should show types.
```ts
/**
 * @augments {}
 * @implements {}
 */
declare class B {
    b(): void;
    i(): void;
}

```

## Checklist

My suggestion meets these guidelines:

* [X] This wouldn't be a breaking change in existing TypeScript/JavaScript code
* [X] This wouldn't change the runtime behavior of existing JavaScript code
* [X] This could be implemented without emitting different JS based on the types of the expressions
* [X] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [X] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).


This is a flow-on from #36292 cc: @sandersn
Repository: flutter
Issue: Namespace collision with flutter_android_lifecycle 
Labels: platform-android,package,P3,p: flutter_plugin_android_lifecycle,team-android,triaged-android

**This is the counter-issue I'm opening for the issue I have opened in the other repository: https://github.com/blackmenthor/flutter-android-lifecycle-plugin/issues/6 . I'm doing this to facilitate communication for both packages, if necessary.**

This is very unfortunate and I don't have a good solution for this. Personally, I'll be forking the other repository for a while and change the name until this has been "officially" resolved.

After updating the `image_picker` dependency (https://pub.dev/packages/image_picker), I am now getting this error:

```
...\app-name\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java:17: error: a type with the same simple name is already defined by the single-type-import of FlutterAndroidLifecyclePlugin
import io.flutter.plugins.flutter_plugin_android_lifecycle.FlutterAndroidLifecyclePlugin;
```

(Because of this change in `image_picker`: https://github.com/flutter/plugins/commit/35957436b517793fa4cb568a3af6a1f054c7bdbb#diff-94aec143fa15896e4c8aca6854f7ecd7R19)

`...\app-name\android\app\src\main\java\io\flutter\plugins\GeneratedPluginRegistrant.java` looks like this:

```java
/**
 * Generated file. Do not edit.
 */
public final class GeneratedPluginRegistrant {
  public static void registerWith(PluginRegistry registry) {
    if (alreadyRegisteredWith(registry)) {
      return;
    }
    FlutterAndroidLifecyclePlugin.registerWith(registry.registrarFor("com.anggach.flutterandroidlifecycle.FlutterAndroidLifecyclePlugin"));
    FlutterAndroidLifecyclePlugin.registerWith(registry.registrarFor("io.flutter.plugins.flutter_plugin_android_lifecycle.FlutterAndroidLifecyclePlugin"));

...
  }

...
```

This package is the package with the competing namespace: https://pub.dev/packages/flutter_android_lifecycle

Again, this is super unfortunate because either you have to change the namespace of this package, or communicate with the maintainers of the other package to change it on their end.
Repository: rust
Issue: Possibly incorrect syntax `Enum::<Type, Params>::Variant` allowed since 1.33
Labels: A-type-system,P-medium,T-compiler,regression-from-stable-to-stable,C-bug,T-types

A coworker recently identified the following case:

```rust
pub enum Foo<'a, T> {
    Struct {},
    Tuple(),
    Unit,
    Usage(&'a T),
}
pub fn main() {
    let foo = Foo::<String>::Unit;
    let foo = Foo::<String>::Tuple();
    let foo = Foo::<String>::Struct {};
}
```

[This used to fail because of the lack of implicit bound `T: 'a`](https://godbolt.org/z/-zUiCa):
```
error[E0309]: the parameter type `T` may not live long enough
 --> <source>:5:11
  |
1 | pub enum Foo<'a, T> {
  |                  - help: consider adding an explicit lifetime bound `T: 'a`...
...
5 |     Usage(&'a T),
  |           ^^^^^
  |
note: ...so that the reference type `&'a T` does not outlive the data it points at
 --> <source>:5:11
  |
5 |     Usage(&'a T),
  |           ^^^^^
```

[After fixing that, it complains about the type params](https://godbolt.org/z/HwCIEP):

```
error[E0109]: type parameters are not allowed on this type
 --> <source>:8:21
  |
8 |     let foo = Foo::<String>::Unit;
  |                     ^^^^^^ type parameter not allowed

error[E0109]: type parameters are not allowed on this type
 --> <source>:9:21
  |
9 |     let foo = Foo::<String>::Tuple();
  |                     ^^^^^^ type parameter not allowed

error[E0109]: type parameters are not allowed on this type
  --> <source>:10:21
   |
10 |     let foo = Foo::<String>::Struct {};
   |                     ^^^^^^ type parameter not allowed
```

[Starting in 1.33, all but the `Struct` path are accepted](https://godbolt.org/z/EO_SBq):

```
error[E0110]: lifetime arguments are not allowed on this entity
  --> <source>:10:15
   |
10 |     let foo = Foo::<String>::Struct {};
   |               ^^^^^^^^^^^^^^^^^^^^^ lifetime argument not allowed

error[E0107]: wrong number of lifetime arguments: expected 1, found 0
  --> <source>:10:15
   |
10 |     let foo = Foo::<String>::Struct {};
   |               ^^^^^^^^^^^^^^^^^^^^^ expected 1 lifetime argument
```

[The correct code for this would of course be](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=2afe55bc512078a34ba3e37409d74902):

```rust
pub enum Foo<'a, T> {
    Struct {},
    Tuple(),
    Unit,
    Usage(&'a T),
}
pub fn main() {
    let foo = Foo::Unit::<String>;
    let foo = Foo::Tuple::<String>();
    let foo = Foo::Struct::<String> {};
}
```

My questions:

- Was this change in behavior (accepting some of these paths) intended?
- If so, was it intended to deny only _one_ of these cases?
- If this change wasn't intended, should we try to reintroduce it or grandfather it in?

Depending on the answer to those questions, the solution to this ticket could be:

- Make the compiler accept the `let foo = Foo::Struct::<String> {};` case
- Deny all cases with a suggestion pointing at the right syntax

cc @Centril
Repository: pytorch
Issue: Remove .data subset1 for fixathon
Labels: module: autograd,triaged,enhancement,better-engineering,actionable,fixathon

Even though it is not documented, many users still use it. And it leads to many bugs in user code.
So we should remove it completely to prevent this.

To do this, do one of:
1) [preferred] remove `.data`
2) [if possible] otherwise, replace with either `.detach()` or wrap in a `torch.no_grad` block
3) [otherwise] leave as is.

For 2), generally use whichever is nicer.  `torch.no_grad()` is often clearer but is extra characters and is often done on another line.  One place where you may have to use `.detach()` is in the return of a function, i.e.:
`return x.detach()` returns a tensor without a history.  but:
```
with torch.no_grad():
    return x
```
will return a tensor with history

For 3) This happens rarely, only if you explicitly don't want to share the version counter (e.g. because autograd would complain about the change but you happen to know it is okay, or the version counter is being explicitly tested).

The expected steps are:
  - [ ] `benchmarks/`
  - [ ] `docs/source/scripts/build_activation_images.py` and `docs/source/notes/extending.rst` 
  - [ ] `test/test_numba_integration.py`, `test/onnx/...`
  - [ ] `torch/testing`
  - [ ] `torch/utils/tensorboard/`


cc @ezyang @SsnL @albanD @zou3519 @gqchen
Repository: pytorch
Issue: bitmapToFloat32Tensor() 1 channel Tensor [feature] [mobile]
Labels: oncall: mobile,oncall: java

## 🚀 Feature
``bitmapToFloat32Tensor`` with 1 channel Tensor as return.

## Motivation

While trying to bring my project to android I noticed that there is only a function for RGB / 3 channel Tensors so far, which does not work for my 1 channel input ConvNet.

## Pitch

Add ``TensorImageUtils.bitmapToFloat32Tensor`` with 1 channel Tensor as return. (android)
e.g.: ``shape: [1, 1, 1280, 960]``

## Additional context

Since it is not a particularly extensive or complex feature, I have already tried it locally.
https://github.com/Unity05/pytorch/blob/master/android/pytorch_android_torchvision/src/main/java/org/pytorch/torchvision/TensorImageUtils.java
Repository: vscode
Issue: Cannot load any extensions in extensions marketplace in visual studio code on imac catalina
Labels: bug,proxy

<!-- Please read our Rules of Conduct: https://opensource.microsoft.com/codeofconduct/ -->
<!-- Please search existing issues to avoid creating duplicates. -->
<!-- Also please test using the latest insiders build to make sure your issue has not already been fixed: https://code.visualstudio.com/insiders/ -->

<!-- Use Help > Report Issue to prefill these. -->
- VSCode Version:Version: 1.42.1
Commit: c47d83b293181d9be64f27ff093689e8e7aed054
Date: 2020-02-11T14:44:27.652Z
Electron: 6.1.6
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Darwin x64 19.3.0
- OS Version: macOS Catalina 10.15.3 (19D76)

Steps to Reproduce:

1. double click or open visual studio code in either dock OR in applications folder.
2. go to extensions marketplace by clicking on the icon.

<!-- Launch with `code --disable-extensions` to check. -->
Does this issue occur when all extensions are disabled?: Yes/No
There are no extensions extant yet. This is a brand new download out of the box. 


Here's a screen recording of what happens.
[Screen Recording 2020-02-21 at 4.05.27 PM 480.mov.zip](https://github.com/microsoft/vscode/files/4238065/Screen.Recording.2020-02-21.at.4.05.27.PM.480.mov.zip)


![image](https://user-images.githubusercontent.com/1839603/75072328-5041c700-54c5-11ea-9d90-6108665b405b.png)

# Extra notes
This is a fresh install of vs code on a freshly updated mac OS system
Repository: flutter
Issue: Relax stable ordering of backing stores given to the embedder for presentation.
Labels: engine,c: performance,e: embedder,customer: dream (g3),perf: memory,P3,team-engine,triaged-engine

This will improve render target cache utilization. This optimization must be made when an internal embedder migrates to be resilient to this optimization.

Pessimization added in https://github.com/flutter/engine/pull/16711 for b/146142979.
Repository: flutter
Issue: Collect unused render targets before asking the embedder to create updated targets.
Labels: engine,c: performance,e: embedder,customer: dream (g3),perf: memory,P3,team-engine,triaged-engine

This will reduce peak memory usage. This optimization must be made when an internal embedder migrates to be resilient to this optimization.

Pessimization added in https://github.com/flutter/engine/pull/16711 for b/146142979.
Repository: go
Issue: cmd/link: -X does not work on variables with non-constant default values
Labels: NeedsInvestigation

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.14rc1 darwin/amd64
</pre>

### Does this issue reproduce with the latest release?

This is a regression in Go 1.14rc1. It does not reproduce in 1.13.8.

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/Users/jayconrod/Library/Caches/go-build"
GOENV="/Users/jayconrod/Library/Application Support/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="darwin"
GOINSECURE=""
GONOPROXY=""
GONOSUMDB=""
GOOS="darwin"
GOPATH="/Users/jayconrod/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/opt/go/installed"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/opt/go/installed/pkg/tool/darwin_amd64"
GCCGO="gccgo"
AR="ar"
CC="clang"
CXX="clang++"
CGO_ENABLED="1"
GOMOD="/Users/jayconrod/Code/test/tmp2/go.mod"
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/rq/x0692kqj6ml8cvrhcqh5bswc008xj1/T/go-build343063917=/tmp/go-build -gno-record-gcc-switches -fno-common"
</pre></details>

### What did you do?

Run the testscript below:

```
go run -ldflags='-X=example.com/test/stamp.STAMP=pass' ./main
stdout pass

-- go.mod --
module example.com/test

go 1.14
-- main/main.go --
package main

import (
	"fmt"

	"example.com/test/stamp"
)

func main() {
	fmt.Printf("STAMP = %s\n", stamp.STAMP)
}
-- stamp/stamp.go --
package stamp

var DEFAULT = "fail"
var STAMP = DEFAULT
```

### What did you expect to see?

The program should print `STAMP = pass`, and the test should pass.

### What did you see instead?

The program prints `STAMP = fail`.

This only happens when `STAMP` is assigned to another variable. The test passes if `STAMP` is assigned the value `"fail"` instead of `DEFAULT`.

### Other thoughts

I've milestoned this Go1.14 and added the Soon label because this is a regression. It should be triaged before the 1.14 release.

I don't know if this was intended to work before. If not, feel free to close.

If it was intended to work, I'm not sure whether this should block 1.14.
Repository: react
Issue: Arbitrary log lines may appear in between an error and the subsequent "The above error…" message
Labels: Type: Bug

React version: 16.12

If one component throws, and one of its siblings logs something else to the console, that sibling's logs appear in between the throwing component and the extra React information about that throw.

This is hard to explain in words but easy to explain in code and pictures, so look:

Repro: https://codesandbox.io/s/boring-firefly-bu79e

![image](https://user-images.githubusercontent.com/6820/75078940-d822d380-54bb-11ea-99d2-c77fbc0c9a5b.png)

The third log line ("The above…") refers to the first ("Uncaught…") but looks like it refers to the second ("Please don't…"). This is confusing when debugging.

Instead, I would expect "The above error…" to be right below the uncaught window-level exception we raise. (Maybe this isn't possible without diverging dev vs. prod behavior? Not sure but thought I'd file…)
Repository: go
Issue: x/build/maintner: Maintner does not detect transferred issues
Labels: Builders,NeedsInvestigation

Related to #30184.

Maintner's sync loop uses a ListIssues call sorted by update time to determine which issues it needs to re-fetch issue data and event data for. Deleted issues and transferred issues don't show up in the ListIssues response, Maintner is never aware that they're gone, and ultimately those issues are frozen in the corpus in the state they had before they were deleted/transferred. They are never marked NotExist (tombstoned). https://go-review.googlesource.com/c/build/+/161521/ is an insufficient fix for this reason.

https://go-review.googlesource.com/c/build/+/205598 proposes exposing a mutation method so an external process can inform Maintner of the deleted/transferred issues, but that requires an external process (also, see other comments on that CL).

I think a better solution would be for Maintner, during its issue sync, to pull repository events up to the GitHub poller's lastUpdated timestamp, looking specifically for issue transfer and issue delete events, and tombstoning (mark as `NotExist`) the appropriate issues before moving onto the regular issue sync.

The difficulty will be for repos that are already being synced, this doesn't provide a way to go back in time and handle previous deletes/transfers, which, the external process _would_ be capable of doing.

/cc @bradfitz @dmitshur @orthros