instantiation of "graphvite::SolverMixin<_dim, _Float, _Index, _Graph, _Sampler, _Worker>::~SolverMixin() [with _dim=64UL, _Float=float, _Index=unsigned int, _Graph=graphvite::Graph, _Sampler=graphvite::GraphSampler, _Worker=graphvite::GraphWorker]"
/usr/include/c++/7/bits/unique_ptr.h(78): here
            [ 2 instantiation contexts not shown ]
            instantiation of "void std::default_delete<_Tp>::operator()(_Tp *) const [with _Tp=graphvite::GraphSolver<64UL, float, unsigned int>]"
/usr/include/c++/7/bits/unique_ptr.h(268): here
            instantiation of "std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp=graphvite::GraphSolver<64UL, float, unsigned int>, _Dp=std::default_delete<graphvite::GraphSolver<64UL, float, unsigned int>>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1351): here
            instantiation of "void pybind11::class_<type_, options...>::dealloc(pybind11::detail::value_and_holder &) [with type_=graphvite::GraphSolver<64UL, float, unsigned int>, options=<>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1080): here
            instantiation of "pybind11::class_<type_, options...>::class_(pybind11::handle, const char *, const Extra &...) [with type_=graphvite::GraphSolver<64UL, float, unsigned int>, options=<>, Extra=<>]"
/content/graphvite/include/bind.h(395): here
            instantiation of "pyGraphSolver<dim, Float, Index>::pyGraphSolver(pybind11::handle, const char *, const Args &...) [with dim=64UL, Float=float, Index=unsigned int, Args=<>]"
/content/graphvite/src/graphvite.cu(55): here

/content/graphvite/include/instance/gpu/graph.cuh(263): warning: variable "vertex_buffer" was declared but never referenced
          detected during:
            instantiation of "void graphvite::gpu::graph::predict<Vector,Index,Model>(graphvite::Memory<Vector, Index>, graphvite::Memory<Vector, Index>, graphvite::Memory<Index, int>, graphvite::Memory<Vector::Float, int>) [with Vector=graphvite::Vector<64UL, float>, Index=unsigned int, Model=graphvite::LINE]"
/content/graphvite/include/instance/graph.cuh(568): here
            instantiation of "__nv_bool graphvite::GraphWorker<_Solver>::predict_dispatch() [with _Solver=graphvite::SolverMixin<64UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            implicit generation of "graphvite::GraphWorker<_Solver>::~GraphWorker() [with _Solver=graphvite::SolverMixin<64UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of class "graphvite::GraphWorker<_Solver> [with _Solver=graphvite::SolverMixin<64UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of "graphvite::SolverMixin<_dim, _Float, _Index, _Graph, _Sampler, _Worker>::~SolverMixin() [with _dim=64UL, _Float=float, _Index=unsigned int, _Graph=graphvite::Graph, _Sampler=graphvite::GraphSampler, _Worker=graphvite::GraphWorker]"
/usr/include/c++/7/bits/unique_ptr.h(78): here
            [ 2 instantiation contexts not shown ]
            instantiation of "void std::default_delete<_Tp>::operator()(_Tp *) const [with _Tp=graphvite::GraphSolver<64UL, float, unsigned int>]"
/usr/include/c++/7/bits/unique_ptr.h(268): here
            instantiation of "std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp=graphvite::GraphSolver<64UL, float, unsigned int>, _Dp=std::default_delete<graphvite::GraphSolver<64UL, float, unsigned int>>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1351): here
            instantiation of "void pybind11::class_<type_, options...>::dealloc(pybind11::detail::value_and_holder &) [with type_=graphvite::GraphSolver<64UL, float, unsigned int>, options=<>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1080): here
            instantiation of "pybind11::class_<type_, options...>::class_(pybind11::handle, const char *, const Extra &...) [with type_=graphvite::GraphSolver<64UL, float, unsigned int>, options=<>, Extra=<>]"
/content/graphvite/include/bind.h(395): here
            instantiation of "pyGraphSolver<dim, Float, Index>::pyGraphSolver(pybind11::handle, const char *, const Args &...) [with dim=64UL, Float=float, Index=unsigned int, Args=<>]"
/content/graphvite/src/graphvite.cu(55): here

/content/graphvite/include/instance/gpu/graph.cuh(263): warning: variable "vertex_buffer" was declared but never referenced
          detected during:
            instantiation of "void graphvite::gpu::graph::predict<Vector,Index,Model>(graphvite::Memory<Vector, Index>, graphvite::Memory<Vector, Index>, graphvite::Memory<Index, int>, graphvite::Memory<Vector::Float, int>) [with Vector=graphvite::Vector<64UL, float>, Index=unsigned int, Model=graphvite::Node2Vec]"
/content/graphvite/include/instance/graph.cuh(570): here
            instantiation of "__nv_bool graphvite::GraphWorker<_Solver>::predict_dispatch() [with _Solver=graphvite::SolverMixin<64UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            implicit generation of "graphvite::GraphWorker<_Solver>::~GraphWorker() [with _Solver=graphvite::SolverMixin<64UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of class "graphvite::GraphWorker<_Solver> [with _Solver=graphvite::SolverMixin<64UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of "graphvite::SolverMixin<_dim, _Float, _Index, _Graph, _Sampler, _Worker>::~SolverMixin() [with _dim=64UL, _Float=float, _Index=unsigned int, _Graph=graphvite::Graph, _Sampler=graphvite::GraphSampler, _Worker=graphvite::GraphWorker]"
/usr/include/c++/7/bits/unique_ptr.h(78): here
            [ 2 instantiation contexts not shown ]
            instantiation of "void std::default_delete<_Tp>::operator()(_Tp *) const [with _Tp=graphvite::GraphSolver<64UL, float, unsigned int>]"
/usr/include/c++/7/bits/unique_ptr.h(268): here
            instantiation of "std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp=graphvite::GraphSolver<64UL, float, unsigned int>, _Dp=std::default_delete<graphvite::GraphSolver<64UL, float, unsigned int>>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1351): here
            instantiation of "void pybind11::class_<type_, options...>::dealloc(pybind11::detail::value_and_holder &) [with type_=graphvite::GraphSolver<64UL, float, unsigned int>, options=<>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1080): here
            instantiation of "pybind11::class_<type_, options...>::class_(pybind11::handle, const char *, const Extra &...) [with type_=graphvite::GraphSolver<64UL, float, unsigned int>, options=<>, Extra=<>]"
/content/graphvite/include/bind.h(395): here
            instantiation of "pyGraphSolver<dim, Float, Index>::pyGraphSolver(pybind11::handle, const char *, const Args &...) [with dim=64UL, Float=float, Index=unsigned int, Args=<>]"
/content/graphvite/src/graphvite.cu(55): here

/content/graphvite/include/instance/gpu/graph.cuh(263): warning: variable "vertex_buffer" was declared but never referenced
          detected during:
            instantiation of "void graphvite::gpu::graph::predict<Vector,Index,Model>(graphvite::Memory<Vector, Index>, graphvite::Memory<Vector, Index>, graphvite::Memory<Index, int>, graphvite::Memory<Vector::Float, int>) [with Vector=graphvite::Vector<96UL, float>, Index=unsigned int, Model=graphvite::DeepWalk]"
/content/graphvite/include/instance/graph.cuh(566): here
            instantiation of "__nv_bool graphvite::GraphWorker<_Solver>::predict_dispatch() [with _Solver=graphvite::SolverMixin<96UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            implicit generation of "graphvite::GraphWorker<_Solver>::~GraphWorker() [with _Solver=graphvite::SolverMixin<96UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of class "graphvite::GraphWorker<_Solver> [with _Solver=graphvite::SolverMixin<96UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of "graphvite::SolverMixin<_dim, _Float, _Index, _Graph, _Sampler, _Worker>::~SolverMixin() [with _dim=96UL, _Float=float, _Index=unsigned int, _Graph=graphvite::Graph, _Sampler=graphvite::GraphSampler, _Worker=graphvite::GraphWorker]"
/usr/include/c++/7/bits/unique_ptr.h(78): here
            [ 2 instantiation contexts not shown ]
            instantiation of "void std::default_delete<_Tp>::operator()(_Tp *) const [with _Tp=graphvite::GraphSolver<96UL, float, unsigned int>]"
/usr/include/c++/7/bits/unique_ptr.h(268): here
            instantiation of "std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp=graphvite::GraphSolver<96UL, float, unsigned int>, _Dp=std::default_delete<graphvite::GraphSolver<96UL, float, unsigned int>>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1351): here
            instantiation of "void pybind11::class_<type_, options...>::dealloc(pybind11::detail::value_and_holder &) [with type_=graphvite::GraphSolver<96UL, float, unsigned int>, options=<>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1080): here
            instantiation of "pybind11::class_<type_, options...>::class_(pybind11::handle, const char *, const Extra &...) [with type_=graphvite::GraphSolver<96UL, float, unsigned int>, options=<>, Extra=<>]"
/content/graphvite/include/bind.h(395): here
            instantiation of "pyGraphSolver<dim, Float, Index>::pyGraphSolver(pybind11::handle, const char *, const Args &...) [with dim=96UL, Float=float, Index=unsigned int, Args=<>]"
/content/graphvite/src/graphvite.cu(56): here

/content/graphvite/include/instance/gpu/graph.cuh(263): warning: variable "vertex_buffer" was declared but never referenced
          detected during:
            instantiation of "void graphvite::gpu::graph::predict<Vector,Index,Model>(graphvite::Memory<Vector, Index>, graphvite::Memory<Vector, Index>, graphvite::Memory<Index, int>, graphvite::Memory<Vector::Float, int>) [with Vector=graphvite::Vector<96UL, float>, Index=unsigned int, Model=graphvite::LINE]"
/content/graphvite/include/instance/graph.cuh(568): here
            instantiation of "__nv_bool graphvite::GraphWorker<_Solver>::predict_dispatch() [with _Solver=graphvite::SolverMixin<96UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            implicit generation of "graphvite::GraphWorker<_Solver>::~GraphWorker() [with _Solver=graphvite::SolverMixin<96UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of class "graphvite::GraphWorker<_Solver> [with _Solver=graphvite::SolverMixin<96UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of "graphvite::SolverMixin<_dim, _Float, _Index, _Graph, _Sampler, _Worker>::~SolverMixin() [with _dim=96UL, _Float=float, _Index=unsigned int, _Graph=graphvite::Graph, _Sampler=graphvite::GraphSampler, _Worker=graphvite::GraphWorker]"
/usr/include/c++/7/bits/unique_ptr.h(78): here
            [ 2 instantiation contexts not shown ]
            instantiation of "void std::default_delete<_Tp>::operator()(_Tp *) const [with _Tp=graphvite::GraphSolver<96UL, float, unsigned int>]"
/usr/include/c++/7/bits/unique_ptr.h(268): here
            instantiation of "std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp=graphvite::GraphSolver<96UL, float, unsigned int>, _Dp=std::default_delete<graphvite::GraphSolver<96UL, float, unsigned int>>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1351): here
            instantiation of "void pybind11::class_<type_, options...>::dealloc(pybind11::detail::value_and_holder &) [with type_=graphvite::GraphSolver<96UL, float, unsigned int>, options=<>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1080): here
            instantiation of "pybind11::class_<type_, options...>::class_(pybind11::handle, const char *, const Extra &...) [with type_=graphvite::GraphSolver<96UL, float, unsigned int>, options=<>, Extra=<>]"
/content/graphvite/include/bind.h(395): here
            instantiation of "pyGraphSolver<dim, Float, Index>::pyGraphSolver(pybind11::handle, const char *, const Args &...) [with dim=96UL, Float=float, Index=unsigned int, Args=<>]"
/content/graphvite/src/graphvite.cu(56): here

/content/graphvite/include/instance/gpu/graph.cuh(263): warning: variable "vertex_buffer" was declared but never referenced
          detected during:
            instantiation of "void graphvite::gpu::graph::predict<Vector,Index,Model>(graphvite::Memory<Vector, Index>, graphvite::Memory<Vector, Index>, graphvite::Memory<Index, int>, graphvite::Memory<Vector::Float, int>) [with Vector=graphvite::Vector<96UL, float>, Index=unsigned int, Model=graphvite::Node2Vec]"
/content/graphvite/include/instance/graph.cuh(570): here
            instantiation of "__nv_bool graphvite::GraphWorker<_Solver>::predict_dispatch() [with _Solver=graphvite::SolverMixin<96UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            implicit generation of "graphvite::GraphWorker<_Solver>::~GraphWorker() [with _Solver=graphvite::SolverMixin<96UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of class "graphvite::GraphWorker<_Solver> [with _Solver=graphvite::SolverMixin<96UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of "graphvite::SolverMixin<_dim, _Float, _Index, _Graph, _Sampler, _Worker>::~SolverMixin() [with _dim=96UL, _Float=float, _Index=unsigned int, _Graph=graphvite::Graph, _Sampler=graphvite::GraphSampler, _Worker=graphvite::GraphWorker]"
/usr/include/c++/7/bits/unique_ptr.h(78): here
            [ 2 instantiation contexts not shown ]
            instantiation of "void std::default_delete<_Tp>::operator()(_Tp *) const [with _Tp=graphvite::GraphSolver<96UL, float, unsigned int>]"
/usr/include/c++/7/bits/unique_ptr.h(268): here
            instantiation of "std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp=graphvite::GraphSolver<96UL, float, unsigned int>, _Dp=std::default_delete<graphvite::GraphSolver<96UL, float, unsigned int>>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1351): here
            instantiation of "void pybind11::class_<type_, options...>::dealloc(pybind11::detail::value_and_holder &) [with type_=graphvite::GraphSolver<96UL, float, unsigned int>, options=<>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1080): here
            instantiation of "pybind11::class_<type_, options...>::class_(pybind11::handle, const char *, const Extra &...) [with type_=graphvite::GraphSolver<96UL, float, unsigned int>, options=<>, Extra=<>]"
/content/graphvite/include/bind.h(395): here
            instantiation of "pyGraphSolver<dim, Float, Index>::pyGraphSolver(pybind11::handle, const char *, const Args &...) [with dim=96UL, Float=float, Index=unsigned int, Args=<>]"
/content/graphvite/src/graphvite.cu(56): here

/content/graphvite/include/instance/gpu/graph.cuh(263): warning: variable "vertex_buffer" was declared but never referenced
          detected during:
            instantiation of "void graphvite::gpu::graph::predict<Vector,Index,Model>(graphvite::Memory<Vector, Index>, graphvite::Memory<Vector, Index>, graphvite::Memory<Index, int>, graphvite::Memory<Vector::Float, int>) [with Vector=graphvite::Vector<256UL, float>, Index=unsigned int, Model=graphvite::DeepWalk]"
/content/graphvite/include/instance/graph.cuh(566): here
            instantiation of "__nv_bool graphvite::GraphWorker<_Solver>::predict_dispatch() [with _Solver=graphvite::SolverMixin<256UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            implicit generation of "graphvite::GraphWorker<_Solver>::~GraphWorker() [with _Solver=graphvite::SolverMixin<256UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of class "graphvite::GraphWorker<_Solver> [with _Solver=graphvite::SolverMixin<256UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of "graphvite::SolverMixin<_dim, _Float, _Index, _Graph, _Sampler, _Worker>::~SolverMixin() [with _dim=256UL, _Float=float, _Index=unsigned int, _Graph=graphvite::Graph, _Sampler=graphvite::GraphSampler, _Worker=graphvite::GraphWorker]"
/usr/include/c++/7/bits/unique_ptr.h(78): here
            [ 2 instantiation contexts not shown ]
            instantiation of "void std::default_delete<_Tp>::operator()(_Tp *) const [with _Tp=graphvite::GraphSolver<256UL, float, unsigned int>]"
/usr/include/c++/7/bits/unique_ptr.h(268): here
            instantiation of "std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp=graphvite::GraphSolver<256UL, float, unsigned int>, _Dp=std::default_delete<graphvite::GraphSolver<256UL, float, unsigned int>>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1351): here
            instantiation of "void pybind11::class_<type_, options...>::dealloc(pybind11::detail::value_and_holder &) [with type_=graphvite::GraphSolver<256UL, float, unsigned int>, options=<>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1080): here
            instantiation of "pybind11::class_<type_, options...>::class_(pybind11::handle, const char *, const Extra &...) [with type_=graphvite::GraphSolver<256UL, float, unsigned int>, options=<>, Extra=<>]"
/content/graphvite/include/bind.h(395): here
            instantiation of "pyGraphSolver<dim, Float, Index>::pyGraphSolver(pybind11::handle, const char *, const Args &...) [with dim=256UL, Float=float, Index=unsigned int, Args=<>]"
/content/graphvite/src/graphvite.cu(57): here

/content/graphvite/include/instance/gpu/graph.cuh(263): warning: variable "vertex_buffer" was declared but never referenced
          detected during:
            instantiation of "void graphvite::gpu::graph::predict<Vector,Index,Model>(graphvite::Memory<Vector, Index>, graphvite::Memory<Vector, Index>, graphvite::Memory<Index, int>, graphvite::Memory<Vector::Float, int>) [with Vector=graphvite::Vector<256UL, float>, Index=unsigned int, Model=graphvite::LINE]"
/content/graphvite/include/instance/graph.cuh(568): here
            instantiation of "__nv_bool graphvite::GraphWorker<_Solver>::predict_dispatch() [with _Solver=graphvite::SolverMixin<256UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            implicit generation of "graphvite::GraphWorker<_Solver>::~GraphWorker() [with _Solver=graphvite::SolverMixin<256UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of class "graphvite::GraphWorker<_Solver> [with _Solver=graphvite::SolverMixin<256UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of "graphvite::SolverMixin<_dim, _Float, _Index, _Graph, _Sampler, _Worker>::~SolverMixin() [with _dim=256UL, _Float=float, _Index=unsigned int, _Graph=graphvite::Graph, _Sampler=graphvite::GraphSampler, _Worker=graphvite::GraphWorker]"
/usr/include/c++/7/bits/unique_ptr.h(78): here
            [ 2 instantiation contexts not shown ]
            instantiation of "void std::default_delete<_Tp>::operator()(_Tp *) const [with _Tp=graphvite::GraphSolver<256UL, float, unsigned int>]"
/usr/include/c++/7/bits/unique_ptr.h(268): here
            instantiation of "std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp=graphvite::GraphSolver<256UL, float, unsigned int>, _Dp=std::default_delete<graphvite::GraphSolver<256UL, float, unsigned int>>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1351): here
            instantiation of "void pybind11::class_<type_, options...>::dealloc(pybind11::detail::value_and_holder &) [with type_=graphvite::GraphSolver<256UL, float, unsigned int>, options=<>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1080): here
            instantiation of "pybind11::class_<type_, options...>::class_(pybind11::handle, const char *, const Extra &...) [with type_=graphvite::GraphSolver<256UL, float, unsigned int>, options=<>, Extra=<>]"
/content/graphvite/include/bind.h(395): here
            instantiation of "pyGraphSolver<dim, Float, Index>::pyGraphSolver(pybind11::handle, const char *, const Args &...) [with dim=256UL, Float=float, Index=unsigned int, Args=<>]"
/content/graphvite/src/graphvite.cu(57): here

/content/graphvite/include/instance/gpu/graph.cuh(263): warning: variable "vertex_buffer" was declared but never referenced
          detected during:
            instantiation of "void graphvite::gpu::graph::predict<Vector,Index,Model>(graphvite::Memory<Vector, Index>, graphvite::Memory<Vector, Index>, graphvite::Memory<Index, int>, graphvite::Memory<Vector::Float, int>) [with Vector=graphvite::Vector<256UL, float>, Index=unsigned int, Model=graphvite::Node2Vec]"
/content/graphvite/include/instance/graph.cuh(570): here
            instantiation of "__nv_bool graphvite::GraphWorker<_Solver>::predict_dispatch() [with _Solver=graphvite::SolverMixin<256UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            implicit generation of "graphvite::GraphWorker<_Solver>::~GraphWorker() [with _Solver=graphvite::SolverMixin<256UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of class "graphvite::GraphWorker<_Solver> [with _Solver=graphvite::SolverMixin<256UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of "graphvite::SolverMixin<_dim, _Float, _Index, _Graph, _Sampler, _Worker>::~SolverMixin() [with _dim=256UL, _Float=float, _Index=unsigned int, _Graph=graphvite::Graph, _Sampler=graphvite::GraphSampler, _Worker=graphvite::GraphWorker]"
/usr/include/c++/7/bits/unique_ptr.h(78): here
            [ 2 instantiation contexts not shown ]
            instantiation of "void std::default_delete<_Tp>::operator()(_Tp *) const [with _Tp=graphvite::GraphSolver<256UL, float, unsigned int>]"
/usr/include/c++/7/bits/unique_ptr.h(268): here
            instantiation of "std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp=graphvite::GraphSolver<256UL, float, unsigned int>, _Dp=std::default_delete<graphvite::GraphSolver<256UL, float, unsigned int>>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1351): here
            instantiation of "void pybind11::class_<type_, options...>::dealloc(pybind11::detail::value_and_holder &) [with type_=graphvite::GraphSolver<256UL, float, unsigned int>, options=<>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1080): here
            instantiation of "pybind11::class_<type_, options...>::class_(pybind11::handle, const char *, const Extra &...) [with type_=graphvite::GraphSolver<256UL, float, unsigned int>, options=<>, Extra=<>]"
/content/graphvite/include/bind.h(395): here
            instantiation of "pyGraphSolver<dim, Float, Index>::pyGraphSolver(pybind11::handle, const char *, const Args &...) [with dim=256UL, Float=float, Index=unsigned int, Args=<>]"
/content/graphvite/src/graphvite.cu(57): here

/content/graphvite/include/instance/gpu/graph.cuh(263): warning: variable "vertex_buffer" was declared but never referenced
          detected during:
            instantiation of "void graphvite::gpu::graph::predict<Vector,Index,Model>(graphvite::Memory<Vector, Index>, graphvite::Memory<Vector, Index>, graphvite::Memory<Index, int>, graphvite::Memory<Vector::Float, int>) [with Vector=graphvite::Vector<512UL, float>, Index=unsigned int, Model=graphvite::DeepWalk]"
/content/graphvite/include/instance/graph.cuh(566): here
            instantiation of "__nv_bool graphvite::GraphWorker<_Solver>::predict_dispatch() [with _Solver=graphvite::SolverMixin<512UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            implicit generation of "graphvite::GraphWorker<_Solver>::~GraphWorker() [with _Solver=graphvite::SolverMixin<512UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of class "graphvite::GraphWorker<_Solver> [with _Solver=graphvite::SolverMixin<512UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of "graphvite::SolverMixin<_dim, _Float, _Index, _Graph, _Sampler, _Worker>::~SolverMixin() [with _dim=512UL, _Float=float, _Index=unsigned int, _Graph=graphvite::Graph, _Sampler=graphvite::GraphSampler, _Worker=graphvite::GraphWorker]"
/usr/include/c++/7/bits/unique_ptr.h(78): here
            [ 2 instantiation contexts not shown ]
            instantiation of "void std::default_delete<_Tp>::operator()(_Tp *) const [with _Tp=graphvite::GraphSolver<512UL, float, unsigned int>]"
/usr/include/c++/7/bits/unique_ptr.h(268): here
            instantiation of "std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp=graphvite::GraphSolver<512UL, float, unsigned int>, _Dp=std::default_delete<graphvite::GraphSolver<512UL, float, unsigned int>>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1351): here
            instantiation of "void pybind11::class_<type_, options...>::dealloc(pybind11::detail::value_and_holder &) [with type_=graphvite::GraphSolver<512UL, float, unsigned int>, options=<>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1080): here
            instantiation of "pybind11::class_<type_, options...>::class_(pybind11::handle, const char *, const Extra &...) [with type_=graphvite::GraphSolver<512UL, float, unsigned int>, options=<>, Extra=<>]"
/content/graphvite/include/bind.h(395): here
            instantiation of "pyGraphSolver<dim, Float, Index>::pyGraphSolver(pybind11::handle, const char *, const Args &...) [with dim=512UL, Float=float, Index=unsigned int, Args=<>]"
/content/graphvite/src/graphvite.cu(58): here

/content/graphvite/include/instance/gpu/graph.cuh(263): warning: variable "vertex_buffer" was declared but never referenced
          detected during:
            instantiation of "void graphvite::gpu::graph::predict<Vector,Index,Model>(graphvite::Memory<Vector, Index>, graphvite::Memory<Vector, Index>, graphvite::Memory<Index, int>, graphvite::Memory<Vector::Float, int>) [with Vector=graphvite::Vector<512UL, float>, Index=unsigned int, Model=graphvite::LINE]"
/content/graphvite/include/instance/graph.cuh(568): here
            instantiation of "__nv_bool graphvite::GraphWorker<_Solver>::predict_dispatch() [with _Solver=graphvite::SolverMixin<512UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            implicit generation of "graphvite::GraphWorker<_Solver>::~GraphWorker() [with _Solver=graphvite::SolverMixin<512UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of class "graphvite::GraphWorker<_Solver> [with _Solver=graphvite::SolverMixin<512UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of "graphvite::SolverMixin<_dim, _Float, _Index, _Graph, _Sampler, _Worker>::~SolverMixin() [with _dim=512UL, _Float=float, _Index=unsigned int, _Graph=graphvite::Graph, _Sampler=graphvite::GraphSampler, _Worker=graphvite::GraphWorker]"
/usr/include/c++/7/bits/unique_ptr.h(78): here
            [ 2 instantiation contexts not shown ]
            instantiation of "void std::default_delete<_Tp>::operator()(_Tp *) const [with _Tp=graphvite::GraphSolver<512UL, float, unsigned int>]"
/usr/include/c++/7/bits/unique_ptr.h(268): here
            instantiation of "std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp=graphvite::GraphSolver<512UL, float, unsigned int>, _Dp=std::default_delete<graphvite::GraphSolver<512UL, float, unsigned int>>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1351): here
            instantiation of "void pybind11::class_<type_, options...>::dealloc(pybind11::detail::value_and_holder &) [with type_=graphvite::GraphSolver<512UL, float, unsigned int>, options=<>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1080): here
            instantiation of "pybind11::class_<type_, options...>::class_(pybind11::handle, const char *, const Extra &...) [with type_=graphvite::GraphSolver<512UL, float, unsigned int>, options=<>, Extra=<>]"
/content/graphvite/include/bind.h(395): here
            instantiation of "pyGraphSolver<dim, Float, Index>::pyGraphSolver(pybind11::handle, const char *, const Args &...) [with dim=512UL, Float=float, Index=unsigned int, Args=<>]"
/content/graphvite/src/graphvite.cu(58): here

/content/graphvite/include/instance/gpu/graph.cuh(263): warning: variable "vertex_buffer" was declared but never referenced
          detected during:
            instantiation of "void graphvite::gpu::graph::predict<Vector,Index,Model>(graphvite::Memory<Vector, Index>, graphvite::Memory<Vector, Index>, graphvite::Memory<Index, int>, graphvite::Memory<Vector::Float, int>) [with Vector=graphvite::Vector<512UL, float>, Index=unsigned int, Model=graphvite::Node2Vec]"
/content/graphvite/include/instance/graph.cuh(570): here
            instantiation of "__nv_bool graphvite::GraphWorker<_Solver>::predict_dispatch() [with _Solver=graphvite::SolverMixin<512UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            implicit generation of "graphvite::GraphWorker<_Solver>::~GraphWorker() [with _Solver=graphvite::SolverMixin<512UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of class "graphvite::GraphWorker<_Solver> [with _Solver=graphvite::SolverMixin<512UL, float, unsigned int, graphvite::Graph, graphvite::GraphSampler, graphvite::GraphWorker>]"
/content/graphvite/include/core/solver.h(223): here
            instantiation of "graphvite::SolverMixin<_dim, _Float, _Index, _Graph, _Sampler, _Worker>::~SolverMixin() [with _dim=512UL, _Float=float, _Index=unsigned int, _Graph=graphvite::Graph, _Sampler=graphvite::GraphSampler, _Worker=graphvite::GraphWorker]"
/usr/include/c++/7/bits/unique_ptr.h(78): here
            [ 2 instantiation contexts not shown ]
            instantiation of "void std::default_delete<_Tp>::operator()(_Tp *) const [with _Tp=graphvite::GraphSolver<512UL, float, unsigned int>]"
/usr/include/c++/7/bits/unique_ptr.h(268): here
            instantiation of "std::unique_ptr<_Tp, _Dp>::~unique_ptr() [with _Tp=graphvite::GraphSolver<512UL, float, unsigned int>, _Dp=std::default_delete<graphvite::GraphSolver<512UL, float, unsigned int>>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1351): here
            instantiation of "void pybind11::class_<type_, options...>::dealloc(pybind11::detail::value_and_holder &) [with type_=graphvite::GraphSolver<512UL, float, unsigned int>, options=<>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1080): here
            instantiation of "pybind11::class_<type_, options...>::class_(pybind11::handle, const char *, const Extra &...) [with type_=graphvite::GraphSolver<512UL, float, unsigned int>, options=<>, Extra=<>]"
/content/graphvite/include/bind.h(395): here
            instantiation of "pyGraphSolver<dim, Float, Index>::pyGraphSolver(pybind11::handle, const char *, const Args &...) [with dim=512UL, Float=float, Index=unsigned int, Args=<>]"
/content/graphvite/src/graphvite.cu(58): here

/usr/local/include/python3.7m/pybind11/cast.h(1003): warning: pointless comparison of unsigned integer with zero
          detected during:
            instantiation of "__nv_bool pybind11::detail::type_caster<T, pybind11::detail::enable_if_t<<expression>, void>>::load(pybind11::handle, __nv_bool) [with T=pybind11::detail::intrinsic_t<pybind11::detail::conditional_t<false, pybind11::detail::void_type, const unsigned int &>>]"
(1927): here
            instantiation of "__nv_bool pybind11::detail::argument_loader<Args...>::load_impl_sequence(pybind11::detail::function_call &, pybind11::detail::index_sequence<Is...>) [with Args=<pybind11::detail::value_and_holder &, unsigned int>, Is=<0UL, 1UL>]"
(1907): here
            instantiation of "__nv_bool pybind11::detail::argument_loader<Args...>::load_args(pybind11::detail::function_call &) [with Args=<pybind11::detail::value_and_holder &, unsigned int>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(141): here
            instantiation of "void pybind11::cpp_function::initialize(Func &&, Return (*)(Args...), const Extra &...) [with Func=lambda [](pybind11::detail::value_and_holder &, unsigned int)->void, Return=void, Args=<pybind11::detail::value_and_holder &, unsigned int>, Extra=<pybind11::name, pybind11::is_method, pybind11::sibling, pybind11::detail::is_new_style_constructor>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(72): here
            instantiation of "pybind11::cpp_function::cpp_function(Func &&, const Extra &...) [with Func=lambda [](pybind11::detail::value_and_holder &, unsigned int)->void, Extra=<pybind11::name, pybind11::is_method, pybind11::sibling, pybind11::detail::is_new_style_constructor>, <unnamed>=void]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1112): here
            instantiation of "pybind11::class_<type_, options...> &pybind11::class_<type_, options...>::def(const char *, Func &&, const Extra &...) [with type_=DType, options=<>, Func=lambda [](pybind11::detail::value_and_holder &, unsigned int)->void, Extra=<pybind11::detail::is_new_style_constructor>]"
/usr/local/include/python3.7m/pybind11/detail/init.h(239): here
            instantiation of "void pybind11::detail::initimpl::factory<Func, pybind11::detail::void_type (*)(), Return (Args...), pybind11::detail::function_signature_t<pybind11::detail::void_type (*)(), pybind11::detail::remove_reference_t<pybind11::detail::void_type (*)()>>>::execute(Class &, const Extra &...) && [with Func=lambda [](unsigned int)->DType, Return=DType, Args=<unsigned int>, Class=pybind11::class_<DType>, Extra=<>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1153): here
            instantiation of "pybind11::class_<type_, options...> &pybind11::class_<type_, options...>::def(pybind11::detail::initimpl::factory<Args...> &&, const Extra &...) [with type_=DType, options=<>, Args=<lambda [](unsigned int)->DType, pybind11::detail::void_type (*)(), DType (unsigned int), pybind11::detail::void_type ()>, Extra=<>]"
/usr/local/include/python3.7m/pybind11/pybind11.h(1564): here
            instantiation of "pybind11::enum_<Type>::enum_(const pybind11::handle &, const char *, const Extra &...) [with Type=DType, Extra=<>]"
/content/graphvite/src/graphvite.cu(78): here

[ 90%] Linking CUDA device code CMakeFiles/graphvite.dir/cmake_device_link.o
[100%] Linking CUDA shared library ../lib/libgraphvite.so
[100%] Built target graphvite
/content/graphvite
/content/graphvite/python
running install
running bdist_egg
running egg_info
creating graphvite.egg-info
writing graphvite.egg-info/PKG-INFO
writing dependency_links to graphvite.egg-info/dependency_links.txt
writing entry points to graphvite.egg-info/entry_points.txt
writing top-level names to graphvite.egg-info/top_level.txt
writing manifest file 'graphvite.egg-info/SOURCES.txt'
reading manifest file 'graphvite.egg-info/SOURCES.txt'
writing manifest file 'graphvite.egg-info/SOURCES.txt'
installing library code to build/bdist.linux-x86_64/egg
running install_lib
running build_py
creating build
creating build/lib
creating build/lib/graphvite
copying graphvite/__init__.py -> build/lib/graphvite
copying graphvite/base.py -> build/lib/graphvite
copying graphvite/solver.py -> build/lib/graphvite
copying graphvite/dataset.py -> build/lib/graphvite
copying graphvite/cmd.py -> build/lib/graphvite
copying graphvite/optimizer.py -> build/lib/graphvite
copying graphvite/util.py -> build/lib/graphvite
copying graphvite/graph.py -> build/lib/graphvite
copying graphvite/helper.py -> build/lib/graphvite
creating build/lib/graphvite/application
copying graphvite/application/__init__.py -> build/lib/graphvite/application
copying graphvite/application/application.py -> build/lib/graphvite/application
copying graphvite/application/network.py -> build/lib/graphvite/application
creating build/bdist.linux-x86_64
creating build/bdist.linux-x86_64/egg
creating build/bdist.linux-x86_64/egg/graphvite
creating build/bdist.linux-x86_64/egg/graphvite/application
copying build/lib/graphvite/application/__init__.py -> build/bdist.linux-x86_64/egg/graphvite/application
copying build/lib/graphvite/application/application.py -> build/bdist.linux-x86_64/egg/graphvite/application
copying build/lib/graphvite/application/network.py -> build/bdist.linux-x86_64/egg/graphvite/application
copying build/lib/graphvite/__init__.py -> build/bdist.linux-x86_64/egg/graphvite
copying build/lib/graphvite/base.py -> build/bdist.linux-x86_64/egg/graphvite
copying build/lib/graphvite/solver.py -> build/bdist.linux-x86_64/egg/graphvite
copying build/lib/graphvite/dataset.py -> build/bdist.linux-x86_64/egg/graphvite
copying build/lib/graphvite/cmd.py -> build/bdist.linux-x86_64/egg/graphvite
copying build/lib/graphvite/optimizer.py -> build/bdist.linux-x86_64/egg/graphvite
copying build/lib/graphvite/util.py -> build/bdist.linux-x86_64/egg/graphvite
copying build/lib/graphvite/graph.py -> build/bdist.linux-x86_64/egg/graphvite
copying build/lib/graphvite/helper.py -> build/bdist.linux-x86_64/egg/graphvite
byte-compiling build/bdist.linux-x86_64/egg/graphvite/application/__init__.py to __init__.cpython-37.pyc
byte-compiling build/bdist.linux-x86_64/egg/graphvite/application/application.py to application.cpython-37.pyc
byte-compiling build/bdist.linux-x86_64/egg/graphvite/application/network.py to network.cpython-37.pyc
byte-compiling build/bdist.linux-x86_64/egg/graphvite/__init__.py to __init__.cpython-37.pyc
byte-compiling build/bdist.linux-x86_64/egg/graphvite/base.py to base.cpython-37.pyc
byte-compiling build/bdist.linux-x86_64/egg/graphvite/solver.py to solver.cpython-37.pyc
byte-compiling build/bdist.linux-x86_64/egg/graphvite/dataset.py to dataset.cpython-37.pyc
byte-compiling build/bdist.linux-x86_64/egg/graphvite/cmd.py to cmd.cpython-37.pyc
byte-compiling build/bdist.linux-x86_64/egg/graphvite/optimizer.py to optimizer.cpython-37.pyc
byte-compiling build/bdist.linux-x86_64/egg/graphvite/util.py to util.cpython-37.pyc
byte-compiling build/bdist.linux-x86_64/egg/graphvite/graph.py to graph.cpython-37.pyc
byte-compiling build/bdist.linux-x86_64/egg/graphvite/helper.py to helper.cpython-37.pyc
installing package data to build/bdist.linux-x86_64/egg
running install_data
creating build/bdist.linux-x86_64/egg/graphvite/lib
copying /content/graphvite/build/lib/libgraphvite.so -> build/bdist.linux-x86_64/egg/graphvite/lib
copying /content/graphvite/build/lib/libfaiss.so -> build/bdist.linux-x86_64/egg/graphvite/lib
creating build/bdist.linux-x86_64/egg/graphvite/config
creating build/bdist.linux-x86_64/egg/graphvite/config/demo
copying /content/graphvite/config/demo/quick_start.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/demo
copying /content/graphvite/config/demo/math.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/demo
creating build/bdist.linux-x86_64/egg/graphvite/config/graph
copying /content/graphvite/config/graph/deepwalk_youtube.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/graph
copying /content/graphvite/config/graph/deepwalk_friendster.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/graph
copying /content/graphvite/config/graph/deepwalk_hyperlink-pld.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/graph
copying /content/graphvite/config/graph/line_friendster.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/graph
copying /content/graphvite/config/graph/node2vec_youtube.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/graph
copying /content/graphvite/config/graph/line_hyperlink-pld.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/graph
copying /content/graphvite/config/graph/line_youtube.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/graph
copying /content/graphvite/config/graph/line_friendster-small.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/graph
copying /content/graphvite/config/graph/deepwalk_flickr.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/graph
copying /content/graphvite/config/graph/line_flickr.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/graph
copying /content/graphvite/config/graph/deepwalk_friendster-small.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/graph
creating build/bdist.linux-x86_64/egg/graphvite/config/template
copying /content/graphvite/config/template/word_graph.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/template
copying /content/graphvite/config/template/knowledge_graph.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/template
copying /content/graphvite/config/template/visualization.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/template
copying /content/graphvite/config/template/graph.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/template
creating build/bdist.linux-x86_64/egg/graphvite/config/word_graph
copying /content/graphvite/config/word_graph/line_wikipedia.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/word_graph
creating build/bdist.linux-x86_64/egg/graphvite/config/visualization
copying /content/graphvite/config/visualization/largevis_mnist_2d.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/visualization
copying /content/graphvite/config/visualization/largevis_imagenet.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/visualization
copying /content/graphvite/config/visualization/largevis_mnist_3d.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/visualization
creating build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/simple_fb15k.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/complex_fb15k-237.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/rotate_fb15k.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/transe_wn18.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/complex_wn18.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/transe_wikidata5m.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/rotate_fb15k-237.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/distmult_wn18rr.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/simple_wn18rr.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/transe_fb15k.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/rotate_wikidata5m.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/simple_wn18.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/complex_wn18rr.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/rotate_wn18rr.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/simple_wikidata5m.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/distmult_wn18.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/distmult_fb15k-237.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/rotate_wn18.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/simple_fb15k-237.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/distmult_fb15k.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/transe_wn18rr.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/distmult_wikidata5m.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/complex_fb15k.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/transe_fb15k-237.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
copying /content/graphvite/config/knowledge_graph/complex_wikidata5m.yaml -> build/bdist.linux-x86_64/egg/graphvite/config/knowledge_graph
creating build/bdist.linux-x86_64/egg/EGG-INFO
copying graphvite.egg-info/PKG-INFO -> build/bdist.linux-x86_64/egg/EGG-INFO
copying graphvite.egg-info/SOURCES.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying graphvite.egg-info/dependency_links.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying graphvite.egg-info/entry_points.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
copying graphvite.egg-info/not-zip-safe -> build/bdist.linux-x86_64/egg/EGG-INFO
copying graphvite.egg-info/top_level.txt -> build/bdist.linux-x86_64/egg/EGG-INFO
creating dist
creating 'dist/graphvite-0.2.1-py3.7.egg' and adding 'build/bdist.linux-x86_64/egg' to it
removing 'build/bdist.linux-x86_64/egg' (and everything under it)
Processing graphvite-0.2.1-py3.7.egg
creating /usr/local/lib/python3.7/site-packages/graphvite-0.2.1-py3.7.egg
Extracting graphvite-0.2.1-py3.7.egg to /usr/local/lib/python3.7/site-packages
Adding graphvite 0.2.1 to easy-install.pth file
Installing graphvite script to /usr/local/bin

Installed /usr/local/lib/python3.7/site-packages/graphvite-0.2.1-py3.7.egg
Processing dependencies for graphvite==0.2.1
Finished processing dependencies for graphvite==0.2.1
/content/graphvite

But when i run
!graphvite baseline quick start

i get the error:
running baseline: demo/quick_start.yaml
downloading http://socialcomputing.asu.edu/uploads/1283153973/BlogCatalog-dataset.zip to BlogCatalog-dataset.zip
extracting BlogCatalog-dataset/data/edges.csv from BlogCatalog-dataset.zip to edges.csv
converting edges.csv to blogcatalog_graph.txt
splitting graph blogcatalog_graph.txt into blogcatalog_train.txt, blogcatalog_valid.txt, blogcatalog_test.txt
extracting BlogCatalog-dataset/data/group-edges.csv from BlogCatalog-dataset.zip to group-edges.csv
converting group-edges.csv to blogcatalog_label.txt
loading graph from /root/.graphvite/dataset/blogcatalog/blogcatalog_train.txt
0.00018755%
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<
Graph<uint32>
------------------ Graph -------------------
#vertex: 10308, #edge: 327429
as undirected: yes, normalization: no
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
[time] GraphApplication.load: 0.0654581 s
#CPU threads is beyond the hardware concurrency
Check failed: error == CURAND_STATUS_SUCCESS CURAND error 203 at /content/graphvite/include/core/solver.h:950
*** Check failure stack trace: ***
    @     0x7f9397bfa4dd  google::LogMessage::Fail()
    @     0x7f9397c02071  google::LogMessage::SendToLog()
    @     0x7f9397bf9ecd  google::LogMessage::Flush()
    @     0x7f9397bfb76a  google::LogMessageFatal::~LogMessageFatal()
    @     0x7f939bd0b1d7  graphvite::CurandCheck()
    @     0x7f939be68564  graphvite::SolverMixin<>::SolverMixin()
    @     0x7f939beab1fd  _ZZN8pybind1112cpp_function10initializeIZNS_6detail8initimpl11constructorIJSt6vectorIiSaIiEEimEE7executeINS_6class_IN9graphvite11GraphSolverILm128EfjEEJEEEJNS_10call_guardIJNS_18gil_scoped_releaseEEEENS_5arg_vESI_SI_ELi0EEEvRT_DpRKT0_EUlRNS2_16value_and_holderES7_imE_vJSQ_S7_imEJNS_4nameENS_9is_methodENS_7siblingENS2_24is_new_style_constructorESH_SI_SI_SI_EEEvOSJ_PFT0_DpT1_EDpRKT2_ENUlRNS2_13function_callEE1_4_FUNES17_
    @     0x7f939bdc3869  pybind11::cpp_function::dispatcher()
    @     0x5561d76cc63d  _PyMethodDef_RawFastCallDict
    @     0x5561d76cc7c1  _PyCFunction_FastCallDict
    @     0x5561d76cae53  _PyObject_Call_Prepend
    @     0x5561d76bddbe  PyObject_Call
    @     0x5561d7635214  slot_tp_init.cold.1880
    @     0x5561d7703327  type_call
    @     0x5561d76bddbe  PyObject_Call
    @     0x5561d7764232  _PyEval_EvalFrameDefault
    @     0x5561d76ab539  _PyEval_EvalCodeWithName
    @     0x5561d76ac635  _PyFunction_FastCallDict
    @     0x5561d76caece  _PyObject_Call_Prepend
    @     0x5561d77055ce  slot_tp_new
    @     0x5561d7703529  _PyObject_FastCallKeywords
    @     0x5561d77676e8  _PyEval_EvalFrameDefault
    @     0x5561d76ab539  _PyEval_EvalCodeWithName
    @     0x5561d76ac860  _PyFunction_FastCallDict
    @     0x5561d76cae53  _PyObject_Call_Prepend
    @     0x5561d76bddbe  PyObject_Call
    @     0x5561d7764232  _PyEval_EvalFrameDefault
    @     0x5561d76ab539  _PyEval_EvalCodeWithName
    @     0x5561d76ac860  _PyFunction_FastCallDict
    @     0x5561d7764232  _PyEval_EvalFrameDefault
    @     0x5561d76abd09  _PyEval_EvalCodeWithName
    @     0x5561d76ac860  _PyFunction_FastCallDict

How could i solve it ?
thanks for your time.

This is because you install cudatoolkit 10.2, while Colab only has CUDA 10.0 driver support. You may explicitly specify the version by conda install -y --file conda/requirements.txt cudatoolkit=10.0.
Btw, do you really need to compile from source on Colab? It's more easy if you directly install from conda on colab.

This is because you install cudatoolkit 10.2, while Colab only has CUDA 10.0 driver support. You may explicitly specify the version by conda install -y --file conda/requirements.txt cudatoolkit=10.0.
Btw, do you really need to compile from source on Colab? It's more easy if you directly install from conda on Colab.

Thanks for your help. i get the rigth result.
i want to customize the model,but I didn't have the hadware equipment that meets the graphvite's requirements, so i truly need to compile from source on colab.


Windows Version

May we have a windows version please?

xwiimote relies on hid-wiimote, which is a linux kernel module. It is not available for Windows.

How much does that differ from this hid-wiimote?


about screen - updated design

What would you like to be added:

[ ] Remove link from settings for community page
[ ] Update link from About -. Participate with active community -> community screen

https://www.figma.com/proto/SDIpZciuxJlUf4xf8yheiY/Light-Wallet?node-id=841%3A29184&viewport=241%2C48%2C0.7&scaling=scale-down&starting-point-node-id=841%3A28305&show-proto-sidebar=1
Why is this needed:

Acceptance Criteria
Expected: About contents updated layout
Android:
Settings >About > displays:

[ ] Social media: YouTube, Twitter, Reddit, GitHub
[ ] Knowledge base
[ ] Participate with active community
[ ] DeFiChain Explorer
[ ] View official website
[ ] Privacy policy
[ ] Licenses
[ ] Whitepaper

iOS:
Settings >About > displays:

[ ] Social media: YouTube, Twitter, Reddit, GitHub
[ ] Knowledge base
[ ] Participate with active community
[ ] DeFiChain Explorer
[ ] View official website
[ ] Privacy policy
[ ] Licenses
[ ] Whitepaper


Update README.md

Insert description of PR here

✅ By submitting this PR, I have verified the following
Guidelines
Content

If adding new advice or content,

[] A tool like Grammarly was utilized to check for spelling and grammar.

Resources

If adding a new resource,

[] There is a link to the resource.
[] There is a description describing what benefits the resource offers.

Formatting

[] No whitespace.
[] Spaces, not tabs. Specifically, 2 spaces.
[] Make sure items in lists are alphabetized.

Adding yourself as a contributor.

[] Added my name to the bottom of the list under the Credits section in the README.md with a link to my website or GitHub profile 👥

@ArviiChoudhary can you link the contribution you made? not sure if I can find it. thank you!


Add RowBinary format for SELECT operations

Work in progress in this branch: https://github.com/ClickHouse/clickhouse-js/compare/1.0.0...row_binary
If you have any feedback on the following, please don't hesitate to comment.
Streaming will be supported out of the box by design.
Target supported ClickHouse data types with SELECT operations for the initial 1.1.0 release; certain types are already completed in the branch:

[x] Boolean
[x] (U)Int8-32 as number
[x] (U)Int64-256 as a native BigInt
[x] Float32, Float64 as a number
[x] String as a string
[x] Nullable, LowCardinality
[x] Date, Date32 as either a JS Date, a string, or UNIX seconds as a number/BigInt by default (needs the decision to be consistent with DateTime family types), with a custom mapper support.
[ ] DateTime, DateTime64 - with a custom mapper support. DateTime could be either an ISO format string or BigInt UNIX seconds. DateTime64 should be either a string or UNIX nanoseconds as a BigInt.
[ ] Enum - needs a decision. Maybe as a string by default, with a custom mapper (index) -> T
[ ] UUID as a string
[ ] FixedString(N) as a string
[ ] IPv4/v6 as a string
[ ] Decimal as string by default, support custom mapper
[ ] Array(T) -  should use custom mappers provided for the value type
[ ] Map(K, V) -  should use custom mappers provided for K and V types
[ ] Tuple(T1, T2, ...) - should use custom mappers provided for T* types
[ ] Geo types - likely, should use [number, number] for Point as the base for the remaining Geo types.

The types that may be included as well, depending on the format complexity:

[ ] Variant(T1, T2, ...) - should use custom mappers provided for T* types.
[ ] SimpleAggregateFunction - could be trivial; needs clarification.
[ ] Nested - needs clarification.
[ ] JSON - maybe not, as it is still experimental; see also this guide about working with JSON in ClickHouse.

INSERT operations with RowBinary will likely be supported in 1.2.0+.
Related issues:

#25 - branched out of that one
https://github.com/ClickHouse/clickhouse-js/issues/212 - feature request, as RowBinary could provide performance benefits
#215 - somewhat related; that one was about INSERT operations. However, RowBinary implementation allows us to implement data mappers for specific data types for both SELECT and INSERT; these types are Date, Date32, DateTime, DateTime64, and Decimal (taking Array or Map values into consideration, too), as the user might want to get Luxon/Decimal.js/etc objects right away.

@slvrtrn Thanks for working on this! I'm watching this topic closely since it'll be useful for the work I do. Since my workload also contains Arrays and Maps (to better cope with semi-hierarchical data) and even Nested types.
Guess I'll wait until Arrays and Maps are supported before jumping in. I also consider moving away from Nested, since it tends to make things more complicated and support for de-/serializing is often lacking / coming last.
Often I can use Maps to replace Nested.
Again, thanks for working on this. I plan at least to support in testing once progress is enough for my usecases.
Clickhouse and this Client are both very awesome! :1st_place_medal:

@cjk, thanks for your feedback. I haven't looked into Nested yet, as the core part was to get the numeric types right first, but I believe it will be one of the trickier data types to implement there.
If you could provide a sample dataset for benchmarks or just table DDLs (I will just generate the random data there in the right shape), that would be great.


Observation Count Not In Proper English

"0 observation"
cc @floatplane

really a duplicate of #329

fixed


Upgrade coredependencies

Ugraded core dependencies. It's related to https://github.com/kytos-ng/kytos/pull/284.
I've also upgraded pylint and fixed linter errors that showed up.
For now, feature/upgrade_dependencies kytos branch is pinned just so tests pass in the CI. I'll revert this after before this PR gets merged after review.

I've also ignored missing-timeout linter errors, they'll be handled in the future on issue #184
Explored locally after bumping a minor patch on openapi-core it's working as intended:
{
    "code": 400,
    "description": "The request body contains invalid API data. 1 is not of type string for field uni_a/interface_id.",
    "name": "Bad Request"
}

https://github.com/kytos-ng/kytos/pull/284 has landed, I'll go ahead and merge this.


How to mimick the '?file=' query parameter via javaScript

Hi,
How can I mimic the http://localhost/viewer.html?file=abc.pdf' via JavaScript?
I post a message via postMessage from my web app in which host an iFrame which has its source set to the viewer.html.
In the Viewer.html, I capture the message via the addEventListener but I need to load the relevant pdf file via code but I don't understand how to get it to work using the Viewer.html in order to mimic the '?file=' behaviour.
`

Hi,
I've actually figured it out. I don't know if this is correct or not, but it seems to work ok using the following:
``

Note that I've noticed a couple of problem using this method:

Memory leaks: The memory used by the browser keeps on increasing over and over and while it doesn't seem to go over a certain amount i.e. 280Mb/300Mb, it does start at 85Mb and even when calling the 'PDFViewerApplication.cleanup();' it does not seem to have any effect regarding releasing memory.

When flicking from one document to another over and over, it does a weird thing with the Zoom In, Zoom Out and the Zoom dropdown where it moves it out of the toolbar and displays it over the viewer and it remains there until I close the browser.

I've attached a screencast where you can clearly see the issue: Odd toolbar behaviour
I'll revert my code back tomorrow and see if the same happens when using the file query parameter.

Please note that the toolbar does not get messed up when opening multiple documents one after the other when using the query string parameter ?file= so something must not be reset when calling the above code event though it is technically the same as what is in the webViewerLoad method which calls the 'pdfjsWebApp.PDFViewerApplication.run'.

You have two options:

Make a custom viewer using the viewer components (see the examples/components folder) so you can just use var loadingTask = pdfjsLib.getDocument(url); loadingTask.promise.then(function(pdf) {....
Edit the default viewer and check how the default URL is set in code.

Memory leaks may happen if you don't close the file properly when reloading. Hence, it's best to reuse the logic that is already there to open and close files. Refer to:
https://github.com/mozilla/pdf.js/blob/master/web/app.js#L695


508: Focus Issue when Closing Import

When closing the import pop-up, focus does not return to the Import Data Button

Testing complete, closing the import pop up now puts focus on the Import Data Button


Cycle detection failed when resourceExplorer LoadType function use AdaptiveDialog as the type

Github issues should be used for bugs and feature requests. Use Stack Overflow for general "how-to" questions.
Version
4.11.1
Describe the bug
When use resourceExplorer.LoadType function to load the adaptive dialogs that has dialog call loop in it, the cycle detection function will not detect the cycle correctly and new DIalogManager will three exception.
To Reproduce
Steps to reproduce the behavior:

Create a adaptive bot will loop in it, such as the sample here https://github.com/microsoft/botbuilder-dotnet/tree/main/tests/Microsoft.Bot.Builder.TestBot.Json/Samples/CycleDetection
Load this bot with resourceExplorer.LoadType<AdaptiveDialog> instead of resource.LoadType<Dialog>
New DialogManager with the loaded adaptive bot
You will see the Object reference not set to an instance of an object exception thrown from EnsureDependenciesInstalled() function

Expected behavior
No exception should be thrown
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
LoadType<AdaptiveDialog> and LoadType<Dialog> has different dialog stack for the same adaptive dialog. For bot that has loop in it, the different dialog call stack will cause the CycleDetectionObserver fail on cycle detection.

cc @EricDahlvang

Checking this and circling back with Eric.

Checking this and circling back with Eric.


Converting more than one slide at a time fails

On Mac OS 10.15.5 when I use the same PDF, I am able to convert each slide to a PNG, one slide at a time.  However, if I specify more than one slide at a time or all slides, I get this error:
(node:88658) UnhandledPromiseRejectionWarning: Error: Command failed: GPL Ghostscript 9.52: Unrecoverable error, exit code 1
gm convert: "gs" "-q" "-dBATCH" "-dSAFER" "-dMaxBitmap=50000000" "-dNOPAUSE" "-sDEVICE=ppmraw" "-dTextAlphaBits=4" "-dGraphicsAlphaBits=4" "-r100x100" "-dFirstPage=18446744073709551615" "-dLastPage=18446744073709551615" "-sOutputFile=/var/folders/rw/mlnbjynj2qsc7bfjvx_wdxth0000gn/T/gmm0uuxL" "--" "/var/folders/rw/mlnbjynj2qsc7bfjvx_wdxth0000gn/T/gm8LT82h" "-c" "quit".
gm convert: Postscript delegate failed (/var/folders/rw/mlnbjynj2qsc7bfjvx_wdxth0000gn/T/gmpqgZXA).

    at ChildProcess.onExit (/Users/fstrecker/dev-ng/gw-server/node_modules/gm/lib/command.js:301:17)
    at ChildProcess.emit (events.js:198:13)
    at maybeClose (internal/child_process.js:982:16)
    at Process.ChildProcess._handle.onexit (internal/child_process.js:259:5)
(node:88658) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). (rejection id: 1)
(node:88658) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

It seems that this also has an uncaught error that should be caught and dealt with to avoid the server being killed.
Debian 10 has the exact same issue.  Just confirmed it.

Was totally my fault for not noticing convertBulk vs convert.


new list -> blocklists-unit42-silverterrier

based on panunit42 silverterrier (nigerian emal scam)
Source ->
https://raw.githubusercontent.com/scafroglia93/blocklists/master/blocklists-unit42-silverterrier.txt

I've actually been researching some of these sources: https://github.com/T145/the-blacklist/issues/22
Can you give some more details on them? I'm interested in hearing some of your research, as https://github.com/pan-unit42/iocs is a bit daunting at first glance.


Wrong arguments for equals()

In https://github.com/OSGeo/PROJ-JNI/blob/1e06ea8225bc0355bbbe8030fdbb4e8010c80469/src/main/java/org/osgeo/proj/SimpleDirectPosition.java#L141 a CRS is compared to a boolean. I guess it needs to be like this:
return Objects.equals(crs, other.getCoordinateReferenceSystem())

Indeed, thanks for spotting that! I just pushed the fix.


Convert to promises, add header footer

I wanted to add header/footer functionality to support common-JS style import of pre-compiled templates.
The asynchronous code was hard to follow and very hard to add strict ordering semantics.  I converted all asynchronous code to promises which has made templito much more deterministic.
I also added header/footer functionality and added an example header/footer for amd/cjs/global defintion support

Hi, Daniel
I just made you a collaborator, and I went ahead a merged it. I haven't had a need for this since I left minted, so I would be happy to transfer ownership of the repo to minted if that makes things easier for you guys.
Sorry about the coffeescript :P


Update vizualizer to include latest from main

given that we are going to continue with the cytoscape branch instead, I am closing this PR


Proposal: Grammatical Typology to Enable Advanced Tooling

Crosspost from https://github.com/cujojs/most/issues/516
Observables are one of the most general abstractions we have available in Computer Science. They provide a common interface to operate on singular or plural and synchronous or asynchronous items.
But programming with Observables is a path riddled with traps, partly due to its novelty, but also that our tooling mostly is built around synchronous imperative code, and not asynchronous functional code.
Typing can get us really far in removing common errors when piping Observables through our code, but our types are not going to help us with the problem of time.
I have spent some days philosophizing whether we need a temporal-type to decorate our Observables, to get a better immediate idea of the consequences when merging, combining, delaying, debouncing, skipping, etc...
At first I set out to categories Observables in my own made-up categories, but then I realized we already have a quite extensive and rigid categorization of temporal events, this system is known as Grammar more properly conjugation, and it provides us with an opportunity to type our Observables not just with their expected value, but when that value might arrive.
In Latin conjugation we can operate with four dimensions, mood, voice, tense, and person. These four dimensions map well to what we need to properly time-categorize Streams.
Grammatical Mood
Grammatical mood helps us know the certainty of an event. Moods can be divided into Realis and Irrealis, things that are certain, and things that are uncurtain. Indicative is a Realis mood, the rest are Irrealis.
They may not all be applicable for Observables
enum Mood {
  Indicative, // realis certain
  Subjunctive, // it might
  Conditional, // if
  Optative, // hope
  Imperative, // command
  Jussive, // command to non-present
  Potential, // it could
  Hypothetical, // it is unlikely
  Inferential, // tree falling in forest without observer
  Interrogative // asking (probably better for a pull based thing)
}

Grammatical Voice
Voice indicates whether something is doing something, or something is happening to something. In observables it could indicate whether the Observable producer has all it's futures defined, or whether it awaits input from the outside (such as passing of time, mouse clicks).
Most Observables would be Passive, with the exception of Observables created from arrays or constants.

enum Voice {
  Acitve,
  Passive
}

Grammatical Tense
Grammatical tense indicates when something may happen, or when something did happen, we might want to add a Never, or Never may simply be an undefined Tense.
enum Tense {
  Present, // now
  Imperfect, // past and ongoing
  Perfect, //past and complete
  Future, // soon
  Pluperfect, // happened before something else in the past
  FuturePerfect // will happen at this time
};

Gramatical Person
Finally we have grammatical persons, that indicates who is doing what. We could use the person to indicate singular and plural events of a stream, and the degree of stream (higher-order-streams)
enum Person {
  FirstPersonSingular, // a stream of one thing
  FirstPersonPlural, // a stream of many things
  SecondPersonSinglar, // a stream of one stream of one thing
  SecondPersonPlural, // a stream of streams of things.
  ThirdPersonSingular, // a stream of one stream of one stream of one thing
  ThirdPersonPlural // a stream of streams of streams of things
}

Once our Observable producers are properly decorated with grammatical metadata. We can proceed to ensure that our operators determine what the conjugation of the resulting stream would be.
Practical Applications
Imagine you are combining stream a$ and b$, they are both Stream<number> but a$ is defined far away from where you are currently working, a$ happens to be never() while b$ is just(3) but you are unaware and spend some time trying to find the culprit. With gramatical typings you could get a warning, indicating you are trying to combine something b$ (Present, FirstPersonSingular, Active, Indicative) with a$ (Never), you would get a hint as to where something is amiss.
I would welcome some input on the ideas above, is it useful?

I have given this more thought. In order for this to work, we at least need to basic operators for combination and merge.
We could define them as AND and OR.
The OR operator would result in the earliest tense, the most real mood, the most quntative number.
The AND operator would result in the latest tense, the most irreal mood, and the least quantitative number.
For both operators voice will only be active if all inputs are active.
With these two primitive operators it should be possible to express most operators.
For schedulers we need something different.

Since the discussion seems to have died off, I am closing the issue.


Lab 08: Unable to Get NameSpace for Object Storage

In terraform/Lab_08_Infrastructure_Security_Network, terraform plan fails with:
│ Error: 401-NotAuthenticated, The required information to complete authentication was not provided.
│ Suggestion: Please retry or contact support for help with service: Object Storage Namespace
│ Documentation: https://registry.terraform.io/providers/oracle/oci/latest/docs/data-sources/object_storage_namespace
│ API Reference: https://docs.oracle.com/iaas/api/#/en/objectstorage/20160918/Namespace/GetNamespace
│ Request Target: GET https://objectstorage.us-ashburn-1.oraclecloud.com/n?compartmentId=ocid1.compartment.oc1..aaaaaaaarybkgsqrjcyzhdsceimit4ou47oslgyuwands5ghcdhkq2eb2ena
│ Provider version: 6.18.0, released on 2024-11-13. This provider is 2 Update(s) behind to current.
│ Service: Object Storage Namespace
│ Operation Name: GetNamespace
│ OPC request ID: iad-1:2HrO49JpLlNdSP9li3Yt5owHvfBvxtYd-YLvQBqZB6SCOSOY-zwrddxH4mG7qfRA
│
│
│   with data.oci_objectstorage_namespace.IAD-NP-LAB08-namespace,
│   on ashburn_bucket.tf line 29, in data "oci_objectstorage_namespace" "IAD-NP-LAB08-namespace":
│   29: data "oci_objectstorage_namespace" "IAD-NP-LAB08-namespace" {

Created a script terraform/common/update_tfvars.sh to update terraform/common/terraform.tfvars based on current MyLearn Lab OCI CLI configuration.


[New Output] Support Note Output

Adresses #208.
Changes
Add a capture group for the Note output.
Testing

Added new unit tests

@cpisciotta Currently, the tests do not check if the strings are coloured correctly if I am not mistaken. Do you think this should be covered? What do you think about the formatting I chose for this output?

@cpisciotta Currently, the tests do not check if the strings are coloured correctly if I am not mistaken. Do you think this should be covered? What do you think about the formatting I chose for this output?

I think it LGTM! No need to test the colored output.


Fix:Service Account Annotation Formatting Error

Please provide a description of this PR:
This pr held to fix the issue by removing the dashes
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.

[ ] Ambient
[ ] Configuration Infrastructure
[ ] Docs
[ ] Dual Stack
[x] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Policies and Telemetry
[ ] Security
[] Test and Release
[ ] User Experience
[ ] Developer Infrastructure

Hi @7h3-3mp7y-m4n. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@7h3-3mp7y-m4n: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
c893d6425d06dc99997825e15990edae99dc835c
link
true
/test release-notes

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

@7h3-3mp7y-m4n: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio
c893d6425d06dc99997825e15990edae99dc835c
link
true
/test release-notes

gencheck_istio
c893d6425d06dc99997825e15990edae99dc835c
link
true
/test gencheck

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

Please also add a release note (check for an example in the releasenotes directory). You can link the fixed issue there as well


Reducing complexity of ipm by delegating tf transformation responsibility to caller

Currently, IPM handles cases where the plane's frame_id is different to that of output_frame.
Because of this, IPM must keep track of the transforms using a tfbuffer, which increases complexity.
I think that the transformation can take place outside IPM (delegating responsibilty to the caller of the library or service), and we should assume that the incoming plane and outgoing point are in the same frame.
Is this possible, or am I missing something? What's your thoughts @Flova?

Another benefit would be that we can get rid of PlaneStamped, and just use shape_msgs.msg.Plane

We still need a tf_buffer from a purely logical perspective. If we have a given plane like the ground in e.g. the base_footprint frame it needs to be transformed into the camera frame for the projection to work out. We need to consider the relations between the base_footprint and camera frame. This relationship changes over time as e.g. the head moves. The camera frame is also different to the optional output frame, which is used to bring the projected points from the camera frame to a different one, like the base_footprint from the beginning.
We could just implement the projection itself and do everything in the camera frame. But this would move complexity that is needed in nearly every implementation of the ipm to the caller of the library. There is some additional error potential and verbosity on the user side. Most users will have planes that are not located in the camera frame, so a transformation is needed. Even if they are in the same frame tf is smart enough to just directly pass an identity transform which has a low overhead. All of this is independent of the output frame. The projected points are in the camera frame by default. A transformation can be applied to get them back into the output frame which is the plane's frame most of the time. The user could do this by hand later on, but most users will apply this transformation anyway, and it is faster to spare on one message serialization for large point clouds (the transformation is directly applied on the NumPy array without a msg conversion). I think all of this greatly improved the ease of use of the ipm and reduces possible the errors by the user. For example, explicitly defining the planes frame in the plane stamped msg helps with errors where the user might not assume that a plane needs to be generated in the camera frame for each call.

Hmm, so I had a bit of time to think about this. I understand your point, but I also think that the ipm class is doing too much currently.
I original posted this issue suggesting we take all tf stuff completely outside this library, but I think you have changed my mind. It would be good to at least break up the code into two or more classes because ipm has more than one responsibilty currently.
If you agree, I want to keep this issue until we implement the changes.

How would you split the IPM class in some way that is easier to understand and has benefits regarding the maintainability?
We currently do the projection itself using utils.get_field_intersection_for_pixels which handles the projection math itself and is in itself stateless. You can use it your self if you want to handle all tf things your self. The IPM class is statefull (holds tf buffer and camera info) and responsible for the ROS/TF side of things. Mainly making sure that the plane is viewed from the right coordinate system at the right time and that the output is also in an expected frame. Both of which are pretty simple, and I don't see where an additional layer might be useful. The IPM class itself is also not that large imo (< 130 loc).

Going to close this, as (at least for now), we're going to proceed with doing the tf inside ipm for ease of use.


node安装失败

cloning into  '/home/laradock/.nvm'...卡住

@hudarui Could you repeat in English if you could?

@philtrep i think when he opened this configuration "INSTALL_NODE=true"  to build the container and stop at "cloning into '/home/laradock/.nvm' ..."   sorry, my English is so bad.

yes，I edit the configuration install_node＝True
,but it stop  at  cloning into/home/laravel/.nvm

win10 docker native

@alixez help

I set node to true and it hangs here
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>Please update to minimatch 3.0.2 or higher to avoid a RegExp DoS issue
npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.```

@iannazzi your issue is different to this issue, this issue is spesifically about failing to clone node version manager, you are beyond that step.


feat(SetTheory/ZFC/Ordinal): von Neumann hierarchy of sets

[x] depends on: #16996
[ ] depends on: #17016
[x] depends on: #17026
[ ] depends on: #18239
[ ] depends on: #19946

If we're going to talk about cardinalities of the von Neumann hierarchy, it might be nice to first define a preBeth function (analogous to preAleph and preOmega) defined as the beth function but starting from 0. Then #(V_ o) = preBeth o. I'll do this in a separate PR, and the rest should be smooth sailing.

I've formalized your suggested proof of #ZFSet=univ here, but it increases transitive imports from 531 to 640 due to Cardinal.Arithmetic. Would you include it in this PR? And can you confirm whether you'll rename the file?

I think it'd be best to instead have a Card file collecting at least the #(V_ o) = preBeth o and #ZFSet = univ results.


Enable PodSecurityPolicy check for diagnostic tool

What this PR does / why we need it:
This PR is to enable PodSecurityPolicy check for diagnostic tool.
Which issue(s) this PR fixes (optional, in fixes #(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
None
Special notes for your reviewer:
Tested with K8S cluster deployed in IBM Cloud Kubernetes Service(IKS) and IBM Cloud Private(ICP).

Sample Outputs:

$ ./ibm-cos-diag
****Checking access to cluster****
error: You must be logged in to the server (Unauthorized)
ERROR: Unable to access cluster.
In case of IBM Cloud Kubernetes Service(IKS), export correct KUBECONFIG.
For IBM Cloud Private(ICP), run "cloudctl login" before running this tool.
Exiting!!!

2. IKS
$ ./ibm-cos-diag --node all --provisioner-log --driver-log
****Checking access to cluster****
> nodes are accessible... ok

****ibmcloud-object-storage-plugin pod status****
> ibmcloud-object-storage-plugin pod is in "Running" state... ok

****ibmcloud-object-storage-driver pods status****
> All ibmcloud-object-storage-driver pods are in "Running" state... ok

****Default storage class list****
> ibmc-s3fs-cold-cross-region            ibm.io/ibmc-s3fs
> ibmc-s3fs-cold-regional                ibm.io/ibmc-s3fs
> ibmc-s3fs-flex-cross-region            ibm.io/ibmc-s3fs
> ibmc-s3fs-flex-perf-cross-region       ibm.io/ibmc-s3fs
> ibmc-s3fs-flex-perf-regional           ibm.io/ibmc-s3fs
> ibmc-s3fs-flex-regional                ibm.io/ibmc-s3fs
> ibmc-s3fs-standard-cross-region        ibm.io/ibmc-s3fs
> ibmc-s3fs-standard-perf-cross-region   ibm.io/ibmc-s3fs
> ibmc-s3fs-standard-perf-regional       ibm.io/ibmc-s3fs
> ibmc-s3fs-standard-regional            ibm.io/ibmc-s3fs
> ibmc-s3fs-vault-cross-region           ibm.io/ibmc-s3fs
> ibmc-s3fs-vault-regional               ibm.io/ibmc-s3fs

****Inspecting Storage-class "ibmc-s3fs-standard-cross-region"****
> iam-endpoint is set to "https://iam.bluemix.net"
> object-store-endpoint is set to "https://s3.private.dal.us.cloud-object-storage.appdomain.cloud"
> object-store-storage-class is set to "us-standard"
> provisioner is set to "ibm.io/ibmc-s3fs"

****ServiceAccounts****
> ibmcloud-object-storage-driver is defined... ok
> ibmcloud-object-storage-plugin is defined... ok

****ClusterRole****
> ibmcloud-object-storage-plugin is defined... ok
> ibmcloud-object-storage-secret-reader is defined... ok

****ClusterRoleBinding****
> ibmcloud-object-storage-plugin is defined... ok
> ibmcloud-object-storage-secret-reader is defined... ok

> 2 instances of ibm-cos-plugin-diag is running

*****Collecting ibm-cos-plugin-diag logs*****
> th-1: Copying diagnostic log from node <IP_ADDRESS>
> th-0: Copying diagnostic log from node <IP_ADDRESS>

*****Analyzing ibm-cos-plugin-diag logs*****
> No Error

****Collecting provisioner log****
> Collected provisioner log... ok

*****Collecting driver logs*****
> th-1 Copying driver log from node <IP_ADDRESS>
 > th-0 Copying driver log from node <IP_ADDRESS>

Successfully created log archive "ibm-cos-diagnostic-logs.zip"
and saved as: /Users/mayank-macbook/latest/ibm-cos-diagnostic-logs.zip

****Deleting daemonset default/ibm-cos-plugin-diag****
daemonset "ibm-cos-plugin-diag" deleted

3. ICP
$ ./ibm-cos-diag --node all --provisioner-log --driver-log
****Checking access to cluster****
> nodes are accessible... ok

****ibmcloud-object-storage-plugin pod status****
> ibmcloud-object-storage-plugin pod is in "Running" state... ok

****ibmcloud-object-storage-driver pods status****
> All ibmcloud-object-storage-driver pods are in "Running" state... ok

****Default storage class list****
> ibmc-s3fs-icp              ibm.io/ibmc-s3fs
> ibmc-s3fs-icp-perf         ibm.io/ibmc-s3fs

****Inspecting Storage-class "ibmc-s3fs-icp"****
> iam-endpoint is set to "https://iam.bluemix.net"
> object-store-endpoint is set to "https://abcd"
> object-store-storage-class is set to "Standard"
> provisioner is set to "ibm.io/ibmc-s3fs"

****ServiceAccounts****
> ibmcloud-object-storage-driver is defined... ok
> ibmcloud-object-storage-plugin is defined... ok

****ClusterRole****
> ibmcloud-object-storage-plugin is defined... ok
> ibmcloud-object-storage-secret-reader is defined... ok

****ClusterRoleBinding****
> ibmcloud-object-storage-plugin is defined... ok
> ibmcloud-object-storage-secret-reader is defined... ok

****PodSecurityPolicy used by ibm-object-storage-plugin pods****
> ibm-object-storage-plugin pods are deployed using "iibm-object-storage-plugin-psp" PodSecurityPolicy... ok
> 1 instances of ibm-cos-plugin-diag is running

*****Collecting ibm-cos-plugin-diag logs*****
> th-0: Copying diagnostic log from node <IP_ADDRESS>

*****Analyzing ibm-cos-plugin-diag logs*****
> No Error

****Collecting provisioner log****
> Collected provisioner log... ok

*****Collecting driver logs*****
> th-0 Copying driver log from node <IP_ADDRESS>

Successfully created log archive "ibm-cos-diagnostic-logs.zip"
and saved as: /Users/mayank-macbook/latest/ibm-cos-diagnostic-logs.zip

****Deleting daemonset default/ibm-cos-plugin-diag****
daemonset "ibm-cos-plugin-diag" deleted

4. ICP
$ ./ibm-cos-diag --node all --provisioner-log --driver-log
****Checking access to cluster****
> nodes are accessible... ok

****ibmcloud-object-storage-plugin pod status****
> ibmcloud-object-storage-plugin pod is in "CreateContainerConfigError" state... not ok

****ibmcloud-object-storage-driver pods status****
> ibmcloud-object-storage-driver pods are not found... not ok

****Default storage class list****
> ibmc-s3fs-icp              ibm.io/ibmc-s3fs
> ibmc-s3fs-icp-perf         ibm.io/ibmc-s3fs

****Inspecting Storage-class "ibmc-s3fs-icp"****
> iam-endpoint is set to "https://iam.bluemix.net"
> object-store-endpoint is set to "https://abcd"
> object-store-storage-class is set to "Standard"
> provisioner is set to "ibm.io/ibmc-s3fs"

****ServiceAccounts****
> ibmcloud-object-storage-driver is defined... ok
> ibmcloud-object-storage-plugin is defined... ok

****ClusterRole****
> ibmcloud-object-storage-plugin is defined... ok
> ibmcloud-object-storage-secret-reader is defined... ok

****ClusterRoleBinding****
> ibmcloud-object-storage-plugin is defined... ok
> ibmcloud-object-storage-secret-reader is defined... ok

****PodSecurityPolicy used by ibm-object-storage-plugin pods****
> ibm-object-storage-plugin pods are deployed using "ibm-restricted-psp" PodSecurityPolicy instead of "ibm-object-storage-plugin-psp"... not ok
> To fix this issue, refer to: https://cloud.ibm.com/docs/containers/cs_storage_cos.html#object_storage


Airtable assign reviewer

This PR updates the ROpenSci Reviewers responder so now it updates the Airtable reviews and reviewers tables and replies with the reviewers form, as described in #9

When assigning reviewers I can see a new review entry, and current assignment added.
Once the label seeking-reviewers has been removed I do not see the invites.
When removing a reviewer the current assignment is removed but not the review entry in the reviews table.


Project is consistently read as PRAWject

A persistent point of confusion I observe as people test Malloy for the first time is the word "project." It consistently gets read "PRAWject" as in "art project." Relatively few people I've shown Malloy to have the background or recent memory of linear algebra to know/remember the word, and even those who do still read it PRAWject.

When Malloy was young, we had "reduce" and "project" queries. Now that "reduce" is gone, "project" is kinda weird. We need some word to mean "these fields" and we can't use "select". This has bugged me, I haven't has the aha moment for an alternative yet.


🐛 Bug Report: adr plugin routing issue

📜 Description
Navigating within the adr plugin breaks if you have the tab mounted on two different paths on different types of entity.
👍 Expected behavior
I expect the following code within the adr plugin to route to the correct path as specified on EntityLayout.Route.
https://github.com/backstage/backstage/blob/efb7f7afa8f9d246f562fa8b3988873c7b8d3d2c/plugins/adr/src/components/EntityAdrContent/EntityAdrContent.tsx#L131
👎 Actual Behavior with Screenshots
It seems to navigate to the last registered path.
👟 Reproduction steps
In EntityPage.tsx configure the Adr plugin twice with different paths:
const serviceEntityPage = (
  <EntityLayoutWrapper>
    <EntityLayout.Route if={isAdrAvailable} path="/adrs" title="ADRS">
      <EntityAdrContent />
    </EntityLayout.Route>
...

const websiteEntityPage = (
  <EntityLayoutWrapper>
    ...

    <EntityLayout.Route if={isAdrAvailable} path="/decision-records" title="ADRS">
      <EntityAdrContent />
    </EntityLayout.Route>

Trigger the rootLink function call by navigating between the individual adrs within the adr plugin..
📃 Provide the context for the Bug.
No response
🖥 Your Environment
No response
👀 Have you spent some time to check if this bug has been raised before?

[X] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
No, but I'm happy to collaborate on a PR with someone else

I guess that makes sense.
Do you think the component allowing the mount path seems to suggest that this should work?

Well maybe there's some place in the docs that could be clarified, not sure exactly where / how. But no it was always this way, that a route ref can only point to one single thing. Otherwise it would not be possible to look up route refs in any kind of consistent way.


⚠ Bofrost.de has degraded performance

In ed9af71, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1361 ms

Resolved: Bofrost.de performance has improved in 8202e20 after 40 minutes.


update to Readme.md

added static keyword in readme example to match the MVC example.

Thanks! :sparkles:


Renames the trait EndPoint to IntoRequest

To follow along with what appear to be common naming conventions in rust
I'm proposing to rename the EndPoint trait to IntoRequest. This does not
change the module (I still like classifying it as endpoints at the
module lever) but I want to be explicit about what the trait does, not
what it's supposed to "be". Since the point of the trait is to consume
itself and produce a request, this trait name seems more appropriate.
see this issue in the rust-nursery:
https://github.com/rust-lang-nursery/api-guidelines/issues/28
warning: This is may be slightly controversial.

This could also warrant a mention in the style section of our contributing.md file.  Maybe that's overkill at this point, but worth thinking about.


PP: prep for meeting with Georgia around exhibition accessibility

Notes from meeting with Georgia and Becca.

Decided to have a larger meeting on November 1st to finalise the organisation of the sessions.
Georgia will be doing the recruitment which may comprise of people with accessibility needs and those without to gather a lot of information about the CGDSYL exhibition in terms of ease of access, what people engage with, use of large print guides etc.
Before November's meeting we need to think about how many of us will be involved in the testing, so we can test multiple visitors concurrently and get the whole team to see and hear the feedback.
Need to decide length of session, thinking about how we might have users with different access needs.
Think about payment for visitors, reward voucher or payment for transport. Let Georgia know so she can specify when recruiting. []
Next meeting will be Hayley, Jenn, Heesoo, Georgia, Becca, and Orla.


Inconsistent view when a transparent background color is used

Using a background color with some alpha (e.g. #99fe0038) when the shadow attribute value is set to true reveals two circles: one for the floating action button and another inside (cf. image below). The latter is probably caused by the shape of the drawable that is used for creating the shadow.
It would be nice to get a circle without the inner one when a transparent background color is used.
I have also noticed that the image drawable used for the shadow isn't provided for xxxhdpi.

https://code.google.com/p/android/issues/detail?id=78248
Android bug seems to mention elevation not working correctly with translucent background. It might be related?

Hi, been running into this problem this morning. as far as I can tell, android draws a flat shadow gradient "border", then lays out content to straddle that gradient. looks great for solid color content, but transparencies allow you to see through that content and see the entire shadow gradient. i think a custom asset as makovkastar commented on Nov 8, 2014 is the only way to use transparent content with pseudo elevation.


security: fix CVE-2022-30635

This is a PRIVATE issue tracked in http://b/231318421 and fixed by http://tg/1484771
This is for 1.17.12 and 1.18.4.
/cc https://github.com/orgs/golang/teams/security and https://github.com/orgs/golang/teams/release

@gopherbot please open backport issues for this security fix


Rename questionRunning to isQuestionRunning

Since questionRunning represents a Boolean value, the variable should be renamed to isQuestionRunning

Hi, can you assign this issue to me please 🤓

Hey @zygisS22 I've assigned it to you.


Theme compendium

Add the theme compendium from the Starfinder Core Rule Book

Its done, source is modified with the page


Time picker is collapsed when clicking time 'icon'

Bug
When enabling a time picker along with date picker, the time picker does not transition fully. It remains collapsed with scroll bars and a very tiny height (see gif)
To Reproduce
Code is as follows
      <VueDatePicker
        v-model="dateTimeRange"
        :dark="true"
        range
        six-weeks
      >

Expected behavior
Time picker expands / calendar is hidden
Screenshots

Desktop & mobile (please complete the following information):

Desktop, Chrome
Library version:  "@vuepic/vue-datepicker": "^4.2.0"

If you initialized a new project using vite, go in the global CSS file and find global selection * and remove position: relative

If you initialized a new project using vite, go in the global CSS file and find global selection * and remove position: relative

@Jasenkoo Can you please share with us exactly which class that is affected by position: relative? Unfortunately removing position: relative entirely from the global selection is not an option for me as it causes me other layout issues.


master_ip needs updating even for minion to be discovered by master

This is a follow-up fix to PR #5245
Without this change when I want to configure a node only as a minion, it fails to connect to master because /etc/default/kubelet hasn't replaced MASTER_IP appropriately.
ping @erictune @WIZARD-CXY @resouer @jlowdermilk

LGTM


Fix/expression test

Summary

Changes to support date/time in expressions
Added actual test to test values in ExpressionTest
Added a directive parse-timestamp-as-date to convert unix timestamp in millis to ZonedDateTime.
Added corresponding test for parse-timestamp-as-date

https://builds.cask.co/browse/HYP-WT205-2

Latest build is green. Squashing and merging.


ROS Message convert to rikai types

Support brute-force conversion between a ROS Message to Python dict,  and ROS Message class / type to Spark DataType.

Will have a follow up PR to convert some ros type to rikai semantic types

Thanks for the reviews, @bobingm @changhiskhan


Buttons

NHS App design system Figma file
NHS design system guidance
NHS design system discussion
Related
GOV.UK Design System guidance
GOV.UK Design System discussion
Examples on the NHS App

Examples
Primary button

Secondary button

Reverse button

Full width (on small screens)

Design changes
Team Frontier have been exploring making buttons full width on smaller screens (640px and below).

Accessibility notes
3.2 Touch Target Size and Spacing
The high resolution of mobile devices means that many interactive elements can be shown together on a small screen. But these elements must be big enough and have enough distance from each other so that users can safely target them by touch.
Best practices for touch target size include the following:

Ensuring that touch targets are at least 9 mm high by 9 mm wide.
Ensuring that touch targets close to the minimum size are surrounded by a small amount of inactive space.

3.5 Placing buttons where they are easy to access
Mobile sites and applications should position interactive elements where they can be easily reached when the device is held in different positions.
When designing mobile web content and applications many developers attempt to optimize use with one hand. This can benefit people with disabilities who may only have one hand available, however, developers should also consider that an easy-to-use button placement for some users might cause difficulties for others (e.g. left- vs. right-handed use, assumptions about thumb range of motion). Therefore, flexible use should always be the goal.
Some (but not all) mobile operating systems provide work-around features that let the user temporarily shift the display downwards or sideways to facilitate one-handed operation.

i asked about this over in the community backlog a while ago

Secondary or low priority CTA
I would add this here regarding the use of secondary buttons because I think it will become particularly relevant to the app in context where there is a promo but a primary button isn't appropriate.
The current secondary had less design effort compared to the primary and it has weaknesses around versatility across different context, plus when paired with the primary, it is relies on colour alone to make the distinction of hierarchy between them.
https://github.com/nhsuk/nhsuk-service-manual-community-backlog/issues/417


Extraneous "selection" in SFR FCS_CKM.4 Cryptographic key destruction in HCD cPP v1.0

This is a comment from Tom Benkart:
Section 5.3.5, FCS_CKM.4 Cryptographic key destruction on page 33: in FCS_CKM.4.1 the last line of the SFR states "] that meets the following: [selection: no standard]."
Since the selection has already been made in the cPP, the "selection:" should be deleted.

This is a duplicate of the NIAP Assesssment comments.