Compiling the ULP RISC-V Code (IDFGH-9542)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
stable (v5.01)
Operating System used.
Linux
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
None
What is the expected behavior?
Compiled
What is the actual behavior?
Compilation failed
Steps to reproduce.

Step
Step
Step
...

Build or installation Logs.
[os@fedora gpio_interrupt]$ idf.py build
Executing action: all (aliases: build)
Running make in directory /home/os/esp/gpio_interrupt/build
Executing "make -j 4 all"...
[  0%] Generating ../../partition_table/partition-table.bin
[  0%] Creating directories for 'ulp_main'
[  0%] Generating memory.ld linker script...
[  0%] Built target custom_bundle
[  0%] Built target memory_ld
[  0%] No download step for 'ulp_main'
[  0%] Generating project_elf_src_esp32s2.c
Partition table binary generated. Contents:
*******************************************************************************
[  0%] Built target _project_elf_src
[  0%] No update step for 'ulp_main'
[  0%] Building C object esp-idf/ulp/CMakeFiles/__idf_ulp.dir/ulp_common/ulp_common.c.obj
[  1%] Building C object esp-idf/ulp/CMakeFiles/__idf_ulp.dir/ulp_riscv/ulp_riscv.c.obj
[  1%] No patch step for 'ulp_main'
# ESP-IDF Partition Table
# Name, Type, SubType, Offset, Size, Flags
nvs,data,nvs,0x9000,24K,
phy_init,data,phy,0xf000,4K,
factory,app,factory,0x10000,1M,
[  2%] Performing configure step for 'ulp_main'
-- Found Git: /usr/bin/git (found version "2.39.2")
*******************************************************************************
[  2%] Built target partition_table_bin
[  2%] Building C object esp-idf/ulp/CMakeFiles/__idf_ulp.dir/ulp_riscv/ulp_riscv_adc.c.obj
[  2%] Creating directories for 'bootloader'
[  2%] Linking C static library libulp.a
[  2%] No download step for 'bootloader'
[  2%] No update step for 'bootloader'
[  2%] Built target __idf_ulp
[  2%] No patch step for 'bootloader'
[  3%] Building C object esp-idf/esp_https_ota/CMakeFiles/__idf_esp_https_ota.dir/src/esp_https_ota.c.obj
[  4%] Performing configure step for 'bootloader'
-- Found Git: /usr/bin/git (found version "2.39.2")
[  4%] Linking C static library libesp_https_ota.a
[  4%] Built target __idf_esp_https_ota
[  4%] Building C object esp-idf/esp_http_server/CMakeFiles/__idf_esp_http_server.dir/src/httpd_parse.c.obj
[  4%] Building C object esp-idf/esp_http_server/CMakeFiles/__idf_esp_http_server.dir/src/httpd_main.c.obj
[  4%] Building C object esp-idf/esp_http_server/CMakeFiles/__idf_esp_http_server.dir/src/httpd_sess.c.obj
[  4%] Building C object esp-idf/esp_http_server/CMakeFiles/__idf_esp_http_server.dir/src/httpd_txrx.c.obj
[  4%] Building C object esp-idf/esp_http_server/CMakeFiles/__idf_esp_http_server.dir/src/httpd_uri.c.obj
[  4%] Building C object esp-idf/esp_http_server/CMakeFiles/__idf_esp_http_server.dir/src/httpd_ws.c.obj
[  4%] Building C object esp-idf/esp_http_server/CMakeFiles/__idf_esp_http_server.dir/src/util/ctrl_sock.c.obj
[  4%] Linking C static library libesp_http_server.a
[  4%] Built target __idf_esp_http_server
[  4%] Building C object esp-idf/esp_http_client/CMakeFiles/__idf_esp_http_client.dir/lib/http_auth.c.obj
[  4%] Building C object esp-idf/esp_http_client/CMakeFiles/__idf_esp_http_client.dir/esp_http_client.c.obj
[  4%] Building C object esp-idf/esp_http_client/CMakeFiles/__idf_esp_http_client.dir/lib/http_header.c.obj
[  4%] Building C object esp-idf/esp_http_client/CMakeFiles/__idf_esp_http_client.dir/lib/http_utils.c.obj
-- The ASM compiler identification is GNU
-- Found assembler: /home/os/.espressif/tools/riscv32-esp-elf/esp-2022r1-11.2.0/riscv32-esp-elf/bin/riscv32-esp-elf-gcc
[  5%] Linking C static library libesp_http_client.a
-- The C compiler identification is GNU 11.2.0
-- Detecting C compiler ABI info
[  5%] Built target __idf_esp_http_client
[  5%] Building C object esp-idf/tcp_transport/CMakeFiles/__idf_tcp_transport.dir/transport.c.obj
[  5%] Building C object esp-idf/tcp_transport/CMakeFiles/__idf_tcp_transport.dir/transport_ssl.c.obj
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /home/os/.espressif/tools/riscv32-esp-elf/esp-2022r1-11.2.0/riscv32-esp-elf/bin/riscv32-esp-elf-gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Building ULP app ulp_main
-- Configuring done (3.3s)
-- Generating done (0.0s)
-- Build files have been written to: /home/os/esp/gpio_interrupt/build/esp-idf/main/ulp_main
[  6%] Building C object esp-idf/tcp_transport/CMakeFiles/__idf_tcp_transport.dir/transport_internal.c.obj
[  6%] Performing build step for 'ulp_main'
gmake[3]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
[  6%] Building C object esp-idf/tcp_transport/CMakeFiles/__idf_tcp_transport.dir/transport_ws.c.obj
-- The C compiler identification is GNU 11.2.0
[  5%] Generating ulp_riscv.ld
-- The CXX compiler identification is GNU 11.2.0
[ 11%] Generating /home/os/esp/gpio_interrupt/main/ulp/main.c
gmake[6]: cmake: Permission denied
gmake[6]: *** [CMakeFiles/ulp_main.dir/build.make:74: /home/os/esp/gpio_interrupt/main/ulp/main.c] Error 127
gmake[5]: *** [CMakeFiles/Makefile2:110: CMakeFiles/ulp_main.dir/all] Error 2
gmake[4]: *** [CMakeFiles/Makefile2:144: CMakeFiles/build.dir/rule] Error 2
gmake[3]: *** [Makefile:150: build] Error 2
make[2]: *** [esp-idf/main/CMakeFiles/ulp_main.dir/build.make:86: esp-idf/main/ulp_main-prefix/src/ulp_main-stamp/ulp_main-build] Error 2
make[1]: *** [CMakeFiles/Makefile2:4490: esp-idf/main/CMakeFiles/ulp_main.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
-- The ASM compiler identification is GNU
-- Found assembler: /home/os/.espressif/tools/xtensa-esp32s2-elf/esp-2022r1-11.2.0/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-gcc
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Check for working C compiler: /home/os/.espressif/tools/xtensa-esp32s2-elf/esp-2022r1-11.2.0/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-gcc - skipped
-- Detecting C compile features
-- Detecting C compile features - done
-- Detecting CXX compiler ABI info
[  6%] Linking C static library libtcp_transport.a
[  6%] Built target __idf_tcp_transport
-- Detecting CXX compiler ABI info - done
-- Check for working CXX compiler: /home/os/.espressif/tools/xtensa-esp32s2-elf/esp-2022r1-11.2.0/xtensa-esp32s2-elf/bin/xtensa-esp32s2-elf-g++ - skipped
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Building ESP-IDF components for target esp32s2
-- Project sdkconfig file /home/os/esp/gpio_interrupt/sdkconfig
-- Looking for sys/types.h
-- Looking for sys/types.h - found
-- Looking for stdint.h
-- Looking for stdint.h - found
-- Looking for stddef.h
-- Looking for stddef.h - found
-- Check size of time_t
-- Check size of time_t - done
-- Adding linker script /home/os/esp/esp-idf/components/soc/esp32s2/ld/esp32s2.peripherals.ld
-- App "bootloader" version: v5.0.1-dirty
-- Adding linker script /home/os/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.ld
-- Adding linker script /home/os/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.api.ld
-- Adding linker script /home/os/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.libgcc.ld
-- Adding linker script /home/os/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.newlib-funcs.ld
-- Adding linker script /home/os/esp/esp-idf/components/esp_rom/esp32s2/ld/esp32s2.rom.spiflash.ld
-- Adding linker script /home/os/esp/esp-idf/components/bootloader/subproject/main/ld/esp32s2/bootloader.ld
-- Adding linker script /home/os/esp/esp-idf/components/bootloader/subproject/main/ld/esp32s2/bootloader.rom.ld
-- Components: bootloader bootloader_support efuse esp_app_format esp_common esp_hw_support esp_rom esp_system esptool_py freertos hal log main micro-ecc newlib partition_table soc spi_flash xtensa
-- Component paths: /home/os/esp/esp-idf/components/bootloader /home/os/esp/esp-idf/components/bootloader_support /home/os/esp/esp-idf/components/efuse /home/os/esp/esp-idf/components/esp_app_format /home/os/esp/esp-idf/components/esp_common /home/os/esp/esp-idf/components/esp_hw_support /home/os/esp/esp-idf/components/esp_rom /home/os/esp/esp-idf/components/esp_system /home/os/esp/esp-idf/components/esptool_py /home/os/esp/esp-idf/components/freertos /home/os/esp/esp-idf/components/hal /home/os/esp/esp-idf/components/log /home/os/esp/esp-idf/components/bootloader/subproject/main /home/os/esp/esp-idf/components/bootloader/subproject/components/micro-ecc /home/os/esp/esp-idf/components/newlib /home/os/esp/esp-idf/components/partition_table /home/os/esp/esp-idf/components/soc /home/os/esp/esp-idf/components/spi_flash /home/os/esp/esp-idf/components/xtensa
-- Configuring done (5.4s)
-- Generating done (0.1s)
-- Build files have been written to: /home/os/esp/gpio_interrupt/build/bootloader
[  6%] Performing build step for 'bootloader'
[  1%] Generating project_elf_src_esp32s2.c
[  2%] Building C object esp-idf/log/CMakeFiles/__idf_log.dir/log.c.obj
[  3%] Building C object esp-idf/log/CMakeFiles/__idf_log.dir/log_buffers.c.obj
[  4%] Building C object esp-idf/log/CMakeFiles/__idf_log.dir/log_noos.c.obj
[  4%] Built target _project_elf_src
[  5%] Linking C static library liblog.a
[  5%] Built target __idf_log
[  5%] Building C object esp-idf/esp_rom/CMakeFiles/__idf_esp_rom.dir/patches/esp_rom_crc.c.obj
[  6%] Building C object esp-idf/esp_rom/CMakeFiles/__idf_esp_rom.dir/patches/esp_rom_sys.c.obj
[  7%] Building C object esp-idf/esp_rom/CMakeFiles/__idf_esp_rom.dir/patches/esp_rom_uart.c.obj
[  8%] Building C object esp-idf/esp_rom/CMakeFiles/__idf_esp_rom.dir/patches/esp_rom_spiflash.c.obj
[  9%] Building C object esp-idf/esp_rom/CMakeFiles/__idf_esp_rom.dir/patches/esp_rom_regi2c.c.obj
[ 10%] Building C object esp-idf/esp_rom/CMakeFiles/__idf_esp_rom.dir/patches/esp_rom_efuse.c.obj
[ 11%] Building ASM object esp-idf/esp_rom/CMakeFiles/__idf_esp_rom.dir/patches/esp_rom_longjmp.S.obj
[ 12%] Building C object esp-idf/esp_rom/CMakeFiles/__idf_esp_rom.dir/patches/esp_rom_systimer.c.obj
[ 13%] Building C object esp-idf/esp_rom/CMakeFiles/__idf_esp_rom.dir/esp32s2/usb_descriptors.c.obj
[ 14%] Linking C static library libesp_rom.a
[ 14%] Built target __idf_esp_rom
[ 14%] Building C object esp-idf/esp_common/CMakeFiles/__idf_esp_common.dir/src/esp_err_to_name.c.obj
[ 15%] Linking C static library libesp_common.a
[ 15%] Built target __idf_esp_common
[ 16%] Building C object esp-idf/esp_hw_support/CMakeFiles/__idf_esp_hw_support.dir/cpu.c.obj
[ 17%] Building C object esp-idf/esp_hw_support/CMakeFiles/__idf_esp_hw_support.dir/port/esp32s2/rtc_clk_init.c.obj
[ 18%] Building C object esp-idf/esp_hw_support/CMakeFiles/__idf_esp_hw_support.dir/esp_memory_utils.c.obj
[ 19%] Building C object esp-idf/esp_hw_support/CMakeFiles/__idf_esp_hw_support.dir/port/esp32s2/rtc_clk.c.obj
[ 20%] Building C object esp-idf/esp_hw_support/CMakeFiles/__idf_esp_hw_support.dir/port/esp32s2/rtc_init.c.obj
[ 21%] Building C object esp-idf/esp_hw_support/CMakeFiles/__idf_esp_hw_support.dir/port/esp32s2/rtc_pm.c.obj
[ 22%] Building C object esp-idf/esp_hw_support/CMakeFiles/__idf_esp_hw_support.dir/port/esp32s2/rtc_sleep.c.obj
[ 23%] Building C object esp-idf/esp_hw_support/CMakeFiles/__idf_esp_hw_support.dir/port/esp32s2/rtc_time.c.obj
[ 24%] Building C object esp-idf/esp_hw_support/CMakeFiles/__idf_esp_hw_support.dir/port/esp32s2/chip_info.c.obj
[ 25%] Linking C static library libesp_hw_support.a
[ 25%] Built target __idf_esp_hw_support
[ 26%] Building C object esp-idf/esp_system/CMakeFiles/__idf_esp_system.dir/esp_err.c.obj
[ 27%] Linking C static library libesp_system.a
[ 27%] Built target __idf_esp_system
[ 27%] Building C object esp-idf/efuse/CMakeFiles/__idf_efuse.dir/esp32s2/esp_efuse_table.c.obj
[ 28%] Building C object esp-idf/efuse/CMakeFiles/__idf_efuse.dir/esp32s2/esp_efuse_rtc_table.c.obj
[ 29%] Building C object esp-idf/efuse/CMakeFiles/__idf_efuse.dir/esp32s2/esp_efuse_rtc_calib.c.obj
[ 30%] Building C object esp-idf/efuse/CMakeFiles/__idf_efuse.dir/esp32s2/esp_efuse_fields.c.obj
[ 31%] Building C object esp-idf/efuse/CMakeFiles/__idf_efuse.dir/esp32s2/esp_efuse_utility.c.obj
[ 32%] Building C object esp-idf/efuse/CMakeFiles/__idf_efuse.dir/src/esp_efuse_api.c.obj
[ 34%] Building C object esp-idf/efuse/CMakeFiles/__idf_efuse.dir/src/esp_efuse_fields.c.obj
[ 35%] Building C object esp-idf/efuse/CMakeFiles/__idf_efuse.dir/src/esp_efuse_utility.c.obj
[ 36%] Building C object esp-idf/efuse/CMakeFiles/__idf_efuse.dir/src/efuse_controller/keys/with_key_purposes/esp_efuse_api_key.c.obj
[ 37%] Linking C static library libefuse.a
[ 37%] Built target __idf_efuse
[ 37%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/bootloader_common.c.obj
[ 38%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/bootloader_clock_init.c.obj
[ 39%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/bootloader_common_loader.c.obj
[ 40%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/bootloader_flash/src/bootloader_flash.c.obj
[ 41%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/bootloader_mem.c.obj
[ 42%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/bootloader_random.c.obj
[ 43%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/bootloader_random_esp32s2.c.obj
[ 44%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/bootloader_utility.c.obj
[ 45%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/esp_image_format.c.obj
[ 46%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/flash_encrypt.c.obj
[ 47%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/secure_boot.c.obj
[ 48%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/flash_partitions.c.obj
[ 48%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/bootloader_flash/src/flash_qio_mode.c.obj
[ 49%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/bootloader_efuse.c.obj
[ 50%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/bootloader_init.c.obj
[ 51%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/bootloader_flash/src/bootloader_flash_config_esp32s2.c.obj
[ 52%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/bootloader_clock_loader.c.obj
[ 53%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/bootloader_console.c.obj
[ 54%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/bootloader_console_loader.c.obj
[ 55%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/bootloader_panic.c.obj
[ 56%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/esp32s2/bootloader_sha.c.obj
[ 57%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/esp32s2/bootloader_soc.c.obj
[ 58%] Building C object esp-idf/bootloader_support/CMakeFiles/__idf_bootloader_support.dir/src/esp32s2/bootloader_esp32s2.c.obj
[ 59%] Linking C static library libbootloader_support.a
[ 59%] Built target __idf_bootloader_support
[ 60%] Building C object esp-idf/esp_app_format/CMakeFiles/__idf_esp_app_format.dir/esp_app_desc.c.obj
[ 61%] Linking C static library libesp_app_format.a
[ 61%] Built target __idf_esp_app_format
[ 61%] Building C object esp-idf/hal/CMakeFiles/__idf_hal.dir/mpu_hal.c.obj
[ 62%] Building C object esp-idf/hal/CMakeFiles/__idf_hal.dir/efuse_hal.c.obj
[ 63%] Building C object esp-idf/hal/CMakeFiles/__idf_hal.dir/esp32s2/efuse_hal.c.obj
[ 64%] Building C object esp-idf/hal/CMakeFiles/__idf_hal.dir/mmu_hal.c.obj
[ 65%] Building C object esp-idf/hal/CMakeFiles/__idf_hal.dir/wdt_hal_iram.c.obj
[ 67%] Building C object esp-idf/hal/CMakeFiles/__idf_hal.dir/cache_hal.c.obj
[ 68%] Linking C static library libhal.a
[ 68%] Built target __idf_hal
[ 69%] Building C object esp-idf/micro-ecc/CMakeFiles/__idf_micro-ecc.dir/uECC_verify_antifault.c.obj
[ 70%] Linking C static library libmicro-ecc.a
[ 70%] Built target __idf_micro-ecc
[ 71%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/dport_access_common.c.obj
[ 72%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/lldesc.c.obj
[ 73%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/adc_periph.c.obj
[ 74%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/dac_periph.c.obj
[ 75%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/dedic_gpio_periph.c.obj
[ 76%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/gpio_periph.c.obj
[ 77%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/i2c_periph.c.obj
[ 78%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/sdm_periph.c.obj
[ 79%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/i2s_periph.c.obj
[ 80%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/lcd_periph.c.obj
[ 80%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/interrupts.c.obj
[ 81%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/ledc_periph.c.obj
[ 82%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/pcnt_periph.c.obj
[ 83%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/rmt_periph.c.obj
[ 84%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/rtc_io_periph.c.obj
[ 85%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/spi_periph.c.obj
[ 86%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/timer_periph.c.obj
[ 87%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/touch_sensor_periph.c.obj
[ 88%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/uart_periph.c.obj
[ 89%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/usb_periph.c.obj
[ 90%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/temperature_sensor_periph.c.obj
[ 90%] Building C object esp-idf/soc/CMakeFiles/__idf_soc.dir/esp32s2/usb_otg_periph.c.obj
[ 91%] Linking C static library libsoc.a
[ 91%] Built target __idf_soc
[ 92%] Building C object esp-idf/xtensa/CMakeFiles/__idf_xtensa.dir/xt_trax.c.obj
[ 93%] Building C object esp-idf/xtensa/CMakeFiles/__idf_xtensa.dir/eri.c.obj
[ 94%] Linking C static library libxtensa.a
[ 94%] Built target __idf_xtensa
[ 95%] Building C object esp-idf/main/CMakeFiles/__idf_main.dir/bootloader_start.c.obj
[ 95%] Linking C static library libmain.a
[ 95%] Built target __idf_main
[ 96%] Building C object CMakeFiles/bootloader.elf.dir/project_elf_src_esp32s2.c.obj
[ 97%] Linking C executable bootloader.elf
[ 98%] Built target bootloader.elf
[100%] Generating binary image from built executable
esptool.py v4.5.1
Creating esp32s2 image...
Merged 1 ELF section
Successfully created esp32s2 image.
Generated /home/os/esp/gpio_interrupt/build/bootloader/bootloader.bin
[100%] Built target gen_project_binary
Bootloader binary size 0x4c30 bytes. 0x23d0 bytes (32%) free.
[100%] Built target bootloader_check_size
[100%] Built target app
[  6%] No install step for 'bootloader'
[  6%] Completed 'bootloader'
[  6%] Built target bootloader
make: *** [Makefile:136: all] Error 2
make failed with exit code 2, output of the command is in the /home/os/esp/gpio_interrupt/build/log/idf_py_stderr_output_132622 and /home/os/esp/gpio_interrupt/build/log/idf_py_stdout_output_132622

More Information.
Hi, I copied the example from Application Examples, ULP RISC-V Coprocessor polls GPIO while main CPU is in deep sleep: system/ulp_riscv/gpio. When I try to run idf.py build, it doesn't complete successfully. What should I do to fix it? Thank you.
hp notebook
windows 10x
Fedora 37

@osmond2023 I see a cmake: Permission denied so this is probably related to your setup somehow.

Can you successfully build the project if you build it inside the esp-idf/examples folder without copying it out first?
Does other examples also give the same error?

Hi Marius,
I reinstalled ESP-IDF and built it inside the examples folder. It builds successfully. Thanks.

That's good, seems like there just a permission problem with the folder when you copy it out then.
If you run into it again then please check that the permission are set correctly (how to do this would depend on your operating system).
Closing this one for now then.

Ran into this problem on a relatively(?) clean but older version (IDF 4.4.2). Just in case anyone runs into the problem and hits a dead end:
The problem seems to be caused in /home/david/esp/esp-idf-v4.4.2.clean/examples/system/ulp_riscv/gpio/build/esp-idf/main/ulp_main/CMakeFiles/ulp_main.dir/build.make
This file contains three rules that look like:
/home/david/esp/esp-idf-v4.4.2.clean/examples/system/ulp_riscv/gpio/main/ulp/main.c: esp32s3.ulp.riscv.ld
	@$(CMAKE_COMMAND) -E cmake_echo_color --switch=$(COLOR) --blue --bold --progress-dir=/home/david/esp/esp-idf-v4.4.2.clean/examples/system/ulp_riscv/gpio/build/esp-idf/main/ulp_main/CMakeFiles --progress-num=$(CMAKE_PROGRESS_1) "Generating /home/david/esp/esp-idf-v4.4.2.clean/examples/system/ulp_riscv/gpio/main/ulp/main.c"
	cmake -E echo

"cmake" in "cmake -E echo" resolves to a directory name, presumably because the parent directory is in the path. The directory in question is "/home/david/esp/esp-idf-v4.4.2.clean/tools/cmake". execve of course can't execute directories, and produces EACCESS.
Replacing all three instances of "cmake" by "@$(CMAKE_COMMAND)" fixes the problem.


Definining "Ladder Capture" and "Ladder Escape"

In Silver et al's paper, Extended Data Table 2 lists the features used as inputs to the policy and value networks. Exactly what moves are considered "ladder capture" and what are considered "ladder escape"?
Here is our best current interpretation:

ladder capture: playing here reduces opponent’s liberties from 2 to 1 and the resulting ladder can end in a capture of the opponent (checked via a potentially expensive search)
ladder escape: playing here reduces opponent’s liberties from 2 to 1 but the resulting ladder cannot end in a capture of the opponent

It's not clear whether the above definition of ladder escape is a useful feature, however.
We also considered the definitions:

ladder escape: playing here prevents the opponent from completing a ladder capture (though this is odd because from the opponent's perspective it never would have been defined as ladder capture in the first place)

Can the ladder breaker move considered as "ladder escape" feature? I guess you know what's the ladder breaker is.. http://senseis.xmp.net/?LadderBreaker

You could mail David Silver.  He was responsive when I asked about code for computing features being available (sadly, it's not).
My understanding of the Escape feature was "playing here increases liberties from 1 to 2 or 3, and if 2 does not result in a ladder capture."
Is ladder capture that expensive to search for?  If the group ever gets 3 liberties, it's no longer a ladder capture, though moves other than at the tip of the ladder have to be considered (in the case where playing out the ladder puts "chasing" stones in atari).

Also, move, that counters LadderBreaker can be considered as "ladder capture", not only the move, which reduces liberties from 2 to 1 imho ^^ Move that you can call "Ladder works again" =) You don't need to capture on any ladderbreaker-tenuki of opponent, but usually capture the ladder is an urgent move..

See Feugos files
GoLadder.cpp
FeBasicFeatures.cpp
GoUctLadderKnowledge.cpp
These define functions
bool GoLadderUtil::IsLadderEscapeMove
bool GoLadderUtil::IsLadderCaptureMove
why reinvent the wheel...

On the note of not reinventing the wheel, I've started a Cython wrapper for Fuego:
https://github.com/thouis/pyfuego
I don't know if it would be useful or not, but it may be easier to re-use Fuego's code rather than reimplement it.

thouis, nice. See https://github.com/Rochester-NRT/AlphaGo/issues/48 that has a list of the functions we need that are already implemented in Fuego.

Copying Fuego's definitions of ladder capture and ladder escape seems to be the way to proceed. Copying them will not be the difficult part, optimizing them will be.. and for the sake of starting supervised training, we do not need to compute features from a board blazingly fast.
@thouis we may come back to your pyfuego project later, but I think it would just obfuscate the process of computing features right now.

+1 on leaving it for now.  I'm going to add the rest of the AG features to the pyfuego code, and write an SGF-to-HDF5 writer, in the meantime.
Fuego has several small tests for capture/escape that I can try to extract in a form useful for this project.

Good idea. I just made a separate ticket for upgrading the whole testing process to function more like Fuego's #59

I've finished writing the feature extractor in my fuego wrapper, and have started converting the KGS 6d+ archives to HDF5.  At some point, it would be good to compare features to make sure we agree (and understand where we don't).

@thouis I'm curious what your thoughts are on formats for saving/loading tensor data. Is it a standard for go programs to concatenate data into large tensors and save as HDF5? Our current implementation is not very efficient - we're saving each training example in its own file, which at least has the advantage of making it easy to select random minibatches (simply loading random files)
@cjbates-mit can you push your current ladder code to a new branch so that we can compare with thouis'?

I don't know what's standard for Go programs.  For ML, I know many use HDF (we do so in our research).  The built-in compression is probably quite helpful for this sort of data.


Wrong converting to class case

This code:
assert_eq!(
    inflector::cases::classcase::to_class_case("editMessageMedia"),
    "EditMessageMedia"
);

Fails with this error:
thread 'main' panicked at 'assertion failed: `(left == right)`
  left: `"EditMessageMedum"`,
 right: `"EditMessageMedia"`', src/main.rs:228:5

This happens on i or t in the second last position or s in the last position (when the second last is not s:
use inflector::Inflector;

fn main() {

    for b_last_letter in b'a'..=b'z' {
        let last_letter = b_last_letter as char;

        for b_mid_letter in b'a'..=b'z' {
            let mid_letter = b_mid_letter as char;
            let class_case_string =
                format!("a{}{}", mid_letter, last_letter).to_class_case();

            if class_case_string != format!("A{}{}", mid_letter, last_letter) {
                println!("a{}{} => {}",
                    mid_letter, last_letter, class_case_string);
            }
        }
    }
}

outputs:
aia => Aum
ata => Aum
aas => Aa
abs => Ab
acs => Ac
ads => Ad
aes => Ae
afs => Af
ags => Ag
ahs => Ah
ais => Ai
ajs => Aj
aks => Ak
als => Al
ams => Am
ans => An
aos => Ao
aps => Ap
aqs => Aq
ars => Ar
ats => At
aus => Au
avs => Av
aws => Aw
axs => Ax
ays => Ay
azs => Az

The problem is the final to_singular().
This seems like the wrong behaviour to me...


Cannot connect if Ubuntu is on.

I have Maintainer up and running but it will not connect unless I turn off the Ubuntu firewall.
I have rules allowing 8154 in anywhere.
8154/tcp                   ALLOW       Anywhere
8154/tcp (v6)              ALLOW       Anywhere (v6)
If I turn off the firewall it connects immediately.  I'm stumped as to why the firewall would block it if there is an inbound rule.
Docker inspect:
https://pastebin.com/AL172Yqd
Any suggestions?
I tried posting on reddit in Docker and got pretty much no help.

I removed ufw and changed to firewalld. No longer an issue.


Python API: update syntax for 0.2.0

Syntax changed to reduce future maintenance efforts.
See also this comment.

Nice changes! :+1:


feat(functions/helloworld): add functions_helloworld_get, functions_helloworld_http

The first PHP function sample.

Adds sample functions_helloworld_get and functions_helloworld_http
Includes end-to-end DeployTest, locally run SystemTest, and UnitTest.
Helloworld HTTP uses a common trait to drive the same test cases in each test mode.

Open Questions

Anything special needed for code coverage?
Is it valuable to keep both System and Unit tests? I find System & Deploy tests to be valuable but unit may be a bit redundant.
PHP 7.2 is failing, but I don't need this to pass on PHP 7.2. Can we skip it?

DeployTests are currently failing. Not sure how I broke them yet :)

Fixed feedback, and found the bug in the DeployTests.

Failing test is still only PHP 7.2


[Proposal] Add rest API for configuration store.

In what area(s)?
Configuration store rest API.

/area runtime

/area test-and-release

Describe the proposal

We would support 3 configuration rest APIs: Get, Subscribe and Unsubscribe, like gRPC API does.

ConfigurationItem JSON

{
  "key":"",
  "value":"",
  "version":"",
  "metadata": {
    "metedataitem1":"",
    "metedataitem2":"",
  }
}

Configuration Get API

request

Method: Get
Route: configuration/{storeName}
Version: v1apha1
Query Param: key=key1,key2,key3

response body

[
  {ConfigurationItem}
]

Configuration Subscribe API

request

Method: Get
Route: configuration/{storeName}/subscribe
Version: v1apha1
Query Param: key=key1,key2,key3

response websocket body:

{
  "id":"", // subscription id
  "items": [{ConfigurationItem}]
}

Configuration UnSubscribe API

request

Method: DELETE
Route: configuration/{storeName}/subscribe
Version: v1apha1
Query Param: Id="" // subscription id
I encountered a problem that , "github.com/valyala/fasthttp" can't be convert to websocket.Conn gracefully. Do you have any suggestion to upgrade fasthttp requestContext to websocket conn?

@yaron2 @daixiang0
cc @beiwei30

LGTM. Pls. clarify how metadata is encoded in query.

@beiwei30 @LaurenceLiZhixin today, Dapr uses regular HTTP Restful endpoints to invoke the app. I suggest we keep this consistent behavior and not introduce websockets.
For example, when an app consumed a pub/sub event over HTTP, Dapr will send a POST request to the app on /<name-of-topic>.
It'd be preferable to invoke the app on a path like dapr/configuration/<name-of-component> and send the data via a POST body.

@yaron2 without websocket, I think we cannot be able to support configuration notification via 'subscribe', and in fact, pubsub HTTP API doesn't support 'subscribe' either.

@yaron2 without websocket, I think we cannot be able to support configuration notification via 'subscribe', and in fact, pubsub HTTP API doesn't support 'subscribe' either.

Pub/sub calls the user's HTTP endpoint to get subscriptions and then once an event arrives, Dapr notifies the app through a different HTTP endpoint.
Can we do the same for configuration? users subscribe through the HTTP endpoint defined in the proposal above, and when a change occurs, Dapr invokes the app at: http://<app-port>/configuration/<name-of-component>/<key>.
Any reason this can't work?

I think this would be the best solution to solve configuration subscription in without websocket, I try to follow this idea to implement.
@yaron2

@yaron2 without websocket, I think we cannot be able to support configuration notification via 'subscribe', and in fact, pubsub HTTP API doesn't support 'subscribe' either.

Pub/sub calls the user's HTTP endpoint to get subscriptions and then once an event arrives, Dapr notifies the app through a different HTTP endpoint.
Can we do the same for configuration? users subscribe through the HTTP endpoint defined in the proposal above, and when a change occurs, Dapr invokes the app at: http://<app-port>/configuration/<name-of-component>/<key>.
Any reason this can't work?

Agree, we should align with the solution pub/sub uses.


Fix WindowsEventLog: Evaluation of event log differ

Pull Request (PR) description
Fix WindowsEventLog: Evaluation of event log differ
This Pull Request (PR) fixes the following issues
- Fixes #229

Task list

[x] Added an entry under the Unreleased section of the change log in the CHANGELOG.md.
Entry should say what was changed, and how that affects users (if applicable).
[ ] Resource documentation added/updated in README.md in the resource folder.
[ ] Resource parameter descriptions added/updated in schema.mof
and comment-based help.
[ ] Comment-based help added/updated.
[ ] Localization strings added/updated in all localization files as appropriate.
[ ] Examples appropriately added/updated.
[ ] Unit tests added/updated. See DSC Resource Testing Guidelines.
[ ] Integration tests added/updated (where possible). See DSC Resource Testing Guidelines.
[x] New/changed code adheres to DSC Resource Style Guidelines and Best Practices.

This change is

Codecov Report

Merging #277 into dev will decrease coverage by <1%.
The diff coverage is 100%.

@@         Coverage Diff         @@
##            dev   #277   +/-   ##
===================================
- Coverage    88%    88%   -1%
===================================
  Files        14     14
  Lines      1483   1481    -2
===================================
- Hits       1308   1306    -2
  Misses      175    175

Hi @Outek - you might need to rebase your branch as this PR includes a bunch of changes that have already been merged to dev. Although this doesn't have merge conflicts the instructions are still valid: https://github.com/PowerShell/DscResources/blob/master/GettingStartedWithGitHub.md#resolve-merge-conflicts

@Outek - Oh wait - I updated the branch and it corrected it. So all good. Sorry about that.

Hi @Outek - looks like you've got some trailing spaces in the MD: https://ci.appveyor.com/project/PowerShell/computermanagementdsc/builds/27898015?fullLog=true#L1083

Hi @PlagueHO
Is here something wrong with the MR?


ENH/TST: add spiral and fermat spiral scans

This was a lot simpler when it was hidden in hxntools...

[Current coverage][cc-pull] is 75.74%

Merging [#438][cc-pull] into [master][cc-base-branch] will increase coverage by +0.66%

@@             master       #438   diff @@
==========================================
  Files            17         17
  Lines          3329       3421    +92
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits           2499       2591    +92
  Misses          830        830
  Partials          0          0

Powered by Codecov. Last updated by [7f7bb51...2db13e5][cc-compare]
[cc-base-branch]: https://codecov.io/gh/NSLS-II/bluesky/branch/master?src=pr
[cc-compare]: https://codecov.io/gh/NSLS-II/bluesky/compare/7f7bb514d5137cbaf2c815adcd9e66814d05beaf...2db13e57d934afe342f43e2f42575ee67ddda71a
[cc-pull]: https://codecov.io/gh/NSLS-II/bluesky/pull/438?src=pr

Why was it simpler hidden in hxntools?

@tacaswell no class wrappers, no 'spec api'/gs-aware separation, no tests... and no PR means no bikeshedding 😄

We could just drop the spec api / gs....

@tacaswell up to you as far as dropping the gs-aware one.

I was being sarcastic about dropping gs

attn @gjwillms @imrealkaren


⬆  (deps) jeromefitz/... peer-deps update [b]

I know it would make sense for everything to live together, but I do like having them separate to show how you can interact with two monorepos at the moment.
Plus not sure how much overhead there is uploading the entire packages repo to vercel just for a singular website.
I digress, updates to
@jeromefitz/conventional-gitmoji
@jeromefitz/design-system
@jeromefitz/eslint-config
@jeromefitz/git-cz
@jeromefitz/lint-staged
@jeromefitz/notion
@jeromefitz/prettier-config
@jeromefitz/release-notes-generator
@jeromefitz/semantic
@jeromefitz/spotify
@jeromefitz/tsconfig
@jeromefitz/utils

Which reflect a series of releases that basically boil down to:

Making lodash a dev|peerDependencies
Trimming the dependencies further
Ensuring tsup-node has no confusion in the code with tsup external|noExternal

This pull request has been deployed to Vercel.

Latest commit:
726315e

✅ Preview:
https://jeromefitzgerald-a5jwkia2i-jerome5.vercel.app

🔍 Inspect:
https://vercel.com/jerome/jeromefitzgerald/Gfq4rnpf4pDQsLVnfLNwre9jwzBQ

View Workflow Logs

This pull request has been deployed to Vercel.

Latest commit:
6dc57af

✅ Preview:
https://jeromefitzgerald-mqe9c4hjy-jerome5.vercel.app

🔍 Inspect:
https://vercel.com/jerome/jeromefitzgerald/DsgUSYxm198uxfGbMbsUgGodadZ2

View Workflow Logs

It is a bit odd, as I feel if the pnpm update happens on a non-CI machine its gets bloated.
And then trimmed in a CI environment.
Something to keep an eye on is all.


[🐞] Type error with async component$ render function

Which component is affected?
Qwik Runtime
Describe the bug
When using an async render function (which the docs imply should be supported here) TypeScript reports an error with the return type. However, the code itself compiles and runs as expected with the initial rendering being blocked while the promise is resolved.
Argument of type '() => Promise<JSX.Element>' is not assignable to parameter of type 'OnRenderFn<{}>'.
  Type 'Promise<Element>' is missing the following properties from type 'JSXNode<any>': type, props, immutableProps, children, and 2 more.(2345)

Reproduction
https://stackblitz.com/edit/qwik-starter-h1dy5b?file=src%2Froutes%2Findex.tsx
Steps to reproduce
Create a new Qwik project
Change a component to async render
Type error appears.
System Info
  System:
    OS: macOS 12.3
    CPU: (8) arm64 Apple M1 Pro
    Memory: 115.02 MB / 16.00 GB
    Shell: 5.8 - /bin/zsh
  Binaries:
    Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node
    Yarn: 1.22.19 - /opt/homebrew/bin/yarn
    npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm
  Browsers:
    Chrome: 113.0.5672.126
    Firefox: 113.0.2
    Safari: 15.4

Additional Information
No response

@zanettin, I believe your wrote this doc that demonstrates the issue in question (Advanced/ESLint).  Is the async function in the example erroneous? I was under the impression that components had to be synchronous.

Hi @ulic75 and @rshackleton 👋
thanks for pinging me! i have the eslint examples from the unit test file and i guess that during my local tests TSC was not working correctly. That's why these examples are on the page. i can't see any cases on the code base where this is used by now. maybe it was once an option.
hope @manucorporat can bring in a bit light to this. i can't tell if this is just an TS typing issue or smth that is technically not/no longer possible tbh

We dont allow to return a promise in component$ on purpose, this is not an issue. after await of reactivity would be broken, leaving developers confused why the component is not rerendering when the state changes.

We might need to fix the docs, the render is async, but the components must return some JSX syncronously.
It's possible to do this:
<div>{promise}</div>


feat(parameters): add param set generation

What does this change

Adds Parameter Set generation cmds/logic
Refactors previous generation logic into common code and credential-/parameter-specific logic

TODO:

[x] add/update documentation

What issue does it fix
Closes https://github.com/deislabs/porter/issues/1073
Contributes towards https://github.com/deislabs/porter/issues/1053
Notes for the reviewer
Depends on https://github.com/deislabs/porter/pull/1068
For changes separate from https://github.com/deislabs/porter/pull/1068, see the following commit: https://github.com/deislabs/porter/pull/1074/commits/1fbc86917bbc2e42a68daf5f4eb2a5e83874dfe6
Checklist

[x] Unit Tests
[x] Documentation TODO
[x] Schema (porter.yaml) N/A

Oops, botched the rebase on this branch; created a new PR in https://github.com/deislabs/porter/pull/1078


Switch arg parsing to clap v3

Clap 3 has been released 🥳

Had to rename the short bump hook profile flag to cargo bump -H <profile> to make it work, I'm not sure how much of a breaking problem that is...

The recent change makes the bump arguments version, auto, major, minor, patch part of a required bump-spec group - now exactly one of them is required to be given when invoking cog bump which should make the usage and errors more obvious.


Azure AD copy fails to download

trying to download from
https://devicesamd.dfs.core.windows.net/orpheusengagement/Users/MikeG/MEMORY_VR_2.198.0_0x3b.zip
details:
{
"message": ""UnexpectedQuit""
}

@kfroe Could you copy the azcopy command and try it with the AzCopy cmd tool and send us the output + the log? You can get AzCopy cmd tool here.
When you run the azcopy command using the cmd tool, please add one argument --output-type=json at the end to help us troubleshoot. We internally rely on the json output to determine the job status when it finishes.

Closing due to lack of response. If you are still having issue, please open a new one instead.


Unresponsive icons

Icons are either small or with smaller gesture area making them unresponsive.
Suggested solution:

Make entire cell touchable
Make icons a bit larger
Make touchable area a bit larger

Update 10 Apr 2021
Removed GestureDetector in favour of IconButton meanwhile retaining the icon size to whatever is defined by developer or default value is used, however, doubling the tap area.
**Note: This update is scheduled to be released in upcoming version of Fluttable in the first half of this week.


multiplicative noise

fig E1 shows the "no noise" setting.
there is no parameter in 19 that allows us to rescale noise.
i think we need a sigma before I_D, and let sigma --> 0, right?
otherwise, i don't know what the "noise free" setting means?

oh, actually 19 & 20 have no noise at all.
So 19 and 20 in E1 just has same noise-free setting being generated for 100 & 1000 points.
Maybe I should re-generated E1 by 1000 points only for both settings, and point out those two are special cases without noise?

i don't think it is acurate to say that 19 has no noise.
the variance on y given x is noise.
20 is "all noise"
20 might should be called "Multimodal Independence", rather than just
"Independence"?
On Fri, Dec 30, 2016 at 7:03 PM, cshen6<EMAIL_ADDRESS>wrote:

oh, actually 19 & 20 have no noise at all.
So 19 and 20 in E1 just has same noise-free setting being generated for
100 & 1000 points.
Maybe I should re-generated E1 by 1000 points only for both settings, and
point out those two are special cases without noise?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/MGC/issues/189#issuecomment-269836841, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACjcioFljynPor6eFk7RXAWx1MB2AL-ks5rNZvngaJpZM4LYYy0
.

--
the glass is all full:  half water, half air.
neurodata.io, jovo calendar
https://calendar.google.com/calendar/embed?src=joshuav%40gmail.com&ctz=America/New_York
starting in 2017, i will be responding to emails approximately weekly,
so that i can focus more on the people around me.
thank you for your understanding.

i don't think it is acurate to say that 19 has no noise.
the variance on y given x is noise.
20 is "all noise"
20 might should be called "Multimodal Independence", rather than just
"Independence"?
On Fri, Dec 30, 2016 at 7:03 PM, cshen6<EMAIL_ADDRESS>wrote:

oh, actually 19 & 20 have no noise at all.
So 19 and 20 in E1 just has same noise-free setting being generated for
100 & 1000 points.
Maybe I should re-generated E1 by 1000 points only for both settings, and
point out those two are special cases without noise?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/MGC/issues/189#issuecomment-269836841, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACjcioFljynPor6eFk7RXAWx1MB2AL-ks5rNZvngaJpZM4LYYy0
.

--
the glass is all full:  half water, half air.
neurodata.io, jovo calendar
https://calendar.google.com/calendar/embed?src=joshuav%40gmail.com&ctz=America/New_York
starting in 2017, i will be responding to emails approximately weekly,
so that i can focus more on the people around me.
thank you for your understanding.

yes you are right. Because of that I thought there is no need to add another white noise to type 19; also type 19 at its current form is the same as that used in HHG.
And why do you think multimodal independence is better? After all, independence is a concept between two modalities?

19: i'm not saying add anything to 19.  i'm saying make it more explicit
that there is a variance term, and when we plot the noise free version, let
the various be zero.  otherwise, it is non-sense. if you refuse, i'm happy
to fix it myself.
20: because it is more specific.  for example, joint normal could also be
independent, its just not. i see no downside to being more clear?
On Tue, Jan 3, 2017 at 1:28 AM, cshen6<EMAIL_ADDRESS>wrote:

yes you are right. Because of that I thought there is no need to add
another white noise to type 19; also type 19 at its current form is the
same as that used in HHG.
And why do you think multimodal independence is better? After all,
independence is a concept between two modalities?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/MGC/issues/189#issuecomment-270057792, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACjcjYYyGGttq60DOyTRPqnVYaJ-_0wks5rOeqEgaJpZM4LYYy0
.

--
the glass is all full:  half water, half air.
neurodata.io, jovo calendar
https://calendar.google.com/calendar/embed?src=joshuav%40gmail.com&ctz=America/New_York
starting in 2017, i will be responding to emails approximately weekly,
so that i can focus more on the people around me.
thank you for your understanding.

ok, I will just let noise-free version to be variance 0 then.
and will change name of 20 accordingly.
once done I will close the issue.

ok updated visualization figure first.
However, for type 20, "MultiModal independence" seems too long, see first figure in appendix...
As to  type 19, the noise-free version is just the linear relationship. Such a noise-free version may not be very meaningful?
If you are ok with both, I will change the name & function type in a few other appendix places then.

20: i think it is perfect as is.  in appendix D and Fig E1, it includes the
word multimodal, and the others it just says independent.
19: crap, when the variance is zero, because it is multiplicative, y--> 0
always.  i kinda hoped that the black dots would make a cross.
in fact, i have no idea how you got that straight line like that?
if we add a +/- 1 multiplicative term, so that y is either x or -x, and
then scale the variance.
something like:
y = (w*u + (1-w)*b)*x
where b is 50% +1 and 50% -1, and w \in (0,1), then we can add noise by
making w bigger?
On Wed, Jan 4, 2017 at 1:15 AM, cshen6<EMAIL_ADDRESS>wrote:

ok updated visualization figure first.
However, for type 20, "MultiModal independence" seems too long, see first
figure in appendix...
As to type 19, the noise-free version is just the linear relationship.
Such a noise-free version may not be very meaningful?
If you are ok with both, I will change the name & function type in a few
other appendix places then.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/MGC/issues/189#issuecomment-270302021, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACjctvzLcN-4aTypJ3hKp0ZB5KMpjnlks5rOzkXgaJpZM4LYYy0
.

--
the glass is all full:  half water, half air.
neurodata.io, jovo calendar
https://calendar.google.com/calendar/embed?src=joshuav%40gmail.com&ctz=America/New_York
starting in 2017, i will be responding to emails approximately weekly,
so that i can focus more on the people around me.
thank you for your understanding.

yes you are right; y=0 always under zero variance.
So it will be a single point at (0,0) always, not a line nor a cross.
I can make it a single point then, for the noise-free version (just like the uncorrelated binomial, where we only have three points for the noise-free version). Is that ok with you?
The weighted version will become a mixture of multiplicative noise and Gaussian distribution, which is no longer the original multiplicative noise...

no dude, seriously?
x would still vary, y would always be zero, so it would be a horizontal
line at zero.
that's why i don't understand how you got a line at x=y, its like you set
the mean of u to be 1, and the variance zero?
all i'm saying is that you need to have a real "noise free" and "noisy"
version, where the equations and the plots agree,
and the equations have a parameter that you change to increase the amount
of noise.
i don't really care what it is, but the current thing is non-sense.
if you want to set the mean of u=1 and variance zero for noise free, and
then for noisy, set the mean of u=0 and make variance 1, i'm fine with
that.
or, if you set the mean to be +/-1 always, then there is only a variance
term.  and, the distribution of y when variance > 0 is the same except for
a scale term that is irrelevant anyway i think?
On Wed, Jan 4, 2017 at 9:31 AM, cshen6<EMAIL_ADDRESS>wrote:

yes you are right; y=0 always under zero variance.
So it will be a single point at (0,0) always, not a line nor a cross.
I can make it a single point then, for the noise-free version (just like
the uncorrelated binomial, where we only have three points for the
noise-free version). Is that ok with you?
The weighted version will become a mixture of multiplicative noise and
Gaussian distribution, which is no longer the original multiplicative
noise...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/MGC/issues/189#issuecomment-270383596, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACjcp5Un1EyiFp6Psk045KD8B-Xwlr6ks5rO61JgaJpZM4LYYy0
.

--
the glass is all full:  half water, half air.
neurodata.io, jovo calendar
https://calendar.google.com/calendar/embed?src=joshuav%40gmail.com&ctz=America/New_York
starting in 2017, i will be responding to emails approximately weekly,
so that i can focus more on the people around me.
thank you for your understanding.

yeah you are absolutely right. Not sure what happened to my mind these two
days....
ok I will just plot x normal vs y 0 for the noise-free version.
once updated I will let you know and close this issue.
On Wed, Jan 4, 2017 at 10:49 AM, joshua vogelstein<EMAIL_ADDRESS>
wrote:

no dude, seriously?
x would still vary, y would always be zero, so it would be a horizontal
line at zero.
that's why i don't understand how you got a line at x=y, its like you set
the mean of u to be 1, and the variance zero?
all i'm saying is that you need to have a real "noise free" and "noisy"
version, where the equations and the plots agree,
and the equations have a parameter that you change to increase the amount
of noise.
i don't really care what it is, but the current thing is non-sense.
if you want to set the mean of u=1 and variance zero for noise free, and
then for noisy, set the mean of u=0 and make variance 1, i'm fine with
that.
or, if you set the mean to be +/-1 always, then there is only a variance
term. and, the distribution of y when variance > 0 is the same except for
a scale term that is irrelevant anyway i think?
On Wed, Jan 4, 2017 at 9:31 AM, cshen6<EMAIL_ADDRESS>wrote:

yes you are right; y=0 always under zero variance.
So it will be a single point at (0,0) always, not a line nor a cross.
I can make it a single point then, for the noise-free version (just like
the uncorrelated binomial, where we only have three points for the
noise-free version). Is that ok with you?
The weighted version will become a mixture of multiplicative noise and
Gaussian distribution, which is no longer the original multiplicative
noise...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/MGC/issues/189#issuecomment-270383596,
or mute
the thread
<https://github.com/notifications/unsubscribe-auth/
AACjcp5Un1EyiFp6Psk045KD8B-Xwlr6ks5rO61JgaJpZM4LYYy0>

.

--
the glass is all full: half water, half air.
neurodata.io, jovo calendar
<https://calendar.google.com/calendar/embed?src=joshuav%
40gmail.com&ctz=America/New_York>
starting in 2017, i will be responding to emails approximately weekly,
so that i can focus more on the people around me.
thank you for your understanding.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/MGC/issues/189#issuecomment-270404226, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALX0yxFy0WOOLBT53g8Z2MYc-6MH7We-ks5rO7-fgaJpZM4LYYy0
.

ok updated the appendix figure and appendix set-up...looks right to you this time?

yes, now it looks right.
however, now the no noise case means that x & y are independent.
to me, this is silly.
can we not think of a setting where x & y are not independent even when
there is no noise?
On Wed, Jan 4, 2017 at 7:12 PM, cshen6<EMAIL_ADDRESS>wrote:

ok updated the appendix figure and appendix set-up...looks right to you
this time?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/MGC/issues/189#issuecomment-270525093, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACjchryPNicp-94RURFtVZ8V0JRgMWFks5rPDVigaJpZM4LYYy0
.

--
the glass is all full:  half water, half air.
neurodata.io, jovo calendar
https://calendar.google.com/calendar/embed?src=joshuav%40gmail.com&ctz=America/New_York
starting in 2017, i will be responding to emails approximately weekly,
so that i can focus more on the people around me.
thank you for your understanding.

well, the multiplicative noise is y=ux, where x is normal and u is normal. We should keep this form in both 1-d and h-d, so it is the same as Gabor's trial.
So what about just set y=ux+ \epsilon? This is in-accordance with all the other noise settings.
The only downside is that the visualization figure of noise vs noise-free version of type 19 will still be very similar to each other. But that is not a big problem from my view. Sounds good with you?

ok, I have updated the visual plot and tex write-up of type 19, for y=ux+ \epsilon.
Hopefully you are ok with it, so we can make this issue done :-)

I get your point.
From my view, noise does not matter much, and is merely a way to better distinguish different methods...
But let us put the issue here for now, and discuss post-submission.

still, we should skype...
On Thu, Jan 5, 2017 at 8:03 PM, cshen6<EMAIL_ADDRESS>wrote:

I get your point.
From my view, noise does not matter much, and is merely a way to better
distinguish different methods...
But let us put the issue here for now, and discuss post-submission.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/MGC/issues/189#issuecomment-270803641, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACjckduwNeu_9HtKNo1DfXKN4jOyvqMks5rPZL4gaJpZM4LYYy0
.

--
the glass is all full:  half water, half air.
neurodata.io, jovo calendar
https://calendar.google.com/calendar/embed?src=joshuav%40gmail.com&ctz=America/New_York
starting in 2017, i will be responding to emails approximately weekly,
so that i can focus more on the people around me.
thank you for your understanding.

corrected type 4 \epsilon, type 19 text back to previous version.
Visualization figure updated to only have black points for type 19 & 20, with captions saying they do not have the noise parameter c such that we only plot black points for them

yay!!!!
i'm offline for the next 25 hours.
if you can answer carey's question before then, i'll be excited to read it
when i get back online!
On Fri, Jan 6, 2017 at 7:21 PM, cshen6<EMAIL_ADDRESS>wrote:

corrected type 4 \epsilon, type 19 text back to previous version.
Visualization figure updated to only have black points for type 19 & 20,
with captions saying they do not have the noise parameter c such that we
only plot black points for them
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/neurodata/MGC/issues/189#issuecomment-271045210, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACjclQOOwtyf2utr4HnbtoFxZS--bpjks5rPtpwgaJpZM4LYYy0
.

--
the glass is all full:  half water, half air.
neurodata.io, jovo calendar
https://calendar.google.com/calendar/embed?src=joshuav%40gmail.com&ctz=America/New_York
starting in 2017, i will be responding to emails approximately weekly,
so that i can focus more on the people around me.
thank you for your understanding.


Internal server error on searching golang.org/x/tools/cmd/vet

Internal server error during search:
https://godoc.org/?q=golang.org%2Fx%2Ftools%2Fcmd%2Fvet

I cannot reproduce this failure, can you still see it?

Seems gone


Change tab width for .go files to 4

I thing 8-wide tabs are kind of archaic and inconsisten with template files which already use 4-wide.
Also did some misc cleanups in the .editorconfig files.

Looks like gofmt hardcodes tab width to 8, so I'm not sure it's good to change it because if gofmt outputs spaces for some cases (I don't know) those would be misaligned.

Based on https://github.com/golang/go/commit/25b51810014cefb8dba31321fcf40eb1a008fc3e, I think it's fine we change this. It says tab width has no effect on alignment of:

Since "columns of alignment" are terminated whenever indentation changes from one line to the next, alignment with spaces will work independent of the actually chosen tab width


problem when generating program commitee

When the first author of the entries in a block misses the institution field, the entire block is not displayed (i.e., it is not reported in the latex file).
@rswilkens : can you check with the responsible(s) of the program committee (I imagine the Program Chair) to check this missing information?
@zhzhang : anyway, I suggest that, when the institution is missing, the software should not display:
John Doe,
but
John Doe (without the comma).
There may be a rare case that some institutions are actually missing....

I'll check with the PCs, but this might be critical for the workshops. The
institution field is from peoples' profiles on OR. In sum, will it trigger
an error every time someone doesn't fill in this field?
On Fri, Mar 18, 2022 at 11:39 AM Danilo Croce @.***>
wrote:

When the first author of the entries in a block misses the institution
field, the entire block is not displayed (i.e., it is not reported in the
latex file).
@rswilkens https://github.com/rswilkens : can you check with the
responsible(s) of the program committee (I imagine the Program Chair) to
check this missing information?
@zhzhang https://github.com/zhzhang : anyway, I suggest that, when the
institution is missing, the software should not display:
John Doe,
but
John Doe (without the comma).
There may be a rare case that some institutions are actually missing....
—
Reply to this email directly, view it on GitHub
https://github.com/rycolab/aclpub2/issues/42, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL223XS3SRCWCRNLBNVJBL3VARMOPANCNFSM5RBOPFLA
.
You are receiving this because you were mentioned.Message ID:
@.***>

No, I just suggest removing the comma.
It is then the responsibility of the volume editors (i.e., the organizers of each workshop) to check this information and eventually integrate it by hand...
However, I suggest adding the Institution in OpenReview as a required input.

@zhzhang Unfortunately, when the institution of the first entry of a group is missing, the group is still not shown


fix: using same labels everywhere

Description
Use the same (case-sensitive) labels everywhere
Issue linked
Close #3184
Checklist

[x] I have visited and read Develop PyMAPDL.
[ ] I have tested my changes locally
[ ] I have added necessary documentation or updated existing documentation.
[x] I have followed the PyMAPDL coding style guidelines.
[ ] I have added appropriate unit tests that also ensure the minimal coverage criteria.
[x] I have reviewed my changes before submitting this pull request.
[x] I have linked the issue or issues that are solved to the PR if any.
[x] I have assigned this PR to myself.
[ ] I have marked this PR as draft if it is not ready to be reviewed yet.
[x] I have made sure that the title of my PR follows Commit naming conventions (e.g. feat: adding new MAPDL command)

I knew I was missing something: https://github.com/ansys/pymapdl/pull/3197#issuecomment-2182230068


docs(*): fix plunkr URL

The plunker owner should update it to remove the traceur script load as it isn't needed. Keeping up with the parade of alphas is a different matter ;-)

closed by 8519574

@wardbell i'll update the plunkr.


keyd interferes with xkb option "grp_led:scroll"

When keyd is running and matched on my keyboard, the xkb option "grp_led:scroll" (see xkeyboard-config(7)) does not work well. When I switch to another layout using the keyboard, the layout changes but the led does not change accordingly.
I've reproduced the problem in a qemu vm from a clean install:

Install Ubuntu 23.04
apt install kde-plasma-desktop, logout from Gnome and login to KDE
From KDE System Settings, Input Devices, Keyboard

on the Layouts tab, add English (US) and French (Canada)
on the Advanced tab

enable "Switching to another layout"/"Win+Space"
enable "Use keyboard LED to show alternative layout"/"Scroll Lock"

Open a terminal and run the following command to monitor the scroll lock led:
watch -n0.3 -d 'grep -H . /sys/class/leds/input1::scrolllock/brightness; xset -q | grep Lock'
Open another terminal, switch keyboard layouts a few times by pressing Win+Space
In each layout,

type the '/' key to confirm that the layout is changed (result is '/' or 'é')
look in the terminal running watch, confirm that the scroll lock led is on according to sysfs and xset when the second layout ("ca") is active

apt install git build-essential
Clone, compile and install keyd (reproduced with commit eeea96a)
Create /etc/keyd/default with the following contents:

[ids]
*
[main]

Start keyd (systemctl start keyd.service)
Change the keyboard layout again by pressing Win+Space. Look at the terminal running watch, the output of xset is as expected but the scroll lock led file in sysfs is not updated accordingly. This is the problem. On a real machine, it manifests itself as the physical keyboard led not being on.

Extra observations
When changing the keyboard layout using the task bar layout indicator, the problem does not occur.
When running keyd with no configuration file, the problem does not occur. When running keyd with the minimual configuration file specified above, the problem does occur. So it seems the problem only occurs when keyd matches on the keyboard.
Instead of KDE, I have also reproduced the problem using openbox, i3 and twm.
In those cases, I set the keyboard configuration using
setxkbmap -layout us,ca -option -option grp:win_space_toggle -option grp_led:scroll

The problem does not reproduce with gnome-x11. According to this ticket, "mutter implements some custom mechanism for switching keyboard layouts". Maybe it's related to that. The problem also does not reproduce under gnome-wayland and plasma-wayland.
I have also tried using evremap instead of keyd and the same problem occurs. I guess both utilities work in a similar way.
The issue I'm reporting is probably the same problem that was reported in the following comment:
https://github.com/rvaiya/keyd/issues/305#issuecomment-1480210485
Can you narrow down if this is a problem with how evdev is used in keyd, or a problem in evdev itself or Xorg?

I have created a small screen recording to show the issue:
https://github.com/rvaiya/keyd/assets/254681/9edfb3ce-33ad-44ac-a342-4a5f985c5af1
00:38 Scroll lock led changes according to keyboard layout
01:00 Starting keyd
01:26 Scroll lock led no longer changes when changing the layout using win+space keyboard shortcut
01:44 Scroll lock led changes when using taskbar layout indicator
02:05 Stopping keyd
02:14 Scroll lock led changes according to keyboard layout again

Experiencing the same issue when changing keyboard layouts with setxkbmap and the grp_led:scroll option. (openbox)

Thanks for the detailed reproduction steps. I don't have the time to set up  a virtual machine at the moment, but running setxkbmap -layout us,ca -option -option grp:win_space_toggle -option grp_led:scroll on my local box seems to produce the desired result. What version of keyd are you using (keyd -v)? Does this problem persist when building the latest one from source?

Nevermind, I was indeed able to reproduce it. My suspicion is that the compositor/X server sets the LED status using evdev and can't wrest control from the keyd virtual device. Assuming this is indeed the case, I'm not sure it will be possible to fix, as uinput doesn't provide a way to capture the EV_LED event (as far as I can tell).

I did a bit of kernel diving and it appears it is indeed possible to capture EV_LED events from userspace. This should work in the latest commit. Can you give it a go?

I just tested at commit 23f329a in my normal environment (openbox) and the keyboard led changes according to the layout, as expected. Thank you for resolving this issue.

Unfortunately, I'm facing this issue on FreeBSD 14.1 with all latest versions; using Xfce.
/usr/local/etc/keyd/menu.conf
[ids]
*

[main]
meta = overload(meta, A-f1)

/usr/local/etc/X11/xorg.conf.d/xkb.conf
Section "InputClass"
	Identifier "MyXkbRules"
	MatchIsKeyboard "true"
	MatchDriver "libinput"
	Option "XkbModel" "pc104"
	Option "XkbLayout" "us,ru"
	Option "XkbOptions" "shift:both_capslock_cancel,grp:caps_toggle,grp_led:scroll"
EndSection

Meaning of my xkb setup:

CapsLock: toggle us/ru layout, use Scroll LED as indicator;
LShift + RShift: switch Caps mode on, use Caps LED as indicator;
2.1. Any Shift: switch Caps mode off.

When keyd is running, the effect on that is the following:

CapsLock still toggles layout, but the indicator (Scroll LED) not working;
Caps mode and LED aren't working entirely.

Everything starts working again as soon as keyd is stopped. keyd itself working great.
Off-topic: NumLock and its LED are always works.

I'm not sure whether I should create a new issue on this matter, and whether @rvaiya will be notified now, so I'm tagging them. Thank you.


Clarify what "API endpoint" is and where to get it

The instructions and code snippet says ....
Replace with valid values
ENDPOINT = ""
training_key = ""
prediction_key = ""
prediction_resource_id = ""
But ...
Nowhere do the instructions explain what the "API endpoint " is , and where to get it.
There are several endpoints for different things ;- resource ?? resource group ?? prediction endpoint ?? training endpoint ??
Which is the "API endpoint " ?
That and other vague statements makes these instructions difficult for new comers to Azure.

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

ID: 4f6c3f20-25a4-bc19-0cb6-377eff01b00e
Version Independent ID: 02d76c7b-cffa-c94f-2298-ba7e506d4f79
Content: Quickstart: Image classification with Custom Vision client library or REST API - Azure Cognitive Services
Content Source: articles/cognitive-services/Custom-Vision-Service/quickstarts/image-classification.md
Service: cognitive-services
Sub-service: custom-vision
GitHub Login: @PatrickFarley
Microsoft Alias: pafarley

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

Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
@PatrickFarley Hello, could you please check on this issue and update the document ? Thanks.

I've added text to further clarify that it is the training resource endpoint.
#please-close


ios15 截图失败

iOS15截图失败了，有大佬遇到过吗

IOS14.6 有滚动条的H5页面截图不全，上方会有空白

iOS15.6生成二维码失败

Ios15.6 failed to generate QR code

Check "-apple-system" in "Font Family". In iOS 15, using "-apple-system" will cause canvas rendering to fail.

@foooooouny Can you provide a repro of this in jsfiddle?

ios15 生成失败+1

ios15 生成失败+1

font-family: Helvetica, Tahoma, Arial, 'PingFang SC', 'Hiragino Sans GB', 'Heiti SC', STXihei, 'Microsoft YaHei',
SimHei;

ios15 生成失败+1

font-family: Helvetica, Tahoma, Arial, 'PingFang SC', 'Hiragino Sans GB', 'Heiti SC', STXihei, 'Microsoft YaHei',
SimHei;

same, how to fix?

I am unable to repro this on an iOS15 simulator #2645

Can you take a look at IOS14, I see it render not correct the width of elements, it's here https://codepen.io/dinhvandai63/pen/OJmQVRg


Haddock loses section markers with named-chunks

For this input:
module A (
 -- * Section 1
 -- * Section 2
 foo
 ) where

-- | foo is True
foo = True

haddock nicely produces  a document with two section names (Section 1 and 2) as expected. (Invoked as haddock --html a.hs)
However, if one inserts a "named-chunk" in between section headers, like this:
module A (
 -- * Section 1
 -- $doc
 -- * Section 2
 foo
 ) where

-- | foo is True
foo = True

{- $doc
   This is a named doc
-}

Then the generated html no longer has Section 2 in it. (Same invocation: haddock --html a.hs)

Interesting, which haddock version do you use?
Levent Erkök<EMAIL_ADDRESS>schrieb am Sa., 7. Apr. 2018, 22:05:

For this input:
module A (
-- * Section 1
-- * Section 2
foo
) where
-- | foo is True
foo = True
haddock nicely produces a document with two section names (Section 1 and
2) as expected. (Invoked as haddock --html a.hs)
However, if one inserts a "named-chunk" in between section headers, like
this:
module A (
-- * Section 1
-- $doc
-- * Section 2
foo
) where
-- | foo is True
foo = True
{- $doc
This is a named doc
-}
Then the generated html no longer has Section 2 in it. (Same invocation: haddock
--html a.hs
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/haskell/haddock/issues/797, or mute the thread
https://github.com/notifications/unsubscribe-auth/AByiiUbNGTDJ6lnnlRjywHqHT79_aYHOks5tmRwQgaJpZM4TLOzb
.

$ haddock --version
Haddock version 2.19.0, (c) Simon Marlow 2006
Ported to use the GHC API by David Waern 2006-2008

This seems to be a GHC bug. For
Your example
module A (
 -- * Section 1
 -- $doc
 -- * Section 2
 foo
 ) where

-- | foo is True
foo = True

{- $doc
   This is a named doc
-}

with
$ ghc -ddump-parsed-ast -haddock Bug797.hs

gives this syntax tree for the export list:
 (HsModule
  (Just
   ({ html-test/src/Bug797.hs:1:8-13 }
    {ModuleName: Bug797}))
  (Just
   ({ html-test/src/Bug797.hs:(1,15)-(7,2) }
    [({ html-test/src/Bug797.hs:2:2-15 }
      (IEGroup
       (1)
       (HsDocString
        {FastString: " Section 1"})))
    ,({ html-test/src/Bug797.hs:(4,2)-(5,15) }
      (IEDocNamed
       "doc"))
    ,({ html-test/src/Bug797.hs:6:2-4 }
      (IEVar
       ({ html-test/src/Bug797.hs:6:2-4 }
        (IEName
         ({ html-test/src/Bug797.hs:6:2-4 }
          (Unqual
           {OccName: foo}))))))]))

Note that  "Section 2" is missing.
Changing the input to:
module Bug797 (
 -- * Section 1
 -- $doc

 -- * Section 2
 foo
 ) where
...

results in
 (HsModule
  (Just
   ({ html-test/src/Bug797.hs:1:8-13 }
    {ModuleName: Bug797}))
  (Just
   ({ html-test/src/Bug797.hs:(1,15)-(7,2) }
    [({ html-test/src/Bug797.hs:2:2-15 }
      (IEGroup
       (1)
       (HsDocString
        {FastString: " Section 1"})))
    ,({ html-test/src/Bug797.hs:3:2-8 }
      (IEDocNamed
       "doc"))
    ,({ html-test/src/Bug797.hs:5:2-15 }
      (IEGroup
       (1)
       (HsDocString
        {FastString: " Section 2"})))
    ,({ html-test/src/Bug797.hs:6:2-4 }
      (IEVar
       ({ html-test/src/Bug797.hs:6:2-4 }
        (IEName
         ({ html-test/src/Bug797.hs:6:2-4 }
          (Unqual
           {OccName: foo}))))))]))
...

Now both sections and the named doc is present in the AST.

See here:
https://github.com/ghc/ghc/blob/8b823f270e53627ddca1a993c05f1ab556742d96/compiler/parser/Parser.y#L834-L837
GHC tries to parse a full named doc section. All we want it to parse is just the reference to the named doc section here.

Levent, are you interested in taking the lead in fixing this issue upstream?

@alexbiehl Thanks for the analysis!
Filed here as a GHC issue: https://ghc.haskell.org/trac/ghc/ticket/15015#ticket

@sjakobi IIRC you are in that area currently, would you like to take the lead here?

I'm quite busy until April 20, but I'll take a look then.

I'm afraid I still haven't looked into this. Admittedly I haven't had any contact with ghc's happy logic so far.
@harpocrates: You have more experience in this area. Is this something you would like to take a stab at?

Yeah, eventually... 😄
I know what the issue is though, so perhaps that's worth elaborating a bit more. The problem is actually at the token level. There is no lexical distinction drawn between a reference to a named chunk in an export list and an actual named chunk - both use ITdocCommentNamed. We should probably have a ITdocCommentReference which expects only a name (compared to ITdocCommentNamed which expects a name followed by a paragraph of comments).

Can the former happen in a haddock comment? I.e. is it valid to define a named chunk within a haddock comment, like this:
-- | Stuff
-- $doc
-- Is this within the definition of the named chunk \$doc?

It sounds like this should not be the case, otherwise the syntax would be ambiguous.


Modifying video player for live event to allow using youtube

Modifying video player for live event to allow using youtube
Changes

Modifed cfgov/jinja2/v1/_includes/macros/video-player.html to determine video type solely based on the URL.

Modified cfgov/v1/models/learn_page.py validation regex and help text to acommodate allowing youtube.

Testing

Create an event page.
Modify the event date / times to create an live event.
Enter in a youtube live event url (https://www.youtube.com/embed/TY8bZHo6iRg).
Preview.
Play the event and verify it plays, stops, and restarts correctly. Check the console for errors.
Edit the event again in Wagtail.
Enter in a Ustream event (https://www.ustream.tv/embed/6540154?html5ui).
Preview.
Play the event, you should be redirected to Ustream to view the event.
Visit http://localhost:8000/about-us/events/archive-past-events/ and verify the archived events play.

Screenshots

Notes

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the front end playbook
[ ] Passes all existing automated tests
[ ] New functions include new tests
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged
[ ] Visually tested in supported browsers and devices
[ ] Project documentation has been updated
[ ] Reviewers requested with the Assignee tool :arrow_right:

Not directly related to this PR, but this is not the ideal way to learn that I have to save an event draft before the preview will work:

When I'm using a Ustream URL the player has the CFPB logo before I click play. When using YouTube, it doesn't. Is that specific the services/setup that happens outside of cfgov-refresh?

Yeah, we wrote code to attempt to grab the high res image for youtube if available. If it isn't, then it just falls back to the default CFPB image.  When didn't do that for Ustream, it always uses the default image.

Not directly related to this PR, but this is not the ideal way to learn that I have to save an event draft before the preview will work:

@willbarton, yeah, I'll looking into to that error.


Build(deps-dev): Bump @typescript-eslint/parser from 5.12.0 to 5.12.1 (#2834)

Pull request opened by the merge tool on behalf of #2834

Merged in f303c78f0de6232138692a926f20ed1df3927f1a


As a Content Creator I want to arrange the order of Arguendo responses manually so I can control the order

not time critical, but this shouldn't be a hard fix.

AT record


propagate correlation fields locally, but not over the wire

You can now use the spring.sleuth.local-keys property to pass a list keys that will be propagated locally but will not be propagated over the wire.
Original background below:

Some people want to add "extra fields" but at process scope, and not propagated downstream. Currently, the approach to implementing this is to add them as "redacted" https://github.com/openzipkin/brave/tree/master/brave#redacting-fields
This serves use cases like log context synchronization for totally trusted applications. What I mean by trusted is that applications should be as careful about what to put in extra fields as they are about MDC, as anything in the classpath can read them.
Incidentally, this was added for sleuth, requested by @alonbl but I don't think we hooked it together, yet. hence the issue.
https://github.com/openzipkin/brave/tree/master/brave#redacting-fields
https://github.com/openzipkin/brave/pull/931

You can now use the spring.sleuth.local-keys property to pass a list keys that will be propagated locally but will not be propagated over the wire.

Thank you all! Much appreciated.


bump to latest nightly

Just because it has been a while since the last bump.

@bors r+

:pushpin: Commit c2e4c877c5c47a20cc66de848d6eb51b0f478dd9 has been approved by RalfJung

:hourglass: Testing commit c2e4c877c5c47a20cc66de848d6eb51b0f478dd9 with merge 3899dce3b6be8e5f523288b76e7a22c5ce10365e...

:sunny: Test successful - checks-travis, status-appveyor
Approved by: RalfJung
Pushing 3899dce3b6be8e5f523288b76e7a22c5ce10365e to master...


How to disable Mask

Hi! I'm using the lib, and want to have some functionality of Youtube. I  open the modal, but I want to click a video behind the mask.
There's a option to disable the mask, in order to touch thinks behind it?

Since the mask is a React Native Modal, we are unable to click any elements that are located behind it.


Why does the expression of the parent rule become invalid when the parent rule has child rules?

Parent rule and child rule. When the parent rule has "Expression", the expression of the parent rule should be run first. When the parent rule is "false", all child rules will not be run. Why does the expression of the parent rule become invalid when the parent rule has child rules? What can I do to achieve this result?
The result I want in the illustration is that the rule is false

@jing1345061 RulesEngine only allows leaf rules to have expression. As such passing expression to parent rule is invalid and is ignored.

If RulesEngine can have an options to also allow parent expression, that will be able to support nest if else and to make the expressions much simpler in some situations.


[feature] Support line feed char "\n" in the "formatter function".

Summary
Support the line feed "\n" in the formatter function. Without this PR, Echarts will display blank when use '\n' in the formatter function.
In the toString util function, every '\n' will be removed. This PR will keep '\n' in the return string of the formatter function.
Test plan
Use the line feed char '\n' in the formatter function.
Without this PR, Echarts is blank.
With this PR, rendering well with line feed where you want.
<RNEChartsPro
    width="100%"
    height={300}
    option={{
      xAxis: {
        type: 'category',
        data: ['Mon', 'Tue', 'Wed', 'Thu', 'Fri', 'Sat', 'Sun'],
        axisLabel: {
          formatter(value) {
            return value + '\n' + '(week)';
          }
        }
      },
      yAxis: {
        type: 'value'
      },
      series: [
        {
          data: [150, 230, 224, 218, 135, 147, 260],
          type: 'line'
        }
      ]
    }}
/>

Compatibility
For both Android and iOS.

This PR is closed and replaced with #41.


redis_events does not deliver webhooks

Given I configure an ACA-Py (v. 0.10.3) agent with the redis_events plugin (v. 0.1.0)
Given I have following ACA-Py configuration :
auto-provision: true

admin: [<IP_ADDRESS>, 3001]
admin-insecure-mode: true

inbound-transport:
  - [redis_events.v1_0.redis_queue.inbound, redis, 0]
outbound-transport: redis_events.v1_0.redis_queue.outbound
endpoint:
  - http://relay:8071

plugin:
  - redis_events.v1_0.redis_queue.events
plugin-config: plugins-config.yml

no-ledger: true

debug-connections: true
auto-accept-invites: true
auto-accept-requests: true
auto-ping-connection: true
auto-respond-messages: true

Given I have following plugin configuration :
redis_queue:
  connection:
    connection_url: "redis://default:test1234@<IP_ADDRESS>:6379"

  inbound:
    acapy_inbound_topic: "acapy_inbound"
    acapy_direct_resp_topic: "acapy_inbound_direct_resp"

  outbound:
    acapy_outbound_topic: "acapy_outbound"
    mediator_mode: false

  event:
    event_topic_maps:
      ^acapy::webhook::(.*)$: acapy-webhook-$wallet_id
      ^acapy::record::([^:]*)::([^:]*)$: acapy-record-with-state-$wallet_id
      ^acapy::record::([^:])?: acapy-record-$wallet_id
      acapy::basicmessage::received: acapy-basicmessage-received
      acapy::problem_report: acapy-problem_report
      acapy::ping::received: acapy-ping-received
      acapy::ping::response_received: acapy-ping-response_received
      acapy::actionmenu::received: acapy-actionmenu-received
      acapy::actionmenu::get-active-menu: acapy-actionmenu-get-active-menu
      acapy::actionmenu::perform-menu-action: acapy-actionmenu-perform-menu-action
      acapy::keylist::updated: acapy-keylist-updated
      acapy::revocation-notification::received: acapy-revocation-notification-received
      acapy::revocation-notification-v2::received: acapy-revocation-notification-v2-received
      acapy::forward::received: acapy-forward-received
    event_webhook_topic_maps:
      acapy::basicmessage::received: basicmessages
      acapy::problem_report: problem_report
      acapy::ping::received: ping
      acapy::ping::response_received: ping
      acapy::actionmenu::received: actionmenu
      acapy::actionmenu::get-active-menu: get-active-menu
      acapy::actionmenu::perform-menu-action: perform-menu-action
      acapy::keylist::updated: keylist
    deliver_webhook: true

Given I start the ACA-Py agent with a --webhook-url parameter pointing to a runnnig mock server.
When the agent accepts a connection request and sends a connection response
Then I do see the webhook messages in redis in the acapy_outbound list (with configured url + '/topic/None' as topic)
Then webhooks are never delivered to the endpoint (the mock server).
Then connection response is never sent and connection stalls in a 'response' state (vs state': 'completed').
Expected : Endpoint does receive webhook post requests (that have a real '/topic/' defined in url and not '/topic/None') AND connection is correctly established.
Note : I did confirm that with this same exact setup, if plugin is not loaded, endpoint does receive webhook post requests with correct topics defined and connection is correctly established  (state': 'completed').
Note : I also did confirm that with this same exact setup, if plugin IS loaded but there is no --webhook-url start argument passed to ACA-Py, then connection is correctly established (state': 'completed')

Ok. I can replicate the issue. I'm not sure if having the webhook url forwarding was ever considered. It wasn't tested with the current setup.
It should be supported though, that's for sure. I'll work on fixing it.

I could replicate the issue but I'm pretty sure this is a configuration issue. Although the documentation and sample plugin-config should be better.
The default webhook event map is in redis_events/v1_0/redis_queue/config.py and is:

EVENT_WEBHOOK_TOPIC_MAP = {
"acapy::basicmessage::received": "basicmessages",
"acapy::problem_report": "problem_report",
"acapy::ping::received": "ping",
"acapy::ping::response_received": "ping",
"acapy::actionmenu::received": "actionmenu",
"acapy::actionmenu::get-active-menu": "get-active-menu",
"acapy::actionmenu::perform-menu-action": "perform-menu-action",
"acapy::keylist::updated": "keylist",
}

But this actually misses a lot of events, hence getting the None topics.
The plugin-config file actually needs a event_webhook_topic_maps section to customize it.
  ### For Event ###
  event:
    event_topic_maps:
      ^acapy::webhook::(.*)$: acapy-webhook-$wallet_id
      ^acapy::record::([^:]*)::([^:]*)$: acapy-record-with-state-$wallet_id
      ^acapy::record::([^:])?: acapy-record-$wallet_id
      acapy::basicmessage::received: acapy-basicmessage-received
      acapy::problem_report: acapy-problem_report
      acapy::ping::received: acapy-ping-received
      acapy::ping::response_received: acapy-ping-response_received
      acapy::actionmenu::received: acapy-actionmenu-received
      acapy::actionmenu::get-active-menu: acapy-actionmenu-get-active-menu
      acapy::actionmenu::perform-menu-action: acapy-actionmenu-perform-menu-action
      acapy::keylist::updated: acapy-keylist-updated
      acapy::revocation-notification::received: acapy-revocation-notification-received
      acapy::revocation-notification-v2::received: acapy-revocation-notification-v2-received
      acapy::forward::received: acapy-forward-received
    event_webhook_topic_maps:
      acapy::basicmessage::received: basicmessages
      acapy::problem_report: problem_report
      acapy::ping::received: ping
      acapy::ping::response_received: ping
      acapy::actionmenu::received: actionmenu
      acapy::actionmenu::get-active-menu: get-active-menu
      acapy::actionmenu::perform-menu-action: perform-menu-action
      acapy::keylist::updated: keylist
      acapy::record::connections::response: acapy-record-connections-response
      acapy::record::connections::request: acapy-record-connections-request
      acapy::record::connections::invitation: acapy-record-connections-invitation
      acapy::record::connections::active: acapy-record-connections-active
    deliver_webhook: true

This config stops the None topic types in the integration tests.
I'm going to improve the documentation and plugin-config sample but I'm pretty confident it is working correctly.

Thank you for the investigation and update.
I tried this updated event_webhook_topic_maps and indeed, the topics are now (mostly) defined (I still have 4 /topic/None entries in acapy_outbound, before it was 8 or 9). BUT ... messages are still stuck in acapy_outbound and still not delivered. Furthermore, this still stops the connexion response message from beeing sent to the second agent.

Could the deliverer not deliver those messages anyway (even if topic is topic/None) ? Its a message with an url and a payload, like any other messages and the url is reachable. Of course the controler would not know what to do with those /topic/None but at least messages would not get stuck in acapy_outbound.
Or even more generaly, why can one single message stuck in acapy_outbound keep the deliverer from delivering all following messages ? Is there an intention behind this ? It seems to be a single point of failure where as soon as some message cannot be delivered (no matter the reason), all following messages get stuck forever in acapy_outbound.

I'm trying to look into what your saying. I didn't design this so I'm not sure.
It shouldn't be queuing messages when it doesn't match a topic. I was going to fix that.

Thanks! The reason I bring up this idea that a single message stuck in acapy_outbound should probably not prevent any following messages from beeing delivered is that I've seen, in my tests, other contexts absolutely not related to the webhooks, where a message  not beeing delivered forced other following messages to stay indefinitely stuck. It happened when I did weird and unnatural changes to the configurations and set-up without resetting redis data but still, it crippled the outbound queue. This most probably should be considered as an issue all by itself though.

I understand the problem better now. It seems like it has something to do with not handling bad responses from and available web hook server. I'll try and sort it out. Thanks for your help.

@jpnorthernblock  https://github.com/hyperledger/aries-acapy-plugins/pull/86. Can't add you as a reviewer.

@jamshale Works for me with current scenario! With PR #86 the web-hooks are pushed to the redis outbound queue with right topic and delivered correctly.
I'll be playing around with the plugin in the days to come to see if I can still reproduce the "message stuck in outbound queue" problem in any other way, and if I do, it'll be a different issue.
Big thank you!


Newton solver implementation with ISPC backend

In order to use ISPC backend with derivimplicit method, we need newton solver implementation.

hi @pramodk, is this ticket still open?

ISPC backend have been removed in https://github.com/BlueBrain/nmodl/pull/963


Sensitive Data Exposure

Sensitive Data Exposure in content/notes/search.md
Issue Description:
First and foremost, I want to express my appreciation for the excellent work on this project. It works wonderfully, and I am delighted with the cost savings it offers.
During my review of one of the documentation pages that I hadn't removed from my clone of your garden, I came across a potential privacy concern:
Since Operand went private, this might not be an issue. However, you unintentionally left your operand API key and index ID exposed in the content/notes/search.md file within the Hugo directory. Although it's removed from content/notes/config.md and data/config.yaml, the sensitive information is still accessible in search.md, potentially posing a security risk.
Steps to Reproduce:

Navigate to the content/notes/search.md file.
Search for the API key and index ID.

Expected Behavior:
Sensitive data such as API keys and index IDs should not be exposed or stored within the repository.
Actual Behavior:
The API key and index ID are still present in content/notes/search.md, despite being removed from other relevant files.
Suggested Solution:

Remove the exposed API key and index ID from content/notes/search.md.
Ensure that sensitive data is appropriately handled, such as using environment variables or a secure configuration mechanism.
Conduct a thorough review of other files within the repository to confirm there are no other occurrences of sensitive data exposure.

Additionally, if this repository were private, I might suggest using a git tree filter to completely remove the sensitive data from the repository's history. However, please be cautious if applying such a filter, as it could potentially lead to unintended data loss or history modification.
Your attention to this matter might enhance the security of the repository and prevent any potential data breaches or cost leakage / financial losses. Please feel free to proceed with addressing this issue. If you have any questions or need further assistance, don't hesitate to ask.

Thanks for the concern! However, this is a public API key and public index ID, there is no security issue (as the only thing the key has permission to do is read)

Thank you for getting back to me so quickly. I apologize for any confusion caused by my assumption that the API key and index ID were private and sensitive, since I thought you might be charged if people plugged them in and searched. I understand the importance of being accurate and not causing unnecessary concern. Going forward, I will do my best to gather all relevant information before making any assumptions or conclusions. Thanks for your understanding.


Updated Composer requirements

First of all, we can't merge this pull request. I've just opened to get your feedback and comments about it.
In my computer, the demo application works perfectly and I see no errors or warnings. However, if I set a PHP extension constraint in PHP, I get the following Composer errors:
ext-pdo-sqlite

ext-sqlite

@javiereguiluz should it be ext-pdo_sqlite (since the extension is called pdo_sqlite)? I haven't needed to add an ext- before, so I thought I'd make the easy suggestion first :).

@weaverryan that was exactly the problem! Everything works now. Thanks!

Hi @javiereguiluz, I am a rookie in Symfony and I am making my first deploy with a brand new copy of Symfony Demo's project.
Locally, all is running OK...
I have not too many permissions in my Server and I can't access via SSH to execute $ composer install command so I only can copy all my project via FTP to the Server and expect it'll work.
When I go to ~/web/config.php page in my Server, all is OK, but when I navigate inside de Demo site, I have Error 500 because SQLite PDO is not activated in my Server (I will need an Administrator do it)...
Perhaps, config.php could advertised me about this to know what was the problem.
I have a bit experience in other technologies like Angular2+ where Angular CLI's projects are prepared to make a build --prod out of the box... I am surprised how Symfony have not any automatic scripts to do the same in composer.json to generate a /build copy ready for production, and how I must copy all the files and folders to my Server to make it run (I don't know if there is another way of do it)...
I have been investigating a little about Robo Task Runner and I think it is very cool... perhaps you could use this tool in this Demo and all new templates generated by $ php symfony new <my-project> command...
PS.- I have seen that 2 Test are failing now in last version of this Demo too.
Congratulations for your good work.


docs: make svelte switch example in sync with react

Sync for example apps
This brings svelte in sync with the example react app (and vue/angular).

@bartduisters the local apps for the Svelte/React apps are dev sandboxes. They are not intended to be use facing, so no need for parity. Just gives us a place to build and test things.
Additionally Svelte has two-way data binding, so we would use bind:checked={stateVar}.

Can be closed then!