从0.15.3升级到1.0.1 在执行‘poetry run flask migrate-data-for-plugin’的时候报错。 Upgraded from 0.15.3 to 1.0.1 An error is reported when running 'poetry run flask migrate-data-for-plugin'.

[XiaoCC]

Self Checks

• This is only for bug report, if you would like to ask a question, please head to Discussions.
• I have searched for existing issues search for existing issues, including closed ones.
• I confirm that I am using English to submit this report (我已阅读并同意 Language Policy).
• [FOR CHINESE USERS] 请务必使用英文提交 Issue，否则会被关闭。谢谢！:）
• Please do not modify this template :) and fill in all the required fields.

Dify version

1.0.1

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

从0.15.3升级到1.0.1 在执行‘poetry run flask migrate-data-for-plugin’的时候报错。
Upgraded from 0.15.3 to 1.0.1 An error is reported when running 'poetry run flask migrate-data-for-plugin'.

✔️ Expected Behavior

从0.15.3升级到1.0.1 在执行‘poetry run flask migrate-data-for-plugin’的时候报错。
Upgraded from 0.15.3 to 1.0.1 An error is reported when running 'poetry run flask migrate-data-for-plugin'.

❌ Actual Behavior

[dosubot]

I found a similar issue that was closed: poetry run flask migrate-data-for-plugin failed when upgrade from 0.15.3 to 1.0.0. This issue was resolved by a pull request that addressed a psycopg2.errors.StringDataRightTruncation error, which was caused by a value being too long for a specific character type ^[1].

The error you're encountering, InFailedSqlTransaction, suggests that the transaction is aborted, and commands are ignored until the end of the transaction block. This can occur if there is an error in the SQL command being executed during the migration process. It might be helpful to check if the solution from the closed issue applies to your case, such as verifying the data types and lengths in your database schema.

To continue talking to Dosu, mention @dosu.

---

^{Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Bug Report | Other}

[XiaoCC]

我发现了一个类似的问题已关闭：从 0.15.3 升级到 1.0.0 时失败。此问题已通过解决错误的拉取请求得到解决，该错误是由值对于特定字符类型来说太长引起的psycopg2.errors.StringDataRightTruncation[1].

您遇到的错误 表示事务已中止，并且命令将被忽略，直到事务块结束。如果在迁移过程中执行的 SQL 命令出错，则可能会发生这种情况。检查已关闭问题的解决方案是否适用于您的案例可能会有所帮助，例如验证数据库架构中的数据类型和长度。InFailedSqlTransaction

要继续与 Dosu 交谈，请提及 。

帮助 Dosu 学习！给它反馈：伟大的回应 |无关紧要的答案 |不正确的来源 |太冗长 |幻觉 |Bug 报告 |其他

我已经把字段长度加大了还是报错。
I've increased the field length and still get an error。

我不确定是不是0.15.3之前有一个xinference的工具插件，用于对接xinference的sd、flux之类的生图功能，但是在1.0.1的插件市场里没有这个插件，在0.15.3升级到1.0.1后插件迁移后，执行‘poetry run flask migrate-data-for-plugin’的时候报的错误是不是这个之前缺失的xinference插件导致的？
I'm not sure if there was a tool plugin for xinference before 0.15.3, which was used to connect with xinference's sd, flux and other image generation functions, but there was no such plugin in the plugin market of 1.0.1, and after the plugin migration after upgrading from 0.15.3 to 1.0.1, execute 'poetry run flask Is the error reported by migrate-data-for-plugin' caused by the previously missing xinference plugin?
xorbitsai/inference#2832
#8385

[XiaoCC]

@crazywoola Why close this？I haven't gotten an answer yet