-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA512 Karsten Loesing: >>> That timestamp is updated as last step of the hourly update >>>>> process. The details documents that you're fetching may >>>>> have been updated before. That would also explain some >>>>> differences. >>> >>> Wouldn't it make sense to mention/use the timestamp of the >>> consensus that has been used to generate the output instead >>> then? > It *is* the timestamp of the consensus that has been used to > generate the output. But generating the documents that go into the > output is not an atomic step. It's an hourly cronjob that runs for > 15--30 minutes and writes documents for all relays to disk, and > only after that is done, the relays-published timestamp is updated > on disk. As I'm saying on one of the tickets, one way to change > this would be to use a database and update all documents in a > single transaction, but that's a major change to the current > design. Which doesn't mean we shouldn't do it, but it's not > trivial, and maybe it's not the most pressing missing feature.
Would it be a quick and dirty fix to state the timestamp for every record separately (to become "more atomic") or does that not fix anything/is not possible? (I have no onionoo insides) "fix" in terms of: a record with a given timestamp should not change over time and multiple instances would provide the same record for a given timestamp. -----BEGIN PGP SIGNATURE----- iQIcBAEBCgAGBQJVO9W9AAoJEFv7XvVCELh0EscP/imDkVPdyuJ+QPcc0vdKcIcv njW2YefPmLgP3NgiSZDCjhj7V2XTf/g99XQqgRupC9i0MoTnc7P8lvbNjXy0b9NL ig8DDoX6JPp4Lx2pPKolQpI2WYPbLCzNazbsmiTGQ7TU8lC/REsvFg3Tf+I+/saq HdL8MyL9rJ55VSlIOmMW7ojx/+mz1j1tBVnOECqNTtOlOY+/5Yx0oYKf4QKDr92c rvj0dw9DPPqcKnbusKp/mosh6whbZDVS5wNv0H90v9J+FpjFIFn//jnhVNzRnj9y t8lKEio+EyhyewaU8DzL4bUkRHCMIhc/1FKfWJJOHctdLm/9/q5BcBM0Imk9x1jM MoGxipqfMgvO4j7cHjBAMtRasMcDjRD9WMNF9xyOknKG/h99v116UJBq/j4MIigs kac/LIY8rEzBz9kNC5Q/R0QaJoBordfYjga7Ky7M4H3SF2FjmL+yJsnnS5zaUwMF UE001JlkiO0slLYJwmuP/30DZm7vd4gqwJrg3Z0WwMYPEROut0gAHr31xJCkDSAQ /gq54YgBM9V57ZJJiP6LYj5/TZFp8/qRlYKm+sBL3WGXnmsuPhfRXkmTbnvGlLnX Pgg9VSJ2YBwpG5xIP4w1U/7rDjlTtsr/D6mK/f4xsuBx8xXJpp0V30HoNibaYSDR f+2pSSo1vAPZjDXTEev+ =ohOR -----END PGP SIGNATURE----- _______________________________________________ tor-dev mailing list tor-dev@lists.torproject.org https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-dev