-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
prerelease update from v1.0.0a24 to v1.0.0a27 fails to migrate flows #1790
Comments
Attaching log for reference... |
Hey @suggsadc Thanks! The monitor service uses a different database. There are no migrations on it yet and we delete the table every time we make changes to it. I've added better logging on tihs so we can have a clearer picture on what is really causing this. |
* Fix created_at field type in Variable model * Fix created_at field type in ApiKey model * Fix error handling in add_row_to_table function #1790 * Apply type hinting to nest_asyncio import in load.py
rock on... continue on with your awesomeness! |
Could you update it and see if there's any more info on this issue? Were you saving messages to the Chat Memory or were you simply using Langflow when this happened? |
I migrated from v1.0.0a26 to v1.0.0a28 without issue (users, flows, components all were maintained) and no errors in log. I assume this issue to be resolved. thank you! answer to your question You were correct to point out to me that the logs reference the "monitor" utility and most likely not related to missing flows and user after my update. |
Describe the bug
Missing logins and flows after Langflow pre-release update
Browser and Version
Migration from v1.0.0a24 to v1.0.0a27
To Reproduce
Steps to reproduce the behavior:
pip install langflow -U --pre
in-order to update to v1.0.0a27Additional context
Honestly, I chalked it up to expected and intended behavior for a pre-release. However, I did see several references in the the
langflow-pre.db
logs to failed row entries that i thought i would bring to your attention:Example failed DB
add_row_to_table
The text was updated successfully, but these errors were encountered: