is anyone missing any metadata? (patch tag just had another strange crash)
Thomas Hartman
However, I was unable to read state from the latest events file, which
means that the aplication state may be stale (a couple days old):
So, metadata for accounts / repos created in the last couple days
might be missing.
However, the darcs repos are still on the hard disk and should be
accessible via darcs push / pull, they just won't be listed.
I am investigating. Meanwhile, if anyone knows themselves to be
affected please let me know, including account names and other
relevant data (I can't think of any actually).
FWIW, this is the error I got on application start.
patchtag exited: Sat Jun 19 18:47:20 EDT 2010
starting patchtag: Sat Jun 19 18:47:20 EDT 2010
passed sanity check
starting happs server
time: Sat Jun 19 18:47:21 EDT 2010
patchtagserver: internal error: PAP object entered!
(GHC version 6.12.1 for i386_unknown_linux)
Please report this as a GHC bug: http://www.haskell.org/ghc/reportabug
When I moved the latest checkpoint file out of the way it started normally.
Need somewhere to put your code? http://patch-tag.com
Want to build a webapp? http://happstack.com
Jeremy Shaw
Or just remove the checkpoint ?
If you only removed the checkpoint, then it should just replay all the
events and be up to date ?
The 0.6 released is primarily focused on improvements to happstack-
server (and happstack-ixset).
The 0.7 will be focused on happstack-state.
During 0.7, I would like to figure out why patch-tag crashes so much.
Because it shouldn't ;)
- jeremy
> --
> You received this message because you are subscribed to the Google
> Groups "HAppS" group.
> To post to this group, send email to ha...@googlegroups.com.
> To unsubscribe from this group, send email to happs+un...@googlegroups.com
> .
> For more options, visit this group at http://groups.google.com/group/happs?hl=en
> .
>
Thomas Hartman
> "patch-tag-users" group.
> To post to this group, send email to patch-t...@googlegroups.com.
> To unsubscribe from this group, send email to
> patch-tag-use...@googlegroups.com.
> For more options, visit this group at
> http://groups.google.com/group/patch-tag-users?hl=en.
>
>
--
Jeremy Shaw
Investigating this issue, we discovered that some of his update
functions were calling the 'fail' method. This fail was not caught and
cause the whole server to go down when the event was replayed.
Clearly the handling of 'fail' is not correct. It's not obvious what
should happen when you call fail, but making your whole application
fail is certainly not what we want.
If you are *not* currently calling fail inside your query/update
functions, then you should be fine. So for now, just don't call fail.
In the happstack 0.7 we will reexamine this issue and make sure that
something sensible happens if you do call fail.
- jeremy
On Jun 19, 2010, at 6:00 PM, Thomas Hartman wrote: