Fix custom driver registration after box.cfg()
LeonidVas opened this issue · 0 comments
LeonidVas commented
Now if a custom driver is registered after calling box.cfg() it causes a problem when the instance will be restarted. The cause of the problem is an attempt to recreate a tube of custom type (which is not registered yet).
It's needed to implement a deferment of creating a custom tube until the custom driver will be registered.