Bugs for Sorcery are reported here

[bugzilla-daemon AT metalab.unc.edu]

http://bugs.sourcemage.org/show_bug.cgi?id=5609

acedit AT armory.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |ASSIGNED



------- Additional Comments From acedit AT armory.com  2004-04-05 12:43 -------
/me puts on his 'I am an asshole' hat
erics: regardless of how much code is required to be
touched in order to fix the problem, this is a bug.
Even if we have to rip the guts out of something
(which we dont), this is not a feature request.

Im also going to lean towards the side of the grimoire team
as far as the behavior goes as they're are the ones
in the trenches who have to debug their own spells. If they
can't do that then whats the point in doing this at all?
I will answer to the user first and the code second.

We are not going to add any new features to gaze yet, the last
log for a spell is defined as the last time it was cast no matter
if it fails or not. (unless the guru's want it a different way)
/me removes his hat

Later on we can add room for success and fail logs, versioning in gaze
blah blah blah (lets move ideas for that to the appropriate bug)

as for me, Im having trouble reproducing this. When I cast a spell
I get the last log when it succeeds or fails. I also use
cp /var/log/sorcery/compile/$each-${VERSION} $SDIR/compile 2>/dev/null
in prometheus to snag the logs. The bug reports seem to always have the
correct logs. Granted none of those spells were upgrades.

Can you give me an exact sequence of steps to reproduce this?
Preferably on a 2.4 box.

Or better yet (but more work) make up two versions of a fake
spell so I can reproduce this, pin it down and pound a stake through
the heart of this bug.



------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.