Yarn

Recent twts in reply to #aticadq

📣 FYI: For those of you still on yarn v0.10.x you might want to update past these revisions:

* e7c423d 2022-01-01 | Remove Cached.IsDead() and Dead field and defer to humans for how to deal with possible dead feeds [James Mills]
* ff89e56 2022-01-01 | Reduce the level of error logging in the Cache.FetechFeeds() (renamed) [James Mills]
* d5230d2 2022-01-01 | Don't skip dead feeds for now [James Mills]

If you’re running v0.10.x with some code I introduced to try deal with potentially dead feeds automatically; that code is bupkis and totally b0rked 😅

Alternatively just upgrade to the latest v0.11.x that was recently released 🥳

⤋ Read More

@jlj@twt.nfld.uk from IRC:

[08:03:38]  <prologic> jlj if you're still around I can help debug wtf is going on with your pod
[08:05:45]  <prologic> jlj hmm yeah for some reason your jlj and support accounts are appearing "external"
[08:05:49]  <prologic> Which is a bit odd
[08:05:56]  <prologic> I'd nuke the data/cache file and restart
[08:06:29]  <prologic> You _might_ have caught a bad revision somewhere along the way :/
[08:08:05]  <prologic> Jlj oh on more thing actually
[08:08:11]  <prologic> Are you using a custom theme or custom templates?

⤋ Read More

@jlj@twt.nfld.uk FWIW you’re coming across the Yarn network just fine 👌 I’d suspect some bad data got into your cache, can’t explain how but it smells like some refactoring I was doing, fubar’d a few things, fixed a few things and so forth 😅

⤋ Read More

I beiege @jlj@twt.nfld.uk’s symptom here is his pod believes his own local accounts are external users (which they are not) – I can only guess bad cache data, but without a tool (TBD) to view the cache itself (maybe we can just write a JSON dumper?) hard to say.

⤋ Read More

Participate

Login to join in on this yarn.