Hello Tim,
Monday, July 18, 2005, 6:38:12 PM, you wrote:
snip
TP Another: did this actually work before? The only place I've found
TP that set LoopCallback.exit_status is
TP zope/app/server/servercontrol.py,
TP and both methods there have TODO: ... does not work yet comments
TP (in both Zope
Hi there,
I'm trying to debug the security of a Zope 3 application (in Zope 3.1
beta) and I am having trouble getting ZOPE_WATCH_CHECKERS to work.
If I set it to 1, I expect to see information on which attributes on
which object are denied. I however see nothing whatever.
If I set it to a
On Jul 18, 2005, at 7:04 PM, Garrett Smith wrote:
This might be something on my end, but I figure I'd throw it out in
case it's related to any changes related to naïve/non-naïve time
zones.
Here's the relevant part of the traceback:
File /opt/aktari/zope/src/zope/i18n/format.py, line
On Jul 19, 2005, at 12:22 AM, Garrett Smith wrote:
Now that dates have UTC time zones associated with them, will we be
adjusting how they're displayed in various views? Somehow it
doesn't seem appropriate to display UTC by default. I'd assume Zope
would use the server's timezone offset.
Shane Hathaway wrote:
I'd like to change Zope 3 to log exceptions using
zope.exceptions.exceptionformatter. Zope's exceptionformatter formats
tracebacks with information from __traceback_info__ and
__traceback_supplement__ variables, which is very useful for debugging
problems with page
On Jul 19, 2005, at 12:35 PM, Martijn Faassen wrote:
Martijn Faassen wrote:
Martijn Faassen wrote:
Hi there,
I'm trying to debug the security of a Zope 3 application (in Zope
3.1 beta) and I am having trouble getting ZOPE_WATCH_CHECKERS to
work.
Note that I was trying this as
Hello Tim,
Tuesday, July 19, 2005, 8:18:01 PM, you wrote:
[Tim Peters]
None of the above appears to have anything to do with LoopCallback,
though, so if any of that used to work but doesn't anymore, there's
a cause outside of the changes I made to LoopCallback. Best guess is
that the stuff
[Tim Peters]
...
Best guess is that the stuff above never worked in Zope3, and that's
the meaning of the TODO: ... does not work yet comments in
zope/app/server/servercontrol.py.
[Adam Groszer]
Yes, you're right. I just missed my old buddy, the Shutdown function.
I think the functions were
[Adam Groszer]
What do you say, can there be any data loss if I use the Shutdown
button? Does Zope write everything out to disc before it quits?
[Tim Peters]
It didn't look to me like there's any code in Zope3 now supporting
controlled (graceful) shutdown, although this is the first time I
Adam Groszer wrote:
[Adam Groszer]
What do you say, can there be any data loss if I use the Shutdown
button? Does Zope write everything out to disc before it quits?
Zope (or rather ZODB FileStorage) writes all transactions to disk when
they are committed. (Baring extraordinary bugs) any
[Adam Groszer]
Or, a better question: how to stop Zope3 cleanly (and when possible
quickly, for development sessions)?
[Tim Peters]
Sorry, no idea here. Anyone else?
[Benji York]
Control-C.
Adam is running on Windows. Bring up Zope3 from a DOS box, and after
it's running hit Ctrl+C in the
Tim Peters wrote:
Adam is running on Windows.
Sorry, my email has been up and down today, I didn't read the message
mentioning that until later.
Ctrl+Break stops it instantly, but then the C libraries don't get a
chance to clean up (like Unix kill -9).
The Windows Service shutdown code
So this will specifically impact:
- The use of date/time formatters
- Date/time widgets
Anything else?
Since datetime values are immutable, I assume you're envisioning that widgets
create tz-aware values. With that in mind, I don't understand 'collected
timezone-less times from our forms'.
[Tim Peters]
Ctrl+Break stops it instantly, but then the C libraries don't get a
chance to clean up (like Unix kill -9).
The Windows Service shutdown code in Zope3 also does a very hard
kill (a Win32 TerminateProcess()).
[Benji York]
All very true. I think you'll also agree that it
14 matches
Mail list logo
