Ashwin Hirschi
2014-12-11 23:29:57 UTC
Hello everyone,
recently, my team started using Fossil. It took me a while to move our
existing code revisions to Fossil repositories. But it was worth it:
everyone's very pleased with what Fossil offers. So, I'm really glad we
made the jump.
Unfortunately, it looks we've also run into strange crashes related to
(HTTP) redirection. Since many team members work from home, their IP
addresses jump around a lot. To help people find each other, we've set up
a simple redirection service.
In this system, each team member has an associated, fixed URL. And
whenever a HTTP GET or POST request on such a URL occurs, the service
redirects the client to the actual (registered) IP address of the
corresponding member.
Strangely enough, this works well *most* of the time. Fossil picks up the
302 redirect, reports it and goes about its business. Regular "fossil
sync" commands seem to work fine, as do other commands that deal with
remote repositories.
But oddly, 9 out of 10 "fossil commit" commands will fail. The application
crashes always seem to occur when Fossil tries to push the changes to the
remote repository. Sometimes the commited changes were still transmitted,
sometimes not...
As I'm currently unable to build and/or debug Fossil, I've taken up
reading and analysing the Fossil source code to try and find the cause.
But I'm hoping others may have run into similar issues or are perhaps able
to reproduce our problems?
By the way, we're all using the official version 1.29 build and are
running in auto-sync mode.
Ashwin.
recently, my team started using Fossil. It took me a while to move our
existing code revisions to Fossil repositories. But it was worth it:
everyone's very pleased with what Fossil offers. So, I'm really glad we
made the jump.
Unfortunately, it looks we've also run into strange crashes related to
(HTTP) redirection. Since many team members work from home, their IP
addresses jump around a lot. To help people find each other, we've set up
a simple redirection service.
In this system, each team member has an associated, fixed URL. And
whenever a HTTP GET or POST request on such a URL occurs, the service
redirects the client to the actual (registered) IP address of the
corresponding member.
Strangely enough, this works well *most* of the time. Fossil picks up the
302 redirect, reports it and goes about its business. Regular "fossil
sync" commands seem to work fine, as do other commands that deal with
remote repositories.
But oddly, 9 out of 10 "fossil commit" commands will fail. The application
crashes always seem to occur when Fossil tries to push the changes to the
remote repository. Sometimes the commited changes were still transmitted,
sometimes not...
As I'm currently unable to build and/or debug Fossil, I've taken up
reading and analysing the Fossil source code to try and find the cause.
But I'm hoping others may have run into similar issues or are perhaps able
to reproduce our problems?
By the way, we're all using the official version 1.29 build and are
running in auto-sync mode.
Ashwin.