* dgud/testcasecuddle:
  mnesia: Flush late messages
  Add Debug info
  mnesia: better debug info when tests fail
  mnesia: Ensure tables are loaded before testing them

* emauton/mnesia_create_table_docfix:
  Fix index for #person.address in create_table/2

* crownedgrouse/fix_mnesia_subscribe_doc:
  Fix xml doc return value mnesia:(un)subscribe

* dumbbell/mnesia-hang-if-remote-stopped-after-proto-negotiation:
  mnesia: Check nodes after protocol negotiation

OTP-12473

During Mnesia startup, after protocol negotiation, the list of connected
nodes is written to "recover_nodes". This list is later used to merge
the schema.

If Mnesia was stopped on a remote node between the protocol negotiation
and the moment the list is stored in "recover_nodes", the remote node
is still considered running: the value of "recover_nodes" stored during
mnesia_down/1 is overwritten. Therefore, this node may be used to
acquire a write lock on the schema in order to perform the merge. In
this case, the remote node never answers to the lock request and Mnesia
hang forever (application:start(mnesia) never returns).

To fix the problem, we check the list one last time and remove from it
all nodes where Mnesia is stopped. And because there is still a chance
for missing mnesia_down event, handle_cast({mnesia_down, ...}, ...)
writes to recover_nodes again, in addition to mnesia_down/1.

{index, [2]} refers to #person.name rather than #person.address, which
caused a little confusion in #erlang today.

{index, [4]} is the correct "hard coded" field for #person.address.