Planner mutex lock

[petergarud]

Description

Describe your pull request.

Associated / Resolved Issue

Resolves # or ClickUp card

Design Documents

Link

Steps to Test

Test Case 1

1. Step 1
2. Step 2
3. Step 3

Expected result:???

Key Files to Review

Group 1

• File 1
• File 2

Group 2

• File 3
• File 4

Review Checklist

• Docstrings: All methods and classes should have the file appropriate docstrings which follow the guidelines in the "Contributing" page of our docs.
• Remove extra print statements: Any print statements used for debugging should be removed
• Tag reviewers: Tag some people for review and ping them on Slack

(Optional) Sub-issues (for drafts)

Note: if you find yourself breaking this PR into many smaller features, it may make sense to break up the PR into logical units based on these features.

• Step 1
• Step 2

[sid-parikh]

Thanks, exactly what I was looking for