Post Ahu1fHFlRqXEKLcfmS by saagar@federated.saagarjha.com
(DIR) More posts by saagar@federated.saagarjha.com
(DIR) Post #Ahu1fCFE4Q8KnEKfkO by saagar@federated.saagarjha.com
2024-05-03T14:03:21.675982Z
0 likes, 0 repeats
For those of you using Chronicle (even though I told you not to!) I’ve gone ahead and finally added API to get your logs back out: https://github.com/saagarjha/Chronicle/blob/main/Sources/Chronicle/Epilog.swift. Except if I changed the metadata format so old logs don’t parse anymore, which I also did. Don’t say I didn’t warn you.
(DIR) Post #Ahu1fDru26fJpTR4fg by saagar@federated.saagarjha.com
2024-05-03T14:06:57.618402Z
0 likes, 0 repeats
(The updates are pretty minor; the buffer format remains the same. The main change is copying strings into the bundle so logs are now fully self-contained. You don’t need to keep your binaries around to symbolicate anymore.)
(DIR) Post #Ahu1fF0Rnp5vMGRPd2 by saagar@federated.saagarjha.com
2024-05-03T14:11:31.310846Z
0 likes, 0 repeats
(I’m starting to also use it in production myself and liking it a lot, so I doubt it will see many API breaks from here on out. I’ll be sharing some of my experiments with that shortly :) The logging format was just half the story.)
(DIR) Post #Ahu1fGFNBoczCqQqX2 by brzz@mastodon.social
2024-05-03T15:51:25Z
0 likes, 0 repeats
@saagar does this mean 'Chronicle is not yet ready for general-purpose use. In fact it may never be ready for that.' might not stay true? 👀
(DIR) Post #Ahu1fHFlRqXEKLcfmS by saagar@federated.saagarjha.com
2024-05-03T23:31:51.534450Z
0 likes, 0 repeats
@brzz I think I will be unlikely to recommend it for a while–for this to change I would need swift-syntax to stop being bad, and having a little better control over what the compiler does would also be nice. But I understand people will use it anyways so