-
Notifications
You must be signed in to change notification settings - Fork 86
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
Errors while doing upgrade #95
Comments
Issue persists. Not sure why the database username that is passed is being used for the database name? |
Is |
|
Seems like a case of this. Let me try this and report if the fix there works. |
@kevgliss I believe this is an issue due to this. This issue might have to be moved to the As the Towards that, I was wondering is Hope this helps someone else facing the same error. Two days I'll never get back! 😅 |
I see it's pulled in transitively due in this library. I'll pin it while building our container for now and that should tape the issue for now. |
So I was able to run an ECS container with the fix above just to run the The upgrade itself was successful, but it had a bunch of endpoint related errors that I wanted to understand. Would you know how to resolve them?
|
That issue with sqlalchemy-utils is a good catch (we've always had the database and the user match so we've never encountered it). The second error regarding In the near term we can pin aiohttp, or attempt to figure out which library is requiring <chardet4.0 and see if they have an upgrade path. |
Oh yeah, also wanted to mention, RDS uses So regarding the |
Running |
@kevgliss @mvilanova Yes. I was able to pin the version and then
Somehow it seems like the I'm using the latest code on master to run this and also data dump from the link in |
Ah, we recently moved the register url to Sorry about the confusion! |
@kevgliss Ah. That makes sense. It is auth related. I'm happy to report that I was able to get as deep as setting up the data dump and got the endpoint up and running using ECS and RDS and was going to test integrations next. I did get a few errors while doing the data dump, I'm not sure how critical they are, but I thought I'd let you know that I'm looking into them and any insights from you will be super useful.
|
@kevgliss The first one seems to be based on the postgres version so is an easy fix. But the 2nd and 3rd errors seem like they could break something. |
@kevgliss Like I suspected. The 1st one doesn't occur on local (macOS) run of the |
I haven't been able to reproduce these errors on the latest example data dump (released today). Closing for now, please create a new issue if you encounter them again. |
I get the following error message when I try to setup tables using ECS. The easiest way I found was to do the
dispatch database upgrade
using a separate container and have theweb
andscheduler
containers run only after thatmigrate
container has finished execution.Towards doing the database upgrade, I get the following errors:
Do you think this is a connection issue or is it a table setup issue? Are you familiar with this error?
The text was updated successfully, but these errors were encountered: