You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If all your Rayhunter logs just dissapeared from the web interface, first of all don't worry, they are still there! This is because of patch #182 which was created to fix #151. Basically if the QMDL Manifest file gets corrupted we have to make a new one and delete the old one, but all your QMDL files are still in the directory and can be downloaded manually over ADB. We hope to fix this with atomic writes to the QMDL manifest in the future.
The text was updated successfully, but these errors were encountered:
FixEFForg#199FixEFForg#151
rayhunter updates manifest files using write **without truncation**.
This means that if the new manifest is shorter than the old one,
trailing bytes of the old data will persist in the new file.
Switch over to atomic file writes so that this bug is fixed + rayhunter
behaves correctly if it is killed mid-write.
EFForg#182 could be reverted as it
seems to mostly be a workaround.
If all your Rayhunter logs just dissapeared from the web interface, first of all don't worry, they are still there! This is because of patch #182 which was created to fix #151. Basically if the QMDL Manifest file gets corrupted we have to make a new one and delete the old one, but all your QMDL files are still in the directory and can be downloaded manually over ADB. We hope to fix this with atomic writes to the QMDL manifest in the future.
The text was updated successfully, but these errors were encountered: