clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     atomic_writer
  CC       atomic_reader.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     atomic_reader
  CC       external_env.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     external_env
  CC       links_env.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     links_env
  CC       filenotclosed.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     filenotclosed
  CC       del_many_dense_attrs.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     del_many_dense_attrs
  CC       flushrefresh.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     flushrefresh
  CC       use_append_chunk.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       use_common.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     use_append_chunk
  CC       use_append_chunk_mirror.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     use_append_chunk_mirror
  CC       use_append_mchunks.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     use_append_mchunks
  CC       use_disable_mdc_flushes.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     use_disable_mdc_flushes
  CC       swmr_generator.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     swmr_generator
  CC       swmr_start_write.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     swmr_start_write
  CC       swmr_reader.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     swmr_reader
  CC       swmr_writer.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     swmr_writer
  CC       swmr_remove_reader.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     swmr_remove_reader
  CC       swmr_remove_writer.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     swmr_remove_writer
  CC       swmr_addrem_writer.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     swmr_addrem_writer
  CC       swmr_sparse_reader.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     swmr_sparse_reader
  CC       swmr_sparse_writer.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     swmr_sparse_writer
  CC       vds_env.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     vds_env
  CC       vds_swmr_gen.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     vds_swmr_gen
  CC       vds_swmr_reader.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     vds_swmr_reader
  CC       vds_swmr_writer.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     vds_swmr_writer
  CC       filter_plugin.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     filter_plugin
  CC       vfd_plugin.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     vfd_plugin
  CC       vol_plugin.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     vol_plugin
Making all in bin
Making all in tools
Making all in lib
  CC       h5tools.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5tools_dump.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5tools_str.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5tools_utils.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5diff.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5diff_array.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5diff_attr.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5diff_dset.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5diff_util.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5trav.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5tools_filters.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5tools_ref.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5tools_type.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       io_timer.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     libh5tools.la
Making all in src
Making all in h5diff
  CC       h5diff_main.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5diff_common.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5diff
Making all in h5ls
  CC       h5ls.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5ls
Making all in h5dump
  CC       h5dump.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5dump_ddl.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5dump_xml.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5dump
Making all in misc
  CC       h5debug.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5debug
  CC       h5repart.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5repart
  CC       h5mkgrp.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5mkgrp
  CC       h5clear.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5clear
  CC       h5delete.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5delete
Making all in h5import
  CC       h5import.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5import
Making all in h5repack
  CC       h5repack.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5repack_copy.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5repack_filters.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5repack_opttable.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5repack_parse.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5repack_refs.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       h5repack_verify.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     libh5repack.la
  CC       h5repack_main.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5repack
Making all in h5jam
  CC       h5jam.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5jam
  CC       h5unjam.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5unjam
Making all in h5copy
  CC       h5copy.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5copy
Making all in h5format_convert
  CC       h5format_convert.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5format_convert
Making all in h5stat
  CC       h5stat.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5stat
Making all in h5perf
  CC       sio_perf.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CC       sio_engine.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5perf_serial
make[4]: Nothing to be done for `all-am'.
Making all in test
Making all in h5diff
  CC       dynlib_diff.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     libdynlibdiff.la
  CC       h5diffgentest.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5diffgentest
Making all in h5ls
  CC       dynlib_ls.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     libdynlibls.la
Making all in h5dump
  CC       dynlib_dump.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     libdynlibdump.la
  CC       h5dumpgentest.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5dumpgentest
  CC       binread.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     binread
Making all in misc
Making all in vds
  CC       UC_1_one_dim_gen.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     UC_1_one_dim_gen
  CC       UC_2_two_dims_gen.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     UC_2_two_dims_gen
  CC       UC_3_gaps_gen.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     UC_3_gaps_gen
  CC       UC_4_printf_gen.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     UC_4_printf_gen
  CC       UC_5_stride_gen.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     UC_5_stride_gen
  CC       h5repart_gentest.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5repart_gentest
  CC       h5clear_gentest.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5clear_gentest
  CC       talign.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     talign
  CC       repart_test.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     repart_test
  CC       clear_open_chk.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     clear_open_chk
Making all in h5import
  CC       h5importtest.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5importtest
Making all in h5repack
  CC       dynlib_rpk.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     libdynlibadd.la
  CC       dynlib_vrpk.lo
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     libdynlibvers.la
  CC       h5repacktst.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5repacktst
  CC       testh5repack_detect_szip.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     testh5repack_detect_szip
  CC       h5repackgentest.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5repackgentest
Making all in h5jam
  CC       tellub.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     tellub
  CC       h5jamgentest.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5jamgentest
  CC       getub.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     getub
Making all in h5copy
  CC       h5copygentest.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5copygentest
Making all in h5format_convert
  CC       h5fc_gentest.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5fc_gentest
  CC       h5fc_chk_idx.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5fc_chk_idx
Making all in h5stat
  CC       h5stat_gentest.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     h5stat_gentest
Making all in perform
  CC       iopipe.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     iopipe
  CC       chunk.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     chunk
  CC       chunk_cache.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     chunk_cache
  CC       overhead.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     overhead
  CC       zip_perf.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     zip_perf
  CC       perf_meta.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     perf_meta
make[4]: Nothing to be done for `all-am'.
make[3]: Nothing to be done for `all-am'.
Making all in utils
Making all in test
  CC       swmr_check_compat_vfd.o
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
clang: warning: argument unused during compilation: '-L/usr/lib' [-Wunused-command-line-argument]
  CCLD     swmr_check_compat_vfd
Making all in tools
Making all in test
make[5]: Nothing to be done for `all-am'.
make[4]: Nothing to be done for `all-am'.
make[3]: Nothing to be done for `all-am'.
Making all in .
make[2]: Nothing to be done for `all-am'.
Making install in src
 ../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../lib'
 /bin/sh ../libtool   --mode=install /usr/bin/install -c   libhdf5.la '/Users/*****/nanopolish/hdf5-1.13.2/../lib'
libtool: install: /usr/bin/install -c .libs/libhdf5.302.dylib /Users/*****/nanopolish/hdf5-1.13.2/../lib/libhdf5.302.dylib
libtool: install: (cd /Users/*****/nanopolish/hdf5-1.13.2/../lib && { ln -s -f libhdf5.302.dylib libhdf5.dylib || { rm -f libhdf5.dylib && ln -s libhdf5.302.dylib libhdf5.dylib; }; })
libtool: install: /usr/bin/install -c .libs/libhdf5.lai /Users/*****/nanopolish/hdf5-1.13.2/../lib/libhdf5.la
libtool: install: /usr/bin/install -c .libs/libhdf5.a /Users/*****/nanopolish/hdf5-1.13.2/../lib/libhdf5.a
libtool: install: chmod 644 /Users/*****/nanopolish/hdf5-1.13.2/../lib/libhdf5.a
libtool: install: ranlib /Users/*****/nanopolish/hdf5-1.13.2/../lib/libhdf5.a
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: /Users/*****/nanopolish/hdf5-1.13.2/../lib/libhdf5.a(H5CS.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: /Users/*****/nanopolish/hdf5-1.13.2/../lib/libhdf5.a(H5Obogus.o) has no symbols
/Applications/Xcode.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/ranlib: file: /Users/*****/nanopolish/hdf5-1.13.2/../lib/libhdf5.a(H5Zszip.o) has no symbols
 ../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../include'
 /usr/bin/install -c -m 644 hdf5.h H5api_adpt.h H5overflow.h H5pubconf.h H5public.h H5version.h H5Apublic.h H5ACpublic.h H5Cpublic.h H5Dpublic.h H5Epubgen.h H5Epublic.h H5ESpublic.h H5Fpublic.h H5FDpublic.h H5FDcore.h H5FDdirect.h H5FDfamily.h H5FDhdfs.h H5FDlog.h H5FDmirror.h H5FDmpi.h H5FDmpio.h H5FDmulti.h H5FDonion.h H5FDros3.h H5FDsec2.h H5FDsplitter.h H5FDstdio.h H5FDsubfiling/H5FDsubfiling.h H5FDsubfiling/H5FDioc.h H5FDwindows.h H5Gpublic.h H5Ipublic.h H5Lpublic.h H5Mpublic.h H5MMpublic.h H5Opublic.h H5Ppublic.h H5PLextern.h '/Users/*****/nanopolish/hdf5-1.13.2/../include'
 /usr/bin/install -c -m 644 H5PLpublic.h H5Rpublic.h H5Spublic.h H5Tpublic.h H5VLconnector.h H5VLconnector_passthru.h H5VLnative.h H5VLpassthru.h H5VLpublic.h H5Zpublic.h H5ESdevelop.h H5FDdevelop.h H5Idevelop.h H5Ldevelop.h H5Tdevelop.h H5TSdevelop.h H5Zdevelop.h '/Users/*****/nanopolish/hdf5-1.13.2/../include'
 ../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../lib'
 /usr/bin/install -c -m 644 libhdf5.settings '/Users/*****/nanopolish/hdf5-1.13.2/../lib'
Making install in test
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
Making install in bin
 ../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
 /usr/bin/install -c h5redeploy '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
make[3]: Nothing to be done for `install-data-am'.
Making install in tools
Making install in lib
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
Making install in src
Making install in h5diff
 ../../../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
  /bin/sh ../../../libtool   --mode=install /usr/bin/install -c h5diff '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
libtool: install: /usr/bin/install -c .libs/h5diff /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5diff
make[5]: Nothing to be done for `install-data-am'.
Making install in h5ls
 ../../../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
  /bin/sh ../../../libtool   --mode=install /usr/bin/install -c h5ls '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
libtool: install: /usr/bin/install -c .libs/h5ls /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5ls
make[5]: Nothing to be done for `install-data-am'.
Making install in h5dump
 ../../../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
  /bin/sh ../../../libtool   --mode=install /usr/bin/install -c h5dump '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
libtool: install: /usr/bin/install -c .libs/h5dump /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5dump
make[5]: Nothing to be done for `install-data-am'.
Making install in misc
 ../../../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
  /bin/sh ../../../libtool   --mode=install /usr/bin/install -c h5debug h5repart h5mkgrp h5clear h5delete '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
libtool: install: /usr/bin/install -c .libs/h5debug /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5debug
libtool: install: /usr/bin/install -c .libs/h5repart /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5repart
libtool: install: /usr/bin/install -c .libs/h5mkgrp /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5mkgrp
libtool: install: /usr/bin/install -c .libs/h5clear /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5clear
libtool: install: /usr/bin/install -c .libs/h5delete /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5delete
make[5]: Nothing to be done for `install-data-am'.
Making install in h5import
 ../../../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
  /bin/sh ../../../libtool   --mode=install /usr/bin/install -c h5import '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
libtool: install: /usr/bin/install -c .libs/h5import /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5import
make[5]: Nothing to be done for `install-data-am'.
Making install in h5repack
 ../../../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
  /bin/sh ../../../libtool   --mode=install /usr/bin/install -c h5repack '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
libtool: install: /usr/bin/install -c .libs/h5repack /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5repack
make[5]: Nothing to be done for `install-data-am'.
Making install in h5jam
 ../../../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
  /bin/sh ../../../libtool   --mode=install /usr/bin/install -c h5jam h5unjam '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
libtool: install: /usr/bin/install -c .libs/h5jam /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5jam
libtool: install: /usr/bin/install -c .libs/h5unjam /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5unjam
make[5]: Nothing to be done for `install-data-am'.
Making install in h5copy
 ../../../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
  /bin/sh ../../../libtool   --mode=install /usr/bin/install -c h5copy '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
libtool: install: /usr/bin/install -c .libs/h5copy /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5copy
make[5]: Nothing to be done for `install-data-am'.
Making install in h5format_convert
 ../../../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
  /bin/sh ../../../libtool   --mode=install /usr/bin/install -c h5format_convert '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
libtool: install: /usr/bin/install -c .libs/h5format_convert /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5format_convert
make[5]: Nothing to be done for `install-data-am'.
Making install in h5stat
 ../../../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
  /bin/sh ../../../libtool   --mode=install /usr/bin/install -c h5stat '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
libtool: install: /usr/bin/install -c .libs/h5stat /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5stat
make[5]: Nothing to be done for `install-data-am'.
Making install in h5perf
 ../../../bin/install-sh -c -d '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
  /bin/sh ../../../libtool   --mode=install /usr/bin/install -c h5perf_serial '/Users/*****/nanopolish/hdf5-1.13.2/../bin'
libtool: install: /usr/bin/install -c .libs/h5perf_serial /Users/*****/nanopolish/hdf5-1.13.2/../bin/h5perf_serial
make[5]: Nothing to be done for `install-data-am'.
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
Making install in test
Making install in h5diff
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
Making install in h5ls
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
Making install in h5dump
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
Making install in misc
Making install in vds
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
Making install in h5import
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
Making install in h5repack
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
Making install in h5jam
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
Making install in h5copy
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
Making install in h5format_convert
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
Making install in h5stat
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
Making install in perform
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
Making install in utils
Making install in test
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
Making install in tools
Making install in test
make[6]: Nothing to be done for `install-exec-am'.
make[6]: Nothing to be done for `install-data-am'.
make[5]: Nothing to be done for `install-exec-am'.
make[5]: Nothing to be done for `install-data-am'.
make[4]: Nothing to be done for `install-exec-am'.
make[4]: Nothing to be done for `install-data-am'.
Making install in .
make[3]: Nothing to be done for `install-exec-am'.
make[3]: Nothing to be done for `install-data-am'.
for d in examples  ; do               \
	    (cd $d && /Applications/Xcode.app/Contents/Developer/usr/bin/make  install-examples) || exit 1;           \
	done
../bin/mkdirs /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c
+ /usr/bin/install -c ./h5_write.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_read.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_extend_write.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_chunk_read.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_compound.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_crtgrpd.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_subset.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_cmprss.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_rdwt.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_crtgrpar.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_extend.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_crtatt.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_crtgrp.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_crtdat.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_group.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_select.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_attribute.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_mount.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_drivers.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_reference_deprec.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_ref_extern.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_ref_compat.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_ref2reg_deprec.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_extlink.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_elink_unix2win.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_shared_mesg.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_debug_trace.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./ph5example.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./ph5_filtered_writes.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./ph5_filtered_writes_no_sel.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./ph5_subfiling.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_vds.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_vds-exc.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_vds-exclim.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_vds-eiger.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_vds-simpleIO.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_vds-percival.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_vds-percival-unlim.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./h5_vds-percival-unlim-maxmin.c /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c run-c-ex.sh /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/c/.
+ /usr/bin/install -c ./README /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/.
+ /usr/bin/install -c ./run-all-ex.sh /Users/*****/nanopolish/hdf5-1.13.2/../share/hdf5_examples/.
if [ ! -e 3.3.7.tar.bz2 ]; then \
		wget https://gitlab.com/libeigen/eigen/-/archive/3.3.7/eigen-3.3.7.tar.bz2; \
	fi
--2022-09-13 07:35:17--  https://gitlab.com/libeigen/eigen/-/archive/3.3.7/eigen-3.3.7.tar.bz2
Auflösen des Hostnamens gitlab.com (gitlab.com)… 2606:4700:90:0:f22e:fbec:5bed:a9b9, <IP_ADDRESS>
Verbindungsaufbau zu gitlab.com (gitlab.com)|2606:4700:90:0:f22e:fbec:5bed:a9b9|:443 … verbunden.
HTTP-Anforderung gesendet, auf Antwort wird gewartet … 200 OK
Länge: nicht spezifiziert [application/octet-stream]
Wird in »eigen-3.3.7.tar.bz2« gespeichert.

eigen-3.3.7.tar.bz2                         [      <=>                                                                     ]   1.59M  1.26MB/s    in 1.3s

2022-09-13 07:35:20 (1.26 MB/s) - »eigen-3.3.7.tar.bz2« gespeichert [1663474]

tar -xjf eigen-3.3.7.tar.bz2 || exit 255
mv eigen-3.3.7 eigen || exit 255
rm -f ./.depend
c++ -g -O3 -std=c++11 -fopenmp -fsigned-char -D_FILE_OFFSET_BITS=64  -isysroot /Applications/Xcode.app/Contents/Developer/Platforms/MacOSX.platform/Developer/SDKs/MacOSX12.3.sdk -L/usr/lib -I./include -I./htslib -I./minimap2 -I./src -I./src/hmm -I./src/thirdparty -I./src/thirdparty/scrappie -I./src/common -I./src/alignment -I./src/pore_model -I./src/io -I./src/basemods -I./eigen/ -I./slow5lib/include/ -MM  src/nanopolish_call_methylation.cpp src/nanopolish_call_variants.cpp src/nanopolish_detect_polyi.cpp src/nanopolish_fast5_check.cpp src/nanopolish_haplotype.cpp src/nanopolish_index.cpp src/nanopolish_methyltrain.cpp src/nanopolish_phase_reads.cpp src/nanopolish_polya_estimator.cpp src/nanopolish_raw_loader.cpp src/nanopolish_read_db.cpp src/nanopolish_scorereads.cpp src/nanopolish_squiggle_read.cpp src/nanopolish_train_poremodel_from_basecalls.cpp src/nanopolish_variant_db.cpp src/nanopolish_vcf2fasta.cpp src/training_core.cpp  src/hmm/nanopolish_duration_model.cpp src/hmm/nanopolish_profile_hmm.cpp src/hmm/nanopolish_profile_hmm_r7.cpp src/hmm/nanopolish_profile_hmm_r9.cpp src/hmm/nanopolish_transition_parameters.cpp      src/common/fs_support.cpp src/common/logsum.cpp src/common/nanopolish_alphabet.cpp src/common/nanopolish_bam_processor.cpp src/common/nanopolish_bam_utils.cpp src/common/nanopolish_common.cpp src/common/nanopolish_iupac.cpp src/common/nanopolish_klcs.cpp src/common/nanopolish_variant.cpp  src/alignment/nanopolish_alignment_db.cpp src/alignment/nanopolish_anchor.cpp src/alignment/nanopolish_eventalign.cpp  src/pore_model/nanopolish_model_names.cpp src/pore_model/nanopolish_pore_model_set.cpp src/pore_model/nanopolish_poremodel.cpp  src/io/nanopolish_fast5_io.cpp src/io/nanopolish_fast5_loader.cpp src/io/nanopolish_fast5_processor.cpp  src/basemods/nanopolish_basemods.cpp      src/thirdparty/fet.c src/thirdparty/stdaln.c  src/thirdparty/scrappie/event_detection.c src/thirdparty/scrappie/scrappie_common.c           > ./.depend;
clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated [-Wdeprecated]
clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated [-Wdeprecated]
clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated [-Wdeprecated]
clang: warning: treating 'c' input as 'c++' when in C++ mode, this behavior is deprecated [-Wdeprecated]
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
clang: error: unsupported option '-fopenmp'
make: *** [.depend] Error 1

OK. Last night my system updated to 12.6, which caused a few issues with the Xcode command line tools, but i sorted that out. Then I used homebrew to install gcc (12.2.0). As you indicated, I had to specifically call gcc with the version, or it defaulted to clang. The results of using make CC=gcc-12 CXX=g++-12  HDF5_VERSION=1.13.2 are attached below. It eventually failed with:
A linker snapshot was created at:
	/tmp/nanopolish-2022-09-14-122704.ld-snapshot
ld: Assertion failed: (_file->_atomsArrayCount == computedAtomCount && "more atoms allocated than expected"), function parse, file macho_relocatable_file.cpp, line 2061.
collect2: error: ld returned 1 exit status
make: *** [nanopolish] Error 1

log_with_gcc.txt

That's a new one to me as it appears the code compiled successfully but it crashed the linker. A bit of googling hints that it might be a homebrew problem. Any chance you could try to install gcc with conda instead?

Perhaps the method that I  use for building f5c and slow5tools could be adapted to nanopolish which seems to have worked in most circumstances (either with inbuilt clang or homebrew gcc compiler).  This requires the user to install hdf5 using brew install hdf5 and then LDFLAGS=-L/opt/homebrew/lib/ CPPFLAGS=-I/opt/homebrew/include/ flags are added. Perhaps @mikeds211 could you see if you can build f5c, if it works I can look into the nanopolish makefile to see if that method can be integrated.

[jts]

try to install gcc with conda instead?
 conda install gcc fails with PackagesNotFoundError: and suggests I try other channels. Maybe this is because of my recent update in os to 12.6 (?).

[hasindu2008]

Perhaps the method that I use for building f5c
I followed your homebrew instructions for hd5 and then installed f5c with conda without difficulty. However, I saw no compilation of code via gcc here, so I am guessing I just installed the f5c binary. I wish nanopolish was as easy. I noticed that brew installs hdf5 version 1.12.2 but jts recommended version 1.13.2 for nanopolish. Does this make any difference?

I then removed the conda installation of f5c to try compiling from source code. I can download the latest source, unpack and cd into the directory and enter scripts/install-hts.sh. That worked fine but ./configure fails with zsh: no such file or directory: ./configure. Is this supposed to find configure.ac or config.mk.in ? If I ignore the ./config failure and try to make, it fails with;
3 errors generated.
make[3]: *** [H5Odeprec.lo] Error 1
make[3]: *** Waiting for unfinished jobs....
1 warning generated.
make[2]: *** [all] Error 2
make[1]: *** [all-recursive] Error 1
make: *** [build/lib/libhdf5.a] Error 2

I think you clone the gitrepo rather than compiling a release.
Try the following instructions:
brew install hdf5
VERSION=v1.1
wget "https://github.com/hasindu2008/f5c/releases/download/$VERSION/f5c-$VERSION-release.tar.gz" && tar xvf f5c-$VERSION-release.tar.gz && cd f5c-$VERSION/
scripts/install-hts.sh  # download and compile the htslib
./configure LDFLAGS=-L/opt/homebrew/lib/ CPPFLAGS=-I/opt/homebrew/include/
make                    # make cuda=1 to enable CUDA support

@hasindu2008: Try the following instructions: I followed those instructions and ./configure then worked. The compilation only flagged warnings (see below), and I could call f5c with ./f5c from within the f5c-v1.1 directory. This means it compiled OK. I did all of this in my base level of conda, not in a virtual environment. How do you suggest I now deal with installing nanopolish? I prefer to do this within a conda virtual env.
2 warnings generated.
cc -g -Wall -O2 -std=c99 -I include/ -I thirdparty/streamvbyte/include/ src/slow5_idx.c -c -fpic -o lib/slow5_idx.o
cc -g -Wall -O2 -std=c99 -I include/ -I thirdparty/streamvbyte/include/ src/slow5_misc.c -c -fpic -o lib/slow5_misc.o
cc -g -Wall -O2 -std=c99 -I include/ -I thirdparty/streamvbyte/include/ src/slow5_press.c -c -fpic -o lib/slow5_press.o
make -C thirdparty/streamvbyte no_simd= libstreamvbyte.a
cc -fPIC -std=c99 -O3 -Wall -Wextra -pedantic -Wshadow -DSTREAMVBYTE_SSSE3=1 -mssse3 -c ./src/streamvbyte_decode.c -Iinclude
cc -fPIC -std=c99 -O3 -Wall -Wextra -pedantic -Wshadow -DSTREAMVBYTE_SSSE3=1 -mssse3 -c ./src/streamvbyte_encode.c -Iinclude
cc -fPIC -std=c99 -O3 -Wall -Wextra -pedantic -Wshadow -DSTREAMVBYTE_SSSE3=1 -mssse3 -c ./src/streamvbyte_zigzag.c -Iinclude
ar rcs libstreamvbyte.a streamvbyte_decode.o streamvbyte_encode.o streamvbyte_zigzag.o
cp thirdparty/streamvbyte/libstreamvbyte.a lib/libslow5.a
ar rcs lib/libslow5.a lib/slow5.o lib/slow5_idx.o lib/slow5_misc.o lib/slow5_press.o
g++ -g -Wall -O2 -std=c++11 build/main.o build/meth_main.o build/f5c.o build/f5cio.o build/events.o build/nanopolish_read_db.o build/index.o build/nanopolish_fast5_io.o build/model.o build/align.o build/meth.o build/hmm.o build/freq.o build/eventalign.o build/freq_merge.o build/resquiggle.o build/profiles.o slow5lib/lib/libslow5.a -L/opt/homebrew/lib/ htslib/libhts.a   -lhdf5 -lz  -lpthread -lz -rdynamic  -o f5c
ld: warning: directory not found for option '-L/opt/homebrew/lib/'

@jts
Nanopolish make file has an option to specify the location of an existing HDF5 library right?
If that is the case, providing the homebrew location to prevent compiling HDF5 and then letting the rest be compiled with clang could work.


change Buffer.from() to new Buffer()

Added in: v5.10.0
array <Array>
Allocates a new Buffer using an array of octets.
Example:
// Creates a new Buffer containing UTF-8 bytes of the string 'buffer'
const buf = Buffer.from([0x62, 0x75, 0x66, 0x66, 0x65, 0x72]);

A TypeError will be thrown if array is not an Array.

sorry, use of the Buffer constructor is being deprecated, Buffer.from() is the correct way to instantiate a buffer


Custom card missing

Hey!
I don't find the "custom card".
Cache clear, reboot, I had try on Chrome, Firefox, Brave.
Since 4 day's, impossible to find this card for do this thing:
type: 'custom:webrtc-camera'
url: 'rtsp://rtsp:12345678@<IP_ADDRESS>:554/av_stream/ch0'
Thank you in advance :)
PS: I use the version 3.

#260 probably you use Lovelace more YAML

I don't use YAML.
What can I do?

Maybe you haven't install integration. You can also check errors in Hass logs

I use integration. But I don't see anything ^^
I will check logs.
Thank you and have a noce day Alexx

Very weird oO

What is wired for you? If this window is displayed - the integration is not configured. If integration is not configured - there is no card.


support region wellknown label

1. Issue, if available:
https://github.com/aws/karpenter/issues/1109
https://github.com/aws/karpenter/issues/1218
2. Description of changes:
Implement synthetic support for the well known region label
3. How was this change tested?

scaled a node that got the region label

4. Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: link to issue
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Can you try this with the in-tree EBS volume controller to make sure that this isn't the only blocker?

Can you try this with the in-tree EBS volume controller to make sure that this isn't the only blocker?

Yeah, I tested with the in-tree and reproduced with the current main HEAD. I deployed this branch and a node gets provisioned successfully and the pod goes to Running.

Super simple now! It just ignores it :)


Read relationships from config

Provide a way to explicitly set relationships in the
configuration file. Read the configurations and
store them in a convenient map that we will
use for future action.

:shipit:


Dimension error when solving a feasible quadratic convex program with SCS.

Describe the bug
I am getting a dimension error when solving a feasible quadratic convex program involving cp.quad_form(x, P). This happens when the solver is set to CVXOPT, ECOS, or SCS. It works fine when I use the default solver OSQP. I haven't tried it with other solvers.
To Reproduce
Execute
import numpy as np
import cvxpy as cp
x = cp.Variable(3)
A = np.eye(3)
b = np.ones(3,)
c = -np.ones(3,)
P = np.zeros((3,3))
prob = cp.Problem(cp.Minimize((1/2)*cp.quad_form(x, P) + c.T @ x), [A @ x <= b])
prob.solve(solver = cp.CVXOPT)

Expected behavior
The solver should execute and output 3.0 as the optimal value.
Output
ValueError                                Traceback (most recent call last)
<ipython-input-61-70627cb0d052> in <module>
      5 P = np.zeros((3,3))
      6 prob = cp.Problem(cp.Minimize((1/2)*cp.quad_form(x, P) + c.T @ x), [A @ x <= b])
----> 7 prob.solve(solver = cp.CVXOPT)

/usr/local/Cellar/jupyterlab/2.2.6/libexec/lib/python3.8/site-packages/cvxpy/problems/problem.py in solve(self, *args, **kwargs)
    394         else:
    395             solve_func = Problem._solve
--> 396         return solve_func(self, *args, **kwargs)
    397
    398     @classmethod

/usr/local/Cellar/jupyterlab/2.2.6/libexec/lib/python3.8/site-packages/cvxpy/problems/problem.py in _solve(self, solver, warm_start, verbose, gp, qcp, requires_grad, enforce_dpp, **kwargs)
    748                 return self.value
    749
--> 750         data, solving_chain, inverse_data = self.get_problem_data(
    751             solver, gp, enforce_dpp)
    752         solution = solving_chain.solve_via_data(

/usr/local/Cellar/jupyterlab/2.2.6/libexec/lib/python3.8/site-packages/cvxpy/problems/problem.py in get_problem_data(self, solver, gp, enforce_dpp)
    523             inverse_data = self._cache.inverse_data + [solver_inverse_data]
    524         else:
--> 525             data, inverse_data = solving_chain.apply(self)
    526             safe_to_cache = (
    527                 isinstance(data, dict)

/usr/local/Cellar/jupyterlab/2.2.6/libexec/lib/python3.8/site-packages/cvxpy/reductions/chain.py in apply(self, problem)
     69         inverse_data = []
     70         for r in self.reductions:
---> 71             problem, inv = r.apply(problem)
     72             inverse_data.append(inv)
     73         return problem, inverse_data

/usr/local/Cellar/jupyterlab/2.2.6/libexec/lib/python3.8/site-packages/cvxpy/reductions/dcp2cone/dcp2cone.py in apply(self, problem)
     41         if not self.accepts(problem):
     42             raise ValueError("Cannot reduce problem to cone program")
---> 43         return super(Dcp2Cone, self).apply(problem)

/usr/local/Cellar/jupyterlab/2.2.6/libexec/lib/python3.8/site-packages/cvxpy/reductions/canonicalization.py in apply(self, problem)
     57         inverse_data = InverseData(problem)
     58
---> 59         canon_objective, canon_constraints = self.canonicalize_tree(
     60             problem.objective)
     61

/usr/local/Cellar/jupyterlab/2.2.6/libexec/lib/python3.8/site-packages/cvxpy/reductions/canonicalization.py in canonicalize_tree(self, expr)
     97             constrs = []
     98             for arg in expr.args:
---> 99                 canon_arg, c = self.canonicalize_tree(arg)
    100                 canon_args += [canon_arg]
    101                 constrs += c

/usr/local/Cellar/jupyterlab/2.2.6/libexec/lib/python3.8/site-packages/cvxpy/reductions/canonicalization.py in canonicalize_tree(self, expr)
     97             constrs = []
     98             for arg in expr.args:
---> 99                 canon_arg, c = self.canonicalize_tree(arg)
    100                 canon_args += [canon_arg]
    101                 constrs += c

/usr/local/Cellar/jupyterlab/2.2.6/libexec/lib/python3.8/site-packages/cvxpy/reductions/canonicalization.py in canonicalize_tree(self, expr)
     97             constrs = []
     98             for arg in expr.args:
---> 99                 canon_arg, c = self.canonicalize_tree(arg)
    100                 canon_args += [canon_arg]
    101                 constrs += c

/usr/local/Cellar/jupyterlab/2.2.6/libexec/lib/python3.8/site-packages/cvxpy/reductions/canonicalization.py in canonicalize_tree(self, expr)
    100                 canon_args += [canon_arg]
    101                 constrs += c
--> 102             canon_expr, c = self.canonicalize_expr(expr, canon_args)
    103             constrs += c
    104         return canon_expr, constrs

/usr/local/Cellar/jupyterlab/2.2.6/libexec/lib/python3.8/site-packages/cvxpy/reductions/canonicalization.py in canonicalize_expr(self, expr, args)
    111             return expr, []
    112         elif type(expr) in self.canon_methods:
--> 113             return self.canon_methods[type(expr)](expr, args)
    114         else:
    115             return expr.copy(args), []

/usr/local/Cellar/jupyterlab/2.2.6/libexec/lib/python3.8/site-packages/cvxpy/reductions/dcp2cone/atom_canonicalizers/quad_form_canon.py in quad_form_canon(expr, args)
     29         scale = -scale
     30         expr = sum_squares(Constant(M2.T) @ args[0])
---> 31     obj, constr = quad_over_lin_canon(expr, expr.args)
     32     return scale * obj, constr

/usr/local/Cellar/jupyterlab/2.2.6/libexec/lib/python3.8/site-packages/cvxpy/reductions/dcp2cone/atom_canonicalizers/quad_over_lin_canon.py in quad_over_lin_canon(expr, args)
     29     # where y+t is the scalar part of the second-order
     30     # cone constraint.
---> 31     constraints = [SOC(
     32                        t=y+t,
     33                        X=hstack([y-t, 2*x.flatten()]), axis=0

/usr/local/Cellar/jupyterlab/2.2.6/libexec/lib/python3.8/site-packages/cvxpy/constraints/second_order.py in __init__(self, t, X, axis, constr_id)
     41            (len(X.shape) == 2 and t.size != X.shape[1-axis]) or \
     42            (len(X.shape) == 1 and axis == 1):
---> 43             raise ValueError(
     44                 "Argument dimensions %s and %s, with axis=%i, are incompatible."
     45                 % (t.shape, X.shape, axis)

ValueError: Argument dimensions (9,) and (12,), with axis=0, are incompatible.

Version

OS: macOS Catalina, version 10.15.4.
CVXPY Version: 1.1.7.

This only happens when P = 0. It's kind of an edge case.

I've fixed this on master.


Update version - patch

fix for append to existing file

@CodyCBakerPhD this should solve for the last PR problem

fix #140

That does fix it, but it seems hacky isn't very thin - what use case does this come up in and is there no way around it in the downstream stuff?

@luiztauffer What problem does this create in your conversion? All the possibilities I can image can be resolved by setting overwrite appropriately - is that the case or am I missing something?

this piece of code should not be executed if we're just adding data to an existing nwb file:
https://github.com/catalystneuro/nwb-conversion-tools/blob/c7a2989243d9077e4db0c4f4468fbff92fee9daf/nwb_conversion_tools/nwbconverter.py#L136-L151

This piece of code will overwrite the nwbfile object in that case, so I don't see how this could 'cause a problem' in any of our conversions:
https://github.com/catalystneuro/nwb-conversion-tools/blob/update_version/nwb_conversion_tools/nwbconverter.py#L158-L165

@CodyCBakerPhD  you're right, in principle it wouldn't. Nevertheless, we should not run that piece of code, even if that will be overwritten, a matter of good practice imo.
I see now that we could indeed use or overwrite in that first if statement (instead of nwbfile_path is not None and not Path(nwbfile_path).is_file()), maybe that would actually be better

Yeah, we were aware of that fact when we wrote this code, but it's such a small inefficiency it doesn't really matter (one dictionary, one completely minimal NWB object). While it's a matter of practice certainly, it's also (I would argue) a better matter of practice to not expand a single logical if check out to four logical places (for doing what we want here, you'd need nwbfile_path is not None and not Path(nwbfile_path).is_file() and not overwrite).
A better way would be to make a conversion_tool function for generating a default NWBFile, and call it appropriately inside the save_to_file blocks.
Point being, this patch is listed as a 'fix' for a current conversion, not a performance enhancement, and is delaying our latest release. Since it changes nothing in terms of functionality I'll go ahead with the new release while you work on improving the code checks for this.

@CodyCBakerPhD
When appending data to an existing file we should not require metadata, and this for example will break the code. Example:
converter.run_conversion(
    metadata={},
    nwbfile_path=path_to_output_nwb,
    overwrite=False,
    conversion_options=conversion_options
)

Again, we are running a piece of code unnecessary in this case. Please accept the proposed fix or make a fix more of your taste here and let’s release it. The current nwb-conversion-tools release does not work for Movshon

@luiztauffer Thanks for providing the source of  your issues.
Ultimately, that's a failure of our (a) logical checks on the passed metadata structure prior to use and (b) non-safe dictionary retrieval. While your previous suggested changes would have forced your Movshon conversion through, they wouldn't have resolved that core issue so it would have come up again at a later point in time. And also would have broken other conversions without the proper overwrite interaction.
But of course I am always happy to implement these changes myself! Working on it now.

@CodyCBakerPhD
When appending data to an existing file we should not require metadata

We should always require metadata, and encourage that it be retrieved from the call to my_converter.get_metadata(). You never know what contained interfaces in that converter might contain information that isn't already in the NWBFile you're intending to append. In fact, two of our recent conversions (Tank, Mease) support this as an intended usage. I'm pretty sure that if you call get_metadata() in your conversion, instead of passing an empty dictionary, this error should not occur since get_metadata() from the super NWBConverter class will never return an empty dictionary - an importantly, will contain the keys at the source of this issue.
Anyway, I've raised this as an issue with v0.7.0 so we can refer back it it, and made a separate PR that fixes that. If it fixes your issue, then I'll close this PR.
Also, remember that we encourage (as a code style) the use of dictionary literals whenever possible. I.e., metadata=dict().


Medal Solution BBCode

Preview

I might close this PR if we want to use markdown just for the solutions instead.

cooould we do both? also seems there's some conflicting files.
the reason i want both, is because markdown would be best when printing to discord through bathbot, since discord supports markdown, but bbcode has some extra features which may be helpful


Remove -Werror from JavaCompile task options

Hey, thank you for this plugin!
We are encountering a problem where this plugin is causing our Android Gradle build to fail since we're using the latest stable JDK (21). Please see pipeline run:
https://github.com/NIAEFEUP/uni/actions/runs/9971137557/job/27551546683
This PR removes -Werror which should resolve this issue. I think it's the right thing to do, because the plugin shouldn't be the one to decide whether to fail the whole build because of warnings.

That line is there for a reason, which is to force me to fix and eliminate all errors and warnings within the code, and it should only be limited in scope to the code within this plugin. Since I don't use JDK 21, I did not see the warning. Could you copy and paste the warning that you are getting?

I've temporarily switched my system to JDK 21 and can see the issue being that it no longer supports specifying the source and target compatibility options, and thus newer versions of Gradle also issue a warning that these options are obsolete.
This is certainly an unusual scenario in that the warning is not in this package's Java source code but rather in the gradle file. And as long as developers will be using a spread of JDK and Gradle versions I see no solution other than the one you have offered.

Thanks for such a quick response.
Given that you want to ensure there are no warnings during plugin development, maybe you can pass -Werror only on CI, and remove this line from build.gradle (like this PR does).

The inclusion of -Werror here was a practice I think I copied from one of Google's 1st class plugins, video_player, and so I suspect video_player users will likely be reporting similar sorts of issues at this time. What all of their other plugins do instead is only include -Werror in the build.gradle file belonging to the example itself.
In any case, thank you for contributing the fix! It is merged and now published.

I see. Thanks for additional context and for merging it.
have a great day!


chore(main): release 1.5.1

:robot: I have created a release beep boop
1.5.1 (2023-12-11)
🛠 Refactor

release-please: handle new version (0251bf2)
release-please: update to new args (e5392b2)

🧰 Other

bump the deps group with 1 update (7392aa0)
bump the deps group with 2 updates (f937157)
gorelease: clean comment (080a9f2)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/lederniermetre/shortcut/releases/tag/v1.5.1 :sunflower:


feat: add generic selection support for ItemsRepeater

GitHub Issue (If applicable): closes #452, closes #395
PR Type
What kind of change does this PR introduce?

Feature

What is the current behavior?

What is the new behavior?

PR Checklist
Please check if your PR fulfills the following requirements:

[ ] Tested code with current supported SDKs
[ ] Docs have been added/updated which fit documentation template. (for bug fixes / features)
[ ] Unit Tests and/or UI Tests for the changes have been added (for bug fixes / features) (if applicable)
[ ] Wasm UI Tests are not showing unexpected any differences. Validate PR Screenshots Compare Test Run results.
[ ] Contains NO breaking changes
[ ] Updated the Release Notes
[ ] Associated with an issue (GitHub or internal)

Other information

Internal Issue (If applicable):

todo: re-align this to a more generic impl that supports beyond just Chip

last error: https://dev.azure.com/uno-platform/Uno Platform/_build/results?buildId=70309&view=ms.vss-test-web.build-test-results-tab&runId=2253503&resultId=100025&paneView=debug


resource/value: comment to prescribe best usage of resource.Value

Small documentation update to prescribe intended use of resource.Value

I like it. It's a shame these types and funcs are exported, would have been nicer to keep them private so we know this isn't a breaking change.
I can't find any usage outside this package though, so all good.

It's a good point, I definitely didn't think to check. I doubt we'd want to be importing interface types anyways. I think they should always be defined where their used.

I like it. It's a shame these types and funcs are exported, would have been nicer to keep them private so we know this isn't a breaking change.
I can't find any usage outside this package though, so all good.

It's a good point, I definitely didn't think to check. I doubt we'd want to be importing interface types anyways. I think they should always be defined where their used. edit unless they're part of standard Go

Good job they aren't interface types 😉

I like it. It's a shame these types and funcs are exported, would have been nicer to keep them private so we know this isn't a breaking change.
I can't find any usage outside this package though, so all good.

It's a good point, I definitely didn't think to check. I doubt we'd want to be importing interface types anyways. I think they should always be defined where their used. edit unless they're part of standard Go

Good job they aren't interface types 😉

Oh yeah, I had to look up the difference between interfaces and func types. I don't think we should be exporting func types, unless they will implement an interface where they are imported e.g.
```. Which seems redundant as there isn't anything in this package that implements the func types that expects an interface.

I don't think we should be exporting func types, unless they will implement an interface

Exporting func types is fine as it helps people get the signature correct and gives you somewhere to attach docs. I am always a little confused whether to use types or aliases for this kind of thing.
You can see examples in the std lib, context.CancelFunc for example.
Anyway, I don't think this PR is the place to un-export these types, we can follow up with another PR for that


Ah, this was colocated but I think it is the Master that carries /root/cdk
I'll give it a try asap and confirm
On Jul 6, 2017 23:35, "Tim Van Steenburgh"<EMAIL_ADDRESS>wrote:

@SaMnCo https://github.com/samnco Which charm is this on (easyrsa,
master, worker)?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/juju-solutions/bundle-canonical-kubernetes/issues/336#issuecomment-313526110,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACN4d-6r6tBmCUDRSaz1lDbBvGhIp1qUks5sLVMygaJpZM4ONjWE
.

Any update on this? Can this be reproduced?

I haven't tried to reproduce this, but I think the culprit is here: https://github.com/juju-solutions/layer-tls-client/blob/master/reactive/tls_client.py#L118


Sprint v0.0.4

I think its time to merge sprint v0.0.4 with the uat branch (default). If you agree please approve & merge

New changes require approval from someone other than mvarewyck because they were the last pusher.

@SanderDevisscher I've pushed some extra changes to have a clean version, but now I'm no longer a valid reviewer.. For me it's fine to merge.

I'll review your changes and overwrite merge restrictions if everything is
ok.
Mvg
Sander
Op di 9 jan. 2024 15:12 schreef Machteld Varewyck @.***

:

New changes require approval from someone other than mvarewyck because
they were the last pusher.
@SanderDevisscher https://github.com/SanderDevisscher I've pushed some
extra changes to have a clean version, but now I'm no longer a valid
reviewer.. For me it's fine to merge.
—
Reply to this email directly, view it on GitHub
https://github.com/inbo/alien-species-portal/pull/71#issuecomment-1883121805,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEAAQOAOE2FLD5T56BDONXTYNVF5RAVCNFSM6AAAAABBM3RDOGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOBTGEZDCOBQGU
.
You are receiving this because you were mentioned.Message ID:
@.***>


Getting an error while opening gui

Describe the bug
Every time i try to open menu i get this error https://pastebin.com/AMJfe6Ct
To Reproduce
Simply try to open menu with builder#open(player). My builder looks like this https://pastebin.com/nTGxhreH
LibraryPlugin#getInvManager() will just get a InventoryManager

i just update to the lastest version (1.5.2) and remove manager from the build and now im getting this error https://pastebin.com/xBKEZ46B
Whole class: https://pastebin.com/qEYk4QPx

i just update to the lastest version (1.5.2) and remove manager from the build and now im getting this error https://pastebin.com/xBKEZ46B Whole class: https://pastebin.com/qEYk4QPx

[17:08:27 ERROR]: [wLib] [ACF] Caused by: java.lang.IllegalStateException: No manager could be found. Please create an InventoryManager field in your main class.
Can you show your main class please?

My fault for not reading the entire error. I think there's something missing in the main class. Unfortunately, I'm not home, so I can't check it right now.

The fault was on my side because I did pass a main class in Builder#build which did not have an initialized InventoryManager.

@Wupin Glad to hear everything worked out :)


Ltd 5000 add country highlighting

Aim
Highlight the country on denials search page
Corresponding API pr here: https://github.com/uktrade/lite-api/pull/1982
LTD-5000

closed in favour of back end change


Add possibility to get workfiles with specific version

Current state
The current version of OpenPype offers no possibility to retrieve path of a workfile with a specific version, only the last one (see here). For the needs of the archiver, we would like to have that functionality for basic operations on these versions.

Peux tu déplacer le ticket au bon endroit STP


Failed to save image information

I have tried to upload image using file upload field, upload file to server is success but failed to save image information (file name) to database. thank's

It might be not related to the Builder plugin. Did you create a relation in your model class? Please see Builder's documentation (http://octobercms.com/plugin/rainlab-builder) and October documentation (http://octobercms.com/docs/database/attachments#file-attachments) for details.

Thank's for reply,
I have added this in my model class :
public $attachOne = [
'photo' => ['System\Models\File']
];
My table structure :
$table->engine = 'InnoDB';
$table->increments('id')->unsigned();
$table->string('name', 50);
$table->text('photo')->nullable();

The relation for files are stored in the system_files table, therefore you do not need an extra column. This might cause your troubles. I would recommend you to use the official forum: [https://octobercms.com/forum]. I am sure we can solve your issue there.
Suggesting to close this issue.

hello, I have a problem with the same file upload field, already add attachOne in my model class, the error is: "copy (); filename can not be empty" and once I select my image is displayed.
anyone has a solution ?, I think it is server problem, already check the file upload capability in php.ini
I do not know what else can be.
Thank you for your help

how can i display an image stored in my db, with the recordlist component?

Are you referring to the back-end list behavior (http://octobercms.com/docs/backend/lists#column-partial)? There is a way to render a partial (HTML file) in a list column. Inside the partial you can access the model and all its relations. Example:
<?php
    if ($image = $record->hero_image()->first())
        $thumb = $image->getThumb(48, null, 'landscape');
    else
        $thumb = 'http://placehold.it/48x48';
?>

    <img src="<?= $thumb ?>" alt="<?= $record->title ?>" />

@alekseybobkov I don´t know, what I want is to attach my picture, I keep in the base with a ImageUploader, when I access my attribute image through attribute (record, img) returns a JSON or associative arrays with path field, which is i want to access in order to show my image


Add RDS Start/Stop Configuration

Added RDS start/stop module config
Added supporting variable
Add profile config to enable RDS start/stop schedules for CHD and WCK RDS instances

Closing PR as the scope is changing - a new PR will be raised.


DUP - Site metrics results reflect when facilities were noted as "pass not required"

Description
This ticket is meant to align DUP capacity with the actual status of the park. Currently, the status of the facility does not influence capacity, so our reports require manual adjustment.
Acceptance Criteria
Given that I am seeking accurate DUP data on the site metrics page
When I populate the page or pull a report
Then I see data that reflects the actual capacity
Notes
Linked issues
is blocked by

[ ] https://github.com/bcgov/parks-reso-api/issues/309

November 21, 2024 - DUP prioritization session. This ticket/issue was identified as medium-high priority. Additional feedback:

Marshall identified that this is a high priority as the current DUP dataset is not seen as the 'source of truth'.
To have accurate data, the program team is manual checking/updating in an excel spreadsheet

https://app.mural.co/t/bcparks2575/m/bcparks2575/1729124366479/8adea59d9e76fb3eb1e33395f1c1857a8c07fb7b


[Feature request][TS-SDK] More generalized Coin object type validation rule

Steps to Reproduce Issue
Sui coin type has different definitions. Both the following types shall be considered as legit sui coin types:

0x2::coin::Coin<...>
0x02::coin::Coin<...>
0x0000...02::coin::Coin<...>

In the current implementation Coin module, the method to decide whether an object is coin is through RegEx, which is strictly:
export const COIN_TYPE_ARG_REGEX = /^0x2::coin::Coin<(.+)>$/;

Currently, the strict check is resulting in multiple breaking points accross SUI ecosystem since last SUI node update 1.1.0.
Example
The content returned by getObjectById has type defined as:
0x0000...0002::coin::Coin

Which is not recognized as Coin as SuiMoveObject.
Suggested update
Update the REGEX so that arbitrary number of extra zeros (need to be <63) are allowed in the coin type args.

Please help me


Would it be possible to get a printed list of all the available colors?

Might be nice for people trying this library out. I ended up just logging a bunch, which worked OK.

I believe it just uses the standard .NET Color enumeration, so:
string[] s = Enum.GetNames(typeof(System.Drawing.Color));

Thanks @equin0x80 !  Yes, any System.Drawing.Color is usable.


Design principals are missing.

Design Principals are linked in the terminology section of the protocol, but do not seem to exist.  Is there a replacement for this document or should the link be removed from the protocol terminology?

It should be removed. It was replaced by motivations and FAQ.

On Feb 4, 2016, at 11:07 AM, Michael Paulson<EMAIL_ADDRESS>wrote:
Design Principals are linked in the terminology section of the protocol, but do not seem to exist. Is there a replacement for this document or should the link be removed from the protocol terminology?
—
Reply to this email directly or view it on GitHub.


Jamie/fix datetime compliance reports

:nut_and_bolt: Description: What code changed, and why?
This is a continued effort to standardize time displays across the site.  This branch adds RFC2822 time format to the compliance reporting pages.  It also introduces a second time format which will be used that reads ex. Tue, Sept 24 2019
:chains: Related Resources
https://github.com/chef/automate/issues/1678
https://github.com/chef/automate/issues/1679
:+1: Definition of Done
Compliance Pages display with the new requested date format.
:athletic_shoe: How to Build and Test the Change

build components/automate-ui-devproxy && start_all_services
Navigate to https://a2-dev.test/compliance/reports/overview
Click report meta data to view meta data --> View Report date
Scroll down to Chart, View Node Status Over Time Graph --> View date range under graph
Click on Profile Status pill to view Control Status Over Time Graph --> View date range under graph
Click on Nodes tab, Click on any node in list to see its specific page --> View date range next to Last Scan
Click on Scan History in top right to view sidebar slideout --> View formatted date

:white_check_mark: Checklist

[ ] Tests added/updated?
[ ] Docs added/updated?

:camera: Screenshots, if applicable
Reports Meta Info

Node Status Graph

Control Status Graph

Reports - Specific Node and Sidebar

Sweet! Looks good for me!

+1 for either approaches we discussed around d3 time format.

Great idea - using moment for d3 instead.


Build settings: AltMe/Universal wallet

Same thing as Flavor settings/parameters: tokens, gallery#610 with other parameters.

[ ] show/hide Payment section in credential list
[ ] show/hide referral cards
[ ] show/hide NFT section
[ ] show/hide token section

M size


MAPQ of -2147483648 attributed to some reads in samfile (minimum value for an int32)

I'm using the following version of ngmlr:
ngmlr 0.2.7 (build: Jul  3 2020 03:31:03, start: 2020-07-19.14:10:32)
I ran the following command:
ngmlr -t 8 -x ont -r $reference -q $file.fastq.gz -o $file.sam
And one (probably more) of the lines outputs with a MAPQ of -2147483648
CCN_ACA_BMB_26  2048    chromosome15    1074809 -2147483648     2561S12M2D21M2I90M1D15M1I2M2D7M1D5M1I13M1S
I didn't paste the rest to avoid clutter but it's a 2731 bp read so nothing crazy in that respect (I checked in the original fastq file)
To provide more context, I think this is an issue that used to go unnoticed for me, but I now use samtools v1.10, which seems to now check for MapQ and output an error if it's <0
if (b->core.qual < settings->min_mapQ || ((b->core.flag & settings->flag_on) != settings->flag_on) || (b->core.flag & settings->flag_off))
        return 1;

(From: https://github.com/samtools/samtools/blob/a6a160bba842d6afc3da061a8aa4f199fd7b729b/sam_view.c)
Still, I don't know what would cause a MAPQ of -1 in the first place
This issue is also found in https://github.com/philres/ngmlr/issues/75 (looks like no one noticed the negative MAPQ but it's there. I'm not sure if there's a way to merge issues or so, I'm not proficient with github yet.
My hunch is that the following happens:
The mapping for the offending read is an extremely low quality, so I think there are issues with one of the signs in the these lines:
uint32_t mapq = -4.343 * log(1 - (double)abs(a->score1 - a->score2)/(double)a->score1);
mapq = (uint32_t) (mapq + 4.99);

I gather than mapq should be a positive integer, therefore I assume that
log(1 - (double)abs(a->score1 - a->score2)/(double)a->score1) <0
Therefore
1 - (double)abs(a->score1 - a->score2)/(double)a->score1 <1
Therefore
(double)abs(a->score1 - a->score2)/(double)a->score1 >0
Of course, what seems to be happening is the opposite, so the bug is that sometimes
(double)abs(a->score1 - a->score2)/(double)a->score1 <0
This is where my understanding reaches its limit (and maybe the bug is elsewhere but this seems like a good lead).
Either sometimes score1<score2, or sometimes score1<0
I'm not sure I understand what score1 and score2 represent so I don't know if either one is a plausible scenario. I hope all of this helps.

I'm having the exact same issue, my guess would be there seems to be some sort of underflow occurring somewhere but I've not looked through the code to try and pinpoint it.


Add Subscription Level SaaS alongside Tenant Level

Changelog

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[X] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet. December 2020 or January 2021
When you expect to publish swagger? Please provide date, or month to public if date is not available yet. January 2021
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[X] SDK of .NET (need service team to ensure code readiness)
[X] SDK of Python
[X] SDK of Java
[X] SDK of Js
[X] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[ ] No, no need to refresh for updates in this PR

Contribution checklist:

[X] I commit to follow the Breaking Change Policy of “no breaking changes
[X] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[X] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[X] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

Hi @tabenari something is wrong with the go config settings in this RP, therefore I made another PR targeting yours to fix it.

Hi, @tabenari. The PR has be closed for a long time and it's related branch still exist. If no further used for over 14 days, I will delete this related branch. Please tell me if you still need this branch.

Hi, @tabenari. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days.

Hi, @tabenari. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days.

Hi, @tabenari. The PR has be closed for a long time and it's related branch still exist. Please tell me if you still need this branch or i will delete it in 14 days.


Feature request: toggle on/off show control

A button that can toggle on and off show control in the Preferences menu.
Useful actions would be for:
Timecode: (toggle) Control of Main Timeline
MIDI: (toggle) MIDI Show Contol, Device ID:
Unknown if possible, but very helpful in theatre when you need to disable show control to edit cues quickly during tech.

To my knowledge it is not possible, there isn't a documented command to do this for the production (https://www.dataton.com/watchout-users-guide/appendix/c-control-protocol/list-of-commands).
The command timecodeMode only works for clusters, but then it wouldn't be very useful during tech.

This is not supported by the Watchout API.


Why need to log in?

Hello!
My question is:
Why I need to log in inside the webview in order to allow the app to edit a specific spreadsheet?

How could I avoid that? I would like to be already logged in (by giving credentials inside source code) without having to show the webview to the user. It is possible? If yes, how?
Thanks!
PS: I followed the "Setup Instructions" (OAuth 2.0) from the documentation.

@ggunti Have you get any way to edit Google spreadsheet without authentication ?

Use this instead:  https://github.com/xpcrts/-Correct-React-Native-App-With-Google-Spreadsheet-API


.cabal-sandbox/bin/kontiki-udp node3

Running
$ .cabal-sandbox/bin/kontiki-udp node3

Gives
kontiki-udp: Map.!: given key is not an element in the map

after node0, node1, node2 are up.

The kontiki-udp demo is, really, a very simple stupid demo, which only supports 3 nodes: https://github.com/NicolasT/kontiki/blob/e753c5afd0ff2a00fb674890908484137bec4240/bin/udp.hs#L58
I'm not sure adding support for more is worth the trouble...


How get the default route without current parameters with UrlHelper?

I have a pagination route in my twig template: /search[/page/{page:\d+}]. If I am currently on /search/page/5 the default route is /search/page/5 where I expect it to be /search. If I'm on /somewhere/else it's generating /search as expected.
This is caused by the UrlHelper injecting the current route parameters if it's the same route.
Is there anyway to disable this behavior for consistency, or maybe add a parameter to change this behavior when wanted?

@xtreamwayz it would be helpful to know which other routes you have in your routing configuration that begin with /search. I don't think /something/else is matching your /search[/page/{page:\d+}] route in this case, which is why you wouldn't be seeing the page info in the generated url.
UrlHelper is behaving appropriately in this case as far as I can tell, since when it's called without any arguments, the assumption is that you want the current URL - params and all.
The easiest way I can think of for you to work around this is to create a default route for the search landing page, and use that instead of the matched route.
So, if you have something like:
[
    'name' => 'search.index',
    'path' => '/search',
    'middleware' => ...,
    'allowed_methods' => ...,
]

Then, in your template, you could just do {{ url('search.index') }}. Since you'd have that default search index, and you'd know that you're paginating search results.
To make the UrlHelper exhibit the behavior you specified via parameter, we'd need to change the method signatures of __invoke() and generate() to include some kind of $overrideParams or $mergeParams boolean variable, which would break BC, so we'd need to wait for a new major version.
I wouldn't be strictly opposed to bundling all the remaining PRs in this repository into a 3.0.0 release, though, so if the solution I suggested above doesn't work for you, let me know and I'll look into what the best way would be to add this behavior to UrlHelper in a future release.

Let me rephrase it a bit.
// route
[
    'name'            => 'album.index',
    'path'            => '/album[/page/{page:\d+}]',
    'middleware'      => App\Action\AlbumIndexAction::class,
    'allowed_methods' => ['GET'],
],

Current route /album
{{ url('album.index') }} returns /album as expected.
Current route /album/page/5
{{ url('album.index') }} returns /album/page/5 => expected /album since I didn't give any parameters.
Current route /album/page/5
{{ url('album.index', {'page': '5'}) }} returns /album/page/5 as expected.
This is from my head since it's a pretty old issue. I'm not sure if this is still the case though. For myself I've split the route to get around this:
[
    'name'            => 'album.index',
    'path'            => '/album',     // [/page/{page:\d+}]
    'middleware'      => App\Action\AlbumIndexAction::class,
    'allowed_methods' => ['GET'],
],
[
    'name'            => 'album.search',
    'path'            => '/album/page/{page:\d+}',
    'middleware'      => App\Action\AlbumIndexAction::class,
    'allowed_methods' => ['GET'],
],

One solution is to add a third parameter to the helper, so that the signature becomes:
url($route = null, array $params = [], $reuseResultParams = true)

At that point, the condition if ($this->result) would become if ($this->result && $reuseResultParams). The user would then invoke the helper as: url('album.index', [], false). Cumbersome, but also indicative that special treatment of the generated URI was requested.
Now, that said: the approach might conflict with #9. In that case, it might become:
url($route = null, array $params = [], array $options = [])

with a special reuse_result_params option:
$uri = $helper('album.index', [], ['reuse_result_params' => false]);

Would this address your use case, @xtreamwayz ?

Yes, that would fix it. Another solution I have been thinking about is skipping a parameter if it's set with a null value.
Current route /album
{{ url('album.index') }} returns /album
Current route /album/page/5
{{ url('album.index') }} returns /album/page/5
Current route /album/page/5
{{ url('album.index', {'page': '10'}) }} returns /album/page/10
--->>> Current route /album/page/5
{{ url('album.index', {'page': null}) }} returns /album
This might feel a bit more natural. However I'm not sure if this could work with a route like this:
'/artists[/{artistId:\d+}[/albums/{albumId:\d+}]]'
Current route /artists/1/albums/5
{{ url('artists.index', {'albums': null}) }} returns /artists/1
Current route /artists/1/albums/5
{{ url('artists.index', {'artists': null}) }} returns /artists

@xtreamwayz The $reuseResultParams / ['reuse_result_params' => false] approach is more explicit, so I think I'd prefer that. Changing #9 for compatibility is not a big deal either @weierophinney so either approach would work, but the $reuseResultParams flag might make more sense. The purpose of #9 was to pass these $options to the router, but reuse_result_params is intended to be used by the helper.
So either:
url($route = null, array $params = [], array $routerOptions = [], $reuseResultParams = true);

or
url($route = null, array $params = [], $reuseResultParams = true, array $routerOptions = []);

would work, and it'd just be a matter of deciding on the param order so that we list the more common use case first. I've not had the need to do either of these things, so I'll leave it up to either you or a coin-toss. :)

coin-toss :)
It doesn't matter really. I have to add a parameter to the twig renderer anyway.

Considering not all routers support options anyways, I'd recommend $routerOptions be the last argument.

If passing a null value for a given parameter works across the various routers, I think this could then become a documentation issue...

Fixed via #23 and will be released with 3.0.0 due to the BC break.


Meaningless error with check trap xxxx()

function testRunner(string s1, string s2) returns error? {

    check trap testCreateIgVersionService(s1, s2); // [squiggly lines on trap keyword] invalid expression, expected a call expression(BCE0671)
    _ = check trap testCreateIgVersionService(s1, s2);
}

function testCreateIgVersionService(string s1, string s2) returns error? {

}

Steps to reproduce:
Affected Versions:
Ballerina 2201.1.0 (Swan Lake Update 1)
Language specification 2022R2
Update Tool 1.3.9
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

Prior to update to 2 (https://ballerina.io/spec/lang/2022R1/#call-stmt) check was only allowed as a statement if the expression it was used with was a function/method call.
With update 2 (https://ballerina.io/spec/lang/2022R3/#section_7.17) this has been allowed - https://github.com/ballerina-platform/ballerina-lang/issues/36190.