Stephan Beal wrote: > FYI: i committed one on top of that. The advantage is that it's > centralized, the disadvantage is that it hashes every manifest before > parsing (to get the UUID, since parsing modifies it). Might be considered > too expensive, considering how rare broken manifests are.
Follow-up. The investigation led to the following patch: http://fossil-scm.org/index.html/vinfo/bf3db3d16e15ee98f5c72ebdc4ff2f2ed1609ff5?sbs=0 which, if I understand correctly, only makes corrections to the error reporting, and does not change any of the core program logic. After that change, Fossil now only reports errors out of the Tcl core that I am using to implement one of my Transfer hooks. My current suspicion is that something about the PKI stuff on my server box has changed, which causes Tcl to have trouble connecting to a remote HTTPS server from my TH1 hooks. I.e. Fossil itself is no longer implicated as a contributing cause. I'll keep pulling on that thread in private, since it now seems it is specific to my particular deployment. Many thanks to Richard and Stephen for looking into it and making the improvement to the error reporting. Eric -- Eric A. Rubin-Smith Aterlo Networks, Inc. http://aterlo.com _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
