-
Notifications
You must be signed in to change notification settings - Fork 2
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
Server Error #281
Comments
Hm, okay, when pushing changes to #280, it seems the CI errors when deploying it to Fly.io. https://github.com/dwyl/mvp/actions/runs/3988547375/jobs/6839852547 This might be related. Let me see if I can figure out what's going on 👍 |
Uhm. I re-ran that job and it seems to be working now. Perhaps some networking issues on Fly.io's side? Is your issue still occurring @seaneady ? Everything seems fine on my end 😄 |
also tried it on other computers too and I got the same thing. |
Database logs show this. https://fly.io/apps/mvp-db/monitoring
This is probably the issue, perhaps Sean's person row was deleted from the database for whatever reason and can't properly login (?). I don't really know how to access the database and make changes to it, going to leave it to the pros. @nelsonic @SimonLab |
From #281 (comment) I think maybe an error has been created on Fly.io side. the |
@seaneady thanks very much for reporting this. 👌 (😢) |
No problem. I tried from Chrome and Safari on two separate computers and got the same error. Could it have something to do with the fact that I am trying to log in from South Africa maybe? |
It's possible that |
@seaneady when you're back at your desk, please LMK. |
@LuchoTurtle sorry I'm only getting back to you now. Been a bit hectic on my side today. Would 3pm your time work? I have another call starting now 2pm(your time). |
Let's look at this immediately after standup today (stay on the Zoom call). 👌 |
We're taking a look at this now on the Zoom call. 🔥 |
This is going to be a bit of a mission. We need to understand the Database constraint error as shared by @LuchoTurtle above ⏫ #281 (comment) |
We can do this directly on postgres with the command: ALTER TABLE table_name
DROP CONSTRAINT foreign_key_name; in our case ALTER TABLE items
DROP CONSTRAINT items_person_id_fkey; What I'm not sure is why the constraint stayed when we removed it from the migrations. Maybe there is an migration command to do this directly in the Phoenix project. I think we can create a new migration to use |
Ok. we have a snapshot created: dwyl/learn-devops#87 |
Applied the |
The people table has been removed from the phoenix app without creating a migration. b7d7aed |
Yeah, that's my bad. Thought it had been removed cleanly. Thanks for investigating @SimonLab 🔍 🕵️ |
But if the migration file has been deleted from the repo, doesn't Fly.io just run the migrations from scratch? It shouldn't create the |
Nope. Sadly, that's now how it works. It only runs the new migrations. The old ones are already executed. |
Ok. we need @seaneady to re-test on his side ... |
@seaneady thanks for confirming that you were able to login with |
@seaneady looks like you've been able to authenticate and add a couple of |
Reporting a bug which I encountered when attempting to sign up to the mobile and web version of the MVP.
The text was updated successfully, but these errors were encountered: