sharjeelyunus/github-issues-dataset huggingface dataset:
Repository: flutter
Issue: The height of statusbar return 0.0 when running below IOS 11 system 
Labels: platform-ios,framework,engine,e: OS-version specific,P2,team-ios,triaged-ios

I tested the statusbar height in different versions of the IOS system, the system below IOS 11 would got the problem that the statusbar height is 0.0.
Repository: opencv
Issue: python grabcut sample input window, issue with pop-up 
Labels: category: highgui-gui,category: samples,incomplete

##### System information (version)
- OpenCV => 3.4.3
- Operating System / Platform => Ubuntu 64 Bit
- Compiler => Ananconda

##### Detailed description
If anyone tries to play with the python grabcut sample demo from samples/python/grabcut.py, it does not work as expected. The expected functionality is to be able to draw a rectangle using right mouse button in the input window. But the right mouse button is also tied to the help pop up for the window. So the right button-down is not registered properly.


##### Steps to reproduce
Just run the code samples/python/grabcut.py using the latest version. 

##### Solution
Replace this line (121);
 ```.py
cv.namedWindow('input')
```
with this line:
```.py
cv.namedWindow('input', cv.WINDOW_GUI_NORMAL) 
```
Repository: flutter
Issue: BlendMode.multiply and BlendMode.modulate are swapped
Labels: engine,dependency: skia,has reproducible steps,P2,team-engine,triaged-engine,found in release: 3.19,found in release: 3.21

i have the custom `CustomPainter` class:

```dart
class BlendPainter extends CustomPainter {
  ui.Image image, mask;

  BlendPainter(this.image, this.mask);

  @override
  void paint(Canvas canvas, Size size) {
    Rect r = Offset.zero & size;
    Paint paint = Paint();

    if (image != null && mask != null) {
      Size inputSize = Size(mask.width.toDouble(), mask.height.toDouble());
      FittedSizes fs = applyBoxFit(BoxFit.contain, inputSize, size);

      Rect src = Offset.zero & fs.source;
      Rect dst = Alignment.center.inscribe(fs.destination, r);

      canvas.saveLayer(dst, Paint());
      canvas.drawImageRect(image, src, dst, paint);

      // paint.blendMode = BlendMode.multiply;
      paint.blendMode = BlendMode.modulate;

      canvas.drawImageRect(mask, src, dst, paint);
      canvas.restore();
    }
  }

  @override
  bool shouldRepaint(CustomPainter oldDelegate) => true;
}
```
and for `image`:

![image](https://user-images.githubusercontent.com/5962376/47258889-7a830f00-d4a2-11e8-859f-cf01fa7da5b5.png)

and `mask`:

![mask](https://user-images.githubusercontent.com/5962376/47258880-5fb09a80-d4a2-11e8-8afe-b1a7d1f8b9b5.png)

i got the following result for `BlendMode.multiply`:

![multiply](https://user-images.githubusercontent.com/5962376/47264578-0f751f00-d51a-11e8-9e22-0b5e99997890.png)

and `BlendMode.modulate`:

![modulate](https://user-images.githubusercontent.com/5962376/47264583-1c920e00-d51a-11e8-8c78-c94ca0e59d43.png)

i am pretty sure that `BlendMode.multiply` should also multiply the alphas of both images so the result should not be round rectangle - this leads me to the conclusion that those both modes are swapped or something
Repository: TypeScript
Issue: Property ? is missing in wrong type
Labels: Bug

I'm seeing a regression where code that works in 3.1 does not work in tsnext. It seems like typescript is not looking at the right type (`ContourTransform`) and tried to match against a different type (`WordcloudTransform`).

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  @next (3.2) but not 3.1

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:** Property ? is missing in type

**Code**

https://github.com/vega/vega-typings/blob/master/tests/spec/examples.ts#L3394

**Expected behavior:**

The tests should not fail and they work fine in ts 3.1. 

**Actual behavior:**

https://travis-ci.org/vega/vega-typings/jobs/444180003

```
ERROR: 3394:3  expect  TypeScript@next compile error: 
Type '({ name: string; url: string; transform: { type: "filter"; expr: string; }[]; } | { name: string; source: string; transform: { type: "contour"; x: { expr: string; }; y: { expr: string; }; size: { signal: string; }[]; count: { ...; }; }[]; })[]' is not assignable to type 'Data[]'.
  Type '{ name: string; url: string; transform: { type: "filter"; expr: string; }[]; } | { name: string; source: string; transform: { type: "contour"; x: { expr: string; }; y: { expr: string; }; size: { signal: string; }[]; count: { ...; }; }[]; }' is not assignable to type 'Data'.
    Type '{ name: string; source: string; transform: { type: "contour"; x: { expr: string; }; y: { expr: string; }; size: { signal: string; }[]; count: { signal: string; }; }[]; }' is not assignable to type 'Data'.
      Type '{ name: string; source: string; transform: { type: "contour"; x: { expr: string; }; y: { expr: string; }; size: { signal: string; }[]; count: { signal: string; }; }[]; }' is not assignable to type '{ url: string | SignalRef; } & { name: string; on?: OnTrigger[] | undefined; format?: FormatJSON | FormatSV | FormatDSV | ({ type: "topojson"; property?: string | undefined; } & { ...; }) | ({ ...; } & { ...; }) | { ...; } | SignalRef | undefined; transform?: Transform[] | undefined; }'.
        Type '{ name: string; source: string; transform: { type: "contour"; x: { expr: string; }; y: { expr: string; }; size: { signal: string; }[]; count: { signal: string; }; }[]; }' is not assignable to type '{ url: string | SignalRef; }'.
          Property 'url' is missing in type '{ name: string; source: string; transform: { type: "contour"; x: { expr: string; }; y: { expr: string; }; size: { signal: string; }[]; count: { signal: string; }; }[]; }'.
```
Repository: go
Issue: x/build/cmd/gopherbot: reply to commit comments saying we do not monitor them
Labels: Builders,FeatureRequest

We get from time to time a comment on a commit in the main repo. We do not monitor those and nobody gets a ping for them (except the author of the commit who might or might not check GitHub notifications and does not have to). gopherbot should reply automatically pointing them towards the issue tracker and https://github.com/golang/go/wiki/Questions.

(Almost sure there was an issue for this, but couldn't find it. Please close as dup if anyone does.)
Repository: rust
Issue: Unable to trace an crash from the backtrace, no trace for my own code
Labels: T-libs-api,O-windows-msvc,C-bug

Windows, use msvc toolchain, release build and config ‘debug = true’ in [profile.release], and marked #[inline(never)]
the problem is unable to trace an crash from the backtrace, no trace for my own code.
while debug build backtrace works, can find my own code line

```
rustc 1.29.1 (b801ae664 2018-09-20)
cargo 1.29.0 (524a578d7 2018-08-05)

the trace is below:

PS D:\rust-projects\hello_cargo\target\release> $env:RUST_BACKTRACE=1
PS D:\rust-projects\hello_cargo\target\release> .\hello_cargo.exe
The value of x is: 5
thread ‘main’ panicked at ‘Not a number!: ParseIntError { kind: InvalidDigit }’, libcore\result.rs:945:5
stack backtrace:
0: std::sys::windows::backtrace::set_frames
at C:\projects\rust\src\libstd\sys\windows\backtrace\mod.rs:104
1: std::sys::windows::backtrace::set_frames
at C:\projects\rust\src\libstd\sys\windows\backtrace\mod.rs:104
2: std::sys_common::backtrace::_print
at C:\projects\rust\src\libstd\sys_common\backtrace.rs:71
3: std::sys_common::backtrace::_print
at C:\projects\rust\src\libstd\sys_common\backtrace.rs:71
4: std::panicking::default_hook::{{closure}}
at C:\projects\rust\src\libstd\panicking.rs:211
5: std::panicking::default_hook
at C:\projects\rust\src\libstd\panicking.rs:227
6: std::panicking::rust_panic_with_hook
at C:\projects\rust\src\libstd\panicking.rs:475
7: std::panicking::continue_panic_fmt
at C:\projects\rust\src\libstd\panicking.rs:390
8: std::panicking::rust_begin_panic
at C:\projects\rust\src\libstd\panicking.rs:325
9: core::panicking::panic_fmt
at C:\projects\rust\src\libcore\panicking.rs:77
10: core::result::unwrap_failedcore::num::ParseIntError
at C:\projects\rust\src\libcore\macros.rs:26
11: core::result::Result<u32, core::num::ParseIntError>::expect
at C:\projects\rust\src\libcore\result.rs:809
12: core::result::Result<u32, core::num::ParseIntError>::expect
at C:\projects\rust\src\libcore\result.rs:809
13: std::rt::lang_start::{{closure}}<()>
at C:\projects\rust\src\libstd\rt.rs:74
14: std::rt::lang_start_internal::{{closure}}
at C:\projects\rust\src\libstd\rt.rs:59
15: std::rt::lang_start_internal::{{closure}}
at C:\projects\rust\src\libstd\rt.rs:59
16: panic_unwind::__rust_maybe_catch_panic
at C:\projects\rust\src\libpanic_unwind\lib.rs:105
17: std::panicking::try
at C:\projects\rust\src\libstd\panicking.rs:289
18: std::panicking::try
at C:\projects\rust\src\libstd\panicking.rs:289
19: std::panicking::try
at C:\projects\rust\src\libstd\panicking.rs:289
20: main
21: invoke_main
at f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:78
22: invoke_main
at f:\dd\vctools\crt\vcstartup\src\startup\exe_common.inl:78
23: BaseThreadInitThunk
24: RtlUserThreadStart
```
Repository: TypeScript
Issue: language service suggestion for Declare property '...' in constructor argument
Labels: Suggestion,Domain: Quick Fixes,Experience Enhancement

## Search Terms
- typescript declare property in constructor
- typescript language service declare property in constructor
## Suggestion
When a non-existing property `x` is accessed on `this` in a class method,  one of the fixes that ts language service currently suggests, is:

> Declare property x

Which adds property `x` to the class.
It would be nice to also have **Declare property x in constructor arguments**. 
It can use `private` access modifier by default.

## Use Cases
While it's generally useful, it becomes especially handy when developing applications with DI frameworks like Angular that use constructor injection to wire dependencies together.

## Examples
\-
## 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: rust
Issue: Derived trait shadows a blanket default impl, specialization unshadows but the generic impl ends up being used
Labels: T-compiler,A-specialization,C-bug,requires-nightly,F-specialization

This example does not compile with 1.31.0-nightly (2018-10-20 155510e377ae2a8d8ee0):

```rust
#![feature(specialization)]

use std::borrow::Borrow;

#[derive(PartialEq)]
struct MyString(String);

impl Borrow<str> for MyString {
    fn borrow(&self) -> &str {
        &self.0
    }
}

impl<Rhs> PartialEq<Rhs> for MyString
where
    Rhs: ?Sized + Borrow<str>,
{
    default fn eq(&self, rhs: &Rhs) -> bool {
        println!("default impl used");
        self.0 == rhs.borrow()
    }
}

#[cfg(never)]
impl PartialEq<str> for MyString {
    fn eq(&self, other: &str) -> bool {
        println!("specialized impl used");
        self.0 == other
    }
}

fn main() {
    let s = MyString(String::from("Hello, world!"));
    println!("{}", s == "Здравствуй, мир!");
}
```

The error output:

```
error[E0308]: mismatched types
  --> src/main.rs:34:25
   |
34 |     println!("{}", s == "Здравствуй, мир!");
   |                         ^^^^^^^^^^^^^^^^^^ expected struct `MyString`, found reference
   |
   = note: expected type `MyString`
              found type `&'static str`
```

Enabling the specialized `impl PartialEq<str>` makes the example work, but it prints "default impl used".

Removing the `derive` attribute also fixes the example, but only if the manually specialized impl is not present.
Repository: TypeScript
Issue: API about Identifier's scope
Labels: Suggestion,API,Experience Enhancement

I want to write a CustomTransformers for my webpack loader config.

Babel's visitors have API about [scope](https://www.henryzoo.com/babel.github.io/docs/advanced/plugins/scope/)
If I get a path of ImportDeclaration `import * as React from "react"`, I can using  `path.scope.getBinding('React').referencePaths` to get all reference paths using React.

Is there any API in TypeScript to get identifier's **scope** or **referenced nodes/identifiers**?

Also, Is there any API in TypeScript to get  ImportDeclaration's moduleSpecifier's *resolved source file*? for example `import * as React from "react"`'s resolved source file is `/home/me/my-ts-project/node_modules/react/cjs/react.development.js`
Repository: terminal
Issue: Reading extended attributes (RGB colors) from the screen buffer
Labels: Issue-Feature,Product-Conhost,Area-Server

TL;DR: How?

Scenario: an app needs to read a part of the screen buffer, output something, and then, when needed, restore the original buffer content.

ReadConsoleOutput always worked seamlessly for that, but now Windows supports 256 colours, true colours and underline text, but CHAR_INFO.Attributes is still WORD and obviously can't hold all that luxury.

I remember reading somewhere that you don't have plans to extend output APIs (WriteConsoleOutput and friends) because it can be achieved with VT sequences (with limitations, inconvenience, more work, but, technically - yes, it can), but what about reading?

I tried to search first and found [this](https://github.com/Microsoft/console/issues/88#issuecomment-387777464) comment, but I don't think that #57 would help here - no 3rd-party terminals involved in this case, we're reading purely static data.


![screen](https://user-images.githubusercontent.com/11453922/47342037-8cc79d80-d69a-11e8-83b8-d9d12747d7b4.png)
Repository: opencv
Issue: JavaScript fastNlMeansDenoising() Support
Labels: feature,priority: low,category: photo,category: javascript (js)

##### System information (version)

- OpenCV => 3.4.3 (opencv.js)
- Operating System / Platform => Ubuntu 17.10 - x86_64 GNU/Linux
- Compiler => chrome engine ( web browser )

##### Detailed description

I faced this error when i use fastNlMeansDenoising() method:
`Uncaught TypeError exception: cv.fastNlMeansDenoising() is not a function`

##### Steps to reproduce

```
let src = imread(IMG_SRC);
let dst = cv.fastNlMeansDenoising(src,None,10,10,7,21);
imshow('DST_ELEMENT_ID, dst);
```

##### Request

its helpful to present a denoising method for javascript version (not mentioned in documents)
Repository: godot
Issue: Incorrect texture UV for Label (glyphs' UVs are used instead of label's)
Labels: bug,topic:rendering,confirmed,topic:gui

**Godot version:**
3.0.6


**OS/device:**
Windows 8.1, Toshiba Satellite


**Issue description:**
For shaders attached to Labels, UV is not as expected. If you attach a shader to a Label and try to do a simple vertical gradient on it, UV.y = 1.0 does not correspond to the bottom of the Label.


**Steps to reproduce:**
1. Create a Label.
2. Add a dynamic font of your choosing.
2. Attach the following shader.
3. Observe that the bottom of the text does not have color (1.0, 0.0, 0.0), as would be expected at UV = 1.0.
4. The multiplier must be changed to around 10.0 in order to see the expected gradient.

```
shader_type canvas_item;
render_mode unshaded;

// One would expect UV.y = 1.0 to correspond to the bottom of the text.
// This does not seem to be the case, as the bottom of the text is not pure red.
// You must change the multiplier to around 10.0 in order to see the desired gradient.

uniform float multiplier = 1.0; 

void fragment()
{
float texture_alpha = texture(TEXTURE, UV).a;

if (texture_alpha > 0.0)
{
	COLOR = vec4(UV.y * multiplier, 0.0, 0.0, texture_alpha);
}

else
{ 
	COLOR = texture(TEXTURE, UV);
}

}
```

**Minimal reproduction project:**
[ExampleProject.zip](https://github.com/godotengine/godot/files/2499944/ExampleProject.zip)
Repository: vscode
Issue: Expanding emmet abbreviations inside JSX inline functions not working
Labels: bug,emmet

Issue Type: <b>Bug</b>

Expanding emmet abbreviations inside inline functions is not working. Given the example React component below I am unable to expand any abbreviations inside the render function. Expanding works in rest of the file. 

```jsx
import React from 'react';
import { Form } from 'react-final-form';

const SomeComponent = () => (
  <Form render={() => (
    <pre>Expanding Emmet abbreviations inside this function is not working</pre>
  )}
  />
);

export default SomeComponent;
```

What bothers me the most is that it is not even working when explicitly selecting from the menu "Emmet: Expand Abbreviation". If it was up to me I would make the explicit choice from the menu expand whatever and in whatever syntax. Additionally would like to note that "Emmet: Wrap with Abbreviation" seems to already work like that. Shouldn't the "Emmet: Expand Abbreviation" work the same way?

---

VS Code version: Code 1.28.2 (7f3ce96ff4729c91352ae6def877e59c561f4850, 2018-10-17T00:18:43.347Z)
OS version: Darwin x64 18.0.0

<details>
<summary>System Info</summary>

|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i7-4770HQ CPU @ 2.20GHz (8 x 2200)|
|GPU Status|2d_canvas: enabled<br>checker_imaging: disabled_off<br>flash_3d: enabled<br>flash_stage3d: enabled<br>flash_stage3d_baseline: enabled<br>gpu_compositing: enabled<br>multiple_raster_threads: enabled_on<br>native_gpu_memory_buffers: enabled<br>rasterization: enabled<br>video_decode: enabled<br>video_encode: enabled<br>webgl: enabled<br>webgl2: enabled|
|Load (avg)|2, 2, 2|
|Memory (System)|16.00GB (2.19GB free)|
|Process Argv||
|Screen Reader|no|
|VM|0%|

</details><details><summary>Extensions (4)</summary>

Extension|Author (truncated)|Version
---|---|---
vscode-eslint|dba|1.6.1
EditorConfig|Edi|0.12.5
vscode-styled-components|jpo|0.0.22
material-icon-theme|PKi|3.6.0


</details>
<!-- generated by issue reporter -->
Repository: TypeScript
Issue: Declarations are not generated for a high order component
Labels: Suggestion,Domain: Declaration Emit,Experience Enhancement

<!-- 🚨 STOP 🚨 𝗦𝗧𝗢𝗣 🚨 𝑺𝑻𝑶𝑷 🚨

Half of all issues filed here are duplicates, answered in the FAQ, or not appropriate for the bug tracker. Even if you think you've found a *bug*, please read the FAQ first, especially the Common "Bugs" That Aren't Bugs section!

Please help us by doing the following steps before logging an issue:
  * Search: https://github.com/Microsoft/TypeScript/search?type=Issues
  * Read the FAQ: https://github.com/Microsoft/TypeScript/wiki/FAQ

Please fill in the *entire* template below.
-->

<!-- Please try to reproduce the issue with `typescript@next`. It may have already been fixed. -->
**TypeScript Version:**  3.2.0-dev.201xxxxx, 2.9.1, 3.1.3

<!-- Search terms you tried before logging this (so others can find this issue more easily) -->
**Search Terms:**

declaration, high-order, hoc

**Code**

```ts
export function Executor(func: () => any) {
  class ExecutingClass {
    execute() {
      func();
    }
  }

  return ExecutingClass;
}
```

**Expected behavior:**

Running both `tsc` and `tsc -d` produces no errors.

**Actual behavior:**

When I'm running `tsc` on this code, everything works fine.
When I'm running `tsc -d` on this code, I have this error:

```
hoc.ts:1:17 - error TS4060: Return type of exported function has or is using private name 'ExecutingClass'.

1 export function Executor(func: () => any) {
```

It is still possible to generate typings for this if you change code to this:

```ts
export function Executor(func: () => any) {
  const ExecutingClass = class {
    execute() {
      func();
    }
  }

  return ExecutingClass;
}

export default Executor;
```
Repository: go
Issue: cmd/vet: flag using %s:%d to construct network addresses
Labels: Proposal,Proposal-Accepted,FeatureRequest,Analysis

I recently diagnosed a bug in someone’s Go program where a user reported that they couldn’t get the program to connect, and it turned out the issue was that the programmer used `fmt.Sprintf("%s:%d", host, port)` instead of `net.JoinHostPort` to construct a network address to pass to `net.Dial`: https://twitter.com/zekjur/status/1049642773278650368. The issue is subtle: `net.JoinHostPort` correctly handles IPv6 address literals (e.g. 2001:4860:4860::8888), whereas fmt.Sprintf doesn’t.

A very similar issue is to use `strings.Split` instead of `net.SplitHostPort`.

I noticed that both of these issues are fairly prevalent, likely because programmers aren’t that accustomed to using IPv6 literals yet, but I expect them to become more common as IPv6 adoption continues to grow.

I propose adding a vet check to flag using %s:%d format strings with arguments whose names contain port, addr, host, listen or bind. This heuristic will flag 12356 occurrences¹ I found on GitHub using BigQuery, and hopefully make programmers aware not only of net.JoinHostPort but also net.SplitHostPort, for which writing a check is significantly harder.

I can send a CL to implement this. Let me know what you think.

① The BigQuery query I used was:
```
WITH lines AS
  (SELECT
    id,
    SPLIT(content, "\n") AS line
  FROM `gocontents.gocontents`)
SELECT path, flattened_line
FROM lines
CROSS JOIN UNNEST(lines.line) AS flattened_line
JOIN `gocontents.gofiles` AS files ON files.id = lines.id
WHERE
  REGEXP_CONTAINS(flattened_line, r"fmt.Sprintf\(\"%s:%d\", (port|addr|host|listen|bind)")
```
Repository: vscode
Issue: Task Manager: provide the ability to reuse custom problem matchers
Labels: feature-request,tasks

I have several related tasks that share a custom output format.  I'd like to be able to define a problem matcher for this format once and reference it in multiple tasks like I can for built-in matchers, eg. `"problemMatcher": "$my-matcher"`.
Repository: pytorch
Issue: USE_OPENMP=OFF is ignored [Caffe2]
Labels: caffe2

## 🐛 Bug

I've tried submitting this bug report before, but it seems that github is playing funny today so it may be a duplicate.

Since f0d8a36e709dbf6a4c3aed7faf0da2b113668fe7 the ```USE_OPENMP``` cmake flag is ignored and the libcaffe2.so is always linked against libgomp.so

## To Reproduce

<pre><code>
$ ldd libcaffe2.so
        linux-vdso.so.1 =>  (0x00007ffe90ac2000)
        librt.so.1 => /lib64/librt.so.1 (0x00007fdeb32f2000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007fdeb30dc000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007fdeb2ed8000)
        libm.so.6 => /lib64/libm.so.6 (0x00007fdeb2c54000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007fdeb2a37000)
        libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007fdeb2731000)
        <b>libgomp.so.1 => /usr/lib64/libgomp.so.1 (0x00007fdeb251c000)</b>
        libc.so.6 => /lib64/libc.so.6 (0x00007fdeb2188000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fdeb56b5000)
</pre></code>

## Expected behavior

The libcaffe2.so library should not depend on ```libgomp.so``` when building with ```-DUSE_OPENMP=OFF```.

## Environment

 - PyTorch/Caffe2 version: 6dd71947ea39b321dbc7c357122c2d685e973e7d
 - OS: Centos 6 x86_64
 - Build command you used (if compiling from source): ```cmake ../.. -DCMAKE_INSTALL_PREFIX="$install_prefix" -DBUILD_PYTHON=OFF -DUSE_CUDA=OFF -DUSE_NATIVE_ARCH=OFF -DUSE_GFLAGS=OFF -DUSE_GLOG=OFF -DUSE_GLOO=OFF -DBUILD_SHARED_LIBS=ON -DBUILD_TEST=OFF -DBUILD_BINARY=OFF -DUSE_LMDB=OFF -DUSE_LEVELDB=OFF -DUSE_MPI=OFF -DUSE_OPENMP=OFF -DUSE_OPENCV=OFF -DBUILD_ATEN=OFF -DUSE_NNPACK=OFF -DCAFFE2_DISABLE_NUMA=1 -DUSE_MKLDNN=OFF -DUSE_IDEEP=OFF -DUSE_MKLML=OFF -DUSE_DISTRIBUTED=OFF```