I’m using pijul 1.0.0-alpha.7 in WSL Ubuntu 18.04. pijul log output is not ordered when I checked my thrussh clone:

Change F2FHFNIKI4EEUO4MDSGQHWZHDVCA5UNX3LFOLIFDHL36O77UW3CAC Author: [Author { name: “pmeunier”, full_name: Some(“Pierre-Étienne Meunier”), email: None }, Author { name: “jason-ni”, full_name: Some(“Jason Ni”), email: None }] Date: 2020-11-29 10:17:14.499831538 UTC

Fixing the return value of session::data_noqueue

Change VYDCQWSFMKNH4WO63IE3Q2I5BRRPMLUQEATDYTSKZ2B2NXNYELDQC Author: [Author { name: “pmeunier”, full_name: Some(“Pierre-Étienne Meunier”), email: None }] Date: 2020-11-29 11:12:45.674396964 UTC

Version 0.30.6

Change CQSPFH4HFNKYT2B23UMXCO26P3DBJFEDXF3VVZPQX4QMLZ6UDIOAC Author: [Author { name: “pmeunier”, full_name: Some(“Pierre-Étienne Meunier”), email: None }] Date: 2020-11-28 10:19:30.184619205 UTC

Version 0.30.4

Change HDEDMPBT6TKIKQ67T2UYC7QEKF7PG5I6Y4CMRPBDACFY4S3XEWZQC Author: [Author { name: “pmeunier”, full_name: Some(“Pierre-Étienne Meunier”), email: None }] Date: 2020-11-28 10:18:58.923899355 UTC

Client example

Oh, that’s correct. It’s not ordered by the time at which the change was created, it’s order by application time. Unfortunately this isn’t timestamped. I considered using a timestamp, but because these are not always strictly increasing, I decided against it. We could add one though, in addition to the index of the change.