feat(java): static-DAG workflows + package-by-feature reorg#305
Conversation
|
Warning Review limit reached
More reviews will be available in 32 minutes and 38 seconds. Learn how PR review limits work. Your organization has run out of usage credits. Purchase more credits in the billing tab to continue. ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the 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 credits. 🚦 How do rate 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 see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: ⛔ Files ignored due to path filters (1)
📒 Files selected for processing (56)
✨ Finishing Touches🧪 Generate unit tests (beta)
Comment |
Sixth of the Java SDK split series (follows #304). Static-DAG workflows over the JNI core, plus a package-by-feature reorganization of the root package.
What's here
workflowscargo feature ontaskito-java(pullstaskito-workflows) + 4 native fns — submit (builds the dagron DAG from the steps JSON), markNodeResult, getStatus, cancel. Javaworkflows/package: aWorkflow/Stepbuilder,WorkflowRun.await,WorkflowStatus/NodeSnapshot,WorkflowState/NodeStatusenums, and a host-sideWorkflowTracker.Queue.submitWorkflow/workflowStatus/cancelWorkflow+Worker.Builder.trackWorkflows(). Steps run in topological order; the tracker advances node/run state from worker outcomes.refactor(java): organize root package by feature): the rootorg.byteveda.taskitopackage now holds only the front door (Taskito,Queue,DefaultQueue,TaskitoException); everything else moves into feature subpackages (task,model,worker,locks,scheduling, alongside the existingworkflows,serialization,middleware, etc.). Pure structural move — AWS-v2/Stripe convention.Verification
Full
./gradlew build --no-daemonpasses: cargo build--features postgres,redis,workflows+ compile + Spotless + Checkstyle + tests, native bundled. The Java CI job (added in #304) runs the same command.