Hello @AlwaysBluer! I'm here to assist you with any bugs, questions, or contributions you have for the project. Let me know how I can help!

The issue you're encountering is due to a misconfiguration in the docker-compose.yaml file. The password variable for VDB Lindorm is incorrectly named LINDORM_USERNAME instead of LINDORM_PASSWORD. To resolve this, you should update the docker-compose.yaml file to use the correct variable name:

LINDORM_USERNAME: ${LINDORM_USERNAME:-lindorm}
LINDORM_PASSWORD: ${LINDORM_PASSWORD:-lindorm}

This change should help ensure a successful connection to VDB Lindorm ^[1].

To continue talking to Dosu, mention @dosu.

Hello Please checkout from our main branch and open this pr again. There are some conflicts.

Hi, @AlwaysBluer. I'm Dosu, and I'm helping the Dify team manage their backlog. I'm marking this issue as stale.

Issue Summary

• The issue involved a bug in the docker-compose.yaml file for VDB Lindorm.
• The password variable was incorrectly named LINDORM_USERNAME instead of LINDORM_PASSWORD.
• I suggested the correct variable naming, resolving the connection failure.
• @crazywoola recommended checking out from the main branch and reopening the pull request to resolve conflicts.

Next Steps

• Please confirm if this issue is still relevant to the latest version of the Dify repository by commenting on this issue.
• If there is no further activity, this issue will be automatically closed in 15 days.

Thank you for your understanding and contribution!