Skip to content

[Bug] Error UninitializedAllocationDelay() thrown in second run of docker compose #5

Closed
@rubydusa

Description

@rubydusa

For some reason, running docker compose up the second time from a fresh clone causes the UninitiallizedAllocationDelay() error to be thrown.

The error happens in the RegisterOperator.s.sol script when we call modifyAllocations on AllocationManager

This seems to show that the runs are not really stateless, needs further investigation

A work around is to call setAllocationDelay in RegisterOperator.s.sol (see: BreadchainCoop/bls-middleware@8e71c6b)

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions