EOS v2.0.5 can't sync block,pls help!

all-new Ubuntu18.04 system,install the lastest EOS version(v2.0.5),it can't sync block,how to solve the problem?

the error message as follow:error 2020-04-30T06:49:56.356 net-1     net_plugin.cpp:2369           operator()           ] Closing connection to:mainnet.eosamsterdam.net:9876

Need more of the log and your config.ini and command line arguments.

it seems that the node can't be connected.
info  2020-04-30T15:57:12.892 nodeos    platform_timer_accurac:62     compute_and_print_ti ] Checktime timer accuracy: min:3us max:89us mean:6us stddev:2us
info  2020-04-30T15:57:12.893 nodeos    http_plugin.cpp:715           plugin_initialize    ] configured http to listen on <IP_ADDRESS>:8888
info  2020-04-30T15:57:12.893 nodeos    main.cpp:106                  main                 ] nodeos version v2.0.5 v2.0.5-de78b49b5765c88f4e005046d1489c3905985b94
info  2020-04-30T15:57:12.893 nodeos    main.cpp:107                  main                 ] nodeos using configuration file /data/data/config.ini
info  2020-04-30T15:57:12.893 nodeos    main.cpp:108                  main                 ] nodeos data directory is /data/data
info  2020-04-30T15:57:12.893 nodeos    chain_plugin.cpp:1121         plugin_startup       ] starting chain in read/write mode
info  2020-04-30T15:57:12.893 nodeos    chain_plugin.cpp:1129         plugin_startup       ] Blockchain started; head block is #1
info  2020-04-30T15:57:12.893 nodeos    http_plugin.cpp:793           plugin_startup       ] start listening for http requests
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/node/get_supported_apis
info  2020-04-30T15:57:12.894 nodeos    chain_api_plugin.cpp:73       plugin_startup       ] starting chain_api_plugin
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_info
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/abi_bin_to_json
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/abi_json_to_bin
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_abi
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_account
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_activated_protocol_features
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_block
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_block_header_state
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_code
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_code_hash
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_currency_balance
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_currency_stats
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_producer_schedule
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_producers
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_raw_abi
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_raw_code_and_abi
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_required_keys
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_scheduled_transactions
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_table_by_scope
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_table_rows
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/get_transaction_id
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/push_block
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/push_transaction
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/push_transactions
info  2020-04-30T15:57:12.894 nodeos    http_plugin.cpp:890           add_handler          ] add api url: /v1/chain/send_transaction
info  2020-04-30T15:57:12.894 nodeos    net_plugin.cpp:3413           plugin_startup       ] my node_id is 3478d939e706895d8d89cb27ea208518cdcf46e2a3ef69628b96c7c4bc4d12ad
info  2020-04-30T15:57:12.894 nodeos    net_plugin.cpp:3469           plugin_startup       ] starting listener, max clients is 4
info  2020-04-30T15:57:12.894 nodeos    net_plugin.cpp:816            connection           ] creating connection to peer.main.alohaeos.com:9876
info  2020-04-30T15:57:12.894 nodeos    net_plugin.cpp:816            connection           ] creating connection to mainnet.eosamsterdam.net:9876
info  2020-04-30T15:57:12.894 nodeos    net_plugin.cpp:816            connection           ] creating connection to seed.eoscleaner.com:9876
info  2020-04-30T15:57:12.894 nodeos    net_plugin.cpp:816            connection           ] creating connection to p2p.eosflare.io:9876
info  2020-04-30T15:57:12.894 nodeos    net_plugin.cpp:816            connection           ] creating connection to fullnode.eoslaomao.com:443
info  2020-04-30T15:57:12.894 nodeos    net_plugin.cpp:816            connection           ] creating connection to mainnet.eoslaomao.com:443
info  2020-04-30T15:57:12.894 nodeos    net_plugin.cpp:816            connection           ] creating connection to peer1.eosphere.io:9876
info  2020-04-30T15:57:12.894 nodeos    net_plugin.cpp:816            connection           ] creating connection to p2p.eossweden.org:9876
info  2020-04-30T15:57:12.894 nodeos    net_plugin.cpp:816            connection           ] creating connection to eos.okpool.top:9876
info  2020-04-30T15:57:12.894 nodeos    net_plugin.cpp:816            connection           ] creating connection to api3.tokenika.io:9876
info  2020-04-30T15:57:12.894 net-0     net_plugin.cpp:2141           operator()           ] host: mainnet.eosamsterdam.net port: 9876
info  2020-04-30T15:57:12.895 nodeos    producer_plugin.cpp:947       plugin_startup       ] producer plugin:  plugin_startup() begin
info  2020-04-30T15:57:12.895 net-1     net_plugin.cpp:2141           operator()           ] host: peer.main.alohaeos.com port: 9876
info  2020-04-30T15:57:12.895 net-1     net_plugin.cpp:2141           operator()           ] host: p2p.eosflare.io port: 9876
info  2020-04-30T15:57:12.895 net-1     net_plugin.cpp:2141           operator()           ] host: fullnode.eoslaomao.com port: 443
info  2020-04-30T15:57:12.895 net-1     net_plugin.cpp:2141           operator()           ] host: mainnet.eoslaomao.com port: 443
info  2020-04-30T15:57:12.895 net-1     net_plugin.cpp:2141           operator()           ] host: peer1.eosphere.io port: 9876
info  2020-04-30T15:57:12.895 net-1     net_plugin.cpp:2141           operator()           ] host: p2p.eossweden.org port: 9876
info  2020-04-30T15:57:12.895 net-1     net_plugin.cpp:2141           operator()           ] host: eos.okpool.top port: 9876
info  2020-04-30T15:57:12.895 net-1     net_plugin.cpp:2141           operator()           ] host: api3.tokenika.io port: 9876
info  2020-04-30T15:57:12.895 nodeos    producer_plugin.cpp:983       plugin_startup       ] producer plugin:  plugin_startup() end
info  2020-04-30T15:57:12.895 net-0     net_plugin.cpp:2141           operator()           ] host: seed.eoscleaner.com port: 9876
info  2020-04-30T15:57:13.132 net-1     net_plugin.cpp:1070           operator()           ] Sending handshake generation 1 to peer.main.alohaeos.com:9876, lib 1, head 1, id bcf2f448225d0996
info  2020-04-30T15:57:13.146 net-0     net_plugin.cpp:1070           operator()           ] Sending handshake generation 1 to mainnet.eosamsterdam.net:9876, lib 1, head 1, id bcf2f448225d0996
warn  2020-04-30T15:57:13.688 net-1     net_plugin.cpp:2673           handle_message       ] ["peer.main.alohaeos.com:9876" <IP_ADDRESS>:9876]received go_away_message, reason = wrong chain
info  2020-04-30T15:57:13.688 net-1     net_plugin.cpp:943            _close               ] closing 'peer.main.alohaeos.com:9876', peer.main.alohaeos.com:9876
info  2020-04-30T15:57:13.959 net-0     net_plugin.cpp:1070           operator()           ] Sending handshake generation 1 to mainnet.eoslaomao.com:443, lib 1, head 1, id bcf2f448225d0996
info  2020-04-30T15:57:13.970 net-1     net_plugin.cpp:2350           operator()           ] Peer closed connection
error 2020-04-30T15:57:13.970 net-1     net_plugin.cpp:2369           operator()           ] Closing connection to: mainnet.eoslaomao.com:443
info  2020-04-30T15:57:13.970 net-1     net_plugin.cpp:943            _close               ] closing 'mainnet.eoslaomao.com:443', mainnet.eoslaomao.com:443
info  2020-04-30T15:57:14.022 net-0     net_plugin.cpp:1070           operator()           ] Sending handshake generation 1 to fullnode.eoslaomao.com:443, lib 1, head 1, id bcf2f448225d0996
info  2020-04-30T15:57:14.070 net-1     net_plugin.cpp:3090           connection_monitor   ] p2p client connections: 0/4, peer connections: 9/10
info  2020-04-30T15:57:14.070 net-0     net_plugin.cpp:2141           operator()           ] host: mainnet.eoslaomao.com port: 443
info  2020-04-30T15:57:14.095 net-1     net_plugin.cpp:2350           operator()           ] Peer closed connection
error 2020-04-30T15:57:14.095 net-1     net_plugin.cpp:2369           operator()           ] Closing connection to: fullnode.eoslaomao.com:443
info  2020-04-30T15:57:14.095 net-1     net_plugin.cpp:943            _close               ] closing 'fullnode.eoslaomao.com:443', fullnode.eoslaomao.com:443
info  2020-04-30T15:57:14.128 net-0     net_plugin.cpp:1070           operator()           ] Sending handshake generation 1 to p2p.eosflare.io:9876, lib 1, head 1, id bcf2f448225d0996
info  2020-04-30T15:57:14.195 net-1     net_plugin.cpp:3090           connection_monitor   ] p2p client connections: 0/4, peer connections: 9/10
info  2020-04-30T15:57:14.195 net-0     net_plugin.cpp:2141           operator()           ] host: fullnode.eoslaomao.com port: 443
info  2020-04-30T15:57:14.195 net-1     net_plugin.cpp:2141           operator()           ] host: mainnet.eoslaomao.com port: 443
info  2020-04-30T15:57:14.209 net-0     net_plugin.cpp:1070           operator()           ] Sending handshake generation 1 to peer1.eosphere.io:9876, lib 1, head 1, id bcf2f448225d0996
warn  2020-04-30T15:57:14.309 net-1     net_plugin.cpp:2673           handle_message       ] ["p2p.eosflare.io:9876" <IP_ADDRESS>:9876]received go_away_message, reason = wrong chain
info  2020-04-30T15:57:14.309 net-1     net_plugin.cpp:943            _close               ] closing 'p2p.eosflare.io:9876', p2p.eosflare.io:9876
warn  2020-04-30T15:57:14.471 net-0     net_plugin.cpp:2673           handle_message       ] ["peer1.eosphere.io:9876" <IP_ADDRESS>:9876]received go_away_message, reason = wrong chain
info  2020-04-30T15:57:14.471 net-0     net_plugin.cpp:943            _close               ] closing 'peer1.eosphere.io:9876', peer1.eosphere.io:9876
info  2020-04-30T15:57:15.883 net-1     net_plugin.cpp:1070           operator()           ] Sending handshake generation 1 to eos.okpool.top:9876, lib 1, head 1, id bcf2f448225d0996
info  2020-04-30T15:57:16.870 net-0     net_plugin.cpp:1070           operator()           ] Sending handshake generation 1 to p2p.eossweden.org:9876, lib 1, head 1, id bcf2f448225d0996
warn  2020-04-30T15:57:17.138 net-1     net_plugin.cpp:2673           handle_message       ] ["p2p.eossweden.org:9876" <IP_ADDRESS>:9876]received go_away_message, reason = wrong chain
info  2020-04-30T15:57:17.138 net-1     net_plugin.cpp:943            _close               ] closing 'p2p.eossweden.org:9876', p2p.eossweden.org:9876
info  2020-04-30T15:57:18.058 net-0     net_plugin.cpp:1070           operator()           ] Sending handshake generation 1 to api3.tokenika.io:9876, lib 1, head 1, id bcf2f448225d0996
warn  2020-04-30T15:57:18.292 net-1     net_plugin.cpp:2673           handle_message       ] ["api3.tokenika.io:9876" <IP_ADDRESS>:9876]received go_away_message, reason = wrong chain
info  2020-04-30T15:57:18.292 net-1     net_plugin.cpp:943            _close               ] closing 'api3.tokenika.io:9876', api3.tokenika.io:9876
info  2020-04-30T15:57:19.127 net-1     net_plugin.cpp:2350           operator()           ] Peer closed connection
error 2020-04-30T15:57:19.128 net-1     net_plugin.cpp:2369           operator()           ] Closing connection to: mainnet.eosamsterdam.net:9876
info  2020-04-30T15:57:19.128 net-1     net_plugin.cpp:943            _close               ] closing 'mainnet.eosamsterdam.net:9876', mainnet.eosamsterdam.net:9876
info  2020-04-30T15:57:19.228 net-1     net_plugin.cpp:2141           operator()           ] host: mainnet.eosamsterdam.net port: 9876
info  2020-04-30T15:57:19.228 net-0     net_plugin.cpp:3090           connection_monitor   ] p2p client connections: 0/4, peer connections: 5/10
info  2020-04-30T15:57:19.228 net-0     net_plugin.cpp:2141           operator()           ] host: mainnet.eoslaomao.com port: 443
info  2020-04-30T15:57:19.228 net-1     net_plugin.cpp:2141           operator()           ] host: fullnode.eoslaomao.com port: 443
error 2020-04-30T15:57:19.275 net-1     net_plugin.cpp:2348           operator()           ] Error reading message: Connection reset by peer
error 2020-04-30T15:57:19.275 net-1     net_plugin.cpp:2369           operator()           ] Closing connection to: eos.okpool.top:9876
info  2020-04-30T15:57:19.275 net-1     net_plugin.cpp:943            _close               ] closing 'eos.okpool.top:9876', eos.okpool.top:9876
info  2020-04-30T15:57:19.375 net-0     net_plugin.cpp:3090           connection_monitor   ] p2p client connections: 0/4, peer connections: 5/10
info  2020-04-30T15:57:19.375 net-0     net_plugin.cpp:2141           operator()           ] host: fullnode.eoslaomao.com port: 443
info  2020-04-30T15:57:19.375 net-0     net_plugin.cpp:2141           operator()           ] host: mainnet.eoslaomao.com port: 443
info  2020-04-30T15:57:19.375 net-0     net_plugin.cpp:2141           operator()           ] host: eos.okpool.top port: 9876
info  2020-04-30T15:57:19.375 net-1     net_plugin.cpp:2141           operator()           ] host: mainnet.eosamsterdam.net port: 9876
error 2020-04-30T15:57:20.787 net-0     net_plugin.cpp:2185           operator()           ] connection failed to mainnet.eoslaomao.com:443: Operation canceled
info  2020-04-30T15:57:20.787 net-0     net_plugin.cpp:943            _close               ] closing 'mainnet.eoslaomao.com:443', mainnet.eoslaomao.com:443
error 2020-04-30T15:57:20.787 net-0     net_plugin.cpp:2185           operator()           ] connection failed to mainnet.eoslaomao.com:443: Operation canceled
info  2020-04-30T15:57:20.787 net-0     net_plugin.cpp:943            _close               ] closing 'mainnet.eoslaomao.com:443', mainnet.eoslaomao.com:443

root@bc607b692a77:/data# cat start.sh
#!/bin/bash
################################################################################

Scrip Created by http://CryptoLions.io
For EOS mainnet

https://github.com/CryptoLions/EOS-MainNet

###############################################################################
DATADIR="/data/data"
#NODEOSBINDIR="/data/eos/build/programs"
/data/stop.sh
echo -e "Starting Nodeos \n";
ulimit -c unlimited
ulimit -n 65535
ulimit -s 64000
/usr/bin/nodeos --data-dir $DATADIR --config-dir $DATADIR "$@" > $DATADIR/stdout.txt 2> $DATADIR/stderr.txt &  echo $! > $DATADIR/nodeos.pid

root@bc607b692a77:/data# cat data/config.ini
#producer-name = !!!!YOUR_BP_NAME!!!!!!!!
#signature-provider = YOUR_BLOCK_SIGN_PUB_KEY=KEY:YOUR_BLOCK_SIGN_PRIV_KEY

agent-name = AgentName

#blocks-dir = "blocks"
chain-state-db-size-mb = 10240
reversible-blocks-db-size-mb = 1024
contracts-console = false

http-server-address = <IP_ADDRESS>:8888
p2p-listen-endpoint = <IP_ADDRESS>:9876
p2p-server-address = <IP_ADDRESS>:9876
#bnet-endpoint = !!YOUR_ENDPOINT_IP_ADDRESS!!:9875
#bnet_threads = 4

http-validate-host = false
verbose-http-errors = true
abi-serializer-max-time-ms = 2000
chain-threads = 8
http-threads = 6
access-control-allow-origin = *
# access-control-allow-headers =
# access-control-max-age =
#access-control-allow-credentials = false

p2p-max-nodes-per-host = 4

# actor-whitelist =
# actor-blacklist =
# contract-whitelist =
# contract-blacklist =
# filter-on =

# SSL
# Filename with https private key in PEM format. Required for https (eosio::http_plugin)
# https-server-address =
# Filename with the certificate chain to present on https connections. PEM format. Required for https. (eosio::http_plugin)
# https-certificate-chain-file =
# Filename with https private key in PEM format. Required for https (eosio::http_plugin)
# https-private-key-file =

allowed-connection = any

#log-level-net-plugin = info
max-clients = 4
connection-cleanup-period = 30
#network-version-match = 1
sync-fetch-span = 2000
enable-stale-production = false

#max-implicit-request = 1500
pause-on-startup = false
max-transaction-time = 30
max-irreversible-block-age = -1
txn-reference-block-lag = 0
#unlock-timeout = 90000
wasm-runtime=wabt

plugin = eosio::chain_api_plugin
#plugin = eosio::history_plugin
#plugin = eosio::history_api_plugin
plugin = eosio::chain_plugin
#plugin = eosio::bnet_plugin

#plugin = net_plugin
#plugin = net_api_plugin

#bnet-connect =
#bnet-connect =
#bnet-connect =

#p2p-peer-address =
#p2p-peer-address =
#p2p-peer-address =

#p2p-peer-address = <IP_ADDRESS>:9876
#p2p-peer-address = <IP_ADDRESS>:9876

#Other Pub BP nodes
#p2p-peer-address =
#p2p-peer-address =

#2020
alohaeosprod: GB, London
p2p-peer-address = peer.main.alohaeos.com:9876
atticlabeosb: UA, Kyiv
p2p-peer-address = eosbp-0.atticlab.net:9876
atticlabeosb: UA, Kyiv
p2p-peer-address = eosbp-1.atticlab.net:9876
eosamsterdam: FI, bnode
p2p-peer-address = mainnet.eosamsterdam.net:9876
eoscannonchn: HK, Hong Kong
p2p-peer-address = node1.eoscannon.io:59876
eoscleanerbp: US, SV Node A-seed
p2p-peer-address = seed.eoscleaner.com:9876
eosdotwikibp: SG, Singapore
p2p-peer-address = p2p.eos.wiki:39876
eosflareiobp: US, GlobalDAC
p2p-peer-address = p2p.eosflare.io:9876
eoslaomaocom: US, NewYork
p2p-peer-address = fullnode.eoslaomao.com:443
eoslaomaocom: US, NewYork
p2p-peer-address = mainnet.eoslaomao.com:443
eosphereiobp: AU, Sydney
p2p-peer-address = peer1.eosphere.io:9876
eosswedenorg: SE, Sweden
p2p-peer-address = p2p.eossweden.org:9876
okcapitalbp1: JP, Tokyo
p2p-peer-address = eos.okpool.top:9876
tokenika4eos: PL, Poland
p2p-peer-address = api3.tokenika.io:9876
actor-blacklist = blacklistmee
#https://eoscorearbitration.io/wp-content/uploads/2018/07/ECAF_Arbitrator_Order_2018-06-19-AO-001.pdf
actor-blacklist = ge2dmmrqgene
actor-blacklist = gu2timbsguge
actor-blacklist = ge4tsmzvgege
actor-blacklist = gezdonzygage
actor-blacklist = ha4tkobrgqge
actor-blacklist = ha4tamjtguge
actor-blacklist = gq4dkmzzhege
#https://eoscorearbitration.io/wp-content/uploads/2018/07/ECAF_Arbitrator_Order_2018-06-22-AO-002.pdf
actor-blacklist = gu2teobyg4ge
actor-blacklist = gq4demryhage
actor-blacklist = q4dfv32fxfkx
actor-blacklist = ktl2qk5h4bor
actor-blacklist = haydqnbtgene
actor-blacklist = g44dsojygyge
actor-blacklist = guzdonzugmge
actor-blacklist = ha4doojzgyge
actor-blacklist = gu4damztgyge
actor-blacklist = haytanjtgige
actor-blacklist = exchangegdax
actor-blacklist = cmod44jlp14k
actor-blacklist = 2fxfvlvkil4e
actor-blacklist = yxbdknr3hcxt
actor-blacklist = yqjltendhyjp
actor-blacklist = pm241porzybu
actor-blacklist = xkc2gnxfiswe
actor-blacklist = ic433gs42nky
actor-blacklist = fueaji11lhzg
actor-blacklist = w1ewnn4xufob
actor-blacklist = ugunxsrux2a3
actor-blacklist = gz3q24tq3r21
actor-blacklist = u5rlltjtjoeo
actor-blacklist = k5thoceysinj
actor-blacklist = ebhck31fnxbi
actor-blacklist = pvxbvdkces1x
actor-blacklist = oucjrjjvkrom
#https://eoscorearbitration.io/wp-content/uploads/2018/07/ECAF-Temporary-Freeze-Order-2018-07-13-AO-003.pdf
actor-blacklist = neverlandwal
actor-blacklist = tseol5n52kmo
actor-blacklist = potus1111111
#https://eoscorearbitration.io/wp-content/uploads/2018/07/ECAF-Order-of-Emergency-Protection-2018-07-19-AO-004.pdf
actor-blacklist = craigspys211
#https://eoscorearbitration.io/wp-content/uploads/2018/08/ECAF-Order-of-Emergency-Protection-2018-08-07-AO-005.pdf
actor-blacklist = eosfomoplay1
#https://eoscorearbitration.io/wp-content/uploads/2018/08/ECAF-Order-of-Emergency-Protection-2018-08-28-AO-006.pdf
actor-blacklist = wangfuhuahua
#https://eoscorearbitration.io/wp-content/uploads/2018/09/ECAF-Order-of-Emergency-Protection-2018-09-07-AO-008.pdf
#https://eoscorearbitration.io/wp-content/uploads/2018/09/ECAF-Order-of-Emergency-Protection-2018-09-24-AO-010.pdf
#actor-blacklist = ha4timrzguge
actor-blacklist = guytqmbuhege
#https://eoscorearbitration.io/wp-content/uploads/2018/09/ECAF-Order-of-Emergency-Protection-2018-09-09-AO-009.pdf
actor-blacklist = huobldeposit
#https://eoscorearbitration.io/wp-content/uploads/2018/09/ECAF-Order-of-Emergency-Protection-2018-09-25-AO-011.pdf
actor-blacklist = gm3dcnqgenes
actor-blacklist = gm34qnqrepqt
actor-blacklist = gt3ftnqrrpqp
actor-blacklist = gtwvtqptrpqp
actor-blacklist = gm31qndrspqr
actor-blacklist = lxl2atucpyos
#https://eoscorearbitration.io/wp-content/uploads/2018/10/ECAF-Order-of-Emergency-Protection-2018-10-05-AO-012.pdf
actor-blacklist = g4ytenbxgqge
actor-blacklist = jinwen121212
actor-blacklist = ha4tomztgage
actor-blacklist = my1steosobag
actor-blacklist = iloveyouplay
actor-blacklist = eoschinaeos2
actor-blacklist = eosholderkev
actor-blacklist = dreams12true
actor-blacklist = imarichman55
#https://eoscorearbitration.io/wp-content/uploads/2018/10/ECAF-Order-of-Emergency-Protection-2018-10-05-AO-013.pdf
actor-blacklist = gizdcnjyg4ge
#https://eoscorearbitration.io/wp-content/uploads/2018/10/ECAF-Order-of-Emergency-Protection-2018-10-12-AO-014.pdf
actor-blacklist = gyzdmmjsgige
#https://eoscorearbitration.io/wp-content/uploads/2018/10/ECAF-Order-of-Emergency-Protection-2018-10-13-AO-015.pdf
actor-blacklist = guzdanrugene
actor-blacklist = earthsop1sys
#https://eoscorearbitration.io/wp-content/uploads/2018/10/ECAF-Order-of-Emergency-Protection-2018-10-31-AO-017.pdf
actor-blacklist = refundwallet
actor-blacklist = jhonnywalker
actor-blacklist = alibabaioeos
actor-blacklist = whitegroupes
actor-blacklist = 24cryptoshop
actor-blacklist = minedtradeos
#Manual at 2019.02.22 (MainNet gropup)
actor-blacklist = newdexmobapp
actor-blacklist = ftsqfgjoscma
actor-blacklist = hpbcc4k42nxy
actor-blacklist = 3qyty1khhkhv
actor-blacklist = xzr2fbvxwtgt
actor-blacklist = myqdqdj4qbge
actor-blacklist = shprzailrazt
actor-blacklist = qkwrmqowelyu
actor-blacklist = lhjuy3gdkpq4
actor-blacklist = lmfsopxpr324
actor-blacklist = lcxunh51a1gt
actor-blacklist = geydddsfkk5e
actor-blacklist = pnsdiia1pcuy
actor-blacklist = kwmvzswquqpb
actor-blacklist = guagddoefdqu
http-max-response-time-ms = 500

received go_away_message, reason = wrong chain
You need to provide a EOS mainnet genesis.json file?

root@bc607b692a77:/data# cat data/genesis.json
{
"initial_timestamp": "2018-06-08T08:08:08.888",
"initial_key": "EOS7EarnUhcyYqmdnPon8rm7mBCTnBoot6o7fE2WzjvEX2TdggbL3",
"initial_configuration": {
"max_block_net_usage": 1048576,
"target_block_net_usage_pct": 1000,
"max_transaction_net_usage": 524288,
"base_per_transaction_net_usage": 12,
"net_usage_leeway": 500,
"context_free_discount_net_usage_num": 20,
"context_free_discount_net_usage_den": 100,
"max_block_cpu_usage": 200000,
"target_block_cpu_usage_pct": 1000,
"max_transaction_cpu_usage": 150000,
"min_transaction_cpu_usage": 100,
"max_transaction_lifetime": 3600,
"deferred_trx_expiration_window": 600,
"max_transaction_delay": 3888000,
"max_inline_action_size": 4096,
"max_inline_action_depth": 4,
"max_authority_depth": 6
}
}

First run should be with --delete-all-blocks and --genesis-json
./start.sh --delete-all-blocks --genesis-json genesis.json

you're great,the problem has solved,thank you very much.


feature #90 - Add global logger service that logs in JobExecution

See #90

Thank you for this contribution


Add extra GPIOs and rename button access functions

The USB pins are broken out on the new PicoVision, this exposes them to I2C.
PR includes the max sprites commit as both contain modified pico-stick headers - we need to sort that out.

Ah yes, something something pull headers from GitHub artefacts and just reference the specific commit or otherwise.
I need to nip in and tweak the GitHub action, to spit out a widescreen build.


[jvm-packages] xgboost4j-spark Prediction Optimization

Motivation
Recently, I've been testing whether xgboost4j-spark could be a viable solution in production. One problem surfaced when multiple models were applied to the same dataset in sequence.
In an industrial setting, it's very likely that a practitioner builds multiple models using the same dataset, with same features but different labels for different tasks. For example, one might want to predict the demographic status of her users (gender, age, marital status, etc.) with the same set of base features.
Ideal Situation
Once multiple models have been trained on the labeled dataset, one wants to make predictions on a (potentially) much bigger unlabeled dataset. In pseudo code, it looks like
for model in trained_models; do
  data = model.transform(data).withColumnRenamed('prediction', 'prediction_from_model_i')
data.writeoutput

Ideally, this only loops through the dataset ONCE while applying all models.
Current Observations
In a toy setup
I've tried to apply 4 models, using xgboost4j-spark and spark logistic regression (LR), to a small dataset and monitored the IO. What's far from ideal is when applying multiple xgboost4j-spark models, the number of input records grows exponentially with the number of models applied:

model
#models
#input
prediction_time

xgboost4j-spark
0
11952 (size of the data)

xgboost4j-spark
1
23904
6

xgboost4j-spark
2
47808
9

xgboost4j-spark
3
95616
22

xgboost4j-spark
4
192002
23

spark-LR
0
10912 (size of the data)

spark-LR
1
10912
12

spark-LR
2
10912
15

spark-LR
3
10912
15

spark-LR
4
10912
16

In other words, if there are N models, then spark will read the dataset 2^N times. On the contrary, native spark LR simply reads the dataset once no matter how many models applied.
Even when just applying one model, the current implementation requires 2X of the dataset.
In a more realistic setup
This is where I first noticed the problem:

Predicting using one model reads in ~1TB data (again 2X of the dataset size), while applying 8 models together read in 127.4 TB (~2^8 X of the dataset size).
Prediction time went up from 6-7mins using one model to 7-9 hours using all eight, as compared to 7 X 8 ~ 1 hour if we do predictions separately in sequence.

Suspected Reasons
In Implementation, xgboost4j-spark uses the RDD interface with method zipPartition, while spark models uses spark sql udfs to do prediction.
This could make a huge difference in the execution plans.

xgboost4j-spark

spark

Workaround

One workaround for now is to cache the whole dataset that one wants to get predictions, which may not be feasible for some industrial settings where billions of records need to be scored.
A second workaround is just make predictions using single models separately, but this is also not very optimal depending on downstream stages.

Suggested Solutions

Move to the Dataset framework in Spark, similar to how native Spark models make predictions (spark.sql.functions.udf), OR
In RDD framework, append predictions to the spark.sql.Rows to avoid zipping

@mingyang thanks for reporting the issue and the analysis
the reason we didn't use any per-row approach (e.g. udf, appending to Row) is that per-instance prediction with XGBoost is very slow due to the overhead in creating DMatrix, etc.
I don't have a workaround better than the second one you already mentioned for now
I am thinking about provide some built-in tools which overlaps with Spark ML in functionality (e.g. cross-validation, ) but provide better performance with some special cares to the characteristics of XGBoost. What you mentioned here can be a very good use case for the tools

the reason we didn't use any per-row approach (e.g. udf, appending to Row) is that per-instance prediction with XGBoost is very slow due to the overhead in creating DMatrix, etc.

OK, this makes sense to me now. @CodingCat
How about this workaround, then? In pseudo-scala code:
val outputRDD = dataset.rdd.mapPartitions{ rowIterator => {
  // keep a copy of the input rows in memory. potentially a drawback
  val inputRows = rowIterator.toList
  // create the DMatrix for the whole input partition to avoid overhead
  val features = rowIterator.map(row=>row.getAs[Vector]($(featuresCol))).toList
  val dm = new DMatrix(features, ...)
  // get the predictions
  val Array(rawPredictionItr, probabilityItr, predLeafItr, predContribItr) =
            producePredictionItrs(bBooster, dm)
  // zip within the mapPartition instead of zipping two RDDs together
  Iterator(zip(inputRows, rawPredictionItr, probabilityItr, predLeafItr, predContribuItr))
}

Please forgive my syntax errors since I don't normally write scala code. But I hope my idea is clear.
If the memory footprint of keeping the partition in the memory is too high, which I don't think is a real issue since the spark default partition size when reading from hdfs is 128MB only, then we can do multiple mini-batches (e.g. every 100 or 1000 rows) within each partition. This way, we don't need to have another copy of the whole partition in memory, but only one mini-batch.

we do experience some issues with loading everything to memory (you can check https://github.com/dmlc/xgboost/pull/4033),
and actually in your code, the iterator rowIterator is not traversable after you execute val inputRows = rowIterator.toList  as toList has move iterator to the end..... as a result, doing miniBatch in an iterator becomes very complex, I am not sure I would choose to pay such cost here or I would have other ways to do it

Pardon my scala snippet. It was only to illustrate the main idea.
If we weren't using zipPartition before #4033, then it would avoid the problem that I describe above. On the down side, if I understand correctly, this would require more memory per executor.
So, is it possible to leave this tradeoff to the users by providing either 1) two prediction functions (e.g. model.transform and model.transform_inplace) or, 2) a parameter called something similar to prediction_inplace?

we intentionally avoid using too much memory in xgb itself to improve the scalability, and since you have to use more memory with in something like rowIterator.toList, it is nearly the same with caching/persisting/checkpointing the input dataframe before feeding to xgboost,
I think persisting before training will not bring additional overhead here,


[cmake error] Fresh Ubuntu 20.04 server

-- cxxopts version 2.2.0
-- Configuring done
CMake Error in CMakeLists.txt:
  Imported target "pybind11::module" includes non-existent path

    "/usr/include/python3.8"

  in its INTERFACE_INCLUDE_DIRECTORIES.  Possible reasons include:

  * The path was deleted, renamed, or moved to another location.

  * An install or uninstall procedure did not complete successfully.

  * The installation package was faulty and references files it does not
  provide.

-- Generating done
CMake Generate step failed.  Build files cannot be regenerated correctly.

Chia is installed and running.
xxxx@xxxxx:~/chiapos$ whereis python3.8
python3: /usr/bin/python3.8 /usr/bin/python3 /usr/lib/python3.9 /usr/lib/python3.8 /usr/lib/python3 /etc/python3.8 /etc/python3 /usr/local/lib/python3.8 /usr/share/python3 /usr/share/man/man1/python3.1.gz

I think it compiled finally, still with errors but the file exists and runs. Interestingly, adding in lm-sensors and a few other tools fixed the error above. The new error is:
home/chia/chiapos/build/_deps/pybind11-src-src/include/pybind11/detail/common.h:124:10: fatal error: Python.h: No such file or directory
  124 | #include <Python.h>
      |          ^~~~~~~~~~
compilation terminated.
make[2]: *** [CMakeFiles/chiapos.dir/build.make:63: CMakeFiles/chiapos.dir/python-bindings/chiapos.cpp.o] Error 1
make[1]: *** [CMakeFiles/Makefile2:268: CMakeFiles/chiapos.dir/all] Error 2
make[1]: *** Waiting for unfinished jobs....
[ 44%] Building C object CMakeFiles/RunTests.dir/src/b3/blake3.c.o
[ 44%] Built target link_test
[ 46%] Building C object CMakeFiles/RunTests.dir/src/b3/blake3_portable.c.o
[ 48%] Building C object CMakeFiles/RunTests.dir/src/b3/blake3_dispatch.c.o
[ 51%] Building ASM object CMakeFiles/RunTests.dir/src/b3/blake3_avx2_x86-64_unix.S.o
[ 53%] Building ASM object CMakeFiles/RunTests.dir/src/b3/blake3_avx512_x86-64_unix.S.o
[ 55%] Building C object CMakeFiles/ProofOfSpace.dir/src/chacha8.c.o
[ 58%] Building ASM object CMakeFiles/RunTests.dir/src/b3/blake3_sse41_x86-64_unix.S.o
[ 60%] Building C object CMakeFiles/ProofOfSpace.dir/src/b3/blake3.c.o
[ 62%] Building C object CMakeFiles/ProofOfSpace.dir/src/b3/blake3_portable.c.o
[ 65%] Building C object CMakeFiles/ProofOfSpace.dir/src/b3/blake3_dispatch.c.o
[ 67%] Building ASM object CMakeFiles/ProofOfSpace.dir/src/b3/blake3_avx2_x86-64_unix.S.o
[ 69%] Building ASM object CMakeFiles/ProofOfSpace.dir/src/b3/blake3_avx512_x86-64_unix.S.o
[ 72%] Building ASM object CMakeFiles/ProofOfSpace.dir/src/b3/blake3_sse41_x86-64_unix.S.o
[ 74%] Linking CXX executable example
[ 74%] Built target example
[ 76%] Linking CXX executable options_test
[ 76%] Built target options_test
[ 79%] Linking CXX executable ProofOfSpace
[ 79%] Built target ProofOfSpace
[ 81%] Linking CXX executable RunTests
[ 81%] Built target RunTests
make: *** [Makefile:141: all] Error 2

That usually means you are missing your distro's version of python3-devel.

python3-devel

sudo apt-get install python3-dev worked. :smile:

should probably add this to the build/installation instructions in the README.md


Installation

Hi I am new to this,
I would be highly grateful if you can please share steps to install it.
Thanks

In the readme there is already a section that explains how to compile the tool (https://github.com/mauvilsa/imgtxtenh#user-content-compilation). It is the usual cmake compilation procedure. With that you get the imgtxtenh binary. When running the cmake command you will see what prerequisites are required to compile. Installing the tool is optional. You can do "make install" as is standard with makefiles or you can copy it to any location you prefer.

Hi all,
I have a project need to use your imgtxtenh. I installed successfully, but I don't know to enter something. Example: imgtxtenh -N , and it display: term-256colorxterm-256colorxterm-256color. In this case, what will I enter?
Thank you very much!

@trangtran0602 I guess you must have some problem in the configuration of your terminal which is not related to imgtxtenh.


Add Change language option

Add Change language option inside the app to have it different from the system language.

This will be interesting when there is a significant amount of translations, for now this is not useful


Update function descriptions

Some function descriptions in unirep are not updated
e.g.
/**
* Description...
* @param a
* ...
*/
function foo(a) {
 ...
}

Refer to: https://tsdoc.org/

/**
 * Calculate the square of a given number.
 * This function takes a single parameter and returns the square of that number.
 *
 * @param {number} a - The number to be squared.
 * @returns {number} The square of the input number.
 */
function foo(a) {
  return a * a;
}

like this?

Yes~
We wrote some descriptions in each package but they are not updated.


Patch 1 -row 20 FIX- for *.lang

row 20 FIX - "light_blue" to "lightBlue"
This mistake is all * .lang and in the original Archimedes' Ships are also found.
Tested at [1.7.10-<IP_ADDRESS>8]ArchimedesShipsPlus-universal-1.7.10.B-Plus.jar

Accepted, thanks for contributing.


Minor enhancements to original code

Additions:

Flag tested profiles by moving them into a 'tested' folder, these will not be selected again during next run
Fallback to check for alternative ABI folder, with similar ABI in path name, e.g., if the detected ABI is "arm64-v8a", after all JSONs have been tested in the main folder arm64-v8a, it will next use JSONs from the following folders, before using random folders:

arm64-v8a,armeabi-v7a,armeabi
x86_64,arm64-v8a,x86,armeabi-v7a,armeabi
x86_64,x86,arm64-v8a,armeabi-v7a,armeabi
x86_64,x86,armeabi-v7a,armeabi,arm64-v8a

Hi @ptewee, did you mean to open this request? It looks like you're making breaking changes and overwriting most of the readme which I assume is meant only for your fork?

Hi @ptewee, did you mean to open this request? It looks like you're making breaking changes and overwriting most of the readme which I assume is meant only for your fork?

Many apologies, I should have been committing to my own fork instead!

@ptewee No worries!


Support multiple previews per message

Load up to 5 previews per message (to avoid abuse)
Do not load multiple times the same URL
Prepare preview containers per message instead of appending (to maintain correct order)
Store an array of previews instead of a single preview in Msg objects
Consolidate preview rendering for new messages and upon refresh/load history (when rendering entire channels)
Update parse tests to reflect previous point
Add test for multiple URLs
Switch preview tests from assert API to expect API

It's probably not the nicest code, but it works pretty nicely, and I'm sure reviews will highlight the required improvements.
Note that this does not improve the UI of displaying toggles/previews, this will be better left off to another PR and/or #1301.

Is this going to append expand button per new line after the text? You added divs with urls, but I don't see any code changes to move buttons there.

Add a test with multiple URLs, both for parse and link previews.

Is this going to append expand button per new line after the text? You added divs with urls, but I don't see any code changes to move buttons there.

Correct. Not ideal, but not a definitive solution, and I'm leaving UI improvements to your #1301 that we can build upon after this PR lands. I'm also not planning to release this PR without your work in #1301 :)

I'm leaving UI improvements to your #1301 that we can build upon after this PR lands

That PR is unnecessary if buttons are going to appear after links.

Add a test with multiple URLs, both for parse and link previews.

What do you mean? I already did add/update tests, no?

I already did add/update tests, no?

There's no test that has multiple <div data-url>

That PR is unnecessary if buttons are going to appear after links.

Are we set on this idea though? I think it's reasonable to settle on the actual capability of having multiple previews, and then play with different UIs, as yours is already an improvement.

There's no test that has multiple <div data-url>

Will add a test for parse, I believe that's the only missing one, no?

Test added.

Looks like fetch is blocking and it fetches urls one by one instead of asynchronously.

Re: concern of being blocking, I did some tests on the server, using:
───────────────────────────────────
modified: src/plugins/irc-events/link.js
───────────────────────────────────
@ link.js:31 @ module.exports = function(client, chan, msg) {
    ))
        .slice(0, 5) // Only preview the first 5 URLs in message to avoid abuse
        .forEach((link) => {
+           console.log(`Starting ${link}`);
            fetch(link, function(res) {
                if (res === null) {
                    return;
                }

+               console.log(`Finished ${link}`);
+
                parse(msg, link, res, client);
            });
        });

Posting this message (https://cloudhealthtech.com https://thelounge.github.io https://www.facebook.com https://www.google.com https://imgur.com/gallery/51haX) multiple times, I get different orders:
Starting https://cloudhealthtech.com
Starting https://thelounge.github.io
Starting https://www.facebook.com
Starting https://www.google.com
Starting https://imgur.com/gallery/51haX
Finished https://www.google.com
Finished https://www.facebook.com
Finished https://imgur.com/gallery/51haX
Finished https://thelounge.github.io
Finished https://cloudhealthtech.com

Starting https://cloudhealthtech.com
Starting https://thelounge.github.io
Starting https://www.facebook.com
Starting https://www.google.com
Starting https://imgur.com/gallery/51haX
Finished https://thelounge.github.io
Finished https://imgur.com/gallery/51haX
Finished https://www.google.com
Finished https://cloudhealthtech.com
Finished https://www.facebook.com

So unless I'm missing something, it looks fine.

@xPaw, I believe I have addressed all your comments, including splitting the rendering code into its own module :))

For history: This PR broke storage de-referencing because it didn't update the relevant code. Fixed in #2824


False positives on checkbox click (includes test case)

We are seeing intermittent failures when trying to click a checkbox.  Symptoms sound very similar to #120 - Capybara/Poltergeist acts like the click was successful, but it seemed to have clicked in the wrong spot.  In our case we have a form that has options shown/hidden (no animations, just hide/show) depending on other choices, and it seems like there's some sort of a race condition where, intermittently, Poltergeist just misses the checkbox.
Put together a gist that seems to reproduce the problem.  Generally fails within the first 10 iterations for me, often even earlier, but it seems to be a timing thing so you might have to play with the delays a bit.
https://gist.github.com/jpurcell001/5190514
This is using master of capybara/xpath as well as master of poltergeist.
The same gist passes without issue when using either selenium or webkit, so it feels like a poltergeist-specific issue.

