VisitingLog.exitedAt is sometimes not saved correctly.
fummicc1 opened this issue · comments
Log
22 elements
▿ 0 : Optional
▿ some : 2022-07-13 11:29:50 +0000
- timeIntervalSinceReferenceDate : 679404590.047557
▿ 1 : Optional
▿ some : 2022-07-13 11:37:40 +0000
- timeIntervalSinceReferenceDate : 679405060.051003
- 2 : nil
▿ 3 : Optional
▿ some : 2022-07-13 08:22:34 +0000- timeIntervalSinceReferenceDate : 679393354.085143
▿ 4 : Optional
▿ some : 2022-07-13 08:21:44 +0000 - timeIntervalSinceReferenceDate : 679393304.053942
- timeIntervalSinceReferenceDate : 679393354.085143
- 5 : nil
- 6 : nil
- 7 : nil
- 8 : nil
▿ 9 : Optional
▿ some : 2022-07-13 08:35:47 +0000- timeIntervalSinceReferenceDate : 679394147.066705
- 10 : nil
- 11 : nil
▿ 12 : Optional
▿ some : 2022-07-13 02:29:55 +0000- timeIntervalSinceReferenceDate : 679372195.059164
- 13 : nil
- 14 : nil
- 15 : nil
- 16 : nil
- 17 : nil
- 18 : nil
- 19 : nil
- 20 : nil
- 21 : nil
(lldb) po visitingLogs.map(.visitedAt)
▿ 22 elements
▿ 0 : Optional
▿ some : 2022-07-10 14:19:01 +0000
- timeIntervalSinceReferenceDate : 679155541.008708
▿ 1 : Optional
▿ some : 2022-07-11 03:58:29 +0000
- timeIntervalSinceReferenceDate : 679204709.309432
▿ 2 : Optional
▿ some : 2022-07-11 04:07:47 +0000
- timeIntervalSinceReferenceDate : 679205267.351559
▿ 3 : Optional
▿ some : 2022-07-11 04:43:56 +0000
- timeIntervalSinceReferenceDate : 679207436.047801
▿ 4 : Optional
▿ some : 2022-07-11 04:44:46 +0000
- timeIntervalSinceReferenceDate : 679207486.075006
▿ 5 : Optional
▿ some : 2022-07-11 08:49:43 +0000
- timeIntervalSinceReferenceDate : 679222183.066466
▿ 6 : Optional
▿ some : 2022-07-11 08:51:42 +0000
- timeIntervalSinceReferenceDate : 679222302.050003
▿ 7 : Optional
▿ some : 2022-07-12 03:24:51 +0000
- timeIntervalSinceReferenceDate : 679289091.368158
▿ 8 : Optional
▿ some : 2022-07-12 03:33:21 +0000
- timeIntervalSinceReferenceDate : 679289601.055568
▿ 9 : Optional
▿ some : 2022-07-12 04:06:55 +0000
- timeIntervalSinceReferenceDate : 679291615.063822
▿ 10 : Optional
▿ some : 2022-07-12 10:47:59 +0000
- timeIntervalSinceReferenceDate : 679315679.050046
▿ 11 : Optional
▿ some : 2022-07-12 10:53:15 +0000
- timeIntervalSinceReferenceDate : 679315995.061904
▿ 12 : Optional
▿ some : 2022-07-12 11:08:37 +0000
- timeIntervalSinceReferenceDate : 679316917.047841
▿ 13 : Optional
▿ some : 2022-07-13 02:35:25 +0000
- timeIntervalSinceReferenceDate : 679372525.053981
▿ 14 : Optional
▿ some : 2022-07-13 02:47:31 +0000
- timeIntervalSinceReferenceDate : 679373251.076205
▿ 15 : Optional
▿ some : 2022-07-13 04:28:06 +0000
- timeIntervalSinceReferenceDate : 679379286.061886
▿ 16 : Optional
▿ some : 2022-07-13 04:36:51 +0000
- timeIntervalSinceReferenceDate : 679379811.056094
▿ 17 : Optional
▿ some : 2022-07-13 04:37:51 +0000
- timeIntervalSinceReferenceDate : 679379871.046757
▿ 18 : Optional
▿ some : 2022-07-13 08:24:14 +0000
- timeIntervalSinceReferenceDate : 679393454.045661
▿ 19 : Optional
▿ some : 2022-07-13 11:27:39 +0000
- timeIntervalSinceReferenceDate : 679404459.821613
▿ 20 : Optional
▿ some : 2022-07-13 11:30:17 +0000
- timeIntervalSinceReferenceDate : 679404617.082541
▿ 21 : Optional
▿ some : 2022-07-13 11:42:17 +0000
- timeIntervalSinceReferenceDate : 679405337.042955
Solution
Because I just probe earliest log which is at same coordinate as monitoring region, all of exitedAt in visiting logs except the 1st visiting log are null.