ready() method does not wait for changeset index to catch up

digidem / osm-p2p-db

Peer-to-peer database for OpenStreetMap data

BSD 2-Clause "Simplified" License

235 stars 25 forks source link

ready() method does not wait for changeset index to catch up #30

Closed gmaclennan closed 7 years ago

gmaclennan commented 7 years ago

osm.ready() does not wait for the changeset index. As well as fixing this we should make this more robust so that we don't hit this bug again when we add additional indexes, perhaps store all indexes on this._indexes and iterate over each one in ready()?

hackergrrl commented 7 years ago

I think having a list of indexes just pushes the problem to remembering to add the index to the index list. What would be nice is maybe if our tests did a slowdb round, where we'd be more likely to catch issues related to indexes not being caught up.