strange compile error: clang7.0

I have a simple use case which compiles fine:
https://github.com/gabyx/ExecutionGraph/blob/c4b1cccfd855d418dfb3fe53b2cc257aaabcbf14/tests/src/main_Factory.cpp#L36
In another target, I am not even using registration, only RTTR_ENABLE(...).
I get some strange errors:
Backend.hpp
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:18:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/AppHandler.hpp:21:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/backend/Backend.hpp:17:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:32:
In file included from /usr/local/opt/rttr/include/rttr/string_view.h:498:
In file included from /usr/local/opt/rttr/include/rttr/detail/impl/string_view_impl.h:32:
In file included from /usr/local/opt/rttr/include/rttr/detail/misc/utility.h:34:
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:464:79: error: expected member name or ';' after declaration specifiers
        template <typename U> static NoType& check(typename U::no_array_type*);
                              ~~~~~~~~~~~~~                                   ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:465:57: error: expected member name or ';' after declaration specifiers
        template <typename U> static YesType& check(...);
                              ~~~~~~~~~~~~~~            ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:468:61: error: use of undeclared identifier 'check'
        static RTTR_CONSTEXPR_OR_CONST bool value = (sizeof(check<array_mapper<T> >(0)) == sizeof(YesType));
                                                            ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:468:83: error: expected '(' for function-style cast or type construction
        static RTTR_CONSTEXPR_OR_CONST bool value = (sizeof(check<array_mapper<T> >(0)) == sizeof(YesType));
                                                                  ~~~~~~~~~~~~~~~ ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:483:75: error: expected member name or ';' after declaration specifiers
        template <typename U> static YesType& check(typename U::is_valid*);
                              ~~~~~~~~~~~~~~                              ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:484:56: error: expected member name or ';' after declaration specifiers
        template <typename U> static NoType& check(...);
                              ~~~~~~~~~~~~~            ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:487:61: error: use of undeclared identifier 'check'
        static RTTR_CONSTEXPR_OR_CONST bool value = (sizeof(check<T>(0)) == sizeof(YesType));
                                                            ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:487:67: error: 'T' does not refer to a value
        static RTTR_CONSTEXPR_OR_CONST bool value = (sizeof(check<T>(0)) == sizeof(YesType));
                                                                  ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:477:24: note: declared here
    template <typename T>
                       ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:504:31: error: use of undeclared identifier 'check'
        using type = decltype(check<T>(nullptr));
                              ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:504:37: error: 'T' does not refer to a value
        using type = decltype(check<T>(nullptr));
                                    ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:498:24: note: declared here
    template <typename T>
                       ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:472:51: error: non-type template argument is not a constant expression
    using is_array = std::integral_constant<bool, is_array_impl<remove_cv_t< remove_reference_t<T> > >::value>;
                                                  ^
/usr/local/opt/rttr/include/rttr/detail/variant_array_view/variant_array_view_traits.h:48:81: note: in instantiation of template type alias 'is_array' requested here
using can_create_array_container = std::integral_constant<bool, ::rttr::detail::is_array<T>::value || is_wrapper_array_type<T>::value || is_pointer_array_type<T>::value>;
                                                                                ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:298:24: note: in instantiation of template type alias 'can_create_array_container' requested here
                return can_create_array_container<T>::value;
                       ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:55:43: note: in instantiation of member function 'rttr::detail::variant_data_base_policy<bool, rttr::detail::variant_data_policy_arithmetic<bool>, rttr::detail::default_type_converter<bool, rttr::detail::convert_from<bool> > >::invoke' requested here
:   m_policy(&detail::variant_policy<Tp>::invoke)
                                          ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_converter.h:283:31: note: in instantiation of function template specialization 'rttr::variant::variant<const bool &, bool>' requested here
        return to_enumeration(from, to);
                              ^
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:18:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/AppHandler.hpp:21:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/backend/Backend.hpp:17:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:32:
In file included from /usr/local/opt/rttr/include/rttr/string_view.h:498:
In file included from /usr/local/opt/rttr/include/rttr/detail/impl/string_view_impl.h:32:
In file included from /usr/local/opt/rttr/include/rttr/detail/misc/utility.h:34:
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:491:68: error: non-type template argument is not a constant expression
    using is_associative_container = std::integral_constant<bool, !has_is_valid_alias<associative_container_mapper<Tp> >::value>;
                                                                   ^
/usr/local/opt/rttr/include/rttr/detail/variant_associative_view/variant_associative_view_creator.h:46:66: note: in instantiation of template type alias 'is_associative_container' requested here
using can_create_associative_view = std::integral_constant<bool, is_associative_container<raw_type_t<wrapper_address_return_type_t<T>>>::value>;
                                                                 ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:302:24: note: in instantiation of template type alias 'can_create_associative_view' requested here
                return can_create_associative_view<T>::value;
                       ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:55:43: note: in instantiation of member function 'rttr::detail::variant_data_base_policy<bool, rttr::detail::variant_data_policy_arithmetic<bool>, rttr::detail::default_type_converter<bool, rttr::detail::convert_from<bool> > >::invoke' requested here
:   m_policy(&detail::variant_policy<Tp>::invoke)
                                          ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_converter.h:283:31: note: in instantiation of function template specialization 'rttr::variant::variant<const bool &, bool>' requested here
        return to_enumeration(from, to);
                              ^
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:18:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/AppHandler.hpp:21:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/backend/Backend.hpp:17:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:32:
In file included from /usr/local/opt/rttr/include/rttr/string_view.h:498:
In file included from /usr/local/opt/rttr/include/rttr/detail/impl/string_view_impl.h:32:
In file included from /usr/local/opt/rttr/include/rttr/detail/misc/utility.h:34:
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:494:67: error: non-type template argument is not a constant expression
    using is_sequential_container = std::integral_constant<bool, !has_is_valid_alias<sequential_container_mapper<Tp > >::value>;
                                                                  ^
/usr/local/opt/rttr/include/rttr/detail/variant_sequential_view/variant_sequential_view_creator.h:46:65: note: in instantiation of template type alias 'is_sequential_container' requested here
using can_create_sequential_view = std::integral_constant<bool, is_sequential_container<raw_type_t<wrapper_address_return_type_t<T>>>::value>;
                                                                ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:306:24: note: in instantiation of template type alias 'can_create_sequential_view' requested here
                return can_create_sequential_view<T>::value;
                       ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:55:43: note: in instantiation of member function 'rttr::detail::variant_data_base_policy<bool, rttr::detail::variant_data_policy_arithmetic<bool>, rttr::detail::default_type_converter<bool, rttr::detail::convert_from<bool> > >::invoke' requested here
:   m_policy(&detail::variant_policy<Tp>::invoke)
                                          ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_converter.h:283:31: note: in instantiation of function template specialization 'rttr::variant::variant<const bool &, bool>' requested here
        return to_enumeration(from, to);
                              ^
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:18:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/AppHandler.hpp:21:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/backend/Backend.hpp:17:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:1189:
In file included from /usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:36:
In file included from /usr/local/opt/rttr/include/rttr/detail/type/get_create_variant_func.h:32:
In file included from /usr/local/opt/rttr/include/rttr/variant.h:1079:
In file included from /usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:36:
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:310:73: error: no matching function for call to 'create_variant_array_view'
                arg.get_value<std::unique_ptr<array_wrapper_base>&>() = create_variant_array_view(const_cast<T&>(Tp::get_value(src_data)));
                                                                        ^~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:55:43: note: in instantiation of member function 'rttr::detail::variant_data_base_policy<bool, rttr::detail::variant_data_policy_arithmetic<bool>, rttr::detail::default_type_converter<bool, rttr::detail::convert_from<bool> > >::invoke' requested here
:   m_policy(&detail::variant_policy<Tp>::invoke)
                                          ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_converter.h:283:31: note: in instantiation of function template specialization 'rttr::variant::variant<const bool &, bool>' requested here
        return to_enumeration(from, to);
                              ^
/usr/local/opt/rttr/include/rttr/detail/variant_array_view/variant_array_view_creator_impl.h:42:1: note: candidate template ignored: substitution failure [with T = bool &, Tp = bool]: non-type template argument is not a constant expression
create_variant_array_view(T&& value)
^
/usr/local/opt/rttr/include/rttr/detail/variant_array_view/variant_array_view_creator_impl.h:51:1: note: candidate template ignored: substitution failure [with T = bool &, Tp = bool]: non-type template argument is not a constant expression
create_variant_array_view(T&& value)
^
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:18:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/AppHandler.hpp:21:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/backend/Backend.hpp:17:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:1189:
In file included from /usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:36:
In file included from /usr/local/opt/rttr/include/rttr/detail/type/get_create_variant_func.h:32:
In file included from /usr/local/opt/rttr/include/rttr/variant.h:1079:
In file included from /usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:36:
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:315:70: error: no matching function for call to 'create_variant_associative_view'
                arg.get_value<variant_associative_view_private&>() = create_variant_associative_view(const_cast<T&>(Tp::get_value(src_data)));
                                                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/opt/rttr/include/rttr/detail/variant_associative_view/variant_associative_view_creator_impl.h:42:1: note: candidate template ignored: substitution failure [with T = bool &, Tp = bool]: non-type template argument is not a constant expression
create_variant_associative_view(T&& value)
^
/usr/local/opt/rttr/include/rttr/detail/variant_associative_view/variant_associative_view_creator_impl.h:51:1: note: candidate template ignored: substitution failure [with T = bool &, Tp = bool]: non-type template argument is not a constant expression
create_variant_associative_view(T&& value)
^
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:18:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/AppHandler.hpp:21:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/backend/Backend.hpp:17:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:1189:
In file included from /usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:36:
In file included from /usr/local/opt/rttr/include/rttr/detail/type/get_create_variant_func.h:32:
In file included from /usr/local/opt/rttr/include/rttr/variant.h:1079:
In file included from /usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:36:
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:320:69: error: no matching function for call to 'create_variant_sequential_view'
                arg.get_value<variant_sequential_view_private&>() = create_variant_sequential_view(const_cast<T&>(Tp::get_value(src_data)));
                                                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/opt/rttr/include/rttr/detail/variant_sequential_view/variant_sequential_view_creator_impl.h:42:1: note: candidate template ignored: substitution failure [with T = bool &, Tp = bool]: non-type template argument is not a constant expression
create_variant_sequential_view(T&& value)
^
/usr/local/opt/rttr/include/rttr/detail/variant_sequential_view/variant_sequential_view_creator_impl.h:51:1: note: candidate template ignored: substitution failure [with T = bool &, Tp = bool]: non-type template argument is not a constant expression
create_variant_sequential_view(T&& value)
^
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:18:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/AppHandler.hpp:21:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/backend/Backend.hpp:17:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:32:
In file included from /usr/local/opt/rttr/include/rttr/string_view.h:498:
In file included from /usr/local/opt/rttr/include/rttr/detail/impl/string_view_impl.h:32:
In file included from /usr/local/opt/rttr/include/rttr/detail/misc/utility.h:34:
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:472:51: error: non-type template argument is not a constant expression
    using is_array = std::integral_constant<bool, is_array_impl<remove_cv_t< remove_reference_t<T> > >::value>;
                                                  ^
/usr/local/opt/rttr/include/rttr/detail/type/type_data.h:317:92: note: in instantiation of template type alias 'is_array' requested here
                                              TYPE_TRAIT_TO_BITSET_VALUE_2(::rttr::detail::is_array, is_array) |
                                                                                ^
/usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:302:74: note: in instantiation of function template specialization 'rttr::detail::make_type_data<bool>' requested here
        static const type val = get_registration_manager<int>().add_item(make_type_data<T>());
                                                                         ^
/usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:390:105: note: in instantiation of member function 'rttr::detail::type_getter<bool, void>::get_type' requested here
    return detail::type_getter<typename std::remove_cv<typename std::remove_reference<T>::type>::type>::get_type();
                                                                                ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:268:47: note: in instantiation of function template specialization 'rttr::type::get<bool>' requested here
                arg.get_value<type>() = type::get<T>();
                                              ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:55:43: note: in instantiation of member function 'rttr::detail::variant_data_base_policy<bool, rttr::detail::variant_data_policy_arithmetic<bool>, rttr::detail::default_type_converter<bool, rttr::detail::convert_from<bool> > >::invoke' requested here
:   m_policy(&detail::variant_policy<Tp>::invoke)
                                          ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_converter.h:283:31: note: in instantiation of function template specialization 'rttr::variant::variant<const bool &, bool>' requested here
        return to_enumeration(from, to);
                              ^
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:18:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/AppHandler.hpp:21:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/backend/Backend.hpp:17:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:32:
In file included from /usr/local/opt/rttr/include/rttr/string_view.h:498:
In file included from /usr/local/opt/rttr/include/rttr/detail/impl/string_view_impl.h:32:
In file included from /usr/local/opt/rttr/include/rttr/detail/misc/utility.h:34:
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:472:51: error: non-type template argument is not a constant expression
    using is_array = std::integral_constant<bool, is_array_impl<remove_cv_t< remove_reference_t<T> > >::value>;
                                                  ^
/usr/local/opt/rttr/include/rttr/detail/type/type_data.h:317:92: note: in instantiation of template type alias 'is_array' requested here
                                              TYPE_TRAIT_TO_BITSET_VALUE_2(::rttr::detail::is_array, is_array) |
                                                                                ^
/usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:302:74: note: in instantiation of function template specialization 'rttr::detail::make_type_data<bool *>' requested here
        static const type val = get_registration_manager<int>().add_item(make_type_data<T>());
                                                                         ^
/usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:390:105: note: in instantiation of member function 'rttr::detail::type_getter<bool *, void>::get_type' requested here
    return detail::type_getter<typename std::remove_cv<typename std::remove_reference<T>::type>::type>::get_type();
                                                                                ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:290:61: note: in instantiation of function template specialization 'rttr::type::get<bool *>' requested here
                data.m_type                         = type::get< raw_addressof_return_type_t<T> >();
                                                            ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:55:43: note: in instantiation of member function 'rttr::detail::variant_data_base_policy<bool, rttr::detail::variant_data_policy_arithmetic<bool>, rttr::detail::default_type_converter<bool, rttr::detail::convert_from<bool> > >::invoke' requested here
:   m_policy(&detail::variant_policy<Tp>::invoke)
                                          ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_converter.h:283:31: note: in instantiation of function template specialization 'rttr::variant::variant<const bool &, bool>' requested here
        return to_enumeration(from, to);
                              ^
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:18:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/AppHandler.hpp:21:
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/backend/Backend.hpp:17:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:32:
In file included from /usr/local/opt/rttr/include/rttr/string_view.h:498:
In file included from /usr/local/opt/rttr/include/rttr/detail/impl/string_view_impl.h:32:
In file included from /usr/local/opt/rttr/include/rttr/detail/misc/utility.h:34:
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:472:51: error: non-type template argument is not a constant expression
    using is_array = std::integral_constant<bool, is_array_impl<remove_cv_t< remove_reference_t<T> > >::value>;
                                                  ^
/usr/local/opt/rttr/include/rttr/detail/variant_array_view/variant_array_view_traits.h:48:81: note: in instantiation of template type alias 'is_array' requested here
using can_create_array_container = std::integral_constant<bool, ::rttr::detail::is_array<T>::value || is_wrapper_array_type<T>::value || is_pointer_array_type<T>::value>;
                                                                                ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:298:24: note: in instantiation of template type alias 'can_create_array_container' requested here
                return can_create_array_container<T>::value;
                       ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:55:43: note: in instantiation of member function 'rttr::detail::variant_data_base_policy<bool *, rttr::detail::variant_data_policy_small<bool *, rttr::detail::empty_type_converter<bool *> >, rttr::detail::empty_type_converter<bool *> >::invoke' requested here
:   m_policy(&detail::variant_policy<Tp>::invoke)
                                          ^
/usr/local/opt/rttr/include/rttr/detail/type/get_create_variant_func.h:58:16: note: in instantiation of function template specialization 'rttr::variant::variant<bool *&, bool *>' requested here
        return data.get_value<T>();
               ^
/usr/local/opt/rttr/include/rttr/detail/type/type_data.h:307:54: note: in instantiation of member function 'rttr::detail::create_variant_policy<bool *>::create_variant' requested here
                            &create_variant_func<T>::create_variant,
                                                     ^
/usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:302:74: note: in instantiation of function template specialization 'rttr::detail::make_type_data<bool *>' requested here
        static const type val = get_registration_manager<int>().add_item(make_type_data<T>());
                                                                         ^
/usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:390:105: note: in instantiation of member function 'rttr::detail::type_getter<bool *, void>::get_type' requested here
    return detail::type_getter<typename std::remove_cv<typename std::remove_reference<T>::type>::type>::get_type();
                                                                                ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:290:61: note: in instantiation of function template specialization 'rttr::type::get<bool *>' requested here
                data.m_type                         = type::get< raw_addressof_return_type_t<T> >();
                                                            ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:55:43: note: in instantiation of member function 'rttr::detail::variant_data_base_policy<bool, rttr::detail::variant_data_policy_arithmetic<bool>, rttr::detail::default_type_converter<bool, rttr::detail::convert_from<bool> > >::invoke' requested here
:   m_policy(&detail::variant_policy<Tp>::invoke)
                                          ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_converter.h:283:31: note: in instantiation of function template specialization 'rttr::variant::variant<const bool &, bool>' requested here
        return to_enumeration(from, to);
                              ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]

can you make up anything from this? Why does he need rttr::variant::variant<const bool &, bool>
I am nowhere using an rttr::variant

Ok, made it compile removed everything (no rttr includes):
Look at the Standalone compilation below first, I think this described the problem best.
Standalone compilation:
#include <rttr/type>
#include <rttr/registration>
struct point { int x; int y;};
struct foo { point get_point();};
rttr::registration::class_<foo>("foo").method("bar", &foo::get_point);

Output:
[ 93%] Building CXX object gui/executionGraphGui/CMakeFiles/ExecutionGraph-GUI.dir/backend/Test.cpp.o
cd /Users/gabrielnuetzi/Desktop/ExecutionGraph/build/gui/executionGraphGui && ccache /usr/local/opt/llvm/bin/clang++  -DRTTR_DLL -I/Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui -isystem /Users/gabrielnuetzi/Desktop/ExecutionGraph/build/../buildExternal/cefbinaries/cefbinaries-src/include -isystem /Users/gabrielnuetzi/Desktop/ExecutionGraph/build/../buildExternal/cefbinaries/cefbinaries-src -isystem /usr/local/opt/rttr/include -I/Users/gabrielnuetzi/Desktop/ExecutionGraph/include -I/Users/gabrielnuetzi/Desktop/ExecutionGraph/build/include -isystem /usr/local/include/eigen3 -isystem /Users/gabrielnuetzi/Desktop/ExecutionGraph/buildExternal/meta/meta-src/include -isystem /Users/gabrielnuetzi/Desktop/ExecutionGraph/buildExternal/args/args-src -isystem /Users/gabrielnuetzi/Desktop/ExecutionGraph/buildExternal/crossguid/crossguid-src  -I/usr/local/opt/llvm/include -I/usr/local/opt/llvm/include/c++/v1/ -g -arch x86_64 -mmacosx-version-min=10.9   -fno-omit-frame-pointer -Wall -Wpedantic -Wno-documentation -fsanitize=leak -fsanitize=address -std=c++1z -o CMakeFiles/ExecutionGraph-GUI.dir/backend/Test.cpp.o -c /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/backend/Test.cpp
/Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/backend/Test.cpp:5:33: error: expected unqualified-id
rttr::registration::class_<foo>().method("bar", &foo::get_point);
                                ^
1 error generated.
make[3]: *** [gui/executionGraphGui/CMakeFiles/ExecutionGraph-GUI.dir/backend/Test.cpp.o] Error 1

** InApp Test:**
added in a AppMac.mm the following:
#include <rttr/type>
#include <rttr/registration>
struct point { int x; int y;};
struct foo { point get_point();};
rttr::registration::class_<foo>("foo").method("bar", &foo::get_point);

Outputs:
[ 93%] Building CXX object gui/executionGraphGui/CMakeFiles/ExecutionGraph-GUI.dir/cefapp/mac/AppMac.mm.o
cd /Users/gabrielnuetzi/Desktop/ExecutionGraph/build/gui/executionGraphGui && ccache /usr/local/opt/llvm/bin/clang++  -DRTTR_DLL -I/Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui -isystem /Users/gabrielnuetzi/Desktop/ExecutionGraph/build/../buildExternal/cefbinaries/cefbinaries-src/include -isystem /Users/gabrielnuetzi/Desktop/ExecutionGraph/build/../buildExternal/cefbinaries/cefbinaries-src -isystem /usr/local/opt/rttr/include -I/Users/gabrielnuetzi/Desktop/ExecutionGraph/include -I/Users/gabrielnuetzi/Desktop/ExecutionGraph/build/include -isystem /usr/local/include/eigen3 -isystem /Users/gabrielnuetzi/Desktop/ExecutionGraph/buildExternal/meta/meta-src/include -isystem /Users/gabrielnuetzi/Desktop/ExecutionGraph/buildExternal/args/args-src -isystem /Users/gabrielnuetzi/Desktop/ExecutionGraph/buildExternal/crossguid/crossguid-src  -I/usr/local/opt/llvm/include -I/usr/local/opt/llvm/include/c++/v1/ -g -arch x86_64 -mmacosx-version-min=10.9   -fno-omit-frame-pointer -Wall -Wpedantic -Wno-documentation -fsanitize=leak -fsanitize=address -std=c++1z -o CMakeFiles/ExecutionGraph-GUI.dir/cefapp/mac/AppMac.mm.o -c /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:20:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:32:
In file included from /usr/local/opt/rttr/include/rttr/string_view.h:498:
In file included from /usr/local/opt/rttr/include/rttr/detail/impl/string_view_impl.h:32:
In file included from /usr/local/opt/rttr/include/rttr/detail/misc/utility.h:34:
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:464:79: error: expected member name or ';' after declaration specifiers
        template <typename U> static NoType& check(typename U::no_array_type*);
                              ~~~~~~~~~~~~~                                   ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:465:57: error: expected member name or ';' after declaration specifiers
        template <typename U> static YesType& check(...);
                              ~~~~~~~~~~~~~~            ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:468:85: error: 'check' following the 'template' keyword does not refer to a template
        static RTTR_CONSTEXPR_OR_CONST bool value = (sizeof(is_array_impl::template check<array_mapper<T>>(0)) == sizeof(YesType));
                                                                           ~~~~~~~~ ^~~~~
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:468:103: error: expected '>'
        static RTTR_CONSTEXPR_OR_CONST bool value = (sizeof(is_array_impl::template check<array_mapper<T>>(0)) == sizeof(YesType));
                                                                                ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:468:103: error: expected ')'
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:468:60: note: to match this '('
        static RTTR_CONSTEXPR_OR_CONST bool value = (sizeof(is_array_impl::template check<array_mapper<T>>(0)) == sizeof(YesType));
                                                           ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:482:75: error: expected member name or ';' after declaration specifiers
        template <typename U> static YesType& check(typename U::is_valid*);
                              ~~~~~~~~~~~~~~                              ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:483:56: error: expected member name or ';' after declaration specifiers
        template <typename U> static NoType& check(...);
                              ~~~~~~~~~~~~~            ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:486:61: error: use of undeclared identifier 'check'
        static RTTR_CONSTEXPR_OR_CONST bool value = (sizeof(check<T>(nullptr)) == sizeof(YesType));
                                                            ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:486:67: error: 'T' does not refer to a value
        static RTTR_CONSTEXPR_OR_CONST bool value = (sizeof(check<T>(nullptr)) == sizeof(YesType));
                                                                  ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:476:24: note: declared here
    template <typename T>
                       ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:503:31: error: use of undeclared identifier 'check'
        using type = decltype(check<T>(nullptr));
                              ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:503:37: error: 'T' does not refer to a value
        using type = decltype(check<T>(nullptr));
                                    ^
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:497:24: note: declared here
    template <typename T>
                       ^
/Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:24:33: error: expected unqualified-id
rttr::registration::class_<foo>("foo").method("bar", &foo::get_point);
                                ^
/Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:24:33: error: expected ')'
/Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:24:32: note: to match this '('
rttr::registration::class_<foo>("foo").method("bar", &foo::get_point);
                               ^
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:20:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:32:
In file included from /usr/local/opt/rttr/include/rttr/string_view.h:498:
In file included from /usr/local/opt/rttr/include/rttr/detail/impl/string_view_impl.h:32:
In file included from /usr/local/opt/rttr/include/rttr/detail/misc/utility.h:34:
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:490:68: error: non-type template argument is not a constant expression
    using is_associative_container = std::integral_constant<bool, !has_is_valid_alias<associative_container_mapper<Tp> >::value>;
                                                                   ^
/usr/local/opt/rttr/include/rttr/detail/variant_associative_view/variant_associative_view_creator.h:46:66: note: in instantiation of template type alias 'is_associative_container' requested here
using can_create_associative_view = std::integral_constant<bool, is_associative_container<raw_type_t<wrapper_address_return_type_t<T>>>::value>;
                                                                 ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:302:24: note: in instantiation of template type alias 'can_create_associative_view' requested here
                return can_create_associative_view<T>::value;
                       ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:55:43: note: in instantiation of member function 'rttr::detail::variant_data_base_policy<bool, rttr::detail::variant_data_policy_arithmetic<bool>, rttr::detail::default_type_converter<bool, rttr::detail::convert_from<bool> > >::invoke' requested here
:   m_policy(&detail::variant_policy<Tp>::invoke)
                                          ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_converter.h:283:31: note: in instantiation of function template specialization 'rttr::variant::variant<const bool &, bool>' requested here
        return to_enumeration(from, to);
                              ^
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:20:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:32:
In file included from /usr/local/opt/rttr/include/rttr/string_view.h:498:
In file included from /usr/local/opt/rttr/include/rttr/detail/impl/string_view_impl.h:32:
In file included from /usr/local/opt/rttr/include/rttr/detail/misc/utility.h:34:
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:493:67: error: non-type template argument is not a constant expression
    using is_sequential_container = std::integral_constant<bool, !has_is_valid_alias<sequential_container_mapper<Tp > >::value>;
                                                                  ^
/usr/local/opt/rttr/include/rttr/detail/variant_sequential_view/variant_sequential_view_creator.h:46:65: note: in instantiation of template type alias 'is_sequential_container' requested here
using can_create_sequential_view = std::integral_constant<bool, is_sequential_container<raw_type_t<wrapper_address_return_type_t<T>>>::value>;
                                                                ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:306:24: note: in instantiation of template type alias 'can_create_sequential_view' requested here
                return can_create_sequential_view<T>::value;
                       ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:55:43: note: in instantiation of member function 'rttr::detail::variant_data_base_policy<bool, rttr::detail::variant_data_policy_arithmetic<bool>, rttr::detail::default_type_converter<bool, rttr::detail::convert_from<bool> > >::invoke' requested here
:   m_policy(&detail::variant_policy<Tp>::invoke)
                                          ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_converter.h:283:31: note: in instantiation of function template specialization 'rttr::variant::variant<const bool &, bool>' requested here
        return to_enumeration(from, to);
                              ^
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:20:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:1189:
In file included from /usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:36:
In file included from /usr/local/opt/rttr/include/rttr/detail/type/get_create_variant_func.h:32:
In file included from /usr/local/opt/rttr/include/rttr/variant.h:1079:
In file included from /usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:36:
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:315:70: error: no matching function for call to 'create_variant_associative_view'
                arg.get_value<variant_associative_view_private&>() = create_variant_associative_view(const_cast<T&>(Tp::get_value(src_data)));
                                                                     ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:55:43: note: in instantiation of member function 'rttr::detail::variant_data_base_policy<bool, rttr::detail::variant_data_policy_arithmetic<bool>, rttr::detail::default_type_converter<bool, rttr::detail::convert_from<bool> > >::invoke' requested here
:   m_policy(&detail::variant_policy<Tp>::invoke)
                                          ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_converter.h:283:31: note: in instantiation of function template specialization 'rttr::variant::variant<const bool &, bool>' requested here
        return to_enumeration(from, to);
                              ^
/usr/local/opt/rttr/include/rttr/detail/variant_associative_view/variant_associative_view_creator_impl.h:42:1: note: candidate template ignored: substitution failure [with T = bool &, Tp = bool]: non-type template argument is not a constant expression
create_variant_associative_view(T&& value)
^
/usr/local/opt/rttr/include/rttr/detail/variant_associative_view/variant_associative_view_creator_impl.h:51:1: note: candidate template ignored: substitution failure [with T = bool &, Tp = bool]: non-type template argument is not a constant expression
create_variant_associative_view(T&& value)
^
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:20:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:1189:
In file included from /usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:36:
In file included from /usr/local/opt/rttr/include/rttr/detail/type/get_create_variant_func.h:32:
In file included from /usr/local/opt/rttr/include/rttr/variant.h:1079:
In file included from /usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:36:
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:320:69: error: no matching function for call to 'create_variant_sequential_view'
                arg.get_value<variant_sequential_view_private&>() = create_variant_sequential_view(const_cast<T&>(Tp::get_value(src_data)));
                                                                    ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
/usr/local/opt/rttr/include/rttr/detail/variant_sequential_view/variant_sequential_view_creator_impl.h:42:1: note: candidate template ignored: substitution failure [with T = bool &, Tp = bool]: non-type template argument is not a constant expression
create_variant_sequential_view(T&& value)
^
/usr/local/opt/rttr/include/rttr/detail/variant_sequential_view/variant_sequential_view_creator_impl.h:51:1: note: candidate template ignored: substitution failure [with T = bool &, Tp = bool]: non-type template argument is not a constant expression
create_variant_sequential_view(T&& value)
^
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:20:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:32:
In file included from /usr/local/opt/rttr/include/rttr/string_view.h:498:
In file included from /usr/local/opt/rttr/include/rttr/detail/impl/string_view_impl.h:32:
In file included from /usr/local/opt/rttr/include/rttr/detail/misc/utility.h:34:
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:490:68: error: non-type template argument is not a constant expression
    using is_associative_container = std::integral_constant<bool, !has_is_valid_alias<associative_container_mapper<Tp> >::value>;
                                                                   ^
/usr/local/opt/rttr/include/rttr/detail/type/type_data.h:323:92: note: in instantiation of template type alias 'is_associative_container' requested here
                                              TYPE_TRAIT_TO_BITSET_VALUE_2(::rttr::detail::is_associative_container, is_associative_container) |
                                                                                ^
/usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:302:74: note: in instantiation of function template specialization 'rttr::detail::make_type_data<bool>' requested here
        static const type val = get_registration_manager<int>().add_item(make_type_data<T>());
                                                                         ^
/usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:390:105: note: in instantiation of member function 'rttr::detail::type_getter<bool, void>::get_type' requested here
    return detail::type_getter<typename std::remove_cv<typename std::remove_reference<T>::type>::type>::get_type();
                                                                                ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:268:47: note: in instantiation of function template specialization 'rttr::type::get<bool>' requested here
                arg.get_value<type>() = type::get<T>();
                                              ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:55:43: note: in instantiation of member function 'rttr::detail::variant_data_base_policy<bool, rttr::detail::variant_data_policy_arithmetic<bool>, rttr::detail::default_type_converter<bool, rttr::detail::convert_from<bool> > >::invoke' requested here
:   m_policy(&detail::variant_policy<Tp>::invoke)
                                          ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_converter.h:283:31: note: in instantiation of function template specialization 'rttr::variant::variant<const bool &, bool>' requested here
        return to_enumeration(from, to);
                              ^
In file included from /Users/gabrielnuetzi/Desktop/ExecutionGraph/gui/executionGraphGui/cefapp/mac/AppMac.mm:20:
In file included from /usr/local/opt/rttr/include/rttr/type:31:
In file included from /usr/local/opt/rttr/include/rttr/type.h:32:
In file included from /usr/local/opt/rttr/include/rttr/string_view.h:498:
In file included from /usr/local/opt/rttr/include/rttr/detail/impl/string_view_impl.h:32:
In file included from /usr/local/opt/rttr/include/rttr/detail/misc/utility.h:34:
/usr/local/opt/rttr/include/rttr/detail/misc/misc_type_traits.h:490:68: error: non-type template argument is not a constant expression
    using is_associative_container = std::integral_constant<bool, !has_is_valid_alias<associative_container_mapper<Tp> >::value>;
                                                                   ^
/usr/local/opt/rttr/include/rttr/detail/type/type_data.h:323:92: note: in instantiation of template type alias 'is_associative_container' requested here
                                              TYPE_TRAIT_TO_BITSET_VALUE_2(::rttr::detail::is_associative_container, is_associative_container) |
                                                                                ^
/usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:302:74: note: in instantiation of function template specialization 'rttr::detail::make_type_data<bool *>' requested here
        static const type val = get_registration_manager<int>().add_item(make_type_data<T>());
                                                                         ^
/usr/local/opt/rttr/include/rttr/detail/type/type_impl.h:390:105: note: in instantiation of member function 'rttr::detail::type_getter<bool *, void>::get_type' requested here
    return detail::type_getter<typename std::remove_cv<typename std::remove_reference<T>::type>::type>::get_type();
                                                                                ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_policy.h:290:61: note: in instantiation of function template specialization 'rttr::type::get<bool *>' requested here
                data.m_type                         = type::get< raw_addressof_return_type_t<T> >();
                                                            ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_impl.h:55:43: note: in instantiation of member function 'rttr::detail::variant_data_base_policy<bool, rttr::detail::variant_data_policy_arithmetic<bool>, rttr::detail::default_type_converter<bool, rttr::detail::convert_from<bool> > >::invoke' requested here
:   m_policy(&detail::variant_policy<Tp>::invoke)
                                          ^
/usr/local/opt/rttr/include/rttr/detail/variant/variant_data_converter.h:283:31: note: in instantiation of function template specialization 'rttr::variant::variant<const bool &, bool>' requested here
        return to_enumeration(from, to);
                              ^
fatal error: too many errors emitted, stopping now [-ferror-limit=]
20 errors generated.
make[3]: *** [gui/executionGraphGui/CMakeFiles/ExecutionGraph-GUI.dir/cefapp/mac/AppMac.mm.o] Error 1

Thx for the help!

 Any clue???

@acki-m : Got it: with the the macro sourounding it works, but why?
RTTR_REGISTRATION
{
rttr::registration::class_<foo>("foo").method("bar", &foo::get_point);
}

ahhh, I just thought you just simplified the test case and has leave out the macro.
It hast nothing to do with the macro itself
You can also not compile this:
std::string("hello");  // error C2059: syntax error: 'string'

without putting it in a function or assigning a value
auto s = std::string("hello"); // Ok

The same like the registration call.
However, registration object is not copy-able, that's why this doesn't work either:
auto foo = rttr::registration::class_<foo>("foo").method("bar", &foo::get_point); // attempting to reference a deleted function

thanks (that was a bit stupid from my side, I though it also works, because you wrote it like so :-))
the initial compilation problem still existed, up to now. The problem is strange, but I refactored my code such that no .mm ObjectiveC codefile (mixing C++) includes <rttr/type>. I could not get away with it. Somehow clang/gcc does not like it. I am wondering if he ObjectiveC stuff dispatches to XCode???

Is this now solved for you?

jeah, I think its just when I try to compile .mm files meaning objectiv-c and c++ mixed, we have problems, why I have no clue!


imageStore of RWTexture2D

Hi, this is a follow up issue of
https://github.com/shader-slang/slang/issues/615
I can't find a good way to write to a one channel RWTexture2D/3D anymore in the new slang version.
When slang was still supporting glsl, the following code works to write one channel RWTexture:
layout(set = 0, binding = 2, r32f) uniform image3D gOccupancyTex;
imageStore(gOccupancyTex, ivec3(crd), ivec4(outputId, 0,0,0));
But with the depreciation of glsl, I can't find a way to write to one channel RWTexture anymore. I tried:

RWTexture3D gOccupancyTex;
float outputId = 1;
gOccupancyTex[uint3(crd)] = (float4)(outputId, 0,0,0);
It has the error:
Program Linkage failed.
Program with Shaders:
ComputeOccupancy.hlsl/main/
/MyProject/ComputeOccupancy.hlsl(147): error 30019: expected an expression of type 'float', got 'float4'
I also tried
RWTexture3D gOccupancyTex;
float outputId = 1;
gOccupancyTex[uint3(crd)] = outputId;
It has the error:
Program Linkage failed.
Program with Shaders:
ComputeOccupancy.hlsl/main/
ERROR: /MyProject/ComputeOccupancy.hlsl:147: 'imageStore' : no matching overloaded function found
ERROR: /MyProject/ComputeOccupancy.hlsl:147: '' : compilation terminated
ERROR: 2 compilation errors.  No code generated.
None of them works.
This happens during the upgrade from Falcor2 to Falcor3 and I integrated the latest fix from slang. thank you very much!

One note is that the expression (float4)(outputId, 0,0,0) doesn’t do what you might expect. Written that way it is interpreted as a cast of the expression (outputId, 0,0,0) to the type float4. The expression (outputId, 0,0,0) is a valid expression using the “comma operator” and evaluates to zero. Hopefully rewriting to float4(outputId, 0,0,0) will work for you.
On the other stuff, we definitely have a bug where we don’t support RWTexture2D<float> or RWTexture2D<uint> etc. As you might have noticed, we don’t output a correct GLSL format for them. I can try to look at this, but turnaround may not be great with the upcoming SIGGRAPH conference getting close.

