Jeffrey Chupp's dashboard

Jeffrey Chupp replied on March 14, 2009 12:57 to the idea "Add options for a 2/3 1/3 split?" in Irradiated Software:

Again, I'm pretty specific in my needs, but I would be good with specifying a width for a specific app so that i could hit left and terminal would be 1/3 of the left side or right and it would be 1/3 of the right side, but similar presses with textmate would be 2/3 left or right.

Again, that's just me.

Jeffrey Chupp shared an idea in Irradiated Software on February 25, 2009 16:08:

Add options for a 2/3 1/3 split?

This admittedly might be a rare request, but I typically work with a text-editor at approx 2/3 the horizontal real-estate of my monitor and a terminal window on the other 1/3.

This is the best software I've seen for getting a 1/2 1/2 split, but an option like this one would make it absolutely perfect for me.

Thanks for listening and for making a great product.

Jeffrey Chupp replied on January 04, 2009 23:16 to the problem "Please fix the Digg password policy." in Digg:

It is worse than that. If they were storing passwords securely (hashed w/ salt, please) then they wouldn't care what you put in as a password. It would all get converted into a hash and compared with the hash in the database. The only reason you need to restrict character input on a password is if that password is being stored in plain text.

I hope no one is reusing a password on digg that they use elsewhere. God forbid if the db gets compromised.

Jeffrey Chupp started following the problem "Please fix the Digg password policy." in Digg.

Jeffrey Chupp replied on November 06, 2008 16:18 to the problem "Top level data present, drill-down data missing" in New Relic:

Working great now.

Jeffrey Chupp marked one of Bill Kayser's replies in New Relic as useful. Bill Kayser replied to the problem "Top level data present, drill-down data missing".

Jeffrey Chupp replied on November 04, 2008 20:21 to the problem "Top level data present, drill-down data missing" in New Relic:

Thanks, Jim.

Jeffrey Chupp replied on November 04, 2008 19:46 to the problem "Top level data present, drill-down data missing" in New Relic:

Sure enough, this seems to be the issue. I had my window set at 30 minutes, but if I increase it to 24 hours, I suddenly have data.

I'd like the 30 minute window to still be useful. What's the proper course of action here?

Jeffrey Chupp replied on November 04, 2008 19:42 to the problem "Top level data present, drill-down data missing" in New Relic:

We changed our server time to UTC, but that was awhile back. I didn't realize they needed to be in sync. Should I change the NR time zone now?

Jeffrey Chupp replied on November 04, 2008 19:23 to the problem "Top level data present, drill-down data missing" in New Relic:

I primarily use Safari on a Mac. Also just tried Firefox 3 on the Mac and then went to a windows XP machine and tried IE7. All have the same results.

Jeffrey Chupp replied on November 04, 2008 17:48 to the problem "Top level data present, drill-down data missing" in New Relic:

politics4all
my user is jeff@politics4all.com

Jeffrey Chupp reported a problem in New Relic on November 04, 2008 17:28:

Top level data present, drill-down data missing

I have 2.5.3 installed and I'm getting the top-level information for response time, throughput, etc., but when I click on any item, the charts fail to load any data. All the results are blank and the controller actions are just sorted alphabetically with 0ms response times. Things were running fine until a few days ago (about the time i noticed the visual update to the site). I'm not aware of any changes on our end. Any suggestions?

Incidentally, your FAQ (http://sites.google.com/a/newrelic.co...) still points to the old version number file.

Jeffrey Chupp started following the idea "People search based on political compatibility" in Politics4All.