Permit 34 Zigbee devices simultaneously upon power-up cannot be completed. (TZ-1280)

Answers checklist.

[X] I have read the documentation ESP Zigbee SDK Programming Guide and tried the debugging tips, the issue is not addressed there.
[X] I have updated ESP Zigbee libs (esp-zboss-lib and esp-zigbee-lib) to the latest version, with corresponding IDF version, and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
esp-idf-v5.3.1
esp-zigbee-lib version.
1.5.0
esp-zboss-lib version.
1.5.0
Espressif SoC revision.
esp_zigbee_gateway：ESP32S3 + ESP32H2 （rcp），Device：ESP32H2
What is the expected behavior?
34 Zigbee devices can be permit simultaneously. esp_zigbee_gateway no error
What is the actual behavior?
about 10 devices are unable to join the network.
Steps to reproduce.

one esp_zigbee_gateway （TYPE_COORDINATOR），power on
34 zigbee device （TYPE_ROUTER），power on simultaneously
about 10 devices are unable to join the network.

esp_zigbee_gateway log：
I (56020) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Authorized (0x2f), status: ESP_OK
ZBOSS: nwk/nwk_cr_mesh_routing.c:406   Call zb_nlde_data_confirm(), param 12
ZBOSS: common/zb_address.c:1138   zb_address_delete ref 46
ZBOSS: common/zb_address.c:1168   WARNING: pending_for_delete ref 46
I (56170) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Authorized (0x2f), status: ESP_OK
I (56220) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Unavailable (0x3c), status: ESP_OK
I (56220) ESP_ZB_GATEWAY: ZDO Device (0x7ea7) Unavailable
I (56230) ESP_ZB_GATEWAY: node device_name: A9571B000375, short_addr: 0x7ea7 is already in the array, update status to 0, unavailable_count: 0
I (56240) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Unavailable (0x3c), status: ESP_OK
I (56250) ESP_ZB_GATEWAY: ZDO Device (0x7ea7) Unavailable
I (56260) ESP_ZB_GATEWAY: node device_name: A9571B000375, short_addr: 0x7ea7 is already in the array, update status to 0, unavailable_count: 1
ZBOSS: common/zb_address.c:941   WARNING: remove ref 46 which was in pending_for_delete
ZBOSS: common/zb_address.c:1138   zb_address_delete ref 46
I (57010) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Unavailable (0x3c), status: ESP_OK
I (57010) ESP_ZB_GATEWAY: ZDO Device (0x7ebc) Unavailable
I (57020) ESP_ZB_GATEWAY: node device_name: 2E544A010430, short_addr: 0x7ebc is already in the array, update status to 0, unavailable_count: 0
I (58070) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Authorized (0x2f), status: ESP_OK
I (58600) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Authorized (0x2f), status: ESP_OK
I (59160) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Authorized (0x2f), status: ESP_OK
I (59190) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Authorized (0x2f), status: ESP_OK
I (61480) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Unavailable (0x3c), status: ESP_OK
I (61480) ESP_ZB_GATEWAY: ZDO Device (0x8430) Unavailable
I (61480) ESP_ZB_GATEWAY: node device_name: A9578700038D, short_addr: 0x8430 is already in the array, update status to 0, unavailable_count: 0
I (61600) ESP_ZB_GATEWAY: ZDO signal: NLME Status Indication (0x32), status: ESP_OK
I (61600) ESP_ZB_GATEWAY: NLME Status Indication status: 0x0000, network_addr: 0x8430, unknown_command_id: 0
I (62600) ESP_ZB_GATEWAY: ZDO signal: NLME Status Indication (0x32), status: ESP_OK
I (62600) ESP_ZB_GATEWAY: NLME Status Indication status: 0x0000, network_addr: 0x7ebc, unknown_command_id: 0
I (64600) ESP_ZB_GATEWAY: ZDO signal: NLME Status Indication (0x32), status: ESP_OK
I (64600) ESP_ZB_GATEWAY: NLME Status Indication status: 0x0000, network_addr: 0xf28f, unknown_command_id: 0
I (66600) ESP_ZB_GATEWAY: ZDO signal: NLME Status Indication (0x32), status: ESP_OK
I (66600) ESP_ZB_GATEWAY: NLME Status Indication status: 0x0000, network_addr: 0xcc95, unknown_command_id: 0
I (66670) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Unavailable (0x3c), status: ESP_OK
I (66670) ESP_ZB_GATEWAY: ZDO Device (0xcc95) Unavailable
I (66670) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Unavailable (0x3c), status: ESP_OK
I (66680) ESP_ZB_GATEWAY: ZDO Device (0x8430) Unavailable
I (66690) ESP_ZB_GATEWAY: node device_name: A9578700038D, short_addr: 0x8430 is already in the array, update status to 0, unavailable_count: 1
I (66700) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Unavailable (0x3c), status: ESP_OK
I (66710) ESP_ZB_GATEWAY: ZDO Device (0xf28f) Unavailable
D/[1970-01-01 00:01:10] device_name D83BDA587737 is work, need to heartbeat
D/[1970-01-01 00:01:10] [70.222][LK-0309] pub: v1/gateway/D83BDA587737/event
More Information.
No response

Hi @wensenl ,
The issue might be caused by the insufficient static buffers. Could you try using esp_zb_overall_network_size_set(128) and esp_zb_io_buffer_size_set(100) before calling esp_zb_init() and test again?

Hi,@xieqinan
I add code，but also can not Permit join 34 Zigbee devices simultaneously upon power-up.
modify code:
static void esp_zb_task(void *pvParameters)
{
#if CONFIG_OPENTHREAD_SPINEL_ONLY
esp_radio_spinel_register_rcp_failure_handler(rcp_error_handler, ESP_RADIO_SPINEL_ZIGBEE);
#endif
**//设置zb网络和缓冲大小
esp_zb_overall_network_size_set(128);
esp_zb_io_buffer_size_set(100);**

/* initialize Zigbee stack */
esp_zb_cfg_t zb_nwk_cfg = ESP_ZB_ZC_CONFIG();
esp_zb_init(&zb_nwk_cfg);

#if CONFIG_OPENTHREAD_SPINEL_ONLY
ESP_ERROR_CHECK(check_ot_rcp_version());
#endif
#if 0
esp_zb_set_primary_network_channel_set(ESP_ZB_PRIMARY_CHANNEL_MASK);
#else
uint32_t zb_channel = 0, channel_mask = 0;
//设置zb channel
zb_channel = 11;
channel_mask = (1l << zb_channel);
esp_zb_set_primary_network_channel_set(channel_mask);
//设置pannid
esp_zb_set_pan_id(0xfedc);
#endif
esp_zb_ep_list_t *ep_list = esp_zb_ep_list_create();
esp_zb_cluster_list_t *cluster_list = esp_zb_zcl_cluster_list_create();
esp_zb_endpoint_config_t endpoint_config = {
    .endpoint = HA_ESP_GW_ENDPOINT,
    .app_profile_id = ESP_ZB_AF_HA_PROFILE_ID,
    .app_device_id = ESP_ZB_HA_REMOTE_CONTROL_DEVICE_ID,
    .app_device_version = 0,
};
//basic cluster
esp_zb_attribute_list_t *basic_cluster = esp_zb_basic_cluster_create(NULL);
esp_zb_basic_cluster_add_attr(basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_MANUFACTURER_NAME_ID, ESP_MANUFACTURER_NAME);
esp_zb_basic_cluster_add_attr(basic_cluster, ESP_ZB_ZCL_ATTR_BASIC_MODEL_IDENTIFIER_ID, ESP_MODEL_IDENTIFIER);
esp_zb_cluster_list_add_basic_cluster(cluster_list, basic_cluster, ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
//identify cluster
esp_zb_cluster_list_add_identify_cluster(cluster_list, esp_zb_identify_cluster_create(NULL), ESP_ZB_ZCL_CLUSTER_SERVER_ROLE);
//groups cluster
esp_zb_groups_cluster_cfg_t group_cfg;
group_cfg.groups_name_support_id = ESP_ZB_ZCL_GROUPS_NAME_SUPPORT_DEFAULT_VALUE;
esp_zb_attribute_list_t *esp_zb_groups_cluster = esp_zb_groups_cluster_create(&group_cfg);
esp_zb_cluster_list_add_groups_cluster(cluster_list, esp_zb_groups_cluster, ESP_ZB_ZCL_CLUSTER_CLIENT_ROLE);
//custom cluster
esp_zb_attribute_list_t *custom_attr = esp_zb_zcl_attr_list_create(ESP_ZB_ZCL_CLUSTER_ID_TRANSMIT_NODE);
esp_zb_cluster_list_add_custom_cluster(cluster_list, custom_attr, ESP_ZB_ZCL_CLUSTER_CLIENT_ROLE);
//
esp_zb_ep_list_add_gateway_ep(ep_list, cluster_list, endpoint_config);
esp_zb_device_register(ep_list);

//
esp_zb_core_action_handler_register(zb_action_handler);
//
ESP_ERROR_CHECK(esp_zb_start(false));
esp_zb_stack_main_loop();
esp_rcp_update_deinit();
vTaskDelete(NULL);

}
error log：
D/[1970-01-01 00:00:35] smart light power device A9572A000366 other func
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 0, address 0x5293, device 74:4d:bd:ff:fe:61:d9:b0, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 0, address 0xf35b, device 74:4d:bd:ff:fe:61:d6:77, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 0, address 0xc503, device 74:4d:bd:ff:fe:61:d9:b7, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 0, address 0x9e3f, device 74:4d:bd:ff:fe:61:d6:7c, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d6:7d, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:da:37, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 0, address 0xe268, device 74:4d:bd:ff:fe:61:d6:8f, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d6:7d, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d6:86, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d6:91, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d6:7f, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 0, address 0x9489, device 74:4d:bd:ff:fe:61:d6:95, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d9:b5, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d9:ae, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:da:39, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d6:53, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:da:30, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d6:53, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 0, address 0x3629, device 74:4d:bd:ff:fe:61:d6:90, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 0, address 0xbdef, device 74:4d:bd:ff:fe:61:d6:7b, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 0, address 0x32ca, device 74:4d:bd:ff:fe:61:d6:87, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 0, address 0x403, device 74:4d:bd:ff:fe:61:da:35, mac_iface_idx 0
ZBOSS: nwk/nwk_nlme.c:803   OOM state is detected. ACHTUNG: Out of memory!
ZBOSS: common/zb_bufpool_mult.c:1650   OOM! bufs allocated {48 i-o 5} max 100
ZBOSS: nwk/nwk_nlme.c:845   ACHTUNG: Sending OOM status
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d6:8e, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d6:43, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d6:80, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d6:41, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d6:8a, mac_iface_idx 0
ZBOSS: nwk/nwk_cr_join.c:1285   association: status 2, address 0xffff, device 74:4d:bd:ff:fe:61:d9:c4, mac_iface_idx 0
ZBOSS: nwk/nwk_nlme.c:866   OOM state ends
ZBOSS: nwk/nwk_nlme.c:803   OOM state is detected. ACHTUNG: Out of memory!
ZBOSS: common/zb_bufpool_mult.c:1650   OOM! bufs allocated {48 i-o 5} max 100
I (42319) ESP_ZB_GATEWAY: ZDO signal: NWK Device Associated (0x12), status: ESP_OK
ZBOSS: secur/bdb_secur.c:398   ACHTUNG: schedule bdb_link_key_refresh_alarm, param 60
I (42319) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Update (0x30), status: ESP_OK
I (42369) ESP_ZB_GATEWAY: ZDO signal: NWK Device Associated (0x12), status: ESP_OK
ZBOSS: secur/bdb_secur.c:398   ACHTUNG: schedule bdb_link_key_refresh_alarm, param 62
I (42379) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Update (0x30), status: ESP_OK
I (42419) ESP_ZB_GATEWAY: ZDO signal: NWK Device Associated (0x12), status: ESP_OK
ZBOSS: secur/bdb_secur.c:398   ACHTUNG: schedule bdb_link_key_refresh_alarm, param 64
I (42429) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Update (0x30), status: ESP_OK
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 12
ZBOSS: common/zb_scheduler.c:565   MAC callbacks rb overflow! param 59

Hi,@xieqinan
Additionally, if we need to provision 34 devices in batch, can all 34 devices be powered on simultaneously, or do they need to be powered on in batches? What is the maximum number of devices our Zigbee network can support for simultaneous power-on and provisioning?

@wensenl We face the same problem and raised #480, it looks like they didn't increase the ZBOSS input static buffer.

Hi,@xieqinan，
I increased the ZBOSS input static buffer, but the same error still occurs. When 34 unprovisioned devices are powered on simultaneously for provisioning, the above error appears. How can this issue be resolved?
code：
//设置zb网络和缓冲大小
esp_zb_overall_network_size_set(128);
esp_zb_io_buffer_size_set(100);

Hi @wensenl ,
The esp_zb_io_buffer_size_set(100); function allocates a total of 100 buffers for the stack, with 4 reserved for high-priority events. The remaining buffers are evenly divided between input and output buffers. The log message OOM! bufs allocated {48 i-o 5} max 100 indicates that the input buffers are insufficient. Could you please set the esp_zb_io_buffer_size_set(254) and esp_zb_scheduler_queue_size_set(254) then test again?

Hi,@xieqinan，
set the esp_zb_io_buffer_size_set(254) and esp_zb_scheduler_queue_size_set(254)，the OOM! bufs allocated {48 i-o 5} max 10 error did not occur.
However, the problem of 34 Zigbee devices being unable to successfully power on for permit join network remains. How to solve this problem? Can you set up an environment to test this issue on your end?
The error message printed by Zigbee during my testing is as follows:
I (1697997) ESP_ZB_GATEWAY: ZDO signal: NLME Status Indication (0x32), status: ESP_OK
I (1697997) ESP_ZB_GATEWAY: NLME Status Indication status: 0x0000, network_addr: 0xee46, unknown_command_id: 0
D/[1970-01-01 01:50:42] heartbeat response
ZBOSS: zdo/af_rx.c:494   zb_zdo_device_is_unreachable: addr_ref 56
ZBOSS: zdo/af_rx.c:494   zb_zdo_device_is_unreachable: addr_ref 56
ZBOSS: zdo/zdo_app_leave.c:360   no nbt for addr_ref 56, do nothing
ZBOSS: zdo/zdo_app_leave.c:383   zb_nwk_neighbor_delete addr_ref not found [-28]
ZBOSS: zdo/zdo_app_leave.c:360   no nbt for addr_ref 56, do nothing
ZBOSS: zdo/zdo_app_leave.c:383   zb_nwk_neighbor_delete addr_ref not found [-28]
I (1701987) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Unavailable (0x3c), status: ESP_OK
I (1701997) ESP_ZB_GATEWAY: ZDO Device (0xee46) Unavailable
I (1702007) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Unavailable (0x3c), status: ESP_OK
I (1702007) ESP_ZB_GATEWAY: ZDO Device (0xee46) Unavailable
E (1713147) ESP_RADIO_SPINEL: dropping radio frame: Parse
ZBOSS: nwk/nwk_main.c:3775   Put 2 into input queue (blocked by 49)
ZBOSS: common/zb_address.c:696   WARNING: clear pending_for_delete for ref 102
ZBOSS: mac/mac_cr_coordinator.c:250   Oops - out of MAC queue!
I (1713197) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Update (0x30), status: ESP_OK
ZBOSS: nwk/nwk_main.c:3775   Put 17 into input queue (blocked by 49)
ZBOSS: secur/bdb_secur.c:398   ACHTUNG: schedule bdb_link_key_refresh_alarm, param 12
ZBOSS: nwk/nwk_main.c:2360   set input_blocked_by and process 2 from in queue
I (1713267) ESP_ZB_GATEWAY: ZDO signal: ZDO Device Update (0x30), status: ESP_OK
ZBOSS: secur/bdb_secur.c:398   ACHTUNG: schedule bdb_link_key_refresh_alarm, param 42
ZBOSS: nwk/nwk_main.c:2360   set input_blocked_by and process 17 from in queue
I (1713287) ESP_ZB_GATEWAY: ZDO signal: NLME Status Indication (0x32), status: ESP_OK
I (1713287) ESP_ZB_GATEWAY: NLME Status Indication status: 0x0006, network_addr: 0xb771, unknown_command_id: 0
I (1713297) ESP_ZB_GATEWAY: ZDO signal: NLME Status Indication (0x32), status: ESP_OK
I (1713307) ESP_ZB_GATEWAY: NLME Status Indication status: 0x0006, network_addr: 0xb771, unknown_command_id: 0
I (1713317) ESP_ZB_GATEWAY: New device commissioned or rejoined (short: 0x9ffb)
I (1713327) ESP_ZB_GATEWAY: esp_zb_zcl_add_group add device 0x9ffb to group 0x0001 successfully
111811227s3.txt

Hi,@xieqinan，
Do we have API interfaces to set up whitelists for permit join networks to control device permit join networks? If so, which APIs are they? How to use it?

Hi @wensenl ,

However, the problem of 34 Zigbee devices being unable to successfully power on for permit join network remains. How to solve this problem? Can you set up an environment to test this issue on your end?

We are setting up the test environment based on the above description on our side. Please be patient.

Do we have API interfaces to set up whitelists for permit join networks to control device permit join networks? If so, which APIs are they? How to use it?

No, the whitelist API is not available in the current SDK (v1.6.0).

Hi @wensenl ,
Could you please also share the logs generated by the devices that failed to join the network?

Hi,@xieqinan，
the devices log
11211125h2.txt

Hi,@xieqinan，
the devices log
11211125h2.txt

Hi,@xieqinan，
the devices log
device esp32h2.txt
gateway esp32s3.txt

Hi,@xieqinan，
Has there been any progress on the issue?

Has there been any progress on the issue?

We have reproduced this issue, although with some differences. The issue is triggered by an insufficient size of the TX queue on our side, causing an infinite loop. We have fixed it and successfully joined 40 devices. This fix will be included in the next release. If you would like to receive temporary libraries to address this issue, please contact our technical inquiries.

Hi,@xieqinan，
What is the new SDK version? When will the release version be released?

I can't provide a specific time as it mainly depends on the development progress of the release plan.

Hi,
We provided you with the temporary Zigbee libraries; were they helpful? The fixes included in those temporary libraries have already been incorporated into esp-zigbee-sdk v1.6.1. Please check it out.

The issue should be fixed in the 1.6.1 release, feel free to reopen if any follow up questions.


Mention second installation method/ OSx --> macOS

Codecov Report

Merging #29 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #29   +/-   ##
=======================================
  Coverage   74.69%   74.69%
=======================================
  Files          18       18
  Lines        1055     1055
=======================================
  Hits          788      788
  Misses        267      267

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update a0f5e9c...79579a5. Read the comment docs.

Looks good. I think long term I will need to package and distribute rather then having users manually install.

My only suggestion is to have it separated out into it's own lines like this:
If the org_to_anki command returns a module not found error try the following
pip3 install ./

instead of
python3 setup.py install


DCR container uses host network mode

What does this change?
Why?

This was just to test that host mode outside of the other changes in #948. Closing as all the checks passed.


unsupported message

Hello, when trying to send a set mode i get unsupported command.
I've tried using both that message body
{
        "header": {
            "system_id": 1,
            "component_id": 1,
            "sequence": 0
        },
        "message": {
            "type": "SET_MODE",
            "custom_mode": 2,
            "target_system": 0,
            "base_mode": {
                "type": "MAV_MODE_PREFLIGHT"
            }
        }
    }

and this one
{
        "header": {
            "system_id": 1,
            "component_id": 1,
            "sequence": 0
        },
        "message": {
            "type": "COMMAND_LONG",
            "param1": 2,  # mode
            "param2": 0.0,  # custom mode
            "param3": 0.0,  # custom submode
            "param4": 0.0,  # empty
            "param5": 0.0,  # empty
            "param6": 0.0,  # empty
            "param7": 0.0,  # empty
            "command": {
                "type": "MAV_CMD_DO_SET_MODE"
            },
            "target_system": 0,
            "target_component": 0,
            "confirmation": 0
      }
}

Any suggestion ?

Hi @arendeutsch, Please can you inform which version of mavlink2rest that you are running ? It should give you a feedback about wrong messages.
Both commands work just fine here, can you please information what is the error message ?

If you want to try it yourself:
$ export DATA='{
        "header": {
            "system_id": 1,
            "component_id": 1,
            "sequence": 0
        },
        "message": {
            "type": "SET_MODE",
            "custom_mode": 2,
            "target_system": 0,
            "base_mode": {
                "type": "MAV_MODE_PREFLIGHT"
            }
        }
    }'
$ curl --request POST http://<IP_ADDRESS>:8088/mavlink -H "Content-Type: application/json" --data $DATA

or
$ export DATA='{
        "header": {
            "system_id": 1,
            "component_id": 1,
            "sequence": 0
        },
        "message": {
            "type": "COMMAND_LONG",
            "param1": 2,
            "param2": 0.0,
            "param3": 0.0,
            "param4": 0.0,
            "param5": 0.0,
            "param6": 0.0,
            "param7": 0.0,
            "command": {
                "type": "MAV_CMD_DO_SET_MODE"
            },
            "target_system": 0,
            "target_component": 0,
            "confirmation": 0
      }
}'
$ curl --request POST http://<IP_ADDRESS>:8088/mavlink -H "Content-Type: application/json" --data $DATA

I'm using version 0.8.0 of mavlink2rest

Please provide the output of the commands that I just said in my previous post or the answer from the server when you do a http post.

curl --request POST http://<IP_ADDRESS>:4777/mavlink -H "Content-Type: application/json" --data $DATA
Error: ["Failed to parse common message: Error("EOF while parsing a value", line: 1, column: 10)", "Failed to parse ardupilotmega message: Error("EOF while parsing a value", line: 1, column: 10)"]curl: (3) [globbing] unmatched brace in column 1
curl: (6) Could not resolve host: 1,
curl: (6) Could not resolve host: "component_id"
curl: (6) Could not resolve host: 1,
curl: (6) Could not resolve host: "sequence"
curl: (3) [globbing] unmatched close brace/bracket in column 2
curl: (6) Could not resolve host: "message"
curl: (3) [globbing] unmatched brace in column 1
curl: (6) Could not resolve host: "SET_MODE",
curl: (6) Could not resolve host: "custom_mode"
curl: (6) Could not resolve host: 2,
curl: (6) Could not resolve host: "target_system"
curl: (6) Could not resolve host: 0,
curl: (6) Could not resolve host: "base_mode"
curl: (3) [globbing] unmatched brace in column 1
curl: (3) [globbing] unmatched close brace/bracket in column 21

It appears that something is wrong with your bash or curl, it's failing to create the command and contact with the server, as you can see from the error message, it's ignoring the http:// address and trying to use everything after that as a host address.
Please provide the output of curl --request GET http://<IP_ADDRESS>:4777/mavlink  and curl --version.
Besides that, can you provide a screenshot of both export DATA=... and curl --request POST.. to see if anything was copy-pasted wrongly ?

Hi @arendeutsch, thank you for the information, it appears that this version of curl has a problem related to the data field, I'm running 7.71 here.
To fix that problem in your curl version, please call curl $DATA variable with double quotes, line this:
curl --request POST http://<IP_ADDRESS>:4777/mavlink -H "Content-Type: application/json" --data "$DATA"

Thank. I get now empty response which i guess means OK 200.
But nothing happens. I was expected to see the flight mode changes to Depth hold mode.
BTW - The same thing is was happening yesterday when i used postman and when i was running it via python script using post requests. I get response OK 200. but when looking at the log of mavproxy i get "God mavlink message COMMAND_ACK {command: 176, result: 3}" which means unsupported

Just an update on my testing.
When using the following payload in the body:
{         "header": {             "system_id": 1,             "component_id": 1,             "sequence": 0         },         "message": {             "type": "COMMAND_LONG",             "param1": 2,  # mode             "param2": 0.0,  # custom mode             "param3": 0.0,  # custom submode             "param4": 0.0,  # empty             "param5": 0.0,  # empty             "param6": 0.0,  # empty             "param7": 0.0,  # empty             "command": {                 "type": "MAV_CMD_DO_SET_MODE"             },             "target_system": 0,             "target_component": 0,             "confirmation": 0       } }
I can set only stabilize flight mode when changing param1: 1, 3, 5, 7, 9, 11 are changing the vehicle mode to stabilize which does not corresponds to the mode mapping i found in the code. Other values give me the previous error:
Got MAVLink msg: COMMAND_ACK {command : 176, result : 3}

new update, it seems that to get it work param1 had to be 1 while param 2 is the mode mapping for the ardusub, i.e 1 - acro, 2 - depth, 19 - manual etc.

But maybe you can help me with some other issue. Im trying to send manual command with the following payload
    payload = {         "header": {             "system_id": 1,             "component_id": 1,             "sequence": 0         },         "message": {             "type": "MANUAL_CONTROL",             "x": joy_x,             "y": joy_y,             "z": joy_z,             "r": joy_r,             "buttons": 0,             "target": 0         }     }
I do get OK 200 in my response but nothing happens. Can you try that command please ?

I can set only stabilize flight mode when changing param1: 1, 3, 5, 7, 9, 11 are changing the vehicle mode to stabilize which does not corresponds to the mode mapping i found in the code. Other values give me the previous error:

Where you come up with this numbers ?
MAV_CMD_DO_SET_MODE uses MAV_MODE in param 1, as described in the documentation.
Like: 80 for MAV_MODE_STABILIZE_DISARMED, 208 for MAV_MODE_STABILIZE_ARMED and etc.
Besides that, I'm not aware if ardupilot supports MAV_MODE at all, the project uses mainly custom modes for each vehicle, so I recommend to set param1 as 1 and change param2 based in the custom mode that you want.
Right now there is a problem in the ardusub documentation that does not display the list of custom modes with the parameter value, but you can grab it from here: https://github.com/ArduPilot/ardupilot/blob/master/ArduSub/defines.h#L33
So you can use param1: 1 and param2: 0 for stabilize, or param2: 1 for acro and etc.

Examples
```
# Stabilize
'{
        "header": {
            "system_id": 1,
            "component_id": 1,
            "sequence": 0
        },
        "message": {
            "type": "COMMAND_LONG",
            "param1": 1,
            "param2": 0.0,
            "param3": 0.0,
            "param4": 0.0,
            "param5": 0.0,
            "param6": 0.0,
            "param7": 0.0,
            "command": {
                "type": "MAV_CMD_DO_SET_MODE"
            },
            "target_system": 0,
            "target_component": 0,
            "confirmation": 0
      }
}'
Acro
'{
"header": {
"system_id": 1,
"component_id": 1,
"sequence": 0
},
"message": {
"type": "COMMAND_LONG",
"param1": 1,
"param2": 1,
"param3": 0.0,
"param4": 0.0,
"param5": 0.0,
"param6": 0.0,
"param7": 0.0,
"command": {
"type": "MAV_CMD_DO_SET_MODE"
},
"target_system": 0,
"target_component": 0,
"confirmation": 0
}
}'
</details>

I do get OK 200 in my response but nothing happens. I was expecting the rov to run in 50% thrust forward Can you try that command please ?

You need to configure system_id to 255, since ardupilot will only accept this command from GCS (you can change this value in the GCS parameter ID), and target should be 1since this is the default sysid of ardupilot.

I've change the system id to 255 both in the header and in QGC (SYSID_THISMAV) but still nothong happens
{         "header": {             "system_id": 255,             "component_id": 1,             "sequence": 0         },         "message": {             "type": "MANUAL_CONTROL",             "x": 500,             "y": 100,             "z": 250,             "r": 500,             "buttons": 0,             "target": 1         }     }
Are there other parameters in QGS that need to be changed ? is this command should be sent in a some interval, I've tried different intervals of sending this request with no luck

Did you arm the vehicle before sending manual contorl ?

@arendeutsch Let me know if you have fixed your problem, from what I can tell just arming the vehicle and sending the manual control with the correct parameters should work

Sorry for the late replay @patrickelectric,
Everything works fine with sending manual command, i had to change a parameter in QGS.
Thank you very much for the support :+1:

thank you for the update


Purchase Failed

It does everything up to enter cvv not sure why I put --cvv ___

any luck @J420C ?

No luck for me getting payment errors I think I need new accounts.

I have this issue as well, would help if there is one full functional argument line as an example, does it matter the position where the argument is placed?


Esp-idf installation is failing in Windows

Hi! I think esp-idf installation is failing for Windows, I discovered the issue while working in espup, at first I thought I was doing something wrong (as it's my first from-scratch Rust project) but I managed to reproduce it with esp-idf-sys via esp-idf-template. Steps to reproduce:

Generate an esp-idf-template project: In my case I generated for esp32 with std and v.4.4
Export  $Env:LIBCLANG_PATH="<path_to_esp>/.espressif/tools/xtensa-esp32-elf-clang/lib"
Build the project. At this point, esp-idf-sys should download and install esp-idf under the .embuild directory. The build fails with:

 ERROR: Could not find a version that satisfies the requirement windows-curses; sys_platform == "win32" (from esp-windows-curses) (from versions: none)
  ERROR: No matching distribution found for windows-curses; sys_platform == "win32"
  Traceback (most recent call last):
    File "C:\Users\sergio\Documents\Espressif\tests\espidf-test\.embuild\espressif\esp-idf\release-v4.4\tools\idf_tools.py", line 1973, in <module>
      main(sys.argv[1:])
    File "C:\Users\sergio\Documents\Espressif\tests\espidf-test\.embuild\espressif\esp-idf\release-v4.4\tools\idf_tools.py", line 1969, in main
      action_func(args)
    File "C:\Users\sergio\Documents\Espressif\tests\espidf-test\.embuild\espressif\esp-idf\release-v4.4\tools\idf_tools.py", line 1619, in action_install_python_env
      subprocess.check_call(run_args, stdout=sys.stdout, stderr=sys.stderr, env=env_copy)
    File "C:\Python311\Lib\subprocess.py", line 413, in check_call
      raise CalledProcessError(retcode, cmd)
  subprocess.CalledProcessError: Command '['C:\\Users\\sergio\\Documents\\Espressif\\tests\\espidf-test\\.embuild\\espressif\\python_env\\idf4.4_py3.11_env\\Scripts\\python.exe', '-m', 'pip', 'install', '--no-warn-script-location', '-r', 'C:\\Users\\sergio\\Documents\\Espressif\\tests\\espidf-test\\.embuild\\espressif\\esp-idf\\release-v4.4\\requirements.txt', '--extra-index-url', 'https://dl.espressif.com/pypi']' returned non-zero exit status 1.
  Error: Could not install esp-idf

  Caused by:
      command '"python" "C:\\Users\\sergio\\Documents\\Espressif\\tests\\espidf-test\\.embuild\\espressif\\esp-idf\\release-v4.4\\tools\\idf_tools.py" "--idf-path" "C:\\Users\\sergio\\Documents\\Espressif\\tests\\espidf-test\\.embuild\\espressif\\esp-idf\\release-v4.4" "--non-interactive" "install-python-env"' exited with non-zero status code 1

Again, I am no expert in embuild/esp-idf-sys and even less, in Windows, so let me know if I'm missing something.

After some more testing, I found out that the error comes from the Window install script. Both install.bat and ìnstall.ps1 are giving me the same error

Mistery solved, I was using python Python 3.11.0b5 which is a pre-release and there are no wheels for windows-curses for python 3.11. Running the installers with python 3.8.7 works fine. Now, the question is.... Should any check be done in embuild to avoid this situation?


errror: in your SQL syntax

Issue Report

IP-Check Version:
2.07
Java Version:
8
Database Type:
MySQL
Description of the problem:
Evertime I restart the server I got the message, after I have congigurd the myqul database:

[IP-Check] You have an error in your SQL syntax; check the manual that corresponds to your MariaDB server version for the right syntax to use near '-check.ipcheck_user' at line 1

I tried every datbase config, for exemple:
dbUsername: "makemp1997"
dbPassword: "test123"
dbHostname: "123.123.321.123"
dbName: "ip-check"
dbPort: 3306
Although it have contact to the datase, becase there is database sturcture of ip-check, but still I got that error.
So do you know how I can fix this?
How to replicate:

Checklist:

[X] I made sure there aren't duplicates of this report (Use Search)
[X] I made sure I am using an up-to-date version of IP-Check.
[X] I Made sure the bug/error is not caused by any other plugin.

As a cursory, I'd first verify that there are no spaces in the dbName field. The error would seem to suggest that the database name is being cut off for some reason.
If there are no spaces, my next suggestion would be to change the value of dbName from 'ip-check' to 'ipcheck' and reflect this change in your MySQL database accordingly. It's possible that whatever SQL version is being used by your server may have a problem with the dash '-' character being used.
If neither of these work, please let me know.
-Jnk


Update composer.json for packagist.org

Description
New github account (foundation) requires updates to composer.json
Someone will still have to submit it to packagist.org and depreciate the zurb version and link to the latest.
Thanks for continuing to support PHP and packagist.org
Types of changes

[ ] Documentation
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (anything that would change an existing functionality)
[ ] Maintenance (refactor, code cleaning, development tools...)

Checklist

[X] I have read and follow the CONTRIBUTING.md document.
[X] The pull request title and template are correctly filled.
[X] The pull request targets the right branch (develop or develop-v...).
[X] My commits are correctly titled and contain all relevant information.
[x] I have updated the documentation accordingly to my changes (if relevant).
[ ] I have added tests to cover my changes (if relevant).

Unfortunately someone else has grabbed it:
https://packagist.org/packages/foundation/foundation

It seems there was nothing published under these names:
https://packagist.org/packages/zurb/foundation-sites
https://packagist.org/packages/founation/foundation-sites
Only https://packagist.org/packages/zurb/foundation

This pull request has been mentioned on Foundation Open Source Community. There might be relevant details there:
https://foundation.discourse.group/t/foundation-v6-6-1-shipped/67/1

That was me.  I assumed Packagist accounts were linked to github some how,
but obviously not.
In any case, I would think in separating from Zurb you would want a
separate Packagist account not related to Zurb.  I'll reach out to the
author and see if they will release the name, as the package has 18
installs and no commits in 3 years, so assuming it is abandoned.
Bruce
On Fri, Dec 13, 2019 at 3:28 PM Joe Workman<EMAIL_ADDRESS>wrote:

This pull request has been mentioned on Foundation Open Source Community.
There might be relevant details there:
https://foundation.discourse.group/t/foundation-v6-6-1-shipped/67/1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/foundation/foundation-sites/pull/11936?email_source=notifications&email_token=ABYW6S472M2OGISOQVCOA6LQYPV7TA5CNFSM4JZTU722YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG3FJHY#issuecomment-565597343,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYW6S6ZXNJYCMDDSXNU5Q3QYPV7TANCNFSM4JZTU72Q
.

Reached out to shukrunor at gmail.  I'll let you know if I hear anything.
Bruce
On Fri, Dec 13, 2019 at 3:36 PM Bruce Wells<EMAIL_ADDRESS>wrote:

That was me.  I assumed Packagist accounts were linked to github some how,
but obviously not.
In any case, I would think in separating from Zurb you would want a
separate Packagist account not related to Zurb.  I'll reach out to the
author and see if they will release the name, as the package has 18
installs and no commits in 3 years, so assuming it is abandoned.
Bruce
On Fri, Dec 13, 2019 at 3:28 PM Joe Workman<EMAIL_ADDRESS>wrote:

This pull request has been mentioned on Foundation Open Source
Community. There might be relevant details there:
https://foundation.discourse.group/t/foundation-v6-6-1-shipped/67/1
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/foundation/foundation-sites/pull/11936?email_source=notifications&email_token=ABYW6S472M2OGISOQVCOA6LQYPV7TA5CNFSM4JZTU722YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG3FJHY#issuecomment-565597343,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABYW6S6ZXNJYCMDDSXNU5Q3QYPV7TANCNFSM4JZTU72Q
.

He said he is planning on using it. Pick another name and we can use that.  zfoundation maybe?

He is going to help out.  Look for him on discord channel!

zfoundation

It is a community project now so no more z.


AudioStore development (original #322)

This issue has been migrated from the CC Search Catalog repository
Author: mariuszskon
Date: Fri Mar 13 2020
Labels: 🙅 status: discontinued

As per #311, integrating audio into CC Catalog will require a few different things. This issue hopes to keep track of everything relevant to the development of AudioStore.
(NEW) means a field that was not in ImageStore that was added to AudioStore
Current schema (in audio.py):

Foreign ID
Landing URL
Audio URL
File format (NEW)
Thumbnail URL
Filesize
Duration (NEW)
Samplerate (NEW)
Bitdepth (NEW)
Channels (NEW)
License (like ImageStore, license and license version)
Creator
Creator URL
Title
Collection/Album (NEW)
Type (music, podcast, lecture) (NEW)
Genre (NEW)
Language (NEW)
Metadata
Tags
Provider
Source

Other data to keep, but inside metadata rather than dedicated columns:

Date of publishing
Instruments
Mood
Description
Bitrate (as provided by source, rather than calculating ourselves from samplerate and bitdepth)
Views
Number of ratings
Numbers of comments
Related (list of foreign IDs of sounds which source considers to be similar)

Inappropriate columns for AudioStore that are in ImageStore:

Width
Height
Watermarked

Original Comments:
Issue author mariuszskon commented on Fri Mar 13 2020:

I am uncertain about the "type" field (as in music, podcast, lecture) and if it could be combined with genre in some way, or if we should keep it separate. What do you think @mathemancer ?
source

Issue author mariuszskon commented on Fri Mar 13 2020:

Date field blocked by #324
source

mathemancer commented on Mon Mar 16 2020:

@mariuszskon I think Genre and Type are different.  We could probably come up with a list of 'allowed' types, e.g., music, podcast, lecture.  Then, within music, we'd have the genres:  rock, pop, classical, jazz, etc.  On the other hand, in the 'podcast' type, for genre, we'd have: 'science', 'comedy', 'news', etc.
source

mathemancer commented on Mon Mar 16 2020:

@brenoferreira Do you have any guidance or ideas based on what you'd like to have available to the front end here?
source

brenoferreira commented on Mon Mar 16 2020:

Based on some of the designs here, it seems very comprehensive to me.
The frontend probably won't look exactly like this, but it'll probably be inspired by it. The only thing missing from the metadata list here are things like music instruments and mood. But I think that's ok
source

Issue author mariuszskon commented on Tue Mar 17 2020:

@mathemancer Indeed I see the distinction much more clearly, and it is certainly worth having them separate.
source

Issue author mariuszskon commented on Tue Mar 17 2020:

@brenoferreira instruments and mood can be added no problem, but I am concerned that audio sources might not have this information available for ingestion.
source

brenoferreira commented on Tue Mar 17 2020:

yes. that's what I meant. If the source has the info, great. But if not, it
should be fine for now

On Mon, Mar 16, 2020 at 11:33 PM Mariusz Skoneczko<EMAIL_ADDRESS>wrote:

@brenoferreira https://github.com/brenoferreira instruments and mood
can be added no problem, but I am concerned that audio sources might not
have this information available for ingestion.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/creativecommons/cccatalog/issues/322#issuecomment-599846329,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAFMTSYST7AKUKEJPCGGO4LRH3ON7ANCNFSM4LG32CIQ
.

--
Thank you
Breno Ferreira
Front-end Engineer
Creative Commons
source

I think this is ready to close! See https://github.com/WordPress/openverse-catalog/pull/130 and https://github.com/WordPress/openverse-catalog/pull/123
If anyone sees a reason to reopen, please do


Target MRTCore projection dll to any CPU

Does this support apps that do want to target a specific CPU?

Does this support apps that do want to target a specific CPU?

The app using the projection dll can still target a specific CPU.


ssh not connecting

I was trying out the editor with remote code editing on my mac.
when I try to access the remote server it says disconnected. ( I can connect to remote host via my iterm without any issues)
where can I see logs ? my gut feeling says that editor is not picking up the keys on my ssh-agent
The only error I see on the terminal is
/root/.lapce/lapce-proxy-0.0.12: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.28' not found (required by /root/.lapce/lapce-proxy-0.0.12)

which is kind of odd as I was trying this on my mac

can you tell more about remote server ?

@harrydevnull The remote server will run something to talk with Lapce local ui. The binary on the server was compiled with GLIBC_2.28 so that's why it didn't run. It means it's running on a slightly old Linux OS.

it's running bionic
NAME="Ubuntu"
VERSION="18.04.5 LTS (Bionic Beaver)"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 18.04.5 LTS"
VERSION_ID="18.04"
HOME_URL="https://www.ubuntu.com/"
SUPPORT_URL="https://help.ubuntu.com/"
BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/"
PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy"
VERSION_CODENAME=bionic
UBUNTU_CODENAME=bionic

would it be possible to stream the logs while connecting to server?
something akin to
ssh -vvv username@serverip

I think I'm having a similar issue from Windows (with https://github.com/lapce/lapce/releases/tag/v0.0.12 portable version) to an older Linux server that ssh/putty can connect to without any problem.

actually Lapce hangs under windows :( Quiting and restarting does NOT resolve it, on re-open Lapce attempts to ssh connect again. Can open previous work space which appears to cancel the ssh attempt

I'm having this issue as well. Is there any way to debug what might be going on for myself?

actually Lapce hangs under windows :(

Can confirm. I have two PCs with Lapce installed on them and a homeserver. I configured the two PCs with the same .ssh/config and copied both of their public keys to the authorized_keys file of my homeserver. When I use the "Connect to ssh host" dialog in Lapce with username@homeserver it connects instantly on the PC running arch and takes about 30s on the PC running windows.


removing accesory

Hi,
What's the way to remove an accesory or plugin altogether without messing rest of my setup like automation rules etc. I have 70+ devices sort/hard so doing all my automations from scratch is mad.
Does removing accesories and persists folders reset everything including my custom device names and automations?
Many thanks,

Remove the plugin from the platforms or accessories section in config.json (and from the plugins array if you use that).  Then restart homebridge with -R to remove the stale cached accessories.
Do not mess with the directories.  Deleting persist is like factory-resetting your bridge: it will no longer be paired to HomeKit, but HomeKit still thinks it is.  Deleting accessories will start homebridge without exposing the cached accessories, causing HomeKit to delete them, incl. the names set in HomeKit and any links to rooms, groups, scenes, and automations.  The plugins will re-expose the accessories shortly, but HomeKit will see these as new accessories.


Incorrect display of battery charge

The battery charge is not displayed correctly. When charging shows 95-100%, when charging is off 2-10%

It fixed itself LOL


Delete mixed case file 1143-Longest-Common-Subsequence.java

File(s) Modified: 1143-longest-common-subsequence.java
Language(s) Used: java
Submission URL: N/A

There is a single version of each file. For some reason there are 2 versions of the file 1143-longest-common-subsequence.java in the repo. One version is lowercase and the other is mixed case, 1143-Longest-Common-Subsequence.java. The mixed case file is Untracked by git, so I removed it.

I'm happy to help @sujal-goswami
I noticed other mixed case files in the repo.
Let me know if you want me to remove them too, defaulting to the lowercase filename.

Yes, please go ahead with defaulting to lowercase filenames for consistency. I really appreciate your contribution.

Cool!
I think this is the list of all mixed-case filenames within a code directory.
go/0236-Lowest-Common-Ancestor-of-Binary-Tree.go
go/0852-Peak-Index-In-A-Mountain-Array.go
go/0063-Unique-Paths-II.go
go/0876-Middle-Of-The-Linked-List.go
python/1137-N-th-Tribonacci-Number.py
python/0119-Pascal-Triangle-II.py
java/1275-Find-Winner-on-a-Tic-Tac-Toe-Game.java
java/2328-Number-of-Increasing-Paths-in-a-Grid.java
java/2390-Removing-Stars-From-a-String.java
java/1160-Find-Words-That-Can-Be-Formed-by-Characters.java
java/0402-Remove-K-Digits.java
java/2310-Sum-of-Numbers-With-Units-Digit-K.java
java/1155-Number-of-Dice-Rolls-With-Target-Sum.java
java/0456-132-Pattern.java
cpp/2235-Add-Two-Integers.cpp
cpp/1641-Count-Sorted-Vowel-Strings.cpp
cpp/2315-Count-Asterisks.cpp
cpp/0387-First-Unique-Character-In-A-String.cpp
cpp/0122 - Best Time to Buy And Sell Stock II.cpp
cpp/0219-Contains-Duplicate-II.cpp
cpp/0236-Power-Of-Three.cpp
cpp/1213-Maximum-Product-Difference-Between-Two-Pairs.cpp
cpp/0740-Delete-And-Earn.cpp
cpp/1512-Number-Of-Good-Pairs.cpp
cpp/0279-Perfect-Squares.cpp
cpp/0278-First-Bad-Version.cpp
cpp/1920-Build-Array-From-Permutation.cpp
cpp/0342-Power-Of-Four.cpp
csharp/1480-Running-Sum-Of-1D-Array.cs
javascript/1486-XOR-operation-in-an-array.js
javascript/1863-sum-of-all-subset-XOR-totals.js
javascript/1514-Path-With-Maximum-Probability.js

OK, just submitted the pull request.


remove BkgErrSOCA

Description
@guillaumevernieres , @Dooruk , do either of you still use the BkgErrSOCA linear variable change?
I would like to delete it, as people should instead be using the StdDev saber outer block now.

No we use SOCABkgErrFilt (SABER outer block), BkgErrGODAS, BalanceSOCA. Should we switch from BkgErrGODAS to StdDev?

No we use SOCABkgErrFilt (SABER outer block), BkgErrGODAS, BalanceSOCA. Should we also switch from BkgErrGODAS to StdDev?

@Dooruk nope, keep using that! though after https://github.com/JCSDA-internal/soca/pull/1085 it will be renamed to the ParametricOceanStdDev saber outer block


Updates to gp toolbox to remove the reference to App6b

updates to both tools and the tool description for the removal of the
reference to App6b

The removal of App6 is complete; however, now the model has a broken link:

Also, just wanted to make sure I am seeing the same changes. The difference that I am seeing is in the option to select APP6, which only leaves us 2525. I think it might make sense to now just not expose this option and update the tools to just expect 2525 and remove this parameter. No reason to give options to users that end up with only one option.

The removal of these parameters needs to be put in as enhancements and should not be fixed a part of this pull request.


ADF sync from DataFactoriesDev branch into master

I've synced whatever in our private branch into master with a few changes.

removed an internal property ActivityRunId.
bumped up nugget version.

Hi @yitao-zhang, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (yitzhang). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, or work for Microsoft Open Technologies, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;


Panic error when decoding

Hello,
I am trying to update document, but it always fail.
Status of update it's always same:
{
    "status": "failed",
    "updateId": 348,
    "type": {
        "name": "DocumentsPartial"
    },
    "message": "internal: decoding failed",
    "errorCode": "internal",
    "errorType": "internal_error",
    "errorLink": "https://docs.meilisearch.com/errors#internal",
    "duration": 0.007,
    "enqueuedAt": "2021-08-17T13:44:39.126708739Z",
    "processedAt": "2021-08-17T13:44:39.150588898Z"
}

Error could be caused by sending only updated fields to database not whole object, but in old version  v0.20 everything works as expected.
Working with Meilisearch in NestJS project. My code:
  const client = new MeiliSearch({
    host: `http://http://<IP_ADDRESS>:7700/`,
    apiKey: `${appConfig().meiliDatabase.apiKey}`,
  });

....

this.meiliService.meiliSearchClient.index(`notes`).updateDocuments([{_id: '123', text: 'Hello'  }])

Hello @lev-michael! Thanks for your return!
can you send us the dataset that causes the failure? Otherwise, we cannot reproduce it.

Also, if you have time, could you check to import your data using our new indexer? It's available at the branch test-new-indexer on this PR https://github.com/meilisearch/MeiliSearch/pull/1588:
git clone git@github.com:meilisearch/MeiliSearch.git
cd MeiliSearch
git checkout test-new-indexer
cargo run --release -- --master-key=YourMasterKey

It would be very helpful!
Thanks in advance 🙂

Hello @lev-michael! Thanks for your return!
can you send us the dataset that causes the failure? Otherwise, we cannot reproduce it
What is your machine? Are you using the docker image or the binary file of rc5?

Sure, object I am trying to update:
{
_id: "611a3dd9d2371e1e31599367",
createdAt:<PHONE_NUMBER>442,
label: "New case",
slug: null,
author: "John Cage",
category: 103,
status: {
   "state":"CREATED",
   "updatedAt": "2021-08-16T10:28:41.414Z",
   "description":"Case created"
},
responsiblePersons: ["John Cage"],
advisors: [],
clients: [],
watchers: ["John Cage"],
type: "case",
updatedAt:<PHONE_NUMBER>171,
}

With update:
this.meiliService.meiliSearchClient.index(`cases`).updateDocuments([{
  _id: '611a3dd9d2371e1e31599367',
  label: 'Not new case',
  updatedAt:<PHONE_NUMBER>171
}])

Index primary key is set as '_id'.

Also, if you have time, could you check to import your data using our new indexer? It's available at the branch test-new-indexer on this PR #1588:
git clone git@github.com:meilisearch/MeiliSearch.git
cd MeiliSearch
git checkout test-new-indexer
cargo run --release -- --master-key=YourMasterKey

It would be very helpful!
Thanks in advance

Ok if I have time I will try it and check it.

Hello @lev-michael! I'm sorry, I didn't succeed to reproduce your error with the document you gave.
Here are my steps:

create an index with _id as primary key
add the document with this route :

[
{
"_id": "611a3dd9d2371e1e31599367",
"createdAt":<PHONE_NUMBER>442,
"label": "New case",
"slug": null,
"author": "John Cage",
"category": 103,
"status": {
   "state":"CREATED",
   "updatedAt": "2021-08-16T10:28:41.414Z",
   "description":"Case created"
},
"responsiblePersons": ["John Cage"],
"advisors": [],
"clients": [],
"watchers": ["John Cage"],
"type": "case",
"updatedAt":<PHONE_NUMBER>171
}
]

Update the document with this route:

[
  {
	"_id": "611a3dd9d2371e1e31599367",
    "label": "Not new case",
    "updatedAt":<PHONE_NUMBER>171
  }
]

Check the update with this route, here is the result:

[
    {
        "status": "processed",
        "updateId": 0,
        "type": {
            "name": "DocumentsAddition",
            "number": 1
        },
        "duration": 0.058,
        "enqueuedAt": "2021-08-18T07:30:43.550368Z",
        "processedAt": "2021-08-18T07:30:43.609698Z"
    },
    {
        "status": "processed",
        "updateId": 1,
        "type": {
            "name": "DocumentsPartial",
            "number": 1
        },
        "duration": 0.021,
        "enqueuedAt": "2021-08-18T07:30:47.460047Z",
        "processedAt": "2021-08-18T07:30:47.481681Z"
    }
]

Be sure we really want to fix this bug, this is indeed NOT expected and not the user's fault. We just need more information to reproduce it and fix it.
Could you send us the detailed steps? And if possible your dataset. In private by mail if you cannot share it!

Is your machine 32bit?
Can you give us the output of
uname -a

in your terminal?

Hello @lev-michael
MeiliSearch v0.21.0 is out. Does this version solve your issue?

Is your machine 32bit?
Can you give us the output of
uname -a

in your terminal?

I have 64bit machine with Ubuntu 20.04.

Hello @lev-michael MeiliSearch v0.21.0 is out. Does this version solve your issue?

Yes, it does. I tried it today with new version and it runs without any problem. Unfortunately I didn't find what caused my problem before.
Thank you for your help.

Thank you for you report 😄
I close this issue then


Add ProcessDataBroadcastThread

Codecov Report

Merging #158 (a715d58) into main (4d70f9f) will decrease coverage by 0.40%.
The diff coverage is 65.85%.

@@            Coverage Diff             @@
##             main     #158      +/-   ##
==========================================
- Coverage   83.19%   82.79%   -0.41%
==========================================
  Files          89       89
  Lines        5319     5369      +50
  Branches      892      881      -11
==========================================
+ Hits         4425     4445      +20
- Misses        733      763      +30
  Partials      161      161

Impacted Files
Coverage Δ

orchestrator/services/processes.py
83.33% <57.40%> (-6.93%)
:arrow_down:

orchestrator/websocket/__init__.py
77.61% <61.53%> (-3.04%)
:arrow_down:

orchestrator/api/api_v1/endpoints/processes.py
72.53% <100.00%> (+0.58%)
:arrow_up:

orchestrator/app.py
79.72% <100.00%> (+0.56%)
:arrow_up:

orchestrator/types.py
96.49% <100.00%> (-0.84%)
:arrow_down:

...tor/websocket/managers/memory_websocket_manager.py
54.34% <0.00%> (-0.98%)
:arrow_down:

orchestrator/cli/scheduler.py
69.69% <0.00%> (-0.90%)
:arrow_down:

orchestrator/domain/base.py
87.92% <0.00%> (-0.49%)
:arrow_down:

...rator/distlock/managers/memory_distlock_manager.py
82.60% <0.00%> (-0.38%)
:arrow_down:

... and 1 more

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4d70f9f...a715d58. Read the comment docs.


⚠ SceneTime has degraded performance

In b341079, SceneTime ($ST) experienced degraded performance:

HTTP code: 200
Response time: 17213 ms

Resolved: SceneTime performance has improved in dda1889 after 5 minutes.


Graphene 3 support?

Any plan to support Graphene 3?

+1

I would love to work on it but I don't see any contribution guide.


Solovay-Kitaev Sa

Environment

Qiskit Terra version: 0.23.1
Python version: python3.8
Operating system: Linux (Google Colab)

What is happening?
When factorizing the S gate with SolovayKitaev(), the output gives $T^2$ but not a single S gate. I know it's mathematically correct, but when I try to define the basis_gates to only include S gate but not T gate, the result is still $T^2$. Same goes the Sdg gate.
How can we reproduce the issue?

What should happen?
The expected output should be a single S or Sdg gate when the basis_gate set is defined to include them.
Any suggestions?
No response

You defined a basis set for transpile, but not for the subsequent pass of SolovayKitaev. It's therefore going to resynthesise into its default gate set, which is $H$, $T$ and $T^\dagger$, so the output you're seeing is expected.  You'd need to specify the basic_approximations argument to that if you want to use a different basis in the SK decomposition.

You defined a basis set for transpile, but not for the subsequent pass of SolovayKitaev. It's therefore going to resynthesise into its default gate set, which is H, T and T†, so the output you're seeing is expected. You'd need to specify the basic_approximations argument to that if you want to use a different basis in the SK decomposition.

Thank you! Just a follow-up question, there's an error when I try to add SdgGate to the basis gate, while it works fine for SGate. Any reason why SdgGate fails to be included as basis?

Off the top of my head, that feels like it might be a bug, but @Cryoris is much more familiar with the code than I am, so I'll pass it to him.

Yep, that's indeed a bug! See #9635 for a fix.


ng test Environment "undefined" does not exist.

Upgraded to Angular 5.1.2 today as well as to Angular CLI 1.6.3
When I try and run my tests I get the error: Environment "undefined" does not exist.
I can get it to work by providing -e dev, but didn't have to before.
Versions
Angular CLI: 1.6.3
Node: 8.9.1
OS: darwin x64
Angular: 5.1.2
... animations, common, compiler, compiler-cli, core, forms
... http, language-service, platform-browser
... platform-browser-dynamic, router

@angular/cdk: 5.0.2
@angular/cli: 1.6.3
@angular/material: 5.0.2
@angular-devkit/build-optimizer: 0.0.36
@angular-devkit/core: 0.0.22
@angular-devkit/schematics: 0.0.42
@ngtools/json-schema: 1.1.0
@ngtools/webpack: 1.9.3
@schematics/angular: 0.1.11
@schematics/schematics: 0.0.11
typescript: 2.4.2
webpack: 3.10.0

Repro steps
ng test
Observed behavior
Environment "undefined" does not exist.
If I run with ng test -e dev my tests run
Desired behavior
Should default to dev as it did previously.

Thanks for reporting this issue. This issue is now obsolete due to changes in the recent releases. Please update to the most recent Angular CLI version.
If the problem persists after upgrading, please open a new issue, provide a simple repository reproducing the problem, and describe the difference between the expected and current behavior.