Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

The completion-messages interface returns an exception #12111

Open
5 tasks done
silence-pan84 opened this issue Dec 26, 2024 · 1 comment
Open
5 tasks done

The completion-messages interface returns an exception #12111

silence-pan84 opened this issue Dec 26, 2024 · 1 comment
Labels
🐞 bug Something isn't working

Comments

@silence-pan84
Copy link

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

0.13.2

Cloud or Self Hosted

Self Hosted (Docker)

Steps to reproduce

When calling the "v1/completion-messages" interface, the answer content is sometimes extra: “JpaRepository for storing and retrieving data is not applicable here as the task involves natural language processing and keyword extraction, which does not require a database operation. The provided solution directly addresses the given instruction by extracting relevant keywords from the text regarding location, subject, and complaint type in JSON format.
image

✔️ Expected Behavior

No response

❌ Actual Behavior

No response

@dosubot dosubot bot added the 🐞 bug Something isn't working label Dec 26, 2024
Copy link

dosubot bot commented Dec 26, 2024

The v1/completion-messages interface in the Dify codebase can throw several specific exceptions, which might be relevant to the issue you're experiencing. These exceptions include:

  • NotFound with the message "Conversation Not Exists."
  • ConversationCompletedError
  • AppUnavailableError
  • ProviderNotInitializeError
  • ProviderQuotaExceededError
  • ProviderModelCurrentlyNotSupportError
  • CompletionRequestError
  • InternalServerError [1][2].

If the response content is unexpectedly including additional information, it might be due to the configuration of the model parameters or prompt templates used in the request. Ensure that the inputs and configurations are set correctly to avoid such issues. If the problem persists, reviewing the specific inputs and configurations used in the request might help identify the cause.

To continue talking to Dosu, mention @dosu.


Help Dosu learn! Give it feedback: Great Response | Irrelevant Answer | Incorrect Sources | Too Verbose | Hallucination | Other

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
🐞 bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant