Bootstrap gets stuck at 20% when connecting through a bridge.
I believe this is different from all the other instances of this bug (#11965 (moved) and friends), because the client never recovers (I am using a pluggable transport that is experimental, but the symptoms don't point at my code at first glance).
Client debug log:
May 15 19:36:24.000 [debug] connection_dir_client_reached_eof(): Received response from directory server '127.0.0.1:52810': 404 "Not found" (purpose: 6)
May 15 19:36:24.000 [info] connection_dir_client_reached_eof(): Received server info (size 0) from server '127.0.0.1:52810'
May 15 19:36:24.000 [info] connection_dir_client_reached_eof(): Received http status code 404 ("Not found") from server '127.0.0.1:52810' while fetching "/tor/server/authority.z". I'll try again soon.
May 15 19:36:24.000 [debug] conn_close_if_marked(): Cleaning up connection (fd -1).
May 15 19:36:24.000 [debug] connection_remove(): removing socket -1 (type Directory), n_conns now 3
The bridge is fully bootstrapped at this point according to the logs. Bridge functionality should be fully working once the bridge bootstraps to 100% right? This does seem to happen most after I restart both the client and bridge to pick up a new build of the pt binary...
The only notable config option besides the PT is "PublishServerDescriptor 0" (A cursory search for authority.z brings up #9366 (moved)).