On Thu, May 29, 2014 at 5:45 PM, Michai Ramakers <m.ramak...@gmail.com>
wrote:
> However... is it an idea to at least hint at at permissions being the
> cause of an error, if it is clear at that point in code? (Errors like
> the one given in my example-snippet are not always clear to me.)
>
In fact, you hinted at the problem being potentially permissions-related in
your first post:
> In short, syncing with repo seems to work or not depending of
> perms/ownership of that repo:
;)
This level of error:
> Error: Database error: unable to open database file: {CREATE TEMP
> TABLE onremote(rid INTEGER PRIMARY KEY);}
That happens one level below fossil (in sqlite), and (A) i'm not certain
fossil could recognize it as a permissions problem and (B) the vast, vast
majority of fossil's internals will exit() on any sort of error, which
could lead to the exit() happening in before the code which triggers the
error has a chance to evaluate the error code. Fossil's fail-fast approach
greatly simplifies writing higher-level bits, but also makes it (at times)
impossible (without bypassing the internal APIs) to detect the exact nature
of the error.
--
----- stephan beal
http://wanderinghorse.net/home/stephan/
http://gplus.to/sgbeal
"Freedom is sloppy. But since tyranny's the only guaranteed byproduct of
those who insist on a perfect world, freedom will have to do." -- Bigby Wolf
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