This would seem to be a duplicate of #286 so I'm going to close this one - as a potential solution - rather than switching to trigger(:click) when you know your checkboxes will hide rows you can use
 #click the checkbox
 expect(page).not_to have_selector(:css, 'css selector of the element that should be hidden')
#click the next checkbox

This will have the effect of testing that your rows do hide as you expect, and also making the test wait until the page is stable to click the next checkbox

No problem @twalpole.   Hopefully the test case / gist is still helpful in resolving #286.


Add new exercise: grep

problem specification | description |  canonical data

@TomPradat go ahead. I've added some helpful links for you!

How is it going? Need any help?

Sry i wasn't available this week-end. I barely started, i'll keep you in touch :)


Error performing kronecker product between large sparse vectors

My issue is about ...
Kronecker product does not handle large sparse vectors.
Reproducing code example:

import numpy as np
from scipy.sparse import random, kron
from time import time

np.random.seed(10)

sparse_A = random(1, 2**16, format='csr', density=0.1)
sparse_B = random(1, 2**16, format='csr', density=0.1)

begin = time()
scipy_kron = kron(sparse_A,sparse_B)
print('sparse took %.2f seconds'%(time()-begin))

Error message:

Traceback (most recent call last):
  File "sparse_test.py", line 12, in <module>
    scipy_kron = kron(sparse_A,sparse_B)
  File "/Users/weitang/opt/anaconda3/envs/cc-env/lib/python3.7/site-packages/scipy/sparse/construct.py", line 355, in kron
    return coo_matrix((data,(row,col)), shape=output_shape).asformat(format)
  File "/Users/weitang/opt/anaconda3/envs/cc-env/lib/python3.7/site-packages/scipy/sparse/coo.py", line 198, in __init__
    self._check()
  File "/Users/weitang/opt/anaconda3/envs/cc-env/lib/python3.7/site-packages/scipy/sparse/coo.py", line 291, in _check
    raise ValueError('negative column index found')
ValueError: negative column index found

Scipy/Numpy/Python version information:

1.4.1 1.18.1 sys.version_info(major=3, minor=7, micro=6, releaselevel='final', serial=0)

I've investigated it. Negative values first appear after this multiplication. It seems, overflow happens inside the underlying C code of numpy.

With sparse arrays of this size the index arrays will be 'int32'.  Since 2**16 * 2**16 doesn't fit in a signed 32-bit integer, kron is failing.  The fix here will be to make sure the necessary arrays are 64 bit integers when necessary.  This would push the failure out to 2**32 or so, which i guess is probably far enough.

And how can I change the index arrays' data type to be 'int64'?


Create knapsack.cpp

Hi, pls make my pull request hacktoberfest, hactoberfest-accepted, thank you for your consideration!

Please add my pull request and add hacktoberfest

Please add my pull request and add hacktoberfest

I've made suggestion on the code part please rectify the, rest of the things are fine.

Please add my pull request and add hacktoberfest

I've made suggestion on the code part please rectify the, rest of the things are fine.

changes made successfully


Bintray Shutting Down May 2021 -- Host artifacts elsewhere?

Hi! Today JFrog (which owns Bintray/JCenter) announced that they're sunsetting Bintray/JCenter - the last day to access these repositories will be May 2021. https://jfrog.com/blog/into-the-sunset-bintray-jcenter-gocenter-and-chartcenter/
I know a lot of tooling goes into artifact upload to a repository, so I wanted to throw a signal flare up now so nobody is caught by surprise on May 1.

In case it makes your life any easier, there's a tool that Martin Bonnin developed that seems to make this pretty straightforward: https://github.com/martinbonnin/vespene

Better move to OSS Sonatype (free for open source) and use this Maven Gradle Plugin to publish this library. Vanniktech's Maven Gradle Plugin is the easiest plugin for me. Another advantage of OSS Sonatype is you can publish snapshots version, which is very helpful to test Material Dialog before putting it on stable versions.
Before you create an account on OSS Sonatype, you had better change your domain from af.codes to afollestad.com, or change Material Dialog's group ID to codes.af. They will verify your domain before registering your group ID.

Better move to OSS Sonatype (free for open source) and use this Maven Gradle Plugin to publish this library. Vanniktech's Maven Gradle Plugin is the easiest plugin for me. Another advantage of OSS Sonatype is you can publish snapshots version, which is very helpful to test Material Dialog before putting it on stable versions.
Before you create an account on OSS Sonatype, you had better change your domain from af.codes to afollestad.com, or change Material Dialog's group ID to codes.af. They will verify your domain before registering your group ID.

I own afollestad.com, aidanfollestad.com, and af.codes.
I will migrate when I have some free time.

Here we are: https://repo1.maven.org/maven2/com/afollestad/material-dialogs/

Any chance for getting earlier versions too? The latest version unfortunately has some blocking issues from being used for some devices.

Unfortunately it's a pretty manual process since Bintray did not require ASC files, thus forcing me to generate them or checkout old branches and republish them (haven't tried doing that yet).
What version do you need?

I'm currently using 3.1.1, as newer versions result in issue #1957.

Sorry if this isn't the right place to ask, since I am on a pretty old version, could I just download the AAR somehow?

Alright, every version should now be available on Maven Central: https://repo1.maven.org/maven2/com/afollestad/material-dialogs/

I'm assuming I'm not the only one stuck on <IP_ADDRESS> because AlertDialogWrapper was removed on <IP_ADDRESS>
Would it be possible to add that version as well?
Also, I do plan on modifying my code at some point to remove AlertDialogWrapper but a substantial amount of my code is still on Java, is it possible for you to add the last version that supports Java applications if that isn't supported anymore on newer versions?
Thank you.

The Java versions are all there.

Thanks, didn't realize that.


Failed test: mem_protect/usespace failed in nsim_sem and em_starterkit_em7d_v22

appmem_init_app_memory() will raise mpu violation exception
it's not an arc only issue, for MPU which does not support mpu overlap, it will some similar issue.
Because before through 'appmem_add_thread_xxx()' to add the partitions, there are no corresponding mpu entries in hardware. So the 'appmem_init_app_memory' should raise the mpu violation error as it will do bss zero to all parations.
Why it passed for some archs? Because one background/default mpu entry is set up to cover the regions which are not in mpu hardware through 'appmem_add_thread_xxx()' . But this background/default mpu entry will bring the risk that privileged thread blow up the kernel.

This issue can be closed as:

APP_APPLICATION_MEM is removed in latest code
the handling of app_shared_mem is implemented in latest code


[Event Extension Request] Codeunit 80 - Purch Post - OnBeforeArchiveUnpostedOrder

We would like an extension to the event OnBeforeArchiveUnpostedOrder. We would like to use the ishandled pattern from this event, but we need some global variables that are used in this function.
Old:
local procedure OnBeforeArchiveUnpostedOrder(var PurchaseHeader: Record "Purchase Header"; var IsHandled: Boolean)
New:
local procedure OnBeforeArchiveUnpostedOrder(var PurchaseHeader: Record "Purchase Header"; var IsHandled: Boolean; var OrderArchived: Boolean; PreviewMode: Boolean)

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.
Build ID: 47651.


feat: HTTP file rule (PAD-272)

Rule allows users to specify that a list of HTTP files  are publicly accessible. It does this by sending a HEAD request to each of the paths in the rule. If any path results in a non-200 OK response to a HEAD request, or if any request fails, the rule is considered failing.
Also updates Go, build submodule, and copyright headings.
Example rule:
apiVersion: validation.spectrocloud.labs/v1alpha1
kind: NetworkValidator
metadata:
  name: network-validator-http-file
spec:
  httpFileRules:
  - name: Spectro Cloud Azure VM VHD file
    paths:
    - https://spectroimageprod.blob.core.windows.net/system/Microsoft.Compute/Images/spectroimages/c-77-0-k-11611-0-osDisk.8ed00fe6-11e0-42e9-8da9-28ea8bbf2046.vhd

Example succeeded:
status:
  state: Succeeded
  validationConditions:
  - details:
    - Ensuring that files [https://spectroimageprod.blob.core.windows.net/system/Microsoft.Compute/Images/spectroimages/c-77-0-k-11611-0-osDisk.8ed00fe6-11e0-42e9-8da9-28ea8bbf2046.vhd]
      are publicly accessible.
    - File 'https://spectroimageprod.blob.core.windows.net/system/Microsoft.Compute/Images/spectroimages/c-77-0-k-11611-0-osDisk.8ed00fe6-11e0-42e9-8da9-28ea8bbf2046.vhd'
      is publicly accessible.
    lastValidationTime: "2024-07-12T17:14:48Z"
    message: All files are publicly accessible.
    status: "True"
    validationRule: Spectro Cloud Azure VM VHD file
    validationType: http-file

Example failed (file not accessible):
status:
  state: Failed
  validationConditions:
  - details:
    - Ensuring that files [https://spectroimageprod.blob.core.windows.net/system/Microsoft.Compute/Images/spectroimages/c-77-0-k-11611-0-osDisk.8ed00fe6-11e0-42e9-8da9-28ea8bbf2046.vhs]
      are publicly accessible.
    failures:
    - file 'https://spectroimageprod.blob.core.windows.net/system/Microsoft.Compute/Images/spectroimages/c-77-0-k-11611-0-osDisk.8ed00fe6-11e0-42e9-8da9-28ea8bbf2046.vhs'
      is not publicly accessible; '404' status code in response to HEAD request
    lastValidationTime: "2024-07-12T17:18:54Z"
    message: One or more files not publicly accessible. See failures for details.
    status: "False"
    validationRule: Spectro Cloud Azure VM VHD file
    validationType: http-file

Example failed (HTTP request error):
status:
  state: Failed
  validationConditions:
  - details:
    - Ensuring that files [https://nonexistentstorageaccount.blob.core.windows.net/system/Microsoft.Compute/Images/spectroimages/c-77-0-k-11611-0-osDisk.8ed00fe6-11e0-42e9-8da9-28ea8bbf2046.vhd]
      are publicly accessible.
    failures:
    - 'failed to check file ''https://nonexistentstorageaccount.blob.core.windows.net/system/Microsoft.Compute/Images/spectroimages/c-77-0-k-11611-0-osDisk.8ed00fe6-11e0-42e9-8da9-28ea8bbf2046.vhd'':
      failed to send HTTP request: Head "https://nonexistentstorageaccount.blob.core.windows.net/system/Microsoft.Compute/Images/spectroimages/c-77-0-k-11611-0-osDisk.8ed00fe6-11e0-42e9-8da9-28ea8bbf2046.vhd":
      dial tcp: lookup nonexistentstorageaccount.blob.core.windows.net on <IP_ADDRESS>:53:
      no such host'
    lastValidationTime: "2024-07-12T17:20:18Z"
    message: One or more files not publicly accessible. See failures for details.
    status: "False"
    validationRule: Spectro Cloud Azure VM VHD file
    validationType: http-file

WIP. Has unit tests but needs a manual test and examples added to PR.

Changed to use httptest. After looking into it, I mostly found examples online of using it to test HTTP handlers you've written. Here, I'm mocking an HTTP client to be able to test how reconciliation happens when the HTTP client doesn't find what it's looking for when it makes requests to a server I don't control. But I was able to find a way to use it. It involves a bit more helper code in the testing side of things but simplifies the actual network.go code. Let me know what you think.
Making the HTTP client more powerful (loading certs, making TLS configurable) is a WIP.

@TylerGillson Thanks for reviewing! A few things about this PR though:

So far I've made the TLS configurable (see my reply to your comment) but I didn't finish because I needed to wire it up all the way to the entry point so that plugin users can actually configure it. And I didn't understand yet the different ways they would configure it. Can you help me with that? Or is it that we don't need to configure it differently yet?

You also mentioned certificates and linked some Spectro code to look at. I see that that code did two things (loaded system certs manually and supported adding more certs). I don't think we need any of that right now because system certs should be loaded automatically when we create a default HTTP client and I don't think we need to support custom certs yet. Can you confirm?

If you could handle that as part of this PR, that would be awesome!

I think that sounds doable as part of this PR. I'll take a stab at it. ty


[Crash] Crash when Chunky is finishing pregeneration

Mod Version
LoadMyChunks-1.0.6-hf1+1.21+fabric
What were you doing before the crash happened?
Basically, Chunky (GH) was finishing a 2500x2500 pregeneration on singleplayer and was almost finished when this crash happened. Related to #21 ?
Provide Logs here:
Gist

Yup. This is likely a threading issue as mentioned in #21
The save method needs to be labelled as sync. Be on the look out for hf2.

I'll close this for now. If you haven't already update to hf2. If you experience any crashes at the end of chunk pregen, reopen this issue with the crash report.


More semantically correct alternative to markDeleted

Enhancement Description

A more 'semantically correct' alternative to markDeleted.
Of course what is more 'correct' is always up to interpretation. I hope I can convince you of what I mean and am suggesting in the rest of the issue below.
Current Behaviour

Currently, we model aggregates as if they have a lifecycle i.e. they have a start state, bunch of intermediate states, and an end state. Once the end state is reached the lifecycle is over.
This aligns with the style mentioned by @abuijze in the podcast here: https://www.youtube.com/watch?v=zhzR1WiHQqE (apologies I don't remember the exact minute he mentions it but its there somewhere!).
Let's take the example from @idugalic's state machine demo project. We have an aggregate with the following lifecycle:

Currently to transition to the [END] state we need to publish an event which triggers the following event handler:
    @EventSourcingHandler
    void on(AbstractOrderDeletedEvent event) {
        markDeleted();
    }

Everything works fine and as expected. However, I think that calling markDeleted() kind of throws me here. The documentation on the method states:
Marks this aggregate as deleted, instructing a repository to remove that aggregate at an appropriate time.
Note that different repository implementations may react differently to aggregates marked for deletion.
Typically, Event Sourced Repositories will ignore the marking and expect deletion to be provided as
part of Event information.

The problem here is that I believe we are overloading the term 'delete' to mean something which makes the code less understandable. The use of markDeleted conveys that we want to delete the aggregate which in actual fact is completely incorrect in this case - we simply want to transition it to the END state so it rejects future commands. This is confusing.
When our intent is to transition the aggregate to the [END] state we are having to use the markDeleted() method as kind of a workaround.
The confusion about markDeleted() has led me to ask a question on the discuss site to get further clarification in the past.  Other people will most likely end up in the same boat. It would be better to have an explicit method which does not cause confusion.
Wanted Behaviour

This to me is confusing and I would like to actually have a separate method whose semantics are not ambiguous and would make the code much more readable such as: transitionToEndState(..) /  markAsLifecycleEnded() / (or whatever name makes the most sense).
Possible Workarounds

As mentioned the current way of using markDeleted() works but creates confusion.
Other notes
This may relate to https://github.com/AxonFramework/AxonFramework/issues/1415

As an addendum, it would also be nice to have a declarative exception handler to deal with the case when after the aggregate lifecycle has ended (i.e. it has transitioned to its [END] state) AND a command is received for that aggregate. Currently we get the following (illustrative) exception message logged:
2020-12-20 15:50:47.002  WARN 15336 --- [ault-executor-2] o.a.c.gateway.DefaultCommandGateway      : Command 'pro.idugalic.axonstatemachine.command.api.command.MarkOrderAsCancelledCommand' resulted in org.axonframework.commandhandling.CommandExecutionException(Aggregate with identifier [0e9727f7-1d08-469d-9a7c-1d28a86a7e47] not found. It has been deleted.)

Placing this on the aggregate has no effect:
    @ExceptionHandler(resultType = AggregateDeletedException.class)
    public void handle(AggregateDeletedException exception) {
        log.info("In the exception handler to deal with a command being sent to an aggregate which has been deleted", exception);
        // deal with the fact that the aggregate lifecycle has ended but we have received a command.
       // ....
    }

org.axonframework.eventsourcing.EventSourcingRepository::doLoadWithLock has the following in it:
    protected EventSourcedAggregate<T> doLoadWithLock(String aggregateIdentifier, Long expectedVersion) {
        // ..... snipping method body to show only relevant part
        if (aggregate.isDeleted()) {
            throw new AggregateDeletedException(aggregateIdentifier);
        }
        // ..... snipping method body to show only relevant part
   }

Perhaps a separate special if statement could be added to the effect of (pseudo-code below):
       if (aggregate.lifecycleHasEnded()) {
            if(aggregate.hasLifecycleEndedExceptionHandler()) {
                     aggregate.invokeLifecycleHasEndedExceptionHandler()
            }
           // If no specialised exception handler exists for this situation throw the generic exception
            throw new AggregateLifecycleHasEndedException(aggregateIdentifier);
        }
      // .....

Just sharing my thoughts.... hopefully you find them useful.
Thanks

What about having an explicit end state? You never mark the aggregate as deleted but just update the state. Yes, you have to check the state in each CommandHandler, but don't you have to do this anyway in order to ensure that only valid state transitions are performed?

Hi, @vab2048. I am the creator of https://github.com/idugalic/axon-statemachine-demo.  My idea was to force us to think about our models in terms of behavior. The consequence is that we tend to design better systems when we use the Finite-State-Machine pattern.
I believe that @OLibutzki has a good point here: "markDeleted is not the best term for expressing that an aggregate has reached its lifecycle end". This is domain-specific, and (looking from this perspective, today) I would rather use custom validation (as @OLibutzki described) in my aggregates than marking them deleted.
As this is a domain-specific problem, I (personally) do not see a general solution by having Axon Fremwerk introducing markAsLifecycleEnded  method(s) TBH.
Hopefully, this makes sense to you as well. Please let us know what do you think?
Thank you very much for opening this discussion!

Thanks @OLibutzki and @idugalic for your comments.
@OLibutzki - you are of course absolutely correct - having an explicit [END] state would work.
I'll edit my original post to add this to the workarounds list.
You also mention:

Yes, you have to check the state in each CommandHandler, but don't you have to do this anyway in order to ensure that only valid state transitions are performed?

If an aggregate has reached [END] then no state transition is a valid one, right?
And so my idea was rather than having to write the boiler plate "to check the state in each CommandHandler" - the framework
would handle it for you (if the aggregate is marked as having its lifecycle ended it would know to reject the command).
@idugalic - I've learned a lot about how to use the framework from your projects - thanks for making them open source!

(looking from this perspective, today) I would rather use custom validation (as @OLibutzki described) in my aggregates than marking them deleted.

I think this is a good recommendation which I will also follow.

As this is a domain-specific problem, I (personally) do not see a general solution by having Axon Fremwerk introducing markAsLifecycleEnded method(s) TBH.

I think you may be right - I was mainly just hoping that when going down the custom validation route the framework could help remove the boiler plate (as I mentioned above). But as it currently stands this would probably be low priority on the delivery path for the framework... and custom validation in each command handler is obviously the most flexible route.
I guess for now a simple pattern would be to have something like the following within an aggregate:
private boolean lifecycleEnded;

@CommandHandler
void on(Cmd cmd) {
  Assert.isTrue(!lifecycleEnded, () -> "The aggregate's lifeycle has ended. It is no longer accepting commands.");
  // ....
}

Closing this issue in favour of the custom validation route is probably the best way forward... :)

Worthwhile discussion everybody, thanks for that. As pointed out by @vab2048, this issue will be closed for now.

Worthwhile discussion everybody, thanks for that.
As pointed out by @vab2048, this issue will be closed for now.
Feel free to keep providing insights here though.
Who knows, we might just reopen it when new insights turn up.


[HELP WANTED] Fix Typos and Grammar in Documentation

There could be typos in our documentation or even grammar mistakes. If you found any typos or grammar issues, please mention this issue when creating the pull request.

I would like to work on it

Assigned @kushal9897


remove non-standard query param options

The Champion Service had a non-consistent way of specifying query parameters.
This pull request changes that.

Coverage remained the same at 100.0% when pulling 09532efeb90dbdd651e9d0e42df5ee81d83e6c89 on remove-champion-list-request into 7791799d9007555f5de953fd277baf1847e02626 on master.


redis coroutine make exception

Describe the bug
A clear and concise description of what the bug is.
It is ok when the redis coro codes place in main.cc.
But when i place the redis coro codes in other .cc files, the g++ print these:
../controllers/EchoWebsock.cc:15:29: error: unable to find the promise type for this coroutine
auto transPtr = co_await redisClient->newTransactionCoro();
I'm make in wsl2 ubuntu20.04, use gcc10.3.
/bin/x86_64-linux-gnu-g++-10   -I../ -I../models -isystem /usr/include/jsoncpp -fcoroutines -g   -std=c++2a -MD -MT CMakeFiles/drogon_hello.dir/controllers/demo_v1_User.cc.o -MF CMakeFiles/drogon_hello.dir/controllers/demo_v1_User.cc.o.d -o CMakeFiles/drogon_hello.dir/controllers/demo_v1_User.cc.o -c ../controllers/EchoWebsock.cc
// 访问redis
auto redisClient = drogon::app().getRedisClient();
if (redisClient)
{
    try
    {
        auto transPtr = co_await redisClient->newTransactionCoro();
        co_await transPtr->execCommandCoro("set zzz 123");
        co_await transPtr->execCommandCoro("set mening 52");
        co_await transPtr->executeCoro();
    }
    catch (const std::exception& err)
    {
        LOG_ERROR << "redis coroution failed: " << err.what();
    }
}

To Reproduce
Steps to reproduce the behavior:

Go to '...'
Click on '....'
Scroll down to '....'
See error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

i'm sorry, my codes has bugs.


dlrs_OpportunityTrigger blocking insert/updates of Opportunities

Errors when creating or updating an opportunity.
Error Message #1: "Apex trigger dlrs_OpportunityTrigger caused an unexpected exception, contact your administrator: dlrs_OpportunityTrigger: execution of AfterInsert caused by: System.SObjectException: Invalid field Account for Opportunity: (dlrs)"
Error Meesage #2: "Apex trigger dlrs_OpportunityTrigger caused an unexpected exception, contact your administrator: dlrs_OpportunityTrigger: execution of AfterInsert caused by: System.SObjectException: Invalid field RecordType for Opportunity: (dlrs)"
Both of the "invalid" fields referenced are standard fields on the Opportunity object. Please make fixing this issue a priority as we cannot create a single opportunity record in our org right now.
Thanks!

Which part of the configuration would you like screenshots for?
We've deactivated every Lookup Rollup Summary in our org and the problem persists, so I'm not sure what to document. Also, everything was working for us yesterday, but it looks like an update to the package was pushed to our org last night around 12:00 am CST. I'm not sure if that update could have caused anything to change.

I wasn't aware any updates had been pushed for the package. What version are you on?
If you could screenshot the configuration of any related rollups on the Opportunity that might be a good start. I'm not sure what would have changed in your system.
Is it possible for you to run a debug log for one of the transactions that is failing? Maybe pull the stack trace portion that is reporting all of the classes involved in the crash? (Might not work well depending on where it is in the managed package)
Nothing else in the org that could have changed in that window?

I didn't think the dlrs package was setup for auto pushing always manual
upgrades.
On Wed, Dec 5, 2018, 6:53 PM Heber<EMAIL_ADDRESS>wrote:

I wasn't aware any updates had been pushed for the package. What version
are you on?
If you could screenshot the configuration of any related rollups on the
Opportunity that might be a good start. I'm not sure what would have
changed in your system.
Is it possible for you to run a debug log for one of the transactions that
is failing? Maybe pull the stack trace portion that is reporting all of the
classes involved in the crash? (Might not work well depending on where it
is in the managed package)
Nothing else in the org that could have changed in that window?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/afawcett/declarative-lookup-rollup-summaries/issues/768#issuecomment-444730043,
or mute the thread
https://github.com/notifications/unsubscribe-auth/APXKqtmRwIznZ2M74KTZaFQ49KJPfLufks5u2IaNgaJpZM4ZFEzG
.

Yes, I mispoke on the automatic upgrade - that was for a separate package installed for a similar function. There are currently two Lookup Rollup Summaries on the Opportunity. I've attached screenshots of both.
And unfortunately, it's tough to pinpoint the error because we've had a large team deploying, loading data, etc. to get through our pre-deployment UAT phase. I'll follow-up with the rest of my team to see if any of them are aware of what else might have changed.
I appreciate you looking at the config to confirm nothing is causing issues there.

We got to the bottom of this one. Your initial assessment of referencing Account and RecordType instead of AccountId and RecordTypeId was spot on.
The challenge in finding which Rollup was causing this errror was due to my accessing the Lookup Rollup Summary tab directly instead of going to the "Manage Lookup Rollup Summaries tab". When accessing that tab directly, it was only my two rollup summaries that showed an association to the Opportunity object, however there was another that was scheduled to run (but showed inactive in the UI) that was actually still calculating. As soon as we updated those field references, everything started working again.
Thank you both for your help!

Awesome! Yeah DLRS can be a bit confusing wherein you can schedule through two different interfaces and into two different sets of rollups jobs.
Glad you got it taken care of.

Hey I have same problem but, not able to figure out which DLRS is causing this.
As I am new to this tool, if any one can help me it would be great help!!


SQOOP-611. add the --hbase-timestamp-column option while importing the d...

...ata into HBase from tranditional database.

Closing conflicting PRs older than a year. Please reopen if it is still applicable.


Allow building from a temporary ports tree

Prerequisites

[x] Have you checked for an existing issue describing your idea?

What is your proposal?

In a CI environment, the ports tree that I would like to build could potentially live in /path/to/build/12345/ports. I would like to use this ports tree one-off for a specific build only, but don't save it (without poudriere ports -c first).
What is the existing behavior, if any?

To my knowledge (I could be wrong), there is no easy way of just specifying a path to build from, something like
sudo poudriere bulk -t -j /path/to/build/12345/ports ports-mgmt/pkg net/nc

or quickly update the path to a tree to be pwd.

I don't see any reason to implement this. It's not trivial and would require modifying anything that uses a ports tree in the code. It's trivial for you to wrap your build with a ports -c and ports -d to import the system tree.

https://github.com/freebsd/poudriere/wiki/use_system_ports_tree


Cannot perform this operation because the connection pool has been closed

Having concurrent connections to the same SQLite database I was experiencing the following errors:

"Cannot perform this operation because the connection pool has been closed."
"attempt to re-open an already-closed object"

Using commit https://github.com/SQLDroid/SQLDroid/commit/4666757512f8019ad1f11eed3c5d5c16c7bb7297 in the pull request the problems are gone.
When you review the pull request the error fixed should be obvious. If not just ask :-)

This change looks reasonable. I have done some local testing and have not found any regressions.

@donv, if you are OK with it, I can merge this pull request. Thanks,

👍


"kivy.properties" is not accessed

macOS Monterey Version 12.0.1
Python 3.10.1
Kivy Version: 2.2.1
Kivy installation method: pip
IDE : Visual Studio Code
Somehow my program does not recognise Kivy.properties as one of the modules. I have no idea why all the other seem to be working just fine. Could not find solutions for this anywhere.
"kivy.properties" is not accessed

I'd love to hear suggestions!

This is a syntax error in an import statement - nothing to do with Kivy.

@Ramboliner Try with a full statement: from kivy.properties import *
This module is never colorized by VSCode, but it works

@Ramboliner Try with a full statement: from kivy.properties import *
This module is never colorized by VSCode, but it works

Yes this was the problem, I was confused by this. Thank you!


Migrate to pathlib in catalog_collections

This migrates the catalog collection script to pathlib away from file and directory paths created from strings and using os.path.xxx.
Additional testing was done locally:

With the default image
With ee-minimal
With ee-supported

Before and after deleting the collection cache.
Pulling this one down and trying it out would be a great help.  Admittedly I am not too familiar with pathlib, although more now :)
Fixtures were updates as a result of pathlib removing the trailing slash: https://bugs.python.org/issue21039

I'll work on this some more probably this weekend, but here's what I'm seeing (mostly as a note to myself for later):
First, this is my directory structure for testing:
In [22]: !tree baz
baz
├── a.txt
├── b.txt
├── dir1
│   └── c.txt
└── dir2
    ├── d.txt
    └── dir3
        └── e.txt

3 directories, 5 files

I have your _path_walk pulled out into a function called path_walk with no modifications other than changing its name and recursive call to point to the right thing and removing self as an argument. There are a fair number of differences (yours never seems to show directories - the baz entry should have ['dir2', 'dir3'] as the second element of the tuple, for example).
In [16]: for a, b, c in list(path_walk(Path("baz"), top_down=True)):
    ...:     print((a, list(b), list(c)))
    ...:
(PosixPath('baz'), [], [PosixPath('baz/b.txt'), PosixPath('baz/a.txt')])
(PosixPath('baz/dir2'), [], [PosixPath('baz/dir2/d.txt')])
(PosixPath('baz/dir2/dir3'), [], [PosixPath('baz/dir2/dir3/e.txt')])
(PosixPath('baz/dir1'), [], [PosixPath('baz/dir1/c.txt')])

In [17]: for a, b, c in list(path_walk(Path("baz"), top_down=False)):
    ...:     print((a, list(b), list(c)))
    ...:
(PosixPath('baz'), [], [PosixPath('baz/b.txt'), PosixPath('baz/a.txt')])
(PosixPath('baz/dir2'), [], [PosixPath('baz/dir2/d.txt')])
(PosixPath('baz/dir2/dir3'), [], [PosixPath('baz/dir2/dir3/e.txt')])
(PosixPath('baz/dir2/dir3'), [], [])
(PosixPath('baz/dir2'), [], [])
(PosixPath('baz/dir1'), [], [PosixPath('baz/dir1/c.txt')])
(PosixPath('baz/dir1'), [], [])
(PosixPath('baz'), [], [])

In [18]: import os

In [19]: for a, b, c in list(os.walk("baz", topdown=True)):
    ...:     print((a, b, c))
    ...:
('baz', ['dir2', 'dir1'], ['b.txt', 'a.txt'])
('baz/dir2', ['dir3'], ['d.txt'])
('baz/dir2/dir3', [], ['e.txt'])
('baz/dir1', [], ['c.txt'])

In [20]: for a, b, c in list(os.walk("baz", topdown=False)):
    ...:     print((a, b, c))
    ...:
('baz/dir2/dir3', [], ['e.txt'])
('baz/dir2', ['dir3'], ['d.txt'])
('baz/dir1', [], ['c.txt'])
('baz', ['dir2', 'dir1'], ['b.txt', 'a.txt'])

@relrod Switched to a glob per plugin directory, cleaner and smaller.

This PR is being closed.


Better Intergration

Found a couple of things, when I was trying to add support to your mod, One of them being Parents get registered as soon as the Chicken is registered, only down side with this is it makes it hard to register a chickens parent out of order, or if say in configs someone wanted to change a chicken's parent to a different parent, they would have to stay in the loading order. Basically if chicken A  and Chicken B are about to be registered but chicken C was added before A and B, Chicken C couldn't select A or B cause they aren't in the registry yet. I am thinking that if you register the chickens but register their parents after all chickens have been added. perhaps, register chickens where they are at now, and register parents on POST loadup.
https://github.com/setycz/ChickensMod/blob/1.10.2/src/main/java/com/setycz/chickens/ChickensMod.java#L146-L152
Also Version numbers are incorrect for the @Mod annotation. Last time I checked I think you added  - "MCVersion - ModVersion". More chickens is dependent on Chickens mod, but I cant make sure its dependent on a specific version because of the dash" The Version number should be just the ModVersion only with no letters or special characters. basically "1.0.0" or "1.0".

Hi. Thank you for you suggestions, I really appreciate that. Let's continue with the first think in this thread and that's the chicken registration. I have created #41 for the mod version issue.

BTW, what do you think about MC 1.9.4, do you think that it make any sense to keep it updated? I would like to know your opinion.

To be honest, Most ppl just updated from 1.9.4 to 1.10.2. I don't see a reason to keep the 1.9.4 updated. And more than likely the 1.10.2 version will still work on 1.9.4 unless you happen to call a new method.  I will be busy today, but we can discuss more on the chicken registry later.

The chickens registry, it was designed in a way that it won't allow to have 'children' without both 'parents'. So as you said, parents need to be in the registry first. I haven't realised that it may be to strict and that it could cause hard times for addon developers. I think I can change that it to be flexible and e.g. do a validation in the post load event and possibly removing invalid combinations (chicken which any of its parents are not in the registry). What do you think?

I'm guessing you will store the parents String ID during configuration load than in post actually find the parents in the chicken registry.  or something along those lines. Either way that will make sure every chicken is loaded and it should find the parent. if it exist.
Side note I am realizing as I go back though your code.. I could have done some things differently.. mainly I did some things I didn't need too. So I am going to rewrite parts of my code before posting it up.
I will try to keep up to date so More chickens wont be broken for the new version.

@setycz  I may have over thought this, I'm thinking I can handle the parents on my side.  I started to look at the code again, and realized I can just handle mine on my side believe.  I think I can simply call a new method to go though and set all the parent's after the registering.  I realized the fisrt time I wrote this I sort of rushed its. Missed a few things I could have done better.  I will get back with ya.

Ok sure. Let me know what you'll find out and based on that I can increase the priority if this issues slows your development down.

https://github.com/GenDeathrow/MoreChickens I think were good on the issue with parents now.  I had to change some things over, but it works now.  Some things are redundant

Hey I noticed you deleted a method getAllItems() im getting a crash report with the newest update cause I had been calling that method. Not a big deal but could you @depreciate any method you wont be using and leave them in for an update or two.Just So I have time to fix it?

https://github.com/GenDeathrow/MoreChickens/issues/2

I do like how you separated the enabled/disabled chickens though.

@GenDeathrow I have created a hotfix for the missing getAllItems(), it's great that your mod is now on GitHub so I can check what methods do you use.

I appreciate.. I did just release a fix for the new stuff anyways. probably not available yet.  Hatchery also got an update to display your dna stats in the eggs. and drops inside the nesting pens with jei.
And I'm working around your mod for the most part, if you remove something that's ok in my book.  I have your mod inside my dev environment. So if you make changes hopefully I will see them and can change as needed.

Integration problem is handled in More Chickens mod, further improvements can be done later in a new issue.

Integration problem is handled in More Chickens mod, further improvements can be done later in a new issue.


Kshitij Zutshi - OPT Volunteer Work Update

Description of my work alongside Dev Shah and Meet Gandhi towards Refer Mate Club platform (The Nirvana Labs)
@aiskunks OPT Volunteer Work Update

Mergeable. Admin can merge.


ApiParam annotation documentation - list supported values for type and format

unclear what the supported values were for type and format options in ApiParam annotation.

Any idea to improve this documentation section?
What supported values should be on the documentation? @HaithamMaya


MAINT: Fix/parametrize Rotation tests.

The test were slightly incorrect in the sens that they were testing that at least one of the combination of angle/sequence/intrinsic-extrinsic angle where emitting a Gimbal Lock warning, instead of each of them.
The warning is now checked only and on all on the line that are supposed to emit such a warning.
And while I was at it I parametrized the tests, so each appear as a separate intem when running with pytest, and extended to all the parametrized test in case it ever have an issue somewhere.
In all of the angles = np.array(...) I have the impression that each one should emit a warning and that angle should likely also be a parameter, but it was starting to be a lot (maybe open an issue to parametrize angle?)

Another possible refactor is to reify seq_tuple and join it into a string/uppsercaseify. Right now the test looks like
... asymmetric_axes[False-seq_tuple0] PASSED

with a cleanup they could look like
... asymmetric_axes['xzy'] PASSED
... asymmetric_axes['ZYX'] PASSED

Failure seem unrelated, can someone restart the failing item ?

Gentle poke on this one.

Just some small nits around keeping the comments unambiguous and clear. I guess for people familiar with rotations it's clear that the case of the letters switches on extrinsic/intrinsic, but it doesn't hurt to keep that context in the test for easier digestibility.

Yeah, I'm not too familiar with rotation either. My understanding from the docs is that Upper/lower is intrinsic/Extrinsic (ie global, of related to the objects), and axes in the form  abc/aba are either symmetric or asymmetric. I've updated the comments.

Gentle check-in here, as this is only a refactor for further work.

Would appreciate if someone else could double-check here from either the spatial owners or other regular reviewers. Once the above nits are fixed, I'll merge this in a few days, if no other comments/reviews appear.

Do you want me to send an email to scipy-dev ?

Do you want me to send an email to scipy-dev ? (to ask for more reviews)

You're free to do so, but I don't think it's that much of a critical issue. At least, I'm happy to merge it as is.

Thanks!

Thanks !


fix: update rule description

The desc of the rule Write below monitored dir have a typo.
https://github.com/falcosecurity/charts/blob/master/falco/rules/falco_rules.yaml#L1027
What type of PR is this?

/kind bug

Any specific area of the project related to this PR?

/area falco-chart

What this PR does / why we need it:
fix typo.
Which issue(s) this PR fixes:
none
Special notes for your reviewer:
Checklist

[x] Chart Version bumped
[x] Variables are documented in the README.md
[x] CHANGELOG.md updated

Thanks for your pull request. Before we can look at it, you'll need to add a 'DCO signoff' to your commits.
:memo: Please follow instructions in the contributing guide to update your commits with the DCO
Full details of the Developer Certificate of Origin can be found at developercertificate.org.
The list of commits missing DCO signoff:

dbd4168 fix: update rule description

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

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please assign bencer after the PR has been reviewed.
You can assign the PR to them by writing /assign @bencer in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

falco/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @stevenshuang! It looks like this is your first PR to falcosecurity/charts 🎉

/assign @nestorsalceda

Hey @stevenshuang
Thank you! Would you like to correct that in the falco repository too?

please bump the chart version

Okay, I'll deal with it right away. Thanks for your review.

Hey @stevenshuang
Thank you! Would you like to correct that in the falco repository too?

Okay. Deal with it now.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please ask for approval from nestorsalceda after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

falco/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To complete the pull request process, please ask for approval from cpanato after the PR has been reviewed.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

falco/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 407325eb868c1d93a1d02363562846afd6deeb88

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: cpanato
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

falco/OWNERS [cpanato]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Collapsable side panels

can collapse right side bar seperate
can collapse main sidebar sepeartely
on side bar collaspe the main frame expands to fill the available space
vscode linter lints whitespace makes it appear I wrote more modules than I did

holy moly, my bad, i haven't looked at this repo for months, I feel honoured that this repo is getting supported by the community
nice idea of an addition, i will have to find some time to look into this, sry that it took so long...

Greetings this is me k_j_code in the discord we spoke about this a month back, and you said you were going to merge when you have time thats ok

I'd like to try and run it locally, to see the changes live, however I get the weird Error: [ERROR] Cannot find module 'virtual:astro-icon' imported from<EMAIL_ADDRESS> Stack trace:     at nodeImport (file:///D:/repos/conform-mode/node_modules/.pnpm/vite@5.2.12_sass@1.77.4/node_modules/vite/dist/node/chunks/dep-BKbDVx1T.js:56262:25)     at eval (D:/repos/conform-mode/node_modules/.pnpm/astro-icon@1.1.1/node_modules/astro-icon/components/Icon.astro:4:37)
Did you use pnpm or npm?

can you maybe deactive the linter and commit again? if possible this would make it easier to review...

Greetings how would I go about deactivatating the linter?

I'd really like to merge this PR but first I need to test it locally. Unfortunately, I have tested it multiple times and I always get an error with the astro-icon package. Node cant find the virtual module.  I cloned your repo, ran pnpm i and pnpm dev in the docs folder and get this error nonetheless:
[ERROR] Cannot find module 'virtual:astro-icon' imported from<EMAIL_ADDRESS>  Stack trace:
    at nodeImport (file:///D:/repos/conform-mode/node_modules/.pnpm/vite@5.2.12_sass@1.77.4/node_modules/vite/dist/node/chunks/dep-BKbDVx1T.js:56262:25)
    at eval (D:/repos/conform-mode/node_modules/.pnpm/astro-icon@1.1.1/node_modules/astro-icon/components/Icon.astro:4:37)

I have also tried to add the types from the package astro-icon but it doesnt work either...
Can you explain what this package does and maybe why it doesnt work on my machine... How did you manage to run it locally?
I feel kinda stupid asking these questions but I would love to integrate the functionality into this plugin but I cant just merge without testing...

Greetings would you like to schedule time to join a zoom call to further debug? https://windmillcode.com/contact
It seems to work when astro-icon is installed in the consumer as well as the library I removed it from the consumer not sure why the library does not install it


source code organization

This pull request cleans up some inconsistency (and an error) in package naming. It also removes some single-class packages and moves some classes into more logical locations.
This is better, however, more work is still needed, see #151.

I've also deleted the unused class FlatClassLoaderService. @DavideD please yell at me if that class was needed for something.

I don't think so. It's probably a leftover from something else

Merged https://github.com/hibernate/hibernate-reactive/pull/152
Nice, Thanks!


mitogen_ansible compares ansible.version without parsing it

ansible.__version__ is a string that contains the release version of Ansible, as a string (e.g. "2.10.0"), ansible_mitogen contains several checks against this to decide on behaviours. These worked up to and including Ansible 2.9, but they are incorrect for 2.10 onward.
I have a patch in the works.

Additionally mitogen contains one comparsion against sys.version, rather than sys.version_info. The Ansible test playbooks contain comparisons direct string comparisons against ansible_version.full.

Additionally mitogen contains one comparsion against sys.version, rather than sys.version_info. The Ansible test playbooks contain comparisons direct string comparisons against ansible_version.full.


Xcode not recognizing .response in certain swift files

In my view controllers, Alamofire works great. However, in my AppDelegate.swift file, when I try to make the same alamofire request, i get an error "Cannot invoke "response" with an argument list of type '((,,,) -> _)'"
The exact function I am using is
Alamofire.request(.PATCH, URL, parameters: params).validate().response { (_, _, _, error) in  }.
Also, if I put in nil for params, it works.

We do not use Github as a support forum for Alamofire. Please open a question on StackOverflow and tag Alamofire. Once you have done so, please post a link to the question in this issue and close this out.
Additionally, there is already a question that is very similar posted that is receiving help. Is this you?

Nope, not me. But I will do as you asked. Question on stackoverflow.


ATC login after pilot login will cause problems

Reported by SKY8906
If ATC login after pilot login:

ATC won't able to see pilot's flight plan
If ATC use distance calculate tool in euroscope, first point is fixed to somewhere

I'm going to improving debug.patch to generate pcap files.

Fixed: d032f94