Support production mode

@micgur01 thanks for the PR!
Can you please edit the comment section of the PR and add more information what's being added and details on the enhancement?
Also, I see many changes on this PR. Are all of them required?
Have you tested this on a platform?
If so, can you share the results of the tests? (see https://github.com/ARMmbed/simple-mbed-cloud-client#testing)

file simple-mbed-cloud-client.cpp

removed some unnecessary includes
put "update_client_hub.h" under DEV flag
ARM_UC_SetVendorId should be set only for development mode as well

storage_helper has to be changed as Factory Configuration Client Example  uses partition mode
we have to support it here or changed the FCCE behavior.
file storage_helper.h
mcc_platform_storage_size  moved into the class and put under MCC_PLATFORM_PARTITION_MODE ==1
it's used only for partition mode
same for create_partitions(void); function
It was passed compilation in case MCC_PLATFORM_PARTITION_MODE mode enabled
file storage_helper.cpp
has to be initialize - fs1(NULL), fs2(NULL), part1(NULL), part2(NULL)
The code moved to be C++, but it was never compiled and used for partition mode
Using same code as Mbed Clound Client Example , changes are for C++ only
has to use class members, _bd and create_partitions

I've tested on K64F, L429ZI and F496ZG target
All connected to Cloud on both development and production mode
Changes has to be aligned with mbed_app.json from this pull request
https://github.com/ARMmbed/simple-mbed-cloud-client-template-restricted/pull/44

Can you share the tests results when using mbed tests ... please?
https://github.com/ARMmbed/simple-mbed-cloud-client#testing

I did not run tests yet, going to run it now
never done it before, trying to find out easiest way to do so

@micgur01 You could try to import the https://github.com/ARMmbed/pelion-enablement repository, which has configuration for many of the currently supported platforms.

It's not correct to format before storage init, it could be used partition mode
in case of problem it formats the correct partition ( if failed to verify_cloud_configuration)
merged the last changes and run tests , results below
mbedgt: all tests finished!
mbedgt: shuffle seed: 0.4297118341
mbedgt: test suite report:
+--------------+---------------+------------------------------+--------+--------------------+-------------+
| target       | platform_name | test suite                   | result | elapsed_time (sec) | copy_method |
+--------------+---------------+------------------------------+--------+--------------------+-------------+
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | OK     | 133.17             | default     |
+--------------+---------------+------------------------------+--------+--------------------+-------------+
mbedgt: test suite results: 1 OK
mbedgt: test case report:
+--------------+---------------+------------------------------+----------------------------+--------+--------+--------+--------------------+
| target       | platform_name | test suite                   | test case                  | passed | failed | result | elapsed_time (sec) |
+--------------+---------------+------------------------------+----------------------------+--------+--------+--------+--------------------+
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | Connect to Network         | 1      | 0      | OK     | 6.55               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | Consistent Identity        | 1      | 0      | OK     | 2.12               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | Initialize Storage         | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | LwM2M GET Test             | 1      | 0      | OK     | 1.14               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | LwM2M POST Test            | 1      | 0      | OK     | 0.67               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | LwM2M PUT Test             | 1      | 0      | OK     | 0.82               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | LwM2M SET Test             | 1      | 0      | OK     | 0.45               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | Pelion DM Bootstrap & Reg. | 1      | 0      | OK     | 12.17              |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | Pelion DM Directory        | 1      | 0      | OK     | 6.29               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | Pelion DM Re-register      | 1      | 0      | OK     | 4.96               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | Simple PDMC Initialization | 1      | 0      | OK     | 17.81              |
+--------------+---------------+------------------------------+----------------------------+--------+--------+--------+--------------------+
mbedgt: test case results: 10 OK / 1 ERROR
mbedgt: completed in 139.33 sec

All tested passed, consistently
| target       | platform_name | test suite                   | test case                  | passed | failed | result | elapsed_time (sec) |
+--------------+---------------+------------------------------+----------------------------+--------+--------+--------+--------------------+
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | Connect to Network         | 1      | 0      | OK     | 7.05               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | Consistent Identity        | 1      | 0      | OK     | 2.12               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | Initialize Storage         | 1      | 0      | OK     | 0.04               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | LwM2M GET Test             | 1      | 0      | OK     | 1.06               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | LwM2M POST Test            | 1      | 0      | OK     | 0.66               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | LwM2M PUT Test             | 1      | 0      | OK     | 0.93               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | LwM2M SET Test             | 1      | 0      | OK     | 0.54               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | Pelion DM Bootstrap & Reg. | 1      | 0      | OK     | 11.69              |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | Pelion DM Directory        | 1      | 0      | OK     | 6.01               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | Pelion DM Re-register      | 1      | 0      | OK     | 4.91               |
| K64F-GCC_ARM | K64F          | spdmc-tests-dev_mgmt-connect | Simple PDMC Initialization | 1      | 0      | OK     | 17.8               |
+--------------+---------------+------------------------------+----------------------------+--------+--------+--------+--------------------+
mbedgt: test case results: 11 OK
mbedgt: completed in 141.13 sec

Rebased and update test according to production flow both connect and update tests.
all tests related to connect and update passed, some tests failed with strange error and last 0 sec
looks like it doesn't really run, but not related to my changes
Running latest simple-mbed-cloud-client get the same errors...
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet   128 buffer                    | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet   256 buffer                    | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet  1024 buffer                    | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet  4096 buffer                    | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet network setup                   | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-threaded  | Ethernet 1 thread                        | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-threaded  | Ethernet 2 threads                       | 0      | 0      | ERROR  | 0.0
here the results:
+--------------+---------------+----------------------------------------------------+--------+--------------------+-------------+
| target       | platform_name | test suite                                         | result | elapsed_time (sec) | copy_method |
+--------------+---------------+----------------------------------------------------+--------+--------------------+-------------+
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-fs-single     | OK     | 5525.1             | default     |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-fs-threaded   | OK     | 123.49             | default     |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-single    | OK     | 78.83              | default     |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-threaded  | OK     | 56.53              | default     |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-stress-net-fs | OK     | 106.61             | default     |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-connect    | OK     | 129.9              | default     |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-update     | OK     | 257.44             | default     |
+--------------+---------------+----------------------------------------------------+--------+--------------------+-------------+
mbedgt: test suite results: 7 OK
mbedgt: test case report:
+--------------+---------------+----------------------------------------------------+------------------------------------------+--------+--------+--------+--------------------+
| target       | platform_name | test suite                                         | test case                                | passed | failed | result | elapsed_time (sec) |
+--------------+---------------+----------------------------------------------------+------------------------------------------+--------+--------+--------+--------------------+
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff     1                | 1      | 0      | OK     | 18.07              |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff     4                | 1      | 0      | OK     | 18.19              |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff    16                | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff    64                | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff   256                | 1      | 0      | OK     | 17.91              |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff  1024                | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff  4096                | 1      | 0      | OK     | 17.52              |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff 16384                | 1      | 0      | OK     | 17.97              |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT format                            | 1      | 0      | OK     | 0.13               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-fs-threaded   | SD+FAT 2 files, buff 4b/256b             | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-fs-threaded   | SD+FAT 3 files, buff 256b/1kb/4kb        | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-fs-threaded   | SD+FAT format                            | 1      | 0      | OK     | 0.09               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet   128 buffer                    | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet   256 buffer                    | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet  1024 buffer                    | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet  4096 buffer                    | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet network setup                   | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-threaded  | Ethernet 1 thread                        | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-threaded  | Ethernet 2 threads                       | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-net-threaded  | Ethernet network setup                   | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-stress-net-fs | Ethernet network setup                   | 1      | 0      | OK     | 7.01               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-stress-net-fs | SD+FAT format                            | 1      | 0      | OK     | 0.08               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-stress-net-fs | SD+FAT+Ethernet 1 thread, dl, file seq.  | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-stress-net-fs | SD+FAT+Ethernet 2 threads, dl, 1kb       | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-basic-stress-net-fs | SD+FAT+Ethernet 3 threads, dl, 256b, 1kb | 0      | 0      | ERROR  | 0.0                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Connect to Ethernet                      | 2      | 0      | OK     | 7.05               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Initialize Simple PDMC                   | 2      | 0      | OK     | 17.86              |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Initialize Storage                       | 1      | 0      | OK     | 0.05               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Pelion Bootstrap & Reg.                  | 1      | 0      | OK     | 15.49              |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Pelion Directory                         | 1      | 0      | OK     | 0.95               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Pelion Re-register                       | 1      | 0      | OK     | 5.25               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Post-reset Identity                      | 1      | 0      | OK     | 0.11               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Resource LwM2M GET                       | 1      | 0      | OK     | 6.33               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Resource LwM2M POST                      | 1      | 0      | OK     | 0.67               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Resource LwM2M PUT                       | 1      | 0      | OK     | 0.9                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Resource LwM2M SET                       | 1      | 0      | OK     | 0.43               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-update     | Connect to Ethernet                      | 2      | 0      | OK     | 5.05               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-update     | Initialize Simple PDMC                   | 2      | 0      | OK     | 17.85              |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-update     | Initialize Storage                       | 1      | 0      | OK     | 0.05               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Bootstrap & Reg.                  | 1      | 0      | OK     | 15.83              |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Directory                         | 1      | 0      | OK     | 1.2                |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Firmware Download                 | 1      | 0      | OK     | 108.61             |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Firmware Prepare                  | 1      | 0      | OK     | 0.86               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Firmware Update                   | 1      | 0      | OK     | 31.67              |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Re-register                       | 1      | 0      | OK     | 5.29               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-update     | Post-update Erase                        | 1      | 0      | OK     | 0.01               |
| K64F-GCC_ARM | K64F          | simple-mbed-cloud-client-tests-dev_mgmt-update     | Post-update Identity                     | 1      | 0      | OK     | 0.1                |
+--------------+---------------+----------------------------------------------------+------------------------------------------+--------+--------+--------+--------------------+
mbedgt: test case results: 31 OK / 16 ERROR
mbedgt: completed in 6321.77 sec

I've got it now, why I had to changed it at first place
this code used to format SD before your last changes
int storage_status = client.reformat_storage();
I had to change it, but you are not using now client to format file system now
only function of file system, so I suppose it should be fine now

@micgur01 Can you try to minimize the changes to the tests and rather focus on SMCC? Ideally there should be no impact on the developer application, where the test is also a developer application.

@micgur01 Further failures on more targets - see below.
[2018-12-05 21:32:28] INFO: EXEC: "mbed test --compile -t ARM -m MTB_USI_WM_BN_BM_22 -n simple-mbed-cloud-client-tests* -v" (code: 0)
None
[2018-12-05 21:32:28] ERROR: FAILED: "mbed test --run -t ARM -m MTB_USI_WM_BN_BM_22 --report-json TEST_OUTPUT\e0c32da4c8ab4763770560b7eb98e5bc5e876dbc\2018-12-05 20-52-28/MTB_USI_WM_BN_BM_22_ARM_results.json -n simple-mbed-cloud-client-tests* -v" (code: 2)
None
[2018-12-05 21:32:28] INFO: TEST RESULTS

+-------------------------+---------------------+----------------------------------------------------+----------------------------------------+--------+--------+---------+--------+
| target                  | platform_name       | test suite                                         | test case                              | passed | failed | result  |   time |
+-------------------------+---------------------+----------------------------------------------------+----------------------------------------+--------+--------+---------+--------+
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-net-single    | WiFi   128 buffer                      | 1      | 0      | OK      |   9.38 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-net-single    | WiFi   256 buffer                      | 1      | 0      | OK      |    5.7 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-net-single    | WiFi  1024 buffer                      | 1      | 0      | OK      |   5.64 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-net-single    | WiFi  4096 buffer                      | 1      | 0      | OK      |   2.61 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-net-single    | WiFi network setup                     | 1      | 0      | OK      |   8.48 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-net-single    | ----- TOTAL -----                      | 5      | 0      | OK      |  87.74 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-stress-net-fs | SPIF+LFS format                        | 1      | 0      | OK      |   0.14 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-stress-net-fs | SPIF+LFS+WiFi 1 thread, dl, file seq.  | 1      | 0      | OK      |   5.64 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-stress-net-fs | SPIF+LFS+WiFi 2 threads, dl, 1kb       | 1      | 0      | OK      |  11.56 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-stress-net-fs | SPIF+LFS+WiFi 3 threads, dl, 256b, 1kb | 1      | 0      | OK      |  19.72 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-stress-net-fs | WiFi network setup                     | 1      | 0      | OK      |   8.48 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-stress-net-fs | ----- TOTAL -----                      | 5      | 0      | OK      | 102.78 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-net-threaded  | WiFi 1 thread                          | 1      | 0      | OK      |   5.15 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-net-threaded  | WiFi 2 threads                         | 1      | 0      | OK      |    4.2 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-net-threaded  | WiFi network setup                     | 1      | 0      | OK      |   6.48 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-net-threaded  | ----- TOTAL -----                      | 3      | 0      | OK      |  73.28 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-fs-threaded   | SPIF+LFS 2 files, buff 4b/256b         | 1      | 0      | OK      |  16.53 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-fs-threaded   | SPIF+LFS 3 files, buff 256b/1kb/4kb    | 1      | 0      | OK      |  23.04 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-fs-threaded   | SPIF+LFS format                        | 1      | 0      | OK      |   0.15 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-fs-threaded   | ----- TOTAL -----                      | 3      | 0      | OK      |  79.68 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Connect to WiFi                        | 1      | 0      | OK      |   8.53 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Initialize Simple PDMC                 | 0      | 1      | FAIL    |  36.21 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Initialize Storage                     | 1      | 0      | OK      |   0.03 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Pelion Bootstrap & Reg.                | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Pelion Directory                       | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Pelion Re-register                     | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Post-reset Identity                    | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Resource LwM2M GET                     | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Resource LwM2M POST                    | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Resource LwM2M PUT                     | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Resource LwM2M SET                     | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-connect    | ----- TOTAL -----                      | 2      | 1      | FAIL    | 106.28 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-fs-single     | SPIF+LFS 1 file, buff     1            | 1      | 0      | OK      |  10.06 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-fs-single     | SPIF+LFS 1 file, buff     4            | 1      | 0      | OK      |   8.27 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-fs-single     | SPIF+LFS 1 file, buff    16            | 1      | 0      | OK      |   8.02 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-fs-single     | SPIF+LFS 1 file, buff    64            | 1      | 0      | OK      |   7.86 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-fs-single     | SPIF+LFS 1 file, buff   256            | 1      | 0      | OK      |   7.85 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-fs-single     | SPIF+LFS 1 file, buff  1024            | 1      | 0      | OK      |   7.77 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-fs-single     | SPIF+LFS 1 file, buff  4096            | 1      | 0      | OK      |    7.3 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-fs-single     | SPIF+LFS 1 file, buff 16384            | 1      | 0      | OK      |   7.19 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-fs-single     | SPIF+LFS format                        | 1      | 0      | OK      |   0.16 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-basic-fs-single     | ----- TOTAL -----                      | 9      | 0      | OK      | 107.23 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-update     | Connect to WiFi                        | 1      | 0      | OK      |   6.54 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-update     | Initialize Simple PDMC                 | 0      | 1      | FAIL    |  36.21 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-update     | Initialize Storage                     | 1      | 0      | OK      |   0.03 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Bootstrap & Reg.                | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Directory                       | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Firmware Download               | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Firmware Prepare                | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Firmware Update                 | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Re-register                     | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-update     | Post-update Erase                      | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-update     | Post-update Identity                   | 0      | 0      | SKIPPED |    0.0 |
| MTB_USI_WM_BN_BM_22-ARM | MTB_USI_WM_BN_BM_22 | simple-mbed-cloud-client-tests-dev_mgmt-update     | ----- TOTAL -----                      | 2      | 1      | FAIL    | 103.93 |
+-------------------------+---------------------+----------------------------------------------------+----------------------------------------+--------+--------+---------+--------+

[2018-12-05 21:41:34] INFO: EXEC: "mbed test --compile -t ARM -m NUCLEO_F767ZI -n simple-mbed-cloud-client-tests* -v" (code: 0)
None
[2018-12-05 21:41:34] ERROR: FAILED: "mbed test --run -t ARM -m NUCLEO_F767ZI --report-json TEST_OUTPUT\e0c32da4c8ab4763770560b7eb98e5bc5e876dbc\2018-12-05 20-52-28/NUCLEO_F767ZI_ARM_results.json -n simple-mbed-cloud-client-tests* -v" (code: 3)
None
[2018-12-05 21:41:34] INFO: TEST RESULTS

+-------------------+---------------+----------------------------------------------------+------------------------------------------+--------+--------+---------+--------+
| target            | platform_name | test suite                                         | test case                                | passed | failed | result  |   time |
+-------------------+---------------+----------------------------------------------------+------------------------------------------+--------+--------+---------+--------+
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet   128 buffer                    | 1      | 0      | OK      |   9.28 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet   256 buffer                    | 1      | 0      | OK      |   5.53 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet  1024 buffer                    | 1      | 0      | OK      |   1.87 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet  4096 buffer                    | 1      | 0      | OK      |   1.86 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-net-single    | Ethernet network setup                   | 1      | 0      | OK      |   3.01 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-net-single    | ----- TOTAL -----                        | 5      | 0      | OK      |  42.91 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-stress-net-fs | Ethernet network setup                   | 1      | 0      | OK      |   4.01 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-stress-net-fs | SD+FAT format                            | 1      | 0      | OK      |   0.08 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-stress-net-fs | SD+FAT+Ethernet 1 thread, dl, file seq.  | 1      | 0      | OK      |   5.61 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-stress-net-fs | SD+FAT+Ethernet 2 threads, dl, 1kb       | 1      | 0      | OK      |  23.31 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-stress-net-fs | SD+FAT+Ethernet 3 threads, dl, 256b, 1kb | 1      | 0      | OK      |  42.38 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-stress-net-fs | ----- TOTAL -----                        | 5      | 0      | OK      |   97.4 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-net-threaded  | Ethernet 1 thread                        | 1      | 0      | OK      |   1.88 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-net-threaded  | Ethernet 2 threads                       | 1      | 0      | OK      |   3.93 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-net-threaded  | Ethernet network setup                   | 1      | 0      | OK      |   3.01 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-net-threaded  | ----- TOTAL -----                        | 3      | 0      | OK      |  30.11 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-fs-threaded   | SD+FAT 2 files, buff 4b/256b             | 1      | 0      | OK      |  37.17 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-fs-threaded   | SD+FAT 3 files, buff 256b/1kb/4kb        | 1      | 0      | OK      |  60.01 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-fs-threaded   | SD+FAT format                            | 1      | 0      | OK      |   0.08 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-fs-threaded   | ----- TOTAL -----                        | 3      | 0      | OK      | 117.89 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Connect to Ethernet                      | 1      | 0      | OK      |   4.05 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Initialize Simple PDMC                   | 0      | 1      | FAIL    |  85.59 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Initialize Storage                       | 1      | 0      | OK      |   0.04 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Pelion Bootstrap & Reg.                  | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Pelion Directory                         | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Pelion Re-register                       | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Post-reset Identity                      | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Resource LwM2M GET                       | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Resource LwM2M POST                      | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Resource LwM2M PUT                       | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-connect    | Resource LwM2M SET                       | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-connect    | ----- TOTAL -----                        | 2      | 1      | FAIL    |  114.1 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff     1                | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff     4                | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff    16                | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff    64                | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff   256                | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff  1024                | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff  4096                | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT 1 file, buff 16384                | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-fs-single     | SD+FAT format                            | 0      | 1      | FAIL    |   0.03 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-basic-fs-single     | ----- TOTAL -----                        | 0      | 1      | FAIL    |   20.7 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-update     | Connect to Ethernet                      | 1      | 0      | OK      |   4.55 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-update     | Initialize Simple PDMC                   | 0      | 1      | FAIL    |  68.83 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-update     | Initialize Storage                       | 1      | 0      | OK      |   0.05 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Bootstrap & Reg.                  | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Directory                         | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Firmware Download                 | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Firmware Prepare                  | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Firmware Update                   | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-update     | Pelion Re-register                       | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-update     | Post-update Erase                        | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-update     | Post-update Identity                     | 0      | 0      | SKIPPED |    0.0 |
| NUCLEO_F767ZI-ARM | NUCLEO_F767ZI | simple-mbed-cloud-client-tests-dev_mgmt-update     | ----- TOTAL -----                        | 2      | 1      | FAIL    |  97.72 |
+-------------------+---------------+----------------------------------------------------+------------------------------------------+--------+--------+---------+--------+

sure, I am rolling back test changes now, after your fix
as client not formatting filesystem before init, it should not be a problem
this was the case on released 2.0.1 code

Hi
Could you please rerun the tests now?
rollback the test changes
Could you please help me to fix the SYNC_FAILED
after this upgrade , can't run the tests anymore.
pip install -U mbed-host-tests mbed-greentea – done

by the way, are you running the tests using corresponded pull request?
https://github.com/ARMmbed/simple-mbed-cloud-client-template-restricted/pull/44
also test compilation and run include --app-config mbed_app_test.json.

Merging to continue testing on production-workflow branch


Eloquent: Associative parameter binding is broken

https://github.com/laravel/framework/blob/master/src/Illuminate/Database/Query/Builder.php#L2048
    /**
     * Add a binding to the query.
     *
     * @param  mixed   $value
     * @param  string  $type
     * @return $this
     *
     * @throws \InvalidArgumentException
     */
    public function addBinding($value, $type = 'where')
    {
        if (! array_key_exists($type, $this->bindings)) {
            throw new InvalidArgumentException("Invalid binding type: {$type}.");
        }
        if (is_array($value)) {
            $this->bindings[$type] = array_values(array_merge($this->bindings[$type], $value));
        } else {
            $this->bindings[$type][] = $value;
        }
        return $this;
    }

Because of the array_values call, all associative keys are discarded and only the order in which the elements were defined in the array matters.
This works:
$users = User::whereRaw('userId = :userId AND email = :email', [
    'userId' => 1,
    'email' =><EMAIL_ADDRESS>]);

This does not work:
$users = User::whereRaw('userId = :userId AND email = :email', [
    'email' =><EMAIL_ADDRESS>    'userId' => 1,
]);

I believe this is on purpose. Eloquent only works with non-associative bindings since all default clauses always add "?" bindings. And I don't really see a valid use case to change that, since it's very rare that you need to provide more than one custom binding.


error in Xcode 8 swift 3

i got an error
Module compiled with Swift 2.3 cannot be imported in Swift 3.0
how to fix?

The source code will have to be updated to 3.0.

Will it be updated?

Is anybody working on a Swift 3.0 version?

I worked on swift 3.0 and my Page view controller is not initial controller.
Not the issue is pagination style is always in curl not scroll. I want to use this as scroll transition.
Plz help in this.

Closed thanks to #104 (and possibly others)


Template does not work

Problem
if I execute dixous template, it does not work, and looks like this image.
Steps To Reproduce
Steps to reproduce the behavior:

cargo install dioxus-cli
dx new
dx serve
it happens with
 WARN dioxus_desktop::protocol: Assets built with manganis cannot be preloaded (failed to read "C:\\Users\\hirom\\RustroverProjects\\tetris\\test\\__assets_head.html"). This warning may occur when you build a desktop application without the dioxus CLI. If you do not use manganis, you can ignore this warning: 指定されたファイルが見つかりません。 (os error 2).

Expected behavior

I can execute the template successfully.
Screenshots

Environment:

Dioxus version:  v0.5.6
Rust version:    v1.80.1
OS info:    Windows 11
App platform:   desktop

Questionnaire

[ ] I'm interested in fixing this myself but don't know where to start
[ ] I would like to fix and I have a solution
[ ] I don't have time to fix this right now, but maybe later

I think the reason is because asset_dir and out_dir are not loaded.

Can you provide more information about the options you choose when running dx new. I cannot reproduce this issue with these settings: desktop, no router, vanilla or tailwind css

Can you provide more information about the options you choose when running dx new. I cannot reproduce this issue with these settings: desktop, no router, vanilla or tailwind css

I chose "desktop, no router, vanila" and this happend.
I tried to do it on windows sandbox, but this happend too.
Is your dioxus version the same as mine?
I tried to install dioxus cli of 0.6.0-alpha2, but Compile errors happend. Therefore I used 0.5.6 version.

Can you provide more information about the options you choose when running dx new. I cannot reproduce this issue with these settings: desktop, no router, vanilla or tailwind css

Or you might be using windows 10

I am currently in the same situation.
Trying to find solutions and causes.
Dioxus:0.5.6
OS:Windows11
Rust:1.80.1
Platform:desktop

link { rel: "stylesheet", href: "./assets/main.css" }
img { src: "./assets/header.svg", id: "header" }

If you add "./assets/" it will load correctly.

me too

dioxus 0.5.7
`rustc 1.79.0
sub-template: Desctop
CSS: Vanilla
router: false
Windows 11

Yeah, I get the same issue on NixOS. :/
@hiro1234omochi shouldn't this be reopened? If dx new produces broken demo code on some targets, it seems like the sort of thing that ought to be addressed.


WIP Examples

I've created a schema and some data and started creating some queries. Not sure if I've put the .sql file in the right location but happy to move it. This is only for sql server at the moment.
I've been raising issues as I go and fixed a couple of minor things (like missing uuid type and bigdecimal not being "numeric")
From a usability point of view, so far it's been ok, but not spectacular. Error messages are helpful but frequently very very long due to the complexity of the types, so take a fair while to try to figure out the problem. Having to wrap a select in brackets
One thing that's been a bit annoying is namespace issues, where different tables contain foreign keys for the same table. I've worked around this by stuffing things in objects, but I think it would work a lot better if the tables contained their column vals so you could write e.g. users.userId instead of awkward imports, but I'm not really sure how we could achieve this.

relates to #12 #13 #14 #15, need to add one for 16

@jdegoes or @adamgfraser can you please review?

Awesome work and identified some issues we have to work on! Will comment on the issues separately (one of them, I don't think we need to 'fix', at least at the type level).
Thank you!


Identifiers validation failed for dataset VIP topsoil data jointsampling soilfauna, 2008

Identifier validation failed for the dataset VIP topsoil data jointsampling soilfauna, 2008:

Crawler attempt: 288
Publishing organization: Biodiversity Exploratories
Publishing country: GERMANY
Installation: Biodiversity Exploratories HTTP installation
Number of occurrences indexed for this dataset at the time of the issue: 313
Cause: GBIF IDs hit maximum allowed - 50%, duplicates - 100%, total records count 313, absent records count 313
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3085362/step

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the VIP topsoil data jointsampling soilfauna, 2008 : https://doi.org/10.15468/elfvlo.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

There was no change of the IDs and this happened due to the wrong link on their repository. Data ingestion was successful on 2023-08-21.


for any cypress tests in a sub-directory screenshot are stored in a wrong locations skipping visual regression validation

the issue is that  --spec param is used to generate snapshots locally but that seem to change test's root director and snapshots are placed directly under snapshots dir rather than in the sub directory (for examples snapshots/client-display)

PR: https://github.com/NationalSecurityAgency/skills-service/pull/1649


Unicode "|" character is being replaced in filenames on filesystems that support it

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2022.07.18 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are playable in a browser with the same IP and same login details
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
Per the documentation --no-restrict-filenames should support Unicode characters. However the | character, which is valid Unicode is being replaced with _ in file paths -
Actual behavior -
$ yt-dlp -vU \
--get-filename \
-o "/%(uploader)s/S01E%(video_autonumber)02d - %(title)s/S01E%(video_autonumber)02d - %(title)s [%(id)s].%(ext)s" \
l4gGWufoIYI

[debug] Command-line config: ['-vU', '--get-filename', '-o', '/%(uploader)s/S01E%(video_autonumber)02d - %(title)s/S01E%(video_autonumber)02d - %(title)s [%(id)s].%(ext)s', 'l4gGWufoIYI']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.07.18 [135f05e] (zip)
[debug] Python 3.10.4 (CPython 64bit) - Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 (glibc 2.35)
[debug] Checking exe version: ffmpeg -bsfs
[debug] Checking exe version: avconv -bsfs
[debug] Checking exe version: ffprobe -bsfs
[debug] Checking exe version: avprobe -bsfs
[debug] exe versions: none
[debug] Optional libraries: brotli-1.0.9, certifi-2020.06.20, secretstorage-3.3.1, sqlite3-2.6.0
[debug] Proxy map: {}
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2022.07.18, Current version: 2022.07.18
yt-dlp is up to date (2022.07.18)
[debug] [youtube] Extracting URL: l4gGWufoIYI
[youtube] l4gGWufoIYI: Downloading webpage
[youtube] l4gGWufoIYI: Downloading android player API JSON
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, codec:vp9.2, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] l4gGWufoIYI: Downloading 1 format(s): 248+251

/Action BOX/S01E01 - Homemade Plastic Injection Machine _ DIY/S01E01 - Homemade Plastic Injection Machine _ DIY [l4gGWufoIYI].webm

Expected behavior -
The video title on Youtube is "Homemade Plastic Injection Machine | DIY" so the expected file path is -
/Action BOX/S01E01 - Homemade Plastic Injection Machine | DIY/S01E01 - Homemade Plastic Injection Machine | DIY [l4gGWufoIYI].webm

Notes -
I'm running Ubuntu 21 with a ext4 filesystem, | is a supported character in filenames -
$ touch 'this is a pipe | in a filename'
$ ls
'this is a pipe | in a filename'

To the best of my knowledge NTFS (Windows) is the only filesystem that doesn't support | in a path. yt-dlp already handles filenames differently when running on Windows via the default --no-windows-filenames. Removing the | restriction for non-NTFS shouldn't cause an issue.
Extras -
While this ticket is specific to the '|' character NTFS is the only filesystem that doesn't support all Unicode characters -
$ touch 'this is a happy filename 😀'
$ ls
'this is a happy filename 😀'

It may be worth exploring supporting the entire Unicode character set in yt-dlp.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[X] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
[debug] Command-line config: ['-vU', '--get-filename', '-o', '/%(uploader)s/S01E%(video_autonumber)02d - %(title)s/S01E%(video_autonumber)02d - %(title)s [%(id)s].%(ext)s', 'l4gGWufoIYI']
[debug] Encodings: locale UTF-8, fs utf-8, pref UTF-8, out utf-8, error utf-8, screen utf-8
[debug] yt-dlp version 2022.07.18 [135f05e] (zip)
[debug] Python 3.10.4 (CPython 64bit) - Linux-5.17.15-76051715-generic-x86_64-with-glibc2.35 (glibc 2.35)
[debug] Checking exe version: ffmpeg -bsfs
[debug] Checking exe version: avconv -bsfs
[debug] Checking exe version: ffprobe -bsfs
[debug] Checking exe version: avprobe -bsfs
[debug] exe versions: none
[debug] Optional libraries: brotli-1.0.9, certifi-2020.06.20, secretstorage-3.3.1, sqlite3-2.6.0
[debug] Proxy map: {}
[debug] Fetching release info: https://api.github.com/repos/yt-dlp/yt-dlp/releases/latest
Latest version: 2022.07.18, Current version: 2022.07.18
yt-dlp is up to date (2022.07.18)
[debug] [youtube] Extracting URL: l4gGWufoIYI
[youtube] l4gGWufoIYI: Downloading webpage
[youtube] l4gGWufoIYI: Downloading android player API JSON
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, codec:vp9.2, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
[debug] Default format spec: bestvideo*+bestaudio/best
[info] l4gGWufoIYI: Downloading 1 format(s): 248+251

/Action BOX/S01E01 - Homemade Plastic Injection Machine _ DIY/S01E01 - Homemade Plastic Injection Machine _ DIY [l4gGWufoIYI].webm

Duplicate of https://github.com/yt-dlp/yt-dlp/issues/3385

Actually, this issue is better reported. So I'll close that one instead

Maybe you can add simple flag --ext4-filename-sanitization, if you have problems with filename restrictions deduction. In this fs you need to replace only / symbol

Documentation suggests to use --no-windows-filenames but it still tries to replace characters like *, ?, | -- all of them are perfectly valid file name characters in Unix.
(Maybe yt-dlp could default to --windows-filenames if the filesystem is one of msdos/vfat/exfat, otherwise it should be all fine.)

I got a reversed issue. I have --windows-filenames arg but it does not replace |.

Can someone make a summary of which popular FS/OS blocks which characters? We may be able to get away with using --windows-filenames to deal with this, but I need to be sure it won't cause issues

https://stackoverflow.com/a/31976060

Here:
https://en.m.wikipedia.org/wiki/Comparison_of_file_systems
Limits -> 3rd column
вс, 12 мар. 2023 г., 01:39 pukkandan @.***>:

Can someone make a summary of which popular FS/OS blocks which characters?
We may be able to get away with using --windows-filenames to deal with
this, but I need to be sure it won't cause issues
—
Reply to this email directly, view it on GitHub
https://github.com/yt-dlp/yt-dlp/issues/4547#issuecomment-1465027099,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH7QXG3OOTCRZCMYAFJW7QDW3TWIVANCNFSM55P3MMBQ
.
You are receiving this because you commented.Message ID:
@.***>

In Linux out of all the characters, there are only / (forward slash) and 0 (Null) forbidden.
I suggest checking the OS environment and automatically applying --windows-filenames in Windows and --no-windows-filenames (perhaps should be divided into --linux-filenames and --macos-filenames) in Linux.

Unlike I wrote in my bug report #6480 , the issue does not only concern Cyrillic/UTF-16 names, but ordinary Latin ones as well.
Example of the video: https://www.youtube.com/watch?v=Xfl6ZL5FK54
Run: yt-dlp -o '%(title)s_%(fulltitle)s.%(ext)s' -f "bv*[height=480]+ba" --merge-output-format mkv --progress --concurrent-fragments 10 -R infinite -vU https://www.youtube.com/watch\?v\=Xfl6ZL5FK54
Any chances of fixing the issue, @pukkandan ?

The character set support in the destination file system is a factor, as well as the OS.
Then one could consider whether some weird character might be censored even if the FS allows it, so as to make the filename acceptable in other common FSs (to which the file might be copied).

What needs to be done is to substitute (or to stop substituting, if that's what is happening now) a certain set of characters. There aren't that many of them. And not all of them even have anything to do with the OS filesystem limitations.

Should use | instead of ｜.
Should use : instead of ：.
Should use ? instead of ？.
Should use * instead of ＊.
Should use " instead of ＂.

In case someone wonders how to rename the already saved files, use the Linux shell command is rename 's/｜/|/' name-of-the-file.mkv (fixes 1 out of 5 cases named in my previous comment just above)
In order to rename all of the files in the current directory recursively, one can apply the following commands one after another:
find . -type f -name '*' -exec rename 's/｜/|/' {} +
find . -type f -name '*' -exec rename 's/：/:/' {} +
find . -type f -name '*' -exec rename 's/？/?/' {} +
find . -type f -name '*' -exec rename 's/＊/*/' {} +
find . -type f -name '*' -exec rename 's/＂/"/' {} +

An implementation where explicitly passing --no-windows-filenames prevents this sanitization is welcome

Looking forward to any progress on this issue!

As of writing, the --no-windows-filenames --no-restrict-filenames options still do not work. yt-dlp still replaces the double quotes in titles with the Unicode "Fullwidth Quotation Mark" (also known as char code 65282 or ＂).
I did find a workaround that works today, by setting --compat-options filename-sanitization.
This will replace double quotes with regular single quotes instead. Ideally they'd be left alone, but at least these are more reasonable to work with.

I just recently realized that, while a standard ASCII / is replaced with a unicode slash that looks darned-near identical, a standard ASCII : is replaced by the substantially wider-spaced full-width colon ： rather than a colon that's similarly-sized to the standard ASCII colon, such as the modifier letter colon ꞉ (U+A789):

https://www.fileformat.info/info/unicode/char/a789/index.htm

@NintendoManiac64 Off topic... It's just what seemed reasonable to me at the time. It is possible there are better alternatives, but any benefit gained by changing this is not worth breaking compatibility now. You can always do custom replacements with --replace-in-metadata

@NintendoManiac64 Off topic

Then what is the appropriate issue for unicode character replacement of ascii characters? I specifically put my comment here because, when doing a searching for the relevant issue, I thought that this is what this issue was discussing (but apparently not?).

Then what is the appropriate issue for reporting and/or discussing unicode character replacement of ascii characters?

You could open a new issue. But,

It is possible there are better alternatives, but any benefit gained by changing this is not worth breaking compatibility now

It is possible there are better alternatives, but any benefit gained by changing this is not worth breaking compatibility now

I completely agree, but my lack of software dev skills means I'm at a loss as for what compatibility there even is? Like, does the file name matter for programs that directly hook the likes of yt-dlp to steam videos from YouTube? I only ask because I only ever use yt-dlp directly via batch scripts to download a given audio or video format...

So, this drives me nuts also. Here's a crazy idea... don't sanitize the file name at all (except /) and try to create it. If the OS throws an error, apply some sanitization and try again. Rinse and repeat until success, each time with progressively more restrictions. (Also, adding ./ to the name should avoid pitfalls with certain prefixes having special meaning, though those are so unlikely to occur "in the wild" that sanitizing them always is probably fine.)
Honestly, since I don't know how to determine the FS type from Python (and Linux can mount FSs that have restrictions), I don't think there's a way to reliably know whether a filename is valid except to just try it.
That said, #9591 (i.e. "trust the user and they can keep the pieces if it breaks") would be an improvement!


Support 2"x7" Dymo labels (11019) for Zebra printers

I have produced a custom PPD for my Zebra LP 2824 to support Dymo's 2x7(2 5/16"x7 1/2") labels (model 11019). I think this label type is used enough to warrant support for it without having to add a custom size(which is not always easily possible for my work environment).
I'm not sure if my PPD is perfect. The measurements for the labels in the PPD do not exactly match the size of the printing area as the label printer seems to have margins that cannot be overcome(the print head is physically less wide than the page). My PPD was made purely out of a time of frustration and trying to figure out how things work in a limited amount of time(I've never customized a PPD before). It also removes all other page sizes because I needed it to support 2x7 and nothing else.
Let this issue serve as a request to officially support this label/page size. If I've posted this in the wrong place, please let me know.
zebra_2x7.ppd.txt

I suppose this label size could also be added to other printers; I only have a Zebra so the PPD is made for that.


Report for PR #612 Set bound to false when unbinding 'if' binder

Report PR #612 on ES6 branch. Fixes #611

@jccazeaux thanks, hoped you would do this!


Adds gateway to expose internal services

This patch adds the common gateway (flex-gateway) in nginx-gateway namespace. This gateway will be shared by all other namespaces to expose services internally. To do so the service that is getting exposed internally simply need to follow the fqdn naming of *.sjc.ohthree.com and ref the flex-gateway.
Also, adding the http routes for prometheus and alertmanager that use the above method to expose the two services internally.

👍🏼  lgtm - Can you add a doc entry about this?

👍🏼 lgtm - Can you add a doc entry about this?

https://docs.rackspacecloud.com/infrastructure-gateway-api/
Docs already in.


Add exception-handling proposal to wasm-smith

These commits add support to wasm-smith for the exception-handling proposal. I've manually tested this using wasm-smith/tests/tests.rs with the feature enabled (it defaults off) and can confirm it generates exception-handling code and also passes.

This looks great, thanks!
Could you update a few of the fuzz targets here as well so we can test this while fuzzing? The locations I think are:

here
here

and I think that might be it? If you wouldn't mind as well if you could run the *-valid-module fuzz targets as well for a minute or so just to make sure nothing is too far off, that'd also help give this some further testing. I think they can all be run with cargo fuzz run validate-valid-module (etc)

This looks great, thanks!
Could you update a few of the fuzz targets here as well so we can test this while fuzzing? The locations I think are:
* [here](https://github.com/bytecodealliance/wasm-tools/blob/873dd3ef4650fdb7251bd8349190df825ed0265b/fuzz/src/lib.rs#L12-L17)

* [here](https://github.com/bytecodealliance/wasm-tools/blob/873dd3ef4650fdb7251bd8349190df825ed0265b/fuzz/fuzz_targets/validate-valid-module.rs#L16-L25)

and I think that might be it? If you wouldn't mind as well if you could run the *-valid-module fuzz targets as well for a minute or so just to make sure nothing is too far off, that'd also help give this some further testing. I think they can all be run with cargo fuzz run validate-valid-module (etc)

I'm probably doing something plainly wrong. Getting the following output.
rhunt@rhunt-mac~/s/m/wasm-tools> cargo fuzz run validate-valid-module
warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

    Finished release [optimized] target(s) in 0.08s
warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

warning: unknown pass `sancov-module`, ignoring

warning: 1 warning emitted

    Finished release [optimized] target(s) in 0.08s
     Running `target/x86_64-apple-darwin/release/validate-valid-module -artifact_prefix=/Users/rhunt/src/mozilla/wasm-tools/fuzz/artifacts/validate-valid-module/ /Users/rhunt/src/mozilla/wasm-tools/fuzz/corpus/validate-valid-module`
INFO: Running with entropic power schedule (0xFF, 100).
INFO: Seed:<PHONE_NUMBER>
INFO:        0 files found in /Users/rhunt/src/mozilla/wasm-tools/fuzz/corpus/validate-valid-module
INFO: -max_len is not provided; libFuzzer will not generate inputs larger than 4096 bytes
INFO: A corpus is not provided, starting from an empty corpus
#2	INITED exec/s: 0 rss: 31Mb
ERROR: no interesting inputs were found. Is the code instrumented for coverage? Exiting.
────────────────────────────────────────────────────────────────────────────────

Error: Fuzz target exited with exit status: 1

This is with nightly as the default toolchain on OSX x86_64.

You might need to cargo install cargo-fuzz to get the latest version perhaps? I think some changes happened on nightly recently (you'll also probably need the most up-to-date nightly). I can help dig in if those don't work though.

Updating both nightly and cargo-fuzz fixed it. Thanks!

Okay, I should have addressed all the comments. I also ran fuzzing for the three -valid-module fuzz targets for two minutes each and didn't encounter any obvious issue.

👍 Thanks!

@alexcrichton Could we get a new version published for this? I'd like to use this in SpiderMonkey CI.

Sure yeah, I've posted https://github.com/bytecodealliance/wasm-tools/pull/348 for that.


Tag push creates webhook with empty commits and head_commit

Gitea Version
1.15.8
Git Version
2.33.1
Operating System
Windows Server 2016
How are you running Gitea?
based on gitea-1.15.8-windows-4.0-amd64.exe as Windows Service
Database
SQLite
Can you reproduce the bug on the Gitea demo site?
Yes
Log Gist
No response
Description
Creating a new tag for a gitea repo creates a webhook with empty commits and head_commit. See example from gitea demo site:
{
  "ref": "refs/tags/v1.1.1",
  "before": "0000000000000000000000000000000000000000",
  "after": "3f150d39b92dd50cdd0248f5edea5767c2172584",
  "compare_url": "https://try.gitea.io/",
  "commits": [],
  "head_commit": null,
  "repository": {
  ...

I have an on-prem gitea instance connected with on-prem AppVeyor server. AppVeyor can't create new builds if  commits and head_commit are empty, see also open issue on AppVeyor: appveyor/ci#3765
Screenshots
No response

@DoLearnWhileAlive Does AppVeyor work now?

Just tested newest Gitea main build (1.16.0+dev-785-g496acbe9e) and AppVeyor is still not triggering a new build for a new tag. AppVeyor seems to expect both commits and head_commit to be defined.

AppVeyor Server was updated with version 7.0.3134 to support head_commit in the webhook payload. With that change AppVeyor Server is creating a build for a Gitea tag webhook again. See also appveyor/ci#3765.
Thanks for fixing the Gitea part!


🐛 Fix bug when cluster is not found

What this PR does / why we need it:
And remove the restrictions on the events triggering the reconciliation from IPClaims to
catch update events when the deletion timestamp is set

/cc @kashifest
/cc @fmuyassarov
/cc @furkatgofurov7


Feature - Default Name while creating or renaming with current date/time

Hi, one of the use cases I encountered is that we take down raw notes in a new sublime tab but then these tabs are cluttered with very less visibility about when they were created.
Therefore, it would be great if we could add the default file name option as well while creating or renaming the file.

Hi @nanocent, apologize for the month (!) delay in replying. I don't actively maintain this anymore. However, is the default_initial the setting you're looking for? The string you place in that value will populate the initial input.

As a workaround, you may use the commands provided by https://packagecontrol.io/packages/InsertDate via key bindings to insert the current date into ANF's "New File" input panel.
Since that package is way more flexible and I could see different use cases for similarly complex default file names, I'd rather provide the ability to specify commands to be run on the input view rather than adding the ability to use a formatted timestamp in the template. This would also allow inserting snippets with fields using the insert_snippet command, for example.


Need support for Node v16

Hello,
Thanks for the project, any plan to support Node v16, we need it.

Hello. Yes I plan to support Node v16, however, I am currently unavailable
and not at the PC for a while. I'd be happy to review a pull request.
Am Di., 11. Mai 2021 um 10:12 Uhr schrieb Mikuu @.***>:

Hello,
Thanks for the project, any plan to support Node v16, we need it.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/Prior99/node-libpng/issues/37, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALME5TM33OKP62UEDXN3ETTNDRIVANCNFSM44UWCW5A
.

Support has been added in 0.2.20.

thanks


CLOUD-57108 fixed response json from salt bootstrap

@akanto @doktoric

Jenkins build finished, all tests passed.
Refer to this link for build results: http://ci.sequenceiq.com/job/cloudbreak-pull-request/2468/


Search does not yield any results from /docs/cloud at all

About
When using the search on this documentation section, for example per https://crate.io/docs/cloud/en/latest/search.html?q=subscription plans, it does not display any results from here at all.

@amotl this is fixed now, the results however are still pointing to crate.io, but this will be resolved soon (migration in the search console is in progress)


Train a chatbot model: error: one of the arguments --datasetdir/-d --checkpointfile/-c is required An exception has occurred, use %tb to see the full traceback.

The exception occurs in general_utils.py file at line 31, when we try to parse all the arguments in training mode.
args = parser.parse_args()

Hi @irdanish11, can you share the command you are using that generates this error?

when I run the train.py file to train, on 18th line of train.py it creates the model using 'general_utils.initialize_session' then the above described exception occurs. when I checked the 'general_utils.py' file line by line, it turned out that it is the 'args = parser.parse_args()' is line that generating the exception.
`def initialize_session(mode):
"""Helper method for initializing a chatbot training session
by loading the model dir from command line args and reading the hparams in
Args:
    mode: "train" or "chat"
"""
parser = argparse.ArgumentParser("Train a chatbot model" if mode == "train" else "Chat with a trained chatbot model")
if mode == "train":
    ex_group = parser.add_mutually_exclusive_group(required=True)
    ex_group.add_argument("--datasetdir", "-d", help="Path structured as datasets/dataset_name. A new model will be trained using the dataset contained in this directory.")
    ex_group.add_argument("--checkpointfile", "-c", help="Path structured as 'models/dataset_name/model_name/checkpoint_name.ckpt'. Training will resume from the selected checkpoint. The hparams.json file should exist in the same directory as the checkpoint.")
    em_group = parser.add_argument_group()
    em_group.add_argument("--encoderembeddingsdir", "--embeddingsdir", "-e", help="Path structured as embeddings/embeddings_name. Encoder (& Decoder if shared) vocabulary and embeddings will be initialized from the checkpoint file and tokens file contained in this directory.")
    em_group.add_argument("--decoderembeddingsdir", help="Path structured as embeddings/embeddings_name. Decoder vocabulary and embeddings will be initialized from the checkpoint file and tokens file contained in this directory.")
elif mode == "chat":
    parser.add_argument("checkpointfile", help="Path structured as 'models/dataset_name/model_name/checkpoint_name.ckpt'. The hparams.json file and the vocabulary file(s) should exist in the same directory as the checkpoint.")
else:
    raise ValueError("Unsupported session mode. Choose 'train' or 'chat'.")
args = parser.parse_args()`

The last line in the above code is causing exception and the entire trace message is:
`usage: Train a chatbot model [-h]
(--datasetdir DATASETDIR | --checkpointfile CHECKPOINTFILE)
[--encoderembeddingsdir ENCODEREMBEDDINGSDIR]
[--decoderembeddingsdir DECODEREMBEDDINGSDIR]
Train a chatbot model: error: one of the arguments --datasetdir/-d --checkpointfile/-c is required
An exception has occurred, use %tb to see the full traceback.
SystemExit: 2
/root/anaconda3/lib/python3.7/site-packages/IPython/core/interactiveshell.py:2969: UserWarning: To exit: use 'exit', 'quit', or Ctrl-D.
warn("To exit: use 'exit', 'quit', or Ctrl-D.", stacklevel=1)`

I'm using spyder on linux

As the error is saying, you need either --datasetdir or --checkpointfile parameters to train.
In spyder go to Run -> Configuration per file
You can set Command Line options. Try setting --datasetdir=datasets\cornell_movie_dialog
Let me know if this works. If not, you can always just train from an Anaconda console:
run train.py --datasetdir=datasets\cornell_movie_dialog

I've changed the setting in spyder that you have recommended, the same error remains

Actually I want to build the chatbot in urdu language so I have totally different corpus, so can you please guide me about your code and where you have done the preprocessing and overview of your code that how it works

That is strange that spyder is not sending the commands properly, You can try running the training directly in an Anaconda console. I recommend doing it that way anyway since training may take a long time and you won't be able to close Spyder.
Can you share the format of your Urdu dataset? You will need to format it using the CSV, Cornell, or DailyDialog formats (see the readme files under these directories: datasets
Also the clean_text function in vocabulary.py is doing the text normalization. You may need to modify it to work with the specifics of your language if it does not work out of the box. You can check the cleaned_dataset.txt file that is generated when you train a model to make sure that the text normalization is working the way you expect. For languages that use an English or similar european alphabet, the normalization makes everything lowercase, strips out special characters, treats punctuation as its own word, and can optionally expand contractions like "don't" --> "do not".

Here is the example some of the sentences in our corpus, now can you please tell in which file I have to change the corpus name so that it would start training on my corpus instead of cornell. And thanks for helping me the method you have told is just working fine now in spyder.

And one thing more can I have to split m dataset in question and answers files separately

my corpus is .txt format what changes I have to make to my corpus , and please explain me about
movie_lines.txt
movie_conversations.txt
do I have to change my corpus according to these 2 files, currently my corpus is in plain text file

Can we train these models on Google Cloud Platform?? If yes. then please let me know how to do it?


inlineManifestWebpackName not working

I try to inline webpack manifest but with the following config is not working:
module.exports = {
  optimization: {
    runtimeChunk: { name: 'runtime' }
  },
  plugins: [
    new HtmlWebpackPlugin({
      inject: false,
      template: require('html-webpack-template'),
      inlineManifestWebpackName: 'runtime'
    }),
    new InlineManifestWebpackPlugin()
  ]
};

Note: 'runtime' is the default name for webpack manifest.
My devDependencies versions:
"html-webpack-plugin": "^3.2.0",
"html-webpack-template": "^6.2.0",
"inline-manifest-webpack-plugin": "^4.0.0",
"webpack": "^4.10.1"

What's happen
Looking inside html-webpack-template.ejs I see:
<% if (htmlWebpackPlugin.options.inlineManifestWebpackName) { %>
  <%= htmlWebpackPlugin.files[htmlWebpackPlugin.options.inlineManifestWebpackName] %>
<% } %>

Logging htmlWebpackPlugin.files, there is no plain manifest code inside this object but only a reference to 'runtime' chunk.
Solution
We can use the compilation object and add the following code to the template:

Add new code: set a global variable webpackManifestName above <!DOCTYPE html>

<% const webpackManifestName = htmlWebpackPlugin.options.inlineManifestWebpackName ?
new RegExp(htmlWebpackPlugin.options.inlineManifestWebpackName, 'g') : '' %>

Replace the old inlineManifestWebpackName logic with a new one

<% if (webpackManifestName) { %>
    <script type="text/javascript">
      <% const webpackManifest = htmlWebpackPlugin.files.js
      .filter( file => file.match(webpackManifestName) ); %>

      <%= compilation.assets[webpackManifest].source() %>
    </script>
<% } %>

Modify the original code used to link the chunks: add some logic to prevent the manifest to be linked if its set as inline

<% Object.keys(htmlWebpackPlugin.files.chunks)
  .filter(chunk => webpackManifestName ? !chunk.match(webpackManifestName) : chunk)
  .forEach(chunk => {
    if (htmlWebpackPlugin.files.jsIntegrity) { %>
      <script
        src="<%= htmlWebpackPlugin.files.chunks[chunk].entry %>"
        type="text/javascript"
        integrity="<%= htmlWebpackPlugin.files.jsIntegrity[htmlWebpackPlugin.files.js.indexOf(htmlWebpackPlugin.files.chunks[chunk].entry)] %>"
        crossorigin="<%= webpackConfig.output.crossOriginLoading %>">
      </script>
    <% } else { %>
      <script src="<%= htmlWebpackPlugin.files.chunks[chunk].entry %>" type="text/javascript"></script>
    <% } %>
<% }) %>

Note: InlineManifestWebpackPlugin is not strictly necessary, in this case it's used to delete runtime.js chunk in the dist/ folder.

I ran into this issue as well - @pldg 's solution worked with one alteration to support Webpack's publicPath config.
<% if (webpackManifestName) { %>
<script type="text/javascript">
    <% const webpackManifest = htmlWebpackPlugin.files.js
        .filter( file => file.match(webpackManifestName) )[0]
        .replace(webpackConfig.output.publicPath, '') %>

    <%= compilation.assets[webpackManifest].source() %>
</script>
<% } %>

Would be nice a solution that works without adding InlineManifestWebpackPlugin to delete dist/runtime.js but for now I'm closing this issue.


Add sorting options

It would be great if users could sort a subreddit by: hot, new, top, and rising from the header after they search.

Closed via https://github.com/gregrickaby/reddit-image-viewer/pull/77


Broken Link

This is a problem with the theme (Koru).  It's outside of our purview.  I'll submit a ticket to the repository, linked below:
https://github.com/NCAR/koru-jekyll


Add playbook for spawning logdetective02

Fixes: #77

instance started/stopped:
i-003ca4c5cf2e8914c

Closing, we can start from this PR next time.


Lambda environment variables parser/global data class initializer

I think that this basic part of the lambda best practices is missing from the repo.
Validating environment variables, parsing them and saving them into an easy to reach singleton data class could be a very handy utility.
This is especially useful if you have multiple files in your lambda and you want an easy way to get an env variable (without having magic strings all over the code os.getenv('magic_string') etc.).
You could call a get_env_vars() which will return a validated data class.
For an example:
def handler(event, context):
# init env vars
conf = get_env_vars(MY_PYDANTIC_SCHEMA) # this will raise an exception in case of broken environment vars configuration

# init feature flags

# parse event input with powertools parser

if conf.magic_string:
    # handle business logic

Implementation:
The easiest way to do this is to use Pydantic as it allows the user to parse according to schemas quite easily.
MY_PYDANTIC_SCHEMA in the example can look like this:
from pydantic import BaseModel, HttpURL
class MY_PYDANTIC_SCHEMA(BaseModel):
    env_var1: str
    env_var2: bool
    role_arn: str  # can add validations on ARN
   rest_api_endpoint: HttpURL

get_env_vars will init a global instance of MY_PYDANTIC_SCHEMA if it's None and return it. This will allow the easy use of parsed environment variables in any lambda file.
It also allows to transform any string based environment variables into a more complicated objects automatically.
I'd be happy to implement this. What do you think?

Hi @ran-isenberg! I'm closing this issue as a duplicate of https://github.com/aws-powertools/powertools-lambda-python/issues/1172.


Update reason example

Following up on #512

The Router and Link components are borrowed from https://github.com/thangngoc89/reason-react-router with slight modifications to allow passing in a URL for ssr.

The Router and Link components are borrowed from https://github.com/thangngoc89/reason-react-router with slight modifications to allow passing in a URL for ssr.

Does the built-in reason router support SSR?

If you take a look at the Router component there is nothing that needs the browser there. The only thing that is needed is for us to pass a initial URL because then we will use that instead of dangerously getting the URL.
So on the server we really don't use the router, we just use the switch statement in App.re.

I've just noticed that going to root url actually renders "page not found" instead of home component. Going to "/home" or "/counter" rendered correctly on the server.

Noticed that now as well. In my app I added this util:
/* copied from  ReasonReact */
let urlToUrlList = url =>
  switch url {
  | ""
  | "/" => []
  | _ =>
    /* remove the preceeding /, which every pathname seems to have */
    let raw = Js.String.sliceToEnd(~from=1, url);
    /* remove the trailing /, which some pathnames might have. Ugh */
    let raw =
      switch (Js.String.get(raw, Js.String.length(raw) - 1)) {
      | "/" => Js.String.slice(~from=0, ~to_=-1, raw)
      | _ => raw
      };
    raw |> Js.String.split("/") |> Array.to_list;
  };

And then parse the URL with that (this also solved that I had to remove the leading "/"). Not sure if that is too much to add for this simple example or if I should include it. Would love for  ReasonReact to expose it instead.

I would add this to the example for now but it would be preferable if ReasonReact exposed something like this.

@jaredpalmer I think this is fine. Anything else you want me to fix?


Problem with Xcode wrong error

Xcode Version 9.2 (9C40b)
This is not stopping the work, but it's confusing so probably it should be mentioned in the setup guide.
When I open the project the project compiles and probably because the project file is empty it is not creating the package. After creating function, class or whatever everything is ok, but Test environment already cached this and trows strange errors that are ignored even by the compiler, they are just shown. Even after the task is finished and all tests pass, the errors are still there.
This can not be fixed by clean or clean build folder.
The only solution I found is comment out "@testable import Leap". Then build. An error occurs, but after you uncomment the line and build again, everything is fine. No errors occur.

Have you tried the new xcode?

Reopen if you are still having issues.


Add github links

Added links to official GitHub repositories for NeRF++ (nerfplusplus) and pixelNeRF (pixel-nerf).

Thanks for the contribution.


Fix link in Contributors [Delivers #154929981]

Clicking on a user profile image in Contributors should go to the user's page,
but instead gets:

Sorry, the user you tried to display (id #) does not exist. Someone may have deleted it or merged it into another.
Your query has expired, please try again.

Fixed thumbnail link by correctly including user.id in the target
Made relevant part of view more readble:

Shortened lines
used If .. end instead of multi-line if modifier

Deleted unnecessary

Coverage decreased (-0.002%) to 94.658% when pulling 2fc5dd81b3431b90bcaceb974b988840916ede34 on JoeCohen:contrib-photo into 47f4b90fafae508a1dc36f15b3c853b9a36b398f on MushroomObserver:master.


Click the web service endpoint, application error.

Describe the issue:
After azd deploy, click the endpoint of service web, you will get the error below:

Repro Steps:

azd init -t <template_name>
azd package
azd provision
azd deploy, click the endpoint of service web.

Environment:
OS: Windows
Azd version: azd version 0.8.0-beta.1-daily.2689578 (commit 3b28fc8f84717d732f646a3e3b9521204f122112)
Expected behavior:
After deployment, the page can be opened normally.
@rajeshkamal5050, @tonybaloney for notification.

@zedy-wj - what region are you using... I tried using one of my normal choices (WestUS) and ran into some region errors.
I saw you're a part of MSFT - I've noticed that I run into errors deploying that are sometimes region based... I just tried to reproduce using EastUS and was able to deploy via azd.
Notes:

Using azd version 0.7.0-beta-1 Trying again after updating AZD

@kjaymiller - Thanks for your feedback. The region I used is also EastUS. I tried again with this azd version: 0.7.0-beta.1 (commit 9ce71659f7688d0dc3dda8b84e5accedca58cf01) and got the same error.
What you mentioned: was able to deployed via azd, after the deployment is complete, do you click the web endpoint to view it? There is nothing wrong with the azd deploy command itself. The result of my execution is shown in the figure:

But we found this problem after clicking the endpoint.

Yes I was able to view the website as expected.
Were you able to access the streaming logs either in VS Code or in the Azure Portal?

It's Platform logs in the Azure Portal:

It's Application logs in the Azure Portal:

It's Http Server Errors in the Azure Portal:

Let's me know if you need more info.
Notes: We found that the page opened in the Linux environment is normal, what environment are you using?

Yes and it looks like there is a carriage return being added to the end of the script that is being added.
Unknown command: 'migrate\r'. Did you mean migrate?
This is being called in demo-application/startup.sh.  The \r is halting the build on windows systems.
Was this file edited while on your system. I wonder if the files were modified silently when opened on your machine swapping the \n with \r.

@kjaymiller - Thanks for your help, we can open the web page normally!

Closed it as completed.


Ability to change the default url text

When you supply a URL, the text shows up in the dialog as "View". It's be cool to have an extra param in the data like, url_text to be able to customize the popup.
So like:
- title: Place Name
  url: http://www.place.net
  url_text: View place name
  latitude: 6.206731
  longitude: -75.5677747

Implemented in v2.3.0

Yay it works! 🎉


Convert all .md documents except Spec/README to .adoc

This is a DRAFT pull request. I'm going to force push a new changes with the changes looking like a rename and edit so hopefully we can see the formatting changes correctly in a diff.
As our plan moving forward is to convert the Spec and other documents in this repository to Asciidoctor format, this PR converts all the documents except the Spec (README.md)
(The spec is a little trickier to convert because there are two unmarked PRs that need to be converted as well, so we'll do the Spec separately.)

After over an hour in Git hell, I decided to close this branch and open a new one. Stay tuned...


zip files exercise

@kytrinyx This is just a draft but I want to know if this is heading to where looking for

Thanks @GustavoCaso I think this is a good direction.

@kytrinyx I added some test. I was having a hard time testing the endpoint with an ensure clause, it was deleting the file before the test ended. I don't know a better way of doing it ?

Yeah, if you move the code that creates the zip down into the model code, then we can put the ensure up in the route (untested).

Have you had a chance to test if tempfiles will work on heroku?

@kytrinyx I haven't try it in real life with heroku but I will, I can create a dummy app to test it and tell you the result.

Excellent, thanks.

@kytrinyx please have a look to this dummy app I setup so we can try has the code from my branch.
http://testxapiexercism.herokuapp.com/
Right hitting the endpoint will ask if you want to download the file, so that part is working.
I'm going to test with curl to download it.
Please feel free to tell me anything that you want to add.

OK, cool. That should be fine then. Thanks!

Did the suggestion for testing make sense?

What do you mean the suggestion ??

Yes, moving the code to the model, and keeping the ensure in the route, that way the code can be tested at the model level.

Yes it work they thing I'm missing is the test that the service ZipFileGenerator is called from problem model, for that I will have to change the interface, to pass the dependency with the method that way I'm will be able to mock that in the test, something like problem.zip_files_problem(ZipFileGenerator).
What do you think ?

Yeah, passing the dependency seems fine. It would make sense to make the default parameter value ZipFileGenerator so that the method can be called without arguments.

@kytrinyx hope this is what you are looking for ?

I like where this is going. I have a bunch of suggestions to simplify the naming of things (removing redundancy, clarifying where it might be ambiguous).

@kytrinyx I have apply the feedback about naming, removing redundancy I hope is more your taste. :-)

This looks great. Merging! Thanks so much for working your way through this one.


Wrong filter for multiple facet.

Hello,
I have a case that I can't understand, for the example: https://community.algolia.com/instantsearch.js/examples/e-commerce/
In Material filter, I select Polypropylene option, have some products (e.g SPRUTT) matching the condition with the Green option in Color filter.
Then, I select both of Polypropylene and 100 % polyester options, the operator for the Material filter is 'or' and I can find the SPRUTT product in the result, but the Green option in the Color filter will disappear.
Can anyone explain to me? Thanks!

I think this happen because of the number of values for color facet default is 10, so it just can display maximum 10 color and Green color will disappear.


Place text and Greek characters

Hello,
I am trying to place a text that contains greek characters, but it always puts '.....' in the pdf no matter what. I tried multiple things with .encode and .decode but nothing seems to work. I also experimented with different fonts because I read that some font families might not support greek.
If I add all my data to a dictionary and use write_fillable_pdf it works. But unfortunately I want to create a black pdf with text in specific positions to print on pre-printed forms.
Any suggestions?

i am consistently getting this error


BUG-ID:CLOUDSTACK-9678

listNetworkOfferings API is listing all the offerings which has same prefix in their name

Why this is a bug? Most of ACS searches using name field work exactly this way to bring list of VMs, templates etc when partial name is specified. If exact name match is expected it needs to be processed on a client side.

For listing of other offerings  Disk, Compute and VPC, we have to provide exact name and not partial one.So this fix is done for consistent behaviour of all list APIs

@pdumbre I confirm your observation. LGTM on code review.

Test Results Passed:
https://travis-ci.org/apache/cloudstack/builds/201069131

ACS CI BVT Run
Sumarry:
Build Number 344
Hypervisor xenserver
NetworkType Advanced
Passed=103
Failed=1
Skipped=7
Link to logs Folder (search by build_no): https://www.dropbox.com/sh/yj3wnzbceo9uef2/AAB6u-Iap-xztdm6jHX9SjPja?dl=0
Failed tests:

test_routers_network_ops.py

test_03_RVR_Network_check_router_state Failed

Skipped tests:
test_01_test_vm_volume_snapshot
test_vm_nic_adapter_vmxnet3
test_static_role_account_acls
test_11_ss_nfs_version_on_ssvm
test_nested_virtualization_vmware
test_3d_gpu_support
test_deploy_vgpu_enabled_vm
Passed test suits:
test_deploy_vm_with_userdata.py
test_affinity_groups_projects.py
test_portable_publicip.py
test_over_provisioning.py
test_global_settings.py
test_scale_vm.py
test_service_offerings.py
test_routers_iptables_default_policy.py
test_loadbalance.py
test_routers.py
test_reset_vm_on_reboot.py
test_deploy_vms_with_varied_deploymentplanners.py
test_network.py
test_router_dns.py
test_non_contigiousvlan.py
test_login.py
test_deploy_vm_iso.py
test_list_ids_parameter.py
test_public_ip_range.py
test_multipleips_per_nic.py
test_regions.py
test_affinity_groups.py
test_network_acl.py
test_pvlan.py
test_volumes.py
test_nic.py
test_deploy_vm_root_resize.py
test_resource_detail.py
test_secondary_storage.py
test_vm_life_cycle.py
test_disk_offerings.py


fix(pattenlab), docs(update project name), fix(patternlab and storybook) : Multiple Fixes.

Issues Fixed :

If we are using patternlab theme generated using this,

On running yarn start, we get the following errors.
[15:32:44] Starting 'pl:build'...
Pattern Lab Node v5.15.2
Pattern Engine mustache: good to go
Pattern Engine twig-php: good to go
Pattern Engine mustache: already loaded, skipping.
Pattern Engine twig-php: already loaded, skipping.
atoms-button-button "Pattern", "Group" and "Subgroup" ordering by number prefix (##-) will be deprecated in the future.
 See https://patternlab.io/docs/reorganizing-patterns/
Built pattern: atoms-button
Built Pattern Lab front end
[15:32:45] Finished 'pl:build' after 1.37 s
[15:32:45] Finished 'default' after 5.45 s
[15:32:45] Starting 'pl:serve'...
[15:32:45] Starting 'watch:scss'...
[15:32:45] Starting 'watch:ts'...
env: node\r: No such file or directory
[15:32:45] Finished 'pl:serve' after 20 ms
[15:32:45] The following tasks did not complete: watch, <parallel>, watch:scss, watch:ts
[15:32:45] Did you forget to signal async completion?
node:events:371
      throw er; // Unhandled 'error' event
      ^

Error: ENOENT: no such file or directory, lstat './dist/js'
Emitted 'error' event on Domain instance at:
    at emit (node:internal/process/promises:134:35)
    at processPromiseRejections (node:internal/process/promises:242:25)
    at processTicksAndRejections (node:internal/process/task_queues:97:32) {
  errno: -2,
  code: 'ENOENT',
  syscall: 'lstat',
  path: './dist/js'
}
Error Command failed with exit code 1.

This PR Fixes it.

Documentation updated by removing instances of Kashmir.

Fixed the following warning in Patternlab generated themes.

Pattern Engine twig-php: already loaded, skipping.
atoms-button-button "Pattern", "Group" and "Subgroup" ordering by number prefix (##-) will be deprecated in the future.
 See https://patternlab.io/docs/reorganizing-patterns/

It was updated as per https://github.com/pattern-lab/starterkit-handlebars-vanilla/tree/master/dist/_patterns
The component naming conventions are updated as a result from for ex: 02-atoms to just atom

Removed unwanted document section and updated yarn start doc in design systems.

The PR looks good to me. Thanks!


[Feature Request] Docker Image to run openapi-validator

Is there a Docker Image to run openapi-validator? (Similar to openapitools/openapi-generator-cli)

Hi @dkirrane - I'm not officially connected to the project, but I've got a public docker container on gitlab here: https://gitlab.com/jamescooke/ibm-openapi-validator-docker
I was just looking at moving that container to docker hub, but my guess would be that it would be best if it was shipped there under the IBM verified publisher account.
Am happy to contribute / help out if any of the team here wishes. The Dockerfile I've written could be pinched and re-used if helpful: https://gitlab.com/jamescooke/ibm-openapi-validator-docker/blob/master/Dockerfile

@jamescooke if you have a public container already, I would be more than happy for you to move it to Docker Hub and just have a community Docker image for the validator.

@jamescooke Is the image in Docker Hub? If so, I'll close this issue

@dpopp07 Not yet, sorry :disappointed:
While writing this, I spotted that @dkirrane has created a public image here: https://hub.docker.com/r/dkirrane/ibm-openapi-validator - maybe that's a good enough reason to close this issue?

Ah yes, that sounds good to me.
@dkirrane as the OP if you're after a different solution, feel free to re-open. I'm going to close for now

An updated, semi-auto-building, slim container is now up on Docker hub: https://hub.docker.com/r/jamescooke/openapi-validator
I've only just spotted that it's possible to compile a binary with npm run pkg - so it might be possible to make future improvements to this container in terms of reduced size, speed.