make: *** [px4fmu-v2_default] Error 2

I reinstalled Ubuntu 16.04LTS on my notebook, so I have to reinstalled PX4 Toolchain but error happen when I tried 'make px4fmu-v2_default' (I've already 'make distclean') I have no idea what to do? it's shown like this
-- Build Type: MinSizeRel
-- PX4 VERSION: v1.6.5-1384-g0d5480e
-- CONFIG: nuttx-px4fmu-v2-default
-- The ASM compiler identification is GNU
-- Found assembler: /home/bsowlin/gcc-arm-none-eabi-5_4-2016q2/bin/arm-none-eabi-gcc
-- Found PythonInterp: /usr/bin/python (found version "2.7.12")
-- Found PY_jinja2: /usr/local/lib/python2.7/dist-packages/jinja2
-- C compiler: arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 5.4.1 20160609 (release) [ARM/embedded-5-branch revision 237715]
-- C++ compiler: arm-none-eabi-g++ (GNU Tools for ARM Embedded Processors) 5.4.1 20160609 (release) [ARM/embedded-5-branch revision 237715]
-- Building and including px4io-v2
-- Configuring
-- Version: 1.0.6
-- To change the version modify the file configure.ac
-- micro-CDR without check endianness
-- NuttX: px4fmu-v2 nsh cortex-m4
-- ROMFS: px4fmu_common
-- Configuring done
-- Generating done
-- Build files have been written to: /home/bsowlin/src/Firmware/build/px4fmu-v2_default
Scanning dependencies of target ver_gen
Scanning dependencies of target uorb_headers
Scanning dependencies of target lib__micro-CDR
[  1%] Generating git hash header
[  1%] Generating uORB topic headers
[  1%] Building C object src/lib/micro-CDR/src/c/CMakeFiles/lib__micro-CDR.dir/microCdr.c.obj
[  1%] Built target ver_gen
Scanning dependencies of target copy_px4io_bin
[  1%] Building px4io-v2
make[4]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
Scanning dependencies of target nuttx_configure
[  1%] Linking C static library liblib__micro-CDR.a
[  1%] Built target lib__micro-CDR
Scanning dependencies of target git_nuttx
[  1%] git submodule platforms/nuttx/NuttX/nuttx
[  1%] Copying NuttX/apps to /home/bsowlin/src/Firmware/build/px4fmu-v2_default/NuttX
[  1%] Built target git_nuttx
Scanning dependencies of target git_ecl
[  1%] git submodule src/lib/ecl
[  1%] Built target git_ecl
Scanning dependencies of target mixer_gen
[  1%] Generating mixer_multirotor.generated.h
[  1%] Built target mixer_gen
Scanning dependencies of target airframes_xml
[  1%] Creating airframes.xml
[  1%] Built target airframes_xml
Scanning dependencies of target parameters_xml
[  1%] Generating parameters.xml
[  1%] Copying NuttX/nuttx to /home/bsowlin/src/Firmware/build/px4fmu-v2_default/NuttX
-- Build Type: MinSizeRel
[  1%] Copying NuttX config px4fmu-v2 and configuring
-- PX4 VERSION: v1.6.5-1384-g0d5480e
-- CONFIG: nuttx-px4io-v2-default
-- The ASM compiler identification is GNU
-- Found assembler: /home/bsowlin/gcc-arm-none-eabi-5_4-2016q2/bin/arm-none-eabi-gcc
-- Found PythonInterp: /usr/bin/python (found version "2.7.12")
[  1%] Built target nuttx_configure
-- Found PY_jinja2: /usr/local/lib/python2.7/dist-packages/jinja2
-- C compiler: arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 5.4.1 20160609 (release) [ARM/embedded-5-branch revision 237715]
-- C++ compiler: arm-none-eabi-g++ (GNU Tools for ARM Embedded Processors) 5.4.1 20160609 (release) [ARM/embedded-5-branch revision 237715]
-- Configuring
-- Version: 1.0.6
-- To change the version modify the file configure.ac
-- micro-CDR without check endianness
-- NuttX: px4io-v2 nsh cortex-m3
-- Configuring done
Scanning dependencies of target nuttx_context
[  1%] Built target uorb_headers
-- Generating done
-- Build files have been written to: /home/bsowlin/src/Firmware/build/px4io-v2_default
Scanning dependencies of target lib__micro-CDR
Scanning dependencies of target git_nuttx
Scanning dependencies of target uorb_headers
[  0%] git submodule platforms/nuttx/NuttX/nuttx
[  0%] Building C object src/lib/micro-CDR/src/c/CMakeFiles/lib__micro-CDR.dir/microCdr.c.obj
[  0%] Generating uORB topic headers
[  1%] Built target parameters_xml
[  0%] Built target git_nuttx
Scanning dependencies of target mixer_gen
[  0%] Generating mixer_multirotor.generated.h
[  0%] Built target mixer_gen
[  1%] Generating nuttx/include/nuttx/version.h, nuttx/include/nuttx/config.h
make[4]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
Scanning dependencies of target nuttx_configure
[  0%] Copying NuttX/apps to /home/bsowlin/src/Firmware/build/px4io-v2_default/NuttX
[  3%] Copying NuttX/nuttx to /home/bsowlin/src/Firmware/build/px4io-v2_default/NuttX
[  7%] Linking C static library liblib__micro-CDR.a
[ 10%] Copying NuttX config px4io-v2 and configuring
[ 10%] Built target lib__micro-CDR
[ 10%] Built target nuttx_configure
[ 10%] Built target uorb_headers
Scanning dependencies of target nuttx_context
[  2%] Built target nuttx_context
Scanning dependencies of target nuttx_mm_build
Scanning dependencies of target nuttx_sched_build
[  2%] Generating nuttx/mm/libmm.a
[  2%] Generating nuttx/sched/libsched.a
make[4]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
make[4]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
Scanning dependencies of target nuttx_configs_build
[  2%] Generating nuttx/configs/libconfigs.a
make[4]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
[  2%] Built target nuttx_configs_build
Scanning dependencies of target nuttx_binfmt_build
[  2%] Generating nuttx/binfmt/libbinfmt.a
make[4]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
[ 14%] Generating nuttx/include/nuttx/version.h, nuttx/include/nuttx/config.h
make[8]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
[  2%] Built target nuttx_mm_build
Scanning dependencies of target nuttx_drivers_build
[  2%] Generating nuttx/drivers/libdrivers.a
make[4]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
[  2%] Built target nuttx_binfmt_build
Scanning dependencies of target nuttx_arch_build
[  2%] Generating nuttx/arch/arm/src/libarch.a
make[4]: warning: jobserver unavailable: using -j1.  Add '+' to parent make rule.
[ 17%] Built target nuttx_context
Scanning dependencies of target prebuild_targets
[ 17%] Built target prebuild_targets
Scanning dependencies of target platforms__common
[ 17%] Building CXX object src/platforms/common/CMakeFiles/platforms__common.dir/module.cpp.obj
[ 21%] Building C object src/platforms/common/CMakeFiles/platforms__common.dir/px4_getopt.c.obj
[ 25%] Building CXX object src/platforms/common/CMakeFiles/platforms__common.dir/shutdown.cpp.obj
[ 25%] Linking CXX static library libplatforms__common.a
[ 25%] Built target platforms__common
Scanning dependencies of target modules__px4iofirmware
Scanning dependencies of target drivers__boards__px4io-v2
Scanning dependencies of target drivers__stm32
Scanning dependencies of target lib__rc
[ 28%] Building C object src/drivers/boards/px4io-v2/CMakeFiles/drivers__boards__px4io-v2.dir/px4io_init.c.obj
[ 28%] Building CXX object src/lib/rc/CMakeFiles/lib__rc.dir/st24.cpp.obj
[ 32%] Building C object src/modules/px4iofirmware/CMakeFiles/modules__px4iofirmware.dir//systemlib/hx_stream.c.obj
[ 32%] Building C object src/drivers/stm32/CMakeFiles/drivers__stm32.dir/drv_hrt.c.obj
[ 32%] Building C object src/drivers/boards/px4io-v2/CMakeFiles/drivers__boards__px4io-v2.dir/px4io_timer_config.c.obj
[ 35%] Building C object src/modules/px4iofirmware/CMakeFiles/modules__px4iofirmware.dir//systemlib/perf_counter.c.obj
[ 39%] Linking C static library libdrivers__boards__px4io-v2.a
[ 42%] Building CXX object src/lib/rc/CMakeFiles/lib__rc.dir/sumd.cpp.obj
[ 46%] Building C object src/drivers/stm32/CMakeFiles/drivers__stm32.dir/drv_io_timer.c.obj
[ 46%] Built target drivers__boards__px4io-v2
[ 46%] Building C object src/drivers/stm32/CMakeFiles/drivers__stm32.dir/drv_pwm_servo.c.obj
[ 50%] Building C object src/drivers/stm32/CMakeFiles/drivers__stm32.dir/drv_pwm_trigger.c.obj
[ 50%] Building C object src/modules/px4iofirmware/CMakeFiles/modules__px4iofirmware.dir//systemlib/pwm_limit/pwm_limit.c.obj
[ 53%] Building CXX object src/lib/rc/CMakeFiles/lib__rc.dir/sbus.cpp.obj
[ 57%] Building C object src/drivers/stm32/CMakeFiles/drivers__stm32.dir/drv_input_capture.c.obj
[ 57%] Building CXX object src/drivers/stm32/CMakeFiles/drivers__stm32.dir/drv_led_pwm.cpp.obj
[ 60%] Building C object src/modules/px4iofirmware/CMakeFiles/modules__px4iofirmware.dir/adc.c.obj
[ 60%] Building C object src/modules/px4iofirmware/CMakeFiles/modules__px4iofirmware.dir/controls.c.obj
[ 64%] Linking CXX static library libdrivers__stm32.a
[ 64%] Built target drivers__stm32
[ 67%] Building CXX object src/modules/px4iofirmware/CMakeFiles/modules__px4iofirmware.dir/mixer.cpp.obj
[ 67%] Building C object src/modules/px4iofirmware/CMakeFiles/modules__px4iofirmware.dir/px4io.c.obj
[ 67%] Building CXX object src/lib/rc/CMakeFiles/lib__rc.dir/dsm.cpp.obj
[ 71%] Building C object src/modules/px4iofirmware/CMakeFiles/modules__px4iofirmware.dir/registers.c.obj
[ 71%] Building C object src/modules/px4iofirmware/CMakeFiles/modules__px4iofirmware.dir/safety.c.obj
[ 75%] Building CXX object src/lib/rc/CMakeFiles/lib__rc.dir/common_rc.cpp.obj
[ 78%] Building C object src/modules/px4iofirmware/CMakeFiles/modules__px4iofirmware.dir/serial.c.obj
Scanning dependencies of target modules__systemlib__mixer
[ 78%] Linking CXX static library liblib__rc.a
[ 82%] Building CXX object src/modules/systemlib/mixer/CMakeFiles/modules__systemlib__mixer.dir/mixer_group.cpp.obj
[ 82%] Building CXX object src/modules/systemlib/mixer/CMakeFiles/modules__systemlib__mixer.dir/mixer.cpp.obj
[ 82%] Built target lib__rc
[ 85%] Linking CXX static library libmodules__px4iofirmware.a
[ 85%] Building CXX object src/modules/systemlib/mixer/CMakeFiles/modules__systemlib__mixer.dir/mixer_helicopter.cpp.obj
[ 85%] Built target modules__px4iofirmware
[ 89%] Building C object src/modules/systemlib/mixer/CMakeFiles/modules__systemlib__mixer.dir/mixer_load.c.obj
[ 89%] Building CXX object src/modules/systemlib/mixer/CMakeFiles/modules__systemlib__mixer.dir/mixer_multirotor.cpp.obj
[ 92%] Building CXX object src/modules/systemlib/mixer/CMakeFiles/modules__systemlib__mixer.dir/mixer_simple.cpp.obj
[ 96%] Linking CXX static library libmodules__systemlib__mixer.a
[ 96%] Built target modules__systemlib__mixer
Scanning dependencies of target nuttx_px4io-v2_default.elf
make[7]: *** No rule to make target 'NuttX/apps/libapps.a', needed by 'nuttx_px4io-v2_default.elf'.  Stop.
make[7]: *** Waiting for unfinished jobs....
[ 96%] Building C object src/firmware/nuttx/CMakeFiles/nuttx_px4io-v2_default.elf.dir//__/platforms/empty.c.obj
CMakeFiles/Makefile2:2260: recipe for target 'src/firmware/nuttx/CMakeFiles/nuttx_px4io-v2_default.elf.dir/all' failed
make[6]: *** [src/firmware/nuttx/CMakeFiles/nuttx_px4io-v2_default.elf.dir/all] Error 2
Makefile:160: recipe for target 'all' failed
make[5]: *** [all] Error 2
Makefile:166: recipe for target 'px4io-v2_default' failed
make[4]: *** [px4io-v2_default] Error 2
src/drivers/px4io/CMakeFiles/copy_px4io_bin.dir/build.make:93: recipe for target '../px4io-v2_default/nuttx_px4io-v2_default.elf' failed
make[3]: *** [../px4io-v2_default/nuttx_px4io-v2_default.elf] Error 2
CMakeFiles/Makefile2:1945: recipe for target 'src/drivers/px4io/CMakeFiles/copy_px4io_bin.dir/all' failed
make[2]: *** [src/drivers/px4io/CMakeFiles/copy_px4io_bin.dir/all] Error 2
make[2]: *** Waiting for unfinished jobs....
[  2%] Built target nuttx_arch_build
[  2%] Built target nuttx_drivers_build
[  2%] Built target nuttx_sched_build
Makefile:160: recipe for target 'all' failed
make[1]: *** [all] Error 2
Makefile:166: recipe for target 'px4fmu-v2_default' failed
make: *** [px4fmu-v2_default] Error 2
Appreciate every answer. Thank you.

Hi @bsowlin, I wonder if you've hit on a Makefile problem. All the CI systems and most developers are using ninja-build instead of cmake.
Can you try ninja? sudo apt-get install ninja-build Then make distclean and make px4fmu-v2_default.
I'll try to reproduce this with regular Makefiles and find a fix.

@dagar Thank you so much man. It's work!!!! and surprisingly. It's so much faster than regular one I love it.

Yes it will use ninja by default if found.

sorry, can't follow as i have the same error. is it that my system should only contain ninja-build only ?
ninja: error: '../../platforms/nuttx/NuttX/nuttx/.git', needed by 'NuttX/git_init_nuttx.stamp', missing and no known rule to make it
$ ninja --version
1.6.0
$ ninja-build --version
1.7.2

I got the same problem....currently I am using PixhawkPSP_v3.0.3. I try to build firmware, and the following error appear...
-- PX4 VERSION: v1.8.0-1010-gbf87270ded
-- CONFIG: nuttx_px4fmu-v2_default
-- Build Type: MinSizeRel
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:69 (message):
The CMAKE_FORCE_C_COMPILER macro is deprecated.  Instead just set
CMAKE_C_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:30 (cmake_force_c_compiler)
/usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:94 (include)
CMakeLists.txt:174 (project)
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:83 (message):
The CMAKE_FORCE_CXX_COMPILER macro is deprecated.  Instead just set
CMAKE_CXX_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:36 (cmake_force_cxx_compiler)
/usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:94 (include)
CMakeLists.txt:174 (project)
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:69 (message):
The CMAKE_FORCE_C_COMPILER macro is deprecated.  Instead just set
CMAKE_C_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:30 (cmake_force_c_compiler)
build/nuttx_px4fmu-v2_default/CMakeFiles/3.10.2/CMakeSystem.cmake:6 (include)
CMakeLists.txt:174 (project)
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:83 (message):
The CMAKE_FORCE_CXX_COMPILER macro is deprecated.  Instead just set
CMAKE_CXX_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:36 (cmake_force_cxx_compiler)
build/nuttx_px4fmu-v2_default/CMakeFiles/3.10.2/CMakeSystem.cmake:6 (include)
CMakeLists.txt:174 (project)
-- The ASM compiler identification is GNU
-- Found assembler: /home/mbangtri/gcc-arm-none-eabi-5_4-2017q2/bin/arm-none-eabi-gcc
-- Found PythonInterp: /usr/bin/python (found version "2.7.15")
-- Found PY_jinja2: /usr/local/lib/python2.7/dist-packages/jinja2
-- C compiler: arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 5.4.1 20160919 (release) [ARM/embedded-5-branch revision 240496]
-- C++ compiler: arm-none-eabi-g++ (GNU Tools for ARM Embedded Processors) 5.4.1 20160919 (release) [ARM/embedded-5-branch revision 240496]
-- PX4 ECL: Very lightweight Estimation & Control Library v0.9.0-583-g56b8bb0
-- Building and including px4io-v2
-- NuttX: px4fmu-v2 nsh cortex-m4
-- ROMFS: px4fmu_common
-- Configuring done
-- Generating done
-- Build files have been written to: /mnt/c/PX4/Firmware/build/nuttx_px4fmu-v2_default
ninja: Entering directory `/mnt/c/PX4/Firmware/build/nuttx_px4fmu-v2_default'
[3/658] Building px4io-v2
-- PX4 VERSION: v1.8.0-1010-gbf87270ded
-- CONFIG: nuttx_px4io-v2_default
-- Build Type: MinSizeRel
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:69 (message):
The CMAKE_FORCE_C_COMPILER macro is deprecated.  Instead just set
CMAKE_C_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:30 (cmake_force_c_compiler)
/usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:94 (include)
CMakeLists.txt:174 (project)
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:83 (message):
The CMAKE_FORCE_CXX_COMPILER macro is deprecated.  Instead just set
CMAKE_CXX_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:36 (cmake_force_cxx_compiler)
/usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:94 (include)
CMakeLists.txt:174 (project)
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:69 (message):
The CMAKE_FORCE_C_COMPILER macro is deprecated.  Instead just set
CMAKE_C_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:30 (cmake_force_c_compiler)
build/nuttx_px4io-v2_default/CMakeFiles/3.10.2/CMakeSystem.cmake:6 (include)
CMakeLists.txt:174 (project)
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:83 (message):
The CMAKE_FORCE_CXX_COMPILER macro is deprecated.  Instead just set
CMAKE_CXX_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:36 (cmake_force_cxx_compiler)
build/nuttx_px4io-v2_default/CMakeFiles/3.10.2/CMakeSystem.cmake:6 (include)
CMakeLists.txt:174 (project)
-- The ASM compiler identification is GNU
-- Found assembler: /home/mbangtri/gcc-arm-none-eabi-5_4-2017q2/bin/arm-none-eabi-gcc
-- Found PythonInterp: /usr/bin/python (found version "2.7.15")
-- Found PY_jinja2: /usr/local/lib/python2.7/dist-packages/jinja2
-- C compiler: arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 5.4.1 20160919 (release) [ARM/embedded-5-branch revision 240496]
-- C++ compiler: arm-none-eabi-g++ (GNU Tools for ARM Embedded Processors) 5.4.1 20160919 (release) [ARM/embedded-5-branch revision 240496]
-- PX4 ECL: Very lightweight Estimation & Control Library v0.9.0-583-g56b8bb0
-- NuttX: px4io-v2 nsh cortex-m3
-- Configuring done
-- Generating done
-- Build files have been written to: /mnt/c/PX4/Firmware/build/nuttx_px4io-v2_default
ninja: Entering directory `/mnt/c/PX4/Firmware/build/nuttx_px4io-v2_default'
[202/202] Creating /mnt/c/PX4/Firmware/build/nuttx_px4io-v2_default/px4io-v2_default.px4
[11/658] Generating parameters.xml
FAILED: parameters.xml
cd /mnt/c/PX4/Firmware/build/nuttx_px4fmu-v2_default/src/lib/parameters && /usr/bin/python /mnt/c/PX4/Firmware/src/lib/parameters/px_process_params.py --src-path /mnt/c/PX4/Firmware/src/lib/DriverFramework/framework /mnt/c/PX4/Firmware/src/lib/airspeed /mnt/c/PX4/Firmware/src/lib/battery /mnt/c/PX4/Firmware/src/lib/bezier /mnt/c/PX4/Firmware/src/lib/cdev /mnt/c/PX4/Firmware/src/lib/circuit_breaker /mnt/c/PX4/Firmware/src/lib/controllib /mnt/c/PX4/Firmware/src/lib/conversion /mnt/c/PX4/Firmware/src/lib/drivers/airspeed /mnt/c/PX4/Firmware/src/lib/drivers/device /mnt/c/PX4/Firmware/src/lib/drivers/led /mnt/c/PX4/Firmware/src/lib/FlightTasks /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/FlightTask /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/Utility /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/Manual /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/Auto /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/AutoMapper /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/ManualStabilized /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/ManualAltitude /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/ManualAltitudeSmooth /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/ManualPosition /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/ManualPositionSmooth /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/AutoLine /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/AutoFollowMe /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/Offboard /mnt/c/PX4/Firmware/src/lib/led /mnt/c/PX4/Firmware/src/lib/mathlib /mnt/c/PX4/Firmware/src/lib/pid /mnt/c/PX4/Firmware/src/lib/pwm_limit /mnt/c/PX4/Firmware/src/lib/terrain_estimation /mnt/c/PX4/Firmware/src/lib/tunes /mnt/c/PX4/Firmware/src/platforms/common /mnt/c/PX4/Firmware/src/modules/systemlib /mnt/c/PX4/Firmware/src/modules/uORB /mnt/c/PX4/Firmware/src/drivers/boards/common /mnt/c/PX4/Firmware/src/drivers/boards/px4fmu-v2 /mnt/c/PX4/Firmware/src/drivers/barometer/ms5611 /mnt/c/PX4/Firmware/src/drivers/camera_trigger /mnt/c/PX4/Firmware/src/drivers/differential_pressure/ms4525 /mnt/c/PX4/Firmware/src/drivers/differential_pressure/ms5525 /mnt/c/PX4/Firmware/src/drivers/differential_pressure/sdp3x /mnt/c/PX4/Firmware/src/drivers/distance_sensor/ll40ls /mnt/c/PX4/Firmware/src/drivers/distance_sensor/sf0x /mnt/c/PX4/Firmware/src/drivers/distance_sensor/sf1xx /mnt/c/PX4/Firmware/src/drivers/distance_sensor/srf02 /mnt/c/PX4/Firmware/src/drivers/gps /mnt/c/PX4/Firmware/src/drivers/imu/l3gd20 /mnt/c/PX4/Firmware/src/drivers/imu/lsm303d /mnt/c/PX4/Firmware/src/drivers/imu/mpu6000 /mnt/c/PX4/Firmware/src/drivers/imu/mpu9250 /mnt/c/PX4/Firmware/src/drivers/magnetometer/hmc5883 /mnt/c/PX4/Firmware/src/drivers/magnetometer/lis3mdl /mnt/c/PX4/Firmware/src/drivers/pwm_input /mnt/c/PX4/Firmware/src/drivers/px4flow /mnt/c/PX4/Firmware/src/drivers/px4fmu /mnt/c/PX4/Firmware/src/drivers/px4io /mnt/c/PX4/Firmware/src/drivers/rgbled /mnt/c/PX4/Firmware/src/drivers/stm32/adc /mnt/c/PX4/Firmware/src/drivers/stm32/tone_alarm /mnt/c/PX4/Firmware/src/drivers/vmount /mnt/c/PX4/Firmware/src/modules/sensors /mnt/c/PX4/Firmware/src/systemcmds/hardfault_log /mnt/c/PX4/Firmware/src/systemcmds/mixer /mnt/c/PX4/Firmware/src/systemcmds/mtd /mnt/c/PX4/Firmware/src/systemcmds/param /mnt/c/PX4/Firmware/src/systemcmds/perf /mnt/c/PX4/Firmware/src/systemcmds/pwm /mnt/c/PX4/Firmware/src/systemcmds/reboot /mnt/c/PX4/Firmware/src/systemcmds/top /mnt/c/PX4/Firmware/src/systemcmds/tune_control /mnt/c/PX4/Firmware/src/systemcmds/ver /mnt/c/PX4/Firmware/src/modules/camera_feedback /mnt/c/PX4/Firmware/src/modules/commander /mnt/c/PX4/Firmware/src/modules/events /mnt/c/PX4/Firmware/src/modules/land_detector /mnt/c/PX4/Firmware/src/modules/load_mon /mnt/c/PX4/Firmware/src/modules/mavlink /mnt/c/PX4/Firmware/src/modules/navigator /mnt/c/PX4/Firmware/src/modules/ekf2 /mnt/c/PX4/Firmware/src/modules/fw_att_control /mnt/c/PX4/Firmware/src/modules/fw_pos_control_l1/launchdetection /mnt/c/PX4/Firmware/src/modules/fw_pos_control_l1/runway_takeoff /mnt/c/PX4/Firmware/src/modules/fw_pos_control_l1 /mnt/c/PX4/Firmware/src/modules/mc_att_control /mnt/c/PX4/Firmware/src/modules/mc_pos_control /mnt/c/PX4/Firmware/src/modules/vtol_att_control /mnt/c/PX4/Firmware/src/modules/logger /mnt/c/PX4/Firmware/src/modules/dataman /mnt/c/PX4/Firmware/src/drivers/camera_trigger/interfaces /mnt/c/PX4/Firmware/src/drivers/distance_sensor/sf0x/sf0x_tests /mnt/c/PX4/Firmware/src/drivers/gps/devices /mnt/c/PX4/Firmware/src/drivers/stm32 /mnt/c/PX4/Firmware/src/modules/commander/commander_tests /mnt/c/PX4/Firmware/src/modules/commander/failure_detector /mnt/c/PX4/Firmware/src/modules/events/temperature_calibration /mnt/c/PX4/Firmware/src/modules/mavlink/mavlink_tests /mnt/c/PX4/Firmware/src/modules/fw_pos_control_l1/mtecs /mnt/c/PX4/Firmware/src/modules/mc_pos_control/Utility /mnt/c/PX4/Firmware/src/modules/mc_pos_control/mc_pos_control_tests --xml /mnt/c/PX4/Firmware/build/nuttx_px4fmu-v2_default/parameters.xml --inject-xml /mnt/c/PX4/Firmware/src/lib/parameters/parameters_injected.xml --overrides {} --board px4fmu-v2
Duplicate parameter definition: BAT_CAPACITY+
[14/658] Copying NuttX/nuttx to /mnt/c/PX4/Firmware/build/nuttx_px4fmu-v2_default/NuttX
ninja: build stopped: subcommand failed.
Makefile:154: recipe for target 'px4fmu-v2_default' failed
make: *** [px4fmu-v2_default] Error 1

I got the same problem....currently I am using PixhawkPSP_v3.0.3. I try to build firmware, and the following error appear...
-- PX4 VERSION: v1.8.0-1010-gbf87270ded
-- CONFIG: nuttx_px4fmu-v2_default
-- Build Type: MinSizeRel
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:69 (message):
The CMAKE_FORCE_C_COMPILER macro is deprecated. Instead just set
CMAKE_C_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:30 (cmake_force_c_compiler)
/usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:94 (include)
CMakeLists.txt:174 (project)
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:83 (message):
The CMAKE_FORCE_CXX_COMPILER macro is deprecated. Instead just set
CMAKE_CXX_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:36 (cmake_force_cxx_compiler)
/usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:94 (include)
CMakeLists.txt:174 (project)
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:69 (message):
The CMAKE_FORCE_C_COMPILER macro is deprecated. Instead just set
CMAKE_C_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:30 (cmake_force_c_compiler)
build/nuttx_px4fmu-v2_default/CMakeFiles/3.10.2/CMakeSystem.cmake:6 (include)
CMakeLists.txt:174 (project)
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:83 (message):
The CMAKE_FORCE_CXX_COMPILER macro is deprecated. Instead just set
CMAKE_CXX_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:36 (cmake_force_cxx_compiler)
build/nuttx_px4fmu-v2_default/CMakeFiles/3.10.2/CMakeSystem.cmake:6 (include)
CMakeLists.txt:174 (project)
-- The ASM compiler identification is GNU
-- Found assembler: /home/mbangtri/gcc-arm-none-eabi-5_4-2017q2/bin/arm-none-eabi-gcc
-- Found PythonInterp: /usr/bin/python (found version "2.7.15")
-- Found PY_jinja2: /usr/local/lib/python2.7/dist-packages/jinja2
-- C compiler: arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 5.4.1 20160919 (release) [ARM/embedded-5-branch revision 240496]
-- C++ compiler: arm-none-eabi-g++ (GNU Tools for ARM Embedded Processors) 5.4.1 20160919 (release) [ARM/embedded-5-branch revision 240496]
-- PX4 ECL: Very lightweight Estimation & Control Library v0.9.0-583-g56b8bb0
-- Building and including px4io-v2
-- NuttX: px4fmu-v2 nsh cortex-m4
-- ROMFS: px4fmu_common
-- Configuring done
-- Generating done
-- Build files have been written to: /mnt/c/PX4/Firmware/build/nuttx_px4fmu-v2_default
ninja: Entering directory `/mnt/c/PX4/Firmware/build/nuttx_px4fmu-v2_default'
[3/658] Building px4io-v2
-- PX4 VERSION: v1.8.0-1010-gbf87270ded
-- CONFIG: nuttx_px4io-v2_default
-- Build Type: MinSizeRel
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:69 (message):
The CMAKE_FORCE_C_COMPILER macro is deprecated. Instead just set
CMAKE_C_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:30 (cmake_force_c_compiler)
/usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:94 (include)
CMakeLists.txt:174 (project)
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:83 (message):
The CMAKE_FORCE_CXX_COMPILER macro is deprecated. Instead just set
CMAKE_CXX_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:36 (cmake_force_cxx_compiler)
/usr/share/cmake-3.10/Modules/CMakeDetermineSystem.cmake:94 (include)
CMakeLists.txt:174 (project)
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:69 (message):
The CMAKE_FORCE_C_COMPILER macro is deprecated. Instead just set
CMAKE_C_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:30 (cmake_force_c_compiler)
build/nuttx_px4io-v2_default/CMakeFiles/3.10.2/CMakeSystem.cmake:6 (include)
CMakeLists.txt:174 (project)
CMake Deprecation Warning at /usr/share/cmake-3.10/Modules/CMakeForceCompiler.cmake:83 (message):
The CMAKE_FORCE_CXX_COMPILER macro is deprecated. Instead just set
CMAKE_CXX_COMPILER and allow CMake to identify the compiler.
Call Stack (most recent call first):
cmake/toolchains/Toolchain-arm-none-eabi.cmake:36 (cmake_force_cxx_compiler)
build/nuttx_px4io-v2_default/CMakeFiles/3.10.2/CMakeSystem.cmake:6 (include)
CMakeLists.txt:174 (project)
-- The ASM compiler identification is GNU
-- Found assembler: /home/mbangtri/gcc-arm-none-eabi-5_4-2017q2/bin/arm-none-eabi-gcc
-- Found PythonInterp: /usr/bin/python (found version "2.7.15")
-- Found PY_jinja2: /usr/local/lib/python2.7/dist-packages/jinja2
-- C compiler: arm-none-eabi-gcc (GNU Tools for ARM Embedded Processors) 5.4.1 20160919 (release) [ARM/embedded-5-branch revision 240496]
-- C++ compiler: arm-none-eabi-g++ (GNU Tools for ARM Embedded Processors) 5.4.1 20160919 (release) [ARM/embedded-5-branch revision 240496]
-- PX4 ECL: Very lightweight Estimation & Control Library v0.9.0-583-g56b8bb0
-- NuttX: px4io-v2 nsh cortex-m3
-- Configuring done
-- Generating done
-- Build files have been written to: /mnt/c/PX4/Firmware/build/nuttx_px4io-v2_default
ninja: Entering directory `/mnt/c/PX4/Firmware/build/nuttx_px4io-v2_default'
[202/202] Creating /mnt/c/PX4/Firmware/build/nuttx_px4io-v2_default/px4io-v2_default.px4
[11/658] Generating parameters.xml
FAILED: parameters.xml
cd /mnt/c/PX4/Firmware/build/nuttx_px4fmu-v2_default/src/lib/parameters && /usr/bin/python /mnt/c/PX4/Firmware/src/lib/parameters/px_process_params.py --src-path /mnt/c/PX4/Firmware/src/lib/DriverFramework/framework /mnt/c/PX4/Firmware/src/lib/airspeed /mnt/c/PX4/Firmware/src/lib/battery /mnt/c/PX4/Firmware/src/lib/bezier /mnt/c/PX4/Firmware/src/lib/cdev /mnt/c/PX4/Firmware/src/lib/circuit_breaker /mnt/c/PX4/Firmware/src/lib/controllib /mnt/c/PX4/Firmware/src/lib/conversion /mnt/c/PX4/Firmware/src/lib/drivers/airspeed /mnt/c/PX4/Firmware/src/lib/drivers/device /mnt/c/PX4/Firmware/src/lib/drivers/led /mnt/c/PX4/Firmware/src/lib/FlightTasks /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/FlightTask /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/Utility /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/Manual /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/Auto /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/AutoMapper /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/ManualStabilized /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/ManualAltitude /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/ManualAltitudeSmooth /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/ManualPosition /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/ManualPositionSmooth /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/AutoLine /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/AutoFollowMe /mnt/c/PX4/Firmware/src/lib/FlightTasks/tasks/Offboard /mnt/c/PX4/Firmware/src/lib/led /mnt/c/PX4/Firmware/src/lib/mathlib /mnt/c/PX4/Firmware/src/lib/pid /mnt/c/PX4/Firmware/src/lib/pwm_limit /mnt/c/PX4/Firmware/src/lib/terrain_estimation /mnt/c/PX4/Firmware/src/lib/tunes /mnt/c/PX4/Firmware/src/platforms/common /mnt/c/PX4/Firmware/src/modules/systemlib /mnt/c/PX4/Firmware/src/modules/uORB /mnt/c/PX4/Firmware/src/drivers/boards/common /mnt/c/PX4/Firmware/src/drivers/boards/px4fmu-v2 /mnt/c/PX4/Firmware/src/drivers/barometer/ms5611 /mnt/c/PX4/Firmware/src/drivers/camera_trigger /mnt/c/PX4/Firmware/src/drivers/differential_pressure/ms4525 /mnt/c/PX4/Firmware/src/drivers/differential_pressure/ms5525 /mnt/c/PX4/Firmware/src/drivers/differential_pressure/sdp3x /mnt/c/PX4/Firmware/src/drivers/distance_sensor/ll40ls /mnt/c/PX4/Firmware/src/drivers/distance_sensor/sf0x /mnt/c/PX4/Firmware/src/drivers/distance_sensor/sf1xx /mnt/c/PX4/Firmware/src/drivers/distance_sensor/srf02 /mnt/c/PX4/Firmware/src/drivers/gps /mnt/c/PX4/Firmware/src/drivers/imu/l3gd20 /mnt/c/PX4/Firmware/src/drivers/imu/lsm303d /mnt/c/PX4/Firmware/src/drivers/imu/mpu6000 /mnt/c/PX4/Firmware/src/drivers/imu/mpu9250 /mnt/c/PX4/Firmware/src/drivers/magnetometer/hmc5883 /mnt/c/PX4/Firmware/src/drivers/magnetometer/lis3mdl /mnt/c/PX4/Firmware/src/drivers/pwm_input /mnt/c/PX4/Firmware/src/drivers/px4flow /mnt/c/PX4/Firmware/src/drivers/px4fmu /mnt/c/PX4/Firmware/src/drivers/px4io /mnt/c/PX4/Firmware/src/drivers/rgbled /mnt/c/PX4/Firmware/src/drivers/stm32/adc /mnt/c/PX4/Firmware/src/drivers/stm32/tone_alarm /mnt/c/PX4/Firmware/src/drivers/vmount /mnt/c/PX4/Firmware/src/modules/sensors /mnt/c/PX4/Firmware/src/systemcmds/hardfault_log /mnt/c/PX4/Firmware/src/systemcmds/mixer /mnt/c/PX4/Firmware/src/systemcmds/mtd /mnt/c/PX4/Firmware/src/systemcmds/param /mnt/c/PX4/Firmware/src/systemcmds/perf /mnt/c/PX4/Firmware/src/systemcmds/pwm /mnt/c/PX4/Firmware/src/systemcmds/reboot /mnt/c/PX4/Firmware/src/systemcmds/top /mnt/c/PX4/Firmware/src/systemcmds/tune_control /mnt/c/PX4/Firmware/src/systemcmds/ver /mnt/c/PX4/Firmware/src/modules/camera_feedback /mnt/c/PX4/Firmware/src/modules/commander /mnt/c/PX4/Firmware/src/modules/events /mnt/c/PX4/Firmware/src/modules/land_detector /mnt/c/PX4/Firmware/src/modules/load_mon /mnt/c/PX4/Firmware/src/modules/mavlink /mnt/c/PX4/Firmware/src/modules/navigator /mnt/c/PX4/Firmware/src/modules/ekf2 /mnt/c/PX4/Firmware/src/modules/fw_att_control /mnt/c/PX4/Firmware/src/modules/fw_pos_control_l1/launchdetection /mnt/c/PX4/Firmware/src/modules/fw_pos_control_l1/runway_takeoff /mnt/c/PX4/Firmware/src/modules/fw_pos_control_l1 /mnt/c/PX4/Firmware/src/modules/mc_att_control /mnt/c/PX4/Firmware/src/modules/mc_pos_control /mnt/c/PX4/Firmware/src/modules/vtol_att_control /mnt/c/PX4/Firmware/src/modules/logger /mnt/c/PX4/Firmware/src/modules/dataman /mnt/c/PX4/Firmware/src/drivers/camera_trigger/interfaces /mnt/c/PX4/Firmware/src/drivers/distance_sensor/sf0x/sf0x_tests /mnt/c/PX4/Firmware/src/drivers/gps/devices /mnt/c/PX4/Firmware/src/drivers/stm32 /mnt/c/PX4/Firmware/src/modules/commander/commander_tests /mnt/c/PX4/Firmware/src/modules/commander/failure_detector /mnt/c/PX4/Firmware/src/modules/events/temperature_calibration /mnt/c/PX4/Firmware/src/modules/mavlink/mavlink_tests /mnt/c/PX4/Firmware/src/modules/fw_pos_control_l1/mtecs /mnt/c/PX4/Firmware/src/modules/mc_pos_control/Utility /mnt/c/PX4/Firmware/src/modules/mc_pos_control/mc_pos_control_tests --xml /mnt/c/PX4/Firmware/build/nuttx_px4fmu-v2_default/parameters.xml --inject-xml /mnt/c/PX4/Firmware/src/lib/parameters/parameters_injected.xml --overrides {} --board px4fmu-v2
Duplicate parameter definition: BAT_CAPACITY+
[14/658] Copying NuttX/nuttx to /mnt/c/PX4/Firmware/build/nuttx_px4fmu-v2_default/NuttX
ninja: build stopped: subcommand failed.
Makefile:154: recipe for target 'px4fmu-v2_default' failed
make: *** [px4fmu-v2_default] Error 1

Again that problem any answer for it ?
ninja: fatal: chdir to '/cygdrive/d/mypx4/Firmware/build/nuttx_px4fmu-v3_default' - No such file or directory
make: *** [Makefile:154: px4fmu-v3_default] Error 1

@algebratech i too have same Problem, did you get any solution by now ?


Playback does not correctly end for some content

Description of the problem
When reaching the end of some contents we may get an error. For these same contents the player also does not reach the end screen displaying a restart button, even when playing the content normally to its end.
Relevant stack trace or log output
No response
Reproducibility
Always
Steps to reproduce

Open the Pillarbox demo.
Play the Switzerland say sorry example.
Seek to the end while keeping the finger down until the very end of the slider. The player displays an error (-16040).

Alternatively:

Open the Pillarbox demo.
Play the Switzerland say sorry example.
Seek near the end and wait until playback ends. The restart button is never displayed and the player is stuck with a non-working play button.

Library version
0.5.0
Operating system
iOS 16 and 17 beta 4
Code sample
No response
Is there an existing issue for this?

[x] I have searched existing issues and found no similar bug report.

This is an AVQueuePlayer issue which arises when seeking continuously (calling seek each time the slider is moved, e.g.) with tolerance before set to zero and tolerance after to infinity.
Here is a simple example that reproduces the issue with the system native player and UI. It also logs errors and seek targets to the console:
import AVKit
import Combine
import SwiftUI

class InspectorPlayer: AVQueuePlayer {
    override func seek(to time: CMTime, toleranceBefore: CMTime, toleranceAfter: CMTime, completionHandler: @escaping (Bool) -> Void) {
        print("--> t = \(time.seconds), b = \(toleranceBefore.seconds), a = \(toleranceAfter.seconds)")
        super.seek(to: time, toleranceBefore: toleranceBefore, toleranceAfter: toleranceAfter, completionHandler: completionHandler)
    }
}

// Behavior: h-exp, v-exp
struct VanillaPlayerView: View {
    let item: AVPlayerItem

    @State private var player = InspectorPlayer()

    var body: some View {
        VideoPlayer(player: player)
            .ignoresSafeArea()
            .overlay(alignment: .topLeading) {
                CloseButton()
            }
            .onAppear(perform: play)
            .onReceive(errorPublisher()) { error in
                print("--> error: \(error)")
            }
    }

    private func errorPublisher() -> AnyPublisher<Error, Never> {
        player.publisher(for: \.currentItem)
            .compactMap { item -> AnyPublisher<Error, Never>? in
                guard let item else { return nil }
                return NotificationCenter.default.publisher(for: .AVPlayerItemFailedToPlayToEndTime, object: item)
                    .compactMap { notification in
                        notification.userInfo?[AVPlayerItemFailedToPlayToEndTimeErrorKey] as? Error
                    }
                    .eraseToAnyPublisher()
            }
            .switchToLatest()
            .eraseToAnyPublisher()
    }

    private func play() {
        player.insert(item, after: nil)
        player.play()
    }
}

Setting both tolerances to zero or infinity fixes the issue, at the expense of a different behavior of course. The issue really seems to arise when one tolerance is zero and the other not zero (no matter which one).
We should definitely report this issue to Apple. @waliid also found that forcing tolerances to both zero (not both infinity) near the end of the stream seems to work, while preserving seeking behaviors that we currently have. This is similar to the mitigations (unsuccessful in this case) we attempted to ensure that playlist behavior is correct when seeking to the end of the current item. All these issues are likely related somehow.

If we replace AVQueuePlayer with AVPlayer in the above code (passing an item at construction time) the issue arises the same.

Setting tolerances near the end of the stream to .zero works, though the tolerance applied must be large. I tried several values but had to increase the tolerance to 18 seconds at least to get stable behavior on a wide variety of content.
This value does not seem to be related to the chunk size of the content being played (in my case I considered content with a chunk size of 10 seconds, e.g.). But 18 is still an interesting value. It corresponds to 3 times the recommended HLS chunk size. Maybe a coincidence, maybe not.

A workaround is to enhance accuracy towards the end of playback by adjusting tolerance parameters.
func seek(
        to time: CMTime,
        toleranceBefore: CMTime = .positiveInfinity,
        toleranceAfter: CMTime = .positiveInfinity,
        smooth: Bool,
        completionHandler: @escaping (Bool) -> Void
    ) {
        ...
        let isVeryCloseToTheEnd = ((currentItem?.duration.seconds ?? 0) - 4)...(currentItem?.duration.seconds ?? 0) ~= time.seconds
        let seek = Seek(
            time: time,
            toleranceBefore: isVeryCloseToTheEnd ? .zero : toleranceBefore,
            toleranceAfter: isVeryCloseToTheEnd ? .zero : toleranceAfter,
            isSmooth: smooth,
            completionHandler: completionHandler
        )
        ...
    }

ℹ The smallest working value is 3.7

Interesting information about media playlist packaging and durations.

The issue has been identified as a bug, likely only affecting streams supporting trick mode (we can namely easily reproduce it with Apple 16:9 basic streams or our own DRM-protected streams).
Reported under AVPlayer: Playback fails with a CoreMedia -16040 error when seeking near the end of a stream (FB13070742).

We mitigated the issue only for on-demand streams near the end of the time range, i.e. based on the itemDuration and time range. The testSkipForDvrInPastConditions was namely flaky if we attempted to apply the same criteria in all cases, which was also superfluous for DVR streams.


licenses: add OSL-3.0.

This change adds the Open Software License 3.0 (OSL-3.0). Downloaded from
https://opensource.org/licenses/OSL-3.0.

@googlebot I fixed it.


remove GetNonDerivedAttributes

i dont think it is used?

I am not planning on using it, it was probably factored out of the spaghetti code that was there before, that grabbed all the  attributes and filtered them in variety of ways, and later I've used IsNonDerivedAttributeDefined instead of it.


Changes to .reek.yml not updated in VSCode integration

The issues from #2 are fixed (very quickly, nice work!).
There is no LSP server error when .reek.yml is updated... However, config changes are not reflected in syntax highlighting.
For example, going from an 'empty' config file to:
---
detectors:
  IrresponsibleModule:
    enabled: false

Will restart the add on, but this will still be shown in the file:

Notes:

File was opened before config change.
Warning is still present if file is closed/re-opened.
Goes away if Ruby LSP server restarted.
I confirmed that changes to .rubocop.yml are reflected without restart (both in rubyLsp.linters VSCode config)

Not as big an issue as previous, config shouldn't change often, & restarting LSP is easy. But unexpected behavior nonetheless.

Unfortunately, I don't use VSCode and my nvim-lsp does not have the config-file detection, so I'm flying a bit blind here. I'll try to see what rubocop is doing and try to emulate that.

Understandable! Again, I don't think it is urgently needed, hopefully if other people run into the issue they will find this and know to just restart the server.
I will poke around some myself. If you want me to test out a branch locally, feel free to ping me!


Replace: replacing one by one flickers the editor

See this video where upon replacing individual entries the editor flashes quite badly:

Looks like the affect of adoption to text model.


feat: Add Compression to Hacker News w/ Islands Example

One of the things I love about leptos is how easy it is to ship a small frontend.
Leptos provides islands that reduce the amount of total HTML generated and it's build tool minifies CSS with lightningcss, soon will be minifying javascript with swc, and it can even precompress these static assets. That last of which I think may be the most important because web assembly compress fairly well and it allows the user to ship their entire app as 1 static binary (with musl).
Since precompression was added as a feature in cargo-leptos I haven't seen it mentioned a whole lot so I wanted to help people see how to use it. I have also seen a couple question about setting up compression in general so I added that too.
I've updated the hackernews_islands_axum example to serve all static assets precompressed with cargo-leptos and to dynamically compress the HTML.
The type of compression sent will depend on what the client supports.
The resulting network usage

Asset
No Compression
Compression
Difference

HTML
16.25 kB
4.80 kB
- 70.46%

CSS
3.84 kB
1.17 kB
- 69.53%

JS
16.86 kB
4.63 kB
- 72.53%

WASM
200.15 kB
69.93 kB
- 65.06%

ICON
15.54 kB
3.29 kB
- 78.83%

TOTAL
252.64 kB
83.82 kB
- 66.82%

Fix lints for CI

Looks like the issue is that when building it is trying to access target/site which doesn't exist until cargo leptos build is run. I have updated the makefile to account for this.

I also add hash_file to the Cargo.toml. Since the compressed file are served with a Cache-Control policy hash_file is necessary to ensure that client receives the correct file when updates are made to an asset. I don't expect the example files to change much but for users copying & pasting this example to base their own app off of this will be helpful.

Cool -- This looks great, thanks!


Please add a licence file

Without a license file, the use of this great plugin in a private or commercial app is legally not allowed.

Hi, if you attach appropriate license file, i will add it to plugin

I created a pull request with an MIT license file.
I hope that the MIT license suits you. Otherwise I can create another one 👍


build: fix minor 'make check' error with go1.19

Fixed minor lint error when compiling the code with go1.19 (amd64, Fedora35).
Signed-off-by: Shachar Sharon<EMAIL_ADDRESS>

If this is related to a similar error I saw myself the other day (unstable iexport format). I think an alternative way to "fix" it that doesn't disable checks would be to update to a newer version of golangci-lint (see 33de25a for my "hack-around")

If this is related to a similar error I saw myself the other day (unstable iexport format). I think an alternative way to "fix" it that doesn't disable checks would be to update to a newer version of golangci-lint (see 33de25a for my "hack-around")

In that case, I will try to solve this (an other) by upgrading to newer version of golangci-lint. Please ignore this PR.

Fixed minor lint error when compiling the code with go1.19 (amd64, Fedora35).

I also encountered this make check error while working on #242 which I mentioned as a comment there.


Rare race condition suspected

Please provide the following details.

OS: Linux Debian 12
PHP: 8.1
php-mysql-replication: 7.0.1
8.0.27 - Oracle MYSQL
On a rare occasion, maybe once every 1000 times, an INSERT event will be triggered by php-mysql-replication, but an immediate SELECT query on the unique ID (passed in the insert values) will return no rows.
The same SELECT query will return a row if subsequently entered manually.
Is the INSERT event first sent to the binlog and THEN to the actual MySQL engine? It feels like there's a race condition there.
Transactions are not used in this particular scenario.

hi, can you replicate this using some code example ?


dashboard sensingkit: audio-level

Do not get any data for the audio-level sensingkit sensor.  Confirmed that light and accelerometer work as expected.  Using nexus 7, and have had audio-level work fine with standalone version of the sensingkit app.

Yeah. I know audio-level is currently not currently working. It requires a runtime permission request. Location only needs the permission when you choose to use location as a sensor. Audio-level however requires the permission as soon as the sensor kit stuff starts running regardless or whether you're using audio-level or not. I haven't quite worked out the best way to deal with that yet.

Could we just remove it from the driver for now?

(IIRC this is because SensingKit was written before runtime permissions were a thing (when you had to agree to all permissions while installing) and ideally should be fixed upstream in SensingKit)

@ktg is this still and issue?


Reset the research database on the research namespace

What does this pull request do?
The current research reset DB job fails with a cryptic message
from server for: "user_research/reset_env.yaml": \
  jobs.batch "clean-and-migrate-user-research-env" is forbidden: \
  User "system:serviceaccount:***********************:circleci" \
  cannot get resource "jobs" in API group "batch" \
  in the namespace "hmpps-interventions-research"

The research environment's CircleCI token does have these
credentials though
The default Kubernetes setup for CircleCI requires KUBE_ENV_NAMESPACE
and KUBE_ENV_TOKEN -- these were set from the application's context,
which defaults to development environment
To fix this, we need to use the research context to import the proper
KUBE_ENV_* variables
What is the intent behind these changes?
Make the "reset DB" job work :)

I'd be happier if jobs would have to explicitly pull in contexts like hmpps-interventions-dev -- then we wouldn't have defaults that don't work and not visible (CircleCI masks (*********) them out as they come from secrets)

cc @tomsmyers

Shall we completely delete the job then?

I'll open a PR to delete the job


Can I run this plugin against my custom DITA OT plugin?

I was exploring the plugins functionality and I noticed that, plugin is running against some test suites. Is it possible to run the plugin against my custom DITA OT plugin like HTML and PDF?

Thank you for sharing the details.
I am able to run the test within my html plugin. I have few clarification here.

In which scenario the test is failing? I wanted to make my test fail ex: in my html codeblock is transformed to  tag. How can I write a test case for fail scenario?
If some one extend my plugin and wrongly transforming codeblock to some other html tag, then I need to flag this in my unit test, is it possible?

This shows a canonically failed test  here. More realistically, any test that throws a fail with work. The usual way is to include a compare-output like this .  The output must exactly match the expectation.html so in the case of a codeblock being returned as <pre> rather than <pre><code> the expectation will fail and the test will error.
Usually I generated my initial expectation for a test by running ant -Dtest.copy=true and then run the test suite for regression testing.


Can the ReadMe file produce a table of instructions that match the Redisson version and the JAVA version

Can the ReadMe file produce a table of instructions that match the Redisson version and the JAVA version!

Don't need to. Redisson has been compiled with Java 8 binary compatibility since 3.0.0 version


Allow configuration blocks

like
RSpec.configure do |c|
  c.before(:suite) do
    db_clean
  end
end

It's an interesting idea. However I wonder if we could not place this kind of settings outside the framework (or at least before running tests).
A rake task might be perfect for this.

Well, there are some use cases such as https://github.com/DatabaseCleaner/database_cleaner#rspec-example or cleaning a tmp/storage dir

Yes, but we could use a rake task for this.


[FEATURE] Build examples in CI

Is your feature request related to a problem? Please describe.
The CI currently does not build the examples; however, it would be highly beneficial to verify that the examples still build even after changing stuff. This is especially relevant when changing API related things.
Describe a possible solution.
This change is rather simple. Just add the appropriate flags to the cmake script in the travis config.
Describe alternatives you've considered
Alternatively, we end up with plenty of potentially non-working examples for each PR.

Nevermind, for some reason I didn't catch that this is already implemented.


Implement S3 data storage.

Create S3 Data storage to be able to store files on S3.
The main idea is to create many file chunks 5MB each and concatenate them after upload is finished.

It's quite a challenge. For all people who want to work with S3 as a primary storage, you can use this project (https://github.com/s3fs-fuse/s3fs-fuse) to mount s3 in a directory.

Would it be more straightforward if the implementation used the volume storage as scratch space but then pushed to s3 as part of finishing the upload?

Hi @Kaelten, it took a long time, but this feature is finally coming in the next release! Currently we will only have a hybrid-s3 which works exactly as you said. The fully operating S3 storage would be implemented a little bit later.
Related PR: #108.

Hybrid-s3 storage is released in 0.6.0. S3 storage without storing files locally will come later.

For an S3 only implementation, would not be S3 Multipart upload the solution?
https://docs.aws.amazon.com/AmazonS3/latest/userguide/mpuoverview.html
(So concat should not be needed, that makes S3 for you)

Hi, @genofire. Indeed, that's exactly it. But the tricky part here is that minimum size for a chunk is 5Mb. For some systems it just don't work. That's why I implemented hybrid storage first.

Does https://docs.rs/chicon/latest/chicon/struct.S3File.html ib chicon helps?

Hi, @genofire. Yes, I guess it may work. I need to try it.
I would have no time in 1-2 weeks. If you feel that you might take this over, please do. If you don't, I'll take it as soon as I have more time.
Thank you for pointing this out.


Add summary output even for less verbose options

Some users need the Nexus2Artifactory script to run quickly without much output, but need the summary to validate the migration was successful.
The "info" log level can slow the script as it has to print each event to the log file.
The script should print out a summary to the standard output or log file even if the -v warn or -v error log level is specified.

Changed the log level of the summary to CRITICAL, so it will show up even if you set the log filter to a high level.


sidecar scopes pushes to namespace

We say a proxy depends on a Sidecar config change if the change was in the root namespace or the same namespace as the proxy. This would reduce unnecessary pushes to proxies in other namespaces that are unaffected.
[ ] Configuration Infrastructure
[ ] Docs
[ ] Installation
[X] Networking
[X] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
d922a73874b68a80217d613f25c669374b11c6f5
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
291100c24eab53fe1556fb1f912c410523742e6d
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
291100c24eab53fe1556fb1f912c410523742e6d
link
/test lint_istio

gencheck_istio
291100c24eab53fe1556fb1f912c410523742e6d
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
291100c24eab53fe1556fb1f912c410523742e6d
link
/test lint_istio

gencheck_istio
291100c24eab53fe1556fb1f912c410523742e6d
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
291100c24eab53fe1556fb1f912c410523742e6d
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

lint_istio
291100c24eab53fe1556fb1f912c410523742e6d
link
/test lint_istio

gencheck_istio
291100c24eab53fe1556fb1f912c410523742e6d
link
/test gencheck_istio

integ-telemetry-k8s-tests_istio
291100c24eab53fe1556fb1f912c410523742e6d
link
/test integ-telemetry-k8s-tests_istio