Thanks Tim. You are right about(float4)(outputID, 0,0,0). It was a typo. But removing () surrounding float4 has the same error in slang. We were able to write ImageStore(gOccupancyTex, ivec3(crd), ivec4(outputId, 0,0,0) and it works before glsl is supported. This is currently blocking us. thanks.

To make sure I understand. The issue here is that a 4-component image works fine, but you need a 1-component image format (e.g., Slang must output layout(r32f) for the GLSL declaration of the image).
Otherwise, it would seem like using RWTexture3D<float4> (aka, just RWTexture3D) would be usable for a workaround.

That's correct.
RWTexture3D would work for shader compilation, but it uses 4 times more memory and bandwidth affecting performance, and code patches in cpp which i am trying to avoid doing that.

PR #622 should implement a fix for this issue.

thanks!

A fix has been merged in #622, and is now released as part of Slang v0.10.31.
I'm closing this out, but please feel free to re-open or file a new issue if something doesn't work as needed.


Make PurchaseInfo a proper class that can be overridden in the same way as other classes

I need to add extra methods to the PurchaseInfo class, but because it's defined and used directly in apps/partner/strategy.py I can't without duplicating that whole file.
It'd be helpful if apps/partner/strategy.py was changed to attempt loading that class using get_class and falling back to the current default if it's not been overridden somewhere else.

I needed to add a method any_available_to_buy that would return True if the product or any variants were available to buy. This is used in templates to conditionally show the basket or let users sign up for alerts if nothing can be bought.

I needed to add a method any_available_to_buy that would return True if the product or any variants were available to buy.

This is something that would typically be done in the Strategy and Selector classes (both of which can be overridden), which are responsible for determining whether a product or variants is available to buy or not, and the price information.
The PurchaseInfo tuple is intended to be a very lightweight container for holding the results of a strategy (price, availability, stock record) rather than for performing any logic.
Is there a reason why you can't do this logic in a custom Strategy class?

Oh right, I hadn't seen that the strategy instance was available as request.strategy.  Is that always the case? If it is I can probably move my code into my strategy. I'll try and get back to you.

Yes, the BasketMiddleware sets request.strategy for all requests.

Closing as it seems that the Strategy class should let you achieve what you want. Feel free to reopen if you still think there's a use case that isn't being met.


Create gitattributes file on CreateProject

On CreateProject, the gitattributes file should also be created recognizing APL as a language.
Could have it right after
_←p WriteGitIgnore ''
_←p WriteGitAttributes ''
WriteGitAttributes would look very similar to WriteGitIgnore, the only difference is the text written and the filename. Hence, it might be better to refactor as one 'WriteGitFile' function that takes 'attributes' or 'ignore' and then the text to insert.
The important line to add would be
*.apl? linguist-language=APL
N.B. This may be a "temporary" solution, so you may decide that it's not worth adding. Ideally GitHub will recognize .apl* files as being APL source code (see https://github.com/Dyalog/link/issues/52 for context). I'm just not sure when that will happen.

Yes, I've been doing this manually. Will put it.


Review "Mind the progress"

Link: https://kreativgesellschaft.org/wissen/mind-the-progress/

Spotify: https://open.spotify.com/show/1lyvtdWVEKT3uyl2TCtB5R?si=83db31715d064848

In my opinion: Not fitting our tech definition.
Big topic is manipulation in the current times, Fake news, etc.


[Android] Fix selection state restoration

Problem
The selection position is not preserved when sharing state between two composable editors (which represent the same editor but exist at different call sites).
Solution

When creating a new editor, apply the selection position found in the state
Also, save the selection when saving state

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (e32ea98) 88.36% compared to head (f3482d3) 89.88%.

Additional details and impacted files
@@             Coverage Diff              @@
##               main     #825      +/-   ##
============================================
+ Coverage     88.36%   89.88%   +1.52%
============================================
  Files           157       82      -75
  Lines         18051    14725    -3326
  Branches        944        0     -944
============================================
- Hits          15951    13236    -2715
+ Misses         1851     1489     -362
+ Partials        249        0     -249

Flag
Coverage Δ

uitests
?

uitests-android
?

uitests-ios
?

unittests
89.88% <ø> (+3.21%)
:arrow_up:

unittests-android
?

unittests-ios
?

unittests-rust
89.88% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.
see 75 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Sorry, that was a bit unclear. This is not meant to support two different editors being displayed at the same time and sharing the same state; it's to support the same editor being displayed in different layouts (i.e. at different call sties in the compose tree).


Sqlite provider uses ambigous DateTime format

Steps to reproduce

Suppose I'm in GMT+2
Have a DateTime field in an entity
Store there a date built from "2016-06-20 08:50:56Z"
The database will contain the string representation without time zone (using @"yyyy-MM-dd HH:mm:ss.FFFFFFF") i.e "2016-06-20 08:50:56.12345"
In another process, load the entity from the db, the default parser will use current time zone to convert string to date
The date will be 2 hours off

The issue
This will work only if server and client are both in Greenwich
Since sqlite uses TEXT for DateTime, the format should be explicit with time zone (i.e. "u" will do)
Further technical details
EF Core version: 7.0.0-rc1-final
Operating system: OSX
Visual Studio version: n/a

Hey,
The lack of time zone awareness is an inherent limitation of DateTime. For time zone aware dates, you should use DateTimeOffset instead.
~Rowan


[glfw3] Fix the name of the dynamic library under win in the pc file

Fixes https://github.com/microsoft/vcpkg/issues/33337
Fix the inconsistency between the library name and the link library name in the pc file when dynamically compiling on the window platform.
Usage test pass with following triplets:
x86-windows
x64-windows

[X] Changes comply with the maintainer guide
[X] SHA512s are updated for each updated download
[ ] The "supports" clause reflects platforms that may be fixed by this new version
[ ] Any fixed CI baseline entries are removed from that file.
[ ] Any patches that are no longer applied are deleted from the port's directory.
[X] The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[X] Only one version is added to each modified port's versions file.

A fix PR 2420 has been submitted to upstream.


fontdir: add ttc to font regex

.ttc fonts are used by noto-fonts-cjk

Motivation for this change
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 101724 1


Update CodeQL Auto-Setup extension documentation

This pull request introduces the documentation for CodeQL Auto-Setup task extension for Azure DevOps. The changes include a comprehensive guide in the README.md file under the src/extensions/codeql-autosetup directory. The guide provides detailed instructions on how to use the extension, from installing dependencies, compiling the task, configuring the publisher, to packaging the extension. It also includes information on how to share the extension with the desired organization and ensure the correct permissions are set for the pipelines.

src/extensions/codeql-autosetup/README.md: Added a comprehensive guide on how to use the CodeQL Auto-Setup task extension, including details on how to install dependencies, compile the task, configure the publisher, package the extension, share it with the desired organization, and set up necessary permissions for the pipelines.

Closes #31


 Replacing them with placeholders might make people more inclined to use their own instead.

I am fine with this change but concerned this is Empties territory.


chore: jsonfmt billing

Automation for azure-sdk-for-go

Automation for azure-sdk-for-python

Can one of the admins verify this patch?


add client key and certificate for logging fluentd

Problem:
advance mode have support client key and certificate for fluentd logging
target but normal mode not yet
Solution:
add client key and certificate for fluentd
Issue:
https://github.com/rancher/rancher/issues/18438

LGTM

rebase

lgtm


Performance work

Updates PyO3 to 0.20
Use a persistent output buffer in flat_map
Use GILPool to GC memory earlier
Turn logic functions into refs before item loops
Make map a core operator
Comment on swapping
map uses outbuff too; renames for consistency
Don't convert next_awake into Python if the wakeup was immediate
Fixes encoder tests

Just another datapoint to prove this is useful, I ran my usual kafka-to-kafka throughput benchmark for my schema_registry_pyoperators branch both with and without this PR merged in, and without it the dataflow struggles to handle even 5k msgs/s, while with this PR merged its back to ~100k msgs/s that we had in 0.17


X-Request-Id instead of X-Vcap-Request-Id

By default, a Ruby on Rails app will tag all logs with the value of X-Request-Id. For example, here's a request to a Rails 5 app on Pivotal Web Services:
$ curl -I https://rails5.cfapps.io/
HTTP/1.1 200 OK
Content-Type: text/html; charset=utf-8
Date: Fri, 26 Aug 2016 23:30:36 GMT
X-Request-Id: 55bdeb17-ad2d-4c59-b033-bee8a8e6430d
X-Runtime: 0.002347
X-Vcap-Request-Id: 4bf49bd8-7e62-4a09-720c-2cd4443e8d87
Connection: keep-alive

And the corresponding cf logs output:
2016-08-26T17:30:36.49-0600 [APP/0]      OUT I, [2016-08-26T23:30:36.498456 #20]  INFO -- : [55bdeb17-ad2d-4c59-b033-bee8a8e6430d] method=HEAD path=/ format=*/* controller=WelcomeController action=index status=200 duration=1.13 view=0.81 db=0.00 params={}
2016-08-26T17:30:36.50-0600 [RTR/3]      OUT rails5.cfapps.io - [26/08/2016:23:30:36.497 +0000] "HEAD / HTTP/1.1" 200 0 0 "-" "curl/7.43.0" <IP_ADDRESS>:38653 x_forwarded_for:"<IP_ADDRESS>" x_forwarded_proto:"https" vcap_request_id:4bf49bd8-7e62-4a09-720c-2cd4443e8d87 response_time:0.007176212 app_id:3e7d31a6-e880-4f50-ae05-149fc44c4257

The app log includes X-Request-Id of 55bdeb17-ad2d-4c59-b033-bee8a8e6430d. Has there been consideration of adopting X-Request-Id in place of X-Vcap-Request-Id? It would improve the developer experience of correlating gorouter logs with application logs.

Hi Glenn,
Unfortunately, there are no standards in the tracing community. I'm feeling particularly frustrated about this at the moment.
Years ago, the Cloud Foundry dev team had Gorouter initiate X-Vcap-Request-Id, and many of the CF components passed this header through and it has been very helpful in troubleshooting internal Cloud Foundry system interactions. I'm not sure we can remove support for that; I believe there's logic for it throughout the CF system components.
Recently we added support for Zipkin tracing, because surprise(!) Zipkin doesn't work with anything but it's own headers. So when enabled, Gorouter will send backends X-B3-TraceId, X-B3-SpanId, and X-B3-ParentSpanId.
I'm not surprised to hear Rails has its own tracing header. Where does it end? We would have to add another optional deployment switch for "Rails tracing" to send X-Request-Id, because with every additional header the app request payloads grow and the router access logs grow.
1000 requests / second * 30 Bytes = 2.4 GB / day, just to log the additional header.
Maybe you could use a Zipkin library with your app to handle logging of tracing data? Then you could correlate the Zipkin trace id logged by the app with the same id logged by the router.
Thoughts?

Hi Shannon,
Thanks for taking the time to give a thoughtful response. Rails most likely adopted X-Request-Id from Heroku: https://devcenter.heroku.com/articles/http-request-id
Perhaps we should instead try a PR for Rails that allows the header to be configurable, while defaulting to Heroku's X-Request-Id.

Thank you, Glenn. I don't want you to feel like we're leaving Rails in the cold, bu I would love to avoid adding many more trace ids if there's a painless workaround.
If Rails can't use a configurable header natively, there are Zipkin libraries for most frameworks. FWIW, Zipkin came out of Twitter and seems to be a popular tracing spec. Here's a ruby lib I found, I suspect there are others: https://github.com/openzipkin/zipkin-ruby
I'll close this issue for now; please feel free to re-open with followup questions.


[fix] adding contrib to package_data in setup.py

fixing the problem with xnd build on my OSX
ses details here

Thank you!


Plan going forward

Hi,
This project seems to be first Kotlin-friendly attempt to model mapping. Since there is a new (final) release of MapStruct 1.3.0 do you have any plans to publish this library to the public?

Hi @Nekromancer !
Thanks for your question. Yes, I have.
I plan to publish this to maven central and/or jcenter. You might expect this around mid/end of October since right now I'm very busy and I couldn't find a spot for this project.
In the meantime feel free to ask any question, and remind me this after a few weeks.
Cheers.

Hi, just a friendly reminder about this! :)

@Nekromancer Thank you for your patience.
The first release is out. I've updated the readme as well.


HrHRNet seems to need much time for training 300 epochs if using 1 GPU

Hi authors,
When I train the source code with one GPU of TitanX which does not have distributed training, I calculate that the training for 300 epochs at least takes 25.5days.  Do you have suggestions that make it faster? I would be very appreciate if you could response me.
Thanks~~


make snapshot file location configurable

I am trying to switch from ava to node-tap and really enjoying the switch, not least for the fact that the code is much more grok-able.
The only feature from ava that I miss, is the location of the snapshot files. node-tap
stores these in a global, hard-wired path.
ava co-locates these with source files, traced through compilation via source-maps.
My use case:
I find this particularly useful when developing complex applications, when the final set of
useful modules for the application is in flux. These can be developed as sub-directories
within the single node-module, without worrying about final form.
As the code-base stabilizes, it's a simple matter to create a new node-module, copy and paste the appropriate sub-directory to its new resting place, re-build and commit.
The issue
Ideally, acceptance criteria should involve a simple re-build. However, since the snapshots
are not co-located and in-fact don't preserve the directory structure, this is not possible without significant effort - because the dir-path in the new repo is different and will have to be hand modified/scripted.
Ideal solution
Obviously, preserving the directory structure would help some, but ideally, co-locating the snapshot files and preserving the directory structure would be the ideal.
Possible solution
Interestingly, it seems this should be as simple as changing the computation of this.file here Perhaps this could be a configurable option, or the snapshot location could be a function that is passed in.
The ask
Before I go implementing such a change, I wanted to check in to see if there is any appetite for such a modification and what for would be acceptable.

I'm glad to hear you're finding tap enjoyable :)  I can see that it imposes some friction on refactoring though, to be sure.  I'm not opposed in principle to making this configurable (or even changing it entirely), but there are a few things to consider.
One hazard will be that the default file inclusion logic may happen upon snapshot files, which we don't want, and it's nice to be able to just require() them as .js files.  (Currently, the default include regex walker can avoid even descending into the tap-snapshots folder.)
Also, I sometimes do things like tap test/fixtures/*.js --test-arg=test/run.js so that the executed command is something like node test/run.js test/fixtures/foo.js.  Then test/run.js loads the fixture and compares it against a snapshot.  In order for this to work, the filename has to be dependent on not just the main filename, but the entire set of command-line arguments.  (Otherwise node test/run.js test/fixtures/bar.js will load/clobber the same snapshot.)
It would help encourage people to check snapshots into source control if they weren't in a separate folder.  However, deleting and re-generating might be trickier.  When I refactor tests, I sometimes do rm -r tap-snapshots; npm run snap to regenerate.  If they were scattered throughout my test suite, that might be trickier.  (I guess I could still just do rm test/**/*.snap.js or whatever?  Or even add a --clear-snapshots option to delete any snapshot files that weren't loaded?)
If you implement it as a configurable function, take a look at how the --coverage-map option is implemented.  I'd probably want to follow that same pattern.  In the Test class, it should look at an environment variable TAP_SNAPSHOT_FILE, which is set in the environment by the test runner.

thanks for being so welcoming on this @isaacs.
I will be working on this, but have limited time. To not clutter up the open issues, will close this one for now and reopen once I have something to share.

Hi @sramam how is your experience with node-tap nearly a year on from AVA?


fix: dev environment

:tada: This PR is included in version 1.1.4 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Security Issue: Upgrade package " " to " "

You can fix this yourself by not compiling the package again


Feature/1495/verification

For issue ga4gh/dockstore#1495
remove whitespace changes using "?w=1" in url or via github controls
First pass at using the new verificationSource object in sourcefiles.
3 changes:

Version component removed tool/workflow path, verified column changed to verified platforms
View version component has a verified table appended to it with (path, metadata, and platform fields)
entry component sidebar updated to only show 1 version's verified info.

Also fixes the infamous starring bug
Also fixes the TRS link's href

Remind me to review in action

(suggestions provided in 1-1, request re-review when ready)


No Hires.Fix

I would be good to get images with higher dimensions, but it seems there are no ways to upscale an image in the notebook

In Utils section of the notebook there is an img2img refiner, that allows to upscale image using the same stable diffusion pipeline and prompt as in txt2img.


About Screen Updates

Multiple updates to the About Screen

Add Accessibility link to https://accessibility.mit.edu
Add Acknowledgements Section--discuss if link to Github https://github.com/digitalcredentials/learner-credential-wallet#acknowledgements or self contained in apps
- Consider license file with included libraries
Add link to Privacy and Terms of Service (once we create them!)
License?

@bmuramatsu, my apologies, I must've missed this. I've added a PT story so this can get into iteration planning
https://www.pivotaltracker.com/story/show/180525340

No you didn't miss it! We hadn't figured out what to do about Acknowledgements yet.

We decided to change the "For more information" link from DCC website to http://eduwallet.app.
Closing this.


how to reset with changed state

i got 2 wrappers ,  both of them got zoom.
i need -
when 1 wrapper is clicked , the other one zoom need to reset.
so my question is -
how can control the zoom reset in useEffect ?
or mabye a better solution.

it may be helpful  https://github.com/prc5/react-zoom-pan-pinch/issues/94#issuecomment-614626023


deps: bump dvc-objects to 0.14.1

see https://github.com/iterative/dvc-objects/pull/181#discussion_r1065743880

Codecov Report
Base: 55.19% // Head: 55.19% // No change to project coverage :thumbsup:

Coverage data is based on head (23ff6df) compared to base (627c901).
Patch has no changes to coverable lines.

Additional details and impacted files
@@           Coverage Diff           @@
##             main     #250   +/-   ##
=======================================
  Coverage   55.19%   55.19%
=======================================
  Files          49       49
  Lines        2937     2937
  Branches      506      506
=======================================
  Hits         1621     1621
  Misses       1235     1235
  Partials       81       81

Impacted Files
Coverage Δ

src/dvc_data/hashfile/db/__init__.py
55.67% <ø> (ø)

src/dvc_data/hashfile/db/reference.py
52.17% <ø> (ø)

src/dvc_data/hashfile/transfer.py
16.85% <ø> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Signature invisible in Adobe Reader but visible in other viewers

Describe the bug
When I create a visible signature, I can see it in Preview and Skim, but not o Adobe Reader.
The visible signature display should be about halfway down, centralized in the page.
To Reproduce
pyhanko sign addsig  --field 1/500,530,100,485/Signature1 pkcs12 in.pdf out.pdf cert.pfx

Open in Skim and Preview, the signature is visible, but Acrobat Reader does not display it.
Expected behavior
I expect all PDF viewers to display the visible part of the signature.
The pyhanko signature validates digitally, but it might pose bureaucratic impediments if the officer cannot see any visual mark.
Environment (please complete the following information):

OS: Mac OS 12.6.6 Monterey
Adobe Reader 2024.001.20615

Hi, this kind of problem is unfortunately impossible to diagnose without a copy of the specific input document that's giving you issues. Can you provide one?
I'm also assuming that the actual configuration you're using to populate the visible field is somewhere in your configuration file, can you share that as well?

I have encountered this behavior when AcroForm ->NeedAppearances is present and set to 'true', when document is not signed PDF acrobat reader displays signature field ok, but when i sign it using pyhanko, NeedAppereances is copied over with signature to this block:
<ORIGINAL_PDF>
%%EOF
2 0 obj
<<
/Producer (WeasyPrint 61\0562\073 pyHanko 0\05623\0561)
/ModDate (D\07220240408220437\05302\04700\047)
>>
endobj
3 0 obj
<<
/Type /Catalog
/Pages 1 0 R
/AcroForm <<
/Fields [ 7 0 R ]
/DR 4 0 R
/NeedAppearances true
/SigFlags 3
>>
<REST_OF_SIGNATURE>

And signature field become invisible, it also disappear from list of signatures... (So PDF in PDF acrobat reader looks like unsigned)
All other PDF readers are fine, just PDF acrobat reader is doing this..., when i remove NeedAppearances or set it to false in unsigned PDF and sign it using pyhanko all is well in PDF acrobat reader...
From my testing it looks like /NeedAppearances true carried over to signature block is the issue?
I'm also attaching my testing PDFs:

signed-61.2-need-app-false.pdf: Signed PDF where NeedAppearances was set to 'false' before signing (Work ok in PDF acrobat reader)
signed-61.2-need-app-removed.pdf: Signed PDF where NeedAppearances was removed before signing (Work ok in PDF acrobat reader)
signed-61.2-uncompressed.pdf: Signed PDF where NeedAppearances was set to 'true' (default behavior of my PDF * generator) this is broken in PDF acrobat reader
unsigned-61.2-uncompressed.pdf: Unsigned PDF where NeedAppearances was set to 'true' (default behavior of my PDF generator) this is displayed correctly in PDF acrobat reader
unsigned-54.2.pdf: Unsigned PDF where NeedAppearances is missing (Work ok in PDF acrobat reader)
signed-54.2.pdf: Signed PDF where NeedAppearances is missing (Work ok in PDF acrobat reader)
signed-61.2-uncompressed-app-removed-from-sig.pdf: Signed PDF where NeedAppearances was manually removed from signature block, signature is displayed correctly in PDF acrobat reader but PDF is corrupted (i did simple delete in text editor)

signed-61.2-need-app-false.pdf
signed-61.2-need-app-removed.pdf
signed-61.2-uncompressed.pdf
unsigned-61.2-uncompressed.pdf
unsigned-54.2.pdf
signed-54.2.pdf
signed-61.2-uncompressed-app-removed-from-sig.pdf
54.2 means PDF generated using Weasyprint 54.2
61.2 means PDF generated using Weasyprint 61.2
(I was dissecting missing signatures in PDF acrobat reader after weasyprint update)

Huh, interesting. If NeedAppearances is the culprit, that kind of tracks. It's deprecated in PDF 2.0 and probably ignored by all non-Acrobat processors anyhow. The PDF 2.0 requirement is that all fields need to supply appearance streams, so NeedAppearances is pretty much obsolete.
Nonetheless, I would assume that NeedAppearances only kicks in on fields that don't already have an appearance stream... The fact that that's not what you observe is indeed strange.
If systematically removing NeedAppearances solves the problem, I'm happy to do that (or perhaps hiding it behind a toggle). I don't really have the energy to hunt down all the quirks of Acrobat these days :)

Hmm i'm going to check if /AP is set for signature field...

Ok affected field does have AP specified...

@MatthiasValvekens i think that not passing NeedAppearances to signature block after EOF as a option should do the trick (not sure what should be the default behavior tho, up to you)

Thanks for that analysis. I think removing NeedAppearances by default is probably a sane thing to do. I plan to cut a release later this month, this can probably be squeezed in.

Thanks for this amazing library. I just wanted to check if there is any update on this?


[FLINK-26214] Helm chart uses GitHub packages for docker image

Adds the new package to the helm chart and removes the now unnecessary steps from the quickstart.

Out the scope of this PR, I am thinking how we could install the flink-kubernetes-operator like airflow. Then we do not force the users to download the source code.
helm repo add apache-airflow https://airflow.apache.org
helm upgrade --install airflow apache-airflow/airflow --namespace airflow --create-namespace

https://airflow.apache.org/docs/helm-chart/stable/index.html

Thanks or the feedback, team. I am closing this as per #126 we are probably taking a better approach to this.


Cannot add custom class to tooltips

The documentation states that I should be able to add a custom class to tooltips using data-options, but it just doesn't seem to work. I've tried this:
data-options="tooltip_class: '.newstip';"
data-options="tooltip_class: 'newstip';"
data-options="tooltip_class: .newstip;"
data-options="tooltip_class: newstip;"

There is a closed (I can't see why) issue about this: #3542

Hey there !
I agree that this is not working and I wonder why the other issue ended up with such answers.
After giving it a look, I think this should be fixable with just those 2 modifications :
On line 17 of foundation.tooltip.js :
tip_template : function (selector, tooltip_class, content) {
        return '' + content + '';
      }

and line 167 of the same file :
      var $tip = $(tip_template(this.selector($target), settings.tooltip_class.substring(1), $('

').html($target.attr('title')).html())),

Here is a messy jsfiddle showing it in action : http://jsfiddle.net/qq6nzxaj/
This deliberatly keep the "tooltip" class on the tooltips, because I like just adding some little modifications without rewriting it all and removing it may mess it all up anyway because of how this plugin is currently coded (no offense to anyone here).
Regards,
Lyn.

We added this to our "known issues" section in our planning board for the next version. A PR would be valuable to the community, otherwise It will be addressed then. You can see and vote on the proposed updates here: https://trello.com/b/QBPKlQqf/foundation-sites


connectionPlugin breaks with 0.19-next.6

We have nonNullDefaults.input = true in our project. But that now results in all connectionPlugin arguments to also be non null.
This was not the case previously, and connectionPlugin should probably be explicit in its requirements.
There is a similar case for nonNullDefaults.output = true where it sets PageInfo.startCursor/endCursor to be non-nullable

👍 check #671

Awesome!

I guess we should mention that this is actually an issue in the newest release 0.19 😅


where is warp_r   in  loss_functions.py #44

We updated loss_functions.py to be inclusive with an example of the ranking used in the paper.


[bug]: Incorrect clear_balace value after cooperative channel close if funds are sent to an address that does not belong to the given lnd

Background
I noticed this issue within the Zeus app when I was viewing the closed channel details. In this channel, at the time of its closure, there were several tens of % of oubound liquidity on my side, after its closure, the Zeus application showed me 100% of the funds as inbound liquidity. I investigated this problem directly in lnd and when I typed lncli closedchannels I found that the settled_balance value here is 0. The same problem was repeated when closing another channel, the first closing was remote initiator, the second closing was initiated by me. I subsequently tested this behavior within Polar. I found that this behavior occurs when my funds are sent to an address that does not belong to the lnd wallet. This can happen for 2 reasons (both tested): 1. close_address is set when the channel is opened (I am the initiator). 2. when the channel is closed (I am the initiator) and delivery_addr is set.
Your environment
tested on 2 setups:
1.
Polar v2.2.0; Docker v25.0.3; Compose v2.24.5 (Win 10); network setup: 2 Bitcoin Core v26.0; 2 LND v0.17.4-beta (both connected to the same Bitcoin Core node)
2.
uname -mrsv
Linux 5.4.0-164-generic

bitcoind --version || btcd --version
Bitcoin Core version v26.0.0

lsb_release -a
Distributor ID: Ubuntu
Description:    Ubuntu 20.04.6 LTS
Release:        20.04
Codename:       focal

lncli --version
lncli version 0.17.3-beta commit=v0.17.3-beta

Steps to reproduce
Example 1: close_address specified when creating the channel - Polar:

I have 2 lnd nodes here (Alice and Bob) both connected to Bitcoin core called backend 1. In addition to this I also have backend2 Bitcoin core to which no lnd is connected. Then send some BTC to Alice's node
using backend2 Bitcoin core I generate address bitcoin-cli getnewaddress "" "bech32"
Open a channel from the Alice node to Bob using: lncli openchannel --node_key <Bob-Pubkey> --local_amt 2000000 --close_address <address generated by backend2>
Mine some blocks
Now I'll close the channel with cooperative close - it doesn't matter who the initiator is, using Polar's graphical interface or using lncli closechannel --funding_txid <funding_txid>
Mine some blocks
List the closed channels on the Alice node: lncli closedchannels

It can be seen here that settled_balance = 0 despite the fact that all the funds were owned by Alice all the time

Example 2: opening a channel without close_address, closing it using a command in the terminal with the delivery_addr flag - Polar:

same as example 1
same as example 1
Using Polar's graphical interface or using lncli openchannel --node_key <Bob-Pubkey> --local_amt open a channel from the Alice node to Bob
Mine some blocks
Now close the channel with cooperative close from Alice node using terminal: lncli closechannel --funding_txid <funding_txid> --delivery_addr <address generated by backend2>

Mine some blocks

List the closed channels on the Alice node (lncli closedchannels) - same result as example 1

Example 1 happened to me on the node I run on the mainnet. When opening the channel, I used the --close_address flag with the address of my HW wallet. During cooperative close, the funds were sent to this address, in the lncli closedchannels listing I subsequently see settled_balance 0.
If the channel is closed using force close, this problem does not occur.
Expected behaviour
settled_balance will correspond to the correct amount in all channel closing cases
Actual behaviour
In certain cases it does not match and is 0

Thanks for the issue report @kulisekf!
I've reproduced the issue and have verified that "settled_balance" indeed doesn't include the local balance if a non wallet close_address is passed when opening the channel.
The issue is that in chain_watcher.go we assign the value for the SettledBalance to the local localAmt variable:
https://github.com/lightningnetwork/lnd/blob/5cb4811e86ed1607c1c9671756d7276256e2ec44/contractcourt/chain_watcher.go#L1022
The localAmt variable is assigned at:
https://github.com/lightningnetwork/lnd/blob/5cb4811e86ed1607c1c9671756d7276256e2ec44/contractcourt/chain_watcher.go#L1010
Now the toSelfAmount func will currently only return balance for addresses which are controlled by the wallet due to the definition of the isOurAddr func, and not for non wallet addresses, despite the fact the address has been sent in as our close_address for the channel.
https://github.com/lightningnetwork/lnd/blob/5cb4811e86ed1607c1c9671756d7276256e2ec44/contractcourt/chain_watcher.go#L976-L995
That behaviour would need to be changed in order to solve this issue.
I think a potential solution would be to modify the isOurAddr func that is sent in to chainWatcher, and that the function also matches against the close_address if one has been set. Though I haven't verified if this would work expected  nor if this is the optimal solution.
https://github.com/lightningnetwork/lnd/blob/5cb4811e86ed1607c1c9671756d7276256e2ec44/contractcourt/chain_arbitrator.go#L1146
The isOurAddr func would also need to be updated if an address is passed as the delivery_addr during the closechannel call.


DummyLSU: Delay pushing store result until execution

Small change, useful for implementing reporting exceptions on store in #394, exported as independent change for eventual discussion.
This PR unifies LOAD and STORE instruction result pushing/accepting to point where instruction in actually executed. It will be useful to be able to pass pipeline exception flags in STORE instructions. Additional benefit is slightly easier to understand logic and it may be helpful in implementing IO reads.
Downside - increased dealy on stores as we need to wait for result. Previously they were executing also after instruction was retired? But this is the only way to handle exceptions on stores - to wait until completion. (Additonal different delay between FU->RET is negligible). I don't think that's a big issue for now as dummyLSU will be replaced, but may be useful note for future. Maybe we could specify Exception-less memory regions, where STORES could execute 'detached'?

Downside - increased dealy on stores as we need to wait for result

I wouldn't care about that now. From one side DummyLSU should be removed and refactored. From the other in normal LSU we will have a store queue, so we will be able to handle loads before committing stores, so they could stay in pipeline for long time, without negative impact for the core.

Previously they were executing also after instruction was retired?

Yes this was an artifact of refactor to add precommit support, which have taken infrastructure of old LSU directly.

Maybe we could specify Exception-less memory regions, where STORES could execute 'detached'?

This is an interesting idea to check while implementing normal LSU.

IPC in benchmarks increased, good, but why??


Update steampipe-plugin-sdk to v1.6.1. Closes #2

Integration test logs

Logs
turbot-macpro-raj:steampipe-plugin-aws raj$ steampipe query
Welcome to Steampipe v0.8.2
For more information, type .help
> select
  url,
  uptime,
  down,
  down_since
from
  updown_check
+----------------------+--------+-------+------------+
| url                  | uptime | down  | down_since |
+----------------------+--------+-------+------------+
| https://turbot.com   | 100    | false | <null>     |
| https://steampipe.io | 100    | false | <null>     |
+----------------------+--------+-------+------------+
> ```
</details>

# Example query results
<details>
  <summary>Results</summary>

Add example SQL query results here (please include the input queries as well)
</details>

Wait to see the feedback on the change suggested to idex.md


when fire the action via chooseAction with startFilter=true options, the mode will be INSERT.

Warning: I will close the issue without the minimal init.vim and the
reproduction instructions.
Problems summary
SSIA
Expected
the mode after firing the action is expected to be INESRT.
Environment Information

ddu-ui-ff version (SHA1):
ab39554
denops.vim version (SHA1):
83f167b
deno version(deno -V output):
deno 1.38.5
OS:
WSL Ubuntu22.04.3
neovim/Vim :version output:
NVIM v0.10.0-dev-1846+gf31f260f0
Build type: RelWithDebInfo
LuaJIT 2.1.1702233742

Provide a minimal init.vim/vimrc without plugin managers (Required!)
set rtp+=~/.cache/dein/nvim/repos/github.com/vim-denops/denops.vim

set rtp+=~/.cache/dein/nvim/repos/github.com/Shougo/ddu.vim
set rtp+=~/.cache/dein/nvim/repos/github.com/Shougo/ddu-ui-ff
set rtp+=~/.cache/dein/nvim/repos/github.com/Shougo/ddu-source-file
set rtp+=~/.cache/dein/nvim/repos/github.com/Shougo/ddu-source-action
set rtp+=~/.cache/dein/nvim/repos/github.com/Shougo/ddu-kind-file

let s:ddu_config_json =<< trim MARK
	{
		"ui": "ff",
		"uiParams": {
			"ff": {
				"startFilter": true
			}
		},
		"kindOptions": {
			"action": {
				"defaultAction": "do"
			}
		}
	}
MARK

let s:ddu_config_json = s:ddu_config_json->join('')->json_decode()

call ddu#custom#patch_global(s:ddu_config_json)

nnoremap [ddu] <Nop>
nmap <Space>u [ddu]
nmap <silent> [ddu]f <Cmd>call ddu#start({
			\ 'ui': 'ff',
			\ 'sources': [{'name': 'file', 'params': {}}],
			\ })<CR>

autocmd FileType ddu-ff call s:ddu_my_settings()

function! s:ddu_my_settings() abort
	nnoremap <buffer> <CR>
				\ <ESC><Cmd>call ddu#ui#do_action('itemAction')<CR>
	nnoremap <buffer> a
				\ <Cmd>call ddu#ui#do_action('chooseAction')<CR>
	nnoremap <buffer><silent> q
				\ <Cmd>call ddu#ui#ff#do_action('quit')<CR>

endfunction

autocmd FileType ddu-ff-filter call s:ddu_filter_my_settings()

function! s:ddu_filter_my_settings() abort
	inoremap <buffer> <C-l>
				\ <ESC><Cmd>call ddu#ui#ff#do_action('leaveFilterWindow')<CR>
	inoremap <buffer> <C-q>
				\ <ESC><Cmd>call ddu#ui#ff#do_action('quit')<CR>
endfunction

How to reproduce the problem from neovim/Vim startup (Required!)

type <Space> u f to start ddu
type <C-l> in filter window to leave filter window
type a to fire chooseAction
move cursor to open action
type <CR> to fire open action

Screenshot (if possible)

Upload the log messages by :redir and :message (if errored)

I think that startFilter should be applied even after chooseAction.
However there are other ui like ddu-ui-filer that don't have startFilter otpion, So it seems to be difficult from a compatibility point of view.

Fixed.  Please update ddu-source-action.


Inconsistent name in custom-query

This is my custom query:
SELECT
  price
FROM sales
WHERE type_id= %%type_id integer%%
  AND key = %%key string%%

The field type_id is named as TypeID in type Sale struct:
type Sale struct {
	SaleID   int            `json:"sale_id"`  // sale_id
	TypeID   int            `json:"type_id"`  // type_id
...

However, the field type_id is named as Type_id in custom query func definition:
// GetPricesByType_idKey runs a custom query, returning results as GetPrice.
func GetPricesByType_idKey(db XODB, type_id integer, key string) ([]*GetPrice, error) {

I think, for consistency, the func definition's name should be func GetPricesByTypeIDKey instead.
Please consider.

That definitely seems like a valid expectation.

As a workaround, you can manually specify the name used when generating a custom query:
xo -N -T Price -F GetPrices pgsql://xodb:xodb@localhost/xodb <<ENDSQL
SELECT
  price
FROM sales
WHERE type_id= %%type_id int%%
  AND key = %%key string%%
ENDSQL

Thanks @kenshaw, I can wait, as I have the same gen script across different DBs and projects.


Private deployment. Non-Docker Windows 11. Unclear how to gain API access[DOCS]:

Description
Testing the suggested endpoint of /api/docs on port 3001 times out for both 'localhost' and '<IP_ADDRESS>'.
There are no docs that mention how to use / access the API for non-docker, private deployment of anything-llm.
Use case is to only use the desktop app for training. Once the LLM is ready to go, all access will be via home spun web page interface to the API.
Can the docs be updated for the Windows install API access.

Non-docker? You are using the desktop app? The desktop app is more for a "single-player" experience and we likely won't expose the API that comes with the docker image because it doesn't really make sense for something that is basically all local.
However, I'm open to discussing this. Why do you need the desktop client API access and what is the use case? Happy to explore that.

Honest... I did watch your YouTubes and read all the docs here, but there was no mention that the different versions had different features.
Also it was not clear to me that the Docker version was an option?
There is no download link for Docker, hence thinking since Im running Windows, the windows download link here is the correct and only choice?

Please point me to the WSL docker running on Windows download / install docs and I will go that way (Happy to nuke the 10+ hours I have in the embedding process).

https://github.com/Mintplex-Labs/anything-llm/blob/master/docker/HOW_TO_USE_DOCKER.md#recommend-way-to-run-dockerized-anythingllm
Can get latest image from docker pull mintplexlabs/anythingllm. You can also keep the embeddings and progress you already have & you don't have to use WSL if you have a docker desktop client running on the host. WSL is known to give networking issues if trying to communicate with programs running on the same machine outside of WSL
Walkthrough on how to do this:

Open the desktop storage folder at C:\Users\<user>\AppData\Roaming\anythingllm-desktop\storage. You should see several folders in this. This is the local storage of the desktop app.

Create a folder where your docker information will persist. Typically this is $HOME\Documents\anythingllm. It should be somewhere your user has access to.

Copy all of the contents of C:\Users\<user>\AppData\Roaming\anythingllm-desktop\storage into the $HOME\Documents\anythingllm directory (or wherever you decided to create the folder from the previous step.)

Run the docker run command to start the container and use the existing storage folder.

$env:STORAGE_LOCATION="$HOME\Documents\anythingllm"; `
If(!(Test-Path $env:STORAGE_LOCATION)) {New-Item $env:STORAGE_LOCATION -ItemType Directory}; `
If(!(Test-Path "$env:STORAGE_LOCATION\.env")) {New-Item "$env:STORAGE_LOCATION\.env"}; `
docker run -d -p 3001:3001 `
--cap-add SYS_ADMIN `
-v "$env:STORAGE_LOCATION`:/app/server/storage" `
-v "$env:STORAGE_LOCATION\.env:/app/server/.env" `
-e STORAGE_DIR="/app/server/storage" `
mintplexlabs/anythingllm;

The docker container should boot and you should have all of your data, embeddings, and settings ready to go, but now in the dockerized app.


Use Vec in ColumnReader (#5177)

Which issue does this PR close?

Part of #5177
Closes #5150
Rationale for this change

See ticket, this pushes Vec into ColumnReader avoiding a whole host of issues related to buffer capacity
What changes are included in this PR?

Are there any user-facing changes?
Most of the changes are to crate-private interfaces, but this is a breaking change to ColumnReader which is public

This currently represents a non-trivial regression for primitive columns with large numbers of nulls, I am investigating this now

Well having bashed my head against these phantom regressions for an embarrassingly long amount of time, it transpires the benchmarks are just exceptionally noisy :facepalm: As written this PR does not represent a consistent performance regression as far as I can ascertain


Improve 'Press any key to close the terminal'

Testing #19057

When a task terminates, the terminal says:
'Press any key to close the terminal'

Maybe better 'Press any key to close'.
It just closes the terminal instance. The terminal stays open if there are other instances.

The message comes from the terminal. I only control it via a Boolean.
@Tyriar best would be if I could control the message shown. The I could show something like:
The task xxx has finished with code: nnn. Press any key to close the terminal.

I believe I already show a message when the task terminates with a non 0 code as well. Currently there is no way outside to send text only to the front end for rendering (bypassing the terminal process). We should try avoid adding this to the api (where tasks will be eventually) unless absolutely necessary as it could cause confusion for both the user and extension author.

Closing this as designed, it's closing the terminal, not the terminal panel. "Terminal instance" is terminology only used within code.


Docs Changes Needed from dbt-core Issue #10062

At a minimum, update body to include a link to the page on docs.getdbt.com requiring updates and what part(s) of the page you would like to see updated.

Already documented and relevant backported features added to v1.6 and v1.7


Please add linux support

When either Pafford or I run Linux, I'll consider it.

I thought maybe I could make the change myself but I can't get it to build.

Haha, yeah. Also, there's no GDI, which is what it's using to add/remove fonts.

I'll try it on my BeOS box instead.  Thanks for your help.

I tried to use Haiku on a machine, but their wifi drivers are from FreeBSD 9.3, and the chip in the machine only works on Windows and Linux. :'(