sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: node
Issue: --cpu-prof not generate profile file when killed by SIGINT
Labels: v8 engine

<!--
Thank you for reporting a possible bug in Node.js.

Please fill in as much of the template below as you can.

Version: output of `node -v`
Platform: output of `uname -a` (UNIX), or version and 32 or 64-bit (Windows)
Subsystem: if known, please specify the affected core module name

If possible, please provide code that demonstrates the problem, keeping it as
simple and free of external dependencies as you can.
-->

* **Version**: 12.0.0
* **Platform**: mac 10.12.4 && Debian 8
* **Subsystem**:

<!-- Please provide more details below this comment. -->
```
// app.js
// for more info about ReDoS, see:
// https://en.wikipedia.org/wiki/ReDoS

var r = /([a-z]+)+$/
var s = 'aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa!'

console.log('Running regular expression... please wait')
for(let i=1;i<100;i++){
  console.time('benchmark');
  const s = 'a'.repeat(i) + '!'
  r.test(s);
  console.timeEnd('benchmark');
}

```
```
$ node --cpu-prof app.js 
$ kill -SIGINT {pid}
```
is this purpose ? or how can i get profile file when app killed by SIGINT?
Repository: opencv
Issue: Mantiuk06 tonemapping does not converge for this image
Labels: category: photo

<!--
* Try to be as detailed as possible in your report.
-->

##### System information (version)
- OpenCV => 4.0.0
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2017


##### Detailed description

In many cases, the result of cv's mantiuk tonemapping is a mess, which leads me to believe that the iterative algorithm does not converge.

Attached one such case.

[MantiukTestcase.zip](https://github.com/opencv/opencv/files/3116812/MantiukTestcase.zip)
Repository: pytorch
Issue: Importing open3d after PyTorch causes free(): invalid pointer
Labels: module: crash,triaged,module: pybind

## 🐛 Bug

Importing the open3d python package after importing PyTorch causes the above crash.

## To Reproduce

Steps to reproduce the behavior:

>>> import torch
>>> import open3d

A two line script with the above statements crashes every time for me. Reversing the order of the imports fixes the problem. I'm using open3d version 0.6.0.0 and PyTorch version 1.0.1.post2.

## Expected behavior

Both packages should be imported normally.

## Environment

PyTorch version: 1.0.1.post2
Is debug build: No
CUDA used to build PyTorch: 9.0.176

OS: Ubuntu 18.04.2 LTS
GCC version: (Ubuntu 7.3.0-27ubuntu1~18.04) 7.3.0
CMake version: version 3.14.0

Python version: 3.6
Is CUDA available: Yes
CUDA runtime version: 10.0.130
GPU models and configuration: 
GPU 0: GeForce GTX 1080 Ti
GPU 1: GeForce GTX 1080 Ti
GPU 2: GeForce GTX 1080 Ti
GPU 3: GeForce GTX 1080 Ti

Nvidia driver version: 410.78
cuDNN version: /usr/lib/x86_64-linux-gnu/libcudnn.so.7.4.2

Versions of relevant libraries:
[pip3] numpy==1.16.3
[pip3] torch==1.0.1.post2
[pip3] torchfile==0.1.0
[pip3] torchvision==0.2.2.post3
[pip3] torchviz==0.0.1
[conda] Could not collect
Repository: TypeScript
Issue: Type safety  for enum property names
Labels: Suggestion,Awaiting More Feedback

## Suggestion

Enums work in two directions, where an enum property value can be retrieved via `AnEnum.aProperty` and a property name can be retrieved via `AnEnum[aValue]`. In TypeScript 3.4.3, the type of the second expression is `string`. Instead, it should be equivalent to `keyof typeof AnEnum | undefined`.

## Use Cases

While the `nameof` operator (suggested in #1579) does not exist yet, a construct such as `AnEnum[AnEnum.aProperty]` can currently be used to safely refer to an enum property name. Unfortunately, since the type of that expression is `string` it requires a cast when assigning it to a type safe target.

## Examples

```typescript
enum AnEnum { aProperty = 1, anotherProperty = 23, yetAnotherOne = 42 };
let target: keyof typeof AnEnum;

…

// Compilation error here: Type 'string' is not assignable to type '"aProperty" | "anotherProperty" | "yetAnotherOne"'.
target = AnEnum[AnEnum.aProperty];
```

## 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).
Repository: vue-element-admin
Issue: 标签栏导航关闭有问题
Labels: need repro :mag_right:

<!--
    注意：为更好的解决你的问题，请参考模板提供完整信息，准确描述问题，信息不全的 issue 将被关闭。

    Note: In order to better solve your problem, please refer to the template to provide complete information, accurately describe the problem, and the incomplete information issue will be closed.
-->


## Bug report（问题描述）
当标签栏导航打开多个的时候入demo中的综合实例-文章列表-点开多个详情的时候如果大于2的数目的时候，页面的显示会出错，之前的详情都被激活....

#### Steps to reproduce（问题复现步骤）
<!--
1. 版本 3.9.3
2. 在综合实例中点开多个文章详情，然后从最后一个依次关闭
3. 即可复现问题
-->

#### Screenshot or Gif（截图或动态图）
![image](https://user-images.githubusercontent.com/31301552/56737742-ae1a5b00-679d-11e9-8f7a-51338a3ccb29.png)


#### Link to minimal reproduction（最小可在线还原demo）
版本 3.9.3 即可
<!--
Please only use Codepen, JSFiddle, CodeSandbox or a github repo
-->

#### Other relevant information（格外信息）
- Your OS:  window
- Node.js version:  8.12.0
- vue-element-admin version: 3.9.3
Repository: flutter
Issue: At the driver test case, i want to know the details about the phone that is being tested such as the chosen locale and screen size
Labels: c: new feature,framework,t: flutter driver,c: proposal,P3,team-framework,triaged-framework

At the driver test case, i want to know few things like which locale where used within the app or the screen size that is being tested (Consider that i run the same set of tests on several combinations of phones and locales).

I can use this informations to test some behaviors that should happen depending on the screen size or locale. Sometimes, you want to be sure that some localized info is being displayed on the screen. Or some behavior should happen depending on the locale.
Repository: godot
Issue: Export var ruins Instantiated objects export variables
Labels: enhancement,topic:gdscript

**Godot version:**
Godot_v3.1-stable_win64

**Issue description:**
Main's instance object.tscn of a variable named example is set to 30.
Here's a line from object.gd,
export var example = 42
I found that removing "export" from above line and then saving the project removes all other instantiated object.tscn's example variable.
Then by adding "export" back and then saving which reverts all other example variable back to 42 instead of 30.
This is a very serious issue for two reasons, there is no undo button and I have made levels with export variables set and I have made a mistake of removing "export" in code and then saving the project which messed up my levels.

**Steps to reproduce:**
Open bug_showcase.zip
Look at Node2D in Main.tscn first to see the number 30
Remove "export" from line 3 in object.gd.
Save.
Then put back "export".
Save.
You will see in the Main.tscn and by inspecting Node2D that 30 has been replaced by 42.

**Minimal reproduction project:**
[bug_showcase.zip](https://github.com/godotengine/godot/files/3118411/bug_showcase.zip)
Repository: create-react-app
Issue: Using `BigInt` primitives
Labels: issue: proposal

### Is this a bug report?

No

### Did you try recovering your dependencies?

n/a

### Which terms did you search for in User Guide?

`bigint`, `babel plugin`,`babel syntax macro`, `"Identifier directly after number"`

### Environment

n/a

### Steps to Reproduce

(Write your steps here:)

1. Use a BigInt primitive, e.g., `42n`
2. Define supported browsers in package.json to be `last 1 chrome version`. I.e., ignore targets that haven't implemented BigInts yet.

### ~~Expected~~ Desired Behavior

A way to use BigInt primitives in CRA without ejecting.

`BigInt` ([Spec](https://tc39.es/proposal-bigint/)) is currently at [Stage 4](https://github.com/tc39/proposal-bigint), with support in Node (since 10.4) and all major desktop and mobile browsers [Caniuse details](https://caniuse.com/#feat=bigint). 

*Side note: You can get partial support by declaring the global (`/* global BigInt */`) if each `BigInt` is wrapped (`BigInt(42)` or `BigInt('42')`). However this still means that a code rewrite will be needed once full support lands to remove the clunky syntax.*

### Actual Behavior

Syntax error:

`Identifier directly after number`

### Reproducible Demo

```js
const foo = 42n;
```

(Edited to reflect this proposal has moved to Stage 4 and has additional browser support and removed reference to the Babel plugin which is no longer necessary.)
Repository: kubernetes
Issue: modifying namespace spec.finalizers via PATCH should return a validation error
Labels: kind/documentation,sig/api-machinery,lifecycle/frozen

**What happened**:

PATCH `{"spec":{"finalizers":null}}` doesn't clear the finalizers and also doesn't return an error.

**What you expected to happen**: It should return an error (use the /finalize subresource).

**How to reproduce it (as minimally and precisely as possible)**: see #77086
Repository: flutter
Issue: Help understanding the profiling summary
Labels: c: new feature,tool,t: flutter driver,P3,team-tool,triaged-tool

I was following this documentation page to understand how to generate profile reports of my application: [Performance profiling](https://flutter.dev/docs/cookbook/testing/integration/profiling)

After that, I have been able to obtain a report of a test in my app, that looks like this (the summary version):

```json
{
  "average_frame_build_time_millis": 11.888272727272728,
  "90th_percentile_frame_build_time_millis": 11.209,
  "99th_percentile_frame_build_time_millis": 37.459,
  "worst_frame_build_time_millis": 37.459,
  "missed_frame_build_budget_count": 10,
  "average_frame_rasterizer_time_millis": 4.998090909090909,
  "90th_percentile_frame_rasterizer_time_millis": 6.575,
  "99th_percentile_frame_rasterizer_time_millis": 6.728,
  "worst_frame_rasterizer_time_millis": 6.728,
  "missed_frame_rasterizer_budget_count": 0,
  "frame_count": 11,
  "frame_build_times": [
    11209,
    37459,
    8001,
    10131,
    7925,
    9552,
    9601,
    10334,
    8129,
    9054,
    9376
  ],
  "frame_rasterizer_times": [
    1947,
    4032,
    3472,
    5550,
    4255,
    6256,
    6728,
    6016,
    6575,
    4607,
    5541
  ]
}
```

However, I don't understand what to do with that information, and what could I do with it in my pipeline to fail when we degrade quality. Could you please give me some more details?

Thank you so much!
Repository: TypeScript
Issue: 3.4.1 regression in distributed types
Labels: Needs Investigation,Domain: Conditional Types

**TypeScript Version:**  3.5.0-dev.20190425

The example below was taken from a real world use-case and simplified.

The `U` type is distributed while the `T` type remains the original union.

The `T` type is wrapped with `Box<T>` when `U` is not an object.

```ts
type Box<T> = { value: T }
type Test<T> = [T] extends [infer U]
  ? U extends object
    ? U
    : U | Box<T>
  : never

type A = number | { foo: number }
type B = Test<A>
```

In theory, the `B` type should be identical to:
```ts
type B = number | { foo: number } | Box<number | { foo: number }>
```

But in the latest version, the `B` type is instead identical to:
```ts
type B = number | { foo: number } | Box<number | (number & { foo: number })>
```

This works correctly in 3.3.x but not 3.4.x and later.

**Playground Link:** [click here](https://typescript-play.js.org/#code/C4TwDgpgBAQg9gDwDwBUB8UC8UDeUBuAhgDYCuEAXFClAL4BQok1EAzsKhtgNooC6UCAmAQAdgBNWUbgEtRAMwgAnKAFU+9KFAD8awcLGSocAEYArCAGNgmrTrW2tVVVAA+sRJ1tVREfMvpGcGgAQSwoUVIAWxNlN1woeTg4H2jYlQYmaBhwlDYOELQgA)
Repository: TypeScript
Issue: [Feature request] allow use `showConfig` in tsconfig.json
Labels: Suggestion,Awaiting More Feedback

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Please read the FAQ first, especially the "Common Feature Requests" section.

-->

## Search Terms

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->

## Suggestion

<!-- A summary of what you'd like to see added or changed -->

allow use `showConfig` in tsconfig.json
and print config in console, and also show tsconfig.json path

## Use Cases

<!--
What do you want to use this for?
What shortcomings exist with current approaches?
-->

so can make sure know what is final config at current process

without use `tsc --showConfig`

## Examples

<!-- Show how this would be used and what the behavior would be -->

## 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
* [ ] This isn't a runtime feature (e.g. library functionality, non-ECMAScript syntax with JavaScript output, etc.)
* [ ] This feature would agree with the rest of [TypeScript's Design Goals](https://github.com/Microsoft/TypeScript/wiki/TypeScript-Design-Goals).
Repository: create-react-app
Issue: Why not use HashedModuleIdsPlugin
Labels: issue: needs investigation

<!--
  PLEASE READ THE FIRST SECTION :-)
-->

### Is this a bug report?
No
<!--
  If you answered "Yes":

    Please note that your issue will be fixed much faster if you spend about
    half an hour preparing it, including the exact reproduction steps and a demo.

    If you're in a hurry or don't feel confident, it's fine to report bugs with
    less details, but this makes it less likely they'll get fixed soon.

    In either case, please fill as many fields below as you can.

  If you answered "No":

    If this is a question or a discussion, you may delete this template and write in a free form.
    Note that we don't provide help for webpack questions after ejecting.
    You can find webpack docs at https://webpack.js.org/.
-->
I was curious about how create-react-app implements long cache, how do you control the file hashes to remain the same when adding or removing files, because I didn't see HashedModuleIdsPlugin added to the webpack configuration
Repository: storybook
Issue: Addon-docs: Source editing support
Labels: feature request,addon: storysource,addon: docs

Add editing support to #6641

Details TBD
Repository: storybook
Issue: Addon-docs: styleguide support
Labels: feature request,addon: docs

Add doc blocks for:
- [x] Type
- [x] Colors
- [x] Icons
- [ ] Documentation

Relies on #6644
Repository: angular
Issue: Router scrolling does not work properly when dealing with content that is not immediately visible
Labels: type: bug/fix,freq3: high,area: router,state: confirmed,P3

<!--🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅

Oh hi there! 😄 

To expedite issue processing please search open and closed issues before submitting a new one.
Existing issues often contain information about workarounds, resolution, or progress updates.

🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅🔅-->


# 🚀 feature request

### Relevant Package
<!-- Can you pin-point one or more @angular/* packages the are relevant for this feature request? -->
<!-- ✍️edit: --> This feature request is for @angular/router


### Description
<!-- ✍️-->
When using routerLink fragment to scroll to an anchor it might not work properly if unless the element is already loaded (this might be the case for a component that is rendered once data from a API has been loaded)

Another problem is that the anchor might be pushed down in the viewport when data is loaded.
A simple example: https://angular-7fpprl.stackblitz.io/qwe#qwe

### Describe the solution you'd like
<!-- ✍️-->
Perhaps there should be some wait mechanism in place that waits for the element to be rendered? I assume it would also need have a configurable timeout setting.

Also if the anchor is pushed down by dynamic content then perhaps position should be updated?

### Describe alternatives you've considered
<!-- ✍️-->
One option might be to create a custom directive that checks if the element exsists and then scrollIntoView() but it feels like monkey patching a feature that should be handled by the router
Repository: material-ui
Issue: Cleanup package scripts
Labels: core

We currently leverage the `scripts` entry in our package.json. As of right now this includes around 34 scripts that aren't really documented. Any addition, change etc. has to be followed by contributors to be understood. 

It would be nice if we could consolidate those into a single place that also adds documentation. This should put emphasis on common tasks as well as guiding contributors: What script can I use to perform X task?

https://github.com/kentcdodds/nps looks very close to what I have in mind (task +  description + watch mode in a single place). 

Maybe there are other solutions for large monorepos. In any case it would be nice if we could improve the first contributor experience.
Repository: rust
Issue: Split up files with `// ignore-tidy-filelength`
Labels: C-cleanup,T-rustdoc,T-compiler,E-medium,C-tracking-issue

These files are over 3,000 lines, which is not ideal for navigating or comprehending. If we can, it would be good to split these up. See also https://github.com/rust-lang/rust/issues/60015, which is a specific issue of this problem.

T-compiler:

- [ ] rustc_parse/src/parser/expr.rs
- [ ] rustc_borrowck/src/diagnostics/conflict_errors.rs
- [ ] rustc_trait_selection/src/error_reporting/traits/suggestions.rs
- [ ] rustc_hir_typeck/src/method/suggest.rs
- [ ] rustc_resolve/src/late.rs
- [ ] rustc_resolve/src/late/diagnostics.rs

T-rustdoc:

- [ ] src/librustdoc/html/static/js/search.js
Repository: rust
Issue: Display original source location for doc test failures
Labels: T-rustdoc,C-enhancement,A-doctests,E-needs-mcve

I have the following file:

```rust
// This Source Code Form is subject to the terms of the Mozilla Public
// License, v. 2.0. If a copy of the MPL was not distributed with this
// file, You can obtain one at http://mozilla.org/MPL/2.0/.

use oraide_parser_miniyaml::{
    ParserCtxExt,
    ParserCtxStorage,
};

/// Entrypoint into MiniYaml parsing
///
/// Contains inputs and memoized computation results
///
/// # Example
/// ```rust
/// use oraide_parser_miniyaml::{Database,ParserCtx,ParserCtxExt,Tree};
/// let mut db = Database::default();
/// let file_id = db.add_file("example.yaml", "Hello:\n");
/// let tree: Tree = db.file_tree(file_id);
/// ```
#[salsa::database(ParserCtxStorage)]
pub struct Database {
    rt: salsa::Runtime<Self>,
}
```

When I run `cargo test` for this package I get the following, valid, failure:

```
failures:

---- src/lib.rs - Database (line 6) stdout ----
error[E0432]: unresolved import `oraide_parser_miniyaml::Database`
 --> src/lib.rs:7:30
  |
3 | use oraide_parser_miniyaml::{Database,ParserCtx,ParserCtxExt,Tree};
  |                              ^^^^^^^^ no `Database` in the root

thread 'src/lib.rs - Database (line 6)' panicked at 'couldn't compile the test', src/librustdoc/test.rs:354:13
note: Run with `RUST_BACKTRACE=1` environment variable to display a backtrace.
```

Unfortunately the reported error location is from the generated (I assume) code that is actually tested and not the correct location in the original source.

It is indeed the 7th line in the doc but that isn't as helpful as it could be.

Ideally I would see `src/lib.rs:16:30`.

Mapping these locations back to original source location would, IMO, be more useful because we could then see exactly where doc tests are failing (especially in a file with many doc tests) and, in some environments, can ctrl/cmd-click the `src/lib.rs:X:Y` output to take our editor directly to the failure.
Repository: go
Issue: cmd/vet: add unkeyed field literal check to 'go test' set
Labels: NeedsDecision,early-in-cycle,Analysis

#2794 proposes requiring keyed (tagged) literals for any imported struct.
`go vet` has a test for this already.
But the test is only on in `go vet` not the automatic vet during `go test`.
I suggest we enable it during `go test` at the start of the Go 1.14 cycle
as an experiment. If it works well there then maybe it would make sense
to promote the restriction to the language itself. And if not, then not.
Or maybe vet alone will be enough. Time will tell.

/cc @robpike @ianlancetaylor @griesemer
Repository: create-react-app
Issue: Non module css doesn't work with :local() in CRA 3.0
Labels: issue: needs investigation

### Is this a bug report?

Yes

### Did you try recovering your dependencies?

Yes

### Environment

```
Environment Info:

  System:
    OS: Linux 4.14 Manjaro Linux
    CPU: (12) x64 Intel(R) Core(TM) i9-8950HK CPU @ 2.90GHz
  Binaries:
    Node: 10.15.1 - ~/.nvm/versions/node/v10.15.1/bin/node
    Yarn: 1.15.2 - /usr/bin/yarn
    npm: 6.4.1 - ~/.nvm/versions/node/v10.15.1/bin/npm
  Browsers:
    Chrome: Not Found
    Firefox: Not Found
  npmPackages:
    react: ^16.8.6 => 16.8.6 
    react-dom: ^16.8.6 => 16.8.6 
    react-scripts: 3.0.0 => 3.0.0 
  npmGlobalPackages:
    create-react-app: Not Found
```


### Steps to Reproduce

(Write your steps here:)

1. Have a non module css-file, e.g. MyStyle.css
2. Have a class in said file as a `:local` scoped class, e.g. `:local(.myClass) { ... }`
3. Import CSS file in a React-component, e.g. `import css from './MyStyle.css'`
4. Observe that the classname is not exported

### Expected Behavior

That the css class has been given a random name and is available as a property on the css object, e.g. `{ myClass: "_2uhJkdnDbAceZ0gQC-r3vz" }`

### Actual Behavior

Object was empty: `{}`

### Reproducible Demo

Source:
https://github.com/almyy/local-classname-repro

Deployed example:
 https://almyy.github.io/local-classname-repro/
Repository: go
Issue: internal/singleflight: delete, use golang.org/x/sync/singleflight
Labels: help wanted,NeedsFix

The singleflight package started life in internal/singleflight and then moved to golang.org/x/sync/singleflight, and the two have had slightly divergent development histories since. It's getting kinda messy. Their APIs have even somewhat diverged.

I just tried to re-unify them and delete internal/singleflight from std, but we can't use mod/vendor packages during bootstrap.

/cc @ianlancetaylor
Repository: rust
Issue: Compiler error when I remove unreachable code
Labels: C-enhancement,A-lints,A-diagnostics,T-lang,T-compiler,D-confusing

Consider the following minimal example ([playground](https://play.rust-lang.org/?version=stable&mode=debug&edition=2018&gist=5fd9665e0b90ff589f07af468da21d98)):

```rust
use futures::{Future, future::ok};

fn main() {
    ok(()).then(|_a: Result<(), ()>| {
        std::process::exit(1);
        Ok(()) as Result<(), ()>
    }).wait().unwrap();
}
```

It compiles successfully but warns me that line 6 (`Ok(()) as Result<(), ()>`) is unreachable.  That is correct, because `std::process::exit` is a diverging function.  But when I remove that line, compilation fails with the following error:

```
error[E0277]: the trait bound `(): futures::future::Future` is not satisfied
```

So I am forced to include unreachable code to work around the error.