sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: error: undefined symbol: __chkstk in compiling UEFI application on ARM64
Labels: A-linkage,O-AArch64

Hi,

I'm creating a UEFI application on ARM64. My target .json file is as follows and it works well for a simple hello_world application.

```
{
  "llvm-target": "aarch64-pc-windows-msvc",
  "target-endian": "little",
  "target-pointer-width": "64",
  "target-c-int-width": "32",
  "os": "uefi",
  "arch": "aarch64",
  "data-layout": "e-m:e-i64:64-f80:128-n8:16:32:64-S128",
  "linker": "rust-lld",
  "linker-flavor": "lld-link",
  "pre-link-args": {
    "lld-link": [
        "/Subsystem:EFI_Application",
	"/Entry:wenqiu_entry",
	"/Machine:arm64"
    ]
  },
  "panic-strategy": "abort",
  "default-hidden-visibility": true,
  "executables": true,
  "exe-suffix": ".efi",
  "is-like-windows": true,
  "emit-debug-gdb-scripts": false,
}
```

However, when I create a static Once object 
`pub static MY_OBJECT: Once<MutexIrqSafe<MyStruct>> = Once::new();`
and initialize it with 
`MY_OBJECT.call_once(|| {MutexIrqSafe::new( myobj )  });`, 
an error occurs

` note: rust-lld: error: undefined symbol: __chkstk`

