# 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/lhudyga
@eldersnake Oh that's the same problem as what @jlj ran in to. Just nuke the twtxt.db/config.json file. You'll find it's an empty JSON file 😢 It's a bug I need to fix 😳
@eldersnake Oh that's the same problem as what @jlj ran in to. Just nuke the twtxt.db/config.json file. You'll find it's an empty JSON file 😢 It's a bug I need to fix 😳
err cc @eldersnake (_thank goodness you have multiple pods!_) 🤗
err cc @eldersnake (_thank goodness you have multiple pods!_) 🤗
@prologic thanks mate, I found I had to _also_ delete meta.json as well as config.json as they were both empty files in txtxt.db, but with both nuked, all back up and running 😊
@eldersnake Ahh yeah sorry that makes sense! I will fix this bug in bitcask ASAP because that's becoming more common than I'd like, mostly due to "crashes" or "lost of power" 😢 Can't have shit like this happen and the database not able to either self-heal or yarnd not correctly start back up again 🤦♂️ (_without human intervention_)
@eldersnake Ahh yeah sorry that makes sense! I will fix this bug in bitcask ASAP because that's becoming more common than I'd like, mostly due to "crashes" or "lost of power" 😢 Can't have shit like this happen and the database not able to either self-heal or yarnd not correctly start back up again 🤦♂️ (_without human intervention_)
@eldersnake @prologic Thanks again for the help on this. FYI, my meta.json was empty, but my config.json had maybe 179 bytes in.
@jlj I have PRs out to fix this and automatically recover 👌 Hoping to get them merged soon 👌\n\nAny ideas what caused your crash? 🤔 In @eldersnake ‘s case it was power failure 😁
@jlj I have PRs out to fix this and automatically recover 👌 Hoping to get them merged soon 👌
Any ideas what caused your crash? 🤔 In @eldersnake ‘s case it was power failure 😁
@jlj I have PRs out to fix this and automatically recover 👌 Hoping to get them merged soon 👌
Any ideas what caused your crash? 🤔 In @eldersnake ‘s case it was power failure 😁
@prologic Yup, indeed power failure as the weather has been miserable i.e a massive lack of sun 😅\nWhen I can feed in voltage readings to the RPi I'll probably set up a script to detect when voltage is getting to a certain low point and automatically shut down. Your bitcask fix is no doubt important, but I want to minimize any other potential disk corruptions of course.
@prologic re my crash: unclear. I'm slowly becoming aware of some automated, systemd-initiated restarts on both RPis. Further investigation needed.