-
Notifications
You must be signed in to change notification settings - Fork 14
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
Revit_Core_Engine: Handle null exception on Nurbs curves in element boundaries #1291
Revit_Core_Engine: Handle null exception on Nurbs curves in element boundaries #1291
Conversation
@vietle-bh to confirm, the following actions are now queued:
There are 30 requests in the queue ahead of you. |
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.
The fix itself makes sense to me and will improve the UX of the adapter - however, please have a look at my comment under the issue before merging.
@pawelbaran to confirm, the following actions are now queued:
|
Please be advised that the check with reference 10063178213 has more than 50 annotations of notes. API limitations restrict annotations to 50. You may need to rerun this check to obtain the next set when you make changes. At the time of reporting this check, there are 266 additional annotations waiting, made up of 266 errors and 0 warnings. |
@pawelbaran to confirm, the following actions are now queued:
There are 26 requests in the queue ahead of you. |
Another failed Installer check although Versioning has passed 😱 |
@vietle-bh to confirm, the following actions are now queued:
|
@BHoMBot check ready-to-merge |
@pawelbaran to confirm, the following actions are now queued:
|
NOTE: Depends on
Issues addressed by this PR
Closes #1290
Revit elements with nurbs curves in their boundaries will fail to pull with the message "Outline isn't closed" message. This PR handles another error this exception then triggers.
Test files
On SharePoint
Changelog