AIDA and Squeak trunk

>
> I can confirm it works up to update 10382 but stopped working around
> Christmas. Also updating my app from 10382 to newer trunk images
> failed.
>
> The latter was caused due to some underscore assignments in
> SwazooServerTest. Alas this only lets the update succeed but AIDA
> still does not work.
>
> I have a hunch, that the CSS (or imgs) of the header of the page is not
> delivered properly. When the browser waits for the the (login) page to
> be downloaded and I do a SwazooAida demoStop the page is displayed but
> with missing styling for the page header. The actual login is
> displayed properly.
>
> Later I'll try with 6.2 beta.
>
> Cheers,
>
> Herbert                          mailto:[hidden email]
>
> _______________________________________________
> Aida mailing list
> [hidden email]
> http://lists.aidaweb.si/mailman/listinfo/aida
>

> Hi Janko,
>
> JM> Yes, it seems that something is wrong with critical section support. At
> JM> least what Edgar already confirmed - if you switch-off critical sections
> in AIDASite>>>critical: , Aida works well again. Please try and let me know.
>
> unless I misunderstood you, in AIDA6.1 that does not help because
>
> AIDASite>>critical: aBlock is implemented as:
>
>   ^WebTransactionMonitor critical: aBlock
>
> which in turn is already deactivated with a Timestamp of JM 4/25/2007:
> WebTransactionMonitor>>critical: aBlock
>         "For protecting critical sections in parallel execution of web requests. Use it always
>         when you do things, which cannot be disturbed by another request. Example:
>                 WebTransactionMonitor critical: [<a block with critical section>]. "
>
> "       ^self lock critical: aBlock. "
>         ^aBlock value "Semaphore critical: somehow don't work"
>
> exactly the same with the beta including the fact that
> SwazooAida demoStop makes the page appear.
>
>
> Cheers,
>
> Herbert                            mailto:[hidden email]
>
> _______________________________________________
> Aida mailing list
> [hidden email]
> http://lists.aidaweb.si/mailman/listinfo/aida
>

> Hi,
>
> JM> Try to follow Swazoo debugging instructions at
> JM> http://www.swazoo.org/debbuging, maybe the error is somewhere in Swazoo
>
> ok I did start. The only debugging success was to find a typo in:
> "Here are steps to debug your Swazoo absed web projects:"
> (letters exchanged in based so it reads absed)
>
> I did Step one:
> Add breakpoint to SwazooSite>>answerTo: (or your subclass of SwazooSite)
>
>     * if breakpoint is reached, step forward to your code
>     * if not reached, error is in Swazoo code, continue with next step
>
> The breakpoint in AIDASite answerTo: was reached. I stepped through it
> and never got into code which would produce the login page, so I guess
> I should have stepped into at a place where I stepped over.
>
> What happened was that after some stepping several debuggers came up
> (I guess because the browser repeated the request because of a timeout
> but they came up all at once). I closed these debuggers with continue
> but the main debugger went into a circle ending up in the original
> halt I put into answerTo:
>
> So I guess I need more detailed instruction.
> I tried with Aida6.1final2, sport2031 and swazoo2.2.mcz.
>
> But remember it worked up to Trunk 10382 build and the first one I
> noticed it stopped was a 10850 build. So it was a change in Squeak not
> a bug in Swazoo.
>
> I think the most effective steps would be to start from a 10382 trunk
> (sadly I only have one with my app loaded and my modifications to
> swazoo sport and aida) and update one update after the other and see
> which update breaks Aida.
>    
> I you agree that these are the most effective steps I'll go to Squeak
> dev and ask how to start from an older image and do one update at a
> time.
>
>
> Cheers,
>
> Herbert                            mailto:[hidden email]
>
> _______________________________________________
> Aida mailing list
> [hidden email]
> http://lists.aidaweb.si/mailman/listinfo/aida
>