[Zope] Re: Installing Products with Errors in Zope 2.7.4

[Chris McDonough]

On Thu, 2005-03-10 at 14:35, Tres Seaver wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Dieter Maurer wrote:
> | Tres Seaver wrote at 2005-3-9 16:24 -0500:
> |
> |>...
> |> But crashing without writing the details to the event log | isn't
> |> what I would expect from a debug mode.
> |>
> |> That isn't what I see:  when I try to start Zope for debugging
> |> ('debug-mode on' in zope.conf, running 'zopectl foreground') with a
> |>  broken product, I see the traceback from the broken product on the
> |> console.
> |
> | We usually start Zope with "bin/zopectl start" (because consoles are
> | not garanteed to remain open). And then you see nothing, when there
> | are problems during startup.
> 
> When debugging a starup problem, I always start the appserver in the
> foreground, with debug-mode turned on;  I then Ctrl-C to kill the
> foreground process (once it *does* start) and restart it in the background.
> 
> The only glitch I see in this approach is that I think starting Zope in
> the foreground (via 'zopectl fg') should automatically turn on
> debug-mode;  then I wouldn't need to edit zope.conf, and then re-edit it
> when done.

FWIW, while I don't like the fact that "debug mode" implies a bunch of
different things, I do like the "dont start if there's a code error"
feature that's implied by the debug-mode behavior.  I think the fact
that it drives other people nuts is because (unlike me or Tres), when
they're developing, they start Zope in a background process.  I always
start Zope in the foreground when doing development and I don't do any
development on production instances so I don't care whether the console
goes away or not (I just restart it).

I'd prefer not to waste any time clicking around, finding out something
doesn't work, then ultimately needing to visit the control panel to look
for "broken products".  The error log messages that occur after a
successful startup that fails to initialize a product (because of, say,
a syntax error) are often pretty baroque. 

- C