-
Notifications
You must be signed in to change notification settings - Fork 4
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
Occasional Errors When Generating Large Diagrams #33
Comments
@jamestiotio sorry for the late reply, been busy getting new TALA release out. Can you try again with the diagram you tried with? it should be faster now. also if you get a panic, would love to get a few more lines of the stack trace (to get to a line number). |
Sure, I have attached this file that contains the complete logs when I encountered the panic. I managed to reproduce the panic using d2 v0.2.1 and TALA v0.3.0. It seems that only the last part of the logs is relevant:
|
Additionally, it seems that a diagram that was successfully generated on older TALA versions (tested on v0.2.15) can fail to compile on v0.3.0 of TALA with the following error:
The
This is strange since using only the above declaration works (as demonstrated here), but in the context of additional nodes and connections present in a large diagram such as mine, it fails. |
ah shoot, someone added that feature flag and forgot to add it to TALA plugin. i'm going to release a hotfix for that. thank you for surfacing. cc @gavin-ts |
No problem. Testing with TALA v0.3.1 (which includes the hotfix for the container self-loop edges) seems to indicate that it is much more stable now. I have not encountered any |
With d2 v0.4.2 and TALA v0.3.7 I am facing a similar issue on a fairly complex graph. The output and the failure is:
|
@orange-buffalo would you mind sending me the D2 for that for us to investigate? [email protected] if you prefer email |
@alixander, sent via email, hopefully it does not end up in the spam folder :) |
@alixander, is there anything else we can provide to help with the investigation? We are currently evaluating TALA to support our architecture diagrams, and this issue is a blocker for us. |
oh we actually did fix this but just haven't done a release. will cut one today and email you when it's out @orange-buffalo |
Thanks @alixander! I've tested v0.3.8, but it fails with the same |
@alixander, with v0.3.9 we still observe timeouts on our diagram. Any chance to have a timeout configuration so we could set it is get the diagram generated, even if it takes more time? |
@orange-buffalo just did a new release! should be able to set timeout now with the latest D2 (might have to wait a bit for package managers like homebrew to pick it up) and latest TALA
|
Thank you @alixander! We now have it generated successfully. |
On top of the
err: Timed out: EdgeRouting
error specified in #20, experimenting with different seeds to generate a fairly large diagram would also sometimes produce either of the following errors:The larger the diagram, the higher the chances of these errors occurring (and the lower the chances of successfully generating a diagram).
The diagram does not have to contain$>= 100$ nodes for these errors to start cropping up. I encountered the above issues on a moderately-sized diagram of around 50-60 nodes/shapes (with a maximum of 2 hierarchy levels), 90-100 connections, and a decent amount of text (around 13000 characters including shape labels) sprinkled across the entire diagram.
The text was updated successfully, but these errors were encountered: