catkin_make error on ubuntu 16.04 + ROS kinetic

I try to make this package and get the following error:
[ 66%] Building CXX object LeGO-LOAM/LeGO-LOAM/CMakeFiles/mapOptmization.dir/src/mapOptmization.cpp.o
In file included from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:36:0:
/usr/local/include/gtsam/geometry/Rot3.h: In static member function ‘static gtsam::Rot3 gtsam::Rot3::rodriguez(double, double, double)’:
/usr/local/include/gtsam/geometry/Rot3.h:197:51: error: no matching function for call to ‘gtsam::Rot3::rodriguez(Eigen::CommaInitializer<Eigen::Matrix<double, -1, 1> >&)’
{ return rodriguez((Vector(3) << wx, wy, wz));}
^
/usr/local/include/gtsam/geometry/Rot3.h:164:17: note: candidate: static gtsam::Rot3 gtsam::Rot3::rodriguez(const Vector&, double)
static Rot3 rodriguez(const Vector& w, double theta);
^
/usr/local/include/gtsam/geometry/Rot3.h:164:17: note:   candidate expects 2 arguments, 1 provided
/usr/local/include/gtsam/geometry/Rot3.h:172:17: note: candidate: static gtsam::Rot3 gtsam::Rot3::rodriguez(const gtsam::Point3&, double)
static Rot3 rodriguez(const Point3& w, double theta);
^
/usr/local/include/gtsam/geometry/Rot3.h:172:17: note:   candidate expects 2 arguments, 1 provided
/usr/local/include/gtsam/geometry/Rot3.h:180:17: note: candidate: static gtsam::Rot3 gtsam::Rot3::rodriguez(const gtsam::Unit3&, double)
static Rot3 rodriguez(const Unit3& w, double theta);
^
/usr/local/include/gtsam/geometry/Rot3.h:180:17: note:   candidate expects 2 arguments, 1 provided
/usr/local/include/gtsam/geometry/Rot3.h:187:17: note: candidate: static gtsam::Rot3 gtsam::Rot3::rodriguez(const Vector&)
static Rot3 rodriguez(const Vector& v);
^
/usr/local/include/gtsam/geometry/Rot3.h:187:17: note:   no known conversion for argument 1 from ‘Eigen::CommaInitializer<Eigen::Matrix<double, -1, 1> >’ to ‘const Vector& {aka const Eigen::Matrix<double, -1, 1>&}’
/usr/local/include/gtsam/geometry/Rot3.h:196:17: note: candidate: static gtsam::Rot3 gtsam::Rot3::rodriguez(double, double, double)
static Rot3 rodriguez(double wx, double wy, double wz)
^
/usr/local/include/gtsam/geometry/Rot3.h:196:17: note:   candidate expects 3 arguments, 1 provided
In file included from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:37:0:
/usr/local/include/gtsam/geometry/Pose3.h: In static member function ‘static gtsam::Matrix gtsam::Pose3::wedge(double, double, double, double, double, double)’:
/usr/local/include/gtsam/geometry/Pose3.h:226:28: error: could not convert ‘(&(&(&(&(&(&(&(&(&(&(&(&(&(& Eigen::DenseBase::operator<<(const Scalar&) with Derived = Eigen::Matrix<double, -1, -1>; Eigen::DenseBase::Scalar = double.Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >((- wz)))->Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >(wy))->Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >(vx))->Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >(wz))->Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >(0.0))->Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >((- wx)))->Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >(vy))->Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >((- wy)))->Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >(wx))->Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >(0.0))->Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >(vz))->Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >(0.0))->Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >(0.0))->Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >(0.0))->Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, -1> >(0.0)’ from ‘Eigen::CommaInitializer<Eigen::Matrix<double, -1, -1> >’ to ‘gtsam::Matrix {aka Eigen::Matrix<double, -1, -1>}’
0.,  0.,  0.,  0.);
^
In file included from /usr/local/include/gtsam/nonlinear/NonlinearFactorGraph.h:24:0,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:40:
/usr/local/include/gtsam/geometry/Point2.h: In static member function ‘static gtsam::Vector gtsam::Point2::Logmap(const gtsam::Point2&)’:
/usr/local/include/gtsam/geometry/Point2.h:175:86: error: could not convert ‘Eigen::DenseBase::operator<<(const Scalar&) [with Derived = Eigen::Matrix<double, -1, 1>; Eigen::DenseBase::Scalar = double]((& dp)->gtsam::Point2::x()).Eigen::CommaInitializer::operator,<Eigen::Matrix<double, -1, 1> >((& dp)->gtsam::Point2::y())’ from ‘Eigen::CommaInitializer<Eigen::Matrix<double, -1, 1> >’ to ‘gtsam::Vector {aka Eigen::Matrix<double, -1, 1>}’
static inline Vector Logmap(const Point2& dp) { return (Vector(2) << dp.x(), dp.y()); }
^
In file included from /usr/local/include/gtsam/base/SymmetricBlockMatrix.h:22:0,
from /usr/local/include/gtsam/linear/HessianFactor.h:21,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h: In instantiation of ‘class gtsam::SymmetricBlockMatrixBlockExprgtsam::SymmetricBlockMatrix’:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h:118:62:   required from here
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h:62:59: error: no type named ‘Index’ in ‘struct Eigen::internal::traits<gtsam::SymmetricBlockMatrixBlockExprgtsam::SymmetricBlockMatrix >’
typedef typename Eigen::internal::traits::Index Index;
^
In file included from /usr/local/include/gtsam/linear/HessianFactor.h:21:0,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h: In member function ‘gtsam::SymmetricBlockMatrix::Block gtsam::SymmetricBlockMatrix::operator()(gtsam::DenseIndex, gtsam::DenseIndex)’:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h:119:43: error: no matching function for call to ‘gtsam::SymmetricBlockMatrixBlockExprgtsam::SymmetricBlockMatrix::SymmetricBlockMatrixBlockExpr(gtsam::SymmetricBlockMatrix&, gtsam::DenseIndex&, gtsam::DenseIndex&)’
return Block(*this, i_block, j_block);
^
In file included from /usr/local/include/gtsam/base/SymmetricBlockMatrix.h:22:0,
from /usr/local/include/gtsam/linear/HessianFactor.h:21,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h:46:9: note: candidate: constexpr gtsam::SymmetricBlockMatrixBlockExprgtsam::SymmetricBlockMatrix::SymmetricBlockMatrixBlockExpr(const gtsam::SymmetricBlockMatrixBlockExprgtsam::SymmetricBlockMatrix&)
class SymmetricBlockMatrixBlockExpr : public Eigen::EigenBase<SymmetricBlockMatrixBlockExpr >
^
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h:46:9: note:   candidate expects 1 argument, 3 provided
In file included from /usr/local/include/gtsam/base/SymmetricBlockMatrix.h:22:0,
from /usr/local/include/gtsam/linear/HessianFactor.h:21,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h: In instantiation of ‘class gtsam::SymmetricBlockMatrixBlockExpr’:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h:124:73:   required from here
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h:62:59: error: no type named ‘Index’ in ‘struct Eigen::internal::traits<gtsam::SymmetricBlockMatrixBlockExpr >’
typedef typename Eigen::internal::traits::Index Index;
^
In file included from /usr/local/include/gtsam/linear/HessianFactor.h:21:0,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h: In member function ‘gtsam::SymmetricBlockMatrix::constBlock gtsam::SymmetricBlockMatrix::operator()(gtsam::DenseIndex, gtsam::DenseIndex) const’:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h:125:48: error: no matching function for call to ‘gtsam::SymmetricBlockMatrixBlockExpr::SymmetricBlockMatrixBlockExpr(const gtsam::SymmetricBlockMatrix&, gtsam::DenseIndex&, gtsam::DenseIndex&)’
return constBlock(*this, i_block, j_block);
^
In file included from /usr/local/include/gtsam/base/SymmetricBlockMatrix.h:22:0,
from /usr/local/include/gtsam/linear/HessianFactor.h:21,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h:46:9: note: candidate: constexpr gtsam::SymmetricBlockMatrixBlockExpr::SymmetricBlockMatrixBlockExpr(const gtsam::SymmetricBlockMatrixBlockExpr&)
class SymmetricBlockMatrixBlockExpr : public Eigen::EigenBase<SymmetricBlockMatrixBlockExpr >
^
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h:46:9: note:   candidate expects 1 argument, 3 provided
In file included from /usr/local/include/gtsam/linear/HessianFactor.h:21:0,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h: In member function ‘gtsam::SymmetricBlockMatrix::Block gtsam::SymmetricBlockMatrix::range(gtsam::DenseIndex, gtsam::DenseIndex, gtsam::DenseIndex, gtsam::DenseIndex)’:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h:134:107: error: no matching function for call to ‘gtsam::SymmetricBlockMatrixBlockExprgtsam::SymmetricBlockMatrix::SymmetricBlockMatrixBlockExpr(gtsam::SymmetricBlockMatrix&, gtsam::DenseIndex&, gtsam::DenseIndex&, gtsam::DenseIndex, gtsam::DenseIndex)’
return Block(*this, i_startBlock, j_startBlock, i_endBlock - i_startBlock, j_endBlock - j_startBlock);
^
In file included from /usr/local/include/gtsam/base/SymmetricBlockMatrix.h:22:0,
from /usr/local/include/gtsam/linear/HessianFactor.h:21,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h:46:9: note: candidate: constexpr gtsam::SymmetricBlockMatrixBlockExprgtsam::SymmetricBlockMatrix::SymmetricBlockMatrixBlockExpr(const gtsam::SymmetricBlockMatrixBlockExprgtsam::SymmetricBlockMatrix&)
class SymmetricBlockMatrixBlockExpr : public Eigen::EigenBase<SymmetricBlockMatrixBlockExpr >
^
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h:46:9: note:   candidate expects 1 argument, 5 provided
In file included from /usr/local/include/gtsam/linear/HessianFactor.h:21:0,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h: In member function ‘gtsam::SymmetricBlockMatrix::constBlock gtsam::SymmetricBlockMatrix::range(gtsam::DenseIndex, gtsam::DenseIndex, gtsam::DenseIndex, gtsam::DenseIndex) const’:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h:143:112: error: no matching function for call to ‘gtsam::SymmetricBlockMatrixBlockExpr::SymmetricBlockMatrixBlockExpr(const gtsam::SymmetricBlockMatrix&, gtsam::DenseIndex&, gtsam::DenseIndex&, gtsam::DenseIndex, gtsam::DenseIndex)’
return constBlock(*this, i_startBlock, j_startBlock, i_endBlock - i_startBlock, j_endBlock - j_startBlock);
^
In file included from /usr/local/include/gtsam/base/SymmetricBlockMatrix.h:22:0,
from /usr/local/include/gtsam/linear/HessianFactor.h:21,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h:46:9: note: candidate: constexpr gtsam::SymmetricBlockMatrixBlockExpr::SymmetricBlockMatrixBlockExpr(const gtsam::SymmetricBlockMatrixBlockExpr&)
class SymmetricBlockMatrixBlockExpr : public Eigen::EigenBase<SymmetricBlockMatrixBlockExpr >
^
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h:46:9: note:   candidate expects 1 argument, 5 provided
In file included from /usr/local/include/gtsam/linear/HessianFactor.h:21:0,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h: In member function ‘gtsam::SymmetricBlockMatrix::Block gtsam::SymmetricBlockMatrix::full()’:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h:149:42: error: no matching function for call to ‘gtsam::SymmetricBlockMatrixBlockExprgtsam::SymmetricBlockMatrix::SymmetricBlockMatrixBlockExpr(gtsam::SymmetricBlockMatrix&, int, gtsam::DenseIndex, int)’
return Block(this, 0, nBlocks(), 0);
^
In file included from /usr/local/include/gtsam/base/SymmetricBlockMatrix.h:22:0,
from /usr/local/include/gtsam/linear/HessianFactor.h:21,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h:46:9: note: candidate: constexpr gtsam::SymmetricBlockMatrixBlockExprgtsam::SymmetricBlockMatrix::SymmetricBlockMatrixBlockExpr(const gtsam::SymmetricBlockMatrixBlockExprgtsam::SymmetricBlockMatrix&)
class SymmetricBlockMatrixBlockExpr : public Eigen::EigenBase<SymmetricBlockMatrixBlockExpr >
^
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h:46:9: note:   candidate expects 1 argument, 4 provided
In file included from /usr/local/include/gtsam/linear/HessianFactor.h:21:0,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h: In member function ‘gtsam::SymmetricBlockMatrix::constBlock gtsam::SymmetricBlockMatrix::full() const’:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h:155:47: error: no matching function for call to ‘gtsam::SymmetricBlockMatrixBlockExpr::SymmetricBlockMatrixBlockExpr(const gtsam::SymmetricBlockMatrix&, int, gtsam::DenseIndex, int)’
return constBlock(this, 0, nBlocks(), 0);
^
In file included from /usr/local/include/gtsam/base/SymmetricBlockMatrix.h:22:0,
from /usr/local/include/gtsam/linear/HessianFactor.h:21,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h:46:9: note: candidate: constexpr gtsam::SymmetricBlockMatrixBlockExpr::SymmetricBlockMatrixBlockExpr(const gtsam::SymmetricBlockMatrixBlockExpr&)
class SymmetricBlockMatrixBlockExpr : public Eigen::EigenBase<SymmetricBlockMatrixBlockExpr >
^
/usr/local/include/gtsam/base/SymmetricBlockMatrixBlockExpr.h:46:9: note:   candidate expects 1 argument, 4 provided
In file included from /usr/local/include/gtsam/linear/HessianFactor.h:21:0,
from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h: In member function ‘Eigen::SelfAdjointView<const Eigen::Matrix<double, -1, -1>, 2u> gtsam::SymmetricBlockMatrix::matrix() const’:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h:161:14: error: could not convert ‘((const gtsam::SymmetricBlockMatrix)this)->gtsam::SymmetricBlockMatrix::matrix_’ from ‘const Matrix {aka const Eigen::Matrix<double, -1, -1>}’ to ‘Eigen::SelfAdjointView<const Eigen::Matrix<double, -1, -1>, 2u>’
return matrix_;
^
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h: In member function ‘Eigen::SelfAdjointView<Eigen::Matrix<double, -1, -1>, 2u> gtsam::SymmetricBlockMatrix::matrix()’:
/usr/local/include/gtsam/base/SymmetricBlockMatrix.h:167:14: error: could not convert ‘((gtsam::SymmetricBlockMatrix)this)->gtsam::SymmetricBlockMatrix::matrix_’ from ‘gtsam::Matrix {aka Eigen::Matrix<double, -1, -1>}’ to ‘Eigen::SelfAdjointView<Eigen::Matrix<double, -1, -1>, 2u>’
return matrix_;
^
In file included from /usr/local/include/gtsam/linear/GaussianFactorGraph.h:28:0,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizerParams.h:23,
from /usr/local/include/gtsam/nonlinear/NonlinearOptimizer.h:22,
from /usr/local/include/gtsam/nonlinear/LevenbergMarquardtOptimizer.h:21,
from /home/wangbx/catkin_ws/src/LeGO-LOAM/LeGO-LOAM/src/mapOptmization.cpp:41:
/usr/local/include/gtsam/linear/HessianFactor.h: In member function ‘double gtsam::HessianFactor::constantTerm() const’:
/usr/local/include/gtsam/linear/HessianFactor.h:287:79: error: no match for call to ‘(gtsam::SymmetricBlockMatrix::constBlock {aka gtsam::SymmetricBlockMatrixBlockExpr}) (int, int)’
double constantTerm() const { return info_(this->size(), this->size())(0,0); }
^
/usr/local/include/gtsam/linear/HessianFactor.h: In member function ‘double& gtsam::HessianFactor::constantTerm()’:
/usr/local/include/gtsam/linear/HessianFactor.h:292:74: error: no match for call to ‘(gtsam::SymmetricBlockMatrix::Block {aka gtsam::SymmetricBlockMatrixBlockExprgtsam::SymmetricBlockMatrix}) (int, int)’
double& constantTerm() { return info_(this->size(), this->size())(0,0); }
^
LeGO-LOAM/LeGO-LOAM/CMakeFiles/mapOptmization.dir/build.make:62: recipe for target 'LeGO-LOAM/LeGO-LOAM/CMakeFiles/mapOptmization.dir/src/mapOptmization.cpp.o' failed
make[2]: *** [LeGO-LOAM/LeGO-LOAM/CMakeFiles/mapOptmization.dir/src/mapOptmization.cpp.o] Error 1
CMakeFiles/Makefile2:3321: recipe for target 'LeGO-LOAM/LeGO-LOAM/CMakeFiles/mapOptmization.dir/all' failed
make[1]: *** [LeGO-LOAM/LeGO-LOAM/CMakeFiles/mapOptmization.dir/all] Error 2
Makefile:138: recipe for target 'all' failed
make: *** [all] Error 2
Invoking "make -j1" failed
what's the problem and how to do?Thx

Hi, I have the same error, do you have known how to do ? Thx

Hi, any update on this? Updating to boost 1.68 helped in building gtsam. But other packages fail which depend on boost 1.58.
Is there a particular version/release of gtsam that was used to build lego loam?

Hi, I solved it by re-download gtsam,  maybe you can try it:
$ cd
$ git clone https://bitbucket.org/gtborg/gtsam.git
$ cd gtsam
$ mkdir build
$ cd build
$ cmake ..
$ make check
$ make install

Hi, any update on this? Updating to boost 1.68 helped in building gtsam. But other packages fail which depend on boost 1.58.
Is there a particular version/release of gtsam that was used to build lego loam?

Hi, any update on this? Updating to boost 1.68 helped in building gtsam. But other packages fail which depend on boost 1.58.
Is there a particular version/release of gtsam that was used to build lego loam?

Hello, this problem has been solved. The solution is provided by liuxiaonan123. We only need to download the gtsam-4.0 source code and compile and install it to solve this problem.

Hi, I solved it by re-download gtsam, maybe you can try it:
$ cd
$ git clone https://bitbucket.org/gtborg/gtsam.git
$ cd gtsam
$ mkdir build
$ cd build
$ cmake ..
$ make check
$ make install

Yes, this problem is solved by upgrading gtsam to version 4. Thank you very much.

Hi all,
I'm having the same error as @XuanboWang .
I did what @liuxiaonan123 said. But I had to install it as admin.
Then, when I try to compile the ROS package I have the next error:
-- +++ processing catkin package: 'lego_loam'
-- ==> add_subdirectory(LeGO-LOAM/LeGO-LOAM)
-- Using these message generators: gencpp;geneus;genlisp;gennodejs;genpy
CMake Error at /usr/share/cmake-3.5/Modules/CMakeFindDependencyMacro.cmake:45 (message):
  Invalid arguments to find_dependency
Call Stack (most recent call first):
  /usr/local/lib/cmake/GTSAM/GTSAMConfig.cmake:17 (find_dependency)
  LeGO-LOAM/LeGO-LOAM/CMakeLists.txt:23 (find_package)

-- Configuring incomplete, errors occurred!
See also "/home/silth/WS/jaguar_ws/build/CMakeFiles/CMakeOutput.log".
See also "/home/silth/WS/jaguar_ws/build/CMakeFiles/CMakeError.log".
Invoking "cmake" failed

What can I do?

@grafoteka Hello.I have the same error as yours.Do  you have know how to solve it? Thanks.


feat: Optimize completion range field

improve #71060
The ISuggestDataDto should also be able to compress the range field？

{
  startLineNumber: 1,
  startColumn: 2,
  endLineNumber: 3,  -- convert -> [1,2,3,4]
  endColumn: 4,
}

Thanks so far.
Did you, by any chance, do some measurements about how much this improves receiving large IntelliSense data? Also, a further improvement would be not send the range when an items range is the default value (e.g the range that's computed on the renderer already). Further geek-out would be have the array as [startColumn, endColumn, startLine, (optional) endLine]  and leave the endLine out if it's the same as the startLine (which is almost always is)


Add UBO TileMap example

Here's the first graf from the README:

This example shows a shader-driven, Uniform Buffer Object (UBO)-backed scrolling tilemap, akin to what is seen in 2D, tile-based games. The tiles are rendered on a single OpenGL plane mesh, with each vertex referencing data in a UBO. The contents of the UBO are updated, as the user "scrolls" around the tilemap, with fragment shader logic determining it's current tile and appropriate offset, which is used to discover the fragment color to be displayed. As a bonus, basic lighting formation is also contained in the UBO data.

I have a youtube video of this example in action.
 Let me know what you'd like me to clean up so this can land.
Thanks!

build failure seems unrelated:
Build failed, waiting for other jobs to finish...
Could not document `lazy_static`.
Caused by:
  Process didn't exit successfully: `rustdoc /home/travis/.cargo/registry/src/github.com-0a35038f75765ae4/lazy_static-0.1.14/src/lib.rs --crate-name lazy_static -o /home/travis/build/gfx-rs/gfx/target/doc -L dependency=/home/travis/build/gfx-rs/gfx/target/debug/deps -L dependency=/home/travis/build/gfx-rs/gfx/target/debug/deps` (exit code: 101)
--- stderr
thread '<unnamed>' panicked at 'failed to generate documentation: File exists (os error 17)', ../src/librustdoc/lib.rs:293
thread '<main>' panicked at 'called `Result::unwrap()` on an `Err` value: Any', ../src/libcore/result.rs:731

Rebuilding it seemed to clear the error. So maybe there is a race in how we are building gfx on travis.

Overall this is a pretty neat demo. Other then a few nits, it LGTM.

@csherratt thanks! I will address the feedback and push up changes later today.

:+1:! I'm not able to look at the code from where I am right now but I saw the video and it looks great!
I think we need More "pratical" examples like this, maybe even a game soon :)

Thanks @olsonjeffery ! I skimmed through the code, put some notes, but overall it looks good.
One thing being not clear to me is why using UBO here in the first place? You are essentially using it as a 2D texture, so why not expressing it explicitly as such?

One thing being not clear to me is why using UBO here in the first place? You are essentially using it as a 2D texture, so why not expressing it explicitly as such?

@kvark I think dynamically generating a texture in application code/memory and then copying a subset of the texture into video memory every time the tile offset changes is going to be very slow in comparison? Also, you'd be placing a much lower ceiling on how large of a tilemap you could generate if you're generating and keeping a huge texture in application memory (also with this UBO approach you can store arbitrary, per-tile metadata like lighting-level-and-tint, visibility, etc to drive shader logic)
In this case, the a_BufPos passed into the vertex program and varied through to the frag shader is a fixed pointer to a cell in the UBO, whose contents are better suited to be updated frequently by the applicaton, IMO. I'll yield that you know much more about the semantics and implications of this stuff than I do, but this is my impression and experience.
Also, as a small bit of appeal-to-authority: I actually discussed the "generate a huge texture and copy a subset to the GPU as needed" approach with an acquaintance of mine who does a lot of AAA gamedev consulting, and he explained the approached used in this example to me (this technique is actually called a "character map" and it goes back to console programming on constrained systems like GBA, NDS, SNES, etc). After reasoning through and implementing, I personally feel like its a much more efficient way to approach the problem, and it gives you a lot more control.

@olsonjeffery I didn't have a large texture in mind. I was thinking about using a small texture for exactly the same purpose as your UBO but with 2D indexing. Assuming you'd rewrite it every frame and seeing that the data you store is just vec4 anyways. Really though, there is nothing wrong with your approach ;) We'll be happy to merge once you address @csherratt's suggestions.

@kvark hah, yeah! other examples I've seen have taken that approach (particularly this example using SFML/C++ ), but the programatic texture API stuff looked pretty hairy, so I ended up just doing in this direction :) . Maybe I can follow-up with that sort of approach to get more comfortable with that part of the API.

updates have been made. should be gtg.

@homu r+

:pushpin: Commit 6e66d24 has been approved by kvark

:hourglass: Testing commit 6e66d24 with merge 9bddd98...

:sunny: Test successful - status


Implement use of linting rule set for Carrier Billing API

Problem description
Implement use of linting rule set for Carrier Billing API.
what we have to do is well documented in Commonalities:
https://github.com/camaraproject/Commonalities/pull/110
https://github.com/camaraproject/Commonalities/pull/74
Expected action
Check our API with linting rule set
provide feedback to commonalities team
Additional context
cc: @rartych who asked project volunteer to perform this action.

