sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: Provide a localized message for screenreaders for TextFields when character limit is exceeded
Labels: a: text input,platform-ios,framework,engine,f: material design,a: accessibility,a: internationalization,customer: mulligan (g3),c: proposal,P2,team-ios,triaged-ios

Internal: b/150477021

<!-- Thank you for using Flutter!

     If you are looking for support, please check out our documentation
     or consider asking a question on Stack Overflow:
      * https://flutter.dev/
      * https://api.flutter.dev/
      * https://stackoverflow.com/questions/tagged/flutter?sort=frequent

     If you have found a bug or if our documentation doesn't have an answer
     to what you're looking for, then fill our the template below. Please read
     our guide to filing a bug first: https://flutter.dev/docs/resources/bug-reports
-->

## Use case

When the number of characters exceeds the limit for say a TextFormField, it would be useful to have a standard localized message to communicate to how many characters the user is over by. Otherwise, for an A11y user it can be very difficult to understand what they have to do to correct the error unless we manually code this into our input fields.

## Proposal

Add a localized message that the screenreader announces when the character limit is exceeded in a textfield

cc @goderbauer @xster
Repository: kubernetes
Issue: HPA conversion serializes internal struct to annotation
Labels: kind/bug,priority/important-soon,sig/autoscaling,kind/api-change,lifecycle/frozen

**What happened**:
Found while fixing #88738 in #89963

The internal Spec.Behavior field is serialized to annotations when converting to v1 or v2beta1 HPA types. This causes several problems:
* The internal type does not have json tags, so the data is serialized upper-case
* The internal type is not guaranteed to preserve field layout/names, so the serialized data can become incompatible if that happens

To fix this, we should do something like the following:

1. Freeze the internal Behavior type schema
2. Update the unmarshaling in conversion to first try to unmarshal to a v2beta2 Behavior struct, and fall back to unmarshaling to an internal Behavior struct on error or if the result is an empty struct
3. Release
4. Update the marshaling in conversion to convert to a v2beta2 Behavior struct and marshal that to the annotation
5. Determine a way to force existing HPA objects with a serialized behavior annotation to remarshal on upgrade
6. Release
7. Unfreeze the internal Behavior type schema

@kubernetes/sig-autoscaling-api-reviews 
cc @DirectXMan12 @smarterclayton
Repository: neovim
Issue: Setting the timeoutlen on a per-mapping basis
Labels: enhancement,mappings

Say you `ino` re-mapped `hh` to `<Esc>` like some people do to be able to escape insert mode faster.

When you type text and end with `h`, like `mouth`, and want to escape insert mode right after, you end up having to wait for the timeout to occur.

I believe that being able to set the `timeoutlen` on a per-mapping setting would be a good customisation of neovim's behaviour.
Repository: go
Issue: x/build: missing failure output from windows-amd64-2008 builder
Labels: Builders,NeedsInvestigation

https://build.golang.org/log/59a049ac56f1c7dbcf9de1f6002512a70f765e0c is marked as a failure on the dashboard, but its output doesn't contain the word `FAIL` anywhere.

It's not obvious to me whether the test timed out, or failed without output. Better output from `cmd/dist` and/or the Builder infrastructure would probably help.

(CC @andybons @cagedmantis @toothrot @dmitshur)
Repository: vscode
Issue: Search does not respect `workbench.editor.revealIfOpen`
Labels: bug,search,confirmed

Selecting a search result will reveal an existing editor in an unfocused group even when `workbench.editor.revealIfOpen` is set to false.

Steps to Repro
* Set `workbench.editor.revealIfOpen` to false
* Open two editor groups
* Focus an editor in one of the groups
* Perform a search that will find results in the unfocused group (note that focus state is maintained while searching. The editor title color reflects this and `workbench.action.focusActiveEditorGroup` will focus the correct group).
* Select the result
* Notice it focuses the unfocused group instead of opening a new editor in the focused group
Repository: go
Issue: x/net/idna: adds 680KiB to binary when imported but unreferenced
Labels: NeedsInvestigation,binary-size

I'm working on a Go program in a severely constrained environment and found that I can save 680 KiB of disk (and disk == RAM in this environment) by making sure x/net/idna is never imported (even if unused).

That is, the init tasks for x/net/idna and its deps don't layout in memory such that the linker can discard enough:

```go
package main

import (
        _ "golang.org/x/net/idna"
)

func main() {
        println("hi")
}
```

It adds 680KiB to binary compared to just the `println("hi")` line without the import.

Linker says:

```
dev:underidna $ go build --ldflags=-dumpdep 2>&1 | grep idna
# _/home/bradfitz/tailscale/size-reduce/testidna/underidna
main..inittask -> golang.org/x/net/idna..inittask
golang.org/x/net/idna..inittask -> fmt..inittask
golang.org/x/net/idna..inittask -> strings..inittask
golang.org/x/net/idna..inittask -> golang.org/x/text/secure/bidirule..inittask
golang.org/x/net/idna..inittask -> golang.org/x/text/unicode/bidi..inittask
golang.org/x/net/idna..inittask -> golang.org/x/text/unicode/norm..inittask
golang.org/x/net/idna..inittask -> math..inittask
golang.org/x/net/idna..inittask -> golang.org/x/net/idna.init
golang.org/x/net/idna.init -> golang.org/x/net/idna.idnaSparse
golang.org/x/net/idna.init -> golang.org/x/net/idna.idnaSparseValues
golang.org/x/net/idna.init -> golang.org/x/net/idna.idnaSparseOffset
golang.org/x/net/idna.idnaSparseOffset -> golang.org/x/net/idna..stmp_8
golang.org/x/net/idna.idnaSparseValues -> type.[1997]golang.org/x/net/idna.valueRange
golang.org/x/net/idna.idnaSparse -> type.golang.org/x/net/idna.sparseBlocks
golang.org/x/net/idna..stmp_8 -> type.[276]uint16
type.golang.org/x/net/idna.sparseBlocks -> type..namedata.*idna.sparseBlocks-
type.golang.org/x/net/idna.sparseBlocks -> type.*golang.org/x/net/idna.sparseBlocks
type.golang.org/x/net/idna.sparseBlocks -> type..importpath.golang.org/x/net/idna.
type.golang.org/x/net/idna.sparseBlocks -> type..namedata.values-
type.golang.org/x/net/idna.sparseBlocks -> type.[]golang.org/x/net/idna.valueRange
type.*golang.org/x/net/idna.sparseBlocks -> type..namedata.lookup-
type.[]golang.org/x/net/idna.valueRange -> type..namedata.*[]idna.valueRange-
type.[]golang.org/x/net/idna.valueRange -> type.golang.org/x/net/idna.valueRange
type.golang.org/x/net/idna.valueRange -> type..namedata.*idna.valueRange-
type.golang.org/x/net/idna.valueRange -> type.*golang.org/x/net/idna.valueRange
type.[1997]golang.org/x/net/idna.valueRange -> type..eqfunc7988
type.[1997]golang.org/x/net/idna.valueRange -> type..namedata.*[1997]idna.valueRange-
```

/cc @randall77 @mpvl @rsc @ianlancetaylor
Repository: javascript
Issue: Misleading documentation 10.8
Labels: needs eslint rule change/addition

The documentation for [10.8](https://github.com/airbnb/javascript#modules--multiline-imports-over-newlines) references [`object-curly-newline`](https://github.com/airbnb/javascript#modules--multiline-imports-over-newlines) however object-curly-newline does not catch this rule. Furthermore airbnb's set of rules also doesn't catch this rule.

See [Example](https://eslint.org/demo#eyJ0ZXh0IjoiaW1wb3J0IHtmb28sIFxuICAgICAgICBiYXIsIGJheiwgYmFuZ30gZnJvbSAnZm9vLWJhcic7XG5cbmNvbnN0IHRoaW5nID0ge1xuICBmaXJzdCA6IGZvbyxcbiAgc2Vjb25kIDogYmFyLCBcbiAgdGhpcmQgOiBiYXosIGZvdXJ0aCA6IGJhbmdcbn1cblxuY29uc3QgbGlzdCA9IFtcbiAgZm9vLFxuICBiYXIsXG4gIGJheiwgYmFuZ1xuXTtcblxuKGxpc3QhPT10aGluZykiLCJvcHRpb25zIjp7InBhcnNlck9wdGlvbnMiOnsiZWNtYVZlcnNpb24iOjExLCJzb3VyY2VUeXBlIjoibW9kdWxlIiwiZWNtYUZlYXR1cmVzIjp7fX0sInJ1bGVzIjp7ImNvbnN0cnVjdG9yLXN1cGVyIjoyLCJmb3ItZGlyZWN0aW9uIjoyLCJnZXR0ZXItcmV0dXJuIjoyLCJuby1hc3luYy1wcm9taXNlLWV4ZWN1dG9yIjoyLCJuby1jYXNlLWRlY2xhcmF0aW9ucyI6Miwibm8tY2xhc3MtYXNzaWduIjoyLCJuby1jb21wYXJlLW5lZy16ZXJvIjoyLCJuby1jb25kLWFzc2lnbiI6Miwibm8tY29uc3QtYXNzaWduIjoyLCJuby1jb25zdGFudC1jb25kaXRpb24iOjIsIm5vLWNvbnRyb2wtcmVnZXgiOjIsIm5vLWRlYnVnZ2VyIjoyLCJuby1kZWxldGUtdmFyIjoyLCJuby1kdXBlLWFyZ3MiOjIsIm5vLWR1cGUtY2xhc3MtbWVtYmVycyI6Miwibm8tZHVwZS1rZXlzIjoyLCJuby1kdXBsaWNhdGUtY2FzZSI6Miwibm8tZW1wdHkiOjIsIm5vLWVtcHR5LWNoYXJhY3Rlci1jbGFzcyI6Miwibm8tZW1wdHktcGF0dGVybiI6Miwibm8tZXgtYXNzaWduIjoyLCJuby1leHRyYS1ib29sZWFuLWNhc3QiOjIsIm5vLWV4dHJhLXNlbWkiOjIsIm5vLWZhbGx0aHJvdWdoIjoyLCJuby1mdW5jLWFzc2lnbiI6Miwibm8tZ2xvYmFsLWFzc2lnbiI6Miwibm8taW5uZXItZGVjbGFyYXRpb25zIjoyLCJuby1pbnZhbGlkLXJlZ2V4cCI6Miwibm8taXJyZWd1bGFyLXdoaXRlc3BhY2UiOjIsIm5vLW1pc2xlYWRpbmctY2hhcmFjdGVyLWNsYXNzIjoyLCJuby1taXhlZC1zcGFjZXMtYW5kLXRhYnMiOjIsIm5vLW5ldy1zeW1ib2wiOjIsIm5vLW9iai1jYWxscyI6Miwibm8tb2N0YWwiOjIsIm5vLXByb3RvdHlwZS1idWlsdGlucyI6Miwibm8tcmVkZWNsYXJlIjoyLCJuby1yZWdleC1zcGFjZXMiOjIsIm5vLXNlbGYtYXNzaWduIjoyLCJuby1zaGFkb3ctcmVzdHJpY3RlZC1uYW1lcyI6Miwibm8tc3BhcnNlLWFycmF5cyI6Miwibm8tdGhpcy1iZWZvcmUtc3VwZXIiOjIsIm5vLXVuZGVmIjoyLCJuby11bmV4cGVjdGVkLW11bHRpbGluZSI6Miwibm8tdW5yZWFjaGFibGUiOjIsIm5vLXVuc2FmZS1maW5hbGx5IjoyLCJuby11bnNhZmUtbmVnYXRpb24iOjIsIm5vLXVudXNlZC1sYWJlbHMiOjIsIm5vLXVudXNlZC12YXJzIjoyLCJuby11c2VsZXNzLWNhdGNoIjoyLCJuby11c2VsZXNzLWVzY2FwZSI6Miwibm8td2l0aCI6MiwicmVxdWlyZS15aWVsZCI6MiwidXNlLWlzbmFuIjoyLCJ2YWxpZC10eXBlb2YiOjIsIm9iamVjdC1jdXJseS1uZXdsaW5lIjoyLCJvYmplY3QtY3VybHktc3BhY2luZyI6Miwib2JqZWN0LXByb3BlcnR5LW5ld2xpbmUiOjIsImFycmF5LWJyYWNrZXQtbmV3bGluZSI6MiwiYXJyYXktYnJhY2tldC1zcGFjaW5nIjoyLCJhcnJheS1lbGVtZW50LW5ld2xpbmUiOjJ9LCJlbnYiOnt9fX0=) 

The guidance is good, however the documentation leads you to believe the linter will catch you if you put imports on the same line, which it doesn't.
Repository: TypeScript
Issue: Enhance event type of ServiceWorker `onstatechange` listener
Labels: Bug,Domain: lib.d.ts

<!-- 🚨 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 the latest published version. It may have already been fixed.
For npm: `typescript@next`
This is also the 'Nightly' version in the playground: http://www.typescriptlang.org/play/?ts=Nightly
-->
**TypeScript Version:**  3.8.3

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**
- serviceworker listener
- serviceworker statechange
- serviceworker typing
- serviceworker onstatechange

**Code**

The current master branch is still with the issue:
https://github.com/microsoft/TypeScript/blob/126c6ab80d2dca28d4a3d1889f19ad3504c1f74d/lib/lib.dom.d.ts#L14872

```ts
registration.wait.addEventListener('statechange', (event) => {
  console.log(event?.target?.state);
}
```

**Expected behavior:**
Above `event.target` is `ServiceWorker` type

**Actual behavior:**
Above `event.target` is `EventTarget` type
```
Property 'state' does not exist on type 'EventTarget'.
```

**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: godot
Issue: [Bullet] 3d physics stepping is two frames late for bullet physics
Labels: bug,confirmed,topic:physics,topic:3d

**Godot version:**

3.2.1-stable

**OS/device including version:**

Mac

**Issue description:**

3d physics stepping is two frames late using bullet physics. Expected would be that it is one frame late.

**Steps to reproduce:**

Apply either velocity or force to a 3d rigid body. You will notice that the object moves two frames after you apply the velocity.

**Minimal reproduction project:**

Create a 3d scene and add rigid body with this script.

```gdscript
extends RigidBody

var frame = 0

func _ready():
	pass # Replace with function body.

func _physics_process(delta):
	match frame:
		10:
			linear_velocity = Vector3(1,0,0)
		12:
			linear_velocity = Vector3(0,0,0)

	force_update_transform()
	print("frame: " + str(frame) + " vel " + str(linear_velocity) +" " + str(transform.origin))

	frame += 1
```

The output is 

```
frame: 9 vel (0, 0, 0) (0, 0, 0)
frame: 10 vel (1, 0, 0) (0, 0, 0)
frame: 11 vel (1, 0, 0) (0, 0, 0)
frame: 12 vel (0, 0, 0) (0.1, 0, 0)
frame: 13 vel (0, 0, 0) (0.2, 0, 0)
frame: 14 vel (0, 0, 0) (0.2, 0, 0)
```

Expected would be that body has moved at frame 11.

** Note **

Using godot physics is the update is only one frame late. Hence bullet physics works differently.

Create equivalent script for 2d. You will notice that the body moves on frame 11. Hence, 2d physics works correctly.
Repository: material-ui
Issue: [RFC] Chip markup
Labels: accessibility,discussion,component: chip,RFC

Regarding https://material-ui.com/components/chips/#chip-2

## Problem

Chips currently have both a bad a11y and UX story:
- delete action is inaccessible on iOS devices (and requires knowledge of keyboard shortcuts in any other screen reader)
- deleteable Chips are announced as buttons
- clicking the delete icon triggers the same ripple as clicking the Chip itself. The ripple shouldn't bubble to elements that are not activated.
- a deleteable button is by default selectable but not a basic Chip. Why?
- demos illustrates a trailing icon that is not used as the delete action. Having it trigger onDelete is misleading (adressed in #16097)

## Current implementation

This uses terminology from the accessibility tree. A `<button>` does not necessarily represent a `HTMLButtonElement`

- Basic: `<generic tabindex="-1">Basic</generic>`
- clickable: `<button>Clickable</button>`
- deleteable: `<button>Deleteable <SVGRoot aria-hidden="true" focusable="false">...</SVGRoot></button>`
- deletable + clickable: `<button tabindex="0">Clickable deleteable <SVGRoot aria-hidden="true" focusable="false">...</SVGRoot></button>`

## Proposal

- don't nest interactive elements
- whether the delete action should be in tab order is a hard question. I lean towards having it in tab order and making it easily customizale (for grid-like implementations or Autocomplete)

### Basic
```diff
-<generic tabindex="-1">Basic</generic>
+<generic>Basic</generic>
```
### Clickable
These are fine.

### deleteable
```diff
-<button>Deleteable <SVGRoot aria-hidden="true" focusable="false">...</SVGRoot></button>
+<generic>Deleteable<button><SVGRoot>...</SVGRoot></button></generic>
```
### deletable + clickable
```diff
-<button tabindex="0">Clickable deleteable <SVGRoot aria-hidden="true" focusable="false">...</SVGRoot></button>
+<generic><button tabindex="0">Clickable deleteable</button><button tabindex="0"><SVGRoot aria-hidden="true" focusable="false">...</SVGRoot></button></generic>
```

## Context
#17708
Closes #19468
Repository: flutter
Issue: Assert that timeline events are sorted in the Flutter driver
Labels: tool,t: flutter driver,c: proposal,P3,team-tool,triaged-tool

Observatory should sort the timeline events before we decide to assert
Repository: go
Issue: runtime/pprof: TestCPUProfileLabel is flaky on aix-ppc64
Labels: Builders,NeedsInvestigation,OS-AIX,compiler/runtime

[2020-04-08T18:37:38-d5e1b7c/aix-ppc64](https://build.golang.org/log/1b609fea568da538d9a0f53ea44c16b37dde01b8)
[2020-03-17T01:24:51-7ec4adb/aix-ppc64](https://build.golang.org/log/67294431057b77bc013c73313025b5462c29398e)
[2019-12-20T20:12:18-b234fdb/aix-ppc64](https://build.golang.org/log/1ad954ec72490dbd3d8e36a82da5453cf4ae5cd4)
[2019-11-19T19:21:57-e0306c1/aix-ppc64](https://build.golang.org/log/533ca5f7f8ff334f011d8c8822d324b4ac2453d6)
[2019-09-26T17:37:02-a37f2b4/aix-ppc64](https://build.golang.org/log/c2b1566354f26d77038d3cddf3ba182b1dc1b577)

Not clear to me whether this is a builder issue, an AIX platform issue, or a timing-sensitive test.

CC @hyangah for `pprof`, @trex58 @Helflym for `aix`, @andybons @toothrot @cagedmantis @dmitshur for builders.
Repository: flutter
Issue: [web] Write e2e comprehensive test for pointers
Labels: a: tests,team,framework,platform-web,P2,team-web,triaged-web

Given the relatively high number of pointer-related regressions we've had in the past, it's important to have e2e tests for it. Some regressions were desktop-only (e.g. [right-click](https://github.com/flutter/engine/pull/15103)), some were mobile-only (e.g. [semantics placeholder](https://github.com/flutter/engine/pull/17595)), and some affected both (e.g. [pointer data sanitization](https://github.com/flutter/engine/pull/14082)).

#### Requirements
* The test has to send real browser events, not framework events.

#### Scenarios
* Clicking/tapping
* Hovering
* Dragging
* Right-clicking (context menu)
* Scrolling (wheel events)

The unit tests in `pointer_binding_test.dart` have a lot of edge cases that have regressed before.
Repository: TypeScript
Issue: the type of super() should be instance, not void
Labels: Needs Investigation,Has Repro

**TypeScript Version:**  3.8.3

**Search Terms:**

**Code**

```ts
class Sub extends Super {
  constructor () { return super(); }
}
```

**Expected behavior:** no error

**Actual behavior:** `TS2322`

**Playground Link:**

**Related Issues:**
Repository: angular
Issue: Ivy: :leave animations trigger when navigating away from component
Labels: area: animations,state: confirmed,state: needs more investigation,P3

# 🐞 Bug report

### Affected Package
@angular/animations (presumably)

### Is this a regression?
No, happens in all versions of 9.x with Ivy enabled.

### Description
When an animation query is specified with `:leave`, it should only fire when an item is added/removed per the documentation. In 9.x with Ivy enabled, however, all `:leave` animations fire whenever the component is navigated away from, even though nothing is being added/removed. This is especially annoying because the new component won't load until the animations have finished.

You can disable Ivy in the repro and see that it does what you would expect--`:leave` doesn't fire when navigating away from the component.

## 🔬 Minimal Reproduction
https://stackblitz.com/edit/angular-udwujp

## 🔥 Exception or Error
N/A

## 🌍  Your Environment

**Angular Version:**
<pre><code>Angular CLI: 9.1.1
Node: 13.12.0
OS: win32 x64

Angular: 9.1.1
... animations, cli, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router
Ivy Workspace: Yes

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.901.1
@angular-devkit/build-angular     0.901.1
@angular-devkit/build-optimizer   0.901.1
@angular-devkit/build-webpack     0.901.1
@angular-devkit/core              9.1.1
@angular-devkit/schematics        9.1.1
@ngtools/webpack                  9.1.1
@schematics/angular               9.1.1
@schematics/update                0.901.1
rxjs                              6.5.5
typescript                        3.8.3
webpack                           4.42.0
</code></pre>

**Anything else relevant?**
N/A
Repository: opencv
Issue: I tried to write json data larger than 10k to FileStorage, but the write failed.why? help?
Labels: feature,priority: low,category: core

##### System information (version)
- OpenCV => 4.2
- Operating System / Platform => Windows 64 Bit
- Compiler => Visual Studio 2017

##### Detailed description

I tried to write json data larger than 10k to FileStorage, but the write failed.why? help?

##### Steps to reproduce
I tried to write json data larger than 10k to FileStorage, but the write failed.

    ```.cpp
    bool writeCacheJson(const std::string &filePath, const std::string &key, std::string &content) {
        if(content.empty() || key.empty()){
            return false;
        }
        std::string file = filePath + "/facepp_landmark.json";
        try {
            cv::FileStorage fs(file, cv::FileStorage::WRITE | cv::FileStorage::MEMORY);
            if (!fs.isOpened()) {
                std::cerr << "cannot open " << file << " for write" << std::endl;
                return false;
            }
            std::string json = std::string(content);
            fs.write(key, json);
            fs.release(); // 关闭文件，释放内存
        } catch (...) {
            std::cerr << "cannot open facepp_landmark.json for write" << std::endl;
            return false;
        }
        return true;
    }
    ```


error:OpenCV(3.4.6) /Volumes/build-storage/build/3_4_iOS-mac/opencv/modules/core/src/persistence_json.cpp:837: error: (-5:Bad argument) The written string is too long in function 'icvJSONWriteString'

Is there any other solution？
Repository: vscode
Issue: Create a data science "working group"
Labels: question-discussion

Refs: #93604

There was a request from the March Extension Authors call to create a sort of working group of data science extension authors (Julia, R, Python, etc) to share and collaborate on cross-cutting requirements and for VS Code to learn in be informed from the baseline infrastructure required for VS Code to support innovation in the data science space.

/cc @davidanthoff
Repository: rust
Issue: [mir-opt] New optimization: eliminate concrete type -> trait object conversions
Labels: T-compiler,C-feature-request,A-coercions,A-mir-opt,A-trait-objects

Basically I am suggesting to turn

```rust
let x = SomeStruct;
let y: &dyn SomeTrait = &x;
y.some_method();
```

into

```rust
let x = SomeStruct;
let y: &SomeStruct = &x;
x.some_method()
```

While the above code is likely never written, you can easily get this after inlining some function that e.g. returns a `Box<dyn Trait>` where the type that was turned into a trait object is always the same. I case the function is a trait method, we can't change the function into one returning `impl Trait`. This optimization would do the transformation for us.

cc @rust-lang/wg-mir-opt
Repository: opencv
Issue: [OpenCL] Support for INTER_CUBIC resize
Labels: optimization,feature,category: imgproc,category: ocl

I tested INTER_CUBIC resize on my PC.
- OpenCV 3.4.5
- Win10 , Intel UHD 620
- Visual Studio 2017

With 720P input and 4K output,  I got the report below.
- 12.09ms in case IPP is enabled
-  26.55ms in case IPP is disabled

Then I tried to use UMAT to speed up by OpenCL, but nothing happened.

I found the conditional statement in function `ocl_resize` which means INTER_CUBIC is not supported.
```    
if( !(cn <= 4 &&
           (interpolation == INTER_NEAREST || interpolation == INTER_LINEAR ||
            (interpolation == INTER_AREA && inv_fx >= 1 && inv_fy >= 1) )) )
        return false;
```

Is there a plan to add INTER_CUBIC to OpenCL function `resize.cl`?