[Bug]: pyRevit Crashing Revit When Edited by Multiple Users #2388
Labels
Bug
Bug that stops user from using the tool or a major portion of pyRevit functionality [class]
Heisenbug
Bug that is very hard to find [class]
Prioritize
The issue is planned to be resolved in the next version
Tools
Issues related to pyRevit commands [subsystem]
✈ Pre-Flight checks
🐞 Describe the bug
We have done extensive internal testing, as well as presented this issue to Eshan and worked with Autodesk on a resolution. Autodesk has determined the issue is on the pyRevit side, and are willing to collaborate on a solution via the ADN. Here is the issue:
We've tried this on pyRevit v4.8.13, 15 and now 16. We've seen this in multiple versions of Revit, but notably the crashes seem to be only in 2024. We've also tried hosting the TXT file in different locations, ACC vs local server, with the same behavior. What happens is that when more than one person edits the same keynote WHILE another person has the editor open as well, upon trying to place that keynote, they will receive the pop-up from Revit saying "X owns the element" with the option to Place Request or Cancel. Choosing Cancel on this pop-up crashes Revit 2024. In Revit 2023, choosing Cancel forces both parties to sync before anything else can be done in keynotes.
There are inconsistent indicators that the particular keynote is being edited, but when this does show, it's works well because it prevents anyone from touching that keynote. It just rarely shows that info.
⌨ Error/Debug Message
If the "editing" note shown on an individual keynote would show consistently on all notes being touched, it would be helpful. Ultimately though, pyRevit needs ot properly relinquish the TXT back so that Revit does not encounter the ownership error that leads to the crash.
♻️ To Reproduce
2 users need to be working in the same project using Manage Keynotes.
⏲️ Expected behavior
Either the note indictaing a keynote has/is edited, or non-crashing when ownership error is encountered.
🖥️ Hardware and Software Setup (please complete the following information)
Additional context
No response
The text was updated successfully, but these errors were encountered: