-
Notifications
You must be signed in to change notification settings - Fork 4.2k
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
version 1.1.0 fresh reinstall issue #4593
Comments
To resolve the Here's how you can do it: database_service = DatabaseService(settings_service)
database_service.run_migrations(fix=True) This code snippet initializes the Additionally, there is a similar unsolved discussion about a large list of errors after running |
did not work
|
seems like removing db files from ~/.local/lib/python3.10/site-packages/langflow and running again langflow migration --fix worked out... now langflow starts, but with errors
|
after that, seems like i can't login with password set insite .env file :-/ hmmm |
now i see why...
|
okay, anyhow, installation yet ignores my admin user and password set in .env hmmm |
reinstalled again, similar errors. seems 1.1.0 is broken :-( |
another error, after total reinstall
|
Hi,
I totally removed older version
all with dependencies and db files
thanks
a.
|
Right! I'm trying to reproduce the issue! |
Thank you for your help!
I also wonder if that may be server related issue like with rights or something related to python itself
what information would you need to have?
|
I upgraded from 1.0.19Post 2 to 1.1.0 and got thousands of lines of stack trace logs flooding my screen. I can't keep up with the errors and langflow never successfully launches:
|
I think I fixed it. It has something to do with the psycopg2 dependency. The current version uses sqlalchemy and the prior versions uses psycopg directly. Also I made some changes to the service.py to always define the driver for postgres. I will need to double check what was doing the trick but then I can probably give an update. |
@KevinMichaelSchindler awesome! @italojohnny If that would be the issue, I wonder if the hotfix for langflow could be released? I am also using sqlite version |
The previous langflow version worked without the sqlalchemy dependency but probably there is a reason for adding it so it might be that some specific component or scenario breaks when reverting the dependencies. The default docker image uses postgres so I haven't tested the sqlite version. The tests definitely break for the sqlite stuff so more tinkering needs to be done to get the sqlite stuff to work. I assume the langflow team will bring out a proper fix soon but I thought I'll share this for the folks who are currently struggling with it. P.S. I confirmed that when I change just the dependency to: It seems to work for the default docker yml, so no changes to service.py are required it seems. |
I tried to add the aiosqlite manually: But there are still unresolved errors: Results (312.75s (0:05:12)): So currently the dependency update fixes the postgres issues but not the sqlite stuff as it seems. |
@KevinMichaelSchindler that was the error i was getting at the beginning, mismatch between the models and the database... after next reinstall i got #4593 (comment) |
You are using sqlite in your .env right? (python3 -m langflow run --env-file ./.env --no-open-browser --auto-saving --host localhost) I just tested it for the "make init" locally and the docker-compose.yml in the docker-example. These use postgres out of the box but the docker image was showing the same error regarding sqlalchemy, so that is what I fixed. As said if you are using sqlite there might be some additional fixing required, I am sorry :( |
@KevinMichaelSchindler Yes, I am. I used pip installation. I am not using docker installation here. |
I found the issue is with dependencies, especially Pydantic, used AI to help me a bit...
|
therefore...
|
Hello @severfire, @KevinMichaelSchindler and @greenmotion , First of all, I want to express our deep gratitude for everyone’s help in making Langflow a better tool. Your support means a lot to us! Secondly, I apologize for the delay in responding. This particular issue has been quite challenging to reproduce. In addition to myself, others are also working to address it. The tracebacks point to a migration issue, but the exact cause remains unclear. There is a possibility that fix #4599 resolved the problem. However, since we haven’t been able to reproduce the issue consistently, we cannot guarantee this with 100% certainty yet. For this reason, I would recommend, as an alternative, trying out the nightly version, which already includes this fix along with others. This might serve as a temporary solution until we can confirm the fix and proceed with the next official release. Thank you for your patience and understanding |
@italojohnny I have feeling it is python dependency issue. (I was playing with reinstalling different versions of Pydantic, staying with latest version, and also with pip install grpcio==1.59.0 grpcio-tools==1.59.0) Anyhow today my morning - like 12h ago I was able to run langflow, but it did not load .env config, I had to use exports. next week or later this week I will check your fixes, as right now my installation seems stable (with workarounds), and I have to do different tasks) thank you for all your help! |
@italojohnny: I'd be more than happy to test your nightly build, but I must admit I'm relatively new to Python and have been running Langflow in a venv and not a docker container. How would I update my langflow instance to a nightly build version? |
Bug Description
Hello,
I totally removed and reinstalled langflow, to update to new 1.1.0 version, while doing that i got very bad error...
while running:
python3 -m langflow run --env-file ./.env --no-open-browser --auto-saving --host localhost
got error:
Reproduction
Expected behavior
it should start without problems
Who can help?
No response
Operating System
Ubuntu 22.04
Langflow Version
1.1.00
Python Version
3.10
Screenshot
No response
Flow File
No response
The text was updated successfully, but these errors were encountered: