HomeGroupsTalkZeitgeist
This site uses cookies to deliver our services, improve performance, for analytics, and (if not signed in) for advertising. By using LibraryThing you acknowledge that you have read and understand our Terms of Service and Privacy Policy. Your use of the site and services is subject to these policies and terms.
  • LibraryThing
  • Book discussions
  • Your LibraryThing
  • Join to start using.

Error going to "Your Books"

Bug Collectors

Join LibraryThing to post.

1FAMeulstee
Mar 30, 4:23pm Top

Both on the Enlish (.com) as on the Dutch (.nl) LT site I can't reach Your Books. Getting this message:

Some sort of error just happened. The error was logged and Tim has been alerted. If problems persist, email timspaldingAT SIGNlibrarything.com

In most cases, the problem can be fixed by using this link.

The reported error was:

Problem with the concurrent query manager in the LibraryThing Bureau of Garbage Collections.
We have an entire room of trained monkeys working to solve the problem..

2rodneyvc
Mar 30, 5:04pm Top

>1 FAMeulstee: Confirmed for me!

3MarthaJeanne
Edited: Mar 30, 5:22pm Top

I can get to my 'Your books', but not to >1 FAMeulstee:'s, or >2 rodneyvc:'s.

4FAMeulstee
Mar 30, 5:26pm Top

>3 MarthaJeanne: Indeed, I can reach your "Your Books", but still not my "Your Books".

5Lyndatrue
Mar 30, 5:35pm Top

Interesting, in an upsetting sort of way. I'm hoping that it's achieved notice from someone on staff who can fix it, but if it still appears unrepaired in a bit (it's been an hour, already, after all), I may poke Tim directly.

6elenchus
Edited: Mar 30, 5:37pm Top

Same experience here, unable to get to my own account's Your Books, with same Trained Monkey message.

The suggested "In most cases" link does not make a difference other than to duplicate the brown menu header.

7divinenanny
Mar 30, 5:41pm Top

Mine also doesn't work, MarthaJeanne's does

8lilithcat
Mar 30, 6:09pm Top

Mine is okay.

I'm able to get to everyone's library using the "In most cases" link, but am also seeing the duplicate header when I do that.

>7 divinenanny:

I have no problem seeing your books.

This is weird.

9MarthaJeanne
Mar 30, 6:56pm Top

>8 lilithcat: When I follow the "In most cases" link, I get my catalogue, not the one I was trying to see.

10lilithcat
Edited: Mar 30, 8:09pm Top

>9 MarthaJeanne:

Oops! You're right. But, oddly, in a sort that's not the one I usually use.

11VivienneR
Mar 30, 8:40pm Top

I've had the same problem all day - I can go to threads or a book page, but not my catalogue. I signed out and my daughter-in-law signed in to her account and all was well with her books.

12mpultroon
Mar 30, 8:41pm Top

As most have indicated -- unable to get to "Your Books". The link to fix does nothing. Its now been over 3.5 hours. Very frustrating.

13newcrossbooks
Mar 30, 10:47pm Top

Same problem - but TinyCat is working for me so I am able to work round the problem for now by accessing my catalogue via TinyCat.

14Nicole_VanK
Mar 31, 2:23am Top

Confirming

15timspalding
Mar 31, 2:33am Top

I'm looking into this.

16FAMeulstee
Edited: Mar 31, 2:41am Top

>15 timspalding: Don't know what you did, Tim, but my "Your Books" is working again :-)
Thanks!

17timspalding
Edited: Mar 31, 2:50am Top

Yeah. Complex explanation:

1. There's an in-memory cache that contains some details about CK fields, like their names and such.
2. The app needs this. If it's there, it uses it; if it's not it makes it.
3. This in-memory cache got corrupted somehow. My GUESS is that it was requested during a brief downtime earlier today, and then an empty value got stored as if it were correct.
4. If your view had any CK elements, or if you were sorting by a CK element, it looked for values from this cache. When it came back empty, it errored out.
5. I started looking into it and then suddenly it started working. It started working because, on the development server, the cache is refreshed every time you ask for it. This was a convenience while developing it, not an intentional feature. But it had the effect of fixing it.

This was a weird one. And it's the rare bug that gets fixed… unintentionally. I am now analyzing the function to see if I can make it detect the corruption in the future.

18elenchus
Mar 31, 1:48pm Top

Like science, observation of natural experiments often provide insights unlikely if sought intentionally ... those Eureka! moments.

I'm not a developer, but your explanation suggests to me it was a pretty difficult thing to "observe" when not actually looking for it. Nice job that you weren't so focused on your plan that you missed it.

19VivienneR
Mar 31, 2:01pm Top

>17 timspalding: Thank you, Tim. Interesting solution.

20RobertDay
Mar 31, 4:47pm Top

>17 timspalding:, >18 elenchus: My reaction as a professional software tester is to say "Yes, we get them like that sometimes..."

I recollect on one project trying to spot a bug for about three months that only ever manifested itself as a "Did I just see it do that...?" moment that I could never reproduce to order. They're hard to spot, hard to replicate and often hard to explain.

Group: Bug Collectors

903 members

92,483 messages

Bug Tracking

This topic is part of LibraryThing's in-talk bug tracking.

Join or watch Bug Collectors to get "Bug Tracking" under "The World" in Talk all the time.

Bug (edit)

ID: 305349

Category: Uncategorized

Assigned to all

Reported by FAMeulstee

Status: Fixed

Mar 31, 2:50am

51 days since last change

By timspalding

Status log

Reported. FAMeulstee (Mar 30, 4:23pm)

Fixed. timspalding (Mar 31, 2:50am)

About

This topic is not marked as primarily about any work, author or other topic.

Touchstones

No touchstones

About | Contact | Privacy/Terms | Help/FAQs | Blog | Store | APIs | TinyCat | Legacy Libraries | Early Reviewers | Common Knowledge | 134,777,375 books! | Top bar: Always visible