feat(object_validator): add glog (not working)

Description

Tests performed

Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

Memo:
current commit will output the following build error:
--- stderr: detected_object_validation
In file included from /usr/include/c++/11/vector:67,
                 from /usr/include/c++/11/functional:62,
                 from /usr/include/c++/11/pstl/glue_algorithm_defs.h:13,
                 from /usr/include/c++/11/algorithm:74,
                 from /opt/ros/humble/include/rclcpp/rclcpp/executor.hpp:18,
                 from /opt/ros/humble/include/rclcpp/rclcpp/executors/multi_threaded_executor.hpp:25,
                 from /opt/ros/humble/include/rclcpp/rclcpp/executors.hpp:21,
                 from /opt/ros/humble/include/rclcpp/rclcpp/rclcpp.hpp:155,
                 from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/include/detected_object_validation/detected_object_filter/object
_lanelet_filter.hpp:20,
                 from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/src/object_lanelet_filter_node.cpp:15:
/usr/include/c++/11/bits/stl_vector.h: In instantiation of ‘std::_Vector_base<_Tp, _Alloc>::~_Vector_base() [with _Tp = lanelet::ConstLanelet; _Alloc = std::allocator<lanelet::ConstLanelet>]’:
/usr/include/c++/11/bits/stl_vector.h:683:7:   required from ‘std::vector<_Tp, _Alloc>::~vector() [with _Tp = lanelet::ConstLanelet; _Alloc = std::allocator<lanelet::ConstLanelet>]’
/home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/include/detected_object_validation/detected_object_filter/object_lanelet_filter.hpp:42
:7:   required from ‘void __gnu_cxx::new_allocator<_Tp>::destroy(_Up*) [with _Up = object_lanelet_filter::ObjectLaneletFilterNode; _Tp = object_lanelet_filter::ObjectLaneletFilterNode]’
/usr/include/c++/11/bits/alloc_traits.h:535:15:   required from ‘static void std::allocator_traits<std::allocator<_Tp1> >::destroy(std::allocator_traits<std::allocator<_Tp1> >::allocator_type&, _Up*) [with _Up =
 object_lanelet_filter::ObjectLaneletFilterNode; _Tp = object_lanelet_filter::ObjectLaneletFilterNode; std::allocator_traits<std::allocator<_Tp1> >::allocator_type = std::allocator<object_lanelet_filter::ObjectL
aneletFilterNode>]’
/usr/include/c++/11/bits/shared_ptr_base.h:528:35:   required from ‘void std::_Sp_counted_ptr_inplace<_Tp, _Alloc, _Lp>::_M_dispose() [with _Tp = object_lanelet_filter::ObjectLaneletFilterNode; _Alloc = std::all
ocator<object_lanelet_filter::ObjectLaneletFilterNode>; __gnu_cxx::_Lock_policy _Lp = __gnu_cxx::_S_atomic]’
/usr/include/c++/11/bits/shared_ptr_base.h:526:7:   required from here
/usr/include/c++/11/bits/stl_vector.h:336:49: error: invalid use of incomplete type ‘class lanelet::ConstLanelet’
  336 |                       _M_impl._M_end_of_storage - _M_impl._M_start);
      |                       ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
      |                       ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
In file included from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/include/detected_object_validation/detected_object_filter/object
_lanelet_filter.hpp:28,
                 from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/src/object_lanelet_filter_node.cpp:15:
/opt/ros/humble/include/lanelet2_core/Forward.h:110:7: note: forward declaration of ‘class lanelet::ConstLanelet’
  110 | class ConstLanelet;
      |       ^~~~~~~~~~~~
In file included from /usr/include/c++/11/bits/move.h:57,
                 from /usr/include/c++/11/bits/stl_pair.h:59,
                 from /usr/include/c++/11/bits/stl_algobase.h:64,
                 from /usr/include/c++/11/memory:63,
                 from /opt/ros/humble/include/rclcpp/rclcpp/rclcpp.hpp:153,
                 from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/include/detected_object_validation/detected_object_filter/object
_lanelet_filter.hpp:20,
                 from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/src/object_lanelet_filter_node.cpp:15:
/usr/include/c++/11/type_traits: In instantiation of ‘struct std::is_destructible<lanelet::ConstLanelet>’:
/usr/include/c++/11/bits/stl_construct.h:188:51:   required from ‘void std::_Destroy(_ForwardIterator, _ForwardIterator) [with _ForwardIterator = lanelet::ConstLanelet*]’
/usr/include/c++/11/bits/alloc_traits.h:848:15:   required from ‘void std::_Destroy(_ForwardIterator, _ForwardIterator, std::allocator<_T2>&) [with _ForwardIterator = lanelet::ConstLanelet*; _Tp = lanelet::Const
Lanelet]’
/usr/include/c++/11/bits/stl_vector.h:680:15:   required from ‘std::vector<_Tp, _Alloc>::~vector() [with _Tp = lanelet::ConstLanelet; _Alloc = std::allocator<lanelet::ConstLanelet>]’
/home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/include/detected_object_validation/detected_object_filter/object_lanelet_filter.hpp:42
:7:   required from ‘void __gnu_cxx::new_allocator<_Tp>::destroy(_Up*) [with _Up = object_lanelet_filter::ObjectLaneletFilterNode; _Tp = object_lanelet_filter::ObjectLaneletFilterNode]’
/usr/include/c++/11/bits/alloc_traits.h:535:15:   required from ‘static void std::allocator_traits<std::allocator<_Tp1> >::destroy(std::allocator_traits<std::allocator<_Tp1> >::allocator_type&, _Up*) [with _Up =
 object_lanelet_filter::ObjectLaneletFilterNode; _Tp = object_lanelet_filter::ObjectLaneletFilterNode; std::allocator_traits<std::allocator<_Tp1> >::allocator_type = std::allocator<object_lanelet_filter::ObjectL
aneletFilterNode>]’
/usr/include/c++/11/bits/shared_ptr_base.h:528:35:   required from ‘void std::_Sp_counted_ptr_inplace<_Tp, _Alloc, _Lp>::_M_dispose() [with _Tp = object_lanelet_filter::ObjectLaneletFilterNode; _Alloc = std::all
ocator<object_lanelet_filter::ObjectLaneletFilterNode>; __gnu_cxx::_Lock_policy _Lp = __gnu_cxx::_S_atomic]’
/usr/include/c++/11/bits/shared_ptr_base.h:526:7:   required from here
/usr/include/c++/11/bits/stl_vector.h:336:49: error: invalid use of incomplete type ‘class lanelet::ConstLanelet’
  336 |                       _M_impl._M_end_of_storage - _M_impl._M_start);
      |                       ~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~
In file included from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/include/detected_object_validation/detected_object_filter/object
_lanelet_filter.hpp:28,
                 from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/src/object_lanelet_filter_node.cpp:15:
/opt/ros/humble/include/lanelet2_core/Forward.h:110:7: note: forward declaration of ‘class lanelet::ConstLanelet’
  110 | class ConstLanelet;
      |       ^~~~~~~~~~~~
In file included from /usr/include/c++/11/bits/move.h:57,
                 from /usr/include/c++/11/bits/stl_pair.h:59,
                 from /usr/include/c++/11/bits/stl_algobase.h:64,
                 from /usr/include/c++/11/memory:63,
                 from /opt/ros/humble/include/rclcpp/rclcpp/rclcpp.hpp:153,
                 from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/include/detected_object_validation/detected_object_filter/object
_lanelet_filter.hpp:20,
                 from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/src/object_lanelet_filter_node.cpp:15:
/usr/include/c++/11/type_traits: In instantiation of ‘struct std::is_destructible<lanelet::ConstLanelet>’:
/usr/include/c++/11/bits/stl_construct.h:188:51:   required from ‘void std::_Destroy(_ForwardIterator, _ForwardIterator) [with _ForwardIterator = lanelet::ConstLanelet*]’
/usr/include/c++/11/bits/alloc_traits.h:848:15:   required from ‘void std::_Destroy(_ForwardIterator, _ForwardIterator, std::allocator<_T2>&) [with _ForwardIterator = lanelet::ConstLanelet*; _Tp = lanelet::Const
Lanelet]’
/usr/include/c++/11/bits/stl_vector.h:680:15:   required from ‘std::vector<_Tp, _Alloc>::~vector() [with _Tp = lanelet::ConstLanelet; _Alloc = std::allocator<lanelet::ConstLanelet>]’
/home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/include/detected_object_validation/detected_object_filter/object_lanelet_filter.hpp:42
:7:   required from ‘void __gnu_cxx::new_allocator<_Tp>::destroy(_Up*) [with _Up = object_lanelet_filter::ObjectLaneletFilterNode; _Tp = object_lanelet_filter::ObjectLaneletFilterNode]’
/usr/include/c++/11/bits/alloc_traits.h:535:15:   required from ‘static void std::allocator_traits<std::allocator<_Tp1> >::destroy(std::allocator_traits<std::allocator<_Tp1> >::allocator_type&, _Up*) [with _Up =
 object_lanelet_filter::ObjectLaneletFilterNode; _Tp = object_lanelet_filter::ObjectLaneletFilterNode; std::allocator_traits<std::allocator<_Tp1> >::allocator_type = std::allocator<object_lanelet_filter::ObjectL
aneletFilterNode>]’
/usr/include/c++/11/bits/shared_ptr_base.h:528:35:   required from ‘void std::_Sp_counted_ptr_inplace<_Tp, _Alloc, _Lp>::_M_dispose() [with _Tp = object_lanelet_filter::ObjectLaneletFilterNode; _Alloc = std::all
ocator<object_lanelet_filter::ObjectLaneletFilterNode>; __gnu_cxx::_Lock_policy _Lp = __gnu_cxx::_S_atomic]’
/usr/include/c++/11/bits/shared_ptr_base.h:526:7:   required from here
/usr/include/c++/11/type_traits:885:52: error: static assertion failed: template argument must be a complete class or an unbounded array
  885 |       static_assert(std::__is_complete_or_unbounded(__type_identity<_Tp>{}),
      |                     ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~^~~~~~~~~~~~~~~~~~~~~~~~
/usr/include/c++/11/type_traits:885:52: note: ‘std::__is_complete_or_unbounded<std::__type_identity<lanelet::ConstLanelet> >((std::__type_identity<lanelet::ConstLanelet>{}, std::__type_identity<lanelet::ConstLan
elet>()))’ evaluates to false
In file included from /usr/include/c++/11/memory:65,
                 from /opt/ros/humble/include/rclcpp/rclcpp/rclcpp.hpp:153,
                 from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/include/detected_object_validation/detected_object_filter/object
_lanelet_filter.hpp:20,
                 from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/src/object_lanelet_filter_node.cpp:15:
/usr/include/c++/11/bits/stl_construct.h: In instantiation of ‘void std::_Destroy(_ForwardIterator, _ForwardIterator) [with _ForwardIterator = lanelet::ConstLanelet*]’:
/usr/include/c++/11/bits/alloc_traits.h:848:15:   required from ‘void std::_Destroy(_ForwardIterator, _ForwardIterator, std::allocator<_T2>&) [with _ForwardIterator = lanelet::ConstLanelet*; _Tp = lanelet::Const
Lanelet]’
/usr/include/c++/11/bits/stl_vector.h:680:15:   required from ‘std::vector<_Tp, _Alloc>::~vector() [with _Tp = lanelet::ConstLanelet; _Alloc = std::allocator<lanelet::ConstLanelet>]’
/home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/include/detected_object_validation/detected_object_filter/object_lanelet_filter.hpp:42
:7:   required from ‘void __gnu_cxx::new_allocator<_Tp>::destroy(_Up*) [with _Up = object_lanelet_filter::ObjectLaneletFilterNode; _Tp = object_lanelet_filter::ObjectLaneletFilterNode]’
/usr/include/c++/11/bits/alloc_traits.h:535:15:   required from ‘static void std::allocator_traits<std::allocator<_Tp1> >::destroy(std::allocator_traits<std::allocator<_Tp1> >::allocator_type&, _Up*) [with _Up =
 object_lanelet_filter::ObjectLaneletFilterNode; _Tp = object_lanelet_filter::ObjectLaneletFilterNode; std::allocator_traits<std::allocator<_Tp1> >::allocator_type = std::allocator<object_lanelet_filter::ObjectL
aneletFilterNode>]’
/usr/include/c++/11/bits/shared_ptr_base.h:528:35:   required from ‘void std::_Sp_counted_ptr_inplace<_Tp, _Alloc, _Lp>::_M_dispose() [with _Tp = object_lanelet_filter::ObjectLaneletFilterNode; _Alloc = std::all
ocator<object_lanelet_filter::ObjectLaneletFilterNode>; __gnu_cxx::_Lock_policy _Lp = __gnu_cxx::_S_atomic]’
/usr/include/c++/11/bits/shared_ptr_base.h:526:7:   required from here
/usr/include/c++/11/bits/stl_construct.h:188:51: error: static assertion failed: value type is destructible
  188 |       static_assert(is_destructible<_Value_type>::value,
      |                                                   ^~~~~
/usr/include/c++/11/bits/stl_construct.h:188:51: note: ‘std::integral_constant<bool, false>::value’ evaluates to false
/usr/include/c++/11/bits/stl_construct.h:195:25: error: invalid use of incomplete type ‘std::iterator_traits<lanelet::ConstLanelet*>::value_type’ {aka ‘class lanelet::ConstLanelet’}
  195 |       std::_Destroy_aux<__has_trivial_destructor(_Value_type)>::
      |                                                   ^~~~~
/usr/include/c++/11/bits/stl_construct.h:188:51: note: ‘std::integral_constant<bool, false>::value’ evaluates to false
/usr/include/c++/11/bits/stl_construct.h:195:25: error: invalid use of incomplete type ‘std::iterator_traits<lanelet::ConstLanelet*>::value_type’ {aka ‘class lanelet::ConstLanelet’}
  195 |       std::_Destroy_aux<__has_trivial_destructor(_Value_type)>::
      |                         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/include/detected_object_validation/detected_object_filter/object
_lanelet_filter.hpp:28,
                 from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/src/object_lanelet_filter_node.cpp:15:
/opt/ros/humble/include/lanelet2_core/Forward.h:110:7: note: forward declaration of ‘std::iterator_traits<lanelet::ConstLanelet*>::value_type’ {aka ‘class lanelet::ConstLanelet’}
  110 | class ConstLanelet;
      |       ^~~~~~~~~~~~
In file included from /usr/include/x86_64-linux-gnu/c++/11/bits/c++allocator.h:33,
                 from /usr/include/c++/11/bits/allocator.h:46,
                 from /usr/include/c++/11/memory:64,
                 from /opt/ros/humble/include/rclcpp/rclcpp/rclcpp.hpp:153,
                 from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/include/detected_object_validation/detected_object_filter/object
_lanelet_filter.hpp:20,
                 from /home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/src/object_lanelet_filter_node.cpp:15:
/usr/include/c++/11/ext/new_allocator.h: In instantiation of ‘void __gnu_cxx::new_allocator<_Tp>::deallocate(_Tp*, __gnu_cxx::new_allocator<_Tp>::size_type) [with _Tp = lanelet::ConstLanelet; __gnu_cxx::new_allo
cator<_Tp>::size_type = long unsigned int]’:
/usr/include/c++/11/bits/alloc_traits.h:496:23:   required from ‘static void std::allocator_traits<std::allocator<_Tp1> >::deallocate(std::allocator_traits<std::allocator<_Tp1> >::allocator_type&, std::allocator
_traits<std::allocator<_Tp1> >::pointer, std::allocator_traits<std::allocator<_Tp1> >::size_type) [with _Tp = lanelet::ConstLanelet; std::allocator_traits<std::allocator<_Tp1> >::allocator_type = std::allocator<
lanelet::ConstLanelet>; std::allocator_traits<std::allocator<_Tp1> >::pointer = lanelet::ConstLanelet*; std::allocator_traits<std::allocator<_Tp1> >::size_type = long unsigned int]’
/usr/include/c++/11/bits/stl_vector.h:354:19:   required from ‘void std::_Vector_base<_Tp, _Alloc>::_M_deallocate(std::_Vector_base<_Tp, _Alloc>::pointer, std::size_t) [with _Tp = lanelet::ConstLanelet; _Alloc =
 std::allocator<lanelet::ConstLanelet>; std::_Vector_base<_Tp, _Alloc>::pointer = lanelet::ConstLanelet*; std::size_t = long unsigned int]’
/usr/include/c++/11/bits/stl_vector.h:335:2:   required from ‘std::_Vector_base<_Tp, _Alloc>::~_Vector_base() [with _Tp = lanelet::ConstLanelet; _Alloc = std::allocator<lanelet::ConstLanelet>]’
/usr/include/c++/11/bits/stl_vector.h:683:7:   required from ‘std::vector<_Tp, _Alloc>::~vector() [with _Tp = lanelet::ConstLanelet; _Alloc = std::allocator<lanelet::ConstLanelet>]’
/home/minoda/ghq/github.com/autowarefoundation/autoware/src/universe/autoware.universe/perception/detected_object_validation/include/detected_object_validation/detected_object_filter/object_lanelet_filter.hpp:42
:7:   required from ‘void __gnu_cxx::new_allocator<_Tp>::destroy(_Up*) [with _Up = object_lanelet_filter::ObjectLaneletFilterNode; _Tp = object_lanelet_filter::ObjectLaneletFilterNode]’
/usr/include/c++/11/bits/alloc_traits.h:535:15:   required from ‘static void std::allocator_traits<std::allocator<_Tp1> >::destroy(std::allocator_traits<std::allocator<_Tp1> >::allocator_type&, _Up*) [with _Up =
 object_lanelet_filter::ObjectLaneletFilterNode; _Tp = object_lanelet_filter::ObjectLaneletFilterNode; std::allocator_traits<std::allocator<_Tp1> >::allocator_type = std::allocator<object_lanelet_filter::ObjectL
aneletFilterNode>]’
/usr/include/c++/11/bits/shared_ptr_base.h:528:35:   required from ‘void std::_Sp_counted_ptr_inplace<_Tp, _Alloc, _Lp>::_M_dispose() [with _Tp = object_lanelet_filter::ObjectLaneletFilterNode; _Alloc = std::all
ocator<object_lanelet_filter::ObjectLaneletFilterNode>; __gnu_cxx::_Lock_policy _Lp = __gnu_cxx::_S_atomic]’
/usr/include/c++/11/bits/shared_ptr_base.h:526:7:   required from here
/usr/include/c++/11/ext/new_allocator.h:135:13: error: invalid application of ‘__alignof__’ to incomplete type ‘lanelet::ConstLanelet’
  135 |         if (alignof(_Tp) > __STDCPP_DEFAULT_NEW_ALIGNMENT__)
      |             ^~~~~~~~~~~~
/usr/include/c++/11/ext/new_allocator.h:139:37: error: invalid application of ‘sizeof’ to incomplete type ‘lanelet::ConstLanelet’
  139 |                               __t * sizeof(_Tp),
      |                                     ^~~~~~~~~~~
/usr/include/c++/11/ext/new_allocator.h:141:48: error: invalid application of ‘__alignof__’ to incomplete type ‘lanelet::ConstLanelet’
  141 |                               std::align_val_t(alignof(_Tp)));
      |                                                ^~~~~~~~~~~~
/usr/include/c++/11/ext/new_allocator.h:147:35: error: invalid application of ‘sizeof’ to incomplete type ‘lanelet::ConstLanelet’
  147 |                           , __t * sizeof(_Tp)
      |                                   ^~~~~~~~~~~
gmake[2]: *** [CMakeFiles/object_lanelet_filter_node.dir/build.make:76: CMakeFiles/object_lanelet_filter_node.dir/src/object_lanelet_filter_node.cpp.o] エラー 1
gmake[1]: *** [CMakeFiles/Makefile2:290: CMakeFiles/object_lanelet_filter_node.dir/all] エラー 2
gmake: *** [Makefile:146: all] エラー 2
---
Failed   <<< detected_object_validation [5.96s, exited with code 2]


Use fmuladd for fma and document this behavior

Fixes #112.
When it comes to performance, the performance in my updated stencil benchmark with avx2 enabled is the same. But when avx2 is disabled, the avx fallback is much faster (before this pull request, I saw some 10x performance reduction on AVX 1).
So there are no downsides to this change, only performance improvements.
Also added some documentation for crate users.
I didn't rename the extern "C" fns, only changed the link_name attribute.

So there are no downsides to this change,

So this isn't exactly accurate. The reason why, without this change the performance is worse, is IIUC because LLVM has to emulates the infinite precision of the fma instruction on the platforms that do not have it, which is expensive.
First, thank you for doing this, since I mainly test on an AVX1 machine and this is what I was seeing. I think we should do two things, and then reconsider later:

keep ::fma as is, guaranteeing precision - add some tests (e.g. to the ./test directory) that check this (I don't know for which triple of values lower precision is observable, but maybe we can find something).

add an fma-estimate method, e.g., ::fmae that uses fmuladd to produce an "estimate" of the infinite precision fma. On platforms that support it, it is exact, but on platforms that do not, it just does an a * b + c instead of trying to emulate the infinite precision.

finally: update the aobench and other benchmarks to use ::fmae.

I haven't added the tests for the existing fma because I don't know which numbers to use when testing either.

I've been fuzzing fma and a * b + c for a while and I do not manage to get them to produce different results on my machine :/

@gnzlbg Alright, the links aren't the most critical since I expect rustdoc to place these functions one next to another in the end.
I have removed the mention of fmsub from fma's documentation, because it didn't tell the full story anyway. x86 additionally has intrinsics for fmaddsub, masked fma, etc. LLVM will simply do its best to pick the right instruction, as long as the user calls fma.

Any reason for not choosing that name?

Oversight probably. Please open an issue about this. The floating-point methods are not in the initial round for stabilization so not much discussion has been going on about these.


Starting the triton server maxBatchSize is always 1, although max has been modified max_ batch_ size,  but not effective

Hi @PAOPAO6 You can set the max_batch_size in config.json in your building files, the priority of the max_batch_size value in config.json is greater than config.pbtxt.
{
  "builder_config": {
    "fp8": false,
    "hidden_act": "silu",
    "hidden_size": 4096,
    "int8": false,
    "max_batch_size": 64,
    "max_input_len": 2048,
    "max_num_tokens": null,
    "max_output_len": 512,

Hi @PAOPAO6 You can set the max_batch_size to a bigger value in config.json in your building engines files, the priority of the max_batch_size value in config.json is greater than config.pbtxt.
{
  "builder_config": {
    "fp8": false,
    "hidden_act": "silu",
    "hidden_size": 4096,
    "int8": false,
    "max_batch_size": 64,
    "max_input_len": 2048,
    "max_num_tokens": null,
    "max_output_len": 512,

think you for answer, I set it up as you said， error:

Hi @PAOPAO6 You can set the max_batch_size to a bigger value in config.json in your building engines files, the priority of the max_batch_size value in config.json is greater than config.pbtxt.
{
  "builder_config": {
    "fp8": false,
    "hidden_act": "silu",
    "hidden_size": 4096,
    "int8": false,
    "max_batch_size": 64,
    "max_input_len": 2048,
    "max_num_tokens": null,
    "max_output_len": 512,

think you for answer, I set it up as you said， error:

@PAOPAO6 Can I see your config.json configuration?
And you can call the endpoint to get result.
curl -X POST localhost:8000/v2/models/ensemble/generate -d '{"text_input": "What is machine learning?", "max_tokens": 20, "bad_words": "", "stop_words": ""}'

You should set larger max_batch_size when you build your engine.


502 Bad Gateway an all services

I just set up the same solution we are running on some other data centers without any issues.
However, all the services just return "Bad Gateway" in the browser.
This is a docker swarm network, and Traefik is running on the swarm manager.
We are running Traefik v2.0.4
Docker is running version 19.03.4
Traefik is launched through a stack with the following configuration:
version: '3.7'
volumes::
traefik:
image: traefik
command:
- "--api=true"
- "--api.insecure=true"
- "--api.dashboard=true"
- "--ping"
- "--providers.docker=true"
- "--providers.docker.endpoint=unix:///var/run/docker.sock"
- "--providers.docker.network=traefik-public"
- "--providers.docker.swarmMode=true"
- "--entrypoints.web.address=:80"
- "--accesslog=true"
- "--accesslog.bufferingsize=100"
- "--accesslog.filepath=/var/log/traefik.log"
- "--metrics.prometheus=true"
- "--entryPoints.metrics.address=:8082"
- "--metrics.prometheus.entryPoint=metrics"
- "--metrics.prometheus.buckets=0.1,0.3,1.2,5.0"
- "--tracing.jaeger=true"
- "--tracing.jaeger.samplingServerURL=http://localhost:5778/sampling"
- "--tracing.jaeger.samplingType=const"
- "--tracing.jaeger.samplingParam=1.0"
- "--tracing.jaeger.localAgentHostPort=<IP_ADDRESS>:6831"
- "--tracing.jaeger.propagation=jaeger"
- "--tracing.jaeger.traceContextHeaderName=uber-trace-id"
networks:
monitor-net:
traefik-public:
driver: overlay
external: true
And then a service is added through another stack with the following configuration. This is running on a docker node in the swarm:
version: '3.7'
services:
frontend:
image: enevodocker/enevoleadsfe:production
ports:
- 80
environment:
- SERVICE_PORTS=80
deploy:
labels:
- "traefik.http.routers.portalproxy.rule=Host(myportal.no)"
- "traefik.http.services.portalservice.loadbalancer.server.port=80"
- "traefik.docker.network=traefik-public"
replicas: 4
update_config:
parallelism: 2
delay: 10s
restart_policy:
condition: on-failure
max_attempts: 2
window: 60s
placement:
constraints: [node.role != manager]
networks:
- web
- traefik-public
labels:
- "traefik.docker.network=traefik-public"
When I inspect the traefik container, as well ad the frontend container, both are connected to the traefik-public networks.
Now, if I visit http://myportal.no it just returns "bad gateway".
I am now stuck in debugging this, and can't find anything to go further with.
I have tried deleting the network, adding it again, deleting the stacks and adding them again and so on.
Anyone with any further suggestions?

Hi! I'm Træfiker :robot: the bot in charge of communication regulation.
Thanks for your interest in Traefik!
We dedicate the issue tracker to bug reports and feature requests only. My advanced AI has spotted that your issue might be a configuration problem or relates to something that doesn't look like a bug.
To confirm this, please join our Community Forum and reach out to us on the Traefik section.
In case I'm wrong (well, that would be embarrassing :sweat_smile:), my developers will re-open the issue and fix me!
In the meantime, you can double check Traefik's documentation.


5.3.1 Issue: "Visual Studio config issue: {}"

Just updated to 5.3.1 from 5.3.0-beta.3 and hit a build issue.
Running "ts:src" (ts) task
Visual Studio config issue: {}
Warning: Task "ts:src" failed. Use --force to continue.

Aborted due to warnings.

My grunt ts:src task:
    ts: {
      src : {
        src: ["src/**/*.ts"],
        options: {
          fast: 'always',
          inlineSources: true,
          compiler: './node_modules/typescript/bin/tsc'
        }
      }
    }

I'm also getting this.  Config below (working in v5.3.0-beta3 and -beta4)
    ts: {
        options: {
            compiler: "./node_modules/typescript/bin/tsc",
            declaration: true,
            module: "commonjs",
            moduleResolution: "node",
            noImplicitAny: true,
            preserveConstEnums: true,
            removeComments: true,
            sourceMap: true,
            target: "es5"
        },
        all: {
            options: {
                fast: "never"
            },
            outDir: "./<%= config.tmp %>/compiled",
            src: [
                "*.ts",
                "./!(<%= ignorePaths %>)/**/*.ts",
                "./<%= config.test %>/**/*.ts"
            ]
        },
        src: {
            options: {
                rootDir: "./"
            },
            src: [
                "*.ts",
                "./!(<%= ignorePaths %>)/**/*.ts"
            ]
        }
    }

Thanks for the report.  I will take a look asap.  If it was working in 5.3.0-beta.3, please revert to that version in the meantime.
Just to confirm - neither of you are using the Visual Studio integration?  (Does not appear so bases on your gruntfiles).
Thanks.

Interesting that your targets are both named src...

Nope, no Visual Studio integration on my end.

This should be fixed in v5.3.2.  The issue was specifically with targets named src.
Thank you for the report!  You're in the patch notes.  If there is still a problem, please comment or re-open.

Fame at last.
In answer to your question, no I'm not using Visual Studio - I use WebStorm.  v5.3.2 has fixed the issue.  Thanks

I am still seeing this issue with v5.4

Did you rerun npm install after editing your package.json? Did 5.3.2 fix it and 5.4 was a regression? Thanks.

I've seen this from v5.3.0 to v5.4.0. I created #353 describing that.


made responsive

Thanks for your valuable contribution.
Don't forget to star the repo.

Thanks for the merged.... pleasure to contribute in yours repo...
On Wed, 4 Oct 2023, 22:17 Kritika Gupta, @.***> wrote:

Thanks for your valuable contribution.
Don't forget to star the repo.
—
Reply to this email directly, view it on GitHub
https://github.com/Kritika30032002/To-Do-List-Application/pull/77#issuecomment-1747282026,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AZOBOAVL7Y2ILR2CWABB6ZDX5WHLPAVCNFSM6AAAAAA5S5UNTWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONBXGI4DEMBSGY
.
You are receiving this because you authored the thread.Message ID:
@.***>


Glacier Update

Glacier Update
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Summary
A pretty major update to Glacier that modernises the map, adding new features, removing old and generally beautifying the map as a whole.
Major changes include a total rework for Perma, visual updates for outdoor and indoor areas, removal of the static arrivals shuttle, addition of solar arrays, fixes for a number of issues, conversion of cargo to use the teleports and generally darker more interesting maints. Full change below.
Additional Images
New Perma

New sec outpost in arrivals

Changelog

Swapped surgery scrubber/vent so distro will chug a bit less miasma
Added vent and scrubber to the chef's fridge
Re-coloured all atmos pipes to fit standards
Fixed botany/kitchen chute break
Fixed Salv/cargo chute break
Renamed and marked the kitchen/botany chute so chefs might stop sending their empty flower bags to the botanists and botanists will stop sending their empty robust harvest to the chefs
Added a proper disposal chute to botany. Had to move some stuff around to do so
Added decals and button-linked windoors to Hop queue. Make a neat line or you don't get AA
Added more windows to open up sight lines and make corridors a bit more interesting
Added a lot more rocky walls in the station. I liked that the original station was built into the rocks and wanted to use that motif a bit more to make the hallways more interesting
Also in the interest of making the hallways around Hop more detailed, botany now has a market stall-style desk. But to mini fan or not to mini fan? That is the question
Changed some windows in unrestricted spaces to be non-reinforced and changed others in restricted areas to be reinforced, but generally reduced the number of reinforced windows in public spaces. Having reinforced windows on everything makes the map feel a bit restrictive and Glacier is one of the few maps that can get off with having more regular windows, so it seems a shame to use mostly reinforced
Made some visual changes to sec
Added more visual scatter in maints
Added more loot to maints
Removed/disconnected a number of lights from maints
Added more flashlights to maints
Added some small veins of mineable rock to give salv a bit more to do if they feel the need
Added a single cell charger to medical
Added two defibs to med. One in trama and one in surgery
Reworked outdoor pathways to look more like outdoor paving covered in snow. Not sure how I feel about this one as I liked the old tiles with the dark filter over them, but I wanted a more pronounced difference between indoors and outdoors
Added a lot more foliage to the outdoor areas, again, just to make them seem more outdoors
Chef starts with a few more ingredients. Iv noticed that as a chef on Glacier, you are often without a botanist so this might help a bit to get some starting food done before you start growing your own stuff
Changed the heads starting donuts to more accurately match their colours. This is very important
Added the smallest, shittiest solar arrays you have ever seen. They are basically useless for powering the station, but it is nice to be able to show new players how to set up the solar arrays
Because the solars are a thing now, the CE loses his personal solar PC but gains a wardrobe with some drip
Added some misc items on the outside of the station for salvs to find while they mine the new ore veins
Added a few of the guidebooks for starter or recipe-heavy jobs
Improved signage mostly in terms of evac directions
Added some more detail to the court and changed lockup so prisoners can better see the court while imprisoned. Makes space court a bit more engaging for criminals, even if sec doesn't let them out to testify
Added desk bells so that the clown can steal them and drive Hop to insanity
Mail carriers get their vending machine
Added the matter reclaimer to disposals and its board to the lockup. Not sure if it good idea to put it there
Swabs box added to viro and gave them the virodrobe
The old static arrivals shuttle is gone in preparation for the real arrivals shuttle. RIP bozo.
Moved the security outpost a bit over so that it acts as a sort of “Papers Please” checkpoint if sec feels like RPing
Added a small clothing kiosk just after the arrivals checkpoint so that newly arrived players can get a jacket in a more natural way. Also lets players man the till and make their own shop
Perma reworked completely. Made larger and kitted out with more stuff for prisoners to work with. It's still a shithole but it can't be made much larger without seriously reworking the surrounding areas. Armory shifted around to make space for perma
Cargo retrofit to use teleports
Removed shutters from Hop and similar where they overlap with windows a this no longer works

Test failure on this PR is valid. Open the map in your editor of choice and delete any lines containing - invalid

Ill take a look, thanks

pain

System.TimeoutException : Event took too long to trigger

This is actually better than what we had. Now we're back to the old days of tests failing because GitHub just took too long. For future reference, if Debug/Release passes on one operating system but fails on the other, there's a good chance that everything will pan out after one re-run of tests. I'll queue it up now.

Thanks a mill. Sorry for the hassle

YEEEESSS. Thanks again

All tests passing. It's a beautiful thing.
@OldDanceJacket Would you like to officially review this?

Alright after reviewing this it seems to be all in-line with what was talked about before, best thing to do is let it rip and see if the players can find any missing wires. ;D


MWPW-144603 - Update path in helix query for sitemap

Update /promo/ path /partnerpromo/ in helix query.

Resolves: MWPW-144603
Test URLs:

Before: https://main--cc--adobecom.hlx.live/?martech=off
After: https://partnerpromo--cc--adobecom.hlx.live/?martech=off

Unit tests are failing but it's not related to this PR. There are some issue in starting the browser hence the issue. As this PR is urgent for Tuesday hence merging it for now.


Docker fails to run as base:core22 apparmor_parser denial

+ sudo docker run --rm hello-world
docker: Error response from daemon: AppArmor enabled on system but the docker-default profile could not be loaded: running `/usr/sbin/apparmor_parser apparmor_parser --version` failed with output: Failed to load policy-features from '/etc/apparmor.d/abi/kernel-[5](https://github.com/docker-snap/docker-snap/actions/runs/4409275831/jobs/7725502411#step:10:6).4-outoftree-network': Permission denied

Blocks upgrade to core22 as seen in https://github.com/docker-snap/docker-snap/pull/93

https://github.com/snapcore/snapd/pull/12644


Add 1.15 upgrade survey

@therealmitchconnors: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.15
816e76e8e2b67d93de7411f7469a04cd7cb3bae2
link
true
/test release-notes

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

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.15
816e76e8e2b67d93de7411f7469a04cd7cb3bae2
link
true
/test release-notes

lint_istio_release-1.15
816e76e8e2b67d93de7411f7469a04cd7cb3bae2
link
true
/test lint

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

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

release-notes_istio_release-1.15
816e76e8e2b67d93de7411f7469a04cd7cb3bae2
link
true
/test release-notes

lint_istio_release-1.15
816e76e8e2b67d93de7411f7469a04cd7cb3bae2
link
true
/test lint

gencheck_istio_release-1.15
816e76e8e2b67d93de7411f7469a04cd7cb3bae2
link
true
/test gencheck

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

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

lint_istio_release-1.15
816e76e8e2b67d93de7411f7469a04cd7cb3bae2
link
true
/test lint

gencheck_istio_release-1.15
816e76e8e2b67d93de7411f7469a04cd7cb3bae2
link
true
/test gencheck

release-notes_istio_release-1.15
2775e7522b0bd77eca03ed880642ada8a1373133
link
true
/test release-notes

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

/retest

@therealmitchconnors: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio_release-1.15
20b06bff1ce8e36e8c04da3ab5a1ed619c2d5bca
link
true
/test integ-pilot-istiodremote-mc

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

@therealmitchconnors: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio_release-1.15
20b06bff1ce8e36e8c04da3ab5a1ed619c2d5bca
link
true
/test integ-pilot-istiodremote-mc

unit-tests-arm64_istio_release-1.15
20b06bff1ce8e36e8c04da3ab5a1ed619c2d5bca
link
true
/test unit-tests-arm64

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

/retest


Allow relative EmitterPackageJsonPath in New-EmitterPackageLock.ps1

The following pipelines have been queued for testing:java - templatejava - template - testsjs - templatenet - templatenet - template - testspython - templatepython - template - tests You can sign off on the approval gate to test the release stage of each pipeline. See eng/common workflow


TP2000-857  Implement geo area create journey

TP2000-857  Implement geo area create journey
Why
Now that the ‘Edit Geographical area’ journey has been implemented, we should complete the final journey, ‘Create a new geographical area’, which will allow users to create their own geographical areas without the need to involve data engineers.
What

Adds GeoAreaCreate view and GeographicalAreaCreateForm, enabling users to create new geo areas
Adds GeographicalMembershipCreate view and GeographicalMembershipBaseFormSet, enabling users to create multiple new memberships for a geo area (TP2000-858)
Adds 'create a new geo area' link to workbasket menu
Adds 'create a new membership' link to memberships tab of a geo area
Adds view and form unit tests

Codecov Report
Patch coverage: 93.61% and project coverage change: +0.02 :tada:

Comparison is base (5535540) 92.42% compared to head (ffdf580) 92.44%.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #893      +/-   ##
==========================================
+ Coverage   92.42%   92.44%   +0.02%
==========================================
  Files         413      413
  Lines       28362    28670     +308
  Branches     2161     2182      +21
==========================================
+ Hits        26213    26505     +292
- Misses       1743     1753      +10
- Partials      406      412       +6

Impacted Files
Coverage Δ

geo_areas/validators.py
80.00% <80.00%> (+10.00%)
:arrow_up:

geo_areas/views.py
94.18% <83.87%> (-5.82%)
:arrow_down:

geo_areas/forms.py
95.20% <93.02%> (-1.73%)
:arrow_down:

geo_areas/tests/test_forms.py
100.00% <100.00%> (ø)

geo_areas/tests/test_views.py
98.87% <100.00%> (+0.28%)
:arrow_up:

geo_areas/urls.py
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes

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


add filter-event Shopware_Controllers_Frontend_Account_Login_Redirect

1. Why is this change necessary?
Give us the possibility to manipulate the redirection after successfull Login
2. What does this change do, exactly?
add an filter-event Shopware_Controllers_Frontend_Account_Login_Redirect
3. Describe each step to reproduce the issue or behaviour.
4. Please link to the relevant issues (if any).
5. Which documentation changes (if any) need to be made because of this PR?
6. Checklist

[ ] I have written tests and verified that they fail without my change
[x] I have squashed any insignificant commits
[x] This change has comments for package types, values, functions, and non-obvious lines of code
[x] I have read the contribution requirements and fulfil them.

You can not do that with a postdispatch event?

Hey @tinect,
Is there any benefit with this new event instead using of using PostDispatch event?

using this event I don't need to check the state of login and errors again. I just can start at the place I want.

Since the overhead in the PostDispatch is small and for consistency reasons, we think this event is not necessary. Thank you anyway for your Contribution


STREAMS-314 | Timing out regular expressions that cause catastrophic backtracking

:+1:

I've got a revision to this PR I need to make before it's ready to merge.

@robdouglas Hey, do you have this change still? Can't tell what's going on with the issue/branch.


Requirements review for SAP JCo Connector

Description:
$subject
Need to finalize,

Functionalities to be supported for common use case
High level architecture

Find the initial design document based on above research  - https://docs.google.com/document/d/1eGjCVTjV77XvaSey4vh-7XLGVh_KWWBYqTjItFyGsnk/edit
Base module build structure - https://github.com/niveathika/module-ballerinax-sap.jco

Closing this issue as implementation to be tracked in separate issue.


Conflict between /apps/v1 and apps/v1beta1

When creating custom controller, i get the following error:
https://play.golang.org/p/qYc_VSGtfFl
612 reflector.go:205]........Failed to list *v1.Deployment: the server could not find the requested resource
But when i change line 78 from
watch(clientSet.AppsV1().RESTClient(), new(apps_v1.Deployment), "deployments")
to
watch(clientSet.AppsV1beta1().RESTClient(), new(apps_v1.Deployment), "deployments")
it seems to work fine.
https://play.golang.org/p/0O3DN4Tyea7
Am i missing something, or maybe mismatch of clientset object?

what version server are you running against? deployments in the apps/v1 API group only exist in 1.9 and newer

I am running it in gke cluster. Here is the info:
kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.7", GitCommit:"dd5e1a2978fd0b97d9b78e1564398aeea7e7fe92", GitTreeState:"clean", BuildDate:"2018-04-19T00:05:56Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"8+", GitVersion:"v1.8.8-gke.0", GitCommit:"6e5b33a290a99c067003632e0fd6be0ead48b233", GitTreeState:"clean", BuildDate:"2
018-02-16T18:26:58Z", GoVersion:"go1.8.3b4", Compiler:"gc", Platform:"linux/amd64"}
it seems it is 1.8. I guess it will be safe to use /apps/v1beta1.
Thanks for pointing this out.

it seems it is 1.8. I guess it will be safe to use /apps/v1beta1.
Thanks for pointing this out.

sure
/close


Support subtypes of basic types when encoding

The current implementation of TomlEncoder doesn't support subtypes of the supported basic types. For example:
from enum import StrEnum
import toml

class ValidStrings(StrEnum):
    FOO = "foo"

assert isinstance(ValidStrings.FOO, str) # OK
data = {"foo": ValidStrings.FOO}
print(toml.dumps(data))

Output:
foo = [ "f", "o", "o",]

This pull request changes the implementation to use isinstance instead of get(type(...)) to play nice with inheritence.
Fixes #418

Thank you for the pull request!

Looks like this introduces a syntax error:
pip install -e .
Obtaining .../toml
  Preparing metadata (setup.py) ... error
  error: subprocess-exited-with-error

  × python setup.py egg_info did not run successfully.
  │ exit code: 1
  ╰─> [11 lines of output]
      Traceback (most recent call last):
        File "<string>", line 2, in <module>
        File "<pip-setuptools-caller>", line 34, in <module>
        File ".../toml/setup.py", line 6, in <module>
          import toml
        File ".../toml/__init__.py", line 6, in <module>
          from toml import encoder
        File ".../toml/encoder.py", line 176
          dump_fn = next(f for t, f in self.dump_funcs.items() if isinstance(v, t), None)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
      SyntaxError: Generator expression must be parenthesized
      [end of output]


Add more reactive inspired functionality on Stream (and maybe Iterable)

Currently the simplest way to perform custom transformations of streams is to use the transform method.
someStream.transform(debounce(sec)).map(...).transform(switchLatest(...))

This is long and awkward compared to having the methods on the stream itself:
someStream.debounce(sec).map(...).switchLatest(...)

We should add more Rx inspired operations.

Those methods would allow for late binding, of course, but if they only have a single implementation (they can still call methods on the Stream using late binding) then we could also express the transformations as functions without loss of expressive power:
switchLatest(map(debounce(someStream, sec), ...), ...)

and of course they could then be called using a BETA style "pipeline" syntax if we add something like the '->' that you've proposed:
someStream -> debounce(sec) -> map(...) -> switchLatest(...)

Would definitely be nice if it were 'native' Dart.
Meanwhile you might want to have a look at https://github.com/ReactiveX/rxdart.

In C#, the reactive functionality is added through extension methods (for example, C# Skip. This works really well. They've added extension methods for just about everything without cluttering their version of the Iterable type.


Guarding against clojure.core/any?

Guarding against any?, which is part of clojure.core in 1.9.

Sorry this took so long. Busy, but also depressed about the existence of core.any?

No problem. Thank you.


Initial Pre-Commit CI

Configures the pre-commit tool to automatically format the repository code in a consistent, PEP-compliant, manner.

@kchason - did this start from the most recent develop state?  I'm surprised there are conflicts if so.

Can this please be distilled to running black with pre-commit?  There are other issues that are confusing the question of whether we incorporate pre-commit at all, such as Turtle whitespace normalization butting heads between pre-commit and rdf-toolkit.jar.


Monitor CPU/event loop saturation.

Let's monitor how much a new event must wait before the event loop starts to process it. E.g. if there is a 5-seconds long CPU processing, other requests on that isolate are being stalled.
I've done this on both node.js and Dart, but need to extract and open-source the related code from the rest of that stack.

I've did a fresh analysis with periodic timers (on my Macbook):

Timer.periodic(Duration.zero) will get the CPU spinning at 100%, with 500k callbacks per second (2 microseconds each)
Duration(milliseconds: 1) will get the CPU at 10.5%
Duration(milliseconds: 5) will get the CPU at 4.5%
Duration(milliseconds: 10) will get the CPU at 2.5%
Duration(milliseconds: 100) will get the CPU at 0.28%
Duration(milliseconds: 1000) will get the CPU at 0.03%

I'll redo the #1303 a bit based on the numbers.


Client crash while pondering

Minecraft Version
1.20.1
Describe the Bug
While pondering the client crashes
Reproduction Steps
Select disenchanter and ponder
Expected Result
Not crashing
Screenshots and Videos
No response
Crash Report or Log
https://gist.github.com/VillainVibe/89f8039905ed81a86c2f4e9a75f9d6df
Other Mods
They are in the crash log
Mod Version
1.2.9.c
Forge Version
Neoforge - 1.20.1-47.1.104

This is a conflict with CIT Resewn (or rather, the Forge port of it that you're using).

Okay, thank you for the info.


perlin-network/noise #Go

Add perlin-network/noise // Go P2P library.

Looks good, thanks for sharing!


suggestion: vue ts example with single file component

Would be nice to have vue single file component project, with typescript, less, sass, vue-class-component example provided.

Hi @Jack85 everything you mentioned there (apart from vue-class-component) is in the vue-seed. It would be a great help if you can create a PR to add in the vue-class-component side of things.

Unfortunately not quite, you are using babel there (not like
  |  -->
  |

styles not loaded with less plugin when importing like so


Numba distance module

Reference Issues/PRs

#1538 #1547
What does this implement/fix? Explain your changes.

This pr takes all the current distance metrics in sktime and converts them to numba. The distances can be used in the exact same way they were before (params are consistent). Furthermore, a multitude of bugs/errors were found and fixed.
In addition there are 3 new features that come along with this. The first is pairwise distance. This allows you to perform a distance computation across a dataset of timeseries or between two timeseries with massive performance gains.
The second (a much demanded request) both distance and pairwise distance now support 1d and 2d arrays.
The third new feature is the ability to create a numba compiled function for your specific use case via a factory method. This then allows you to embed your created function directly into another numba function  (you can't call non numba compiled functions from inside another numba meaning you have to exit effectivly removing any potential performance gains). This will allow for many other modules to more easily be converted to numba (i.e. classification and clustering) and find massive performance gains.
Finally there were no docstrings or tests for the previous distances and this pr adds a huge amount of testing and validation and well as docstrings to everything.
There is also custom logic to create LowerBounding matrices compatiable with the module.
Does your contribution introduce a new dependency? If yes, which one?

No
What should a reviewer concentrate their feedback on?

There is a lot stuff here (sorry). Normally i'd split this up but the intention of the pr was to swap the old distances out all at the same time and so we never have to touch cython again. Most of the 'new' stuff is really docstrings and tests that the previous distances were severily lacking (there were no docstrings or tests at all).
When looking at the code there are going to be a couple of things that will appear a 'weird' way of doing something. 90% of the time it's will have something to do with working around a restriction with numba so please ask about anything you see.
Any other comments?

PR checklist

For all contributions

[x] I've added myself to the list of contributors.
[ ] Optionally, I've updated sktime's CODEOWNERS to receive notifications about future changes to these files.
[x] I've added unit tests and made sure they pass locally.

For new estimators

[x] I've added the estimator to the online documentation.
[x] I've updated the existing example notebooks or provided a new one to showcase how my estimator works.

I forgot to add there are 3 more distances coming Ill finish them tomorrow.

As an addition because someone is going to bring up the location of it being in sktime/dist-kernels/numba/distance/... I put it in here just because @fkiraly suggested it would be a good location, but we need to have a discussion about the 'dist-kernels' name and just renaming this whole directory to 'distances' now we're replacing the cython stuff. But ill let you disucss I have no preference.

also we are using github IDs not full names author = ["Chris Holder"]

update CODEOWNERS

I think these should all be accessed via an init rather than directly?

this test failing is something we see all the time when refactoring, I'm not sure if its a bug or not, maybe we should raise an issue? @MatthewMiddlehurst has the same on the distance_based  refactor.

thats a strange error!

great, simple use case of full DTW seems to work fine, I will run it through the lot later to compare to cython and tsml. Questions to address prior to approval are

setting parameters (how do you do it and is it equivalent)
tuning parameters in the way done in knn (is it still fast)

I think we will get this lot in then raise an issues for MSM, KNN and PF.

The results I know will differ from the previous knn are for:
ddtw - changed the derivative algorithm to match the original papers implementation
wdtw - this I may have implemented wrong but I know it gives a different answer
wddtw - as derivative algorithm changed will give different (and depending on if wdtw is correct
edr - this is new (I accidently implemented this one as I missread erp 😂. erp is also implemented as well)

I'm going to merge this to unlock the CI/CD refactor, I assume it's "done" and there are no objections?

hi @fkiraly there is still work in progress, but it can go in and we can refine in a new PR

lol, ok then, 2 mins to answer!

whoops, sorry - I thought this was done (according to statements of @chrisholder).
I thought worst case we can unmerge, but if you're fine to have increments in another PR, I would prefer that too since the "big chunk of work" is now in.

Yes it all good, just a bit surprising :)


New item statuses

Next steps:

Adapt scripts as well (see https://github.com/leih-lokal/scripts/issues/22)
Deploy (when at present at leih.lokal next time, so I can update the laptops and immediately react to potential complications)

Closes #518.

@ColofoniusRegenschein Please have a quick look and check if you think the changes look good (as far as you can follow along without being very much involved with the code). Same for https://github.com/leih-lokal/scripts/pull/23.


Enable to parse more backend_kwargs when opening via PydapDataStore (e.g. output_grid)

Is your feature request related to a problem?
I am planning to use xarray to access netcdf data from a thredds server. For my particular application, I need to be able to set pydap client option output_grid=False, to avoid some issues that I have experienced with a particular dataset on the server I am downloading from.
I use xarray.open_dataset to access the data via pydap backend, which currently only allows to specify "session" as a keyword in backend_kwargs.
https://github.com/pydata/xarray/blob/8c5c230881d616af32c5a42cca261eb11fce3916/xarray/backends/pydap_.py#L89
It would be helpful to be able to provide additional backend_kwargs accepted by the pydap client (such as output_grid).
https://github.com/pydap/pydap/blob/dbe9b8d15831f21c28b97ed5661b2708faec45f2/src/pydap/client.py#L58
Describe the solution you'd like
It could be perhaps as simple as extending the signature of PydapDataStore.open from:
@classmethod
def open(cls, url, session=None):

    ds = pydap.client.open_url(url, session=session)
    return cls(ds)

to, e.g.:
@classmethod
def open(cls, url, **kwargs):

    ds = pydap.client.open_url(url, **kwargs)
    return cls(ds)

Describe alternatives you've considered
No response
Additional context
No response

That sounds reasonable - are you up to create a PR?

Yes, I can create a PR. Thanks for your fast reply.


Xray: TypeError: string indices must be integers

Proof of concept code:
import json
from aws_lambda_powertools import Tracer
import boto3

tracer = Tracer()

@tracer.capture_method
def my_method():
    sts = boto3.client("sts")
    sts.get_caller_identity()
    raise RuntimeError("Error happens!")

@tracer.capture_lambda_handler
def lambda_handler(event, context):
    my_method()
    return {"statusCode": 200, "body": json.dumps({"hello": "world"})}

Logs
[ERROR]	2021-04-05T05:33:00.732Z	8a4d5027-4faa-4f4f-8d08-df63b7ea72ed	Failed to serialize ## lambda_handler
Traceback (most recent call last):
  File "/var/task/aws_lambda_powertools/tracing/tracer.py", line 313, in decorate
    response = lambda_handler(event, context, **kwargs)
  File "/var/task/app.py", line 17, in lambda_handler
    my_method()
  File "/var/task/aws_lambda_powertools/tracing/tracer.py", line 612, in decorate
    response = method(*args, **kwargs)
  File "/var/task/app.py", line 12, in my_method
    raise RuntimeError("Error happens!")
RuntimeError: Error happens!

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/var/task/aws_xray_sdk/core/models/entity.py", line 263, in serialize
    return json.dumps(self.to_dict(), default=str)
  File "/var/task/aws_xray_sdk/core/models/subsegment.py", line 157, in to_dict
    subsegment_dict = super(Subsegment, self).to_dict()
  File "/var/task/aws_xray_sdk/core/models/entity.py", line 284, in to_dict
    entity_dict[key]['working_directory'] = self.cause['working_directory']
TypeError: string indices must be integers

Xray screenshot:

Xray screenshot without @tracer.capture_method :

hey @michaelbrewer - I can't reproduce this using the latest version, however I remember X-Ray SDK team changed the serialization from jsonpickle to their own, and this line tells there's an issue with the new implementation
 File "/var/task/aws_xray_sdk/core/models/subsegment.py", line 157, in to_dict

Could you open up an issue upstream with them?
It's a regression only available in the develop branch. Lambda Powertools 1.13.0 doesn't have this issue as it uses X-Ray SDK 2.6.0
I'll lock to 2.6.0 in the meantime as we near 1.14.0 release this week.

I've subscribed to the upstream issue pending PR merge so I can revert the dependency pinning to the working version of X-Ray SDK. For now, I am closing this issue as 1.14.0 uses a previous working version.


(PE-37113) Allow benchmark to send command related queries

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


README cleanup

Fixed some spelling and grammatical mistakes, and reworded a few other things.
Are we good with advertising the invite to Slack link here in the README?  I know we had problems with spam in the past, but I also don't know where one would be able to find it otherwise.  If so, I'll add it in here.

In the context of README cleanup, is the duplicated "The master branch..." paragraph OK?

Sounds so much better now. Thanks!


chore: fix two more tests

Sorry - these are passing for me because I have access to the secrets, but then failing for build dist.


Add dennisreimann to donation list

Thanks @pavlenex for the invite! 🙏

Dennis has been a great and consistent contributor. He also contributed to docs repository.
ACK.

Ack

@vswee can you please push these changes live?

@vswee can you please push these changes live?

Have you though about automating the deployment so that fresh commits on master build the changes and deploy a new version of the website (via GitHub Actions)? I do this with several of my static sites and could help setting it up.

@dennisreimann #71


Make FileBackend VCS diff friendly

Please check if the PR fulfills these requirements

[x] The commit messages are descriptive
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] An issue has been created for the pull requests. Some issues might require previous discussion.

What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)

Increase CI/CD-friendlyness for FileBackend state files. Recent introduction of JSON for state files in JulieOps made it harder to track state changes in git, since the entire JSON was stored as a single line. This patch will pretty-print the JSON text, in order to better be able to track what has changed.
NOTE: This patch is built on top of my previous, unmerged PR.

What is the current behavior? (You can also link to an open issue here)

.cluster-state is a single line of JSON, so when committing to git, it is impossible (or at least cumbersome) to se what has changed.

What is the new behavior (if this is a feature change)?

.cluster-state is a pretty-printed, multi-line JSON file.

Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)

I don't think so.

Other information:

I guess the failing test is a transient failure. Integration tests (-Pacls) run fine on my Mac and on my Linux.

@sverrehu I merged the other PR and now this needs rebase. Not sure about the test, I will test as well once conflicts are fixed. thanks a lot again for your help and steady contributions, I am personally sad I can't keep up due to family and work.
Thanks again

so yes, test was transient failure ;-)

I tried to fix, but there are unrelated changes in my PR, so I failed. Closing for now. My git-foo is not as strong as my Java-foo.

Re "I am personally sad I can't keep up due to family and work"... Yes, I have been there. I'm probably 20 years ahead, and both my kids have moved out. Would like to send you a PM, if I figured out how to do it<EMAIL_ADDRESS>


Speed up SQLMetadataStorageActionHandlerTest

Motivation
testMigration creates about 3k tasks and verifies their migration. This takes around 45s since tasks are updated in batches of 100 after every 1s.
The same assertions can be made with a much smaller number of tasks, reducing the test time to 4s.
Changes

Reduce test time of SQLMetadataStorageActionHandlerTest.testMigration
Slightly modify log messages to adhere to Druid style

Thanks for the review, @AmatyaAvadhanula !


SpannerIO: Handling pg spanner.commit_timestamp

SpannerIO: Handling pg spanner.commit_timestamp
Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

@nielm @pabloem  Please review

LGTM

Note, as this is fixing a bug, please create an issue

Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue

This will mean that the fixed issue will be included in the release notes.

lgtm


Revert "encryption: Turn file dictionary into log style (#8865) (#8960)"

This reverts commit 5f7744942e61946f942148efb0b60389a37b6fa9.

What problem does this PR solve?
Problem Summary:
The feature modified the stored file format and brings incompatibility. So the cluster using new format cannot downgrade. The feature should be introduced in next major version like 5.x.
What is changed and how it works?
This reverts commit 5f7744942e61946f942148efb0b60389a37b6fa9.
Release note

Revert "encryption: Turn file dictionary into log style"

/run-all-tests

/merge


Session Timeout

Is there a way we can have the widget auto renew the session so that the widget always stay logged in?

Hi, @AndyHaas If you want to have it auto renew the session, you need to use authorization code flow to auth instead of implicit grant flow. So you need to provide 'appSecret' to this app. In authorization code flow, it will renew the token automatically. But if the app disconnect network from server for a long time, the session will timeout.

@embbnux am I able to add appSecret to the src on the iFrame?


[Proposal] Custom file extension

My proposal is that GB Studio saves the json files as a different extension e.g, .gbproj.
This way, the application could register the extension (at least on macOS), and it would be possible to implement a "Open with GB Studio" functionality

This would also work on Windows. When you launch the 'unknown' file it will ask what program you want to use to launch it. And if you want to use it with all these file types.

Yeah that would work. I guess on Windows, you would have to update a registry setting to automate it?

By opening an unkown file type you'll get a menu just like this. and you'll have to locate the GBstudio.exe and it will always open this file type with GBstudio(if you check that box on the bottom)

I'm going with .gbsproj rather than .gbproj (because GarageBand already took it!) but commit 27fc5e8b57696019407288c0edebf2a5e06ab457 adds support for this in the macOS build. It will only work with the version built for distributing so you need to npm run make and open the version in the out folder.
I also changed the naming on new projects so instead of project.json it's The Name Of Your Game.gbsproj. Kept compatibility with .json files though so old projects will still open.
I believe the Electron event app.on("open-file") only fires on macOS so there's a little bit needed to make this work on Windows, sounds like you use process.argv instead but not sure yet how you handle opening a file while the app is already open, need a bit of time by Windows machine to test.
This is the icon projects will use:

Commit b266a2af4b5074e98c3215c9121be955fdbcb3de adds support for opening directly from project files in Windows but the user first needs to select GB Studio from the list manually as shown in  Derek's screenshot.
To add the window registry I found this https://github.com/CatalystCode/windows-registry-node which has an associateExeForFile helper but I'm having trouble installing the module dependencies. Then there's also https://www.npmjs.com/package/regedit which I believe has no native dependencies but seems a bit more manual. I had a look at the link you sent Derek and did some research myself but I don't really know enough about the Windows registry to know what commands need to be run to associate the exe, the extension and the icon file together.

Great. I will close this issue then! 🙂


Add RabbitMQ support for payment hooks

This will need a rebase after #79 gets merged. RabbitMQ is an optional dependency that defaults to "OFF".
The CI has not been updated yet to verify RabbitMQ enabled builds (it only checks the OFF case).

Performed a rebase after the new account webhook PR was merged.


Improved dark mode/updated color system

Is your UI update related to a problem? Please describe.
This update is responding to two problems

dark mode issues
overly complicated color system causing design drift.

Describe the solution you'd like (include image or link to prototype)
To improve the dark mode, the monochromes have been updated, with a blue tint added to the darker colors. See the dark mode implemented here.
At the same time, the color system has been implemented with clear roles for each color used. See the updated color system here.
Describe alternatives you've considered
You can see other dark mode explorations here.
Technical considerations
New color values are as follows:
:root {

    /* Monochrome */
    --mono00: #fff; /* Card Background Light Mode */
    --mono20: #F7F8F7; /* Body Background Light Mode */
    --mono40: #E2E5EB; /* h1-h5 text Dark Mode */
    --mono60: #D3D8E2;
    --mono80: #C2C8D4;
    --mono100: #9CA0B0; /* P color Dark Mode */
    --mono120: #6C7180; /* P color Light Mode */
    --mono140: #4E5463;
    --mono160: #3A3E53;
    --mono170: #2E3244; /*new to improve dark mode*/
    --mono180: #2B2F40; /* card Background Dark Mode */
    --mono190: #252836; /*new to improve dark mode*/
    --mono200: #1F1D2B; /* h1-h5 Light Mode */

    /*light mode*/
    --purple10: #F6F4FF;
    --purple40: #B5A9F2;
    --purple70: #624FBE; /*primary*/
    --purple90: #4B3AA4;

    --blue10: #ECF4FF;
    --blue40: #9BC5FC;
    --blue70: #3D7BCE; /*primary*/
    --blue90: #23579D;

    --green10: #EBFFF0;
    --green40: #85DC8E;
    --green70: #288E32; /*primary*/
    --green90: #01550A;

    --yellow10: #FFFAEA;
    --yellow40: #FFE07C;
    --yellow70: #EAB612; /*primary*/
    --yellow90: #8D721A;

    --red10: #FFEDE4;
    --red40: #FFB18B;
    --red70: #EF570D; /*primary*/
    --red90: #A0370B;

    /*dark mode*/
    --purple120: #221C41;
    --purple90: #6756BC;
    --purple50: #C6BBFA; /*primary*/
    --purple30: #E7E2FF;

    --blue120: #181F2B;
    --blue90: #23579D;
    --blue50: #81B3F6; /*primary*/
    --blue30: #B8D6FF;

    --green120: #0C270F;
    --green90: #01550A;
    --green50: #4CB457; /*primary*/
    --green30: #85DC8E;

    --yellow120: #3F3517;
    --yellow90: #8D721A;
    --yellow50: #F8D567; /*primary*/
    --yellow30: #FFEAA6;

    --red120: #422417;
    --red90: #A0370B;
    --red50: #FF874D; /*primary*/
    --red30: #FFCEB7;

  }

Additional context
Because this editing process has removed some color variables, this update will require some minor style changes to be made to many of the elements in the design system.

Related: #599

Closed in #628


Component/757 autotest cloudprovider

Tweaks to the registration API for easier use
Hook the post registration URL up to the cloud provider list
A simple registration test

Looks like the new test failed.

We have a failing test:
[info] ! Cloud Providers.register a cloud provider: Exception raised on property evaluation.
[info] > ARG_0: List(RegisterProvider(TestCloudProviderDetails(reverifying ostracism,Some(cnijbrqomK txpkhwhs yyqgj ssslVkctu zbtshcd mxsfbnkpam izgUjsbh lcgnnanPm glooihz lLgjcsze),None)), RegisterProvider(TestCloudProviderDetails(paralysed amnesty,Some(ljxlfoxxy maSYthsuxb mbpyfr wbjzrpmbod),None)), DeleteProvider(paralysed amnesty))
[info] > Exception: org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"id('cloudProviderList')//li[.//h6[text() = "fea82570b1a448aa9b80d7248a184eaf reverifying ostracism"]]"}

Need to fix. Is this something you can look at @PenghaiZhang ?

We have a failing test:
[info] ! Cloud Providers.register a cloud provider: Exception raised on property evaluation.
[info] > ARG_0: List(RegisterProvider(TestCloudProviderDetails(reverifying ostracism,Some(cnijbrqomK txpkhwhs yyqgj ssslVkctu zbtshcd mxsfbnkpam izgUjsbh lcgnnanPm glooihz lLgjcsze),None)), RegisterProvider(TestCloudProviderDetails(paralysed amnesty,Some(ljxlfoxxy maSYthsuxb mbpyfr wbjzrpmbod),None)), DeleteProvider(paralysed amnesty))
[info] > Exception: org.openqa.selenium.NoSuchElementException: no such element: Unable to locate element: {"method":"xpath","selector":"id('cloudProviderList')//li[.//h6[text() = "fea82570b1a448aa9b80d7248a184eaf reverifying ostracism"]]"}

Need to fix. Is this something you can look at @PenghaiZhang ?

Yes, this has been fixed. It happened because the Typescript component we reused does not have the HTML element to be located.

Yup, already approved. If it passes the builds, lets get it merged and then maybe we can get it all into develop.


Manylinux Python wheels

Alright! This is finally working!
https://test.pypi.org/project/moordyn/2.2.2/#files
I excluded, for the time being, the musllinux platforms, which is popular just on embedded devices. They can anyway install moordyn using the sdist, so they are actually supported by the same pip command

Uhm... problems with the regular buildings... Weird...

It works now!


Assertion in addPropertiesHandler is non-functional and wrong :p

https://github.com/web-animations/web-animations-next/blob/127a8cefc3516dd8c94264e95b3d22d1daa3e91c/src/property-interpolation.js#L25
It should be checking that the property is not camel cased, and it should happen after var property is set.

This is fixed in head.


The controls such as "Repository" and "License" are not announced with proper role for screen reader users.

“Check out Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.”
GitHub Tags:#A11yMAS; #A11yTCS; #MAC; #ColorContrast; #A11y_VSCode; #A11ySev2;#CAITestPass_May2020;#Benchmark;#Visual Studio Code;#FTP;#VoiceOver;#WCAG1.3.1;#WCAG4.1.2;
Environment Details:
Application Name: VS Code
Application Version: 1.48.0-insider
Commit: cfbd1999769f4f08dce29629fb92fdc0fac53829
Date: 2020-08-06T05:40:40.871Z
Electron: 7.3.2
Chrome: 78.0.3904.130
Node.js: 12.8.1
V8: 7.8.279.23-electron.0
OS: Darwin x64 19.6.0
Operating system: macOS Catalina Version 10.15.6 (19G73)
Screen Reader: VoiceOver
Repro Steps:

Open Visual studio code
Click on extension button and search for "Azure Functions"
Click on install and move to the "Azure" button, the "Default Screen" will appear.
Start screen reader and navigate to controls such as "Repository" and "License" and observe if these are announced with role as link or not.

Actual:
When screen reader users navigate to the controls such as "Repository" and "License" they are announced as group and text which is incorrect as on activating them web page appears on the screen so they should be announced with proper role for screen reader users.
Expected:
The controls such as "Repository" and "License" should be announced as 'link' for screen reader users when they navigate to these controls.
User Impact:
If proper role is not announced for the interactive elements on the screen content then the screen reader users will miss out on the information available on these elements.
Attachment link for Reference:
2281_A11y_AzureExtensionsforVSCode_AzureFuction_DefaultScreen_Screenreader The controls such as "Repository" and "License" are not announced with proper role for screen reader users.zip

Dup of https://github.com/microsoft/vscode/issues/104552


User management in Admin settings on Community Edition

The instance admin should be able to manage users from Admin settings in Community Edition.

One instance where is a must is if an unrelated user signs up to the instance and is using their own workspace, the admin has no way to remove this user from the instance.

Community Request - https://community.appsmith.com/t/how-do-i-manage-global-users-on-self-hosted-community-edition/1642/4

As this is primarily an instance management feature and not an access control feature, we don't need to have the invite user and assign role/group functionality. We can achieve this by showing the Users page of GAC in the community edition and not having the below functionalities. The admin will then be able to keep tabs on users in the instance and remove unnecessary users as required.

Add Users
Edit User (2 entry points - 1. from 3-dot menu and 2. from clicking on user email)

Closing this as it is a duplicate of https://github.com/appsmithorg/appsmith/issues/21205. Please add any information on the linked issue.


Make it easier for customers to depart experiment

https://stackoverflow.com/questions/67983403/debugging-of-jupyter-notebooks-in-vscode
This is just an insiders user, but as we roll out native notebooks heavier we might get more requests for this in the near future. Might be worth a stopgap setting / command to help users depart the experiment?

We could add a command to do this.

Toggle menu?

Command pops up survey?

Survey might instead open an issue.


[TC-DA-1.8] - Manual script has to be updated as per VS changes

Description:
[TC-DA-1.8] - Manual script has to be updated as per VS changes

Test Step 31 and 47
All the test step numbering should be modified

Verification doc reference :
https://docs.google.com/spreadsheets/d/13zltSz50GRs_kidvobceEuIT8kAAHSK64ANyWcc3xQI/edit?usp=sharing
Test-Plan Reference :
https://github.com/CHIP-Specifications/chip-test-plans/blob/master/src/deviceattestation.adoc#218-tc-da-18-device-attestation-request-validation-success-scenario-dut-commissioner

See comments on the 1.4 PR, they apply here too, but worse because these are happy path tests so the result is that the TH should be commissioned.
That file has over a thousand lines, most of which are nearly identical logs that differ only by the timestamp, all mean to illustrate "Commissioning worked".
Can this be simplified? Those logs make it HARDER to tell what's going on, don't apply to most commissioners (chip-tool only) and are a make-work project for whoever is updating that script with basically NO benefit.


Flow error after 6.1.1 update

Error: node_modules/jest-enzyme/lib/index.js.flow:16
 16:   const { exposeGlobals } = require('jest-environment-enzyme/lib/setup');
                                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ jest-environment-enzyme/lib/setup. Required module not found

Found 1 error
error Command failed with exit code 2.

EDIT: the 'jest-environment-enzyme package is empty, no lib folder. Investigating.

Looks like the lib wasn't built, the prepublish hook didn't work as expected or whatever...
So this needs a new release.

Oof. I'm just gonna try to do a whole new patch bump and see if that fixes things..

try 6.1.2, does it fix it?

sigh of relief, thank goodness. I'm not sure how this release became so rough. Thanks for the help


Updated packaeg one line description to something more interesting

Work for this issue will begin begin on branch work-liquid-labs/cloudsite/41.

Duped and dealt with in #42.


🚀 Release alpha2

Description
Alpha2 release.
In this PR,

CHANGELOG updated
gitbook docs - https://docs.classifai.ai/
Release page draft - https://github.com/CertifaiAI/classifai/releases/tag/untagged-f1bfe807929e3bd1b5e0

We still don't have Mac installer for now.
Will publish the draft once merged.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[ ] Bug fix (Non-breaking change which fixes an issue)
[ ] New feature (Non-breaking change which adds functionality)
[ ] Breaking change (Fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update (Example: REST API changes)

Tested on?

[ ] Windows
[ ] Linux Ubuntu
[ ] Centos
[ ] Mac
[ ] Others  (State here -> xxx )

Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] New and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged
[ ] CHANGELOG.md has been updated
[ ] Update Gitbook REST API Page

@devenyantis
Reminder on
distribution link in readme and docs.classifai.ai
is created with bit.ly (by kenge using specific account) to track the demographics of downloads of each package.
For release tag, we included the raw distribution
(The assumption is normally people will not know/use here to download)

Ahh. Forgot. Thanks

@codenamewei
Deleting Installation for mac guide for now. Will add it back once we have the installer.


Cell borders are lost

Thank you for providing this library. For some reason, it loses cell borders. Here's a minimal reproduction with an .xlsx file made in LibreOffice. I have a single cell with no data, some borders and some background color. I read the Spreadsheet from that file and then immediately save it to another file. That new file still has the background color, but the cell borders are gone.
umya_spreadsheet_repro.zip

@Expurple
Thank you for your report.
We will investigate.

I have a feeling that all the recent issues may have a common source -- that when round-tripping, some structures are omitted and so everything beyond those omitted data are shifted in position and thus disappear or mapped to other cells.

The latest version is now available.
This issue has been resolved.
Please check it out.

Thank you, this issue is fixed in 1.3.0. But there is another problem with 1.3.0: #207

1.3.0 was yanked and re-released as 2.0.0


chore: release main

:robot: I have created a release beep boop
forms: 0.2.3
0.2.3 (2024-11-22)
Features

cep field: return address from onValidChange (fb8992c)
useForm: add onChange, onBlur, and onStateChange handlers (077f067)

form-example: 0.0.5
0.0.5 (2024-11-22)
Dependencies

The following workspace dependencies were updated

dependencies

@tabnews/forms bumped from 0.2.2 to 0.2.3

This PR was generated with Release Please. See documentation.

:robot: Created releases:

form-example-v0.0.5
forms-v0.2.3
:sunflower:


How to extend so default is assigned when coercion fails?

I really like Virtus and appreciate the high quality and tight focus.
I'm trying to use Virtus as a form-object.  I know there has been discussion on this in https://github.com/solnic/virtus/issues/99, so I'm looking at how to properly build atop/use Virtus.
This gist overrides the reader to return default when it isn't the expected type:
https://gist.github.com/joakimk/3515735
I'm using something similar but relying on Virtus and using a writer:
https://gist.github.com/adz/8215768
However, it's a bit crappy.  I'd really like to add an attribute extension like this one (or some other nice extension point):
https://github.com/solnic/virtus/blob/master/lib/virtus/attribute/strict.rb
My goal is to assign the default value when coercion fails.
Any help appreciated!

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1367463-how-to-extend-so-default-is-assigned-when-coercion-fails?utm_campaign=plugin&utm_content=tracker%2F144935&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F144935&utm_medium=issues&utm_source=github).

My two cents here are
:+1: for "having a way to instruct virtus what to do when a coercion fails"
Here is a quick workaround I have used so that a default value is set if coercion fails - its not ideal but...
  attribute :delay, Integer, strict: true, default: Config.default_delay #wherever this is stored

  def delay=(value)
    super(value) rescue Config.default_delay #wherever this is stored
  end

It makes totally sence, if coercion fails set the default. I don't understand why there hasn't been any progress on that.

@vasilakisfil because clearly nobody had the time to work on it

cool I thought it was another reason, I will come up with a solution.


Connection strings for parameterized linked services

One issue I've run into is using parameters for a linked service, specifically the AzureSqlDatabase type. In my case, I use the Managed Identity authentication type and then provide parameters for the Azure SQL server name and database name. In the end, my connection string looks like this in my development environment:
{
    "name": "AzureSqlDatabase1",
    "type": "Microsoft.DataFactory/factories/linkedservices",
    "properties": {
        "description": "Generic Azure SQL Database for use by datasets.",
        "parameters": {
            "DBServer": {
                "type": "string",
                "defaultValue": "sql-contoso1.database.windows.net"
            },
            "DBName": {
                "type": "string",
                "defaultValue": "AdventureWorks"
            }
        },
        "annotations": [],
        "type": "AzureSqlDatabase",
        "typeProperties": {
            "connectionString": "Integrated Security=False;Encrypt=True;Connection Timeout=30;Data Source=@{linkedService().DBServer};Initial Catalog=@{linkedService().DBName}"
        }
    }
}

The problem is that when using Azure DevOps releases, the connection string is always overwritten with a secure string value. Even if I provide the above connection string as the secure string value, the parameters are not interpreted since the connection string is secure. I can't figure out a way to provide the connection string in plain text using CI. I have to have add a script to my release that updates the connection string after the resource group deployment step. I've tried changing the parameterization template to something like this, but my DevOps release always wants a connection string for the AzureSqlDatabase.
  "Microsoft.DataFactory/factories/linkedServices": {
    "*": {
      "properties": {
        "typeProperties": {
          "connectionString": "="
        }
     }
  }

The Linked services section of the documentation says "The connectionString property will be parameterized as a securestring value. It won't have a default value." Just to clarify, does this mean that the connectionString property must always be provided at release time? I understand the security justification for this, but if that's the case, perhaps the documentation could clarify that this won't work for managed identities or for parameterized linked services.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1e22e4d6-366f-fbf8-e141-8905ca7ab7ae
Version Independent ID: 5be2acf2-66e7-cadf-6666-5a85a65b9771
Content: Continuous integration and delivery in Azure Data Factory - Azure Data Factory
Content Source: articles/data-factory/continuous-integration-deployment.md
Service: data-factory
GitHub Login: @djpmsft
Microsoft Alias: daperlov

Can  I Help let me know
On Sun, Sep 27, 2020, 12:01 PM Blaine<EMAIL_ADDRESS>wrote:

One issue I've run into is using parameters for a linked service,
specifically the AzureSqlDatabase type. In my case, I use the Managed
Identity authentication type and then provide parameters for the Azure SQL
server name and database name. In the end, my connection string looks like
this in my development environment:
{
"name": "AzureSqlDatabase1",

"type": "Microsoft.DataFactory/factories/linkedservices",

"properties": {

    "description": "Generic Azure SQL Database for use by datasets.",

    "parameters": {

        "DBServer": {

            "type": "string",

            "defaultValue": "sql-contoso1.database.windows.net"

        },

        "DBName": {

            "type": "string",

            "defaultValue": "AdventureWorks"

        }

    },

    "annotations": [],

    "type": "AzureSqlDatabase",

    "typeProperties": {

        "connectionString": "Integrated Security=False;Encrypt=True;Connection Timeout=30;Data Source=@{linkedService().DBServer};Initial Catalog=@{linkedService().DBName}"

    }

}

}
The problem is that when using Azure DevOps releases, the connection
string is always overwritten with a secure string value. Even if I provide
the above connection string as the secure string value, the parameters are
not interpreted since the connection string is secure. I can't figure out a
way to provide the connection string in plain text using CI. I have to have
add a script to my release that updates the connection string after the
resource group deployment step. I've tried changing the parameterization
template to something like this, but my DevOps release always wants a
connection string for the AzureSqlDatabase.
"Microsoft.DataFactory/factories/linkedServices": {
"*": {

  "properties": {

    "typeProperties": {

      "connectionString": "="

    }

 }

}
The Linked services
https://docs.microsoft.com/en-us/azure/data-factory/continuous-integration-deployment#linkedservices
section of the documentation says "The connectionString property will be
parameterized as a securestring value. It won't have a default value."
Just to clarify, does this mean that the connectionString property must
always be provided at release time? I understand the security justification
for this, but if that's the case, perhaps the documentation could clarify
that this won't work for managed identities or for parameterized linked
services.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com
http://docs.microsoft.com ➟ GitHub issue linking.

ID: 1e22e4d6-366f-fbf8-e141-8905ca7ab7ae
Version Independent ID: 5be2acf2-66e7-cadf-6666-5a85a65b9771
Content: Continuous integration and delivery in Azure Data Factory -
Azure Data Factory
https://docs.microsoft.com/en-us/azure/data-factory/continuous-integration-deployment#use-custom-parameters-with-the-resource-manager-template
Content Source:
articles/data-factory/continuous-integration-deployment.md
https://github.com/MicrosoftDocs/azure-docs/blob/master/articles/data-factory/continuous-integration-deployment.md
Service: data-factory
GitHub Login: @djpmsft https://github.com/djpmsft
Microsoft Alias: daperlov

—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/63347, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AP5XOAXXAIMTJ7DIEOWXBWTSH5VWVANCNFSM4R3VDKGQ
.

Thanks for the question! We will review and get back to you shortly.

@sc-bperry - Thanks for detailed inputs and valuable feedback. We dont have environment to repro and check if below suggestion helps. Kindly let us know if modifying the type to string in JSON here during deployment will work in this scenario.

@sc-bperry Thanks for the feedback! We have assigned the issue to the content author to further review this and provide an update as appropriate.
Hi @djpmsft - Could you please have a look at the above feedback and share your insights? - Thank you.

Thanks for your dedication to our documentation. Unfortunately, at this time we have been unable to review your issue in a timely manner and we sincerely apologize for the delayed response. Though the scope of our feedback channel here on GitHub covers specific documentation fixes, we can help redirect you to the right support channel to get an answer to your question.  You can engage support directly at the Microsoft Support web site or through your Azure Data Factory portal page in Azure, at the bottom of the blade panel on the left, under Support & Troubleshooting.  Because this issue does not relate to documentation, we are closing this issue. #please-close

Any suggestions regarding set parameter in Synapse TokenLibrary for a linked service would be very much appreciated.


USX 3.x support

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Hello
Do you plan to support USX 3.x? With the new possibilities it would by able to add Strong's numbers etc. https://ubsicap.github.io/usx/usx3.0/charstyles.html#w
Thanks

Thanks for reporting this issue. Currently Adapt It desktop does support USFM 3.0, and Adapt It Mobile supports  USFM 2.5 and USX version 2.0. It was on my radar to update to USFM and USX 3.x support in Adapt It Mobile as well, but it looks like I never wrote up an issue to track it (yikes!).

Marking this work item as closed/ implemented.


Create metrics API proof of concept

Related to #1344, this demonstrates a proof of concept metrics API to begin using. This implements the metric added in #1927, though I think we should be defining several more metrics beyond that. Before going too far into this idea, here's the gist of what I've come up with so far. API is loosely based on Micrometer which will be added as an implementation (probably its own module; this is effectively a plugin).

This PR has me very confused. I do see the new metrics package but the vast majority of this PR seems to have nothing to do with metrics.  Could you please separate out the builder improvements into their own PR?

The builder updates are related to adding dependency-injected values. I did not include any concrete implementations of the metrics API yet, but I updated some areas that are supposed to export metrics.

Or to be more specific, instead of creating yet another global variable, I had to refactor some code to apply inversion of control a little bit. If we were adapting Log4j to work via Spring beans, we'd still have to do the exact same thing.

What sort of event would be published here that could correspond to a counter? That's a push-based mechanism itself.

Looking through https://opentelemetry.io/docs/specs/otel/logs/ and OTel in general, it seems like we should have support for some of this directly. I don't think we need to implement all the APIs (like metrics and traces, though they might be natural logging APIs to include in the future). The alternative is a dependency stack larger than Log4j 2.x with optional dependencies in practice.

What sort of event would be published here that could correspond to a counter? That's a push-based mechanism itself.

For me an event is just any kind of object: in this case long is an event. ;-)
So stripped to the bone we need methods that return long and methods that consume Supplier<Long>.

@jvz,
I think we could choose an approach similar to RxJavaHooks to provide instrumentation hooks without affecting the performance of our application.
For 2.x we could create an InstrumentationService to give users the possibility to wrap our most important services:
public interface InstrumentationService {

    ReliabilityStrategy instrumentReliabilityStrategy(ReliabilityStrategy strategy);

    MessageFactory instrumentMessageFactory(MessageFactory factory);

    LogEventFactory instrumentEventFactory(LogEventFactory factory);

    AsyncQueueFullPolicy instrumentQueueFullPolicy(AsyncQueueFullPolicy policy);

    Appender instrumentAppender(Appender appender);
}

The default implementation would of course return the argument unchanged. What do you think?
For 3.x I believe that users can use the DI system to post-process these services.
Can we close this PR?

I think that's a good idea.


This page calls out not using Task.Delay in a loop while the Custom orchestrations page shows exactly that.

[Enter feedback here]

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 1d1a5a8a-2bff-1994-59bf-708900728297
Version Independent ID: 9e1a5c40-686d-78b5-37f6-b16b4e0843e4
Content: Timers in Durable Functions - Azure
Content Source: articles/azure-functions/durable/durable-functions-timers.md
Service: azure-functions
GitHub Login: @ggailey777
Microsoft Alias: azfuncdf

Hello @cwickham33, Thank you for your feedback! We will review and update as appropriate.

Hi @cwickham33 - Thanks again for your feedback. Could you point out the specific part that's calling out so?

@cwickham33 Since we didn't determine any updates for this documentation upon reviewing your feedback, we will proceed to close this thread for now. Please feel free to reopen with additional details and we will gladly continue the discussion.


Add Berge meetup group

This PR adds Bergen

Ping @Starefossen

@Starefossen @audunstrand could you please help filling in the speakers and sponsor information from your meetups? That will generate the markdown files, and website content so that it looks really nice, and you have a way to track what companies/speakers have been presenting previously.
I added TODO's in the YAML file for this.