Open grantfitzsimmons opened 1 year ago
The main issue here (for me) is that the crash report is incredibly cryptic and not useful, instead of retrieving the URL of where the crash occurred. Where do I look to see the issue? Does it give me any kind of useful information that I can give to the user? We need to make these crashes somewhat intuitive to resolve on the user's end, or at least intelligible for me.
Piggy banking on this.
Need to properly demonstrate what exactly caused the merge failing. If you are merging A into B, but B was modified by A, then if the modifedbyagent field is preserved from B, then the merge will fail - tested this also. Simply clearing out the modifiedbyagent field in new record fixes this. In cases like these, user should be notified by dependencies.
TLDR: a simple click can convert a failed merge into successful one. we should hint user towards (or force) the successful one.
Possibly the same error when trying to merge agents, I get the following file download: Merging 29700913-bf1e-4bb6-973b-5b208db3b72f Crash Report - 2023-10-31T07_20_37.969Z.txt
@ianengelbrecht that error happened because you were trying to merge two (or more) agents that have a specify user associated with them. Currently, that is not supported. So, if you are merging agent A and agent B, and there is a specify user associated with both of them, the merging cannot occur.
Cannot recreate the specific issue from https://github.com/specify/specify7/issues/4017#issuecomment-1722563343 but when an agent merge does fail (e.g. by merging 2 agents with a specify user attached) you get a similar not very useful error in edge (7.9.6)
Happens on both
v.7.9-load-manual-ref
andv7.9-dev
https://fwri6123-v79-load-manual-ref.test.specifysystems.org/specify/overlay/merge/Agent/?records=1%2C2
https://github.com/specify/specify7/assets/37256050/467fceb2-d23e-4feb-ac3f-efd8bfcc8f3b
Merging 9835f5fb-7de7-4dfd-b1bb-03974517d8ab Crash Report - 2023-09-17T18 10 04.309Z.txt