Was noticing something like this while testing last night, but hadn't
gotten around to determining if it was in master or just the branch I
was testing.
Are you seeing this even if rpc = False? I noticed this only when my
settings got reset to make rpc = True, though I haven't investigated
it enough to know if that is the rpc flag is just a coincidence.
Another possible correlation I've noticed is that it occurs when I use
a script to spin up multiple VMs in succession, possibly suggesting
some kind of race/timing issue. Does that match your use case?
p.s. moving this to 'confirmed', as i've seen something like it as well, and so think its worthy of investigation.
Was noticing something like this while testing last night, but hadn't
gotten around to determining if it was in master or just the branch I
was testing.
Are you seeing this even if rpc = False? I noticed this only when my
settings got reset to make rpc = True, though I haven't investigated
it enough to know if that is the rpc flag is just a coincidence.
Another possible correlation I've noticed is that it occurs when I use
a script to spin up multiple VMs in succession, possibly suggesting
some kind of race/timing issue. Does that match your use case?
p.s. moving this to 'confirmed', as i've seen something like it as well, and so think its worthy of investigation.