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

Create instance actor if it hasn't been properly seeded #15693

Merged
merged 1 commit into from
Feb 9, 2021

Commits on Feb 9, 2021

  1. Create instance actor if it hasn't been properly seeded

    An uncommon but somewhat difficult to digagnose issue is dealing with
    improperly-seeded databases. In such cases, instance-signed fetches will
    fail with a ActiveRecord::RecordNotFound error, usually caught and handled
    as generic 404, leading people to think the remote resource itself has not
    been found, while it's the local instance actor that does not exist.
    
    This commit changes the code so that failure to find the instance actor
    automatically creates a new one, so that improperly-seeded databases do
    not cause any issue.
    ClearlyClaire committed Feb 9, 2021
    Configuration menu
    Copy the full SHA
    ac218d9 View commit details
    Browse the repository at this point in the history