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

Raggenie Preview Section Does Not Prompt for Chatbot Restart After Bot configuration & plugin creation #50

Open
agberoz opened this issue Sep 30, 2024 · 0 comments · May be fixed by #112
Assignees
Labels
bug Something isn't working front-end

Comments

@agberoz
Copy link
Collaborator

agberoz commented Sep 30, 2024

The Raggenie preview section fails to inform users about the need to restart the chatbot after making changes to the plugin, bot configuration, and inference details. Instead of displaying a message regarding the deployment section for a restart, it directs users straight to the chat window, resulting in errors due to the bot not being reloaded.

Steps to Reproduce:

  1. Add a plugin.
  2. Add bot configuration.
  3. Add inference details.
  4. Navigate back to the preview page, which takes you to the chat window without restarting the bot.

Specific File Affected:

  • raggenie/ui/src/pages/Preview/ChatBox.jsx

Proposed Solution:

  • Check the status of the current configuration:
    • If the status is 1, it indicates that the bot has not been reloaded.
    • If the status is 2, it indicates that the bot has been reloaded.
    • Prompt the user to restart the chatbot from the preview section if the status is 1 and direct them to deployment section
@agberoz agberoz added bug Something isn't working front-end labels Sep 30, 2024
@sethumadhavan-k sethumadhavan-k self-assigned this Oct 14, 2024
@sethumadhavan-k sethumadhavan-k linked a pull request Oct 14, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working front-end
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants