Neighbor disconnection result in global rib empty

[frozon]

I have the following situation

- gobgp server
  - static neighbor external bgp server
  - static neighbor bgp route server
  - dynamic neighbors (docker container with a bgp daemon runing inside)

If I restart a container, the dynamic neighbor's bgp daemon connection get closed, then the global rib of the main gobgp server get cleared, once the container is back the only route in the global rib is the one from the container.
All neighbor are still there with their adj-in rib being populated as expected. Just the global rib getting screwed.

This is a new behavior it used to work as expected before.

[fujita]

The peer down of a dynamic neighbor deletes routes for the other peers in the global rib, right?
Hmm, I can't reproduce it with the current master. You can reproduce this if you change the dynamic neighbor configuration to the static one? It would be helpful if I could know this bug is about the dynamic neighbor handling or not.