Bowen Liang

Rebased and re-applied the Ruff fixes on to the latest commit of the master branch to resolve conflicts.

> This is a new conflict in files. Resolved.

Hi @takatost , this PR has been rebased onto latest commit, and it's ready to go.

Several popular Python linter tools were considered, including black, isort, ruff and etc. As dify community requested minimum impact to existed code for commit history traceability, `isort` is introduced to...

Closing this PR. `ruff` seems to to be a much better option for lining Python imports. As we want to apply Python imports linting in pre-commit stage, we'd better choose...

Would you like to consider applying `dev/reformat` to python import styling before the release ofevery version? This would be great for rebasing our self-hosted repos. Thanks. @takatost

We use the style check test and the reformat tools together, which leads to a good practice in Apache Kyuubi. The key point is that both approaches should be brought...

> What action should I take? It's an optional suggestion anyway. We could apply the `dev/reformat` script and commit the changes in a new PR before cutting the branch for...

The orginal feature and bug introduced by https://github.com/langgenius/dify/pull/2190. I don't know the reason that the guard conditions in purple block does not work as expectedly and I suggested a temporary...

Already tested in my local environment.