Repository navigation
Packvium 1.9.0
No API change, but admission is stricter: some requests 1.8 accepted are now refused (see the
weight and length limits below). Answers now agree with the other engines where 1.8 found them
apart.
Changed
- Under a clearance a compressible item bears its load on its own footprint, so its crush
check is stricter andvalidatemeasures its own compressed volume. - A weight is at most
2^63 - 1ticks, and so is every item's weight times its quantity plus
the heaviest tare: past it,invalid_request/above_maximum; a weight written as a JSON
number past2^53 - 1isinvalid_valueand must be a string. - Agrees with the other engines where 1.8 did not: nesting under a clearance shares the
items' own overlap and a deep nesting column nests in pairs; a length past2^53 - 1ticks or
a box past10^30cubic ticks isinvalid_request/above_maximum; a side that reads as zero
ticks isinvalid_value/must be positive; an obstacle box outside its container is
invalid_value/lies outside inner_dimensions, each at its own pointer. validatechecks the centroid (centre_of_gravity_unsupported) and the whole stack's load
(top_load_exceeded), an item on several bearers shared by contact area. It no longer
holds that item's whole weight against every bearer, so it accepts some results 1.8 rejected
and names the overloaded bearer.- A plan beam wider than 1 compares every container type, whatever the node limit.
- A JSON request is checked once, not twice, on the same objects the request check built.
Fixed
- A narrow nesting item under a clearance reported a negative
used_volume_ticks3, and a
deep nesting column on the lattice returnedinvalid_result. - An obstacle origin with a wrong type is refused with
invalid_request, rather than
being defaulted or raisingAttributeError; an explicit null origin defaults to zero,
including in additional boxes. Null coordinates default to zero, and null
additional_boxesdefaults to an empty list, as request admission already permits.