Linter rules output: https://github.com/PedroDiez/CarrierBillingCheckOut/actions/runs/7642915617/job/20823677108?pr=1
Main topics are API spec errors needed to be fixed. Take advantage of https://github.com/camaraproject/CarrierBillingCheckOut/pull/134 to deal with them

Re-open explicitly issue, as want to check intermediate outputs

Considerations/Feedback:

130:7     error  oas3-valid-media-example          "status" property type must be string: Do not get the result of this output and if any actions required

**131:13    error  camara-parameter-casing-convention  /payments should be kebab-case: must be kebab case  **: False positive. It appears several times. No action required

135:13  warning  oas3-operation-security-defined     "carrier-billing:payments:create" must be listed among scopes.                                                                    paths./payments.post.security[0].openId[0]: Same as in Blockchain, rule removed. This error appears several times (one per API scope). No actions required

151:23    error  oas3-valid-media-example            "status" property type must be string                                                                                paths./payments.post.callbacks.notifications: Do not get the result of this output and if any actions required

192:9     error  parser                              Mapping key must be a string scalar rather than number                                                                            paths./payments.post.responses[201]: Appears many times, do not see the action point here

1210:21    error  oas3-valid-media-example            "status" property type must be string                                                                                components.responses.Generic400.content.application/json.example.status: Appears several times in different scenarios. "status" is an integer as per commonalities. Do not see the action here

Warnings with no impact in API Spec

Please @rartych when you can, in order on how to proceed with topics: i, iv, v and vi

Linter according to 31/JAN config applied:
https://github.com/camaraproject/Commonalities/commit/29e4e9da8b8ca7dd0e435fb8a942ac4ba3952b59
Pending to check output:
https://github.com/PedroDiez/CarrierBillingCheckOut/actions/runs/7759600592/job/21163998825?pr=1

Update the files from the PR. and test them. Test today 07/FEB

Spec errors:

`
[spectral] documentation/SupportingDocuments/carrier_billing_payment.yaml - ERROR - 1 error(s)
--Error detail:
/github/workspace/documentation/SupportingDocuments/carrier_billing_payment.yaml
26:10   warning  camara-routes-description             Functionality method description Warning: Each method should have description.                                                      paths./payments.post
26:10   warning  operation-description                 Operation "description" must be present and non-empty string.                                                                       paths./payments.post
32:9   warning  operation-tag-defined                 Operation tags must be defined in global tags.                                                                                paths./payments.post.tags[0]
43:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments.post.responses[201]
49:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments.post.responses[400]
60:29     error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments.post.responses[400].content.application/json.examples.Generic400.value.status
66:29     error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments.post.responses[400].content.application/json.examples.wrongCurrency.value.status
72:29     error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments.post.responses[400].content.application/json.examples.duplicateClientCorrelator.value.status
78:29     error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments.post.responses[400].content.application/json.examples.unauthorizedAmount.value.status
80:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments.post.responses[401]
86:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments.post.responses[403]
92:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments.post.responses[409]
98:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments.post.responses[500]
104:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments.post.responses[503]
116:9   warning  operation-tag-defined                 Operation tags must be defined in global tags.                                                                                paths./payments.get.tags[0]
125:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments.get.responses[200]
126:26    error  no-$ref-siblings                      $ref must not be placed next to any other properties                                                                                paths./payments.get.responses[200].description
128:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments.get.responses[400]
139:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments.get.responses[400].content.application/json.examples.Generic400.value.status
145:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments.get.responses[400].content.application/json.examples.endUserIdRequired.value.status
151:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments.get.responses[400].content.application/json.examples.paymentIdRequired.value.status
153:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments.get.responses[401]
155:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments.get.responses[403]
157:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments.get.responses[409]
165:25    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments.get.responses[409].content.application/json.example.status
167:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments.get.responses[500]
175:25    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments.get.responses[500].content.application/json.example.status
177:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments.get.responses[503]
186:9   warning  operation-tag-defined                 Operation tags must be defined in global tags.                                                                                paths./payments/{paymentId}.get.tags[0]
198:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}.get.responses[200]
204:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}.get.responses[400]
215:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/{paymentId}.get.responses[400].content.application/json.examples.Generic400.value.status
221:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/{paymentId}.get.responses[400].content.application/json.examples.endUserIdRequired.value.status
227:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/{paymentId}.get.responses[400].content.application/json.examples.paymentIdRequired.value.status
229:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}.get.responses[401]
231:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}.get.responses[403]
233:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}.get.responses[404]
235:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}.get.responses[500]
241:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}.get.responses[503]
244:10  warning  camara-routes-description             Functionality method description Warning: Each method should have description.                                                      paths./payments/prepare.post
244:10  warning  operation-description                 Operation "description" must be present and non-empty string.                                                                       paths./payments/prepare.post
250:9   warning  operation-tag-defined                 Operation tags must be defined in global tags.                                                                                paths./payments/prepare.post.tags[0]
261:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/prepare.post.responses[201]
267:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/prepare.post.responses[400]
278:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/prepare.post.responses[400].content.application/json.examples.Generic400.value.status
284:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/prepare.post.responses[400].content.application/json.examples.endUserIdRequired.value.status
290:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/prepare.post.responses[400].content.application/json.examples.paymentIdRequired.value.status
292:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/prepare.post.responses[401]
294:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/prepare.post.responses[403]
296:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/prepare.post.responses[409]
304:25    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/prepare.post.responses[409].content.application/json.example.status
306:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/prepare.post.responses[500]
314:25    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/prepare.post.responses[500].content.application/json.example.status
316:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/prepare.post.responses[503]
319:10  warning  camara-routes-description             Functionality method description Warning: Each method should have description.                                                      paths./payments/{paymentId}/confirm.post
319:10  warning  operation-description                 Operation "description" must be present and non-empty string.                                                                       paths./payments/{paymentId}/confirm.post
325:9   warning  operation-tag-defined                 Operation tags must be defined in global tags.                                                                                paths./payments/{paymentId}/confirm.post.tags[0]
344:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}/confirm.post.responses[202]
346:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}/confirm.post.responses[400]
357:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/{paymentId}/confirm.post.responses[400].content.application/json.examples.Generic400.value.status
363:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/{paymentId}/confirm.post.responses[400].content.application/json.examples.endUserIdRequired.value.status
369:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/{paymentId}/confirm.post.responses[400].content.application/json.examples.paymentIdRequired.value.status
371:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}/confirm.post.responses[401]
373:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}/confirm.post.responses[403]
375:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}/confirm.post.responses[409]
383:25    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/{paymentId}/confirm.post.responses[409].content.application/json.example.status
385:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}/confirm.post.responses[500]
393:25    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/{paymentId}/confirm.post.responses[500].content.application/json.example.status
395:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}/confirm.post.responses[503]
399:10  warning  camara-routes-description             Functionality method description Warning: Each method should have description.                                                      paths./payments/{paymentId}/cancel.post
399:10  warning  operation-description                 Operation "description" must be present and non-empty string.                                                                       paths./payments/{paymentId}/cancel.post
405:9   warning  operation-tag-defined                 Operation tags must be defined in global tags.                                                                                paths./payments/{paymentId}/cancel.post.tags[0]
407:20     hint  camara-operationid-casing-convention  Operation Id must be in Camel case "must be camel case"                                                                             paths./payments/{paymentId}/cancel.post.operationId
423:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}/cancel.post.responses[202]
425:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}/cancel.post.responses[400]
436:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/{paymentId}/cancel.post.responses[400].content.application/json.examples.Generic400.value.status
442:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/{paymentId}/cancel.post.responses[400].content.application/json.examples.endUserIdRequired.value.status
448:29    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/{paymentId}/cancel.post.responses[400].content.application/json.examples.paymentIdRequired.value.status
450:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}/cancel.post.responses[401]
452:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}/cancel.post.responses[403]
454:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}/cancel.post.responses[409]
462:25    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/{paymentId}/cancel.post.responses[409].content.application/json.example.status
464:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}/cancel.post.responses[500]
472:25    error  oas3-valid-media-example              "status" property type must be string                                                                                paths./payments/{paymentId}/cancel.post.responses[500].content.application/json.example.status
474:9     error  parser                                Mapping key must be a string scalar rather than number                                                                              paths./payments/{paymentId}/cancel.post.responses[503]
480:11  warning  operation-tag-defined                 Operation tags must be defined in global tags.                                                                                paths./notifications.post.tags[0]
510:19  warning  camara-properties-descriptions        Property description is missing or empty: "CreatePayment.description" property must be truthy                                       components.schemas.CreatePayment
524:13  warning  camara-properties-descriptions        Property description is missing or empty: "Payment.description" property must be truthy                                             components.schemas.Payment
550:23  warning  camara-properties-descriptions        Property description is missing or empty: "AmountTransaction" property must be truthy                                               components.schemas.AmountTransaction
550:23  warning  camara-properties-descriptions        Property description is missing or empty: "AmountTransaction.description" property must be truthy                                   components.schemas.AmountTransaction
584:28  warning  camara-properties-descriptions        Property description is missing or empty: "AmountTransactionInput" property must be truthy                                          components.schemas.AmountTransactionInput
584:28  warning  camara-properties-descriptions        Property description is missing or empty: "AmountTransactionInput.description" property must be truthy                              components.schemas.AmountTransactionInput
606:28  warning  camara-properties-descriptions        Property description is missing or empty: "PaymentAmountForCharge" property must be truthy                                          components.schemas.PaymentAmountForCharge
606:28  warning  camara-properties-descriptions        Property description is missing or empty: "PaymentAmountForCharge.description" property must be truthy                              components.schemas.PaymentAmountForCharge
615:15  warning  camara-properties-descriptions        Property description is missing or empty: "EndUserId.description" property must be truthy                                           components.schemas.EndUserId
623:48  warning  camara-properties-descriptions        Property description is missing or empty: "BodyAmountReservationTransactionForReserve.description" property must be truthy          components.schemas.BodyAmountReservationTransactionForReserve
641:53  warning  camara-properties-descriptions        Property description is missing or empty: "BodyAmountReservationTransactionForReserveInput.description" property must be truthy     components.schemas.BodyAmountReservationTransactionForReserveInput
655:44  warning  camara-properties-descriptions        Property description is missing or empty: "AmountReservationTransactionForReserve" property must be truthy                          components.schemas.AmountReservationTransactionForReserve
655:44  warning  camara-properties-descriptions        Property description is missing or empty: "AmountReservationTransactionForReserve.description" property must be truthy              components.schemas.AmountReservationTransactionForReserve
689:49  warning  camara-properties-descriptions        Property description is missing or empty: "AmountReservationTransactionForReserveInput" property must be truthy                     components.schemas.AmountReservationTransactionForReserveInput
689:49  warning  camara-properties-descriptions        Property description is missing or empty: "AmountReservationTransactionForReserveInput.description" property must be truthy         components.schemas.AmountReservationTransactionForReserveInput
711:29  warning  camara-properties-descriptions        Property description is missing or empty: "PaymentAmountForReserve" property must be truthy                                         components.schemas.PaymentAmountForReserve
711:29  warning  camara-properties-descriptions        Property description is missing or empty: "PaymentAmountForReserve.description" property must be truthy                             components.schemas.PaymentAmountForReserve
720:56  warning  camara-properties-descriptions        Property description is missing or empty: "BodyAmountReservationTransactionForConfirmOrCancel.description" property must be truthy  components.schemas.BodyAmountReservationTransactionForConfirmOrCancel
720:56  warning  oas3-unused-component                 Potentially unused component has been detected.                                                                                components.schemas.BodyAmountReservationTransactionForConfirmOrCancel
730:44  warning  camara-properties-descriptions        Property description is missing or empty: "BodyAmountReservationTransactionCancel.description" property must be truthy              components.schemas.BodyAmountReservationTransactionCancel
730:44  warning  oas3-unused-component                 Potentially unused component has been detected.                                                                                components.schemas.BodyAmountReservationTransactionCancel
737:52  warning  camara-properties-descriptions        Property description is missing or empty: "AmountReservationTransactionForConfirmOrCancel" property must be truthy                  components.schemas.AmountReservationTransactionForConfirmOrCancel
737:52  warning  camara-properties-descriptions        Property description is missing or empty: "AmountReservationTransactionForConfirmOrCancel.description" property must be truthy      components.schemas.AmountReservationTransactionForConfirmOrCancel
769:37  warning  camara-properties-descriptions        Property description is missing or empty: "PaymentAmountForConfirmOrCancel" property must be truthy                                 components.schemas.PaymentAmountForConfirmOrCancel
769:37  warning  camara-properties-descriptions        Property description is missing or empty: "PaymentAmountForConfirmOrCancel.description" property must be truthy                     components.schemas.PaymentAmountForConfirmOrCancel
784:25  warning  camara-properties-descriptions        Property description is missing or empty: "ChargingInformation" property must be truthy                                             components.schemas.ChargingInformation
784:25  warning  camara-properties-descriptions        Property description is missing or empty: "ChargingInformation.description" property must be truthy                                 components.schemas.ChargingInformation
800:22  warning  camara-properties-descriptions        Property description is missing or empty: "ChargingMetaData" property must be truthy                                                components.schemas.ChargingMetaData
800:22  warning  camara-properties-descriptions        Property description is missing or empty: "ChargingMetaData.description" property must be truthy                                    components.schemas.ChargingMetaData
826:15  warning  camara-properties-descriptions        Property description is missing or empty: "ErrorInfo.description" property must be truthy                                           components.schemas.ErrorInfo
891:21    error  oas3-valid-media-example              "status" property type must be string                                                                                components.responses.Generic400.content.application/json.example.status
901:22    error  oas3-valid-media-example              "status" property type must be string                                                                                components.responses.Generic401.content.application/json.example.status
911:21    error  oas3-valid-media-example              "status" property type must be string                                                                                components.responses.Generic403.content.application/json.example.status
921:22    error  oas3-valid-media-example              "status" property type must be string                                                                                components.responses.Generic404.content.application/json.example.status
931:21    error  oas3-valid-media-example              "status" property type must be string                                                                                components.responses.Generic500.content.application/json.example.status
941:21    error  oas3-valid-media-example              "status" property type must be string                                                                                components.responses.Generic503.content.application/json.example.status
951:21    error  oas3-valid-media-example              "status" property type must be string                                                                                components.responses.Generic504.content.application/json.example.status
995:29  warning  camara-properties-descriptions        Property description is missing or empty: "oAuth2ClientCredentials.description" property must be truthy                             components.securitySchemes.oAuth2ClientCredentials
995:29    error  oas3-schema                           Invalid security scheme.                                                                                components.securitySchemes.oAuth2ClientCredentials
997:13    error  oas3-schema                           Property "flows" is not expected to be here.                                                                                components.securitySchemes.oAuth2ClientCredentials.flows
999:21    error  oas3-schema                           "tokenUrl" property must match format "uri-reference".                                                                              components.securitySchemes.oAuth2ClientCredentials.flows.clientCredentials.tokenUrl
1001:15  warning  camara-properties-descriptions        Property description is missing or empty: "BasicAuth.description" property must be truthy                                           components.securitySchemes.BasicAuth
1009:18  warning  camara-properties-descriptions        Property description is missing or empty: "three_legged.description" property must be truthy                                        components.securitySchemes.three_legged
`

The second ones is due to is checking history "YAML" info so i will adapt linter to only check the one in the repository

@rartych, @bigludo7

Will adapt linter in order to only check "yaml" within code subfolder
Will trigger new PR to adapt API Spec "format"

@rartych checked again with the latest linter configuration in Commonalities and it is OK!!!!
❌ Linted [YAML] files with [yamllint]: Found 1 error(s) - (0.52s) (expand for details)

Using [yamllint v1.32.0] https://megalinter.io/7.3.0/descriptors/yaml_yamllint
MegaLinter key: [YAML_YAMLLINT]
Rules config: [/github/workspace/.yamllint.yaml]
Number of files analyzed: [1]
--Error detail:
code/API_definitions/carrier_billing.yaml
Error: 16:19 [trailing-spaces] trailing spaces
Error: 19:26 [trailing-spaces] trailing spaces
Error: 22:26 [trailing-spaces] trailing spaces
Error: 28:1 [trailing-spaces] trailing spaces
Error: 43:35 [trailing-spaces] trailing spaces
Error: 55:1 [trailing-spaces] trailing spaces
Error: 78:1 [trailing-spaces] trailing spaces
Error: 135:11 [indentation] wrong indentation: expected 12 but found 10
Error: 218:11 [indentation] wrong indentation: expected 12 but found 10
Error: 223:22 [trailing-spaces] trailing spaces
Error: 230:87 [trailing-spaces] trailing spaces
Error: 234:135 [trailing-spaces] trailing spaces
Error: 274:11 [indentation] wrong indentation: expected 12 but found 10
Error: 317:11 [indentation] wrong indentation: expected 12 but found 10
Error: 412:11 [indentation] wrong indentation: expected 12 but found 10
Error: 471:11 [indentation] wrong indentation: expected 12 but found 10
Error: 517:11 [indentation] wrong indentation: expected 12 but found 10
Error: 988:29 [trailing-spaces] trailing spaces
Error: 1176:54 [trailing-spaces] trailing spaces
Error: 1317:21 [trailing-spaces] trailing spaces
Error: 1401:123 [trailing-spaces] trailing spaces
Error: 1417:48 [trailing-spaces] trailing spaces
Error: 1450:123 [trailing-spaces] trailing spaces
Error: 1475:1 [trailing-spaces] trailing spaces
Error: 1671:32 [trailing-spaces] trailing spaces
Error: 1680:16 [trailing-spaces] trailing spaces
Error: 1687:24 [trailing-spaces] trailing spaces

Just format topics, for them I will trigger PR
cc @bigludo7


updated package.json devDependency

updated package es6-promise from 4.0.5 to 4.1.0
Npm link :  https://www.npmjs.com/package/es6-promise
Repository link : https://github.com/stefanpenner/es6-promise/releases

Coverage remained the same at 93.734% when pulling 61330d0dc545fe375620e0435fd45adcb2168a8b on EsrefDurna:master into 46e275c407f81c44dd9aad419b6e861d8a936580 on mzabriskie:master.


v1.74: no client side decorations in GNOME on Wayland

Type: Bug
This started happening with the update to 1.74.
Launching with the flags "--ozone-platform-hint=auto --enable-features=WaylandWindowDecorations" does run in Wayland, but client side decorations are no longer present
VS Code version: Code - OSS 1.74.0 (5235c6bb189b60b01b1f49062f4ffa42384f8c91, 2022-12-07T23:49:16.764Z)
OS version: Linux x64 6.0.11-arch1-1
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
12th Gen Intel(R) Core(TM) i7-1255U (12 x 3982)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
1, 1, 1

Memory (System)
15.33GB (10.55GB free)

Process Argv
--ozone-platform-hint=auto --enable-features=WaylandWindowDecorations

Screen Reader
no

VM
0%

DESKTOP_SESSION
gnome

XDG_CURRENT_DESKTOP
GNOME

XDG_SESSION_DESKTOP
gnome

XDG_SESSION_TYPE
wayland

Extensions: none

confirm this bug.
in console when running code --enable-features=WaylandWindowDecorations --ozone-platform-hint=auto:
Warning: 'enable-features' is not in the list of known options, but still passed to Electron/Chromium.
Warning: 'ozone-platform-hint' is not in the list of known options, but still passed to Electron/Chromium.

/gifPlease

Thanks for reporting this issue! Unfortunately, it's hard for us to understand what issue you're seeing. Please help us out by providing a screen recording showing exactly what isn't working as expected. While we can work with most standard formats, .gif files are preferred as they are displayed inline on GitHub. You may find https://gifcap.dev helpful as a browser-based gif recording tool.
If the issue depends on keyboard input, you can help us by enabling screencast mode for the recording (Developer: Toggle Screencast Mode in the command palette). Lastly, please attach this file via the GitHub web interface as emailed responses will strip files out from the issue.
Happy coding!

Version 1.73.1 with client side decorations:

Version 1.74 without csd:

In both cases, launched with code --ozone-platform-hint=auto --enable-features=WaylandWindowDecorations. Window: Title Bar Style is set to native in settings

Is it on Electron side if they removed these options?

Only relevant changed that happened in runtime for CSD in Electron 19 was https://github.com/electron/electron/commit/4b483799cb6de62a387646bd9c7fc8db1863659b. Both 1.73 and 1.74 contain the mentioned change. Need to confirm if the issue repros with OSS to eliminate any internal changes.

Confirming I see the same behavior. Running a fully updated Arch system with Gnome and the proprietary NVidia drivers. I am happy to provide any specific info if it's helpful, just let me know what you would like to see.

I'm using VSCodium 1.74.0 made from the the same AUR package as @chrislea and I do have the same problem. VSCodium does run under wayland, but with no window decorations

Experiencing the same issue here as well

updated to 1.74.2 and now Wayland decorations came back.

Also confirmed, Wayland CSD working with 1.74.2

Sorry for the breakage, this was caused as a side effect of having this line before 1.74.2 which cause the runtime to ignore --enable-features=WaylandWindowDecorations when passed from the CLI.

Thanks for the fix!


[DATA-4839] Do not delete queued TIs from invisible DAGs

The airflow 1.7 scheduler deletes any queued TI's belonging to DAGs that are not in the DagBag [1].  Since we're filtering out DAGs whitelisted for 1.8 (just the long_running_test DAG for now), the scheduler thinks those TI's belong to a DAG that has been removed and deletes them before they get picked up by an airflow 1.8 worker.
With this change, we'll simply ignore any TI's from a DAG that we know is handled by the 1.8 scheduler.
[1] [2017-09-13 17:34:26,285] {jobs.py:580} INFO - DAG no longer in dagbag, deleting <TaskInstance: long_running_test.entrypoint 2017-08-30 00:00:00 [queued]>
cc @lyft/data-platform

👍


Added [GitLabTag] service

Added GitLab Tag (latest by date) service, equivalent to GitHub Tag (latest by date) but for gitlab.com instead of github.com.
I created issue #6388 for this, but it is closed as a duplicate of #4867 (which asks to replicate all GitHub Tags and Releases services for GitLab. Right now my priority is this badge, but I promise to to include the rest in the future.

Messages

:book:
:sparkles: Thanks for your contribution to Shields, @guillermin!

  Generated by :no_entry_sign: dangerJS against b267857b3a5de3585b8ac94b45bc2b22fbe571d9

Hello @guillermin! 👋🏻
Thanks for opening this. Unfortunately, we don't intend on expanding our GitLab badge offering at this point in time, due to API rate limit concerns. Right now, the badge you've implemented would probably fail most of the time on our production servers due to these limitations. See https://github.com/badges/shields/issues/541#issuecomment-640950235 and various other messages for a bit more context. 😉

Due to aforementioned API rate limiting concerns, I don't see a path forward with this pull request for the time being. Thanks for sharing your code, but I'm afraid I'll have to close it for now.
The next steps for any Gitlab badge using the official API would be to engage in #541 and help us figure out the state of the access token features offered by Gitlab.


CrossConnectivity.Current.IsConnected produces starting and finishing tasks on XAMARIN.Android

Hello, maybe it's a normal behavior but I think it isn't. As written in the headline. After calling CrossConnectivity.Current.IsConnected the first time, the app starts and finishes task constantly.
Is it a bug or a feature?
Thanks for your support!
Marcel
Bug Information
Version Number of Plugin: 3.1.1
Device Tested On: Android 7.0 (ZTE BLADE V8 MINI)
Simulator Tested On: not tested
Version of VS: 15.6 Preview 6
Version of Xamarin:
XAMARIN - <IP_ADDRESS>8
XAMARIN.Android SDK - <IP_ADDRESS>
Versions of other things you are using:
Compile using Android Version 7.1
Min Android Version 5.0 (API Level 21)
Target Android Version 7.1 (API Level 25)
Steps to reproduce the Behavior
Create a new XAMARIN.Android project.
Simply call CrossConnectivity.Current.IsConnected in an Activity (e.g. after clicking on a button).
Expected Behavior
The component should only return the internet connection status.
Actual Behavior
Everthing works good, but the application constantly produces starting and finishing threads after callng the IsConnected  member.
You can see this in the console. Here are some examples (unfortunately in german):
Thread finished: <Thread Pool> #4 Der Thread 0x4 hat mit Code 0 (0x0) geendet. Thread finished: <Thread Pool> #3 Thread started: <Thread Pool> #7 Der Thread 0x3 hat mit Code 0 (0x0) geendet. Thread finished: <Thread Pool> #6 Der Thread 0x6 hat mit Code 0 (0x0) geendet. Thread finished: <Thread Pool> #5 Thread started: <Thread Pool> #8 Der Thread 0x5 hat mit Code 0 (0x0) geendet. Thread started: <Thread Pool> #9 Thread finished: <Thread Pool> #7 Thread started: <Thread Pool> #10 Der Thread 0x7 hat mit Code 0 (0x0) geendet. Thread finished: <Thread Pool> #8 Der Thread 0x8 hat mit Code 0 (0x0) geendet. Thread finished: <Thread Pool> #10 Thread started: <Thread Pool> #11 Der Thread 0xa hat mit Code 0 (0x0) geendet. Thread finished: <Thread Pool> #9 Thread started: <Thread Pool> #12 Thread started: <Thread Pool> #13 Der Thread 0x9 hat mit Code 0 (0x0) geendet. Thread finished: <Thread Pool> #12 Der Thread 0xc hat mit Code 0 (0x0) geendet. Thread finished: <Thread Pool> #11 Thread started: <Thread Pool> #14 Der Thread 0xb hat mit Code 0 (0x0) geendet. Thread finished: <Thread Pool> #13 Thread started: <Thread Pool> #15 Thread started: <Thread Pool> #16 Der Thread 0xd hat mit Code 0 (0x0) geendet.
Code snippet

Screenshots

What does your code look like? I start no threads

It's quite simple.
I have a very simple Activity:
`using System;
using System.Threading.Tasks;
using Android.App;
using Android.OS;
using Android.Widget;
using Plugin.Connectivity;
using Schiessbuch.Model.Service;
namespace Schiessbuch.Droid
{
[Activity(Label = "RestServiceActivity")]
public class RestServiceActivity : Activity
{
private async Task FetchTestRequest()
{
RestService service = new RestService();
string sResponse = await Task.Run(() => service.TestRequest());
return sResponse;
}
    protected override void OnCreate(Bundle savedInstanceState)
    {
        base.OnCreate(savedInstanceState);

        // Set our view from the "main" layout resource
        SetContentView(Resource.Layout.RestService);

        Button testButton = FindViewById<Button>(Resource.Id.TestButton);
        TextView restTextView = FindViewById<TextView>(Resource.Id.RestTextView);

        testButton.Click += async (sender, e) =>
        {
            if (CrossConnectivity.Current.IsConnected)
            {
                // Code is commented ou. So I found out, that the issue starty only with calling IsConnected
            }
            else
            {
                Toast.MakeText(this, "Keine Internetverbindung verfügbar!", ToastLength.Long).Show();
            }
        };
    }
}

}`

No issues for me here or with the plugin.


Update: Zulip.Zulip version <IP_ADDRESS>

Result: Installation Successful

Manifest
Add/Remove Programs

Name
Zulip
Zulip

Version
<IP_ADDRESS>
<IP_ADDRESS>

Publisher
Kandra Labs, Inc.
Kandra Labs, Inc.

ProductCode
{A6ABF2C1-85D0-4EB8-AEF9-5675BCAD141C}
{A6ABF2C1-85D0-4EB8-AEF9-5675BCAD141C}

Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 1939
Microsoft Reviewers: Open in CodeFlow

@wingetbot run


HADOOP-18209. Fix links to DataNodes in NameNode UI to support IPv6

…

Description of PR
How was this patch tested?
For code changes:

[ ] Does the title or this PR starts with the corresponding JIRA issue id (e.g. 'HADOOP-17799. Your PR title ...')?
[ ] Object storage: have the integration tests been executed and the endpoint declared according to the connector-specific documentation?
[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?
[ ] If applicable, have you updated the LICENSE, LICENSE-binary, NOTICE-binary files?

@brahmareddybattula @hemanthboyina ,
Please review the MR when you get time. Thank you.

As there is no test, could you upload a screenshot with this fix? Thanks,

Thanks @liuml07 for quick review & feedback.
Updated the snapshot of the fix, please review.

@prasad-acit Just noticed that your PR is against a feature branch HADOOP-17800. Was that intentional? For changes like this I assume it's safe to get in to trunk and active release versions directly. @brahmareddybattula thoughs?

Thank you @liuml07 ,
HADOOP-17800 got branched out from trunk recently & started merging from older IPv6 branch (HADOOP-11890).
Yes, @brahmareddybattula can clarify it further.

Thank you @liuml07 , HADOOP-17800 got branched out from trunk recently & started merging from older IPv6 branch (HADOOP-11890). Yes, @brahmareddybattula can clarify it further.

@hemanthboyina Do you have any thought on this?


Unable to use vue-carousel as a local package

Bug Report
Current Behavior
Unable to use vue-carousel as a local package using yarn link. The following warnings are produced:
➜  ryu-carousel-cli git:(master) ✗ yarn serve
yarn run v1.10.1
$ vue-cli-service serve
 INFO  Starting development server...
 98% after emitting CopyPlugin

 WARNING  Compiled with 2 warnings                                                                                12:29:37 AM

 warning  in ./src/App.vue?vue&type=script&lang=js&

"export 'Carousel' was not found in 'vue-carousel'

 warning  in ./src/App.vue?vue&type=script&lang=js&

"export 'Slide' was not found in 'vue-carousel'

Input Code and steps to reproduce
App.js
<template>
  <div id="app">
		<carousel :per-page="1" :custom-slide-width="1">
			<slide>
				Slide 1 Content
			</slide>
			<slide>
				Slide 2 Content
			</slide>
		</carousel>
	</div>
</template>

<script>
import { Carousel, Slide } from 'vue-carousel'

export default {
	name: 'App',
	components: {
		Carousel,
		Slide
	}
}
</script>

Expected behavior/code
Doing a yarn link should allow me to use vue-carousel in a local project.
Babel Configuration (.babelrc, package.json, cli command)
{
  "name": "ryu-carousel-cli",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "serve": "vue-cli-service serve",
    "build": "vue-cli-service build",
    "lint": "vue-cli-service lint"
  },
  "dependencies": {
    "vue": "^2.5.17",
    "vue-carousel": "file:../vue-carousel"
  },
  "devDependencies": {
    "@vue/cli-plugin-babel": "^3.0.5",
    "@vue/cli-plugin-eslint": "^3.0.5",
    "@vue/cli-service": "^3.0.5",
    "vue-template-compiler": "^2.5.17"
  },
  "eslintConfig": {
    "root": true,
    "env": {
      "node": true
    },
    "extends": [
      "plugin:vue/essential",
      "eslint:recommended"
    ],
    "rules": {},
    "parserOptions": {
      "parser": "babel-eslint"
    }
  },
  "postcss": {
    "plugins": {
      "autoprefixer": {}
    }
  },
  "browserslist": [
    "> 1%",
    "last 2 versions",
    "not ie <= 8"
  ]
}

Environment

"@vue/cli-plugin-babel": "^3.0.5"
Node/npm version: Node 11.0.0/npm 6.4.1
OS: macOS 10.12.6

Hey @rkomiyama, yarn has an open issue that's likely effecting this. I can recreate this issue on local if I use yarn link, but it works fine if instead I point to my local directory with node_modules installed in my package json (i.e vue-carousel: link: ../path/to/vue-carousel)
Since it's likely that this is an issue on yarns end, I'll close this. Feel free to reopen of make a comment here if you feel otherwise! :octocat:

@quinnlangille I'm still getting the same warnings even with npm link. There might be an issue with vue create, but I'm not sure how relevant it is to this issue (https://github.com/vuejs/vue-cli/issues/1494).


service name is without preview now

service name is just Kubernetes Service

@itayct : Thanks for your contribution! The author, @neilpeterson, has been notified to review your proposed change.

@itayct - thanks a bunch. Confirmed on my end, looks good.
#sign-off


Research, evaluate, and set up essential technologies.

User Stories:

As a developer, I need to understand how to set up a .NET API with a React frontend so that I can efficiently manage communication between frontend and backend.
As a developer, I want to research user authentication methods compatible with .NET and React, allowing secure login and registration.
As a developer, I need to establish a scalable database structure that supports product inventory, orders, and user profiles.
As a developer, I want to understand how to integrate payment processing (e.g., Stripe or PayPal) to handle transactions.


RN-269 fix for huawei not rendering posts

To be included in dot release 1.0.1
Summary
In some Android devices the style for transform does not work causing the list of post to render as blank, this PR will fix that issue by using the scaleY directly instead of a transform object.
Note: This will cause RN to display a deprecation warning in the yellowbox but it works as expected in all Android phones
Ticket Link
https://mattermost.atlassian.net/browse/RN-269

@enahum This is the fix that will cause a warning for a deprecated property right?

as stated in the summary note on the PR ;)

haha well it would help if I read more than the title ;)


pgbouncer: 1.7.2 -> 1.8.1

Semi-automatic update generated by https://github.com/ryantm/nix-update tools. These checks were done:

built on NixOS
ran /nix/store/29ywgqx9kl3bv67b4r19yydrvwj29ssb-pgbouncer-1.8.1/bin/pgbouncer -h got 0 exit code
ran /nix/store/29ywgqx9kl3bv67b4r19yydrvwj29ssb-pgbouncer-1.8.1/bin/pgbouncer --help got 0 exit code
ran /nix/store/29ywgqx9kl3bv67b4r19yydrvwj29ssb-pgbouncer-1.8.1/bin/pgbouncer -V and found version 1.8.1
ran /nix/store/29ywgqx9kl3bv67b4r19yydrvwj29ssb-pgbouncer-1.8.1/bin/pgbouncer --version and found version 1.8.1
found 1.8.1 with grep in /nix/store/29ywgqx9kl3bv67b4r19yydrvwj29ssb-pgbouncer-1.8.1
found 1.8.1 in filename of file in /nix/store/29ywgqx9kl3bv67b4r19yydrvwj29ssb-pgbouncer-1.8.1

No attempt on x86_64-darwin
The following builds were skipped because they don't evaluate on x86_64-darwin: pgbouncer
No log is available.

Success on x86_64-linux (full log)
Attempted: pgbouncer
Partial log (click to expand)
     INSTALL  doc/pgbouncer.5 /nix/store/29ywgqx9kl3bv67b4r19yydrvwj29ssb-pgbouncer-1.8.1/share/man/man5
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/29ywgqx9kl3bv67b4r19yydrvwj29ssb-pgbouncer-1.8.1
shrinking /nix/store/29ywgqx9kl3bv67b4r19yydrvwj29ssb-pgbouncer-1.8.1/bin/pgbouncer
gzipping man pages under /nix/store/29ywgqx9kl3bv67b4r19yydrvwj29ssb-pgbouncer-1.8.1/share/man/
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/29ywgqx9kl3bv67b4r19yydrvwj29ssb-pgbouncer-1.8.1/bin
patching script interpreter paths in /nix/store/29ywgqx9kl3bv67b4r19yydrvwj29ssb-pgbouncer-1.8.1
checking for references to /tmp/nix-build-pgbouncer-1.8.1.drv-0 in /nix/store/29ywgqx9kl3bv67b4r19yydrvwj29ssb-pgbouncer-1.8.1...
/nix/store/29ywgqx9kl3bv67b4r19yydrvwj29ssb-pgbouncer-1.8.1

Success on aarch64-linux (full log)
Attempted: pgbouncer
Partial log (click to expand)
     INSTALL  doc/pgbouncer.5 /nix/store/95l268sa6nk212m5q8yirlh4v4cfrkck-pgbouncer-1.8.1/share/man/man5
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/95l268sa6nk212m5q8yirlh4v4cfrkck-pgbouncer-1.8.1
shrinking /nix/store/95l268sa6nk212m5q8yirlh4v4cfrkck-pgbouncer-1.8.1/bin/pgbouncer
gzipping man pages under /nix/store/95l268sa6nk212m5q8yirlh4v4cfrkck-pgbouncer-1.8.1/share/man/
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/95l268sa6nk212m5q8yirlh4v4cfrkck-pgbouncer-1.8.1/bin
patching script interpreter paths in /nix/store/95l268sa6nk212m5q8yirlh4v4cfrkck-pgbouncer-1.8.1
checking for references to /build in /nix/store/95l268sa6nk212m5q8yirlh4v4cfrkck-pgbouncer-1.8.1...
/nix/store/95l268sa6nk212m5q8yirlh4v4cfrkck-pgbouncer-1.8.1


chore(deps): bump docker image ghcr.io/pingcap-qe/ee-apps/cloudevents-server to v2024.11.4-6-g495e6f0

This pull request updates the Docker image tag for the cloudevents-server in the release.yaml file.

apps/prod/cloudevents-server/release.yaml: Updated the Docker image tag from v20240228-76-geadd400 to v2024.11.4-6-g495e6f0.

/approve


Could this be made into a basic web browser?

It appears to support basic functionality that a web browser might use.
It could support like HTML4 or something like that.
Does anyone know of alternative project that works like this(other then lynx)?

HTML4 would be overkill for blessed itself, but a HTML4 renderer would be implemented on top of it the same way there's a React renderer (and I would love to see something like this :-D)

@piranna please let me know if you have any ideas.  It would be awesome if you could develop applications that are both browser and terminal supported.  If done right you can translate the drag and drop panes in the terminal to equivalent JavaScript apis

The first thing would be to clean-up the project architecture to allow double buffering and remove the non-esential widgets. that's the purposse of blessed-ng but I don't have time to work on that. After that, it would be easy to implement the DOM elements on top of the blessed basic widgets, but would need a lot of work... Probably react-blessed is the best option at this moment.

@piranna it sounds like you have more experience with this but do you think it would be possible to maybe spawn a chrome process and simply convert that to a canvas or something terminals support?

Yes, it would be possible, but the result will be absolutely useless.

@limeblack As far as I'm concerned what you are asking about is no longer related to blessed. And yes, you can use something like phantom.js to render webpages and later use own logic display them as raster graphic in terminal. I have to say that it's a terrible idea and won't really work as good as you would want it to.


Add Surface::new()

Creates a Surface given the raw handler
This is needed for me, since I want to use the glfw crate with the glfw::ffi::glfwCreateWindowSurface function. After creating the Surface with this function, I had no way to integrate it into the framework: creating a vulkano::swapchain::Surface object seemed out of the question because there is no public method/way to do it.
It's probably not the best solution. I'm open to better ones.
I propose it unsafe because it is very unsafe to use if you don't know what you are doing, I suppose.

Thanks for the PR.
The function looks good, but I think it needs another name. Something like from_raw_surface, rather than new.

Correction done
I'm thinking... Does it make sense to use it also in all the Surface::from_* to remove the repetition of AtomicBool::new(false)?

Does it make sense to use it also in all the Surface::from_* to remove the repetition of AtomicBool::new(false)?

It's not worth saving one line of code. Maybe in the future if Surface gets more fields.


How to get compiled apk?

Your Rocket.Chat.Android version: (make sure you are running the latest)

Mobile device model and OS version: (e.g. "Nexus 7 - Android 6.0.1")

Hi! I not a java developer and get errors via making application. How to get apk?

It's on google play. https://play.google.com/store/apps/details?id=chat.rocket.android&hl=de

To get the most recent apk in production you should go to the Play Store and download the Rocket.Chat+ app (you already posted the link above).
To get the most recent apk in development you should generate the app from the AS. How? https://developer.android.com/studio/run/index.html


need to add traditional list view

Is your feature request related to a problem? Please describe.
The Files UWP doesn't have the traditional list view.  The list view looks like the traditional Details view.  While it matches the list view of things like OneDrive.com, it doesn't match the traditional list view.  The list view maximizes window space to see the most content.
Describe the solution you'd like
The Files UWP doesn't have the traditional list view.  The list view looks like the Details view.  While it matches the list view of things like OneDrive.com, it doesn't match the traditional list view.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here. Ex: What device type/UI layout and app version?

@yaichenbaum Could you assign me on this issue?

@Jaiganeshkumaran Have you made any progress on this feature?

Merging with #2509.

@onlysublime thank you for your patience, I'm excited to share that a List View layout will be included in the next release.