Repository navigation
Packvium 1.5.0
No API changes. The beam search is faster with identical placements, a block answer reports
its real support, and a misspelt configuration key is now refused (see Fixed).
Changed
- Beam search 18–24% faster, same results. The bound that ranks beam nodes reads prefix
sums built once per step, one binary search per node instead of aBigIntaddition per
future item, and expansions that cannot beat the best plan so far are skipped early.
Fixed
- A block answer reports the support each item really has.
HomogeneousBlockSolverwrote
supportRatio1.0 for every item, including those of a block set on a smaller one, which
overhang it. The bottom layer of each block now reports the share of its base that rests on
something. WithminimumSupportRatioabove zero the block solver is no longer tried at all;
its answer was built and then discarded by validation. - A misspelt
configurationkey is refused. A key the request schema does not declare in
configurationor itseffort_budget(profileforsolver_profile,top_kfor
alternatives) was silently ignored, so the request ran on defaults.ArrayCodec::packnow
throwsInvalidRequestExceptionwith reasonnot_allowedand the key's pointer, for example
/configuration/profile. - A number past PHP's integer range is refused instead of changed. A length or weight of
9223372036854775808became9223372036854775807, and a decimal whose scaled value overflowed
became a float, so the request was solved for a different size than the one sent. Both now
throwInvalidArgumentException("Scaled unit value exceeds integer range"). - An unknown
objectiveor access direction is refused with its pointer. It was
invalid_valuewith an empty field; it is nownot_allowedwith, for example,
/configuration/objective. - Compressible items are no longer laid out as rigid blocks by
HomogeneousBlockSolver. - Refusal messages match the documentation, e.g. a fixed placement with unknown keys says it
cannot carrythem.