Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

intent: the roll-up capacity guard runs before calculatedOnCreate - a calculated child amount is guarded as 0

Abierto
  • ¿Algo no está bien?
#7,943 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
57/100
Tipo de issue
Error
Claridad
Bien especificado
Estado de actividad
Activo
Stack tecnológico
java
Área
backend

Línea de trabajo

Start with components/template/template-application-dao-java/src/main/resources/META-INF/dirigible/template-application-dao-java/data/Repository.java.template, especially save() around lines 439–465 and the update path around line 569. Compare when roll-up capacity guards read the child amount with when create-time and update-time calculated fields are assigned; the body also points to calculatedForCreate(entity) and issues #7542 and #7544. Done when the guard evaluates the calculated amount and rejects a create or update that would exceed capacity.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

Problem

The generated repository's save() runs the roll-up capacity guard before the create-time calculated fields are assigned. A child whose summed of field is calculatedOnCreate (an expression or an action, e.g. Amount = Quantity * Price) reaches the guard as null, which is counted as 0. So the guard never refuses an over-capacity create, and the roll-up then sums the real value and drives the balance negative.

Where (release commit 862f6d1a, 14.93.0)

In Repository.java.template, save():

  • #rollupGuardCheck() / #gatedRollupGuardCheck() run at ~L450;
  • the calculatedActionOnCreate / calculatedPropertyExpressionCreate assignments come at ~L456-L464;
  • the guard body reads entity.<of> and treats null as BigDecimal.ZERO.

guardAt: (#7542) moves the guard to a later status, which works for a document total. It does nothing for a plain calculated child amount on create.

Expected

Assign the create-time calculated fields before the capacity guards, or evaluate the guard on calculatedForCreate(entity) (the candidate row the checks already use, #7544). The same ordering question applies to the update path (~L569 vs the on-update calcs).

Found on 14.88.0 by BusinessIntents (wave 2026-10-17) and re-checked against the 14.93.0 source; still present.

🤖 Generated with Claude Code

Lenguaje dominante
Java
Estrellas
278
Forks
97
Merge medio
19 h 30 min
PR fusionados (30 d)
242

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de eclipse-dirigible/dirigible

Todos los issues de eclipse-dirigible/dirigible

Issues similares

Más issues de Java

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.