There's an art to debugging with print statements. You need to show enough to be able to identify problems happening, without being so verbose as to overwhelm with useless noise. When #LMDB is built with debug logging enabled, the output can be too voluminous to sift thru.
But it shows exactly what the code is doing, in such a way that you can parse the log and rerun the exact same operations, and get an identical database as a result.
Howard Chu @ Symas /
npub1tt…ex9ud
2023-12-24 11:52:20
Author Public Key
npub1tt4j2zeswksjh5z7zmy283qd4yd920afy9j28xg45wsxzhl9rpjqrex9udPublished at
2023-12-24 11:52:20Event JSON
{
"id": "1520711c3045214bcc2c41dfb2858826fb089b0ac7582b7aed0d65afd34468f7",
"pubkey": "5aeb250b3075a12bd05e16c8a3c40da91a553fa92164a39915a3a0615fe51864",
"created_at": 1703418740,
"kind": 1,
"tags": [
[
"t",
"lmdb"
],
[
"proxy",
"https://mastodon.social/users/hyc/statuses/111635250563665138",
"activitypub"
]
],
"content": "There's an art to debugging with print statements. You need to show enough to be able to identify problems happening, without being so verbose as to overwhelm with useless noise. When #LMDB is built with debug logging enabled, the output can be too voluminous to sift thru.\n\nBut it shows exactly what the code is doing, in such a way that you can parse the log and rerun the exact same operations, and get an identical database as a result.",
"sig": "511caa40bad1d8d670a025c149645deb201db1b14e6c38faf99bae4911faf31623536b9762d9dc89055a2580c07e7cf91e91a3720be56410abe7378d7248390f"
}