fix(nodes): improve error handling in remote node execution

[charliegillet]

Summary

• Replace fragile string-based error origin detection ('RemoteException:' not in msg) with proper type checking (isinstance(e, APERR) and e.ec == Ec.RemoteException)
• Always send error signals to the remote side before re-raising, preventing the remote pipeline from hanging when an already-wrapped RemoteException is caught
• Narrow exception catch from BaseException to Exception to avoid intercepting KeyboardInterrupt and SystemExit

Type

fix

Testing

• Verify remote node pipeline execution completes normally (no regression)
• Trigger an error in local pipeline processing and confirm the remote side receives the error signal instead of hanging
• Trigger a KeyboardInterrupt during remote execution and confirm it is no longer caught by the error handler

Changed files

• nodes/src/nodes/remote/base/IInstance.py — callRemote() error handler
• nodes/src/nodes/remote/server/IInstance.py — handleWebSocket() error handler

🤖 Generated with Claude Code

[coderabbitai]

Warning

Rate limit exceeded

@charliegillet has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 2 minutes and 1 seconds before requesting another review.

Your organization is not enrolled in usage-based pricing. Contact your admin to enable usage-based pricing to continue reviews beyond the rate limit, or try again in 2 minutes and 1 seconds.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 69f8dc7b-b664-48bb-bdb9-b709f14d5bc8

📥 Commits

Reviewing files that changed from the base of the PR and between b6b2dc1 and 02adaef.

📒 Files selected for processing (4)

• apps/vscode/src/providers/views/PageStatus/PageStatus.tsx
• apps/vscode/src/providers/views/PageStatus/styles.css
• nodes/src/nodes/remote/base/IInstance.py
• nodes/src/nodes/remote/server/IInstance.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[ryan-t-christensen]

Looks good @charliegillet - I did test the STOPPING button state — it transitioned in ~0.6ms, so it's never visible in practice. The UI change is correct but the STOPPING state is set in _terminated() (task_engine.py:551) after the subprocess has already exited, not when the stop is requested. To make this useful the server would need to transition to STOPPING at the moment the stop command is issued. As-is the button will never render. That probably warrants a separate issue.

cc @stepmikhaylov

[charliegillet]

@ryan-t-christensen thanks for the thorough testing and the approval! Good catch on the STOPPING state timing — you're right that since _terminated() sets it after the subprocess exits, the button state is effectively invisible. I'll open a separate issue to track moving the STOPPING transition to the moment the stop command is issued on the server side, so the UI can actually reflect it.