# I am the Watcher. I am your guide through this vast new twtiverse.
#
# Usage:
# https://watcher.sour.is/api/plain/users View list of users and latest twt date.
# https://watcher.sour.is/api/plain/twt View all twts.
# https://watcher.sour.is/api/plain/mentions?uri=:uri View all mentions for uri.
# https://watcher.sour.is/api/plain/conv/:hash View all twts for a conversation subject.
#
# Options:
# uri Filter to show a specific users twts.
# offset Start index for quey.
# limit Count of items to return (going back in time).
#
# twt range = 1 15
# self = https://watcher.sour.is/conv/xk2gaga
Submitted the first PR #241 to Bitcask that is required in order to sort out the yarnd database issues both @eldersnake and @jlj have run in to recently due to power failures or crashes.
Since Bitcask is a production-grade v1 embedded KV store for the Go with _many_ uses beyond my own projects and software, I have to make sure it gets some eyes from other users in the wider community π€
Stay tuned! π€
Submitted the first PR #241 to Bitcask that is required in order to sort out the yarnd database issues both @eldersnake and @jlj have run in to recently due to power failures or crashes.
Since Bitcask is a production-grade v1 embedded KV store for the Go with _many_ uses beyond my own projects and software, I have to make sure it gets some eyes from other users in the wider community π€
Stay tuned! π€
The intention once that PR is merged is to have yarnd check for these errors and basically nuke the offending empty .json files and re-open the database as you _would_ have done by hand (_or as I've instructed in the past_) π
The intention once that PR is merged is to have yarnd check for these errors and basically nuke the offending empty .json files and re-open the database as you _would_ have done by hand (_or as I've instructed in the past_) π
@prologic Should the original error be wrapped so you get a bit more information on the cause?
The PR for the yarnd side is now done => PR #474=
The PR for the yarnd side is now done => PR #474=
@lyse Hmmm yes probably but that would require a much more custom error type I guess π€
@lyse Hmmm yes probably but that would require a much more custom error type I guess π€
Good stuff @prologic. I guess this is one of the handy things about having a few extra pods in the wild, you come across some edge cases like this! (if you'd call it an edge case)
@eldersnake Yup! π Itβs only because of increased pods in the wild many improvements have been discovered π
@eldersnake Yup! π Itβs only because of increased pods in the wild many improvements have been discovered π