Change Details

Since we just check if the `chronikscripthashindex` is unset to return a 400 error, this test was not actually checking that index is wiped the first time the flag is unset. We could be returning that error even with the index still intact on disk. We can at least check the presence of the relevant log line to verify that we hit the function that is supposed to wipe the index..

Since we just check if the `-chronikscripthashindex` init flag is unset to return a 400 error, this test was not actually checking that index is wiped the first time the flag is unset. We could be returning that error even with the index still intact on disk. We can at least check the presence of the relevant log line to verify that we hit the function that is supposed to wipe the index..

Since we just check if the ``-chronikscripthashindex` init flag is unset to return a 400 error, this test was not actually checking that index is wiped the first time the flag is unset. We could be returning that error even with the index still intact on disk. We can at least check the presence of the relevant log line to verify that we hit the function that is supposed to wipe the index..