it's because we are fetching a zig dependency. In the fetching actor we fetch things in parallel and we keep a list of outstanding downloads. ZigDependency inherits from Dependency, which is also the type used for acton package dependencies. We have no way to separate the base class from the concrete class here due to a bad class hierarchy and thus we end up trying to delete what is a ZigDependency, also from the list of outstanding Dependency.
From https://github.com/actonlang/acton/actions/runs/11702817027/job/32592475885
it's because we are fetching a zig dependency. In the fetching actor we fetch things in parallel and we keep a list of outstanding downloads. ZigDependency inherits from Dependency, which is also the type used for acton package dependencies. We have no way to separate the base class from the concrete class here due to a bad class hierarchy and thus we end up trying to delete what is a ZigDependency, also from the list of outstanding Dependency.