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

Installer: Shows errors on submit & move runMigrations #722

Merged
merged 3 commits into from
Dec 1, 2024

Conversation

Boy132
Copy link
Member

@Boy132 Boy132 commented Nov 21, 2024

Yet Another Installer PR.

Fixes errors on submit not showing because of Halt exception.
Moves the runMigrations call to submit to avoid cache problems.

@Boy132 Boy132 self-assigned this Nov 21, 2024
Copy link
Contributor

@RMartinOscar RMartinOscar left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Errors are now shown but if any error occurs (like if redis is not reachable for a second when clicking finish) it will display

Migrations failed
SQLSTATE[HY000]: General error: 1 table "permissions" already exists (Connection: sqlite, SQL: create table "permissions" ("id" integer primary key autoincrement not null, "name" varchar not null, "guard_name" varchar not null, "created_at" datetime, "updated_at" datetime))

cause migrations already ran even though redis failed causing the finish step to never work and you need to manually empty the database

@Boy132
Copy link
Member Author

Boy132 commented Nov 21, 2024

Errors are now shown but if any error occurs (like if redis is not reachable for a second when clicking finish) it will display

Migrations failed
SQLSTATE[HY000]: General error: 1 table "permissions" already exists (Connection: sqlite, SQL: create table "permissions" ("id" integer primary key autoincrement not null, "name" varchar not null, "guard_name" varchar not null, "created_at" datetime, "updated_at" datetime))

cause migrations already ran even though redis failed causing the finish step to never work and you need to manually empty the database

Not sure if I understand you correctly, you got a redis error and that caused migrations to fail?

@notAreYouScared
Copy link
Member

notAreYouScared commented Nov 21, 2024

It should be noted that it creates a blank database.sqlite even if you change from sqlite

Edit: Image below, I got to the database screen, change the database name to databa1se.sqlite and it created both? but database.sqlite is a blank file.
image

@Boy132
Copy link
Member Author

Boy132 commented Nov 26, 2024

It should be noted that it creates a blank database.sqlite even if you change from sqlite

Edit: Image below, I got to the database screen, change the database name to databa1se.sqlite and it created both? but database.sqlite is a blank file. image

Can't reproduce that. Make sure you are on the right branch/ have the right files.

Copy link
Member

@notAreYouScared notAreYouScared left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good, Did notice that it no longer auto-logins for you. Might just be a windows environment thing.

@Boy132 Boy132 dismissed RMartinOscar’s stale review December 1, 2024 03:04

followup if reproducible

@Boy132 Boy132 merged commit e0c6137 into pelican-dev:main Dec 1, 2024
15 checks passed
@Boy132 Boy132 deleted the fix/submit-errors branch December 1, 2024 03:04
@github-actions github-actions bot locked and limited conversation to collaborators Dec 1, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants