Skip to content
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

Crash report from Dynamo 2.10.1.3976 #14726

Closed
elboselyibraheim opened this issue Dec 9, 2023 · 1 comment
Closed

Crash report from Dynamo 2.10.1.3976 #14726

elboselyibraheim opened this issue Dec 9, 2023 · 1 comment

Comments

@elboselyibraheim
Copy link

Issue Description

Please fill in the following information to help us reproduce the issue:

What did you do?

(Fill in here)

What did you expect to see?

(Fill in here)

What did you see instead?

(Fill in here)

What packages or external references (if any) were used?

(Fill in here)

Stack Trace

(From the Dynamo crash window select 'Details' -> 'Copy' and paste here)

OS: Microsoft Windows NT 10.0.22000.0
CLR: 4.0.30319.42000
Dynamo: 2.10.1.3976

Copy link

github-actions bot commented Dec 9, 2023

Hello elboselyibraheim, thank you for submitting this issue! We are super excited that you want to help us make Dynamo all that it can be. However, given that there has been no additional information added, this issue will be closed for now. Please reopen and provide additional information if you wish the Dynamo team to investigate further.

Additional information:

  • Filling in of the provided Template (What did you do, What did you expect to see, What did you see instead, What packages or external references (if any) were used)
  • Attaching the Stack Trace (Error message that shows up when Dynamo crashes - You can copy and paste this into the Github Issue)
  • Upload a .DYN file that showcases the issue in action and any additional needed files, such as Revit (Note: If you cannot share a project, you can recreate this in a quick mock-up file)
  • Upload a Screenshot of the error messages you see (Hover over the offending node and showcase said errors message in the screenshot)
  • Reproducible steps on how to create the error in question.

@github-actions github-actions bot closed this as completed Dec 9, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

No branches or pull requests

1 participant