-
Notifications
You must be signed in to change notification settings - Fork 36
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
Cannot save Collecting Trip or Storage with an attachment #3289
Comments
There are likely other tables with this issue. We need to go through each of the tables that have attachments and try it out.
|
This issue has been mentioned on Specify Community Forum. There might be relevant details there: https://discourse.specifysoftware.org/t/attachment-save-errors/1126/2 |
@grantfitzsimmons can you please merge the duplicate issues? |
Once you fix the issue 😉 /s Will do! |
This does not happen with a new CT record. https://willemcatno-edge.test.specifysystems.org/specify/view/collectingtrip/1057/ Steps to Recreate:
Same database as #2409. Seems to be a back-end error, but needs to be resolved ASAP. Reported By: Willem at SAIAB |
Screen.Recording.2022-11-04.at.1.39.23.PM.mp4This is a problem in
|
@melton-jason Is the fix you used here relevant to these issues? |
I believe so. I have not looked at the Storage or Collecting Trip issue and uncovered the cause, but I think it is the same issue which means the fix should be the same as the fix for exchange in/exchange out. The problem occurs as an attachment business rule problem and occurs at this line.
More specifically, For quick reference, here is the Scoping class. specify7/specifyweb/specify/scoping.py Lines 11 to 96 in 0345888
I tried to alleviate potential issues like this in #2744 by implementing a way to infer the table's scoping, but (obviously) it seems there is a bug in the code. Aside from also fixing the bug, I will add scoping tests on the backend to reduce the possibility of this happening again. |
That scoping.py file is criminally bug-prone. def locality(self): return self._simple_discipline_scope() It is needlesly bug prone and causes issues like #2525 |
@maxpatiiuk |
oh that would be awesome! |
Same issue happens with DNA Sequencing Run attachments |
Fixed |
https://fwri-edge.test.specifysystems.org/specify/view/collectingtrip/991/
After uploading an attachment, you are unable to save without a crash.
Short error:
Full error:
Specify 7 Crash Report - 2023-04-03T18 45 35.340Z.txt
Screen.Recording.2023-04-03.at.1.44.56.PM.mov
Reported By: @Plarson at the Speciforum
The text was updated successfully, but these errors were encountered: