Fix uncaught error: Can’t apply message of unknown type: 8 on rumors-site #6
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Error on rumors-site that may break transcript function
![image](https://private-user-images.githubusercontent.com/6376572/298976108-b180a34f-6232-472f-ab0b-5a86869918fc.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwNTk3MzgsIm5iZiI6MTczOTA1OTQzOCwicGF0aCI6Ii82Mzc2NTcyLzI5ODk3NjEwOC1iMTgwYTM0Zi02MjMyLTQ3MmYtYWIwYi01YTg2ODY5OTE4ZmMucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDlUMDAwMzU4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9M2ViNDllZjAyNzdjZWQxODBlYWQ0ZWU5ZjQ1NzU5NDM2NThlMjQwY2FkZjFkZjZiYWNmMmM4MDQ1NzhkMTUxMSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.4spPXzzXmfvKGP85HZcSKMLSo2nX8LUpgVrIUYWSk1w)
Reproduce steps: find an article with a transcript, edit the transcript.
Root cause:
![image](https://private-user-images.githubusercontent.com/6376572/298975684-f6641ae8-f17c-418c-9251-043aa2a279b7.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzkwNTk3MzgsIm5iZiI6MTczOTA1OTQzOCwicGF0aCI6Ii82Mzc2NTcyLzI5ODk3NTY4NC1mNjY0MWFlOC1mMTdjLTQxOGMtOTI1MS0wNDNhYTJhMjc5YjcucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDIwOSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTAyMDlUMDAwMzU4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ODYwNTU5NDk0MGZjYmNjMzQyNmI0MDNiMjE4ZWI2MjUyYWE4NDM3MTM4MjQyZDk5NWY4MjM1NjU3Mjc4NGExMiZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.DuvUEcfT5du5I3_3zrCnl4as5UCPf65S12JGybGNFeU)
It's because we upgraded hocuspocus/server to 2.7.1 in package-lock by accident.
And newer version adds a new MessageType which old client does not know