I just posted in the rules of the table thread; the thread on the messageboard says last post 2mins by me, but the post is not there; what gives?
And when I scroll over my name in the main message list; I can read the beginning but entering the thread it is not there at all; very wierd...
Woot; when you grow up you can work with me as most of what I do all day is test; test; test; suggest a change; enact a change; test, test; repeat; lol; life in a quality department of a high tech companty; sigh, never grow up. (grown up to me means you forgot how to make simple activities fun).
oh; and I haven't seen this issue in a while, so, good job.
well, you might check the skinwalkers thread as it seems that person just had an invisible post that finally showed up; just trying to help; lol, with help like mine....
lol; thanks for that; I would like to see more of the list; is interesting. Who knew werewolves were so loquacious.
Pokey pokey!
Tee-hee! *giggles*
Senior Software Developer
|
The messageboard post snapshot gets broadcast and received, but an exception gets thrown while inserting the post into the thread's cache. The exception happens when the database context is firing a deferred fault for the join table between posts and threads. Adding a delegate for databaseContextWillFireArrayFaultForGlobalID shows that the fetch specification, source global ID and relationship look OK to me. Hmmm.
|
Senior Software Developer
|
Naw, they help actually.
Here's a handy hint. When you're working with an in-place change notification network and you notice a method called "shapshotsForUpdateGroupedByEntity", don't fix the typo because that changes the serialVersionUID for the class and therefore messages coming from all the other machines will get dumped instead of processed because the serialVersionUID doesn't match.
I think that's why this method has retained its name over the years. Nobody wants to roll their entire network of instances just to fix it!
RPG Superstar 2013 Top 32
|
Naw, they help actually.
Here's a handy hint. When you're working with an in-place change notification network and you notice a method called "shapshotsForUpdateGroupedByEntity", don't fix the typo because that changes the serialVersionUID for the class and therefore messages coming from all the other machines will get dumped instead of processed because the serialVersionUID doesn't match.
I think that's why this method has retained its name over the years. Nobody wants to roll their entire network of instances just to fix it!
It's amazing how much grief one lousy typo can cause.
~laughter~ Go Code Monkey, Go!!!
~sighs~ My post got eaten! Hands off my meal, you savage server you! ~avoids getting bitten~
BTW, "Calvin" Teter, good joke!
~sighs~ My post got eaten! Hands off my meal, you savage server you! ~avoids getting bitten~If you're referring to this:
~laughter~ Go Code Monkey, Go!!!it wasn't eaten.... just another victim of this bug I'm attempting to squash.
Ah-HA!!! Trying to eat my post are you, oh vile one! ~gets into fencing mode~ Prepare to fight, fiend! ~winks~