Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

All my rayhunter logs dissapeared from the web interface! #199

Open
cooperq opened this issue Mar 25, 2025 · 0 comments · May be fixed by #225
Open

All my rayhunter logs dissapeared from the web interface! #199

cooperq opened this issue Mar 25, 2025 · 0 comments · May be fixed by #225
Labels
bug Something isn't working unplanned

Comments

@cooperq
Copy link
Collaborator

cooperq commented Mar 25, 2025

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.

@cooperq cooperq added bug Something isn't working unplanned labels Mar 25, 2025
untitaker added a commit to untitaker/rayhunter that referenced this issue Mar 30, 2025
Fix EFForg#199
Fix EFForg#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.
@untitaker untitaker linked a pull request Mar 30, 2025 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working unplanned
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant