After Finisih replay block 37519474 can't sync

After spend 2 week with C5.4Xlarge instance for deploy node eos from backup and get stop sync when finish replay .
Need advice to deploy fast sync with history plugin.
info  2019-01-26T11:00:11.311 thread-0  controller.cpp:317            replay               ] existing block log, attempting to replay from 37473401 to 37519474 blocks
info  2019-01-26T11:00:11.311 thread-0  transaction_context.cp:103    deadline_timer       ] Using 8us deadline timer for checktime: min:3us max:14us mean:5us stddev:1us
  37519400 of 37519474
info  2019-01-26T11:25:49.209 thread-0  controller.cpp:328            replay               ] 46073 blocks replayed
info  2019-01-26T11:25:49.209 thread-0  controller.cpp:341            replay               ] 0 reversible blocks replayed
info  2019-01-26T11:25:49.209 thread-0  controller.cpp:345            replay               ] replayed 46073 blocks in 1537 seconds, 33.37958700323400052 ms/block
info  2019-01-26T11:26:24.263 thread-0  controller.cpp:413            init                 ] database initialized with hash: eb1eb95b51f5411c7d13c98488251ad9938a5534edfdfda4988db0922ef101cd
info  2019-01-26T11:26:24.263 thread-0  chain_plugin.cpp:724          plugin_startup       ] starting chain in read/write mode
info  2019-01-26T11:26:24.263 thread-0  chain_plugin.cpp:728          plugin_startup       ] Blockchain started; head block is #37519474, genesis timestamp is 2018-06-08T08:08:08.888
warn  2019-01-26T11:26:24.263 thread-0  bnet_plugin.cpp:1354          plugin_startup       ] bnet startup
warn  2019-01-26T11:26:24.264 thread-1  bnet_plugin.cpp:1408          operator()           ] start thread
info  2019-01-26T11:26:24.265 thread-0  http_plugin.cpp:486           plugin_startup       ] start listening for http requests
info  2019-01-26T11:26:24.267 thread-0  login_plugin.cpp:80           plugin_startup       ] starting login_plugin
info  2019-01-26T11:26:24.267 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/login/finalize_login_request
info  2019-01-26T11:26:24.267 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/login/start_login_request
info  2019-01-26T11:26:24.267 thread-0  net_plugin.cpp:3014           plugin_startup       ] starting listener, max clients is 100
warn  2019-01-26T11:26:24.275 thread-0  net_plugin.cpp:707            connection           ] created connection to <IP_ADDRESS>:19876
info  2019-01-26T11:26:24.275 thread-0  net_plugin.cpp:1921           connect              ] host: <IP_ADDRESS> port: 19876
warn  2019-01-26T11:26:24.275 thread-0  net_plugin.cpp:707            connection           ] created connection to 807534da.eosnodeone.io:19872
info  2019-01-26T11:26:24.275 thread-0  net_plugin.cpp:1921           connect              ] host: 807534da.eosnodeone.io port: 19872
warn  2019-01-26T11:26:24.275 thread-0  net_plugin.cpp:707            connection           ] created connection to api-full1.eoseoul.io:9876
info  2019-01-26T11:26:24.275 thread-0  net_plugin.cpp:1921           connect              ] host: api-full1.eoseoul.io port: 9876
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to api-full2.eoseoul.io:9876
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: api-full2.eoseoul.io port: 9876
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to api.eosuk.io:12000
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: api.eosuk.io port: 12000
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to boot.eostitan.com:9876
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: boot.eostitan.com port: 9876
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to bp.antpool.com:443
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: bp.antpool.com port: 443
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to bp.cryptolions.io:9876
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: bp.cryptolions.io port: 9876
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to bp.eosbeijing.one:8080
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: bp.eosbeijing.one port: 8080
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to bp.libertyblock.io:9800
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: bp.libertyblock.io port: 9800
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to br.eosrio.io:9876
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: br.eosrio.io port: 9876
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to eos-seed-de.privex.io:9876
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: eos-seed-de.privex.io port: 9876
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to eos.nodepacific.com:9876
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: eos.nodepacific.com port: 9876
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to eos.staked.us:9870
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: eos.staked.us port: 9870
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to eu-west-nl.eosamsterdam.net:9876
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: eu-west-nl.eosamsterdam.net port: 9876
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to eu1.eosdac.io:49876
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: eu1.eosdac.io port: 49876
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to fn001.eossv.org:443
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: fn001.eossv.org port: 443
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to fullnode.eoslaomao.com:443
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: fullnode.eoslaomao.com port: 443
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to mainnet.eosarabia.org:3571
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: mainnet.eosarabia.org port: 3571
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to mainnet.eoscalgary.io:5222
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: mainnet.eoscalgary.io port: 5222
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to mainnet.eospay.host:19876
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: mainnet.eospay.host port: 19876
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to mars.fnp2p.eosbixin.com:443
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: mars.fnp2p.eosbixin.com port: 443
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to node.eosflare.io:1883
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: node.eosflare.io port: 1883
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to node1.eosnewyork.io:6987
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: node1.eosnewyork.io port: 6987
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to node2.eosnewyork.io:6987
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: node2.eosnewyork.io port: 6987
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to p.jeda.one:3322
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: p.jeda.one port: 3322
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to p2p.eos.bitspace.no:9876
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: p2p.eos.bitspace.no port: 9876
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to p2p.eosio.cr:1976
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: p2p.eosio.cr port: 1976
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to p2p.meet.one:9876
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: p2p.meet.one port: 9876
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to p2p.one.eosdublin.io:9876
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: p2p.one.eosdublin.io port: 9876
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to p2p.two.eosdublin.io:9876
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: p2p.two.eosdublin.io port: 9876
warn  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:707            connection           ] created connection to p2p.unlimitedeos.com:15555
info  2019-01-26T11:26:24.276 thread-0  net_plugin.cpp:1921           connect              ] host: p2p.unlimitedeos.com port: 15555
warn  2019-01-26T11:26:24.290 thread-0  net_plugin.cpp:707            connection           ] created connection to peer.eosjrr.io:9876
info  2019-01-26T11:26:24.290 thread-0  net_plugin.cpp:1921           connect              ] host: peer.eosjrr.io port: 9876
warn  2019-01-26T11:26:24.290 thread-0  net_plugin.cpp:707            connection           ] created connection to peer.eosn.io:9876
info  2019-01-26T11:26:24.290 thread-0  net_plugin.cpp:1921           connect              ] host: peer.eosn.io port: 9876
warn  2019-01-26T11:26:24.290 thread-0  net_plugin.cpp:707            connection           ] created connection to peer.main.alohaeos.com:9876
info  2019-01-26T11:26:24.290 thread-0  net_plugin.cpp:1921           connect              ] host: peer.main.alohaeos.com port: 9876
warn  2019-01-26T11:26:24.290 thread-0  net_plugin.cpp:707            connection           ] created connection to peer1.mainnet.helloeos.com.cn:80
info  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:1921           connect              ] host: peer1.mainnet.helloeos.com.cn port: 80
warn  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:707            connection           ] created connection to peer2.mainnet.helloeos.com.cn:80
info  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:1921           connect              ] host: peer2.mainnet.helloeos.com.cn port: 80
warn  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:707            connection           ] created connection to peering.mainnet.eoscanada.com:9876
info  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:1921           connect              ] host: peering.mainnet.eoscanada.com port: 9876
warn  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:707            connection           ] created connection to peering2.mainnet.eosasia.one:80
info  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:1921           connect              ] host: peering2.mainnet.eosasia.one port: 80
warn  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:707            connection           ] created connection to pub0.eosys.io:6637
info  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:1921           connect              ] host: pub0.eosys.io port: 6637
warn  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:707            connection           ] created connection to pub1.eosys.io:6637
info  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:1921           connect              ] host: pub1.eosys.io port: 6637
warn  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:707            connection           ] created connection to publicnode.cypherglass.com:9876
info  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:1921           connect              ] host: publicnode.cypherglass.com port: 9876
warn  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:707            connection           ] created connection to seed1.greymass.com:9876
info  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:1921           connect              ] host: seed1.greymass.com port: 9876
warn  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:707            connection           ] created connection to seed2.greymass.com:9876
info  2019-01-26T11:26:24.291 thread-0  net_plugin.cpp:1921           connect              ] host: seed2.greymass.com port: 9876
info  2019-01-26T11:26:24.291 thread-0  producer_plugin.cpp:718       plugin_startup       ] producer plugin:  plugin_startup() begin
info  2019-01-26T11:26:24.294 thread-0  net_plugin.cpp:3046           plugin_shutdown      ] shutdown..
info  2019-01-26T11:26:24.294 thread-0  net_plugin.cpp:3049           plugin_shutdown      ] close acceptor
info  2019-01-26T11:26:24.296 thread-0  net_plugin.cpp:3052           plugin_shutdown      ] close 44 connections
info  2019-01-26T11:26:24.296 thread-0  net_plugin.cpp:3060           plugin_shutdown      ] exit shutdown
warn  2019-01-26T11:26:24.296 thread-0  bnet_plugin.cpp:1436          plugin_shutdown      ] joining bnet threads
warn  2019-01-26T11:26:24.296 thread-1  bnet_plugin.cpp:1408          operator()           ] end thread
warn  2019-01-26T11:26:24.296 thread-0  bnet_plugin.cpp:1440          plugin_shutdown      ] done joining threads
error 2019-01-26T11:26:43.981 thread-0  main.cpp:129                  main                 ] 3110006 plugin_config_exception: Incorrect plugin configuration
node cannot have any producer-name configured because block production is not safe when validation_mode is not "full"
    {}
    thread-0  producer_plugin.cpp:725 plugin_startup

    {}
    thread-0  producer_plugin.cpp:753 plugin_startup
info  2019-01-26T11:32:17.162 thread-0  chain_plugin.cpp:333          plugin_initialize    ] initializing chain plugin
info  2019-01-26T11:32:17.166 thread-0  block_log.cpp:134             open                 ] Log is nonempty
info  2019-01-26T11:32:17.166 thread-0  block_log.cpp:161             open                 ] Index is nonempty
info  2019-01-26T11:32:17.258 thread-0  bnet_plugin.cpp:1317          plugin_initialize    ] Initialize bnet plugin
info  2019-01-26T11:32:17.259 thread-0  bnet_plugin.cpp:1330          plugin_initialize    ] ip_port: <IP_ADDRESS>:4321 host: <IP_ADDRESS> port: 4321 my->_follow_irreversible: false
info  2019-01-26T11:32:17.259 thread-0  http_plugin.cpp:422           plugin_initialize    ] configured http to listen on <IP_ADDRESS>:8888
warn  2019-01-26T11:32:17.259 thread-0  mongo_db_plugin.cpp:1626      plugin_initialize    ] eosio::mongo_db_plugin configured, but no --mongodb-uri specified.
warn  2019-01-26T11:32:17.259 thread-0  mongo_db_plugin.cpp:1627      plugin_initialize    ] mongo_db_plugin disabled.
info  2019-01-26T11:32:17.259 thread-0  net_plugin.cpp:2898           plugin_initialize    ] Initialize net plugin
info  2019-01-26T11:32:17.259 thread-0  net_plugin.cpp:2924           plugin_initialize    ] host: <IP_ADDRESS> port: 9876
info  2019-01-26T11:32:17.259 thread-0  net_plugin.cpp:2995           plugin_initialize    ] my node_id is 26dba8bf2f92230e4806ce8420bb6ab6b91374eb4c8a023b2e8695e772c66bcb
info  2019-01-26T11:32:17.259 thread-0  state_history_plugin.c:543    plugin_initialize    ] ip_port: <IP_ADDRESS>:8080 host: <IP_ADDRESS> port: 8080
info  2019-01-26T11:32:17.259 thread-0  http_plugin.cpp:377           operator()           ] configured http with Access-Control-Allow-Origin: *
info  2019-01-26T11:32:17.259 thread-0  main.cpp:107                  main                 ] nodeos version v1.5.0
info  2019-01-26T11:32:17.259 thread-0  main.cpp:108                  main                 ] eosio root is /home/coinone/.local/share
info  2019-01-26T11:32:17.259 thread-0  main.cpp:109                  main                 ] nodeos using configuration file /mnt/dataeos2/eosio/config/config.ini
info  2019-01-26T11:32:17.259 thread-0  main.cpp:110                  main                 ] nodeos data directory is /mnt/dataeos2/eosio/data
info  2019-01-26T11:32:17.259 thread-0  chain_plugin.cpp:724          plugin_startup       ] starting chain in read/write mode
info  2019-01-26T11:32:17.259 thread-0  chain_plugin.cpp:728          plugin_startup       ] Blockchain started; head block is #37519474, genesis timestamp is 2018-06-08T08:08:08.888
warn  2019-01-26T11:32:17.259 thread-0  bnet_plugin.cpp:1354          plugin_startup       ] bnet startup
info  2019-01-26T11:32:17.259 thread-0  http_plugin.cpp:486           plugin_startup       ] start listening for http requests
warn  2019-01-26T11:32:17.259 thread-1  bnet_plugin.cpp:1408          operator()           ] start thread
info  2019-01-26T11:32:17.259 thread-0  login_plugin.cpp:80           plugin_startup       ] starting login_plugin
info  2019-01-26T11:32:17.259 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/login/finalize_login_request
info  2019-01-26T11:32:17.259 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/login/start_login_request
info  2019-01-26T11:32:17.259 thread-0  net_plugin.cpp:3014           plugin_startup       ] starting listener, max clients is 100
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to <IP_ADDRESS>:19876
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: <IP_ADDRESS> port: 19876
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to 807534da.eosnodeone.io:19872
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: 807534da.eosnodeone.io port: 19872
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to api-full1.eoseoul.io:9876
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: api-full1.eoseoul.io port: 9876
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to api-full2.eoseoul.io:9876
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: api-full2.eoseoul.io port: 9876
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to api.eosuk.io:12000
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: api.eosuk.io port: 12000
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to boot.eostitan.com:9876
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: boot.eostitan.com port: 9876
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to bp.antpool.com:443
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: bp.antpool.com port: 443
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to bp.cryptolions.io:9876
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: bp.cryptolions.io port: 9876
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to bp.eosbeijing.one:8080
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: bp.eosbeijing.one port: 8080
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to bp.libertyblock.io:9800
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: bp.libertyblock.io port: 9800
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to br.eosrio.io:9876
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: br.eosrio.io port: 9876
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to eos-seed-de.privex.io:9876
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: eos-seed-de.privex.io port: 9876
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to eos.nodepacific.com:9876
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: eos.nodepacific.com port: 9876
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to eos.staked.us:9870
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: eos.staked.us port: 9870
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to eu-west-nl.eosamsterdam.net:9876
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: eu-west-nl.eosamsterdam.net port: 9876
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to eu1.eosdac.io:49876
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: eu1.eosdac.io port: 49876
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to fn001.eossv.org:443
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: fn001.eossv.org port: 443
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to fullnode.eoslaomao.com:443
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: fullnode.eoslaomao.com port: 443
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to mainnet.eosarabia.org:3571
info  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:1921           connect              ] host: mainnet.eosarabia.org port: 3571
warn  2019-01-26T11:32:17.266 thread-0  net_plugin.cpp:707            connection           ] created connection to mainnet.eoscalgary.io:5222
info  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:1921           connect              ] host: mainnet.eoscalgary.io port: 5222
warn  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:707            connection           ] created connection to mainnet.eospay.host:19876
info  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:1921           connect              ] host: mainnet.eospay.host port: 19876
warn  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:707            connection           ] created connection to mars.fnp2p.eosbixin.com:443
info  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:1921           connect              ] host: mars.fnp2p.eosbixin.com port: 443
warn  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:707            connection           ] created connection to node.eosflare.io:1883
info  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:1921           connect              ] host: node.eosflare.io port: 1883
warn  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:707            connection           ] created connection to node1.eosnewyork.io:6987
info  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:1921           connect              ] host: node1.eosnewyork.io port: 6987
warn  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:707            connection           ] created connection to node2.eosnewyork.io:6987
info  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:1921           connect              ] host: node2.eosnewyork.io port: 6987
warn  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:707            connection           ] created connection to p.jeda.one:3322
info  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:1921           connect              ] host: p.jeda.one port: 3322
warn  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:707            connection           ] created connection to p2p.eos.bitspace.no:9876
info  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:1921           connect              ] host: p2p.eos.bitspace.no port: 9876
warn  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:707            connection           ] created connection to p2p.eosio.cr:1976
info  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:1921           connect              ] host: p2p.eosio.cr port: 1976
warn  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:707            connection           ] created connection to p2p.meet.one:9876
info  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:1921           connect              ] host: p2p.meet.one port: 9876
warn  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:707            connection           ] created connection to p2p.one.eosdublin.io:9876
info  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:1921           connect              ] host: p2p.one.eosdublin.io port: 9876
warn  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:707            connection           ] created connection to p2p.two.eosdublin.io:9876
info  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:1921           connect              ] host: p2p.two.eosdublin.io port: 9876
warn  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:707            connection           ] created connection to p2p.unlimitedeos.com:15555
info  2019-01-26T11:32:17.267 thread-0  net_plugin.cpp:1921           connect              ] host: p2p.unlimitedeos.com port: 15555
warn  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:707            connection           ] created connection to peer.eosjrr.io:9876
info  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:1921           connect              ] host: peer.eosjrr.io port: 9876
warn  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:707            connection           ] created connection to peer.eosn.io:9876
info  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:1921           connect              ] host: peer.eosn.io port: 9876
warn  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:707            connection           ] created connection to peer.main.alohaeos.com:9876
info  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:1921           connect              ] host: peer.main.alohaeos.com port: 9876
warn  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:707            connection           ] created connection to peer1.mainnet.helloeos.com.cn:80
info  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:1921           connect              ] host: peer1.mainnet.helloeos.com.cn port: 80
warn  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:707            connection           ] created connection to peer2.mainnet.helloeos.com.cn:80
info  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:1921           connect              ] host: peer2.mainnet.helloeos.com.cn port: 80
warn  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:707            connection           ] created connection to peering.mainnet.eoscanada.com:9876
info  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:1921           connect              ] host: peering.mainnet.eoscanada.com port: 9876
warn  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:707            connection           ] created connection to peering2.mainnet.eosasia.one:80
info  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:1921           connect              ] host: peering2.mainnet.eosasia.one port: 80
warn  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:707            connection           ] created connection to pub0.eosys.io:6637
info  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:1921           connect              ] host: pub0.eosys.io port: 6637
warn  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:707            connection           ] created connection to pub1.eosys.io:6637
info  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:1921           connect              ] host: pub1.eosys.io port: 6637
warn  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:707            connection           ] created connection to publicnode.cypherglass.com:9876
info  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:1921           connect              ] host: publicnode.cypherglass.com port: 9876
warn  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:707            connection           ] created connection to seed1.greymass.com:9876
info  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:1921           connect              ] host: seed1.greymass.com port: 9876
warn  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:707            connection           ] created connection to seed2.greymass.com:9876
info  2019-01-26T11:32:17.280 thread-0  net_plugin.cpp:1921           connect              ] host: seed2.greymass.com port: 9876
info  2019-01-26T11:32:17.280 thread-0  producer_plugin.cpp:718       plugin_startup       ] producer plugin:  plugin_startup() begin
info  2019-01-26T11:32:17.280 thread-0  producer_plugin.cpp:740       plugin_startup       ] Launching block production for 1 producers at 2019-01-26T11:32:17.280.
info  2019-01-26T11:32:17.280 thread-0  producer_plugin.cpp:752       plugin_startup       ] producer plugin:  plugin_startup() end
info  2019-01-26T11:32:17.280 thread-0  chain_api_plugin.cpp:77       plugin_startup       ] starting chain_api_plugin
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/abi_bin_to_json
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/abi_json_to_bin
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_abi
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_account
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_block
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_block_header_state
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_code
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_code_hash
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_currency_balance
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_currency_stats
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_info
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_producer_schedule
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_producers
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_raw_abi
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_raw_code_and_abi
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_required_keys
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_scheduled_transactions
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_table_by_scope
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_table_rows
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/get_transaction_id
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/push_block
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/push_transaction
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/chain/push_transactions
info  2019-01-26T11:32:17.281 thread-0  http_plugin.cpp:554           add_handler          ] add api url: /v1/db_size/get
info  2019-01-26T11:32:17.914 thread-0  transaction_context.cp:103    deadline_timer       ] Using 9us deadline timer for checktime: min:3us max:11us mean:5us stddev:2us
info  2019-01-26T11:32:18.685 thread-0  net_plugin.cpp:2142           operator()           ] Peer fn001.eossv.org:443 closed connection
info  2019-01-26T11:32:18.937 thread-0  net_plugin.cpp:2142           operator()           ] Peer peer1.mainnet.helloeos.com.cn:80 closed connection
info  2019-01-26T11:32:18.937 thread-0  net_plugin.cpp:2142           operator()           ] Peer peer2.mainnet.helloeos.com.cn:80 closed connection
info  2019-01-26T11:32:22.492 thread-0  net_plugin.cpp:3046           plugin_shutdown      ] shutdown..
info  2019-01-26T11:32:22.492 thread-0  net_plugin.cpp:3049           plugin_shutdown      ] close acceptor
info  2019-01-26T11:32:22.492 thread-0  net_plugin.cpp:3052           plugin_shutdown      ] close 44 connections
error 2019-01-26T11:32:22.492 thread-0  net_plugin.cpp:1372           request_next_chunk   ] Unable to continue syncing at this time
info  2019-01-26T11:32:22.492 thread-0  net_plugin.cpp:3060           plugin_shutdown      ] exit shutdown
warn  2019-01-26T11:32:22.492 thread-0  bnet_plugin.cpp:1436          plugin_shutdown      ] joining bnet threads
warn  2019-01-26T11:32:22.492 thread-1  bnet_plugin.cpp:1408          operator()           ] end thread
warn  2019-01-26T11:32:22.492 thread-0  bnet_plugin.cpp:1440          plugin_shutdown      ] done joining threads
info  2019-01-26T11:32:57.887 thread-0  chain_plugin.cpp:333          plugin_initialize    ] initializing chain plugin
warn  2019-01-26T11:32:57.894 thread-0  chain_plugin.cpp:700          plugin_initialize    ] 13 St13runtime_error: database dirty flag set
rethrow database dirty flag set:
    {"what":"database dirty flag set"}
    thread-0  chain_plugin.cpp:700 plugin_initialize
error 2019-01-26T11:32:57.896 thread-0  main.cpp:122                  main                 ] database dirty flag set (likely due to unclean shutdown): replay required
info  2019-01-26T11:34:52.388 thread-0  chain_plugin.cpp:333          plugin_initialize    ] initializing chain plugin
warn  2019-01-26T11:34:52.388 thread-0  chain_plugin.cpp:700          plugin_initialize    ] 13 St13runtime_error: database dirty flag set
rethrow database dirty flag set:
    {"what":"database dirty flag set"}
    thread-0  chain_plugin.cpp:700 plugin_initialize
error 2019-01-26T11:34:52.388 thread-0  main.cpp:122                  main                 ] database dirty flag set (likely due to unclean shutdown): replay required
info  2019-01-26T11:36:00.281 thread-0  chain_plugin.cpp:333          plugin_initialize    ] initializing chain plugin
warn  2019-01-26T11:36:00.281 thread-0  chain_plugin.cpp:700          plugin_initialize    ] 13 St13runtime_error: database dirty flag set
rethrow database dirty flag set:
    {"what":"database dirty flag set"}
    thread-0  chain_plugin.cpp:700 plugin_initialize
error 2019-01-26T11:36:00.281 thread-0  main.cpp:122                  main                 ] database dirty flag set (likely due to unclean shutdown): replay required
info  2019-01-26T11:37:50.466 thread-0  chain_plugin.cpp:333          plugin_initialize    ] initializing chain plugin
info  2019-01-26T11:37:50.466 thread-0  chain_plugin.cpp:487          plugin_initialize    ] Hard replay requested: deleting state database
info  2019-01-26T11:37:51.318 thread-0  block_log.cpp:368             repair_log           ] Recovering Block Log...
info  2019-01-26T11:37:51.319 thread-0  block_log.cpp:388             repair_log           ] Moved existing blocks directory to backup location: '/mnt/dataeos2/eosio/data/blocks-2019-01-26T11:37:51.318'
info  2019-01-26T11:37:51.319 thread-0  block_log.cpp:393             repair_log           ] Reconstructing '/mnt/dataeos2/eosio/data/blocks/blocks.log' from backed up block log
coinone@ip-10-0-211-73:~$ tail -f  /mnt/dataeos2/nodeos.log
warn  2019-01-26T11:36:00.281 thread-0  chain_plugin.cpp:700          plugin_initialize    ] 13 St13runtime_error: database dirty flag set
rethrow database dirty flag set:
    {"what":"database dirty flag set"}
    thread-0  chain_plugin.cpp:700 plugin_initialize
error 2019-01-26T11:36:00.281 thread-0  main.cpp:122                  main                 ] database dirty flag set (likely due to unclean shutdown): replay required
info  2019-01-26T11:37:50.466 thread-0  chain_plugin.cpp:333          plugin_initialize    ] initializing chain plugin
info  2019-01-26T11:37:50.466 thread-0  chain_plugin.cpp:487          plugin_initialize    ] Hard replay requested: deleting state database
info  2019-01-26T11:37:51.318 thread-0  block_log.cpp:368             repair_log           ] Recovering Block Log...
info  2019-01-26T11:37:51.319 thread-0  block_log.cpp:388             repair_log           ] Moved existing blocks directory to backup location: '/mnt/dataeos2/eosio/data/blocks-2019-01-26T11:37:51.318'
info  2019-01-26T11:37:51.319 thread-0  block_log.cpp:393             repair_log           ] Reconstructing '/mnt/dataeos2/eosio/data/blocks/blocks.log' from backed up block log

Should be more stable now.


Idea: make KSPBuildTools available through nuget

I Think that msbuild stuff can be put on nuget on its own. That would allow usage without having to deal with submodules

Would definitely help keep it up-to-date, there might be a MSBuild nuget package that you'd reference?

https://github.com/adamralph/minver Did just stumble upon this, much more minimal than GitVersion or Nerdbank and uses Git Tags directly


OSGi Dependency Update

This patch updates several OSGi dependencies.
Amoung others:

Elasticsearch
Apache Karaf
All of the Apache Commons packages
Apache ActiveMQ
GSON
Jettison
junit
RESt-assured
…

Your pull request should…

[x] have a concise title
[x] close an accompanying issue if one exists
[x] be against the correct branch (features can only go into develop)
[x] include migration scripts and documentation, if appropriate
[x] pass automated testing
[x] have a clean commit history
[x] have proper commit messages (title and body) for all commits
[x] have appropriate tags applied

Three modules complained about a junit dependency problem while building:
[INFO] --- maven-dependency-plugin:3.1.2:analyze-only (analyze) @ opencast-userdirectory-moodle ---
[WARNING] Used undeclared dependencies found:
[WARNING]    junit:junit:jar:4.13:test

The modules are
userdirectory-moodle
userdirectory-sakai
userdirectory-brightspace

Adding junit as a dependency did resolve the problem, although I do wonder why these modules claim to rely on junit when they're seemingly not using it?

Added the Elasticsearch update to the new container compose files added with pull request #1895


Source code?

There is a way to read the src code so the community may push new updates? I really like New Frontier, and for me is the right way to play minecraft in 2022, but I would like to add more content ( even if it's just for me ). After going through the files I only found the xdelta, there is a way to compile/decompile it?

README.md explains how to use the source package. Also this isn't an issue.


Add support to migrate wiki from PostgreSQL dump files.

This is a small update to allow generating GitHub wiki pages from Trac pq_dump.
It only handled the creation of the git revision.
There is no content conversion in this PR.
TracWiki to MediaWiki or to Markdown or to RST can be done in a separate ticket.

@danuker please give it a try ... i think that the code works, so this only needs a quick sanity check.
The result is here https://github.com/twisted/twisted/wiki/ReviewProcess
with wiki at https://github.com/twisted/twisted.wiki.git


Using relation fields as ID on a Prisma model doesn't work

@nikolasburk  The example given in the release 2.0.0-preview024: Use relation fields as ID on a Prisma model didn't work when I added directly to my schema.prisma file.
<EMAIL_ADDRESS>binary version: d3b0ceed5d87544b9d2decb70e08664f9047bb73
generator client {
  provider = "prisma-client-js"
}

datasource db {
  provider = "postgresql"
  url      = env("DATABASE_URL")
}

model Movie {
  director Director @id
  title    String
}

model Director {
  id Int @id @default(autoincrement())
  name String
}

throws Error:
 ERROR  Oops, an unexpected error occured!
Failure during a migration command: Connector error. (error: Error querying the database: Error querying the database: Error querying the database: db error: ERROR: foreign key constraint "Movie_director_fkey" cannot be implemented)

Please help us improve Prisma 2 by submitting an error report.
Error reports never contain personal or other sensitive information.
Learn more: https://pris.ly/d/telemetry

I am unable to reproduce the issue with migrate in preview024 and as well as in preview023.
I was also able to query the data in preview024. It doesn't work in preview023 as expected as support for this feature was released in preview024.
So please try again this with a fresh database using preview024.

@martineboh I am going to close this as its been 3 months now and there is no activity here.
Please reply if you want us to take another look.

I'm getting this error with this model. I believe there are no errors here
model FormPipeline {
  id                              String            @id @default(uuid())
  slug                            String
  title                           String
  salesDomainId                   String
  salesDomain                     SalesDomain       @relation(fields: [salesDomainId], references: [id])
  body                            Json
  changedAt                       DateTime
  formPipelineDependencyIds       String[]
  formPipelineDependencies        FormPipeline[]    @relation("FormPipelineFormPipelineDependency", fields: [formPipelineDependencyIds])
  processPipelineDependencies     ProcessPipeline[]
  constantDependencies            Constant[]
  tableDependencies               Table[]           @relation("FormPipelineTableDependency")
  dependantFormPipelineIds        String[]
  dependantFormPipelines          FormPipeline[]    @relation("FormPipelineFormPipelineDependency", fields: [dependantFormPipelineIds])
  dependantOfferingsAsPayload     Offering[]        @relation("OfferingPayloadFormPipelineDependency")
  dependantOfferingsAsQuoteResult Offering[]        @relation("OfferingQuoteResultFormPipelineDependency")
  dependantOfferingsAsOrderResult Offering[]        @relation("OfferingOrderResultFormPipelineDependency")
}

Please open a new issue @FrankSandqvist and we are happy to look into this. Tjanks.


Separate env provisioning

What does this PR do?
Provision common environment variables (e.g. DEVWORKSPACE_ID) and workspaceEnv-defined environment variables only into components defined in the devfile (i.e. don't provision them into project-clone, async sidecar, etc.)
What issues does this PR fix or reference?
Potential for e.g. workspaceEnv to interfere with built-in containers.
Is it tested? How?
Create a devworkspace, inspect the pod that holds the deployment. Non-devfile containers should not have any unnecessary environment variables.
PR Checklist

[ ] E2E tests pass (when PR is ready, comment /test v8-devworkspace-operator-e2e, v8-che-happy-path to trigger)

[ ] v8-devworkspace-operator-e2e: DevWorkspace e2e test
[ ] v8-che-happy-path: Happy path for verification integration with Che

Fixes https://github.com/devfile/devworkspace-operator/issues/715

/test v8-devworkspace-operator-e2e


KAFKA-4705: ConfigDef should support deprecated keys as synonyms

There is a minor merge conflicts that needs to be resolved.

@cmccabe What is the status of this? I think it would be nice to get it for <IP_ADDRESS> -- not sure if you find time finishing this up. My PR #2648 depends on this one :)

@cmccabe ping, looks like we might only need a rebase on this PR to get it merged

rebased

LGTM.

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5701/
Test FAILed (JDK 8 and Scala 2.12).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5715/
Test PASSed (JDK 7 and Scala 2.11).

Test failure is a Jenkins environment issue:
Total time: 1 hrs 27 mins 13.543 secs
[FINDBUGS] Collecting findbugs analysis files...
Setting GRADLE_3_4_RC_2_HOME=/home/jenkins/jenkins-slave/tools/hudson.plugins.gradle.GradleInstallation/Gradle_3.4-rc-2
ERROR: Step ?Publish FindBugs analysis results? aborted due to exception:
java.lang.OutOfMemoryError: GC overhead limit exceeded
Caused: java.io.IOException: Remote call on ubuntu-2 failed
	at hudson.remoting.Channel.call(Channel.java:838)
	at hudson.FilePath.act(FilePath.java:985)
Caused: java.io.IOException: remote file operation failed: /home/jenkins/jenkins-slave/workspace/kafka-pr-jdk8-scala2.12 at hudson.remoting.Channel@4cfb1c65:ubuntu-2
	at hudson.FilePath.act(FilePath.java:992)
	at hudson.FilePath.act(FilePath.java:974)

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk7-scala2.11/5725/
Test PASSed (JDK 7 and Scala 2.11).

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/kafka-pr-jdk8-scala2.12/5711/
Test PASSed (JDK 8 and Scala 2.12).

@cmccabe Any update on this one?

Ping an this again... It is still blocking one of my PRs... \cc @guozhangwang

I already gave a +1 on this, and I think once @cmccabe addressed @ijuma 's comments it is good to go.

@ijuma Can you have a look? This is still blocking one of my PRs.

@mjsax it's near the top of my list.

Ping.

Another regular ping here...

Ping :)

Retest this please.

SUCCESS
8069 tests run, 5 skipped, 0 failed.
--none--

SUCCESS
8069 tests run, 5 skipped, 0 failed.
--none--

FAILURE
7961 tests run, 5 skipped, 2 failed.
--none--

@cmccabe @ijuma What is the status here?

Sorry, have been having a hard time getting back to this. Hopefully tomorrow.

Periodic ping :)

Anything new here?

Closing as stale since this is quite old


Reorder material for 1st day, add functions exercise

As discussed, the functions part was moved right after pointers and references.
There's a small exercise for pass by copy / pass by reference
Some small tweaks / fix typos.
Added code highlighting to slides where symbolic stacks are shown.

Note:
On the slide about arrays and pointers, there was an array cookie/pointer after the array on the symbolic stack. Since this isn't a dynamic allocation, there shouldn't be anything but padding bytes, so I removed it. It won't make a difference for the lecture.

Close in  favour of #3


Add CODEOWNERS

It's already there (3 lines, 2 lines of source code, https://github.com/SwissDataScienceCenter/renga-ui/blob/62480236f4cb7550864f9c4d4cbf1ecdc8a7c49b/CODEOWNERS). Before there was the 'no newline at the end of file' warning from git. Sorry, hard to see this since i amended the commit and force-updated the branch.


Approaches to get a destructor when main finishes.

Hi, I have a problem that I wish I could rely somehow on destruction of lazy_static to call drop on what's inside it. I know it might be impossible, but I guess it's worth asking. Suggestions for workaround etc. are welcome. I was eg. thinking about using a Weak inside lazy_static, but then I do have to have a strong reference somewhere in the main thread.

Rust as a language has basically made the design decision to not have custom user code running before or after main(), so if a static variable contains a type with a destructor, that destructor will just never be called. As far as I'm aware, there is no good way to have a automatic destruction anyway, so lazy_static just mirrors that semantic.
However, the crate could provide something like lazy_static::destroy() for manually destroying a static. The issue there is just that the internally used std::Once has no way to be "reset", so someone who is more knowledgeable about thread synchronisation primitives than I would have to write a custom implementation for that (which would also be useful for #60).

One possible workaround you could do is to have the lazy_static be of a Mutex<Option<T>> or similar, and then destroy the T by overwriting the Option with a None

For synchronization I'm quite sure to resort to ArcCell from crossbeam or what you have mentioned.

It's been a while now, so I'll go ahead and close this issue as a design decision we inherit from Rust upstream. Please feel free to re-open though if there's anything more you'd like to add!

FYI this affects crate tempfile.


Feat/generate postgres secret

What this PR does / why we need it:
Changes the default behaviour of setting the postrges password. As described in #214 the existingSecret attribute is used. The matching secret is generated by this chart and won't get overwritten when an upgrade is done.
Which issue this PR fixes

fixes #214

Special notes for your reviewer:
It's a kind of a breaking change, but the actual default behaviour also, because it generates a new password everytime the chart runs. I don't know if my documentation for that is sufficient. Please give me a hint about this.
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] PR is based off the current tip of the main branch.
[x] Changes are documented under the "Unreleased" header in CHANGELOG.md
[x] New or modified sections of values.yaml are documented in the README.md
[x] Commits follow the Kong commit message guidelines

Do you know if this is actually still needed in any scenario? I think our upgrade to the latest Bitnami chart version obsoleted it. Per https://github.com/bitnami/charts/pull/4416#issuecomment-1094880576 part of that was migrating to a lookup-based password Secret manager, and a brief test indicates that it's indeed no longer replaced on upgrade:
11:13:50-0700 esenin $ kubectl get secrets aaa-postgresql -oyaml
apiVersion: v1
data:
  password: eEQ0ME9lZU8xWA==
  postgres-password: RkpiYVFqVVpYWg==
kind: Secret
metadata:
  annotations:
    meta.helm.sh/release-name: aaa
    meta.helm.sh/release-namespace: default
  creationTimestamp: "2022-04-18T18:12:35Z"
  labels:
    app.kubernetes.io/instance: aaa
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: postgresql
    helm.sh/chart: postgresql-11.1.15
  name: aaa-postgresql
  namespace: default
  resourceVersion: "1493"
  uid: ecd99333-f063-4a35-928d-4ea706ac7467
type: Opaque

11:13:57-0700 esenin $ helm upgrade aaa kong/kong -f /tmp/values.yaml
Release "aaa" has been upgraded. Happy Helming!
NAME: aaa
LAST DEPLOYED: Mon Apr 18 11:14:09 2022
NAMESPACE: default
STATUS: deployed
REVISION: 2
NOTES:
...

11:14:14-0700 esenin $ kubectl get secrets aaa-postgresql -oyaml
apiVersion: v1
data:
  password: eEQ0ME9lZU8xWA==
  postgres-password: RkpiYVFqVVpYWg==
kind: Secret
metadata:
  annotations:
    meta.helm.sh/release-name: aaa
    meta.helm.sh/release-namespace: default
  creationTimestamp: "2022-04-18T18:12:35Z"
  labels:
    app.kubernetes.io/instance: aaa
    app.kubernetes.io/managed-by: Helm
    app.kubernetes.io/name: postgresql
    helm.sh/chart: postgresql-11.1.15
  name: aaa-postgresql
  namespace: default
  resourceVersion: "1493"
  uid: ecd99333-f063-4a35-928d-4ea706ac7467
type: Opaque

So I think all we need to do now is mark that the FAQ only applies to Kong chart versions <2.8.

You're right, it's fixed for the update case in the new bitnami chart. But the annotation "helm.sh/resource-policy": "keep" isn't used for the secret, so you can't do a helm delete and reinstall the chart like you often do in development situations.
I think with explicit secret generation it's more robust than the original way of bitnami. But it's just my personal opinion.
It's no problem if you won't merge it, cause I still could use explicit secret generation in my use case.

The upgrade case was more of a concern, since it meant losing something you didn't intend to (access to the current DB you're still trying to use) with no way to recover. The delete one less so, since that's instead something you should have deleted but didn't. The old PVC that breaks subsequent installs should be deleted regardless since it will also contain old DB rows and schemas, not just the previous password, so closing this in favor of improving that doc in https://github.com/Kong/charts/pull/586


fixed spine texture bug when using prefixes

This PR

Fixes a bug

Describe the changes below:
When using an asset pack with a prefix, and loading a spine file, the prefix gets appended twice since it was added manually here (the loader already appends the prefix).
example asset pack, with testasset.png referenced by the .atlas:
{
    "scenePack": {
        "prefix": "testpack-",
        "files": [
            {
                "type": "spine",
                "key": "testasset",
                "jsonURL": "assets/testasset.json",
                "atlasURL": "assets/testasset.atlas"
            }
        ]
    },
}

This results in the spine missing textures at runtime, because the spine plugin searches the texture cache for "testpack-testpack-testasset.png" instead of "testpack-testasset.png".

👍

👍


Revert "Update game"

Reverts bielaugustos/skills-review-pull-requests#1

Well done, leaving a review.


retry on conflict: cluster console object

Description
This PR allows operator retry updating the console object cluster when version conflict happens.
This can happen often because the console object is shared by all the cluster.
This eliminates the confusing log like
2024-10-03T19:35:22+02:00	ERROR	Reconciler	Failed to remove console UI	{"error": "failed to deactivate Console Plugin: failed to update Console: Operation cannot be fulfilled on consoles.operator.openshift.io \"cluster\": the object has been modified; please apply your changes to the latest version and try again"}
github.com/openshift/lightspeed-operator/internal/controller.(*OLSConfigReconciler).Reconcile
	/home/hasun/GitRepo/lightspeed-operator/internal/controller/olsconfig_controller.go:125
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Reconcile
	/home/hasun/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.3/pkg/internal/controller/controller.go:119
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
	/home/hasun/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.3/pkg/internal/controller/controller.go:316
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
	/home/hasun/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.3/pkg/internal/controller/controller.go:266
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2
	/home/hasun/go/pkg/mod/sigs.k8s.io/controller-runtime@v0.17.3/pkg/internal/controller/controller.go:227

Type of change

[ ] Refactor
[ ] New feature
[ ] Bug fix
[ ] CVE fix
[x] Optimization
[ ] Documentation Update
[ ] Configuration Update
[ ] Bump-up dependent library

Related Tickets & Documents

Related Issue #
Closes #

Checklist before requesting a review

[ ] I have performed a self-review of my code.
[ ] PR has passed all pre-merge test jobs.
[ ] If it is a core feature, I have added thorough tests.

Testing

Please provide detailed steps to perform tests related to this code change.
How were the fix/results from this change verified? Please provide relevant screenshots or results.

@raptorsun The console spec is empty even when the console is active. Please check the updates .

We need keep modifying the console CR in the operator code.
The console  short hand has 2 CRDs:

consoles.config.openshift.io
consoles.operator.openshift.io

In the operator we uses consoles.operator.openshift.io.
It is a cluster scope object so we often encouter a conflict of update when the console operator is updating its fields such as the status. So we had better silently retry the update in case of version conflict .
apiVersion: operator.openshift.io/v1
kind: Console
metadata:
  annotations:
    capability.openshift.io/name: Console
    include.release.openshift.io/hypershift: "true"
    include.release.openshift.io/ibm-cloud-managed: "true"
    include.release.openshift.io/self-managed-high-availability: "true"
    include.release.openshift.io/single-node-developer: "true"
    release.openshift.io/create-only: "true"
  creationTimestamp: "2024-10-09T16:14:54Z"
  generation: 5
  name: cluster
  ownerReferences:
  - apiVersion: config.openshift.io/v1
    kind: ClusterVersion
    name: version
    uid: 08f159e9-6c3c-488c-8199-f52a23793544
  resourceVersion: "47097"
  uid: 7dbd6d6f-3fa3-4709-9a01-8825e61ce9e5
spec:
  customization:
    addPage: {}
    customLogoFile:
      name: ""
    developerCatalog:
      types:
        state: Enabled
    projectAccess: {}
    quickStarts: {}
  logLevel: Normal
  managementState: Managed
  observedConfig: null
  operatorLogLevel: Normal
  plugins:
  - monitoring-plugin
  - lightspeed-console-plugin
  providers: {}
  route:
    hostname: ""
    secret:
      name: ""
  unsupportedConfigOverrides: null
status:
  conditions:
  - lastTransitionTime: "2024-10-09T16:21:09Z"
    status: "False"
    type: ConsoleNotificationSyncDegraded
  - lastTransitionTime: "2024-10-09T16:21:09Z"
    status: "False"
    type: ConsoleNotificationSyncProgressing
  - lastTransitionTime: "2024-10-09T16:21:09Z"
    status: "False"
    type: ManagementStateDegraded
  - lastTransitionTime: "2024-10-09T16:21:09Z"
    status: "False"
    type: PDBSyncDegraded
  - lastTransitionTime: "2024-10-09T16:21:09Z"
    status: "False"
    type: PDBSyncProgressing
  - lastTransitionTime: "2024-10-09T16:21:17Z"
    status: "True"
    type: DownloadsDefaultRouteSyncUpgradeable
....

/lgtm
/approve

/override "Red Hat Konflux / lightspeed-operator-on-pull-request"


Add documentation for custom inno setup template

Adds documentation on how to use a custom inno setup template.
I used this for my project and it looks like the author of this issue is trying to do the same.

LGTM


Remat uses inefficient custom forward kernel

Description
When defining custom kernels, there are three distinct kernels for a jax.custom_vjp: f, f_fwd, f_bwd. When inside a jax.vjp and jax.remat, all three kernels should called: first f, then f_fwd, then f_bwd. Instead, f_fwd is called twice and f_bwd is called once:
@jax.custom_vjp
def f(x):
  jax.debug.print('f')
  return jnp.sin(x)

def f_fwd(x):
  jax.debug.print('f_fwd')
  return jnp.sin(x), (x,)

def f_bwd(res, g):
  jax.debug.print('f_bwd')
  x, = res
  cos_x = jnp.cos(x)  # do the cosine here
  return (cos_x * g,)

f.defvjp(f_fwd, f_bwd)

def temp(x):
  out = jax.remat(f)(x)
  out = out ** 2
  return out

jax.jit(jax.grad(temp))(3.2)

prints
# f_bwd
# f_fwd
# f_fwd

This is not a problem with f, f_fwd defined using standard JAX functions due to XLA DCE. With custom kernels, f_fwd will be indeed be called twice, which is generally slower than f as it must move residuals/intermediates to GPU DRAM, which can be very slow.
This impacts all JAX custom kernel libraries.
@mattjj, @chr1sj0nes
System info (python version, jaxlib version, accelerator, etc.)
import jax; jax.print_environment_info()
jax:    0.4.29
jaxlib: 0.4.29
numpy:  1.26.3
python: 3.11.8
jax.devices (1 total, 1 local): [cuda(id=0)]
process_count: 1
platform: ...

Thanks for raising this!
Something not represented in your minimal repro: because it doesn't actually use custom primitives/kernels, and instead calls regular JAX functions, the cosine will actually get DCE'd (at the JAX level, not the XLA level):
import jax
import jax.numpy as jnp

@jax.custom_vjp
def f(x):
  jax.debug.print('f')
  return jnp.sin(x)

def f_fwd(x):
  jax.debug.print('f_fwd')
  return jnp.sin(x), (x,)

def f_bwd(res, g):
  jax.debug.print('f_bwd')
  x, = res
  cos_x = jnp.cos(x)  # do the cosine here
  return (cos_x * g,)

f.defvjp(f_fwd, f_bwd)

def temp(x):
  out = jax.remat(f)(x)
  out = out ** 2
  return out

print(jax.make_jaxpr(jax.grad(temp))(3.2))  # CHANGED

