-
Notifications
You must be signed in to change notification settings - Fork 143
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
Resource editor raises KeyError when switching languages #10079
Comments
This comment was marked as outdated.
This comment was marked as outdated.
Can still reproduce |
Can you add the steps to reproduce? |
Looks like the OP was missing a step. (sorry!)
Now it strikes me that the problem goes away if I run I'll also update the traceback, which is a little different now. |
Looks like I was a little confused about whether the error emanated from the graph designer or the resource instance editor. Looks like it's only emanating from the latter now. I'll retitle. |
No worries! The |
Nice. In terms of documentation, I bet you could throw a system check from the |
@jacobtylerwalls I've assigned a PR to you here #10652 that should address the issue. Unfortunately I couldn't override the |
…age-check Add check for published graph in every system language #10079
Automate the changes to the github action template re #10079
This model check should have been skippped by checking the `databases` kwarg provided when `check()` is called, but that reduces the circumstances on which this check is run to either: - manage.py migrate - manage.py check --databases So, given how infrequently this would be run, better to just implement this in our validation framework.
This model check should have been skippped by checking the `databases` kwarg provided when `check()` is called, but that reduces the circumstances on which this check is run to either: - manage.py migrate - manage.py check --databases So, given how infrequently this would be run, better to just implement this in our validation framework.
This model check should have been skippped by checking the `databases` kwarg provided when `check()` is called, but that reduces the circumstances on which this check is run to either: - manage.py migrate - manage.py check --databases So, given how infrequently this would be run, better to just implement this in our validation framework.
* Rewrite model check as validation check re #10079 This model check should have been skippped by checking the `databases` kwarg provided when `check()` is called, but that reduces the circumstances on which this check is run to either: - manage.py migrate - manage.py check --databases So, given how infrequently this would be run, better to just implement this in our validation framework. This also prevents the possibility of failures when migrating.
the language switcheran additional languagemodelinstanceTested with afs
Version 7.5 dev
The text was updated successfully, but these errors were encountered: