Added retries parameters to pipeline.draw()

[nickprock]

Related Issues

• fixes Add retries parameter to pipeline.draw() to help mitigate mermaid server issues #9045

Proposed Changes:

• Implemented an exponential retry mechanism
• Added max_retries and initial_delay parameters to control retry behavior and allow more customization
• Included unit test to check the correct operation of the retry mechanism and exponential backoff

How did you test it?

unit tests

Notes for the reviewer

@anakin87 check if it's ok, you are cited in the issue.

Checklist

• I have read the contributors guidelines and the code of conduct
• I have updated the related issue with new insights and changes
• I added unit tests and updated the docstrings
• I've used one of the conventional commit types for my PR title: fix:, feat:, build:, chore:, ci:, docs:, style:, refactor:, perf:, test: and added ! in case the PR includes breaking changes.
• I documented my code
• I ran pre-commit hooks and fixed any issue

[coveralls]

Pull Request Test Coverage Report for Build 13922026747

Details

• 0 of 0 changed or added relevant lines in 0 files are covered.
• 8 unchanged lines in 1 file lost coverage.
• Overall coverage increased (+0.006%) to 90.076%

---

Files with Coverage Reduction	New Missed Lines	%
core/pipeline/draw.py	8	87.9%

Totals
Change from base Build 13920793695:	0.006%
Covered Lines:	9730
Relevant Lines:	10802

---

💛 - Coveralls

[davidsbatista]

This is good, and I agree with the PR, but in the future, we probably should:

• only run this test if this file is changed in a PR and not for every single PR
• make sure that, regardless of changes, it runs at least 1 or 2 a week

My point is that running it for every PR might be a might too much charge for mermaid servers - alternatively, we can also host a Docker with a mermaid server and run against that server