[quoted lines by Jaroslav Skarvada on 2016/05/12 at 05:52 -0400]
>Thanks, it works for me.
Good, I'll commit it.
>But isn't more clean to just partially revert the commit (change while/do to
>do/while), i.e. the previous patch?
No, there was a reason for the change. The order of the three actio
- Original Message -
> [quoted lines by Jaroslav Skarvada on 2016/05/11 at 12:42 -0400]
>
> >Hmm, for me the control flow reaches asyncAwaitCondition and then
> >immediately exits
> >due to the timeout. Maybe there is another/different problem.
>
> You're correct. I didn't look closely
[quoted lines by Jaroslav Skarvada on 2016/05/11 at 12:42 -0400]
>Hmm, for me the control flow reaches asyncAwaitCondition and then immediately
>exits
>due to the timeout. Maybe there is another/different problem.
You're correct. I didn't look closely enough. The timeout test shouldn't be
done
Hi,
thanks for info.
> >a) fix asyncAwaitCondition to handle zero timeouts, or
>
> It already does. Async checks for pending events before even "thinking" about
> going into a wait.
>
Hmm, for me the control flow reaches asyncAwaitCondition and then immediately
exits
due to the timeout. Maybe t
[quoted lines by Jaroslav Skarvada on 2016/05/10 at 05:23 -0400]
>what's your opinion how to fix it?
That it's still a mystery that I haven't yet had time to try to figure out.
>a) fix asyncAwaitCondition to handle zero timeouts, or
It already does. Async checks for pending events before even "
- Original Message -
>
>
> - Original Message -
> > - Original Message -
> > > Hi,
> > >
> > > for me the Virtual driver (vr) doesn't work, reproducer:
> > >
> > > $ brltty -b vr -d server:127.0.0.1 -x a2 -A auth=none
> > > $ telnet 127.0.0.1 35752
> > > cells 20
> > >
- Original Message -
> - Original Message -
> > Hi,
> >
> > for me the Virtual driver (vr) doesn't work, reproducer:
> >
> > $ brltty -b vr -d server:127.0.0.1 -x a2 -A auth=none
> > $ telnet 127.0.0.1 35752
> > cells 20
> >
> > And nothing happened. It seems the 'vr' driver th
- Original Message -
> Hi,
>
> for me the Virtual driver (vr) doesn't work, reproducer:
>
> $ brltty -b vr -d server:127.0.0.1 -x a2 -A auth=none
> $ telnet 127.0.0.1 35752
> cells 20
>
> And nothing happened. It seems the 'vr' driver thinks there is
> no data on the socket received, i.e
Hi,
for me the Virtual driver (vr) doesn't work, reproducer:
$ brltty -b vr -d server:127.0.0.1 -x a2 -A auth=none
$ telnet 127.0.0.1 35752
cells 20
And nothing happened. It seems the 'vr' driver thinks there is
no data on the socket received, i.e. the awaitSocketInput check in
readNetworkSocket