I found this link [https://github.com/rust-lang/rust/pull/56913](https://github.com/rust-lang/rust/pull/56913) and it says this error is caused by a large local variable. According to the corresponding commitment [0b00db](https://github.com/rust-lang/rust/commit/0b00dbedce3100b3c6504630896725035c12b1a7), I add

`  "stack_probes": true,`

in the target.json file, but the problem is still there. The toolchain I use is nightly-2019-01-02.

Does anyone know how to solve the problem?
Repository: pytorch
Issue: KeyError: 'No translator registered for layer: name: "res3b_relu_norm"\ntype: "Normalize"\nbottom: "res3b"\ntop: "res3b_relu_norm"\nnorm_param
Labels: caffe2

It looks like "Normalize" op is not supported in 'caffe_translator.py' when i convert my model from caffe to caffe2.right? I just call the script directly from command line:
`python -m caffe2.python.caffe_translator deploy.prototxt pretrained.caffemodel`

Will you guys add this op to 'caffe_translator.py' in near future?

My environment:
 - PyTorch Version : 1.0.0
 - OS : Linux
 - How you installed PyTorch (`conda`, `pip`, source): conda
 - Python version: python3.7.1
 - CUDA/cuDNN version: cuda-9.2 / cuDNN-7.2
 - GPU models and configuration:Titan
Repository: flutter
Issue: Additional TextOverflow variants: middle, start
Labels: c: new feature,framework,engine,a: typography,P2,team-engine,triaged-engine

need an equivalent like an android: middle, start

https://developer.android.com/reference/android/widget/TextView#attr_android:ellipsize
Repository: flutter
Issue: Wrapped Text has unexpected intrinsic size
Labels: framework,a: typography,has reproducible steps,P2,found in release: 3.7,found in release: 3.8,team-framework,triaged-framework

I'd expect wrapped Text to have an intrinsic size that fits the text. However, if I wrap such a text with an `IntrinsicHeight` widget, the height includes the first line, only. If wrapped with an `IntrinsicWidth` widget, on the other hand, the width does not only fit the text, but stretches to the available width.

Here is an example for "intrinsic height only includes the first line" (the yellow box should include all three lines):

![image](https://user-images.githubusercontent.com/14989/51988710-a4869d00-24a5-11e9-84eb-5c4752c4b521.png)

```dart
class TestPage extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: IntrinsicHeight(
          child: Container(
            color: Colors.black12,
            width: 105,
            alignment: Alignment.centerLeft,
            child: IntrinsicWidth(
              child: Container(
                color: Colors.yellow,
                child: Text("Hallo! dies sollte umbrechen"),
              ),
            ),
          ),
        ),
      ),
    );
  }
}
```

Here is an example for "intrinsic width stretches to available width" (the yellow box should be left-aligned and stop at the "n" in the third line):

![image](https://user-images.githubusercontent.com/14989/51989206-d3514300-24a6-11e9-9055-04cac7b0597d.png)


```dart
class TestPage extends StatelessWidget {
  @override
  Widget build(BuildContext context) {
    return Scaffold(
      body: Center(
        child: Container(
          color: Colors.back12,
          width: 105,
          height: 105,
          alignment: Alignment.centerLeft,
          child: IntrinsicWidth(
            child: Container(
              color: Colors.yellow,
              child: Text("Hallo! dies sollte umbrechen"),
            ),
          ),
        ),
      ),
    );
  }
}
```

My Flutter version:

```sh
$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel master, v1.1.10-pre.220, on Mac OS X 10.14.2 18C54, locale de-DE)
[✓] Android toolchain - develop for Android devices (Android SDK version 28.0.3)
[✓] iOS toolchain - develop for iOS devices (Xcode 10.1)
[✓] Android Studio (version 3.3)
[✓] VS Code (version 1.30.2)
[✓] Connected device (1 available)
```
Repository: go
Issue: go/parser: keep parsing after error limit is reached?
Labels: NeedsInvestigation

This issue and repro case was raised by @rogpeppe:

This file fails to parse:

```go
package m

func _()  {
	_(_
}

func _() {
	if _ {
		_
	}
	if _ {
	}
	_ = _
	if _ {
		_
	}
}
```

However, commenting out one line (unrelated to the error) causes the file to parse correctly.

```go
package m

func _()  {
	_(_
}

func _() {
	if _ {
		_
	}
	if _ {
	}
	// _ = _
	if _ {
		_
	}
}
```
Repository: vscode
Issue: Revealing in the editor should be aware of how much space the command palette is using
Labels: feature-request,quick-pick

Was trying to navigate symbols but I couldn't see the active symbol:

![image](https://user-images.githubusercontent.com/2193314/52002779-b0f40100-2477-11e9-9434-51ef1a7566e3.png)

This was with editor.zoomLevel: 0 and and terminal with 13 rows active.
Repository: flutter
Issue: Embedder proc resolver API requires questionable cast
Labels: engine,a: quality,e: embedder,P2,team-engine,triaged-engine

Following on from discussion [here](https://github.com/google/flutter-desktop-embedding/pull/184#pullrequestreview-188183991).

Unless I'm confused, the current API requires clients to cast between a function pointer and an object pointer (void*). The standard does *not* require that this is a safe/valid cast, which means that on some platforms this might explode. Even where it does work, it requires a reinterpret_cast, which is not ideal.

It seems like the type should be using a generic function pointer (`void*(*)()`), not a generic object pointer (`void*`).
Repository: TypeScript
Issue: Readonly type breaks Set and Map
Labels: Suggestion,In Discussion

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.4.0-dev.201xxxxx

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

**Code**

```ts
// A *self-contained* demonstration of the problem follows...
// Test this by running `tsc` on the command-line, rather than through another build tool such as Gulp, Webpack, etc.
```

**Expected behavior:**

However, Set and Map can't use with es3 and es5. We need any workaround.

```ts
export type Readonly<T> =
  T extends ReadonlySet<infer V> ? ReadonlySet<V> :
  T extends ReadonlyMap<infer K, infer V> ? ReadonlyMap<K, V> :
  { readonly [P in keyof T]: T[P]; };
```

**Actual behavior:**

```ts
type Readonly<T> = {
    readonly [P in keyof T]: T[P];
};
```

**Playground Link:** <!-- A link to a TypeScript Playground "Share" link which demonstrates this behavior -->

**Related Issues:** <!-- Did you find other bugs that looked similar? -->
Repository: pytorch
Issue: Make sure `data_ptr` for non-zero-size input tensors stays the same after the VariableType dispatch
Labels: module: autograd,module: molly-guard,triaged,module: assert failure

In VariableType.cpp, https://github.com/pytorch/pytorch/pull/16305 adds checks to make sure we are still using the same input `TensorImpl` and `Storage` after we call the non-autograd in-place function. However, it is still possible that the in-place function changes the `data_ptr` of the input tensors without changing `TensorImpl` or `Storage` (e.g. by calling `tensor.resize_({bigger_than_original})`. If the input tensors have 0-size, then we expect this behavior to happen and all is good; if the input tensors have non-zero-size and is smaller than needed, we want to tell the user to resize their input tensors to the correct size before passing them into the VariableType function, to prevent `tensor.resize_({size_needed})` from allocating a new `data_ptr` and to make sure the buffer they pass in would be the buffer that contains the returned data.


cc @ezyang @albanD @zou3519 @gqchen @pearu @nikitaved @soulitzer @Lezcano @Varal7
Repository: pytorch
Issue: Benchmarking pre-trained model in Caffe2
Labels: caffe2

If you have a question or would like help and support, please ask at our
[forums](https://discuss.pytorch.org/).

If you are submitting a feature request, please preface the title with [feature request].
If you are submitting a bug report, please fill in the following details.

## Issue description
I am trying to benchmark Caffe2 framework. In the pytorch I see the convnet python script
to do benchmarking. We have to defined the ML network in this python script.
But this python script does not accept any pre-trained caffe2 model.
How can I run a pre-trained model and do benchmarking in Caffe2?


Provide a short description.

## Code example

Please try to provide a minimal example to repro the bug.
Error messages and stack traces are also helpful.

## System Info
Please copy and paste the output from our
[environment collection script](https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py)
(or fill out the checklist below manually).

You can get the script and run it with:
```
wget https://raw.githubusercontent.com/pytorch/pytorch/master/torch/utils/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py
```

- PyTorch or Caffe2:
- How you installed PyTorch (conda, pip, source):
- Build command you used (if compiling from source):
- OS:
- PyTorch version:
- Python version:
- CUDA/cuDNN version:
- GPU models and configuration:
- GCC version (if compiling from source):
- CMake version:
- Versions of any other relevant libraries:
Repository: pytorch
Issue: Feature Request: Earth Mover's Distance Loss
Labels: module: loss,triaged,function request

## 🚀 Feature
(Approximate) Earth Mover's Distance Loss Function

## Motivation
This is a common function used in deep learning papers for point cloud generation and distribution matching.

## Pitch
This ought to be added to the loss function library as it is only increasing in usage in deep learning literature.

## Additional context
There are a few open source implementations out there already. I have updated [this older one](https://github.com/fxia22/pointGAN/tree/74b6c432c5eaa1e0a833e755f450df2ee2c5488e/emd) for PyTorch 1.0 according to the CUDA extension tutorial. While it generally works, there are some bugs though that go beyond my expertise (or understanding) when it comes to larger point sets. These bugs were extant before I started toying with it. My version [can be found here](https://github.com/meder411/PyTorch-EMDLoss).
Repository: pytorch
Issue: Error while installing pytorch
Labels: module: build,caffe2

I am trying to install pytorch with caffe2 support. After cloning the library, I ran this command:

> FULL_CAFFE2=1 python setup.py install

Error 

```
make: *** No rule to make target 'install'.  Stop.
Traceback (most recent call last):
  File "setup.py", line 720, in <module>
    build_deps()
  File "setup.py", line 279, in build_deps
    build_dir='build')
  File "/home/afzal/mmdnn_test/pytorch/tools/build_pytorch_libs.py", line 227, in build_caffe2
    check_call(['make', '-j', str(max_jobs), 'install'], cwd=build_dir)
  File "/usr/lib/python3.5/subprocess.py", line 581, in check_call
    raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '['make', '-j', '12', 'install']' returned non-zero exit status 2

```

Any help?
Repository: flutter
Issue: Debug console spew from WebView plugin on Android
Labels: platform-android,a: quality,p: webview,package,has reproducible steps,P2,found in release: 3.10,found in release: 3.11,team-android,triaged-android

When running WebView widget on Android Simulator I see constant stream of messages in the console like the following:
```
I/zygote  ( 5185): NativeAlloc concurrent copying GC freed 14(32KB) AllocSpace objects, 0(0B) LOS objects, 49% free, 1597KB/3MB, paused 271us total 241.543ms
W/zygote  ( 5185): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 5185): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 5185): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 5185): Attempt to remove non-JNI local reference, dumping thread
I/zygote  ( 5185): NativeAlloc concurrent copying GC freed 18(63KB) AllocSpace objects, 0(0B) LOS objects, 49% free, 1598KB/3MB, paused 37us total 409.673ms
W/zygote  ( 5185): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 5185): Attempt to remove non-JNI local reference, dumping thread
W/zygote  ( 5185): Attempt to remove non-JNI local reference, dumping thread
I/zygote  ( 5185): NativeAlloc concurrent copying GC freed 16(47KB) AllocSpace objects, 0(0B) LOS objects, 49% free, 1598KB/3MB, paused 7.778ms total 253.467ms
W/zygote  ( 5185): Attempt to remove non-JNI local reference, dumping thread
I/zygote  ( 5185): NativeAlloc concurrent copying GC freed 21(64KB) AllocSpace objects, 0(0B) LOS objects, 49% free, 1550KB/3MB, paused 25us total 159.171ms
```

Is it OK or is there some kind of issue?
Repository: godot
Issue: Materials are rendering black if there are no lights in the scene (Intel driver bug)
Labels: bug,platform:windows,topic:rendering,confirmed,topic:thirdparty,topic:3d

<!-- Please search existing issues for potential duplicates before filing yours:
https://github.com/godotengine/godot/issues?q=is%3Aissue
-->

**Godot version:3.1**
<!-- Specify commit hash if non-official. -->


**OS/device including version:Windows 7 64 bit**
 Intel g41 express chipset
Open Gl 2.1
<!-- Specify GPU model and drivers if graphics-related. -->


**Issue description:** I used GLES2 renderer. Adding  a mesh instance gives a completely black cube. Adding materials has no effect. The sky is rendering as it should. Using mesa3d as a open GL 3.1 fixes this problem. Otherwise it occurs on every project
<!-- What happened, and what was expected. -->


**Steps to reproduce:** Add a cube in Godot 3.1 on intel g41 express on GLES2 project


**Minimal reproduction project:**
<!-- Recommended as it greatly speeds up debugging. Drag and drop a zip archive to upload it. -->
Repository: rust
Issue: Unnecessary implicit reborrow cause confusing compiler error
Labels: C-enhancement,A-diagnostics,T-compiler,D-papercut

When calling a function with mutable reference itself, it will cause unnecessary implicit reborrow, which may produces "cannot borrow ... because it is also borrowed as mutable", though there is "no borrow" in the error line.

[Example](https://play.rust-lang.org/?version=nightly&mode=debug&edition=2018&gist=5276b24d3ddd33dcd50b62f26dac17dd)

I think there should be no reborrowing in all 3 calls, and the expected error message should be "borrow of moved value" here.

```rust
pub fn id<'a, T>(x: T) -> T { x }
pub fn id_ref<'a, T: 'a>(x: &'a mut T) -> &'a mut T { x }

fn main() {
    let p = &mut 0i32;
    let q = id_ref(p); // error[E0502]: cannot borrow `p` as immutable because it is also borrowed as mutable
    // let q = id(&mut *p); // error[E0502]: cannot borrow `p` as immutable because it is also borrowed as mutable
    // let q = id(p); // error[E0382]: borrow of moved value: `p`
    println!("{}", p);
    q; // Keep `q` lives here
}
```

Noting that the call to `id_ref` causes reborrowing, but the call to `id` doesn't.
I'm not sure whether it is the expected behavior.
Repository: go
Issue: x/build/cmd/gerritbot: not possible to make cherry-pick CLs via PRs
Labels: Builders,NeedsInvestigation,FeatureRequest

I investigated whether it's possible to create cherry-pick CLs by making a Pull Request, a question that was brought up on the golang-dev mailing list [here](https://groups.google.com/d/msg/golang-dev/Tc8OlLRsju0/AysH6zdeAwAJ) and in issue #25020.

In order to learn whether it's supported, I made an attempt and learned from the experience:

- Backport issue - https://github.com/golang/go/issues/29922#issuecomment-457381644
- Cherry-pick PR I created - PR #29926
- Cherry-pick CL that gerritbot imported - [CL 159478](https://golang.org/cl/159478)

It was possible to create the cherry-pick CL against the correct release branch by having the appropriate base branch in the PR.

However, gerritbot does not recognize it when the PR description contains Change-Id and other lines from the commit being backported. In the PR, the description ended with:

```
<body>

Change-Id: I09a2212eb74c63db575223277aec363c55421ed8
Reviewed-on: https://go-review.googlesource.com/c/159157
Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Filippo Valsorda <filippo@golang.org>
```

In the imported CL, the commit message ended up having:

```
<body>

Change-Id: I09a2212eb74c63db575223277aec363c55421ed8
Reviewed-on: https://go-review.googlesource.com/c/159157
Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Filippo Valsorda <filippo@golang.org>

Change-Id: I09a2212eb74c63db575223277aec363c55421ed8
GitHub-Last-Rev: 396cc6b3a61292ccbe3ccad4e55c3a9842145cab
GitHub-Pull-Request: golang/go#29926
```

In order for it to be possible to make cherry-pick CLs via gerritbot, it would need to gain support for recognizing when the PR description contains `Change-Id` lines from the original commit, and reuse it. So the final commit message imported by gerritbot would need to look something like:

```
<body>

Change-Id: I09a2212eb74c63db575223277aec363c55421ed8
Reviewed-on: https://go-review.googlesource.com/c/159157
Run-TryBot: Brad Fitzpatrick <bradfitz@golang.org>
TryBot-Result: Gobot Gobot <gobot@golang.org>
Reviewed-by: Filippo Valsorda <filippo@golang.org>
GitHub-Last-Rev: 396cc6b3a61292ccbe3ccad4e55c3a9842145cab
GitHub-Pull-Request: golang/go#29926
```

Until this is resolved, it's not possible to send cherry-pick CLs via Pull Requests. /cc @andybons
Repository: go
Issue: xerrors: allow accessing the frame for each error directly
Labels: NeedsDecision

When using structured logging with errors, we don't want a string representation of the error + the frame, we want to access the error string, function name and file:line separately to make them separate fields in the UI and to make it easier to analyze logs. For now, I've written an `xerrors.printer` that just stores all lines that are printed to it and then returns those and based on `xerrors` atm, the first line is the error message, second is the function and third is the file name. But this is janky and fragile.

An easy way to do this is to add an interface to the package that errors can implement to return their frames.
Repository: vscode
Issue: Auto-indent on closing brace
Labels: feature-request,typescript,javascript,editor-autoindent,on-unit-test

VSCode Version: Code 1.30.2
OS Version: Windows_NT x64 10.0.17763
Extensions: Extensions are enabled
![image](https://user-images.githubusercontent.com/28403336/52084629-5500a980-2557-11e9-9175-8a91ef3efaf0.png)

on typing the closing brace. Meaning VSCode should take the current tab indentation size in account and auto-indent the code-block when typing the closing brace.
Repository: rust
Issue: Inconsistencies when exporting dynamic symbols from executables
Labels: A-FFI

I'm working on a project that uses dynamic loading with callbacks back into the Rust executable. Now that the project is big enough to require some of these callbacks to be defined in separate crates, I'm finding the behavior of when a symbol is exported or not to be very inconsistent.

I've tried to shrink the issue by creating a repo that contains several variants that do and don't work. The README describes the variations in more detail: https://github.com/acfoltzer/exported-symbol-example

The upshot is that based on #54451, I would expect that any `#[no_mangle]` definitions in both the executable crate and any dependencies to be exported from the final executable, assuming `--export-dynamic` is used for the final link step.

Instead, the exported `#[no_mangle]` callbacks are eliminated from the final executable in many situations. It's not as simple as whether the callbacks are used/reachable directly from `main`, but also seems to be influenced by the use of trait objects that happen to share a module with the callbacks. This doesn't seem like the intended behavior.

## Meta
Reproducible on nightly and stable:

```
% rustc --version --verbose
rustc 1.32.0 (9fda7c223 2019-01-16)
binary: rustc
commit-hash: 9fda7c2237db910e41d6a712e9a2139b352e558b
commit-date: 2019-01-16
host: x86_64-unknown-linux-gnu
release: 1.32.0
LLVM version: 8.0
```
```
%rustc --version --verbose
rustc 1.34.0-nightly (c1c3c4e95 2019-01-29)
binary: rustc
commit-hash: c1c3c4e95b69dfeaca5c5db6c622d7f90ad30a54
commit-date: 2019-01-29
host: x86_64-unknown-linux-gnu
release: 1.34.0-nightly
LLVM version: 8.0
```
Repository: rust
Issue: self-less method missing return type lifetime should suggest adding &self
Labels: C-enhancement,A-diagnostics,T-compiler

I frequently find myself forgetting to write the `&self` on methods. In the scenario where I write a method whose return type has a lifetime that I've elided, it would be nice if the compiler could include a note suggesting that I might have meant to add `&self` on the method, instead of (or in addition to) suggesting that I should add `'static`.

Example:

```rust
struct Foo<'a>;

struct Bar;

impl Bar {
    fn foos() -> Vec<Foo> {
        unimplemented!()
    }
}
```

This produces the error

```
error[E0106]: missing lifetime specifier
 --> unnamed.rs:6:22
  |
6 |     fn foos() -> Vec<Foo> {
  |                      ^^^ help: consider giving it a 'static lifetime: `Foo + 'static`
  |
  = help: this function's return type contains a borrowed value, but there is no value for it to be borrowed from
```

In fact, looking at that error, even the current help is incorrect, I'd want to write `Foo<'static>`, not `Foo + 'static`.