Jan 30 03:16:54.652 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 941.734577ms...
Jan 30 03:16:54.822 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.058441455s...
Jan 30 03:16:55.594 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.095998788s...
Jan 30 03:16:55.882 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.078392147s...
Jan 30 03:16:56.691 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 989.534957ms...
Jan 30 03:16:56.962 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 947.630572ms...
Jan 30 03:16:57.683 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 957.328637ms...
Jan 30 03:16:57.910 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.062500081s...
Jan 30 03:16:58.641 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 958.80729ms...
Jan 30 03:16:58.974 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 988.695011ms...
Jan 30 03:16:59.601 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 979.964151ms...
Jan 30 03:16:59.964 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.073181828s...
Jan 30 03:17:00.582 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.002077803s...
Jan 30 03:17:01.039 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.087581189s...
Jan 30 03:17:01.585 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 965.924093ms...
Jan 30 03:17:02.128 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 931.965022ms...
Jan 30 03:17:02.553 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 937.041826ms...
Jan 30 03:17:03.061 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.051637516s...
Jan 30 03:17:03.491 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.098408728s...
Jan 30 03:17:04.114 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 950.201078ms...
Jan 30 03:17:04.591 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.091543915s...
Jan 30 03:17:05.066 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.054220809s...
Jan 30 03:17:05.684 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.042357794s...
Jan 30 03:17:06.121 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 962.518876ms...
Jan 30 03:17:06.727 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.037769873s...
Jan 30 03:17:07.085 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.044203803s...
Jan 30 03:17:07.766 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 959.928389ms...
Jan 30 03:17:08.131 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.044318763s...
Jan 30 03:17:08.728 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.04667003s...
Jan 30 03:17:09.176 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 906.381977ms...
Jan 30 03:17:09.775 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.098269522s...
Jan 30 03:17:10.084 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.057507405s...
Jan 30 03:17:10.874 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 901.820955ms...
Jan 30 03:17:11.142 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 927.110725ms...
Jan 30 03:17:11.777 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.013205245s...
Jan 30 03:17:12.071 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.098554206s...
Jan 30 03:17:12.792 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 963.267123ms...
Jan 30 03:17:13.171 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 988.864488ms...
Jan 30 03:17:13.757 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 957.51882ms...
Jan 30 03:17:14.161 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.09457071s...
Jan 30 03:17:14.715 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.014816925s...
Jan 30 03:17:15.257 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 963.936026ms...
Jan 30 03:17:15.731 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.097010888s...
Jan 30 03:17:16.223 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 979.833044ms...
Jan 30 03:17:16.830 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 900.150132ms...
Jan 30 03:17:17.204 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.046113487s...
Jan 30 03:17:17.731 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 943.59697ms...
Jan 30 03:17:18.251 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.086981495s...
Jan 30 03:17:18.677 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 983.255337ms...
Jan 30 03:17:19.340 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.049249933s...
Jan 30 03:17:19.661 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 972.116374ms...
Jan 30 03:17:20.390 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 912.301936ms...
Jan 30 03:17:20.635 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.033413881s...
Jan 30 03:17:21.304 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 909.534315ms...
Jan 30 03:17:21.669 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 938.342761ms...
Jan 30 03:17:22.216 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 958.94333ms...
Jan 30 03:17:22.609 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 927.240576ms...
Jan 30 03:17:23.177 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 958.96611ms...
Jan 30 03:17:23.537 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.013524088s...
Jan 30 03:17:24.136 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.05215777s...
Jan 30 03:17:24.553 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.0804203s...
Jan 30 03:17:25.189 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.069335093s...
Jan 30 03:17:25.634 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 911.677484ms...
Jan 30 03:17:26.259 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.089729728s...
Jan 30 03:17:26.548 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 935.103629ms...
Jan 30 03:17:27.351 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.050086003s...
Jan 30 03:17:27.484 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.012780502s...
Jan 30 03:17:28.403 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 926.380192ms...
Jan 30 03:17:28.498 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 986.530592ms...
Jan 30 03:17:29.331 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.090923356s...
Jan 30 03:17:29.486 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 981.962093ms...
Jan 30 03:17:30.424 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.013681341s...
Jan 30 03:17:30.469 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 930.328506ms...
Jan 30 03:17:31.401 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.093394501s...
Jan 30 03:17:31.439 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 954.722552ms...
Jan 30 03:17:32.394 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.057895016s...
Jan 30 03:17:32.497 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.032545966s...
Jan 30 03:17:33.453 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.081318012s...
Jan 30 03:17:33.530 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.035419098s...
Jan 30 03:17:34.536 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.08897334s...
Jan 30 03:17:34.567 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 974.760161ms...
Jan 30 03:17:35.544 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.038004431s...
Jan 30 03:17:35.626 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 919.143538ms...
Jan 30 03:17:36.547 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.07437875s...
Jan 30 03:17:36.583 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 962.255763ms...
Jan 30 03:17:37.547 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.019502448s...
Jan 30 03:17:37.622 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.036344122s...
Jan 30 03:17:38.568 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 942.931426ms...
Jan 30 03:17:38.660 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.050338156s...
Jan 30 03:17:39.513 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.062783696s...
Jan 30 03:17:39.712 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.055161926s...
Jan 30 03:17:40.577 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.099983939s...
Jan 30 03:17:40.769 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 973.900562ms...
Jan 30 03:17:41.679 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 917.482732ms...
Jan 30 03:17:41.744 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 987.229657ms...
Jan 30 03:17:42.597 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.033375069s...
Jan 30 03:17:42.732 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.041663291s...
Jan 30 03:17:43.633 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 924.335085ms...
Jan 30 03:17:43.775 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 950.436381ms...
Jan 30 03:17:44.558 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.063216357s...
Jan 30 03:17:44.727 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.04925799s...
Jan 30 03:17:45.624 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 925.744934ms...
Jan 30 03:17:45.777 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 941.164833ms...
Jan 30 03:17:46.550 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.043314105s...
Jan 30 03:17:46.719 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.060290044s...
Jan 30 03:17:47.595 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.025456994s...
Jan 30 03:17:47.780 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.07913555s...
Jan 30 03:17:48.622 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.09685261s...
Jan 30 03:17:48.860 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.055439323s...
Jan 30 03:17:49.720 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.035811166s...
Jan 30 03:17:49.916 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 930.040091ms...
Jan 30 03:17:50.758 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.036169786s...
Jan 30 03:17:50.847 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.005473953s...
Jan 30 03:17:51.796 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.012317024s...
Jan 30 03:17:51.854 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 998.181665ms...
Jan 30 03:17:52.810 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 903.811231ms...
Jan 30 03:17:52.853 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 937.633204ms...
Jan 30 03:17:53.714 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.011901645s...
Jan 30 03:17:53.793 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.094596324s...
Jan 30 03:17:54.727 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.092582902s...
Jan 30 03:17:54.889 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.053526723s...
Jan 30 03:17:55.821 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.067812291s...
Jan 30 03:17:55.944 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 974.956231ms...
Jan 30 03:17:56.890 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 996.524005ms...
Jan 30 03:17:56.921 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 988.599415ms...
Jan 30 03:17:57.888 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.091550364s...
Jan 30 03:17:57.910 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 993.933471ms...
Jan 30 03:17:58.905 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.08794096s...
Jan 30 03:17:58.981 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.073972036s...
Jan 30 03:17:59.994 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.023241804s...
Jan 30 03:18:00.057 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.06739889s...
Jan 30 03:18:01.018 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 922.378143ms...
Jan 30 03:18:01.126 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.097423688s...
Jan 30 03:18:01.941 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.079579782s...
Jan 30 03:18:02.225 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 901.003642ms...
Jan 30 03:18:03.022 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.009709073s...
Jan 30 03:18:03.128 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 966.442959ms...
Jan 30 03:18:04.033 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 953.519481ms...
Jan 30 03:18:04.096 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 993.379496ms...
Jan 30 03:18:04.988 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.042199561s...
Jan 30 03:18:05.091 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 991.933698ms...
Jan 30 03:18:06.031 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 968.849243ms...
Jan 30 03:18:06.083 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.068433264s...
Jan 30 03:18:07.001 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.083366024s...
Jan 30 03:18:07.154 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 941.535422ms...
Jan 30 03:18:08.085 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.032444971s...
Jan 30 03:18:08.096 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 992.508327ms...
Jan 30 03:18:09.090 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.083008129s...
Jan 30 03:18:09.120 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 945.467229ms...
Jan 30 03:18:10.066 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.000214087s...
Jan 30 03:18:10.175 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.004568036s...
Jan 30 03:18:11.067 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.015707755s...
Jan 30 03:18:11.180 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 963.872829ms...
Jan 30 03:18:12.085 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.00541579s...
Jan 30 03:18:12.145 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.069513942s...
Jan 30 03:18:13.091 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 967.331879ms...
Jan 30 03:18:13.216 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 910.303249ms...
Jan 30 03:18:14.060 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 959.216713ms...
Jan 30 03:18:14.128 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 981.486175ms...
Jan 30 03:18:15.020 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 998.477227ms...
Jan 30 03:18:15.110 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.075622518s...
Jan 30 03:18:16.020 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 965.190746ms...
Jan 30 03:18:16.187 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 920.877328ms...
Jan 30 03:18:16.986 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.046358664s...
Jan 30 03:18:17.109 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.036038799s...
Jan 30 03:18:18.034 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.078556734s...
Jan 30 03:18:18.146 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 970.877878ms...
Jan 30 03:18:19.113 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.013706286s...
Jan 30 03:18:19.118 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.066130686s...
Jan 30 03:18:20.129 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 906.243262ms...
Jan 30 03:18:20.186 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.092138201s...
Jan 30 03:18:21.036 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.051361199s...
Jan 30 03:18:21.280 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.050155322s...
Jan 30 03:18:22.089 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 954.674432ms...
Jan 30 03:18:22.331 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.01119555s...
Jan 30 03:18:23.044 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.076426476s...
Jan 30 03:18:23.344 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.012025947s...
Jan 30 03:18:24.123 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.041215562s...
Jan 30 03:18:24.357 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 944.598517ms...
Jan 30 03:18:25.165 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 972.845403ms...
Jan 30 03:18:25.304 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 955.970348ms...
Jan 30 03:18:26.139 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.065891056s...
Jan 30 03:18:26.261 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.050134449s...
Jan 30 03:18:27.206 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.04255497s...
Jan 30 03:18:27.312 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.08151228s...
Jan 30 03:18:28.250 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 923.473306ms...
Jan 30 03:18:28.394 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 946.019948ms...
Jan 30 03:18:29.174 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.064344811s...
Jan 30 03:18:29.341 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 946.405149ms...
Jan 30 03:18:30.240 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.032878721s...
Jan 30 03:18:30.288 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.046650509s...
Jan 30 03:18:31.275 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 966.456174ms...
Jan 30 03:18:31.336 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.018637987s...
Jan 30 03:18:32.242 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 902.102596ms...
Jan 30 03:18:32.357 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.050370958s...
Jan 30 03:18:33.146 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.003042783s...
Jan 30 03:18:33.408 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 908.248505ms...
Jan 30 03:18:34.150 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 992.356181ms...
Jan 30 03:18:34.318 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 952.748266ms...
Jan 30 03:18:35.145 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.046307828s...
Jan 30 03:18:35.272 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.0418102s...
Jan 30 03:18:36.193 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 954.024899ms...
Jan 30 03:18:36.315 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.040543971s...
Jan 30 03:18:37.148 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 963.874254ms...
Jan 30 03:18:37.357 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.077387132s...
Jan 30 03:18:38.113 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 927.713983ms...
Jan 30 03:18:38.435 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.012576644s...
Jan 30 03:18:39.042 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.091343417s...
Jan 30 03:18:39.449 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 984.303423ms...
Jan 30 03:18:40.135 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.064985695s...
Jan 30 03:18:40.434 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 987.319381ms...
Jan 30 03:18:41.201 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.054198269s...
Jan 30 03:18:41.423 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.008424338s...
Jan 30 03:18:42.257 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.004531235s...
Jan 30 03:18:42.434 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.053294246s...
Jan 30 03:18:43.263 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 967.986138ms...
Jan 30 03:18:43.489 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.085007355s...
Jan 30 03:18:44.233 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 937.644497ms...
Jan 30 03:18:44.576 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.041599212s...
Jan 30 03:18:45.172 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.016501874s...
Jan 30 03:18:45.619 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.050073366s...
Jan 30 03:18:46.190 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 948.292305ms...
Jan 30 03:18:46.671 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.02132635s...
Jan 30 03:18:47.140 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.020307095s...
Jan 30 03:18:47.694 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 985.345035ms...
Jan 30 03:18:48.162 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.061975781s...
Jan 30 03:18:48.681 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 919.379402ms...
Jan 30 03:18:49.226 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.062446329s...
Jan 30 03:18:49.601 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 943.845143ms...
Jan 30 03:18:50.290 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 925.300916ms...
Jan 30 03:18:50.546 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 968.514698ms...
Jan 30 03:18:51.217 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 956.778614ms...
Jan 30 03:18:51.516 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 920.815263ms...
Jan 30 03:18:52.175 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 909.436369ms...
Jan 30 03:18:52.438 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 992.451465ms...
Jan 30 03:18:53.085 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.032916846s...
Jan 30 03:18:53.432 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.033540521s...
Jan 30 03:18:54.119 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 940.533907ms...
Jan 30 03:18:54.467 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 976.302305ms...
Jan 30 03:18:55.061 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 971.6348ms...
Jan 30 03:18:55.445 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 930.510501ms...
Jan 30 03:18:56.034 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.059162708s...
Jan 30 03:18:56.377 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.047116145s...
Jan 30 03:18:57.095 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 995.496856ms...
Jan 30 03:18:57.425 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.042688466s...
Jan 30 03:18:58.092 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.064163142s...
Jan 30 03:18:58.469 ERROR handle{service=echo}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.087255999s...
Jan 30 03:18:59.158 ERROR handle{service=pingpong}: rathole::client: Failed to run the control channel: Failed to connect to <IP_ADDRESS>:2332: Connection refused (os error 111). Retry in 1.011408707s...

The repeating output has been trimmed it continued to be produced for six hours before the command was killed and is over 10MB uncompressed.
Environment:

OS:
Arch Linux
rathole --version output:
rathole
Build Timestamp:     2022-01-21T17:16:26.704280400+00:00
Build Version:       0.3.9
Commit SHA:          None
Commit Date:         None
Commit Branch:       None
cargo Target Triple: x86_64-unknown-linux-gnu
cargo Profile:       release
cargo Features:      base64,client,default,hot_reload,noise,notify,server,snowstorm,tls,tokio_native_tls
CPU architecture:
x86_64

Can you try main branch?

Can you include instructions about how to use openssl3 to compile the package, so I can debug it?

I think it's related to the breaking change about PKCS#12 in OpenSSL 3. I've update the test cases to address that. Can you test out https://github.com/rapiz1/rathole/pull/126 ?

I applied #126 and that fixed it.
Thank you for the fast response,  you had it fixed before I had written up the instructions for Arch.


I cant build, help please.

im try build from here, https://travis-ci.org/klange/osdev
But when i type ./.build-travis.sh i have error.
bekir@ubuntu:~/klange/osdev$ sudo ./.build-travis.sh
/home/build/osdev/toolchain ~/klange/osdev
~/klange/osdev
   CC   ./gui/ttk/lib/ttk-core.cIn file included from ./gui/ttk/lib/ttk-core.c:10:0:
./gui/ttk/ttk.h:7:19: fatal error: cairo.h: No such file or directory
compilation terminated.
   CC   ./gui/ttk/lib/ttk-core.c
/home/bekir/klange/osdev/userspace/gui/ttk/lib/ttk-core.o 1
['i686-pc-toaru-gcc', '-std=c99', '-U__STRICT_ANSI__', '-O3', '-m32', '-Wa,--32', '-g', '-I.', '-I/home/build/osdev/toolchain/local/i686-pc-toaru/include/freetype2', '-I/home/build/osdev/toolchain/local/i686-pc-toaru/include/cairo', '-I/home/build/osdev/toolchain/local/i686-pc-toaru/include/pixman-1', '-c', '-o', '/home/bekir/klange/osdev/userspace/gui/ttk/lib/ttk-core.o', './gui/ttk/lib/ttk-core.c']
Traceback (most recent call last):
  File "build.py", line 220, in <module>
    source_obj.run()
  File "build.py", line 108, in run
    raise Exception
Exception
make: *** [.userspace-check] Error 1
bekir@ubuntu:~/klange/osdev$

I have a problem i cant seem to go through
File "build.py", line 157, in
sources[os.path.abspath(source)] = compiler(source)
File "build.py", line 56, in init
self.includes, self.libs = self._depends()
File "build.py", line 86, in _depends
depends = self._calculate([], depends)
File "build.py", line 75, in _calculate
depends = self._calculate(depends, other)
File "build.py", line 75, in _calculate
depends = self._calculate(depends, other)
File "build.py", line 75, in _calculate
depends = self._calculate(depends, other)
File "build.py", line 75, in _calculate
depends = self._calculate(depends, other)
File "build.py", line 74, in _calculate
_, _, other = self.dependency_hints[k]
KeyError: ''

You are responding to a closed issue about an unrelated problem. If you have a different issue with the build tools, please file a separate ticket.


Regenerate action delete 'User' invite links

Regenerate invite link action deletes user invite link event if Organization Administrator is selected
A clear and concise description of what the bug is.
Steps to reproduce the behavior:

Go to 'Organization Setting->Members.'
Select "User"
Click on 'Regenerate'
Confirm the action
After this operation the 'Organization administrator' invite link is re-generated but the "User" link disappears.

The expectation is that only the "Organization administrator' link to be regenerated.
Looking at API requests sent from the browser, I have observed that the DELETE request is sent with the user's invite id (OK), but then the POST request is sent with {role:ADMIN} instead of {role:USER} (NOK) and this is causing the creation of a second invite link for ADMIN instead of USER.
And then the GET request returns two ADMIN invite links.
How are you running Flagsmith?

[x] Self Hosted with Docker

Thanks @luciantimar, we'll take a look into this.

Closed by #2307


Implement multi theme feature based on data attributes

Self Checklist

[ ] I wrote a PR title in English and added an appropriate label to the PR.
[ ] I wrote the commit message in English and to follow the Conventional Commits specification.
[ ] I added the changeset about the changes that needed to be released. (or didn't have to)
[ ] I wrote or updated documentation related to the changes. (or didn't have to)
[ ] I wrote or updated tests related to the changes. (or didn't have to)
[ ] I tested the changes in various browsers. (or didn't have to)

Windows: Chrome, Edge, (Optional) Firefox
macOS: Chrome, Edge, Safari, (Optional) Firefox

Related Issue

Fixes #1690
Summary

Details

Breaking change? (Yes/No)

References

Slot을 사용하여 ThemeContext(light or dark) / InvertedThemeContext 구현
툴팁 등은 --inverted 시맨틱 토큰을 사용하는 게 아닌, InvertedThemeContext 내부에서 일반적인 시맨틱 토큰을 사용하는 방식으로 구현됨

초기 테마 지정 로직에 미디어 쿼리 체크 로직을 포함하기?

@yangwooseong 전반적으로 업데이트해서 다시 한 번만 확인 부탁드리겠습니다 🙇


 Another question, when did this change? Didn't we just cut a new release so that this could be vendored somewhere?

Err, it was this PR that David stated we needed actually: https://github.com/microsoft/hcsshim/pull/890

@dcantah yeah the naming similarity of l4proxy and l4wfpproxy is unfortunate. but yes, I will fix the formatting and sign the commit


stackstac.stack returns empty array when items have different CRS

I'm trying to stack all the Landsat 8 images for a site (-67.008753, -9.96445, -65.615556, -8.57408) on Planetary Computer. The site happens to be in between two Landsat paths. As a result, when I search the images in the Planetary Computer catalog, I get images in different UTM zones, about half the images in epsg:32720 and about half in epsg:32719. I just picked 32720 but then an empty was returned.
bbox = (-67.008753, -9.96445, -65.615556, -8.57408)

search = catalog.search(
    intersects=tile,
    datetime="2020-01-01/2020-12-31",
    collections=["landsat-8-c2-l2"],
    limit=1000,
    query={'landsat:collection_category': {'eq': 'T1'}}
)

signed_items = [planetary_computer.sign(item).to_dict() for item in items]

data = (
    stackstac.stack(
        signed_items,
        chunksize=4096,
        resolution=30,
        epsg=32720,
        bounds_latlon=bbox
    )
)

Array	Chunk

Bytes	0 B	0 B
Shape	(0, 0, 5181, 5157)	(0, 0, 4096, 4096)
Count	10 Tasks	4 Chunks
Type	float64	numpy.ndarray

Here's a reproducer:
import pystac_client
import shapely.geometry
import stackstac

catalog = pystac_client.Client.open("https://planetarycomputer.microsoft.com/api/stac/v1")

bbox = (-67.008753, -9.96445, -65.615556, -8.57408)

tile = shapely.geometry.mapping(shapely.geometry.box(*bbox))

search = catalog.search(
    intersects=tile,
    datetime="2020-01-01/2020-12-31",
    collections=["landsat-8-c2-l2"],
    limit=1000,
    query={'landsat:collection_category': {'eq': 'T1'}}
)
items = search.get_all_items()

data = (
    stackstac.stack(
        items,
        chunksize=4096,
        resolution=30,
        epsg=32719,
        bounds_latlon=bbox
    )
)

data.shape

Which outputs (0, 0, 5170, 5145).
Here's a plot of the items and the bbox:
import geopandas
import folium

df = geopandas.GeoDataFrame.from_features(items.to_dict(), crs="epsg:4326")[["geometry", "proj:epsg"]]
m = df.explore(style_kwds={"fill": False}, column="proj:epsg")
layer = folium.GeoJson(tile)
layer.add_to(m)
m

If you leave off the bounds_latlon then things seem OK, so possibly some poor interaction between bounds_latlon and epsg when it needs to reproject.

I think it's more of an issue with bounds_latlon, If I add query={'proj:epsg': {'eq': 32720}} to the code and limit the image s to one UTM zone, I still get an empty array whenever bounds_latlon is specified, even without specifying epsg.

A quick update, seems like the problem is not really related to multiple UTM zones. The problem is unique to UTM South Zones.

Ah, that's likely https://github.com/stactools-packages/landsat/issues/12 then.
That's fixed in an upcoming release (it's deployed to our staging STAC API at planetarycomputer-staging.microsoft.com)
import pystac_client
import shapely.geometry
import stackstac

catalog = pystac_client.Client.open("https://planetarycomputer-staging.microsoft.com/api/stac/v1")

bbox = (-67.008753, -9.96445, -65.615556, -8.57408)

tile = shapely.geometry.mapping(shapely.geometry.box(*bbox))

search = catalog.search(
    intersects=tile,
    datetime="2020-01-01/2020-12-31",
    collections=["landsat-c2-l2"],
    limit=1000,
    query={'landsat:collection_category': {'eq': 'T1'}}
)
items = search.get_all_items()

data = (
    stackstac.stack(
        items,
        chunksize=4096,
        resolution=30,
        epsg=32719,
        # bounds_latlon=bbox
    )
)

data.shape

Note that the name of the collection is landsat-c2-l2, rather than landsat-8-c2-l2 since this includes results from all of Landsat Collection 2 (including Landsat 9).
That should be released to production later this week.
@gjoseph92 you can safely close this. The issues just with the STAC metadata (again)

Thanks for doing the research @TomAugspurger and @xjtang!
Just to clarify, the problem is that according to the STAC metadata, none of those items actually overlap with the bounding box?
I'm wondering if there should be any behavior change in stackstac to make this clearer?


[5.0][stdlib] Remove Swift 3-only Compatibility Shims

Cherry pick of #21019.
The ABI changes are false positives. These are method deletions and none have been callable since 3.0 support was removed.
Pulling this into 5.0 as it has library size benefits and found to improve some odd type diagnostic errors.

@swift-ci please test

@swift-ci please test source compatibility

Build failed
Swift Test OS X Platform
Git Sha - 58449109f37deacc01d03bf06413df86b11a2d34

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - 58449109f37deacc01d03bf06413df86b11a2d34

@swift-ci please test

@swift-ci please test

Build failed
Swift Test OS X Platform
Git Sha - f718a851d28a34de96aca605649748954c3c3b4b


Iox #1036 in place creation for shared memory

Pre-Review Checklist for the PR Author

[x] Code follows the coding style of CONTRIBUTING.md
[x] Tests follow the best practice for testing
[x] Changelog updated in the unreleased section including API breaking changes
[x] Branch follows the naming format (iox-#123-this-is-a-branch)
[x] Commits messages are according to this guideline

[x] Commit messages have the issue ID (iox-#123 commit text)
[x] Commit messages are signed (git commit -s)
[x] Commit author matches Eclipse Contributor Agreement (and ECA is signed)

[x] Update the PR title

Follow the same conventions as for commit messages
Link to the relevant issue

[x] Relevant issues are linked
[x] Add sensible notes for the reviewer
[x] All checks have passed (except task-list-completed)
[x] Assign PR to reviewer

Notes for Reviewer
This PR introduces the SharedMemoryBuilder for the SharedMemory class and removes the creation pattern. Furthermore, the leading slash requirement is fixed as well which closes #439
Checklist for the PR Reviewer

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code according to our coding style and naming conventions
[ ] Unit tests have been written for new behavior

[ ] Each unit test case has a unique UUID

[ ] Public API changes are documented via doxygen
[ ] Copyright owner are updated in the changed files
[ ] PR title describes the changes

Post-review Checklist for the PR Author

[ ] All open points are addressed and tracked via issues

References

Closes #439

@elBoberido I created the pull request #1059 and a separate issue which only handles the C++17 perms enum class.


Add authorization to function worker REST endpoints

Motivation
Currently, some of the REST endpoints for the worker does have perform any authorization checks.  However, these endpoints are to help cluster admins debug the cluster and contain internal information about the cluster.
Modifications
Add authorization to these endpoints so that only a cluster admin can access these endpoints

rerun java8 tests


docs(spec): revert next spec release

This PR reverts https://github.com/asyncapi/website/pull/1278/files to its previous state
@derberg

just remove v2.5.0-next-spec.5.md completely

just remove v2.5.0-next-spec.5.md completely

Then v2.5.0 would be missing 🤔

oh yes, I did not notice last Pr renamed the file. So do not remove but rename to v2.5.0.md

Done!


Fixed 'forEach' member function problem.

forEach was created as a function, where all the other
member functions are created inline. For whatever reason
this was causing a parsing error when used from webpack
and typescript.
The error as printed was:
"
ERROR in ./src/lru.js 227:10
Module parse failed: Unexpected token (227:10)
You may need an appropriate loader to handle this file type, currently no loaders are configured to process this file. See https://webpack.js.org/concepts#loaders
|   }
|

forEach = function(fun, thisObj) {
|     if (typeof thisObj !== 'object') {
|       thisObj = this;
@ ./src/index.ts 9:12-28
"

This change fixes the problem.

Duplicate of https://github.com/rsms/js-lru/pull/36


feat: Add segment by rect

:tada: This PR is included in version 1.0.0 :tada:
The release is available on npm package (@latest dist-tag)
Your semantic-release bot :package::rocket:


Run tests

How to run all tests (no only in unit group)? Documentation is missing that

I add this to documentation. See bae28103dd83b5fe9e0d10ff2ec3d42249557918

Thx


grafana-watcher: retry failed updates from ConfigMap changes

Currently, an update will only be partially applied if an
error occurs in one of the handler routines. The grafana
system will be left in a dirty intermediate state until
the ConfigMap is updated again. This change will retry failed updates
until all scheduled updates have succeeded OR until the ConfigMap
is changed again.
This log file from the grafana-watcher container in the grafanaXXX pod from a kube-prometheus deployment shows the retry loop working correctly (I have no idea why I get so many timouts T_T):
2017/08/04 20:45:25 Waiting for Grafana to be available.
2017/08/04 20:45:41 Initializing datasources.
2017/08/04 20:45:41 Retrieving existing datasources
2017/08/04 20:45:41 Deleting 0 datasources
2017/08/04 20:45:41 Creating datasource from: /var/grafana-dashboards/prometheus-datasource.json
2017/08/04 20:45:42 Initializing dashboards.
2017/08/04 20:45:42 Retrieving existing dashboards
2017/08/04 20:45:58 Deleting 0 dashboards
2017/08/04 20:45:58 Creating dashboard from: /var/grafana-dashboards/all-nodes-dashboard.json
2017/08/04 20:45:58 Creating dashboard from: /var/grafana-dashboards/deployment-dashboard.json
2017/08/04 20:46:24 Creating dashboard from: /var/grafana-dashboards/kubernetes-pods-dashboard.json
2017/08/04 20:46:50 Creating dashboard from: /var/grafana-dashboards/node-dashboard.json
2017/08/04 20:47:06 Creating dashboard from: /var/grafana-dashboards/resource-requests-dashboard.json
2017/08/04 20:47:12 Starting...
2017/08/04 20:48:32 ConfigMap modified
2017/08/04 20:48:32 Retrieving existing dashboards
2017/08/04 20:49:02 error: Get http://admin:admin@localhost:3000/api/search: dial tcp: i/o timeout
2017/08/04 20:49:02 Retrieving existing datasources
2017/08/04 20:49:17 Deleting 1 datasources
2017/08/04 20:49:17 Deleting datasource: 1
2017/08/04 20:49:18 Creating datasource from: /var/grafana-dashboards/prometheus-datasource.json
2017/08/04 20:49:29 Retrieving existing dashboards
2017/08/04 20:49:44 Deleting 5 dashboards
2017/08/04 20:49:44 Deleting dashboard: all-nodes
2017/08/04 20:49:45 Deleting dashboard: deployment
2017/08/04 20:50:10 error during retry attempt: Delete http://admin:admin@localhost:3000/api/dashboards/db/deployment: dial tcp [::1]:3000: connect: cannot assign requested address
2017/08/04 20:50:20 Retrieving existing dashboards
2017/08/04 20:50:31 Deleting 4 dashboards
2017/08/04 20:50:31 Deleting dashboard: deployment
2017/08/04 20:50:31 Deleting dashboard: nodes
2017/08/04 20:51:01 error during retry attempt: Delete http://admin:admin@localhost:3000/api/dashboards/db/nodes: dial tcp: i/o timeout
2017/08/04 20:51:11 Retrieving existing dashboards
2017/08/04 20:51:41 error during retry attempt: Get http://admin:admin@localhost:3000/api/search: dial tcp: i/o timeout
2017/08/04 20:51:51 Retrieving existing dashboards
2017/08/04 20:52:21 error during retry attempt: Get http://admin:admin@localhost:3000/api/search: dial tcp: i/o timeout
2017/08/04 20:52:31 Retrieving existing dashboards
2017/08/04 20:52:57 Deleting 3 dashboards
2017/08/04 20:52:57 Deleting dashboard: nodes
2017/08/04 20:52:57 Deleting dashboard: pods
2017/08/04 20:53:18 Deleting dashboard: resource-requests
2017/08/04 20:53:48 error during retry attempt: Delete http://admin:admin@localhost:3000/api/dashboards/db/resource-requests: dial tcp: i/o timeout
2017/08/04 20:53:58 Retrieving existing dashboards
2017/08/04 20:54:24 Deleting 1 dashboards
2017/08/04 20:54:24 Deleting dashboard: resource-requests
2017/08/04 20:54:25 Creating dashboard from: /var/grafana-dashboards/all-nodes-dashboard.json
2017/08/04 20:54:55 Creating dashboard from: /var/grafana-dashboards/deployment-dashboard.json
2017/08/04 20:55:15 Creating dashboard from: /var/grafana-dashboards/kubernetes-pods-dashboard.json
2017/08/04 20:55:45 Creating dashboard from: /var/grafana-dashboards/node-dashboard.json
2017/08/04 20:56:06 Creating dashboard from: /var/grafana-dashboards/resource-requests-dashboard.json

Due to some changes in our CI infrastructure this will also need a rebase.

thanks for heads up - will rebase changes tonight

Updated to use a ticker (though default has one advantage as mentioned in my other reply, let me know your thoughts on that). Confirmed still works by killing grafana-server immediately after ConfigMap update to force some operations to fail:
2017/08/11 19:30:13 ConfigMap modified
2017/08/11 19:30:13 Retrieving existing dashboards
2017/08/11 19:30:13 error: Get http://admin:admin@localhost:3000/api/search: dial tcp [::1]:3000: getsockopt: connection refused
2017/08/11 19:30:13 Retrieving existing datasources
2017/08/11 19:30:13 error: Get http://admin:admin@localhost:3000/api/datasources: dial tcp [::1]:3000: getsockopt: connection refused
2017/08/11 19:30:20 Retrying 2 previously failed operations...
2017/08/11 19:30:20 Retrieving existing dashboards
2017/08/11 19:30:21 Deleting 0 dashboards
2017/08/11 19:30:21 Creating dashboard from: /var/grafana-dashboards/all-nodes-dashboard.json
2017/08/11 19:30:22 Creating dashboard from: /var/grafana-dashboards/deployment-dashboard.json
2017/08/11 19:30:22 Creating dashboard from: /var/grafana-dashboards/kubernetes-pods-dashboard.json
2017/08/11 19:30:23 Creating dashboard from: /var/grafana-dashboards/node-dashboard.json
2017/08/11 19:30:24 Creating dashboard from: /var/grafana-dashboards/resource-requests-dashboard.json
2017/08/11 19:30:24 Retrieving existing datasources
2017/08/11 19:30:25 Deleting 0 datasources
2017/08/11 19:30:25 Creating datasource from: /var/grafana-dashboards/prometheus-datasource.json

ok, after latest rebase should be conflict-free and ready to go - let me know if anything else needed here

@brancz does this look good now?

Sorry for not getting back to this! The code lgtm. Could you just bump the grafana-watcher version used throughout this repo, so I can just publish the new image right before I merge this PR?

Ok, should be bumped everywhere, looks like these were the 3 where bump needed:
	modified:   contrib/grafana-watcher/examples/grafana-bundle.yaml
	modified:   contrib/kube-prometheus/manifests/grafana/grafana-deployment.yaml
	modified:   helm/grafana/templates/grafana-deployment.yaml

Perfect! Will push the image and then merge the PR. Thanks a lot for all your efforts!


feat: implement shm size adjustment

Describe your changes
This PR implements two things:

Adding a /dev/shm volume to the StatefulSet
The option to adjust /dev/shm in the CRD

Issue ticket number and link
Closes #630
Part of https://github.com/SwissDataScienceCenter/renku/issues/3679

Do we want that to be mandatory or an option ?
I get that this was always mounted in the previous implementation though I am not sure this is always needed. Any inputs ?

Do we want that to be mandatory or an option ?

I get that this was always mounted in the previous implementation though I am not sure this is always needed. Any inputs ?

Actually I think @SalimKayal is right, it is probably better to not always have this. I know people want this when they use tensorflow/pytorch but whether they always need it or only when they are doing something fancier like using multiple gpus I cannot remember.
@sgaist what do you think?

@olevski I agree as well, it will also make the session lighter on resource.

Thanks this looks good. But there is a merge conflict. So let me know and I will re-approve when you resolve it.

Done, the tests were conflicting :-)


[FLINK-24697][flink-connectors-kafka] add auto.offset.reset configuration for group-offsets startup mode

What is the purpose of the change
This PR provides the way to change the 'auto.offset.reset' for kafka table source when use 'group-offsets' startup mode .
When 'auto.offset.reset' is set, the 'group-offsets' startup mode will use the provided auto offset reset strategy, or else 'none' reset strategy in order to be consistent with the DataStream API.
Brief change log

When 'auto.offset.reset' is set, the 'group-offsets' startup mode will use the provided auto offset reset strategy, or else 'none' reset strategy as default

Verifying this change

Added test that validates that the 'auto.offset.reset' is set for kafka consumers

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (no)
The serializers: (no)
The runtime per-record code paths (performance sensitive): (no)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (no)
The S3 file system connector: (no)

Documentation

Does this pull request introduce a new feature? (no)

@flinkbot run azure

When to merge this PR？

@fapaul Could you help to review this PR?
By the way, please assign this ticket to me in the JIRA.

@flinkbot run azure

@flinkbot run azure

@flinkbot run azure


Issues when using interfuser agent with route_based scenario from scenario runner

Hello, hope you are doing well, thanks for your great work, I've been trying to use the Interfuser agent lately with the pretrained part, I could make the leaderboard evaluator work successfully, but unfortunately for some reason, using it as an agent with route-based scenarios is still not possible for me, I have been facing this issue related to sensors:
PS C:\Users\taha\Desktop\scenario_runner-0.9.10\scenario_runner-0.9.10> python scenario_runner.py --route C:\Users\taha\Desktop\scenario_runner-0.9.10\scenario_runner-0.9.10\srunner\data\routes_training.xml C:\Users\taha\Desktop\scenario_runner-0.9.10\scenario_runner-0.9.10\srunner\data\all_towns_traffic_scenarios.json 7 --agent C:\Users\taha\Desktop\InterFuser\InterFuser\leaderboard\team_code\interfuser_agent.py --agentConfig C:\Users\taha\Desktop\InterFuser\InterFuser\leaderboard\team_code\interfuser_config.py
pygame 2.1.2 (SDL 2.0.18, Python 3.7.9)
Hello from the pygame community. https://www.pygame.org/contribute.html
load model: C:/Users/taha/Desktop/InterFuser/InterFuser/leaderboard/team_code/interfuser.pth.tar
42routes_07_07_16_11_45
Preparing scenario: RouteScenario_7
Traceback (most recent call last):
File "scenario_runner.py", line 398, in _load_and_run_scenario
self.manager.load_scenario(scenario, self.agent_instance)
File "C:\Users\taha\Desktop\scenario_runner-0.9.10\scenario_runner-0.9.10\srunner\scenariomanager\scenario_manager.py", line 112, in load_scenario
self._agent.setup_sensors(self.ego_vehicles[0], self._debug_mode)
File "C:\Users\taha\Desktop\scenario_runner-0.9.10\scenario_runner-0.9.10\srunner\autoagents\agent_wrapper.py", line 81, in setup_sensors
sensor.listen(CallBack(sensor_spec['id'], sensor, self._agent.sensor_interface))
File "C:\Users\taha\Desktop\scenario_runner-0.9.10\scenario_runner-0.9.10\srunner\autoagents\sensor_interface.py", line 31, in init
self._data_provider.register_sensor(tag, sensor)
TypeError: register_sensor() missing 1 required positional argument: 'sensor'
register_sensor() missing 1 required positional argument: 'sensor'
No more scenarios .... Exiting
I also face this error when I try to run these scenarios with dummy agent, which is a strange one because dummy agent and agent wrapper should be consistent, but it has these errors because of sensors too.
python scenario_runner.py --route C:\Users\taha\Desktop\scenario_runner-0.9.10\scenario_runner-0.9.10\srunner\data\routes_training.xml C:\Users\taha\Desktop\scenario_runner-0.9.10\scenario_runner-0.9.10\srunner\data\all_towns_traffic_scenarios.json 7 --agent C:\Users\taha\Desktop\scenario_runner-0.9.10\scenario_runner-0.9.10\srunner\autoagents\dummy_agent.py
Preparing scenario: RouteScenario_7
Traceback (most recent call last):
File "scenario_runner.py", line 398, in _load_and_run_scenario
self.manager.load_scenario(scenario, self.agent_instance)
File "C:\Users\taha\Desktop\scenario_runner-0.9.10\scenario_runner-0.9.10\srunner\scenariomanager\scenario_manager.py", line 112, in load_scenario
self._agent.setup_sensors(self.ego_vehicles[0], self._debug_mode)
File "C:\Users\taha\Desktop\scenario_runner-0.9.10\scenario_runner-0.9.10\srunner\autoagents\agent_wrapper.py", line 61, in setup_sensors
bp.set_attribute('range', str(sensor_spec['range']))
KeyError: 'range'
'range'
No more scenarios .... Exiting
I found in LAV agent that you should add vulkan flag and this also generates an issue for me, is it also needed to run interfuser or there is something i'm doing wrong that I don't know.
Thank you in advance.

Hi!
Could you provide more information about your setting and why did you need to run "python scenario_runner.py"? I'm not familiar with this entry script. The two problems look like the reason is the sensors' error set. The correct set can refer tohttps://github.com/opendilab/InterFuser/blob/4145d6ca58c19ce2a29d319c47980cea05586b06/leaderboard/team_code/interfuser_agent.py#L244 .If you need to specify the test routes or scenarios, modifying the environmental varieties in the evaluation script is just ok.

Hello! Thank you for your reply.
python scenario_runner.py
--route C:\Users\taha\Desktop\InterFuser\InterFuser\leaderboard\data\training_routes\routes_town05_long.xml C:\Users\taha\Desktop\InterFuser\InterFuser\leaderboard\data\scenarios\town05_all_scenarios.json 16
--agent C:\Users\taha\Desktop\InterFuser\InterFuser\leaderboard\team_code\interfuser_agent.py
--agentConfig C:\Users\taha\Desktop\InterFuser\InterFuser\leaderboard\team_code\interfuser_config.py
In this command, I am running scenario runner in order to run a route-based scenario with interfuser as an agent like specified in the code inside scenario runner:
parser.add_argument(
'--route', help='Run a route as a scenario (input: (route_file,scenario_file,[route id]))', nargs='+', type=str)
parser.add_argument(
'--agent', help="Agent used to execute the scenario. Currently only compatible with route-based scenarios.")    parser.add_argument('--agentConfig', type=str, help="Path to Agent's configuration file", default="")
This way, we could use autonomous_agent and human_agent from autoagents folder with those scenarios and it worked fine, but we had problems when agents need sensors even if we're using exactly the same files from the github link and we did change the environment variables to look for the scenario runner inside interfuser folder. If there is still something unclear about our situation, please feel free to ask.
Thank you!

Hi!
I'm very sorry that I cannot solve your problem. The issue is not from the Interfuser itself and I have never used scenario_runner.py to evaluate the agent before. However, I have some suggestions which may help you:

Raise an issue in these repos: https://github.com/carla-simulator/carla https://github.com/carla-simulator/scenario_runner
Upgrade/ Degrade the version of scenario_runner
After running the agents with sensors successfully, you may try to use the Interfuser agent again.


Investigate backend's verbose logging performance

Nowadays, we recommend (not only) Enso developers to run LS/Engine with very verbose logging enabled, as described in https://github.com/enso-org/enso/blob/develop/docs/CONTRIBUTING.md#turning-on-verbose-logs. Additional logging should not affect performance. @jdunkerley reported that on his machine, running project-manager with
.\built-distribution\enso-project-manager-0.0.0-dev-windows-amd64\enso\bin\project-manager.exe -vv 2>&1 | out-null

Still feels more sluggish than running the project-manager without very verbose logs enabled.
We should investigate the cause of this performance decrease. Log collection should have a negligible impact on the performance, as we strive to collect as many logs as possible.

@jdunkerley to run the profiler.
Start Visual VM and sample for a while while running it in loggy mode

Will most probably be solved by https://github.com/enso-org/enso/issues/7253

Will gather some feedback from users now that the new integration is merged.

Apparently, Windows still has problems with verbose logging. Currently lowered to DEBUG.


Opening access to the wiki

Good on-boarding documentation is key to smooth the welcoming of new users.
Documentation on installation steps exists on the website but to allow quick documentation on commons problems that can occur from different setups a wiki is key to allow users to share their solutions from problems they faced and solved for other users to benefit from their experiences.
A wiki tab exists but is not accessible probably because no pages were created but also because "Only repository collaborators can edit a public repository's wiki by default, but you can allow anyone with a GitHub account to edit your wiki." --The Github documentation.
A quick fix will be to follow the steps of the documentation cited.

Wiki has been opened and a first initial page created. I'm not sure what you thought would be good here as much is on the official documentation: pymodaq.cnrs.fr

I saw that the wiki could be another way, this time for users, to contribute to documentation in a low-bar way, to document difficulties and solutions they found.  Not a replacement for any existing system.
It is a parallel way to document different experiences : API reference for the official website, troubleshooting tips and general advice for the wiki.
I will be, for my part, adding steps to document my journey for a Nix script for building pyMoDAQ to improve reproducibility on system using Nix package manager.

Alright but it seems only owners can update the wiki...

The documentation, cited in the original post, reads (emphasis mine) : "Only repository collaborators can edit a public repository's wiki by default, but you can allow anyone with a GitHub account to edit your wiki."

From the repo settings, here it is:

So is it editable yet? I cannot check actually! (I did it unsigned but obviously it didn't work)

Given the revision I succeed to make the wiki seems functional! :partying_face:


Respose::sendFile() does not correctly generate Content-Disposition header for UTF8 filenames with character 127

What steps will reproduce the problem?
Execute Respose::sendFile() with a filename containing US-ASCII character with code 127 (hex 7F).
What is the expected result?
Generated response does not contain Content-Disposition HTTP header with a character 127.
Successful file download (no errors).
What do you get instead?
Generated response contains Content-Disposition HTTP header with a character 127. This leads to Internal Server Error 500 under Apache httpd server.
For more info see https://github.com/yiisoft/yii2/issues/10563#issuecomment-457332342.
Additional info

Q
A

Yii version
<IP_ADDRESS>

PHP version
7.3.1

Operating system
Windows 10

This character is considered as invalid by Apache, there is nothing we can do about it.
AH02430: Response header 'Test2' value of '-\x7f-.txt' contains invalid characters, aborting request

We can only just strip that character from the filename. What do you think?

The reason why apache shows 500 error is that it considers this character as invalid and it is actually correctly converted to utf-8 by the Response class but the error is caused by fallback name where this character is added as is, so we need to strip it.
Here is the current value of the Content-Disposition header
attachment; filename="-\x7f-.txt"; filename*=utf-8''-%7F-.txt

And we need to change it like this:
attachment; filename="-_-.txt"; filename*=utf-8''-%7F-.txt

Then the correct filename will be used but in the end, it will get converted by the browser (at least Chrome) to "-_-.txt" after saving in any case.


UVI Request

--- UVI JSON ---
{
  "vendor_name": "Linux",
  "product_name": "Kernel",
  "product_version": "versions from v4.20 to before v5.4.135",
  "vulnerability_type": "unspecified",
  "affected_component": "unspecified",
  "attack_vector": "unspecified",
  "impact": "unspecified",
  "credit": "",
  "references": [
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=61414f5ec9834df8aa4f55c90de16b71a3d6ca8d",
    "https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?id=04b06716838bfc26742dbed3ae1d3697fe5317ee"
  ],
  "extended_references": [
    {
      "type": "commit",
      "value": "61414f5ec9834df8aa4f55c90de16b71a3d6ca8d",
      "note": "introduced"
    },
    {
      "type": "commit",
      "value": "04b06716838bfc26742dbed3ae1d3697fe5317ee",
      "note": "fixed"
    }
  ],
  "reporter": "joshbressers",
  "reporter_id": 1692786,
  "notes": "",
  "description": "net: fddi: fix UAF in fza_probe\n\nThis is an automated ID intended to aid in discovery of potential security vulnerabilities. The actual impact and attack plausibility have not yet been proven.\nThis ID is fixed in Linux Kernel version v5.4.135 by commit 04b06716838bfc26742dbed3ae1d3697fe5317ee, it was introduced in version v4.20 by commit 61414f5ec9834df8aa4f55c90de16b71a3d6ca8d. For more details please see the references link."
}
--- UVI JSON ---

This issue has been assigned UVI-2021-1001319


Server Disconnected (Code 1006)

Everything was working fine until a few days ago.  When I try to open CrashPlan, I get a white screen with the VNC toolbar on the top.  Server Disconnected (Code 1006) is all the closest thing to any feedback that the screen gives me.  I've tried using RealVNC to connect to the listening port, and no luck there.  The docker logs seem to indicate it's happy and listening.  I'm running this in UnRaid if that makes a difference.  I've tried restarting the docker and server for good measure.

Can you try to clear your browser's cache and/or try with another browser?

have the same issue... cleared the cache and deleted and recreated the container downloaded a recent image... same issue.

@KamikazeFighter, are you using the latest version of Chrome?  On Windows I guess?
@ahiguero, did you try with a different browser?

please disregard, my issue is solved , had another service that "hijacked"
the vnc port. my apologies. my issue has been solved.
On Wed, Nov 21, 2018 at 4:45 AM Jocelyn Le Sage<EMAIL_ADDRESS>wrote:

@KamikazeFighter https://github.com/KamikazeFighter, are you using the
latest version of Chrome? On Windows I guess?
@ahiguero https://github.com/ahiguero, did you try with a different
browser?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jlesage/docker-crashplan-pro/issues/141#issuecomment-440619188,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AInIcfaG8U9u4uOKI0ObMcNz89gSF3x1ks5uxS7JgaJpZM4Xyr_p
.

My Chrome is auto updating (like normal Chrome).  I just checked it again,
and the problem seems to have resolved since I first reported it.  For a
while, IE would would work but Chrome stopped working.  I'll chalk it up to
an oddity for now I guess, since I can't recreate the problem.
On Wed, Nov 21, 2018 at 5:45 AM Jocelyn Le Sage<EMAIL_ADDRESS>wrote:

@KamikazeFighter https://github.com/KamikazeFighter, are you using the
latest version of Chrome? On Windows I guess?
@ahiguero https://github.com/ahiguero, did you try with a different
browser?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jlesage/docker-crashplan-pro/issues/141#issuecomment-440619188,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Am-nM6BtfvEb7_Bnj0t7I_QBgMmX0OIOks5uxS7JgaJpZM4Xyr_p
.

I have the same issue and i tried it on edge an chrome (latest versions). Any suggestions?
https://ibb.co/xSHT0L9

Closing this issue.  Please re-open if needed.


Is there any way to trigger another datepicker by clicking the first datepicker?

I have created two popup datepickers(two input fields). I am curious if the second datepicker can be triggered to open automatically once I choose a date from the first datepicker for the first input. The scenario will be like below:

click the first input box(first datepicker). The first datepicker shows up.
choose a date from the first datepicker. This datepicker will close and the date I choose will be filled into the first input box.
the second datepicker will open automatically once the first datepicker closes and the date fills into input box.
I can choose date from the second datepicker for the second input box.

If there is any way and anyone can provide a solution will be much appreciated! A brief example will be awesome! Thanks!

https://github.com/angular-ui/bootstrap#need-help


Node v14+ support and fix for TypeScript and EventEmitter

Node v14 is the active LTS and it switches to "maintenance" tomorrow, making Node v16 the current LTS as of Tuesday. It would be great to be able to upgrade the project so it builds without errors. When I try, I get the following:
node_modules/@fluent-org/logger/build/src/server.d.ts:63:43 - error TS2507: Type 'typeof EventEmitter' is not a constructor function type.

63 export declare class FluentServer extends EventEmitter {
                                             ~~~~~~~~~~~~

node_modules/@fluent-org/logger/build/src/socket.d.ts:164:43 - error TS2507: Type 'typeof EventEmitter' is not a constructor function type.

164 export declare class FluentSocket extends EventEmitter {
                                              ~~~~~~~~~~~~

Found 2 errors.

From what I see at DefinitelyTyped, the upgrade at 13.4 or 13.5 caused issues. Geckos.io has a simple fix, as does cheap-watch. It basically means you have to change the import line.
// Old
import * as EventEmitter from "events";

// New
import { EventEmitter } from 'events';

Sorry for taking so long on this, I finally found some time, and addressed this in the recently cut v1.0.4 :) Let me know if that works for you!

This still seems to be an issue in node 16. Was this fixed?


Remove unnecessary options from transform-package tests

Just some minor changes removing unnecessary options. I guess it's up to you whether you want these changes, but I think it's best to keep things minimal!

Codecov Report

Merging #137 into use-transform will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff               @@
##           use-transform     #137   +/-   ##
==============================================
  Coverage          97.63%   97.63%
==============================================
  Files                  2        2
  Lines                169      169
==============================================
  Hits                 165      165
  Misses                 4        4

Continue to review full report at Codecov.

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


Add creationTime to Status for ScalableTarget and ScalingPolicy resources

Issue #, if available:
aws-controllers-k8s/community#932
Description of changes:
Add creationTime to Status for ScalableTarget and ScalingPolicy resources based off of code gen changes in this PR.
TODO: Add required check to the existing integration test.
Testing
Manually tested that the field is present in the Status of the kubectl get response.
Kind tests pass locally
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

+1 need to make sure creation and last modified time are reported in the same time zone
if they are not, we can overwrite the creation time in custom code similar to modified time

Sure, but I am creating a separate PR for that since this is also a demo of the associated Code-gen change.


ODBC Support for Serverless

Does the latest version of the ODBC driver support Synapse Serverless?  I see Synapse Analytics at the top, but when I try to connect to Serverless with ODBC it errors out for me.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a36a1d7f-a410-b597-0eb7-98212934fb0e
Version Independent ID: e706f2bd-e051-fcff-7c3d-2ef3d9f80e87
Content: Download ODBC Driver for SQL Server - SQL Server
Content Source: docs/connect/odbc/download-odbc-driver-for-sql-server.md
Product: sql
Technology: connectivity
GitHub Login: @David-Engel
Microsoft Alias: v-daenge

@furlong46 -- Leo, thank you for your question.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

@David-Engel -- David, please look into this issue.

@furlong46 -- Leo, thank you for your question.  Please consider these resources:

SQL Server on Microsoft Q&A
DBA Stack Exchange
Stack Overflow

@David-Engel -- David, please look into this issue.

@furlong46
The Microsoft ODBC Driver for SQL Server does not differentiate between provisioned and serverless Synapse instances.
My understanding of the issue with Azure Synapse serverless is that since there is no constantly provisioned resource behind it, when the database is in a paused state, the first connection request to the database may fail or take longer than the default connection timeout period used by the ODBC driver (all drivers, really). So your application needs to be able to handle the initial error(s) and retry until the database is fully available. There is desire to add functionality to the driver to be able to recognize these errors itself and implement transparent retry logic for applications, but the driver does not currently have that capability.
Regards,
David

@furlong46
The Microsoft ODBC Driver for SQL Server does not differentiate between provisioned and serverless Synapse instances.
My understanding of the issue with Azure Synapse serverless is that since there is no constantly provisioned resource behind it, when the database is in a paused state, the first connection request to the database may fail or take longer than the default connection timeout period used by the ODBC driver (all drivers, really). So your application needs to be able to handle the initial error(s) and retry until the database is fully available. There is desire to add functionality to the driver to be able to recognize these errors itself and implement transparent retry logic for applications, but the driver does not currently have that capability.
Regards,
David

The connection works just fine, but it fails when I try and link an actual table.

The connection works just fine, but it fails when I try and link an actual table.

@furlong46 That's interesting. I think this is an issue with serverless not supporting that specific procedure used by the driver. See the note on this doc page for that procedure:
https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-special-columns-100-sql-data-warehouse?view=azure-sqldw-latest

This would affect the ability of many drivers to support browse-mode type functionality in applications. You can probably still write and execute SQL manually, though. The "#15871" in the error message from the server indicates to me that the Synapse team probably is aware of the issue. You could raise an issue with Microsoft Support to be certain.
This does not appear to be an ODBC documentation issue.

@furlong46 That's interesting. I think this is an issue with serverless not supporting that specific procedure used by the driver. See the note on this doc page for that procedure:
https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-special-columns-100-sql-data-warehouse?view=azure-sqldw-latest

This would affect the ability of many drivers to support browse-mode type functionality in applications. You can probably still write and execute SQL manually, though. The "#15871" in the error message from the server indicates to me that the Synapse team probably is aware of the issue. You could raise an issue with Microsoft Support to be certain.
This does not appear to be an ODBC documentation issue.

Closing since this isn't an ODBC driver doc issue.
#please-close

Closing since this isn't an ODBC driver doc issue.
#please-close


*: Count used / alloc memory per query.

AC:

In order to ensure isolation and limits some day, as a first step we want to measure memory we use per query on all component
API response should have it (similar to query stats)

To track on next issue:

Present that on UI

yolo statistics I want to focus on per request (e.g query):
message Usage {
    uint64 memory_alloc_bytes = 1 [(gogoproto.jsontag) = "memoryAllocBytes" ];
    uint64 memory_max_used_bytes = 2 [(gogoproto.jsontag) = "memoryMaxUsedBytes" ];

    uint64 network_sent_bytes = 3 [(gogoproto.jsontag) = "networkSentBytes" ];
    uint64 network_recv_bytes = 4 [(gogoproto.jsontag) = "networkRecvBytes" ];

    uint64 go_routines_used = 5 [(gogoproto.jsontag) = "goRoutinesUsed" ];
    uint64 go_routines_max_used = 6 [(gogoproto.jsontag) = "goRoutinesMaxUsed" ];

    uint64 rpc_services_visited = 7 [(gogoproto.jsontag) = "rpcServicesVisited" ];
}

Tracking memory in Go is hard, but the ideas are to least know estimation OR know on how many samples / series were touched on storage.


Added patch to cluster-autoscaler configmaps

Fixes a permissions issue when scaling down.

Hmm, interesting. It scaled down well for me without the patch permission. Anyway, should be fine to merge this. Thanks for the PR.


update canonicalizeLocale to handle 中文(chinese)

J=SLAP-1526
TEST=auto,manual
unit tests
ran build with zh-hans-ch in locale config, saw that the generated source code used the correct locale in the page
tried building a page with a locale with >3 sections, got a jambo warning but build continued without changing the locale

Coverage increased (+0.1%) to 46.869% when pulling 3d312a7ea4d2d792da6534ac82da21637e2a81ea on dev/canonicalize-locale-handle-zhongwen into 2d76f4dfb0828656fdb757b3c934378e964927f8 on develop.

was testing in the theme and this doesn't handle zh-Hans correctly (i.e. chinese w/ no region code)


What backend does TGI use?

Hi TGI team!
Just a quick question -- what backends does TGI use? e.g. TensorRT LLM, vLLM, etc. Curious to know which technologies are currently used :D
Cheers,
Brian

AFAIK it uses the HuggingFace transformers one.

Hi @brianyu-nexusflowai 👋
Thank's for asking a good question 👍 We've made a lot of changes lately but in short:

by default we use the TGI python backend server here https://github.com/huggingface/text-generation-inference/tree/main/server it's the one we've had "always".  It has all the bells & whistles with optimizes attention kernels etc.
For this one if there isn't a optimized implementation of a model the fallback would be the transformers implementation.
TensorRT LLM: https://github.com/huggingface/text-generation-inference/tree/main/backends/trtllm was recently added

Hopefully this helps uncover this a bit :)

Hi @ErikKaum !
Yes it does, thank you so much for the response. Excited to see what you guys are cooking :eyes:
Brian


AADSTS65005 not listed

> AADSTS650052: The app needs access to a service ("https://myapp.myservice.com") that your organization "xxxxxxxx-xxxx-xxxx-xxxx-xxxxxxxxxxxx" has not subscribed to or enabled. Contact your IT Admin to review the configuration of your service subscriptions.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: a826ee6f-f457-7109-9f77-67c57977d4e7
Version Independent ID: 11766f27-492e-a579-dced-8a42528cbb47
Content: Azure AD authentication & authorization error codes
Content Source: articles/active-directory/develop/reference-aadsts-error-codes.md
Service: active-directory
Sub-service: develop
GitHub Login: @rwike77
Microsoft Alias: ryanwi

@aelij Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.

@aelij Thanks, just added it to the list.  Updates should publish later today. #please-close