unit_test_binaryen (Failed)；unit_test_wavm (SEGFAULT)

make test and display 2 errors
eostest@ubuntu:~/eos$ export PATH=${HOME}/opt/mongodb/bin:$PATH
eostest@ubuntu:~/eos$ sudo /home/eostest/opt/mongodb/bin/mongod -f /home/eostest/opt/mongodb/mongod.conf &
[1] 2020
eostest@ubuntu:~/eos$ cd /home/eostest/eos/build; make test
Running tests...
Test project /home/eostest/eos/build
Start  1: test_cypher_suites
1/46 Test  #1: test_cypher_suites ...................   Passed    0.08 sec
Start  2: validate_simple.token_abi
2/46 Test  #2: validate_simple.token_abi ............   Passed    0.07 sec
Start  3: validate_eosio.token_abi
3/46 Test  #3: validate_eosio.token_abi .............   Passed    0.07 sec
Start  4: validate_eosio.msig_abi
4/46 Test  #4: validate_eosio.msig_abi ..............   Passed    0.06 sec
Start  5: validate_eosio.sudo_abi
5/46 Test  #5: validate_eosio.sudo_abi ..............   Passed    0.07 sec
Start  6: validate_multi_index_test_abi
6/46 Test  #6: validate_multi_index_test_abi ........   Passed    0.09 sec
Start  7: validate_eosio.system_abi
7/46 Test  #7: validate_eosio.system_abi ............   Passed    0.07 sec
Start  8: validate_identity_abi
8/46 Test  #8: validate_identity_abi ................   Passed    0.06 sec
Start  9: validate_identity_test_abi
9/46 Test  #9: validate_identity_test_abi ...........   Passed    0.06 sec
Start 10: validate_stltest_abi
10/46 Test #10: validate_stltest_abi .................   Passed    0.06 sec
Start 11: validate_exchange_abi
11/46 Test #11: validate_exchange_abi ................   Passed    0.09 sec
Start 12: validate_test.inline_abi
12/46 Test #12: validate_test.inline_abi .............   Passed    0.07 sec
Start 13: validate_hello_abi
13/46 Test #13: validate_hello_abi ...................   Passed    0.07 sec
Start 14: validate_asserter_abi
14/46 Test #14: validate_asserter_abi ................   Passed    0.07 sec
Start 15: validate_infinite_abi
15/46 Test #15: validate_infinite_abi ................   Passed    0.07 sec
Start 16: validate_proxy_abi
16/46 Test #16: validate_proxy_abi ...................   Passed    0.10 sec
Start 17: validate_test_api_abi
17/46 Test #17: validate_test_api_abi ................   Passed    0.06 sec
Start 18: validate_test_api_mem_abi
18/46 Test #18: validate_test_api_mem_abi ............   Passed    0.06 sec
Start 19: validate_test_api_db_abi
19/46 Test #19: validate_test_api_db_abi .............   Passed    0.07 sec
Start 20: validate_test_api_multi_index_abi
20/46 Test #20: validate_test_api_multi_index_abi ....   Passed    0.08 sec
Start 21: validate_test_ram_limit_abi
21/46 Test #21: validate_test_ram_limit_abi ..........   Passed    0.09 sec
Start 22: validate_eosio.bios_abi
22/46 Test #22: validate_eosio.bios_abi ..............   Passed    0.07 sec
Start 23: validate_noop_abi
23/46 Test #23: validate_noop_abi ....................   Passed    0.07 sec
Start 24: validate_dice_abi
24/46 Test #24: validate_dice_abi ....................   Passed    0.05 sec
Start 25: validate_tic_tac_toe_abi
25/46 Test #25: validate_tic_tac_toe_abi .............   Passed    0.07 sec
Start 26: validate_payloadless_abi
26/46 Test #26: validate_payloadless_abi .............   Passed    0.06 sec
Start 27: validate_integration_test_abi
27/46 Test #27: validate_integration_test_abi ........   Passed    0.07 sec
Start 28: unit_test_binaryen
28/46 Test #28: unit_test_binaryen ...................***Failed  210.60 sec
Start 29: unit_test_wavm
29/46 Test #29: unit_test_wavm .......................***Exception: SegFault895.18 sec
Start 30: validate_deferred_test_abi
30/46 Test #30: validate_deferred_test_abi ...........   Passed    0.14 sec
Start 31: plugin_test
31/46 Test #31: plugin_test ..........................   Passed    1.53 sec
Start 32: nodeos_sanity_test
32/46 Test #32: nodeos_sanity_test ...................   Passed    2.89 sec
Start 33: nodeos_run_test
33/46 Test #33: nodeos_run_test ......................   Passed   65.41 sec
Start 34: bnet_nodeos_run_test
34/46 Test #34: bnet_nodeos_run_test .................   Passed   68.67 sec
Start 35: p2p_dawn515_test
35/46 Test #35: p2p_dawn515_test .....................   Passed    8.20 sec
Start 36: nodeos_run_test-mongodb
36/46 Test #36: nodeos_run_test-mongodb ..............   Passed   71.68 sec
Start 37: distributed-transactions-test
37/46 Test #37: distributed-transactions-test ........   Passed   71.35 sec
Start 38: restart-scenarios-test-resync
38/46 Test #38: restart-scenarios-test-resync ........   Passed  133.50 sec
Start 39: restart-scenarios-test-hard_replay
39/46 Test #39: restart-scenarios-test-hard_replay ...   Passed  124.24 sec
Start 40: restart-scenarios-test-none
40/46 Test #40: restart-scenarios-test-none ..........   Passed  139.75 sec
Start 41: validate_dirty_db_test
41/46 Test #41: validate_dirty_db_test ...............   Passed    2.78 sec
Start 42: nodeos_sanity_lr_test
42/46 Test #42: nodeos_sanity_lr_test ................   Passed    2.63 sec
Start 43: bnet_nodeos_sanity_lr_test
43/46 Test #43: bnet_nodeos_sanity_lr_test ...........   Passed    2.68 sec
Start 44: nodeos_voting_lr_test
44/46 Test #44: nodeos_voting_lr_test ................   Passed  1259.30 sec
Start 45: bnet_nodeos_voting_lr_test
45/46 Test #45: bnet_nodeos_voting_lr_test ...........   Passed  1264.05 sec
Start 46: nodeos_under_min_avail_ram_lr_test
46/46 Test #46: nodeos_under_min_avail_ram_lr_test ...   Passed  443.06 sec
96% tests passed, 2 tests failed out of 46
Label Time Summary:
long_running_tests    = 2971.71 sec*proc (5 tests)
Total Test time (real) = 4769.88 sec
The following tests FAILED:
28 - unit_test_binaryen (Failed)
29 - unit_test_wavm (SEGFAULT)
Errors while running CTest
Makefile:119: recipe for target 'test' failed
make: *** [test] Error 8
=========================================================================================================================================================================================================
unit test：
eostest@ubuntu:~/eos/build$ unittests/unit_test --report_level=detailed
Random number generator seeded to<PHONE_NUMBER>
Running 288 test cases...
unknown location(0): fatal error: in "wasm_tests/check_big_deserialization": memory access violation at address: 0x00000000: no mapping at fault address
/home/eostest/eos/unittests/wasm_tests.cpp(1221): last checkpoint
Test module "Master Test Suite" has failed with:
279 test cases out of 280 passed
1 test case out of 280 failed
1 test case out of 280 aborted
7235 assertions out of 7236 passed
1 assertion out of 7236 failed
Test suite "abi_tests" has passed with:
51 test cases out of 51 passed
284 assertions out of 284 passed
Test case "abi_tests/uint_types" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_unknown_type" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_all_types" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_double_base" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_double_action" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_all_indexes" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_unable_to_determine_index" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_long_field_name" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_long_type_name" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_same_type_different_namespace" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_bad_index_type" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_full_table_decl" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_union_table" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_same_action_different_type" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_template_base" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_action_and_table" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_simple_typedef" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_field_typedef" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_vector_of_POD" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_vector_of_structs" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_vector_multidimension" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_vector_alias" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_eosioabi_macro" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_contract_inheritance" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abigen_no_eosioabi_macro" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/general" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abi_cycle" has passed with:
  2 assertions out of 2 passed

Test case "abi_tests/linkauth_test" has passed with:
  11 assertions out of 11 passed

Test case "abi_tests/unlinkauth_test" has passed with:
  9 assertions out of 9 passed

Test case "abi_tests/updateauth_test" has passed with:
  35 assertions out of 35 passed

Test case "abi_tests/deleteauth_test" has passed with:
  7 assertions out of 7 passed

Test case "abi_tests/newaccount_test" has passed with:
  59 assertions out of 59 passed

Test case "abi_tests/setcode_test" has passed with:
  10 assertions out of 10 passed

Test case "abi_tests/setabi_test" has passed with:
  73 assertions out of 73 passed

Test case "abi_tests/packed_transaction" has passed with:
  35 assertions out of 35 passed

Test case "abi_tests/abi_type_repeat" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abi_struct_repeat" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abi_action_repeat" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abi_table_repeat" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abi_type_def" has passed with:
  3 assertions out of 3 passed

Test case "abi_tests/abi_type_loop" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abi_type_redefine" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abi_type_redefine_to_name" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abi_type_nested_in_vector" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abi_account_name_in_eosio_abi" has passed

Test case "abi_tests/abi_large_array" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abi_is_type_recursion" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abi_recursive_structs" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abi_very_deep_structs" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abi_very_deep_structs_1ms" has passed with:
  1 assertion out of 1 passed

Test case "abi_tests/abi_deep_structs_validate" has passed with:
  1 assertion out of 1 passed

Test suite "api_tests" has passed with:
33 test cases out of 33 passed
374 assertions out of 374 passed
Test case "api_tests/action_receipt_tests" has passed with:
  13 assertions out of 13 passed

Test case "api_tests/action_tests" has passed with:
  21 assertions out of 21 passed

Test case "api_tests/ram_billing_in_notify_tests" has passed with:
  5 assertions out of 5 passed

Test case "api_tests/cf_action_tests" has passed with:
  26 assertions out of 26 passed

Test case "api_tests/cfa_tx_signature" has passed with:
  3 assertions out of 3 passed

Test case "api_tests/cfa_stateful_api" has passed with:
  3 assertions out of 3 passed

Test case "api_tests/deferred_cfa_failed" has passed with:
  3 assertions out of 3 passed

Test case "api_tests/deferred_cfa_success" has passed with:
  6 assertions out of 6 passed

Test case "api_tests/checktime_pass_tests" has passed with:
  3 assertions out of 3 passed

Test case "api_tests/checktime_fail_tests" has passed with:
  5 assertions out of 5 passed

Test case "api_tests/checktime_intrinsic" has passed with:
  3 assertions out of 3 passed

Test case "api_tests/checktime_hashing_fail" has passed with:
  11 assertions out of 11 passed

Test case "api_tests/compiler_builtins_tests" has passed with:
  13 assertions out of 13 passed

Test case "api_tests/transaction_tests" has passed with:
  18 assertions out of 18 passed

Test case "api_tests/deferred_transaction_tests" has passed with:
  25 assertions out of 25 passed

Test case "api_tests/chain_tests" has passed with:
  3 assertions out of 3 passed

Test case "api_tests/db_tests" has passed with:
  24 assertions out of 24 passed

Test case "api_tests/multi_index_tests" has passed with:
  34 assertions out of 34 passed

Test case "api_tests/fixedpoint_tests" has passed with:
  8 assertions out of 8 passed

Test case "api_tests/crypto_tests" has passed with:
  21 assertions out of 21 passed

Test case "api_tests/memory_tests" has passed with:
  23 assertions out of 23 passed

Test case "api_tests/extended_memory_test_initial_memory" has passed with:
  3 assertions out of 3 passed

Test case "api_tests/extended_memory_test_page_memory" has passed with:
  3 assertions out of 3 passed

Test case "api_tests/extended_memory_test_page_memory_exceeded" has passed with:
  3 assertions out of 3 passed

Test case "api_tests/extended_memory_test_page_memory_negative_bytes" has passed with:
  3 assertions out of 3 passed

Test case "api_tests/print_tests" has passed with:
  44 assertions out of 44 passed

Test case "api_tests/types_tests" has passed with:
  6 assertions out of 6 passed

Test case "api_tests/permission_tests" has passed with:
  13 assertions out of 13 passed

Test case "api_tests/datastream_tests" has passed with:
  3 assertions out of 3 passed

Test case "api_tests/new_api_feature_tests" has passed with:
  6 assertions out of 6 passed

Test case "api_tests/permission_usage_tests" has passed with:
  8 assertions out of 8 passed

Test case "api_tests/account_creation_time_tests" has passed with:
  3 assertions out of 3 passed

Test case "api_tests/eosio_assert_code_tests" has passed with:
  8 assertions out of 8 passed

Test suite "auth_tests" has passed with:
12 test cases out of 12 passed
90 assertions out of 90 passed
Test case "auth_tests/missing_sigs" has passed with:
  3 assertions out of 3 passed

Test case "auth_tests/missing_multi_sigs" has passed with:
  3 assertions out of 3 passed

Test case "auth_tests/missing_auths" has passed with:
  2 assertions out of 2 passed

Test case "auth_tests/delegate_auth" has passed with:
  3 assertions out of 3 passed

Test case "auth_tests/update_auths" has passed with:
  43 assertions out of 43 passed

Test case "auth_tests/link_auths" has passed with:
  5 assertions out of 5 passed

Test case "auth_tests/link_then_update_auth" has passed with:
  2 assertions out of 2 passed

Test case "auth_tests/create_account" has passed with:
  14 assertions out of 14 passed

Test case "auth_tests/any_auth" has passed with:
  3 assertions out of 3 passed

Test case "auth_tests/no_double_billing" has passed with:
  5 assertions out of 5 passed

Test case "auth_tests/stricter_auth" has passed with:
  1 assertion out of 1 passed

Test case "auth_tests/linkauth_special" has passed with:
  6 assertions out of 6 passed

Test suite "block_tests" has passed with:
1 test case out of 1 passed
1 assertion out of 1 passed
Test case "block_tests/block_with_invalid_tx_test" has passed with:
  1 assertion out of 1 passed

Test suite "block_timestamp_tests" has passed with:
2 test cases out of 2 passed
4 assertions out of 4 passed
Test case "block_timestamp_tests/constructor_test" has passed with:
  2 assertions out of 2 passed

Test case "block_timestamp_tests/conversion_test" has passed with:
  2 assertions out of 2 passed

Test suite "bootseq_tests" has passed with:
1 test case out of 1 passed
99 assertions out of 99 passed
Test case "bootseq_tests/bootseq_test" has passed with:
  99 assertions out of 99 passed

Test suite "currency_tests" has passed with:
10 test cases out of 10 passed
328 assertions out of 328 passed
Test case "currency_tests/bootstrap" has passed with:
  2 assertions out of 2 passed

Test case "currency_tests/test_transfer" has passed with:
  3 assertions out of 3 passed

Test case "currency_tests/test_duplicate_transfer" has passed with:
  4 assertions out of 4 passed

Test case "currency_tests/test_addtransfer" has passed with:
  5 assertions out of 5 passed

Test case "currency_tests/test_overspend" has passed with:
  6 assertions out of 6 passed

Test case "currency_tests/test_fullspend" has passed with:
  6 assertions out of 6 passed

Test case "currency_tests/test_symbol" has passed with:
  47 assertions out of 47 passed

Test case "currency_tests/test_proxy" has passed with:
  44 assertions out of 44 passed

Test case "currency_tests/test_deferred_failure" has passed with:
  204 assertions out of 204 passed

Test case "currency_tests/test_input_quantity" has passed with:
  7 assertions out of 7 passed

Test suite "database_tests" has passed with:
2 test cases out of 2 passed
409 assertions out of 409 passed
Test case "database_tests/undo_test" has passed with:
  3 assertions out of 3 passed

Test case "database_tests/get_blocks" has passed with:
  406 assertions out of 406 passed

Test suite "delay_tests" has passed with:
17 test cases out of 17 passed
400 assertions out of 400 passed
Test case "delay_tests/delay_create_account" has passed with:
  1 assertion out of 1 passed

Test case "delay_tests/delay_error_create_account" has passed with:
  4 assertions out of 4 passed

Test case "delay_tests/link_delay_direct_test" has passed with:
  25 assertions out of 25 passed

Test case "delay_tests/delete_auth_test" has passed with:
  15 assertions out of 15 passed

Test case "delay_tests/link_delay_direct_parent_permission_test" has passed with:
  25 assertions out of 25 passed

Test case "delay_tests/link_delay_direct_walk_parent_permissions_test" has passed with:
  25 assertions out of 25 passed

Test case "delay_tests/link_delay_permission_change_test" has passed with:
  38 assertions out of 38 passed

Test case "delay_tests/link_delay_permission_change_with_delay_heirarchy_test" has passed with:
  37 assertions out of 37 passed

Test case "delay_tests/link_delay_link_change_test" has passed with:
  36 assertions out of 36 passed

Test case "delay_tests/link_delay_unlink_test" has passed with:
  34 assertions out of 34 passed

Test case "delay_tests/link_delay_link_change_heirarchy_test" has passed with:
  35 assertions out of 35 passed

Test case "delay_tests/mindelay_test" has passed with:
  23 assertions out of 23 passed

Test case "delay_tests/canceldelay_test" has passed with:
  45 assertions out of 45 passed

Test case "delay_tests/canceldelay_test2" has passed with:
  42 assertions out of 42 passed

Test case "delay_tests/max_transaction_delay_create" has passed with:
  2 assertions out of 2 passed

Test case "delay_tests/max_transaction_delay_execute" has passed with:
  8 assertions out of 8 passed

Test case "delay_tests/delay_expired" has passed with:
  5 assertions out of 5 passed

Test suite "dice_tests" has passed with:
1 test case out of 1 passed
35 assertions out of 35 passed
Test case "dice_tests/dice_test" has passed with:
  35 assertions out of 35 passed

Test suite "eosio_sudo_tests" has passed with:
4 test cases out of 4 passed
30 assertions out of 30 passed
Test case "eosio_sudo_tests/sudo_exec_direct" has passed with:
  6 assertions out of 6 passed

Test case "eosio_sudo_tests/sudo_with_msig" has passed with:
  10 assertions out of 10 passed

Test case "eosio_sudo_tests/sudo_with_msig_unapprove" has passed with:
  2 assertions out of 2 passed

Test case "eosio_sudo_tests/sudo_with_msig_producers_change" has passed with:
  12 assertions out of 12 passed

Test suite "eosio_system_tests" has passed with:
40 test cases out of 40 passed
3982 assertions out of 3982 passed
Test case "eosio_system_tests/buysell" has passed with:
  70 assertions out of 70 passed

Test case "eosio_system_tests/stake_unstake" has passed with:
  44 assertions out of 44 passed

Test case "eosio_system_tests/stake_unstake_with_transfer" has passed with:
  36 assertions out of 36 passed

Test case "eosio_system_tests/stake_to_self_with_transfer" has passed with:
  9 assertions out of 9 passed

Test case "eosio_system_tests/stake_while_pending_refund" has passed with:
  36 assertions out of 36 passed

Test case "eosio_system_tests/fail_without_auth" has passed with:
  13 assertions out of 13 passed

Test case "eosio_system_tests/stake_negative" has passed with:
  10 assertions out of 10 passed

Test case "eosio_system_tests/unstake_negative" has passed with:
  14 assertions out of 14 passed

Test case "eosio_system_tests/unstake_more_than_at_stake" has passed with:
  17 assertions out of 17 passed

Test case "eosio_system_tests/delegate_to_another_user" has passed with:
  38 assertions out of 38 passed

Test case "eosio_system_tests/stake_unstake_separate" has passed with:
  28 assertions out of 28 passed

Test case "eosio_system_tests/adding_stake_partial_unstake" has passed with:
  36 assertions out of 36 passed

Test case "eosio_system_tests/stake_from_refund" has passed with:
  68 assertions out of 68 passed

Test case "eosio_system_tests/stake_to_another_user_not_from_refund" has passed with:
  27 assertions out of 27 passed

Test case "eosio_system_tests/producer_register_unregister" has passed with:
  29 assertions out of 29 passed

Test case "eosio_system_tests/vote_for_producer" has passed with:
  48 assertions out of 48 passed

Test case "eosio_system_tests/unregistered_producer_voting" has passed with:
  17 assertions out of 17 passed

Test case "eosio_system_tests/more_than_30_producer_voting" has passed with:
  11 assertions out of 11 passed

Test case "eosio_system_tests/vote_same_producer_30_times" has passed with:
  14 assertions out of 14 passed

Test case "eosio_system_tests/producer_keep_votes" has passed with:
  25 assertions out of 25 passed

Test case "eosio_system_tests/vote_for_two_producers" has passed with:
  25 assertions out of 25 passed

Test case "eosio_system_tests/proxy_register_unregister_keeps_stake" has passed with:
  39 assertions out of 39 passed

Test case "eosio_system_tests/proxy_stake_unstake_keeps_proxy_flag" has passed with:
  32 assertions out of 32 passed

Test case "eosio_system_tests/proxy_actions_affect_producers" has passed with:
  55 assertions out of 55 passed

Test case "eosio_system_tests/producer_pay" has passed with:
  2238 assertions out of 2238 passed

Test case "eosio_system_tests/multiple_producer_pay" has passed with:
  236 assertions out of 236 passed

Test case "eosio_system_tests/producers_upgrade_system_contract" has passed with:
  121 assertions out of 121 passed

Test case "eosio_system_tests/producer_onblock_check" has passed with:
  86 assertions out of 86 passed

Test case "eosio_system_tests/voters_actions_affect_proxy_and_producers" has passed with:
  74 assertions out of 74 passed

Test case "eosio_system_tests/vote_both_proxy_and_producers" has passed with:
  16 assertions out of 16 passed

Test case "eosio_system_tests/select_invalid_proxy" has passed with:
  9 assertions out of 9 passed

Test case "eosio_system_tests/double_register_unregister_proxy_keeps_votes" has passed with:
  32 assertions out of 32 passed

Test case "eosio_system_tests/proxy_cannot_use_another_proxy" has passed with:
  18 assertions out of 18 passed

Test case "eosio_system_tests/elect_producers" has passed with:
  36 assertions out of 36 passed

Test case "eosio_system_tests/buyname" has passed with:
  20 assertions out of 20 passed

Test case "eosio_system_tests/bid_invalid_names" has passed with:
  9 assertions out of 9 passed

Test case "eosio_system_tests/multiple_namebids" has passed with:
  65 assertions out of 65 passed

Test case "eosio_system_tests/vote_producers_in_and_out" has passed with:
  136 assertions out of 136 passed

Test case "eosio_system_tests/setparams" has passed with:
  121 assertions out of 121 passed

Test case "eosio_system_tests/setram_effect" has passed with:
  24 assertions out of 24 passed

Test suite "eosio_token_tests" has passed with:
7 test cases out of 7 passed
56 assertions out of 56 passed
Test case "eosio_token_tests/create_tests" has passed with:
  5 assertions out of 5 passed

Test case "eosio_token_tests/create_negative_max_supply" has passed with:
  2 assertions out of 2 passed

Test case "eosio_token_tests/symbol_already_exists" has passed with:
  6 assertions out of 6 passed

Test case "eosio_token_tests/create_max_supply" has passed with:
  6 assertions out of 6 passed

Test case "eosio_token_tests/create_max_decimals" has passed with:
  6 assertions out of 6 passed

Test case "eosio_token_tests/issue_tests" has passed with:
  13 assertions out of 13 passed

Test case "eosio_token_tests/transfer_tests" has passed with:
  18 assertions out of 18 passed

Test suite "exchange_tests" has passed with:
3 test cases out of 3 passed
8 assertions out of 8 passed
Test case "exchange_tests/bootstrap" has passed with:
  2 assertions out of 2 passed

Test case "exchange_tests/exchange_create" has passed with:
  3 assertions out of 3 passed

Test case "exchange_tests/exchange_lend" has passed with:
  3 assertions out of 3 passed

Test suite "forked_tests" has passed with:
6 test cases out of 6 passed
58 assertions out of 58 passed
Test case "forked_tests/irrblock" has passed

Test case "forked_tests/fork_with_bad_block" has passed with:
  20 assertions out of 20 passed

Test case "forked_tests/forking" has passed with:
  6 assertions out of 6 passed

Test case "forked_tests/prune_remove_branch" has passed with:
  5 assertions out of 5 passed

Test case "forked_tests/confirmation" has passed with:
  21 assertions out of 21 passed

Test case "forked_tests/read_modes" has passed with:
  6 assertions out of 6 passed

Test suite "identity_tests" has passed with:
8 test cases out of 8 passed
253 assertions out of 253 passed
Test case "identity_tests/identity_create" has passed with:
  24 assertions out of 24 passed

Test case "identity_tests/certify_decertify" has passed with:
  52 assertions out of 52 passed

Test case "identity_tests/trust_untrust" has passed with:
  10 assertions out of 10 passed

Test case "identity_tests/certify_decertify_owner" has passed with:
  35 assertions out of 35 passed

Test case "identity_tests/owner_certified_by_producer" has passed with:
  37 assertions out of 37 passed

Test case "identity_tests/owner_certified_by_trusted_account" has passed with:
  37 assertions out of 37 passed

Test case "identity_tests/owner_certification_becomes_trusted" has passed with:
  28 assertions out of 28 passed

Test case "identity_tests/ownership_contradiction" has passed with:
  30 assertions out of 30 passed

Test suite "message_buffer_tests" has passed with:
6 test cases out of 6 passed
306 assertions out of 306 passed
Test case "message_buffer_tests/message_buffer_construction" has passed with:
  7 assertions out of 7 passed

Test case "message_buffer_tests/message_buffer_growth" has passed with:
  43 assertions out of 43 passed

Test case "message_buffer_tests/message_buffer_peek_read" has passed with:
  228 assertions out of 228 passed

Test case "message_buffer_tests/message_buffer_write_ptr_to_end" has passed with:
  20 assertions out of 20 passed

Test case "message_buffer_tests/message_buffer_read_peek_bounds" has passed with:
  4 assertions out of 4 passed

Test case "message_buffer_tests/message_buffer_read_peek_bounds_multi" has passed with:
  4 assertions out of 4 passed

Test suite "misc_tests" has passed with:
8 test cases out of 8 passed
203 assertions out of 203 passed
Test case "misc_tests/name_suffix_tests" has passed with:
  15 assertions out of 15 passed

Test case "misc_tests/json_from_string_test" has passed with:
  2 assertions out of 2 passed

Test case "misc_tests/asset_from_string_overflow" has passed with:
  24 assertions out of 24 passed

Test case "misc_tests/deterministic_randomness" has passed with:
  2 assertions out of 2 passed

Test case "misc_tests/deterministic_distributions" has passed with:
  6 assertions out of 6 passed

Test case "misc_tests/authority_checker" has passed with:
  124 assertions out of 124 passed

Test case "misc_tests/alphabetic_sort" has passed with:
  21 assertions out of 21 passed

Test case "misc_tests/transaction_test" has passed with:
  9 assertions out of 9 passed

Test suite "multi_index_tests" has passed with:
1 test case out of 1 passed
3 assertions out of 3 passed
Test case "multi_index_tests/multi_index_load" has passed with:
  3 assertions out of 3 passed

Test suite "eosio_msig_tests" has passed with:
7 test cases out of 7 passed
57 assertions out of 57 passed
Test case "eosio_msig_tests/propose_approve_execute" has passed with:
  8 assertions out of 8 passed

Test case "eosio_msig_tests/propose_approve_unapprove" has passed with:
  5 assertions out of 5 passed

Test case "eosio_msig_tests/propose_approve_by_two" has passed with:
  9 assertions out of 9 passed

Test case "eosio_msig_tests/propose_with_wrong_requested_auth" has passed with:
  2 assertions out of 2 passed

Test case "eosio_msig_tests/big_transaction" has passed with:
  8 assertions out of 8 passed

Test case "eosio_msig_tests/update_system_contract_all_approve" has passed with:
  12 assertions out of 12 passed

Test case "eosio_msig_tests/update_system_contract_major_approve" has passed with:
  13 assertions out of 13 passed

Test suite "payloadless_tests" has passed with:
2 test cases out of 2 passed
4 assertions out of 4 passed
Test case "payloadless_tests/test_doit" has passed with:
  2 assertions out of 2 passed

Test case "payloadless_tests/test_abi_serializer" has passed with:
  2 assertions out of 2 passed

Test suite "producer_schedule_tests" has passed with:
1 test case out of 1 passed
21 assertions out of 21 passed
Test case "producer_schedule_tests/producer_schedule_promotion_test" has passed with:
  21 assertions out of 21 passed

Test suite "ram_tests" has passed with:
1 test case out of 1 passed
31 assertions out of 31 passed
Test case "ram_tests/ram_tests" has passed with:
  31 assertions out of 31 passed

Test suite "resource_limits_test" has passed with:
9 test cases out of 9 passed
14 assertions out of 14 passed
Test case "resource_limits_test/elastic_cpu_relax_contract" has passed with:
  4 assertions out of 4 passed

Test case "resource_limits_test/elastic_net_relax_contract" has passed with:
  4 assertions out of 4 passed

Test case "resource_limits_test/enforce_block_limits_cpu" has passed with:
  1 assertion out of 1 passed

Test case "resource_limits_test/enforce_block_limits_net" has passed with:
  1 assertion out of 1 passed

Test case "resource_limits_test/enforce_account_ram_limit" has passed with:
  1 assertion out of 1 passed

Test case "resource_limits_test/enforce_account_ram_limit_underflow" has passed with:
  1 assertion out of 1 passed

Test case "resource_limits_test/enforce_account_ram_limit_overflow" has passed with:
  1 assertion out of 1 passed

Test case "resource_limits_test/enforce_account_ram_commitment" has passed with:
  1 assertion out of 1 passed

Test case "resource_limits_test/sanity_check" has passed

Test suite "special_account_tests" has passed with:
1 test case out of 1 passed
15 assertions out of 15 passed
Test case "special_account_tests/accounts_exists" has passed with:
  15 assertions out of 15 passed

Test suite "tic_tac_toe_tests" has passed with:
1 test case out of 1 passed
8 assertions out of 8 passed
Test case "tic_tac_toe_tests/tic_tac_toe_game" has passed with:
  8 assertions out of 8 passed

Test suite "wasm_tests" has failed with:
44 test cases out of 45 passed
1 test case out of 45 failed
1 test case out of 45 aborted
162 assertions out of 163 passed
1 assertion out of 163 failed
Test case "wasm_tests/basic_test" has passed with:
  13 assertions out of 13 passed

Test case "wasm_tests/prove_mem_reset" has passed with:
  11 assertions out of 11 passed

Test case "wasm_tests/abi_from_variant" has passed with:
  3 assertions out of 3 passed

Test case "wasm_tests/f32_tests" has passed with:
  2 assertions out of 2 passed

Test case "wasm_tests/f32_test_bitwise" has passed with:
  2 assertions out of 2 passed

Test case "wasm_tests/f32_test_cmp" has passed with:
  2 assertions out of 2 passed

Test case "wasm_tests/f64_tests" has passed with:
  2 assertions out of 2 passed

Test case "wasm_tests/f64_test_bitwise" has passed with:
  2 assertions out of 2 passed

Test case "wasm_tests/f64_test_cmp" has passed with:
  2 assertions out of 2 passed

Test case "wasm_tests/f32_f64_conversion_tests" has passed with:
  1 assertion out of 1 passed

Test case "wasm_tests/f32_f64_overflow_tests" has passed with:
  48 assertions out of 48 passed

Test case "wasm_tests/misaligned_tests" has passed with:
  4 assertions out of 4 passed

Test case "wasm_tests/weighted_cpu_limit_tests" has passed with:
  8 assertions out of 8 passed

Test case "wasm_tests/check_entry_behavior" has passed with:
  3 assertions out of 3 passed

Test case "wasm_tests/check_entry_behavior_2" has passed with:
  3 assertions out of 3 passed

Test case "wasm_tests/simple_no_memory_check" has passed with:
  2 assertions out of 2 passed

Test case "wasm_tests/check_global_reset" has passed with:
  3 assertions out of 3 passed

Test case "wasm_tests/stl_test" has passed with:
  3 assertions out of 3 passed

Test case "wasm_tests/big_memory" has passed with:
  2 assertions out of 2 passed

Test case "wasm_tests/table_init_tests" has passed with:
  2 assertions out of 2 passed

Test case "wasm_tests/memory_init_border" has passed with:
  3 assertions out of 3 passed

Test case "wasm_tests/imports" has passed with:
  2 assertions out of 2 passed

Test case "wasm_tests/nested_limit_test" has passed with:
  5 assertions out of 5 passed

Test case "wasm_tests/lotso_globals" has passed with:
  2 assertions out of 2 passed

Test case "wasm_tests/offset_check" has passed with:
  24 assertions out of 24 passed

Test case "wasm_tests/noop" has passed with:
  4 assertions out of 4 passed

Test case "wasm_tests/eosio_abi" has passed with:
  3 assertions out of 3 passed

Test case "wasm_tests/check_big_deserialization" was aborted with:
  1 assertion out of 2 passed
  1 assertion out of 2 failed

Test case "wasm_tests/check_table_maximum" has passed

Test case "wasm_tests/protected_globals" has passed

Test case "wasm_tests/lotso_stack_1" has passed

Test case "wasm_tests/lotso_stack_2" has passed

Test case "wasm_tests/lotso_stack_3" has passed

Test case "wasm_tests/lotso_stack_4" has passed

Test case "wasm_tests/lotso_stack_5" has passed

Test case "wasm_tests/lotso_stack_6" has passed

Test case "wasm_tests/lotso_stack_7" has passed

Test case "wasm_tests/lotso_stack_8" has passed

Test case "wasm_tests/lotso_stack_9" has passed

Test case "wasm_tests/apply_export_and_signature" has passed

Test case "wasm_tests/trigger_serialization_errors" has passed

Test case "wasm_tests/protect_injected" has passed

Test case "wasm_tests/mem_growth_memset" has passed

Test case "wasm_tests/fuzz" has passed

Test case "wasm_tests/getcode_checks" has passed

Test suite "whitelist_blacklist_tests" has passed
Test case "whitelist_blacklist_tests/actor_whitelist" has passed

Test case "whitelist_blacklist_tests/actor_blacklist" has passed

Test case "whitelist_blacklist_tests/contract_whitelist" has passed

Test case "whitelist_blacklist_tests/contract_blacklist" has passed

Test case "whitelist_blacklist_tests/action_blacklist" has passed

Test case "whitelist_blacklist_tests/blacklist_eosio" has passed

Test case "whitelist_blacklist_tests/deferred_blacklist_failure" has passed

Test case "whitelist_blacklist_tests/blacklist_onerror" has passed

I know it will be compile well,but when we compile the smartcontract it will be failed.So I haven't run “eosio_install.sh” yet.
Anybody who can help me.

just now i add virtual ram，and this problem had been solved，all of the tests are passed.


Duplicate id! Old RelationalModel=ServerModel, new RelationalModel=ServerModel

I cant use your master right now... do you know what might be the problem? i know you were working on removing the relational models maybe there is somethign still hanging around

Oops. That was an oversight. Does #ddf09bc1ef6b446158395cd926df2e0bbe5b8160 fix it?


Paper on RASH for SePublica 2015

Dear Mike,
Some of my colleagues and I have written a first draft of a paper describing the RASH framework to submit to the SePublica 2015 Workshop (http://sepublica.mywikipaper.org/drupal/). You can find the paper in the directory “papers”. Of course, it is written in RASH :-)
I’ve also added you as co-author since your amazing contribution to the framework in the past two weeks. It would be terrific if you could spend a bit of your time in reading the paper and modifying it where you think is appropriate – however I totally understand whether you have not time to dedicate to this task, don’t worry.
I will work again on the paper only on Monday Mar 15 afternoon (CET time) in order to finalise and submitting it to the workshop.
Thanks in advance for your time.
Have a nice day :-)
S.

Hi @essepuntato Thanks—yes I’ll look through the paper and get back to you by Monday morning your time

Hi @essepuntato I look through the paper and don't have any comments except to say think it’s great and I’m looking forward to hearing about how it’s received.
One note fwiw: While I work for the W3C I'm also a professor at Keio University so feel free to include mention of Keio in the authorship section if you think it helps. Certainly as far as readership here in Japan goes, it might make some readers here a bit more inclined to look further into the paper.

OK, thanks Mike. I've added also your other affiliation in the new revision I've just committed to the repo.

Hi all,
First of all, a news: the deadline for submitting the paper to SePublica has changed. The new one is Monday 23rd of March.
As a consequence, I've modified the paper according to several comments received from you in the past few days. I'm just asking you now to read the current version of the paper and to add/modify where you think is more appropriate, preferably before Monday 23rd, in order to be able to finalise the paper before the deadline.
Thanks all of you for your help!
Have a nice day :-)
S.

OK, thanks—will take another look

The paper was submitted on Tuesday (March 24) at 11:30 CET.


Discord and email are both broken

<EMAIL_ADDRESS>- this is undeliverable
https://discord.gg/donetsk - this fails in Discord, says it's an invalid invitation

donetsk discord link is defunct due to lack of boosts.
i can't speak for the email, i don't control that. zero does.

Please leave relative issues about the discord server, dlls, executables, donetsk provided software @ https://support.donetsk.live
Please forward any complaints you have about the email to<EMAIL_ADDRESS>


Stackoverflow exception in AbstractValidator.Validate

I have my application running with ASP.NET MVC and IOC.  More specifically in the following line of the IValidator instance.
public override ValidationResult Validate(ValidationContext<T> context)
        {
            return this.Validate(context.InstanceToValidate, ruleSet: AllValidationRulesetNames);
        }

The model sent does not implements any validator, and the default is triggering the Validate.
public class ReportPageNavigationModel
    {
        public ReportPage CurrentPage { get; set; }
    }

Before updating FluentValidation to version 7.5  it was working.

You're creating an infinite loop.
The overload of Validate you're calling internally calls Validate again passing in a ValidationContext<T>, so you're creating an infinite loop. You should not call the Validate extension methods from inside the main Validate method as they just call back into it! This is the internal implementation of the method you're calling:
https://github.com/JeremySkinner/FluentValidation/blob/3a1648cf2062a51baa22d3a57de3f40acfb3870e/src/FluentValidation/DefaultValidatorExtensions.cs#L861-L877
You should implement your override like this:
public override ValidationResult Validate(ValidationContext<Person> context) {
	var newContext = new ValidationContext<Person>(context.InstanceToValidate, context.PropertyChain, new RulesetValidatorSelector(AllValidationRulesetNames));
	return base.Validate(newContext);
}

(Note, This is not new behaviour and will also be an issue in versions prior to 7.5.)

Thanks for your help.
Indeed the implementation changed quite a lot, we come from version 3.4.6.  Now we having working.
Again, thanks for the help and your quick response.

Wow, that's a very old version! Glad you got it working.


[Sharing NG] Replace dav property public-link-permission with type

Describe the bug
When doing a PROPFIND on a public space, the response contains a dav property public-link-permission to indicate the permissions for this link. However, these permissions are being represented via permission bits, which is the old (deprecated) way of the OCS API.
Web needs this information to distinguish between the link types view and uploadOnly, since these can't be distinguished solely by the webdav permissions.
Steps to reproduce

Create a public link for a folder
Do a PROPFIND to list the resources for this folder (e.g. https://host.docker.internal:9200/remote.php/dav/public-files/CIlnOrnDLxMmPHx)
Check the server response for the first resource (= the share itself)

Expected behavior
There is a dav property that represents the link's type, since that's the graph property representing the permissions.
Actual behavior
The is a dav property public-link-permission.
cc @rhafer

@JammingBen What format do you expect for the public-link-permission?

@2403905
public-link-permission is the actual behaviour. The new property should reflect the link's type, so I'd name it public-link-type. It should be a simple string representing the type, e.g. view.


feat: update My Account page to split viewing and editing

:tada: This PR is included in version 1.47.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


@itembuy issue with return 1

When doing return 1 on @itembuy, it still seems to do the speech that says the player bought the items, saying how much it was and thanking them for their business. return 1 should stop all actions I think.

on=@itembuy
if (<act.type>==t_figurine)
if (<eval +> > )
argo.say Your order cannot be fulfilled, please try again.
return 1
endif
endif

Fix Sent

fix confirmed, thank you!


Prepare v0.2.0 release

Includes initial release process documentation
Signed-off-by: James Taylor<EMAIL_ADDRESS>

Splitting in to two PRs...


Unclear error message from ClasspathFileSource.getZipEntryUri

This code:
https://github.com/tomakehurst/wiremock/blob/master/src/main/java/com/github/tomakehurst/wiremock/common/ClasspathFileSource.java#L107
    private URI getZipEntryUri(final String name) {
        ZipEntry zipEntry = find(forEnumeration(zipFile.entries()), new Predicate<ZipEntry>() {
            public boolean apply(ZipEntry input) {
                return input.getName().equals(path + "/" + name);
            }
        });
        return getUriFor(zipEntry);
    }

May fail with something like:
java.util.NoSuchElementException
        at com.google.common.collect.AbstractIterator.next(AbstractIterator.java:157)
        at com.google.common.collect.Iterators.find(Iterators.java:672)
        at com.github.tomakehurst.wiremock.common.ClasspathFileSource.getZipEntryUri(ClasspathFileSource.java:107)
        at com.github.tomakehurst.wiremock.common.ClasspathFileSource.getBinaryFileNamed(ClasspathFileSource.java:94)
        at com.github.tomakehurst.wiremock.http.StubResponseRenderer.renderDirectly(StubResponseRenderer.java:94)
        at com.github.tomakehurst.wiremock.http.StubResponseRenderer.buildResponse(StubResponseRenderer.java:65)
        at com.github.tomakehurst.wiremock.http.StubResponseRenderer.render(StubResponseRenderer.java:54)
        at com.github.tomakehurst.wiremock.http.AbstractRequestHandler.handle(AbstractRequestHandler.java:47)
        at com.github.tomakehurst.wiremock.servlet.WireMockHandlerDispatchingServlet.service(WireMockHandlerDispatchingServlet.java:100)

And can be changed to fail with something more helpful. It would be helpful if the error included a list of all the entries that did not match.

More than happy to merge a PR if you feel like creating one


Linkage error when crosscompiling for Windows with mono

Godot version:

3418f76a9eab9f496e5b26310bd3bc1125b8119b
OS/device including version:

Arch Linux
Issue description:

When crosscompiling for Windows with mono enabled I got this linkage error at the end of compilation
[100%] /usr/lib/gcc/x86_64-w64-mingw32/9.1.0/../../../../x86_64-w64-mingw32/bin/ld: cannot find -lo
/usr/lib/gcc/x86_64-w64-mingw32/9.1.0/../../../../x86_64-w64-mingw32/bin/ld: cannot find -ln
/usr/lib/gcc/x86_64-w64-mingw32/9.1.0/../../../../x86_64-w64-mingw32/bin/ld: cannot find -lo
/usr/lib/gcc/x86_64-w64-mingw32/9.1.0/../../../../x86_64-w64-mingw32/bin/ld: cannot find -l-
/usr/lib/gcc/x86_64-w64-mingw32/9.1.0/../../../../x86_64-w64-mingw32/bin/ld: cannot find -l2
/usr/lib/gcc/x86_64-w64-mingw32/9.1.0/../../../../x86_64-w64-mingw32/bin/ld: cannot find -l.
/usr/lib/gcc/x86_64-w64-mingw32/9.1.0/../../../../x86_64-w64-mingw32/bin/ld: cannot find -l0
/usr/lib/gcc/x86_64-w64-mingw32/9.1.0/../../../../x86_64-w64-mingw32/bin/ld: cannot find -l-
/usr/lib/gcc/x86_64-w64-mingw32/9.1.0/../../../../x86_64-w64-mingw32/bin/ld: cannot find -ls
/usr/lib/gcc/x86_64-w64-mingw32/9.1.0/../../../../x86_64-w64-mingw32/bin/ld: cannot find -lg
/usr/lib/gcc/x86_64-w64-mingw32/9.1.0/../../../../x86_64-w64-mingw32/bin/ld: cannot find -le
/usr/lib/gcc/x86_64-w64-mingw32/9.1.0/../../../../x86_64-w64-mingw32/bin/ld: cannot find -ln
collect2: error: ld returned 1 exit status
scons: *** [bin/godot.windows.opt.tools.64.mono.exe] Error 1
scons: building terminated because of errors.
The problem appears to be in this line:
https://github.com/godotengine/godot/blob/3418f76a9eab9f496e5b26310bd3bc1125b8119b/modules/mono/build_scripts/mono_configure.py#L127
When changed the line above to env.Append(LIBS=[mono_lib_name]) compilation completes successfully
Steps to reproduce:
Build from source with
scons -j8 p=windows target=release_debug tools=yes module_mono_enabled=yes mono_prefix=/path/to/windows/mono bits=64
The mono directory i have copied from windows installation

What does the mono_lib_name variable prints?

What does the mono_lib_name variable prints?
It prints mono-2.0-sgen. But if I print env.Dump(), then in LIBS section will be the following:

'LIBS': [<SCons.Node.FS.File object at 0x563ae45fa5d0>, [<SCons.Node.FS.File object at 0x563ae45da630>], [<SCons.Node.FS.File object at 0x563ae4596970>], [<SCons.Node.FS.File object at 0x563ae440f4f0>], [<SCons.Node.FS.File object at 0x563ae439aa90>], [<SCons.Node.FS.File object at 0x563ae4370050>], [<SCons.Node.FS.File object at 0x563ae479bf90>], 'mingw32', 'opengl32', 'dsound', 'ole32', 'd3d9', 'winmm', 'gdi32', 'iphlpapi', 'shlwapi', 'wsock32', 'ws2_32', 'kernel32', 'oleaut32', 'dinput8', 'dxguid', 'ksuser', 'imm32', 'bcrypt', 'avrt', 'uuid', 'm', 'o', 'n', 'o', '-', '2', '.', '0', '-', 's', 'g', 'e', 'n'],
I think that env.Append() treats mono_lib_name as a list and adds every individual character from that string to LIBS.

'LIBS': [<SCons.Node.FS.File object at 0x563ae45fa5d0>, [<SCons.Node.FS.File object at 0x563ae45da630>], [<SCons.Node.FS.File object at 0x563ae4596970>], [<SCons.Node.FS.File object at 0x563ae440f4f0>], [<SCons.Node.FS.File object at 0x563ae439aa90>], [<SCons.Node.FS.File object at 0x563ae4370050>], [<SCons.Node.FS.File object at 0x563ae479bf90>], 'mingw32', 'opengl32', 'dsound', 'ole32', 'd3d9', 'winmm', 'gdi32', 'iphlpapi', 'shlwapi', 'wsock32', 'ws2_32', 'kernel32', 'oleaut32', 'dinput8', 'dxguid', 'ksuser', 'imm32', 'bcrypt', 'avrt', 'uuid', 'm', 'o', 'n', 'o', '-', '2', '.', '0', '-', 's', 'g', 'e', 'n'],
I think that env.Append() treats mono_lib_name as a list and adds every individual character from that string to LIBS.

Thanks, I didn't understand what was actually happening until I read this. Saved me some time.


"page not found" is reported for "join as Volunteer" on "about Us -> Get Involved" page

open "https://fightpandemics.com"
Navigate to About Us Page and click on 'Get Involved' button
Click on 'Join as volunteer'

Issue: You will observe that 'Page not found' issues is displayed.
Refer below screen
https://user-images.githubusercontent.com/67168400/110247257-5de3b680-7f39-11eb-8e2d-07659f960def.MP4
Please note as this issue is reported in Production,, and exist in STG as well. Thanks

Please hold this issue until further confirmation from Yegor or Andrew from business perspective.
PR #2261 have been created for same.
Thanks


Links not working in pdf.js / Firefox 38.05

Links are not clickable in following document, only for Firefox / builtin pdf.js - other browsers/pdf viewers are working as intended:
https://www.apis.de/pub/docs/training/ApisTR02WI.pdf
-> Page 4, hotelasam

That PDF file doesn't actually contain any links, but just text styled to look like standard hyperlinks.
Those links can work in e.g. Adobe Reader, but only if you have enabled automatic creation of hyperlinks (this setting seems to default to on).
The issue is tracked in #3172, hence I'm closing this this as duplicate.

Thank you very much for claryfing this issue!


router * not working check page 404

I set * to match all routers that don't exist but it doesn't work
app.get('*', (req, res) => {
res.status(404).send({ url: ${req.originalUrl} not found });
});

fixed.


Build Fails: Out of Bounds

I'm submitting a ...
[x ] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[ ] question about how to use this project

Summary

Automerge succeeds but build fails on an Out Of Bound error for a listed tokens' Twitter URL

My PR: https://github.com/solana-labs/token-list/pull/23416

Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

issue fixed


Send a copy of repo manifest through garage-push

Depends on ~~https://github.com/advancedtelematic/aktualizr/pull/1438~~
https://github.com/advancedtelematic/aktualizr/pull/1440

One concern I have right now is that this PR is coupled with the aktualizr change: as we're using a recently added cli flag, the garage-push command will fail if used on an older aktualizr version.
This is not a major issue but can be inconvenient nonetheless, I'll try to see if there is a clean workaround for that.

One concern I have right now is that this PR is coupled with the aktualizr change: as we're using a recently added cli flag, the garage-push command will fail if used on an older aktualizr version.

What's the problem as long as we bump the aktualizr version as part of this PR? I think it's fine.

What's the problem as long as we bump the aktualizr version as part of this PR? I think it's fine.

It's a bit more coupling than necessary and could be annoying if we're trying to bisect some issue on aktualizr for example. But yes, not major.
Still, I just pushed a small change to first check if the option shows up in --help. If you think it makes things worse, we can drop it.


Add rxfetch

Rxfetch is a custom system fetching tool that is made in bash script.

Thanks for contribute.


[SPARK-12785][SQL] Add ColumnarBatch, an in memory columnar format for execution.

There are many potential benefits of having an efficient in memory columnar format as an alternate
to UnsafeRow. This patch introduces ColumnarBatch/ColumnarVector which starts this effort. The
remaining implementation can be done as follow up patches.
As stated in the in the JIRA, there are useful external components that operate on memory in a
simple columnar format. ColumnarBatch would serve that purpose and could server as a
zero-serialization/zero-copy exchange for this use case.
This patch supports running the underlying data either on heap or off heap. On heap runs a bit
faster but we would need offheap for zero-copy exchanges. Currently, this mode is hidden behind one
interface (ColumnVector).
This differs from Parquet or the existing columnar cache because this is not intended to be used
as a storage format. The focus is entirely on CPU efficiency as we expect to only have 1 of these
batches in memory per task. The layout of the values is just dense arrays of the value type.

This patch uses this class to decode parquet.
https://github.com/apache/spark/pull/10593

Test build #48897 has started for PR 10628 at commit 381492e.

Test build #48897 has finished for PR 10628 at commit 381492e.

This patch fails RAT tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
public abstract class ColumnVector
public final class ColumnarBatch
 public final class Row extends InternalRow
public final class OffHeapColumnVector extends ColumnVector
public final class OnHeapColumnVector extends ColumnVector

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/48897/
Test FAILed.

Merged build finished. Test FAILed.

Is this PR the first step to enable vectorized execution in Spark SQL or just for efficient serialization to use external components?

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/49194/
Test FAILed.

Test build #49195 has started for PR 10628 at commit 5b27f65.

Test build #49195 has finished for PR 10628 at commit 5b27f65.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/49195/
Test FAILed.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/49201/
Test FAILed.

Test build #49216 has started for PR 10628 at commit 36c8ddb.

Test build #49216 has finished for PR 10628 at commit 36c8ddb.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/49216/
Test PASSed.

I'm going to merge this. Thanks.

@nongli @davies
Hi, by implementing the feature this way we've eliminated every big-endian user from using this feature with Spark - Z systems, for example, or Power big-endian machines. Critical if we want Spark to be used by large industries such as those that IBM et al support.
Any intention to have this not rely on the byte ordering of the platform? putLittleEndian is not going to cut it when we're wanting to use Spark for handling large volumes of customer data that traditionally sits on big-endian systems.
Also, are there any design docs for this? I found the documentation for Tungsten (UnsafeRows) to be very useful for understanding and debugging purposes.

This is not an architectural limitation. We have just not implemented support for it and there are only a few methods that would need to be implemented to support big endian. It would be great if someone in the community working on big endian hardware could do this.
We don't rely on the byte ordering of the platform. The function you are referring to, putIntLittleEndian, is converting the input, which is little endian, to whatever the machine's endianness is. It doesn't specify what the host endian has to be. This is used in cases where the data is encoded on disk in a canonical binary format. On a big endian host, this would have to byte swap but I think that's inevitable as the on disk data had to pick an endianness (this is the code that's not implemented right now).
If you find places where spark requires a particular endianness, i'd consider that a bug.

So big endian implementations of  OffHeapColumnVector and OnHeapColumnVector are needed. I don't think we'd want to have an inline 'if (bigEndian)' in the relevent methods so it may be that we'd want to subclass those classes, override the methods which require handling big endian, and instantiate the big endian version in ColumnVector.allocate if on a BE platform?
xxxHeapColumnVector classes would have to lose the 'final' attribute.

I don't think it should be needed for OnHeap (it uses Platform.getInt which I think should work for both). For offheap, as far as I know, only a few of the puts that take byte[] as input would care. Subclassing or if(...) both sound fine to me.

We are actually seeing this issue in the OnHeap code as the byte array passed in to putIntLittleEndian is in little endian and the code is trying to read that with Platform.getInt, which on big endian platform will return the wrong value as it assumes the bytes are in big endian

@nongli I'm just about there with a solution for Big Endian platforms and will be using https://issues.apache.org/jira/browse/SPARK-14151 for the changes.
I have one question:
It is clear from the tests using Parquet that the byte array passed into putIntsLittleEndian is in little endian order. It is also the case that the byte array passed in to the putFloats and putDoubles has the values in little endian. Reversing the floats/doubles enables all the tests to pass.
In OffHeapColumnVector putDoubles(int rowId, int count, byte[] src, int srcIndex) if I assume input is LE then the org.apache.spark.sql.execution.vectorized.ColumnarBatchSuite.Double APIs test fails. This is because it is passing in a byte array of doubles that are in platform endian order (created with Platform.putDouble).
My question is: are the byte arrays always in little endian? This seems to be true for the Parquet sources?? If so then I can modify the testcase 'org.apache.spark.sql.execution.vectorized.ColumnarBatchSuite.Double APIs' to force the test data into LE.


Non human exception when wrong template name or catalog

When I miswrite the template_name it was appear this error:
(Rambafile): found unexpected ':' while scanning a plain scalar at line 38 column 38
(Psych::SyntaxError)

Will be great to have more clear error text, like "There aren't templates with name XXX in catalog YYY"

@MaksimBazarov can you specify the Rambafile templaes section contents? We are already handling this issue with an error: Cannot find test in any catalog. Try another name..

Closing the issue as outdated.


Adjust config for new composer-config-plugin

Q
A

Is bugfix?
✔

New feature?
❌

Breaks BC?
❌

Fixed issues
merge after https://github.com/yiisoft/composer-config-plugin/pull/124

Won't be merged, new config plugin was implemented: https://github.com/yiisoft/config


Analysis toolkit

Ideas for analysis toolkit:

[x] process mesh (read from meshes-x_yyyy.h5 tiles into dense array)
[x] process analysis/fields snapshots into dense array

Latest commit 8c046b255298630a8058ab2c7ae5c913caf45ddf implements this.


Debug Using Local LLM

Could not import duckduckgo-search python package. Please install it with pip install duckduckgo-search. (type=value_error)
tried pip install duckduckgo-search but this is still not working

There is currently no way to see whether the model is downloading

@ZackBradshaw Interesting, we'll have to implement our own LLM class

Issue Description
While attempting to run the llmexample.py file, I encountered an issue where the script hangs indefinitely. The script successfully creates a temporary directory at /tmp/tmp9sirzp06 and writes to _remote_module_non_scriptable.py. It also successfully loads faiss with AVX2 support. However, when it attempts to establish a HTTPS connection to huggingface.co, the script hangs and does not proceed further. I left it running overnight, but it still did not download the required resources.
Problem Analysis
I am currently having trouble identifying the root cause of this problem. It requires further investigation and troubleshooting.
Proposed Solutions
In the meantime, I have identified two potential alternatives for running inference on local models:

Text-gen webui: This project (link) has an extension that allows the use of local models as a drop-in replacement for the OpenAI API. Given that our code is set up to use the OpenAI API, this could potentially be the fastest way to get a proof of concept up and running. However, this approach is not without its own issues, which I am familiar with from previous work.

Petals: This project (link) allows the end user to run inference on any model on any hardware. It also provides an example project that demonstrates how to set up a WebSocket API and run inference in that manner. This could be a viable alternative for our needs.

I look forward to your feedback on these proposed solutions and any guidance on further troubleshooting the original issue.

@ZackBradshaw Yeah this is a dealbreaker, we need to get local models setup in with the huggingface model class, let's debug it and then we need to pass it into the agent and worker classes


Added screenshot of Kali Linux

ISSUE: #2
Added the drive link of screenshot

Hey @iking07
Thanks for opening this PR 🚀. Mentor will review your pull request soon and till then, keep contributing and stay calm.
Thanks for contributing in OpenCode'24 ✨✨!

@iking07 Please solve Task2 after making a separate PR with issue: #3, you will only receive points here for issue: #2

Hey @iking07
Your PR has been merged 🥳🥳 and you have earned 20 points.
Thanks for contributing in OpenCode'24 ✨✨


Issue starting gui?

Ran into this problem today.
[GYY73] 08:05:43 INFO: Starting web GUI on https://<IP_ADDRESS>:8384/
[GYY73] 08:05:44 FATAL: Cannot start GUI: listen tcp: too many colons in address       https://localhost:8384/

Setting <gui enabled="false".... bypasses the error, but no gui.
I do not see another service running on that port.
Any suggestions would be appreciated.
an other may be relevant issues is that the windows gui is always https. No matter the option selected.

That's an incompatibility with v0.12 (it would have been useful to state that you were using a beta in the issue!).
See syncthing/syncthing#2371

Sorry. I did not realize I was using beta.

I've confirmed that v0.12-beta4 seems to fix this.


[release-4.8] Bug 2036042: Bump the elasticsearch's log4j 2.x version

/label backport-risk-assessed

/cherry-pick-approved

Manually adding the CPA label as Peter had ack-ed it (but need to prefix the comment with /label ...)

/cherry-pick release-4.7


Add integration tests for android

Add integration tests for all plugin methods.
Note: No unit tests because all functionality is a "pass thru"

closed in #9


file checksums are not included in the installed-db

If you run e.g. apk manifest busybox on the wolfi-base image, you get:
/ # apk manifest busybox
WARNING: opening from cache https://packages.wolfi.dev/os: No such file or directory
(null):  var/busybox
(null):  var/securetty
(null):  var/lib/db/sbom/busybox-1.36.0-r0.spdx.json

The (null): is because there is no checksum for the file entry.
Additionally the paths are wrong, var/busybox is supposed to be bin/busybox.

cc @deitch

Looks like the installed db file is messed up. Well, I did say that, in my comparisons between native and apk-tools, I found some differences I didn't like. This definitely is one of them. Forcing function to clean it up.

Interesting. I can reproduce it with just busybox:
contents:
  keyring:
    - https://packages.wolfi.dev/os/wolfi-signing.rsa.pub
  repositories:
    - https://packages.wolfi.dev/os
  packages:
    - busybox

The installed file shows things out of place and missing the hashes:
F:bin
F:etc
F:sbin
F:tmp
M:0:0:0777
F:usr
F:var
R:busybox
a:0:0:0755
R:securetty
F:usr/bin
F:usr/sbin
F:usr/share
F:usr/share/man
F:usr/share/man/man1
F:var/cache
F:var/lib
F:var/cache/misc
F:var/lib/db
F:var/lib/db/sbom
R:busybox-1.36.0-r0.spdx.json

These lines should be at earlier places:
R:busybox
a:0:0:0755
R:securetty
``

But interestingly, if I do the same thing using alpine, it works:

```yaml
contents:
  repositories:
    - https://dl-cdn.alpinelinux.org/alpine/v3.16/main
  packages:
    - busybox

The relevant part of the installed file:
F:bin
R:busybox
a:0:0:0755
R:sh
a:0:0:0777
F:etc
R:securetty
R:udhcpd.conf
F:etc/logrotate.d
R:acpid
F:etc/network
F:etc/network/if-down.d
F:etc/network/if-post-down.d
F:etc/network/if-post-up.d
F:etc/network/if-pre-down.d
F:etc/network/if-pre-up.d
F:etc/network/if-up.d
R:dad
a:0:0:0775
F:sbin
F:tmp
M:0:0:0777
F:usr
F:usr/sbin
F:usr/share
F:usr/share/udhcpc
R:default.script
a:0:0:0755
F:var
F:var/cache
F:var/cache/misc
F:var/lib
F:var/lib/udhcpd

In all case, the usual command:
apko build --arch amd64 /tmp/apko.yaml busybox /tmp/output.tar

Still missing the hashes in both cases, but the changed ordering is surprising.

Got that part. OK


Installing from the Snap Store makes the application awkward

I first installed this application from the Snap Store and found this application is not good because it takes a long time to start and cannot access files from the removable storage. And I uninstalled and reinstall this application with the Deb file. Now this application starts fast and of course no issue about accessing files from the removable storage.

I think the snap may need special permission to have the snap access removable media... will leave issue open for now until I find out. As for startup times, that'll probably have more to do with the snap VM rather than the app itself... so may very well be outside of my control.


Remove ignored files

@henrykironde - can you rebase this on the current master and see if it passes. It would definitely be nice to get this clean up in.

I have a meeting with Ben tomorrow, I will clean up after the meeting.


[HPRO-1228] Fix WQ site & org filter unpaired option issue

Q
A

Target Release?
<IP_ADDRESS>

Bug fix?
✅

New feature?
❌

Database migration?
❌

New configuration?
❌

Composer updates?
❌

NPM updates?
❌

Jira Ticket(s)
HPRO-1228

Closing this PR and creating new one


Update Remote Grid execution configuration

The "DesiredCapabilities" object is crucial to configuring remote execution on the Selenium Grid. Updated so this is passed from the program using Crawljax as a library.

Resolves #528


docs(git-clone): correct path example to not use the repo name

After #124, we now automatically append the path with the repo name, so the example should be changed to pass only the base directory as the path input.

@mafredri Yes, I agree, but that would be a breaking change. We do have versioning now, and Depedanbot should handle version bumps, too. Unfortunately, Dependabot can not suggest a change of input variable names. That is why I am avoiding renaming inputs as this is out top used module.

@matifali I agree about breaking, but to be fair, this change is breaking too. If someone had previously configured a path, it would change due to #124m, no?

@mafredri Hmm, yes. So let's change it. What about base_dir?


bootstrap3 model.js

code :
edit
edit
edit

removeData()  Not triggered when hidden
Instead, you can see the content being replaced when you open it second times？
I don't want to see the process of content being replaced.
How to solve it ？

Bootstrap 3 is essentially in maintenance mode as we focus on working towards a stable v4. As such, we're only accepting changes to v3's code on a case-by-case basis, usually only for critical bug fixes or docs improvements.


Is this still under active development?

I am intrigued by the idea, but it seems like there haven't been any recent commits.

I would like to help out... Got some (easy to implement) idea's and it looks like I just found a bug that I will try to fix.

Would be great if someone could maintain an updated fork.

I am sort of doing that here https://github.com/tmrts/boilr

@Ilyes512 would that not be better as just a fork with issues enabled? I'm not a fan of all of the commits being attributed to you.

@jackwilsdon what? I did not change any of the original commits? I also added a disclaimer here https://github.com/Ilyes512/boilr#note So not sure what you mean with "commits being attributed to you". So please explain what you mean.
Maybe I should't have chosen to "hard" fork it, but I got a little "scared" after reading this https://www.niels-ole.com/ownership/2018/03/16/github-forks.html Did not wanted to deal with that chance.

It looks like your hard-fork has re-attributed all of the commits to you (I'm sure that was not your intent), although I'm not sure that there's all that much that can be done in this case (due to how GitHub manages who commits belong to).
I can understand your concern with GitHub's forks, but the issues listed in that article seem to relate to repositories which are already private. Those don't seem to apply here thankfully;

If the repository is deleted then one of the forks becomes the new base
If the repository is made private then one of the forks becomes the new base

Ah my apologies @Ilyes512, I see you've been adding additional commits! From the first page it looked like existing ones had been re-attributed to you. Sorry!


Ignore classes which implement the TestCase interface

The new path collection algorithm from f704f3c might be a bit over-agressive.
For example, it also collects the tests\commands\RecordCommandTest class from flightphp\active-record.
This prevents runway from working when active-record is installed.
By ignoring classes which implement PHPUnit\Framework\TestCase, I was able to get runway up and running again on my machine.

Great catch! And thanks for the fix!


chore(release): add release-plz

coverage: 76.797%. remained the same
when pulling 4aead28c91a871830f4905cfdb2db436edb90d39 on feat/release-plz
into a6ef831da2aae0d88e9e72a5bc5f57f541a67ce9 on main.


Initial implementation of a bump allocation "GC".

The gc is built for all platforms now.
The build and packaging happens before any tests are run.
I download 7zip and create our own compressed artifacts for future deployment to Unity. These artifacts include the unitygc dynamic library.
Bare bones implementation until I can further test in a Unity player. This runs simple HelloWorld .NET Core console applications.

Please re-review, I think this is ready to land now.

Actually, a few more TODO I need to fix.


Updated the kubefed controller manager to v0.1.0-rc3.

Fixed the bug for supporting Cluster scope kubefed controller manager.

/cc @sohankunkerkar

/lgtm

/approve


OpenIDConnect::Forbidden error on callback (insufficient scope)

Dear developer thank you for this gem repo. I've been trying to implement an authentication flow with OpenID Connect in our RoR application, but so far with no luck. I'm sorry if this is not the right place to ask the question, as I'm unsure if the issue is related to this gem (but it might).
I've set up the middleware config, and paths as described and a user is correctly redirected starting an OAuth flow. However the callback does not seem to hit the specified controller action but instead I see an error page.

The provided scope is [:openid, :rrn], changing the scope to only :openid or expanding it with other (unnecessary) options like :profile result in the same error.
I'm unsure what causes this error, but I would be very grateful if you'd be able to shed some light on the issue.
Thanks in advance.

Hi @Augustin-Grenne,
From the looks of it the OIDC provider is responding with 403 Forbidden when the Rails app + gem are attempting to exchange access token for user info. The most likely cause is that the access token does not support the requested scope (requested by the Rails app when making a call to OIDC provider’s user info endpoint).
When you visit the config_endpoint_url, what scopes are listed there?
By default if there is no manual configuration in the initializer for the scope, the gem applies for all scopes listed by the config_endpoint_url, but we can override manually specifying the needed scopes in the initializer. If the access token is not authorized to request a scope, can you please modify omniauth initializer to include following?
Rails.application.config.middleware.use OmniAuth::Builder do
  provider :oidc, {
    Your configuration for name, endpoints, etc.
    scope: [:openid], # let's try with only openid and nothing else, no :email or :group, etc.
    }
  }

Scope for :openid is usually always supported and see if this resolves your issue. If yes, you can try adding more scopes that are shown in the config_endpoint_url one by one until you find the one that is throwing 403 Forbidden. Once found, then just don't request it and list all other scopes in the initializer. If the problematic scope is absolutely necessary for your application, you will have to contact OIDC provider for support on how to properly to request that scope.
If that does not help, would you mind sharing config_endpoint_url or name of your OIDC provider and I can try to reproduce the issue on my side

@msuliq Thanks for your response.
The discovery/config endpoint url https://authenticatie-ti.vlaanderen.be/op/.well-known/openid-configuration lists two accepted scopes: openid and webid, adding only openid, as well as adding both scopes ([:openid, :webid]) to the omniauth initializer results in the aforementioned scope error.
Additionally leaving out the issuer, as in your 'simple provider' example results in an
undefined local variable or method `issuer' for #<OmniAuth::Strategies::OIDC>

@Augustin-Grenne I have tested out some of the hypothetical places in code that might not be handling this case but so far the gem code seems to work fine. Referring to generic OIDC documentation, 403 is thrown in case the access token that we obtained for a user does not have permissions from the OIDC provider to request JWT with user info. I looked into documentation for Flemish Access Management using in-browser translator and there is a paragraph saying that integration application has to explicitly mention that client will use the userinfo endpoint

@msuliq Thank you very much for all your help. I've checked our integration application and it seems we didn't check that box for some reason. I'll be in touch with our contact about this. However there's actually only one piece of information that our application need and that is the rrn (rijksregisternummer) which is a separate scope, in also in the integration application, which we did check. However this scope is not listed as 'acceptable' on the config endpoint. I'll ask my contact about that too. Do you know of a way to skip sending a request to the user info endpoint? That way I can verify the issue is indeed related to this as we expect. Which would be insightful while we wait on more info from my contact. Thanks again for your help.

Unfortunately, there is no config option to skip call to the userinfo_endpoint, since the whole point of this gem is to fetch user's data from that endpoint. One way to make sure that this call is the root cause would be to clone this repo, install the gem in your Rails app from your local directory:
gem 'omniauth_oidc', path: '/path_to_the_directory_with_cloned_repo'
First you will need to modify Gemfile to add the debugger of your preference, run bundle install and place a breakpoint right at the beginning of the user_info_from_access_tokenmethod incallback.rbfile before it makes http call to theuserinfo_endpoint. From there you should be able to see parameters of the request to the userinfo_endpoint` as well as server response

I've shot a lengthy email to my contact with our findings and to ask to make some changes in our integration. I hope to hear soon from them. But it might be until Tuesday, earliest, that I can resume with this.
I've cloned the repo in development and put the debugger where you said, but hit a JSON parse error before hitting the breakpoint. I didn't dig in much deeper as it doesn't seem the most optimal path to resolve my core issue.

Since you asked here is a full Network trace of the call (or were you more interested in the case when no issuer is provided?)
# Request
:authority: authenticatie-ti.vlaanderen.be
:method: GET
:path: /op/v1/auth?client_id=9547c460-8bef-435d-b16d-fea18a4823cc&nonce=8&redirect_uri=https%3A%2F%2Freview.bpart-staging.eu%2Fburgerbegroting%2Fvoters%2Fauth%2Foidc%2Fcallback&response_mode=query&response_type=code&scope=openid%20rrn&state=7
:scheme: https
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,image/avif,image/webp,image/apng,*/*;q=0.8,application/signed-exchange;v=b3;q=0.7
Accept-Encoding: gzip, deflate, br, zstd
Accept-Language: en-GB,en-US;q=0.9,en;q=0.8,nl;q=0.7
Cache-Control: max-age=0
Cookie: tbsession=YibQjIeWLb__46Z5WgQ.iBARrPHFaaentLBauqQbGE7rWUFju0kDl.DDvC6aMz0t; vo-authmethod=itsme; vo-cot=vo; PD_STATEFUL_1e86fa40-98d3-11e9-85af-f73b02aa33ed=%2Fsps; IV_JCT=%2Fsps; vo-taalkeuze=NL; AMWEBJCT!%2Fsps!JSESSIONID=2b5ed8e2776f8066~0000QYYnUrh4ewp2G8ZY5ZfvsU1:e304ab04-69c8-49a6-87e5-16310b9c8cfd:ed26dbec-5858-45c0-a942-6216cf3009c3:fa38f714-d063-41c6-b69a-2908653fd6c2; VOGTIANONUSER=rB/ge2aFf590swAWBrR8Ag==; AMWEBJCT!%2Fsps!https%3A%2F%2Fauthenticatie-ti.vlaanderen.be%2Fsps%2Fspfas2%2Fsaml20FIMSAML20=uuid933e50a1-4b24-4e6e-8483-d581c637ffa5; PD-H-SESSION-ID=1_+9XjySewIDmpYYix7uh45mXnuoewrZJPPdiH5RAkY0JpVqcb7BY=_AAAAAQA=_oxM8O+IYTf+cvXt9t9UZGi/mDuA=
Dnt: 1
Priority: u=0, i
Sec-Ch-Ua: "Not/A)Brand";v="8", "Chromium";v="126", "Google Chrome";v="126"
Sec-Ch-Ua-Mobile: ?0
Sec-Ch-Ua-Platform: "macOS"
Sec-Fetch-Dest: document
Sec-Fetch-Mode: navigate
Sec-Fetch-Site: same-origin
Sec-Gpc: 1
Upgrade-Insecure-Requests: 1
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/<IP_ADDRESS> Safari/537.36

# Response
Content-Type: text/html; charset=utf-8
Date: Wed, 03 Jul 2024 16:43:39 GMT
Location: https://review.bpart-staging.eu/burgerbegroting/voters/auth/oidc/callback?code=qUE02fxUP-c&state=7
P3p: CP="NON CUR OTPi OUR NOR UNI"
Referrer-Policy: no-referrer
Server: nginx
Strict-Transport-Security: max-age=31536000; includeSubDomains
Strict-Transport-Security: max-age=15768000
X-Content-Type-Options: nosniff
X-Correlation-Id: bcd90022-680d-487e-85ac-3fa1f7819519
X-Group-Correlation-Id: rB/ge2aFf590swAWBrR8Ag==
X-Old-Content-Length: 125
X-Vo-Op-Request-Id: ebd249dd-0c8b-4467-9738-a76f6a22bfa8
X-Xss-Protection: 1; mode=block

@Augustin-Grenne I published version 0.2.0 of this gem which has an optional parameter that will allow your app to skip the part of fetching data from the user_info_endpoint and it will return only access token-related parameters to the controller in your app.
There is also a new section in readme dedicated to this use case

@Augustin-Grenne have you been able to resolve this issue?

Dear @msuliq I'm happy to announce that my issue is resolved. Our contact changed our permission and being allowed to call the user info endpoint resulted in an error free flow. 🙌
I'm very grateful for your help debugging an fixing this issue. Even if skipping the user info endpoint might not be useful for most users, I think adding it as an optional configuration, is a great idea. Indeed I've included fetch_user_info: false in our config and everything works as expected. So thank you for releasing 0.2.0.
Since the initial error I saw is resolved, and wasn't directly related to this gem I'll close this issue. However there's another small issue that's currently holding me back from using your gem in production. Installing it required some other gems we're using to be downgraded for compatibility, namely: rack, rack-session, rackup, omniauth, omniauth-oauth2, omniauth-google-oauth2, omniauth-rails_csrf_protection. Some of them changed a major version, calling for unrelated code changes. Is this something your able/willing to look into and possibly fix and should I open another issue for it with more info?

Glad to hear that the issue is resolved. Please feel free to open another issue for the dependencies that need to be updated. I will look into them in the course of the next two weeks


Fix logging of val loss

My suggestion in https://github.com/Lightning-AI/litgpt/pull/1055 was missed. We can't log "n/a" as a scalar. Also, the val loss is already logged, we don't need to log it twice.

Arg sorry, and thanks for the fix!


Add coverage

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

Project coverage is 100.00%. Comparing base (c8cfcc9) to head (faad9a5).

Additional details and impacted files
@@            Coverage Diff            @@
##              main        #5   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            4         4
  Lines          248       256    +8
=========================================
+ Hits           248       256    +8

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


Create VariableGroup with Azure Key vault

Hi, I got this issue when creating a VariableGroup with Azure Key vault
error: azuredevops:index/variableGroup:VariableGroup resource 'key vault name' has a problem: "variable.0.value": conflicts with key_vault

Here is my code
const project = await devops.getProject({ name: 'Code' });
  //Create Vairable Group Link to Global Key Vault
  new devops.VariableGroup('MyGroup', {
    projectId: project.id,
    allowAccess: true,
    keyVault: {
      name: 'key vault name',
      serviceEndpointId: 'xxxxx-yyyyy-zzzzz-bbbb-xxxxxxx',
    },
    variables: [{ name: 'key vault variable name' }],
  });

The error implies that somehow the first element of variables has set the value property (which in your code hasn't happened), so this might a bug in the way the bridge is handling the default value and passing that in (vs. not specifying it at all).

Closing as duplicate of #52


Array inference

Fixes the final item in #394. The only problem is that infering the repeat cause some types to be infered twices.
i.e
fn test() {
    let y = unknown;
    [y, &y];
}

results in the following diff:
[11; 48) '{     ...&y]; }': ()
[21; 22) 'y': &{unknown}
[25; 32) 'unknown': &{unknown}
-[38; 45) '[y, &y]': [&&{unknown}]
+[38; 45) '[y, &y]': [&&{unknown};usize]
[39; 40) 'y': &{unknown}
+[39; 40) 'y': &{unknown}
[42; 44) '&y': &&{unknown}
[43; 44) 'y': &{unknown}

Should the code produce two inference results for 'y' and if not could any tell me what needs to change.

Thanks!
bors r+


lms in non-callback mode?

Is it possible to use LMS in tf.keras without using the callback? This is required when using iterative loop for training on batches. It is very hard to intercept all calls to LMS in appropriate places for all implemented callback methods.

The version of LMS that used Keras callbacks was used for TensorFlow 1.x. We did some initial testing and work with it on top of TensorFlow 2 but don't think we ever supported it that way in WML CE. It seems that you may be using TensorFlow 2 since you mention a custom iterative training loop.
Instead we wrote a new memory allocator-based LMS for TensorFlow which is what is contained in the master branch of this repository and was included in the TensorFlow 2 based versions of WML CE. I would suggest using that version.

To directly answer your question about using LMS in tf.keras without the callback, I don't think it's possible. TFLMSv2 (the TF 1.x graph based version of LMS), requires TensorFlow to run in graph mode. The callback is necessary so that t.keras calls LMS to add the swapping nodes into the graph after it builds the backward propagation nodes.


Add commands for credential management

Issue: #68

apparently if an rp is too dumb to set a name for the credential (like it is possible in my sandbox) this thing apparently breaks upon running list:
Relying Party       Username            Credential ID
-----------------------------------------------------
Traceback (most recent call last):
  File "/home/my1/.local/bin/solo", line 11, in <module>
    sys.exit(solo_cli())
  File "/home/my1/.local/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/home/my1/.local/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/home/my1/.local/lib/python3.6/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/my1/.local/lib/python3.6/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/my1/.local/lib/python3.6/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/my1/.local/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/my1/.local/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/home/my1/.local/lib/python3.6/site-packages/solo/cli/key.py", line 525, in cred_ls
    print("{:20}{:20}{}".format(rp_id, user['name'], cred_id_b64))

(line numbers not accurate as i have this and the file signing PR both monkeypatched in there)

Thanks for the report, will update the patch soon

bonus tip:
if #76 passes you can change the top few lines of every command's PIN request to this:
    client = solo.client.find(serial, udp=udp)
    if client.has_pin() is False:
        print ("Credential Management needs to have a PIN set up, please Set a PIN.")
        sys.exit(1)
    if not pin:
        pin = getpass.getpass("PIN: ")

(and drop the client.find that happens later)
to have users get a pretty error if a PIN isnt set yet

bonus error if no RKs stored:
my1@my1-qb:~$ solo key credential list
PIN:
Traceback (most recent call last):
  File "/home/my1/.local/bin/solo", line 11, in <module>
    sys.exit(solo_cli())
  File "/home/my1/.local/lib/python3.6/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/home/my1/.local/lib/python3.6/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/home/my1/.local/lib/python3.6/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/my1/.local/lib/python3.6/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/my1/.local/lib/python3.6/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/my1/.local/lib/python3.6/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/my1/.local/lib/python3.6/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/home/my1/.local/lib/python3.6/site-packages/solo/cli/key.py", line 527, in cred_ls
    rps = cm.enumerate_rps()
  File "/home/my1/.local/lib/python3.6/site-packages/fido2/ctap2.py", line 1071, in enumerate_rps
    n_rps = first[CredentialManagement.RESULT.TOTAL_RPS]
TypeError: 'NoneType' object is not subscriptable

as if stuff hadnt been crazy enough, it gets weirder.
Just Updated my Somu Secure (so sadly no somu-side debug) from 3.1.1 to 4 and it's weird.
getting RK info tells that it has zero keys stored, yet when actually attempting to use an rk it totally lets you do so. I cant check whether that given RK works or not as it was probably before I moved hosting so I dont have the old db with me, but it is weird none the less.

Just Updated my Somu Secure (so sadly no somu-side debug) from 3.1.1 to 4 and it's weird.

I think this is expected as we changed how RKs are represented in versions >= 3.2.0

maybe it might be useful then to either grill RKs or maybe if possible fix the RKs stored some way.

@My1 the reason we yanked release 3.2.0 (and instead released 4.x) is exactly because it's a breaking change (as signaled by major version bump).

Sure but it's kinda breaking in a really weird way and maybe it might be nice to have it break cleaner (like by grilling rks without wiping all) and not everyone is gonna read changelogs.

Yeah, I think we should actually prevent major updates on non-reset state keys (https://github.com/solokeys/solo-python/issues/77 is relevant). However we can't add that on existing keys...

well while not possible on device level the client could give a confirmation.
although ideally if a breaking change doesnt need a full reset it would be FAR better in my opinion, and if possible to avoid changes by adapting the changes, even better.

Let's please stop derailing review of the PR at hand.

okay I'll split this into an issue

Ping. Does this require more work?

you could throw in an error if

the device doesnt show the feature (e.g. solo outdated)
there is no PIN


Security Considerations Should Discuss Endpoint Disclosure

Section Number Identify the most specific section number the issue occurs (e.g. 4.1.2)
1:46.5
Issue Describe your issue. Don't write a book, but do include enough to indicate what you see as a problem.
The Security Considerations section should probably be updated to discuss the security considerations of storing and exposing endpoints in a directory.
Proposed Change Propose a resolution to your issue (e.g., suggested new wording or description of a way to address the issue). The committee might simply accept your suggested text. Even if they don't, it gives a good sense of what you are looking for. Leaving this blank means you can't imagine how to resolve the issue, which makes it easier for the committee to admit they can't imagine how to resolve it either and leave it unresolved.
Add some guidance on how to think about the implications of exposing endpoints in a directory.
Priority:

Low: Typo or other minor classification that an editor can manage. Requires no group discussion.

Closing per committee.


🌱 Bump controller-runtime to v0.15.2

as title

/test-centos-e2e-integration-main
/test-ubuntu-integration-main


bt4gprx.com doesnt work with thorium anymore

Windows 11 Last thorium version
https://github.com/user-attachments/assets/d0757cbf-076d-4f36-99ad-b95e77592a61
I tried with chrome browser it works again just thorium and firefox doesnt seem to work
https://bt4gprx.com/magnet/ZZeftoGTmD8DvzZue8eJYaS9ykZwgoTVF

You write "anymore". Did it work before?

You write "anymore". Did it work before?

yea it did before now it just a blank page

This script might help
https://gist.github.com/zhimiaoli/fc7c22a27feaa2cbf9ec4563fe860d30

I installed this script on greaysfork this fixed it

I installed this script on greaysfork this fixed it

I don't find it...
only this
https://greasyfork.org/it/scripts/508413-bt4g-limetorrents-enhanced-search


Custom xkbcomp copy and paste misfire only under Chrome browser

I get some quirky behavior under google-chrome-stable.
I've got a custom xkbcomp configuration that binds C-C and C-V to copy and paste.  Under my xkbcomp configuration I've got a type for Shift+Control-based hotkeys:
type "HOT_KEYABLE_ALPHABETIC" {
    modifiers= Shift+Control;
    map[Shift]= Level2;
    map[Control+Shift]= Level3;
    preserve[Control]= Control;
};

For 'c' and 'v', I've got bindings:
key <COPY> {         [        XF86Copy ] };
key <PAST> {         [       XF86Paste ] };
key <AB03> {
    type= "HOT_KEYABLE_ALPHABETIC",
    symbols[Group1]= [               c,               C ],
    actions[Group1]= [      NoAction(),      NoAction(), RedirectKey(key=<COPY>, clearmods=Shift+Control) ]
};
key <AB04> {
    type= "HOT_KEYABLE_ALPHABETIC",
    symbols[Group1]= [               v,               V ],
    actions[Group1]= [      NoAction(),      NoAction(), RedirectKey(key=<PAST>, clearmods=Shift+Control) ]
};

When I

enter Chrome,
highlight some text, 'asdf', in the address bar,
press 'c',
move my cursor to unhighlight,
and finally press 'v',

I get 'c' in place of the original 'asdf', and I get 'asdfv' inserted at the cursor position.  If I perform the same sequence of operations in a new Firefox session, then everything behaves as expected.  That is, the original 'asdf' maps to 'c', the final cursor position gets a 'v' inserted, and C-V is independent of 'asdf'.  If I poke at the configuration under xev, then I get my expected bindings.
I've just recently coped with the migration to Freon, so I suspect that Chrome is detecting its Freon environment and circumventing/incorporating my bindings in some goofball fashion.
croutonversion:
crouton: version git
release: precise
architecture: amd64
xmethod: xorg
targets: x11
host: version 6946.55.0 (Official Build) stable-channel candy
kernel: Linux localhost 3.10.18 #1 SMP Tue May 26 18:03:06 PDT 2015 x86_64 x86_64 x86_64 GNU/Linux
freon: yes

Hello @Popham,
I am a coder, but this message is not related to this issue. I am a friend of one of your former employers.
He has a matter of pressing importance to discuss with you. Since he is unfamiliar with GitHub he asked me to see if I could reach you on here. It is nothing bad - in fact, the situation is in your favor.
For further details, please contact me as soon as you can at<EMAIL_ADDRESS>Thanks,
Aron


Minor fix to Vitalik's lmd ghost.

I think this is a slight error in your implementation of Vitalik's algorithm. It seems the loop is running the same getClearWinner in each iteration.
This may help if you are benching all the algorithms.

Good spot, I somehow confused the calculation with the above line, thanks.


Slots not working with importWrappers when migrating to v2.x

Hey, we are using vue-lazy-hydration very extensively and started migrating to version 2.0.
However, when using named slots like this while the components are imported via importWrappers
<CustomComponent>
	<template #headline>Text</template>
	<template #button>Text</template>
</CustomComponent>
//
CustomComponent: hydrateWhenIdle(() => import('@package/components/CustomComponent.vue'))

the content doesn't seem to get rendered.
Using it via <LazyHydrate /> fixed the issue for us. But we would like to know why.

Hello Kilian! Thanks for reporting this issue! I just realized that I made a mistake when I implemented the import wrappers. I'm working on it. In the meantime you can stick to v1 or use <LazyHydrate/>


Update README.md to include emmet script

Otherwise it fails using 2.0.0.

Coverage remained the same at 91.096% when pulling 8c9e45773934495faf3fc72e8a7769afa8fc2865 on antoineleclair:master into 3c0eb500ce5d813a247dd671bedb4257fcb7b3d4 on chemerisuk:master.

Thanks!


mavenCentral

Please add version 10.0.5 to mavenCentral

Hi, you can use older version thorough jitpack.

can you tell me how to add it, until it turned out to be done, probably we are doing something wrong

thanks in advance


Allow to create custom insets

As I understand currently your code allows to change bottom sheet height only. What about to allow to customize layout more?

Hi @gerchicov-vg
You can find it at https://github.com/OhKanghoon/FloatingBottomSheet/pull/14.


Addressing checkstyle

Enable checkstyle on more modules and address violations.

I ran into a few issues I couldn't resolve with some new files since the PR.  disabled checkstyle for autconf and ollama.
Can fix in a subsequent pass.
merged in e72ab6ba250adeebec0714f6a781d82c335e93a5