lvgl/lvgl.h : no such file or directory

Hello everyone,
I tried installing the pc simulator for windows. I firstly tried to make it work on eclipse and got the following error :
23:25:14 **** Incremental Build of configuration Debug for project lv_sim_eclipse_sdl-master ****
make all
'Building file: ../main.c'
'Invoking: Cross GCC Compiler'
gcc -I"C:\Users\pauld\Documents\Eclipse Workspace\lv_sim_eclipse_sdl-master" -O0 -g3 -Wall -c -fmessage-length=0 -Wall -Wmaybe-uninitialized -MMD -MP -MF"main.d" -MT"main.o" -o "main.o" "../main.c"
../main.c:16:10: fatal error: lvgl/lvgl.h: No such file or directory
 #include "lvgl/lvgl.h"
          ^~~~~~~~~~~~~
compilation terminated.
make: *** [subdir.mk:23: main.o] Error 1
"make all" terminated with exit code 2. Build might be incomplete.

23:25:19 Build Failed. 2 errors, 0 warnings. (took 4s.473ms)

I then tried to make it work on codeblocks (as I read on an other issue that it was easier to make it work). But same problem again as you can read :
||=== Build: Debug in LittlevGL (compiler: GNU GCC Compiler) ===|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_drivers\display\fbdev.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_drivers\display\monitor.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_drivers\display\R61581.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_drivers\display\SSD1963.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_drivers\display\ST7565.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_drivers\indev\AD_touch.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_drivers\indev\evdev.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_drivers\indev\FT5406EE8.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_drivers\indev\keyboard.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_drivers\indev\mouse.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_drivers\indev\XPT2046.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_drivers\win_drv.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_apps\benchmark\benchmark.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_apps\benchmark\benchmark_bg.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_apps\demo\demo.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_apps\demo\img_bubble_pattern.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_apps\sysmon\sysmon.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_apps\terminal\terminal.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_apps\tpcal\tpcal.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_group\lv_test_group.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_misc\lv_test_task.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_obj\lv_test_obj.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_arc\lv_test_arc.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_bar\lv_test_bar.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_btn\lv_test_btn.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_btnm\lv_test_btnm.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_canvas\lv_test_canvas.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_cb\lv_test_cb.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_chart\lv_test_chart.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_cont\lv_test_cont.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_ddlist\lv_test_ddlist.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_gauge\lv_test_gauge.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_img\img_flower_icon.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_img\lv_test_img.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_imgbtn\imgbtn_img_1.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_imgbtn\imgbtn_img_2.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_imgbtn\imgbtn_img_3.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_imgbtn\imgbtn_img_4.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_imgbtn\lv_test_imgbtn.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_kb\lv_test_kb.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_label\lv_test_label.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_led\lv_test_led.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_line\lv_test_line.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_list\lv_test_list.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_lmeter\lv_test_lmeter.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_mbox\lv_test_mbox.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_page\lv_test_page.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_preload\lv_test_preload.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_roller\lv_test_roller.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_slider\lv_test_slider.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_sw\lv_test_sw.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_ta\lv_test_ta.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_table\lv_test_table.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_tabview\lv_test_tabview.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_tileview\lv_test_tileview.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_objx\lv_test_win\lv_test_win.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_stress\lv_test_stress.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_theme\lv_test_theme_1.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tests\lv_test_theme\lv_test_theme_2.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\10_keyboard\lv_tutorial_keyboard.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\1_hello_world\lv_tutorial_hello_world.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\2_objects\lv_tutorial_objects.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\3_styles\lv_tutorial_styles.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\4_themes\lv_tutorial_themes.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\5_antialiasing\apple_icon_alpha.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\5_antialiasing\apple_icon_chroma.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\5_antialiasing\lv_tutorial_antialiasing.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\6_images\flower_icon_alpha.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\6_images\lv_tutorial_images.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\6_images\red_flower.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\6_images\red_rose_16.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\7_fonts\arial_20.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\7_fonts\lv_tutorial_fonts.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\8_animations\lv_tutorial_animations.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lv_examples\lv_tutorial\9_responsive\lv_tutorial_responsive.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\porting\lv_port_disp_template.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\porting\lv_port_fs_template.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\porting\lv_port_indev_template.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_core\lv_debug.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_core\lv_disp.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_core\lv_group.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_core\lv_indev.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_core\lv_obj.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_core\lv_refr.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_core\lv_style.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_draw\lv_draw.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_draw\lv_draw_arc.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_draw\lv_draw_basic.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_draw\lv_draw_img.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_draw\lv_draw_label.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_draw\lv_draw_line.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_draw\lv_draw_rect.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_draw\lv_draw_triangle.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_draw\lv_img_cache.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_draw\lv_img_decoder.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_font\lv_font.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_font\lv_font_fmt_txt.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_font\lv_font_roboto_12.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_font\lv_font_roboto_12_subpx.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_font\lv_font_roboto_16.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_font\lv_font_roboto_22.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_font\lv_font_roboto_28.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_font\lv_font_roboto_28_compressed.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_font\lv_font_unscii_8.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_hal\lv_hal_disp.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_hal\lv_hal_indev.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_hal\lv_hal_tick.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_anim.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_area.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_async.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_bidi.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_circ.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_color.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_fs.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_gc.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_ll.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_log.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_math.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_mem.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_printf.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_task.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_templ.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_txt.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_misc\lv_utils.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_arc.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_bar.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_btn.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_btnm.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_calendar.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_canvas.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_cb.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_chart.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_cont.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_cpicker.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_ddlist.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_gauge.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_img.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_imgbtn.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_kb.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_label.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_led.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_line.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_list.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_lmeter.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_mbox.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_objx_templ.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_page.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_preload.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_roller.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_slider.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_spinbox.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_sw.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_ta.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_table.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_tabview.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_tileview.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_objx\lv_win.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_themes\lv_theme.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_themes\lv_theme_alien.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_themes\lv_theme_default.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_themes\lv_theme_material.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_themes\lv_theme_mono.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_themes\lv_theme_nemo.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_themes\lv_theme_night.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_themes\lv_theme_templ.c|
||WARNING: Can't read file's timestamp: C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\lvgl\src\lv_themes\lv_theme_zen.c|
C:\Users\pauld\Downloads\lv_sim_codeblocks_win-master\lv_sim_codeblocks_win-master\main.c|13|fatal error: lvgl/lvgl.h: No such file or directory|
||=== Build failed: 1 error(s), 166 warning(s) (0 minute(s), 0 second(s)) ===|

I must say I'm a bit of a newbie here, I mostly code on the arduino ide or in python. What did I do wrong ?
Thanks !

You need to clone the CodeBlocks repository and update submodules. Downloading a ZIP from GitHub won't work.
git clone --recursive https://github.com/lvgl/lv_sim_codeblocks_win.git

Ho ! Thanks. It works now !


Update README.md

Added and If you have time, please do a pull request for me.

Thank you for your contribution!


feat: allow for tests over flightsql

closes #2234
There's still a bit of cleanup to do, but it seems to work.
I'm planning on refactoring the test suites a bit, currently they always spin up a pg instance, which is not needed at all for the flightsql tests.
My plan is to refactor them so the following commands are accepted
> just slt 'path/to/test' # default pg behavior
> just slt 'path/to/test' --protocol=rpc # equivalent to the current `just slt 'path/to/test' --rpc-test`
> just slt 'path/to/test' --protocol=flightsql # run the tests over the flightsql wire protocol
> just slt 'path/to/test' --protocol=postgres # run the tests over the postgres wire protocol. (same as the default)

12/12 updates.
There are a few additional changes to the following files that I introduced in this PR worth highlighting.
crates/sqlexec/src/session.rs

rename a few methods to make the intent clearer
add a few new helper methods for the flightsql client

crates/glaredb/src/server.rs
There were some bigger changes in here, namely to ComputeServer. To make the tests easier to run in isolation (pg/rpc/flightsql), I decided to refactor the compute server a bit to make the postgres server optional.
Previously, we would always start up a postgres instance, now it is fully optional. You can specify what protocols you want to be exposed -- TODO: cleanup the cli args for this --

12/12 updates pt 2.
This PR really got away from me.. A lot bigger than I had originally anticipated. sorry reviewers
Updated the CLI args to allow for postgres to be optional. Just to be safe, I added a bunch of additional tests to make sure nothing broke in the process. So there are some changes to the cli args to handle the new functionality.
The only breaking change is to how you run the tests. just slt 'path/to/test' --protocol=rpc instead of just slt 'path/to/test' --rpc-test.

Previously, we would always start up a postgres instance [...]

We should make sure to be clear what we mean by this. We're starting up a server implementing the pg protocol. By saying "postgres instance", that can lead to confusion as we're not starting up a postgres instance.

Previously, we would always start up a postgres instance [...]

We should make sure to be clear what we mean by this. We're starting up a server implementing the pg protocol. By saying "postgres instance", that can lead to confusion as we're not starting up a postgres instance.

yeah sorry, i meant a postgres compatible api here.


[Important]Test functions for our project!!

We need test functions for our project, especially since this is also a project requirement!!
Please create test functions for your code when adding stuff.

That's really a good point here. But I have a question.
Do everyone need to create its own test function, or can anyone help to create test function for any available code?
Let's say if I create function A, B, C and D.
Do I need to create the test function for A, B, C and D myself or can anyone help me with the test function?

we can end up together looking at writing these test functions


bigfix for decorator error handling

bugfix for decorators:
when there is an error when running the try block in the mspass_func_wrapper and inplace_return is True, we better return the original data object so that it won't block the downstream processing.

Codecov Report

Merging #236 (e9c9e67) into master (d36b300) will increase coverage by 0.07%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master     #236      +/-   ##
==========================================
+ Coverage   47.84%   47.92%   +0.07%
==========================================
  Files         118      118
  Lines       15346    15350       +4
==========================================
+ Hits         7343     7356      +13
+ Misses       8003     7994       -9

Impacted Files
Coverage Δ

python/mspasspy/util/decorators.py
67.12% <50.00%> (+1.49%)
:arrow_up:

cxx/src/lib/seismic/CoreSeismogram.cc
91.50% <0.00%> (+1.13%)
:arrow_up:

Continue to review full report at Codecov.

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


FITCount app - Argentina to live

Argentina have test the online version and are ready to move live.
There is not a rush for this, if it's easier we can wait and move Sweden live at the same time if that helps.
Thanks

It would be easier to release both SE and AR simultaneously to the public.

Thanks. Will have the warehouse updated accordingly and let you know when Sweden are happy to go live.


add comments to config.toml

Missed setting this config value when I copied it over. Thought this might save the next person some trouble

Thank you, @tvieregge 👍.


Dsa: 7.2.5 Cycles in a Graph #8471 issue

Description 📜
Explained detection of cycles in directed as well as undirected graph with diagrams,  algorithms and dry-run.
Fixes #8471

Type of change 📝

[ ] Au#dio (Should be in mp3 format Includes speech clarity, Concise ,Low distortion)
[ ] Vi#deo (Animations, screen-recordings, presentations and regular explanatory films are all possibilties etc)
[x] Documentation (Content Creation in the form of codes or tutorials)
[ ] Other (If you choose other, Please mention changes below)

Domain of Contribution 📊

[ ] Android Dev #(Flutter)
[ ] Android Dev #(Java)
[ ] Android Dev #(Kotlin)
[ ] Backend Dev #(Java)
[ ] Backend Dev #(.NET)
[ ] Backend Dev #(PHP)
[ ] Backend Dev #(Python)
[ ] C/#CPP
[ ] Competitive #Programming
[ ] Cyber #Security
[x] DSA
[ ] Data#base
[ ] Datascience with #Python
[ ] Datascience with #R
[ ] Frontend Dev #HTML/CSS/JS
[ ] Frontend Dev #React/Angular/Vue
[ ] Go#lang
[ ] Interview #Prep
[ ] Java_#Domain
[ ] JavaScript_#Domain
[ ] ME#RN
[ ] Machine #Learning
[ ] Open #Source
[ ] Python_#Domain
[ ] Ru#st
[ ] Statis#tics
[ ] UI/#UX

Checklist ✅

[x] I follow Contributing Guidelines & Code of conduct of this project.
[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GWOC'21 contributor

Screenshots / Gif (Optional) 📸

@nimisha-yadav ma'am
pls review this PR


Blogs -> Blog Posts

I used to contribute Greasemonkey scripts back in the day for previous incarnations. Thanks for taking the initiative today.
(See Accuracy and precision in language for background to this change :-))

love it!
I know and use that because of you.
Found more instances of Blogs


test: remove borderColor lint

Codecov Report

Merging #18 (8cefc19) into master (dd0e102) will decrease coverage by 0.00%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master      #18      +/-   ##
==========================================
- Coverage   99.64%   99.64%   -0.01%
==========================================
  Files           8        8
  Lines         282      281       -1
  Branches       93       92       -1
==========================================
- Hits          281      280       -1
  Misses          1        1

Impacted Files
Coverage Δ

src/util.ts
100.00% <ø> (ø)

Continue to review full report at Codecov.

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


update i18 development guide document

update i18 development guide document

Coverage increased (+0.05%) to 55.226% when pulling e1325f383ef9f47116813bc3b74fd95cf1089e2e on steven-zou:master into 05378cbd85be141c19d9aa7542356beb274d8845 on vmware:master.

Coverage remained the same at 55.179% when pulling 7113f1f279c0c8103b3b4459c9a500bf8b4d1909 on steven-zou:master into d84218d7f0b6eba88d5f046438518de8d77069ff on vmware:master.

Coverage remained the same at 55.179% when pulling 7113f1f279c0c8103b3b4459c9a500bf8b4d1909 on steven-zou:master into d84218d7f0b6eba88d5f046438518de8d77069ff on vmware:master.

Coverage remained the same at 55.179% when pulling f87e7475f406d74c1191c24908482c14c4b41ed3 on steven-zou:master into d84218d7f0b6eba88d5f046438518de8d77069ff on vmware:master.

Coverage remained the same at 55.179% when pulling f87e7475f406d74c1191c24908482c14c4b41ed3 on steven-zou:master into d84218d7f0b6eba88d5f046438518de8d77069ff on vmware:master.


Trouble setting up Spotify media_player

Home Assistant release (hass --version):
0.42.3
Python release (python3 --version):
Python 3.5.3
Component/platform:
media_player.spotify
Description of problem:
Configurator gets me this when trying to link: (The link uses a wrong redirect uri since i use a reverse proxy for external access: https://accounts.spotify.com/authorize?client_id=x&response_type=code&redirect_uri=http%3A%2F%2F<IP_ADDRESS>%3A8123%2Fapi%2Fspotify&scope=user-modify-playback-state+user-read-playback-state)
INVALID_CLIENT: Invalid redirect URI

/api/spotify gives:
500 Internal Server Error
Server got itself in trouble

Logs show:
ESC[31m17-04-28 07:44:43 ERROR (MainThread) [aiohttp.server] Error handling requestESC[0m
Traceback (most recent call last):
  File "/usr/local/lib/python3.5/site-packages/aiohttp/web_protocol.py", line 417, in start
    resp = yield from self._request_handler(request)
  File "/usr/local/lib/python3.5/site-packages/aiohttp/web.py", line 289, in _handle
    resp = yield from handler(request)
  File "/usr/local/lib/python3.5/asyncio/coroutines.py", line 213, in coro
    res = yield from res
  File "/usr/local/lib/python3.5/asyncio/coroutines.py", line 213, in coro
    res = yield from res
  File "/usr/src/app/homeassistant/components/http/ban.py", line 58, in ban_middleware_handler
    return (yield from handler(request))
  File "/usr/src/app/homeassistant/components/http/__init__.py", line 422, in handle
    result = handler(request, **request.match_info)
  File "/usr/src/app/homeassistant/components/media_player/spotify.py", line 115, in get
    self.oauth.get_access_token(request.GET['code'])
  File "multidict/_multidict.pyx", line 124, in multidict._multidict._Base.__getitem__ (multidict/_multidict.c:3486)
  File "multidict/_multidict.pyx", line 119, in multidict._multidict._Base._getone (multidict/_multidict.c:3421)
KeyError: "Key not found: 'code'"ESC[0m

Problem-relevant configuration.yaml entries and steps to reproduce:
- platform: spotify
  client_id: x
  client_secret: x

It doesn't have to use external access, it's all happening client-side. So if you can, from inside your network, hit that redirect URI, you're good to go. Just set it in the App as a valid redirect URI. If it doesn't match, it simply won't work.

Thanks, that fixed it


Added quickstart readme

Readme to get started with our chef cookbooks.

`
Building the Json file for the chef zero run
{
'minimal_ohai' => true,
'run_list' => ['recipe[cpe_init]']
}
`

Tested and working.

Should be good now.


[BUG] cuGraph Force-Atlas2.ipynb can't execute, holoviews not installed in rapidsai:cuda10.2-runtime-ubuntu18.04, possibly others

Describe the bug
holoviews not installed in rapidsai:cuda10.2-runtime-ubuntu18.04, possibly other builds.
The cuGraph Force-Atlas2.ipynb demo relies on this.
Steps/Code to reproduce bug
execute  /rapids/notebooks/cugraph/layout/Force-Atlas2.ipynb
Expected behavior
The demo should run with no errors, instead it produces:
---------------------------------------------------------------------------
ModuleNotFoundError                       Traceback (most recent call last)
<ipython-input-13-cdaa39fc78bd> in <module>
      3 import numpy as np
      4 import pandas as pd
----> 5 import holoviews as hv
      6
      7 from colorcet import fire

ModuleNotFoundError: No module named 'holoviews'

Environment details (please complete the following information):

Environment location: [Bare-metal, Docker, Cloud(specify cloud provider)]
Docker
Method of cuDF install: [conda, Docker, or from source]
NGC rapidsai:cuda10.2-runtime-ubuntu18.04

If method of install is [Docker], provide docker pull & docker run commands used
docker pull nvcr.io/nvidia/rapidsai/rapidsai:cuda10.2-runtime-ubuntu18.04
docker run --gpus all --rm -it -p 8888:8888 -p 8787:8787 -p 8786:8786
-v /bulk:/rapids/notebooks/my_data
--shm-size=8G
rapidsai:cuda10.2-runtime-ubuntu18.04

Please run and attach the output of the cudf/print_env.sh script to gather relevant environment details

print_env.sh-output.txt
Additional context
Add any other context about the problem here.

Hi.  holoviews has been included in the repo.  This should close out this ticket.


Sourcemaps are broken for @swc-node/register/esm

index.ts:
function main() {

    // Some whitespace for swc to optimize away...

    console.log('hello world');
    throw new Error('foo');
}

main()

@swc-node/register gives us sourcemap support:
$ node -r @swc-node/register ./index.ts
hello world
/Users/jwalton/t/index.ts:4
    throw new Error('foo');
    ^

Error: foo
    at main (/Users/jwalton/t/index.ts:7:11)

But @swc-node/register/esm does not:
node --loader @swc-node/register/esm ./index.ts
(node:81567) ExperimentalWarning: Custom ESM Loaders is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
hello world
file:///Users/jwalton/t/index.ts.mjs:3
    throw new Error('foo');
          ^

Error: foo
    at main (file:///Users/jwalton/t/index.ts.mjs:3:11)

I believe I might be having the same issue as I'm having trouble using Node's debugger (through VSCode) with the ESM loader, but it works fine with the standard loader.

This finally bothered me enough so I took a look.
Finding:
Unlike https://github.com/swc-project/swc-node/blob/e34f006484d89c53dd4cac7cface3c4d70841e34/packages/register/register.ts#L115, esm.mts does not call the installSourceMapSupport to enable source map support.
I then tried adding the following in esm.mts, as documented at https://nodejs.org/docs/latest-v20.x/api/module.html#initialize. Sadly, it does not work.
export async function initialize() {
    console.log("This function is indeed called without error, but source map does not apply");
    installSourceMapSupport();
}

Solution:
I finally found this to be working (tested on Node 20). https://nodejs.org/docs/latest-v20.x/api/module.html#source-map-v3-support.
$ node --enable-source-maps --loader @swc-node/register/esm index.ts

Both the CJS and ESM stack traces seem to be incorrect. In @jwalton's report, the CJS stack trace reports an error thrown at line 4 when it should report being thrown at line 7. The only way I have been able to work around this in CJS was to prevent source-map-support from being loaded and use Node's --enable-source-maps instead.

Yep, stumbled upon this too.
@Xinkai thank you for a great workaround.
Happy new year :)


Add a profile icon for Pinboard.in (not pinterest 😆)

When I add a pinboard URL like https://pinboard.in/u:PogiNate I'd love to see it with a pushpin style icon. Please and thank you!

You got it! Should be live now.


JAVA SDK 1.18/1.19 issue: stopContinuousRecognitionAsync().get() costs 10 seconds

Hello, we call "stopContinuousRecognitionAsync().get()" in session stopped listener.
For sdk 1.16, it works fine.
After we upgrade the sdk version to 1.19, "stopContinuousRecognitionAsync().get()"  always costs 10 seconds.
Now, we have to call "stopContinuousRecognitionAsync().get()" asynchronously to avoid the issue.
However, I still wonder what's the change in 1.19 causes this issue.
reco.sessionStopped.addEventListener((s, e) -> {
    System.out.println("Session stopped event.");
    // it works fine in 1.16, but always costs 10 seconds in 1.19,
    try {
        System.out.println("Begin Time is " + (new Date()).toString());
        reco.stopContinuousRecognitionAsync().get();
        System.out.println("End Time is " + (new Date()).toString());
    } catch (Exception ex) {
        ex.printStackTrace();
    }
});

Add some black-box test.
In 1.19, It seems  stopContinuousRecognitionAsync().get() is waiting eventListener to be finished.
Session stopped event in. Begin Time is Fri Nov 19 17:03:13 CST 2021 Session stopped event out. time cost= 9998 End Time is Fri Nov 19 17:03:23 CST 2021
In 1.16. stopContinuousRecognitionAsync().get() finishes without waiting.
Session stopped event in. Begin Time is Fri Nov 19 17:06:17 CST 2021 time cost= 191 End Time is Fri Nov 19 17:06:17 CST 2021
Test codes are listed below.
`reco.sessionStopped.addEventListener((s, e) -> {
System.out.println("Session stopped event in.");
try {
stopTranslationWithFileSemaphore.release();
Thread.sleep(9999);
} catch (Exception ex) {
ex.printStackTrace();
}
System.out.println("Session stopped event out.");
});
        System.out.println("Begin working...");
        reco.startContinuousRecognitionAsync().get();

        stopTranslationWithFileSemaphore.acquire();
        long startTime = System.currentTimeMillis();
        System.out.println("Begin Time is " + (new Date()).toString());
        reco.stopContinuousRecognitionAsync().get();
        System.out.println("time cost= " + (System.currentTimeMillis() - startTime));
        System.out.println("End Time is " + (new Date()).toString());`

@Bob-Pengcheng
There's a known usability challenge with synchronizing these stopContinuousRecognitionAsync() calls with stopping audio flow. We plan to improve this in an upcoming release, but we can share some information about the behavior and workarounds:
The problem: internally, the SpeechRecognizer processes input audio in chunks of 100ms (3200B for default 16khz16bit mono PCM). When stopContinuousRecognitionAsync() is called, the recognizer patiently waits to fill the rest of its current chunk (up to another 100ms worth) before gracefully requesting a final result and stop. If audio input (e.g. via a PushAudioInputStream) is stopped before the stopContinuousRecognitionAsync() call is completed, the recognizer may wait up to 10s in case more audio arrives.
Workaround option 1: if the end of audio flow can be deferred until the final recognition or SessionStopped event arrives, that will fully prevent the recognizer from getting stuck waiting for 10s. The downside is that this may result in a small audio discontinuity--audio that was "in flight" while stopContinuousRecognitionAsync() is called will be sent but not used, and if the audio after the stop*() needed to be kept then this may be inappropriate.
Workaround option 2: to fully work around the problem and lose absolutely no audio at the end of a session, a bit of state management is needed:
Premise: don't directly call stopContinuousRecognitionAsync() (which could be thought of as "waitForTheLastAudioAndRequestALastRecognitionAsync()") but instead use an "end of stream" state to produce a more forceful (but still graceful) closure
When a stop is desired:
Stop servicing more data: don't write more to a PushAudioInputStream or don't return new real data out of a PullAudioInputStream; Instead, write a 0-length buffer (for push streams) or return a 0-length read (for pull streams)
Internally, the SDK marks the stream as "ended" when it processes this 0-byte element and will immediately begin stopping with no expectation of more audio
With the stream ended, the recognizer will quickly receive a final recognition result (if applicable) immediately followed by a Canceled event with a Reason of "EndOfStream." This isn't an error--rather it's the signal that the recognizer is now fully stopped and can be used again.
To restore the stream: at any point after the Canceled event arrives and before a new start*() call is made, ensure a non-zero-length data component is made available. This can mean ensuring the next "real" PushAudioInputStream::Write call is made before the recognizer is started or it can mean immediately pushing a very small amount (e.g. 32B) of artificial silence (0s) when Canceled with EndOfStream arrives -- either way, what's important is to clear that "end of stream" state before calling start*() again.
As long as the "ended" stream was restored first, a subsequent startContinuousRecognitionAsync() call will behave normally and allow recognition to continue.
That last one is certainly a headache and it's a priority to make this more elegant. If the slightly "lossy" first workaround is usable, it's much simpler.


Changes in documentation and the functions in accordance with PR #84

Consistent objects in documentation
Consistent variable names between the functions and the documentation, to make it easier for developers.
Other minor improvements.

@meghapatnaik @Toodlepoodle, can you clone the PR from here, and compile the code and documentation?
Suggest changes accordingly.

Codecov Report

Merging #88 (8595b3c) into main (059896b) will decrease coverage by 1.32%.
The diff coverage is 97.84%.

:exclamation: Current head 8595b3c differs from pull request most recent head 69233c7. Consider uploading reports for the commit 69233c7 to get more accurate results

@@            Coverage Diff             @@
##             main      #88      +/-   ##
==========================================
- Coverage   96.96%   95.65%   -1.32%
==========================================
  Files          16       14       -2
  Lines         363      345      -18
==========================================
- Hits          352      330      -22
- Misses         11       15       +4

Impacted Files
Coverage Δ

src/data_cleaning/interpolation.jl
80.76% <ø> (-15.39%)
:arrow_down:

src/other/com.jl
100.00% <ø> (ø)

src/data_cleaning/replace_negative.jl
87.50% <83.33%> (-12.50%)
:arrow_down:

src/data_cleaning/bgnoise.jl
92.30% <88.88%> (-1.03%)
:arrow_down:

src/data_cleaning/bias_correction.jl
97.14% <100.00%> (-0.30%)
:arrow_down:

src/data_cleaning/full_procedures.jl
100.00% <100.00%> (ø)

src/data_cleaning/na_recode.jl
100.00% <100.00%> (ø)

src/data_cleaning/outlier_removal.jl
93.93% <100.00%> (-0.18%)
:arrow_down:

src/example.jl
92.30% <100.00%> (ø)

src/f_apply.jl
88.88% <100.00%> (-1.12%)
:arrow_down:

... and 3 more


Flat fielding script did not did not execute

[I'm copying an email I sent to Petr + Scott here]
1st email:
Hey guys --
RTS2 and the telescope started up like a dream tonight.  It even went to try to do a set of flats (/etc/rts2/flat.py), but it is stuck, and not taking any data.  Attached is a screenshot I took with my phone.  You can zoom in and see what is going on.   (see img_1311)
2nd email:
It sat there for about 10 min, and now it seems to be looking for targets.  See new picture. (see img_1312)

Just FYI.  This still seems to be an issue.  Tonight the RTS2 took biases, and then we think it tried flats, but we could not find the images.  Petr, can you look at tonight's log or observations to figure this out?

On April 27, we attempted to run flats at the beginning of the night.  As the appropriate time approached, in rts2-mon on the camera driver we received a warning that the priority had changed, and then the flats did not execute.  By restarting RTS2, we were able to get the flats to start.

Flats have worked the last two ARTN nights. Its not clear why


CrossLineDetection not processed correctly in home assistant

Hello,
First of all thanks for all your hard work you put into this project. I'm very pleased with it.
Unfortunately I have a problem with the Crosslinedetection on one of my cams.
I have 2 different types of Dahua cams.
Camera1   IPC-HDW4421EM-AS    Firmware: 2.620.0000002.0.R,build:2017-08-30
Camera2   IPC-HDW5442TM-ASE  Firmware: 2.800.0000000.19.R,build:2020-07-09
One works fine (camera1) with the detection of the "crosslinedetection"events
2022-05-18 09:39:09 DEBUG (MainThread) [custom_components.dahua] Events received from <IP_ADDRESS> on channel 0: [{'Code': 'CrossLineDetection', 'action': 'Start', 'index': '0'}]
2022-05-18 09:39:11 DEBUG (MainThread) [custom_components.dahua] Events received from <IP_ADDRESS> on channel 0: [{'Code': 'CrossLineDetection', 'action': 'Stop', 'index': '0'}]
But HA receives the event from camera2, but does NOT trigger the entity in HA.
2022-05-18 09:44:31 DEBUG (MainThread) [custom_components.dahua] Events received from <IP_ADDRESS> on channel 0: [{'Code': 'CrossLineDetection', 'action': 'Start', 'index': '0', 'data': {'Class': 'Normal', 'CountInGroup': 1, 'DetectLine': [[2209, 6041], [3386, 4450], [5256, 6708], [4918, 7998], [2499, 7933]], 'Direction': 'RightToLeft', 'EventID': 10021, 'GroupID': 20, 'Name': 'Rule 1', 'Object': {'Action': 'Appear', 'BoundingBox': [1032, 2352, 3832, 7952], 'Center': [2432, 5152], 'Confidence': 0, 'LowerBodyColor': [0, 0, 0, 0], 'MainColor': [0, 0, 0, 0], 'ObjectID': 20530, 'ObjectType': 'Human', 'RelativeID': 0, 'Speed': 0}, 'PTS':<PHONE_NUMBER>0.0, 'RuleID': 4, 'Track': [], 'UTC':<PHONE_NUMBER>, 'UTCMS': 448}}]
2022-05-18 09:44:34 DEBUG (MainThread) [custom_components.dahua] Events received from <IP_ADDRESS> on channel 0: [{'Code': 'CrossLineDetection', 'action': 'Stop', 'index': '0', 'data': {'Class': 'Normal', 'CountInGroup': 1, 'DetectLine': [[2209, 6041], [3386, 4450], [5256, 6708], [4918, 7998], [2499, 7933]], 'Direction': 'RightToLeft', 'EventID': 10021, 'GroupID': 20, 'Name': 'Rule 1', 'Object': {'Action': 'Appear', 'BoundingBox': [1032, 2352, 3832, 7952], 'Center': [2432, 5152], 'Confidence': 0, 'LowerBodyColor': [0, 0, 0, 0], 'MainColor': [0, 0, 0, 0], 'ObjectID': 20530, 'ObjectType': 'Human', 'RelativeID': 0, 'Speed': 0}, 'PTS':<PHONE_NUMBER>0.0, 'RuleID': 4, 'Track': [], 'UTC':<PHONE_NUMBER>, 'UTCMS': 448}}]
Configuration:
Version:                                   core-2022.5.4
Install type:                             Home Assistant OS
Dahua integration version      0.9.39
I think the problem has something to do with the extra "data" (Class, CountIngroup, etc.) in the response of the camera during an event such as somebody walking by.
Hope you can help.
Robin

I've encountered the same thing and I think it happens with both CrossLineDetection and CrossRegionDetection. There is some mention in other places but it's not clear it's the same issue - the closest I have found is on the HA forums (https://community.home-assistant.io/t/home-assistant-dahua-integration-questions/387305/21 user: "undecimo" Jun 13)
I've been looking at the code and I'm wondering if it's in line 481 of init.py where I think for some reason CrossLineDetection and CrossRegionDetection is being renamed SmartMotionHuman?

I don't know if it's exactly the same problem, but with my IPC-HDW5241H-AS-PV camera, I correctly receive Crossline=Tripware, but I don't receive Crossregion=Intrusion.
The controls work properly, from the tested Crossline and Smart Motion Human sensors.
HomeAssistant 2022.8.6
IPC-HDW5241H-AS-PV
Firmware: 2.800.9999007.0.R,build:2021-04-12

@isabido looking at the code I wouldn't think it's the same issue (because the code looks to apply for both CrossLine and CrossRegion), but maybe try it and see what you find. I've now had the change in code for more than 1 week and it's working fine for me.


KAFKA-4644: Improve test coverage of StreamsPartitionAssignor

Some exception paths not previously covered. Extracted ensureCopartitioning into a static class.

@enothereska @guozhangwang @mjsax

Merged to trunk and 0.10.2.


Remove redundant PtrackerId and MotherName columns on child visit list

Requirements

[ ] This PR has a title that briefly describes the work done including the ticket number. If there is a ticket, make sure your PR title includes the ticket number in the format OHRI-123 My PR title.
[ ] My work includes tests or is validated by existing tests.

Summary
Since Mother Name is already displayed on the child's patient banner, there is no need to display it also on the infant PNC encounter list. Same applies to the PtrackerId that will always stay the same for the child thus creating more space for required variables
Screenshots

Related Issue
https://ohri.atlassian.net/browse/OHRI-2317
Other

This PR is dependant on https://github.com/UCSF-IGHS/openmrs-esm-ohri/pull/1929


Multiple Voices?

If multiple voices possible with jianpu-ly?
I.e., same song sang by different group of people Soprano, Alto, Tenor, Bass etc with their own tunes, and put  on the same sheet.
Again from the afromentend jianpu bible, p3:

You can use voice name marker such as Soprano, Mezzo-soprano, Alto, Tenor,
Baritone, Bass, Lead, ... Please put them before the system bracket.

Yes, use NextPart and instrument (the human voice counts as an instrument...)
instrument=Soprano
1 2 3 4
L: lah lah di dah
NextPart instrument=Alto
5, 6, 7, 1
L: dum dum di dum
NextPart instrument=Tenor
3, 4, 5, 6,
L: pom pom pom pom

Gocha. Thx!!

Oh, a follow up question, what's the syntax to change instrument / voice?
I just dup the above lines again, but got:
Error: Changing header 'instrument' from 'Tenor' to 'Soprano' (is there a missing NextPart or NextScore?)
Our music basically have three instruments / voices. The first line keeps changing from T.B to S.A to T.S... and the 2nd and 3rd lines keeps changing like that as well.

Hi, I'm afraid changing instrument or voice in the middle of the same part isn't really supported, but you can hack it with Lilypond code:
instrument=Bass
1, 2, 3, 4,
LP: \mark \markup "Change to Soprano" \set Staff.shortInstrumentName = "S"
:LP
1' 2' 3' 4'
L: low low low low high high high high

Maybe just make it an ordinary text command

YEP!
instrument=1
1, ^"T.B." 2, 3, 4,
1' ^"S.A" 2' 3' 4'
L: mlow low mlow low whigh high whigh high

NextPart instrument=2
1, ^"S" - 3, -
1 ^"T" - 3 -

NextPart instrument=3
1 ^"A" - 3 -
1, ^"B" - 3, -

That works perfectly!!

Thanks!!!


Cleared all errors in all iiit own carousel

Changed all images to  same pixel and dimentions ratio
alligned all images to center vertically and horizontally

The logo errors are removed.


Add a little top-padding on the editor container

It's not really nice that the code is stuck against the tab list.

Hi @Xstoudi, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

What exactly is bad right now, can we file an issue too please? For comparison:
Code:

ST:

Atom:

VS:

I didn't compared with others text editor and I just think it's more nice to see the code a little bit separated from tabs.
So I edited the code locally and I suggest you to do the same. But by the way, you do what you want. :)

Ok I think you should open an issue and we take it to UX meetings. I am closing this PR as it is not fit yet (e.g. it looks weird that the scrollbar is pushed down).


Locale maintenance

[Narc edit:] This issue will be updated when locale changes happen. Subscribe to notifications if you're interested in these updates.

As noted in f1aa00b, the locale key "YARM-unknown-resource-category" was removed. There are no changes required from translators.

7ce97e63ce50165d324134c5b4e4d7ccf539870e added the locale key YARM-err-sand-is-bad, which shows up for folks who have the Homeworld mod and try to track their sand in YARM.

eb32d07 added three locale keys supporting the new site expansion feature.

The new version 0.8 added some locale keys and removed a couple of others. It's a pretty major change, needs a pretty major review.

#94 added a locale key for controls.get-yarm-selector. Previously, it would show as "unknown key" in the controls screen.


Tanks drop reactor cores that are valuable

We had a group discussion about gameplay ideas, and the idea of "reactor cores" as a form of in-game currency is a cool idea.
@Gomer3261 had the idea that tanks should drop valuable reactor cores when they die, which can be collected by the other team for an in-game currency reward, with which you might build turrets or walls or buy some kind of upgrade for your tank.
We figured that to avoid teammates feeding each other reactors by getting themselves repeatedly killed by an enemy turret, you cannot pick up a reactor dropped by your own team – you can only destroy them by running over them and crushing them, stopping the enemy from taking them for their own advantage.
I thought it'd be cool if the tanks would shoot out a grappling hook (at close range) that attaches the reactor via a rope, allowing the player to drag it back to their team's base for the money reward.

I was just thinking, that maybe reactor cores could provide more than just a monetary reward for the player which returns them, but in addition, each reactor core could represent one life.  When a team runs out of reactor cores, no more tanks can be spawned, and thus the round ends when the last player dies. If they're a badass, maybe they could collect some more cores, resurrect their team mates, and turn the tide.. Food for thought, boys.

Let's eventually close this ticket by finalizing the ideas here into an official gameplay plan for Nanoshooter.

Information here should be summarized in #38.


Add dockerfile for java on CentOS

@kahootali Image is available for testing. docker pull docker.io/stakater/java-centos:7-1.8

@kahootali Image is available for testing. docker pull docker.io/stakater/java-centos:7-1.8


Add the plugin as a maven dependency

Hello,
In order to improve the plugins, I would like to know if it was possible to integrate your plugin into Maven, in order to be able to use them internally?
thx

Hello. I am unsure what exactly you mean by "integrating your plugin into Maven".
Do you want us to change to using Maven instead of Gradle?
Do you want us to create a remote Maven repository from where you can download the plugin?
Do you want us to create a remote Maven repository with an API that lets you integrate with the plugin?
There are so many things that could mean and I am really not sure which one it is.

I would like a repository on Maven, in order to be able to use the plugin API, in my own plugins

The plugin does not have an API yet. I am going to mark this as a duplicate of https://github.com/HelpChat/DeluxeMenus/issues/29


Disable day selector in unsupported dashboard views

Description:
Please disable day selector in unsupported dashboard views
Image View
Simple View

Looks like in image view actually selector is supported.
Now looks good to me.

QA passed


Export abc not in alphabetical order

This is exactly how  bash does it as well so this will not be changed, only thing that should be changed is that the equals sign after the key should not be there, but this will be made into a different issue


Solution for #831

So this time with signing!
I kept to your exapmles and how you implemented the 24h Timeformat.

Thanks, I may make some small changes to better fit it into Trail Sense's patterns, but this looks good.

Thanks, now I see what you meant. Thanks for adapting it directly. Will keep that in mind in the future.


Add test for BI-2001 and BI-2002.

Description
BI-2001 - Check the import file formats.
Added:
Then user can see Import file extension supported are ".csv, .xls, .xlsx"
Added fileSelector in importPage.
Testing
https://github.com/Breeding-Insight/taf/actions/runs/11047812952
Checklist:

[x ] I have performed a self-review of my own code
[ ] I have tested my code and ensured it meets the acceptance criteria of the story
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to documentation

BI-2001 and BI-2002 seem to be about checking the file formats available and defaulted in the popup when downloading germplasm and ontology, not importing/uploading them. Ie for germplasm it is accessed via going to germplasm > lists and clicking on the download link for a particular row.

Sorry, I misunderstood the test.
I'll cancel this pull request.


Cannot install - premature close

I'm trying to install this on my Macbook running node v12.5.0. Any ideas on how to debug this?
➜  proxy git:(master) ✗ npm install uNetworking/uWebSockets.js
npm ERR! premature close

npm ERR!      /Users/xo/.npm/_logs/2020-03-15T04_29_08_579Z-debug.log

➜  proxy git:(master) ✗ cat  /Users/xo/.npm/_logs/2020-03-15T04_29_08_579Z-debug.log
0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli   '/usr/local/Cellar/node/12.5.0/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'install',
1 verbose cli   'uNetworking/uWebSockets.js'
1 verbose cli ]
2 info using<EMAIL_ADDRESS>3 info using<EMAIL_ADDRESS>4 verbose npm-session c5eedc51b34d9932
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 silly fetchPackageMetaData error for github:uNetworking/uWebSockets.js premature close
8 timing stage:rollbackFailedOptional Completed in 2ms
9 timing stage:runTopLevelLifecycles Completed in 34529ms
10 verbose stack Error: premature close
10 verbose stack     at PassThrough.onclose (/usr/local/lib/node_modules/npm/node_modules/end-of-stream/index.js:47:67)
10 verbose stack     at PassThrough.emit (events.js:205:15)
10 verbose stack     at emitCloseNT (internal/streams/destroy.js:68:8)
10 verbose stack     at processTicksAndRejections (internal/process/task_queues.js:74:11)
11 verbose cwd /Users/xo/code/unraid/proxy
12 verbose Darwin 19.2.0
13 verbose argv "/usr/local/Cellar/node/12.5.0/bin/node" "/usr/local/bin/npm" "install" "uNetworking/uWebSockets.js"
14 verbose node v12.5.0
15 verbose npm  v6.13.0
16 error premature close
17 verbose exit [ 1, true ]

Would make sense to tag the latest stable release as latest so users won't need to pin a specific version.

Hi, I'm getting probably the same error with "npm install uNetworking/uWebSockets.js#v17.3.0".
I than just manually downloaded "uWebSockets.js" and added it to my node_modules folder.
But when i cd "./node_modules/uWebSockets.js" and try a "nom install":
npm ERR! code E404
npm ERR! 404 Not Found - GET https://registry.npmjs.org/uWebSockets.js - Not found
npm ERR! 404
npm ERR! 404<EMAIL_ADDRESS>is not in the npm registry.
npm ERR! 404 Your package name is not valid, because
npm ERR! 404  1. name can no longer contain capital letters
... see the last line: "can no longer contain capital letters" ... is the a major problem for all installs? Your package does not seem to be in the registry ... or how do I do install this?

@alexhultman why was this closed? You could at least have the courtesy of replying before closing the issue.

Hello. I marked this issue won't fix and FAQ. It is courteous to read the frequently asked questions so that I do not have to personally respond to the same questions over and over. Thank you for understanding

You're not helping yourself here. I read the FAQ. Why not spending the same amount of time and just link me to the issue if it's already been asked.
I would like to use your library, sorry I need a little help.

@ChrisGitIt what version of npm do you have? I have seen that issue before I think you need to update your npm I have 6.13.4 and no issues here

npm install uNetworking/uWebSockets.js results in the premature close error.
npm install uNetworking/uWebSockets.js#v17.4.0 seems to work though.

Sorry for the late feedback. Will check (and close this issue) shortly with my new project setup!

@alexhultman there is neither a link to nor even a mention of the FAQ in the project readme, the uWebSockets project readme or the "read more..." link. The project Wiki is disabled for both. A search for issues labelled with "FAQ" and the term "npm" doesn't bring up anything else related to the topic.
If one crawls the web a little instead, there's two relevant stories hinting at what actually happened:

Beware of uWebsockets.js! written by Manuel Astudillo, and
The story of “uws” so far, written by @alexhultman

You claim you don't want to be hold liable for legacy versions of your library, even though it's licensed under the Apache License 2.0. I perfectly understand that, as an Open Source developer, you don't want to be held accountable for bugs in your software, much less so in old versions. However there's neither a precedent here nor does your license choice leave any legal foothold for that.
Instead, you chose to not distribute uWebSockets via npm but from your GitHub repository instead, providing pre-compiled binary bindings to users. While I absolutely do not want to insinuate any sort of malevolence from your side, this theoretically gives you the opportunity to include malware in your binary bindings without anyone noticing.
You're free to shrug all this off with a "don't use it then", but if you request courtesy at least have the courtesy to make the situation clear for users of your library, which you chose to publish on the internet for others to use. If you decide to do things differently than the rest of the entire software world, at least include a notice about what is going on and why. Don't just close issues and point to a non-existent FAQ.

@Radiergummi You are getting all upset for no reason. There is clearly an install section in the readme where it says to do npm install uNetworking/uWebSockets.js#v18.3.0 which I just ran and works fine.
If you want to compile it from source which is what I do you simply run git clone --recurse-submodules https://github.com/uNetworking/uWebSockets.js and then run make. I am confused why you are all upset and wrote this large rambling paragraph. Does this help your issue?

While I absolutely do not want to insinuate any sort of malevolence from your side, this theoretically gives you the opportunity to include malware in your binary bindings without anyone noticing.

In Sweden - best country on earth - we have laws of "Förtal" where slanderous rumors that end up hurting a company or person are penalized by the relative damages.

I also want to add that in Sweden - best country on earth - you are allowed to spread any defamatory information, even regarding the very king himself, if it is true. So please, find this supposed malware and pop this supposed conspiracy wide open.
Binaries - they are clearly magical containers of uninterpretable secrecy! Your CPU and kernel dail God himself on Viber to ask how to read this magical sorcery no man will ever understand - every time you double click anything on your desktop.
Did you compile Node.js from source? Did you compile your compiler from source? Did you compile your compiler compiler from source? Did you call the president of Zimbabwe and tell him to change his socks?
Clearly, we have a conspiracy here! Also, Earth is a triangle!


Revamp HttpServerUpgradeHandler for cleartext upgrade

Motivation:
Netty's HttpServerUpgradeHandler fully aggregates a request to handle an
upgrade request. The maximum allowed length for aggregation is hard-coded
with 16384. If the payload size of an upgrade request is greater than 16384,
the request always fails. See #3859 for more information.
Modifications:

Fork HttpServerUpgradeHandler and remove HttpObjectAggregator from
super class.

Only see HTTP headers to upgrade HTTP/1.x requests.
After upgrading, an outbound hander for HTTP/1 codec will be removed
and HTTP/2 codec will be promoted.
HTTP/1 codec will be fully removed after receiving the entire request.

Forked Http2ServerUpgradeCodec and de-generalized and optimized for
Armeria.

Result:

You no longer see 413 Request Entity Too Large when receiving a cleartext(h2c)
upgrade with a size greater than 16384.

The maximum allowed length of an upgrade request will respect
ServerBuilder.maxRequestLength().

Fixes #3859

Left just one comment which you might want to address in a follow-up PR.

Let me file an issue and do handle it in the f/u PR. 🙇♂


Update TestFramework

Description

Update TestFramework submodule
Switching Output.WriteLine to comments to reduce string count

Motivation and Context
Improved unit test output
How Has This Been Tested?
Manually
Screenshots
Types of changes

[X] Improvement (non-breaking change that improves a feature, code or algorithm)
[ ] Bug fix (non-breaking change which fixes an issue with code or algorithm)
[ ] New feature (non-breaking change which adds functionality to code)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Config and build (change in the configuration and build system, has no impact on code or features)
[X] Dependencies (update dependencies and changes associated, has no impact on code or features)
[X] Unit Tests (add new Unit Test(s) or improved existing one(s), has no impact on code or features)
[ ] Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

[X] My code follows the code style of this project (only if there are changes in source code).
[ ] My changes require an update to the documentation (there are changes that require the docs website to be updated).
[ ] I have updated the documentation accordingly (the changes require an update on the docs in this repo).
[X] I have read the CONTRIBUTING document.
[X] I have tested everything locally and all new and existing tests passed (only if there are changes in source code).
[ ] I have added new tests to cover my changes.

** DO NOT MERGE **
I'm still waiting for https://github.com/nanoframework/nanoFramework.TestFramework/pull/259 to be merged. At that point I will update the submodule and fix the "incepted" libraries to include all the new files.

@CoryCharlton PR with test framework v2.1.107 is out!

@josesimoes I updated the nanoFramework.TestFramework submodule and confirmed all the tests run.
This PR is ready to be merged.


fix: rename cpu-share to cpu-shares in command line

Signed-off-by: Allen Sun<EMAIL_ADDRESS>
Ⅰ. Describe what this PR did
the related command line flag about cpu share should be --cpu-shares rather than --cpu-share.
This update would be compatible with moby's way.
Ⅱ. Does this pull request fix one issue?

none
Ⅲ. Describe how you did it
change the flag file and test
Ⅳ. Describe how to verify it
none
Ⅴ. Special notes for reviews
none

LGTM


php version ???

would it be possible to write a php version of ssh-room?

Yes

does this version already exist? If not, What does it take to write on?
A php version could be installed on any regular Shard host Webserver.

Ohhh...  closed this as not planned

I meant that it's possible, I didn't say I plan to build it. Someone who knows PHP well could build it.

if i find someone who knows php well - would there be a chance to get the needed work funded?

@staltz maybe you want to reopen this issue. I find it important that everybody can host a server app with a minimum of effort. PHP offers here a lot of advantages over GO.
Maybe there is someone in the community who can do the job in PHP.   What do you think?

@rocky-III this is not an "issue" about go-ssb-room, this is just an idea you want to build.

@staltz it´s in issue in that scene that if the app would be available in php it would be much easier to spread. I can´t do this in PHP - i can´t build it... but the community should think about it. Let the discuss this and reopen the issue - of find an other place to discuss it...


Resolve Windows path installation problems.

This fixes #17
I tested on Windows 10 and Mac:
⚡ ember install https://github.com/emberwatch/ember-cli-typescript.git#b006262
⚡ ember g ember-cli-typescript

@locks can you merge, update package.json with version bump, tag and release?


Set linux autoroller as bringup to reopen the tree.

The build is failing to decrypt the key after it was moved to a
different GCP project. Disabling temporarily to reopen the tree while
the key is regenerated.
Pre-launch Checklist

[X] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[X] I read the Tree Hygiene wiki page, which explains my responsibilities.
[X] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[X] I signed the CLA.
[X] I listed at least one issue that this PR fixes in the description above.
[X] I updated/added relevant documentation (doc comments with ///).
[X] I added new tests to check the change I am making, or this PR is test-exempt.
[X] All existing and new tests are passing.

If you need help, consider asking for advice on the #hackers-new channel on Discord.

lgtm
Please file a P0 issue, or re-purpose the existing P0, to track getting this working again.

I am going to land this manually. It is only moving one job to staging, and keeping the tree closed for another 20 minutes while the presubmits run doesn't make sense.


Function refactoring

https://github.com/radekxrandom/device_bridge/blob/95b810411554fce0a641294c193e3faeba369f21/front/src/connected/midCol/SharedFilesContainer.js#L8
If you don't need any param you could use just () =>
** Also function could be changed to togglePostingMode to make it cleaner to understand.
*** And don't forget to wrap it in useCallback function
const switchPostingMode = () => {
		setIsFormOpen(prev => !prev);
	};
	```

Is there any practical difference between () and _?
I agree on the second and the third points.


[Bug]: Segfault in pgbouncer

Is there an existing issue already for this bug?

[x] I have searched for an existing issue, and could not find anything. I believe this is a new bug.

I have read the troubleshooting guide

[x] I have read the troubleshooting guide and I think this is a new bug.

I am running a supported version of CloudNativePG

[x] I have read the troubleshooting guide and I think this is a new bug.

Contact Details
<EMAIL_ADDRESS>Version
1.24.0
What version of Kubernetes are you using?
1.30
What is your Kubernetes environment?
Other
How did you install the operator?
YAML manifest
What happened?
It just happened several times on a new cnpg cluster. I also run around 10 more cnpg clusters in the same kubernetes cluster, and it was only 2 pods from one of them that were affected.
Nothing particularly interesting in logs before this core:
dropping database '<dbname-redacted>' as it does not exist anymore or inactive auto-database

☝ this is the log record 90ms before the core dump 👇
github.com/cloudnative-pg/machinery/pkg/log.(*logger).Error
	pkg/mod/github.com/cloudnative-pg/machinery@v0.0.0-20241014090714-c27747f9974b/pkg/log/log.go:125
github.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/pgbouncer/run.runSubCommand
	internal/cmd/manager/pgbouncer/run/cmd.go:144
github.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/pgbouncer/run.NewCmd.func2
	internal/cmd/manager/pgbouncer/run/cmd.go:74
github.com/spf13/cobra.(*Command).execute
	pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:985
github.com/spf13/cobra.(*Command).ExecuteC
	pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1117
github.com/spf13/cobra.(*Command).Execute
	pkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1041
main.main
	cmd/manager/main.go:68
runtime.main
	/opt/hostedtoolcache/go/1.23.2/x64/src/runtime/proc.go:272

Cluster resource

Relevant log output

Code of Conduct

[x] I agree to follow this project's Code of Conduct

1. Cluster and Pooler yaml definitions
apiVersion: postgresql.cnpg.io/v1
kind: Cluster
metadata:
  annotations:
  creationTimestamp: "2024-12-09T04:09:39Z"
  generation: 2
  name: db
  namespace: <redacted>
  resourceVersion: "14000397"
  uid: 819d2929-ef97-438b-8e5b-02ee840ac35f
spec:
  affinity:
    podAntiAffinityType: required
  backup:
    barmanObjectStore:
      data:
        compression: bzip2
      destinationPath: s3://<redacted>
      endpointURL: https://<redacted>
      s3Credentials:
        accessKeyId:
          key: ACCESS_KEY
          name: cnpg-db-backup-credentials
        secretAccessKey:
          key: SECRET_KEY
          name: cnpg-db-backup-credentials
      serverName: db
      wal:
        compression: bzip2
    retentionPolicy: 3d
    target: prefer-standby
  bootstrap:
    initdb:
      database: app
      postInitApplicationSQL:
      - ALTER user app <redacted>
      - CREATE SCHEMA <redacted>
      - ALTER SCHEMA <redacted> OWNER TO app;
  enablePDB: false
  imageName: ghcr.io/cloudnative-pg/postgis:17-3.5-2
  inheritedMetadata:
    annotations:
      prometheus.io/port: "9187"
      prometheus.io/scrape: "true"
  instances: 3
  managed:
    services:
      disabledDefaultServices:
      - r
      - ro
  postgresql:
    parameters:
      statement_timeout: 30min
      lock_timeout: 30min
      idle_in_transaction_session_timeout: 30min
      idle_session_timeout: 30min
    synchronous:
      method: any
      number: 1
  primaryUpdateMethod: switchover
  resources:
    limits:
      cpu: "1"
      memory: 500Mi
    requests:
      cpu: 1m
      memory: 80Mi
  storage:
    size: 1000Mi
    storageClass: <redacted>

---

apiVersion: postgresql.cnpg.io/v1
kind: Pooler
metadata:
  creationTimestamp: "2024-12-09T04:09:39Z"
  generation: 2
  name: db-pooler
  namespace: <redacted>
  resourceVersion: "14154801"
  uid: 672b3b7c-8bc8-4c1c-a23d-0317df6ab57f
spec:
  cluster:
    name: db
  instances: 2
  pgbouncer:
    parameters:
      client_idle_timeout: "1800"
      default_pool_size: "100"
      idle_transaction_timeout: "1800"
      tcp_keepcnt: "10"
      tcp_keepidle: "300"
      tcp_keepintvl: "20"
  template:
    metadata:
      annotations:
        prometheus.io/port: "9127"
        prometheus.io/scrape: "true"
    spec:
      affinity:
        podAntiAffinity:
          requiredDuringSchedulingIgnoredDuringExecution:
          - labelSelector:
              matchLabels:
                cnpg.io/cluster: db
                cnpg.io/podRole: pooler
            topologyKey: kubernetes.io/hostname
      containers:
      - name: pgbouncer
        resources:
          limits:
            cpu: "1"
            memory: 128Mi
          requests:
            cpu: 1m
            memory: 16Mi
      initContainers:
      - name: bootstrap-controller
        resources:
          limits:
            cpu: "1"
            memory: 96Mi
          requests:
            cpu: 1m
            memory: 96Mi
  type: rw

It's random, I cannot see any pattern when it happens. More often though it's right after the connection to db is closed: msg":"dropping database '<redacted>' as it does not exist anymore or inactive auto-database. BUT I can also see cases when there are no events logged just before core dump (in close proximity).

No, tbh I don't even know how to enable them

I run quite a number of cnpg clusters, and this one is the only problematic one. They all are created using the same template for the Cluster resorce, BUT this one is the only one that has multiple postgresql databases created (unmanaged, I created them manually with CREATE DATABASE).

UPDATE
I also found the following interesting behaviour: as you can see I have 2 instances of pools. And when one of the pgbouncer pods segfaulted, the other pod has crashed within one minute too, with a different message
crash without segfault
{"level":"info","ts":"2024-12-11T02:48:10.706380554Z","msg":"record","logger":"pgbouncer-manager","pipe":"stderr","record":{"timestamp":"2024-12-11 02:48:10.706 UTC","pid":"16","level":"FATAL","msg":"@src/objects.c:420 in function put_in_order(): put_in_order: found existing elem"}}
{"level":"error","ts":"2024-12-11T02:48:10.70742981Z","msg":"pgbouncer process exited with errors","logger":"pgbouncer-manager","error":"exit status 1","stacktrace":"github.com/cloudnative-pg/machinery/pkg/log.(*logger).Error\n\tpkg/mod/github.com/cloudnative-pg/machinery@v0.0.0-20241014090714-c27747f9974b/pkg/log/log.go:125\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/pgbouncer/run.runSubCommand\n\tinternal/cmd/manager/pgbouncer/run/cmd.go:144\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/pgbouncer/run.NewCmd.func2\n\tinternal/cmd/manager/pgbouncer/run/cmd.go:74\ngithub.com/spf13/cobra.(*Command).execute\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:985\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1041\nmain.main\n\tcmd/manager/main.go:68\nruntime.main\n\t/opt/hostedtoolcache/go/1.23.2/x64/src/runtime/proc.go:272"}
{"level":"error","ts":"2024-12-11T02:48:10.707575711Z","msg":"Error while running manager","logger":"pgbouncer-manager","error":"exit status 1","stacktrace":"github.com/cloudnative-pg/machinery/pkg/log.(*logger).Error\n\tpkg/mod/github.com/cloudnative-pg/machinery@v0.0.0-20241014090714-c27747f9974b/pkg/log/log.go:125\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/pgbouncer/run.NewCmd.func2\n\tinternal/cmd/manager/pgbouncer/run/cmd.go:75\ngithub.com/spf13/cobra.(*Command).execute\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:985\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1041\nmain.main\n\tcmd/manager/main.go:68\nruntime.main\n\t/opt/hostedtoolcache/go/1.23.2/x64/src/runtime/proc.go:272"}

crash with segfault
{"level":"info","ts":"2024-12-11T01:49:10.58213842Z","msg":"record","logger":"pgbouncer-manager","pipe":"stderr","record":{"timestamp":"2024-12-11 01:49:10.581 UTC","pid":"16","level":"WARNING","msg":"dropping database '<redacted>' as it does not exist anymore or inactive auto-database"}}
{"level":"error","ts":"2024-12-11T01:49:10.701797437Z","msg":"pgbouncer process exited with errors","logger":"pgbouncer-manager","error":"signal: segmentation fault (core dumped)","stacktrace":"github.com/cloudnative-pg/machinery/pkg/log.(*logger).Error\n\tpkg/mod/github.com/cloudnative-pg/machinery@v0.0.0-20241014090714-c27747f9974b/pkg/log/log.go:125\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/pgbouncer/run.runSubCommand\n\tinternal/cmd/manager/pgbouncer/run/cmd.go:144\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/pgbouncer/run.NewCmd.func2\n\tinternal/cmd/manager/pgbouncer/run/cmd.go:74\ngithub.com/spf13/cobra.(*Command).execute\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:985\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1041\nmain.main\n\tcmd/manager/main.go:68\nruntime.main\n\t/opt/hostedtoolcache/go/1.23.2/x64/src/runtime/proc.go:272"}
{"level":"error","ts":"2024-12-11T01:49:10.701906708Z","msg":"Error while running manager","logger":"pgbouncer-manager","error":"signal: segmentation fault (core dumped)","stacktrace":"github.com/cloudnative-pg/machinery/pkg/log.(*logger).Error\n\tpkg/mod/github.com/cloudnative-pg/machinery@v0.0.0-20241014090714-c27747f9974b/pkg/log/log.go:125\ngithub.com/cloudnative-pg/cloudnative-pg/internal/cmd/manager/pgbouncer/run.NewCmd.func2\n\tinternal/cmd/manager/pgbouncer/run/cmd.go:75\ngithub.com/spf13/cobra.(*Command).execute\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:985\ngithub.com/spf13/cobra.(*Command).ExecuteC\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1117\ngithub.com/spf13/cobra.(*Command).Execute\n\tpkg/mod/github.com/spf13/cobra@v1.8.1/command.go:1041\nmain.main\n\tcmd/manager/main.go:68\nruntime.main\n\t/opt/hostedtoolcache/go/1.23.2/x64/src/runtime/proc.go:272"}

$ pgbouncer --version
PgBouncer 1.23.0
libevent 2.1.8-stable
adns: evdns2
tls: OpenSSL 1.1.1n  15 Mar 2022

and given https://github.com/pgbouncer/pgbouncer/releases/tag/pgbouncer_1_23_1-fixed --- see that this very problem was a bug fixed in 1.23.1.

same here