You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Here, we aim to provide solutions and clarity on common queries that users might encounter while using xlang. We're dedicated to ensuring a smooth experience for everyone, so don't hesitate to explore the following FAQs. If your question isn't covered here, feel free to reach out, and we'll be more than happy to assist you.
Also, you can always find some useful information in our documentation page.
FAQs about online demo
Q: Why is the response stuck; what can I do? A: If you find that a response seems stuck, there is a time limit for each response. To address this, you can either click the "Stop" button to halt the response or simply refresh the page. This should resolve the issue in most cases.
Q: Why is there an internal server error? A: Internal server errors can occur due to various reasons, such as request errors in the OpenAI API (e.g., rate limits or streaming errors). If you encounter this error, you can click "Retry" to attempt the request again. Alternatively, waiting for some time and then returning to the chat might also resolve the issue.
Q: Why is my code generated but not executed? A: For code to be executed, it must be wrapped within the relevant tools, such as Python code generation. Raw code that isn't enclosed in tool-specific outputs will not be executed by the agent.
Q: How do I apply my data to the chat? A: To apply data to the ongoing chat, click on the file you wish to upload and then select the "📎" (attachment) button followed by the "☑️" (apply) button. This will incorporate the file's content into the current chat session.
Q: What if my quota is used up? A: Our API key comes with a restricted quota due to budget limitations. However, you have the option to upload your own API key, which grants you double the quota by routing usage through your personal key. Rest assured, we do not store your key. Please be aware that this approach might result in multiple API calls within a single response due to our system's design.
The text was updated successfully, but these errors were encountered:
Welcome to the xlang FAQ GitHub issues page!
Here, we aim to provide solutions and clarity on common queries that users might encounter while using xlang. We're dedicated to ensuring a smooth experience for everyone, so don't hesitate to explore the following FAQs. If your question isn't covered here, feel free to reach out, and we'll be more than happy to assist you.
Also, you can always find some useful information in our documentation page.
FAQs about online demo
Q: Why is the response stuck; what can I do?
A: If you find that a response seems stuck, there is a time limit for each response. To address this, you can either click the "Stop" button to halt the response or simply refresh the page. This should resolve the issue in most cases.
Q: Why is there an internal server error?
A: Internal server errors can occur due to various reasons, such as request errors in the OpenAI API (e.g., rate limits or streaming errors). If you encounter this error, you can click "Retry" to attempt the request again. Alternatively, waiting for some time and then returning to the chat might also resolve the issue.
Q: Why is my code generated but not executed?
A: For code to be executed, it must be wrapped within the relevant tools, such as Python code generation. Raw code that isn't enclosed in tool-specific outputs will not be executed by the agent.
Q: How do I apply my data to the chat?
A: To apply data to the ongoing chat, click on the file you wish to upload and then select the "📎" (attachment) button followed by the "☑️" (apply) button. This will incorporate the file's content into the current chat session.
Q: What if my quota is used up?
A: Our API key comes with a restricted quota due to budget limitations. However, you have the option to upload your own API key, which grants you double the quota by routing usage through your personal key. Rest assured, we do not store your key. Please be aware that this approach might result in multiple API calls within a single response due to our system's design.
The text was updated successfully, but these errors were encountered: