数据导入工具导入数据，报错：AttributeError: 'NoneType' object has no attribute 'flush'

2023-04-13 17:48:53,263 [INFO] - 搜索通达信服务器 [UsePytdxImportToH5Thread::init_task]
2023-04-13 17:48:53,268 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,268 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,269 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,269 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,276 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,277 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,281 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,284 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:53,284 [DEBUG] - connecting to server : <IP_ADDRESS> on port :80 [PYTDX::connect]
2023-04-13 17:48:53,295 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,298 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:53,301 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:53,304 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:53,306 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,309 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:53,309 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,310 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,316 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,316 [DEBUG] - last ack time update to<PHONE_NUMBER>.3167315 [PYTDX::wrapper]
2023-04-13 17:48:53,316 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:53,322 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,322 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,326 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,330 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:53,332 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:53,334 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,334 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,336 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,336 [DEBUG] - last ack time update to<PHONE_NUMBER>.336705 [PYTDX::wrapper]
2023-04-13 17:48:53,336 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:53,337 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,338 [DEBUG] - last ack time update to<PHONE_NUMBER>.338695 [PYTDX::wrapper]
2023-04-13 17:48:53,338 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:53,349 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,354 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:53,355 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,356 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:53,356 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,356 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,358 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:53,358 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:53,358 [DEBUG] - connecting to server : <IP_ADDRESS> on port :80 [PYTDX::connect]
2023-04-13 17:48:53,370 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,384 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:53,397 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,398 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,399 [DEBUG] - last ack time update to<PHONE_NUMBER>.3980672 [PYTDX::wrapper]
2023-04-13 17:48:53,399 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:53,416 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,428 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,431 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:53,431 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:53,434 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,437 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,437 [DEBUG] - last ack time update to<PHONE_NUMBER>.4376695 [PYTDX::wrapper]
2023-04-13 17:48:53,437 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:53,447 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,457 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:53,477 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,478 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,481 [DEBUG] - last ack time update to<PHONE_NUMBER>.4817374 [PYTDX::wrapper]
2023-04-13 17:48:53,481 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:53,481 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,483 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:53,483 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:53,483 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,494 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,495 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:53,511 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,512 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:53,515 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,516 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:53,516 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,516 [DEBUG] - last ack time update to<PHONE_NUMBER>.5167673 [PYTDX::wrapper]
2023-04-13 17:48:53,518 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,518 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:53,526 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:53,537 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,539 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,539 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,541 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:53,546 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:53,547 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,554 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,554 [DEBUG] - last ack time update to<PHONE_NUMBER>.554779 [PYTDX::wrapper]
2023-04-13 17:48:53,554 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:53,559 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,565 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:53,571 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,571 [DEBUG] - last ack time update to<PHONE_NUMBER>.5711818 [PYTDX::wrapper]
2023-04-13 17:48:53,571 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:53,577 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,577 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,579 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:53,582 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,583 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:53,584 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:53,584 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,589 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:53,590 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,590 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,601 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,602 [DEBUG] - last ack time update to<PHONE_NUMBER>.602785 [PYTDX::wrapper]
2023-04-13 17:48:53,603 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:53,609 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:53,613 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,615 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:53,618 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:53,618 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:53,622 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,636 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,650 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,651 [DEBUG] - last ack time update to<PHONE_NUMBER>.6516669 [PYTDX::wrapper]
2023-04-13 17:48:53,651 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:53,664 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:53,667 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:53,668 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:53,668 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:54,270 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:54,270 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:54,278 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:54,278 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:54,279 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:54,279 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:54,338 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:54,340 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:54,359 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:54,359 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:54,373 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:54,382 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,392 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,404 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,407 [DEBUG] - last ack time update to<PHONE_NUMBER>.4072502 [PYTDX::wrapper]
2023-04-13 17:48:54,407 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:54,418 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,420 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:54,424 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:54,424 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:54,440 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:54,451 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,461 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,470 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,472 [DEBUG] - last ack time update to<PHONE_NUMBER>.4721704 [PYTDX::wrapper]
2023-04-13 17:48:54,472 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:54,482 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,484 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:54,487 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:54,487 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:54,504 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:54,512 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,521 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,530 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,532 [DEBUG] - last ack time update to<PHONE_NUMBER>.532757 [PYTDX::wrapper]
2023-04-13 17:48:54,533 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:54,543 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,548 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:54,548 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:54,548 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:54,588 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:54,589 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:54,590 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:54,619 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:54,620 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:54,626 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,662 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,670 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:54,670 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:54,697 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,699 [DEBUG] - last ack time update to<PHONE_NUMBER>.6991112 [PYTDX::wrapper]
2023-04-13 17:48:54,699 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:54,734 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:54,738 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:54,738 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:54,740 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:55,279 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:55,279 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:55,280 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:55,283 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:55,283 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:55,283 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:55,341 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:55,344 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:55,590 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:55,592 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:55,621 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:55,622 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:55,670 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:55,671 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:55,741 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:55,744 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:56,296 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:56,296 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:56,297 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:56,298 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:56,305 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:56,311 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:56,344 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:56,344 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:56,612 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:56,613 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:56,624 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:56,626 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:56,672 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:56,673 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:56,746 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:56,747 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:57,305 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:57,308 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:57,311 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:57,311 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:57,317 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:57,323 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:57,345 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:57,345 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:57,386 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:57,421 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:57,457 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:57,493 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:48:57,494 [DEBUG] - last ack time update to<PHONE_NUMBER>.4947624 [PYTDX::wrapper]
2023-04-13 17:48:57,494 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:57,530 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:57,532 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:57,535 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:57,535 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:57,580 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:57,614 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:57,615 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:57,623 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:57,627 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:57,627 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:57,667 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:57,674 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:57,675 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:57,706 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:48:57,706 [DEBUG] - last ack time update to<PHONE_NUMBER>.706709 [PYTDX::wrapper]
2023-04-13 17:48:57,706 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:57,747 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:57,751 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:57,751 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:57,753 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:57,753 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:57,754 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:58,309 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:58,318 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:58,318 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:58,319 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:58,334 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:58,344 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:58,617 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:58,621 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:58,632 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:58,633 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:58,676 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:58,679 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:58,754 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:58,754 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:58,759 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:58,760 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:58,793 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:58,802 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:58,831 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:58,839 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:58,868 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:58,875 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:58,905 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:48:58,905 [DEBUG] - last ack time update to<PHONE_NUMBER>.9050908 [PYTDX::wrapper]
2023-04-13 17:48:58,905 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:58,913 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:48:58,913 [DEBUG] - last ack time update to<PHONE_NUMBER>.9130847 [PYTDX::wrapper]
2023-04-13 17:48:58,913 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:58,942 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:58,945 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:58,947 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:58,947 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:58,949 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:58,951 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:58,956 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:58,957 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:59,319 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:59,324 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:59,324 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:59,325 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:59,350 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:59,351 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:59,622 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:59,626 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:59,634 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:59,636 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:59,677 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:59,681 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:59,683 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:59,713 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:59,723 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:59,748 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:59,757 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:59,783 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:48:59,783 [DEBUG] - last ack time update to<PHONE_NUMBER>.7838976 [PYTDX::wrapper]
2023-04-13 17:48:59,783 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:59,793 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:59,820 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:59,823 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:59,823 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:59,827 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:59,827 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:48:59,827 [DEBUG] - last ack time update to<PHONE_NUMBER>.8279004 [PYTDX::wrapper]
2023-04-13 17:48:59,827 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:59,857 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:59,863 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:59,866 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:48:59,866 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:48:59,868 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:59,894 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:59,907 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:59,929 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:59,941 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:59,949 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:59,951 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:59,958 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:48:59,958 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:48:59,963 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:48:59,963 [DEBUG] - last ack time update to<PHONE_NUMBER>.9632752 [PYTDX::wrapper]
2023-04-13 17:48:59,964 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:48:59,974 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:48:59,989 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:48:59,997 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:00,000 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,002 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:00,002 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:00,006 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,008 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,008 [DEBUG] - last ack time update to<PHONE_NUMBER>.0083096 [PYTDX::wrapper]
2023-04-13 17:49:00,008 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:00,022 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,035 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,041 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,044 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:00,044 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:00,044 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:00,044 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,056 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,069 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,077 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,077 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:00,089 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,089 [DEBUG] - last ack time update to<PHONE_NUMBER>.0892656 [PYTDX::wrapper]
2023-04-13 17:49:00,089 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:00,104 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,104 [DEBUG] - last ack time update to<PHONE_NUMBER>.1041574 [PYTDX::wrapper]
2023-04-13 17:49:00,104 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:00,110 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,114 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,122 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,124 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:00,127 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:00,127 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,139 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,143 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:00,144 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,144 [DEBUG] - last ack time update to<PHONE_NUMBER>.1441436 [PYTDX::wrapper]
2023-04-13 17:49:00,144 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:00,144 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:00,149 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,151 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,158 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:00,181 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,184 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:00,184 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:00,185 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,189 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,189 [DEBUG] - last ack time update to<PHONE_NUMBER>.1891181 [PYTDX::wrapper]
2023-04-13 17:49:00,189 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:00,195 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,223 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,226 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:00,226 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:00,229 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,229 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,263 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,263 [DEBUG] - last ack time update to<PHONE_NUMBER>.2638316 [PYTDX::wrapper]
2023-04-13 17:49:00,267 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:00,303 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,306 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:00,306 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:00,309 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,326 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:49:00,326 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:49:00,327 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,332 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,353 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:49:00,355 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,389 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:00,428 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,467 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,508 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,508 [DEBUG] - last ack time update to<PHONE_NUMBER>.5084517 [PYTDX::wrapper]
2023-04-13 17:49:00,508 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:00,547 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,549 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:00,552 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:00,552 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,586 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:00,613 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,626 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:49:00,629 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,640 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,663 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:00,668 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,668 [DEBUG] - last ack time update to<PHONE_NUMBER>.6682587 [PYTDX::wrapper]
2023-04-13 17:49:00,671 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:00,696 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,699 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,701 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:00,704 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:00,704 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,727 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,738 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:00,754 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,755 [DEBUG] - last ack time update to<PHONE_NUMBER>.7558627 [PYTDX::wrapper]
2023-04-13 17:49:00,755 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:00,764 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,784 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,787 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:00,790 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:00,791 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,791 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,816 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,816 [DEBUG] - last ack time update to<PHONE_NUMBER>.8169992 [PYTDX::wrapper]
2023-04-13 17:49:00,818 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:00,828 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:00,845 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,846 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:00,850 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:00,850 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:00,870 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,913 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,922 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:00,956 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:00,956 [DEBUG] - last ack time update to<PHONE_NUMBER>.9563558 [PYTDX::wrapper]
2023-04-13 17:49:00,958 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:00,998 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,001 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,004 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:01,007 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:01,008 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:01,076 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,153 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:49:01,160 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:01,160 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,160 [DEBUG] - last ack time update to<PHONE_NUMBER>.1607068 [PYTDX::wrapper]
2023-04-13 17:49:01,160 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:01,190 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:49:01,191 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:01,230 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:49:01,232 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:01,233 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:01,238 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,240 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:01,243 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:01,244 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:01,268 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,270 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:01,303 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,305 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,310 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:49:01,310 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:01,333 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:49:01,335 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:49:01,335 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:01,335 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:01,338 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,339 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,340 [DEBUG] - last ack time update to<PHONE_NUMBER>.3403294 [PYTDX::wrapper]
2023-04-13 17:49:01,340 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:01,371 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,371 [DEBUG] - last ack time update to<PHONE_NUMBER>.3713808 [PYTDX::wrapper]
2023-04-13 17:49:01,373 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:01,376 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,377 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:01,379 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:01,380 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:01,383 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:01,404 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:01,407 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,409 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:01,409 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:01,413 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:01,414 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,414 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:01,422 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,425 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:01,438 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,441 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,448 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,456 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,458 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,458 [DEBUG] - last ack time update to<PHONE_NUMBER>.4583728 [PYTDX::wrapper]
2023-04-13 17:49:01,458 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:01,470 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,470 [DEBUG] - last ack time update to<PHONE_NUMBER>.4707675 [PYTDX::wrapper]
2023-04-13 17:49:01,470 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:01,475 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,476 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:01,479 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:01,479 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:01,482 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,482 [DEBUG] - last ack time update to<PHONE_NUMBER>.4824197 [PYTDX::wrapper]
2023-04-13 17:49:01,482 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:01,490 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,490 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,492 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:01,492 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:01,492 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:01,500 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:01,508 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,517 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,520 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:01,521 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:01,521 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:01,525 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,535 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,543 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,543 [DEBUG] - last ack time update to<PHONE_NUMBER>.543136 [PYTDX::wrapper]
2023-04-13 17:49:01,544 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:01,551 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,564 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,567 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:01,567 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,568 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,568 [DEBUG] - last ack time update to<PHONE_NUMBER>.568641 [PYTDX::wrapper]
2023-04-13 17:49:01,568 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:01,568 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:01,583 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,586 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:01,587 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:01,643 [DEBUG] - 不需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,643 [DEBUG] - last ack time update to<PHONE_NUMBER>.6432443 [PYTDX::wrapper]
2023-04-13 17:49:01,647 [DEBUG] - sending thread lock api call [PYTDX::call_api]
2023-04-13 17:49:01,723 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:01,726 [DEBUG] - disconnecting [PYTDX::disconnect]
2023-04-13 17:49:01,727 [DEBUG] - disconnected [PYTDX::disconnect]
2023-04-13 17:49:02,008 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:49:02,162 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:49:02,244 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:49:02,312 [DEBUG] - connection expired [PYTDX::connect]
2023-04-13 17:49:02,314 [INFO] - 导入股票代码表 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:02,324 [DEBUG] - connecting to server : <IP_ADDRESS> on port :7709 [PYTDX::connect]
2023-04-13 17:49:02,339 [DEBUG] - connected! [PYTDX::connect]
2023-04-13 17:49:02,348 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:02,358 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:02,367 [DEBUG] - 需要解压 [PYTDX::_call_api]
2023-04-13 17:49:02,367 [INFO] - 导入交易所休假日历 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:02,373 [DEBUG] - Starting new HTTPS connection (1): www.tdx.com.cn:443 [urllib3.connectionpool::_new_conn]
2023-04-13 17:49:02,373 [DEBUG] - Starting new HTTPS connection (1): www.tdx.com.cn:443 [urllib3.connectionpool::_new_conn]
2023-04-13 17:49:02,886 [DEBUG] - https://www.tdx.com.cn:443 "GET /url/holiday/ HTTP/1.1" 200 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:02,886 [DEBUG] - https://www.tdx.com.cn:443 "GET /url/holiday/ HTTP/1.1" 200 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:03,035 [DEBUG] - Starting new HTTP connection (1): vip.stock.finance.sina.com.cn:80 [urllib3.connectionpool::_new_conn]
2023-04-13 17:49:03,035 [DEBUG] - Starting new HTTP connection (1): vip.stock.finance.sina.com.cn:80 [urllib3.connectionpool::_new_conn]
2023-04-13 17:49:03,908 [DEBUG] - http://vip.stock.finance.sina.com.cn:80 "GET /quotes_service/api/json_v2.php/Market_Center.getHQNodeStockCountSimple?node=hs_s HTTP/1.1" 200 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:03,908 [DEBUG] - http://vip.stock.finance.sina.com.cn:80 "GET /quotes_service/api/json_v2.php/Market_Center.getHQNodeStockCountSimple?node=hs_s HTTP/1.1" 200 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:03,914 [ERROR] - AttributeError: 'NoneType' object has no attribute 'flush' [hikyuu.data.common.get_index_code_name_list] [hikyuu::wrappedFunc]
Traceback (most recent call last):
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\hikyuu\util\check.py", line 111, in wrappedFunc val = func(*args, **kargs)
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\hikyuu\data\common.py", line 131, in get_index_code_name_list df = ak.stock_zh_index_spot()
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\akshare\index\index_stock_zh.py", line 67, in stock_zh_index_spot for page in tqdm(range(1, page_count + 1), leave=False):
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\tqdm\std.py", line 1107, in init self.sp = self.status_printer(self.fp)
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\tqdm\std.py", line 339, in status_printer sys.stderr.flush()
AttributeError: 'NoneType' object has no attribute 'flush'
2023-04-13 17:49:03,916 [INFO] - 指数数量: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:03,949 [DEBUG] - Starting new HTTP connection (1): query.sse.com.cn:80 [urllib3.connectionpool::_new_conn]
2023-04-13 17:49:03,949 [DEBUG] - Starting new HTTP connection (1): query.sse.com.cn:80 [urllib3.connectionpool::new_conn]
2023-04-13 17:49:04,487 [DEBUG] - http://query.sse.com.cn:80 "GET /sseQuery/commonQuery.do?STOCK_TYPE=1&REG_PROVINCE=&CSRC_CODE=&STOCK_CODE=&sqlId=COMMON_SSE_CP_GPJCTPZ_GPLB_GP_L&COMPANY_STATUS=2%2C4%2C5%2C7%2C8&type=inParams&isPagination=true&pageHelp.cacheSize=1&pageHelp.beginPage=1&pageHelp.pageSize=10000&pageHelp.pageNo=1&pageHelp.endPage=1&=1653291270045 HTTP/1.1" 302 None [urllib3.connectionpool::make_request]
2023-04-13 17:49:04,487 [DEBUG] - http://query.sse.com.cn:80 "GET /sseQuery/commonQuery.do?STOCK_TYPE=1&REG_PROVINCE=&CSRC_CODE=&STOCK_CODE=&sqlId=COMMON_SSE_CP_GPJCTPZ_GPLB_GP_L&COMPANY_STATUS=2%2C4%2C5%2C7%2C8&type=inParams&isPagination=true&pageHelp.cacheSize=1&pageHelp.beginPage=1&pageHelp.pageSize=10000&pageHelp.pageNo=1&pageHelp.endPage=1&=1653291270045 HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:04,498 [DEBUG] - Starting new HTTP connection (1): www.sse.com.cn:80 [urllib3.connectionpool::_new_conn]
2023-04-13 17:49:04,498 [DEBUG] - Starting new HTTP connection (1): www.sse.com.cn:80 [urllib3.connectionpool::_new_conn]
2023-04-13 17:49:04,983 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:04,983 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,009 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,009 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,034 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,034 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,051 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,051 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,066 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,066 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,079 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,079 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,094 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,094 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,109 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,109 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,123 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,123 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,137 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,137 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,151 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,151 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,168 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,168 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,183 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,183 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,197 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,197 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,213 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,213 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,229 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,229 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,243 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,243 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,257 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,257 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,274 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,274 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,286 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,286 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,302 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,302 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,317 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,317 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,336 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,336 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,350 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,350 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,365 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,365 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,379 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,379 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,395 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,395 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,409 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,409 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,422 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,422 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,436 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,436 [DEBUG] - http://www.sse.com.cn:80 "GET /err.html HTTP/1.1" 302 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:05,441 [ERROR] - TooManyRedirects: Exceeded 30 redirects. [hikyuu.data.common.get_stk_code_name_list] [hikyuu::wrappedFunc]
Traceback (most recent call last):
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\hikyuu\util\check.py", line 111, in wrappedFunc val = func(*args, **kargs)
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\hikyuu\data\common.py", line 109, in get_stk_code_name_list tmp_df = ak.stock_info_sh_name_code(ind)
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\akshare\stock\stock_info.py", line 151, in stock_info_sh_name_code r = requests.get(url, params=params, headers=headers)
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\requests\api.py", line 75, in get return request('get', url, params=params, **kwargs)
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\requests\api.py", line 61, in request return session.request(method=method, url=url, **kwargs)
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\requests\sessions.py", line 542, in request resp = self.send(prep, **send_kwargs)
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\requests\sessions.py", line 677, in send history = [resp for resp in gen]
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\requests\sessions.py", line 677, in history = [resp for resp in gen]
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\requests\sessions.py", line 166, in resolve_redirects raise TooManyRedirects('Exceeded {} redirects.'.format(self.max_redirects), response=resp)
requests.exceptions.TooManyRedirects: Exceeded 30 redirects.
2023-04-13 17:49:05,445 [ERROR] - 获取 SH 股票代码表失败 [import_stock_name] (C:\Users\zhimin.li\Anaconda3\lib\site-packages\hikyuu\data\pytdx_to_h5.py:107) [hikyuu::hku_error]
2023-04-13 17:49:05,479 [DEBUG] - Starting new HTTP connection (1): www.szse.cn:80 [urllib3.connectionpool::_new_conn]
2023-04-13 17:49:05,479 [DEBUG] - Starting new HTTP connection (1): www.szse.cn:80 [urllib3.connectionpool::_new_conn]
2023-04-13 17:49:06,947 [DEBUG] - http://www.szse.cn:80 "GET /api/report/ShowReport?SHOWTYPE=xlsx&CATALOGID=1110&TABKEY=tab1&random=0.6935816432433362 HTTP/1.1" 200 549035 [urllib3.connectionpool::_make_request]
2023-04-13 17:49:06,947 [DEBUG] - http://www.szse.cn:80 "GET /api/report/ShowReport?SHOWTYPE=xlsx&CATALOGID=1110&TABKEY=tab1&random=0.6935816432433362 HTTP/1.1" 200 549035 [urllib3.connectionpool::_make_request]
2023-04-13 17:49:08,496 [DEBUG] - Starting new HTTP connection (1): www.szse.cn:80 [urllib3.connectionpool::_new_conn]
2023-04-13 17:49:08,496 [DEBUG] - Starting new HTTP connection (1): www.szse.cn:80 [urllib3.connectionpool::_new_conn]
2023-04-13 17:49:09,121 [DEBUG] - http://www.szse.cn:80 "GET /api/report/ShowReport?SHOWTYPE=xlsx&CATALOGID=1110&TABKEY=tab2&random=0.6935816432433362 HTTP/1.1" 200 12031 [urllib3.connectionpool::_make_request]
2023-04-13 17:49:09,121 [DEBUG] - http://www.szse.cn:80 "GET /api/report/ShowReport?SHOWTYPE=xlsx&CATALOGID=1110&TABKEY=tab2&random=0.6935816432433362 HTTP/1.1" 200 12031 [urllib3.connectionpool::_make_request]
2023-04-13 17:49:09,161 [INFO] - 获取深圳证券交易所股票数量: 2807 [get_stk_code_name_list] (C:\Users\zhimin.li\Anaconda3\lib\site-packages\hikyuu\data\common.py:101) [hikyuu::hku_info]
2023-04-13 17:49:09,184 [DEBUG] - Starting new HTTPS connection (1): www.bse.cn:443 [urllib3.connectionpool::_new_conn]
2023-04-13 17:49:09,184 [DEBUG] - Starting new HTTPS connection (1): www.bse.cn:443 [urllib3.connectionpool::_new_conn]
2023-04-13 17:49:10,784 [DEBUG] - https://www.bse.cn:443 "POST /nqxxController/nqxxCnzq.do HTTP/1.1" 200 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:10,784 [DEBUG] - https://www.bse.cn:443 "POST /nqxxController/nqxxCnzq.do HTTP/1.1" 200 None [urllib3.connectionpool::_make_request]
2023-04-13 17:49:10,803 [ERROR] - AttributeError: 'NoneType' object has no attribute 'flush' [hikyuu.data.common.get_stk_code_name_list] [hikyuu::wrappedFunc]
Traceback (most recent call last):
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\hikyuu\util\check.py", line 111, in wrappedFunc val = func(*args, **kargs)
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\hikyuu\data\common.py", line 117, in get_stk_code_name_list df = ak.stock_info_bj_name_code()
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\akshare\stock\stock_info.py", line 195, in stock_info_bj_name_code for page in tqdm(range(total_page), leave=False):
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\tqdm\std.py", line 1107, in init self.sp = self.status_printer(self.fp)
File "C:\Users\zhimin.li\Anaconda3\lib\site-packages\tqdm\std.py", line 339, in status_printer sys.stderr.flush()
AttributeError: 'NoneType' object has no attribute 'flush'
2023-04-13 17:49:10,813 [ERROR] - 获取 BJ 股票代码表失败 [import_stock_name] (C:\Users\zhimin.li\Anaconda3\lib\site-packages\hikyuu\data\pytdx_to_h5.py:107) [hikyuu::hku_error]
2023-04-13 17:49:35,407 [INFO] - task (ImportWeightToSqliteTask) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,407 [INFO] - task (ImportHistoryFinanceTask) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxTransToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxTransToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxTransToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxTimeToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxTimeToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxTimeToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - task (ImportPytdxToH5) status: no run! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,409 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [INFO] - Process exit code: 0 [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,410 [ERROR] - All process is finished, but some tasks are running! [UsePytdxImportToH5Thread::_run]
2023-04-13 17:49:35,425 [INFO] - 导入完毕 [UsePytdxImportToH5Thread::run]

接上截图：

后续执行
pip  uninstall pytdx 卸载了pytdx，
从新安装 pip  install pytdx
以及更新
pip install --upgrade akshare
也没有解决。

这是akshare的报错，还是升级akshare，现在akshare至少是1.19.48以上了


Bug Report - Full Screen bug in extended display

Environment
Windows build number: Microsoft Windows [Version 10.0.18922.1000]
Windows Terminal version: 0.2.1715.0

Description
When I use extended secondary display, and make terminal fullscreen (press rectangular button from top right side), terminal overflowed from left side.
Expected behavior
Terminal should fit overall display

Actual behavior
Terminal overflows and leftmost characters not showing.

#1055


Related pages links for docs per suggestion in PR#3903

Signed-off-by: Victoria Bialas<EMAIL_ADDRESS>Proposed changes

Added some cross-references to related Compose docs per most recent customer comments from @amelvill in PR #3903 on restart options (thought this might help)

Related issues (optional)

PR #3903

cc: @joaofnfernandes @shin-

Deploy preview for docsdocker ready!
Built with commit 8e9e0813ba2484ad443bd7e0caf5fe8491272fb4
https://deploy-preview-7875--docsdocker.netlify.com

@londoncalling 👋
I'd suggest introducing this paragraph with something like "if you're looking to configure a service's restart policy, please refer to [...]" instead, so people know what they're being referred to before clicking ; especially because the command and the policy are separate concepts that don't interact with one another.

Hi Joffrey ,
That makes sense. I’ll make that change. I also think there are a few more
pages where I could add a similar x-ref. I’ll find those too.
Vicky
On Tue, Dec 18, 2018 at 1:34 AM Joffrey F<EMAIL_ADDRESS>wrote:

@londoncalling https://github.com/londoncalling 👋
I'd suggest introducing this paragraph with something like "if you're
looking to configure a service's restart policy, please refer to [...]"
instead, so people know what they're being referred to before clicking ;
especially because the command and the policy are separate concepts that
don't interact with one another.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docker/docker.github.io/pull/7875#issuecomment-448156265,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALHuA3ouF_Mi1WsfDGpfQ5xeIIx5nWnUks5u6La2gaJpZM4ZXJ7l
.

@shin- sorry this took so long .. let me know what you think. Happy Holidays, hope you are well 🎁🎄

Thanks, @londoncalling and @shin- . Happy new year to both of you!


Use a true singleton

Precursor to SSR #53
the package now exports a cashay singleton instead of a Cashay class that you have to turn into a singleton. This means no more dirty exporting from where you create it.

Coverage remained the same at 86.772% when pulling 5494f171e0feaede6a0a1b092e783fece7f790b6 on singleton into 941db5ca591a9d3552341d130985f48e496c3ae1 on master.


Ctrl+f overwrites X11's Primary selection buffer.

VS Code Version:

Version: 1.58.2
Commit: c3f126316369cd610563c75b1b1725e0679adfb3
Date: 2021-07-14T22:30:16.440Z
Electron: 12.0.13
Chrome: 89.0.4389.128
Node.js: 14.16.0
V8: <IP_ADDRESS>-electron.0
OS: Linux x64 5.4.0-80-generic snap

OS Version: Ubuntu 20.04.2 LTS + XFce

When first exposed to X11, most people will figure out that you can paste your last selection with mouse's middle click. Many will hate the feature and disable it (so much that Ubuntu 20.04 has disabled it by default), others will learn to live with it, but a few will learn to use and depend on it. I belong in this last group, and I am used to have 2 copy paste buffers: one long term (the normal ctrl+c → ctrl+v CLIPBOARD buffer), and one short term (the select → middle click PRIMARY buffer). With a few exceptions, it works transparently with most applications, but in vscode, the Find (ctrl+f) functionality disrupts the primary buffer by replacing its contents to whatever ends up being seeded in the find box.

Does this issue occur when all extensions are disabled?: Yes

Steps to Reproduce:

Make sure you have middle click paste enabled (the default in most distros I have used in the past 20 years, but I am not so sure about recent ones). This is how to do it in Ubuntu's Gnome.
Select any text, inside or outside vscode;
Middle-click several times to confirm you can paste from the PRIMARY buffer, inside or outside the vscode
Press ctrl+f in another vscode editor tab, where the cursor is over a different string (the intention is that you can middle-click and find the string you have previously selected);
Middle-click in the editor, to surprisingly find that the contents of your PRIMARY buffer has been replaced by the pre-filled contents of the Find box.

I think this is a bug because the pre-filling of the find box is certainly not intended to replace the user's copied content (and it should not).
BTW, I also think that the find box should be pre-filled with the contents of the PRIMARY buffer, but maybe that should be a feature request ticket.
This is somewhat related to Issue #20768.
References os this PRIMARY buffer thing:

https://unix.stackexchange.com/questions/139191/whats-the-difference-between-primary-selection-and-clipboard-buffer
https://tronche.com/gui/x/icccm/sec-2.html#s-2.6.1

@rebornix I think we have some find options that would prevent the current word from being selected in the editor when pressing ctrl+f?

This is also very annoying when I open the Search tab.


Add microshift.io to website url for this repo

Add microshift.io to website url for this repo

/assign @cooktheryan


Add A image lightbox in imageColumn

[x] Changes have been thoroughly tested to not break existing functionality.
[x] New functionality has been documented or existing documentation has been updated to reflect changes.
[x] Visual changes are explained in the PR description using a screenshot/recording of before and after.

In this pull request,
Our goal is to introduce a basic image lightbox functionality without incorporating any extra libraries.
For a more sophisticated image lightbox effect or if additional libraries are desired, the use of an additional filament plugin is recommended.
Upon clicking an image within the imageColumn, a lightbox popup will be displayed.

Honestly, I think this would be better suited as a plugin.
Also, you could simply attach an action to the column already and have it open a modal that shows the image.
Going to close this, but will notify @danharrin for a final decision.

could simply attach an action to the column already and have it open a modal

would like to see this lightbox implementation in the core, a modal with static content (eg: an image or announcement) without a server request

ya, my target is simple lightbox in image. for other attachments, eg pdf , i think need additional plugin.

@wychoong
Since it will not merge into core function, i make a package to do this now.
Keep base on ImageColumn and TextColumn.
Support Image , PDF, Word, PPTX too.
Enjoy
https://github.com/solutionforest/Filament-SimpleLightBox


Add a mini FAQ to gift cards admin

Add a mini FAQ at the bottom or as a sidebar to make it clear that you will only be charged when gift cards are used. See the FAQ on https://opencollective.com/gift-of-giving

@Betree Where should it be added ? Can you point the location

It's hard to see exactly where this should go, we don't have  proper design for it. I'd be in favor of adding a simple link to the docs so that we don't duplicate the FAQ's content: https://docs.opencollective.com/help/backers-and-sponsors/gift-cards#faq
So for clearer specs:

On https://staging.opencollective.com/{ORGANIZATION_SLUG}/edit/gift-cards-create
Add a link to the position shown on the screenshot bellow with the following message:

Learn more about Gift Cards

File is https://github.com/opencollective/opencollective-frontend/blob/820c3dbf5e3eb898b612a26fa8eb7453f6133964/components/EditCollectiveForm.js#L835, though that'd be cleaner to move all that to CreateVirtualCardsForm (not requested for this issue).


[flutter_tools] remove automatic multiroot scheme

Description
A multi-root scheme confuses IDEs and breakpoint setting, see https://github.com/flutter/flutter/issues/50198
The multi-root scheme is only required if the final generated dart source from a builder is left in the .dart_tool directory. If the builder uses the SharedPartBuilder or build_to: source, then no multiroot scheme is required.
Since the default behavior of flutter run is to not use a multiroot scheme, and because users not using the builders key are otherwise able to run their applications, I do not believe it had a lot of value. Also, it seems unlikely to be a breaking change

This is currently tested via the codegen integration test


Wrong return type of decimalPlaces()

According to the doc:

If dp is omitted, or is null or undefined, the return value is the number of decimal places of the value of this BigNumber, or null if the value of this BigNumber is ±Infinity or NaN

By the way, the return type of decimalPlaces() is just number, which is wrong. The correct type should be number | null.

Thank you for letting me know.

Got the same issue +1 Was wondering which version can resolve the issue. Thx.

@lukelu0520
I'm sure you can find that out for yourself.


[Feature] :grey_question: Support for html/pdf pages and YT videos ?

Is this your first time submitting a feature request?

[X] I have searched the existing issues, and I could not find an existing issue for this feature
[X] I am requesting a straightforward extension of existing functionality

Describe the feature
Hi, I see in the README that canopy actually supports local files likes parquet, is there nay kind of DocumentLoader for online contents like:

YT Video
Html page

... and does it support local pdf import ?
Describe alternatives you've considered

Scrap web content into text files then load them
For YT : build transcript, then load the txt output

Who will this benefit?
I gues almost any lazy people wanting to give a try and use canopy
Are you interested in contributing this feature?
No response
Anything else?
No response

Would it be possible to use an existing Pinecone index for Canopy? I built it from PDF files using llama-index; and also the free version of Pinecone does not support more than one index - so it would be great to re-use the existing one...

PDF is a must have

Yes, please include PDF in Canopy

@adriens @NB-123 @pashpashpash @strelkon Check out this library: PineconePDFExtractor it will accept a list of pdf files and convert them back to your desired format so that you can use pinecone-canopy's upsert data into this endpoint: v1/context/upsert on FastAPI

Thanks a lot for pointing this library @kowshik24 :pray:


Unsupported file for collecting classes: with com.sun.xm.ws

I added this dependency
implementation 'com.sun.xml.ws:jaxws-ri:4.0.0'
And now I am getting this error
Execution failed for task ':gar2-data-app:analyzeClassesDependencies'. Unsupported file for collecting classes: .gradle/caches/modules-2/files-2.1/com.sun.xml.ws/release-documentation/4.0.0/5eb09d77be092684546352a35f315423d67e044b/release-documentation-4.0.0-docbook.zip
Versions
Java: 17
Gradle: 7.5.1
Plugin: 1.9.0

i see, i think the best is to exclude zip files from being analyzed as this type of dependency looks like a complete archive containing libs and much other stuff instead of being a normal jar dependency.
will fix this soon

can you @mysticdrew maybe share a small sample project of how you use this dependency? I'm now struggling with the ìmplementation`scope for this zip file.

@BigMichi1
Sorry, I somehow missed this email that you responded.
It looks like this dependency creates this zip file. We do not use it at all in our project. I will look into creating a test project for you.

Ahh, okay.
I was able to fix this by changing the dependency to 'com.sun.xml.ws:jaxws-rt:4.0.0'
Per these stackoverflows.
https://stackoverflow.com/questions/74606504/jaxws-not-compatible-with-javafx-modules
https://stackoverflow.com/questions/5401358/whats-the-difference-between-jaxws-ri-and-jaxws-rt


fix --alias flag for lxc image copy

Signed-off-by: Serge Hallyn<EMAIL_ADDRESS>

Whoops, I should have figured that out too :)


fix: js fallback sourcemap content should be using original content

Description
Follow up to #14247.
fixes https://github.com/vitejs/vite/pull/14247#issuecomment-1824584073
I tested this change with VSCode, Chrome, Firefox.
Additional context

What is the purpose of this pull request?

[x] Bug fix
[ ] New Feature
[ ] Documentation update
[ ] Other

Before submitting the PR, please make sure you do the following

[x] Read the Contributing Guidelines, especially the Pull Request Guidelines.
[x] Check that there isn't already a PR that solves the problem the same way to avoid creating a duplicate.
[x] Provide a description in this PR that addresses what the PR is solving, or reference the issue that it solves (e.g. fixes #123).
[x] Update the corresponding documentation if needed.
[ ] Ideally, include relevant tests that fail without this PR but pass with it.

/ecosystem-ci run

Thank you for such a quick response!
I also checked in the WebStorm debugger and now everything works fine.


call place_cursor_at function by callback

It rasied ValueError, when fuzzySearch again. Even though the file exists
Changed to calling place_cursor_at function by callback

Sorry, I just now noticed this.
I believe that it is fixed now, right?


[admin] Publish

Docs Build status updates of commit 117538a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs/includes/modern-js-note.md
:white_check_mark:Succeeded
View

docs/includes/quickstart-vs-prerequisites.md
:white_check_mark:Succeeded
View

docs/includes/quickstart-yo-prerequisites.md
:white_check_mark:Succeeded
View

docs/quickstarts/excel-quickstart-jquery.md
:white_check_mark:Succeeded
View

docs/quickstarts/word-quickstart.md
:white_check_mark:Succeeded
View

docs/testing/debug-add-ins-in-office-online.md
:white_check_mark:Succeeded
View

docs/tutorials/excel-tutorial.md
:white_check_mark:Succeeded
View

docs/tutorials/word-tutorial.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


chore: bootstrap releases for path: .

Configuring release-please for path: .

ignore please, just testing a tool


Add system identifier for the tags

Whichever classification is of type system should have an identifier.

@devyani-kaushik lets use a better styling for this. We can use badge styling

https://www.figma.com/file/VaeQD2fIhQVDCvqBHyEv7J/Open-Metadata?node-id=18582%3A22371&t=ZtvaH5N1wXZ11X9z-1

@chirag-madlani


feat: remove usage of privilege dictionary in favour of getattr() in addition and removal of privileges

Describe your changes
removes str_priv_dict in favour of getattr() in !addpriv and !rmpriv
Related Issues / Projects
Checklist

[x] I've manually tested my code
[x] The changes pass pre-commit checks (make lint)
[x] The changes follow coding style

eh tbh if it ain't broke, don't fix it - better to focus on adding functionality or improving ux like some of your other recent prs

i don't rly like that mindset but to each their own i guess


Fixed dashboard stats card layout break

Fixed layout break on the dashboard:
Before:

After:

Hi @cgartner-redstage
We have removed "increased" or "Aumento" & vice-versa because symbols represents the same think.
Now our dashboard look like -

Hi @rahulshukla-webkul
Without the "increased" text will be ok, but I think we need to change the fixed height for min-height to avoid future problems.
You can close this PR for now :)
I don't have the rights to close my PR.


Removed a few unused imports, missing references, and other errors

Decided to go through a bunch of the files to learn more about each, in the process also decided to clean things up where possible.

Current coverage is 96.86% (diff: 80.00%)

Merging #992 into develop will decrease coverage by 0.43%

@@            develop       #992   diff @@
==========================================
  Files            43         43
  Lines          7089       7084     -5
  Methods           0          0
  Messages          0          0
  Branches          0          0
==========================================
- Hits           6898       6862    -36
- Misses          191        222    +31
  Partials          0          0

Powered by Codecov. Last update c26ee47...11f4007

Could you split the commits up?  I prefer not to have commits that are doing multiple things.  Your comments on this PR would be a good way to break up the commits :)
Have you had a chance to look at why codecov is complaining?

Sure I can split it up. as for why codecov is complaining, im not sure. Nothing is changing that I can see that would affect coverage.

codecov is complaining I believe because you are overall removing lines and as a result a removal of lines that were completely covered would cause the overall code coverage to decrease. Let us know when you split up the commits.


Dapr APISIX integration - Tracing is not starting from apisix

We are using Dapr with all our services and all the pods are having dapr sidecar. We wanted to integrate dapr with APISIX gateway. The main objective for this integration is to start mTLS and tracing from APISIX gateway itself instead of the service.
We followed this blog from dapr for the same.
We were able to successfully integrate dapr with API six and we created a route for one of our application named governor and rout was configured to route the request through dapr sidecar. We also created a Dapr Configuration to enable tracing for APISIX.
We are able to hit the request and the request is routing properly through dapr sidecar but when I see the traces.. Tracing is starting from Governor service, not APISIX Gateway.
APISIX also provides plugin to enable zipkin tracing I tried that as well.
In this scenario even though I am able to see the traces of APISIX as well but it's creating two traces one for APISIX and one for Governor service.
On further investigation, I found out that the Zipkin plugin is passing trace header with a different name (x-b3-traceid) but dapr expects traceparent, That is why dapr is generating a new traceId and hence we are seeing 2 traces.
In what area(s)?

area runtime - dapr sidecar
What version of Dapr?

1.8.0
Expected Behavior

Tracing and mtls should start from apisix cloud gateway and should trace end to end requests in a single trace
Actual Behavior

By default, tracing is not starting from APISIX and dapr tracing and APISIX Zipkin tracing are not compatible.
Steps to Reproduce the Problem

Release Note

RELEASE NOTE:
APISIX Route Config for your Reference.
components: {} info:   title: RoutesExport   version: 3.0.0 openapi: 3.0.0 paths:   /governor/{params}:     delete:       operationId: governor-routeDELETE       parameters:         - description: params in path           in: path           name: params           required: true           schema:             type: string       requestBody: {}       responses:         default:           description: ''       security: []       x-apisix-enable_websocket: false       x-apisix-id: '419010533459493399'       x-apisix-plugins:         proxy-rewrite:           regex_uri:             - ^/governor/(.*)             - /v1.0/invoke/governor.governor/method/$1         zipkin:           disable: false           endpoint: http://otel-collector.management.svc.cluster.local:9411/api/v2/spans           sample_ratio: 1           service_name: APISIX-IN-SG       x-apisix-priority: 0       x-apisix-status: 1       x-apisix-upstream:         nodes:           - host: <IP_ADDRESS>             port: 3500             weight: 1         timeout:           connect: 6           send: 6           read: 6         type: roundrobin         scheme: http         pass_host: pass         name: httpbin-dapr         keepalive_pool:           idle_timeout: 60           requests: 1000           size: 320     get:       operationId: governor-routeGET       parameters:         - description: params in path           in: path           name: params           required: true           schema:             type: string       requestBody: {}       responses:         default:           description: ''       security: []       x-apisix-enable_websocket: false       x-apisix-id: '419010533459493399'       x-apisix-plugins:         proxy-rewrite:           regex_uri:             - ^/governor/(.*)             - /v1.0/invoke/governor.governor/method/$1         zipkin:           disable: false           endpoint: http://otel-collector.management.svc.cluster.local:9411/api/v2/spans           sample_ratio: 1           service_name: APISIX-IN-SG       x-apisix-priority: 0       x-apisix-status: 1       x-apisix-upstream:         nodes:           - host: <IP_ADDRESS>             port: 3500             weight: 1         timeout:           connect: 6           send: 6           read: 6         type: roundrobin         scheme: http         pass_host: pass         name: httpbin-dapr         keepalive_pool:           idle_timeout: 60           requests: 1000           size: 320     head:       operationId: governor-routeHEAD       parameters:         - description: params in path           in: path           name: params           required: true           schema:             type: string       requestBody: {}       responses:         default:           description: ''       security: []       x-apisix-enable_websocket: false       x-apisix-id: '419010533459493399'       x-apisix-plugins:         proxy-rewrite:           regex_uri:             - ^/governor/(.*)             - /v1.0/invoke/governor.governor/method/$1         zipkin:           disable: false           endpoint: http://otel-collector.management.svc.cluster.local:9411/api/v2/spans           sample_ratio: 1           service_name: APISIX-IN-SG       x-apisix-priority: 0       x-apisix-status: 1       x-apisix-upstream:         nodes:           - host: <IP_ADDRESS>             port: 3500             weight: 1         timeout:           connect: 6           send: 6           read: 6         type: roundrobin         scheme: http         pass_host: pass         name: httpbin-dapr         keepalive_pool:           idle_timeout: 60           requests: 1000           size: 320     patch:       operationId: governor-routePATCH       parameters:         - description: params in path           in: path           name: params           required: true           schema:             type: string       requestBody: {}       responses:         default:           description: ''       security: []       x-apisix-enable_websocket: false       x-apisix-id: '419010533459493399'       x-apisix-plugins:         proxy-rewrite:           regex_uri:             - ^/governor/(.*)             - /v1.0/invoke/governor.governor/method/$1         zipkin:           disable: false           endpoint: http://otel-collector.management.svc.cluster.local:9411/api/v2/spans           sample_ratio: 1           service_name: APISIX-IN-SG       x-apisix-priority: 0       x-apisix-status: 1       x-apisix-upstream:         nodes:           - host: <IP_ADDRESS>             port: 3500             weight: 1         timeout:           connect: 6           send: 6           read: 6         type: roundrobin         scheme: http         pass_host: pass         name: httpbin-dapr         keepalive_pool:           idle_timeout: 60           requests: 1000           size: 320     post:       operationId: governor-routePOST       parameters:         - description: params in path           in: path           name: params           required: true           schema:             type: string       requestBody: {}       responses:         default:           description: ''       security: []       x-apisix-enable_websocket: false       x-apisix-id: '419010533459493399'       x-apisix-plugins:         proxy-rewrite:           regex_uri:             - ^/governor/(.*)             - /v1.0/invoke/governor.governor/method/$1         zipkin:           disable: false           endpoint: http://otel-collector.management.svc.cluster.local:9411/api/v2/spans           sample_ratio: 1           service_name: APISIX-IN-SG       x-apisix-priority: 0       x-apisix-status: 1       x-apisix-upstream:         nodes:           - host: <IP_ADDRESS>             port: 3500             weight: 1         timeout:           connect: 6           send: 6           read: 6         type: roundrobin         scheme: http         pass_host: pass         name: httpbin-dapr         keepalive_pool:           idle_timeout: 60           requests: 1000           size: 320     put:       operationId: governor-routePUT       parameters:         - description: params in path           in: path           name: params           required: true           schema:             type: string       requestBody: {}       responses:         default:           description: ''       security: []       x-apisix-enable_websocket: false       x-apisix-id: '419010533459493399'       x-apisix-plugins:         proxy-rewrite:           regex_uri:             - ^/governor/(.*)             - /v1.0/invoke/governor.governor/method/$1         zipkin:           disable: false           endpoint: http://otel-collector.management.svc.cluster.local:9411/api/v2/spans           sample_ratio: 1           service_name: APISIX-IN-SG       x-apisix-priority: 0       x-apisix-status: 1       x-apisix-upstream:         nodes:           - host: <IP_ADDRESS>             port: 3500             weight: 1         timeout:           connect: 6           send: 6           read: 6         type: roundrobin         scheme: http         pass_host: pass         name: httpbin-dapr         keepalive_pool:           idle_timeout: 60           requests: 1000           size: 320
cc: @akhilac1

