Hacktoberfest 2026: the issues maintainers tagged for October, open and beginner-friendly. Browse Hacktoberfest issues

intent: a roll-up status: without statusWhenPartial (or statusWhenFull) generates uncompilable Java - the whole app 404s

Open
  • Is something wrong?
#7,941 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
3/5
Estimated time
1-2 days
Newbie friendliness
55/100
Issue type
Bug
Clarity
Clearly specified
Activity status
Active
Tech stack
java
Domain
backend

Research direction

Read IntentParser and trace how it validates the roll-up status configuration; compare that with GlueIntentGenerator and RollupAggregates.appendStatus. Start by running the existing RollupAggregatesTest and identify coverage for only one of statusWhenFull and statusWhenPartial being set. Done means this configuration is rejected with the missing key named, or status emission handles the missing value, with a regression test confirming the behavior.

Written by the indexing model from the issue text.

Description

Problem

A sum roll-up that declares status: + statusWhenFull: but no statusWhenPartial: (or the reverse) passes the parser and generates Java that does not compile. Because one javac task compiles the whole client-Java batch, every controller of the app 404s, not just the roll-up.

Where (release commit 862f6d1a, 14.93.0)

  • GlueIntentGenerator writes the missing key as "": base.put("statusWhenPartial", withStatus && rollup.getStatusWhenPartial() != null ? ... : "") (GlueIntentGenerator.java ~L705-710).
  • RollupAggregates.appendStatus splices it in verbatim: java.util.Objects.equals(parent.Status, ) and parent.Status = sum.compareTo(capacity) >= 0 ? 7 : ; (RollupAggregates.java L186-L215). The same file already guards capacityField / balanceField with strOrEmpty for exactly this reason. The status pair has no such guard.
  • IntentParser checks only that status: is a to-one relation of the parent. It never requires both statusWhenFull and statusWhenPartial.
  • RollupAggregatesTest covers both-set and both-empty, but not one set with the other missing.

Expected

Either the parser refuses status: without both statusWhenFull and statusWhenPartial (naming the missing key), or the emission treats a missing one as "leave the status alone in that band". The refusal is the smaller fix.

Found on 14.88.0 by BusinessIntents (wave 2026-10-17, base-fixed-assets / base-cash-desk) and re-checked against the 14.93.0 source; still present.

🤖 Generated with Claude Code

Dominant language
Java
Stars
278
Forks
97
Avg merge
18h 53m
Merged PRs (30d)
228

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from eclipse-dirigible/dirigible

All issues in eclipse-dirigible/dirigible

Similar issues

More Java issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.