While install azure-cli-ml, pip failed with status code 1

If the issue is to do with Azure CLI 2.0 in-particular, create an issue here at Azure/azure-cli

Extension name (the extension in question)
azure-cli-ml
Description of issue (in as much detail as possible)
I see an error when I install azure-cli-ml extension on mcr.microsoft.com/azure-cli docker.
ERROR: An error occurred. Pip failed with status code 1. Use --debug for more information.

Here is azure-cli version I tested. Install failed on following docker images:

mcr.microsoft.com/azure-cli:2.14.1
mcr.microsoft.com/azure-cli:2.10.1
mcr.microsoft.com/azure-cli:latest

azure-cli                         2.10.1

command-modules-nspkg              2.0.3
core                              2.10.1
nspkg                              3.0.4
telemetry                          1.0.4

Python location '/usr/local/bin/python'
Extensions directory '/root/.azure/cliextensions'

Python (Linux) 3.6.10 (default, May 21 2020, 05:54:39)
[GCC 9.2.0]

Legal docs and information: aka.ms/AzureCliLegal

Unable to check if your CLI is up-to-date. Check your internet connection.

Please let us know how we are doing: https://aka.ms/azureclihats
and let us know if you're interested in trying out our newest features: https://aka.ms/CLIUXstudy

Lastly, here is what i got using --debug option.
  Building wheel for cryptography (PEP 517): finished with status 'error'
  ERROR: Failed building wheel for cryptography
...
copying cffi/_cffi_errors.h -> build/lib.linux-x86_64-3.6/cffi
  running build_ext
  building '_cffi_backend' extension
  creating build/temp.linux-x86_64-3.6
  creating build/temp.linux-x86_64-3.6/c
  gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DTHREAD_STACK_SIZE=0x100000 -fPIC -DUSE__THREAD -DHAVE_SYNC_SYNCHRONIZE -I/usr/local/include/python3.6m -c c/_cffi_backend.c -o build/temp.linux-x86_64-3.6/c/_cffi_backend.o
  c/_cffi_backend.c: In function 'fb_prepare_cif':
  c/_cffi_backend.c:5887:16: warning: comparison of integer expressions of different signedness: 'ffi_status' {aka 'enum <anonymous>'} and 'int' [-Wsign-compare]
   5887 |     if (status == -1) {
        |                ^~
...

  copying ./__init__.py -> build/lib.linux-x86_64-3.6/ruamel/yaml/clib
  copying ./LICENSE -> build/lib.linux-x86_64-3.6/ruamel/yaml/clib
  running build_ext
  building '_ruamel_yaml' extension
  creating build/temp.linux-x86_64-3.6
  gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DTHREAD_STACK_SIZE=0x100000 -fPIC -I/usr/local/include/python3.6m -c _ruamel_yaml.c -o build/temp.linux-x86_64-3.6/_ruamel_yaml.o
  In file included from _ruamel_yaml.c:596:
  _ruamel_yaml.h:10: warning: "PyString_CheckExact" redefined
     10 | #define PyString_CheckExact PyBytes_CheckExact
        |
  _ruamel_yaml.c:486: note: this is the location of the previous definition
    486 |   #define PyString_CheckExact          PyUnicode_CheckExact
        |
  _ruamel_yaml.c: In function '__pyx_pf_12_ruamel_yaml_get_version_string':
  _ruamel_yaml.c:1889:17: warning: assignment discards 'const' qualifier from pointer target type [-Wdiscarded-qualifiers]
   1889 |   __pyx_v_value = yaml_get_version_string();
        |                 ^
  _ruamel_yaml.c: In function '__pyx_pf_12_ruamel_yaml_7CParser___init__':
  _ruamel_yaml.c:3389:52: warning: passing argument 2 of 'yaml_parser_set_input' from incompatible pointer type [-Wincompatible-pointer-types]
   3389 |     yaml_parser_set_input((&__pyx_v_self->parser), __pyx_f_12_ruamel_yaml_input_handler, ((void *)__pyx_v_self));
        |                                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        |                                                    |
        |                                                    int (*)(void *, char *, int,  int *)
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:1370:30: note: expected 'int (*)(void *, unsigned char *, size_t,  size_t *)' {aka 'int (*)(void *, unsigned char *, long unsigned int,  long unsigned int *)'} but argument is of type 'int (*)(void *, char *, int,  int *)'
   1370 |         yaml_read_handler_t *handler, void *data);
        |         ~~~~~~~~~~~~~~~~~~~~~^~~~~~~
  In file included from /usr/local/include/python3.6m/Python.h:88,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/bytesobject.h:87:57: warning: pointer targets in passing argument 2 of 'yaml_parser_set_input_string' differ in signedness [-Wpointer-sign]
     87 | #define PyBytes_AS_STRING(op) (assert(PyBytes_Check(op)), \
        |                               ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~
        |                                                         |
        |                                                         char *
     88 |                                 (((PyBytesObject *)(op))->ob_sval))
        |                                 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.h:11:29: note: in expansion of macro 'PyBytes_AS_STRING'
     11 | #define PyString_AS_STRING  PyBytes_AS_STRING
        |                             ^~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:3630:59: note: in expansion of macro 'PyString_AS_STRING'
   3630 |     yaml_parser_set_input_string((&__pyx_v_self->parser), PyString_AS_STRING(__pyx_v_stream), PyString_GET_SIZE(__pyx_v_stream));
        |                                                           ^~~~~~~~~~~~~~~~~~
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:1344:30: note: expected 'const unsigned char *' but argument is of type 'char *'
   1344 |         const unsigned char *input, size_t size);
        |         ~~~~~~~~~~~~~~~~~~~~~^~~~~
  _ruamel_yaml.c: In function '__pyx_f_12_ruamel_yaml_7CParser__token_to_object':
  _ruamel_yaml.c:5464:71: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   5464 |     __pyx_t_2 = PyUnicode_FromString(__pyx_v_token->data.tag_directive.handle); if (unlikely(!__pyx_t_2)) __PYX_ERR(0, 416, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
        |                                                                       |
        |                                                                       yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:5476:71: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   5476 |     __pyx_t_2 = PyUnicode_FromString(__pyx_v_token->data.tag_directive.prefix); if (unlikely(!__pyx_t_2)) __PYX_ERR(0, 417, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
        |                                                                       |
        |                                                                       yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:6478:63: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   6478 |     __pyx_t_2 = PyUnicode_FromString(__pyx_v_token->data.alias.value); if (unlikely(!__pyx_t_2)) __PYX_ERR(0, 447, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~
        |                                                               |
        |                                                               yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:6562:64: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   6562 |     __pyx_t_2 = PyUnicode_FromString(__pyx_v_token->data.anchor.value); if (unlikely(!__pyx_t_2)) __PYX_ERR(0, 450, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~
        |                                                                |
        |                                                                yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:6646:61: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   6646 |     __pyx_t_2 = PyUnicode_FromString(__pyx_v_token->data.tag.handle); if (unlikely(!__pyx_t_2)) __PYX_ERR(0, 453, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
        |                                                             |
        |                                                             yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:6658:61: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   6658 |     __pyx_t_2 = PyUnicode_FromString(__pyx_v_token->data.tag.suffix); if (unlikely(!__pyx_t_2)) __PYX_ERR(0, 454, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
        |                                                             |
        |                                                             yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:6782:64: warning: pointer targets in passing argument 1 of 'PyUnicode_DecodeUTF8' differ in signedness [-Wpointer-sign]
   6782 |     __pyx_t_2 = PyUnicode_DecodeUTF8(__pyx_v_token->data.scalar.value, __pyx_v_token->data.scalar.length, ((char *)"strict")); if (unlikely(!__pyx_t_2)) __PYX_ERR(0, 459, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~
        |                                                                |
        |                                                                yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:1304:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
   1304 | PyAPI_FUNC(PyObject*) PyUnicode_DecodeUTF8(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c: In function '__pyx_f_12_ruamel_yaml_7CParser__event_to_object':
  _ruamel_yaml.c:8463:63: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   8463 |         __pyx_t_4 = PyUnicode_FromString(__pyx_v_tag_directive->handle); if (unlikely(!__pyx_t_4)) __PYX_ERR(0, 573, __pyx_L1_error)
        |                                          ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~
        |                                                               |
        |                                                               yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:8475:63: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   8475 |         __pyx_t_4 = PyUnicode_FromString(__pyx_v_tag_directive->prefix); if (unlikely(!__pyx_t_4)) __PYX_ERR(0, 574, __pyx_L1_error)
        |                                          ~~~~~~~~~~~~~~~~~~~~~^~~~~~~~
        |                                                               |
        |                                                               yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:8718:63: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   8718 |     __pyx_t_4 = PyUnicode_FromString(__pyx_v_event->data.alias.anchor); if (unlikely(!__pyx_t_4)) __PYX_ERR(0, 585, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
        |                                                               |
        |                                                               yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:8822:66: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   8822 |       __pyx_t_4 = PyUnicode_FromString(__pyx_v_event->data.scalar.anchor); if (unlikely(!__pyx_t_4)) __PYX_ERR(0, 590, __pyx_L1_error)
        |                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
        |                                                                  |
        |                                                                  yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:8863:66: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   8863 |       __pyx_t_4 = PyUnicode_FromString(__pyx_v_event->data.scalar.tag); if (unlikely(!__pyx_t_4)) __PYX_ERR(0, 593, __pyx_L1_error)
        |                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
        |                                                                  |
        |                                                                  yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:8884:64: warning: pointer targets in passing argument 1 of 'PyUnicode_DecodeUTF8' differ in signedness [-Wpointer-sign]
   8884 |     __pyx_t_4 = PyUnicode_DecodeUTF8(__pyx_v_event->data.scalar.value, __pyx_v_event->data.scalar.length, ((char *)"strict")); if (unlikely(!__pyx_t_4)) __PYX_ERR(0, 594, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~
        |                                                                |
        |                                                                yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:1304:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
   1304 | PyAPI_FUNC(PyObject*) PyUnicode_DecodeUTF8(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:9225:74: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   9225 |       __pyx_t_4 = PyUnicode_FromString(__pyx_v_event->data.sequence_start.anchor); if (unlikely(!__pyx_t_4)) __PYX_ERR(0, 619, __pyx_L1_error)
        |                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
        |                                                                          |
        |                                                                          yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:9266:74: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   9266 |       __pyx_t_4 = PyUnicode_FromString(__pyx_v_event->data.sequence_start.tag); if (unlikely(!__pyx_t_4)) __PYX_ERR(0, 622, __pyx_L1_error)
        |                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
        |                                                                          |
        |                                                                          yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:9498:73: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   9498 |       __pyx_t_4 = PyUnicode_FromString(__pyx_v_event->data.mapping_start.anchor); if (unlikely(!__pyx_t_4)) __PYX_ERR(0, 636, __pyx_L1_error)
        |                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
        |                                                                         |
        |                                                                         yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:9539:73: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
   9539 |       __pyx_t_4 = PyUnicode_FromString(__pyx_v_event->data.mapping_start.tag); if (unlikely(!__pyx_t_4)) __PYX_ERR(0, 639, __pyx_L1_error)
        |                                        ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
        |                                                                         |
        |                                                                         yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c: In function '__pyx_f_12_ruamel_yaml_7CParser__compose_node':
  _ruamel_yaml.c:11212:75: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
  11212 |     __pyx_t_3 = PyUnicode_FromString(__pyx_v_self->parsed_event.data.alias.anchor); if (unlikely(!__pyx_t_3)) __PYX_ERR(0, 733, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
        |                                                                           |
        |                                                                           yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:11532:76: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
  11532 |     __pyx_t_6 = PyUnicode_FromString(__pyx_v_self->parsed_event.data.scalar.anchor); if (unlikely(!__pyx_t_6)) __PYX_ERR(0, 749, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
        |                                                                            |
        |                                                                            yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:11588:84: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
  11588 |     __pyx_t_6 = PyUnicode_FromString(__pyx_v_self->parsed_event.data.sequence_start.anchor); if (unlikely(!__pyx_t_6)) __PYX_ERR(0, 752, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
        |                                                                                |
        |                                                                                yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:11644:83: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
  11644 |     __pyx_t_6 = PyUnicode_FromString(__pyx_v_self->parsed_event.data.mapping_start.anchor); if (unlikely(!__pyx_t_6)) __PYX_ERR(0, 755, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
        |                                                                                |
        |                                                                                yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c: In function '__pyx_f_12_ruamel_yaml_7CParser__compose_scalar_node':
  _ruamel_yaml.c:12302:74: warning: pointer targets in passing argument 1 of 'PyUnicode_DecodeUTF8' differ in signedness [-Wpointer-sign]
  12302 |   __pyx_t_2 = PyUnicode_DecodeUTF8(__pyx_v_self->parsed_event.data.scalar.value, __pyx_v_self->parsed_event.data.scalar.length, ((char *)"strict")); if (unlikely(!__pyx_t_2)) __PYX_ERR(0, 790, __pyx_L1_error)
        |                                    ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~
        |                                                                          |
        |                                                                          yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:1304:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
   1304 | PyAPI_FUNC(PyObject*) PyUnicode_DecodeUTF8(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c:12525:76: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
  12525 |     __pyx_t_2 = PyUnicode_FromString(__pyx_v_self->parsed_event.data.scalar.tag); if (unlikely(!__pyx_t_2)) __PYX_ERR(0, 803, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
        |                                                                            |
        |                                                                            yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c: In function '__pyx_f_12_ruamel_yaml_7CParser__compose_sequence_node':
  _ruamel_yaml.c:13063:84: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
  13063 |     __pyx_t_3 = PyUnicode_FromString(__pyx_v_self->parsed_event.data.sequence_start.tag); if (unlikely(!__pyx_t_3)) __PYX_ERR(0, 836, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
        |                                                                                |
        |                                                                                yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c: In function '__pyx_f_12_ruamel_yaml_7CParser__compose_mapping_node':
  _ruamel_yaml.c:13688:83: warning: pointer targets in passing argument 1 of 'PyUnicode_FromString' differ in signedness [-Wpointer-sign]
  13688 |     __pyx_t_3 = PyUnicode_FromString(__pyx_v_self->parsed_event.data.mapping_start.tag); if (unlikely(!__pyx_t_3)) __PYX_ERR(0, 875, __pyx_L1_error)
        |                                      ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~
        |                                                                                |
        |                                                                                yaml_char_t * {aka unsigned char *}
  In file included from /usr/local/include/python3.6m/Python.h:89,
                   from _ruamel_yaml.c:4:
  /usr/local/include/python3.6m/unicodeobject.h:702:23: note: expected 'const char *' but argument is of type 'yaml_char_t *' {aka 'unsigned char *'}
    702 | PyAPI_FUNC(PyObject*) PyUnicode_FromString(
        |                       ^~~~~~~~~~~~~~~~~~~~
  _ruamel_yaml.c: In function '__pyx_pf_12_ruamel_yaml_8CEmitter___init__':
  _ruamel_yaml.c:15019:53: warning: passing argument 2 of 'yaml_emitter_set_output' from incompatible pointer type [-Wincompatible-pointer-types]
  15019 |   yaml_emitter_set_output((&__pyx_v_self->emitter), __pyx_f_12_ruamel_yaml_output_handler, ((void *)__pyx_v_self));
        |                                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
        |                                                     |
        |                                                     int (*)(void *, char *, int)
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:1837:31: note: expected 'int (*)(void *, unsigned char *, size_t)' {aka 'int (*)(void *, unsigned char *, long unsigned int)'} but argument is of type 'int (*)(void *, char *, int)'
   1837 |         yaml_write_handler_t *handler, void *data);
        |         ~~~~~~~~~~~~~~~~~~~~~~^~~~~~~
  _ruamel_yaml.c: In function '__pyx_f_12_ruamel_yaml_8CEmitter__object_to_event':
  _ruamel_yaml.c:16371:44: warning: pointer targets in assignment from 'char *' to 'yaml_char_t *' {aka 'unsigned char *'} differ in signedness [-Wpointer-sign]
  16371 |         __pyx_v_tag_directives_end->handle = PyString_AS_STRING(__pyx_v_handle);
        |                                            ^
  _ruamel_yaml.c:16486:44: warning: pointer targets in assignment from 'char *' to 'yaml_char_t *' {aka 'unsigned char *'} differ in signedness [-Wpointer-sign]
  16486 |         __pyx_v_tag_directives_end->prefix = PyString_AS_STRING(__pyx_v_prefix);
        |                                            ^
  _ruamel_yaml.c:16823:62: warning: pointer targets in passing argument 2 of 'yaml_alias_event_initialize' differ in signedness [-Wpointer-sign]
  16823 |     __pyx_t_2 = ((yaml_alias_event_initialize(__pyx_v_event, __pyx_v_anchor) == 0) != 0);
        |                                                              ^~~~~~~~~~~~~~
        |                                                              |
        |                                                              char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:555:63: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    555 | yaml_alias_event_initialize(yaml_event_t *event, yaml_char_t *anchor);
        |                                                  ~~~~~~~~~~~~~^~~~~~
  _ruamel_yaml.c:17538:63: warning: pointer targets in passing argument 2 of 'yaml_scalar_event_initialize' differ in signedness [-Wpointer-sign]
  17538 |     __pyx_t_2 = ((yaml_scalar_event_initialize(__pyx_v_event, __pyx_v_anchor, __pyx_v_tag, __pyx_v_value, __pyx_v_length, __pyx_v_plain_implicit, __pyx_v_quoted_implicit, __pyx_v_scalar_style) == 0) != 0);
        |                                                               ^~~~~~~~~~~~~~
        |                                                               |
        |                                                               char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:581:22: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    581 |         yaml_char_t *anchor, yaml_char_t *tag,
        |         ~~~~~~~~~~~~~^~~~~~
  _ruamel_yaml.c:17538:79: warning: pointer targets in passing argument 3 of 'yaml_scalar_event_initialize' differ in signedness [-Wpointer-sign]
  17538 |     __pyx_t_2 = ((yaml_scalar_event_initialize(__pyx_v_event, __pyx_v_anchor, __pyx_v_tag, __pyx_v_value, __pyx_v_length, __pyx_v_plain_implicit, __pyx_v_quoted_implicit, __pyx_v_scalar_style) == 0) != 0);
        |                                                                               ^~~~~~~~~~~
        |                                                                               |
        |                                                                               char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:581:43: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    581 |         yaml_char_t *anchor, yaml_char_t *tag,
        |                              ~~~~~~~~~~~~~^~~
  _ruamel_yaml.c:17538:92: warning: pointer targets in passing argument 4 of 'yaml_scalar_event_initialize' differ in signedness [-Wpointer-sign]
  17538 |     __pyx_t_2 = ((yaml_scalar_event_initialize(__pyx_v_event, __pyx_v_anchor, __pyx_v_tag, __pyx_v_value, __pyx_v_length, __pyx_v_plain_implicit, __pyx_v_quoted_implicit, __pyx_v_scalar_style) == 0) != 0);
        |                                                                                ^~~~~~~~~~~~~
        |                                                                                |
        |                                                                                char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:582:22: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    582 |         yaml_char_t *value, int length,
        |         ~~~~~~~~~~~~~^~~~~
  _ruamel_yaml.c:17972:71: warning: pointer targets in passing argument 2 of 'yaml_sequence_start_event_initialize' differ in signedness [-Wpointer-sign]
  17972 |     __pyx_t_3 = ((yaml_sequence_start_event_initialize(__pyx_v_event, __pyx_v_anchor, __pyx_v_tag, __pyx_v_implicit, __pyx_v_sequence_style) == 0) != 0);
        |                                                                       ^~~~~~~~~~~~~~
        |                                                                       |
        |                                                                       char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:604:22: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    604 |         yaml_char_t *anchor, yaml_char_t *tag, int implicit,
        |         ~~~~~~~~~~~~~^~~~~~
  _ruamel_yaml.c:17972:87: warning: pointer targets in passing argument 3 of 'yaml_sequence_start_event_initialize' differ in signedness [-Wpointer-sign]
  17972 |     __pyx_t_3 = ((yaml_sequence_start_event_initialize(__pyx_v_event, __pyx_v_anchor, __pyx_v_tag, __pyx_v_implicit, __pyx_v_sequence_style) == 0) != 0);
        |                                                                                ^~~~~~~~~~~
        |                                                                                |
        |                                                                                char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:604:43: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    604 |         yaml_char_t *anchor, yaml_char_t *tag, int implicit,
        |                              ~~~~~~~~~~~~~^~~
  _ruamel_yaml.c:18406:70: warning: pointer targets in passing argument 2 of 'yaml_mapping_start_event_initialize' differ in signedness [-Wpointer-sign]
  18406 |     __pyx_t_2 = ((yaml_mapping_start_event_initialize(__pyx_v_event, __pyx_v_anchor, __pyx_v_tag, __pyx_v_implicit, __pyx_v_mapping_style) == 0) != 0);
        |                                                                      ^~~~~~~~~~~~~~
        |                                                                      |
        |                                                                      char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:636:22: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    636 |         yaml_char_t *anchor, yaml_char_t *tag, int implicit,
        |         ~~~~~~~~~~~~~^~~~~~
  _ruamel_yaml.c:18406:86: warning: pointer targets in passing argument 3 of 'yaml_mapping_start_event_initialize' differ in signedness [-Wpointer-sign]
  18406 |     __pyx_t_2 = ((yaml_mapping_start_event_initialize(__pyx_v_event, __pyx_v_anchor, __pyx_v_tag, __pyx_v_implicit, __pyx_v_mapping_style) == 0) != 0);
        |                                                                                ^~~~~~~~~~~
        |                                                                                |
        |                                                                                char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:636:43: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    636 |         yaml_char_t *anchor, yaml_char_t *tag, int implicit,
        |                              ~~~~~~~~~~~~~^~~
  _ruamel_yaml.c: In function '__pyx_pf_12_ruamel_yaml_8CEmitter_12serialize':
  _ruamel_yaml.c:19976:42: warning: pointer targets in assignment from 'char *' to 'yaml_char_t *' {aka 'unsigned char *'} differ in signedness [-Wpointer-sign]
  19976 |       __pyx_v_tag_directives_end->handle = PyString_AS_STRING(__pyx_v_handle);
        |                                          ^
  _ruamel_yaml.c:20091:42: warning: pointer targets in assignment from 'char *' to 'yaml_char_t *' {aka 'unsigned char *'} differ in signedness [-Wpointer-sign]
  20091 |       __pyx_v_tag_directives_end->prefix = PyString_AS_STRING(__pyx_v_prefix);
        |                                          ^
  _ruamel_yaml.c: In function '__pyx_f_12_ruamel_yaml_8CEmitter__serialize_node':
  _ruamel_yaml.c:20948:65: warning: pointer targets in passing argument 2 of 'yaml_alias_event_initialize' differ in signedness [-Wpointer-sign]
  20948 |     __pyx_t_2 = ((yaml_alias_event_initialize((&__pyx_v_event), __pyx_v_anchor) == 0) != 0);
        |                                                                 ^~~~~~~~~~~~~~
        |                                                                 |
        |                                                                 char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:555:63: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    555 | yaml_alias_event_initialize(yaml_event_t *event, yaml_char_t *anchor);
        |                                                  ~~~~~~~~~~~~~^~~~~~
  _ruamel_yaml.c:21759:68: warning: pointer targets in passing argument 2 of 'yaml_scalar_event_initialize' differ in signedness [-Wpointer-sign]
  21759 |       __pyx_t_2 = ((yaml_scalar_event_initialize((&__pyx_v_event), __pyx_v_anchor, __pyx_v_tag, __pyx_v_value, __pyx_v_length, __pyx_v_plain_implicit, __pyx_v_quoted_implicit, __pyx_v_scalar_style) == 0) != 0);
        |                                                                    ^~~~~~~~~~~~~~
        |                                                                    |
        |                                                                    char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:581:22: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    581 |         yaml_char_t *anchor, yaml_char_t *tag,
        |         ~~~~~~~~~~~~~^~~~~~
  _ruamel_yaml.c:21759:84: warning: pointer targets in passing argument 3 of 'yaml_scalar_event_initialize' differ in signedness [-Wpointer-sign]
  21759 |       __pyx_t_2 = ((yaml_scalar_event_initialize((&__pyx_v_event), __pyx_v_anchor, __pyx_v_tag, __pyx_v_value, __pyx_v_length, __pyx_v_plain_implicit, __pyx_v_quoted_implicit, __pyx_v_scalar_style) == 0) != 0);
        |                                                                                ^~~~~~~~~~~
        |                                                                                |
        |                                                                                char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:581:43: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    581 |         yaml_char_t *anchor, yaml_char_t *tag,
        |                              ~~~~~~~~~~~~~^~~
  _ruamel_yaml.c:21759:97: warning: pointer targets in passing argument 4 of 'yaml_scalar_event_initialize' differ in signedness [-Wpointer-sign]
  21759 |       __pyx_t_2 = ((yaml_scalar_event_initialize((&__pyx_v_event), __pyx_v_anchor, __pyx_v_tag, __pyx_v_value, __pyx_v_length, __pyx_v_plain_implicit, __pyx_v_quoted_implicit, __pyx_v_scalar_style) == 0) != 0);
        |                                                                                ^~~~~~~~~~~~~
        |                                                                                |
        |                                                                                char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:582:22: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    582 |         yaml_char_t *value, int length,
        |         ~~~~~~~~~~~~~^~~~~
  _ruamel_yaml.c:22146:76: warning: pointer targets in passing argument 2 of 'yaml_sequence_start_event_initialize' differ in signedness [-Wpointer-sign]
  22146 |       __pyx_t_2 = ((yaml_sequence_start_event_initialize((&__pyx_v_event), __pyx_v_anchor, __pyx_v_tag, __pyx_v_implicit, __pyx_v_sequence_style) == 0) != 0);
        |                                                                            ^~~~~~~~~~~~~~
        |                                                                            |
        |                                                                            char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:604:22: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    604 |         yaml_char_t *anchor, yaml_char_t *tag, int implicit,
        |         ~~~~~~~~~~~~~^~~~~~
  _ruamel_yaml.c:22146:92: warning: pointer targets in passing argument 3 of 'yaml_sequence_start_event_initialize' differ in signedness [-Wpointer-sign]
  22146 |       __pyx_t_2 = ((yaml_sequence_start_event_initialize((&__pyx_v_event), __pyx_v_anchor, __pyx_v_tag, __pyx_v_implicit, __pyx_v_sequence_style) == 0) != 0);
        |                                                                                ^~~~~~~~~~~
        |                                                                                |
        |                                                                                char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:604:43: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    604 |         yaml_char_t *anchor, yaml_char_t *tag, int implicit,
        |                              ~~~~~~~~~~~~~^~~
  _ruamel_yaml.c:22676:75: warning: pointer targets in passing argument 2 of 'yaml_mapping_start_event_initialize' differ in signedness [-Wpointer-sign]
  22676 |       __pyx_t_2 = ((yaml_mapping_start_event_initialize((&__pyx_v_event), __pyx_v_anchor, __pyx_v_tag, __pyx_v_implicit, __pyx_v_mapping_style) == 0) != 0);
        |                                                                           ^~~~~~~~~~~~~~
        |                                                                           |
        |                                                                           char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:636:22: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    636 |         yaml_char_t *anchor, yaml_char_t *tag, int implicit,
        |         ~~~~~~~~~~~~~^~~~~~
  _ruamel_yaml.c:22676:91: warning: pointer targets in passing argument 3 of 'yaml_mapping_start_event_initialize' differ in signedness [-Wpointer-sign]
  22676 |       __pyx_t_2 = ((yaml_mapping_start_event_initialize((&__pyx_v_event), __pyx_v_anchor, __pyx_v_tag, __pyx_v_implicit, __pyx_v_mapping_style) == 0) != 0);
        |                                                                                ^~~~~~~~~~~
        |                                                                                |
        |                                                                                char *
  In file included from _ruamel_yaml.h:2,
                   from _ruamel_yaml.c:596:
  yaml.h:636:43: note: expected 'yaml_char_t *' {aka 'unsigned char *'} but argument is of type 'char *'
    636 |         yaml_char_t *anchor, yaml_char_t *tag, int implicit,
        |                              ~~~~~~~~~~~~~^~~
  gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DTHREAD_STACK_SIZE=0x100000 -fPIC -I/usr/local/include/python3.6m -c api.c -o build/temp.linux-x86_64-3.6/api.o
  api.c: In function 'yaml_document_delete':
  api.c:1127:7: warning: variable 'context' set but not used [-Wunused-but-set-variable]
   1127 |     } context;
        |       ^~~~~~~
  gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DTHREAD_STACK_SIZE=0x100000 -fPIC -I/usr/local/include/python3.6m -c writer.c -o build/temp.linux-x86_64-3.6/writer.o
  gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DTHREAD_STACK_SIZE=0x100000 -fPIC -I/usr/local/include/python3.6m -c dumper.c -o build/temp.linux-x86_64-3.6/dumper.o
  gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DTHREAD_STACK_SIZE=0x100000 -fPIC -I/usr/local/include/python3.6m -c loader.c -o build/temp.linux-x86_64-3.6/loader.o
  gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DTHREAD_STACK_SIZE=0x100000 -fPIC -I/usr/local/include/python3.6m -c reader.c -o build/temp.linux-x86_64-3.6/reader.o
  gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DTHREAD_STACK_SIZE=0x100000 -fPIC -I/usr/local/include/python3.6m -c scanner.c -o build/temp.linux-x86_64-3.6/scanner.o
  scanner.c: In function 'yaml_parser_decrease_flow_level':
  scanner.c:1189:23: warning: variable 'dummy_key' set but not used [-Wunused-but-set-variable]
   1189 |     yaml_simple_key_t dummy_key;    /* Used to eliminate a compiler warning. */
        |                       ^~~~~~~~~
  gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DTHREAD_STACK_SIZE=0x100000 -fPIC -I/usr/local/include/python3.6m -c parser.c -o build/temp.linux-x86_64-3.6/parser.o
  parser.c: In function 'yaml_parser_parse_block_sequence_entry':
  parser.c:762:21: warning: variable 'dummy_mark' set but not used [-Wunused-but-set-variable]
    762 |         yaml_mark_t dummy_mark;     /* Used to eliminate a compiler warning. */
        |                     ^~~~~~~~~~
  parser.c: In function 'yaml_parser_parse_block_mapping_key':
  parser.c:872:21: warning: variable 'dummy_mark' set but not used [-Wunused-but-set-variable]
    872 |         yaml_mark_t dummy_mark;     /* Used to eliminate a compiler warning. */
        |                     ^~~~~~~~~~
  parser.c: In function 'yaml_parser_parse_flow_sequence_entry':
  parser.c:955:17: warning: variable 'dummy_mark' set but not used [-Wunused-but-set-variable]
    955 |     yaml_mark_t dummy_mark;     /* Used to eliminate a compiler warning. */
        |                 ^~~~~~~~~~
  parser.c: In function 'yaml_parser_parse_flow_mapping_key':
  parser.c:1107:17: warning: variable 'dummy_mark' set but not used [-Wunused-but-set-variable]
   1107 |     yaml_mark_t dummy_mark;     /* Used to eliminate a compiler warning. */
        |                 ^~~~~~~~~~
  gcc -Wno-unused-result -Wsign-compare -DNDEBUG -g -fwrapv -O3 -Wall -DTHREAD_STACK_SIZE=0x100000 -fPIC -I/usr/local/include/python3.6m -c emitter.c -o build/temp.linux-x86_64-3.6/emitter.o
  emitter.c: In function 'yaml_emitter_write_plain_scalar':
  emitter.c:28:6: warning: value computed is not used [-Wunused-value]
     28 |      && ((emitter->line_break == YAML_CR_BREAK ?                                \
        |      ^~
  emitter.c:56:11: note: in expansion of macro 'PUT_BREAK'
     56 |          (PUT_BREAK(emitter),                                                   \
        |           ^~~~~~~~~
  emitter.c:1941:18: note: in expansion of macro 'WRITE_BREAK'
   1941 |             if (!WRITE_BREAK(emitter, string)) return 0;
        |                  ^~~~~~~~~~~
  emitter.c: In function 'yaml_emitter_write_single_quoted_scalar':
  emitter.c:28:6: warning: value computed is not used [-Wunused-value]
     28 |      && ((emitter->line_break == YAML_CR_BREAK ?                                \
        |      ^~
  emitter.c:56:11: note: in expansion of macro 'PUT_BREAK'
     56 |          (PUT_BREAK(emitter),                                                   \
        |           ^~~~~~~~~
  emitter.c:2002:18: note: in expansion of macro 'WRITE_BREAK'
   2002 |             if (!WRITE_BREAK(emitter, string)) return 0;
        |                  ^~~~~~~~~~~
  emitter.c: In function 'yaml_emitter_write_literal_scalar':
  emitter.c:28:6: warning: value computed is not used [-Wunused-value]
     28 |      && ((emitter->line_break == YAML_CR_BREAK ?                                \
        |      ^~
  emitter.c:56:11: note: in expansion of macro 'PUT_BREAK'
     56 |          (PUT_BREAK(emitter),                                                   \
        |           ^~~~~~~~~
  emitter.c:2268:18: note: in expansion of macro 'WRITE_BREAK'
   2268 |             if (!WRITE_BREAK(emitter, string)) return 0;
        |                  ^~~~~~~~~~~
  emitter.c: In function 'yaml_emitter_write_folded_scalar':
  emitter.c:28:6: warning: value computed is not used [-Wunused-value]
     28 |      && ((emitter->line_break == YAML_CR_BREAK ?                                \
        |      ^~
  emitter.c:56:11: note: in expansion of macro 'PUT_BREAK'
     56 |          (PUT_BREAK(emitter),                                                   \
        |           ^~~~~~~~~
  emitter.c:2317:18: note: in expansion of macro 'WRITE_BREAK'
   2317 |             if (!WRITE_BREAK(emitter, string)) return 0;
        |                  ^~~~~~~~~~~
...

DEBUG: cli.azure.cli.core.extension.operations: Command '['/usr/local/bin/python', '-m', 'pip', 'install', '--target', '/root/.azure/cliextensions/azure-cli-ml', '/tmp/tmp32cdcuy8/azure_cli_ml-1.21.0-py3-none-any.whl', '-vv', '--disable-pip-version-check', '--no-cache-dir']' returned non-zero exit status 1.
DEBUG: cli.azure.cli.core.extension.operations: Pip failed so deleting anything we might have installed at /root/.azure/cliextensions/azure-cli-ml
DEBUG: cli.azure.cli.core.util: azure.cli.core.util.handle_exception is called with an exception:
DEBUG: cli.azure.cli.core.util: Traceback (most recent call last):
  File "/usr/local/lib/python3.6/site-packages/knack/cli.py", line 233, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/local/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 664, in execute
    raise ex
  File "/usr/local/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 727, in _run_jobs_serially
    results.append(self._run_job(expanded_arg, cmd_copy))
  File "/usr/local/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 720, in _run_job
    six.reraise(*sys.exc_info())
  File "/usr/local/lib/python3.6/site-packages/six.py", line 703, in reraise
    raise value
  File "/usr/local/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 698, in _run_job
    result = cmd_copy(params)
  File "/usr/local/lib/python3.6/site-packages/azure/cli/core/commands/__init__.py", line 331, in __call__
    return self.handler(*args, **kwargs)
  File "/usr/local/lib/python3.6/site-packages/azure/cli/core/__init__.py", line 816, in default_command_handler
    return op(**command_args)
  File "/usr/local/lib/python3.6/site-packages/azure/cli/command_modules/extension/custom.py", line 18, in add_extension_cmd
    version=version, upgrade=upgrade)
  File "/usr/local/lib/python3.6/site-packages/azure/cli/core/extension/operations.py", line 318, in add_extension
    pip_extra_index_urls=pip_extra_index_urls, pip_proxy=pip_proxy, system=system)
  File "/usr/local/lib/python3.6/site-packages/azure/cli/core/extension/operations.py", line 163, in _add_whl_ext
    'Use --debug for more information.'.format(pip_status_code))
knack.util.CLIError: An error occurred. Pip failed with status code 1. Use --debug for more information.

ERROR: cli.azure.cli.core.azclierror: An error occurred. Pip failed with status code 1. Use --debug for more information.
ERROR: cli.azure.cli.core.azclierror: An error occurred. Pip failed with status code 1. Use --debug for more information.
DEBUG: cli.knack.cli: Event: Cli.PostExecute [<function AzCliLogging.deinit_cmd_metadata_logging at 0x7ff73ddbb620>]
INFO: az_command_data_logger: exit code: 1

azure-cli-ml

Related: https://github.com/Azure/azure-cli/issues/16880

A new patch release whl has been made that should fix this issue. It pins the cryptography package to be compatible:
az extension add -s https://azurecliext.blob.core.windows.net/release/azure_cli_ml-<IP_ADDRESS>-py3-none-any.whl -y
This has not yet been released to the general az extension add -n azure-cli-ml yet - we are working on that.

The latest version for az extension add -n azure-cli-ml has been updated with the patch.


Send OnChunkGenerated when a new chunk gets generated.

It used to get sent when a old chunk got loaded.

Refer to this link for build results (access rights to CI server needed):
http://jenkins.terasology.org/job/TerasologyPRs/421/
Hooray Jenkins reported success with all tests good!

Makes sense to me - thanks for fixing this!

thanks


feat: June 5th balance changes

| D.va |
Defense Matrix cooldown increased from 1 to 1.5 seconds
| Mauga |
Overrun cooldown reduced from 10 to 8 seconds
| Reinhardt |
Base health increased from 250 to 300 HP
| Roadhog |
Base health increased from 550 to 600 HP
Take a Breather cooldown increased from 1.25 to 3.5 seconds
| Sigma |
Base health reduced from 300 to 250 HP
Kinetic Grasp overhealth generation increased from 0% to 40% of damage mitigated
| Bastion |
Reconfigure cooldown reduced from 12 to 10 seconds
Configuration: Assault movement speed reduced from 65% to 50%
| Echo |
Fixed a bug that caused Focusing Beam to not deal as much damage as intended
Duplicate health when copying Reinhard increased from 250 to 300 HP
Duplicate health when copying Roadhog increased from 475 to 500 HP
| Genji |
Deflect duration reduced from 2 to 1.5 seconds
| Venture |
Base health increased from 200 to 225 HP
Smart Excavator total damage reduced from 70 to 67

:tada: This PR is included in version 1.4.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Feature request: option for notifications only on problems

I was wondering whether it would be able to fine-tune the "notifications" command by including an option to notify only on problems. What I have in mind basically is:

sync errors
connectivity issues (related to sync errors, but could just be internet connection problems)
failure to start the daemon.

Let me give some background. I work with LaTeX a lot, which means building frequently (tex to pdf). When notifications are on, there is so much incoming that the Gnome notification area becomes a mess. I therefore tend to turn them off, and just use the system tray icon from gui to see whether syncing happens, and whether there are any sync errors. This is literally the only thing that I use it for - if there was a way to know if anything is wrong without having to look at the system tray icon, and get notified only when something goes wrong, I would have no need for GUI at all.
I believe that this option could also benefit other users - if it is not too tough to implement, I would love to see it.
System (please complete the following information):

Maestral version: 0.5.2
OS: Arch
Desktop environment: Gnome 3.34

Yes, I realised too late that there were some issues in the code that keeps systemd informed about the daemon's status. The risk of the pre-release channel :)
The systemd service file looks good to me, it means that maestral is configured as a 'notify' service and that systemd expects regular updates from it or otherwise considers it failed. More details are given in the wiki.
The only issue with the file is the reload command: According to freedesktop.org for a 'notify' or 'exec' service:

It is expected that the process configured with ExecStart= is the main process of the service

However, maestral restart will spawn a separate process for the daemon and systemd will likely consider the reload failed. You can just leave out this line and let systemd use ExecStop and ExecStrart instead.

Regarding notifications, is the issue with the notification pop-ups being annoying, or rather the notifications piling up in the 'notification center' history? In the second case, it should be possible to limit the number of notifications shown for maestral. Implementing this on a per-folder basis will be a bit tedious, but one could simply clear old notifications if not already done by the platform itself.
It will require switching from notify-send to a dbus implementation on Linux but this should not be difficult.

let me know when the issues with the pre-release have been resolved and I can proceed testing. for the time being I am sticking to 0.5.2, but I can switch and ditch systemd service in the meantime, if you want any feedback.
regarding notifications: both pop-ups and the pile-up is a bit distracting. Provided you could fix the pile up, you could add an option to temporarily disable notifications. (I recall the official dropbox client had some option like that - for half hour or so.) A way to go for the cli would be to provide a number of notification levels, ranging from "errors only" to "everything". Maybe 3 could be enough (these two, plus a "middle" one). More users should get in this discussion, to understand what the average need is.
this is coming along very nicely. it clearly has almost all functionality of the official client in linux, but is lighter and uses system libraries instead of everything bundled as dropbox does. the separation of frontend and backend is another huge plus. I believe that, when you feel it has become more stable and towards 1.0, and you advertise this to the right channels (e.g., omg ubuntu), there will be a lot of interest from linux users.

The issues should be resolved now - I have tested it on Ubuntu and the daemon starts up fine.
Regarding notification levels, I was thinking: 1) file changes, 2) sync issues, 3) fatal errors. But it would indeed be good to get other users' input on this.
I am glad you like the project :) It still has a few kinks to iron out, but hopefully soon it will be sufficiently stable. The input from Github has actually been very helpful eliminating issues.

excellent - I have switched to dev2 and testing. all good till now. the notification levels you suggest make sense.
as I mentioned,  maybe you can add a snooze option in notifications; for example, maestral notifications --snooze 20 could snooze everything (except fatal errors) for 20 minutes. A default of 30 or 60 would make sense, I guess.

This is implemented in the dev branch now but it will still take some time to be released. v0.6.0 will come with some changes in package structure (a split of gui and daemon into separate packages) which will need to be properly tested. I am also hoping to ship a native Cocoa GUI on macOS with the next release, but this will depend on some bugs in the used libraries to be fixed first...

If you would like to try it out, feedback on the CLI and GUI would be welcome.

many thanks - 0.6 seems like an exciting release. I cannot really test the new GUI, since I am on Linux. If you create a GTK equivalent I will be happy to take a look. I avoid using the Qt GUI due to poor integration and heavy memory footprint.

Most of this has been implemented in v0.6.1 (v0.6.0 was never released). The only part which I did not implement is a limit to the number of messages in the notification centre. This would have required adding PyGObject or dbus as a dependency.


Base materials

Notebooks borrowed from ipython-in-depth and @ellisonbg 's ds4e course.  We can use these as reference material or scrap together the talk from pieces of them. @rgbkrk

Jennifer Klay will be teaching a intro tutorial to NumPy and SciPy, so I
would steer clear of that material...I would possibly even touch base with
her to see what she is going to cover...
On Sun, Feb 8, 2015 at 10:16 AM, Jonathan Frederic<EMAIL_ADDRESS>
wrote:

Merged #6 https://github.com/jupyter/strata-sv-2015-tutorial/pull/6.
—
Reply to this email directly or view it on GitHub
https://github.com/jupyter/strata-sv-2015-tutorial/pull/6#event-232128646
.

--
Brian E. Granger
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>

@ellisonbg thanks, that's good to know.


Update HowtoIdentifyFacesinImage.md

Change DetectAsync() method references to DetectWithStreamAsync(). DetectAsync() method does not exist.

@mpapas : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Create implementation of NetworkEvents using RxJava for Android

This should be done in a separate project. Not in this one.


The test case L2 GetTVGammaTarget fails due to the loop iterating over all possible enum values instead of the supported color temperature values.

Problem/Opportunity
The test case is failing because the loop in the GetTVGammaTarget function tests all possible enum values, while only four specific color temperature values (STANDARD, WARM, COLD, USER) are supported.
Steps to reproduce

Run the test case test_l2_tvSettings_GetTVGammaTarget.
Observe the test output where the loop iterates through all possible enum values for color temperature.
The test will fail as the VTS expects only the valid color temperature values.

Expected Behavior
The loop should only iterate over the four supported color temperature values to ensure compatibility with the VTS, and the test
Actual Behavior
The test fails because the loop is iterating over all enum values, which includes invalid color temperature values, causing mismatched expectations in the VTS.
Notes (Optional)
No response

Fix available in tag 2.1.3


Move wal-set script from the scripts submodule to the util folder

util is where I want to put all of the scripts needed to install/configure the dotfiles. wal-set doesn't belong in my scripts repository.
If I do this, then I'll have to modify any config files that reference the original path of ~/bin/scripts/wal-set to point to <dotfiles-path>/util/wal-set. I think my i3 configs are the only place where this is needed. But then it might be prudent to use a shell script to properly set the <dotfiles-path> in those places instead, so that if a user wants to put their dotfiles in any place other than ~/.dotfiles, they can without having to manually fix the configs.
For now though, I'll just assume the dotfiles are always in ~/.dotfiles.

Done after 5e9f933


Cannot change the colour and text format

Hi, I'm a newbie for bootsy.
I have few questions here.
i wrap the bootsy_area inside my form.
           <%= bootsy_area :email_content, editor_options: { link: false, lists: false, html: false, alert_unsaved: true} %>
which displays as

as the link, lists and html buttons are still there, and I cannot choose the word formatting and color selection buttons (no dropdown lists).
and there's a bootstrap error when the icons works correctly

BTW:
how could i set the default text ?
and how could i set the size of text area?

Bootsy is intended to be used with form builders, not as standalone form tags. You can set any text you want just like you would do in a regular text_area helper. Bootsy will assume whatever size you set to the text area. Also, the errors you're are seeing appear to be from your app, not Bootsy.


Add tutorial on how to pick the right mapping predicate

It is frequently confusing to people to see mapping predicates like

skos:closeMatch and oboInOwl:hasDbXref
skos:exactMatch and owl:equivalentClass

side by side. Beyond the spec we should provide a better guide on selecting the appropriate mapping predicate for every case.

One perspective that should be covered is mappings for an ontology with many annotations that needs to propagate annotations from other systems
here mappings are implicitly exact or narrow from the perspective of the resource, otherwise propagation is invalid . Think ec2go interpro2go etc. the predicate is implicitly in the name. but people get confused using the mappings for other purposes.
I think using pragmatic examples like this could help future docs

Sounds great, I think we should probably discuss this a bit in one of our next calls, I put in on the agenda.

A good first draft is provided here: https://mapping-commons.github.io/sssom/mapping-predicates/ closing for more concrete issues.


Break out signup router

@keybase/react-hackers
login/index.js:parseRoute was starting to get big, this breaks out all signup routing into a normal (and pure!) function.

:+1:


Adds podspec to deployment; better sample CR

Codecov Report
Base: 71.52% // Head: 72.71% // Increases project coverage by +1.18% :tada:

Coverage data is based on head (4da36ea) compared to base (c7e005b).
Patch coverage: 81.10% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #24      +/-   ##
==========================================
+ Coverage   71.52%   72.71%   +1.18%
==========================================
  Files          11       11
  Lines         727      843     +116
==========================================
+ Hits          520      613      +93
- Misses        152      172      +20
- Partials       55       58       +3

Impacted Files
Coverage Δ

controllers/install/eventingester_controller.go
70.58% <81.10%> (+15.65%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


ci: fix mdl configuration

This commit makes the following changes:
Please replace \":code_blocks => false\" \
by \":ignore_code_blocks => true\" in your configuration.
Some rules are ignore for the time being,
these will be fixed later on.
Signed-off-by: Rakshith R<EMAIL_ADDRESS>

Created #3448 issue to track fixes required.

@mergifyio refresh


Migrate the initial version

Push sources from the personal repo: https://github.com/sskorol/minipupper-teleop.git

Already in main.


time data does not match format '%Y-%m-%dT%H:%M:%S.%f%z'

I am getting the following error when running on python 3.7 on centos7
It looks like it is getting the date format incorrect
I am able to work around this by changing line 1311 in /usr/local/lib/python3.7/site-packages/tesla_dashcam/tesla_dashcam.py
to
                line_split[1].strip(), "%Y-%m-%d %H:%M:%S"
but it's a really hacky solution
[root@rocky tesla]# tesla_dashcam --merge --chapter_offset -30 --quality MEDIUM  --output /mnt2/tesla_dashcam/2019-10-06.mp4 /mnt2/tesla/2019-10-06/2019-10-06_15-23-12/
Discovered 1 folders containing total of 44 files in /mnt2/tesla/2019-10-06/2019-10-06_15-23-12/
Traceback (most recent call last):
  File "/usr/local/bin/tesla_dashcam", line 5, in <module>
    from tesla_dashcam import main
  File "/usr/local/lib/python3.7/site-packages/tesla_dashcam/__init__.py", line 1, in <module>
    from .tesla_dashcam import main
  File "/usr/local/lib/python3.7/site-packages/tesla_dashcam/tesla_dashcam.py", line 3431, in <module>
    sys.exit(main())
  File "/usr/local/lib/python3.7/site-packages/tesla_dashcam/tesla_dashcam.py", line 3411, in main
    video_settings["source_folder"], args.exclude_subdirs, video_settings
  File "/usr/local/lib/python3.7/site-packages/tesla_dashcam/tesla_dashcam.py", line 1161, in get_movie_files
    [front_path, left_path, right_path, rear_path],
  File "/usr/local/lib/python3.7/site-packages/tesla_dashcam/tesla_dashcam.py", line 1311, in get_metadata
    line_split[1].strip(), "%Y-%m-%dT%H:%M:%S.%f%z"
  File "/usr/local/lib/python3.7/_strptime.py", line 577, in _strptime_datetime
    tt, fraction, gmtoff_fraction = _strptime(data_string, format)
  File "/usr/local/lib/python3.7/_strptime.py", line 359, in _strptime
    (data_string, format))
ValueError: time data '2019-10-06 19:12:18' does not match format '%Y-%m-%dT%H:%M:%S.%f%z'

Download a newer version of ffmpeg. Same issue was reported earlier (Issue #93) and was resolved by updating ffmpeg from 2.8.15 to 4.x.
2.8.15 is now a very old version BTW.

Wow didn't expect that fast of a response.  Going to update now.   not to derail this but is there any other documentation on using the docker container?  I'll post results shortly on the ffmpeg upgrade

This is definitely my fault, updating the ffmpeg fixed it.  Not sure how I missed the other issue already opened.  Thank you.

Wow didn't expect that fast of a response. Going to update now. not to derail this but is there any other documentation on using the docker container? I'll post results shortly on the ffmpeg upgrade

Sorry no, someone provided that to me to make it easy to have with Docker container but I have never used it or so.


fix(Tactic/PushNeg): add consumeMData to push_neg

Exprs now have an mdata field.  It seems that this gets in the way of push_neg, as reported on Zulip.
The above seems to fix the reported errors.

Alex, thanks for the comment!  I had not come across cleanupAnnotations: I simply search the Expr file for mdata guessing that there was a way to extract the defeq part of the term...

Thanks!
bors r+


Corrections and additions for Punjabi Shahmukhi (Arabic script)

These updates are concerned with correcting the set of characters used for the language. When I have time in the future, I will add sample text as well that mirrors that of the Punjabi Gurmukhi file. Thank you

@bgo-eiu The data originally comes from the CLDR https://github.com/unicode-org/cldr/blob/aa0dd5acb1e68876c730e90ef6cb43cfc4d7006f/common/main/pa_Arab.xml#L32-L36.
These changes look likes they are replacing ڻ used in Panjabi [pa] by ݨ which is used in Saraiki [skr] or Western Panjabi [pnb], and adding ࣇ which is used in Western Panjabi [pnb].
Note that Panjabi [pa] in ISO 639-1 is called "Eastern Panjabi" in Ethnologue and Panjabi [pan] in ISO 639-3).
Should these changes be a separate language data file for Western Panjabi pnb_Arab.textproto?
If this is indeed for Eastern Panjabi [pan], do you have a reference.
Elena Bashir and Thomas J. Conners, with Brook Hefright, A Descriptive Grammar of Hindko, Panjabi, and Saraiki, 2019, p. 65 indicates ݨ is used in Saraiki and ن is used in Panjabi.
Lorna Priest Evans and M. G. Abbas Malik, Proposal to encode ARABIC LETTER LAM WITH SMALL ARABIC LETTER TAH ABOVE in the UCS, 2019 shows ݨ being used in Punjabi but it does indicate Western Punjabi uses the Arabic script (Shahmukhi) and hasn’t been standardized.
I’m leaning towards creating a separate file for Western Panjabi [pnb].


feat: improve the Project flow in cli

[x] List

[x] Delete

[x] Create

[ ] View

In the view where we display project information, we will also list the scanners and repositories associated with that project.

@Vad1mo

Test Case :

[ ] Project
[ ] Registry

We handle projects in this PR only. Will open a separate one for the registry. I've also added subcommands logs to the project command recently.

keep in mind that the harbor CLIs should also be usable in non-interactive mode, In CI/CD pipelines, in scripts. piping in yaml/json and outputting jsons/yaml are equally important.

It will works both ways.

added table for project logs -


Support for the 834: Benefit Enrollment and Maintenance

It would be nice if there would be an 834 sample in the test/Models folder.

Hi @michaelachrisco and thank you for your interest.
Unfortunately the time is limited but If you get something working you can add a test with your sample data and code and submit a pull request.
This is the case with the other samples as well and that will help future integrators.

Sounds like a plan. Ill plan on building out the 834.

834 class has been created and works as intended for writing. Reading, on the other hand, seems to not be working. I may revisit at some later time.

I'm still getting issues with the reading structure. I can partially read and the write tests all pass. @cleftheris Would you an open PR with the changes (so we/the community can collaborate) or wait until I get it working on both reading and writing? It may take a while...
Either way, thanks for the library! Its been working out great!


[2.0] After successfully SignIn "IsAuthenticated" (IIdentity) property is always false even all claims are set.

Hi.
My code in ConfigureServices method in Startup.cs
            services.AddAuthentication()                 .AddCookie(c =>                 {                     c.LoginPath = new PathString("/User/SignIn");                     c.ExpireTimeSpan = TimeSpan.FromDays(1);                     c.SlidingExpiration = true;                     c.Cookie.Name = "RodoApiAuthCookie";                     c.AccessDeniedPath = "/User/AccessDenied";                 })                 .AddJwtBearer(opt =>                 {                     opt.Audience = Configuration["Auth:Audience"];                     opt.ClaimsIssuer = Configuration["Auth:Issuer"];                     opt.SaveToken = true;                     opt.TokenValidationParameters = new TokenValidationParameters                     {                         RequireExpirationTime = true,                         RequireSignedTokens = true,                         ValidateIssuerSigningKey = true,                         IssuerSigningKey = signingKey,                         ValidateIssuer = true,                         ValidIssuer = Configuration["Auth:Issuer"],                         ValidateAudience = true,                         ValidAudience = Configuration["Auth:Audience"],                         ValidateLifetime = true,                         ClockSkew = TimeSpan.Zero                     };                 });
After succesfully SignIn I can't use  [Authorize(AuthenticationSchemes = [SLECETED_SCHEMES])] becasue "IsAuthenticate" property is set to false but all claims created during the SignIn are set:

How can I use [Authorize] attribute without getting acces denied?
Best regards.

You need to specify an AuthenticationType in the claims identity as that's what IsAuthenticated is testing

@HaoK big up for you. Thanks. Issue can be closed.


npm下载包问题

下载最新版的npm包mind-ar-js，一直处于下载中，请尽快解决

that's probably not an issue with the library. maybe npm or your network.
I'm closing it for now. Feel free to reopen the issue if you think otherwise.


Inject PreviewComponent into Dropzone

Hi!
I am trying to inject the PreviewComponent into the Dropzone area with the already existing images once the user wants to edit the created object. I have visited your page and the link pointing to this feature redirects me to an non-existing git page. Is there a way I could accomplish this? Thanks!

I think what you want is covered by the initial file from data-url example:  https://react-dropzone-uploader.js.org/docs/examples#initial-file-from-data-url
The URL doesn't have to be a data: url, you can fetch() from wherever you would like.

Important to note that files in initialFiles will automatically upload

When I use images url link array like:
['http://some-path.jpeg' , 'http://some-other-path.jpeg']
as initial files value, its not working,
also the error shown as below:

Unhandled Rejection (TypeError): Cannot read property 'startsWith' of undefined

Can anyone help me to solve this problem?
Thank you.


Freeze versions of dependences

I got error
root@70afd670efdc:/# pip freeze
html5lib==0.999999999
Pillow==3.3.0
PyPDF2==1.26.0
reportlab==3.3.0
six==1.10.0
virtualenv==14.0.6
webencodings==0.5
wheel==0.29.0
xhtml2pdf==0.0.6
You are using pip version 7.1.2, however version 8.1.2 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
root@70afd670efdc:/# python -c "from xhtml2pdf import pisa"
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "/usr/local/lib/python2.7/site-packages/xhtml2pdf/pisa.py", line 3, in <module>
    from xhtml2pdf.document import pisaDocument
  File "/usr/local/lib/python2.7/site-packages/xhtml2pdf/document.py", line 2, in <module>
    from xhtml2pdf.context import pisaContext
  File "/usr/local/lib/python2.7/site-packages/xhtml2pdf/context.py", line 23, in <module>
    import xhtml2pdf.parser
  File "/usr/local/lib/python2.7/site-packages/xhtml2pdf/parser.py", line 17, in <module>
    from html5lib import treebuilders, inputstream
ImportError: cannot import name inputstream
root@70afd670efdc:/#

I found out that html5lib have breaking changes at new version (https://github.com/html5lib/html5lib-python/issues/295),  but this could have been avoided if the version has been fixed.

https://github.com/xhtml2pdf/xhtml2pdf/pull/321

Okay thanks for reporting this, it's been fixed in 1.0b3


Implement TensorFlow.js model loading

Following these references:

tfjs iris example
Image recognition with TensorFlow.js

I attempted to load model via tf.loadLayersModel but ran into the following error:
Error: Unknown layer: Addons>InstanceNormalization. This may be due to one of the following reasons:
1. The layer is defined in Python, in which case it needs to be ported to TensorFlow.js or your JavaScript code.
2. The custom layer is defined in JavaScript, but is not registered properly with tf.serialization.registerClass().

Some references suggested using graph model instead:

https://github.com/tensorflow/tfjs/issues/3728
https://github.com/tensorflow/tfjs/issues/3410

References for saving and loading model:

https://www.tensorflow.org/js/tutorials/conversion/import_saved_model
https://www.tensorflow.org/tutorials/keras/save_and_load

I was able to successfully work around this issue by saving the weights using the SavedModel format as described in the SavedModel format tutorial.
From there, I converted the model weights to TensorFlow.js web format following TensorFlow.js importing GraphDef models tutorial. Exact command:
tensorflowjs_converter --input_format=tf_saved_model build/monet/epoch1/photo2painting build/monet/epoch1/photo2painting-web


numbskull requires manual pip install

Numbskull won't install using "pip install --requirement python-package-requirement.txt" and needs to be installed with local project repository. Add a separate description in the installation notes for numbskull installation after the general pip package install.

Added to README


Fix bug that null acl in bucket table

What this PR does / why we need it:
Fix bug that null acl in bucket table when create bucket
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #820
Special notes for your reviewer:
Release note:

LGTM


feat: Add Type.Assert HKT that implements behavior of TypeScript as assertions, and add Type.Cast improvements

Adds new HKT Type.Assert, which performs type casting to related subtypes and supertypes, but returns never for impossible coercions.
Type._$cast is now non-distributive for union input params.

No functional change, but makes the intent of the implementation a bit clearer.
Rough proof of equivalence:

1. CastDistributive<T, U> = T extends U ? T : U
CastDistributive<A | B, U>
<=> | (A extends U ? A : U)
    | (B extends U ?  CastNonDistributive<T, U> = [T] extends [U] ? T : U
CastNonDistributive<A | B, U>
<=> [A | B] extends [U] ?  T : U is equivalent to [T] extends [U] ? T : U - to my knowledge there existed a pair ($T$, $U$) such that the equivalence did not hold true - but I wasn't able to prove this, and all the tests pass.

Maybe you were thinking of T extends never vs. [T] extends [never]? It's true that those are not equivalent statements, but T extends never ? T : never and [T] extends [never] ? T : never should both always evaluate to never.


Airflow error while running this image from your helm chart #2

Hey,
I'm trying to use a postgres back-end but keep getting this error. Have you come across this?
kubectl -n dev logs -p mlflow-airflow-webserver-b6778f8db-pmzfs
Traceback (most recent call last):
  File "/home/airflow/.local/bin/airflow", line 25, in <module>
    from airflow.configuration import conf
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/__init__.py", line 31, in <module>
    from airflow.utils.log.logging_mixin import LoggingMixin
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/utils/__init__.py", line 24, in <module>
    from .decorators import apply_defaults as _apply_defaults
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/utils/decorators.py", line 36, in <module>
    from airflow import settings
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/settings.py", line 37, in <module>
    from airflow.configuration import conf, AIRFLOW_HOME, WEBSERVER_CONFIG  # NOQA F401
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/configuration.py", line 622, in <module>
    conf.read(AIRFLOW_CONFIG)
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/configuration.py", line 348, in read
    self._validate()
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/configuration.py", line 204, in _validate
    self.get('core', 'executor')))
airflow.exceptions.AirflowConfigException: error: cannot use sqlite with the KubernetesExecutor

I have same issue but with official airflow image + some additional dependencies installed...
 Warning  Unhealthy  2m3s (x196 over 4h54m)  kubelet, aks-toolset-22416452-vmss000001  Liveness probe failed: Traceback (most recent call last):
  File "<string>", line 4, in <module>
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/__init__.py", line 31, in <module>
    from airflow.utils.log.logging_mixin import LoggingMixin
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/utils/__init__.py", line 24, in <module>
    from .decorators import apply_defaults as _apply_defaults
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/utils/decorators.py", line 36, in <module>
    from airflow import settings
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/settings.py", line 37, in <module>
    from airflow.configuration import conf, AIRFLOW_HOME, WEBSERVER_CONFIG  # NOQA F401
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/configuration.py", line 731, in <module>
    conf.read(AIRFLOW_CONFIG)
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/configuration.py", line 421, in read
    self._validate()
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/configuration.py", line 213, in _validate
    self._validate_config_dependencies()
  File "/home/airflow/.local/lib/python3.6/site-packages/airflow/configuration.py", line 247, in _validate_config_dependencies
    self.get('core', 'executor')))
airflow.exceptions.AirflowConfigException: error: cannot use sqlite with the KubernetesExecutor

I have the same problem and I saw that the /opt/airflow/airflow.cfg, that is dynamically generated, has this config inside:
sql_alchemy_conn = sqlite:////opt/airflow/airflow.db

As I don't know exactly how the airflow.cfg is generated, I made a patch on the airflow-scheduler deployment because I know exactly how Kubernetes works.
Original airflow-scheduler deployment:
[...]
- args:
  - bash
  - -c
  - |-
    true \
     && mkdir -p /home/airflow/.local/bin \
     && echo 'export PATH="/home/airflow/.local/bin:$PATH"' >> /home/airflow/airflow_env.sh \
     && echo 'export AIRFLOW__CORE__SQL_ALCHEMY_CONN="postgresql+psycopg2://${DATABASE_USER}:$( echo ${DATABASE_PASSWORD} | python3 -c "import urllib.parse; encoded_pass = urllib.parse.quote(input()); print(encoded_pass)" )@${DATABASE_HOST}:${DATABASE_PORT}/${DATABASE_DB}${DATABASE_PROPERTIES}"' >> /home/airflow/airflow_env.sh \
     && echo 'source /home/airflow/airflow_env.sh' >> /home/airflow/.profile \
     && echo 'source /home/airflow/airflow_env.sh' >> /home/airflow/.bashrc \
     && source /home/airflow/airflow_env.sh \
     && echo "*** installing global extra pip packages..." \
     && pip install --user  "ldap3==2.8.1"  \
     && echo "*** executing Airflow initdb..." \
     && airflow initdb \
     && echo "*** adding Airflow variables..." \
     && airflow variables -i /home/airflow/variables-pools/variables.json \
     && echo "*** adding Airflow connections..." \
     && /home/airflow/connections/add-connections.sh \
     && echo "*** adding Airflow pools..." \
     && airflow pool -i /home/airflow/variables-pools/pools.json \
     && echo "*** running scheduler..." \
     && exec airflow scheduler -n -1
[...]

Changed airflow-scheduler deployment:
[...]
- args:
  - bash
  - -c
  - |-
    true \
     && mkdir -p /home/airflow/.local/bin \
     && echo 'export PATH="/home/airflow/.local/bin:$PATH"' >> /home/airflow/airflow_env.sh \
     && echo 'export AIRFLOW__CORE__SQL_ALCHEMY_CONN="postgresql+psycopg2://${DATABASE_USER}:$( echo ${DATABASE_PASSWORD} | python3 -c "import urllib.parse; encoded_pass = urllib.parse.quote(input()); print(encoded_pass)" )@${DATABASE_HOST}:${DATABASE_PORT}/${DATABASE_DB}${DATABASE_PROPERTIES}"' >> /home/airflow/airflow_env.sh \
     && echo 'source /home/airflow/airflow_env.sh' >> /home/airflow/.profile \
     && echo 'source /home/airflow/airflow_env.sh' >> /home/airflow/.bashrc \
     && source /home/airflow/airflow_env.sh \
     && echo "*** installing global extra pip packages..." \
     && pip install --user  "ldap3==2.8.1"  \
     && echo "*** executing Airflow initdb..." \
     && airflow initdb \
     && echo "*** patching airflow.cfg sql_alchemy_conn section..." \
     && sed -i "s#sql_alchemy_conn.*#sql_alchemy_conn = $AIRFLOW__CORE__SQL_ALCHEMY_CONN#" /opt/airflow/airflow.cfg \
     && echo "*** adding Airflow variables..." \
     && airflow variables -i /home/airflow/variables-pools/variables.json \
     && echo "*** adding Airflow connections..." \
     && /home/airflow/connections/add-connections.sh \
     && echo "*** adding Airflow pools..." \
     && airflow pool -i /home/airflow/variables-pools/pools.json \
     && echo "*** running scheduler..." \
     && exec airflow scheduler -n -1
[...]