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

bug: API - POST: /thread/{thread_id}/messages broken data #1434

Closed
louis-jan opened this issue Jan 8, 2024 · 0 comments · Fixed by #1479
Closed

bug: API - POST: /thread/{thread_id}/messages broken data #1434

louis-jan opened this issue Jan 8, 2024 · 0 comments · Fixed by #1479
Assignees
Labels
type: bug Something isn't working
Milestone

Comments

@louis-jan
Copy link
Contributor

louis-jan commented Jan 8, 2024

Describe the bug
Wrong data persisted; could not be displayed on the app.

Steps to reproduce
Steps to reproduce the behavior:

  1. Go to Jan App
  2. Turn on API Server
  3. Send POST message to this route
  4. Reload App
  5. See the error

Expected behavior
Should persist corresponding data, and could be displayed in app

Screenshots
Screenshot 2024-01-08 at 11 56 17

Environment details

  • Operating System: [Specify your OS. e.g., MacOS Sonoma 14.2.1, Windows 11, Ubuntu 22, etc]
  • Jan Version: [e.g., 0.1.3]
  • Processor: [e.g., Apple M1, Intel Core i7, AMD Ryzen 5, etc]
  • RAM: [e.g., 8GB, 16GB]
  • Any additional relevant hardware specifics: [e.g., Graphics card, SSD/HDD]

Additional context
Add any other context or information that could be helpful in diagnosing the problem.

@louis-jan louis-jan added the type: bug Something isn't working label Jan 8, 2024
@imtuyethan imtuyethan added this to the v0.4.5 milestone Jan 8, 2024
namchuai pushed a commit that referenced this issue Jan 9, 2024
namchuai added a commit that referenced this issue Jan 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: bug Something isn't working
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants