Porting nimBLE to NuttX

I'm experimenting with porting nimBLE to NuttX. We're in the process of completing a Linux-like socket interface via BTPROTO_HCI and BTPROTO_L2CAP. There's already a host layer on NuttX but I would like to try nimBLE as it already supports Linux and it shouldn't be much harder to support.
I'm finding some issues that I wanted to mention, not sure if these are possibles areas of improvement of nimBLE or I'm simply not fully understanding how to do the port (I couldn't find any documentation).
For starters, I copied linux/ in npl/ and modified it to suit NuttX. As it is mostly Linux compatible, no big changes are needed.  However one issue I find is that NuttX requires an initial include in every .c and .h as: #include <nuttx/config.h> which holds the output of the Kconfig configuration system. For the OS specific files in npl/ I can add this include, but for the rest of the code I would have to manually insert it everywhere. I imagine one way would be to extend the porting layer to have a header which would be included everywhere in nimBLE where I could add this include (LVGL for example does it this way). This is not really a problem
Another issue I find is there there are some macros which are not defined anywhere in nimBLE repo. For now I found (but I think there are many others):

NIMBLE_CFG_CONTROLLER
OS_CFG_ALIGN_4
OS_CFG_ALIGNMENT
BLE_LL_CFG_FEAT_LL_PRIVACY
LOG_LEVEL_*

I'm sensing that there should be some configuration process for the port which defines these but it does not appear to be part of this repo (maybe done in mynewt repo?)
I also started by attempting to build the linux "test" applications but it failed due to ble_npl_eventq_run not being declared. Maybe this test is not maintained? If you don't think it is reasonable to spend time trying to build this test I can skip it. I was now moving on to trying to build the linux "example".
One final question: in Linux there's BTPROTO_L2CAP and on NuttX we're following the same path of exposing L2CAP over a socket. I see nimBLE only uses the HCI socket and solves L2CAP on its own. Is there any plan to make this optional and have BTPROTO_L2CAP sockets supported? This would not only better integrate nimble with NuttX but also Linux IMHO.
That's it so far. If you could give me some points on the porting process it would really be helpful.

I think I'm understanding that i need to generate a syscfg.h for my platform. I've found some information in other issues here on how to supposeddly do this. I've created a newt project, changed version to 0.0.0, ran newt upgrade and then placed my modified porting files for nuttx in the nimble subdirectory. However, running newt build @apache-mynewt-nimble/porting/targets/nuttx produces the following output:

* Warning: Parsing pkg @apache-mynewt-core/boot/split config: strconv.ParseInt: parsing "MYNEWT_VAL(SPLIT_APP_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/fs/fatfs config: strconv.ParseInt: parsing "MYNEWT_VAL(FATFS_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/fs/nffs config: strconv.ParseInt: parsing "MYNEWT_VAL(NFFS_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/battery config: strconv.ParseInt: parsing "MYNEWT_VAL(BATTERY_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/bsp/nordic_pca20020 config: strconv.ParseInt: parsing "MYNEWT_VAL(NORDIC_PCA20020_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/bsp/ruuvitag_rev_b config: strconv.ParseInt: parsing "MYNEWT_VAL(RUUVITAG_REV_B_SYSINIT_STAGE_BME280)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/bsp/stm32f3discovery config: strconv.ParseInt: parsing "MYNEWT_VAL(STM32F3DISCOVERY_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/charge-control config: strconv.ParseInt: parsing "MYNEWT_VAL(CHARGE_CONTROL_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/drivers/bq27z561 config: strconv.ParseInt: parsing "MYNEWT_VAL(BQ27Z561_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/drivers/ipc_nrf5340 config: strconv.ParseInt: parsing "MYNEWT_VAL(IPC_NRF5340_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/drivers/lwip/stm32_eth config: strconv.ParseInt: parsing "MYNEWT_VAL(STM32_ETH_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/drivers/pwm/soft_pwm config: strconv.ParseInt: parsing "MYNEWT_VAL(SOFT_PWM_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/drivers/uart/uart_bitbang config: strconv.ParseInt: parsing "MYNEWT_VAL(UARTBB_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/mcu/dialog/da1469x/hosttest config: strconv.ParseInt: parsing "MYNEWT_VAL(DA1469x_HOSTTEST_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/sensor/creator config: strconv.ParseInt: parsing "MYNEWT_VAL(SENSOR_CREATOR_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/sensor config: strconv.ParseInt: parsing "MYNEWT_VAL(SENSOR_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/usb/tinyusb/cdc_console config: strconv.ParseInt: parsing "MYNEWT_VAL(CONSOLE_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/hw/usb/tinyusb config: strconv.ParseInt: parsing "MYNEWT_VAL(USBD_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/kernel/os config: strconv.ParseInt: parsing "MYNEWT_VAL(OS_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/mgmt/imgmgr config: strconv.ParseInt: parsing "MYNEWT_VAL(IMGMGR_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/mgmt/oicmgr config: strconv.ParseInt: parsing "MYNEWT_VAL(OICMGR_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/mgmt/smp/transport/ble config: strconv.ParseInt: parsing "MYNEWT_VAL(SMP_BLE_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/mgmt/smp/transport/smp_shell config: strconv.ParseInt: parsing "MYNEWT_VAL(SMP_SHELL_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/mgmt/smp/transport/smp_uart config: strconv.ParseInt: parsing "MYNEWT_VAL(SMP_UART_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/mgmt/smp config: strconv.ParseInt: parsing "MYNEWT_VAL(SMP_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/net/ip/lwip_mn config: strconv.ParseInt: parsing "MYNEWT_VAL(IP_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/net/ip/native_sockets config: strconv.ParseInt: parsing "MYNEWT_VAL(NATIVE_SOCKETS_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/net/lora/node config: strconv.ParseInt: parsing "MYNEWT_VAL(LORA_NODE_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/net/oic config: strconv.ParseInt: parsing "MYNEWT_VAL(OC_SYSINIT_STAGE_TCP4)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/config config: strconv.ParseInt: parsing "MYNEWT_VAL(CONFIG_SYSINIT_STAGE_2)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/console/full/history_log config: strconv.ParseInt: parsing "MYNEWT_VAL(CONSOLE_HISTORY_LOG_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/console/full/history_ram config: strconv.ParseInt: parsing "MYNEWT_VAL(CONSOLE_HISTORY_RAM_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/console/full config: strconv.ParseInt: parsing "MYNEWT_VAL(CONSOLE_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/console/minimal config: strconv.ParseInt: parsing "MYNEWT_VAL(CONSOLE_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/fault/fault_cli config: strconv.ParseInt: parsing "MYNEWT_VAL(FAULT_CLI_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/fault config: strconv.ParseInt: parsing "MYNEWT_VAL(FAULT_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/flash_map config: strconv.ParseInt: parsing "MYNEWT_VAL(FLASH_MAP_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/id config: strconv.ParseInt: parsing "MYNEWT_VAL(ID_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/log/full config: strconv.ParseInt: parsing "MYNEWT_VAL(LOG_SYSINIT_STAGE_MAIN)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/log/modlog config: strconv.ParseInt: parsing "MYNEWT_VAL(MODLOG_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/metrics config: strconv.ParseInt: parsing "MYNEWT_VAL(METRICS_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/mfg config: strconv.ParseInt: parsing "MYNEWT_VAL(MFG_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/reboot config: strconv.ParseInt: parsing "MYNEWT_VAL(REBOOT_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/shell config: strconv.ParseInt: parsing "MYNEWT_VAL(SHELL_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/stats/full config: strconv.ParseInt: parsing "MYNEWT_VAL(STATS_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/sys/sysview config: strconv.ParseInt: parsing "MYNEWT_VAL(SYSVIEW_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/test/crash_test config: strconv.ParseInt: parsing "MYNEWT_VAL(CRASH_TEST_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/test/flash_test config: strconv.ParseInt: parsing "MYNEWT_VAL(FLASH_TEST_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/test/i2c_scan config: strconv.ParseInt: parsing "MYNEWT_VAL(I2C_SCAN_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/test/runtest config: strconv.ParseInt: parsing "MYNEWT_VAL(RUNTEST_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/test/testutil config: strconv.ParseInt: parsing "MYNEWT_VAL(TESTUTIL_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/time/timepersist config: strconv.ParseInt: parsing "MYNEWT_VAL(TIMEPERSIST_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-core/time/timesched config: strconv.ParseInt: parsing "MYNEWT_VAL(TIMESCHED_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/controller config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_LL_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/host/mesh config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_MESH_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/host/services/ans config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_SVC_ANS_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/host/services/bas config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_SVC_BAS_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/host/services/bleuart config: strconv.ParseInt: parsing "MYNEWT_VAL(BLEUART_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/host/services/dis config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_SVC_DIS_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/host/services/gap config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_SVC_GAP_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/host/services/gatt config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_SVC_GATT_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/host/services/ias config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_SVC_IAS_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/host/services/ipss config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_SVC_IPSS_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/host/services/lls config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_SVC_LLS_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/host/services/tps config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_SVC_TPS_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/host/store/config config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_STORE_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/host/store/ram config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_STORE_RAM_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/host config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_HS_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/transport/emspi config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_HCI_EMSPI_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/transport/ram config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_TRANS_RAM_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/transport/socket config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_SOCK_CLI_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/transport/uart config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_TRANS_UART_SYSINIT_STAGE)": invalid syntax; ignoring package.
* Warning: Parsing pkg @apache-mynewt-nimble/nimble/transport/usb config: strconv.ParseInt: parsing "MYNEWT_VAL(BLE_TRANS_USB_SYSINIT_STAGE)": invalid syntax; ignoring package.
Building target @apache-mynewt-nimble/porting/targets/nuttx
Error: Could not resolve package dependency: @apache-mynewt-core/kernel/os; depender: porting/targets/nuttx

Is it really necessary to go through this process to generate the syscfg.h? Or is there an easier way?

@v01d I am not sure if there is a better way to generate a syscfg.h file.  The method you are using seems good to me.
Those warning messages look like your version of newt is old.  Which version are you using?  You can get the latest here: http://mynewt.apache.org/download/

Thanks, yes, I've found some email in mailing list archive with similar error and it was suggested to use newt from master. This problem disappeared then. However, I'm struggling now with some undefined macros again. It seems that building nimble also tries to build mynewt OS which I would guess it is not necessary to generate the syscfg.h for a different OS:

gcc -DAPP_NAME=dummy_app -DAPP_dummy_app -DARCH_NAME=dummy -DARCH_dummy -DBSP_NAME=dummy_bsp -DBSP_dummy_bsp -DMN_LINUX -DMYNEWT=1 -O0 -Wall -Werror -fdata-sections -ffunction-sections -fno-common -ggdb -m32 -Ibin/@apache-mynewt-nimble/porting/targets/nuttx/generated/include -Ibin/porting/targets/nuttx/user/pre_build/include -Irepos/apache-mynewt-core/crypto/tinycrypt/include -Irepos/apache-mynewt-core/crypto/tinycrypt/include/tinycrypt/arch/dummy -Irepos/apache-mynewt-core/hw/hal/include -Irepos/apache-mynewt-core/hw/hal/include/hal/arch/dummy -Irepos/apache-mynewt-core/kernel/os/include -Irepos/apache-mynewt-core/kernel/os/include/os/arch/dummy -Irepos/apache-mynewt-core/kernel/os/src -Irepos/apache-mynewt-core/kernel/os/src/arch/dummy -Irepos/apache-mynewt-core/sys/console/stub/include -Irepos/apache-mynewt-core/sys/console/stub/include/stub/arch/dummy -Irepos/apache-mynewt-core/sys/defs/include -Irepos/apache-mynewt-core/sys/defs/include/defs/arch/dummy -Irepos/apache-mynewt-core/sys/flash_map/include -Irepos/apache-mynewt-core/sys/flash_map/include/flash_map/arch/dummy -Irepos/apache-mynewt-core/sys/log/common/include -Irepos/apache-mynewt-core/sys/log/common/include/common/arch/dummy -Irepos/apache-mynewt-core/sys/log/modlog/include -Irepos/apache-mynewt-core/sys/log/modlog/include/modlog/arch/dummy -Irepos/apache-mynewt-core/sys/log/stub/include -Irepos/apache-mynewt-core/sys/log/stub/include/stub/arch/dummy -Irepos/apache-mynewt-core/sys/mfg/include -Irepos/apache-mynewt-core/sys/mfg/include/mfg/arch/dummy -Irepos/apache-mynewt-core/sys/stats/stub/include -Irepos/apache-mynewt-core/sys/stats/stub/include/stub/arch/dummy -Irepos/apache-mynewt-core/sys/sys/include -Irepos/apache-mynewt-core/sys/sys/include/sys/arch/dummy -Irepos/apache-mynewt-core/sys/sysdown/include -Irepos/apache-mynewt-core/sys/sysdown/include/sysdown/arch/dummy -Irepos/apache-mynewt-core/sys/sysinit/include -Irepos/apache-mynewt-core/sys/sysinit/include/sysinit/arch/dummy -Irepos/apache-mynewt-core/util/mem/include -Irepos/apache-mynewt-core/util/mem/include/mem/arch/dummy -Irepos/apache-mynewt-core/util/rwlock/include -Irepos/apache-mynewt-core/util/rwlock/include/rwlock/arch/dummy -Irepos/apache-mynewt-nimble/nimble/host/include -Irepos/apache-mynewt-nimble/nimble/host/include/host/arch/dummy -Irepos/apache-mynewt-nimble/nimble/host/services/gap/include -Irepos/apache-mynewt-nimble/nimble/host/services/gap/include/gap/arch/dummy -Irepos/apache-mynewt-nimble/nimble/host/services/gatt/include -Irepos/apache-mynewt-nimble/nimble/host/services/gatt/include/gatt/arch/dummy -Irepos/apache-mynewt-nimble/nimble/include -Irepos/apache-mynewt-nimble/nimble/include/nimble/arch/dummy -Irepos/apache-mynewt-nimble/nimble/transport/socket/include -Irepos/apache-mynewt-nimble/nimble/transport/socket/include/socket/arch/dummy -Irepos/apache-mynewt-nimble/porting/npl/mynewt/include -Irepos/apache-mynewt-nimble/porting/npl/mynewt/include/mynewt/arch/dummy -Irepos/apache-mynewt-nimble/porting/targets/dummy_app/include -Irepos/apache-mynewt-nimble/porting/targets/dummy_app/include/dummy_app/arch/dummy -Irepos/apache-mynewt-nimble/porting/targets/dummy_app/src -Irepos/apache-mynewt-nimble/porting/targets/dummy_app/src/arch/dummy -Irepos/apache-mynewt-nimble/porting/targets/dummy_bsp/include -Irepos/apache-mynewt-nimble/porting/targets/dummy_bsp/include/dummy_bsp/arch/dummy -Irepos/apache-mynewt-nimble/porting/targets/dummy_bsp/src -Irepos/apache-mynewt-nimble/porting/targets/dummy_bsp/src/arch/dummy -Irepos/apache-mynewt-nimble/porting/targets/nuttx/include -Irepos/apache-mynewt-nimble/porting/targets/nuttx/include/nuttx/arch/dummy -Irepos/apache-mynewt-nimble/porting/targets/nuttx/src -Irepos/apache-mynewt-nimble/porting/targets/nuttx/src/arch/dummy -MM -MG repos/apache-mynewt-core/kernel/os/src/os.c
Error: In file included from repos/apache-mynewt-core/kernel/os/include/os/os.h:131,
                 from repos/apache-mynewt-core/kernel/os/include/os/mynewt.h:27,
                 from repos/apache-mynewt-core/crypto/tinycrypt/src/mynewt.c:20:
repos/apache-mynewt-core/kernel/os/include/os/os_mempool.h:165:2: error: #error "Unhandled `OS_ALIGNMENT` for `os_membuf_t`"
  165 | #error "Unhandled `OS_ALIGNMENT` for `os_membuf_t`"
      |  ^~~~~

I have my nimble_npl_os.h defining #define BLE_NPL_OS_ALIGNMENT    4 which I think should work but it seems that it is not trying to use the nuttx porting headers here. In fact I see an os_mempool.h in both mynewt and the porting layer. How can I skip building the OS and just use the porting layer to generate syscfg?

If the build got that far, the syscfg.h file should be generated.
<EMAIL_ADDRESS>

Ah, you're right. I see it there. Ok, I will continue then to build nimBLE from within NuttX using this syscfg.h.

However one issue I find is that NuttX requires an initial include in every .c and .h as: #include <nuttx/config.h> which holds the output of the Kconfig configuration system. For the OS specific files in npl/ I can add this include, but for the rest of the code I would have to manually insert it everywhere. I imagine one way would be to extend the porting layer to have a header which would be included everywhere in nimBLE where I could add this include (LVGL for example does it this way).

Do you have any thoughts on how this could be addressed?

I'm hitting an issue where some controller-related macros are not defined (not that I'm not using controller), even after adding them to syscfg.yml. For example, BLE_CONTROLLER, which gives this warning: /home/v01d/coding/nuttx_nrf_ble/apps/external/nimble/mynewt-nimble/nimble/transport/socket/src/ble_hci_socket.c:793:5: warning: "MYNEWT" is not defined, evaluates to 0 [-Wundef]. It builds anyway but it doesn't seem to be the right way to do it this way.
Also, note that I tried building @apache-mynewt-nimble/porting/targets/linux target and I get the same error as before for nuttx target so I'm guessing I'm hitting some issues present in that port as well.

However one issue I find is that NuttX requires an initial include in every .c and .h as: #include <nuttx/config.h> which holds the output of the Kconfig configuration system. For the OS specific files in npl/ I can add this include, but for the rest of the code I would have to manually insert it everywhere. I imagine one way would be to extend the porting layer to have a header which would be included everywhere in nimBLE where I could add this include (LVGL for example does it this way).

Do you have any thoughts on how this could be addressed?

Nevermind about this, I realized it is not a problem.
Where I'm really stuck is with the undefined macros. Another problem is that some macros clash with NuttX's. Not sure how we could deal with those. The relevant errors are here: https://gist.github.com/v01d/342b63aee0f7a94a344f16de12a4defd#file-output-L1162
If we were to fix these I think we would be already in good place to have it working with NuttX (the rest of the changes we need to make on our side, getting the socket interface up to shape).

MYNEWY_VAL macros are not defined because relevant syscfg settings are only defined when NimBLE Controller package is included in build. if you'd like to fix those warnings properly, some files would need extra ifdefs to skip declarations that are only used by controller, but I don't know if this will be possible for all warnings (did not check all of them tbh). another option is just to build NimBLE without -Wundef as we do in Mynewt :)
as for LOG_LEVEL_* warning, seems like log headers we have in NimBLE are a bit out of sync with mynewt-core, i.e. required definitions are in log_common/log_common.h file and it's included from log/log.h. copies in mynewt-nimble are missing this include so feel free to sync those headers with latest mynewt-core version (we unfortunately had to include copies of some files from mynewt-core to make build possible without that repo; long term solution would be to have more abstraction in NimBLE so it does not use Mynewt structures directly, but it requires quite a lot of work)

Thanks for your response

MYNEWY_VAL macros are not defined because relevant syscfg settings are only defined when NimBLE Controller package is included in build. if you'd like to fix those warnings properly, some files would need extra ifdefs to skip declarations that are only used by controller, but I don't know if this will be possible for all warnings (did not check all of them tbh). another option is just to build NimBLE without -Wundef as we do in Mynewt :)

I could look into contributing some of this to nimBLE eventually. I will just ignore the undefined macros for now.

as for LOG_LEVEL_* warning, seems like log headers we have in NimBLE are a bit out of sync with mynewt-core, i.e. required definitions are in log_common/log_common.h file and it's included from log/log.h. copies in mynewt-nimble are missing this include so feel free to sync those headers with latest mynewt-core version (we unfortunately had to include copies of some files from mynewt-core to make build possible without that repo; long term solution would be to have more abstraction in NimBLE so it does not use Mynewt structures directly, but it requires quite a lot of work)

I understand. Keeping nimBLE standalone is a good choice.
I copied the log_common.h file and removed an include which pointed to an OS file. I also added an include to log_common.h from modlog.h. With this, all LOG_LEVEL_* warnings disappeared =D
There one final problematic issue: LOG_* (such as LOG_DEBUG, etc) clash with those used in NuttX (see error here https://gist.github.com/v01d/342b63aee0f7a94a344f16de12a4defd#file-output-L1190). Since NuttX is POSIX compatible, these are clashing to standard definitions required for syslog() function (you can see these defined in man syslog). Maybe there's a way to add some prefix to these variables so that nimBLE can be built under a POSIX setting safely?

Mmm, actually I just commented this definitions out in log.h so I guess they are not needed. Is that correct?

They are probably not needed since they were just copied as-is from mynewt-core to make sure everything builds. However, I'd prefer not to make any modifications in those copied files so we can just update them with most recent copy from mynewy-core if needed without need to worry about some changes.
What you can do is to create simple headers with only the required stubs or macros for logging, have them in NuttX porting directory and set includes path to make sure they are used instead of our copied. This way you don't need to worry about contents of our log.h and related files.

I understand. The problem is that modlog.h (another file under porting/nimble/include) does #include "log/log.h" so I cannot override it with include flags. modlog.h in turn is included from host/include/host headers.

But modlog.h is also inside host/include and also uses " to include so I cannot override it. You can see the include path here:
In file included from /home/v01d/coding/nuttx_nrf_ble/apps/external/nimble/mynewt-nimble/porting/nimble/include/modlog/modlog.h:26,
                 from /home/v01d/coding/nuttx_nrf_ble/apps/external/nimble/mynewt-nimble/nimble/host/include/host/ble_hs_log.h:23,
                 from /home/v01d/coding/nuttx_nrf_ble/apps/external/nimble/mynewt-nimble/nimble/host/include/host/ble_hs.h:38,
                 from /home/v01d/coding/nuttx_nrf_ble/apps/external/nimble/mynewt-nimble/porting/examples/nuttx/ble.c:25:
/home/v01d/coding/nuttx_nrf_ble/apps/external/nimble/mynewt-nimble/porting/nimble/include/log/log.h:34: warning: "LOG_DEBUG" redefined

Perhaps I am missing something here, but if you add e.g. porting/nuttx/include/modlog/modlog.h with stubs only and add porting/nuttx/include to include search path before porting/nimble/include, then your file should be always used instead of ours.

I just tried that and it doesn't work. You cannot override include search paths for #include directives using " instead of </>. If it were included as #include <modlog/modlog.h> you can indeed override it. I just tried changing that and that indeed works. But this would require modifying files under nimble/host/include/host. Maybe it is not a bad change to introduce as I suspect it will simplify this whole process of header copies.

ok, makes sense :) so you can just go ahead and change "" to <> in nimble if this solves your problem, we're fine with such change

Cool! I'm hoping I can merge the required change on NuttX side and then I can open a PR here so we can discuss the changes on nimBLE side.

Hi, you can find the PR here: #878

NuttX port is already merged


[PFS-230] Initial fileset service protos

This PR contains the initial protos for the new fileset service described here: https://www.notion.so/2024-02-09-Filesets-gRPC-Service-10f40b1eec9a4af8b48100aadb710fc9

Also need "bazel run //:buildifier"; the list of deps for the all_protos target should be sorted and that tool will do it for you.


WIP: Refresh the "Tested up to" values

This PR updates the "Tested up to" values within the plugin:

WordPress: 5.5 => 5.7
WooCommerce: 4.5 => 5.1

Fixes #60. Additionally, it bumps the versions being tested in the CI pipeline, including @szepeviktor's Travis cleanup work, so this PR closes #57.

@stevegrunwell dealerdirect/phpcodesniffer-composer-installer should be bumped to ^0.7

Basically a composer outdated --direct is necessary.

@szepeviktor Yup, working on that now, along with getting all the tests running locally before pushing. Thanks again for always keeping us honest in our coding practices! 😄

WooCommerce 3.9.3 can be installed only with Composer v1.

I'd like to make CI condition-free.
What do you think?

WooCommerce 3.9.3 can be installed only with Composer v1.
I'd like to make CI condition-free.
What do you think?

What's the oldest version that supports Composer v2?

Honestly, I'm not too concerned about dropping super-old versions of WooCommerce, especially given that 3.9 came out over a year ago (Jan 2020), but support as far back as we can go without it being a huge burden to test.

What's the oldest version that supports Composer v2?

WC 4.4.0

If limit-orders support WC v3.9 it can be easily tested in CI.

We're losing @stevegrunwell to vacation for a week, but we'll get it updated to be no older than 4.4 when he gets back.

Closing this PR against #70.


Overlapping logic with hdf writers

There is a lot of overlapping logic with hdf_writer.py :
https://github.com/bluesky/ophyd-async/blob/0269697acd9de1ff645fdc40aaf7937c6f346bd4/src/ophyd_async/epics/areadetector/writers/hdf_writer.py#L81-L112
and also with panda _hdf_writer.py : https://github.com/bluesky/ophyd-async/blob/0269697acd9de1ff645fdc40aaf7937c6f346bd4/src/ophyd_async/panda/writers/_hdf_writer.py#L69-L79
From a DRY point of view, we can reduce this repeating logic
Originally posted by @subinsaji in https://github.com/bluesky/ophyd-async/issues/436#issuecomment-2225834857

Fixed in #182


Use external_uri in proxy: true mode

We'd like to configure an external_uri that is used for the Karma UI, but only for the clickable hyperlinks. The use case is the following:

we run Karma with proxy mode to Alertmanager
we create a silence from the Karma UI
Karma shows a hyperlink to the silence in Alertmanager...
...but this is the internal (proxied) URL, not reachable from the browser

So then, we enable external_uri, but:

this makes Karma go through this for all requests
this URL to Alertmanager depends on our Ingress stack, making Karma more fragile
it is not compatible for the proxy: true mode, and Karma refuses to start

Questions:

could Karma discover and honor Alertmanager's --web.external-url flag?
could Karma have a dual mode where external_uri is considered only for hyperlinks?
would a new option, maybe external_link_uri, be clearer?

Thanks!

I looked into discoverability on the Alertmanager, and ended up opening this issue: https://github.com/prometheus/alertmanager/issues/2064

RIght, so let's recap, we have those use cases:

backend will read all silences
UI can write silences (create/edit/expire)
UI can display clickable links pointing at the silence in alertmanager web UI

Then we have:

backend always uses alertmanager.uri
UI write:
a. proxy: false - use alertmanager.uri
b. proxy: true - use karma internal API to talk to the backend, then backend talks to alertmanager.uri
c. external_uri - use that value when set, regardless of proxy setting
UI links: not totally sure how this is generated at the moment to be honest

I need to look into this, config file is getting messy and could use some restrcuturing. Proxy/non-proxy mode and external_uri adds to the complexity of deciding what to use where and I need to clean this up a little. Maybe a diagram would be useful.
It could potentially be simplified if proxy was always used for silence management, possibly with a new option to turn read-only mode per instance (so editing silences is not allowed).
I'll look into links and try to clean this up. Thanks!

Raised #1026 that refactors how all those settings interact with each other.
Added more docs on that under the Alertmanagers section
It should solve your problem while retaining of behaviour of the original request for external_uri - #899

Are you able to test lmierzwa/karma:latest docker image and verify if it now works as you expected?
You should be able to set both proxy mode and external_uri, in that setup silence management requests (create/edit/delete silences via the UI) would use proxy but links should use external_uri.

Wow, that was unbelievably fast! I'll give it a spin and chime back. Thanks again!


Bundling preact causes duplicate versions to be packaged in user bundles

Describe the Bug
My build started failing when I started using @bpmn-io/properties-panel. The error is:
ERROR in preact
  Multiple versions of preact found:
    10.5.13 ./~/@bpmn-io/properties-panel/preact from ./~/bpmn-js-properties-panel/dist/index.esm.js
    10.7.1 ./~/preact from<EMAIL_ADDRESS>
That is, because @bpmn-io/properties-panel bundles "manually" preact (not using package.json as a normal dependency), a Webpack plugin that I use (@cerner/duplicate-package-checker-webpack-plugin) for checking for duplicate packages complains about preact because it is now bundled twice.
Why was this change done? This is not the standard way of dealing with dependencies - and cause issues like mine.
Steps to Reproduce
Please see above for a description.
Expected Behavior
preact to be depended-on "normally" - via dependencies in package.json.
Environment

Host (Browser/Node version), if applicable: Browser
OS: Linux
Library version: 0.13.2

Hi,
thanks for creating this issue. We've decided to include preact inside the package to:

Resolve the issues pointed out in https://github.com/camunda/camunda-bpmn-js/issues/113
Not force user to maintain a properties-panel-specific version of preact (which would be the case if preact was a peer dependency.

We are however open to discussion. To resolve your issue for now, I'd suggest making sure that the duplicate checker ignores the preact package vendored in @bpmn-io/properties-panel

Thanks for the information!
I believe that ignoring the warning from the duplicate checker is not a very good solution because in that case my bundle will contain two copies of preact. Which is not ideal. I actually resolved it by adding preact: __dirname + '/node_modules/@bpmn-io/properties-panel/preact' in resolve.alias in my Webpack config which I believe is a better solution (although the preact version bundled in @bpmn-io/properties-panel is pretty old one but I guess it's better to use it rather than a newer one because @bpmn-io/properties-panel might not work with it I suppose?).

(although the preact version bundled in @bpmn-io/properties-panel is a pretty old one but I guess it's better to use it rather than a newer one because @bpmn-io/properties-panel might not work with it?).

@boris-petrov That is exactly the point. We bundle it, because it is part of our infrastructure, not something you ought to use / rely upon. If there is a way to exclude it from your duplicate checker, please investigate that.
If you rely on our (internally bundled) Preact you're depending on something that can change any time, without prior warning. Don't do that.

@nikku - I don't "rely" on the bundled preact but I point all other packages to depend on that version of preact. Otherwise I would get preact twice in my bundle which is not something I want. Do you see what I mean? I don't rely on any specific features of this preact version, I just have to tell webpack to use only ONE version (which I've chosen to be the one from bpmn.js).

@boris-petrov I can relate to you're case of "not wanting a library bundled twice".
Please consider "Preact being used in our tools" an implementation detail though. It could be replaced with inferno, snabdom, or plain JS any time. That is the whole point of us bundling it; you should not be aware, and you should not care. We shall work towards making that clear @barmac; let us chat about that.

Fair enough! When you've put it that way, it makes sense. Thanks for taking the time to explain!


[Lookout] Use orig_job_spec rather than job column for displaying the job yaml

Lookout uses the job.job database column to display the job yaml.  This is a binary json column, which is unfortunately slow to ingest.
To solve this, lookout ingester has started populating the job.orig_job_spec column which is the same data contains gzip compressed proto data stored in a postres bytea column,
We are now populating both columns, and have been for some time, so we can move over to the new column and delete the old one.  To do this we need to:
a) change lookout to take the job yaml from the orig_job_spec column.
b) change lookout ingester to no longer populate the old job column
c) change the lookout schema to drop the old job column.

Hey team! Please add your planning poker estimate with Zenhub @dejanzele @jayofdoom @kannon92 @richscott @suprjinx


TrustCenter links don't redirect to language specific urls

This issue is created by @nschonni from https://github.com/MicrosoftDocs/feedback/issues/409.
Describe the bug
Any links to https://www.microsoft.com/trustcenter/ and below without the language identifer en-us do not seem to work.
I realize this isn't a docs site page, but is linked to quite a bit from the docs, and is likely easier for you to address internally.
To Reproduce
Steps to reproduce the behavior:
Go to https://docs.microsoft.com/en-ca/azure/analysis-services/analysis-services-overview
Click on "Microsoft Trust Center"
The page loads https://www.microsoft.com/trustcenter/Security/AzureSecurity
Manually add en-us/ after microsoft.com/ to be forwarded to https://www.microsoft.com/en-us/trustcenter/security/azure-security
Expected behavior
Language detection to work
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
Add any other context about the problem here.

Document details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 04af7f54-ecc8-f44b-e6f4-f91a1076a881
Version Independent ID: cb4d74d4-383e-67b4-f603-c775a3fea61d
Content: Azure Analysis Services overview
Content Source: articles/analysis-services/analysis-services-overview.md
Service: azure-analysis-services
GitHub Login: @Minewiskan
Microsoft Alias: owend

@Powerhelmsman
Thanks for the feedback! We are currently investigating and will update you shortly.

Copy @nschonni. He is the user who provides the feedback.

@Minewiskan I have assigned the issue to the content author to evaluate and update as appropriate.

Resolved. Thanks for letting me know.
#please-close

@Powerhelmsman We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.

The redirection still isn't working https://www.microsoft.com/trustcenter/Security/AzureSecurity is still a 404

https://www.microsoft.com/en-us/trustcenter without the trailing slash redirescts
Any subpage or just https://www.microsoft.com/en-us/trustcenter/ with the trailing slash doesn't

@nschonni  the url to trust center is: https://www.microsoft.com/en-us/trustcenter

@nschonni @vasivara-MSFT
Please separate the URL issue from the link in article issue that was assigned to me (this one). I just chose to link to a different url, https://www.microsoft.com/trustcenter. The redirection issue is an interesting one. I spent an hour trying to figure it out. No luck, other than use https://www.microsoft.com/trustcenter.

@Powerhelmsman maybe this should get transferred back to the feedback repo till the owner for the site can be found.


Azure Pipelines support (Linux, macOS, and Windows)

Azure Pipelines configuration for building and testing create-react-app on Linux, Windows, and macOS.

Runs all test suites on Linux, macOS, and Windows on Node 8 and 10 (see recent results).

Uses a custom version of Verdaccio (for now) which enables us to set HTTP Agent options (request/agentOptions). This is necessary to work around an Azure VM specific issue caused when too many sockets are opened. See https://docs.microsoft.com/en-us/azure/app-service/app-service-web-nodejs-best-practices-and-troubleshoot-guide#my-node-application-is-making-excessive-outbound-calls

Fixes additional problems not specific to Azure Pipelines that are currently causing builds on Travis to fail:

Error involving different versions of Jest (24.5.0 vs. 24.6.0): The react-scripts package provided by Create React App requires a dependency: "jest": "24.5.0" ... However, a different version of jest was detected higher up in the tree: /home/travis/build/facebook/create-react-app/node_modules/jest (version: 24.6.0). Caused by a new version of Jest (24.6.0) in the last 24 hours and a mix of 24.5.0 and ^24.5.0 in the various package.json
Cannot find module '@babel/plugin-transform-react-jsx after ejection (see https://github.com/facebook/create-react-app/issues/6099)

I added a dummy azure-pipelines.yml back to master as the DevOps connection was broken without it.
I notice that in this PR there is a . prefix for the config file. DevOps seems to pick up the one without the prefix. Should we rename the files in your PR?

@ianschmitz - I renamed the YAML files. There's a way to get Azure Pipelines to use an alternate name, but probably not worth the hassle :)

At quick glance, most of the Azure Pipelines build failures are caused by the same problem discussed in item 3 above (a new minor release of jest and babel-jest). The error shows up like this:
The react-scripts package provided by Create React App requires a dependency:

  "babel-jest": "24.6.0"

Don't try to install it manually: your package manager does it automatically.
However, a different version of babel-jest was detected higher up in the tree:

  /home/vsts/work/_temp/tmp.AQLJ720ftV/test-app/node_modules/babel-jest (version: 24.7.0)

Although my PR "pinned" the various package.json files to "24.6.0", there must be something else producing/generating a "^24.6.0", which then causes a mix of 24.6.0 and 24.7.0 (and this error message).

The react-scripts package provided by Create React App requires a dependency:
"babel-jest": "24.6.0"
Don't try to install it manually: your package manager does it automatically.
However, a different version of babel-jest was detected higher up in the tree:
/home/vsts/work/_temp/tmp.AQLJ720ftV/test-app/node_modules/babel-jest (version: 24.7.0)

I quickly looked into this issue as it's blocking other PRs, and i suspect it's due to this dependency here: https://github.com/facebook/jest/blob/f3dab7cd92006540ecee5a0b8b6811608861bd52/packages/jest-config/package.json#L16. Since we pin the version of jest, when a new version of jest comes out, it pulls in jest-config through other transient dependencies, which pulls in the latest version of babel-jest. I've experienced this a number of times the last couple days as a couple jest versions came out in rapid succession while i was working on https://github.com/facebook/create-react-app/pull/6654. I would update our jest/babel-jest versions, and as soon as a new version of jest came out it triggered the preflight warning again in CI.
Here's an example of our dependencies in a fresh 3.0 alpha app:
<EMAIL_ADDRESS>/c/projects/test-app
└─┬<EMAIL_ADDRESS>  ├──<EMAIL_ADDRESS>  └─┬<EMAIL_ADDRESS>    └─┬<EMAIL_ADDRESS>      └─┬<EMAIL_ADDRESS>        └──<EMAIL_ADDRESS>deduped

I think perhaps the best solution here may be to use a carat version reference to babel-jest in our react-scripts package.json. This should then be deduped out of react-scripts into the root of node_modules in the project, which will get rid of the preflight warning. @SimenB does this sound like a good solution for CRA?

Yeah, I think so!

Not sure why you "lock" down your dependencies - unless you ship a lockfile as well it's not really doing anything as almost every single one of your dependencies are going to be using version rangers

Not sure why you "lock" down your dependencies

Yeah it's something we're going to review as a team after our 3.0 release is out the door. Thanks for all the help over the last few weeks!

@ianschmitz - btw, I previously experimented with softening the logic in https://github.com/ianschmitz/create-react-app/blob/master/packages/react-scripts/scripts/utils/verifyPackageTree.js#L77 --- basically changing the version comparison from a "string equals" to a "is this compatible". I didn't take this too far since I don't have a full understanding of the ramifications of having even slightly different versions of jest, babel-jest, etc, but maybe there are optimizations that can be made in this logic to solve this problem.

/cc @iansu @mrmckeb @Timer @amyrlam @petetnt @bugzpodder @heyimalex - sorry for the spam. Would be great to get your feedback on this.
We're aiming to get good coverage across all 3 platforms as we often get Windows specific issues reported for example.
The test suite reporting you may see above gets rolled up into one big green checkmark if all pass, so don't get too worried about the large number of build status reports there.

Thanks for the feedback. I'll fix the EOL in verdaccio.yaml.
Regarding the number of jobs ad build time ...
The times for the latest build (of master in my fork) look good: start to finish time is 19 minutes. This includes the 5 big test suites across Node 8 and 10 on Linux, macOS, and Windows (30 jobs) and the "old Node" test suite on Linux, macOS, and Windows (3 jobs).
It's your call, but if you don't really need to test on every combination of suite/Node/OS, I wouldn't. One benefit in your case is reducing the risk of an occasional Verdaccio or network problem causing a job [and therefore the entire build] to fail.
Let me know if you want to see any other changes ...

Some additional context to the Verdaccio issues on Windows build agents that @willsmythe provided me earlier:

think it’s related to this: https://docs.microsoft.com/en-us/azure/app-service/app-service-web-nodejs-best-practices-and-troubleshoot-guide#my-node-application-is-making-excessive-outbound-calls
This is a known issue, specific to Windows VMs on Azure.
I was able to get a create-react-app build working by patching Verdaccio with custom HTTP Agent options. Verdaccio uses “request”, so I am just hard-coding the options like this:
    const req = request(
      {
        url: uri,
        method: method
        headers: headers,
        body: json,
        ca: this.ca,
        proxy: this.proxy,
        encoding: null,
        gzip: true,
        timeout: this.timeout,
        strictSSL: this.strict_ssl,
+       agentOptions: {
+         keepAlive: true,
+         maxSockets: 40,
+         maxFreeSockets: 10
+       }

Once I have good confidence in this approach, we can discuss options. But, it’s looking like Verdaccio needs to open up the ability for options to be provided via configuration (which shouldn’t be a hard or controversial change).

@willsmythe assuming this fix makes it into Verdaccio proper, it sounds like you still anticipate the occasional network failures on the Windows agents. Is that correct? If so do you have any suggestions to improve this either on our side or within the Windows build agents?

@willsmythe assuming this fix makes it into Verdaccio proper, it sounds like you still anticipate the occasional network failures on the Windows agents. Is that correct? If so do you have any suggestions to improve this either on our side or within the Windows build agents?

I don't think I have seen any recent build failures related to network/connectivity, so I feel pretty good about the Verdaccio fixes. I have an uneasy feeling about Verdaccio in general (not just on Windows), but this mainly comes from seeing other reported issues with Verdaccio, especially under load.
Overall, I don't think there is a problem here. I do think our upcoming caching support will be useful in reducing the calls to Verdaccio and registry.npmjs.org (which is always a good thing to do).

This looks great. Good job everyone!
In terms of reducing the number of builds, we currently only run the behavior test suite on Mac. The old-node test suite really just needs to run on one platform (probably linux is the easiest) with Node 6. I think that eliminates ~8 builds.

I pushed a few changes to simplify the Azure Pipelines YAML. Mainly this will make it easier to add other common steps (like a step to publish test or coverage results) down the road.
This also [hopefully] fixes a random problem where yarn/npm would fail with an unexpected end of file (usually for react-script-forks .tgz). The root cause was a connectivity problem between the yarn/npm clients and the local Verdaccio HTTP server (so not an issue between Verdaccio and registry.npmjs.org). This issue is described here: https://github.com/verdaccio/verdaccio/issues/301. The workaround was setting keepAliveTimeout to 0 in the Verdaccio config. I also updated the maxage property to 30m to avoid Verdaccio going back to registry.npmjs.org for a package it already pulled down. I picked this timeout since it should generally cover the duration of the build.

Sounds good to me. I just pushed this change.

@willsmythe Sorry, I don't think I was clear about the behavior test suite. We run that test suite on Mac and all other platforms, but it's the only test suite we run on the Mac. All the others are Linux and Windows only.

Here's the latest build on my fork (with the updated configurations/jobs): https://dev.azure.com/willsmythe/create-react-app/_build/results?buildId=996

Hey @willsmythe. We just shipped 3.0 of CRA, so now we're able to focus on getting this in!
I just merged master in and it looks like all the builds are failing because of the git status check. I haven't had time to dig into it yet but will do tomorrow night if you haven't figured it out by that point.

Congrats on 3.0 :) I added a line to echo the current git diff so we can see what's changing.

Based on the breaking changes described in the Lerna 3.0 change log, I played around with replacing --skip-git with --no-push. May also need to do something with --no-commit-hooks.
I won't have much time over the next few days to dig much more into this (fyi).
Related to this, I also noticed a few deprecated warnings related to Lerna 3.0 ...
WARN deprecated --cd-version has been replaced by positional [bump]
WARN deprecated --skip-git has been replaced by --no-git-tag-version --no-push
WARN deprecated --npm-tag has been renamed --dist-tag

@ianschmitz - I figured out the issue with Lerna 3.x and Azure Pipelines. Long story short, the following change in Lerna 3.13.2 https://github.com/lerna/lerna/commit/a7ad9b6 caused a change in behavior related to publishing. It only showed up in Azure Pipelines because Azure Pipelines doesn't (by default) clone into a directory with the same name as the repo. This messed up Lerna's "has rooted" leaf logic (which is new/different in Lerna 3.13.2):
this.hasRootedLeaf = this.packageGraph.has(this.project.manifest.name);

this.project.manifest.name was s (the name of the directory Azure Pipelines cloned into). The fix was to override the default checkout/clone directory in the Azure Pipelines YAML:
  - checkout: self
    path: create-react-app

A better (more universal) fix would be to set this.project.manifest.name to "create-react-app", but I'm not sure what the impact of this would be (or where to do it).
This change should probably have been noted as a breaking changed in the Lerna changelog as well, fwiw.

Woohoo! Thanks @willsmythe.
I'm going to merge this in to my fork now. There were a couple things i wanted to clean up in the publish script that i'll do in another PR and tag you in. Once that's in we'll do a PR back into CRA proper.
I'll keep in touch while we finalize this.


failed (/lib/i386-linux-gnu/libc.so.6: version `glibc_2.34'

How to Fix it?
in Linux Debian

Upgrade your operating system to Ubuntu.

Okey i will try it thanks for Answer

I would appreciate if you let me know the result after trying it.

is there a maximal textdraw if using this?

I would appreciate if you let me know the result after trying it.
is there a limit textdraw if using this?

is there a limit textdraw if using this?

If you show 2048 global textdraws at the same time, there is, but none other than that.
The same is true for player textdraw. If you show 256 textdraws at the same time, you will be stuck at the limit, if you don't, you won't be stuck.

So is there still a limit in textdraw?

So is there still a limit in textdraw?

Yes, there is, but we can say that it does not exist because you will not display 256 or 2048 textdraws at the same time.
Let me give a simple example:
new Text:Global[5000];
for(new i = 0; i < 5000; i++)
{
    Global[i] = TextDrawCreate(320.0, 240.0, "TextDraw ID: %d", i);
}
TextDrawShowForPlayer(playerid, Global[4850]);

/*************************************************************************/

new PlayerText:pText[MAX_PLAYERS][5000];
for(new i = 0; i < 5000; i++)
{
    pText[playerid][i] = CreatePlayerTextDraw(playerid, 320.0, 240.0, "PlayerTextDraw ID: %d", i);
}
PlayerTextDrawShow(playerid, pText[playerid][4850]);

Normally it should tell you which ID it is. Can you tell me your code and what plugins you are using?

Normally it should tell you which ID it is. Can you tell me your code and what plugins you are using?

can i send video you through email or Discord?

Yes, Nexor#4730

Yes, Nexor#4730

Accept Friend My discord : Fraxy

Can you try this version? Also compiled with debian. It should probably work for debian as well.
https://github.com/nexquery/samp-textdraw-streamer/releases/tag/v2.0.0

Hi!
I am having the same problem, using Linux Ubuntu 20.04 X86 64 Minimal Latest V1 with the same error Failed (/lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by plugins/textdraw-streamer.so))

Hi! I am having the same problem, using Linux Ubuntu 20.04 X86 64 Minimal Latest V1 with the same error Failed (/lib/i386-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by plugins/textdraw-streamer.so))

Try this version: https://github.com/nexquery/samp-textdraw-streamer/releases/tag/v2.0.3-hotfix

Oi! Estou tendo o mesmo problema, usando Linux Ubuntu 20.04 X86 64 Minimal Latest V1 com o mesmo erro Failed (/lib/i386-linux-gnu/libc.so.6: versão 'GLIBC_2.34' não encontrada (exigido por plugins/textdraw-streamer.so))

Experimente esta versão: https://github.com/nexquery/samp-textdraw-streamer/releases/tag/v2.0.3-hotfix

Thank you very much, this served well here :)))


Remove the old assembly file

@jpkrohling could you please review and eventually merge?

Looks good to me. Once Travis approves, I'll merge it.


export portage db, oem sysext utils, sysext for azure

CI: http://jenkins.infra.kinvolk.io:8080/job/container/job/packages_all_arches/1905/cldsv
Portage database is put into the tarball and uploaded to bincache before it's dropped from the generic image. This is done in order to reinject it into the mounted generic image when building sysext images, so we have retained all the portage information and we don't need to strip RDEPENDS from the oem packages. That way they can become bog-standard ebuilds.
Adds some scripts for building oem sysexts and then ports azure to use them.
overlay app-emulation/wa-linux-agent: Start changing the ebuild to resemble a normal ebuild, without the OEM hacks. This replaces dependency on dev-lang/python-oem and dev-python/distro-oem with dev-lang/python and dev-python/distro, respectively.
overlay dev-lang/python-oem, dev-python/distro-oem: Drop the unnecessary packages.
overlay profiles, coreos-devel/board-packages: Drop things related to the dropped python packages. Maybe we should start pulling in dev-lang/python instead?
This PR replaces https://github.com/flatcar/scripts/pull/683 and https://github.com/flatcar/coreos-overlay/pull/2506.

[ ] Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)
[ ] Inspected CI output for image differences: /boot and /usr size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.

Needs https://github.com/flatcar/bootengine/pull/62 to be merged first.


Issue #622 is resolved here with a modification of additional-query

Change to additional query to accommodate test case with negative votes.

Superceded by #625


Add English Tutorial for LOJ-1080 Binary simulation

#67

Hello, great effort! :1st_place_medal:
I have some confusions in some of the parts. Let's discuss them.

Fact: as the input string is consist of only 0 and 1, and the type of update is only inverting the index, no matter how many inversions you make it will be same in each odd inversion count and vise versa, 1 will remain 1 after 1,3,5,.. inversions and will become 0 after 2,4,6,.. inversions, for example.

Shouldn't this be "1 will remain 1 after 2,4, 6.. inversions and will be 0 otherwise"?

In the image for query(I, 5, 5), shouldn't the node value for 2-4 be 0 instead of 1 since the update is only to the right subtree of 1-7?

You mentioned lazy propagation for invertRange, but I don't see any propagation in your code. Rather, you are calculating the sum of the values of ancestor nodes for a particular point modulo 2.

Shouldn't this be "1 will remain 1 after 2,4, 6.. inversions and will be 0 otherwise"?
reply:  Yes, you are right.

In the image for query(I, 5, 5), shouldn't the node value for 2-4 be 0 instead of 1 since the update is only to the right subtree of 1-7?
reply: those images got messed up with layers while exporting in iPad and my bad, I asked someone else to revise it as I was in a rush for my midterm exam.

You mentioned lazy propagation for invertRange, but I don't see any propagation in your code. Rather, you are calculating the sum of the values of ancestor nodes for a particular point modulo 2.

reply: In each invert range query, we are not updating the range instantly, rather we are keeping it in the waiting queue as long as we don't need any of its predecessors to make any operations and this logic comes from lazy propagation.
I will make another commit after fixing issues 1 and 2 and thanks for figuring it out.

@rebornplusplus I made an updated commit.

Your code gets WA I am afraid.
printf("%d\n", (query(1,1,len,x) ));

Ln 160, You're not calculating the summation modulo 2.
if(tl==l and tr==r){

Also, at Ln 89, shouldn't this be the following?
if(tl>=l and tr<=r){

Yeah, I should've calculated the modulo 2 value.
rest others will remain the same.

Merged.
Thank you for your contribution. Good work. :clap:


can not find scratch3 project

I got confused that I can not find the Scratch3 project, Could you help me? Many thanks!
gulp.task('scratch3install', ['crossdomain'], function() {
return gulp.src([
'public/scratch3/**',
'public/components/help/help-scratch3*',
'public/components/help/help-scratch.css'
]).pipe(gulp.dest('web/scratch3'));
});
I cant not find any public/scratch3/ file from git repository.

Scratch 3 lives at https://github.com/LLK


docs: note about router version

Thank you, I merged the two tips together to avoid having too much at the top of the docs.


Group add user not working

Hello,
used to use gam to add users into groups with no issues.
Wanted to use it again today finding that it no longer works...
I used to use:
gam csv file.csv gam update group groupname add member user ~EMAIL > log.txt
According to "new documentation" I tried to use:
gam update group<EMAIL_ADDRESS>add member file file.csv > log.txt
This is what I get:
gam.py:8739: UnicodeWarning: Unicode equal comparison failed to convert both arguments to Unicode - interpreting them as being unequal
Traceback (most recent call last):
File "", line 9103, in
File "", line 5951, in doUpdateGroup
File "", line 8741, in getUsersToModify
File "C:\Users\jlee\Documents\GitHub\gam363\src\build\gam\out00-PYZ.pyz\encodings.utf_8", line 16, in decode
UnicodeDecodeError: 'utf8' codec can't decode byte 0xa0 in position 0: invalid start byte
when I do gam user info, I do get correct response therefore no issue with json file...
Any response will be welcome
Thanks
Regards
Jan

This error generally is due to a invalid / corrupt CSV file. Closing issue but feel free to re-open if you can provide a sample CSV that produces the issue.


.NET 4.7 Performance Degrade

All of Our PCs are WIN7. I do not have WIN10 to test it.
Our desktop C# application (mainly scientific calculations):  performance degrades a lot in .NET 4.7 for the first iteration.
Later iterations work normally.
0.1 second for the first iteration in .NET 4.6/4.5/4.0
14 seconds for the first iteration in .NET 4.7
The 32 bit run in .NET 4.7 is OK.
The 64 bit run in debug version is OK.
The 64 bit run in release version without 'Optimize Code" check is OK.
It only happens when .NET 4.7 Release version with "Optimize Code" checked.
It happens in our application in multiple people and multiple PC.
It always happen in the same place when it tries to call a very normal function, but before the first instruction in the called function.
We have used VS Performance Profiling to see what is going on during the 14 seconds: it shows "No Call Tree Data Is Available."
The memory usage is very low for the application. So I do not think memory is an issue here.
I also tried to enforce memory garbage collection before the function.
The problem still stays the same.
Any ideas?

@brianrob any ideas what additional information can be gathered to help root cause?

Yes.  The first step here is to collect ETW traces of the good and bad cases.  The goal is to capture equivalent work in both cases so that we can compare the difference in resources used to accomplish the same amount of work in both cases.
It sounds like you can reproduce this on the same bitness (64-bit) with and without Optimized Code checked.  If you can use these as the two cases that would be good.
To collect the traces, I recommend using PerfView: https://www.microsoft.com/en-us/download/details.aspx?id=28567.
To collect, simply run "PerfView.exe collect", once it starts, run your scenario, and then click stop.  It will produce a file called PerfViewData.etl.zip.
Once you have the two cases - good and bad - just put them up somewhere that I can take a look, and I can help diagnose the issue.  You can also reach me directly at brianrob at microsoft dot com.

@peter---- is this still a problem? Please get back to us with some more info. Otherwise, we'll close the issue.

Hey @peter---- , are you still tracking this?

Hi,
The issue is resolved at the new 4.7 build.Thanks,Peter
  From: Rich Lander<EMAIL_ADDRESS>
To: Microsoft/dotnet<EMAIL_ADDRESS>Cc: peter----<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Sent: Tuesday, November 28, 2017 10:26 PM
Subject: Re: [Microsoft/dotnet] .NET 4.7 Performance Degrade (#492)
Hey @peter---- , are you still tracking this?—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.


Update ts0601_sensor.py

Add sensor variant to quirk.

Codecov Report
Base: 83.53% // Head: 83.53% // No change to project coverage :thumbsup:

Coverage data is based on head (2969b98) compared to base (954745e).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##              dev    #2013   +/-   ##
=======================================
  Coverage   83.53%   83.53%
=======================================
  Files         249      249
  Lines        8016     8016
=======================================
  Hits         6696     6696
  Misses       1320     1320

Impacted Files
Coverage Δ

zhaquirks/tuya/ts0601_sensor.py
100.00% <ø> (ø)

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

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

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.0%) to 83.533%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
6696

Relevant Lines:
8016

💛  - Coveralls


added myself in CONTRIBUTORS.md

@Hritikraj8804 be sure to mention the issue that your are solving in the PR. And you actually placed the  tag wrong. So be sure to check the output of the readme before you make a PR. I have resolved the merge. But keep in mind for the next issues


find adjacent node by edge

@gadial thanks for this, it looks like this is failing cargo fmt check. Can you either make the changes suggested here: https://travis-ci.com/mtreinish/retworkx/jobs/286041461#L289 or run cargo fmt to have cargo make these changes automatically.
Also if it's not too much trouble could you add a test for this it'd be good to have coverage for this method.

Coverage decreased (-1.5%) to 83.463% when pulling 376fcdf8e6356808947e16e6baa4d4e80b139938 on gadial:'find_adjacent_node_by_edge' into f26f0f05903071fc3013aafddbfcbf0937233ea6 on Qiskit:master.


Integrate Framer-motion to animate the website-landing in desktop view

Use Framer-Motion to animate the website landing page :)

Can you describe what type of animation you want , I mean fading and loading or pop-up from left etc.

Can you describe what type of animation you want , I mean fading and loading or pop-up from left etc.

Whatever suits the best or that looks good will work :) make sure you add video with the pr, the changes you made!

let me try to do animation .. if you want then assign me this issue ..  Thank you :)

complete previous issue before starting this 👍🏼 @mahenoorsalat

yeah I'm working on that only :) @pooranjoyb

@pooranjoyb can i work on this issue?

@mahenoorsalat Are you working on it?

I want to work on this issue , can you please assign me.

@mahenoorsalat Are you working on it?

Yeah I'm working on it @sristy17 👍


Don't support Chinese

I take this pdf file. http://www.zstack.io/docs/4.6.0/pdf-cn/PD4906 ZStack Cloud V4.6.0 常见问题解答（FAQ）.pdf
After ingest, I tried some queries. The answer is blank. But I can see correct response in the console log.
How to solve that?

Same problem here. What should I do if I have a file contains more than one language?  Should I change the QA_PROMPT to Chinese if I want to ask and answer all in Chinese? Thanks for answering the question.

I change the prompt to chinese and it works.

很赞！支持中文！

I change the prompt to chinese and it works.

很不错啊！

Just add 'You reply in Chinese' to the original description

@boogunote 兄弟，你在npm run ingest的时候没有网络错误吗？请教怎么搞的


Update aanalytics2.py

Updated call of get_jwt_token_and_expiry_for_config Initially named as -  get_token_and_expiry_for_config

Was getting the error - module 'aanalytics2.token_provider' has no attribute 'get_token_and_expiry_for_config'
Then realised function call name is updated and needs an update in aanalytics2.py file too.

Thanks for catching the miss when I migrate to support Oauth Server to Server

I will release the new version later today


feat(ClientCredentialsFlow): Add the clientcredentials Auth flow. The tokens look slightly different, but are still jwt valid.

:tada: This PR is included in version 3.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


New to using source code. How do I make this main menu idea?

Describe your problem here.
Me and my friend are making a mod and I decided to start trying to learn a bit of code for it and so far I've got something pretty good but I wanted to make it so that story mode is in the middle and the others aren't on screen so when you press up or down story mode will scroll up or down and the next option would come from the opposite side. I don't know how complex this is and honestly I don't even know where to begin so if anyone could help me with this I'd really appreciate it!
I attached some images to try to better describe what we want and what I've made so far.

and here is a concept I made for how I want it to work:

Are you modding a build from source or with Lua?
Source
What is your build target?
Windows x64
Did you edit anything in this build? If so, mention or summarize your changes.
Yes, I replaced the menu and game over music and have edited the menu as what you can see in the attached image as well as adding my own week, songs and characters.

change positions of buttons and move them with FlxTween

change positions of buttons and move them with FlxTween

how do I do that I still don't really understand most of this code

to do this menu concept go into the main menu state in the source code and change the order of the buttons, but first we need to remove the c

redits option (this is not required im just assuming that you need to) to do this just comment the line 40 in main menu state or delete it, now, to change the order of the buttons just look at this image that shows how the code should look

to do this menu concept go into the main menu state in the source code and change the order of the buttons, but first we need to remove the credits option (this is not required im just assuming that you need to) to do this just comment the line 40 in main menu state or delete it, now, to change the order of the buttons just look at this image that shows how the code should look

I'm sorry but I think you may not have understood what my problem is since the order isn't what I wanted to change... I updated the image with a gif to attempt to better explain what I'm trying to make, thank you anyway


tsdk: changing TS version from status bar does not update it in the status bar

Testing the new TS status bar:

have a workspace with NPM installed typescript@next
open the workspace
click on the status bar and change to TS 2.2.next
=> after doing so the status bar is still showing 2.1.5 being used.

I just ran into this new change, and after restarting VSCode the correct version is displayed in the Status Bar.
However, now that typescript.tsdk is no longer a workspace setting, where is this preference actually saved, and how would I share it with other machines/users, like we used to do with .vscode/settings.json?

Having looked at the commit log, I see that the setting is now stored in localStorage, but still leaves the issue that this setting is now un-shareable between computers and/or team members.
Can't the useWorkspaceVersion key be part of user/workspace settings, rather than localStorage?

@bpasero See also #19427

Yes, this new disabling of typescript.tsdk in the workspace settings.json is quite ~annoying~ surprising and just asking for trouble. How are we supposed to share the setting via the git repo without the annoying vscode popup asking what version to use? I think it's pretty clear that if we've gone to the trouble of setting a value in the workspace settings, that THAT is the one we want to use.

I think the item I just entered #19451 might be a partial semantic duplicate of this item.
The essence is: it will be most helpful for a great many of our use cases if the "use the version of TypeScript that this workspace uses" setting was either the default, or was sitting in the .vscode/settings file in the workspace. Sticking it over in invisible localstorage seems awful, I had a brief flashback to the Windows Registry era upon reading about it.

@kylecordes While related, I think your #19451 is worth keeping open on its own. The workspace-specific tsdk config regression needs to be addressed specifically IMHO.

Closing since the new flow changes how this works. You also need to reload after selecting a new TS version. By design, we continue to show the old version in the status bar because it remains active until reload.


[tool_crash] FileSystemException: Cannot open file, OS Error: No such file or directory, errno = 2

Command
flutter pub get

Steps to Reproduce

...
...
...

Logs
FileSystemException: Cannot open file, OS Error: No such file or directory, errno = 2
#0      _File.throwIfError (dart:io/file_impl.dart:635:7)
#1      _File.openSync (dart:io/file_impl.dart:479:5)
#2      _File.readAsBytesSync (dart:io/file_impl.dart:539:18)
#3      _File.readAsStringSync (dart:io/file_impl.dart:584:18)
#4      ForwardingFile.readAsStringSync (package:file/src/forwarding/forwarding_file.dart:96:16)
#5      ErrorHandlingFile.readAsStringSync.<anonymous closure> (package:flutter_tools/src/base/error_handling_io.dart:222:22)
#6      _runSync (package:flutter_tools/src/base/error_handling_io.dart:597:14)
#7      ErrorHandlingFile.readAsStringSync (package:flutter_tools/src/base/error_handling_io.dart:221:12)
#8      _DefaultPub.get (package:flutter_tools/src/dart/pub.dart:293:50)
<asynchronous suspension>
#9      PackagesGetCommand._runPubGet (package:flutter_tools/src/commands/packages.dart:139:7)
<asynchronous suspension>
#10     PackagesGetCommand.runCommand (package:flutter_tools/src/commands/packages.dart:174:5)
<asynchronous suspension>
#11     FlutterCommand.run.<anonymous closure> (package:flutter_tools/src/runner/flutter_command.dart:1209:27)
<asynchronous suspension>
#12     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#13     CommandRunner.runCommand (package:args/command_runner.dart:209:13)
<asynchronous suspension>
#14     FlutterCommandRunner.runCommand.<anonymous closure> (package:flutter_tools/src/runner/flutter_command_runner.dart:281:9)
<asynchronous suspension>
#15     AppContext.run.<anonymous closure> (package:flutter_tools/src/base/context.dart:150:19)
<asynchronous suspension>
#16     FlutterCommandRunner.runCommand (package:flutter_tools/src/runner/flutter_command_runner.dart:229:5)

[!] Flutter (Channel stable, 3.3.4, on macOS 13.0 22A380 darwin-arm, locale en-US)
    • Flutter version 3.3.4 on channel stable at /opt/homebrew/Caskroom/flutter/3.0.4/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision eb6d86ee27 (1), 1970-01-01 03:00:00.000
    • Engine revision 8f2221fbef
    • Dart version 2.18.2
    • DevTools version 2.15.0
    ✗ Downloaded executables cannot execute on host.
      See https://github.com/flutter/flutter/issues/6207 for more information

[!] Android toolchain - develop for Android devices (Android SDK version 33.0.0)
    • Android SDK at /Users/briangathua/Library/Android/sdk
    • Platform android-33, build-tools 33.0.0
    ✗ No Java Development Kit (JDK) found; You must have the environment variable JAVA_HOME set and the java binary in your PATH. You can download the JDK from https://www.oracle.com/technetwork/java/javase/downloads/.

[✗] Xcode - develop for iOS and macOS
    ✗ Xcode installation is incomplete; a full installation is necessary for iOS development.
      Download at: https://developer.apple.com/xcode/download/
      Or install Xcode via the App Store.
      Once installed, run:
        sudo xcode-select --switch /Applications/Xcode.app/Contents/Developer
        sudo xcodebuild -runFirstLaunch
    ✗ CocoaPods not installed.
        CocoaPods is used to retrieve the iOS and macOS platform side's plugin code that responds to your plugin usage on the Dart side.
        Without CocoaPods, plugins will not work on iOS or macOS.
        For more info, see https://flutter.dev/platform-plugins
      To install see https://guides.cocoapods.org/using/getting-started.html#installation for instructions.

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[!] Android Studio
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Unable to determine bundled Java version.
    • Try updating or re-installing Android Studio.

[!] Android Studio
    • Android Studio at 1/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    ✗ Android Studio not found at 1/Contents
    • Try updating or re-installing Android Studio.

[!] IntelliJ IDEA Community Edition (version unknown)
    ✗ Invalid IntelliJ version number.

[✓] VS Code (version 1.73.1)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.52.0

[☠] Connected device (the doctor check crashed)
    ✗ Due to an error, the doctor check did not complete. If the error message below is not helpful, please let us know about this issue at https://github.com/flutter/flutter/issues.
    ✗ Exception: Unable to run "adb", check your Android SDK installation and ANDROID_SDK_ROOT environment variable: /Users/briangathua/Library/Android/sdk/platform-tools/adb
    • #0      throwToolExit (package:flutter_tools/src/base/common.dart:10:3)
      #1      AndroidDevices.pollingGetDevices (package:flutter_tools/src/android/android_device_discovery.dart:75:7)
      <asynchronous suspension>
      #2      PollingDeviceDiscovery._populateDevices (package:flutter_tools/src/device.dart:435:54)
      <asynchronous suspension>
      #3      Future.wait.<anonymous closure> (dart:async/future.dart:522:21)
      <asynchronous suspension>
      #4      DeviceManager.getAllConnectedDevices (package:flutter_tools/src/device.dart:191:40)
      <asynchronous suspension>
      #5      DeviceValidator.validate (package:flutter_tools/src/doctor.dart:602:34)
      <asynchronous suspension>
      #6      Future.any.onValue (dart:async/future.dart:612:5)
      <asynchronous suspension>

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 7 categories.

Flutter Application Metadata
Type: malformed
Version: 1.0.0+1
Material: true
Android X: false
Module: false
Plugin: false
Android package: null
iOS bundle identifier: null
Creation channel: null
Creation framework version: null

Closing as duplicate of https://github.com/flutter/flutter/issues/91559


[AutoPR keyvault/data-plane] Add Certificate backup and restore to Key Vault Data Plane Ops

Created to sync https://github.com/Azure/azure-rest-api-specs/pull/2671

(message created by the CI based on PR content)

Codecov Report

Merging #2190 into restapi_auto_keyvault_preview will decrease coverage by 0.83%.
The diff coverage is 43.65%.

@@                        Coverage Diff                        @@
##           restapi_auto_keyvault_preview    #2190      +/-   ##
=================================================================
- Coverage                           52.9%   52.06%   -0.84%
=================================================================
  Files                               4798     5567     +769
  Lines                             120947   133508   +12561
=================================================================
+ Hits                               63982    69510    +5528
- Misses                             56965    63998    +7033

Impacted Files
Coverage Δ

azure-mgmt-dns/azure/mgmt/dns/models/ptr_record.py
66.66% <0%> (-13.34%)
:arrow_down:

azure-mgmt-dns/azure/mgmt/dns/models/caa_record.py
50% <0%> (-7.15%)
:arrow_down:

...ure-mgmt-dns/azure/mgmt/dns/models/cname_record.py
66.66% <0%> (-13.34%)
:arrow_down:

...re/mgmt/dns/models/record_set_update_parameters.py
66.66% <0%> (-13.34%)
:arrow_down:

azure-mgmt-dns/azure/mgmt/dns/models/txt_record.py
66.66% <0%> (-13.34%)
:arrow_down:

azure-mgmt-dns/azure/mgmt/dns/models/mx_record.py
57.14% <0%> (-9.53%)
:arrow_down:

...zure-mgmt-dns/azure/mgmt/dns/models/aaaa_record.py
66.66% <0%> (-13.34%)
:arrow_down:

...rk/azure/mgmt/network/network_management_client.py
31.77% <0%> (-2.97%)
:arrow_down:

azure-mgmt-dns/azure/mgmt/dns/models/srv_record.py
44.44% <0%> (-5.56%)
:arrow_down:

...on/azure/mgmt/authorization/operations/__init__.py
100% <100%> (ø)
:arrow_up:

... and 1148 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 b107c3c...3e40033. Read the comment docs.


Add match status

:tada: This PR is included in version 2.6.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Fix Tile Bleeding When Using Atlas Feature

Fixes #184 ! 🎉 ( I think )
This issue has plagued me in all the tile renderer's I've written over the last couple years, but I think this might finally fix it. :)
The strategy is to offset the UV sampling of the tilemap one half-pixel away from the edges of the tile so that it doesn't come close to sampling onto the next tile near the edges.
It seems to work great on my hardware, but it could be different for different hardware. Please try it out and see if it works!

Oh, wait, I messed something up. I've got to fix it.

Does anybody know if branching ( using an if statement ) is something to really try to avoid in fragment shaders? I've seen people mention it in random places before and I kind of got the feeling that it was something you want to avoid if possible.
I have a version that works without branching, but it's harder to read and I only got it to work if I handled clamping overflow in the positive x or y direction, and not in in the negative x or y direction.
Apparently for my hardware it only bleeds in the positive direction, but I'm not sure if it's like that for all hardware.
Anyway, if the if statements are a problem I can try more to fix them, but if they aren't then it's easier to read as is.

Does anybody know if branching ( using an if statement ) is something to really try to avoid in fragment shaders? I've seen people mention it in random places before and I kind of got the feeling that it was something you want to avoid if possible.
I have a version that works without branching, but it's harder to read and I only got it to work if I handled clamping overflow in the positive x or y direction, and not in in the negative x or y direction.
Apparently for my hardware it only bleeds in the positive direction, but I'm not sure if it's like that for all hardware.
Anyway, if the if statements are a problem I can try more to fix them, but if they aren't then it's easier to read as is.
And this branch should be ready and working again.

Branching should be avoided in some cases, but I'm not too worried about it here I think. 👍

Awesome! Would we be able to make a new release with the fix?
I'm wanting to release my crate which depends on it, but since I use the atlas feature I wanted to get this fixed before I did the release.

Awesome! Would we be able to make a new release with the fix?
I'm wanting to release my crate which depends on it, but since I use the atlas feature I wanted to get this fixed before I did the release.

I'm not planning on releasing until the rewrite is finished. I just moved this change over to the rewrite.

OK, no problem. :+1:


[jjo] merge #858 into release-1.6 branch

bors r+

bors r+

bors retry

dunno what state bors has reached, as tests are passing -- will file a new PR


Easy way to disable

When sharing nix modules between different systems, some that have an impermanence setup and others that don't, it would be useful to be able to easily enable/disable persistence without having to conditionally set it up. It would also be more consistent with other NixOS module.
Right now I am doing the following to disable:
{
  environment.persistence = lib.mkForce {};
}

But this feels more like a hack.

Hi! You should be able to use the enable option for this. It was undocumented, but I just added a bit about it in the README.


docs: update hexo-generator-serach link and lint

https://github.com/PaicHyperionDev/hexo-generator-search has redirected to https://github.com/wzpan/hexo-generator-search.
And when I save it, markdownlint modified some space between words and others.

Thanks for the contribution!


fixed a bug that caused chat text not to be translated

Is there a quick way to add keys to translation files? Because I did it all one by one

Fix conflicts :)


Cleartext Storage of Sensitive Information in Memory Warning

Please check all of the platforms you are having the issue on (if platform is not listed, it is not supported)

[x] iOS
[] Android
[] UWP
[] NET Standard 1.1

Version of OS(s) listed above with issue
iOS 10.3.3
Version of ACR UserDialogs Library
6.4.1
Expected Behaviour
Actual Behavior
Thank you very much for the great library! I am using Acr.UserDialogs 6.4.1 for our mobile product. We just did a static scan with Veracode and the analyze reported that in loginconfig.cs and credentials.cs (under acr.userdialogs.interface) there's were couple of "Cleartext Storage of Sensitive Information in Memory" flaws.
Code of Conduct

No Library Update Requests
No Timeline Requests
Please read through the documentation and FAQs
Please be respectful of my time. I put a lot of effort into my libraries.  I try to support the issue requests within a day.  I'm not psychic, so please take the time to fill out the above form as complete as possible

Don't use the function then??  It isn't something I plan to do anything as I only ever used it for prototyping once upon a time.


about feta3d_svr_test.py

Hello, thank you so much for sharing the code.
Regarding your code, I have a question to ask. If I need to use additional fetal brain data for reconstruction, do I need to modify feta3d_svr_test.py?

Hello @lx123-j
Yes, you'd need to modify the test script — what are the slice spacing and in-plane resolution of your data? You'd want to ensure the ratio between the two is around 4.

Thank you very much. Can I use only one 32032018 stack with a resolution of 5mm as test data?

5mm slice spacing.
I noticed in the test data, there's the phrase 'self.label_file = '%s_rec-%s_dseg_reg.nii.gz'. If I'm using my own dataset, do I need to provide the label_file?

First, you'd need to re-sample the in-plane resolution to 1.25mm so that the in-plane resolution to slice thickness ratio is 1:4.   The label file just needs to be a foreground mask (which can just be a simple mask of non-zero pixels, for example).

Thank you very much! I'll give it a try. Do I need to maintain the 1:4 slice spacing ratio? If I were to train a new model, would it also require a 1:4 ratio?

Ah, you can change all of these things of course if you're going to be retraining anyway. The ratio really depends on the eventual test cases you'd be working with. In my case, I was targeting mainly 0.8mm:3.0mm – 0.8mm:3.5mm acquisitions, so I chose 1:4 as the ratio.  At test time, I ensure the 1:4 ratio by re-sampling each slice. (For example, the 0.8mm resolution slices above would be resampled to 0.75mm so that 0.75mm:3.0mm = 1:4).

I see, thank you very much!

Hello, sorry to bother you. When my image input is transformed into 1.251.255, with a shape of 27226118, and it is input into the flow = torch.stack([flow[:, d - 2] * ((x.shape[d] - 1)/(flow.shape[d] - 1)) for d in range(2, x.ndim)], 1) line, the shape of the images will become 13240161, causing the last loop to have a 1 which results in an error, ZeroDivisionError: division by zero. Is it because there are too few slices, only 18?

The numbers above appear broken (shows as 1.251.255 and 27226118 for me) so I cannot know for sure the exact resolution and shape you are dealing with, but basically in the case of the 1:4 ratio, you'd need to replicate each slice four times before feeding the stack into the network.  Have you been able to run the test script?  You can step through it to see the kind of preprocessing you need to do for your own data.

Thank you very much for your response. My data has an in-plane resolution of 1.25 and a slice thickness of 5, with dimensions of 272, 261, 18. While running the test script, I observed that during the execution of the code segment flow = torch.stack([flow[:, d - 2] * ((x.shape[d] - 1)/(flow.shape[d] - 1)) for d in range(2, x.ndim)], 1), there is a ZeroDivisionError: division by zero error when looping to the fourth dimension because the last dimension is 18. In your response, you mentioned "you'd need to replicate each slice four times before feeding the stack into the network." Does this mean I need to convert the images to 272, 261, 72?

Yes, but there are other things like padding etc which will be required as well. So please refer to feta3d_svr_test.py and get your data in the same format.

ok, thank you very much!

Hello,
When I replicated the third dimension of my input image four times to become 72, the reconstruction results were still not satisfactory. What could be the reason for this? Do I need to retrain a model to test it?
Thank you.

Is the pre-trained model working on my data? If so, then you should work backwards to see why it doesn't work on your data.

Actually, if you can share a link to your data, I may be able to have a look into it, as it will be quicker that way.  I can't promise anything, though.

MR002962_1102.nii.gz
MR002962_1102_mask.nii.gz
I am able to achieve image reconstruction using the FETA2.2 data, so the issue might be related to my data processing. I would greatly appreciate it if you could take a look at my data to see if reconstruction is possible. I am using the following two Nifti files as test data:


[Bug Report]: No comment on PR after workflow run succeeds

Module path
gpt review
review-gpt CLI version
0.9.5
Describe the bug
Since there was a dependency issue #208  breaking the workflow, I created a copy of the action.yml file in my repository. I edited the file to add the install command as proposed by this solution on the same issue and use this as my workflow.
The workflow runs successfully, but no changes are seen on the PR. No comments or reviews are created.
To reproduce

Create a workflow in the existing repo
Add the following contents shown in code snippet

name: GPT Review on Pull Request

on:
  pull_request_target:
    branches: [ 'main' ]

jobs:
  add_pr_comment:
    runs-on: ubuntu-latest
    environment: <environment name>
    name: Azure OpenAI PR Comment
    steps:
        - uses: actions/checkout@v3
          with:
            ref: ${{ github.event.pull_request.head.sha }}
            fetch-depth: 2

        - name: Set up Python 3.11
          uses: actions/setup-python@v4
          with:
            python-version: 3.11

        - name: Install gpt-review with fixed dependencies
          shell: bash
          run: |
            sudo apt-get update
            python3 -m venv .env
            source .env/bin/activate
            python -m pip install --upgrade pip
            python -m pip install langchain==0.0.301
            python -m pip install pydantic==1.10.13
            python -m pip install gpt-review==v0.9.5

        - name: Populate azure.yaml from vars
          env:
            AZURE_YAML: ${{ vars.AZURE_YAML }}
          shell: bash
          run: |
            echo "$AZURE_YAML" > azure.yaml

        - name: Review PR and make comment
          shell: bash
          run: |
            source .env/bin/activate

            gpt github review \
              --access-token $GITHUB_TOKEN \
              --pull-request $PATCH_PR \
              --repository $PATCH_REPO
          env:
            ACTION_REF: ${{ github.action_ref || env.BRANCH }}
            GIT_COMMIT_HASH: ${{ github.event.pull_request.head.sha }}
            GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
            LINK: "https://github.com/${{ github.repository }}/pull/${{ github.event.pull_request.number }}"
            PR_TITLE: ${{ github.event.pull_request.title }}
            BRANCH:  ${{ env.BRANCH }}
            AZURE_OPENAI_API_KEY: ${{ secrets.AZURE_OPENAI_API_KEY || '' }}
            AZURE_OPENAI_API: ${{ secrets.AZURE_OPENAI_API || '' }}
            PATCH_PR: ${{ github.event.pull_request.number }}
            PATCH_REPO: ${{ github.repository }}
            FULL_SUMMARY: true
            FILE_SUMMARY: false
            TEST_SUMMARY: false
            BUG_SUMMARY: false
            RISK_SUMMARY: false
            RISK_BREAKING: false

Create a PR on the repo
The workflow triggers, succeeds (screenshot below)

No comment is seen in the original PR

Code snippet
No response
Relevant log output
No response

Try to set write permissions for add_pr_comment job.
    permissions:
      pull-requests: write

Thanks a lot, this worked for me


Add pull request template and issue templates

This is an automatic batch pull request.

Pull-request updated, HEAD is now 70ff2958296121c5c73cdeb878630b1ad1b125bb


Crash on Android when call new OpenGLUltravioletContext()

Got The application requested an OpenGL context of version 2.0 or higher, but the driver could not provide such a context.

What device are you getting this error on? What version of Android?

@tlgkccampbell both Emulator (with API 28) and real device (with API 23)
I ran into this error with a simple project, which has one shared project and multiple platform-special project.
It works well on Mac, but crashes on Android. And it does not work on iOS (only a blank screen).
the codes of Game class are from RenderingGeometry sample.

When you create your OpenGLUltravioletConfiguration object, please try setting Debug to false and let me know if that fixes the issue for you.
It looks like there's something wrong with how debug contexts are being handled on Android. I'm going to investigate whether updating SDL2 will fix this.

@tlgkccampbell It works well on Android after commenting Debug settings.
but it still gives me a blank screen on iOS.
Is there any note for using a shared project with Ultraviolet.Game.iOS?

Crashes on iOS solved by adding <AutoGenerateBindingRedirects>true</AutoGenerateBindingRedirects> into the csproj file of iOS project.

Thank you for the information, I'll look into fixing the iOS and Mac packages.

It seems that macMorden packages conflict with packages for other Xamarin platforms.

This will be fixed on supported platforms in the next release. Unfortunately, the next release is also dropping support for iOS entirely, since I no longer have the hardware necessary to run the current set of development tools.


Add an item "My Health Pieces" in the nav menu at the top.

I'll check with clients on 20 Nov 2017 to figure out what the order should be across the top.

Please reassign this to me when you have an agreement with the clients about what to do. When adding a Nav item, it needs to go to something. I haven't seen My Health Pieces defined yet.

I assume this relates to #71 and #72?


Update QC report with more CITE-Seq

As part of this Epic https://github.com/AlexsLemonade/scpca-nf/issues/291, we'll need to update the QC report with more ADT-level processing information. This can include:

Extent of filtering from ADT-level information specifically

In parallel, we might update the filtering report section more generally to have subsections: overall, RNA, and ADT

A plot of some kind, if anyone can think of a plot to show? ADT violins, for example?
Associated textual context for these updates

Yeah, I see what happened here.. I did have an issue for QC report :tada:, but :sad: I got confused about which repo it belonged in! So, this can be closed.