I encountered an issue during the legacy chat migration process. The root cause seems to be that the migration logic is unable to handle chat configurations that have previously enabled Flash Attention.
Specifically, the presence of the following lines in your chat's configuration file triggers the failure:
I encountered an issue during the legacy chat migration process. The root cause seems to be that the migration logic is unable to handle chat configurations that have previously enabled Flash Attention.
Specifically, the presence of the following lines in your chat's configuration file triggers the failure:
As a temporary workaround, you can remove these lines from your chat's configuration file. This will allow the migration to proceed successfully.