...
[16:16:51 CDT(-0500)] <pspaude1> @tbain and everyone it looks like early alerts again work locally!
[16:19:39 CDT(-0500)] <js70> one can not simply build linux. https://www.ohloh.net/p/linux/estimated_cost
[16:21:52 CDT(-0500)] <tbain> Thanks for pushing that change up js2144121654654, my local dev is working now 
[16:22:05 CDT(-0500)] <js70> k
[16:22:19 CDT(-0500)] <JasonElwood> Linux CI is running again
[16:22:46 CDT(-0500)] <pspaude1> Yea! It's working.
[16:26:14 CDT(-0500)] <js70> got a fix for:
[16:26:15 CDT(-0500)] <js70> Uncaught Ext.data.proxy.Server.buildUrl(): You are using a ServerProxy but have not supplied it with a url.
[16:26:19 CDT(-0500)] <js70> is there a ticket.
[16:26:24 CDT(-0500)] <pspaude1> @JS that means we can call Jason with complaints about Linux right? But I guess we should be happy he is doing the work of 5092 people a year in 3 minutes.
[16:26:35 CDT(-0500)] <js70> sweet.
[16:26:44 CDT(-0500)] <js70> Jason is the man.
[16:28:14 CDT(-0500)] <pspaude1> No, tbain found that if you use ext-all-debug-w-comments in ssp-main.jsp line 40. It gets rid of that error when going to early alerts and other such stuff. It seems only the error is found locally as I have never seen it on the CI's.
[16:28:27 CDT(-0500)] <js70> not true
[16:28:46 CDT(-0500)] <pspaude1> You found it?
[16:29:07 CDT(-0500)] <js70> ssp.jsb3 had Ssp.model.reference.EarlyAlertReferral in twice and this was causing issues.
[16:29:13 CDT(-0500)] <js70> I had it locally.
[16:29:26 CDT(-0500)] <pspaude1> Ahh, I see.
[16:29:37 CDT(-0500)] <js70> I'll create a ticket and check it in.
[16:29:59 CDT(-0500)] <pspaude1> ... said the blind man as he picked up his hammer and saw!
[16:30:03 CDT(-0500)] <pspaude1> Sounds good.