You shouldn't need to use a zipkin plugin for APISIX as the local Dapr sidecar will start the trace.

You shouldn't need to use a zipkin plugin for APISIX as the local Dapr sidecar will start the trace.

@vikas2k14 Based on the above comment, Dapr should automatically start the trace. Zipkin uses B3 Propagation and that is not what Dapr uses afaik. @yaron2 Correct me if I am wrong.
@vikas2k14  Can you check without the zipkin plugin for APISIX?

@yaron2 @mukundansundar
That was the expectation that once the sidecar is attached to the apisix pod, it should start tracing from the apisix gateway without using any external plugin, but that's not the observed behavior.
As a workaround, I tried using the Zipkin plugin provided by apisix but that doesn't seem to be a compatible solution.

it seems to be working after a redeploy
I will keep the issue open for a week to observe the behavior and close it out if it is consistent.


Callback listeners that cause events to occur cause deadlocks with parallel execution

We have a TaskExecutionListener that recalculates the hashes for inputs for a task: https://github.com/gradle/gradle/blob/master/gradle/taskCacheBuildScanUserData.gradle
This sometimes causes deadlocks between a TaskExecutionListener and DependencyResolutionListener when running with --parallel.  For now, we've disabled our listener when parallel execution is enabled.  In the long term, we're going to replace this listener with built-in functionality.
I haven't been able to reduce it down to a reproducible test.  The problem seems to be deep down in our listener manager infrastructure and we deadlock trying to handle listener callbacks.

#2406 could be a similar bug.

@rkrisztian no, this is unrelated.


Type error in path.js with node 6.x

After updating to node 6.0.0 and trying to execute gulp bundle I get the following error:
TypeError: Path must be a string. Received undefined     at assertPath (path.js:7:11)     at Object.basename (path.js:1355:5)     at exports.writeOutputs (/media/dfk_7677/New Volume/workspace/js/bfrcon/node_modules/systemjs-builder/lib/output.js:137:23)     at /media/dfk_7677/New Volume/workspace/js/bfrcon/node_modules/systemjs-builder/lib/builder.js:575:14     at tryCatcher (/media/dfk_7677/New Volume/workspace/js/bfrcon/node_modules/systemjs-builder/node_modules/bluebird/js/release/util.js:16:23)     at Promise._settlePromiseFromHandler (/media/dfk_7677/New Volume/workspace/js/bfrcon/node_modules/systemjs-builder/node_modules/bluebird/js/release/promise.js:502:31)     at Promise._settlePromise (/media/dfk_7677/New Volume/workspace/js/bfrcon/node_modules/systemjs-builder/node_modules/bluebird/js/release/promise.js:559:18)     at Promise._settlePromise0 (/media/dfk_7677/New Volume/workspace/js/bfrcon/node_modules/systemjs-builder/node_modules/bluebird/js/release/promise.js:604:10)     at Promise._settlePromises (/media/dfk_7677/New Volume/workspace/js/bfrcon/node_modules/systemjs-builder/node_modules/bluebird/js/release/promise.js:683:18)     at Async._drainQueue (/media/dfk_7677/New Volume/workspace/js/bfrcon/node_modules/systemjs-builder/node_modules/bluebird/js/release/async.js:138:16)     at Async._drainQueues (/media/dfk_7677/New Volume/workspace/js/bfrcon/node_modules/systemjs-builder/node_modules/bluebird/js/release/async.js:148:10)     at Immediate.Async.drainQueues [as _onImmediate] (/media/dfk_7677/New Volume/workspace/js/bfrcon/node_modules/systemjs-builder/node_modules/bluebird/js/release/async.js:17:14)     at tryOnImmediate (timers.js:543:15)     at processImmediate [as _immediateCallback] (timers.js:523:5)

Thanks for reporting. We will be looking into it.

Issue seems to be resolved and aurelia-bundler works with node 6.2.0.

Getting the same issue with node v6.10.0
[14:35:22] Using gulpfile aurelia\gulpfile.js
[14:35:22] Starting 'deploy'...
[14:35:22] Starting 'clean'...
[14:35:22] Finished 'deploy' after 13 ms
[14:35:22] Finished 'clean' after 19 ms
[14:35:22] Starting 'unbundle'...
[14:35:22] Finished 'unbundle' after 9.77 ms
[14:35:22] Starting 'bundle'...
[14:35:37] 'bundle' errored after 15 s
[14:35:37] TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at Object.basename (path.js:799:5)
    at exports.writeOutputs (aurelia\node_modules\systemjs-builder\lib\output.js:145:23)
    at aurelia\node_modules\systemjs-builder\lib\builder.js:373:14
    at tryCatch (aurelia\node_modules\rsvp\dist\rsvp.js:539:12)
    at invokeCallback (aurelia\node_modules\rsvp\dist\rsvp.js:554:13)
    at publish (aurelia\node_modules\rsvp\dist\rsvp.js:522:7)
    at flush (aurelia\node_modules\rsvp\dist\rsvp.js:2414:5)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)
[14:35:37] TypeError in plugin 'run-sequence(bundle)'
Message:
    Path must be a string. Received undefined
Stack:
TypeError: Path must be a string. Received undefined
    at assertPath (path.js:7:11)
    at Object.basename (path.js:799:5)
    at exports.writeOutputs (aurelia\node_modules\systemjs-builder\lib\output.js:145:23)
    at aurelia\node_modules\systemjs-builder\lib\builder.js:373:14
    at tryCatch (aurelia\node_modules\rsvp\dist\rsvp.js:539:12)
    at invokeCallback (aurelia\node_modules\rsvp\dist\rsvp.js:554:13)
    at publish (aurelia\node_modules\rsvp\dist\rsvp.js:522:7)
    at flush (aurelia\node_modules\rsvp\dist\rsvp.js:2414:5)
    at _combinedTickCallback (internal/process/next_tick.js:67:7)
    at process._tickCallback (internal/process/next_tick.js:98:9)

@karthickthangasamy
Updating Auelia Bundler to the latest version will solve this issue.
I checked it with<EMAIL_ADDRESS>,its working fine.


Collect data interval displayed incorrectly in HA

The collect data interval is set to 1 minute for TSUN inverters. The proxy reads the values incorrectly and displays 1 second for GEN3 inverters and 60 seconds for GEN3PLUS inverters.

fixed with #63


Integration with nuxt possible?

Hello! I was looking at the docs for rpgjs and it’s very amazing that it incorporates being able to use vue as the GUI. However, I’m currently using nuxt and I wanted to see if I can use rpgjs to make a small rpg game in a route like in website/rpg. It seems like the directory structure for rpgjs is set, and it uses express as the server. It also defaults to mongodb for auth I think? I wanted to use nuxt as the server + pinia as my central state management tool with this and also my auth depends on Postgres so I wanted to ask if there was some flexibility in defining my own functions to pass to rpgjs for that, kind of like an adapter and also defining the paths for the rpgjs compiler to detect

Hello,
There are currently no tests with Nuxt. I can't really comment on it.
You should know that Vue instance is created directly in the RPGJS engine to then display user interfaces on top of the game. This instance can be retrieved via the API
As for the database, you're free to use whatever you like in RPGJS. MongoDB is only used for a plugin to connect to the game.


azure-cli: use overridePythonAttrs for overrides

Description of changes
It looks like azure-cli overrides the mgmt package versions, but it does so using overrideAttrs (which only affects the internal stdenv.mkDerivation) instead of overridePythonAttrs (which also affects the buildPythonPackage magic)
This indirectly fixes the azure-cli failure after #250560 where the extension was changed from .zip to .tar.gz, but azure-cli was forcing the old .zip src. Because it wasn't overriding the buildPythonPackage attrs, it didn't include unzip in nativeBuildInputs, since buildPythonPackage only adds it when the src that it uses ends in .zip (and before this PR azure-cli was only changing the inner mkDerivation logic, after that would have happened)
Things done

Built on platform(s)

[x] x86_64-linux
[x] aarch64-linux
[x] x86_64-darwin
[x] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 251144 run on x86_64-linux 1

2 packages built:

azure-cli
azure-cli.dist

FYI: @AkechiShiro


Using allStarLite as default for DR16 breaks importation

Not a priority, but I found a slight bug due to the difference in formatting between the allStarLite files in DR16 and DR17. For DR17, the file has 3 HDU's, with HDU 3 being loaded, whereas DR16 just has 2. This means the DR16 file is downloaded then unable to read by the current code in apogee/tools/__init__.py:
https://github.com/jobovy/apogee/blob/b218e62bd158d56695d8f3c8ae4ab3b78800d7af/apogee/tools/__init__.py#L14-L21
Since PARAM_SYMBOL isn't present in the DR16 allStarLite, just changing the extension for DR16 won't help much.
The best solution could be to just check for dr17 or not and just use the regular allStar for all DR's but DR17. Another is to simply catch the IndexError that gets raised (alongside the ValueError catch), but I wasn't sure about what the effect of _INDEX_ARRAYS_LOADED= False might be downstream?

Yeah, we need the index arrays, so I think your proposed fix is correct.


Hiding the table make the empty text no longer centered

mantine-react-table version
v2.0.0.beta7
react & react-dom versions
v18.2.0
Describe the bug and the steps to reproduce it

Display a table with 0 rows
Hide the table (use the Mantine tabs without disabling keepMounted)
Show the table
=> The text "No records to display" will no longer be centered

Minimal, Reproducible Example - (Optional, but Recommended)
The problem is related to these lines:
                  <Text
                    __vars={{
                      '--mrt-paper-width': `${tablePaperRef.current?.clientWidth}`,
                    }}
                    className={clsx(classes['empty-row-td-content'])}
                  >

Once hidden, clientWidth becomes 0. Once we re-display the table again, clientWidth will be 0 on the first redraw but then be properly set on the next one. We can work around the issue by forcing a redraw, however, by removing the var 'mrt-paper-width', the text will occupy 100% of its space and the issue will be fixed. I can open a PR with the removal of this line, but it was introduced in the PR allowing virtualization and might be needed for a certain use case. Feel free to point me in the right direction for the PR.
Screenshots or Videos (Optional)

Do you intend to try to help solve this bug with your own PR?
Yes, I think I know how to fix it and will discuss it in the comments of this issue
Terms

[X] I understand that if my bug cannot be reliably reproduced in a debuggable environment, it will probably not be fixed and this issue may even be closed.

This fixes it for me:
mantinePaperProps: {
  className: classes.root,
},

.root {
  [class*='MRT_TableBody-module_root-no-rows'] {
    p {
      --mrt-paper-width: unset !important;
    }
  }
}


Builds server offline?

The download links gives me a timeout.
Example: http://builds.cuberite.org/job/MCServer Linux x86/lastSuccessfulBuild/artifact/MCServer.tar (Or any in the main MC-Server page).
Is the server down?

The hosting provider appears to be down. Troubleshooting the issue.

The buildserver should be coming back up in a minute or two.

Thanks :D


Start using the log crate

I did this while debugging the issue for PR #120
Users of the library can then decide what logging framework
to use (if any) and get useful debug information.

Thanks!


Improvements to contract factory

The implicit conversion pass is no longer a requirement
Salt (bytes32) is now converted to a bytes30, now it no longer errors
for values bigger than a felt
calldata expected location is set only for reference types

Running Semantic Tests

Sem Tests pass