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.18.1.5096 #15718

Open
juliomax159 opened this issue Dec 10, 2024 · 1 comment
Open

Crash report from Dynamo 2.18.1.5096 #15718

juliomax159 opened this issue Dec 10, 2024 · 1 comment
Labels
needs more info Needs more information from the reporter. NotMLEvaluated

Comments

@juliomax159
Copy link

Issue Description

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

Dynamo version

Dynamo: 2.18.1.5096

Operating system

OS: Microsoft Windows NT 10.0.22631.0

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?

Stack Trace

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

CLR: 4.0.30319.42000

@github-actions github-actions bot added the needs more info Needs more information from the reporter. label Dec 10, 2024
Copy link

Hello juliomax159, thank you for submitting this issue! We are super excited that you want to help us make Dynamo all that it can be. However, we need some more information in order for the Dynamo team to investigate any further.

Can you please fill in the following to the best of your ability:

  • What did you do?
  • What did you expect to see?
  • What did you see instead?.

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
needs more info Needs more information from the reporter. NotMLEvaluated
Projects
Status: Triage
Development

No branches or pull requests

2 participants