specify / specify7

Specify 7
https://www.specifysoftware.org/products/specify-7/
GNU General Public License v2.0
64 stars 36 forks source link

Error when adding additional preparation to an existing collection object #2561

Closed mc0822 closed 1 year ago

mc0822 commented 1 year ago

RBGE reports being unable to save when adding additional preparation to an existing collection object.

(https://herbrbge6802-edge.test.specifysystems.org/specify/view/collectionobject/151675/)

Steps: Add an additional preparation to an existing collection object. It adds the preparation. When click save, get the error message (below).

Expected behavior User should be able to save when adding additional preparation to an existing collection object.

Screenshots 120722 snip rbge

Desktop:

Database Name: herb_rbge_6802 (6.8.02) britchie Herbarium

Reported By Robyn Drinkwater, RBGE

Additional context Specify 7 Crash Report - 2022-12-07T19_18_21.559Z.txt

beach53 commented 1 year ago

Safari for Windows? Curious. Last update from Apple was 2012 for Windows versions.

"Before installing this version of Safari on Windows 11 or 10, remember that it’s an outdated version and lacks many of the security features present in the latest version of Safari. We recommend using the latest version of Chrome, Edge, or Firefox for peace of mind."

grantfitzsimmons commented 1 year ago

@beach53 Based on the screenshot, that is Microsoft Edge

Based on the crash report, Windows 10 64-bit, Edge 107.0.1418.56

grantfitzsimmons commented 1 year ago

I am entirely unable to recreate your issue on my end using edge with the link shared here. Is there some particular behavior necessary to recreate?

I have added values to every field in the preparation subview, but no success.

Interestingly, I was able to get another error when I entered just a barcode as she described in her email.

Reported here: https://github.com/specify/specify7/issues/2563

mc0822 commented 1 year ago

I meant to list Edge, I'll need to edit github issue, sorry for the confusion. Safari was listed in the template, and I forgot to change it.

Thank you,

Mandi Chace Specify Technical Support Manager / Research Informatics Developer KU Biodiversity Institute 1345 Jayhawk Blvd., Rm. 606 Lawrence, KS 66045 Desk: (785) 864-4400 @.**@.> https://biodiversity.ku.edu/informatics

From: Jim Beach @.> Sent: Wednesday, December 7, 2022 3:29 PM To: specify/specify7 @.> Cc: Chace, Mandi K @.>; Author @.> Subject: Re: [specify/specify7] Error when adding additional preparation to an existing collection object (Issue #2561)

Safari for Windows? Curious. Last update from Apple was 2012 for Windows versions.

"Before installing this version of Safari on Windows 11 or 10, remember that it's an outdated version and lacks many of the security features present in the latest version of Safari. We recommend using the latest version of Chrome, Edge, or Firefox for peace of mind."

- Reply to this email directly, view it on GitHubhttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fspecify%2Fspecify7%2Fissues%2F2561%23issuecomment-1341620271&data=05%7C01%7Cmandikc%40ku.edu%7C1fd70db44a47458040ef08dad89a094e%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C0%7C638060453335448888%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xsXzOcSFZE2NmOLMOvu45CYqlcL14bOQSiJGZpXIE8s%3D&reserved=0, or unsubscribehttps://nam10.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FA2RXEHUZZXLL3LFQENGSDCTWMD6RHANCNFSM6AAAAAASXIWQPE&data=05%7C01%7Cmandikc%40ku.edu%7C1fd70db44a47458040ef08dad89a094e%7C3c176536afe643f5b96636feabbe3c1a%7C0%7C0%7C638060453335448888%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=vTDjuvM0UtJp9t2W36AhiO6hg1Yqjx%2Bf5F9pARTKc00%3D&reserved=0. You are receiving this because you authored the thread.Message ID: @.**@.>>

maxpatiiuk commented 1 year ago

This error usually indicates mysql was overloaded, or it was being restarted. And yet, DB usage was quite low.

Are they able to replicate this issue consistently? Maybe it was just a fluke