integ-mixer-k8s-tests_istio
291100c24eab53fe1556fb1f912c410523742e6d
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
291100c24eab53fe1556fb1f912c410523742e6d
link
/test integ-mixer-k8s-tests_istio

integ-telemetry-k8s-tests_istio
c8d2d15c351b056bda32b13f575fb4df5ee1ab34
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
c8d2d15c351b056bda32b13f575fb4df5ee1ab34
link
/test integ-telemetry-k8s-tests_istio

integ-mixer-k8s-tests_istio
c8d2d15c351b056bda32b13f575fb4df5ee1ab34
link
/test integ-mixer-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@stevenctl: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-mixer-k8s-tests_istio
c8d2d15c351b056bda32b13f575fb4df5ee1ab34
link
/test integ-mixer-k8s-tests_istio

integ-multicluster-k8s-tests_istio
daf237d674bf4d8a00672c3b4966756352467311
link
/test integ-multicluster-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/integ-multicluster-k8s-tests_istio

/test integ-multicluster-k8s-tests_istio

/test integ-telemetry-k8s-tests_istio

@stevenctl: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-distroless-k8s-tests_istio
daf237d674bf4d8a00672c3b4966756352467311
link
/test integ-distroless-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/test integ-distroless-k8s-tests_istio


[tinytiff] add new port

[x] Changes comply with the maintainer guide.
[x] The name of the port matches an existing name for this component on https://repology.org/ if possible, and/or is strongly associated with that component on search engines.
[x] Optional dependencies are resolved in exactly one way. For example, if the component is built with CMake, all find_package calls are REQUIRED, are satisfied by vcpkg.json's declared dependencies, or disabled with CMAKE_DISABLE_FIND_PACKAGE_Xxx.
[x] The versioning scheme in vcpkg.json matches what upstream says.
[x] The license declaration in vcpkg.json matches what upstream says.
[x] The installed as the "copyright" file matches what upstream says.
[x] The source code of the component installed comes from an authoritative source.
[x] The generated "usage text" is accurate. See adding-usage for context.
[x] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x] Only one version is in the new port's versions file.
[x] Only one version is added to each modified port's versions file.

#38778
jkriege2/TinyTIFF#29

I can make a Bugfix release!

THere you go: https://github.com/jkriege2/TinyTIFF/releases/tag/<IP_ADDRESS>

@jkriege2 Thanks!

The usage has been tested successfully on x64-windows.


⚠ DesiTorrents has degraded performance

In 918b649, DesiTorrents ($DST) experienced degraded performance:

HTTP code: 200
Response time: 1301 ms

Resolved: DesiTorrents performance has improved in 7fdba33.


Dashboard doesn't run on Mac OS X

I installed Dapr using Homebrew (see https://github.com/dapr/docs/pull/850 )
After a successful dapr init, running dapr dashboard (to run it in standalone mode) doesn't work, here is a screenshot attached:

You need to install dapr runtime first
dapr init --runtime-version 0.11.3

Closing this issue in the meantime. Please, reopen is it can still be reproduced.

i think the github api limit lead to dapr dashboard unavailable，how can i do for this？


Support k8s in spring-xsuaa

Supports kubernetes secrets in spring-xsuaa module and auto configures XsuaaServiceConfiguration based on the environment.
TODOs:

[ ] support multiple xsuaa bindings
[ ] Documentation
[ ] changelog
[x] run python tests

Hi @liga-oz i will review the PR as soon as the target branch has changed to "dev" or so...

replaced with https://github.com/SAP/cloud-security-xsuaa-integration/pull/598


Reverse Image Search functionality added

I have added @spazewalker 's commits to this PR too as I needed to make some minor changes in the scripts


grpc::GoogleDefaultCredentials() hangs

What version of gRPC and what language are you using?
gRPC version: v1.26.0-pre1
language: c++
What operating system (Linux, Windows,...) and version?
Debian Buster
What runtime / compiler are you using (e.g. python version or version of gcc)
g++ (Debian 8.3.0-6) 8.3.0
What did you do?

Run the Docker image:
$ docker run -t -i grpc-repro bash

Run the binary in the Docker container
# /home/src/creds

This program hangs indefinitely (or for a very long time).
What did you expect to see?
This program just exits immediately.
What did you see instead?
This program hangs indefinitely (or for a very long time).
Anything else we should know about your project / environment?
It doesn't happen with gRPC version v1.25.0. With v1.25.0, the same program immediately exits.
When enabling GRPC_TRACE, it displayed the following:
root@34cbc3da3f59:/# /home/src/creds
D1217 22:54:47.710033257       6 ev_posix.cc:174]            Using polling engine: epollex
D1217 22:54:47.710392245       6 dns_resolver_ares.cc:503]   Using ares dns resolver

This looks like the same issue as https://github.com/grpc/grpc/issues/21213
Please try using bazel instead

@yashykt Thanks. FWIW, the program works as expected when building gRPC with cmake.

Looks like there is nothing else to be done here. I'll be closing this issue now


Sub-elements follow element-level zoom

Preflight Checklist

[ ] I agree to follow the Code of Conduct that this project adheres to.
[ ] I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Describe the bug
Drag a diagram element into canvas, scale this element, the element has been resized, but the children element does not resize.
To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
Sub-elements follow element-level zoom
Screenshots
If applicable, add screenshots to help explain your problem.
draw.io version (In the Help->About menu of the draw.io editor):

draw.io version [e.g. 12.6.7]

Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Hi,
Could you provide us with an example screen shot, diagram file or video?
Regards,

Hi,
Could you provide us with an example screen shot, diagram file or video?
Regards,
before scale

after scale, child element has been scaled too

Hi,
Could you provide us with an example screen shot, diagram file or video?
Regards,

before scale

after scaled, child element has been scaled too

Thanks.
Tick "Resize Children" option under Property/Value when the parent shape is selected.


Render user-friendly string representation of open files

Currently, an open S3 object prints like this:
>>> f = smart_open.open('s3://…')
>>> print(f)
<smart_open.s3.SeekableBufferedInputBase object at 0x10ad02b38>

This is not useful, and we can do much better: we have full info about the concrete bucket, key, mode, etc. Compare to boto3's nice native display:
>>> print(f._object)
s3.Object(bucket_name='some-bucket', key='test/bank_form.pdf')

Task: render open objects more nicely in __str__. This is great help during logging and debugging (I consider a human-friendly str() best practice, and define them religiously on custom classes).
It seems easy enough to do for S3, but I'm not sure how much work for our other supported storages (HTTP, FTP or whatever), for consistency.

We could implement __str__ and __repr__ for our custom classes, which would solve the problem partially.
What should we do for non-custom wrapper classes? e.g.
import sys
from smart_open import open

print('str read_text: ' + str(open(sys.argv[1])))

gives
str read_text: <encodings.utf_8.StreamReader object at 0x7fa0b1c14eb8>

We don't really have control of that object. What's the best thing to do there?

I'd leave it as it is. "Falling back to built-in where possible" is a well-communicated property of smart_open.

Hi!
I'm new to OSS and am looking to contribute somewhere, mind if I give this a shot?
Just to clarify, the behavior you're looking for is to related to the __str__ and __repr__ methods of objects created with the s3://... descriptor? Which properties would you like to be shown in the representations? Just the bucket and key or additionally, some of the other, optional properties?

Closed via #359


Tree difference does not work correctly with unnormalized Unicode names

Tree difference algorithm does not handle unnormalized Unicode names correctly (Tree listing does it correctly, however). Here is how to reproduce:
git clone git://github.com/dotnet/cli /tmp/cli
go run bug.go /tmp/cli

bug.go:
package main

import (
    "os"
	"strings"

	"gopkg.in/src-d/go-git.v4"
	"gopkg.in/src-d/go-git.v4/plumbing"
	"gopkg.in/src-d/go-git.v4/plumbing/object"
)

func main() {
    r, err := git.PlainOpen(os.Args[1])
    if err != nil {
        panic(err)
    }
	c, err := r.CommitObject(plumbing.NewHash("55c59d621ea22921ecaabd99266d45a7921aab70"))
	if err != nil {
        panic(err)
    }
	t1, err := c.Tree()
	if err != nil {
        panic(err)
    }
	t1, err = t1.Tree("TestAssets/TestProjects")
	if err != nil {
        panic(err)
    }
    files := map[string]bool{}
	t1.Files().ForEach(func(f *object.File) error {
		files[f.Name] = true
		return nil
	})

	c, err = r.CommitObject(plumbing.NewHash("6fcbefa4f7a0016a68d3cda52779298a5cd20837"))
	if err != nil {
        panic(err)
    }
	t2, err := c.Tree()
	if err != nil {
        panic(err)
    }
	t2, err = t2.Tree("TestAssets/TestProjects")
	if err != nil {
        panic(err)
    }

	diff, err := object.DiffTree(t1, t2)
	for _, d := range diff {
		if strings.HasPrefix(d.To.Name, "TestAppWithUnico") &&
			strings.HasSuffix(d.To.Name, "Program.cs") {
			println(d.String())
			println(files[d.To.Name])
		}
	}
}

We see:
<Action: Insert, Path: TestAppWithUnicodéPath/Program.cs>
true

The expected output is empty.
Here is what is happening. 55c59d621ea22921ecaabd99266d45a7921aab70 and 6fcbefa4f7a0016a68d3cda52779298a5cd20837 are two consecutive commits.
cd /tmp/cli
git checkout 55c59d621ea22921ecaabd99266d45a7921aab70
echo TestAssets/TestProjects/TestAppWithUni*

git checkout 6fcbefa4f7a0016a68d3cda52779298a5cd20837
echo TestAssets/TestProjects/TestAppWithUni*

Output:
TestAssets/TestProjects/TestAppWithUnicodéPath

TestAssets/TestProjects/TestAppWithUnicodéPath TestAssets/TestProjects/TestAppWithUnicodéPath

There are two almost identical directories. One is in normalized Unicode, the other is not.

Linux doesn't normalize unicode in fs, so this means that the directories are different. git behaves different?

Yes, Cgit also treats files as different.

However:
git ls-tree 0d2105a8250ff1b9abb745a83462cc84d15f0699

040000 tree f14424931f1ec29d238c0fc12d150cd67158cae9	"TestAppWithUnicode\314\201Path"
040000 tree f14424931f1ec29d238c0fc12d150cd67158cae9	"TestAppWithUnicod\303\251Path"

This is the reason why our diff tree algorithm thinks those directories are the same - it relies on Git hashes.

Tagging @alcortesm to let him know

Because the directory names are precomposed as @jfontan found: https://sourcegraph.com/github.com/git/git@d62dad7/-/blob/compat/precompose_utf8.c#L113:25

Interesting observation: the original tree diff algorithm checks directory names first, and then proceeds to checking the hashes: https://github.com/git/git/blob/master/tree-diff.c#L483

Removing the normalization from https://github.com/src-d/go-git/blob/master/utils/merkletrie/noder/path.go#L83 resolves the original issue. I am going to prepare the PR with tests.


CI: Determine and set K8s version in GKE pipeline

This change is

test-gke K8sDemosTest*

test-gke K8sDemosTest*

test-gke K8sDemosTest*

test-gke K8sDemosTest*

test-gke K8sDemosTest*

test-gke K8sDemosTest*

Coverage remained the same at 44.778% when pulling fe5a7ac52918763f347b5e6b91ace50f0b42f096 on raybejjani:gke-set-k8s-version into de7e8857e35bf2c8f296ee92995d6fedb8f1fcc4 on cilium:master.

test-gke K8sDemosTest*

test-gke K8sDemosTest*

test-gke K8sDemosTest*

test-gke K8sDemosTest*

test-gke K8sDemosTest*

test-gke K8sDemosTest*

test-gke K8sDemosTest*

test-gke K8sServicesTest External services To Services first endpoint creation match service by labels*


Add missing public properties to BoundingBoxRig

Overview
Currently BoundingBoxRig missing several public properties for private SerializedField fields.
This cause user could not modify component when dynamically add component from Script. This commit open these parameters modifiable.

@guitarrapc, thanks for the contribution!


dask.config.set not working as described in docs

What happened:

What you expected to happen:

Minimal Complete Verifiable Example:
dask.config.set({'scheduler.work-stealing': False})

Environment:

Dask version:  - dask=2021.3.0=pyhd8ed1ab_0, dask-core=2021.3.0=pyhd8ed1ab_0
Python version: 3.8.8
Operating System: OS X 11.2.1
Install method (conda, pip, source): conda

Thanks for raising an issue @kpasko. Unfortunately I'm not able to reproduce using the conda packages you specified (i.e. in a fresh environment created with conda create -n test python=3.8.8 dask=2021.3.0=pyhd8ed1ab_0 dask-core=2021.3.0=pyhd8ed1ab_0) or the latest main branch. In both cases I get:
>>> import dask
>>> dask.__version__
'2021.03.0'
>>> dask.config.set({'scheduler.work-stealing': False})
<dask.config.set object at 0x7fc9a8c09310>

Could you confirm the version of Dask being used in your Jupyter session with dask.__version__?

can confirm it was '2021.03.0' within the kernel that was erroring. tried in a fresh kernel however, also returning '2021.03.0' and it seemed to no longer be an issue, so going to assume it was some minor conda-forge version update/mismatch on my end -- closing.


Private Browsing in Firefox not working

We have a flutter app with flutter_secure_storage.
When running the web version in a private firefox window, it does not work. In a normal window it works fine.
Is this a limit of flutter_secure_storage? Are there any settings we can change to make it work? (in the app, in firefox, ..)

I am closing all older issues. If this issue still exists in the latest version, please let me know.


fix: use polyfilled Promise

Codecov Report

Merging #496 into master will increase coverage by 0.02%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           master     #496      +/-   ##
==========================================
+ Coverage   66.98%   67.01%   +0.02%
==========================================
  Files          36       36
  Lines        2902     2904       +2
==========================================
+ Hits         1944     1946       +2
  Misses        958      958

Impacted Files
Coverage Δ

src/utils/index.js
94.87% <100%> (+0.06%)
:arrow_up:

src/cloudfunction.js
35.48% <100%> (+2.15%)
: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 a7a0d37...91acc27. Read the comment docs.


added sanity check in case theme.features is not defined

I keep deleting the theme.features in mkdocs.yml and then the build breaks when building all the examples. It does not show when building an example on its own, which I guess is a bad idea, although faster. I assume there is no requirement to have theme.features defined, so I added a sanity check.

Jup, we definitely need the check – didn't run into this problem yet because I always used features.


IE9 Fallback

Fix the ie9 fallback css, or add additional/optional bundle

closing as this is no longer a priority


ext: mcux: Update imx rt clock drivers

Updates all imx rt clock drivers to fix building C++ with Zephyr SDK
0.10.0-rc3 (GCC 8.2)
Signed-off-by: Maureen Helm<EMAIL_ADDRESS>Partial fix for #13272

Codecov Report

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

@@           Coverage Diff           @@
##           master   #13643   +/-   ##
=======================================
  Coverage   52.41%   52.41%
=======================================
  Files         322      322
  Lines       46596    46596
  Branches    10772    10772
=======================================
  Hits        24422    24422
  Misses      17267    17267
  Partials     4907     4907

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 edb01e2...53721b2. Read the comment docs.


[FEATURE REQ] Set, or support setting, App Insights session ID and user ID via otel exporter

Library name
Azure.Monitor.OpenTelemetry.Exporter 1.2.0
Please describe the feature.
The Microsoft.ApplicationInsights.AspNetCore library automatically writes session_Id and user_Id and authUserId values for requests, dependencies, and traces/logging based on the ai_session and ai_user cookies. These values are completely missing from the Azure.Monitor.OpenTelemetry.Exporter output, even though there are placeholder keys in ContextTagKeys. This could be considered a bug, or just a missing feature.
This is pretty critical functionality because it allows one to correlate all activity with a user session and a unique user (well, at least all telemetry in the async context, but not cross-process telemetry). Since the Exporter logic is internal and there are no extension points to modify the telemetry, there is no way to set this column.
The corresponding telemetry initializer in app insights classic are:

Microsoft.ApplicationInsights.AspNetCore/TelemetryInitializers/WebSessionTelemetryInitializer.cs
Microsoft.ApplicationInsights.AspNetCore/TelemetryInitializers/WebUserTelemetryInitializer.cs

The workaround I have right now sets these Activity tags and LogRecord attributes using the cookie value, but I have to use custom properties because there's no way to set the root properties; which means the app insights web UI to show all telemetry for a user or user session doesn't work.
One opportunity we have here is to use the Baggage API to flow the userId and sessionId to downstream + out of process activities, which is a significant improvement from app insights classic.

Here's what I have now - it gets me most of the way to the functionality that I want, but I would like to be able to populate the "standard" fields so the app insights web UI works as expected.
I'm using request enrichment to set values based on the request; and then Baggage and Processors to add the values to downstream activities and log records.
/// <summary>
/// Initializes request telemetry, and sets baggage, to log and propagate the app insights sessionId
/// and userId values to downstream operations.
/// </summary>
internal sealed class AppInsightsIdsRequestTelemetryInitializer : IEnrichRequestTelemetry
{

    private const string c_aiSessionCookieKey = "ai_session";

    private const string c_aiUserCookieKey = "ai_user";

    public void Enrich(Activity activity, HttpRequest request)
    {
        if (TryGetAppInsightsIdFromCookie(request, c_aiSessionCookieKey, out var sessionId))
        {
            activity.AddTag(OtelKey.AiSessionIdValue, sessionId);

            // Use otel Baggage to the AI sessionID propagates to downstream processes
            Baggage.SetBaggage(OtelKey.AiSessionIdValue, sessionId);
        }

        // AI user ID is _not_ our user id
        if (TryGetAppInsightsIdFromCookie(request, c_aiUserCookieKey, out var aiUserId))
        {
            activity.AddTag(OtelKey.AiUserIdValue, aiUserId);

            // Propagate downstream
            Baggage.SetBaggage(OtelKey.AiUserIdValue, aiUserId);
        }
    }

    private static bool TryGetAppInsightsIdFromCookie(HttpRequest request, string cookieKey, [NotNullWhen(true)] out string? value)
    {
        if (request.Cookies.TryGetValue(cookieKey, out var cookieValue))
        {
            if (! string.IsNullOrEmpty(cookieValue))
            {
                var cookieParts = ((string) cookieValue).Split('|');
                if (cookieParts.Length >= 1)
                {
                    value = cookieParts[0];
                    return true;
                }
            }
        }

        value = null;
        return false;
    }

}

/// <summary>
/// Adds tags to activity that are stored in request baggage.
/// </summary>
/// <remarks>
/// The objective here is to duplicate key tags in all downstream activities, eg
/// app insights session.id and user.id are useful in the whole downstream tree.
/// </remarks>
internal sealed class AddRequestBaggageActivityProcessor : BaseProcessor<Activity>
{

    public override void OnStart(Activity activity)
    {
        if (activity.IsAllDataRequested)
        {
            foreach (var kvp in Baggage.GetBaggage())
            {
                // We only expect "ai.*" telemetry in Baggage, so only copy those into tags
                if (kvp.Key.StartsWith("ai."))
                {
                    activity.SetTag(kvp.Key, kvp.Value);
                }
            }
        }
    }

}

/// <summary>
/// Adds tags to log records that are stored in request activity baggage.
/// </summary>
internal sealed class AddRequestBaggageLogRecordProcessor : BaseProcessor<LogRecord>
{

    public override void OnStart(LogRecord logRecord)
    {
        foreach (var kvp in Baggage.GetBaggage())
        {
            // We only expect "ai.*" telemetry in Baggage, so only copy those into tags
            if (kvp.Key.StartsWith("ai."))
            {
                logRecord.Attributes.Append(new(kvp.Key, kvp.Value));
            }
        }
    }

}

Related to the above; slight correction in my bug report/feature request: user_AuthenticatedId does work as expected, at least for Activity logging. When I add a tag to an activity with key "enduser.id", the user_AuthenticatedId is populated as expected on the request row.
As of right now I cannot confirm whether user_AuthenticatedId can be populated on dependencies or traces.

I'm consolidating all issues regarding overriding specific fields in the Application Insights schema into another issue to help with tracking. https://github.com/Azure/azure-sdk-for-net/issues/46021

I think this should be re-opened. #46021 is related, but this issue is mainly about making it work automatically, for consistency with AI classic. Or having configuration to turn it on.

@TimothyMothra can you please reopen this?
It looks like setting the opentelemetry tag enduser.id indeed sets the top-level user_AuthenticatedId, but it does not fully work as expected:

it does not set user_Id resulting in the All users bar chart to be filled with the value 1. The below chart should have a higher value at the end of the timeline:

only when manually choosing Authenticated users from the dropdown, it works:

enduser.id is deprecated and is recommended to be replaced by user.id


very funny stuff (read desc btw)

RISKY CHANGES:
launch tracker has been removed (coz its really inefficient + why would u want it?)
.idea directory has been deleted since well... u can just create it yourself when setting up workspace
ig those are the only "risky" changes ive made

@Overwrite @K-ov who taught these guys mixins wtf

@Overwrite @K-ov who taught these guys mixins wtf

uhhh just rewrite it if u dont like it

@Overwrite @K-ov who taught these guys mixins wtf

also tell me a better way of executing EventJump in a better way ill wait

an injection at TAIL...

an injection at TAIL...

how are u gonna do float funny = e.getYaw() * 0.017453292F; if u inject it??????

by returning the motions to their original values and doing it again... it's really not that complicated...

aaaaaaaaaaa whatever rewrite that mixin if u want

i'll rewrite it after/if this is merged

alr cool

First of all the WTap wont work you moved a lot of stuff to a visuals category and added AutoBlock to KA when it is a seperate module

First of all the WTap wont work you moved a lot of stuff to a visuals category and added AutoBlock to KA when it is a seperate module

i did not test w tap
idk why i moved modules around tbh
the separate autoblock does not even function properly

test the code before you make a pull request

test the code before you make a pull request

ok


Use VSCode fs API's in extension

This will close #1670.
I've replaced the CargoWatchers Cargo.toml check with a version that uses the fs API of vscode.
While making this I've identified an issue with the detection of the cargo.toml, we can only load projects where the cargo.toml is in the root of the workspace. but that's a separate issue 😄

Awesome. Do we need to bump the minimum vscode version for this?

Yup, it needs to be bumped to 1.37. I'll commit that tomorrow

bors r+
Thanks!


Add limit parameter to get items in the Application area

https://github.com/podio/podio-py/blob/master/pypodio2/areas.py#L229-230
I think it would be useful to allow for the limit parameter when trying to get all of the items from an app in Podio. That way we can increase the limit when OAuthAppClient is used.

Is available in **kwargs as limit=n paratemer. My bad.


Upload to crates

I see you have this in TODO, but filing an issue so that github can notify me when this happens.
Also, there's some namesquatting already happens: https://crates.io/crates/grpc-rust :)

No problem.
Actually, I also did namesquatting: https://crates.io/crates/grpc :)
Currently

grpc-rust has too many bugs
some important features are not implemented
futures-rs and tokio-core were uploaded to crates just yesterday

Please let me know if you need grpc-rust uploaded to crates even if is not ready yet. Note: you can always use grpc-rust right from git:
[dependencies]
grpc = { git = "http://github.com/stepancheg/grpc-rust" }

It's your decision whether to upload it now or not. I just want to be notified via this issue when I could replace git = in my [dependencies] :)
Personally I'd say it's good enough for upload, since it seems to be somewhat functional and it may be a good way to increase visibility and draw more contributors here.

Uploaded to crates: grpc and grpc-compiler.
It does not mean grpc-rust is ready for production.


[bug]: Paste using system clipboard

while Yank to system clipboard works using, set clipboard=unnamed, but paste not

You are perfectly right, somehow it didn't cross my mind to also implement the paste side :laughing: :man_facepalming:

could you spend sometime to fix it?

Yes, I'll do that once I get to spend some time on the plugin.

thx! when I have time, I will try to learn typescript and write obsidian plugin as well

Should be fixed now, please update to the latest version (0.2.1) and let me know if it works as expected.

Plugin ID mismatch when I try to update

Sorry, fixed now.

solved！thx！


[DO NOT MERGE] Use LGSL 107 instead of 230

We currently use LGSL 230 to refer to sheltered housing, however this is from the Scottish list and is not supported in England and Wales.  107 seems like a better bet for us, also because it refers to sheltered housing more generally, as opposed to just for older people.
As a first step, we'll add 107 as an enabled service.
There is other work that needs to be done as part of this, and this is coordinated via this Trello card.  Once that work is done, we can retire 230.

Is it safe to remove 230 at the same time as adding 107? or do we need to add 107, switch the local transaction over to use it, and then remove 230 afterwards?

Yep, agree with you as discussed.  I'll remove the LGSL 230 entry in a subsequent PR when we're ready

👍


Don't leave stale errors on queue if DSO_dsobyaddr() fails

The init code uses DSO_dsobyaddr() to leak a reference to ourselves to
ensure we remain loaded until atexit() time. In some circumstances that
can fail and leave stale errors on the error queue.
Fixes #3372

Pushed. Thanks.


refactor(Topology/Order/ScottTopology): Unify concepts of Scott Topology

Unify Scott Topologies, following on from #13201 and #16826.
Originally Mathlib had a notion of ω-Scott Continuity and ω-Scott Topology based on Chains for ω-complete partial orders. Previously we introduced a notion of Scott Continuity and Scott Topology based on directed sets for arbitrary pre-orders (#2508). In #13201 we we generalised our definition of Scott Continuity to include ω-Scott Continuity as a special case. This PR continues that work by generalising our notion of Scott Topology to include ω-Scott Topology as a special case.

@YaelDillies please could you review this PR? Thank you.

bors merge


feat: Update pools.ts Gnosis Chain

Description
Added 50 sDAI - 50 WXDAI to Gnosis Chain
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Dependency changes
[ ] Code refactor / cleanup
[ ] Documentation or wording changes
[ ] Other

@Luigy-Lemon The pool requires initial liquidity for being allowlisted.


Fix double counting appointments

If a student was at max capacity (number of appointments per day or week), they would not be able to edit the descriptions of their appointments.

Fixed with https://github.com/Cal-CS-61A-Staff/oh-queue/commit/4c0acba133ec438abcbb732dcbeb285069fbbb85


Allow running deployer from any path

Previously, the deployer could only be run if the current working directory of the running it is the root of the repository. This commit removes that dependency, and allows the deployer to be called from any working directory.

@GeorgianaElena @sgibson91 so the output of get_all_cluster_yaml_files was always used in our code only to iterate, never for set operations. However, to make the overall change in this PR smaller, I've made it return a set again so the only code change here is to get rid of the os.getcwd() calls and not make any other changes. I hope that makes it easier to review too!

Thanks a lot for your review, @sgibson91 and @GeorgianaElena!

I think I hit a bug with this implementation when I accidentally tried to run the deployer from the terraform/aws folder


fix doc rendering issue

this is with reference to https://github.com/fastai/nbdev/issues/1317

That's amazing Deven!
Thanks a lot, you didn't have to go through the trouble


Not valid Cpython files cause crashes in crates/ruff_source_file/src/line_index.rs:115:28

Ruff 0.1.11 - latest version from git
When trying to catch https://github.com/astral-sh/ruff/issues/9398 I found that ruff parses a lot of more files than cpython so it is possible that users will try to fix file with invalid syntax(not sure why, but currently I don't see similar crashes with valid files)
ruff --select ALL . --fix

error: Panicked while linting 130_IDX_0_RAND_6616489086532482962272.py: This indicates a bug in Ruff. If you could open an issue at:

    https://github.com/astral-sh/ruff/issues/new?title=%5BLinter%20panic%5D

...with the relevant file contents, the `pyproject.toml` settings, and the following stack trace, we'd be very appreciative!

panicked at crates/ruff_source_file/src/line_index.rs:115:28:
byte index 30 is out of bounds of `GUILLOTINE_PICS = [r"""
Ô|`
Backtrace:    0: ruff_cli::panic::catch_unwind::{{closure}}
   1: <alloc::boxed::Box<F,A> as core::ops::function::Fn<Args>>::call
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/alloc/src/boxed.rs:2021:9
   2: std::panicking::rust_panic_with_hook
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:783:13
   3: std::panicking::begin_panic_handler::{{closure}}
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:657:13
   4: std::sys_common::backtrace::__rust_end_short_backtrace
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/sys_common/backtrace.rs:170:18
   5: rust_begin_unwind
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/panicking.rs:645:5
   6: core::panicking::panic_fmt
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/panicking.rs:72:14
   7: core::str::slice_error_fail_rt
   8: core::str::slice_error_fail
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/core/src/str/mod.rs:88:9
   9: ruff_source_file::line_index::LineIndex::source_location
  10: ruff_linter::logging::DisplayParseError::from_source_code
  11: ruff_linter::logging::DisplayParseError::from_source_kind
  12: ruff_cli::diagnostics::lint_path
  13: ruff_cli::panic::catch_unwind
  14: ruff_cli::commands::check::lint_path
  15: rayon::iter::plumbing::Producer::fold_with
  16: rayon::iter::plumbing::bridge_producer_consumer::helper
  17: rayon_core::join::join_context::{{closure}}
  18: rayon::iter::plumbing::bridge_producer_consumer::helper
  19: rayon_core::job::StackJob<L,F,R>::run_inline
  20: rayon_core::join::join_context::{{closure}}
  21: rayon::iter::plumbing::bridge_producer_consumer::helper
  22: rayon_core::join::join_context::{{closure}}
  23: rayon::iter::plumbing::bridge_producer_consumer::helper
  24: rayon_core::job::StackJob<L,F,R>::run_inline
  25: rayon_core::join::join_context::{{closure}}
  26: rayon::iter::plumbing::bridge_producer_consumer::helper
  27: rayon_core::join::join_context::{{closure}}
  28: rayon::iter::plumbing::bridge_producer_consumer::helper
  29: <rayon_core::job::StackJob<L,F,R> as rayon_core::job::Job>::execute
  30: rayon_core::registry::WorkerThread::wait_until_cold
  31: rayon_core::registry::ThreadBuilder::run
  32: std::sys_common::backtrace::__rust_begin_short_backtrace
  33: core::ops::function::FnOnce::call_once{{vtable.shim}}
  34: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/alloc/src/boxed.rs:2007:9
  35: <alloc::boxed::Box<F,A> as core::ops::function::FnOnce<Args>>::call_once
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/alloc/src/boxed.rs:2007:9
  36: std::sys::unix::thread::Thread::new::thread_start
             at /rustc/82e1608dfa6e0b5569232559e3d385fea5a93112/library/std/src/sys/unix/thread.rs:108:17
  37: start_thread
             at ./nptl/pthread_create.c:444:8
  38: __GI___clone3
             at ./misc/../sysdeps/unix/sysv/linux/x86_64/clone3.S:78

3800 files with problems -
NOT_PARSABLE.zip

Awesome, thanks for reproducing!

It looks like when we hit an EOF error, the location can be one-past-the-end (since that's the location of the cursor when lexing).

Oohhh, I see the problem here. It's slightly different. We're using the "original" code when computing the display range for the "fixed" code (both of which contain syntax errors).


Confirm before leaving post page with content

http://www.elkarte.net/community/index.php?topic=2566

@Spuds 1.0.5?

Yup (or 1.1)

Let's start with 1.0.5. :angel:

I guess it's time for 1.1. lol