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
Fix registering device error with empty comment #2580
Fix registering device error with empty comment #2580
Conversation
451bce4
to
b9dc0c4
Compare
Codecov Report
@@ Coverage Diff @@
## master #2580 +/- ##
==========================================
+ Coverage 53.75% 54.03% +0.28%
==========================================
Files 558 558
Lines 40588 40588
==========================================
+ Hits 21819 21933 +114
+ Misses 18769 18655 -114
📣 We’re building smart automated test selection to slash your CI/CD build times. Learn more |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good to me!
Older versions of Django were very lenient about what you could put into select_related
calls (i.e. anything was allowed, only the arguments that represented real relations were adhered to). Django changed this, and it became an error to ask for unknown relations.
This just shows that we have no automated tests that revealed this at the time Django was upgraded.
The follow-up challenge, of course, is to add a test that reveals the problem by exercising this code :-)
1d977c0
to
af9a9e9
Compare
The netbox attribute of module is accessed in the template
af9a9e9
to
6cee026
Compare
Kudos, SonarCloud Quality Gate passed! 0 Bugs No Coverage information |
Closes #2579