{ lambda ; a:f32[]. let
    debug_callback[
      callback=<function debug_callback.<locals>._flat_callback at 0x7f5f56355750>
      effect=Debug
    ]
    b:f32[] = sin a
    _:f32[] = integer_pow[y=2] b
    c:f32[] = integer_pow[y=1] b
    d:f32[] = mul 2.0 c
    e:f32[] = mul 1.0 d
    f:f32[] = remat2[
      differentiated=True
      jaxpr={ lambda ; g:f32[] h:f32[]. let
          debug_callback[
            callback=<function debug_callback.<locals>._flat_callback at 0x7f5f56355750>
            effect=Debug
          ]
          _:f32[] = sin g
          debug_callback[
            callback=<function debug_callback.<locals>._flat_callback at 0x7f5f56355bd0>
            effect=Debug
          ]
          i:f32[] = cos g
          j:f32[] = mul i h
        in (j,) }
      policy=None
      prevent_cse=True
    ] a e
  in (f,) }

There aren't two cosines!
But in the custom kernel case, that DCE won't happen. At least not by itself.
But a simple fix would just be to teach JAX's DCE about your custom primitives. In particular, if you have a custom primitive like f_fwd_p, we could set its DCE rule to check if residuals are unused, and if so then just call f_p (i.e. the primal primitive). DCE rules are very simple to register for primitives.
In your real example, do you have primitives like this? E.g. one for the primal computation f, one for f_fwd, and one for f_bwd? Or is your setup different, e.g. with pallas_calls?
Basically, to see if some fast solutions are feasible, we should make your example program model this aspect of your real program.
The DCE approach is basically a way to clean up the mess after we've made it. We also have an idea to avoid making the mess in the first place, but it requires some bigger JAX autodiff changes. So I'd like to see if a quick DCE solution will get you un-stuck.
WDYT?

Here's an example of what I mean:
import jax
import jax.numpy as jnp

from jax._src import core

f_p = core.Primitive('f')
f_fwd_p = core.Primitive('f_fwd')
f_bwd_p = core.Primitive('f_bwd')

f_fwd_p.multiple_results = f_bwd_p.multiple_results = True

@f_p.def_abstract_eval
def f(x): return x

@f_fwd_p.def_abstract_eval
def f_fwd(x):
  return x, x

@f_bwd_p.def_abstract_eval
def f_fwd(x, g):
  return g,

@jax.custom_vjp
def f(x):
  return f_p.bind(x)

def f_fwd(x):
  return f_fwd_p.bind(x)

def f_bwd(res, g):
  return (*f_bwd_p.bind(res, g),)

f.defvjp(f_fwd, f_bwd)

def temp(x):
  out = jax.remat(f)(x)
  out = out ** 2
  return out

jaxpr = jax.make_jaxpr(jax.grad(temp))(3.2)
print(jaxpr)

{ lambda ; a:f32[]. let
    b:f32[] _:f32[] = f_fwd a
    _:f32[] = integer_pow[y=2] b
    c:f32[] = integer_pow[y=1] b
    d:f32[] = mul 2.0 c
    e:f32[] = mul 1.0 d
    f:f32[] = remat2[
      differentiated=True
      jaxpr={ lambda ; g:f32[] h:f32[]. let
          _:f32[] i:f32[] = f_fwd g
          j:f32[] = f_bwd i h
        in (j,) }
      policy=None
      prevent_cse=True
    ] a e
  in (f,) }

Notice we're calling f_fwd twice, and in the primal pass call we're dropping its second output.
But here's how we can set up a DCE rule:
from jax._src.interpreters import partial_eval as pe
def f_fwd_dce(used_outs: list[bool], eqn):
  _, res_used = used_outs
  if res_used:
    return [True], eqn
  else:
    new_eqn = eqn.replace(outvars=eqn.outvars[:1], primitive=f_p)
    return [True], new_eqn
pe.dce_rules[f_fwd_p] = f_fwd_dce

print(pe.dce_jaxpr(jaxpr.jaxpr, [True] * len(jaxpr.out_avals))[0])

{ lambda ; a:f32[]. let
    b:f32[] = f a
    c:f32[] = integer_pow[y=1] b
    d:f32[] = mul 2.0 c
    e:f32[] = mul 1.0 d
    f:f32[] = remat2[
      differentiated=True
      jaxpr={ lambda ; g:f32[] h:f32[]. let
          _:f32[] i:f32[] = f_fwd g
          j:f32[] = f_bwd i h
        in (j,) }
      policy=None
      prevent_cse=True
    ] a e
  in (f,) }

That's interesting. I didn't know it was possible. We are currently using triton_call or pallas_call, but it might be possible to wrap them in primitives and use DCE.
A concrete example would be a Pallas kernel equivalent to the following:
def f(x, w):
  y = x @ w
  z = jax.nn.gelu(y)
  return z

The inference version of the kernel will output z only, but when training, we need to output both y and z.

triton_call is already wrapped as a primitive. Let's try fix it at the Pallas/jax-triton level.

It may also be possible to skip additional primitive-wrapping; we could also register a DCE rule for triton_call and pallas_call that dispatches to a table of handlers indexed by the callables passed to those calls, or something.

I think we should consider the DCE approach the canonical solution until we make some big revisions to autodiff (cc @dfm).
@sbodenstein if you're blocked on the DCE approach, let me know and I can help.

I think the explicit DCE solution should be fine. Will let you know if we hit any issues.


Treat SCSS files changes as live CSS changes

Hey, great extension, been using it a lot lately!
This PR allows people to save scss files and just have the stylesheets reload rather than triggering a full page reload the same way css file updates happen.
Only works if you've added scss to the list of files to trigger too (livereload.exts) so it should be safe.
What do you think?
Tested locally & works well.

Thanks for PR. I patched it for me, works great!


build: Restrict the push trigger to the main branch

There's no need to trigger on every push and pull_requests that merge to master, because we end up with duplicate runs on every PR.
I think what we want here is:

Run on every change to a PR that merges to main (covered by the pull_request trigger) so that devs can validate their code works.
Run on every commit that is merged into main (covered by the new restrictions on the push trigger) so that we validate the code still works once it is pushed, and publish things accordingly.

If we agree on this, it will need to be applied to other projects as well.
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] I have added tests that validate the behaviour of the software
[ ] I validated that new and existing unit tests pass locally with my changes
[ ] Any dependent changes have been merged and published in downstream modules

@Kayra1 You mentioned something about requirements.in in the daily -- can you explain what the issue is?


Dependencies on external file

Checklist

[X] Used a personal fork of the feedstock to propose changes
[X] Bumped the build number (if the version is unchanged)
[X] Reset the build number to 0 (if the version changed)
[X] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[X] Ensured the license file is being packaged.

@conda-forge-admin, please rerender

Hi! This is the friendly automated conda-forge-linting service.
I wanted to let you know that I linted all conda-recipes in your PR (recipe) and found some lint.
Here's what I've got...
For recipe:

Failed to even lint the recipe, probably because of a conda-smithy bug 😢. This likely indicates a problem in your meta.yaml, though. To get a traceback to help figure out what's going on, install conda-smithy and run conda smithy recipe-lint . from the recipe directory.

This relates to conda-forge/wecopttool-feedstock#8

@conda-forge-admin, please rerender


UIScrollView+ZFPlayer导致crash

滑动任意 UIScrollView cpu暴涨崩溃

- (void)scrollViewWillBeginDragging:(UIScrollView *)scrollView {     self.offsetY_last = scrollView.contentOffset.y; }
为什么要用代理的方法名，递归了～

Dervice: iPhone 5s
Version: 10.1.1

收到，我在优化一下

可以加一下我qq吗 459643690，帮我一块测试完善一下。

已经申请加你了
                        levi akeman

<EMAIL_ADDRESS>
签名由 网易邮箱大师 定制
在2018年06月06日 17:09，紫枫 写道： 可以加一下我qq吗 459643690，帮我一块测试完善一下。
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or mute the thread.
{"@context":"http://schema.org","@type":"EmailMessage","potentialAction":{"@type":"ViewAction","target":"https://github.com/renzifeng/ZFPlayer/issues/428#issuecomment-395000169","url":"https://github.com/renzifeng/ZFPlayer/issues/428#issuecomment-395000169","name":"View Issue"},"description":"View this Issue on GitHub","publisher":{"@type":"Organization","name":"GitHub","url":"https://github.com"}}
{"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/renzifeng/ZFPlayer","title":"renzifeng/ZFPlayer","subtitle":"GitHub repository","main_image_url":"https://assets-cdn.github.com/images/email/message_cards/header.png","avatar_image_url":"https://assets-cdn.github.com/images/email/message_cards/avatar.png","action":{"name":"Open in GitHub","url":"https://github.com/renzifeng/ZFPlayer"}},"updates":{"snippets":[{"icon":"PERSON","message":"@renzifeng in #428: 可以加一下我qq吗 459643690，帮我一块测试完善一下。"}],"action":{"name":"View Issue","url":"https://github.com/renzifeng/ZFPlayer/issues/428#issuecomment-395000169"}}}
{
"@type": "MessageCard",
"@context": "http://schema.org/extensions",
"hideOriginalBody": "false",
"originator": "37567f93-e2a7-4e2a-ad37-a9160fc62647",
"title": "Re: [renzifeng/ZFPlayer] UIScrollView+ZFPlayer导致crash (#428)",
"sections": [
{
"text": "",
"activityTitle": "紫枫",
"activityImage": "https://assets-cdn.github.com/images/email/message_cards/avatar.png",
"activitySubtitle": "@renzifeng",
"facts": [
]
}
],
"potentialAction": [
{
"name": "Add a comment",
"@type": "ActionCard",
"inputs": [
{
"isMultiLine": true,
"@type": "TextInput",
"id": "IssueComment",
"isRequired": false
}
],
"actions": [
{
"name": "Comment",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "IssueComment",\n"repositoryFullName": "renzifeng/ZFPlayer",\n"issueId": 428,\n"IssueComment": "{{IssueComment.value}}"\n}"
}
]
},
{
"name": "Close issue",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "IssueClose",\n"repositoryFullName": "renzifeng/ZFPlayer",\n"issueId": 428\n}"
},
{
"targets": [
{
"os": "default",
"uri": "https://github.com/renzifeng/ZFPlayer/issues/428#issuecomment-395000169"
}
],
"@type": "OpenUri",
"name": "View on GitHub"
},
{
"name": "Unsubscribe",
"@type": "HttpPOST",
"target": "https://api.github.com",
"body": "{\n"commandName": "MuteNotification",\n"threadId": 342927509\n}"
}
],
"themeColor": "26292E"
}


Build instructions

It would be great to have instructions on how to build the bundle for deployment myself especially since there seem to be external dependencies.

related to #48


Image Builder Improvements

refactor pyfunc base image

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #
Does this PR introduce a user-facing change?:

Checklist

[ ] Added unit test, integration, and/or e2e tests
[ ] Tested locally
[ ] Updated documentation
[ ] Update Swagger spec if the PR introduce API changes
[ ] Regenerated Golang and Python client if the PR introduce API changes

@ariefrahmansyah, not sure if this is WIP but could you please summarize the changes in the PR description? Like in https://github.com/caraml-dev/merlin/pull/483.
It will make it a lot easier to review. (Doesn't need to be elaborate, a summary of the motivation and the key changes will do.) Thanks!

-> Why is the python/sdk/test/pyfunc/model_2.joblib file removed in this PR? Isn't it needed by the integration tests?
When running pyfunc_integration_test.py from local machine, it will re-train the model hence updating the model. I deleted it  but forgot to restore the old one. I've restored it know.


Custom Icon Presets (Angular, Nest, React, Redux, NgRx)

NgRx is basically an implementation of the same concept as Redux and Flux, and uses a lot of terminology taken from Redux.
Most of the file associations for Redux files therefore work with NgRx files, which is great! But there's one that doesn't. Where Redux has "epics", NgRx has "effects". They do the same thing, but while the first gets a unique icon, the latter just gets the default .ts (or .js) icon.
I'd like the regex .*([eE])ffects?\.(js|ts)$ to return the same file icon (in the same colour) as .*([eE])pics?\.(js|ts)$.
When I saw that custom file associations had been added, I was hoping I could do it myself in Settings. But it looks like we don't have access to the internal icons, and need to provide our own icon files for these custom associations.

I have a plan to add custom "presets" to switch icons according to the framework - for instance nest/angular or redux/ngrx...

Oh, I like that! Yeah, there must be a lot of overlap between these things, come to think of it. I certainly don't mind that my NgRx files have the Redux logo as their icon, but the option to just tell the plugin "No, these are NgRx" would definitely be nice!

You know what you did? You put the idea in my head for specifically NgRx icons, and I spent the morning bouncing back and forth between Paint.net and Inkscape, creating those icons! Should have been working...

Hi @mallowigi I'm keen for this feature I thought I might try to make a pull request for it.
I've forked and cloned the repo but when I try to build the plugin in IntelliJ I'm getting a file not found error: java.io.FileNotFoundException: C:\Data\Dev\a-file-icon-idea\publishToken , is this publishToken file needed to build the plugin locally?

Just create an empty file at the root
--
Elior
On 4 Feb 2021, 4:58 +0200, Peter Scriven<EMAIL_ADDRESS>wrote:

Hi @mallowigi I'm keen for this feature I thought I might try to make a pull request for it.
I've forked and cloned the repo but when I try to build the plugin in IntelliJ I'm getting a file not found error: java.io.FileNotFoundException: C:\Data\Dev\a-file-icon-idea\publishToken , is this publishToken file needed to build the plugin locally?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.

That did it, thanks!

Well it turns out I didn't need to make a fork and my issue was solved just using the Custom File Associations. I'll leave my solution here for anyone who comes looking with the same problem. Here are the icons and patterns I used:
Icons:
Actions:  .*\.actions?\.[tj]s$
Reducers:  .*([rR])educers?\.[tj]s$
Selectors:  .*([sS])electors?\.[tj]s$
I also added icons for the respective test files:
Effects Tests:  .*\.effects?\.spec\.[tj]s$
Reducer Tests:  .*([rR])educers?\.spec\.[tj]s$
Selector Tests:  .*([sS])electors?\.spec\.[tj]s$
Additionally the codebase I work with uses the Facade Pattern so I added an icon for that and it's tests as well:
Facade:  .*\.facade\.[tj]s$
Facade Tests:  .*\.facade\.spec\.[tj]s$
This is what my Custom File Associations look like:

And this is what the files end up looking like in WebStorm: ✨

where you choose icons?

You can download the bundled icons in here: https://github.com/mallowigi/iconGenerator

@TutoDS Whoops I was linking to my fork which I've deleted now. Here's a zip of the new icons I made.
ngrx-icons.zip


wait for player to show before play is actually sent

Play message is sent way before the actual page shows, this is due to the fact that both are on two different protocols, we need to wait for the player page to actually come up first and then send the play request
Fixes issue with playback not working whenever first invoked

As discussed in chat this is a temporary stop gap until we improve things gui side, hardcoded sleeps are bad and we know it, but merging for now


Add header-based event differentiation

See X-Github-Event delivery header: https://docs.github.com/en/developers/webhooks-and-events/webhooks/webhook-events-and-payloads#delivery-headers

see https://github.com/silverton-io/buz/issues/467


Types have separate declarations of a private property '_client'

import NhostClient from @nhost/nextjs then creating instance with backend url , it is saying nhost issue in NhostNextProvider

could you share your package.json dependencies, and try to update to the latest npm versions?


Fix bug when branch is not associated with a PR.

farcy v0.1b :+1:

farcy v0.1b :+1:

farcy v0.1b :+1:

farcy v0.1b :+1:

farcy v0.1b :+1:

farcy v0.1b :+1:

farcy v0.1b :+1:

farcy v0.1b :+1:

farcy v0.1b :+1:

farcy v0.1b :+1:


implemented dotnet core 2.1 bindings

Looks great. I have a few questions/comments:
1- Is it possible to make a READMe.md for the binding? Something like this would do: https://github.com/Picovoice/Porcupine/tree/master/binding/python. I just want people to know what they need to install and how to run the unit test.
2- Is WAV functionality part of some other library? If yes, we need to include the appropriate license information. If not, it will be available under Apache 2 which is great.
3- I wonder if it is possible to use this in a Xamarin project. Any insight? That can open the functionality to app world as well. Just a question for my own knowledge.
Thanks again for your contribution :)

Sure I will add a README.md and look for the licensing (how to add it) for the WAV functionality (this was only added to use in the unit tests).
(I only added this because I didn't really
I think it works in an xamarin project (this is written for general csharp not only dotnet core) only I haven't tested for that.

The full source of the bindings are one csharp file, so it could be easy to just copy the code into an xamarin project to test it.

Looks great. Merging!


Unwavering Stance from Kaom's Roots

Under Other Defences, if I hover over Stun Avoidance Chance it reports 100% from Unwavering Stance and shows me an unselected node in the tree. My Unwavering Stance is from Kaom's Roots, not from the keystone. As a new player, this was somewhat confusing.

This is a fundamental limitation of the way in which keystones work, both in-game and in Path of Building.
When you allocate a keystone, or equip an item that grants the keystone, it doesn't actually give you the keystone's modifiers (e.g 100% stun avoidance) directly, but rather it just sets a flag that says "You have X Keystone"; then at a later point the keystone flags are checked and the appropriate modifiers granted to your character. This is necessary to prevent you from gaining the keystone modifiers multiple times if you have multiple sources for the keystone (say, taking Unwavering Stance and equipping Kaom's Roots).
One side effect of this in Path of Building is that when a keystone's modifiers are being added, they cannot have their source set to the source of the keystone flag, as the code only knows that the flag for that keystone has been set, but not where it was set from. So it defaults to the keystone node (as it has to set a source, even if it may not be the true source).
Fixing it would require me to rework the keystone system to allow the source of the keystone flag to be preserved, and given how minor this issue is, I really don't see it being worth the effort.


DoctrineExtensions 3.0?

Hi!
What are the plans for a 3.0 release? Will it be compatible with Doctrine MongoDB ODM 2.x?
I have been surfing around the project and it seems there are plans for it and work being done in master.
We are using the Tree and Sortable extensions and are looking to upgrade to ODM 2.x

Hey there,
Less than two months ago I did a PR against feature/mongodb-odm-2.0 #2096
The only thing missing detail to move to ODM 2.0 may be fixing the tests. We temporarily forked and merged to master to test compatibility and we have detected no errors so far.
As soon as there is a working version in master, we will test it with our platform. :)

Cheers @Alfro for your addition.
I have the ODM 2.0 branch passing all tests now. Hoping you can take a look and help confirm any potential issues or gotchas.
I'll try to document what was changed a bit further later this evening.

Notably, I think there's a weird in-between state of the original Mongo extension, and the new one with the BSON types. I know there are other deprecated classes being used still (e.g. MongoId). Some are likely not covered by tests, though.
I'm not sure if it's worth completely ripping the band aid off now and eliminating the usages of all of those, getting rid of the old Doctrine adapter package, etc. Any thoughts there would be great.

@AkenRoberts I've just tested one of my projects with dev-master 49c8315 and no problems detected so far. I'm using Translatable(ORM) and Loggable (ODM)
Only those minor changed needed:
---

diff --git a/config/packages/doctrine.yaml b/config/packages/doctrine.yaml
index cc04c61..e53c84a 100644
--- a/config/packages/doctrine.yaml
+++ b/config/packages/doctrine.yaml
@@ -39,7 +39,7 @@ doctrine:
                 alias: Gedmo
                 prefix: Gedmo\Translatable\Entity
                 # make sure vendor library location is correct
-                dir: "%kernel.project_dir%/vendor/gedmo/doctrine-extensions/lib/Gedmo/Translatable/Entity/MappedSuperclass"
+                dir: "%kernel.project_dir%/vendor/gedmo/doctrine-extensions/src/Translatable/Entity/MappedSuperclass"
         hydrators:
             UniqueColHydrator: \App\Hydrators\UniqueColHydrator
             UniqueGroupColHydrator: \App\Hydrators\UniqueGroupColHydrator
diff --git a/config/packages/doctrine_mongodb.yaml b/config/packages/doctrine_mongodb.yaml
index ed5d38e..e184bc5 100644
--- a/config/packages/doctrine_mongodb.yaml
+++ b/config/packages/doctrine_mongodb.yaml
@@ -22,4 +22,4 @@ doctrine_mongodb:
                     alias: GedmoDocument
                     prefix: Gedmo\Loggable\Document
                     # make sure vendor library location is correct
-                    dir: "%kernel.project_dir%/vendor/gedmo/doctrine-extensions/lib/Gedmo/Loggable/Document"
+                    dir: "%kernel.project_dir%/vendor/gedmo/doctrine-extensions/src/Loggable/Document"
--

Thanks for your time!

Hi @AkenRoberts!
Thanks for your hard work! We will be sure to test the 3.0 branch and let you know if we come across anything.
I think we can close this issue, since the original question has been answered and master seems to already have a working support for ODM 2.0 and a 3.0 version on its way eventually.

Thank you for testing and your feedback so far. Happy to hear more any time.


Change HillasReconstructor to take a list of HorizonCoordinates

It should take a dict of Skycoordinates with frame horizon.

This can be closed since in #946 I changed the API in order to pass a dict of Skycoords.


Hand Contact Metacarpal rendering

Summary
Adds metacarpals to the rendering update for hard contact hands for dealing with the first couple of frames being unstable from OXR.
Contributor Tasks

[x] Create or edit test cases here
[x] Ensure documentation requirements are met e.g., public API is commented.
[x] Consider any licensing/other legal implications for this MR e.g. notices required by any new libraries.

Test Cycle
Link to the test cycle here.
Reviewer Tasks

[x] Code reviewed.
[x] Non-code assets e.g. Unity assets/scenes reviewed.
[x] All tests must be ran and cover all scenarios (If not, add new tests to the cycle and run them).
[x] Documentation has been reviewed.
[x] Approve with a comment of any additional tests run or any observations.

Related JIRA Issues
Closes UNITY-1491

All good on my cycle


Color picker closing suddenly when clicking in another color input

Bug Description
If you click in a color input, it will open the color picker, then you change the value in the color picker opened and click in another color input, it will close the previous color picker and don't open a new one
Expected Behaviour
When the user selects a color input B while using a color picker X called by a previous color input A, the color picker X should close and color picker Y called by color input B selection should open.
Steps to Reproduce

Add a text element
Select Text Color Input
As soon as the Color Picker open, change the color and click in the Textbox Color Input
All color pickers will be closed suddenly

Screenshots

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria
QA Instructions

Potentially related to #1042

Fixed by #1187


Improve watchman docs

Only a few changes (the current text is good):

Replaced 'may need' with 'we recommend'
Updated synced 'missing watchman' message, to make this page show up in google results (https://github.com/chrmod/watch-detector/blob/master/lib/index.js#L256)

There are a few more things mentioned in the old docs, but I'm not sure if they're worth moving over, they seem like pretty auxiliary things. If included, it would be neat to fold them into a details/summary block (if the docs site support that).
Debugging & Advanced

Thank you! 🏆 for the first PR.
I don't think we have a summary block, but we could add them at the bottom for now.


correctly parse mappings for each type

tested on elasticsearch-1.4.2

This is probably breaking for an old ElasticSearch version, but hey, let's keep things updated.


Fix validation for recovery phrase with duplicate words

Bit of logic missing there.

Fixed for now so it doesn't break altogether. Still need to improve it so users can click the words independent of their position in the original array.


No data being received in custom route using receiver.router.post

I am using custom routes in bolt to try to receive some data from another app that sends a post request, then post that data to a channel.
The issue I am having is that when I log the request using receiver.router.post I dont get the data that I am passing in from the post request. Here is the method I am using:
receiver.router.post('/post', function (request, response) {
    console.log(request)
}

I am using this simple axios post request in another node application to send the data:
const axios = require('axios')

axios.post(`http://21f935bd559b.ngrok.io/post`, {
    "assetData": "foo",
}).catch(err => {
    console.log(err);
})

And here is the output I get when I console.log(request) in the receiver.router.post method:  https://pastebin.com/5jywyXkA. As you can see the "assetData": "foo" is nowhere to be seen. How can I receive data in this receiver.router.post method?
...
Here is another example of a similar issue that was never solved:
I was able to write post request, But I am not able to read the request data. Generally we import body-parser package from npm and decode data from request. So to use bodyParser I tried using on expressReceiver then it says receiver.use() is not a defined function.
If not possible to use body-parser suggest another alternative!
How to parse request data in expressreceiver?
import bodyParser from "body-parser";

const receiver = new ExpressReceiver({ signingSecret: process.env.SLACK_SIGNING_SECRET });
const app = new App({
  token: process.env.SLACK_BOT_TOKEN,
  receiver
});

receiver.use(bodyParser.urlencoded({ extended: false })); //error
receiver.use(bodyParser.json());

receiver.router.post('/secret', (req, res) => {
  // You're working with an express req and res now.
  console.log(req.body);       //error
  res.send('yay!');
});

Originally posted by @Mogadampalli-Jayanth in https://github.com/slackapi/bolt-js/issues/702#issuecomment-738765449

Solved by adding
const express = require('express')
receiver.router.use(express.json());

before the receiver.router.post request


Update financial-services-secure-collaboration.md

Added more info link about Insider management

@JohanFreelancer9 Please copy review

Issue#https://github.com/MicrosoftDocs/microsoft-365-docs/issues/3477

@BrendaCarter Please merge this PR. Thanks


vm: enable autoUpgradeMinorVersion by default

/CC: @burtbiel, @tjprescott , @derekbekoe
This deals with #716

:shipit:


Fix shadowed branch coverage PC variable

The refactor of coverage code (#8025) is casting a shadow over pc variable for the first branch and results in invalid branch coverage reports.
Motivation

Fix branch coverage reports.
Solution

Use a different name for the jump pc variable to prevent shadowing it for use in the first branch anchor.

@DaniPopes Should we add tests for this? I didn't find any tests related to anchors.

Don't know much about this code so can't say lol, thanks for catching this


No artifacts generated in buildkite job

Example : https://buildkite.com/clima/climaatmos-longruns/builds/1358.
It's unclear if this is true across multiple job-ids.
There are two issues here:
(1) No artifacts generated.
(2) Plot instruction not found - fixed in #2512 (even with the fixed id it's not helpful since the simdir is empty).
The GPU run might also be interesting : https://buildkite.com/clima/climaatmos-gpulongruns/builds/22.
(Will populate with more details as the issue becomes clearer)

#2512 should fix both of these. The files are there: /central/scratch/esm/slurm-buildkite/climaatmos-longruns/1358/climaatmos-longruns/longrun_aquaplanet_rhoe_equil_gray_55km_nz63_0M. It can't be uploaded just because the artifact folder is wrong.


No disable

disabled doesn't work

You need access the input-field by ref. So disabled the input.

If you are using Typescript you can use following line to disable it, make sure to add a reference to the typehead component, in this case reference is 'refmodeltypeahead'
(this.$refs['refmodeltypeahead'] as any).$refs.input.disabled = true;


Use pull_request_target unless workflows are changed

What
:warning:  DON'T MERGE THIS.  the solution I'm trying to implement is probably a bad idea. :warning:

We run a python script that is authenticated with our gcloud credentials.  Even if the workflows are running from main the script itself would run from their repo.  That's a short step to an innocuous initial PR being approved followed by a malicious commit that does something bad to our gcloud instance.

Pull requests from external contributors will currently fail to produce build results because they can't access secrets. This is a reasonable precaution for github in general, but only a risk if the workflows themselves are being modified.
To this end, this is why: pull_request_target exists.
The downside of pull_request_target, however, is that it makes it hard to create a pull request that modifies workflows and test it locally.
This logic is a bit complicated, but we now potentially trigger the workflow on BOTH pull_request and pull_request_target.  If no workflows are changed.
Checklist

[ ] I have read and agree to Contributor Guide and the Code of Conduct
[ ] I've included a screenshot or gif (if applicable)

PR Build Summary: https://build.rerun.io/pr/1991

This wouldn't have worked anyways because pull_request_target would also do the checkout in the target repo and not end up using the submitted code.


Work without internet?

Hello.
Please tell me gardash, does it work without internet?

yes gardash это работает без интернета
internet olmadan çalışıyor
its working without internet))
18 Mar 2022 Cum 07:24 tarihinde yashma052 @.***> şunu
yazdı:

Hello.
Please tell me gardash, does it work without internet?
—
Reply to this email directly, view it on GitHub
https://github.com/mustafasayilan/cryptobrute/issues/5, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AEHDU6UGOQOB7FPPYOO7QFDVARRVPANCNFSM5RBR3X7A
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

EyvAllah abime 💪🏻