error after bulding enviroment - catkin_make

Im using Ubuntu 18.04.6 LTS. Melodic ROS, acording to readme after catkin_make, i get answer:
`Base path: /home/macko-pc/catkin_ws
Source space: /home/macko-pc/catkin_ws/src
Build space: /home/macko-pc/catkin_ws/build
Devel space: /home/macko-pc/catkin_ws/devel
Install space: /home/macko-pc/catkin_ws/install
Creating symlink "/home/macko-pc/catkin_ws/src/CMakeLists.txt" pointing to "/opt/ros/melodic/share/catkin/cmake/toplevel.cmake"

Running command: "cmake /home/macko-pc/catkin_ws/src -DCATKIN_DEVEL_PREFIX=/home/macko-pc/catkin_ws/devel -DCMAKE_INSTALL_PREFIX=/home/macko-pc/catkin_ws/install -G Unix Makefiles" in "/home/macko-pc/catkin_ws/build"

-- The C compiler identification is GNU 7.5.0
-- The CXX compiler identification is GNU 7.5.0
-- Check for working C compiler: /usr/bin/cc
-- Check for working C compiler: /usr/bin/cc -- works
-- Detecting C compiler ABI info
-- Detecting C compiler ABI info - done
-- Detecting C compile features
-- Detecting C compile features - done
-- Check for working CXX compiler: /usr/bin/c++
-- Check for working CXX compiler: /usr/bin/c++ -- works
-- Detecting CXX compiler ABI info
-- Detecting CXX compiler ABI info - done
-- Detecting CXX compile features
-- Detecting CXX compile features - done
-- Using CATKIN_DEVEL_PREFIX: /home/macko-pc/catkin_ws/devel
-- Using CMAKE_PREFIX_PATH: /opt/ros/melodic
-- This workspace overlays: /opt/ros/melodic
-- Found PythonInterp: /usr/bin/python2 (found suitable version "2.7.17", minimum required is "2")
-- Using PYTHON_EXECUTABLE: /usr/bin/python2
-- Using Debian Python package layout
-- Using empy: /usr/bin/empy
-- Using CATKIN_ENABLE_TESTING: ON
-- Call enable_testing()
-- Using CATKIN_TEST_RESULTS_DIR: /home/macko-pc/catkin_ws/build/test_results
-- Found gtest sources under '/usr/src/googletest': gtests will be built
-- Found gmock sources under '/usr/src/googletest': gmock will be built
-- Found PythonInterp: /usr/bin/python2 (found version "2.7.17")
-- Looking for pthread.h
-- Looking for pthread.h - found
-- Looking for pthread_create
-- Looking for pthread_create - not found
-- Looking for pthread_create in pthreads
-- Looking for pthread_create in pthreads - not found
-- Looking for pthread_create in pthread
-- Looking for pthread_create in pthread - found
-- Found Threads: TRUE
-- Using Python nosetests: /usr/bin/nosetests-2.7
-- catkin 0.7.29
-- BUILD_SHARED_LIBS is on
-- BUILD_SHARED_LIBS is on
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- ~~  traversing 1 packages in topological order:
-- ~~  - lio_sam
-- ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-- +++ processing catkin package: 'lio_sam'
-- ==> add_subdirectory(LIO-SAM)
-- Using these message generators: gencpp;geneus;genlisp;gennodejs;genpy
-- Found OpenMP_C: -fopenmp (found version "4.5")
-- Found OpenMP_CXX: -fopenmp (found version "4.5")
-- Found OpenMP: TRUE (found version "4.5")
-- Checking for module 'eigen3'
--   Found eigen3, version 3.3.4
-- Found eigen: /usr/include/eigen3
-- Checking for module 'libopenni'
--   Found libopenni, version <IP_ADDRESS>
-- Found openni: /usr/lib/libOpenNI.so
-- The imported target "vtkRenderingPythonTkWidgets" references the file
"/usr/lib/x86_64-linux-gnu/libvtkRenderingPythonTkWidgets.so"
but this file does not exist.  Possible reasons include:

The file was deleted, renamed, or moved to another location.
An install or uninstall procedure did not complete successfully.
The installation package was faulty and contained
"/usr/lib/cmake/vtk-6.3/VTKTargets.cmake"
but not all the files it references.

-- The imported target "vtk" references the file
"/usr/bin/vtk"
but this file does not exist.  Possible reasons include:

The file was deleted, renamed, or moved to another location.
An install or uninstall procedure did not complete successfully.
The installation package was faulty and contained
"/usr/lib/cmake/vtk-6.3/VTKTargets.cmake"
but not all the files it references.

-- Found libusb-1.0: /usr/include
-- Checking for module 'flann'
--   Found flann, version 1.9.1
-- Found Flann: /usr/lib/x86_64-linux-gnu/libflann_cpp_s.a
-- Found qhull: /usr/lib/x86_64-linux-gnu/libqhull.so
-- Found PCL_COMMON: /usr/lib/x86_64-linux-gnu/libpcl_common.so
-- Found PCL_OCTREE: /usr/lib/x86_64-linux-gnu/libpcl_octree.so
-- Found PCL_IO: /usr/lib/x86_64-linux-gnu/libpcl_io.so
-- Found PCL_KDTREE: /usr/lib/x86_64-linux-gnu/libpcl_kdtree.so
-- Found PCL_SEARCH: /usr/lib/x86_64-linux-gnu/libpcl_search.so
-- Found PCL_SAMPLE_CONSENSUS: /usr/lib/x86_64-linux-gnu/libpcl_sample_consensus.so
-- Found PCL_FILTERS: /usr/lib/x86_64-linux-gnu/libpcl_filters.so
-- Found PCL_2D: /usr/include/pcl-1.8
-- Found PCL_GEOMETRY: /usr/include/pcl-1.8
-- Found PCL_FEATURES: /usr/lib/x86_64-linux-gnu/libpcl_features.so
-- Found PCL_ML: /usr/lib/x86_64-linux-gnu/libpcl_ml.so
-- Found PCL_SEGMENTATION: /usr/lib/x86_64-linux-gnu/libpcl_segmentation.so
-- Found PCL_VISUALIZATION: /usr/lib/x86_64-linux-gnu/libpcl_visualization.so
-- Found PCL_SURFACE: /usr/lib/x86_64-linux-gnu/libpcl_surface.so
-- Found PCL_REGISTRATION: /usr/lib/x86_64-linux-gnu/libpcl_registration.so
-- Found PCL_KEYPOINTS: /usr/lib/x86_64-linux-gnu/libpcl_keypoints.so
-- Found PCL_TRACKING: /usr/lib/x86_64-linux-gnu/libpcl_tracking.so
-- Found PCL_RECOGNITION: /usr/lib/x86_64-linux-gnu/libpcl_recognition.so
-- Found PCL_STEREO: /usr/lib/x86_64-linux-gnu/libpcl_stereo.so
-- Found PCL_APPS: /usr/lib/x86_64-linux-gnu/libpcl_apps.so
-- Found PCL_IN_HAND_SCANNER: /usr/include/pcl-1.8
-- Found PCL_MODELER: /usr/include/pcl-1.8
-- Found PCL_POINT_CLOUD_EDITOR: /usr/include/pcl-1.8
-- Found PCL_OUTOFCORE: /usr/lib/x86_64-linux-gnu/libpcl_outofcore.so
-- Found PCL_PEOPLE: /usr/lib/x86_64-linux-gnu/libpcl_people.so
-- GTSAM include directory:  /usr/lib/cmake/GTSAM/../../../include
-- lio_sam: 1 messages, 1 services
CMake Warning at /opt/ros/melodic/share/catkin/cmake/catkin_package.cmake:166 (message):
catkin_package() DEPENDS on 'GTSAM' but neither 'GTSAM_INCLUDE_DIRS' nor
'GTSAM_LIBRARIES' is defined.
Call Stack (most recent call first):
/opt/ros/melodic/share/catkin/cmake/catkin_package.cmake:102 (_catkin_package)
LIO-SAM/CMakeLists.txt:49 (catkin_package)
-- Configuring done
CMake Warning (dev) at LIO-SAM/CMakeLists.txt:95 (add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.
Target "lio_sam_mapOptmization" links to target "Boost::timer" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
This warning is for project developers.  Use -Wno-dev to suppress it.
CMake Warning (dev) at LIO-SAM/CMakeLists.txt:101 (add_executable):
Policy CMP0028 is not set: Double colon in target name means ALIAS or
IMPORTED target.  Run "cmake --help-policy CMP0028" for policy details.
Use the cmake_policy command to set the policy and suppress this warning.
Target "lio_sam_imuPreintegration" links to target "Boost::timer" but the
target was not found.  Perhaps a find_package() call is missing for an
IMPORTED target, or an ALIAS target is missing?
This warning is for project developers.  Use -Wno-dev to suppress it.
-- Generating done
-- Build files have been written to: /home/macko-pc/catkin_ws/build

Running command: "make -j4 -l4" in "/home/macko-pc/catkin_ws/build"

Scanning dependencies of target nav_msgs_generate_messages_eus
Scanning dependencies of target geometry_msgs_generate_messages_eus
Scanning dependencies of target std_msgs_generate_messages_eus
Scanning dependencies of target _lio_sam_generate_messages_check_deps_cloud_info
[  0%] Built target std_msgs_generate_messages_eus
[  0%] Built target nav_msgs_generate_messages_eus
[  0%] Built target geometry_msgs_generate_messages_eus
Scanning dependencies of target sensor_msgs_generate_messages_eus
Scanning dependencies of target nav_msgs_generate_messages_lisp
Scanning dependencies of target _lio_sam_generate_messages_check_deps_save_map
[  0%] Built target sensor_msgs_generate_messages_eus
[  0%] Built target nav_msgs_generate_messages_lisp
[  0%] Built target _lio_sam_generate_messages_check_deps_cloud_info
Scanning dependencies of target geometry_msgs_generate_messages_lisp
Scanning dependencies of target std_msgs_generate_messages_lisp
Scanning dependencies of target sensor_msgs_generate_messages_lisp
[  0%] Built target geometry_msgs_generate_messages_lisp
[  0%] Built target std_msgs_generate_messages_lisp
[  0%] Built target sensor_msgs_generate_messages_lisp
[  0%] Built target _lio_sam_generate_messages_check_deps_save_map
Scanning dependencies of target nav_msgs_generate_messages_cpp
Scanning dependencies of target geometry_msgs_generate_messages_cpp
Scanning dependencies of target std_msgs_generate_messages_cpp
[  0%] Built target nav_msgs_generate_messages_cpp
Scanning dependencies of target sensor_msgs_generate_messages_cpp
[  0%] Built target std_msgs_generate_messages_cpp
[  0%] Built target geometry_msgs_generate_messages_cpp
Scanning dependencies of target nav_msgs_generate_messages_nodejs
[  0%] Built target sensor_msgs_generate_messages_cpp
Scanning dependencies of target geometry_msgs_generate_messages_nodejs
Scanning dependencies of target sensor_msgs_generate_messages_nodejs
[  0%] Built target nav_msgs_generate_messages_nodejs
Scanning dependencies of target std_msgs_generate_messages_nodejs
[  0%] Built target sensor_msgs_generate_messages_nodejs
Scanning dependencies of target nav_msgs_generate_messages_py
[  0%] Built target geometry_msgs_generate_messages_nodejs
[  0%] Built target std_msgs_generate_messages_nodejs
Scanning dependencies of target sensor_msgs_generate_messages_py
[  0%] Built target nav_msgs_generate_messages_py
Scanning dependencies of target geometry_msgs_generate_messages_py
Scanning dependencies of target std_msgs_generate_messages_py
[  0%] Built target sensor_msgs_generate_messages_py
[  0%] Built target geometry_msgs_generate_messages_py
Scanning dependencies of target tf2_msgs_generate_messages_nodejs
[  0%] Built target std_msgs_generate_messages_py
Scanning dependencies of target tf_generate_messages_py
[  0%] Built target tf2_msgs_generate_messages_nodejs
Scanning dependencies of target actionlib_generate_messages_cpp
[  0%] Built target tf_generate_messages_py
Scanning dependencies of target roscpp_generate_messages_cpp
Scanning dependencies of target rosgraph_msgs_generate_messages_cpp
[  0%] Built target actionlib_generate_messages_cpp
Scanning dependencies of target tf_generate_messages_nodejs
[  0%] Built target roscpp_generate_messages_cpp
[  0%] Built target rosgraph_msgs_generate_messages_cpp
Scanning dependencies of target actionlib_generate_messages_lisp
[  0%] Built target tf_generate_messages_nodejs
Scanning dependencies of target rosgraph_msgs_generate_messages_eus
Scanning dependencies of target actionlib_msgs_generate_messages_cpp
Scanning dependencies of target tf_generate_messages_eus
[  0%] Built target actionlib_generate_messages_lisp
[  0%] Built target rosgraph_msgs_generate_messages_eus
[  0%] Built target actionlib_msgs_generate_messages_cpp
[  0%] Built target tf_generate_messages_eus
Scanning dependencies of target rosgraph_msgs_generate_messages_nodejs
Scanning dependencies of target roscpp_generate_messages_lisp
Scanning dependencies of target tf_generate_messages_lisp
Scanning dependencies of target roscpp_generate_messages_py
[  0%] Built target tf_generate_messages_lisp
[  0%] Built target rosgraph_msgs_generate_messages_nodejs
[  0%] Built target roscpp_generate_messages_lisp
[  0%] Built target roscpp_generate_messages_py
Scanning dependencies of target visualization_msgs_generate_messages_nodejs
Scanning dependencies of target visualization_msgs_generate_messages_lisp
Scanning dependencies of target _catkin_empty_exported_target
Scanning dependencies of target roscpp_generate_messages_nodejs
[  0%] Built target visualization_msgs_generate_messages_lisp
[  0%] Built target visualization_msgs_generate_messages_nodejs
[  0%] Built target roscpp_generate_messages_nodejs
[  0%] Built target _catkin_empty_exported_target
Scanning dependencies of target roscpp_generate_messages_eus
Scanning dependencies of target rosgraph_msgs_generate_messages_py
Scanning dependencies of target actionlib_msgs_generate_messages_eus
Scanning dependencies of target actionlib_msgs_generate_messages_lisp
[  0%] Built target roscpp_generate_messages_eus
[  0%] Built target actionlib_msgs_generate_messages_eus
[  0%] Built target rosgraph_msgs_generate_messages_py
[  0%] Built target actionlib_msgs_generate_messages_lisp
Scanning dependencies of target actionlib_msgs_generate_messages_py
Scanning dependencies of target actionlib_msgs_generate_messages_nodejs
Scanning dependencies of target tf2_msgs_generate_messages_cpp
Scanning dependencies of target actionlib_generate_messages_py
[  0%] Built target actionlib_msgs_generate_messages_py
[  0%] Built target actionlib_msgs_generate_messages_nodejs
[  0%] Built target tf2_msgs_generate_messages_cpp
[  0%] Built target actionlib_generate_messages_py
Scanning dependencies of target tf2_msgs_generate_messages_py
Scanning dependencies of target pcl_msgs_generate_messages_cpp
Scanning dependencies of target pcl_msgs_generate_messages_eus
Scanning dependencies of target actionlib_generate_messages_nodejs
[  0%] Built target tf2_msgs_generate_messages_py
[  0%] Built target pcl_msgs_generate_messages_cpp
[  0%] Built target pcl_msgs_generate_messages_eus
[  0%] Built target actionlib_generate_messages_nodejs
Scanning dependencies of target tf_generate_messages_cpp
Scanning dependencies of target pcl_msgs_generate_messages_lisp
Scanning dependencies of target actionlib_generate_messages_eus
Scanning dependencies of target pcl_msgs_generate_messages_py
[  0%] Built target pcl_msgs_generate_messages_lisp
[  0%] Built target tf_generate_messages_cpp
[  0%] Built target actionlib_generate_messages_eus
[  0%] Built target pcl_msgs_generate_messages_py
Scanning dependencies of target tf2_msgs_generate_messages_lisp
Scanning dependencies of target pcl_msgs_generate_messages_nodejs
Scanning dependencies of target tf2_msgs_generate_messages_eus
Scanning dependencies of target visualization_msgs_generate_messages_cpp
[  0%] Built target tf2_msgs_generate_messages_lisp
[  0%] Built target pcl_msgs_generate_messages_nodejs
[  0%] Built target tf2_msgs_generate_messages_eus
[  0%] Built target visualization_msgs_generate_messages_cpp
Scanning dependencies of target visualization_msgs_generate_messages_eus
Scanning dependencies of target visualization_msgs_generate_messages_py
Scanning dependencies of target rosgraph_msgs_generate_messages_lisp
Scanning dependencies of target lio_sam_imuPreintegration
[  0%] Built target visualization_msgs_generate_messages_eus
[  0%] Built target visualization_msgs_generate_messages_py
[  0%] Built target rosgraph_msgs_generate_messages_lisp
Scanning dependencies of target lio_sam_generate_messages_eus
Scanning dependencies of target lio_sam_generate_messages_cpp
Scanning dependencies of target lio_sam_generate_messages_lisp
[  4%] Generating EusLisp code from lio_sam/cloud_info.msg
[  9%] Generating C++ code from lio_sam/cloud_info.msg
[ 14%] Generating Lisp code from lio_sam/cloud_info.msg
[ 19%] Generating Lisp code from lio_sam/save_map.srv
[ 23%] Generating EusLisp code from lio_sam/save_map.srv
[ 23%] Built target lio_sam_generate_messages_lisp
Scanning dependencies of target lio_sam_generate_messages_nodejs
[ 28%] Generating Javascript code from lio_sam/cloud_info.msg
[ 33%] Generating EusLisp manifest code for lio_sam
[ 38%] Generating C++ code from lio_sam/save_map.srv
[ 42%] Generating Javascript code from lio_sam/save_map.srv
[ 42%] Built target lio_sam_generate_messages_nodejs
Scanning dependencies of target lio_sam_generate_messages_py
[ 47%] Generating Python from MSG lio_sam/cloud_info
[ 47%] Built target lio_sam_generate_messages_cpp
[ 52%] Generating Python code from SRV lio_sam/save_map
Scanning dependencies of target lio_sam_mapOptmization
[ 57%] Building CXX object LIO-SAM/CMakeFiles/lio_sam_imuPreintegration.dir/src/imuPreintegration.cpp.o
[ 61%] Generating Python msg init.py for lio_sam
[ 66%] Generating Python srv init.py for lio_sam
[ 66%] Built target lio_sam_generate_messages_eus
Scanning dependencies of target lio_sam_imageProjection
[ 66%] Built target lio_sam_generate_messages_py
Scanning dependencies of target lio_sam_featureExtraction
[ 71%] Building CXX object LIO-SAM/CMakeFiles/lio_sam_mapOptmization.dir/src/mapOptmization.cpp.o
[ 76%] Building CXX object LIO-SAM/CMakeFiles/lio_sam_imageProjection.dir/src/imageProjection.cpp.o
[ 80%] Building CXX object LIO-SAM/CMakeFiles/lio_sam_featureExtraction.dir/src/featureExtraction.cpp.o
/home/macko-pc/catkin_ws/src/LIO-SAM/src/mapOptmization.cpp: In member function ‘bool mapOptimization::saveMapService(lio_sam::save_mapRequest&, lio_sam::save_mapResponse&)’:
/home/macko-pc/catkin_ws/src/LIO-SAM/src/mapOptmization.cpp:365:11: warning: variable ‘unused’ set but not used [-Wunused-but-set-variable]
int unused = system((std::string("exec rm -r ") + saveMapDirectory).c_str());
^~~~~~
/home/macko-pc/catkin_ws/src/LIO-SAM/src/mapOptmization.cpp: In member function ‘void mapOptimization::publishFrames()’:
/home/macko-pc/catkin_ws/src/LIO-SAM/src/mapOptmization.cpp:1741:37: warning: comparison between signed and unsigned integer expressions [-Wsign-compare]
if (lastSLAMInfoPubSize != cloudKeyPoses6D->size())
^~~~~~
In file included from /usr/include/pcl-1.8/pcl/sample_consensus/sac_model.h:52:0,
from /usr/include/pcl-1.8/pcl/sample_consensus/sac.h:45,
from /usr/include/pcl-1.8/pcl/sample_consensus/ransac.h:44,
from /usr/include/pcl-1.8/pcl/registration/icp.h:45,
from /home/macko-pc/catkin_ws/src/LIO-SAM/include/utility.h:27,
from /home/macko-pc/catkin_ws/src/LIO-SAM/src/featureExtraction.cpp:1:
/usr/include/pcl-1.8/pcl/sample_consensus/model_types.h: In function ‘void __static_initialization_and_destruction_0(int, int)’:
/usr/include/pcl-1.8/pcl/sample_consensus/model_types.h:99:3: warning: ‘pcl::SAC_SAMPLE_SIZE’ is deprecated: This map is deprecated and is kept only to prevent breaking existing user code. Starting from PCL 1.8.0 model sample size is a protected member of the SampleConsensusModel class [-Wdeprecated-declarations]
SAC_SAMPLE_SIZE (sample_size_pairs, sample_size_pairs + sizeof (sample_size_pairs) / sizeof (SampleSizeModel));
^~~~~~~~~~~~~~~
/usr/include/pcl-1.8/pcl/sample_consensus/model_types.h:99:3: note: declared here
In file included from /usr/include/pcl-1.8/pcl/sample_consensus/sac_model.h:52:0,
from /usr/include/pcl-1.8/pcl/sample_consensus/sac.h:45,
from /usr/include/pcl-1.8/pcl/sample_consensus/ransac.h:44,
from /usr/include/pcl-1.8/pcl/registration/icp.h:45,
from /home/macko-pc/catkin_ws/src/LIO-SAM/include/utility.h:27,
from /home/macko-pc/catkin_ws/src/LIO-SAM/src/imageProjection.cpp:1:
/usr/include/pcl-1.8/pcl/sample_consensus/model_types.h: In function ‘void __static_initialization_and_destruction_0(int, int)’:
/usr/include/pcl-1.8/pcl/sample_consensus/model_types.h:99:3: warning: ‘pcl::SAC_SAMPLE_SIZE’ is deprecated: This map is deprecated and is kept only to prevent breaking existing user code. Starting from PCL 1.8.0 model sample size is a protected member of the SampleConsensusModel class [-Wdeprecated-declarations]
SAC_SAMPLE_SIZE (sample_size_pairs, sample_size_pairs + sizeof (sample_size_pairs) / sizeof (SampleSizeModel));
^~~~~~~~~~~~~~~
/usr/include/pcl-1.8/pcl/sample_consensus/model_types.h:99:3: note: declared here
[ 85%] Linking CXX executable /home/macko-pc/catkin_ws/devel/lib/lio_sam/lio_sam_featureExtraction
[ 90%] Linking CXX executable /home/macko-pc/catkin_ws/devel/lib/lio_sam/lio_sam_imageProjection
In file included from /usr/include/pcl-1.8/pcl/sample_consensus/sac_model.h:52:0,
from /usr/include/pcl-1.8/pcl/sample_consensus/sac.h:45,
from /usr/include/pcl-1.8/pcl/sample_consensus/ransac.h:44,
from /usr/include/pcl-1.8/pcl/registration/icp.h:45,
from /home/macko-pc/catkin_ws/src/LIO-SAM/include/utility.h:27,
from /home/macko-pc/catkin_ws/src/LIO-SAM/src/imuPreintegration.cpp:1:
/usr/include/pcl-1.8/pcl/sample_consensus/model_types.h: In function ‘void __static_initialization_and_destruction_0(int, int)’:
/usr/include/pcl-1.8/pcl/sample_consensus/model_types.h:99:3: warning: ‘pcl::SAC_SAMPLE_SIZE’ is deprecated: This map is deprecated and is kept only to prevent breaking existing user code. Starting from PCL 1.8.0 model sample size is a protected member of the SampleConsensusModel class [-Wdeprecated-declarations]
SAC_SAMPLE_SIZE (sample_size_pairs, sample_size_pairs + sizeof (sample_size_pairs) / sizeof (SampleSizeModel));
^~~~~~~~~~~~~~~
/usr/include/pcl-1.8/pcl/sample_consensus/model_types.h:99:3: note: declared here
[ 90%] Built target lio_sam_featureExtraction
Scanning dependencies of target lio_sam_generate_messages
[ 90%] Built target lio_sam_generate_messages
[ 90%] Built target lio_sam_imageProjection
In file included from /usr/include/pcl-1.8/pcl/sample_consensus/sac_model.h:52:0,
from /usr/include/pcl-1.8/pcl/sample_consensus/sac.h:45,
from /usr/include/pcl-1.8/pcl/sample_consensus/ransac.h:44,
from /usr/include/pcl-1.8/pcl/registration/icp.h:45,
from /home/macko-pc/catkin_ws/src/LIO-SAM/include/utility.h:27,
from /home/macko-pc/catkin_ws/src/LIO-SAM/src/mapOptmization.cpp:1:
/usr/include/pcl-1.8/pcl/sample_consensus/model_types.h: In function ‘void __static_initialization_and_destruction_0(int, int)’:
/usr/include/pcl-1.8/pcl/sample_consensus/model_types.h:99:3: warning: ‘pcl::SAC_SAMPLE_SIZE’ is deprecated: This map is deprecated and is kept only to prevent breaking existing user code. Starting from PCL 1.8.0 model sample size is a protected member of the SampleConsensusModel class [-Wdeprecated-declarations]
SAC_SAMPLE_SIZE (sample_size_pairs, sample_size_pairs + sizeof (sample_size_pairs) / sizeof (SampleSizeModel));
^~~~~~~~~~~~~~~
/usr/include/pcl-1.8/pcl/sample_consensus/model_types.h:99:3: note: declared here
[ 95%] Linking CXX executable /home/macko-pc/catkin_ws/devel/lib/lio_sam/lio_sam_imuPreintegration
/usr/bin/ld: cannot find -lBoost::timer
collect2: error: ld returned 1 exit status
LIO-SAM/CMakeFiles/lio_sam_imuPreintegration.dir/build.make:759: recipe for target '/home/macko-pc/catkin_ws/devel/lib/lio_sam/lio_sam_imuPreintegration' failed
make[2]: *** [/home/macko-pc/catkin_ws/devel/lib/lio_sam/lio_sam_imuPreintegration] Error 1
CMakeFiles/Makefile2:3207: recipe for target 'LIO-SAM/CMakeFiles/lio_sam_imuPreintegration.dir/all' failed
make[1]: *** [LIO-SAM/CMakeFiles/lio_sam_imuPreintegration.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[100%] Linking CXX executable /home/macko-pc/catkin_ws/devel/lib/lio_sam/lio_sam_mapOptmization
/usr/bin/ld: cannot find -lBoost::timer
collect2: error: ld returned 1 exit status
LIO-SAM/CMakeFiles/lio_sam_mapOptmization.dir/build.make:759: recipe for target '/home/macko-pc/catkin_ws/devel/lib/lio_sam/lio_sam_mapOptmization' failed
make[2]: *** [/home/macko-pc/catkin_ws/devel/lib/lio_sam/lio_sam_mapOptmization] Error 1
CMakeFiles/Makefile2:2868: recipe for target 'LIO-SAM/CMakeFiles/lio_sam_mapOptmization.dir/all' failed
make[1]: *** [LIO-SAM/CMakeFiles/lio_sam_mapOptmization.dir/all] Error 2
Makefile:140: recipe for target 'all' failed
make: *** [all] Error 2
Invoking "make -j4 -l4" failed`

I have the same problem, did you solve it？ @macnack

I too am having this same problem, any solutions?

I solved this problem by following two methods：
1.Please refer to this link link；
2.I downgraded the version of gtsam from 4.0.3 to 4.0.2，then it compiles fine. This means it's a gtsam version problem。
The second method is recommended，the first method compiles normally, but the node will exit abnormally at runtime.
hope this helps.

Hi , can you help me with the directory or a link to install GTSAM 4.0.2


Is there provision for times zones?

Eg, if someone is viewing events in the US, there will be at a certain time.
but those same events need to appear at different times for someone viewing them in the UK.
Does Evo Cal support this?
Thanks!

Hello @coda-apps, maybe it depends on how you handle timezone..  I haven't tested it yet. :thinking:

I am interested to know when feature upgrade for timezone. Most important to have this.


[HelmChart] No documentation how to use customized image (for development) in HelmChart instruction

Search before asking

[X] I searched the issues and found no similar issues.

KubeRay Component
ray-operator
What happened + What you expected to happen
I have built my own image in my own docker hub, but not able to find instruction where to update the helm chart to use the image.
Reproduction script
N/A
Anything else
No response
Are you willing to submit a PR?

[ ] Yes I am willing to submit a PR!

I agree that the docs should be better on this point.
You might have already figured this out, but you can edit the image in values.yaml:
https://github.com/ray-project/kuberay/blob/16fd58be7e3af171aa83cdb3aee111b2b438013f/helm-chart/kuberay-operator/values.yaml#L5-L8

Thank @sihanwang41 for pointing this out! I will work on this.


fix the underlying type of scheme::type

It looks like @anonrig wants us to access more directly the a type attribute, if so we may want to specify its type precisely.

I'm fine with re-adding the scheme type regardless of this change 👍


TODO: More flexible/correct VRM detection algorithm

I was happened this error in Fix Model feature with imported my VRM file:

I think my VRM file is not broken then I read the source code about this error message.

https://github.com/michaeldegroot/cats-blender-plugin/blob/5306d62014cbf9a99744e45dc94f6e858a62fdf2/tools/armature.py#L94

And, I found the TODO comment in the VRM detection algorithm:
        is_vrm = False
        if len(Common.get_meshes_objects()) == 0:
            for mesh in Common.get_meshes_objects(mode=2):
                if mesh.name.endswith(('.baked', '.baked0')):
                    is_vrm = True  # TODO
            if not is_vrm:
                self.report({'ERROR'}, 'No mesh inside the armature found!')
                return {'CANCELLED'}

Maybe, this implementation is based on an undocumented VRoid Studio specific behavior. It is not VRM or Unity/humanoid or gltf specification. Thus, the author wrote TODO who implement the algorithm temporaly, maybe.
In now, we can use several tools for make a VRM format data. Some tools are output a VRM format file that has a different internal details to VRoid Studio. Therefore, I created this issue.
Reproducable example:

https://hub.vroid.com/characters/1537388192474504367/models/426275608358835909 ; The file is attached in the below:

5383585797165228376.zip
It has no .baked or .baked0 named meshes but it is a correct VRM format file for VRoid Hub at least.

For reference, it is a mesh structure outputed by VRoid Studio. It has a .baked meshes.

Thanks for the report.
Unfortunately it's not possible to detect meshes from any VRM model. The .baked algorithm is just a quick fix solution. But instead I now have improved that error message to tell the user what to do. Also now when the user uses the cats import button to import vrm files, it will automatically reparent the added meshes to the armature without having to press Fix Model. (c434194933253dbe3f60a580413d6557c76aa705)


Operations: priority class enhancements as node count changes

A recent addition to IBM Cloud actually modifies the priority class of the master control plane components to be higher if the customer is using more worker nodes in their cluster (and therefore spending more money on the offering).
The values are shown below
  - apiVersion: scheduling.k8s.io/v1
    kind: PriorityClass
    metadata:
      name: cruiser-mcp-xs
    value: 1000000
    globalDefault: false
    description: "Used on master control plane resources for cruisers with 1-10 workers."
  - apiVersion: scheduling.k8s.io/v1
    kind: PriorityClass
    metadata:
      name: cruiser-etcd-xs
    value: 1500000
    globalDefault: false
    description: "Used on master ETCD resources for cruisers with 1-10 workers."
  - apiVersion: scheduling.k8s.io/v1
    kind: PriorityClass
    metadata:
      name: cruiser-mcp-s
    value: 2000000
    globalDefault: false
    description: "Used on master control plane resources for cruisers with 11-25 workers."
  - apiVersion: scheduling.k8s.io/v1
    kind: PriorityClass
    metadata:
      name: cruiser-etcd-s
    value: 2500000
    globalDefault: false
    description: "Used on master ETCD resources for cruisers with 11-25 workers."
  - apiVersion: scheduling.k8s.io/v1
    kind: PriorityClass
    metadata:
      name: cruiser-mcp-m
    value: 3000000
    globalDefault: false
    description: "Used on master control plane resources for cruisers with 26-50 workers."
  - apiVersion: scheduling.k8s.io/v1
    kind: PriorityClass
    metadata:
      name: cruiser-etcd-m
    value: 3500000
    globalDefault: false
    description: "Used on master ETCD resources for cruisers with 26-50 workers."
  - apiVersion: scheduling.k8s.io/v1
    kind: PriorityClass
    metadata:
      name: cruiser-mcp-l
    value: 4000000
    globalDefault: false
    description: "Used on master control plane resources for cruisers with 51-100 workers."
  - apiVersion: scheduling.k8s.io/v1
    kind: PriorityClass
    metadata:
      name: cruiser-etcd-l
    value: 4500000
    globalDefault: false
    description: "Used on master ETCD resources for cruisers with 51-100 workers."
  - apiVersion: scheduling.k8s.io/v1
    kind: PriorityClass
    metadata:
      name: cruiser-mcp-xl
    value: 5000000
    globalDefault: false
    description: "Used on master control plane resources for cruisers with 101-300 workers."
  - apiVersion: scheduling.k8s.io/v1
    kind: PriorityClass
    metadata:
      name: cruiser-etcd-xl
    value: 5500000
    globalDefault: false
    description: "Used on master ETCD resources for cruisers with 101-300 workers."
  - apiVersion: scheduling.k8s.io/v1
    kind: PriorityClass
    metadata:
      name: cruiser-mcp-xxl
    value: 6000000
    globalDefault: false
    description: "Used on master control plane resources for cruisers with 300+ workers."
  - apiVersion: scheduling.k8s.io/v1
    kind: PriorityClass
    metadata:
      name: cruiser-etcd-xxl
    value: 6500000
    globalDefault: false
    description: "Used on master ETCD resources for cruisers with 300+ workers."
  - apiVersion: scheduling.k8s.io/v1
    kind: PriorityClass
    metadata:
      name: cruiser-mcp-dedicated
    value: 7000000
    globalDefault: false
    description: "Used on master control plane resources for dedicated cruisers."
  - apiVersion: scheduling.k8s.io/v1
    kind: PriorityClass
    metadata:
      name: cruiser-etcd-dedicated
    value: 7500000
    globalDefault: false
    description: "Used on master ETCD resources for dedicated cruisers."

I believe that will be good behavior to have in hypershift if there's a simplistic way to implement it. It helps ensure that larger clusters don't get evicted/rescheduled first due to potential noisy neighbors on smaller clusters (instead with the priority class the smaller clusters would get evicted first).

/remove-lifecycle stale

/assign @a-dsouza

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale


Added initialize script for Xpp Metadata folder

moved folder with Xpp Model to a new Metadata folder
removed BuildModelResult.err.xml file as unnecessary
changed .gitignore for model folder changes
added initialize script linking Model with AOS main directory for easy installation on DEV environment:

Getting Started
Clone the new repository using git clone command on your K drive.
cd K:/
git clone https://github.com/milnet92/MXTXppInterpreter.git MXTXppInterpreter
Execute Initialization script (Make sure to Run As Administrator) from new folder:
cd K:/MXTXppInterpreter/Scripts
.\Initialize.ps1
Build and Test
Open Visual Studio and build MXppTools model with DB sync

@milnet92 Hi,
I got a little confused with the old PR and changes, so in order not to complicate it, I decided to rebuild the fork and the new PR with the same changes :)


Share Xcode scheme so SwiftSpinner works with Carthage

Carthage is a decentralized dependency manager that gives developers more control over how frameworks are integrated compared to CocoaPods, and is becoming increasingly popular. It uses xcodebuild to build dependancies instead of using a shared workspace, and the only requirement for frameworks is that there's a shared scheme so that the tool can discover and build it properly.

is there a step-by-step tutorial you can recommend?

Here's a quick step-by-step from Apple docs: https://developer.apple.com/library/ios/recipes/xcode_help-scheme_editor/Articles/SchemeShare.html. Shared schemes are also used when automating testing via an Xcode build server.

thanks I'll have a look

+1

+1

I've forked, added Carthage support and submitted a pull req.
#53

#53 is merged, thanks!


Bot pulls posts that are older than 1 day and counts them towards the rate limit

The bot recently removed several of Jackie's posts that were several days old and I had to manually restore them. This could be because

The bot pulls successively older posts every time .new() is called on the subreddit
The number of posts it fetches is getting higher and higher each cycle

Will investigate further. Might be fixed in Pyro's pull request

Fixed: https://github.com/NateNate60/ToS_Helper_Bot/commit/2a4979fafe8ce34be608970318ca63b42a9b0a33


GUI layout editor?

Would be nice if you could make layout visually instead of editing config files.

Way too much work, never gonna happen. Text editor is more than good enough.

Not for the target audience that despise coding of any kind and just likes to click stuff, a.k.a. The Artists™
    Dnia 21 czerwca 2024 12:58 minkberry<EMAIL_ADDRESS>napisał(a):

Way too much work, never gonna happen. Text editor is more than good enough.
—  Reply to this email directly,  github.com view it on GitHub , or  github.com unsubscribe .  You are receiving this because you authored the thread. Message ID:  <Martenfur/TabletFriend/issues/48/2182522840 @ github . com>

There's one thing you got wrong - my primary target audience is myself. :)
The problem with GUI editing is that in order to make it - and make it good - you'd have to spend as much time if not more as for the rest of the program. It's a lot, and I mean A LOT of work, and this is just a fun side project for me. The current solution is good and very fast to work with, if you spend half an hour learning the layout structure, which is not that complex, GUI will not make it that much better. More approachable, yes, but as I said I wrote this mainly for myself and put it up for whoever wants to use it also.


make EM.threadpool_size configurable

Due to network latency, the sending speed of Bosh metrics is slow from China region to Datadog server.
After a period,  the time lag is so big  that Datadog drops any new incoming metric.
The possible fix is to change the following file to accept a config param for EM.threadpool_size
bosh_monitor/lib/bosh/monitor/runner.rb

Closing - thanks for PR #1102 which was merged and fixed this issue!


Support for post request in monitoring screen

Signed-off-by: Harkishen-Singh<EMAIL_ADDRESS>

@aquibbaig implemented!


Implementation of folding comments

Side issue: You did make a new branch this time, but it's branched from your last change instead of branched from main. There are no conflicts, and a squash merge will fix it up so no need to change it, but for the future, you should make the new branch from an up-to-date main branch.
Ping me next time you start a new feature branch and I'll walk you through it. I thought about putting a recipe here, but I think it would be more educational if we did it slowly and carefully together.


No keypresses when using app

Not sure if this is an issue caused by Harmony or by the server. Created two sequences:
Play & Dim - added to 'play' button --> sends PLAY command to Shield and PLAY command to Harmony-Span
Pauze & Bright - added to 'pauze' button --> sends PAUZE command to Shield and INSTANTREPLAY to Harmony-Span (had to pick any other than Pauze, as Pauze also sends PLAY command to harmony span).
When using the physical remote (Companion), both sequences work correctly.
When using the APP on the phone, none of the sequences work.
My guess is it's the app and not the harmony-server though, since the sequence created is assigned to as specific remote, but would be good to highlight!

All good. Do you have the ability to create sequences for buttons in the app?
Thanks for opening an issue! I'll investigate this further.


Attach JSON to test execution evidence

Hi! Thanks for the plugin, it solves a lot of issues on our team!
We have an API test execution and the idea is to save the JSON response on the test execution evidence when the test is executed. On the unit test level the framework that the dev team uses has that capability so I'm taking the shot if that's possible to implement here (we're using the screenshot/videos already, works like a charm!)
Thanks!

Hi @reify-lucas-mazzini,
glad to hear that the plugin is making your life easier! So just for my understanding, you have something like this:
describe("GET /users", () => {

  it("PRJ-123 returns 200", () => {
    cy.request("GET", "/users").then((response) => {
      expect(response.status).to.eq(200);
    });
  });

  it("PRJ-456 returns all users", () => {
    cy.request("GET", "/users").then((response) => {
      expect(response.body.content).to.deep.eq(["jeff", "bob"]);
    });
  });
});

And now you would like to attach the responses to the test execution as well?

In the current plugin version, this is not possible out of the box. Do you think something like this would do as well?
import { attachEvidence } from "cypress-xray-plugin";

describe("GET /users", () => {

  it("PRJ-123 returns 200", () => {
    cy.request("GET", "/users").then((response) => {
      attachEvidence("PRJ-123", "body.json", response); // maybe there's a way to avoid duplicating the key
      expect(response.status).to.eq(200);
    });
  });

  it("PRJ-456 returns all users", () => {
    cy.request("GET", "/users").then((response) => {
      attachEvidence("PRJ-456", "body.json", response); // maybe there's a way to avoid duplicating the key
      expect(response.body.content).to.deep.eq(["jeff", "bob"]);
    });
  });
});

Out of curiosity, which framework does the dev team use for this?

Thanks for the quick response @csvtuda!
Yes, the ideal execution would be as you mentioned as an example, making a cy.request() and then attach the evidence inside the same test.
On how to avoid duplicating the key, we implemented an override on the screenshot command that gets the ID from the test and inserts it into the screenshot name, maybe the same logic can be used :)
It uses Cypress.currentTest.title to get the test title and then parses the title with the Jira project key and a regex to return the key
Cypress.Commands.overwrite('screenshot', (originalFn, subject, fileName, options) => {
  const jiraKeyPattern = Cypress.env('JIRA_PROJECT_KEY') + '-\\d+';
  const currentTestTitle = Cypress.currentTest.title;
  const isJiraKeyExists = RegExp(jiraKeyPattern).exec(currentTestTitle);
  if (isJiraKeyExists) {
    const jiraKey = isJiraKeyExists ? isJiraKeyExists[0] : currentTestTitle; // Here would be the Jira key
    fileName = `${jiraKey} ${fileName}`;
  }
  return originalFn(subject, fileName, options);
});

The framework that the dev team uses is Kaocha, they have a plugin to upload results to xray but I'm not 100% sure if the plugin is work from the dev team of the framework team 😅

On how to avoid duplicating the key, we implemented an override on the screenshot command that gets the ID from the test and inserts it into the screenshot name, maybe the same logic can be used :)

This is a very good suggestion, thanks for the input 🥇 I will try to implement it using overwrite, too.
If everything works out as intended, the only thing you'll need to do will be an import inside the commands support file:
// support/commands.[js,ts]
import "cypress-xray-plugin/commands";

Alternatively, if you'd like to do other stuff during the overwrite callback and prevent the plugin from overriding your custom command, I will also make sure to expose the handlers:
// support/commands.[js,ts]
import { on } from "cypress-xray-plugin/commands/handlers";

Cypress.Commands.overwrite("request", (fn, options) => {
    // Other stuff...
    // ...
    return on("cy.request", fn, options);
})

Thanks for all the work and the quick responses! ❤

Hey @reify-lucas-mazzini,
sorry for the delay, writing tests for this issue turned out to be a lot more difficult than I had expected.
I just released version 7.0.0, which includes the new command override. For a list of breaking changes, please see here.

As for your issue, you should now be able to add cy.request JSON upload by performing the following steps:

Import the overwritten command to your support file:
import "cypress-xray-plugin/commands";

If you want to keep existing custom cy.request, please check the documentation. It includes two examples for this very use case.

Enable the requests upload in the configuration:
// ...
async setupNodeEvents(on, config) {
  await configureXrayPlugin(
    on,
    config,
    {
      // ...
      xray: {
        uploadRequests: true
      }
    }
  );
}

Afterwards, you should be able to see request evidence for tests you've linked to existing Jira issues (issue key in test title):

The documentation examples also show how you can customise evidence filenames.
Let me know if the new version works as expected and/or fixes your issue.

Hey @csvtuda! Thanks for all the hard work, and sorry for the delay on the response, just got some capacity to tackle this!
This are the findings on the update so far:
Updated the plugin, configured everything and got the following error:
The 'task' event has not been registered in the setupNodeEvents method. You must register it before using cy.task()
"Fixed" it the following way (not sure if the correct way to solve it):
// cypress.config.js

async setupNodeEvents(on, config) {
  on('task', {
          'cypress-xray-plugin:task:request'() {
              return null;
          },
          'cypress-xray-plugin:task:response'(){
              return null;
          }
  });
  await configureXrayPlugin(
    on,
    config,
    {
      // ...
      xray: {
        uploadRequests: true
      }
    }
  );
}

After solving those issues, the cy.request() function it seems to be not working at it should.
// cypress.test.js
      cy.request('https://jsonplaceholder.typicode.com/comments').then((response) => {
          expect(response.status).to.eq(200)
      });

Using the command as normal givingURL gives the following error:
cy.request() requires a url. You did not provide a url.

Hey @csvtuda!
1- I'm using "cypress-xray-plugin": "^7.0.0" for the package version.
2- Yes!
Trying to run both scenarios (with task "fix" setup on the config file and the url) with npx cypress run and got the same issues:

The issue here is that without the task configuration, the first error is thrown. Even if I set the return on the task to true it returns a different error.

I already try to uninstall the package and installing it clean, any recommendations on how to proceed? 👀

Hey @reify-lucas-mazzini,
I created a sample project for your use case here: https://github.com/Qytera-Gmbh/cypress-xray-plugin-examples/tree/main/request-upload.
As stated in the README, everything works fine in that project.
Can you compare that project with your current one and try to see the differences?


BindableLayoutBuilder depending on position

Is it possible to implement a BindableLayoutBuilder where the view class of an item depends on the item position in the adapter instead of its data?
I tried to return different layout id's when overriding BindableLayout.getLayoutId() but it didn't work (due to viewholders' recycling, I guess) and can't find the way to get the position from the BindableLayoutBuilder.
Thanks for the lib, so useful :)

I will include the position in the builder interface in a next version, as it is a good fit. For the time being, a BindableLayout view has the position in the bind method so you could use that.

That would be nice. Thank you.

I have been able to look at the code and I've seen why the position was not included as part of the BindableLayoutBuilder. In the RecyclerView version you don't know the position up until binding time, and that's why it's passed to the bind(...) method in BindableLayout instead of being in the builder.
I can't think of a way to circumvent this, so it's a tradeoff I had to make to make the library compatible with the old-school *Adapter classes and the RecyclerView adapters.


Problems with signal traps since 0.7

I am the author of vpncloud (https://github.com/dswd/vpncloud) and I am using the igd crate to establish port forwardings in NAT routers. Many thanks for the great crate by the way.
Since version 0.7 I experience the problem, that the vpncloud binary can't be closed via ctrl-c as my custom signal traps do not work anymore. It seems that since 0.7 something swallows all signals.
If you want to test it, you can use my current code, compile the binary and run vpncloud --type dummy. If you upgrade idg to 0.7 ctrl-c will stop working.
Do you have any idea on how to prevent this?
Any help will be greatly appreciated.

It might be related to tokio. Even though we don't use signals explicitly in the crate it might be something that tokio is doing to handle the shutdown of the loop. In 0.7 the synchronous code uses the async code and just blocks on the future.
Does the problem happen systematically or does it only happen while you are doing port mapping? If there's a tokio thread pool somehow left after we do the port mapping, it's probably an issue.

When port forwarding is enabled in vpncloud, crtl-c does no longer work at all. The process just keeps on running infinitely. It is also not the case that something blocks the process from exiting (there is a "shutting down..." message right after receiving the signal that is not printed, so the signal is never received).
When I disable the port forwarding functionality with commandline arguments, ctrl-c works reliably. So the problem must be related to actually calling into igd/tokio and not just including it.
The problem does not seem to be related to whether port forwardings are requested while pressing ctrl-c. The problem persists over multiple minutes and repeated presses of ctrl-c and kill commands.

Alright, thanks for the info. I'm trying to refactor the library right now and I will update all the crates and remove the async code from the sync methods calls. Hopefully that will help you.

Thank you very much.

Oh, when you refactor the library, could you make the tokio/async parts optional using a feature? Currently igd pulls in lots of dependencies, that I think are not needed for my use case.

Yes, I was planning on putting the async stuff behind a feature to make it more lightweight, but I was also planning on using reqwest for the HTTP needs and reqwest depends on the tokio stack. In fact right now it uses hyper which also depends on the tokio stack.
I've been working on a small, lightweight HTTP client in my free time but I'm not quite sure if its robust enough to be used in this crate yet. https://github.com/sbstp/lynx

Oh that sounds interesting. However you are facing a small name clash: here https://lynx.browser.org/

Hey, I just pushed my refactor to the master branch. Can you tell me if your bug is fixed? You can use a git dependency temporarily before I publish this.
igd = { git = "https://github.com/sbstp/rust-igd.git" }

Ok I tested your version:
The good thing is that ctrl-c works now.
The bad thing is that port forwarding does not work anymore:
ERROR - Port-forwarding: failed to obtain external IP: Request Error. Invalid response from gateway: <TITLE>500 Internal Server Error (ERR_INVALID_REQ)</TITLE>
500 Internal Server Error

ERR_INVALID_REQ
Webserver Sun, 03 Mar 2019 09:19:16 GMT

So I did some debugging with wireshark. The differences between your invalid lynx requests and the valid hyper requests are the following:
The headers are quite different:

Hyper sends Host: <IP_ADDRESS>:49000 and Content-Type: text/xml while lynx does not
Lynx sends connection: close and accept-encoding: gzip, deflate while hyper does not
Hyper sends SOAPAction: ... while lynx sends soapaction: ...

The body looks roughly the same with the sole exception that hyper seems to indent the SOAP-ENV tag by 8 spaces while lynx does not.
If I were to bet, I would put my money on the Content-Type header.

Alright I've updated lynx to add the Host header and updated this crate with the Content-Type header. Let me know if this works.

Yes, it works. Thanks a lot for your immediate help. Please tell me when you released those fixes.

Alright, it's released in 0.8.0.

Thanks. Do you actually need openssl as a dependency or is that a mistake?

I've updated igd with the new version of lynx and disabled the features. I've also removed the regex crate, it wasn't needed. Can you test the crate again and I'll publish it if all goes well?
Here's the new dependency tree, it's pretty much as light as it's going to get.
igd v0.8.0 (/home/simon/projects/rust-igd)
├── lynx v0.1.2
│   ├── http v0.1.16
│   │   ├── bytes v0.4.11
│   │   │   ├── byteorder v1.3.1
│   │   │   └── iovec v0.1.2
│   │   │       └── libc v0.2.48
│   │   ├── fnv v1.0.6
│   │   └── itoa v0.4.3
│   ├── log v0.4.6
│   │   └── cfg-if v0.1.6
│   └── url v1.7.2
│       ├── idna v0.1.5
│       │   ├── matches v0.1.8
│       │   ├── unicode-bidi v0.3.4
│       │   │   └── matches v0.1.8 (*)
│       │   └── unicode-normalization v0.1.8
│       │       └── smallvec v0.6.8
│       │           └── unreachable v1.0.0
│       │               └── void v1.0.2
│       ├── matches v0.1.8 (*)
│       └── percent-encoding v1.0.1
├── rand v0.4.6
│   └── libc v0.2.48 (*)
├── url v1.7.2 (*)
└── xmltree v0.8.0
    └── xml-rs v0.7.0
        └── bitflags v1.0.4

Wow, it works and that update reduced my binary size by 25%.


Add update interval to publisher location update messages

Change to Publishers
The LocationUpdate will have a new member updateInterval (units TBC, but should match what we use elsewhere in terms of time intervals / durations).
Change to Subscribers
This would allow subscribers to more accurately render skipped locations when an update is received, with the effect being that the displayed location is intentionally animated from the previously known locations, through the skipped locations and ultimately to the current location over that time period in anticipation of receiving another update after that time.
So, for example, were the following two messages to be received:

at 00:10, update message 1:

location: A

at 00:20, update message 2:

location: F
skippedLocations: B, C, D, E
updateInterval: 10 seconds

Then the subscriber, at the point of receiving message 2, would animate interpolated between the following keyframe locations:

00:20: A
00:22: B
00:24: C
00:26: D
00:28: E
00:30: F

Anticipating that the next update will arrive at 00:30, where the updateInterval might be the same or could be different.
┆Issue is synchronized with this Jira Task by Unito

@QuintinWillison I'm assuming that this change is intended for subscribing example app. As far as I know we are able to move or animate markers on Google maps, however I haven't seen that we can give a custom interpolator to that animation. But there is nothing that stops us from wrapping that functionality inside a custom intrepolator.

We've had a potential customer for Ably Asset Tracking tell us that they are less worried about the 'realtime' nature of the updates to subscribers, and that the smoothness of the rendering is more important to them. Therefore, the theory is that even a network update frequency of something like 30 seconds might be frequent enough - as long as the locations received in those updates are rendered at the subscriber end over the next 30 seconds so that they appear smooth (even though they were all captured 30 seconds ago by the publisher, at the point they are rendered in the subscriber view).
Another term for this could be something like "intentional display latency".

This issue was closed due to the implementation of a similar solution "Publish expected interval after which a batch of new locations will be sent (for subscriber-side rendering)" https://github.com/ably/ably-asset-tracking-android/issues/626 and https://github.com/ably/ably-asset-tracking-android/issues/634 which helps to resolve the issue described in this ticket.


Adding Bitnami chart causes 2-3 minute CPU spikes every 15 minutes and 30-40 minute CPU spike when rancher restarted

What kind of request is this (question/bug/enhancement/feature request):
bug
Steps to reproduce (least amount of steps as possible):

Install Rancher
Enable v1 monitoring on local cluster (so you can get see CPU graphs)
Add the Bitnami catalog - Tools -> Catalogs, add URL=https://charts.bitnami.com/bitnami as a global catalog. Version =Helm v3
Wait a few hours (may not see spikes for a while)

Result:
After waiting a few hours, will see 100% CPU spikes that last 2-3 minutes. These happen every 15 minutes:

Go to System -> workloads and delete the rancher pods, they'll respawn and CPU will be maxed out for 30-40 minutes:

In both cases, it's the k3s-server process that is maxing out the CPU. Observed this in the k3s logs:
Apr 15 03:24:26 ip-10-10-101-200 k3s[937]: I0415 03:24:26.178016     937 trace.go:205] Trace[71675938]: "Update" url:/apis/management.cattle.io/v3/catalogs/bitnami,user-agent:rancher/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (15-Apr-2021 03:23:52.126) (total time: 34050ms):
Apr 15 03:42:18 ip-10-10-101-200 k3s[937]: I0415 03:42:18.555397     937 trace.go:205] Trace[1026252523]: "Update" url:/apis/management.cattle.io/v3/catalogs/bitnami,user-agent:rancher/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (15-Apr-2021 03:41:44.505) (total time: 34049ms):
Apr 15 03:42:54 ip-10-10-101-200 k3s[937]: I0415 03:42:54.299409     937 trace.go:205] Trace[1920579102]: "Update" url:/apis/management.cattle.io/v3/catalogs/bitnami,user-agent:rancher/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (15-Apr-2021 03:42:20.224) (total time: 34075ms):
Apr 15 04:00:11 ip-10-10-101-200 k3s[937]: I0415 04:00:11.110604     937 trace.go:205] Trace[167055759]: "Update" url:/apis/management.cattle.io/v3/catalogs/bitnami,user-agent:rancher/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (15-Apr-2021 03:59:37.057) (total time: 34052ms):
Apr 15 04:00:47 ip-10-10-101-200 k3s[937]: I0415 04:00:47.430394     937 trace.go:205] Trace[1689552688]: "Update" url:/apis/management.cattle.io/v3/catalogs/bitnami,user-agent:rancher/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (15-Apr-2021 04:00:13.277) (total time: 34152ms):
Apr 15 04:18:04 ip-10-10-101-200 k3s[937]: I0415 04:18:04.187835     937 trace.go:205] Trace[1508257776]: "Update" url:/apis/management.cattle.io/v3/catalogs/bitnami,user-agent:rancher/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (15-Apr-2021 04:17:30.132) (total time: 34055ms):
Apr 15 04:18:39 ip-10-10-101-200 k3s[937]: I0415 04:18:39.811915     937 trace.go:205] Trace[878091697]: "Update" url:/apis/management.cattle.io/v3/catalogs/bitnami,user-agent:rancher/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (15-Apr-2021 04:18:05.722) (total time: 34089ms):
Apr 15 04:36:32 ip-10-10-101-200 k3s[937]: I0415 04:36:32.342801     937 trace.go:205] Trace[502588042]: "Update" url:/apis/management.cattle.io/v3/catalogs/bitnami,user-agent:rancher/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (15-Apr-2021 04:35:58.230) (total time: 34112ms):
Apr 15 04:53:49 ip-10-10-101-200 k3s[937]: I0415 04:53:49.019193     937 trace.go:205] Trace[408489179]: "Update" url:/apis/management.cattle.io/v3/catalogs/bitnami,user-agent:rancher/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (15-Apr-2021 04:53:14.969) (total time: 34049ms):
Apr 15 04:54:24 ip-10-10-101-200 k3s[937]: I0415 04:54:24.656113     937 trace.go:205] Trace[1988414344]: "Update" url:/apis/management.cattle.io/v3/catalogs/bitnami,user-agent:rancher/v0.0.0 (linux/amd64) kubernetes/$Format,client:<IP_ADDRESS> (15-Apr-2021 04:53:50.564) (total time: 34091ms):

Other details that may be helpful:
If you delete the bitnami catalog, everything returns to normal - no CPU spikes.
Possible related issue - https://github.com/rancher/rancher/issues/31940
Catalog also displayed in "Refreshed" state and never changes to "Active":

Environment information

Rancher version (rancher/rancher/rancher/server image tag or shown bottom left in the UI):
v2.5.7
Installation option (single install/HA):
HA

Cluster information

Cluster type (Hosted/Infrastructure Provider/Custom/Imported):
k3s

Machine type (cloud/VM/metal) and specifications (CPU/memory):
2 m5a.large AWS instances (2vCPU, 8GB RAM) w/ RDS Aurora MySQL DB

Kubernetes version (use kubectl version):

> kubectl version
Client Version: version.Info{Major:"1", Minor:"19", GitVersion:"v1.19.7", GitCommit:"1dd5338295409edcfff11505e7bb246f0d325d15", GitTreeState:"clean", BuildDate:"2021-01-13T13:23:52Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.5+k3s1", GitCommit:"355fff3017b06cde44dbd879408a3a6826fa7125", GitTreeState:"clean", BuildDate:"2021-03-31T06:21:52Z", GoVersion:"go1.15.10", Compiler:"gc", Platform:"linux/amd64"}

Docker version (use docker version):
containerd

gz#16028

I think this is related as well: https://github.com/rancher/rancher/issues/32295

From further testing found this only happens on Kubernetes 1.20 clusters (both RKE and K3s). Could not reproduce the issue on 1.19.

Was also able to reproduce this issue on k3s 1.21.

This should be fixed now that the upstream k8s patches have fixed, anything past 1.21.3 cc @dnoland1

Tested this on Rancher v2.6.3 with k3s 1.21.7. The CPU seems to stay at a reasonable level after adding the Bitnami catalog. However, if I add ten copies of the catalog, the environment locks up and becomes completely unresponsive. So there still appears to be a scaling issue if you add ten substantially large catalogs.

Thats not too surprising. The fix we made was to compress/minimize the catalogs, so if you add 10x catalogs then you will have gone beyond the space saved by the compression. The upstream k8s fix was included in 1.21.3, so your test includes those fixes too. I think for now we should close until someone hits this again with fixes.

I've also tested this on 2.6.4-rc3 and do not see any sort of spikes 8 hours after adding the bitnami chart.


Compute the intensity of sequential genes after cell re-segmentation

Hello,
Thanks for developing this powerful tool! I have been using it in re-segmenting the MERSCOPE data, and it performed very well so far in terms of improving the ratio of transcripts being assigned to cells.
However, I have sequential genes which are not in the merfish list. I am wondering whether you can re-calculate the density of sequential genes after cell re-segmentation. If you are busy in developing other features, I totally understand, and I wonder whether you can kindly offer some advice on how to do the calculation.
Thanks,
Christina

Hi Christina,
Yes, VPT does allow estimation of the expression of genes in the sequential panel using the new segmentation. The sum-signals functionality quantifies the brightness of the mosaic images within each cell. It returns both the summed intensity of the raw image within the cell, and the summed intensity of a high-pass filtered version of the image. The high-pass filter is calibrated to enhance image features that are roughly the size of a smFISH spot.
In order to run sum-signals, you would use a command like this:
vpt --verbose --processes 8 sum-signals \
--input-images="/PATH_TO_INPUTS/region_0/images/mosaic_(?P<stain>GENE_NAME)_z(?P<z>[0-9]+).tif" \
--input-boundaries /PATH_TO_OUTPUTS/cellpose_micron_space.parquet \
--input-micron-to-mosaic /PATH_TO_INPUTS/region_0/images/micron_to_mosaic_pixel_transform.csv \
--output-csv /PATH_TO_OUTPUTS/sum_signals.csv

Link to documentation: https://vizgen.github.io/vizgen-postprocessing/command_line_interface/index.html#sum-signals
It’s important to note that the output of sum-signals is not in units of counts, it’s in units of intensity. Because of that difference in units, the sum-signals output may require some additional processing before you can integrate it with merfish transcript data. Because the details of that processing may vary depending on the expression level of the gene and the signal-to-noise ratio of the sequential gene output, we do not implement those data integration steps within VPT.

Hi Tim,
Sounds great! Thanks a lot!
Do you have any advice on how to integrate the intensity info of the sequential genes into merfish transcript data? You mentioned that processing may vary depending on the expression level of the gene, and the signal-to-noise ratio. I wonder how we can use them to help with integration. Any advice is very appreciated!

As a first pass, I would recommend performing dimensionality reduction and clustering to create a projection of your data and using the sum-signal intensity as a label on the data. That will show if the sequential gene is expressed in the correct cell type / types and if the intensity is likely to be sufficient to distinguish positive vs. negative cells.
If plotting your data shows face validity, the next step would be to apply a model to your data, for example using a gaussian mixture model to assign your cells a probability of being positive vs negative for the gene of interest.

Thank you very much, Tim!  It helps a lot!
Best,
Christina


Edit conflicts between the same user

Description
I don't know if it's internet connection or what, but I pretty regularly have edits conflicts with edits I am newly saving. I think it has something to do with the edit being saved in the background, but the editor not registering it for some reason, which means I can re-save it. Regardless, it seems weird to have an edit conflict with myself.
Is there some way that the wording can be changed to something like "you have a conflict with your own edits" when it happens? Or better yet, can the newer edits just be saved over the older ones instead of forcing the person to pointlessly go through the review process when there's probably no reason for them to?
Screenshots

Huh, that’s definitely unexpected. iD doesn’t have the capability to save in the background like Potlatch 1 did. I noticed that one of your recent changesets include a way that you managed to modify twice in the same changeset using iD. That isn’t supposed to be possible, because saving a changeset in iD should automatically close it and redownload everything. I wonder if maybe the API call to close the changeset failed or there was some JavaScript error after saving.
What browser are you using? Do you have any possibly relevant extensions installed?

What browser are you using? Do you have any possibly relevant extensions installed?

As far as I know I'm just using stock Chrome without any extensions.


[nri-metadata-injection] Cert manager Documentation

Is your feature request related to a problem? Please describe.
We merged already a feature to support the certificate manager, however this is not well documented.
https://github.com/newrelic/helm-charts/pull/173
Describe the solution you'd like
We should properly document this feature and decide if it is possible (avoiding any breaking change) to make it the default configuration

The main issue is that we cannot know if the user has already installed the cert-manager or not.
We could add it as a dependency as we do for KSM, but I am not sure it would be recommended

Issue moved to newrelic/k8s-metadata-injection #174 via ZenHub


dair animation + logic

dair should cancel the player's upward momentum if they're moving up (to mimic shorthopping)


Moved /usr/home to /home for FreeBSD 14

Is this one still needed? The FreeBSD workflows triggered from multicoretests, e.g., this one https://ocaml-multicoretests.ci.dev:8100/job/2024-04-07/205112-ci-ocluster-build-48496f happily uses /home/opam AFAICS? :thinking:

@jmid Yes.  The workflows are running correctly as this commit is on the live branch.


Transferring locked tokens is broken

return self._transfer_locked_tokens(
          │    └ <function Stellar._transfer_locked_tokens at 0x117a381f0>
          └ Stellar(
              instance_name='foundation',
              network=<Network.STD: 'STD'>,
              address='GAB73WDASF6VKA6IVJQT5DTNG64CILPMAZH4OHXKXPK...

 File "/Users/rob/workspace/github.com/threefoldtech/js-sdk/jumpscale/clients/stellar/stellar.py", line 739, in _transfer_locked_tokens
   self._set_account_signers(escrow_kp.public_key, destination_address, preauth_tx_hash, escrow_kp)
   │    │                    │         │           │                    │                └ <stellar_sdk.keypair.Keypair object at 0x118b471c0>
   │    │                    │         │           │                    └ b'\x9f\xe84\x1f\xba\x82\xf1\x95#\x8f\xb3zoN\x81\xac\x83\xa9L\xbf[\x8c\x95\xb5\xddT\xb0\xd7\x123c\xab'
   │    │                    │         │           └ 'GC6KX4ZSKVMKH4PHXHAT6AOHZRUBWDYZ2TSPM5GBO64R6HJSJTSOELMO'
   │    │                    │         └ <property object at 0x11740e310>
   │    │                    └ <stellar_sdk.keypair.Keypair object at 0x118b471c0>
   │    └ <function Stellar._set_account_signers at 0x117a38310>
   └ Stellar(
       instance_name='foundation',
       network=<Network.STD: 'STD'>,
       address='GAB73WDASF6VKA6IVJQT5DTNG64CILPMAZH4OHXKXPK...

 File "/Users/rob/workspace/github.com/threefoldtech/js-sdk/jumpscale/clients/stellar/stellar.py", line 781, in _set_account_signers
   response = server.submit_transaction(tx)
              │      │                  └ <stellar_sdk.transaction_envelope.TransactionEnvelope object at 0x118b2c9a0>
              │      └ <function Server.submit_transaction at 0x117a1a790>
              └ <jumpscale.clients.stellar.wrapped.Server object at 0x1133bc640>

 File "/Users/rob/workspace/github.com/threefoldtech/js-sdk/jumpscale/clients/stellar/wrapped.py", line 41, in submit_transaction
   raise UnAuthorized(e.extras["envelope_xdr"])
         └ <class 'jumpscale.clients.stellar.exceptions.UnAuthorized'>

jumpscale.clients.stellar.exceptions.UnAuthorized: Unauthorized or not enough signatures for transaction envelope AAAAAgAAAABr+ZfF37qXDGCHq4oWmfEi/r1Cso1OVoAgFdYi0xMqyQAAASwCFF/CAAAAAgAAAAAAAAAAAAAAAwAAAAAAAAAFAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAAZ/oNB+6gvGVI4+zem9OgayDqUy/W4yVtd1UsNcSM2OrAAAAAQAAAAAAAAAFAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAAABAAAAALyr8zJVWKPx57nBPwHHzGgbDxnU5PZ0wXe5Hx0yTOTiAAAAAQAAAAAAAAAFAAAAAAAAAAAAAAAAAAAAAQAAAAEAAAABAAAAAgAAAAEAAAACAAAAAQAAAAIAAAAAAAAAAAAAAAAAAAAB0xMqyQAAAEDnb3wp0BWrPKDvRD4+GUwqRAMlcrciY4Wtr/PkcGTRPoxCylfHlbHSAG5z8FZ6SkNU1x2EcvGy2cjTsPGmF6gC

This only happens on production, not on the Stellar test network

half of the transaction builder instances are missing the network indication


Search not working

Do i need smth to make search working??I use latest theme.
I know that for Ghost i need to use GhostHunter....

exactly what he means when he says that does not work?
what is your blog url?

It simply nothing happens when i trying to search for smth.
http://blog.yurchenkov.ru/
Maybe i need to do some extra actions?

I have same problem. When I search for some text, it just refresh the right bar with posts, but nothing is filtered.

@painhardcore in your website in JavaScript console I see:
$ is not defined
read the release note => https://github.com/Kikobeats/uno-zen/releases/tag/2.5.2
In addition, (for @kotrfa) Ghost doesn't implement a search, so the current solution is based in a RSS scrapping. It's not perfect and in my opinion needs a good quantity of posts have results.


Custom builds stopped working in 2.8.4

Running the following command in 2.8.4:
grunt custom --exclude bitmaptext --split true

returns the following error:
Warning: Task "bitmaptext" not found. Use --force to continue.

Same as #321 ?

Use
grunt custom --exclude=bitmaptext --split true

I'll need to change the Grunt prompt.

Sorry, must have missed the other issue. Adding the equals sign fixes it.

Documented in 9173f9b.


Write xdist output on correct lines

This change improves the output when pytest-sugar is combined with pytest-xdist. Currently, when xdist is used, the reports aren't necessarily run in serial order, and sugar ends up generating a lot of extra lines. This PR allows sugar to move back up and add check marks to the correct line, so a new line doesn't need to be added. Since a picture is worth a thousand words:
Old:

New:

Current coverage is 74.67% (diff: 67.56%)

Merging #118 into master will decrease coverage by 0.27%

@@             master       #118   diff @@
==========================================
  Files             4          4
  Lines           443        458    +15
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
+ Hits            332        342    +10
- Misses          111        116     +5
  Partials          0          0

Powered by Codecov. Last update 00e9102...7ab7221

I would love to see this one merge!

at first glance this one looks beautiful
i wonder if a nice followup could be to ensure that the progress bar is only on one line
btw, pytest also gets this one "wrong" for the dot style output, but we dont plan to fix in core

I do like the idea of ensuring the progress bar is written to the bottom, but I agree it should probably be a follow-up so this PR doesn't grow too big in scope.

I just poke for the merge! Would realy realy love to see this :+1:

This is pretty nice 👍


[FEATURE REQUEST] BIDS Style Derivative Outputs

Is your feature request related to a problem? Please describe.
Even though there is no accepted BIDS derivative format for MRS, many of the files outputted actually can be changed to meet the BIDS derivative format.
Describe the solution you'd like
Perhaps having a flag which will output all of the pipeline derivatives in a BIDS derivative format.
Specifically:

The tabulated data produced per session could emulate the BIDS style suggested for phenotypic and assessment data
The NIFTI or imaging data like the masks or anatomical images could be renamed slightly.

We'll have to restructure the tissue maps provided by SPM12 to match BIDS style. This is mainly about moving the results into a different folder, renaming it, and making sure that Osprey finds them.

Solved in #491


Training scripts for CIFAR-10

Hi Akanimax, thanks for your great work!
Could you please also release the training scripts for CIFAR10 generation?

@GongXinyuu,
I have added the pytorch datasets options in this branch -> cifar_script. Please use the --pytorch_dataset=cifar-10 --dataset_dir=../data/cifar-10/ options for training on the CIFAR-10 dataset. I'll add it to master later.
Hope it helps.
Best regards,
@akanimax

Thank you very much!


Find all symbols always display no list

I don't know how the function find all symbols works.
It only can display list in file with several functions, it can't show once the functions get more. For example, I use it when I look in laravel source code.

Cannot reproduce. Please give the exact steps you do.

I just command+shift+o, it always keep the state.

@to2false Could we get the file?

Note there is a difference between workspace symbol search and document symbol search

In any case, there should be something unless the file is not empty.

Log output in the output panel, dev tools?

[Extension Host] ernel"},{"name":"prependMiddleware","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":189,"character":4},"end":{"line":196,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"pushMiddleware","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":204,"character":4},"end":{"line":211,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"bootstrap","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":218,"character":4},"end":{"line":223,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"dispatchToRouter","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":230,"character":4},"end":{"line":237,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"hasMiddleware","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":245,"character":4},"end":{"line":248,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"bootstrappers","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":255,"character":4},"end":{"line":258,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"reportException","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":266,"character":4},"end":{"line":269,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"renderException","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":278,"character":4},"end":{"line":281,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"getApplication","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":288,"character":4},"end":{"line":291,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"}],"id":65,"jsonrpc":"2.0"}Content-Type: application/vscode-jsonrpc; charset=utf8
Content-Length: 6857

{"result":[{"name":"Illuminate\\Foundation\\Http","kind":3,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":2,"character":10},"end":{"line":2,"character":36}}},"containerName":"Illuminate\\Foundation"},{"name":"Kernel","kind":5,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":13,"character":0},"end":{"line":292,"character":1}}},"containerName":"Illuminate\\Foundation\\Http"},{"name":"app","kind":7,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":20,"character":14},"end":{"line":20,"character":18}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"router","kind":7,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":27,"character":14},"end":{"line":27,"character":21}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"bootstrappers","kind":7,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":34,"character":14},"end":{"line":42,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"middleware","kind":7,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":49,"character":14},"end":{"line":49,"character":30}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"routeMiddleware","kind":7,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":56,"character":14},"end":{"line":56,"character":35}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"__construct","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":65,"character":4},"end":{"line":73,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"handle","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":81,"character":4},"end":{"line":102,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"sendRequestThroughRouter","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":110,"character":4},"end":{"line":122,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"terminate","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":131,"character":4},"end":{"line":149,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"gatherRouteMiddlewares","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":157,"character":4},"end":{"line":164,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"parseMiddleware","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":172,"character":4},"end":{"line":181,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"prependMiddleware","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":189,"character":4},"end":{"line":196,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"pushMiddleware","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":204,"character":4},"end":{"line":211,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"bootstrap","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":218,"character":4},"end":{"line":223,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"},{"name":"dispatchToRouter","kind":6,"location":{"uri":"file:\/\/\/Users\/juwai\/Projects\/juwai-com-v2\/vendor\/laravel\/framework\/src\/Illuminate\/Foundation\/Http\/Kernel.php","range":{"start":{"line":230,"character":4},"end":{"line":237,"character":5}}},"containerName":"Illuminate\\Foundation\\Http\\Kernel"}

[Extension Host] ernel"},{"name":"prependMiddleware","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":189,"character":4},"end":{"line":196,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"pushMiddleware","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":204,"character":4},"end":{"line":211,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"bootstrap","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":218,"character":4},"end":{"line":223,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"dispatchToRouter","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":230,"character":4},"end":{"line":237,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"hasMiddleware","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":245,"character":4},"end":{"line":248,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"bootstrappers","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":255,"character":4},"end":{"line":258,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"reportException","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":266,"character":4},"end":{"line":269,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"renderException","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":278,"character":4},"end":{"line":281,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"getApplication","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":288,"character":4},"end":{"line":291,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"}],"id":65,"jsonrpc":"2.0"}Content-Type: application/vscode-jsonrpc; charset=utf8
Content-Length: 6857
{"result":[{"name":"Illuminate\Foundation\Http","kind":3,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":2,"character":10},"end":{"line":2,"character":36}}},"containerName":"Illuminate\Foundation"},{"name":"Kernel","kind":5,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":13,"character":0},"end":{"line":292,"character":1}}},"containerName":"Illuminate\Foundation\Http"},{"name":"app","kind":7,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":20,"character":14},"end":{"line":20,"character":18}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"router","kind":7,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":27,"character":14},"end":{"line":27,"character":21}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"bootstrappers","kind":7,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":34,"character":14},"end":{"line":42,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"middleware","kind":7,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":49,"character":14},"end":{"line":49,"character":30}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"routeMiddleware","kind":7,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":56,"character":14},"end":{"line":56,"character":35}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"__construct","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":65,"character":4},"end":{"line":73,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"handle","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":81,"character":4},"end":{"line":102,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"sendRequestThroughRouter","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":110,"character":4},"end":{"line":122,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"terminate","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":131,"character":4},"end":{"line":149,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"gatherRouteMiddlewares","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":157,"character":4},"end":{"line":164,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"parseMiddleware","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":172,"character":4},"end":{"line":181,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"prependMiddleware","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":189,"character":4},"end":{"line":196,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"pushMiddleware","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":204,"character":4},"end":{"line":211,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"bootstrap","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":218,"character":4},"end":{"line":223,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"},{"name":"dispatchToRouter","kind":6,"location":{"uri":"file:///Users/juwai/Projects/juwai-com-v2/vendor/laravel/framework/src/Illuminate/Foundation/Http/Kernel.php","range":{"start":{"line":230,"character":4},"end":{"line":237,"character":5}}},"containerName":"Illuminate\Foundation\Http\Kernel"}

It's easy to stop at a point.

I notice same behaviour as OP but on workspace symbols search. File symbol search always works as expected here.

Closing as inactive, wrong repo and not enough info


Bugfix/scheduler SKU net

这个 PR 实现什么功能/修复什么问题:

调度器根据 sku 过滤 host, 如果没有指定 zone ，则按 region 匹配
只给 onecloud 的宿主机 fill onecloud vpc networks

是否需要 backport 到之前的 release 分支:

3.4
/area scheduler
/cc @ioito @swordqiu @yousong

Codecov Report

Merging #9352 (a78c565) into master (84f02c1) will decrease coverage by 1.88%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master   #9352       +/-   ##
==========================================
- Coverage    5.84%   3.95%    -1.89%
==========================================
  Files         837     170      -667
  Lines      130166   25163   -105003
==========================================
- Hits         7602     995     -6607
+ Misses     121877   24056    -97821
+ Partials      687     112      -575

Flag
Coverage Δ

aFlag
3.95% <ø> (-1.89%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

pkg/appsrv/handlerinfo.go

pkg/hostman/isolated_device/isolated_device.go

pkg/multicloud/aws/dbinstance_snapshot.go

pkg/util/fileutils2/size.go

pkg/keystone/models/localusers.go

pkg/util/samlutils/instance.go

pkg/keystone/models/assignments.go

pkg/compute/models/elasticcacheresource.go

pkg/compute/models/instance_snapshot_joint.go

pkg/util/printutils/printobj.go

... and 657 more

Continue to review full report at Codecov.

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


webpack plugin for sw-build

R: @jeffposnick @addyosmani @gauntface
This PR has the webpack plugin for sw-build. I am working to add tests as well.
The index file is just a very minimal wrapper over sw-build, making fallbacks to webpack environment values where ever possible.

Config changes LGTM. Are we going to add a test for the Webpack plugin so we know the interface between it and sw-build doesn't break over time? Fwiw, did this with the preload plugin and didn't find it too bad to orchestrate Webpack's compiler for tests.

Ignore AppVeyor errors for now - it's a total mess :(

@gauntface @addyosmani this PR now contains tests and changes for injectManifestFile

@gauntface I see a test of sw-cli is broken

cc @goldhand @thelarkinn in case there are any Webpack plugin best practices we're missing out on here.

@gauntface What's the process for getting an npm package of this published using our current setup? Are we manually publishing each one?

@prateekbh Nice work on getting this done. Can you update the thread on build system integration to share this is now available and seek any additional feedback that might be useful?
@jpmedley fyi on the Webpack plugin now landing.


Zahi/slice reduce rebased

Test passing with fast/slow path reduce, I need to do more testing though. Not ready for merge.


Add SC Metrics

With the removal of the SC upcoming I'm not sure if this is needed at this point.

With the removal of the SC upcoming I'm not sure if this is needed at this point.

Ack, closing this issue.


address clippy lints

Fix the clippy warnings that appear when running cargo clippy on linux. There may be other warnings on windows and/or macos.

Great! Thanks

Yeah, maybe I should have clippy running on the other platforms also


added-my-readme

What type of PR is this? (check all applicable)

[x] 🚀 Added Name
[ ] ✨ Feature
[ ] ✅ Joined Community
[ ] 🌟 ed the repo
[ ] 🐛 Grammatical Error
[ ] 📝 Documentation Update
[ ] 🚩 Other

Description
Add Link of GitHub Profile

@akhilesh-w Please create an issue :)


Add tests for sigmoid_focal_loss and generalized_box_iou_loss

🚀 The feature
The sigmoid_focal_loss and generalized_box_iou_loss ops are not currently tested. We should create the necessary unit-tests that check the validity for multiple input types.

This will also help folks working on Ciou ad Diou loss. @YosuaMichael I can work on this if you like :)
Reference tests fvcore
https://github.com/facebookresearch/fvcore/blob/main/tests/test_giou_loss.py

Thanks @oke-aditya for the link.

Hi @oke-aditya thanks for the offer! Is there anything urgent that need this test?
Currently I actually do this task for the sake of learning (since I am new and it would be good to touch as many part of the code as possible), hence I would like to do this issues myself if possible, however it would take more times.

This issue is done with #5783 and #5792


Update dependencies & minor cleanups on code

Fix #000 (<-- Add issue number here)
IMPORTANT: Each pull request (PR) should resolve an issue. Please create the issue if it hasn't been created, unless you're fixing typos or making minor changes to documentation or infrastructure. In that case, just leave the issue number as #000.
Details
If the PR title isn't enough to describe your PR, please provide details here.
Checks
Make sure these boxes are checked before your PR is ready to be reviewed and merged. Thanks!

[x] PR is concisely and descriptively titled 📑 and links to the original issue 🔗.
[x] Code is in uniquely-named feature branch and has no merge conflicts 📁.
[x] Tests pass -- look for a green checkbox ✔ a few minutes after opening your PR.
[ ] @mentions of the person or team responsible for reviewing proposed changes. By default, use @BadwaterBay/reviewers.
[ ] (Optional) Screenshots/GIFs are attached 📎 in case of UI updates.

We're happy to help you get this ready. Don't be afraid to ask for help, and don't be discouraged if your tests fail at first.

Thank you for contributing to this project!

Codecov Report

Merging #107 into master will decrease coverage by 0.04%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master     #107      +/-   ##
==========================================
- Coverage   90.45%   90.40%   -0.05%
==========================================
  Files           7        7
  Lines         199      198       -1
  Branches       18       18
==========================================
- Hits          180      179       -1
  Misses         15       15
  Partials        4        4

Impacted Files
Coverage Δ

src/app.py
0.00% <ø> (ø)

src/core/distancematrix/google_distance_matrix.py
100.00% <ø> (ø)

src/core/find_route.py
89.15% <100.00%> (ø)

src/core/get_distance_matrix.py
82.60% <100.00%> (ø)

Continue to review full report at Codecov.

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


Add builtin modules with node: prefix

Closes #13290

What kind of change does this PR introduce?
Support node: prefix for builtin modules
Did you add tests for your changes?
@alexander-akait what tests would you suggest here?
Does this PR introduce a breaking change?
I guess not, since this is now a feature of Node.js?
What needs to be documented once your changes are merged?
Not sure this needs to be documented, but happy to be corrected here.

@sokra Ok thanks for the hint. Can you provide some guidance as to what a test case would look like? And where I would add this test case?

@karlhorky You can put this here https://github.com/webpack/webpack/tree/master/test/configCases/target and add require/import with node prefix

@alexander-akait ok I spent 10 minutes looking at the things in that folder, but I don't know what you mean.
I ended up just guessing that you mean doing something like this: 12108b3 (#13311)

So this feature is about to get more usage: the node: scheme / prefix / protocol was backported to Node.js 14.13.1 / 12.20.0 🎉
https://nodejs.org/api/esm.html -> link "node: Imports" (links with anchors don't scroll properly right now)

An alternative to the approaches in #13311 and #12693 would be to use is-core-module (which was split from resolve in browserify/resolve@7c26483), so that this list doesn't need to be maintained and tested by webpack itself.

Done here https://github.com/webpack/webpack/pull/12693, sorry for delay

No worries, thanks for this!


signature versions should match the downloaded ones

@Wribbe : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


Can no longer build logspout-kinesis due to AWS library change

When I run docker build, I now get:
# github.com/remind101/logspout-kinesis
../../remind101/logspout-kinesis/stream.go:39: cannot use aws.Config literal (type *aws.Config) as type client.ConfigProvider in argument to kinesis.New:
        *aws.Config does not implement client.ConfigProvider (missing ClientConfig method)

It looks like AWS broke backwards compatibility in its recent release. This comment sheds more light on the issue.

@crohr Should be fixed by #23. Thanks for reporting!