sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: local_auth plugin Displays a FaceID error in emulator but the Try FaceID Again doesn't work
Labels: platform-ios,p: local_auth,package,P2,team-ios,triaged-ios

## Steps to Reproduce

Write an app that use the local_auth plugin.  Run it on an IOS Simulator with iPhone X, etc. on IOS 12. 

Using the simulator indicate a non-face match.  A Dialog box (stock) comes up and says "Face Not Recognized" .. with a "Try FaceID again" .. Click on that button.. Nothing happens at all .. 


## Logs

```
flutter: [welcomeScreen] - Pressed Biometric Use Button
    1000 = 1;
}, (null) on <LAClient: 0x600001f71ef0>
    7
), NSLocalizedDescription=User interaction is required.} on <LAClient: 0x600001f71ef0>
    2 = "Please authenticate to login";
}, (null) on <LAClient: 0x600001f71ef0>
flutter: [WelcomeScreen - build()
flutter: [welcomeScreen - _buildBiometricOption] - useBio is true and hasStoredLogin is true
flutter: [welcomeScreen - _buildBiometricOption] - useBio is true!


```

<!-- Finally, paste the output of running `flutter doctor -v` here. -->

```
[✓] Flutter (Channel beta, v0.8.2, on Mac OS X 10.14 18A391, locale en)
    • Flutter version 0.8.2 at /Users/sjm/Development/tools/flutter
    • Framework revision 5ab9e70727 (3 weeks ago), 2018-09-07 12:33:05 -0700
    • Engine revision 58a1894a1c
    • Dart version 2.1.0-dev.3.1.flutter-760a9690c2

[✓] Android toolchain - develop for Android devices (Android SDK 27.0.3)
    • Android SDK at /Users/sjm/Library/Android/sdk
    • Android NDK location not configured (optional; useful for native profiling support)
    • Platform android-27, build-tools 27.0.3
    • Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)
    • All Android licenses accepted.

[✓] iOS toolchain - develop for iOS devices (Xcode 10.0)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Xcode 10.0, Build version 10A255
    • ios-deploy 1.9.2
    • CocoaPods version 1.5.3

[✓] Android Studio (version 3.2)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin version 26.0.1
    • Dart plugin version 173.4700
    • Java version OpenJDK Runtime Environment (build 1.8.0_152-release-1136-b06)

[✓] Connected devices (2 available)
    • Android SDK built for x86 • emulator-5554                        • android-x86 • Android 9 (API 28) (emulator)
    • iPhone X                  • 78590509-1E81-4378-8BDE-92EBAFDB00A0 • ios         • iOS 12.0 (simulator)

• No issues found!
```
Repository: angular
Issue: Add a customizable nonce attribute to injected style elements - CSP
Labels: feature,freq2: medium,security,area: core,area: security,core: stylesheets,cross-cutting: CSP,feature: under consideration

<!--
PLEASE HELP US PROCESS GITHUB ISSUES FASTER BY PROVIDING THE FOLLOWING INFORMATION.

ISSUES MISSING IMPORTANT INFORMATION MAY BE CLOSED WITHOUT INVESTIGATION.
-->

## I'm submitting a...
<!-- Check one of the following options with "x" -->
<pre><code>
[ ] Regression (a behavior that used to work and stopped working in a new release)
[ ] Bug report  <!-- Please search GitHub for a similar issue or PR before submitting -->
[ ] Performance issue
[x] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead see https://github.com/angular/angular/blob/master/CONTRIBUTING.md#question
[ ] Other... Please describe:
</code></pre>

## Current behavior
No ability to define nonce attribute on style tag.

## Expected behavior
I would like the ability to define a nonce generated on the server that angular will add to the inline styles.

## What is the motivation / use case for changing the behavior?
So that I can comply with business requirements not to use 'unsafe-inline' in CSP.

## Environment

<pre><code>
Angular version: 6.1.8

Browser:
- [x] Chrome (desktop) version 69
- [ ] Chrome (Android) version XX
- [ ] Chrome (iOS) version XX
- [ ] Firefox version XX
- [ ] Safari (desktop) version XX
- [ ] Safari (iOS) version XX
- [ ] IE version XX
- [ ] Edge version XX
 
For Tooling issues:
- Node version: 10.11.0
- Platform:  Windows 10

Others:
<!-- Anything else relevant?  Operating system version, IDE, package manager, HTTP server, ... -->
</code></pre>
Repository: go
Issue: cmd/go: get go list context function formatted as json
Labels: NeedsInvestigation,FeatureRequest,GoCommand

The `context` template function available to `go list` has some useful data, even after ignoring the overlap with `go env -json`. There's no way to output the `context` as json, making it hard to use the results programatically.

cc: @bcmills @rsc @ianlancetaylor @alandonovan
Repository: vscode
Issue: Breadcrumbs enhance-> double click change the edit state 
Labels: feature-request,breadcrumbs

Hi,
Waiting for this wonderful feature comes in about the Breadcrumbs.

now the Breadcrumbs is like this:
![image](https://user-images.githubusercontent.com/24240963/46183679-901e7200-c304-11e8-978f-75289a339b98.png)

If I double click this specific room and it will change to the edit state that make me be able to copy the path or manually modify the path and jump when out of focus (will remain unchanged if it does not exist).

I think this is more convenience way that I can get the path than others and more selective for quickly jump to anther file.

below is the edit state I am support to:
```
src/models/TodoModel.js( #method | $property )


// more config for this feature will make better, like this

// ( configName: type:default  -- notation )
// isShowAbsolutePath: boolean:false -- is showing the absolute path when the Breadcrumbs is edit 
state.
// isShowSuffix: boolean:true  -- is showing the previously cursor indicate the file (method / property...) when the Breadcrumbs is edit 
```

Thank you for consider this.
Repository: rust
Issue: fix false negatives in explicit_outlives_requirements 
Labels: A-lints,A-lifetimes,T-compiler,C-bug,L-explicit_outlives_requirements

Niko Matsakis [points out that](https://github.com/rust-lang/rust/pull/53013#discussion_r221053173) the explicit_outlives_requirements lint (from #53013, expected to land soon) should also fire on lifetime-outlives bounds and associated-type-outlives bounds, as illustrated by the following two examples:

```rust
struct Foo<'a, 'b: 'a> {
    x: &'a &'b u32
}

struct Bar<'a, T: Iterator> where T::Item: 'a {
    item: &'a T::Item,
}
```
Repository: pytorch
Issue: clip_grad_norm_ does not work on grads of different types
Labels: todo,module: nn,triaged

see
https://github.com/pytorch/pytorch/blob/117885128073c9c2b32f4b33c6c79df3895b7071/torch/nn/utils/clip_grad.py#L31-L34

example error message can be found at 
https://discuss.pytorch.org/t/error-when-doing-grad-clip-norm/26071/3

cc @albanD @mruberry @jbschlosser
Repository: opencv
Issue: Infrastructure: Python incorrect test summary
Labels: category: infrastructure

Builders indicate that Python have passed 0 tests, which is not correct.
Here is [an example build](http://pullrequest.opencv.org/buildbot/builders/precommit_linux64/builds/18369)

#### Actual summary
```
test_python2 test_python2 ; passed: 0 ; 
test_python3 test_python3 ; passed: 0 ; 
```

#### Expected summary
```
test_python2 test_python2 ; cases (tests): 64 (53) ; passed: 53 ; skipped: 11 ; 
test_python3 test_python3 ; cases (tests): 64 (53) ; passed: 53 ; skipped: 11 ; 
```
Repository: TypeScript
Issue: __importStar sometimes inlined when using dynamic imports with --importHelpers
Labels: Bug

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.1.1

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** __importStar tslib

**Code**
a.ts:
```ts
import('b').then(b => console.log(b));
```
compile with
```
tsc a.ts --esModuleInterop --importHelpers
```

**Expected behavior:**
some type errors, but emitted code should `require("tslib")` and use __importStar from there

**Actual behavior:**
some type errors and generated code looks like this:
```
var __importStar = (this && this.__importStar) || function (mod) {
    if (mod && mod.__esModule) return mod;
    var result = {};
    if (mod != null) for (var k in mod) if (Object.hasOwnProperty.call(mod, k)) result[k] = mod[k];
    result["default"] = mod;
    return result;
};
Promise.resolve().then(function () { return __importStar(require('b')); }).then(function (b) { return console.log(b); });
```

btw an example that works correctly:
```
import('c').then(b => console.log(b));

class Foo {}

export class Bar extends Foo {}
```
both the extends and the export seem to be necessary

**Playground Link:** N/A (--esModuleInterop doesn't exist in the playground)

**Related Issues:** This is basically #21560 but replacing regular imports with dynamic imports
Repository: opencv
Issue: Issue with cv::resize
Labels: category: imgproc,RFC,future

The function cv::resize behaves - from my perspective - incorrectly. Resizing images is not at all a trivial task, and I believe there is a misconception about scale and target image size.

My main issue is that when giving the size parameter, cv::resize ignores the size parameters and overrides them to (as documented) (𝚍𝚘𝚞𝚋𝚕𝚎)𝚍𝚜𝚒𝚣𝚎.𝚠𝚒𝚍𝚝𝚑/𝚜𝚛𝚌.𝚌𝚘𝚕𝚜 and (𝚍𝚘𝚞𝚋𝚕𝚎)𝚍𝚜𝚒𝚣𝚎.height/𝚜𝚛𝚌.row𝚜, respectively. It should not do that, but respect the scales given AND the 

A more natural way, which I understand would break a lot of old code and is thus difficult to introduce, would be changing the scales to the more correct (𝚍𝚘𝚞𝚋𝚕𝚎)(𝚍𝚜𝚒𝚣𝚎.𝚠𝚒𝚍𝚝𝚑-1)/(𝚜𝚛𝚌.𝚌𝚘𝚕𝚜-1), same for rows.

Therefore I propose to change cv::resize such that it does not ignore scale parameters when size is given.

Let me illustrate on an example:

Assume you have an image with 5x5 pixels. The most common interpretation of an image is that your image has 25 square pixels, sampled in the center of each pixel. That means, between the leftmost and rightmost pixels, there is a distance of FOUR (not five!) pixel widths. The image is 5 pixels wide, but the distance between the outermost pixels is only 4 pixels.

If I want to scale this image down by a factor 2 in either direction, I want to make the pixels double the size. By doing that, the distance between the outermost pixels should be 2 pixels (it was 4 before). Since the width of the image is one pixel larger, the target image width (and height) will be 3 afterwards. This can be done without extrapolation.

Now what does OpenCV do? Scaling from 5 to 3 pixels, it calculates this as a scaling factor of 3/5. That means, the pixels are made larger by a factor of 5/3. Now when sampling a grid of pixels with size 5/3 of the original pixels in the old grid, there's more than one way to do that. I can choose an offset in an interval of length 2/3 pixels, and get a valid interpolation for each. I haven't checked, most likely OpenCV chooses the center of this interval as offset. There's no way to choose the offset, but I'd like to be able to choose the scale factor so there is no degree of freedom (without extrapolation).

Now, I'm arguing that scaling an image by a factor 2, scaling from 5 to 3 pixels exactly fits, while scaling from 4 to 2 pixels does not. To some people, this might feel counterintuitive, but when considering images as a grid of square pixels, it is the natural interpretation.

Why is this so important for me? I don't just want to scale images down, I want to scale them up again. To the same size and same scale factors. If I scale with an exact factor not allowing for an offset for sampling the grid, I can do the same in the opposite direction. If I downsample with an offset, I need to extrapolate at upsampling, which I want to avoid.

My solution right now: cv::remap instead of cv::resize. But this really feels like a hack, and I don't see a reason why a function taking four parameters (counting cv::Size as two) ignores half of them... (and that it ignores them is not documented)
Repository: neovim
Issue: shada (viminfo) forgets marks, oldfiles
Labels: bug-regression,core,editor-state

- `nvim --version`:  

```
NVIM v0.3.2-dev
Build type: RelWithDebInfo
Lua 5.1
Compilation: /usr/bin/cc -g -O2 -fdebug-prefix-map=/build/neovim-1vOYWK/neovim-0.3.0~ubuntu1+git201809272035-64a8a8f-479a1d0=. -fstack-protector-strong -Wformat -Werror=format-security -Wconversion -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -g -DMIN_LOG_LEVEL=3 -Og -g -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -Wno-array-bounds -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -I/build/neovim-1vOYWK/neovim-0.3.0~ubuntu1+git201809272035-64a8a8f-479a1d0/build/config -I/build/neovim-1vOYWK/neovim-0.3.0~ubuntu1+git201809272035-64a8a8f-479a1d0/src -I/build/neovim-1vOYWK/neovim-0.3.0~ubuntu1+git201809272035-64a8a8f-479a1d0/.deps/usr/include -I/usr/include -I/build/neovim-1vOYWK/neovim-0.3.0~ubuntu1+git201809272035-64a8a8f-479a1d0/build/src/nvim/auto -I/build/neovim-1vOYWK/neovim-0.3.0~ubuntu1+git201809272035-64a8a8f-479a1d0/build/include
Compiled by buildd@lgw01-amd64-018

Features: +acl +iconv +jemalloc +tui
See ":help feature-compile"

   system vimrc file: "$VIM/sysinit.vim"
  fall-back for $VIM: "/usr/share/nvim"

```

- Operating system/version:  `Ubuntu 18.04.1 LTS \n \l`
- Terminal name/version: xfce4-terminal 0.8.7.4 (Xfce 4.12)
- `$TERM`: screen-256color (within tmux)

### Problem

Hello, sorry I don't think I can have a reproducible example, I don't know yet when the shada file is cleaned but it seems to be cleaned once in a while.

My shada settings are as follows : 

`shada='10000,<10000,s100,h,f1`

For some reason, once in a while (every 3 days maybe), it seems that my shada file is wiped.

The use case I have is that I use the `:oldfiles` command a lot to navigate to files that I have recently seen, however, the list keeps growing up to approximately 500 or so, and the next day, the list of oldfiles is back to something like 75.

Maybe this is because I'm doing some mismanipulation (I sometimes run nvim as root, and also sometimes use nvim -u NONE), could that be one cause of the issue ?

How can you help me debug this issue ?
Repository: TypeScript
Issue: Improve error message for incompatible signatures in union type from typed/untyped function call
Labels: Suggestion,Domain: Error Messages,Experience Enhancement

<!-- 🚨 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.

Cannot invoke an expression whose type lacks a call signature. Type '(() => string) | (T & Function)' has no compatible call signatures. [2349]
-->

## Search Terms  
untyped function call error message union type incompatible signature 

<!-- List of keywords you searched for before creating this issue. Write them down here so that others can find this suggestion more easily -->

## Example

This code errors as follows:
```ts
function foo<T>(x: T | (() => string)) {
    if (typeof x === "function") {
        let a = x();
             // ^ Cannot invoke an expression whose type lacks a call signature. 
             //Type '(() => string) | (T & Function)' has no compatible call signatures. [2349]
    }
}
```

which feels strange given that both of the following are fine:
```ts
function fooL<T>(x: T) {
    if (typeof x === "function") {
        let a = x();
    }
}

function fooR(x: () => string) {
    if (typeof x === "function") {
        let a = x();
    }
}
```

If an evaluation contexts accepts values of type `A` and values of type `B`, then it should accepts values of type `A | B`. I *think* what is going on is that the call signature from `T & Function` is *untyped*, which is incompatible with the *typed* signature of `() => string`.

I don't think this is very obvious to a user, and they end up seeing an application that works for both branches of a union, but not their composition.

## Suggestion

I think making the example work is out of scope. My suggestion is to improve the error message, something like:
```ts
function foo<T>(x: T | (() => string)) {
    if (typeof x === "function") {
        let a = x();
             // ^ Cannot invoke an expression whose type lacks a call signature. 
             // Type '(() => string) | (T & Function)' has no compatible call signatures. [2349]
             //   Cannot combine untyped function call with typed function call
    }
}
```

<!-- A summary of what you'd like to see added or changed -->


## 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. new expression-level syntax)
Repository: TypeScript
Issue: In JSDoc, `?` of conditional is frequently parsed as postfix-`?`
Labels: Bug

**TypeScript Version:**  3.2.0-dev.20180927
**Search Terms:** JSDoc conditional types

Using [Conditional Types](https://www.typescriptlang.org/docs/handbook/advanced-types.html#conditional-types) in JSDoc comments confuses the TypeScript parser since the `T extends Y ? A : B` syntax looks similar to the `Y?` (meaning `Y|null`) syntax from JSDoc.

**Code**

```js
/**
 * @template {{}} T
 * @param {T} o
 * @returns {T extends Readonly<infer U> ? (keyof U)[] : string[]}
 */
function Object_keys(o) {
	let keys = Object.keys(o);
	// @ts-ignore: Type assertion for stripping `Readonly<…>`
	return keys;
}
```

**Expected behavior:**

No error should be reported.
The type of `Object_keys` should be: `<T extends {}>(o: T): T extends Readonly<infer U> ? (keyof U)[] : string[]`.

**Actual behavior:**

TypeScript compiler shows an error (*"?" expected*) and mistakes the existing `?` operator for JSDoc `<type>|null` syntax.

The actual type therefor ends up being: `<T extends {}>(o: T): T extends Readonly<infer U> | null ? (keyof U)[] : string[]`.

**Possible fixes:**

 1. When encountering a top-level (not within parenthesis) `?` token in an extends clause, scan ahead and check whether it is followed by an `|` or `&` token (type intersection or union operators). If yes, treat it as `|null` and keep processing; otherwise, assume it's the start of a conditional type declaration. (Requires at least an LF(2) parser.)
  2. Prohibit the JSDoc `?` operator in the top-level of an extends clause, always causing it to be treated as the start of the conditional type declaration.

**Playground Link:** None, Playground does not seem to support JavaScript with JSDoc instead of TypeScript as input.
Repository: opencv
Issue: flann::Index::radiusSearch(): rename argument "radius" to "squaredRadius"
Labels: category: documentation,category: flann

##### System information (version)
- OpenCV => 3.4.1
- Operating System / Platform => Windows 64 Bit
- Compiler => VS15 x64

##### Detailed description
flann::Index::radiusSearch() expects the **squared** radius but the argument is called `radius`. 

This is also not clear in https://www.cs.ubc.ca/research/flann/uploads/FLANN/flann_manual-1.8.4.pdf. I just found a comment at 3.2.4 `flann_radius_search()`
Repository: create-react-app
Issue: Proposal: Additional JS pre-processing on module build
Labels: issue: proposal

As started in #5103, would like to propose a bit more of module processing than v2 is intended to have.

My first impression on module build was "finally, the same build for all the code!", but as I see it is not actually true, @gaearon [explained](https://github.com/facebook/create-react-app/issues/5103#issuecomment-425459196) that modules should be in a valid JavaScript format already.

Our **use case**: several projects depend on "core" package which was decided to use as a node module via git (not a git submodule for couple of reasons on convenience). Now have to build "core" project files with a separate script and Babel setup. It has some components, helpers, etc. And we want to have ability to use flat imports mainly. Components use JSX, which is not supported by module build as it figured out.

### Proposal: Additional JS pre-processing on module build

Let's have couple options I see for the consideration:

1. Ability to "turn on" same preprocessing for modules as current project already has.
2. Ability to add something to Babel "plugins" section (like "transform-react-jsx").
3. Ability to use those modules as is in application tests (see #5164 with example repos).

Those options would probably have a better use with ability to specify this for the "list of modules/mask", or "per module".
Repository: flutter
Issue: Offline mode needs to be extended to all flutter commands
Labels: c: new feature,tool,a: quality,P3,team-tool,triaged-tool

The `--offline` argument to `flutter packages get` is helpful in preventing packages from being downloaded, but since `flutter build` can also trigger getting packages, it needs to have a `--offline` added too.

Ideally, I'd like the main tool to have the --offline option, and have the individual commands accommodate it if they can. It may mean that if SDK tools need downloading that the command fails, or that additional options be added to allow specification of file locations that might be needed.

This is to assist people who not only want to work offline, but also people who want to build hermetic build systems that include Flutter, which is challenging right now because of the automatic download logic that the flutter tool contains.
Repository: TypeScript
Issue: Stack overflow within collectDynamicImportOrRequireCalls
Labels: Bug,Crash

**TypeScript Version:**  3.1.0-dev.20180925

```
git clone --depth=1 https://github.com/zuiidea/antd-admin.git
cd antd-admin
tsc --init
tsc --allowJs --checkJs
```

Compiler crashes with the callstack:

```
RangeError: Maximum call stack size exceeded
    at Object.isRequireCall (node_modules\typescript\lib\tsc.js:7304:27)
    at collectDynamicImportOrRequireCalls (node_modules\typescript\lib\tsc.js:69739:24)
    at visitNode (node_modules\typescript\lib\tsc.js:12689:24)
    at Object.forEachChild (node_modules\typescript\lib\tsc.js:12890:24)
    at collectDynamicImportOrRequireCallsForEachChild (node_modules\typescript\lib\tsc.js:69754:20)
    at collectDynamicImportOrRequireCalls (node_modules\typescript\lib\tsc.js:69748:17)
    at visitNode (node_modules\typescript\lib\tsc.js:12689:24)
    at Object.forEachChild (node_modules\typescript\lib\tsc.js:12890:24)
    at collectDynamicImportOrRequireCallsForEachChild (node_modules\typescript\lib\tsc.js:69754:20)
    at collectDynamicImportOrRequireCalls (node_modules\typescript\lib\tsc.js:69748:17)
```