Conditional jump or move depends on uninitialised value in apk_db_triggers_read
==8634== Conditional jump or move depends on uninitialised value(s)
==8634== at 0x507EE23: csum_hash (database.c:131)
==8634== by 0x507E8D3: apk_hash_from_key (apk_hash.h:58)
==8634== by 0x507E973: apk_hash_get (apk_hash.h:70)
==8634== by 0x5085B8F: apk_db_get_pkg (database.c:2076)
==8634== by 0x50828F0: apk_db_triggers_read (database.c:1134)
==8634== by 0x5082B19: apk_db_read_state (database.c:1172)
==8634== by 0x5084517: apk_db_open (database.c:1668)
==8634== by 0x5051C88: _D4apkd11ApkDataBaseQn12openDatabaseMFxbZv (ApkDataBase.d:691)
==8634== by 0x5051E64: _D4apkd11ApkDataBaseQn6__ctorMFNcxAyaxQexbZSQBqQBoQBr (ApkDataBase.d:118)
==8634== by 0x1322D1: _D5tests4apkd7install5_mainFAAyaZi (install.d:45)
==8634== by 0x566C9AB: _D2rt6dmain212_d_run_main2UAAamPUQgZiZ6runAllMFZv (in /usr/lib/libdruntime-ldc-shared.so.2.0.90)
==8634== by 0x566C789: _d_run_main2 (in /usr/lib/libdruntime-ldc-shared.so.2.0.90)
==8634== Uninitialised value was created by a stack allocation
==8634== at 0x5082875: apk_db_triggers_read (database.c:1122)
Noticed this one while running apk-polkit's test suite in valgrind. I don't really see how it'd be uninitialized since it should be initialized in apk_blob_pull_csum
on line 1131, but I figured it'd be best to report it either way since I don't know C that well :)