-
Notifications
You must be signed in to change notification settings - Fork 13
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
🚸 Catch Django errors of death #1585
Comments
Agreed - there are a few Django related tracebacks that we're handling downstream. It's a bit dangerous to default to hiding tracebacks in these cases, but you're right that in all cases where the original traceback is not needed, it's super annoying. I'll weigh pros & cons or see whether there is a danger-free solution to this. |
INSTALLED_APPS
error and show an understandable error message
@Zethson shared feedback from a Hackathon
We have to figure out a way to catch this error. |
INSTALLED_APPS
error and show an understandable error message
A new version of this: Internal Slack ref.
|
Another one:
|
How did you get that one? |
Just
|
This is the issue with the v1 migration of all schema modules. It can happen if you have Nothing else tries to import |
Can you print the list of schema modules I have to update in case there's an error like this? Or any unknown error from Django that is not caught. I don't think there's a way for a user to know if all schema versions are synced or not. Just pulling from supabase would be a solution to this. |
These topics are all taken care of above >1 through proper constraints in pyproject.toml which the package manager will log as warnings or errors once we go to lamindb >2 The removal of lnschema_core together with ourprojects was particularly disruptive -- that's why the migration had notes about this Had we thought of v1 in November when making the last <1 releases it wouldn't have happened because all packages would already have had the >1 incompat constraint -- but I didn't think of making "v1" so early, so this bumpiness was foreseeable |
Except
INSTALLED_APPS
error and show an understandable error messageThis happens after I deleted
~/.lamin
. The actual actionable message is hidden under an incomprehensible exception.Edit by @Zethson : This should be resolved in laminlabs/lamin-cli#103
The text was updated successfully, but these errors were encountered: