The time spend on first run

Hello, I just ran your code and found it took nearly  1 day without any outcome, is the situation normal?

Hi, could you provide your machine specs, like CPU, GPU, RAM? Also, did you download the required AF2 database?

Hello, I use the NVIDIA GeForce RTX 3090, is GPU and  I just ran as the steps on Install and Running IntFold, is it needed to download the AF2 database on local machine?

Hello, I check the console output and it turns out that ader.cc:53] Successfully opened dynamic library libcufft.so.10 2024-09-09 02:00:45.848450: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcurand.so.10 2024-09-09 02:00:45.850959: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcusolver.so.11 2024-09-09 02:00:45.851606: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcusparse.so.11 2024-09-09 02:00:45.851735: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcudnn.so.8 2024-09-09 02:00:45.854765: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1871] Adding visible gpu devices: 0, 1 2024-09-09 02:01:24.553172: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F FMA To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags. 2024-09-09 02:01:24.553528: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1258] Device interconnect StreamExecutor with strength 1 edge matrix: 2024-09-09 02:01:24.553553: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1264]       2024-09-09 02:01:24.619603: I tensorflow/core/platform/profile_utils/cpu_utils.cc:114] CPU Frequency:<PHONE_NUMBER> Hz ColabFold on Linux homooligomer: '1' total_length: '231' working_directory: '/app/intermediate/4/1/1/23' running mmseqs2   0%|          | 0/150 [elapsed: 00:00 remaining: ?]   0%|          | 0/1 [elapsed: 00:00 remaining: ?] 2024-09-09 02:02:18.437094: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcudart.so.11.0 2024-09-09 02:02:19.347149: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcuda.so.1 2024-09-09 02:02:19.373172: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1733] Found device 0 with properties:  pciBusID: 0000:17:00.0 name: NVIDIA GeForce RTX 3090 computeCapability: 8.6 coreClock: 1.695GHz coreCount: 82 deviceMemorySize: 23.70GiB deviceMemoryBandwidth: 871.81GiB/s 2024-09-09 02:02:19.374094: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1733] Found device 1 with properties:  pciBusID: 0000:65:00.0 name: NVIDIA GeForce RTX 3090 computeCapability: 8.6 coreClock: 1.695GHz coreCount: 82 deviceMemorySize: 23.70GiB deviceMemoryBandwidth: 871.81GiB/s 2024-09-09 02:02:19.374135: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcudart.so.11.0 2024-09-09 02:02:19.376703: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcublas.so.11 2024-09-09 02:02:19.376759: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcublasLt.so.11 2024-09-09 02:02:19.377581: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcufft.so.10 2024-09-09 02:02:19.377804: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcurand.so.10 2024-09-09 02:02:19.380389: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcusolver.so.11 2024-09-09 02:02:19.381054: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcusparse.so.11 2024-09-09 02:02:19.381178: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcudnn.so.8 2024-09-09 02:02:19.384220: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1871] Adding visible gpu devices: 0, 1 2024-09-09 02:03:44.042420: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F FMA To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags. 2024-09-09 02:03:44.042770: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1258] Device interconnect StreamExecutor with strength 1 edge matrix: 2024-09-09 02:03:44.042797: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1264]       2024-09-09 02:03:44.107632: I tensorflow/core/platform/profile_utils/cpu_utils.cc:114] CPU Frequency:<PHONE_NUMBER> Hz 2024-09-09 02:03:45.788683: W tensorflow/core/framework/cpu_allocator_impl.cc:80] Allocation of 631209040 exceeds 10% of free system memory. 2024-09-09 02:03:45.791021: W tensorflow/core/framework/cpu_allocator_impl.cc:80] Allocation of 639645640 exceeds 10% of free system memory. 2024-09-09 02:03:46.429690: W tensorflow/core/framework/cpu_allocator_impl.cc:80] Allocation of 639645640 exceeds 10% of free system memory. 2024-09-09 02:03:46.897342: W tensorflow/core/framework/cpu_allocator_impl.cc:80] Allocation of 639645640 exceeds 10% of free system memory. 2024-09-09 02:03:47.358656: W tensorflow/core/framework/cpu_allocator_impl.cc:80] Allocation of 639645640 exceeds 10% of free system memory. ColabFold on Linux homooligomer: '1' total_length: '430' working_directory: '/app/intermediate/6/3/4/4' running mmseqs2   0%|          | 0/150 [elapsed: 00:00 remaining: ?]   0%|          | 0/1 [elapsed: 00:00 remaining: ?] 2024-09-09 02:05:19.927337: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcudart.so.11.0 2024-09-09 02:05:20.836905: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcuda.so.1 2024-09-09 02:05:20.866120: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1733] Found device 0 with properties:  pciBusID: 0000:17:00.0 name: NVIDIA GeForce RTX 3090 computeCapability: 8.6 coreClock: 1.695GHz coreCount: 82 deviceMemorySize: 23.70GiB deviceMemoryBandwidth: 871.81GiB/s 2024-09-09 02:05:20.866896: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1733] Found device 1 with properties:  pciBusID: 0000:65:00.0 name: NVIDIA GeForce RTX 3090 computeCapability: 8.6 coreClock: 1.695GHz coreCount: 82 deviceMemorySize: 23.70GiB deviceMemoryBandwidth: 871.81GiB/s 2024-09-09 02:05:20.866931: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcudart.so.11.0 2024-09-09 02:05:20.869310: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcublas.so.11 2024-09-09 02:05:20.869363: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcublasLt.so.11 2024-09-09 02:05:20.870141: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcufft.so.10 2024-09-09 02:05:20.870361: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcurand.so.10 2024-09-09 02:05:20.872760: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcusolver.so.11 2024-09-09 02:05:20.873383: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcusparse.so.11 2024-09-09 02:05:20.873511: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcudnn.so.8 2024-09-09 02:05:20.876369: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1871] Adding visible gpu devices: 0, 1Could you tell me what's wrong with it?

Hello, I check the console output, it shows as follows:
ader.cc:53] Successfully opened dynamic library libcufft.so.10 2024-09-09 02:00:45.848450: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcurand.so.10 2024-09-09 02:00:45.850959: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcusolver.so.11 2024-09-09 02:00:45.851606: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcusparse.so.11 2024-09-09 02:00:45.851735: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcudnn.so.8 2024-09-09 02:00:45.854765: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1871] Adding visible gpu devices: 0, 1 2024-09-09 02:01:24.553172: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F FMA To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags. 2024-09-09 02:01:24.553528: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1258] Device interconnect StreamExecutor with strength 1 edge matrix: 2024-09-09 02:01:24.553553: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1264]       2024-09-09 02:01:24.619603: I tensorflow/core/platform/profile_utils/cpu_utils.cc:114] CPU Frequency:<PHONE_NUMBER> Hz ColabFold on Linux homooligomer: '1' total_length: '231' working_directory: '/app/intermediate/4/1/1/23' running mmseqs2   0%|          | 0/150 [elapsed: 00:00 remaining: ?]   0%|          | 0/1 [elapsed: 00:00 remaining: ?] 2024-09-09 02:02:18.437094: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcudart.so.11.0 2024-09-09 02:02:19.347149: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcuda.so.1 2024-09-09 02:02:19.373172: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1733] Found device 0 with properties:  pciBusID: 0000:17:00.0 name: NVIDIA GeForce RTX 3090 computeCapability: 8.6 coreClock: 1.695GHz coreCount: 82 deviceMemorySize: 23.70GiB deviceMemoryBandwidth: 871.81GiB/s 2024-09-09 02:02:19.374094: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1733] Found device 1 with properties:  pciBusID: 0000:65:00.0 name: NVIDIA GeForce RTX 3090 computeCapability: 8.6 coreClock: 1.695GHz coreCount: 82 deviceMemorySize: 23.70GiB deviceMemoryBandwidth: 871.81GiB/s 2024-09-09 02:02:19.374135: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcudart.so.11.0 2024-09-09 02:02:19.376703: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcublas.so.11 2024-09-09 02:02:19.376759: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcublasLt.so.11 2024-09-09 02:02:19.377581: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcufft.so.10 2024-09-09 02:02:19.377804: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcurand.so.10 2024-09-09 02:02:19.380389: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcusolver.so.11 2024-09-09 02:02:19.381054: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcusparse.so.11 2024-09-09 02:02:19.381178: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcudnn.so.8 2024-09-09 02:02:19.384220: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1871] Adding visible gpu devices: 0, 1 2024-09-09 02:03:44.042420: I tensorflow/core/platform/cpu_feature_guard.cc:142] This TensorFlow binary is optimized with oneAPI Deep Neural Network Library (oneDNN) to use the following CPU instructions in performance-critical operations:  AVX2 AVX512F FMA To enable them in other operations, rebuild TensorFlow with the appropriate compiler flags. 2024-09-09 02:03:44.042770: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1258] Device interconnect StreamExecutor with strength 1 edge matrix: 2024-09-09 02:03:44.042797: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1264]       2024-09-09 02:03:44.107632: I tensorflow/core/platform/profile_utils/cpu_utils.cc:114] CPU Frequency:<PHONE_NUMBER> Hz 2024-09-09 02:03:45.788683: W tensorflow/core/framework/cpu_allocator_impl.cc:80] Allocation of 631209040 exceeds 10% of free system memory. 2024-09-09 02:03:45.791021: W tensorflow/core/framework/cpu_allocator_impl.cc:80] Allocation of 639645640 exceeds 10% of free system memory. 2024-09-09 02:03:46.429690: W tensorflow/core/framework/cpu_allocator_impl.cc:80] Allocation of 639645640 exceeds 10% of free system memory. 2024-09-09 02:03:46.897342: W tensorflow/core/framework/cpu_allocator_impl.cc:80] Allocation of 639645640 exceeds 10% of free system memory. 2024-09-09 02:03:47.358656: W tensorflow/core/framework/cpu_allocator_impl.cc:80] Allocation of 639645640 exceeds 10% of free system memory. ColabFold on Linux homooligomer: '1' total_length: '430' working_directory: '/app/intermediate/6/3/4/4' running mmseqs2   0%|          | 0/150 [elapsed: 00:00 remaining: ?]   0%|          | 0/1 [elapsed: 00:00 remaining: ?] 2024-09-09 02:05:19.927337: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcudart.so.11.0 2024-09-09 02:05:20.836905: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcuda.so.1 2024-09-09 02:05:20.866120: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1733] Found device 0 with properties:  pciBusID: 0000:17:00.0 name: NVIDIA GeForce RTX 3090 computeCapability: 8.6 coreClock: 1.695GHz coreCount: 82 deviceMemorySize: 23.70GiB deviceMemoryBandwidth: 871.81GiB/s 2024-09-09 02:05:20.866896: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1733] Found device 1 with properties:  pciBusID: 0000:65:00.0 name: NVIDIA GeForce RTX 3090 computeCapability: 8.6 coreClock: 1.695GHz coreCount: 82 deviceMemorySize: 23.70GiB deviceMemoryBandwidth: 871.81GiB/s 2024-09-09 02:05:20.866931: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcudart.so.11.0 2024-09-09 02:05:20.869310: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcublas.so.11 2024-09-09 02:05:20.869363: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcublasLt.so.11 2024-09-09 02:05:20.870141: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcufft.so.10 2024-09-09 02:05:20.870361: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcurand.so.10 2024-09-09 02:05:20.872760: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcusolver.so.11 2024-09-09 02:05:20.873383: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcusparse.so.11 2024-09-09 02:05:20.873511: I tensorflow/stream_executor/platform/default/dso_loader.cc:53] Successfully opened dynamic library libcudnn.so.8 2024-09-09 02:05:20.876369: I tensorflow/core/common_runtime/gpu/gpu_device.cc:1871] Adding visible gpu devices: 0, 1

So maybe the reason is the net problem on docker, hope you can answer me. Thanks so lot!

Could you check the /app/intermediate folder in the container using docker exec -t -i <container id> /bin/bash?
If there is nothing inside and you want to generate intermediate representations, you may use this repo. But you need to download all required databases and build the docker image. You can run batch_gen_rep.py in the repo to generate representations.

I check the /app/intermediate, it shows:
!

and as my understanding, maybe the reason is not downloading the databases from Alphafold2, and I need to download it in the docker container?

And as for the repo you shared with me, because I have build the alphafold enviroment before, so the updated for the code is just adding the batch_gen_repr.py or modifying some other codes in alphafold2. And also, as I usually meet the mistakes of  " too many command lines arguments", could you share me your run command of batch_gen_repr.py? Thanks so lot, that helps me a lot.

Thanks for your answer, so is that means the intfold can not use anymore because of the problem you mentioned?
And for running  batch_gen_rep.py, I ran successfully yesterday, but I can not find the intermediate representations in the output dictionary.  Could you tell me where are them or if my output is wrong?

These are the original output of AF2. You should build a new docker image using the repo I shared above. You may use a new tag for this new docker image, and be sure to change the docker image name in the batch_gen_rep.py accordingly.

Thank you so so  much about your kind help!


I2C default ISR resets with Cache disabled but cached memory region accessed (IDFGH-6795)

----------------------------- Delete below -----------------------------
Reminder: If your issue is a general question, starts similar to "How do I..", or is related to 3rd party development kits/libs, please discuss this on our community forum at https://esp32.com instead.
Environment

Development Kit:      [none]
Module or chip used:  [ESP32-WROOM-32]
IDF version (run git describe --tags to find it):
v4.4-rc1-8-g0b46ac1732
Build System:         [idf.py]
Compiler version (run xtensa-esp32-elf-gcc --version to find it):
xtensa-esp32-elf-gcc (crosstool-NG esp-2021r2) 8.4.0
Operating System:     [Linux]
Using an IDE?: [No|Yes (please give details)]
VSCode or CLion
Power Supply:         [USB + Battery]

Problem Description
When setting the I2C interrupt to ESP_INTR_FLAG_IRAM in the i2c_driver_install, the I2C interrupt will reset the system with a cache disabled error when accessing the SPIFFS at the same time the I2C module is reading data from a slave
Expected Behavior
System doesn't reset when using an ISR allocated in IRAM while cache is disabled
Actual Behavior
System resets
Steps to reproduce

Install I2C driver with ESP_INTR_FLAG_IRAM option
Communicate with an I2C slave, initiate some form of long read operation (reading multiple values)
In another task write a file to the SPIFFS
Make sure they are both happening in the same time, so that the I2C interrupt gets called while the cache is disabled

Debug Logs
Guru Meditation Error: Core  0 panic'ed (Cache disabled but cached memory region accessed).
Core  0 register dump:
PC      : 0x4015b278  PS      : 0x00060035  A0      : 0x8008af0d  A1      : 0x3ffbe8e0
0x4015b278: i2c_hal_update_config at /home/hassan/esp/esp-idf/components/hal/i2c_hal.c:223

A2      : 0x00000000  A3      : 0x00000000  A4      : 0x3ffcf370  A5      : 0x3ffbc5e0
A6      : 0x00000026  A7      : 0x3ffd8210  A8      : 0x8008ae40  A9      : 0x00000000
A10     : 0x3ffcf370  A11     : 0x00000000  A12     : 0x00000000  A13     : 0x00000800
A14     : 0x00000000  A15     : 0x3ff53000  SAR     : 0x00000018  EXCCAUSE: 0x00000007
EXCVADDR: 0x00000000  LBEG    : 0x4000c2e0  LEND    : 0x4000c2f6  LCOUNT  : 0x00000002
Backtrace:0x4015b275:0x3ffbe8e00x4008af0a:0x3ffbe910 0x40082f95:0x3ffbe940 0x4000c2e5:0x3ffbc5c0 0x40096c6e:0x3ffbc5d0 0x4009ae8d:0x3ffbc600 0x4008d7d7:0x3ffbc680 0x40136a09:0x3ffbc6c0 0x4012a2c7:0x3ffbc6f0 0x4012dd87:0x3ffbc720 0x4012b9bf:0x3ffbc750 0x4012d196:0x3ffbc790 0x4012a948:0x3ffbc7d0 0x4012a0c9:0x3ffbc800 0x400d4331:0x3ffbc820 0x4014567c:0x3ffbc840 0x40145725:0x3ffbc870 0x400dbd48:0x3ffbc890 0x400dd680:0x3ffbc8c0 0x400d6c1d:0x3ffbc8f0 0x400d7c11:0x3ffbc910 0x400d6a3f:0x3ffbc9a0 0x4015ba89:0x3ffbc9c0 0x40095eb5:0x3ffbc9e0
0x4015b275: i2c_hal_enable_slave_rx_it at /home/hassan/esp/esp-idf/components/hal/i2c_hal.c:170
0x4008af0a: i2c_isr_handler_default at /home/hassan/esp/esp-idf/components/driver/i2c.c:497
0x40082f95: _xt_lowint1 at /home/hassan/esp/esp-idf/components/freertos/port/xtensa/xtensa_vectors.S:1111
0x40096c6e: spi_flash_ll_get_buffer_data at /home/hassan/esp/esp-idf/components/hal/esp32/include/hal/spi_flash_ll.h:148
 (inlined by) spi_flash_hal_read at /home/hassan/esp/esp-idf/components/hal/spi_flash_hal_common.inc:181
0x4009ae8d: spi_flash_chip_generic_read at /home/hassan/esp/esp-idf/components/spi_flash/spi_flash_chip_generic.c:218
0x4008d7d7: esp_flash_read at /home/hassan/esp/esp-idf/components/spi_flash/esp_flash_api.c:832 (discriminator 4)
0x40136a09: esp_partition_read at /home/hassan/esp/esp-idf/components/spi_flash/partition.c:424
0x4012a2c7: spiffs_api_read at /home/hassan/esp/esp-idf/components/spiffs/spiffs_api.c:36
0x4012dd87: spiffs_phys_rd at /home/hassan/esp/esp-idf/components/spiffs/spiffs/src/spiffs_cache.c:161
0x4012b9bf: spiffs_obj_lu_find_entry_visitor at /home/hassan/esp/esp-idf/components/spiffs/spiffs/src/spiffs_nucleus.c:166
0x4012d196: spiffs_object_find_object_index_header_by_name at /home/hassan/esp/esp-idf/components/spiffs/spiffs/src/spiffs_nucleus.c:1694
0x4012a948: SPIFFS_open at /home/hassan/esp/esp-idf/components/spiffs/spiffs/src/spiffs_hydrogen.c:230 (discriminator 2)
0x4012a0c9: vfs_spiffs_open at /home/hassan/esp/esp-idf/components/spiffs/esp_spiffs.c:479
0x400d4331: esp_vfs_open at /home/hassan/esp/esp-idf/components/vfs/vfs.c:399 (discriminator 3)
0x4014567c: _fopen_r at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/newlib/newlib/libc/stdio/fopen.c:129
0x40145725: fopen at /builds/idf/crosstool-NG/.build/xtensa-esp32-elf/src/newlib/newlib/libc/stdio/fopen.c:168
0x400dbd48: readFile at /home/hassan/Documents/Si-Ware/Scanner/ScannerFirmware/components/FileSystem/fileSystem.c:24
0x400dd680: fileSystem_register_gauge_reset at /home/hassan/Documents/Si-Ware/Scanner/ScannerFirmware/components/FileSystem/fileSystem.c:1160
0x400d6c1d: centralManager_run_powerManagement_init at /home/hassan/Documents/Si-Ware/Scanner/ScannerFirmware/components/CentralManager/centralManager.c:40
0x400d7c11: centralManager_systemStart at /home/hassan/Documents/Si-Ware/Scanner/ScannerFirmware/components/CentralManager/centralManager.c:280 (discriminator 13)
0x400d6a3f: app_main at /home/hassan/Documents/Si-Ware/Scanner/ScannerFirmware/main/main.c:5
0x4015ba89: main_task at /home/hassan/esp/esp-idf/components/freertos/port/port_common.c:129 (discriminator 2)
0x40095eb5: vPortTaskWrapper at /home/hassan/esp/esp-idf/components/freertos/port/xtensa/port.c:131

The core dump for the same reset shows a slightly different story, but a much more concise one as i2c_hal_enable_slave_rx_it should never be called, as my I2C is in master mode
'''
#0  i2c_hal_update_config (hal=0x0) at /home/hassan/esp/esp-idf/components/hal/i2c_hal.c:223
#1  0x4008ae40 in i2c_master_cmd_begin_static (i2c_num=0) at /home/hassan/esp/esp-idf/components/driver/i2c.c:1369
#2  0x4008af0d in i2c_isr_handler_default (arg=0x3ffdda4c) at /home/hassan/esp/esp-idf/components/driver/i2c.c:497
#3  0x40082f98 in _xt_lowint1 () at /home/hassan/esp/esp-idf/components/freertos/port/xtensa/xtensa_vectors.S:1111
Backtrace stopped: previous frame inner to this frame (corrupt stack?)
'''
Other items if possible
I did some investigation and I found that the issue is that the function i2c_hal_update_config which is called in i2c_master_cmd_begin_static is not defined with IRAM_ATTR, and it seems to cause the error, because when I comment it every thing works fine.
On my ESP32 this function seems to do nothing, but I think it is necessary for other platforms.
A proposed fix would be to skip the i2c_hal_update_config and directly call the lower layer i2c_ll_update (which is already inline so would pose no problems) via a macro. This fix is in the included patch

[ yes] sdkconfig file (attach the sdkconfig file from your project folder)
[ yes] elf file in the build folder (note this may contain all the code details and symbols of your project.)
[ yes] coredump (This provides stacks of tasks.)
I2CIssue.zip

diff --git a/components/driver/i2c.c b/components/driver/i2c.c
index 438d1efc12..3637288596 100644
--- a/components/driver/i2c.c
+++ b/components/driver/i2c.c
@@ -1366,7 +1366,7 @@ static void IRAM_ATTR i2c_master_cmd_begin_static(i2c_port_t i2c_num)
             break;
         }
     }
-    i2c_hal_update_config(&(i2c_context[i2c_num].hal));
+    i2c_hal_update_config_isr(&(i2c_context[i2c_num].hal));
     i2c_hal_trans_start(&(i2c_context[i2c_num].hal));
     return;
 }
diff --git a/components/esptool_py/esptool b/components/esptool_py/esptool
--- a/components/esptool_py/esptool
+++ b/components/esptool_py/esptool
@@ -1 +1 @@
-Subproject commit b082b0ed2d86b3330134c4854a021dfd14c29b08
+Subproject commit b082b0ed2d86b3330134c4854a021dfd14c29b08-dirty
diff --git a/components/hal/include/hal/i2c_hal.h b/components/hal/include/hal/i2c_hal.h
index b255878cc4..698d0da5d8 100644
--- a/components/hal/include/hal/i2c_hal.h
+++ b/components/hal/include/hal/i2c_hal.h
@@ -91,6 +91,7 @@ typedef struct {
  * @return None
  */
 #define i2c_hal_enable_master_tx_it(hal)    i2c_ll_master_enable_tx_it((hal)->dev)
+#define i2c_hal_update_config_isr(hal)        i2c_ll_update((hal)->dev)

 /**
  * @brief  Clear I2C slave TX interrupt

Hi @HassanSaied Thanks for reporting this issue, and bringing up this fix.
We will look into this issue more detailedly to find out all the wrong cases. This kind of issues are a bit hard to fix completely, because the inline logic is somehow determined by the compiler behavior under different configs...
Before that, you can work with your fix, or try add FORCE_INLINE_ATTR to the i2c_ll_update function.

@ginkgm
Require to backport stable branches.

Hello Friends,
Seems like I am still getting the same issue where I cannot make use of the I2C interrupt in the iram. Environment: Espressif IDE on IDF v4.4.3.
Currently I am only changing the driver install file as below, to enable the iram functionality:
i2c_driver_install(i2c_master_port, conf.mode, I2C_MASTER_RX_BUF_DISABLE, I2C_MASTER_TX_BUF_DISABLE, ESP_INTR_FLAG_IRAM);
Where else do I need to make the necessary changes for the I2C to run from iram?
I am pretty new to ESP, so please point me in the right direction if possible. The config file is attached at the bottom.
sdkconfig.txt


Good framework, not enough documentation.

@HackShitUp Thank you for your interesting in this project! Any advices to make this project better is very appreciated. 😃

Yea, so (I'm writing in Swift) one of the delegate methods you listed isn't initialized in code with the following error:
unresolved identifier: WZAnimatingTransition
I looked into the demo/example project and saw that one of the file is missing for Cocoapods?

Hum, I've  not publish a new version to CocoaPods for a long time. Could you mind change the Podfile to this repo's master, it may works:
pod 'WZDraggableSwitchHeaderView', :git => 'https://github.com/wongzigii/WZDraggableSwitchHeaderView.git', :branch => 'master'

So I've tried that and I still get the error. I'm using this in a UITableViewController (just in case you're wondering). The view appears, but the delegate method: WZAnimatingTransition doesn't seem to exist (?)


Warn on IDNA/Unicode domain confusion

Is your feature request related to a problem? Please describe.

IDNA/Unicode domains can be used to trick users into visiting the wrong website, we should be able to match them and warn users before visiting these sites.
Describe the solution you'd like

Here's an excerpt from https://github.com/bluesky-social/social-app/pull/1644#issuecomment-1754188409

We extract domains out of raw labels manually, check if it contains Unicode, and that it gets converted into punycode xn--, if so, show a warning
Show a different warning UI, one that shows Unicode and the actual punycode domains
Allow users to exclude the domain they're visiting, so they don't get warned on this next time around

This solution tries to balance the risks of IDNA domains, and not bothering users that visits actual legitimate Unicode domains that are not harmful.
Describe alternatives you've considered

None yet.
Additional context

Websites and domains are for everyone, this includes allowing people to do IDNA/Unicode domains, we shouldn't be inconveniencing users who understands foreign writing scripts, especially as Bluesky isn't a social network that's specifically targeted towards an English-only world.
For example, the .みんな top-level domin. That exists, and I'd presume it also encourages your domains to be entirely in Japanese characters. We shouldn't be inconveniencing anyone that tries to visit those sites.
The threat of spoofing is real, but we shouldn't be trampling over other cultures to fix them.

Appreciate how deep you're going into this. I'll have to find time to focus into this at some point.


[VS Code] Unable to connect to the host in "Direct" mode. Verify you and the host are online. If so, switch to "Auto" or "Relay" mode and retry.

Error:
Unable to connect to the host in "Direct" mode. Verify you and the host are online. If so, switch to "Auto" or "Relay" mode and retry.
Steps to Reproduce:

Version Data

extensionName
VSLS

extensionVersion
0.3.395

protocolVersion
2.2

applicationName
VSCode

applicationVersion
1.25.1

platformName
Windows

platformVersion
10.0.17134

@FabianB14 Hey! Did you explicitly change your connect mode setting to “direct”? If so, this message indicates that a direct connection isn’t possible with the host (due to firewalls, etc.). If you change the connect mode setting back to “Auto”, that should unblock you, since it will fallback to a cloud relay to connect to the host.


By default cannot disable grafana repo management

Describe the Bug
The main init.pp file includes the puppet_operational_dashboards::profile::dashboards module - which has a parameter manage_grafana_repo which defaults to true.  For those with air gapped systems we need to be able to set this value to false.
Expected Behavior
We need to have a parameter for the main module which allows this value to be passed via hiera, and for that value to be passed to puppet_operational_dashboards::profile::dashboards.
Steps to Reproduce
Install a system using the module - its impossible to disable creation of the the grafana repo without changing the code.
Environment
Puppet Operational Dashboards Version 1.9.0
Puppet version 7.20
CentOS 7
Additional Context
None

Hi there!
Have you attempted the airgapped instructions here:
https://github.com/puppetlabs/puppet_operational_dashboards#note-on-air-gapped-environments
You should also be able to set any parameter via hiera that is in the profile classes

Yes I did follow the instructions on the air gapped system on the module - however they're not the complete story.
I thought I'd already tried to set it via puppet_operational_dashboards::profile::dashboards::manage_grafana_repo in hieradata - however I must have mis typed the name - it does actually work if you set that value ...  apologies.
I think the doc could do with an update (and also it would be useful to have a method to supply install options for the package install, for example we need to include an option to enable our local repo).
I'm happy to close this off - let me know.   Thanks.

Hi @iscb1962, most parameters related to Grafana repo management should be in the puppet/grafana module, such as setting a custom repo_url.  If that option works for you, you should be able to allow the module to manage the repo and set this parameter in Hiera to point to your local mirror.
I do agree that the docs could be more detailed, including this use case that I didn't consider.  If you can think of any other information do you think would be useful, let me know and we can add it.

The setup of an additional local repository should not be part of this module.
I agree, that there should be some guidelines in the documentation (e.g. pointing to yum_repo, zypper_repo or akt::source).
It would increase module complexity drastically if parameters for local repos for different OS must be added (Deb, Yum, Zypper).
@iscb1962 are you OK to close this issue?

I opened #165 that should resolve this.

Resolved in #165


Cannot read property 'split' of undefined

Hi, I have a scheduled github action which deploys my code everyday at noon UTC.
So far so good but today it threw a weird error - something which I couldn't reproduce locally:
Error! An unexpected error occurred in inspect: TypeError: Cannot read property 'split' of undefined
    at /usr/local/lib/node_modules/vercel/dist/index.js:2:650065
    at Array.reduce (<anonymous>)
    at A (/usr/local/lib/node_modules/vercel/dist/index.js:2:650029)
    at inspect_main (/usr/local/lib/node_modules/vercel/dist/index.js:2:655310)
    at runMicrotasks (<anonymous>)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)
    at he (/usr/local/lib/node_modules/vercel/dist/index.js:2:375059)

Do you have any idea if this error is caused by Vercel or by your action?

I have the same error as well.

Me too.
From yesterday

I tried to switch to vercel-action but they have the same error as well.
I hope this can be fixed soon.
https://github.com/amondnet/vercel-action/issues/28

We encounter the same error regardless of with the vercel or old now action.
Hope this can get fixed soon!

Yep, we're having the same problem using the vercel-action GitHub Action: https://github.com/amondnet/vercel-action/issues/27 I've got a string of troubleshooting notes going on over there if anyone is interested.

It looks like the action runs and completes properly since yesterday. Maybe Vercel updated/fixed something on their side?
Anyone still experiencing issues?
I will give it one more day and then I will close this issue.

Yep, looks like is working now.

https://github.com/amondnet/vercel-action/pull/29

Looks like it's fixed. Closing the issue 😄


add via tag to ferry routes

Ferry routes aren't necessarily point-to-point. They can stop along way, so this PR adds the via field. Ferry routes are now consistent with all other modes of transport.

sure, wiki and PR have been updated


ESHOP website

ESHOP Website
#963 issue
Checklist:

[X] I have mentioned the issue number in my Pull Request.
[X] I have commented my code, particularly in hard-to-understand areas
[X] I have created a helpful and easy to understand README.md

Hey @pranjay-poddar can you please look into this

Hey @pranjay-poddar can you please review it and merge this

Inactive


Use overload instead of override to implement Assertions.{assert, assume}

Background
Because dotty don't permit inline def override inline def,  so in commit 3cfd618, in Assertions.{assert, assume}, we pass 'this to AssertionsMacro. And in AssertionsMacro, we switch the implementation logic of assert/ assume based on type of the passed param.

Problem
The solution above is not flexible enough if we want to extends Assertions as in scalatest/scalatestplus-junit project.

Solution in this PR
As suggested in https://github.com/lampepfl/dotty/pull/8601#pullrequestreview-380646858, I use overload instead of override to implement Assertions.{assert, assume}

@ohze @bvenners Since 3.2.0 is around the corner, may I suggest we bring this dotty support to 3.2.0 instead of 3.1.x?

@ohze Fyi I have cherry-pick your commit(s) into this branch here for the upcoming 3.2.0:
https://github.com/scalatest/scalatest/tree/feature-3.2.0-with-dotty-improvements

@ohze Fyi changes included in this new PR for 3.2.0 https://github.com/scalatest/scalatest/pull/1827

@ohze Closing as this is now merged into 3.2.x-new and included in 3.2.0 release.


Update Google Search Help

Google Search Functionality is constantly in flux. I would like to add some more frequently, or constantly updated documentation to catch unlisted operators and the ever narrowing features in googles search engine.
Some links:
https://bynd.com/news-ideas/google-advanced-search-comprehensive-list-google-search-operators/
http://libguides.mit.edu/c.php?g=176061&p=1159512
http://its-tst.yale.edu/services/web-and-application-services/google-search-appliance/tips-searching-yale-s-google-search-appliance
Google search features removed in the last five years:

finding sites with images
removing already seen links
filtering by reading level.
finding search results in foreign languages ("translated foreign pages")
restricting results to forums, reviews, blogs
removing shopping sites from the list of search results
blocking search results
quick view for PDF files and Office files
timeline view for search results.

Also, we should constantly update other engines operators as we come across them.

https://msdn.microsoft.com/en-us/library/ff795620.aspx
https://help.yahoo.com/kb/search


[Bug]: Airtime balance displays with unwanted text extracted from message

Description
When I request for the airtime balance, it shows the correct balance but the text area also contains unwanted text extracted from the safaricom message.
Steps to reproduce

Open stax app
Go to Sim tab
Request airtime balance
Wait for about a minute for the balance to be updated on the app
Go to the Sim tab again and view the Sim balance details

Expected result
The Sim balance just shows the airtime balance
Actual result
There is extra unwanted text just above the airtime balance details
Link to screenshots/screen recordings
https://drive.google.com/file/d/1qTpBtPaoPxSSaxdEEh0bpctMBqW9DJ2Q/view?usp=drivesdk
Device name
Huawei y5 2019
Android OS
9
Is your phone dual SIM or single SIM?
Dual SIM
Which telco are you using for this test?
Safaricom
Stax device ID or email address
<EMAIL_ADDRESS>

This may be due to the response taking up 2 SMS and concatenating them in the wrong order


Including this role makes it impossible to use --tags to select certain tasks/roles

So this is a strange one.
I have a playbook for managing a server. The playbook includes baseline host setup (ntp, sshd config, etc), backup setup (via this role), and finally workload setup that manages the services running on the host.
When I want to target a specific set of roles/tasks using the --tags option, I receive the following error from this role. Notably this only happens when I've specified a tag that doesn't include the borgbackup role.
$ ansible-playbook services.yml --tags workload-setup

... snip...

TASK [m3nu.ansible_role_borgbackup : Run OS-specific tasks] ****************************************************
Tuesday 24 August 2021  21:54:14 +0200 (0:00:21.284)       0:00:21.284 ********
fatal: [redactedhostname]: FAILED! =>
  msg: No file was found when using first_found. Use errors='ignore' to allow this task to be skipped if no files are found

Here is a simple playbook to repro this:
---
- name: backup config
  hosts: example
  become: true
  tags: [backup]
  roles:
    - role: m3nu.ansible_role_borgbackup

- name: workload
 hosts: example
  become: true
  tags: [workload]
  tasks:
    - debug:
        msg: setup app services

Running this with ansible-playbook test.yml will work fine, but running it with ansible-playbook test.yml --tags workload results in the error above.

The role loads system-specific variables from the "var" directory; those variables are contained in files named after the os family/distribution as they are reported by the fact gathering module. Since you specify a tag at the playbook level (e.g "workload"), when you execute it with -t workload  the "gather_facts" step is not executed, therefore the role doesn't find a file to load. See https://github.com/ansible/ansible/issues/57529.

This needs the tag always, right?


fix: use the sortable handle

Summary
Hi,
Thanks for the CMS. I've started to use it and it has evolved a bit. It's great. I found an issue with the reordering of the items. The issue is here https://github.com/netlify/netlify-cms/issues/1614.
fixes #1614
Test plan
I have no test plan, I'm very unfamiliar with React :/ (it took me long enough just to get that working haha).
A picture of a cute animal (not mandatory but encouraged)

Deploy preview for netlify-cms-www ready!
Built with commit aa2e060e7eae1af9c1e9fa0216c79860d89ea6cf
https://deploy-preview-1655--netlify-cms-www.netlify.com

I've fixed the prettier issue.

Deploy preview for cms-demo ready!
Built with commit 55910ddec663d78fce8fff53c7de1119db35e108
https://deploy-preview-1655--cms-demo.netlify.com

You can see the working result here: https://deploy-preview-1655--cms-demo.netlify.com/#/collections/settings/entries/authors

Thanks @daddykotex! This was fixed in #1395, will be released soon.

Re-opening, as @erquhart's fix caused a regression. All markdown editor widgets are currently broken.
Closes #1672.

Thanks @daddykotex! (and good catch @tech4him1)


Argument of type 'MSIAppServiceTokenCredentials' is not assignable to parameter of type 'ServiceClientCredentials'.

Package Name and Version:
"@azure/arm-containerinstance": "^5.4.0"
"@azure/ms-rest-nodeauth": "^3.0.5"

Operating system:
Linux

[x] nodejs

version: v10.18.0

[x] typescript

version: ^3.9.6

Describe the bug
Typescript gives warning when I try to use loginWithAppServiceMSI in "@azure/ms-rest-nodeauth" to authenticate ContainerInstanceManagementClient in "@azure/arm-containerinstance". Error message is "Argument of type 'MSIAppServiceTokenCredentials' is not assignable to parameter of type 'ServiceClientCredentials'."
Expected behavior
"ms-rest-nodeauth" should work with "@azure/arm-containerinstance" according to https://github.com/Azure/azure-sdk-for-js/tree/master/sdk/containerinstance/arm-containerinstance#sample-code.
Screenshots

@stingray111
You are using a very old version of the @azure/arm-containerinstance package which is not compatible with the latest version of the @azure/ms-rest-nodeauth package.
You have one of two options to move forward:

Either change the version of @azure/ms-rest-nodeauth from v3 to v2
Or change the version of @azure/arm-containerinstance to v9 or above

@ramya-rao-a
Thank you for your response. I would like to update the @azure/arm-containerinstance but the latest I can search for is 5.4.0 ( https://www.npmjs.com/package/@azure/arm-containerinstance). Can you give me some pointer on how to get a v9 library for that?

@stingray111 My apologies, I misunderstood and assumed that you were using @azure/arm-containerservices.
@changlong-liu, This would need us to re-generate the @azure/arm-containerinstance using the latest v4 code generator and release an update.

Thanks @ramya-rao-a .
And I see the swagger for containerinstance has been changed greatly since last release, a regeneration will involve these changes, including some breaking changes. So add service team to advise whether we need to release new package based on latest swagger.

Hi service team, would you help to confirm the swagger for containerinstance are ready for release, and send sdk-release-request if it does. Thank you!

@ramya-rao-a
May I know if there is ETA regarding this issue? We would like update on library asap as we recently faced a fatal error on Azure Function with the old libraries. The Azure Support we contacted suggested us to update the library.

@stingray111 Looks like 4 days ago, an update was released via #10253. So, the latest version i.e. 6.0.0 should work as expected.

Please use the latest version and drop in a comment if you see any other issues
Thanks for reporting!


Scrolling performance regression using intermediate NSImage

I'm filing this issue to track the known scrolling performance regression from #757 (see that thread for more details).  Although it's known already, this way I can subscribe to the issue and hopefully get notified when it's fixed. :)

Here's a first pass at a change which significantly improves performance for me. I'm not quite ready to make a PR, but please try it out:
https://github.com/s4y/macvim/tree/stateful-render
All feedback is welcome.

Two notes re. the above:

Some of the new rendering code is just copied and pasted from MMCoreTextView's three other rendering paths. Since it seems to do as well as them, I'd love to delete the other paths in my PR instead of trying to make them all work at the same time.

I'm not done making rendering faster 😉. If this works out, I know what I want to do next.

Omg, this is night and day faster!
I have a very fast keyboard repeat rate and so scroll performance is super noticeable when it chugs!
Great work so far, excited for what's to come!
(I'm on vacation right now - so won't have a ton of opportunity to test)

Performance look great but UltiSnips stopped working with this patch. Otherwise great work!

@juliuszint How does UltiSnips not work? Please file another issue for that. Also there's a new version coming out that fixes Ctrl-C not working but it's hard to tell if it's related without more info.

@ychin Sorry, that was just meant as a feedback for the patch that @s4y provided. Since he explicitly wrote that this code is not ready for a pull request and not merged into master i think filing a issue would be a little bit early. I never encountered this problem with a official MacVim release.

@juliuszint Ah ok. Cool good to know. One less bug for me to fix.
@s4y if you feel like it I would recommend making a pull request with "[WIP]" as a prefix to the title so conversations and discussions on your fix can be focused there. It's up to you though.

One small thing I have noticed:

Every once in a while, a tiny artifact will appear, in roughly the same-ish location. It looks like a dead pixel but I can confirm its not since (a it comes through on screenshots) and be it follows the window when I move it around.  If I scroll the document it goes away

@ychin et. al: See #858!

@amadeus Let's continue on the PR? The current patch might affect this, but might also not.
@juliuszint If there's any more detail you can share (on the PR), please do!

Just in case it's helpful, for me it's also affecting how fast the caret travels.
I have a really high key repeat rate, with really low delay, so the effect is really noticeable.

@nuc exactly same here. however, there is an open PR #858 which fixes the issue

Could someone share build here for test. I cant build it locally due to Error 65 which should be resolved by installing Xcode - but it doesn't help me.

MacVim.app.zip
Configured with ./configure --enable-python3interp. Hope this works for you.

MacVim.app.zip
Configured with ./configure --enable-python3interp. Hope this works for you.

Better to make it with python3 dynamic


[Bug] In Nav Bar

Description
The contact and newsletter button is not working on the nav bar.
Screenshots

Additional information
No response

I want to work on this issue, would you assign me?
cc: @AvineshTripathi @bhavyastar

Hey @chirag0002 sorry to keep you waiting, the problem is that we are not keeping the contact button and it should be removed. Instead you can start working on navbar responsiveness if that interest you

Yeah @AvineshTripathi, it suits me fine. So, do I have to create another issue for the navbar's responsiveness or to continue on this issue with responsiveness?

You can continue your work on this issue itself.
On Thu, Jul 28, 2022 at 6:38 PM Chirag Varshney @.***>
wrote:

Yeah @AvineshTripathi https://github.com/AvineshTripathi, it suits me
fine. So, do I have to create another issue for the navbar's responsiveness
or to continue on this issue with responsiveness?
—
Reply to this email directly, view it on GitHub
https://github.com/kubesimplify/website/issues/123#issuecomment-1198117383,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AUGNAH446AQXT477RDTR4FLVWKA27ANCNFSM534HCCIA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Ohk @bhavyastar, please do assign me this issue.

Assigned, You can start working on this. @chirag0002

@chirag0002 any updates?

@AvineshTripathi I think Bishal has done the responsiveness and committed it 6 days ago along with some other issues.
In short responsiveness of the navbar has already been done!!

@chirag0002 oh I didn't know that closing this issue you can look for other issues if not let me know I ll help you find one


Remove curly braces from examples dsl

What's wrong with the curly braces? I personally find it easier to read with them

The main problem I see, is that it's irregular and I want the examples to be presented in the simplest form possible.
That's also the reason I've changed joins from the infix notation to normal method call. Otherwise some of the parenthesis position look kind of confusing.
The second reason is that I'm trying to get everything to compile in Scala 3 and there are a lot of errors right now, some of them with our DSL, and I just want to make sure we're not hitting any edge cases here.


can't declare type for esp_hal::lcd_cam::lcd::i8080::I8080

I'm attempting to declare specific type of a use esp_hal::lcd_cam::lcd::i8080::I8080;
#![no_std]
#![no_main]

use esp_backtrace as _;
use esp_hal::dma::gdma::Channel;
use esp_hal::dma::ChannelTx;
use esp_hal::dma::ChannelTxImpl;
use esp_hal::gpio::GpioPin;
use esp_hal::lcd_cam::lcd::i8080::TxSixteenBits;
use esp_hal::lcd_cam::lcd::i8080::I8080;
use esp_hal::prelude::*;

#[entry]
fn main() -> ! {
    let my_i8080: Option<
        I8080<
            ChannelTx<ChannelTxImpl<0>, Channel<0>>,
            TxSixteenBits<
                GpioPin<14>,
                GpioPin<46>,
                GpioPin<13>,
                GpioPin<9>,
                GpioPin<3>,
                GpioPin<10>,
                GpioPin<12>,
                GpioPin<11>,
                GpioPin<6>,
                GpioPin<7>,
                GpioPin<38>,
                GpioPin<42>,
                GpioPin<48>,
                GpioPin<47>,
                GpioPin<2>,
                GpioPin<21>,
            >,
        >,
    > = None;
    loop {}
}

but use esp_hal::dma::gdma::Channel is private (the gdma part is). And that Channel should be available as esp_hal::dma::Channel because its re-exported with a pub use gdma::* here but later another Channel is declared with a different type signature here and that seems to hide the one used.
I'd submit a PR but I'm not sure how that should be fixed .... or maybe I'm just very confused.

I think we had something similar regarding I2S on Matrix and this worked there:
i2s_tx: esp_hal::i2s::I2sTx<'a, esp_hal::peripherals::I2S0, esp_hal::dma::Channel0,esp_hal::Async >,

The generics on that type could really use some simplifying, like what was done for PARL_IO.
A little unrelated to this issue @liebman, can I ask what hardware your talking to with the I8080 driver? (I've been trying to find 16 bit screens to test the driver)

@Dominaezzz I'm (ab)using it to drive a 64x64 HUB75 LED matrix.  This uses 14 pins and I waste 2 pins because they are not optional. See the example I have in this draft PR.

@bjoernQ that works!  Thanks.  Now what I really want is this to be static so I can start the next transaction from the send done interrupt:
static MY_I8080: Mutex<
    RefCell<
        Option<
            I8080<
                ChannelTx<ChannelTxImpl<0>, Channel0>,
                TxSixteenBits<
                    GpioPin<14>,
                    GpioPin<46>,
                    GpioPin<13>,
                    GpioPin<9>,
                    GpioPin<3>,
                    GpioPin<10>,
                    GpioPin<12>,
                    GpioPin<11>,
                    GpioPin<6>,
                    GpioPin<7>,
                    GpioPin<38>,
                    GpioPin<42>,
                    GpioPin<48>,
                    GpioPin<47>,
                    GpioPin<2>,
                    GpioPin<21>,
                >,
            >,
        >,
    >,
> = Mutex::new(RefCell::new(None));

But this yields:
error[E0277]: `*mut DmaDescriptor` cannot be sent between threads safely
    --> board-tests/src/bin/i8080-static.rs:44:18
     |
44   |   static MY_I8080: Mutex<
     |  __________________^
45   | |     RefCell<
46   | |         Option<
47   | |             I8080<
...    |
69   | |     >,
70   | | > = Mutex::new(RefCell::new(None));
     | |_^ `*mut DmaDescriptor` cannot be sent between threads safely

and
error[E0277]: `*const u8` cannot be sent between threads safely
    --> board-tests/src/bin/i8080-static.rs:44:18
     |
44   |   static MY_I8080: Mutex<
     |  __________________^
45   | |     RefCell<
46   | |         Option<
47   | |             I8080<
...    |
69   | |     >,
70   | | > = Mutex::new(RefCell::new(None));
     | |_^ `*const u8` cannot be sent between threads safely

Might need a PR to mark the channel type as Send.
Short term hack could be to wrap the I8080 type in a struct before putting it in the mutex, then you can mark this struct as Send. This will let you store it in the mutex I think.

Can this be closed now? Looks like you've successfully declared the type. (Though the type signature could use some improving, there's a separate issue for that)


MQTT in Node: Error stopping node: Close timed out

What are the steps to reproduce?
Import the flow in: https://cookbook.nodered.org/mqtt/connect-to-broker, start any MQTT broker (e.g. Mosquitto) and deploy
EDIT: The error is not evident with Mosquitto, as initially reported, but e.g. with https://github.com/martin-doyle/node-red-contrib-aedes.
What happens?
Every time the flow is deployed, the MQTT in node gets stuck for a while, then output: "Error stopping node: Close timed out"
What do you expect to happen?
The MQTT in node is immediately closed without errors and the flow is deployed without error and time wasting.
Please tell us about your environment:

[ ] Node-RED version: 1.3.2
[ ] Node.js version: 14.6.1
[ ] npm version:
[ ] Platform/OS: Win 10
[ ] Browser: Chrome

Hi,
I'm not able to reproduce this issue, so there may be something more specific with your environment that is contributing to it.
I assume you have the broker running locally rather than using a remote broker?

Are using mosquito 2.0? And is it on the same machine as node-red?

Thanks Nick, thanks Ben, today it seems that everything is working well. Yesterday I tried many times, restarting many times, too. Anyway, I use Mosquitto 1_6_12a on the same machine. I will close the issue now. If it will happen again I will check and keep you in the loop. Thanks again.

P.S. Seems like the problem arises if you have used Aedes node (https://flows.nodered.org/node/node-red-contrib-aedes) in your flows, no matter if enabled, disabled or erased. I will inform the authors of the node about. I leave the comment for who may encounter the same issue.

The error is connected to https://github.com/node-red/node-red/commit/04a3c4bb222f1708877ddd98379be801bfc6fc72. It happens only when a full deploy, not incremental.
Full credits for the doublecheck go to https://github.com/martin-doyle who I thanks again.
Waiting for v1.3.3.
Thanks for your excellent work!

Hi,
I am the maintainer of node-red-contrib-aedes. This issue only happens with a broker as part of Node-RED. An external broker is fine.
As far as I can see Node-RED closes the MQTT broker node-red-contrib-aedes first. Then the MQTT nodes send a disconnect which can't be answered anymore since the broker is already down.
20 Apr 20:20:43 - [info] [aedes broker:Standard Broker] Unbinding aedes mqtt server from port: 1885
20 Apr 20:20:43 - [info] [mqtt-broker:localhost:1885] Disconnected from broker: mqtt://localhost:1885
20 Apr 20:20:58 - [error] [mqtt in:80486cfb.0747d] Error stopping node: Close timed out
As mentioned before, everything was fine until version 1.2.9. The issue only happens when Node-RED shuts down i.e.  at close and at a full deploy.
Is there anything I can do in order to make the broker close after the MQTT nodes? Or do I have to send a specific signal before close?
No change for version 1.3.3. Any help is welcome.
Martin

Could the change https://github.com/node-red/node-red/pull/2880 be relevant this?

Yes, this will be related to the change in order of stopping things.
Previous, the flow/config nodes would be stopped in a somewhat random order - related to the order they were originally added to the workspace.
Now, the flow nodes are stopped first and then the config nodes are stopped.
This originally broke the 'on-close' message sending of the MQTT nodes as it was being handled by the close event of the config node - by which time all of the MQTT nodes would have already been stopped and the connection closed. So the sending of the message was moved to get triggered when the last MQTT node is closed.
If the aedes broker is a flow node, it will getting stopped alongside the MQTT nodes. If the aedes broker node was added first, it will get stopped before all of the MQTT nodes - meaning the connection will be dropping in parallel to the MQTT nodes stopping and trying to send the final on-close message.
To be honest, I'm not sure why you'd have an on-close message configured in the MQTT nodes if your broker is running inside Node-RED as well - the only time they are going to disconnect cleanly is when the flow is restarting or Node-RED is stopping, in which case the broker is going to be restarting/stopping as well.

As far as I know, sending the on-close message is the standard behaviour of the MQTT config nodes. There is no additonal message configured. So, the problem is now that the MQTT config node expects an answer of a broker which is already down. Right now, I have no idea how to fix this issue on the broker side.

Ah right. I thought this was related to the publishing of the on-close message (which is what the referenced commit fixed).
This is just the node timing out when trying to disconnect.. which is indeed odd. I'll investigate.

The message Nick is referring to in the last paragraph is the one configured in the "Messages" tab for the MQTT-in/out's config node that includes the broker connection details.
These are the Birth/Close/LWT messages. It doesn't make much sense to have any (OK, may be the Birth message) of these messages if the broker is in the same process as the client as they will only fire when the broker is very likely to be in the process of restarting as well.

having the same issue on RaspberryPi with:
Node-RED version: v1.3.5
node.js version: v12.22.1
npm version: 6.14.12
Platform/OS: RaspiOS
Browser: Chrome and Firefox

@emc02 Just to be clear, what broker are you using?

I am using aedes broker and connecting to zigbee2mqtt
It worked fine till I upgraded yesterday to latest version of nodered and broker.

I have this problem too, with an external broker on a separate VM. I use for this:

vernemq v1.11.0
Node-Red v1.3.5

The MQTT broker node is configured with the MQTT protocol version 3.1.1 and there are no messages configured on connection, before disconnecting or unexpected disconnection.

The issue still exists with Node-RED version 2. Is there any fix available?

Same problem here. Any update? Thanks!

Hello Together
after updating from 2.2.0 to 2.2.1 I have the same Behavior.

The update was done by script:
https://nodered.org/docs/getting-started/raspberrypi
I have already completely deleted the flow and recreated by hand. The first 4 or 5 deploys were fast. After that the behavior happened again.

@denonbw This issue is all about using node-red-contrib-aedes.
If you have a problem when using an external broker (mosquitto) then it is very unlikely to be related to this as it is caused by the broker (aedes) being shutdown before the mqtt node connected to it tries to send it's last message.
Given your flow doesn't appear to be using birth or close messages again not likely to be related to this issue. I suggest you open a new issue and include all the relevant data (including the Node-RED log output covering the period before and after the deploy)

Same problem after update

2.2.0 to 2.2.1
mosquitto version 2.0.13
nodejs v16.14.0

@sanyafifa  can you supply Node-RED logs from before and after a deploy and the broker logs from the same period. Along with the type of deploy (full, changed flows, changed nodes).

@sanyafifa
As well as you logs, can you describe you setup (OS, Hardware, direct connection to internet? behind proxy?)
AND
provide a list of installed contrib nodes

Same here since updating from v2.2.0 to v2.2.1.

@Paul-Reed
Hi Paul, I see aedes in your screenshot but I don't say it listed in your nodes.
What gives?
Are you using aedes as a broker in your node-red?

Aedes broker is running on a cloud server, which has not been edited, or even the server accessed during the past few weeks.
The client is running on my local Pi, using the default MQTT 'in node'
The error message occurred immediately after updating my local Pi from  v2.2.0 to v2.2.1 (in the local Pi debug), and every time I restart flows.
The node-RED log shows this problem when my local Pi closes down;
15 Feb 23:49:42 - [info] Stopping flows
15 Feb 23:49:42 - [info] serial port /dev/ttyAMA0 closed
15 Feb 23:49:57 - [error] [mqtt in:Aedes test] Error stopping node: Close timed out
15 Feb 23:49:57 - [error] [mqtt in:Dummy] Error stopping node: Close timed out
15 Feb 23:49:57 - [error] [mqtt in:3e51925c4519d148] Error stopping node: Close timed out
15 Feb 23:49:57 - [info] Stopped flows

When node_RED restarts, If I search amongst my Cron+ log entries... :mute:
The only Aedes entry I see is;
15 Feb 23:49:59 - [info] [mqtt-broker:aedes mqtt] Connected to broker: mqtt://<IP_ADDRESS>:1883

In fact, it's not confined to Aedes.
In the  stopping flows log (my last post above) the entry;
15 Feb 23:49:57 - [error] [mqtt in:Dummy] Error stopping node: Close timed out
That is a standard MQTT 'in node', which is connected to the remote cloudmqtt.com broker on port 15069.
Both Aedes & cloudmqtt have been happily working for a number of months, and these errors have only started after updating to node-RED v2.2.1, and worked fine under v2.2.0.

If you can't replicate, I'm around today, and will gladly help wherever I can.

For me it is not an pressing problem, so I can wait until the problem is found. The deploy works, it just takes a long time and returns an error.
Maybe it will become a problem when more and more instances are updated to 2.2.1 and more people have the bug.
Sorry for not opening a new issues and posting it here in the wrong one.

@knolleary
Thanks for responding :)
Deployment took longer. For me it's not critical.
How can you help with debugging?

@Steve-Mcl
Tell the command how to downgrade correctly?

In node_modules, I see mqtt.js, but checking it's package.json, it's showing v4.2.8 and not v4.3.5 as mentioned above.

@Steve-Mcl
version 4.2.8

The version of the mqtt module we care about is under the Node-RED install, not in your .node-red directory.
Please have a look under /usr/lib/node_modules/ and/or /usr/lib/node_modules/node-red/

@Steve-Mcl so is that npm install<EMAIL_ADDRESS>-g from /usr/lib/node_modules/node-red ?

No...
npm install<EMAIL_ADDRESS>from /usr/lib/node_modules/node-red

sudo is required, otherwise is fails through lack of permission
But downgraded to v4.3.4, restarted and tested.
Can confirm that the Error message still re-occurs.

I'm also encountering this issue since updating to the newest docker container. nodered 2.2.1

@Paul-Reed did you leave off the  -g

Yes.  sudo npm install<EMAIL_ADDRESS>I've also double checked the downgraded version number in it's package.json - (4.3.4)

i downgraded the mqtt version to 4.3.4.
sudo npm install<EMAIL_ADDRESS>The error is still there :(

An updated for those waiting a solution.
I now understand the issue (race condition between in/out nodes closing vs broker disconnecting AND MQTT lib change of when it raises close events between v4.2 and v4.3) and I am working on a number of angles / solutions.
TVH: I rarely use full deploy so hadn't noticed this however I suspect the issue has been present since I added Dynamic subscriptions to MQTT 4 months ago 😱
Should have an update for you today or tomorrow 🤞

Thanks Steve, however I'd be surprised if it has been present 4 months, as I updated to node-RED v2.2.0 on 29th Jan, and this problem did not occur until I updated to v2.2.1 yesterday.
Of late, I've been rebooting my Pi quite a lot, and am confident that I would have noticed.

Have you recently started using FULL DEPLOY?  Or recently started changing MQTT nodes?
The issue is related to when either a FULL DEPLOY or a PARTIAL/NODE DEPLOY causes all MQTT in/out nodes to be closed
In other words, if you have been moving flows around and happened to affect all MQTT in/out nodes that are related to 1 broker, you can trigger this timing issue.
No matter anyhow. Perhaps it is better to say, all the elements of the problem have been in place since dynamic MQTT however a number of other factors (MQTT client internal changes) have highlighted the issue.

mosqutto log using FULL DEPLOY NR:
1645025868: Client mqttjs_24e6b775 disconnected.<PHONE_NUMBER>: New connection from <IP_ADDRESS>:60960 on port 1883.<PHONE_NUMBER>: New connection from <IP_ADDRESS>:60962 on port 1883.<PHONE_NUMBER>: New client connected from <IP_ADDRESS>:60960 as mqttjs_ad2fe142 (p2, c1, k60).<PHONE_NUMBER>: New client connected from <IP_ADDRESS>:60962 as nodered_897808d04322b0bc (p2, c1, k15).

Have you recently started using FULL DEPLOY?

This issue was introduced in v2.2.1 . i always use full deploy

Update: I have a working fix but I will be spending a lot more time trying various scenarios, including the aedes issue mentioned earlier in this thread before I publish. Possibly tomorrow or Friday.
In the meantime, please sit tight (or avoid full deploys if you can)

Same problem.  Thanks!

2.2.2 Works great! Thanks for the quick fix

I'm using the Home Assistant Node Red plugin.  I get the error if I go from nodered_11.0.2 to 11.0.3.
I'm using https://www.home-assistant.io/integrations/mqtt as my broker.

@quadhammer those version numbers are home assistant versions not node-red versions. What version number of node-red  do you see if you look in the nodes hamburger menu?

when is v2.2.2 being released in home assistant?

@jonascoenen005 that is not a question the Node-RED community can answer, we have no input into when Home Assistant release things

@quadhammer those version numbers are home assistant versions not node-red versions. What version number of node-red do you see if you look in the nodes hamburger menu?

Node-RED v2.2.0

I get the error if I go from nodered_11.0.2 to 11.0.3.

Node-RED v2.2.0

@quadhammer  hopefully now you can see you are not on 2.2.2 which contains this fix. The node-red community has no control or influence on when HA release updates.
In the short term, until HA release an update, I suggest you stick to node deploys (instead of full deploys) to reduce the occurrence of this timeout.

now you can see you are not on 2.2.2 which contains this fix.

Yes, thanks.  The latest one is: "Bump node-red from 2.2.0 to 2.2.1 in /node-red" so it shouldn't be too far behind.  I'm sticking with 2.2.0 which doesn't seem to have the problem, even with full deploys.
Cheers!

I do have the same problem
Error stopping node: Close timed out
using:
node-red-contrib-tasmota
0.9.12
Tasmota Button
Tasmota Generic
Tasmota Light
Tasmota Sensor
Tasmota Switch
**tasmota-mqtt-broker**

some Tasmotadevices won't be found anymore.
2.2.2: Maintenance Release
Nodes
Fix "close timed out" error when performing full deploy or modifying broker node. (#3451) @Steve-Mcl

@Mark-Muc this is more likely an issue with that node & you should raise it on the tasmota nodes repository.

Also, @Mark-Muc to minimise / reduce the problem, use "modified nodes" instead of "full deploy" where possible.

@Steve-Mcl
that's what i do normaly . but to geht the devices online i habe to use "Full"
Mark_Muc


Add CouchDB

https://github.com/quangv/awesome-couchdb
This is an awesome curated resources list for CouchDB. CouchDB is one of the first document NoSQL databases.
By submitting this pull request I confirm I've read and complied with the below requirements.
Failure to properly do so will just result in the pull request being closed and everyone's time wasted. Please read it twice. Most people miss many things.

I have read and understood the contribution guidelines and the instructions for creating a list.
This pull request has a descriptive title. For example, Add Name of List, not Update readme.md or Add awesome list.
The entry in the Awesome list should include a short description about the list project/theme (not the list itself), and should be added at the bottom of the appropriate category.
The list I added

has been around for at least 30 days,
is the result of hard work and is the best I could possibly produce,
is a non-generated Markdown file in a GitHub repo,
is not a duplicate,
includes a succinct description of the project/theme at the top (example),
includes a project logo/illustration (whenever possible) at the top right of the readme (example). (The logo should link to the project website or any relevant website. The logo should be high-DPI, so set it to maximum half the width of the original image.),
only has awesome items with descriptions (Awesome lists are curations of the best, not of everything),
contains the awesome badge on the right side of the list heading,
has a Table of Contents section named Contents as the first section,
has an appropriate license (Meaning something like CC0, NOT a code licence like MIT, BSD, Apache, etc) (If you use a license badge, it should be SVG, not PNG),
has contribution guidelines,
doesn't include a Travis badge,
has been checked for inconsistent formatting, spelling, and grammar:

Each link description starts with an uppercase character and ends with a period.
Drop all the A / An prefixes in the descriptions.
Consistent naming. For example, Node.js, not NodeJS or node.js.

includes a succinct description of the project/theme at the top (example),

Not followed

has a Table of Contents section named Contents as the first section,

Not followed

has an appropriate license (Meaning something like CC0, NOT a code licence like MIT, BSD, Apache, etc)

Not followed

has contribution guidelines,

Not followed

Each link description starts with an uppercase character and ends with a period.

Not followed

@sindresorhus k I made the changes. How is it now?
Thanks.

(If you use a license badge, it should be SVG, not PNG),

:arrow_up: (See the one used in this repo)

Official CouchDB Blog => Official Blog
Official CouchDB Docs => Official Docs
And many more cases
Mailing lists description => Mailing Lists Description
StackOverflow => Stack Overflow
Resources like articles and videos could use a description.

Curious why SVG instead of PNG?

Less is more, I like it. Ok, I found the a svg, and made the changes.

Thanks for the changes, only other thing I would say is that some of the resources could do with a description showing why they're awesome! :)

Resources like articles and videos could use a description.

Looks good apart from the point above - there could be some more descriptions to differentiate the links :)

Thanks Craig,
I added more descriptions to some of the links. Let me know if there's any other resources you think could use a description.


Provide access to historical json files

I'd like it if this repo stored the historical json files with slightly more metadata.
The current use case I'm considering is to build a json api on top of these files to, for example, filter and return all changes to a character throughout patches.
If the json file format was changed slightly to have some top level data (patch #, release date)
we could build an even more useful api that could look at a historical replay, and show you the specific skills / multipliers a hero had at the time of the replay.
I saw the closed issue that is somewhat relevant. (https://github.com/nydus/heroesjson/issues/26)
I understand that historical data will be generally hard to reproduce, and that's ok.  I still think it would be something useful to have going forward.

The structure was created before I started the project.  I will not change it at this time.


"requires string as left operand, not list"

OS: Arch
organize v1.4.2
organize config --debug -> no errors
organize sim

/usr/lib/python3.7/site-packages/organize/config.py:28: YAMLLoadWarning: calling yaml.load() without Loader=... is deprecated, as the default Loader is unsafe.

Full Log
2019-08-01 15:48:38,434 - organize.main - ERROR - 'in <string>' requires string as left operand, not list
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/organize/main.py", line 102, in main
    execute_rules(config.rules, simulate=args['sim'])
  File "/usr/lib/python3.7/site-packages/organize/core.py", line 80, in execute_rules
    jobs = list(find_jobs(rules))
  File "/usr/lib/python3.7/site-packages/organize/core.py", line 47, in find_jobs
    if all(f.matches(path) for f in rule.filters):
  File "/usr/lib/python3.7/site-packages/organize/core.py", line 47, in <genexpr>
    if all(f.matches(path) for f in rule.filters):
  File "/usr/lib/python3.7/site-packages/organize/filters/filename.py", line 70, in matches
    self.contains in filename)
TypeError: 'in <string>' requires string as left operand, not list
2019-08-01 15:48:55,504 - organize.main - ERROR - 'in <string>' requires string as left operand, not list
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/organize/main.py", line 102, in main
    execute_rules(config.rules, simulate=args['sim'])
  File "/usr/lib/python3.7/site-packages/organize/core.py", line 80, in execute_rules
    jobs = list(find_jobs(rules))
  File "/usr/lib/python3.7/site-packages/organize/core.py", line 47, in find_jobs
    if all(f.matches(path) for f in rule.filters):
  File "/usr/lib/python3.7/site-packages/organize/core.py", line 47, in <genexpr>
    if all(f.matches(path) for f in rule.filters):
  File "/usr/lib/python3.7/site-packages/organize/filters/filename.py", line 70, in matches
    self.contains in filename)
TypeError: 'in <string>' requires string as left operand, not list

The YAMLLoadWarning is fixed in the new versions. Please update with pip3 install -U organize-tool
The filename filter only supports simple strings for the contains: keyword. Support for lists will come in the next version.

Thanks!

I just published v1.5.3 which supports lists in the filename filter 👌


Correcting the datagrid variable names

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] If applicable, have a visual design approval

PR Type
What kind of change does this PR introduce?

[x] Bugfix
[x] Feature
[x] Code style update (formatting, local variables)
[x] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] CI related changes
[ ] Documentation content changes
[ ] clarity.design website / infrastructure changes
[ ] Other... Please describe:

What is the current behavior?

Issue Number: #6599
What is the new behavior?
As is
Does this PR introduce a breaking change?

[ ] Yes
[x] No

Other information

Thanks, @anooptp ! We appreciate the contribution. Last steps here would be a rebase to handle the branch conflict and a final review from another team-member.
Thanks so much!
CC: @steve-haar @hippee-lee

Thank you @mathisscott . Have corrected the merge conflict.

I would like to ask you to change the commit message to chore(angular:datagrid): correcting datagrid variable names for expandable

@bbogdanov Sure, I will change the commit message.
Any reason for build failure...? Build logs are not clear.

I would like to ask you to change the commit message to chore(angular:datagrid): correcting datagrid variable names for expandable

@bbogdanov Sure, I will change the commit message. Any reason for build failure...? Build logs are not clear.

It failed a code linting/formatting check step.
When you change the commit message, run npm run format to get a list of the files that need fixing. Then run npm run format:fix path/to/file.ts on the files it returns.

It failed a code linting/formatting check step.
When you change the commit message, run npm run format to get a list of the files that need fixing. Then run npm run format:fix path/to/file.ts on the files it returns.

I ran the above mentioned command, however it didn't list any files. Am I missing something.

Look at the build details, it looks like it doesn't like something in this file...
projects/angular/src/data/datagrid/datagrid-row-detail.ts
Try running npm run format:fix projects/angular/src/data/datagrid/datagrid-row-detail.ts

@anooptp : so to fix the build, you'll need to run npm run golden:fix && npm golden:save in terminal from the root /clarity directory. this will update the file that informs us of breaking changes to the public API (our "golden" file).
after doing that, you'll want to squash the commits down again. thanks!

I am getting below error:

I am getting below error:

I'm sorry. You ran the command I gave you but I gave you the wrong command. It should be npm run golden:fix && npm run golden:save.
Maybe that will help?

npm run golden:fix && npm run golden:save

The first query itself is failing, and it is not executing the second one.

I'm sorry. You ran the command I gave you but I gave you the wrong command. It should be npm run golden:fix && npm run golden:save.
Maybe that will help?

@mathisscott - do we need to run this command pre-commit or post-commit.
Currently, I am running this command with changed files in git staged on a Windows 11 machine using git bash.
Am I missing something?

@anooptp
I apologize for these challenges. This is usually a lot easier. Let's check to see if you have the npm package that the golden commands try to run.
Try npm view ts-api-guardian in your terminal and see if it returns anything.
If it doesn't, then try doing a fresh npm install (or just installing that package directly at version 0.6.0.
If it does, then we may be seeing an issue with git bash and I may need to step in and get this branch fixed up for you.

Yes, ts-api-guardian is installed. PFB the screenshot:

This may be a git bash problem then. Something that package/script is trying to do that is not simpatico with git bash.
I'll finish this out. Thank you so much for your contribution @anooptp . I do appreciate it!

Ported this PR to https://github.com/vmware/clarity/pull/6669
Thanks @anooptp .

Thank you @mathisscott for you inputs.


Can't write data to influxdb

Hei Influxdata
Thank you for providing InfluxDB!
We're playing around with it at the university as part of my studies. I'm trying to write data using the influxdb-client-r.
I'm having some issues writing data to InfluxDB. Everything seems to be going well but there's no data attached to the bucket.
Maybe you can see what I'm doing wrong? Writing data with the python client is working.
> client$health()
$name
[1] "influxdb"

$message
[1] "ready for queries and writes"

$status
[1] "pass"

$version
[1] "2.6.1"

$commit
[1] "9dcf880"

> head(data)
   measurement                                time             x          y           z           a
1 acceleration 2023-03-11T11:12:10.289279488+00:00  1.097191e-02 0.03415753 -0.06364671 -0.06364671
2 acceleration 2023-03-11T11:12:10.300296448+00:00  2.318415e-05 0.05538037 -0.05859122 -0.05859122
3 acceleration 2023-03-11T11:12:10.311343360+00:00 -1.529624e-03 0.05245288 -0.05928239 -0.05928239
4 acceleration 2023-03-11T11:12:10.322391552+00:00 -1.915855e-02 0.05766852 -0.04586967 -0.04586967
5 acceleration 2023-03-11T11:12:10.333395456+00:00 -9.410526e-03 0.06199387 -0.05430975 -0.05430975
6 acceleration 2023-03-11T11:12:10.344455424+00:00 -1.272957e-02 0.07212170 -0.05127688 -0.05127688

response <- client$write(
    x = data,
    bucket = influxdb$bucket,
    precision = "ns",
    measurementCol = "measurement",
    tagCols = NULL,
    fieldCols = c("a", "x", "y", "z"),
    timeCol = "time",
    object = "lp"
)

> response
NULL
> head(lp[[1]])
[1] "acceleration a=-0.06364671397,x=0.01097190845,y=0.03415752893,z=-0.06364671397<PHONE_NUMBER>289"
[2] "acceleration a=-0.05859122045,x=2.318415073e-05,y=0.05538037273,z=-0.05859122045<PHONE_NUMBER>300"
[3] "acceleration a=-0.05928239332,x=-0.001529623763,y=0.05245288198,z=-0.05928239332<PHONE_NUMBER>311"
[4] "acceleration a=-0.0458696709,x=-0.01915854827,y=0.05766851612,z=-0.0458696709<PHONE_NUMBER>322"
[5] "acceleration a=-0.05430974754,x=-0.009410526002,y=0.06199386599,z=-0.05430974754<PHONE_NUMBER>333"
[6] "acceleration a=-0.05127688358,x=-0.01272957006,y=0.07212170488,z=-0.05127688358<PHONE_NUMBER>344"

The only curious thing I'm seeing is the following log entries. But I'm honestly not sure what to do with them =/
Mar 12 10:41:50 archlinux influxd[289890]: ts=2023-03-12T09:41:50.637618Z lvl=error msg="Unable to write gathered points" log_id=0gWDzxlG000 service=scraper scraper-name="new target" error="database not found: 5826473e9bf79949"
Mar 12 10:42:00 archlinux influxd[289890]: ts=2023-03-12T09:42:00.643621Z lvl=error msg="Unable to write gathered points" log_id=0gWDzxlG000 service=scraper scraper-name="new target" error="database not found: 5826473e9bf79949"

Hi, the errors in the log are unrelated.
The line protocol output contains timestamp in ms precision, no idea why, could be a bug. So the problem is that server is interpreting timestamp values as nanoseconds and that makes it time from the beginning of unix epoch. The workaround could be to set precision to ms (and check line output after write() protocol again if it matches the precision, you can use eg. https://www.epochconverter.com for validation).
Btw, is time column of nanotime or POSIXct type?

I've tried both. Seems like I forgot to adapt the parameter when I created the ticket. The precision in the line protocol matches the parameter of the write function. However in the bucket there's no new entry for the measurement. Which leads to the assumption that the data is never written.
Here we go again:
> as_tibble(data)
# A tibble: 3,161 × 6
   measurement  time                                         x      y       z       a
   <chr>        <nanotime>                               <dbl>  <dbl>   <dbl>   <dbl>
 1 acceleration 2023-03-11T11:12:10.289279488+00:00  0.0110    0.0342 -0.0636 -0.0636
 2 acceleration 2023-03-11T11:12:10.300296448+00:00  0.0000232 0.0554 -0.0586 -0.0586
 3 acceleration 2023-03-11T11:12:10.311343360+00:00 -0.00153   0.0525 -0.0593 -0.0593
 4 acceleration 2023-03-11T11:12:10.322391552+00:00 -0.0192    0.0577 -0.0459 -0.0459
 5 acceleration 2023-03-11T11:12:10.333395456+00:00 -0.00941   0.0620 -0.0543 -0.0543
 6 acceleration 2023-03-11T11:12:10.344455424+00:00 -0.0127    0.0721 -0.0513 -0.0513
 7 acceleration 2023-03-11T11:12:10.355487488+00:00 -0.0335    0.0917 -0.0506 -0.0506
 8 acceleration 2023-03-11T11:12:10.366540544+00:00 -0.0244    0.0648 -0.0383 -0.0383
 9 acceleration 2023-03-11T11:12:10.377567488+00:00 -0.0273    0.0749 -0.0353 -0.0353
10 acceleration 2023-03-11T11:12:10.388614400+00:00 -0.0254    0.0972 -0.0203 -0.0203
# … with 3,151 more rows
# ℹ Use `print(n = ...)` to see more rows
> response <- client$write(
+     x = data,
+     bucket = influxdb$bucket,
+     precision = "ns",
+     measurementCol = "measurement",
+     tagCols = NULL,
+     fieldCols = c("a", "x", "y", "z"),
+     timeCol = "time",
+     object = "lp"
+ )
'tagCols' is empty
> head(lp[[1]])
[1] "acceleration a=-0.06364671397,x=0.01097190845,y=0.03415752893,z=-0.06364671397<PHONE_NUMBER>289279488"
[2] "acceleration a=-0.05859122045,x=2.318415073e-05,y=0.05538037273,z=-0.05859122045<PHONE_NUMBER>300296448"
[3] "acceleration a=-0.05928239332,x=-0.001529623763,y=0.05245288198,z=-0.05928239332<PHONE_NUMBER>311343360"
[4] "acceleration a=-0.0458696709,x=-0.01915854827,y=0.05766851612,z=-0.0458696709<PHONE_NUMBER>322391552"
[5] "acceleration a=-0.05430974754,x=-0.009410526002,y=0.06199386599,z=-0.05430974754<PHONE_NUMBER>333395456"
[6] "acceleration a=-0.05127688358,x=-0.01272957006,y=0.07212170488,z=-0.05127688358<PHONE_NUMBER>344455424"
> influxdb$bucket
[1] "bfh-bucket"

As a side note: I've executed client$write without starting the server first and didn't get an error in the response. This most likely is a bug?

I can see the problem now. The write is not executed. There is 'tagCols' is empty warning. The client does not allow to write such data.
You can add a column (with string constant as value, if you do not intend to use it) and specify non-NULL tagCols.

Thanks for the quick response.
I tried it with non-NULL tagCols and am seeing the same result.
Seems wierd that the r-client enforces the tag and python-client does not. If I remember the documentation correctly tags are optional for the DB. If that is the case I'd say that's a bug.
Still looks as if write is not executed. The write command still passes without error even though my DB is not running.

Maybe the following gist helps you reproduce the issue on your side. I've shortened the data significantly everything else is very close to my local code.
https://gist.github.com/troubas/0680903d26c438954dfc254c8fc38a7d

Okay yeah. I found the issue. I quickly started using the 'lp' parameter of the write function not realizing it prevents actual writes to the DB :see_no_evil:
https://github.com/influxdata/influxdb-client-r/blob/master/R/influxdb_client.R#L241-L245


add about me update by faiz nurullah

Why:

This is for study purposes only, I can't give a solution to the problem in this main repository.
Closes [-]

What's being changed:

Iam add about me on file readme.md in my branch (readme-faiznurullah)

Check off the following:

[x] I have reviewed my changes in staging (look for "Automatically generated comment" and click Modified to view your latest changes).
[x] For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

[ ] This pull request impacts the contribution experience

[ ] I have added the 'writer impact' label
[ ] I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

This is frist my contribution in github repository, please review guys


highlighting tailwind class directives

First, I"m happy with seeing highlighting instead of a single color, so thank you for your work!
It's fairly obvious why the below happens, but just pointing it out.

Possible to limit parsing to x-*= @data-name= :data-name= maybe?
I have a feeling the x- directive is being removed in future Alpine releases however.

@shaynem That's a good point! In reality, it's really not so much an issue with the grammar selection as it is with where the grammar is being injected. By changing the injection selector from L:text.html which allows the syntax to be injected anywhere to L:meta.tag -meta.attribute which only allows it to be injected within an HTML tag but not within the attribute itself, you get proper highlighting.

I just published a patch to the extension that implements this change. It should update automatically and fix this issue!

It seems that it's still a problem for anything other than HTML files.


Add feature to search through all open panes instead of just active pane

Fixes #34: Add feature to search through all open panes instead of just the active one, a preference to control this, and the ability to invert the current preference with Shift-Enter.
@izuzak Sorry about creating a second PR, I got confused about how to rebase and screwed up the other branch.

@tmunro Thanks! I think this looks good, just had a few comments (thanks @mnquintana! :metal:).
@nathansobo -- you commented on #34 which this PR will close. Do you have some :hourglass: to take a look at this as well?

Thanks for this, I'm going to merge it and then make a few minor changes on master and will link the commit here so you can see what I tweaked.

Here were the tweaks I made, really minor stuff: https://github.com/atom/fuzzy-finder/commit/b44656b239ffb0566465c8e8efffc2f51855d229
Typically in packages and core we try to pass around options objects instead of boolean parameters so they are easier to understand when reading lines calling those methods such as:
@openPath(filePath, false)

versus:
@openPath(filePath, searchAllPanes: false)

Good to know! Happy to help in my own small way, thanks for merging and making those changes.

I also tweaked the fuzzy-finder:invert-confirm keybinding to only be enabled on the mini editor inside the fuzzy finder view. Previously it was registered globally.
https://github.com/atom/fuzzy-finder/commit/9b856d2155c7501ebb81e3adab00f0d6416407bf


Document which babel presets/plugins are required

Since the latest version of Babel stating 'Babel required' in the koa docs is no longer meaningful as by default it does nothing, and you have to configure which syntax it should transpile. At the very least koa needs to document which plugins are required. Even better would be a table indicating which plugins are required for given environments (e.g. none are needed for koa 1 on node 4, but very many are needed for koa 2 on 0.12... I'm currently struggling to figure out what babel transforms are needed to run koa 2 on node 5)

https://github.com/koajs/koa/blob/master/docs/api/index.md#async-functions-with-babel
sorry i think i just need to update the website!

also, koa 2 is node@4+. i guess if you wanted it on 0.12, you would just also use es2015

Thanks for the pointer. It turns out I had chosen the right transform, but still struggling to get koa2 working. I get the following error:
    if (isGeneratorFunction(fn)) throw new TypeError('Support for generators has been removed. See the documentation for examples of how to convert old middleware https://github.com/koajs/koa#example-with-old-signature');

Looking at the koa src this kinda makes sense - async is converted to generator, which koa2 explicitly prohibits from being used - but how do I stop it happening? To I need to have babel-core transpile koa too?

Ah no, figured it out now. I needed to wrap koa-static and koa-router in koa-convert

You can use the preset stage-0 to enable async functions in Babel.

For<EMAIL_ADDRESS>

node version
babel preset

5.0
es2015-node5, stage-3

4.0
preset: es2015-node5, stage-3. plugin: es2015-spread

0.12
es2015, stage3

Dont you just need an async transformer? What other new stuff does koa v2 rely on?
I didnt think it used anything else specifically

yep, you just need the transformer. the presets contain much more-- you may want these, but you 100% don't need them to use Koa with async functions if you have node 4+.

forgive the plug, but if you're using Node 5.x and are specifically building server-side stuff (i.e. not webpack'ing front-end assets), check out my node5 preset for babel
It has async/await.

I've just used @leebenson's preset for a project, works flawlessly! Its not minimal requirement for Koa but very useful nonetheless.

thanks @mattstyles - I've literally just this second bumped the version, too.

they are in the v2 docs. let me know how we can improve it, but we can close it for now.
yes, there's a lot of presets you can use, but the last thing we want to do is add them all to the docs :)


right-to-left languages

Everything is working well, but I was wondering if you could address the issue of right-to-left languages, such as Arabic and Persian

Could you provide me an example? What is the issue?

For example, all symbols instead of the end of the line go to the beginning of the line.

And in this example, where an English word was added to the text, the entire sentence became scrambled and ruined.
I think this might help
https://stackoverflow.com/questions/69424382/fixing-rtl-texts-from-logical-to-visual-before-embedding-in-video-as-subtitle

import pysrt
from collections import Counter
import unicodedata as ud

def dominant_strong_direction(s):
    count = Counter([ud.bidirectional(c) for c in list(s)])
    rtl_count = count['R'] + count['AL'] + count['RLE'] + count["RLI"]
    ltr_count = count['L'] + count['LRE'] + count["LRI"]
    return "rtl" if rtl_count > ltr_count else "ltr"

def convert_srt_to_rtl(input_file, output_file):
    subs = pysrt.open(input_file)
    for sub in subs:
        if dominant_strong_direction(sub.text) == "rtl":
            sub.text = "\u202b" + sub.text + "\u202c"
    subs.save(output_file, encoding='utf-8')

if __name__ == "__main__":
    input_file = "subtitle.srt"
    output_file = "subtitle_rtl.srt"
    convert_srt_to_rtl(input_file, output_file)

Hey, brother, I've written this and it works really well. Please try to incorporate it into the project. For instance, if the target language is Persian, we can use it to ensure the subtitles are generated correctly.

Hi, I'll see what I can do and I'll let you know ;)

@Theamoz can you provide a .srt file and a target language for me to test?

I've done some changes here. @Theamoz can you provide a .srt file and a target language for me to test? I'll translate and give it back to you so you can check if it worked.
sure
The first file, named 'en', has not been translated yet and the target language is Persian The second file, named 'fa', has been translated and the RTL issue has been resolved .
The final output should match the 'fa' file.

Ok, just did a translation. Can you check the result?
001 fa2 test.zip

it's perfect.


Extended enum can't be used as type in extended interface

TypeScript Version:  3.9.2 and 4.0.0-dev.20200514

Search Terms: TS2430 TS2535
Code
enum BaseEnum {
    A = 0,
}

enum ExtendedEnum {
    A = BaseEnum.A,
}

interface IBaseType {
    field: BaseEnum.A;
}

interface IExtendedType extends IBaseType {
    field: ExtendedEnum.A;
}

Expected behavior:
A field in both enums is obviously the same, hence interfaces should be fully compatible too.
Actual behavior:
2 errors, which may in fact be 2 separate issues, but I'm not 100% sure:
Interface 'IExtendedType' incorrectly extends interface 'IBaseType'.
  Types of property 'field' are incompatible.
    Type 'ExtendedEnum' is not assignable to type 'BaseEnum'.(2430)
Enum type 'ExtendedEnum' has members with initializers that are not literals.(2535)

Playground Link: https://www.typescriptlang.org/play/?ts=4.0.0-dev.20200512&ssl=1&ssc=1&pln=2&pc=11#code/KYOwrgtgBAQghgZ2AUXNA3gKCjqBBKAXigAYAaTAX001EimQA8AXUAE2DdXq13yNiIUaAHR4K1TAEsQrAE4AzOAGNgUAJLwkAFQCeABzW9cCqcAA2bAFyCk3CGIDcVGjPlLVGpqxAc2ewyhgFnYEDS1gAKNsEzNLG292TnsnFyA
Related Issues: https://github.com/microsoft/TypeScript/issues/20920

Enums are intentionally not assignable to each other like that; this is one of their reasons for existing.

I'm not extending enums per say, I'm using its variants as values. And it works just fine except when in extended interface.


Extend API-Testing.md

Document Name:
API-Testing.md
Task:
The API-Testing.md document provides guidelines and instructions for testing the API endpoints. It should include information about authentication, request and response formats, and usage examples. It needs further expansion and improvement to cover more request examples and provide comprehensive guidance for developers and testers.

Close as completed.


Auto-update onnx to v1.16.0

New version of onnx detected (package version: nil, last github version: v1.16.0)

Hi @waruqi, not sure how you are generating the auto update PRs but could you run this script again for onnxruntime as well? Version 1.18.0 was published 2 days ago and it's needed so I don't have to use legacy CuDNN

you can open a pr to update it.


ci: dependabot changeset push to use REPO_TOKEN

I believe that this is the same issue that plagued the changeset PR, which was solved in #1848.

closes #2559

Good find, to test this I wonder if we could fork this repo, create a test secret REPO_TOKEN, then modify the dependabot interval to force it to open a PR and then see if the workflow runs there?

@maschad I'm fairly certain that this is the root cause because this solution solved the same problem in #1848. IMO we don't need to go out of our way to test it; merging and verifying the behavior live is okay in this case because, even if this PR is a wrong solution, the workflow itself doesn't block anybody from work nor is it of crucial, "we must get this right the first time" importance.


Dev rebase

Merged with main

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.10 out of 12 committers have signed the CLA.:white_check_mark: Tarraann:white_check_mark: namansleeps:white_check_mark: anisha1607:white_check_mark: luciferlinx101:white_check_mark: nborthy:white_check_mark: NishantBorthakur:white_check_mark: TransformerOptimus:white_check_mark: Fluder-Paradyne:white_check_mark: AdarshJha619:white_check_mark: jedan2506:x: namansleeps2:x: boundless-asuraYou have signed the CLA already but the status is still pending? Let us recheck it.


[Node.js] Add Options API to colorizer and new options

@halton This change is to align our colorizer API with native side, PTAL, thanks.

@halton Thanks for the comments, I have updated and pushed a new commit.

@halton I have updated the commit, thanks.


Error in the TI datas

There is an error in the total positive cases of 04.04.20 of Ticino. The real data is 2’442 positive cases and not 2422. The reported number of positives of 05.04.20 is indeed correct.
(see: https://www4.ti.ch/area-media/comunicati/dettaglio-comunicato/?NEWS_ID=187575&tx_tichareamedia_comunicazioni[action]=show&tx_tichareamedia_comunicazioni[controller]=Comunicazioni&cHash=4b3f64139a9dd36b9fd30a1ace23654a)

Checking, thans

Looks like a human error during a review in https://github.com/openZH/covid_19/commit/aae4e7ee0555883b24a99798ab88cca53c68e0ae by @viktoria023 ?
TI scraper did scrape 2422:
...
TI 2020-04-04T08:00    2442     165 OK 2020-04-04T11:05:45+02:00 # Extras: ncumul_released=287,ncumul_hosp=370,ncumul_ICU=75,ncumul_vent=67 # URLs: https://www4.ti.ch/dss/dsp/covid19/home/, https://www4.ti.ch/area-media/comunicati/, https://www4.ti.ch/area-media/comunicati/dettaglio-comunicato/?NEWS_ID=187570&tx_tic
...

Corrected the row, we're in contact with TI to raise awareness. Hopefully we'll see more easily readable publications soon.


update README for JS API

I found no docs about the JS API, so I started them.

And it's a very good start! Thank you.