Re: Always getting WARequestContextNotFound while debugging
Mariano Martinez Peck <[email protected]>
| Newsgroups | gmane.comp.lang.smalltalk.squeak.seaside |
|---|---|
| Message-ID | <CAA+-=mXox7sohVAa+FR9J3oQW_V1sNeBLiaX3MyMwBTzBaxCPQ@mail.gmail.com> |
On Thu, Apr 11, 2019 at 1:27 AM Tim Johnson <[email protected]> wrote: > Hi, > > Since moving to Seaside 3.x in Squeak 5.x, it seems like I haven't been > able to debug as well as I used to. This has been happening for a while > but I just thought I'd ask about it now. It seems worse lately...? > > It seems like after I hit "Debug" on a Seaside Walkback, I go back to my > image and enter the debugger. Then when I try to evaluate / print / > inspect various statements maybe three items down the stack, I always end > up with something like a WARequestContextNotFound window. > > Basically, it seems like I can't interact with anything but the topmost > item in a debugger anymore, but I could be totally wrong about that. > > I don't suppose this would have anything to do with proxying through > Apache or nginx...? > > I'm also having trouble clicking on individual stack items in the Seaside > Walkback, but that might be unrelated, or related to the proxy. > > Hi Tim, I know that feeling. That's why some time ago I implemented my own workaround (super hackish): https://github.com/marianopeck/SeasideDynamicVariablesDebugger -- Mariano Martinez Peck Email: [email protected] Twitter: @MartinezPeck LinkedIn: https://www.linkedin.com/in/mariano-mart%C3%ADnez-peck/ _______________________________________________ seaside mailing list [email protected] http://lists.squeakfoundation.org/cgi-bin/mailman/listinfo/seaside