Is the dashboard output of 1.2.1 supposed to validate (I get numerous failures)? I''m seeing some issues that I hadn''t been running into before my upgrade. The first time I load the dashboard I''m seeing a blank area at the top and first button isn''t styled. When the refresh triggers the all of the projects except the first are duplicated and the display looks correct (except the duplicated projects aren''t updated with the current build status). I installed into a new tree and copied the projects over. Regards, Lee
On Wed, Mar 12, 2008 at 12:39 PM, Lee Cantey <lcantey at gmail.com> wrote:> Is the dashboard output of 1.2.1 supposed to validateGiven that I don''t understand the question, the answer is probably "no" :)> (I get numerous failures)?Hmm... I never saw (or heard of) the symptoms you are describing. Does the dashboard log say anything enlightening? -- Alexey Verkhovsky CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] RubyWorks [http://rubyworks.thoughtworks.com]
On Mar 12, 2008, at 1:42 PM, Alexey Verkhovsky wrote:> On Wed, Mar 12, 2008 at 12:39 PM, Lee Cantey <lcantey at gmail.com> > wrote: >> Is the dashboard output of 1.2.1 supposed to validate > > Given that I don''t understand the question, the answer is probably > "no" :)Ahh, I just checked the demo server and it doesn''t validate either. http://validator.w3.org/check?uri=http%3A%2F%2Fcruisecontrolrb.thoughtworks.com%2Fprojects&charset=%28detect+automatically%29&doctype=Inline&group=0> >> (I get numerous failures)? > Hmm... I never saw (or heard of) the symptoms you are describing. > Does the dashboard log say anything enlightening?Nothing that looks out of the ordinary to me. Regards, Lee
On Wed, Mar 12, 2008 at 3:30 PM, Lee Cantey <lcantey at gmail.com> wrote:> >> Is the dashboard output of 1.2.1 supposed to validate > > Given that I don''t understand the question, the answer is probably > > "no" :) > Ahh, I just checked the demo server and it doesn''t validate either.Duh! Sorry, didn''t pay attention to the subject. And it wouldn''t be bad if it did validate, of course. I added a bug to JIRA. Still, I haven''t seen CC.rb dashboard behave as you describe. It sounds like your browser is unhappy about something that the server spits out. So... let''s try a few more angles: * What browser is it? * Do you see any JavaScript errors? * What is your Ruby version? * Do you actually have Mongrel installed? What version of it? -- Alexey Verkhovsky CruiseControl.rb [http://cruisecontrolrb.thoughtworks.com] RubyWorks [http://rubyworks.thoughtworks.com]
On Mar 12, 2008, at 3:27 PM, Alexey Verkhovsky wrote:> On Wed, Mar 12, 2008 at 3:30 PM, Lee Cantey <lcantey at gmail.com> wrote: > Still, I haven''t seen CC.rb dashboard behave as you describe. It > sounds like your browser is unhappy about something that the server > spits out. So... let''s try a few more angles: > * What browser is it?All browsers I''ve tried (Safari, IE, Firefox).> > * Do you see any JavaScript errors?No.> > * What is your Ruby version?1.8.5 (2006-12-25 patchlevel 12) [i386-mswin32]> > * Do you actually have Mongrel installed? What version of it? >1.1.4-x86-mswin32-60 Note: since I sent my earlier message I do have a trace-back in the logfile, but it''s not occurring during normal dashboard operation. I''ve attached it although I don''t believe it''s related. An interesting thing of note is that we have another server here running 1.2.1 that isn''t exhibiting the same problem. One difference I''ve noted, besides it controlling fewer builds, is during validation there is an extra failure on mine. Ie. they have the same pattern of failures except mine has an additional one at the start right about where the garbled output starts on first load. Looking at the source generated side by side I get an extra <table> inserted right after <div id="projects"> and before the <div id="project_PROJECT_NAME" class="project build_success"> which causes a " Line 55, Column 65: document type does not allow element "div" here." Regards, Lee -------------- next part -------------- A non-text attachment was scrubbed... Name: trace.log Type: application/octet-stream Size: 10759 bytes Desc: not available Url : http://rubyforge.org/pipermail/cruisecontrolrb-users/attachments/20080312/e9c45cc3/attachment-0001.obj -------------- next part --------------
On Mar 12, 2008, at 4:43 PM, Lee Cantey wrote:> An interesting thing of note is that we have another server here > running 1.2.1 that isn''t exhibiting the same problem. One > difference I''ve noted, besides it controlling fewer builds, is > during validation there is an extra failure on mine. Ie. they have > the same pattern of failures except mine has an additional one at > the start right about where the garbled output starts on first > load. Looking at the source generated side by side I get an extra > <table> inserted right after <div id="projects"> and before the <div > id="project_PROJECT_NAME" class="project build_success"> which > causes a " Line 55, Column 65: document type does not allow element > "div" here."So the difference in the number of projects turned out to be key. The problem lies in app/views/projects/index.rhtml and is triggered by greater than five projects. In this case the extra table element is generated and the invalid xhtml seems to be causing the bad behavior. Regards, Lee