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
Now that ttyrec works even better with -Z and -a i noticed the following issue with ttyrec (or maybe ttyplay) in a very specific setup/use case. This may not be the fault of ttyrec/ttyplay, in which case feel free to close.
I am using ttyrec in a chain with ttyd (https://github.com/tsl0922/ttyd/) and tmux
for example: ttyd -> ttyrec -> tmux -> bash
simplified setup:
/usr/local/bin/ttyd.x86_64 -p 4200 /usr/local/bin/ttyrec -a -Z -f /logs/ttyrec_test -- /usr/local/bin/tmux new -A -s ttyrec_recording /bin/bash
-> connect via browser: http://:4200/
when a second browser connects -> the recording borks (or maybe ttyplay) with errors like
ZSTD_decompressStream() error: Data corruption detected
ZSTD_decompressStream() error: Unknown frame descriptor
This also happens without compression/append so that is probably not to cause.
The error does not occur if the chain is swapped:
for example: ttyd -> tmux -> ttyrec -> bash
however, then the recorded "lines" are often multiline/broken (e.g top) and the recording is not 1:1 or as "clean" as the other way round.
The text was updated successfully, but these errors were encountered:
Your use case is interesting! Glad to see that ttyrec can be of use for this.
When you don't use compression (by not using -Z), ttyplay should not call ZSTD_decompressStream, so I'm wondering whether this is due to the fact that you did not use -Z but still named your ttyrec file something.zst, because ttyplay has a logic where it automatically tries to decompress uzind zstd for files ending in .zst
hello, no, the files/recording do not have .zst extension. I admit the Problem is really weird, and i suspect the second connection joining the terminal somehow introduces some artifact that breaks the recording. I am not sure how to provide usefull information though (please let me know if there is something that would be usefull to) other then the procedure howto reproduce it.
Please let me know if i can provide anything usefull or if the should close it :)
Hello again!
Now that ttyrec works even better with -Z and -a i noticed the following issue with ttyrec (or maybe ttyplay) in a very specific setup/use case. This may not be the fault of ttyrec/ttyplay, in which case feel free to close.
I am using ttyrec in a chain with ttyd (https://github.com/tsl0922/ttyd/) and tmux
for example: ttyd -> ttyrec -> tmux -> bash
simplified setup:
/usr/local/bin/ttyd.x86_64 -p 4200 /usr/local/bin/ttyrec -a -Z -f /logs/ttyrec_test -- /usr/local/bin/tmux new -A -s ttyrec_recording /bin/bash
-> connect via browser: http://:4200/
when a second browser connects -> the recording borks (or maybe ttyplay) with errors like
ZSTD_decompressStream() error: Data corruption detected
ZSTD_decompressStream() error: Unknown frame descriptor
This also happens without compression/append so that is probably not to cause.
The error does not occur if the chain is swapped:
for example: ttyd -> tmux -> ttyrec -> bash
however, then the recorded "lines" are often multiline/broken (e.g top) and the recording is not 1:1 or as "clean" as the other way round.
The text was updated successfully, but these errors were encountered: