Bazel test killed using emissary executor

Pre-requisites

[X] I have double-checked my configuration
[x] I can confirm the issues exists when I tested with :latest
[ ] I'd like to contribute the fix myself (see contributing guide)

What happened/what you expected to happen?
Bazel test get killed when using emissary runtime executor. It works well on argo 3.3.8 with k8sapi executor.
Previous issue https://github.com/argoproj/argo-workflows/issues/8869 also points out similar problem but it's not solved.
Argo version: 3.4.1, 3.4.2 (I didn't test the most recent release v3.4.3 but I guess the problem is still there as there's no related changes in that release)
bazel version: 5.1.1
main log of a failed build on v3.4.1, emissary executor
Cloning into 'abseil-cpp'...
Extracting Bazel installation...
Starting local Bazel server and connecting to it...

INFO: Found 18 targets and 59 test targets...
[0 / 270] [Prepa] BazelWorkspaceStatusAction stable-status.txt ... (32 actions, 0 running)
[646 / 689] 30 / 59 tests; Compiling absl/strings/internal/cord_rep_btree_test.cc; 6s processwrapper-sandbox ... (29 actions, 28 running)
[688 / 703] 46 / 59 tests; Testing //absl/strings:str_cat_benchmark; 13s processwrapper-sandbox ... (14 actions running)
FAIL: //absl/strings:str_split_test (see /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/str_split_test/test.log)
FAIL: //absl/strings:str_cat_benchmark (see /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/str_cat_benchmark/test.log)
FAIL: //absl/strings:escaping_benchmark (see /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/escaping_benchmark/test.log)
FAIL: //absl/strings:charconv_benchmark (see /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/charconv_benchmark/test.log)
FAIL: //absl/strings:memutil_benchmark (see /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/memutil_benchmark/test.log)
[699 / 704] 54 / 59 tests, 5 failed; Testing //absl/strings:str_join_benchmark; 26s processwrapper-sandbox ... (5 actions running)
FAIL: //absl/strings:str_join_benchmark (see /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/str_join_benchmark/test.log)
FAIL: //absl/strings:numbers_benchmark (see /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/numbers_benchmark/test.log)
FAIL: //absl/strings:str_split_benchmark (see /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/str_split_benchmark/test.log)
FAIL: //absl/strings:ascii_benchmark (see /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/ascii_benchmark/test.log)
FAIL: //absl/strings:string_view_benchmark (see /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/string_view_benchmark/test.log)
INFO: Elapsed time: 102.398s, Critical Path: 35.40s
INFO: 704 processes: 299 internal, 405 processwrapper-sandbox.
INFO: Build completed, 10 tests FAILED, 704 total actions
//absl/strings:ascii_test                                                PASSED in 0.1s
//absl/strings:char_map_benchmark                                        PASSED in 1.0s
//absl/strings:char_map_test                                             PASSED in 0.2s
//absl/strings:charconv_bigint_test                                      PASSED in 0.4s
//absl/strings:charconv_parse_test                                       PASSED in 0.2s
//absl/strings:charconv_test                                             PASSED in 11.8s
//absl/strings:cord_buffer_test                                          PASSED in 0.2s
//absl/strings:cord_data_edge_test                                       PASSED in 0.2s
//absl/strings:cord_rep_btree_navigator_test                             PASSED in 0.6s
//absl/strings:cord_rep_btree_reader_test                                PASSED in 0.4s
//absl/strings:cord_rep_btree_test                                       PASSED in 8.0s
//absl/strings:cord_rep_crc_test                                         PASSED in 0.2s
//absl/strings:cord_ring_reader_test                                     PASSED in 0.3s
//absl/strings:cord_ring_test                                            PASSED in 4.2s
//absl/strings:cord_test                                                 PASSED in 5.1s
//absl/strings:cordz_functions_test                                      PASSED in 0.2s
//absl/strings:cordz_handle_test                                         PASSED in 3.1s
//absl/strings:cordz_info_statistics_test                                PASSED in 1.1s
//absl/strings:cordz_info_test                                           PASSED in 0.2s
//absl/strings:cordz_sample_token_test                                   PASSED in 3.0s
//absl/strings:cordz_test                                                PASSED in 0.1s
//absl/strings:cordz_update_scope_test                                   PASSED in 0.2s
//absl/strings:cordz_update_tracker_test                                 PASSED in 0.2s
//absl/strings:damerau_levenshtein_distance_test                         PASSED in 0.0s
//absl/strings:escaping_test                                             PASSED in 0.1s
//absl/strings:match_test                                                PASSED in 0.1s
//absl/strings:memutil_test                                              PASSED in 0.1s
//absl/strings:numbers_test                                              PASSED in 8.7s
//absl/strings:ostringstream_benchmark                                   PASSED in 13.2s
//absl/strings:ostringstream_test                                        PASSED in 0.2s
//absl/strings:pow10_helper_test                                         PASSED in 0.3s
//absl/strings:resize_uninitialized_test                                 PASSED in 0.1s
//absl/strings:str_cat_test                                              PASSED in 1.7s
//absl/strings:str_format_arg_test                                       PASSED in 0.0s
//absl/strings:str_format_bind_test                                      PASSED in 0.2s
//absl/strings:str_format_checker_test                                   PASSED in 0.2s
//absl/strings:str_format_convert_test                                   PASSED in 9.3s
//absl/strings:str_format_extension_test                                 PASSED in 0.0s
//absl/strings:str_format_output_test                                    PASSED in 0.2s
//absl/strings:str_format_parser_test                                    PASSED in 0.2s
//absl/strings:str_format_test                                           PASSED in 1.0s
//absl/strings:str_join_test                                             PASSED in 0.2s
//absl/strings:str_replace_benchmark                                     PASSED in 2.2s
//absl/strings:str_replace_test                                          PASSED in 0.3s
//absl/strings:string_constant_test                                      PASSED in 0.1s
//absl/strings:string_view_test                                          PASSED in 1.6s
//absl/strings:strip_test                                                PASSED in 0.2s
//absl/strings:substitute_test                                           PASSED in 0.0s
//absl/strings:utf8_test                                                 PASSED in 0.2s
//absl/strings:ascii_benchmark                                           FAILED in 32.5s
  /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/ascii_benchmark/test.log
//absl/strings:charconv_benchmark                                        FAILED in 20.7s
  /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/charconv_benchmark/test.log
//absl/strings:escaping_benchmark                                        FAILED in 18.2s
  /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/escaping_benchmark/test.log
//absl/strings:memutil_benchmark                                         FAILED in 19.9s
  /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/memutil_benchmark/test.log
//absl/strings:numbers_benchmark                                         FAILED in 32.5s
  /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/numbers_benchmark/test.log
//absl/strings:str_cat_benchmark                                         FAILED in 18.5s
  /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/str_cat_benchmark/test.log
//absl/strings:str_join_benchmark                                        FAILED in 28.8s
  /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/str_join_benchmark/test.log
//absl/strings:str_split_benchmark                                       FAILED in 32.2s
  /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/str_split_benchmark/test.log
//absl/strings:str_split_test                                            FAILED in 1.5s
  /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/str_split_test/test.log
//absl/strings:string_view_benchmark                                     FAILED in 31.1s
  /home/ubuntu/.cache/bazel/_bazel_ubuntu/f71962201b4450ef22f4a161bf617507/execroot/com_google_absl/bazel-out/k8-fastbuild/testlogs/absl/strings/string_view_benchmark/test.log

Executed 59 out of 59 tests: 49 tests pass and 10 fail locally.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these are.
INFO: Build completed, 10 tests FAILED, 704 total actions
time="2022-11-16T22:14:30.460Z" level=info msg="sub-process exited" argo=true error="<nil>"
Error: exit status 3

  main log of a success build on v3.3.8, k8sapi executor
Cloning into 'abseil-cpp'...
Extracting Bazel installation...
Starting local Bazel server and connecting to it...
Loading:
Loading: 0 packages loaded
Loading: 24 packages loaded
    currently loading: absl
Analyzing: 454 targets (25 packages loaded, 0 targets configured)
Analyzing: 454 targets (54 packages loaded, 616 targets configured)
Analyzing: 454 targets (65 packages loaded, 1702 targets configured)
Analyzing: 454 targets (67 packages loaded, 2142 targets configured)
Analyzing: 454 targets (73 packages loaded, 2204 targets configured)
Analyzing: 454 targets (73 packages loaded, 2204 targets configured)
INFO: Analyzed 454 targets (74 packages loaded, 2561 targets configured).
INFO: Found 230 targets and 224 test targets...
[0 / 43] [Prepa] BazelWorkspaceStatusAction stable-status.txt
[21 / 78] Compiling googlemock/src/gmock-spec-builders.cc; 1s processwrapper-sandbox ... (8 actions, 7 running)
[35 / 83] Compiling googletest/src/gtest.cc; 1s processwrapper-sandbox ... (8 actions, 7 running)
[51 / 83] Compiling googletest/src/gtest.cc; 3s processwrapper-sandbox ... (8 actions, 7 running)
[96 / 174] Compiling absl/hash/hash_benchmark.cc; 1s processwrapper-sandbox ... (8 actions, 7 running)
[119 / 174] Compiling absl/strings/internal/str_format/arg.cc; 0s processwrapper-sandbox ... (8 actions, 7 running)
[148 / 174] Compiling src/benchmark.cc; 0s processwrapper-sandbox ... (8 actions, 7 running)
[229 / 262] Compiling absl/memory/memory_exception_safety_test.cc; 1s processwrapper-sandbox ... (8 actions, 7 running)
[346 / 366] 1 / 224 tests; Compiling absl/memory/memory_test.cc; 4s processwrapper-sandbox ... (8 actions, 7 running)
[426 / 441] 5 / 224 tests; Compiling absl/functional/any_invocable_test.cc; 6s processwrapper-sandbox ... (8 actions running)
[451 / 466] 9 / 224 tests; Compiling absl/functional/any_invocable_test.cc; 11s processwrapper-sandbox ... (8 actions running)
[518 / 533] 16 / 224 tests; Compiling absl/functional/any_invocable_test.cc; 16s processwrapper-sandbox ... (8 actions, 7 running)
[560 / 573] 20 / 224 tests; Compiling absl/functional/any_invocable_test.cc; 24s processwrapper-sandbox ... (8 actions, 7 running)
[619 / 631] 27 / 224 tests; Compiling absl/functional/any_invocable_test.cc; 31s processwrapper-sandbox ... (8 actions running)
[677 / 688] 33 / 224 tests; Compiling absl/functional/any_invocable_test.cc; 40s processwrapper-sandbox ... (8 actions running)
[754 / 763] 44 / 224 tests; Testing //absl/types:variant_benchmark; 24s processwrapper-sandbox ... (8 actions, 7 running)
[789 / 798] 49 / 224 tests; Testing //absl/types:variant_benchmark; 37s processwrapper-sandbox ... (8 actions running)
[871 / 879] 59 / 224 tests; Testing //absl/types:variant_benchmark; 51s processwrapper-sandbox ... (8 actions, 7 running)
[998 / 1,009] 76 / 224 tests; Testing //absl/strings:str_split_benchmark; 60s processwrapper-sandbox ... (8 actions, 7 running)
[1,143 / 1,157] 92 / 224 tests; Testing //absl/strings:string_view_benchmark; 64s processwrapper-sandbox ... (8 actions, 7 running)
[1,197 / 1,207] 100 / 224 tests; Testing //absl/strings:string_view_benchmark; 85s processwrapper-sandbox ... (8 actions running)
[1,313 / 1,325] 113 / 224 tests; Testing //absl/strings:string_view_benchmark; 111s processwrapper-sandbox ... (8 actions, 7 running)
[1,377 / 1,388] 122 / 224 tests; Testing //absl/time:time_benchmark; 78s processwrapper-sandbox ... (8 actions, 7 running)
[1,751 / 1,763] 163 / 224 tests; Testing //absl/time/internal/cctz:cctz_benchmark; 31s processwrapper-sandbox ... (8 actions, 7 running)
INFO: From Compiling absl/debugging/symbolize_test.cc:
/tmp/cca3l2Cz.s: Assembler messages:
/tmp/cca3l2Cz.s:1814: Warning: ignoring changed section attributes for .text
[2,116 / 2,130] 209 / 224 tests; Compiling absl/flags/flag_benchmark.cc; 63s processwrapper-sandbox ... (8 actions running)
[2,201 / 2,203] 223 / 224 tests; Compiling absl/container/btree_test.cc; 47s processwrapper-sandbox
INFO: Elapsed time: 372.528s, Critical Path: 137.87s
INFO: 2213 processes: 1011 internal, 1202 processwrapper-sandbox.
INFO: Build completed successfully, 2213 total actions
//absl/algorithm:algorithm_test                                          PASSED in 0.0s
//absl/algorithm:container_test                                          PASSED in 0.0s
//absl/base:atomic_hook_test                                             PASSED in 0.0s
//absl/base:bit_cast_test                                                PASSED in 0.0s
//absl/base:call_once_test                                               PASSED in 0.0s
//absl/base:config_test                                                  PASSED in 0.0s
//absl/base:endian_test                                                  PASSED in 0.6s
//absl/base:errno_saver_test                                             PASSED in 0.0s
//absl/base:exception_safety_testing_test                                PASSED in 0.0s
//absl/base:fast_type_id_test                                            PASSED in 0.1s
//absl/base:inline_variable_test                                         PASSED in 0.0s
//absl/base:invoke_test                                                  PASSED in 0.0s
//absl/base:log_severity_test                                            PASSED in 0.1s
//absl/base:low_level_alloc_test                                         PASSED in 3.7s
//absl/base:optimization_test                                            PASSED in 0.0s
//absl/base:prefetch_test                                                PASSED in 0.0s
//absl/base:raw_logging_test                                             PASSED in 0.1s
//absl/base:scoped_set_env_test                                          PASSED in 0.0s
//absl/base:spinlock_test                                                PASSED in 0.9s
//absl/base:strerror_test                                                PASSED in 0.1s
//absl/base:sysinfo_test                                                 PASSED in 0.1s
//absl/base:thread_identity_benchmark                                    PASSED in 1.9s
//absl/base:thread_identity_test                                         PASSED in 0.1s
//absl/base:throw_delegate_test                                          PASSED in 0.0s
//absl/base:unique_small_name_test                                       PASSED in 0.0s
//absl/cleanup:cleanup_test                                              PASSED in 0.0s
//absl/container:common_policy_traits_test                               PASSED in 0.0s
//absl/container:compressed_tuple_test                                   PASSED in 0.0s
//absl/container:container_memory_test                                   PASSED in 0.0s
//absl/container:fixed_array_exception_safety_test                       PASSED in 0.2s
//absl/container:fixed_array_test                                        PASSED in 3.2s
//absl/container:flat_hash_map_test                                      PASSED in 0.8s
//absl/container:flat_hash_set_test                                      PASSED in 0.1s
//absl/container:hash_function_defaults_test                             PASSED in 4.4s
//absl/container:hash_policy_testing_test                                PASSED in 0.0s
//absl/container:hash_policy_traits_test                                 PASSED in 0.0s
//absl/container:hashtablez_sampler_test                                 PASSED in 3.1s
//absl/container:inlined_vector_exception_safety_test                    PASSED in 0.5s
//absl/container:inlined_vector_test                                     PASSED in 0.2s
//absl/container:layout_test                                             PASSED in 0.0s
//absl/container:node_hash_map_test                                      PASSED in 0.1s
//absl/container:node_hash_set_test                                      PASSED in 0.1s
//absl/container:node_slot_policy_test                                   PASSED in 0.0s
//absl/container:raw_hash_set_allocator_test                             PASSED in 0.0s
//absl/container:raw_hash_set_test                                       PASSED in 3.6s
//absl/container:sample_element_size_test                                PASSED in 0.0s
//absl/container:test_instance_tracker_test                              PASSED in 0.0s
//absl/container:unordered_map_test                                      PASSED in 0.3s
//absl/container:unordered_set_test                                      PASSED in 0.1s
//absl/crc:crc32c_test                                                   PASSED in 0.1s
//absl/crc:non_temporal_memcpy_test                                      PASSED in 0.2s
//absl/debugging:demangle_test                                           PASSED in 0.0s
//absl/debugging:failure_signal_handler_test                             PASSED in 0.3s
//absl/debugging:leak_check_test                                         PASSED in 0.0s
//absl/debugging:stack_consumption_test                                  PASSED in 0.0s
//absl/debugging:symbolize_test                                          PASSED in 0.1s
//absl/flags:commandlineflag_test                                        PASSED in 0.1s
//absl/flags:config_test                                                 PASSED in 0.0s
//absl/flags:flag_test                                                   PASSED in 1.1s
//absl/flags:marshalling_test                                            PASSED in 0.0s
//absl/flags:parse_test                                                  PASSED in 0.1s
//absl/flags:path_util_test                                              PASSED in 0.0s
//absl/flags:program_name_test                                           PASSED in 0.1s
//absl/flags:reflection_test                                             PASSED in 0.0s
//absl/flags:usage_config_test                                           PASSED in 0.0s
//absl/flags:usage_test                                                  PASSED in 0.1s
//absl/functional:any_invocable_test                                     PASSED in 0.4s
//absl/functional:bind_front_test                                        PASSED in 0.0s
//absl/functional:function_ref_test                                      PASSED in 0.1s
//absl/functional:function_type_benchmark                                PASSED in 13.4s
//absl/hash:city_test                                                    PASSED in 0.1s
//absl/hash:hash_test                                                    PASSED in 0.2s
//absl/hash:low_level_hash_test                                          PASSED in 0.3s
//absl/log:basic_log_test                                                PASSED in 0.2s
//absl/log:check_test                                                    PASSED in 0.4s
//absl/log:die_if_null_test                                              PASSED in 0.1s
//absl/log:flags_test                                                    PASSED in 0.1s
//absl/log:globals_test                                                  PASSED in 0.0s
//absl/log:log_entry_test                                                PASSED in 0.0s
//absl/log:log_format_test                                               PASSED in 0.1s
//absl/log:log_macro_hygiene_test                                        PASSED in 0.2s
//absl/log:log_modifier_methods_test                                     PASSED in 0.1s
//absl/log:log_sink_test                                                 PASSED in 0.3s
//absl/log:log_streamer_test                                             PASSED in 0.1s
//absl/log:scoped_mock_log_test                                          PASSED in 0.1s
//absl/log:stripping_test                                                PASSED in 0.0s
//absl/log/internal:stderr_log_sink_test                                 PASSED in 0.1s
//absl/memory:memory_exception_safety_test                               PASSED in 0.0s
//absl/memory:memory_test                                                PASSED in 0.0s
//absl/meta:type_traits_test                                             PASSED in 0.0s
//absl/numeric:bits_test                                                 PASSED in 0.0s
//absl/numeric:int128_benchmark                                          PASSED in 34.5s
//absl/numeric:int128_test                                               PASSED in 0.4s
//absl/profiling:exponential_biased_test                                 PASSED in 0.5s
//absl/profiling:periodic_sampler_test                                   PASSED in 0.0s
//absl/profiling:sample_recorder_test                                    PASSED in 3.2s
//absl/random:bernoulli_distribution_test                                PASSED in 14.2s
//absl/random:beta_distribution_test                                     PASSED in 28.4s
//absl/random:bit_gen_ref_test                                           PASSED in 0.4s
//absl/random:discrete_distribution_test                                 PASSED in 0.0s
//absl/random:distributions_test                                         PASSED in 1.7s
//absl/random:examples_test                                              PASSED in 0.0s
//absl/random:exponential_distribution_test                              PASSED in 2.4s
//absl/random:gaussian_distribution_test                                 PASSED in 8.1s
//absl/random:generators_test                                            PASSED in 0.0s
//absl/random:log_uniform_int_distribution_test                          PASSED in 0.1s
//absl/random:mock_distributions_test                                    PASSED in 0.0s
//absl/random:mocking_bit_gen_test                                       PASSED in 0.1s
//absl/random:poisson_distribution_test                                  PASSED in 27.9s
//absl/random:seed_sequences_test                                        PASSED in 0.1s
//absl/random:uniform_int_distribution_test                              PASSED in 1.3s
//absl/random:uniform_real_distribution_test                             PASSED in 1.1s
//absl/random:zipf_distribution_test                                     PASSED in 0.1s
//absl/random/internal:chi_square_test                                   PASSED in 0.1s
//absl/random/internal:distribution_test_util_test                       PASSED in 0.8s
//absl/random/internal:explicit_seed_seq_test                            PASSED in 0.1s
//absl/random/internal:fast_uniform_bits_test                            PASSED in 0.0s
//absl/random/internal:fastmath_test                                     PASSED in 0.1s
//absl/random/internal:generate_real_test                                PASSED in 0.0s
//absl/random/internal:iostream_state_saver_test                         PASSED in 0.3s
//absl/random/internal:nanobenchmark_test                                PASSED in 12.0s
//absl/random/internal:nonsecure_base_test                               PASSED in 0.0s
//absl/random/internal:pcg_engine_test                                   PASSED in 0.1s
//absl/random/internal:pool_urbg_test                                    PASSED in 0.0s
//absl/random/internal:randen_benchmarks                                 PASSED in 31.8s
//absl/random/internal:randen_engine_test                                PASSED in 7.8s
//absl/random/internal:randen_hwaes_test                                 PASSED in 0.0s
//absl/random/internal:randen_slow_test                                  PASSED in 0.0s
//absl/random/internal:randen_test                                       PASSED in 0.0s
//absl/random/internal:salted_seed_seq_test                              PASSED in 0.0s
//absl/random/internal:seed_material_test                                PASSED in 0.1s
//absl/random/internal:traits_test                                       PASSED in 0.0s
//absl/random/internal:uniform_helper_test                               PASSED in 0.1s
//absl/random/internal:wide_multiply_test                                PASSED in 0.1s
//absl/status:status_test                                                PASSED in 0.1s
//absl/status:statusor_test                                              PASSED in 0.1s
//absl/strings:ascii_benchmark                                           PASSED in 42.0s
//absl/strings:ascii_test                                                PASSED in 0.0s
//absl/strings:char_map_benchmark                                        PASSED in 0.9s
//absl/strings:char_map_test                                             PASSED in 0.1s
//absl/strings:charconv_benchmark                                        PASSED in 19.9s
//absl/strings:charconv_bigint_test                                      PASSED in 0.2s
//absl/strings:charconv_parse_test                                       PASSED in 0.0s
//absl/strings:charconv_test                                             PASSED in 13.4s
//absl/strings:cord_buffer_test                                          PASSED in 0.0s
//absl/strings:cord_data_edge_test                                       PASSED in 0.4s
//absl/strings:cord_rep_btree_navigator_test                             PASSED in 0.4s
//absl/strings:cord_rep_btree_reader_test                                PASSED in 0.2s
//absl/strings:cord_rep_btree_test                                       PASSED in 10.3s
//absl/strings:cord_rep_crc_test                                         PASSED in 0.2s
//absl/strings:cord_ring_reader_test                                     PASSED in 0.4s
//absl/strings:cord_ring_test                                            PASSED in 9.7s
//absl/strings:cord_test                                                 PASSED in 6.5s
//absl/strings:cordz_functions_test                                      PASSED in 0.0s
//absl/strings:cordz_handle_test                                         PASSED in 3.0s
//absl/strings:cordz_info_statistics_test                                PASSED in 1.0s
//absl/strings:cordz_info_test                                           PASSED in 0.1s
//absl/strings:cordz_sample_token_test                                   PASSED in 3.0s
//absl/strings:cordz_test                                                PASSED in 0.3s
//absl/strings:cordz_update_scope_test                                   PASSED in 0.0s
//absl/strings:cordz_update_tracker_test                                 PASSED in 0.0s
//absl/strings:damerau_levenshtein_distance_test                         PASSED in 0.1s
//absl/strings:escaping_benchmark                                        PASSED in 18.3s
//absl/strings:escaping_test                                             PASSED in 0.1s
//absl/strings:match_test                                                PASSED in 0.1s
//absl/strings:memutil_benchmark                                         PASSED in 20.2s
//absl/strings:memutil_test                                              PASSED in 0.0s
//absl/strings:numbers_benchmark                                         PASSED in 86.4s
//absl/strings:numbers_test                                              PASSED in 11.1s
//absl/strings:ostringstream_benchmark                                   PASSED in 14.5s
//absl/strings:ostringstream_test                                        PASSED in 0.0s
//absl/strings:pow10_helper_test                                         PASSED in 0.1s
//absl/strings:resize_uninitialized_test                                 PASSED in 0.0s
//absl/strings:str_cat_benchmark                                         PASSED in 17.6s
//absl/strings:str_cat_test                                              PASSED in 1.2s
//absl/strings:str_format_arg_test                                       PASSED in 0.0s
//absl/strings:str_format_bind_test                                      PASSED in 0.1s
//absl/strings:str_format_checker_test                                   PASSED in 0.0s
//absl/strings:str_format_convert_test                                   PASSED in 12.9s
//absl/strings:str_format_extension_test                                 PASSED in 0.0s
//absl/strings:str_format_output_test                                    PASSED in 0.0s
//absl/strings:str_format_parser_test                                    PASSED in 0.0s
//absl/strings:str_format_test                                           PASSED in 1.5s
//absl/strings:str_join_benchmark                                        PASSED in 29.8s
//absl/strings:str_join_test                                             PASSED in 0.0s
//absl/strings:str_replace_benchmark                                     PASSED in 2.0s
//absl/strings:str_replace_test                                          PASSED in 0.0s
//absl/strings:str_split_benchmark                                       PASSED in 69.8s
//absl/strings:str_split_test                                            PASSED in 1.8s
//absl/strings:string_constant_test                                      PASSED in 0.0s
//absl/strings:string_view_benchmark                                     PASSED in 135.7s
//absl/strings:string_view_test                                          PASSED in 1.7s
//absl/strings:strip_test                                                PASSED in 0.0s
//absl/strings:substitute_test                                           PASSED in 0.1s
//absl/strings:utf8_test                                                 PASSED in 0.1s
//absl/synchronization:barrier_test                                      PASSED in 1.0s
//absl/synchronization:blocking_counter_test                             PASSED in 1.0s
//absl/synchronization:graphcycles_benchmark                             PASSED in 15.6s
//absl/synchronization:graphcycles_test                                  PASSED in 4.1s
//absl/synchronization:lifetime_test                                     PASSED in 0.0s
//absl/synchronization:notification_test                                 PASSED in 0.2s
//absl/synchronization:per_thread_sem_test                               PASSED in 4.5s
//absl/time:flag_test                                                    PASSED in 0.0s
//absl/time:time_benchmark                                               PASSED in 91.0s
//absl/time:time_test                                                    PASSED in 7.2s
//absl/time/internal/cctz:cctz_benchmark                                 PASSED in 33.1s
//absl/time/internal/cctz:civil_time_test                                PASSED in 0.1s
//absl/time/internal/cctz:time_zone_format_test                          PASSED in 0.5s
//absl/time/internal/cctz:time_zone_lookup_test                          PASSED in 3.5s
//absl/types:any_exception_safety_test                                   PASSED in 0.0s
//absl/types:any_test                                                    PASSED in 0.0s
//absl/types:compare_test                                                PASSED in 0.1s
//absl/types:conformance_testing_test                                    PASSED in 0.1s
//absl/types:optional_exception_safety_test                              PASSED in 0.0s
//absl/types:optional_test                                               PASSED in 0.1s
//absl/types:span_test                                                   PASSED in 0.1s
//absl/types:variant_benchmark                                           PASSED in 51.4s
//absl/types:variant_exception_safety_test                               PASSED in 0.0s
//absl/types:variant_test                                                PASSED in 0.1s
//absl/utility:utility_test                                              PASSED in 0.0s
//absl/crc:crc_memcpy_test                                               PASSED in 0.3s
  Stats over 3 runs: max = 0.3s, min = 0.2s, avg = 0.2s, dev = 0.0s
//absl/container:btree_test                                              PASSED in 32.7s
  Stats over 10 runs: max = 32.7s, min = 17.4s, avg = 23.5s, dev = 4.7s
//absl/synchronization:mutex_test                                        PASSED in 13.6s
  Stats over 25 runs: max = 13.6s, min = 1.0s, avg = 5.0s, dev = 3.7s
//absl/flags:sequence_lock_test                                          PASSED in 0.1s
  Stats over 31 runs: max = 0.1s, min = 0.1s, avg = 0.1s, dev = 0.0s

Executed 224 out of 224 tests: 224 tests pass.
There were tests whose specified size is too big. Use the --test_verbose_timeout_warnings command line option to see which ones these are.
INFO: Build completed successfully, 2213 total actions

Version
v3.4.1, v3.4.2
Paste a small workflow that reproduces the issue. We must be able to run the workflow; don't enter a workflows that uses private images.
metadata:
  name: bazel-test
spec:
  arguments:
    parameters:
      - name: message
        value: hello argo
  entrypoint: argosay
  templates:
    - name: argosay
      inputs:
        parameters:
          - name: message
            value: '{{workflow.parameters.message}}'
      script:
        name: main
        image: gcr.io/bazel-public/bazel:5.1.1
        command: [bash]
        source: |
          git clone https://github.com/abseil/abseil-cpp.git && cd abseil-cpp/
          bazel test //absl/strings/... --cxxopt="-std=c++14"

Logs from the workflow controller
kubectl logs -n argo deploy/workflow-controller | grep ${workflow}
Logs from in your workflow's wait container
time="2022-11-16T22:12:43.105Z" level=info msg="Starting Workflow Executor" version=v3.4.1
time="2022-11-16T22:12:43.109Z" level=info msg="Using executor retry strategy" Duration=1s Factor=1.6 Jitter=0.5 Steps=5
time="2022-11-16T22:12:43.109Z" level=info msg="Executor initialized" deadline="0001-01-01 00:00:00 +0000 UTC" includeScriptOutput=false namespace=map
 podName=bazel-test template="{\"name\":\"argosay\",\"inputs\":{\"parameters\":[{\"name\":\"message\",\"value\":\"hello argo\"}]},\"outputs\":{},\"met
adata\":{},\"script\":{\"name\":\"main\",\"image\":\"gcr.io/bazel-public/bazel:5.1.1\",\"command\":[\"bash\"],\"resources\":{},\"source\":\"git clone
https://github.com/abseil/abseil-cpp.git \\u0026\\u0026 cd abseil-cpp/\\nbazel test //absl/strings/... --cxxopt=\\\"-std=c++14\\\"\\n\"},\"archiveLoca
tion\":{\"archiveLogs\":true,\"s3\":{\"endpoint\":\"argo-workflows-minio.argo-workflows:9000\",\"bucket\":\"artifact\",\"insecure\":true,\"accessKeySe
cret\":{\"name\":\"argo-workflows-minio\",\"key\":\"accesskey\"},\"secretKeySecret\":{\"name\":\"argo-workflows-minio\",\"key\":\"secretkey\"},\"key\"
:\"map/20221116/bazel-test/bazel-test\"}}}" version="&Version{Version:v3.4.1,BuildDate:2022-10-01T15:03:42Z,GitCommit:0546fef0b096d84c9e3362d2b241614e
743ebe97,GitTag:v3.4.1,GitTreeState:clean,GoVersion:go1.18.6,Compiler:gc,Platform:linux/amd64,}"
time="2022-11-16T22:12:43.188Z" level=info msg="Starting deadline monitor"
time="2022-11-16T22:14:31.256Z" level=info msg="Main container completed" error="<nil>"
time="2022-11-16T22:14:31.256Z" level=info msg="No Script output reference in workflow. Capturing script output ignored"
time="2022-11-16T22:14:31.256Z" level=info msg="No output parameters"
time="2022-11-16T22:14:31.256Z" level=info msg="No output artifacts"
time="2022-11-16T22:14:31.257Z" level=info msg="S3 Save path: /tmp/argo/outputs/logs/main.log, key: map/20221116/bazel-test/bazel-test/main.log"
time="2022-11-16T22:14:31.257Z" level=info msg="Creating minio client using static credentials" endpoint="argo-workflows-minio.argo-workflows:9000"
time="2022-11-16T22:14:31.257Z" level=info msg="Saving file to s3" bucket=artifact endpoint="argo-workflows-minio.argo-workflows:9000" key=map/20221116/bazel-test/bazel-test/main.log path=/tmp/argo/outputs/logs/main.log
time="2022-11-16T22:14:31.275Z" level=info msg="Save artifact" artifactName=main-logs duration=18.077644ms error="<nil>" key=map/20221116/bazel-test/bazel-test/main.log
time="2022-11-16T22:14:31.275Z" level=info msg="not deleting local artifact" localArtPath=/tmp/argo/outputs/logs/main.log
time="2022-11-16T22:14:31.275Z" level=info msg="Successfully saved file: /tmp/argo/outputs/logs/main.log"
time="2022-11-16T22:14:31.286Z" level=info msg="Create workflowtaskresults 201"
time="2022-11-16T22:14:31.287Z" level=info msg="Deadline monitor stopped"
time="2022-11-16T22:14:31.287Z" level=info msg="Alloc=7201 TotalAlloc=13372 Sys=29650 NumGC=4 Goroutines=9"

Hazel ran for 2h30m. Do you have its logs to explain what it was doing?

I modified the workflow to only compile targets under //abseil/strings and I updated the log from main container.
Simply put, bazel raises sub-processes to compile code and run test binaries. My wild guess is that bazel and emissary has conflict on sub-process handling.

It maybe that the sub-process exits is a strange way. We did address as similar issue recently with Python, which makes we want to ask you to double check to see if this fails on latest tag.

I just tested with the latest release version (3.4.4) and the problem still exists.


fix(TDI-44903): remove fileio and services

What is the current behavior? (You can also link to an open issue here)
https://jira.talendforge.org/browse/TDI-44903
What is the new behavior?
Modules fileio and services were removed from master branch.
Please check if the PR fulfills these requirements

[ ] The commit message follows Talend standard
[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features) ?
[ ] The code coverage on new code >75%
[ ] The new code does not introduce new technical issues (sonar / eslint)

What kind of change does this PR introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build / CI related changes
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[ ] Yes
[ ] No

If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information:

Pull request test result: success :star:


Android:When i am using stickyHeaderIndices and pull to refresh functionality , the loading spinner is displaying backside of stickyElementContent not above of stickyIndexElement in FlashList

Current behavior

Expected behavior

To Reproduce

Platform:

[ ] iOS
[x] Android

Environment

x.y.z

1

The workaround I did was conditionally add the stickyHeaderIndices based on whether refreshing is happening or not. It's a bit delayed in rendering but it does work.
https://github.com/Shopify/flash-list/assets/889564/e3a7ee43-c3ca-4e6c-a4b8-5e5ad19125ee

+1

+1

Update
Instead of my previously mentioned approach, I used the feed scroll position to turn on or off the sticky headers. When the feed is at the top I don't render the sticky headers. This method allows the feed to work as expected on Android until Shopify fixes the issue.
  const [isFeedAtTop, setIsFeedAtTop] = useState(true);

  const handleScroll = useCallback((event) => {
    if (Platform.OS === 'android') {
      const { contentOffset } = event.nativeEvent;
      if (contentOffset.y <= 0) {
        setIsFeedAtTop(true);
      } else {
        setIsFeedAtTop(false);
      }
    }
  }, []);

  // * This is a hack to fix the issue where the sticky header is blocking the refresh indicator on Android
  // ! Bug: https://github.com/Shopify/flash-list/issues/885
  const returnStickyHeaderIndices = useCallback(() => {
    if (Platform.OS === 'ios') {
      return stickyHeaderIndices;
    }
    if (Platform.OS === 'android') {
      return !isFeedAtTop ? stickyHeaderIndices : [];
    }
  }, [isFeedAtTop, stickyHeaderIndices]);

    <FlashList
      ref={notificationFeedRef}
      onScroll={handleScroll}
      data={formattedNotifications}
      renderItem={renderItem}
      ListEmptyComponent={renderListEmptyComponent}
      stickyHeaderIndices={returnStickyHeaderIndices()}
      showsVerticalScrollIndicator
      getItemType={(item) => (typeof item === 'string' ? 'sectionHeader' : 'row')}
      estimatedItemSize={100}
      refreshing={refreshing}
      onRefresh={refreshNotifications}
      onEndReached={fetchNextNotifications}
      ListFooterComponent={
        loadingMore && (
          <View marginV-30>
            <ActivityIndicator color={Colors.primaryColor} />
          </View>
        )
      }
    />


Cannot deploy as Web APP

Following the instructions and deployed successfully as "Function APP". How do I use it as Web APP?
Thank you!

Solved, the Web APP is next to the function app.


Fix API path in bigtable GetCluster method

Add missing path separator.
Fixes #983

Hello - thanks for your contribution! We'd love to review it but unfortunately, although we're working on getting a bot to help us accept contributions from github, we currently only use Gerrit. Would you mind submitting this change there?
You can follow the instructions for getting set up listed in our CONTRIBUTING.md.

@jadekler thanks for the heads up. Will do.

Thank you very much!


No test were provided or constant time out.

On kata Weight for Weight(5kyu) I constatly get a timeout despite the server status is showing everything is ok, as well as when I press "Run Tests" the following(screenshot) comes up

I thought it mind be just one day issues on 14/06/2016, today I tried again and met the same issues.
P.S I am using C#.

Faced exactly the same problem with another kata, now I might consider that something is wrong with the server.

Faced problem for different js kata.
Retry to push solution helped.

The same on this kata https://www.codewars.com/kata/526a569ca578d7e6e300034e/train/javascript

Had this problem with several kata and multiple languages.
One of which is https://www.codewars.com/kata/540c33513b6532cd58000259/train/clojure
I think it's the random tests might be too much for the server.

For js kata:
Now occurs simultaneoulsly with 'Unknown error'.
Button repush don't help, page refresh don't help.
';' in the end of the line helped many times.

With ';' at the end of the line, issue occued, but button repush helped.

I guess it is related to #394.

Today this https://www.codewars.com/kata/526a569ca578d7e6e300034e/train/javascript cannot be loaded at all.


typos - temperatue

When I was trying the bmp180_i2c example I see this typo, should be temperature.

Fixed, thanks!


Fixed marshalling base members from ref type to value type.

If a value type class inherited from a ref type base then there were errors due to scope of methods and   properties in C# and it was not possible in C++/CLI. Fixed these.

@ddobrev @tritao Please review and merge it!

Closing as https://github.com/mono/CppSharp/pull/518 is a superset of this.


Issue with CloudWatch VPC Endpoint Configuration

I ran into this issue while attempting to the use the option for the cloudwatch VPC endpoint in our nework module. Example setting:
vpc_endpoint_config = {
    s3         = true
    kms        = true
    cloudwatch = true
    elb        = true
    dynamodb   = true
    ec2        = false
    sns        = true
    sqs        = true
  }

Everything works as expected, except for how the underlying CP module works

Pulls in the default SG for a VPC and assigns it to the VPC endpoint
We aren't exposing the configuration options that are needed by the CP module to properly configure
https://github.com/cloudposse/terraform-aws-vpc/blob/2.1.0/modules/vpc-endpoints/main.tf#L27

# Because security group ID may not be known at plan time, we cannot use it as a key
  security_group_associations_list = flatten([for k, v in var.interface_vpc_endpoints : [
    for i, s in v.security_group_ids : {
      key               = "${k}[${i}]"
      index             = i
      interface         = k
      security_group_id = s
    }
  ]])

  security_group_associations_map = { for v in local.security_group_associations_list : v.key => v }

For the VPC endpoints, we can test that
Task stopped at: 2023-10-09T20:15:54.334Z
ResourceInitializationError: failed to validate logger args: create stream has been retried 7 times: failed to create Cloudwatch log stream: RequestError: send request failed caused by: Post "https://logs.us-east-1.amazonaws.com/": dial tcp: lookup logs.us-east-1.amazonaws.com on <IP_ADDRESS>:53: no such host : exit status 1

Once the VPC endpoints are up, they will resolve to IPs in the CIDR range of the VPC
Expected Behaviour 💯
For the ARC IaC reference architecture, I am fine with creating a VPC endpoint SG that is open to the VPC cidr block

This issue is closed because Module has been refactored


Modified how parameters are processed in templates and changed exection logic

Multiple components implemented

Changed how template parameters are processed
Changed how steps are executed
Added support for skipping steps

@ishuverma please review

Will track in #35


Merge develop branch to v2 branch

Codecov Report

Merging #2510 (c04e9fb) into v2 (4e6f207) will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##               v2    #2510      +/-   ##
==========================================
- Coverage   97.21%   97.17%   -0.04%
==========================================
  Files          57       57
  Lines       11061    11061
==========================================
- Hits        10753    10749       -4
- Misses        308      312       +4

Impacted Files
Coverage Δ

botocore/httpsession.py
92.82% <0.00%> (-0.45%)
:arrow_down:

botocore/utils.py
96.85% <0.00%> (-0.16%)
:arrow_down:

botocore/credentials.py
98.35% <0.00%> (-0.11%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 4e6f207...c04e9fb. Read the comment docs.


Patient bio data info not loading on profile view

After updates made to the match fhir sdk update + uploading fhir resources PR , patient bio data is not being displayed on the profile view.

@rkodev assist in creating a ticket for the search by identifier implementation

@Rkareko We have an issue that is listed in search by token types in Android FHIR SDK
We can also add search/find by Resource ID

Issue created for Find Resource by Id

Able to load the patient bio data by getting the info from the patient list as done on this PR
An ideal way is by fetching the patient record using the id. When that functionality is implemented in the SDK, the implementation on FHIR CORE will be updated.


Misc improvements

I'm writing a few notes here that I intend to address ASAP

Synchronising .ipynb and .py paired files
I assume the reason for having both formats is to allow people to easily use the .py version instead and not have the bother of notebooks. These should be made identical and synchronised automatically. It's possible to do this using jupytext and pre-commit, and can be done during a Pull Request (PR)  without adding anything to your local development environment. This means that you can just edit the .ipynb file and push that change, and I'll add a CI service that updates the .py version automatically (or the other way round).
I've added this in https://github.com/IAGA-VMOD/IGRF14eval/pull/3, with some explanation
Protect the main branch and enforce changes to come through PR
That's the "right" way to collaborate on a git repo, firstly to allow a review before merging, and secondly to add things like the above automation.
Building a site that displays the executed notebooks (like this) - uses jupyterbook
The problem this solves is that when someone supplies their .cof files the notebooks are not updated with the new figures. The site is built automatically to provide those (and test that the code actually works if we change it).
See https://github.com/IAGA-VMOD/IGRF14eval/pull/4
Improve the code/notebooks
Of course a lot can be done here, but better to stick with what works already (though it depends what more we want to do for the candidates evaluations). I'll anyway make some tweaks to the notebooks to fix how they appear in the jupyterbook site.
Contribution guide - see https://github.com/IAGA-VMOD/IGRF14eval/issues/1

Excellent - I figured there must be some easy way to keep them in sync. One thing that I wanted to add was a couple of lines of code to truncate any g/h values that were more than 2 decimal places in the load-in-file stage.
Of course - let's protect the main branch now (the sacred timeline!)
OK - how do you build the website like that. I see the advantage of doing that and then produces the images automatically.
Yes - first improvement can be checking 2dp truncation. Other changes are welcome
As noted in #1 Clemens is going to start that.

jupytext - Ok and done. It's my first time using it properly - hopefully there'll be no bad surprises!
main branch now protected (the rules are configured here)
The way I'm building the website is less standard and a bit complex to understand. I'll try document it some more but the plan is that it should just happen in the background and not get in the way. We can also expand it a bit as a nice way to display the process of IGRF candidates evaluation and supplementary material for the publication.


Allow running of supervisord as a non-root user

If running supervisord as another user, it should be possible to change the configuration and look at log files. I change the ownership for supervisor.d and log directory.

I think the problem here is that this would give the runtime user access to change it's own configuration by default. Given the expectation is you'll use puppet to deploy your chosen configuration it would be better practice to now allow this user to change things.
Perhaps it simply needs some additional parameters for this use case.
I have noticed that the permissions on the log directory are incorrect and should be 0755 which might resolve your log viewing issue?

Hello!
In this case, what is the meaning of $user class parameter? BTW, I tried to set a non-root user to run supervisord (using $user parameter) but it is seems that startup scripts were not designed to be safely called for non-root user - the status endpoint will not return success. So puppet is spawning an unlimited number of supervisord daemons...

I am going to close this since it is not relevant anymore


Refine bench

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

Project coverage is 97.31%. Comparing base (25fbeda) to head (82495ab).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #352   +/-   ##
=======================================
  Coverage   97.31%   97.31%
=======================================
  Files         153      153
  Lines        9448     9448
=======================================
  Hits         9194     9194
  Misses        254      254

Flag
Coverage Δ

97.31% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.


Fix stuck navigation

Some details about why we where getting stuck: https://github.com/Expensify/App/issues/15725#issuecomment-1460702183
Details
I noticed that just by calling User.deleteContactMethod(contactMethod) we where being navigated back to ROUTES.SETTINGS_CONTACT_METHODS. I'm assuming it is because the contact method is removed from Onyx.
Removing Navigation.navigate(ROUTES.SETTINGS_CONTACT_METHODS) seems to fix the bug.
Fixed Issues
$ https://github.com/Expensify/App/issues/15725
PROPOSAL: GH_LINK_ISSUE(COMMENT)
Tests

Login in NewDot and go to /settings/profile/contact-methods
Add a phone number (no need to validate)
You should be taken back to the "Contact methods" page:

Click on your phone number contact method and then delete it

Verify that you are taken back to the "Contact methods" page
Verify that you can tap in any of the menu entries and you get navigated

[x] Verify that no errors appear in the JS console

Offline tests

QA Steps

Login in NewDot and go to /settings/profile/contact-methods
Add a phone number (no need to validate)
You should be taken back to the "Contact methods" page:

Click on your phone number contact method and then delete it

Verify that you are taken back to the "Contact methods" page
Verify that you can tap in any of the menu entries and you get navigated

[ ] Verify that no errors appear in the JS console

PR Author Checklist

[ ] I linked the correct issue in the ### Fixed Issues section above
[ ] I wrote clear testing steps that cover the changes made in this PR

[ ] I added steps for local testing in the Tests section
[ ] I added steps for the expected offline behavior in the Offline steps section
[ ] I added steps for Staging and/or Production testing in the QA steps section
[ ] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[ ] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[ ] I included screenshots or videos for tests on all platforms
[ ] I ran the tests on all platforms & verified they passed on:

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[ ] MacOS / Chrome / Safari
[ ] MacOS / Desktop

[ ] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[ ] I followed proper code patterns (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[ ] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is correct English and approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I followed the guidelines as stated in the Review Guidelines
[ ] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] I verified that if a function's arguments changed that all usages have also been updated correctly
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(themeColors.componentBG)

[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR author checklist, including those that don't apply to this PR.

Screenshots/Videos

Web

Mobile Web - Chrome

Mobile Web - Safari

Desktop

iOS

Android

@parasharrajat @neil-marcellini One of you needs to copy/paste the Reviewer Checklist from here into a new comment on this PR and complete it. If you have the K2 extension, you can simply click: [this button]

cc @roryabraham @parasharrajat @syedsaroshfarrukhdot In case you have a better understanding of these navigation transitions and can say if this makes sense or not 🙏

Making it a draft again because I noticed that this has an unwanted effect: if you are offline, successData doesn't remove the contact method from Onyx and you are not navigated back until you come back offline.
Without this PR, when offline, we land here:

With this PR, when offline, we land here:

The code navigating automatically to the main contacts methods page when the contact method is not found is here:
https://github.com/Expensify/App/blob/4237497d7e803acbe52533d12e0b46c6071ee4b6/src/pages/settings/Profile/Contacts/ContactMethodDetailsPage.js#L146-L149
So the problem seems to be cause by this double navigation, I see two options for now:

Don't navigate if the contact method is not found, but show some page mentioning that the information was not found, or
Try to fix ScreenWrapper and Navigation.isNavigating stuff so it doesn't get stuck if we navigate twice.

Update:

We now redirect in componentDidUpdate if the login data is not found (instead of in render())
I added a loading indicator in render if the login information is not available.

This seems to fix the bug correctly without making the offline experience worse.

Which one is the correct behavior?

The one on top (edited the comment to make it more clear)

If ScreenWrapper is getting unmounted before we can set the flags then we should move the logic of setting Navigation.setIsNavigating(value) to the parent component which is never mounted.
I haven't validated the root cause but I believe ya 😉
We can move this setup to top-level navigators in AuthScreens.js & PublicScreens.js.

Oh, that sounds like an interest approach, I can give it a try.
Besides that, maybe we should avoid navigating during rendering anyway. What do you think about that? I feel like the rendering function should be exclusively about rendering (showing data) and not triggering side-effects.

@parasharrajat about this suggestion https://github.com/Expensify/App/pull/15751#issuecomment-1460799962
The difficulty I see is that ScreenWrapper has this state.didScreenTransitionEnd that changes on 'transitionEnd'.
If we moved the event listening part to higher in the tree to AuthScreens.js & PublicScreens.js, I'm not sure how would ScreenWrapper get notified when the transition ends. ScreenWrapper is used in many places, so drilling a state like that from AuthScreens.js & PublicScreens.js until it gets to ScreenWrapper sounds like a looot of work. The other option would be to keep this state in Onyx so we can access it easily in ScreenWrapper, but I'm not sure if there could be some bad consequence of using Onyx as storage here. Do you have some thoughts on that?

The PR adding the ContactMehodDetailsPage got reverted here: https://github.com/Expensify/App/pull/15761

This seems to work quite well, I don't think I've ever noticed the loading indicator, have you @aldo-expensify ?

FYI I re-added pretty much everything from my old PR into this one: https://github.com/Expensify/App/pull/15777 just to see if I could reproduce the bug and I haven't been able to, would either of y'all (@aldo-expensify @parasharrajat ) mind trying to reproduce on that PR?

FYI I re-added pretty much everything from my old PR into this one: #15777 just to see if I could reproduce the bug and I haven't been able to, would either of y'all (@aldo-expensify @parasharrajat ) mind trying to reproduce on that PR?

I'll give it a try

I think we can keep the transitionEnd event handler in screenWrapper component which is responsible for didTransitionEnd. I am only thinking to move the isNavigaying flag setter to high level. Thus both level the AuthScreens and screenWrapper will have event listener.

I see, that should be much easier, I think we should do that.

@aldo-expensify hope you don't mind, but I merged main to get up to date with removing all the related pages (from the revert PR https://github.com/Expensify/App/pull/15761), and adding everything back in https://github.com/Expensify/App/pull/15777.
Then I closed that PR and moved those changes here so we can test out your fix(es). I'll also update the test steps to mention the original test steps from the original reverted PR (https://github.com/Expensify/App/pull/15039)

Yeesh this looks involved haha. Please tag me when it's ready for review.

Agreed with @parasharrajat about the moving the isNavigating stuff, lets do it in a follow up.

@aldo-expensify hope you don't mind, but I merged main to get up to date with removing all the related pages (from the revert PR #15761), and adding everything back in #15777.

I don't mind, I'm just surprised that you did this. I would have thought that you would get a ton of conflicts 🤮

Haha ya @aldo-expensify the only conflicts where the changes you made in the ContactMethodDetailsPage, but those were pretty easy to resolve.
@aldo-expensify I think we can mark this as "Ready for review", then maybe I can redo all of the old tests (all the new pages, green indicators, red dot indicators, offline UX) and would you mind doing videos / screenshots for the bug fix flow? Just b/c I was never able to reproduce that haha

@Beamanator reproduced the original bug:
https://user-images.githubusercontent.com/87341702/224834538-4338b830-4ebe-4aff-b6ff-4c8a10d60728.mov

@aldo-expensify Shnikeys :/ can you explain in detail how you can reproduce?? 🙏

Same as before:

Add unverified phone number
Delete it
Try to click one of the menu entries -> nothing happens

https://user-images.githubusercontent.com/87341702/224847514-bf11d77a-675d-4125-952c-a6104a6af39a.mov

@parasharrajat @Beamanator
I have spent a few hours trying this and I haven't been able to make it work. You can play around with this branch if you want to try it yourself: https://github.com/Expensify/App/tree/aldo_trying-to-move-listener-uo
The problem I encounter is that any listener higher in the tree doesn't get reliably the transitionEnd and transitionStart events, and I'm guessing this is because there isn't a single Navigator (RootStack.Navigator, MainDrawerNavigator, ModalStackNavigators....Navigator), there are multiple nested and I think the event stops at the first one.
Considering that relocating the code is not as easy as it looks, I started to question why do we even have this listener that sets Navigation.isNavigating. I understand that this functionality was added by this https://github.com/Expensify/App/pull/14426 to fix https://github.com/Expensify/App/issues/14258 (double tapping the currency can potentially navigate you back twice)
I tried to reproduce the issue https://github.com/Expensify/App/issues/14258 disabling the Navigation.isNavigating stuff and I couldn't, it is either hard to reproduce or it is not happening any more because of other changes.
Considering all that, I think the best would be to revert https://github.com/Expensify/App/pull/14426:

I think the possibility of leaving someone with the app completely locked is very bad (this bug), and the gains don't justify it. I think it would have been safer to just prevent the double tap at the level of the input with some flag changing value.
The original issue it was solving doesn't seem to happen anymore.

cc @roryabraham since you may have more context about https://github.com/Expensify/App/pull/14426
Agree?

Wow thanks for the great investigation @aldo-expensify ! I will try to find some time to talk to @roryabraham about this today since we're luckily in the same location for this week 👍

@aldo-expensify I'm going to try to reproduce this morning - and if I can, I am going to consider trying to use Navigation.canNavigate in ContactMethodDetailsPage to check if we can navigate or not - I wonder if you've tried this to avoid the double-navigate-stuck state?

I'm going to proceed with removing the Navigation.isNavigating stuff (more details: https://github.com/Expensify/App/pull/15751#issuecomment-1467192602) to unblock the work on the contact methods pages.

@Beamanator  @neil-marcellini @parasharrajat this is ready for review
cc @cristipaval in case you want to review / have a look

Oh ok @aldo-expensify so this will basically just be a straight revert-revert?

Oh ok @aldo-expensify so this will basically just be a straight revert-revert?

The PR you mean?
It is a revert-revert plus:

fix bug by remove the Navigation.isNavigating stuff: https://github.com/Expensify/App/pull/15751/commits/b659e1bbca2d03002f4b01cc96f716ce96b31d7a
move navigation when the login data is not found from render() to componentDidUpdate() (this part is not important for it to work, but I think it is better to put there from a code responsibility point of view - I don't think we should have redirections/side effects during rendering if possible)

For me it looks ok, now it works as expected and doesn't cause any regression.

Resolved conflicts

My take on it is that we can address that in a follow up to keep moving if the problem is already in main.

👍 sounds good.

From point 4., I understand that you added the unverified phone number successfully.

Huh I guess so, but the API command returned an error. I'll provide a video. If I sign out the phone number is still there. Maybe we should not show an error message in this case because clearly it was added, but I guess it failed to be verified? Weird. As a user I have no idea what to do based on the error message.
https://user-images.githubusercontent.com/26260477/226487346-c4a09bec-85fb-4a47-a83b-6ee501773fe7.mov

Looking good, some small things from me. Please ping me when it's updated.

@neil-marcellini ping 👋

@parasharrajat this is ready for review

My take on it is that we can address that in a follow up to keep moving if the problem is already in main.

👍 sounds good.

From point 4., I understand that you added the unverified phone number successfully.

Huh I guess so, but the API command returned an error. I'll provide a video. If I sign out the phone number is still there. Maybe we should not show an error message in this case because clearly it was added, but I guess it failed to be verified? Weird. As a user I have no idea what to do based on the error message.

@neil-marcellini This is a problem in the back end, we insert the entry for the secondary login first, and then we try to send the SMS to validate the phone number. It is on this second step that we have this check and throw, then you see the error in the front end, but the phone was added.
https://github.com/Expensify/Web-Expensify/blob/04892cf77cecf32caf75ecc6772b74a1f58f7544/lib/UserAPI.php#L930-L946
I'll move the check to before we add the login to the database. Related convo: https://github.com/Expensify/Web-Expensify/pull/36152/files#r1102989414

@parasharrajat

BUG: Pressing enter does not submit the verify contact page.

Fixed

Faced the same issue https://github.com/Expensify/App/pull/15751#pullrequestreview-1349255347. Good to debug in followup.

This will be fixed by a PR in the backend

BUG: The phone number is showing the wrong autoComplete list(data of username of the app).

Applied your suggestion, it seems to work fine!

Bug: Inconsistent space between the header and paragraph between the Contact Details page and the default contact method page.

Fixed
Thanks for catching those. Can you have a look again :)

Resolved conflicts.

I wonder why there is this error now:

Do we have a new rule enforcing default props for props that are not required?

Do we have a new rule enforcing default props for props that are not required?

I think it was there from the start.

but github was not complaining before, it just started now that I merged with main

also what does this mean:

We can't use "required" anymore?

Updated prop types removing .isRequired and added missing defaults

Question: When the user removes a contact offline, Should it be navigatable?
It does not open the details page on click.

No, it is disabled.

Great testing and improvements happening in this PR. Thank you!

BUG: After pressing send validations, the browser prompts to save the password. (https://github.com/Expensify/App/pull/15751#issuecomment-1482080346)

We will get rid of the passwords input eventually, and this page will be re-done in a follow up PR.

BUG: Error is not cleared when we navigate again to the add phone number page. (https://github.com/Expensify/App/pull/15751#issuecomment-1482085694)

I noticed this too, but we are deciding not to improve/fix it because we are re-doing this page in the follow up PR.

Bug or not: Is it fine submitting the verify form even if the magic code field is empty?

Good catch, we will fix it

Bug: clicking or tapping on the empty area trigger resend button.

Good catch, we will fix it

@shawnborton where do you think is better the green check position?
Current:

Proposed:

I like the "current" version but I would move it to be a bit closer to the text. Maybe we could try it at 4px margin as well as 8px margin?

Also FYI - the offline behavior for verifying a contact method is a bit confusing to me and @aldo-expensify - previously we've decided it should be pattern B but that doesn't seem super appropriate anymore, and we're not sure how to make that look very nice. So I'm planning to open a follow-up discussion to resolve that - for now I think we can leave move forward w/out completely making that flow perfect (offline verify contact method, pattern B)

Ah sorry for the confusion - I meant, can I see it where there is just 4px between the text and the checkbox? And then where there is just 8px between the text and the checkbox? Thanks!

Ah sorry for the confusion - I meant, can I see it where there is just 4px between the text and the checkbox? And then where there is just 8px between the text and the checkbox? Thanks!

16px:

12px:

8px:

4px:

@parasharrajat I think we're ready for you to test! 👍  I also just made sure the latest build works on iOS 👍  (since it seems you were having trouble a few days ago)

I think we can just use keyboardShouldPersistTaps='handled' https://reactnative.dev/docs/scrollview#keyboardshouldpersisttaps

Aah that looks nice and simple, but maybe this should be a larger app audit to see which pages don't have that - but this is better as a follow-up
As for this comment, the button styles were approved so let's keep them as is for now 👍

Thanks @aldo-expensify for fixing the android double tap issue

@parasharrajat I'll look into that one real quick, though I'd appreciate if you could start final testing everything else in the meantime 🙏  The blue checkmark button is a very very tiny case out of all the other cases so honestly I don't mind trying to implement that now or later - I really want the contact method details page merged ASAP so @cristipaval can move his PR forward which is holding on this one

Present on Main as well.
BUG: Web: Remove Confirm modal position is wrong.

this one looks very bad, I'll fix it now.

Present on Main as well.
BUG: Web: Remove Confirm modal position is wrong.

this one looks very bad, I'll fix it now.

nevermind, that is also in staging

@parasharrajat thanks for finding a few follow-up bugs we need to handle! I'd say we don't need to report them in slack, we can handle them in follow-ups in one of the related issues 👍  I'll probably create a new issue for the follow-ups

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/neil-marcellini in version: 1.2.92-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/luacmartins in version: 1.2.92-2 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

This issue was not considered in this PR.
Issue: Contact Method - Validation error message doesn't disappear upon requesting new magic code


Difference between TuyaLink and TuyaOS development methods

I have build my own device based on "tuya-iot-core-sdk" using ESP32 and TuyaLink development method. It works fine. But I can get access to it only via "Smart Industry" app (or through the debug web page on iot.tuya.com). Our bosses want to use standard "Smart Life" app. So, for this purpose I've used TuyaOS development method and "tuya-iot-link-sdk-embedded-c-without-submodules" example, based on my own esp32 chip (not on tuya's module). I've purchased two free licenses for it. In the end I get "Connection not authorized(11)" message.
Can I build my device without tuya's modules and use "Smart Life" app for access?
Do I need another license or use only China data center in "Smart Life" and device? Or problem is different?

I've resolved my issue with access to "Smart Life", but I still didn't understand, what is the difference between these two methods? What benefits do I get from TuyaLink compared to TuyaOS ?

First,the biggest difference is that TuyaLink uses the object model, while TuyaOS uses the internally mature dp model.
Secondly, different scenarios are targeted. TuyaOS is mainly in the field of smart home, which requires the use of graffiti modules or TuyaOS SDK;  On the other hand, TuyaLink focuses on industrial and agricultural scenarios, connecting more mature finished products to the graffiti cloud.
TuyaLink is a supplement to the TuyaOS device access field, and there is no mutual substitution。

@ViktorVerchenko , you said "I've resolved my issue with access to Smart Life". Were you able to add example devices of this demo to Smart Life App? I used data_model_basic_demo sample code and in iot.tuya.com I can see that my device is online, but I don't know how to communicate with it via Smart Life app.
CC @wenstonqq

Smart

you can read this page https://developer.tuya.com/en/docs/iot/application-dev?id=Kbf53a58zz6t1#title-3-Device binding code

@ViktorVerchenko could you briefly explain how did you use tuya-iot-link-sdk-embedded-c-without-submodule to work with esp32 chip. I am struggling to find a proper approach anywhere.


Mgtitimoli partials ordering

Updated the original PR with some additional changes.

@mgtitimoli Please see these changes.


Revert "Minor Patch TypeError thrown"

Reverts kennethreitz/requests#2513
The change was made to urllib3 which is vendored and to which pull requests should not be accepted.

Further, that breaks the API of urllib3 by raising an exception that is not a urllib3 exception and would introduce a breaking change to requests.

Yeah, this is straight up my bad.


Bump numpy version

Reference Issues/PRs

Fixes #1794
Fixes #1787

What does this implement/fix? Explain your changes.
Bumping numpy to >=1.21.0,<1.22
Does your contribution introduce a new dependency? If yes, which one?

What should a reviewer concentrate their feedback on?

Any other comments?

PR checklist

For all contributions

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

For new estimators

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

Looks like nothing break after bumping numpy :slightly_smiling_face: :rocket:

Quick Q, why does nothing break? Because we discontinued support for python 3.6 (which in turn influences the upper pandas bound)?

This is not an easy question to answer, but recent changes in #1620  made it easy to introduce this change also dropping 3.6 made release some of the constraints on package versions.

So, here's another question, @lmmentel: why a lower bound of 01.21.0? This does not include the old version, and may break things for users.
Would it be problematic to have this at 1.19.3 (the old version)?

I bumped it since I got a dependabot alert about my other package that there are vulnerabilities in numpy the recommended action is to bump it at least to 1.21, I can decrease the lower bound if you are afraid of users not being able to use sktime. BTW this will only affect people installing sktime 0.10.0 onward so I don't think it's an issue.

I bumped it since I got a dependabot alert about my other package

This violates the "Thou shalt have no other packages before sktime" clause in the sktime code of conduct ... or am I confusing this with another literature source? :-)

Is there any specific reason not to include numpy version 1.22 ?

@ilkersigirci, since this is a general Q, answering it here: https://github.com/alan-turing-institute/sktime/discussions/2037


Ensure we properly identify an insider/pre-relase extension

Codecov Report

Merging #11326 (4022e1b) into main (8bb3e19) will increase coverage by 0%.
The diff coverage is 50%.

@@          Coverage Diff           @@
##            main   #11326   +/-   ##
======================================
  Coverage     63%      63%
======================================
  Files        476      476
  Lines      33916    33918    +2
  Branches    5495     5495
======================================
+ Hits       21516    21522    +6
+ Misses     10344    10340    -4
  Partials    2056     2056

Impacted Files
Coverage Δ

src/kernels/serviceRegistry.node.ts
98% <50%> (+2%)
:arrow_up:

.../standalone/survey/dataScienceSurveyBanner.node.ts
66% <0%> (-6%)
:arrow_down:

src/platform/common/process/baseDaemon.node.ts
50% <0%> (-4%)
:arrow_down:

src/kernels/jupyter/baseKernelConnectionWrapper.ts
35% <0%> (-3%)
:arrow_down:

src/kernels/installer/productInstaller.node.ts
78% <0%> (-2%)
:arrow_down:

src/standalone/api/kernelApi.ts
75% <0%> (-2%)
:arrow_down:

src/kernels/common/baseJupyterSession.ts
80% <0%> (-1%)
:arrow_down:

src/platform/msrCrypto/msrCrypto.js
19% <0%> (-1%)
:arrow_down:

src/platform/common/utils/localize.ts
76% <0%> (+<1%)
:arrow_up:

src/notebooks/controllers/kernelRanking/helpers.ts
58% <0%> (+<1%)
:arrow_up:

... and 7 more

extensions which publish pre-releases is that extensions should have an even minor version for stable releases and an odd minor version for

Yes, but we decided not to change our versioning mechanism, as this helps us easily identify releases.


Using a .safetensors T5

Just a quick note, most probably people already have a T5 in safetensors format, cloning the PixArt repo (41 GB on disk) is quite an overkill. So it might be better to use the regular CLIP loader like this (top from the example workflow here, bottom is what I propose):

The result is slightly different, must be some rounding errors, otherwise it's 99% identical. The other CLIP types produce heavy bright artifacts so stick to the SD3 type.

@rkfg thank you! Please note that in latest ComfyUI you should use ltxv for model type.

For me this lxtv type produces noticeably worse results. SD3 or the original loader are much better. Could be an implementation quirk?


Karma coverage not working

Karma coverage seems to be configured, but it doesn't seem to recognize any code to analyze. See the 100% ( 0/0 )'s:

START:
  Books
    Reducer
      ✔ should have an empty initial state
      ✔ should add a book to the entities table and its ID to the IDs list when loaded
    Selectors
      getBookEntities
        ✔ should get the entities table out of the books state
      getBook
        ✔ should get a selected book out of the books state
      getBooks
        ✔ should return all of the books in an array for a given list of ids

Finished in 0.169 secs / 0.007 secs

SUMMARY:
✔ 5 tests completed

=============================== Coverage summary ===============================
Statements   : 100% ( 0/0 )
Branches     : 100% ( 0/0 )
Functions    : 100% ( 0/0 )
Lines        : 100% ( 0/0 )
================================================================================```

duplicate of #28


PMID:20139237

increased negative regulation of transcription by glucose

increased negative regulation of transcription by glucose FYPO:0006296
edit file: f04954f96789e7ea0c9689d4797698e7288f9ea0
release: c736114245c09d058bbe81c0134f1b61b2e3e6b9


Issue with Moonscraper on Linux

Every time i open Moonscraper on my computer (running Ubuntu 20.04.2) it throws a SDL2 InputManager error for the Start and Update functions.

Update error repeats indefinitely.

@bmwalters

Hey @c291bGxlc3Nzb29vZXM can you please make sure all the dependencies in the README are installed?
https://github.com/FireFox2000000/Moonscraper-Chart-Editor#runtime-dependencies-linux
I think on Ubuntu the commands to install them would be something like:
sudo apt update
sudo apt install ffmpeg libsdl2-2.0-0 libx11-6 libgtk-3-0

Already have installed Windows before you commmented but will make sure of it in my next ubuntu install


Disable indoor view of buildings

Is it possible to only show outdoor street view?
I know that we can do like &source=outdoor as an url params in JS API
but not sure how to achieve it here

@brianlaw033 did you find any solution?


Update ESPloit Submodule to latest commit

Submodule is on an old commit.  Please consider pulling latest commit for ESPloit from my repo.
I have added a lot of new features to ESPloit and even made some minor changes to the 32u4 code.

Done!
P.S. Due to all changes I guess that the FW upgrade on-the-fly cannot be achieved (since within the last release, it is also mandatory to upload the 32u4 sketch). Right?

No it will still work, it will just have limited features and tell you to manually update the 32u4 sketch when you click on upgrade firmware.

Perfect! Just wanted to be sure people won't brick WHID with improper flashing the FW.

Perfect! Just wanted to be sure people won't brick WHID with improper flashing the FW.


merge package from arlac77/npm-package-template

package.json

chore(package<EMAIL_ADDRESS>

Coverage remained the same at 83.983% when pulling 182a5503348398856ab8d4c94395a3484de013b3 on template-sync-1 into e0c5e394a0c0d150484831418cd0fe3d59d294ea on master.


Bleno with Raspberry Pi 3 Model B+ not working very well but Model B works fine

Hello,
We have both Raspberry PI 3 Model B and B+.  When comparison between the two devices.  Our software will work just fine on the Model B+ which uses WIFI and Bluetooth.  When we install our software with Model B+ the Bluetooth will not work as the same as the Model B.
What I have found out is that on the Model B+ I can see the device show up on our application that is connecting/listening for.   When connected it will send a few bytes and also let the device know that it is still online (ping/pong).
However on our LOGS shows that it does not receive a App Ping from the mobile app (iOS).  When connected it will then try to get a list of wifi networks from the actual RPI which does show.  However it crashes our mobile application.  Bluetooth remains stuck, and the only way I can actually reset it completely is by rebooting the PI.
Basically commands like hciconfig hci0 reset or hciconfig hci0 down/up will result connection timeout issues.  Nothing I do will not cause it to work.
Is there something that I need to know about to make this work? With Model B+.  I do noticed that when we we're using Bluetooth Dongle at one time it would cause/do the same thing we're seeing again.
I have no clue where to go from here. Any help will be much appreciated.
Thank you,
Ben

For anyone who may have the same issue.  Update your raspberry pi 3 B+ to the latest kernel, nodejs 8.11 (at least) and download/use bleno 0.5.0+ which somehow is what fixed my issue.


Listal ripper errors out when there is an underscore in the url.

Ripme version:1.7.95
Java version:  "1.8.0_241"
Operating system:  Microsoft Windows [Version 10.0.19043.1415]

Exact URL you were trying to rip when the problem occurred: https://www.listal.com/emma-stone_iii/pictures
Please include any additional information about how to reproduce the problem:

Listal ripper fails if there is an underscore in the URL, like in this case there is an underscore in emma-stone_iii
I changed line 28 in ListalRipper.java from:
    private Pattern p2 =Pattern.compile("https:\\/\\/www.listal.com\\/((?:(?:[a-zA-Z0-9-%]+)\\/?)+)");

To:
    private Pattern p2 =Pattern.compile("https:\\/\\/www.listal.com\\/((?:(?:[a-zA-Z0-9-_%]+)\\/?)+)");

(Included underscore _ in the pattern right before the percent sign) And it seems to solve the issue. But I don't know how to run all the tests and create a pull request.
Expected Behavior
URLs with underscores should work...
Actual Behavior
URL's with underscores result in Expected listal.com URL format: listal.com/list/my-list-name - got https://www.listal.com/emma-stone_iii/pictures  error.

fixed in https://github.com/ripmeapp2/ripme/releases

@soloturn could you make a pr against this repro as well?


[Social] The system does not display the information previously inserted when the patient is not checked in

Actual Results
If the user clicks on the social information date/ button when the patient is not chekedin, the system does not list the previously entered information.
Expected results
When the user clicks the date of the last social info button, the system should display all the information listed
Steps to reproduce
Go to the Social Module -> Find a patient with social information recorded in the past -> click the button in the list -> Click on the date
Screenshot

General Observation: This is particularly happening for patients that had social information before the update on the social page was done. I created a new patient and added some social information. Upon accessing information the next day it was available.  The patient was created and social information added after the update was done.
Below are screenshots of my findings:
Patient with social information before update:

Patient with social information after update

I was not able to replicate this @Benilde. Please try with the current version and reopen this if necessary.


Fixed alphabetical sorting in exported excel sheet

#109

Is this working properly with the special Hungarian letters? I think we already did something with this.


renderer: add support for extending node renderers

Hi, I added support for extending node renderer similar to goldmark's HTML renderer.
An example usage:
markdownRenderer := markdown.NewRenderer()
markdownRenderer.AddOptions(
	renderer.WithNodeRenderers(util.Prioritized(&latex.BlockRenderer{
		RendererType: latex.RendererTypeMarkdown,
	}, 502)),
)
md := goldmark.New(
	goldmark.WithRenderer(markdownRenderer),
)

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

42 of 79 (53.16%)  changed or added relevant lines in 2 files are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-8.4%) to 91.593%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

renderer.go
37
52
71.15%

writer.go
5
27
18.52%

Files with Coverage Reduction
New Missed Lines
%

renderer.go
1
94.54%

Totals

Change from base Build<PHONE_NUMBER>:
-8.4%

Covered Lines:
414

Relevant Lines:
452

💛  - Coveralls


DOC-5948 v21.2.17 release notes

Addresses: DOC-5948

Release notes for v21.2.17, scheduled for Monday, October 17.

v21.2.md

This change is

Sweet, TYFR!


I can only import one football worldcup but I want the full history

Hi,
thank you for this amazing work.
I am trying to import the full history of all worldcup by running:
sportdb new worldcup
But I only get a sqlite database with worldcup2014
If I run sportdb new worldcup2018  I only get the worldcup 2018 database
I tried unziping: world-cup-master
and found that in the setups folder and all.txt is having this content:
###########
# All

# Note: just latest world cup - e.g. Brazil 2014 w/ Quali(fiers)
#
# -- use history.txt for all world cups

# -- Brazil 2014 Quali(fiers)
world-cup!/2014--brazil/quali/africa
world-cup!/2014--brazil/quali/asia
world-cup!/2014--brazil/quali/europe
world-cup!/2014--brazil/quali/north_america
world-cup!/2014--brazil/quali/pacific
world-cup!/2014--brazil/quali/playoffs
world-cup!/2014--brazil/quali/south_america

# -- Brazil 2014
world-cup!/2014--brazil/cup

Is this the problem here? How can I solve it?
Thanks

Please send your "I can only import one football worldcup but I want the full history" questions to the forum / mailinglist http://groups.google.com/group/opensport. Cheers. Prost.


tensorflow should be a main dependency (instead of a dev dependency)

I am trying to use scikeras in a poetry based project. I ran
poetry add scikeras

which worked. At runtime, I got an error saying that tensorflow 2.7.0 was needed. This should've been caught at the time I added the package during poetry. The only reason, from my understanding that it wasn't was because tensorflow is a dev dependency, rather than a real dependency, for poetry.

This is a known issue, and stems from a limitation of how TensorFlow packages itself. The TLDR is that there are other versions of tensor flow like tensorflow-cpu, so if we specified tensorflow as a hard dependency users who want to use tensorflow-cpu wouldn't be able to install SciKeras. For more background, see https://github.com/adriangb/scikeras/issues/221.

Ah, I see.
https://github.com/adriangb/scikeras/issues/221#issuecomment-805034870
I think option 1 here is a bit cleaner, but makes sense to go either way to solve the problem. No worries if you just want to close this, I should've read the readme closer. Thanks for the cool package :)

Yeah I guess we can make TensorFlow an optional dependency and the update everywhere in the documentation to use scikeras[tensorflow] so that at least users copy pasting from the readme won't get caught off guard that easily. A PR for something like this would be gladly accepted :)

I see. What do you think of adding both?
poetry add --optional tensorflow==2.7.0
poetry add --optional tensorflow-cpu==2.7.0

?