We have included the NeoFS chain in IR app, and now some logic relies on block time (1s for the current dev-env). Most of the boostrap time, IR waits for a new block, which means that usually IR status changes once per second and nobody knows what exact second to pick, so 1s intervals looks more appropriate here. Also, 5 tries after 20s sleep may confuse with its ERROR: for ir-healthcheck Container "blabla" is unhealthy. output, cause most of the time 100s is not enough on my laptop.
We have included the NeoFS chain in IR app, and now some logic relies on block time (1s for the current dev-env). Most of the boostrap time, IR waits for a new block, which means that usually IR status changes once per second and nobody knows what exact second to pick, so 1s intervals looks more appropriate here. Also, 5 tries after 20s sleep may confuse with its
ERROR: for ir-healthcheck Container "blabla" is unhealthy.output, cause most of the time 100s is not enough on my laptop.