WindPower's dashboard

In the version I have installed, line 1182 is the "Components.utils.reportError(err);" line within the PlaylistPlayback.playURL function:

playURL: function(aURL) {
LOG("playURL");
try {
var core = this.core;
if (!core)
throw Components.results.NS_ERROR_NOT_INITIALIZED;

this._playURL.stringValue = "";
this._metadataURL.stringValue = "";

var uri = newURI(aURL);

// XXXAus: x-mtp uri's are special for the time being. They require
// that we copy the actual content from the device into a temporary
// file on the users hard drive.
if(uri.scheme == "x-mtp") {
return this._handleMTPURI(uri);
}

var file;
try {
file = uri.QueryInterface(Components.interfaces.nsIFileURL).file;
}
catch (err) { }

// See if this is a local file and do a basic integrity check if it is.
if (file) {
if (!file.exists())
throw Components.results.NS_ERROR_FILE_NOT_FOUND;
if (!file.isReadable())
throw Components.results.NS_ERROR_FILE_ACCESS_DENIED;
}

var coreCanPlayURI;
core = this._selectCoreForURI(uri, coreCanPlayURI);

var spec = uri.spec;

this._metadataURL.stringValue = spec;
this._playURL.stringValue = spec;
this._controlTriggered.stringValue = Date.now();

try {
core.playURL(spec);
}
catch(e) {
// XXXAus: SB_EXTERNAL_VIDEO_LAUNCH.
if(e.result == 0x80780001) {
return true;
}
else {
Components.utils.reportError(e);
}
}

LOG( "playURL() '" + core.getId() + "'(" + this.position + "/" +
this.length + ") - playing: " + this.playing +
" paused: " + this.paused
);

// Start the polling loop to feed the metadata dataremotes.
this._startPlayerLoop();

// metrics
var ext = spec.substr( spec.lastIndexOf(".") + 1, spec.length );
if ( ext.length < 1 || ext.length > 6 )
ext = "???"; // Well, we certainly tried to play something.
var protocol = spec.substr(0, spec.indexOf(":"));
if (protocol.length < 1)
protocol = "???"
gMetrics.metricsInc("mediacore.play.attempt", core.getId(), ext + "." + protocol);
} catch( err ) {
Components.utils.reportError(err);
return false;
}
return true;
},

I installed Songbird from the unofficial .deb packages at getdeb.net, so it's probably not the latest version. But would an upgrade really change anything?

Line:1182 is empty line before LOG("playURL.

try {
core.playURL(spec);
}
catch(e) {
// XXXAus: SB_EXTERNAL_VIDEO_LAUNCH.
if(e.result == 0x80780001) {
return true;
}
else {
Components.utils.reportError(e);
}
}

LOG( "playURL() '" + core.getId() + "'(" + this.position + "/" +
this.length + ") - playing: " + this.playing +
" paused: " + this.paused
);

solved.

I noticed the same behavior earlier -- new tweets were intermittently getting interspersed with older ones (though I must admit I didn't try logging out and logging back in). As of now, my Twitter "Recent" stream has stabilized somewhat, and I only see new tweets coming in. If you continue to experience this problem after Twitter announces the successful completion of the 'backfill' process, my suggestion is that you start a new thread here in GetSatisfaction to raise the issue. [ As to being a self-professed 'cyberstalker,' I can totally relate to that! ] – mdy, on April 22, 2008 09:28

Uum...what I could not figure is why the timeline was repaired and then went away again as if 'my cache' was corrupted again having tried to be repaired. Since then I have signed on and off and get different timelines each time. The last twice I have got Tweets globally and had the same timeline. What is strange is the 'yo-yoing'. As if it rebuilds but keeps hitting a faulty bit and jumps. What is amazing is that a few weeks ago I was not even a user and now I am actually concerned I cannot see the people I am following. I have become a cyber-stalker! – adrian moss, on April 22, 2008 08:51

@biz mentioned above that they are "back filling the timelines" -- which to me means they're publishing all the tweets that we hadn't seen over the weekend. That explains why they're old. Once they've finished backfilling, things will have caught up with the present once again. 8-) As to geography, I'm not sure, but my guess is that you were seeing less US-based users right then because the tweets that were being back-filled or posted were sent hours earlier -- when people were still sleeping in the US. – mdy, on April 22, 2008 08:37

Sorry. Don't think this is fixed. Could be me but one minute saw all my Tweets and next minute went back to 10 hours old with all recent ones gone. US based people no Tweets at all. Why a geographic based issue? Tried following/unfollowing. That worked yesterday but now has no effect.

I've got my fingers crossed! Thanks for the update! – Eric Suesz, on April 22, 2008 03:45

Great to hear! – Jake Jarvis, on April 22, 2008 02:15

I suppose It might be solved the problem, but some of my followings are not visible :< – nakameP, on April 22, 2008 02:07

Woah, the timeline is all effed up now! Doc Brown, help! I am so confused. I do not know what Twitter was or what prayin' is. Tommy...TOMMY?

I tell you what good came out of this. We all learned how much we love each other and how much we miss each other in our little Twitterverse. I miss @MouseWords and "maybe" @Tindle, but not really. lol

We also all learned how effective getsatisfaction.com can be in bringing a problem pubic and getting some action. Okay, I know it's public. I'm not stupid. But I still want some pubic action.

Sincere thanks to @biz, @jack and @ev who I tease on a regular basis. But who is this Goldfinger dude and why is Twitter feeding him to the lions?

Catch up soon...

-gj

That explains why I am seeing 2day old tweets appear, good to see a solution has been found

I've got good news. We've caught up with this issue and we're currently backfilling the timelines. This will take a few hours but once things are caught up, we should be back to delivering all updates in a timely fashion. Also, we will have successfully moved to the new memcaching scheme—which will make Twitter better, despite the bumpy road we took to get there.

Wow. I wrote a blog post, went to bed, and now the number of people on this thread has doubled. Thanks, twitter, for at least going public with the issue. You can't hide a three day outage. The best thing to do is put your hand up, admit you broke it, and get on with things. You've made a big step in that direction.

I followed J.Phil's advice, only I just un-followed one of my least favorites and that did the trick; that is, there didn't seem to be a need to find someone new to follow before un-following--unless of course you were afraid of losing them, follow? – quiteme, on April 22, 2008 00:50

J. Phil's solution worked for me, thank you for posting it!

It's nice to see the announce on the web. Thanks.