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

Getting "Please hold on for a moment" frequently #464

Open
AmaliMatharaarachchi opened this issue Feb 16, 2025 · 2 comments
Open

Getting "Please hold on for a moment" frequently #464

AmaliMatharaarachchi opened this issue Feb 16, 2025 · 2 comments

Comments

@AmaliMatharaarachchi
Copy link

Describe the bug
Frequently getting "Please hold on for a moment" kind of responses. This issue was not happened in v.0.0.1 version for me.

To Reproduce
Steps to reproduce the behavior:

  1. Ask a question that requires multiple steps like extracting text from an pdf and use that text to answer the question.

Expected behavior
A clear and concise description of what you expected to happen. NA if feel not applicable.

Screenshots
If applicable, add screenshots to help explain your problem.

Environment Information (please complete the following information):

  • OS: [e.g. Linux, Windows, WSL]
  • Python Version [e.g. 3.10, 3.11]
  • LLM that you're using: [e.g., GPT-4]
  • Other Configurations except the LLM api/key related: [e.g., code_verification: true]

Additional context
Add any other context about the problem here.

@liqul
Copy link
Contributor

liqul commented Feb 17, 2025

I tried to repro your problem. My request was to load a PDF file and give me a summary of its content, but I didn't see the issue you reported. Could you share a trace with us so we can better understand the situation where it happens? I'm using gpt-4o, so if the model is different, it could be a reason. But as long as the model is capable enough, such tasks should have no problems.

@AmaliMatharaarachchi
Copy link
Author

I used gpt-4o model and I was using the main branch at that time. Once I reverted back to v0.0.2 tag, the issue disappeared.

However, I have encountered this issue again in this tag too, but only once; however, that time I suspect it had happened due to a network slowness.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants