You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Is your feature request related to a problem? Please describe.
Thanks to @mastercactapus we've finally the Wait feature, but when waiting for a line on failure it's hard to understand the context as the error is just:
failed to execute command: timeout waiting for "Line Username:$" to match Username:$; last value was: >
Describe the solution you'd like
Other than showing the failed line (ideally in a new line so that's clearer), the whole context should be shown as when using Wait+Screen
Describe alternatives you've considered
Using Wait+Screen /Username:\n/ is an option but that doesn't make sure that we're matching the last screen line.
The text was updated successfully, but these errors were encountered:
I can see how that would help debugging -- we could print the entire buffer, though it would be important to indicate which line the cursor is on (since that's the one being checked).
For your issue, the last line is likely the cursor, but if that ever weren't the case, it would help understand what happened.
That sounds good. It looks like there's definitely room for improvement with the error message here for sure. It would be nice to have the error message similar to the one we will be using in Freeze
Is your feature request related to a problem? Please describe.
Thanks to @mastercactapus we've finally the
Wait
feature, but when waiting for a line on failure it's hard to understand the context as the error is just:Describe the solution you'd like
Other than showing the failed line (ideally in a new line so that's clearer), the whole context should be shown as when using
Wait+Screen
Describe alternatives you've considered
Using
Wait+Screen /Username:\n/
is an option but that doesn't make sure that we're matching the last screen line.The text was updated successfully, but these errors were encountered: