Skip to content

Only clusters with a non-None rect can become active parents during m…#155

Merged
hbmartin merged 1 commit into
masterfrom
testing-timeouts
Jul 9, 2026
Merged

Only clusters with a non-None rect can become active parents during m…#155
hbmartin merged 1 commit into
masterfrom
testing-timeouts

Conversation

@hbmartin

@hbmartin hbmartin commented Jul 9, 2026

Copy link
Copy Markdown
Owner

…embership walking.

No-rect clusters are now transparent, so descendants fall back to the nearest rendered ancestor. Implemented a CI hang guard.

Review in cubic

…embership walking.

No-rect clusters are now transparent, so descendants fall back to the nearest rendered ancestor.
Implemented a CI hang guard.
@cursor

cursor Bot commented Jul 9, 2026

Copy link
Copy Markdown

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

@coderabbitai

coderabbitai Bot commented Jul 9, 2026

Copy link
Copy Markdown
Contributor

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 40 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: Repository UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 99084510-dff7-4a60-84a3-2b831ae07b53

📥 Commits

Reviewing files that changed from the base of the PR and between 368b06a and bd38d81.

📒 Files selected for processing (3)
  • graphviz2drawio/graphviz2drawio.py
  • scripts/drawio_export.sh
  • test/test_graphs.py
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch testing-timeouts

Comment @coderabbitai help to get the list of available commands.

@sonarqubecloud

sonarqubecloud Bot commented Jul 9, 2026

Copy link
Copy Markdown

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request updates the cluster membership logic in graphviz2drawio to ignore clusters without rendered rectangles, allowing nodes to be parented by their nearest rendered ancestor. It also introduces rendering timeout support in drawio_export.sh using timeout or gtimeout, disables GPU and dev-shm-usage on Linux, and adds corresponding unit tests. Feedback suggests simplifying the timeout command detection in the shell script to avoid redundant command checks.

Important

The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.

Comment thread scripts/drawio_export.sh
Comment on lines +78 to +86
if command -v timeout > /dev/null 2>&1; then
command -v timeout
return 0
fi

if command -v gtimeout > /dev/null 2>&1; then
command -v gtimeout
return 0
fi

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

medium

We can simplify the render_timeout_command function by avoiding running command -v twice for each command check. Instead, we can directly output the command name once the check succeeds.

Suggested change
if command -v timeout > /dev/null 2>&1; then
command -v timeout
return 0
fi
if command -v gtimeout > /dev/null 2>&1; then
command -v gtimeout
return 0
fi
if command -v timeout > /dev/null 2>&1; then
echo "timeout"
return 0
fi
if command -v gtimeout > /dev/null 2>&1; then
echo "gtimeout"
return 0
fi

@hbmartin
hbmartin merged commit 040a0d0 into master Jul 9, 2026
16 of 17 checks passed
@hbmartin
hbmartin deleted the testing-timeouts branch July 9, 2026 16:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant