sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: rust
Issue: Support hiding specific stackframes from backtrace by marking on the original functions.
Labels: A-runtime,T-lang,C-feature-request

Recently `#[track_caller]` usages has landed on nightly channel, which is really great! However i want to request a little more here. Currently
```rust
fn main() {
    panic!("foo");
}
```
output is:
```text
thread 'main' panicked at 'foo', src/main.rs:2:5
stack backtrace:
   0: backtrace::backtrace::libunwind::trace
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/libunwind.rs:88
   1: backtrace::backtrace::trace_unsynchronized
             at /cargo/registry/src/github.com-1ecc6299db9ec823/backtrace-0.3.40/src/backtrace/mod.rs:66
   2: std::sys_common::backtrace::_print_fmt
             at src/libstd/sys_common/backtrace.rs:77
   3: <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt
             at src/libstd/sys_common/backtrace.rs:59
   4: core::fmt::write
             at src/libcore/fmt/mod.rs:1057
   5: std::io::Write::write_fmt
             at src/libstd/io/mod.rs:1426
   6: std::sys_common::backtrace::_print
             at src/libstd/sys_common/backtrace.rs:62
   7: std::sys_common::backtrace::print
             at src/libstd/sys_common/backtrace.rs:49
   8: std::panicking::default_hook::{{closure}}
             at src/libstd/panicking.rs:204
   9: std::panicking::default_hook
             at src/libstd/panicking.rs:224
  10: std::panicking::rust_panic_with_hook
             at src/libstd/panicking.rs:472
  11: std::panicking::begin_panic
             at /rustc/689fca01c5a1eac2d240bf08aa728171a28f2285/src/libstd/panicking.rs:399
  12: playground::main
             at src/main.rs:2
  13: std::rt::lang_start::{{closure}}
             at /rustc/689fca01c5a1eac2d240bf08aa728171a28f2285/src/libstd/rt.rs:67
  14: std::rt::lang_start_internal::{{closure}}
             at src/libstd/rt.rs:52
  15: std::panicking::try::do_call
             at src/libstd/panicking.rs:305
  16: __rust_maybe_catch_panic
             at src/libpanic_unwind/lib.rs:86
  17: std::panicking::try
             at src/libstd/panicking.rs:281
  18: std::panic::catch_unwind
             at src/libstd/panic.rs:394
  19: std::rt::lang_start_internal
             at src/libstd/rt.rs:51
  20: std::rt::lang_start
             at /rustc/689fca01c5a1eac2d240bf08aa728171a28f2285/src/libstd/rt.rs:67
  21: main
  22: __libc_start_main
```
However, of the 22 stack frames, only 3 or 4 is meaningful to user. It would be great if rest of the  functions can be marked with a special attribute, and maybe marked somehow in the mangled symbol, then be excluded from the default display of backtrace.
Repository: godot
Issue: Text in the help section of the editor doesn't scale with font settings
Labels: enhancement,topic:editor,confirmed,usability

**Godot version:**
3.2.rc1

**OS/device including version:**
Linux / Pop_OS

**Issue description:**
The text in the help section of the editor stays the same size no matter if `main_font_size` is changed in the editor settings.
![help_font](https://user-images.githubusercontent.com/3285214/72661841-13227a80-39d7-11ea-95c2-14bc574e9fa4.png)
![help_font2](https://user-images.githubusercontent.com/3285214/72661894-d30fc780-39d7-11ea-815a-499738d2e625.png)

**Steps to reproduce:**
Open a new project, navigate to the help section and alter `main_font_size` in the editor settings.

**Minimal reproduction project:**
Repository: neovim
Issue: Debug Adapter Protocol implementation
Labels: enhancement,plugin,lua

Termdebug only works for gdb, which is a major disappointment for the users who've wanted an integrated debugger for years, but don't compile in gcc (or perhaps not at all).

[Vimspector](https://github.com/puremourning/vimspector) implements the [Debug Adapter Protocol](https://microsoft.github.io/debug-adapter-protocol/) (DAP) for Vim, which is a common interface to interop with a lot of different debuggers. The author is working to integrate it with Neovim, but is running into some issues concerning our API; see the [discussion](https://github.com/puremourning/vimspector/issues/29) and his [current progress](https://github.com/puremourning/vimspector/pull/77).

Given that we've already merged a debugger plugin from Vim and that we already like to work with protocols like LSP (DAP is the LSP of debuggers, you could say), would you consider an upgrade of termdebug to implement DAP and interface with a multitude of debuggers?
Repository: node
Issue: we should publish and compare benchmark results some where
Labels: benchmark

It would be cool if we would offer a way to let endusers run the benchmarks complet and submit results with some added data so we can compare the results against diffrent cpu and other metrics.
Repository: create-react-app
Issue: Support for setting default scripts-version from template.json
Labels: issue: proposal,needs triage

### Is your proposal related to a problem?

<!--
  Provide a clear and concise description of what the problem is.
  For example, "I'm always frustrated when..."
-->

I've been maintaining universal-react-scripts, a version of react-scripts which includes SSR support. I've recently been trying to merge in the changes from 3.3.0, but as it stands, it would now require that instead of just asking the user to specify `--scripts-version` with CRA, they'll also need to specify the `--template` option.

The reason for this change is that universal-react-scripts was already applying some changes to the template within its `init` script, with the files stored next to the existing `template` directories. However, with 3.3.0, the template could be anything -- so it's no longer possible to apply this transformation. Instead, the user will need to specify an SSR template from the start.

### Describe the solution you'd like

For something like SSR, the template and scripts version need to work together. To facilitate this, I propose that we add support for a `defaultScriptsVersion` property to `template.json`. Then, the `create-react-app` script should:

1. Install and unpack the template to get access to `template.json`.
2. Check for a defaultScriptsVersion, falling back to `react-scripts` as the default.
3. Then install the scripts and other packages as before.

### Describe alternatives you've considered

The obvious alternative is to ask people to pass compatible `--scripts-version` and `--template` options to `create-react-app`:

```bash
npx create-react-app --scripts-version=universal-react-scripts --template=universal
```

This is pretty verbose though, and will break if only one of the two options are passed. Ideally, the user could just do this:

```bash
npx create-react-app --template=universal
```

Another alternative would be to somehow allow the scripts version to transform the template name. This has the advantage of allowing the scripts to bail on unsupported templates -- but it sounds far more complicated.
Repository: godot
Issue: Joint2D doesn't react to KinematicBody2D
Labels: bug,confirmed,topic:physics

**Godot version:**
3.1.2.
**OS/device including version:**
Win 10
**Issue description:**
Attaching PinJoint2D, DampenedSprintJoint2D or GrooveJoint2D doesn't affect KinematicBody2d either using position, global_position, move_and_slide() or move_and_colide().
**Steps to reproduce:**
Joining 2x KinematicBody2D or KinematicBody2d with StaticBody2D via either of the Joint2D derived classes. No change if parenting bodies or them being siblings.
**Minimal reproduction project:**
[PhysicsCameraShake.zip](https://github.com/godotengine/godot/files/4080679/PhysicsCameraShake.zip)
Repository: godot
Issue: Snapping Controls margins doesn't work after rotating their Rect
Labels: enhancement,topic:editor

**Godot version:**
Godot 3.2.rc1

**OS/device including version:**
Solus 4 Gnome

**Issue description:**
When ou try to drag the margin of a rotated Control node they don't snap anymore. Might be related to #23030

**Steps to reproduce:**
1. Add a Control to the scene
2. Activate snap to grid
3. Try to move its margin in the editor, e.g. with the Selection Mode on drag the margin
4. Now rotate the Control
5. Try to move its margin in the editor again

![bug-report](https://user-images.githubusercontent.com/10171059/72664524-a65eae80-39dd-11ea-9841-c1413d5694a3.gif)
Repository: pytorch
Issue: [JIT] Compile group of functions/modules
Labels: oncall: jit,triaged

## 🚀 Feature

I would like to be able to jit compile a group of functions or modules in order to serialize the obtained library in a single file so that later can be loaded in C++.

## Motivation

The main motivation for this feature is to port Kornia to C++ avoiding the massive effort to re-implement the whole thing from scratch in C++. We expect to do at some point in the future but as a first iteration I think we could bootstrap the process of compiling from python to C++ and producing something functional out of the box.

In addition, this could somehow being extended to port to other frameworks by serializing into ONNX format.

Any thoughts about how to proceed with this will be very welcomed :)

cc @suo
Repository: go
Issue: cmd/go: error: unrecognized command line option '-rdynamic' when cross-compiling to ARM with -pie
Labels: help wanted,NeedsInvestigation

I'm not sure if this is supposed to work, i.e `-buildmode pie` for ARM, but nothing seems to suggest it shouldn't.

### What version of Go are you using (`go version`)?

<pre>
$ go version
go version go1.13.6 linux/amd64
</pre>

### Does this issue reproduce with the latest release?
Yes

### 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="/home/daenney/.cache/go-build"
GOENV="/home/daenney/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/data/Development/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/home/daenney/Applications/asdf/installs/golang/1.13.6/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/home/daenney/Applications/asdf/installs/golang/1.13.6/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
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 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build205825653=/tmp/go-build -gno-record-gcc-switches"
</pre></details>

### What did you do?

main.go:
```go
package main

func main() {
        print("hello")
}
```
```sh
$ env GOOS=linux env GOARCH=arm go build -o test -buildmode pie
```

### What did you expect to see?

No error, and a resulting `test` binary.

### What did you see instead?

```
/home/daenney/Applications/asdf/installs/golang/1.13.6/go/pkg/tool/linux_amd64/link: running gcc failed: exit status 1
gcc: error: unrecognized command line option ‘-marm’; did you mean ‘-mabm’?
```

The error also occurs if I add `GOARM=7`. It triggers on a combination of `-buildmode pie` and `GOARCH=arm`. Dropping `-buildmode pie` the build succeeds.

```
$ gcc --version
gcc (GCC) 9.2.0
Copyright (C) 2019 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
```

```
$ uname -a
Linux monoceros 5.4.8-arch1-1 #1 SMP PREEMPT Sat, 04 Jan 2020 23:46:18 +0000 x86_64 GNU/Linux
```

```
$ pacman -Qq | grep gcc
arm-none-eabi-gcc
gcc
gcc-libs
```
Repository: flutter
Issue: [in_app_purchase] Add documentations to explain: How to detect if an auto renewal subscription is cancelled on iOS.
Labels: platform-ios,d: api docs,p: in_app_purchase,package,P3,team-ios,triaged-ios

I am using in_app_purchase package for Auto-renewal Subscription. In my case, it's working perfectly for android but for Ios when a user cancels the subscription it is still showing purchase status is purchased. How can I detect if a user cancelled the subscription on IOS.
 /// Gets past purchases
 ```dart
 Future<List<PurchaseDetails>> getPastPurchases() async {
    QueryPurchaseDetailsResponse response = await iap.queryPastPurchases();
    if (Platform.isAndroid) {
      for (PurchaseDetails purchase in response.pastPurchases) {
        print('InApp Purchase Helper Android');
        print(purchase.billingClientPurchase.originalJson);
      }
    } else {
      for (PurchaseDetails purchase in response.pastPurchases) {
       
            iap.completePurchase(purchase);
   
        }
      }
    }
    purchases = response.pastPurchases;
    return purchases;
  }
```



  /// Purchase a product
```
  void buyProduct(ProductDetails prod) {
    final PurchaseParam purchaseParam = PurchaseParam(productDetails: prod);
    iap.buyNonConsumable(purchaseParam: purchaseParam);
  }
```

  /// Returns purchase of specific product ID
```
  PurchaseDetails hasPurchased(String productID) {
return purchases.firstWhere((purchase) => purchase.productID == productID,
          orElse: () => null);
  }
```

  /// verifyPurchase
```
  bool verifyPurchase() {
    PurchaseDetails purchased = hasPurchased(productID);
    PurchaseDetails purchasedOneMonth = hasPurchased(productID1);
    if (purchased != null || purchasedOneMonth != null) {
      return true;
    }
    return false;
  }
```



<!-- Thank you for using Flutter!

     Please check out our documentation first:
      * https://flutter.dev/
      * https://api.flutter.dev/

     If you can't find the answer there, please consider asking a question on
     the Stack Overflow Web site:
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     Please don't file a GitHub issue for support requests. GitHub issues are
     for tracking defects in the product. If you file a bug asking for help, we
     will consider this a request for a documentation update.

-->
Repository: TypeScript
Issue: Support safe index access for noImplicitAny
Labels: Suggestion,Awaiting More Feedback

It is hard to use noImplicitAny without enabling suppressImplicitAnyIndexErrors on the current TypeScript.

## Search Terms

noImplicitAny suppressImplicitAnyIndexErrors 

## Suggestion

Provide safe indexes without explicit type declarations to avoid unsafe index access errors.

## Use Cases

- for-in
- Object.keys

## Examples

```ts
const o = {};
for (const key in o) {
    o[key]; // Should be no error.
}
for (const key of Object.keys(o)) {
    o[key]; // Should be no error.
}
```

## Checklist

My suggestion meets these guidelines:

* [x] This wouldn't be a breaking change in existing TypeScript/JavaScript code (for-in only)
* [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).
Repository: rust
Issue: Let custom codegen backends opt out of LTO
Labels: A-linkage,A-codegen,T-compiler,C-feature-request,A-cranelift

For example cg_clif doesn't support LTO. Unfortunately enabling LTO makes the linker code always omit object files, so attempting to use `-Clto=yes` will result in a linker error. It is not practical to just not pass `-Clto=yes`, as many crates enable it in their `Cargo.toml`. I would like to be able to make cg_clif tell rustc that LTO should be disabled, even when `-Clto=yes` is passed. I think there should still be a warning though.
Repository: deno
Issue: Release musl builds
Labels: build,suggestion

Previously I was able to use `--target x86_64-unknown-linux-musl` on rusty_v8 and deno (excluding the plugin). https://github.com/denoland/rusty_v8/issues/49


> It's unclear to me if it's best to _only_ target x86_64-unknown-linux-musl or to additionally support it. e.g. sccache seems to [_only_ provide binaries for that target](https://github.com/mozilla/sccache/releases/tag/0.2.12).

The one concern is that glibc is required for plugins (but I don't know if that means glibc cannot be used on a binary created with musl 🤷‍♂ ).

This is useful for platforms without glibc, examples alpine linux and amazon linux (which is occasionally a pain building, so would be helpful if a compatible binaries was in deno's CI).

xlink: #3243 #1658 #1495 #3356
Repository: TypeScript
Issue: Duplicate identifier errors when using @types inside a Windows junction
Labels: Bug

This is a dupe of #11333, but that issue was marked as closed/fixed (and locked... why?). It's not. It should be reopened and _actually_ fixed. It's also unrelated to 'npm link'.


**IMPORTANT**:

my `e:\work` directory is a JUNCTION point to `y:\work`


node: 13.5.0
npm: 6.13.4
tsc:  3.7.5

index.ts:

````
/// <reference path="node_modules/@types/youtube/index.d.ts" />
````

package.json:

````
{
  "name": "junction-bug",
  "scripts": {
    "tsc": "tsc index.ts"
  },
  "devDependencies": {
    "@types/youtube": "0.0.38",
    "typescript": "^3.7.5"
  }
}
````

**NOTE**: There is NO reference to 'y:' in any of my project's files, nor in any of npm's files. `tsc` is erroneously converting relative paths to absolute paths on the destination drive. look for references to `y:\` in the output below:

````
e:\work\junction-bug>dir e:\ | findstr work
04/19/2016  09:02 AM    <JUNCTION>     work [y:\work]

e:\work\junction-bug>npm i
...
e:\work\junction-bug>findstr /s /i /c:"y:\\" *

e:\work\junction-bug>npm run tsc

> junction-bug@ tsc E:\work\junction-bug
> tsc index.ts

node_modules/@types/youtube/index.d.ts:16:1 - error TS6200: Definitions of the following identifiers conflict with those in another file: UNSTARTED, ENDED, PLAYING, PAUSED, BUFFERING, CUED, InvalidParam, Html5Error, VideoNotFound, EmbeddingNotAllowed, EmbeddingNotAllowed2, AlwaysVisible, HideAllControls, HideProgressBar, NoAutoPlay, AutoPlay, UserDefault, ForceOn, ProgressBarColor, Hide, ShowLoadPlayer, ShowDelayLoadPlayer, Enable, Disable, Show, ListType, ListTypePlayer, ListTypeSearch, ListTypeUserUploads, SinglePlay, Loop, Full, Modest, Fullscreen, Inline, SuggestedVideoQuality, VideoQualityDefault, VideoQualitySmall, VideoQualityMedium, VideoQualityLarge, VideoQualityHD720, VideoQualityHD1080, VideoQualityHighRes, Player

16 declare namespace YT
   ~~~~~~~

  y:/work/junction-bug/node_modules/@types/youtube/index.d.ts:16:1
    16 declare namespace YT
       ~~~~~~~
    Conflicts are in this file.

y:/work/junction-bug/node_modules/@types/youtube/index.d.ts:16:1 - error TS6200: Definitions of the following identifiers conflict with those in 
another file: UNSTARTED, ENDED, PLAYING, PAUSED, BUFFERING, CUED, InvalidParam, Html5Error, VideoNotFound, EmbeddingNotAllowed, EmbeddingNotAllowed2, AlwaysVisible, HideAllControls, HideProgressBar, NoAutoPlay, AutoPlay, UserDefault, ForceOn, ProgressBarColor, Hide, ShowLoadPlayer, ShowDelayLoadPlayer, Enable, Disable, Show, ListType, ListTypePlayer, ListTypeSearch, ListTypeUserUploads, SinglePlay, Loop, Full, Modest, Fullscreen, Inline, SuggestedVideoQuality, VideoQualityDefault, VideoQualitySmall, VideoQualityMedium, VideoQualityLarge, VideoQualityHD720, VideoQualityHD1080, VideoQualityHighRes, Player

16 declare namespace YT
   ~~~~~~~

  node_modules/@types/youtube/index.d.ts:16:1
    16 declare namespace YT
       ~~~~~~~
    Conflicts are in this file.


Found 2 errors.

````

**Related Issues:** 113333
Repository: go
Issue: proposal: x/crypto/argon2: add API variants to support a buffer pool
Labels: Proposal,Proposal-Hold,Proposal-Crypto

argon2.Key() & .IDKey() appear to thrash memory by allocating a (typically) large buffer and using it once.
https://github.com/golang/crypto/blob/master/argon2/argon2.go#L157

This might not scale well where every login on a high-traffic site calls this API to check a password.

Could API variants be added which take a config struct that optionally contains a buffer, so we can use a buffer pool?

@aead @mark-rushakoff @bradfitz
Repository: go
Issue: cmd/go: build fails when %go_import is used in SWIG interfaces
Labels: help wanted,NeedsInvestigation

<!--
Please answer these questions before submitting your issue. Thanks!
For questions please use one of our forums: https://github.com/golang/go/wiki/Questions
-->

### What version of Go are you using (`go version`)?

<pre>
go version go1.13.5 linux/amd64
</pre>

### What operating system and processor architecture are you using (`go env`)?

<details><summary><code>go env</code> Output</summary><br><pre>
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/user/.cache/go-build"
GOENV="/home/user/.config/go/env"
GOEXE=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/user/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GCCGO="gccgo"
AR="ar"
CC="gcc"
CXX="g++"
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 -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build083237116=/tmp/go-build -gno-record-gcc-switches"

</pre></details>

### What did you do?
I have created an empty package and a SWIG interface for it containing only `%go_import(_ "time")`.

### What did you expect to see?
A successful build (by doing `go build`).

### What did you see instead?
The build failed with the following error:
`/tmp/go-build220377569/b001/_dummy_swig.go:40:8: can't find import: "time"`
Repository: vue
Issue: the string constructor cannot be used as a `key`
Labels: bug,discussion

### Version
2.6.11

### Reproduction link
[https://codesandbox.io/s/practical-shaw-br23c](https://codesandbox.io/s/practical-shaw-br23c)







### Steps to reproduce
Open the codesandbox and you'll see a warning like `[Vue warn]: Duplicate keys detected: 'constructor'. This may cause an update error.`

Click the "swap" button TWICE to swap the list in the data, triggering the error.

If the literal string "constructor" in the first list is changed for any other string, there are no errors or warnings.

### What is expected?
The list should swap between the "first" and "second" list

### What is actually happening?
"TypeError: Cannot read property 'key' of undefined"

---
:( this was a hard bug to track down.

<!-- generated by vue-issues. DO NOT REMOVE -->
Repository: flutter
Issue:  IconButton seems to be missing Semantics(container: true)
Labels: framework,f: material design,a: accessibility,customer: money (g3),team-design,triaged-design

Internal bug: b/147830016

Comparing [RawMaterialButton](https://github.com/flutter/flutter/blob/8665e13801fe6b53a0e67866d2ee6cd5ef2083f4/packages/flutter/lib/src/material/button.dart#L458) to [IconButton](https://github.com/flutter/flutter/blob/8665e13801fe6b53a0e67866d2ee6cd5ef2083f4/packages/flutter/lib/src/material/icon_button.dart#L374). It seems that IconButton is missing `container: true`?

This was evident when we had an IconButton that was a child of a `scopesRoute: true, explicitChildNodes: true` Semantics node -- the IconButton wasn't showing up at all in semantic debugger.

Semantics widget seems to be required as a parent to the IconButton with a tooltip set which is used as the semantics label.