Widget.fetch() hangs forever after a reconnect — how do I make it time out?

ines_r · 2 hours ago

It is a race in the reconnect path, there is an open issue about it.

upvote downvote reply share flag

tobiasw · 3 hours ago

This looks like the buffer size default changed between releases.

upvote downvote reply share flag

k_mbeki · 4 hours ago

Does it still happen with the async API?

upvote downvote reply share flag

rsaxena · 5 hours ago

Can you post the full traceback? The second frame matters.

upvote downvote reply share flag

olga.v · 6 hours ago

Have you checked whether the serial port is opened twice?

upvote downvote reply share flag

dmitri_p · 7 hours ago

Setting the timeout explicitly made the error go away on my board.

upvote downvote reply share flag

sunita88 · 8 hours ago

Same here. The workaround below works but it is ugly.

upvote downvote reply share flag

fjord_dev · 9 hours ago

I hit the same thing on 3.12; pinning the driver fixed it for me.

upvote downvote reply share flag

a_nakashima · 10 hours ago

It is a race in the reconnect path, there is an open issue about it.

upvote downvote reply share flag

petra_l · 11 hours ago

This looks like the buffer size default changed between releases.

upvote downvote reply share flag

cwen · 12 hours ago

Setting the timeout explicitly made the error go away on my board.

upvote downvote reply share flag

b_oduya · 13 hours ago

Have you checked whether the serial port is opened twice?

upvote downvote reply share flag

lucca_m · 14 hours ago

I hit the same thing on 3.12; pinning the driver fixed it for me.

upvote downvote reply share flag

haru_t · 15 hours ago

Same here. The workaround below works but it is ugly.

upvote downvote reply share flag

zofia_k · 16 hours ago

This looks like the buffer size default changed between releases.

upvote downvote reply share flag

emeka_o · 17 hours ago

It is a race in the reconnect path, there is an open issue about it.

upvote downvote reply share flag

yusuf.a · 18 hours ago

Can you post the full traceback? The second frame matters.

upvote downvote reply share flag

marek_n · 19 hours ago

Does it still happen with the async API?

upvote downvote reply share flag

marlow_k · 20 hours ago

Setting the timeout explicitly made the error go away on my board.

upvote downvote reply share flag

priya_s · 21 hours ago

Have you checked whether the serial port is opened twice?

upvote downvote reply share flag

jonas_h · 22 hours ago

It is a race in the reconnect path, there is an open issue about it.

upvote downvote reply share flag

aline_c · 23 hours ago

This looks like the buffer size default changed between releases.

upvote downvote reply share flag

wen_li · 24 hours ago

Does it still happen with the async API?

upvote downvote reply share flag

tomas_r · 25 hours ago

Can you post the full traceback? The second frame matters.

upvote downvote reply share flag

greta_v · 26 hours ago

Have you checked whether the serial port is opened twice?

upvote downvote reply share flag

kofi_a · 27 hours ago

Setting the timeout explicitly made the error go away on my board.

upvote downvote reply share flag

mira_d · 28 hours ago

Same here. The workaround below works but it is ugly.

upvote downvote reply share flag

sven_b · 29 hours ago

I hit the same thing on 3.12; pinning the driver fixed it for me.

upvote downvote reply share flag

lea_m · 30 hours ago

It is a race in the reconnect path, there is an open issue about it.

upvote downvote reply share flag

raj_p · 31 hours ago

This looks like the buffer size default changed between releases.

upvote downvote reply share flag

nadia_f · 32 hours ago

Can you post the full traceback? The second frame matters.

upvote downvote reply share flag

oscar_t · 33 hours ago

Does it still happen with the async API?

upvote downvote reply share flag