legion_prof: called `Option::unwrap()` on a `None` value

[syamajala]

Im seeing the following error when running on these logs: https://sapling2.stanford.edu/~seshu/s3d_tdb/DBO_Test_16/run/

Reading log file "prof_0.gz"...

thread 'main' panicked at src/serialize.rs:348:48:
called `Option::unwrap()` on a `None` value
stack backtrace:
   0: rust_begin_unwind
   1: core::panicking::panic_fmt
   2: core::panicking::panic
   3: core::option::unwrap_failed
   4: legion_prof::serialize::parse_event_wait_info
   5: legion_prof::serialize::parse_record
   6: legion_prof::serialize::parse
   7: legion_prof::serialize::deserialize
   8: <alloc::vec::Vec<T,A> as alloc::vec::spec_extend::SpecExtend<T,I>>::spec_extend
   9: rayon::iter::plumbing::bridge_producer_consumer::helper
  10: rayon::iter::extend::<impl rayon::iter::ParallelExtend<T> for alloc::vec::Vec<T>>::par_extend
  11: rayon::result::<impl rayon::iter::FromParallelIterator<core::result::Result<T,E>> for core::result::Result<C,E>>::from_par_iter
  12: legion_prof::main
note: Some details are omitted, run with `RUST_BACKTRACE=full` for a verbose backtrace.

[lightsighter]

I can't reproduce this at all with the latest profiler. Parsing just prof_0.gz as well as all three log files at the same time works for me.

legion_prof archive prof_0.gz 
Reading log file "prof_0.gz"...
Matched 4441384 objects
Warning: This run involved 64 nodes, but only 1 log files were provided. If --verbose is enabled, subsequent warnings may not indicate a true error.
Skipping liveness range computation due to missing logs
Sorting time ranges
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Detected timing skew! Legion Prof found 40632 messages between nodes that appear to have been sent before the (meta-)task on the creating node started (which is clearly impossible because messages can't time-travel into the future). The average skew was at least 198.08 us. Please report this case to the Legion developers along with an accompanying Legion Prof profile and a description of the machine it was run on so we can understand why the timing skew is occuring. In the meantime you can still use this profile to performance debug but you should be aware that the relative position of boxes on different nodes might not be accurate.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Calculating critical paths
Info: Realm event graph data was not present in these logs so critical paths will not be available in this profile.
Created output directory "legion_prof"
Writing level 0 with 1 tiles
[2026-08-04T07:16:44Z WARN  legion_prof::backend::data_source] Debug assertions enabled: checking point overlap. This can be expensive.
Writing level 1 with 4 tiles
Writing level 2 with 16 tiles
Writing level 3 with 60 tiles

and

legion_prof archive *gz                                                                        
Reading log file "prof_0.gz"...
Reading log file "prof_63.gz"...
Reading log file "prof_32.gz"...
Matched 4441384 objects
Matched 4432270 objects
Matched 4423110 objects
Warning: This run involved 64 nodes, but only 3 log files were provided. If --verbose is enabled, subsequent warnings may not indicate a true error.
Skipping liveness range computation due to missing logs
Sorting time ranges
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Detected timing skew! Legion Prof found 108946 messages between nodes that appear to have been sent before the (meta-)task on the creating node started (which is clearly impossible because messages can't time-travel into the future). The average skew was at least 226.27 us. Please report this case to the Legion developers along with an accompanying Legion Prof profile and a description of the machine it was run on so we can understand why the timing skew is occuring. In the meantime you can still use this profile to performance debug but you should be aware that the relative position of boxes on different nodes might not be accurate.
Node 0 appears to be 773.769 us behind node 63 for 559 messages with standard deviation 439.330 us.
Node 32 appears to be 11.854 us behind node 0 for 682 messages with standard deviation 12.936 us.
Node 32 appears to be 621.215 us behind node 63 for 314 messages with standard deviation 354.926 us.
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!! WARNING !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Calculating critical paths
Info: Realm event graph data was not present in these logs so critical paths will not be available in this profile.
Created output directory "legion_prof.1"
Writing level 0 with 1 tiles
[2026-08-04T07:17:47Z WARN  legion_prof::backend::data_source] Debug assertions enabled: checking point overlap. This can be expensive.
Writing level 1 with 4 tiles
Writing level 2 with 16 tiles
Writing level 3 with 60 tiles