Hi,
Apparently the problem only occurs on my MacBook. On other OS’es the fix seems
to work and I was able to create a docker container that works as expected.
The Not found message probably comes from that there are no fossils in the
directory. Maybe it would be nice to handle that case.
I
Hi,
Finally again some time to test this. I figured out how to set the compiler
flags and how to work with gdb.
During these tests I found out that there is a difference between debian/ubuntu
and fedora/OS X. On debian and ubuntu I’m getting a 404 not found and on
fedora/OS X I have the
2015-06-28 21:06 GMT+02:00 Remco Schoen remco_sch...@me.com:
Finally found some time to test and react. The webserver now “freezes” when
trying to open the repolist, like the request never is closed from the
server side. The process takes 100% CPU then.
Even though I'm not familiar with this
On 6/28/15, Remco Schoen remco_sch...@me.com wrote:
Finally found some time to test and react. The webserver now “freezes” when
trying to open the repolist, like the request never is closed from the
server side. The process takes 100% CPU then.
The way to debug this is to compile Fossil with
Op 27 jun. 2015, om 23:48 heeft Richard Hipp d...@sqlite.org het volgende
geschreven:
I found out, that it never reaches that code. It doesn’t pass this check as
the size of .fossil is larger then 1024. So apparently it already attached
.fossil to the folder path and is trying to use it
A simple fix would seem to be to match *.fossil but not .fossil - in other
words, require a non-empty prefix to consider it a fossil.
../Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
On 6/27/15, David Mason dma...@ryerson.ca wrote:
A simple fix would seem to be to match *.fossil but not .fossil - in other
words, require a non-empty prefix to consider it a fossil.
That's what https://www.fossil-scm.org/fossil/info/ceeb1c331bdb7967
tried to do.
--
D. Richard Hipp
Op 27 jun. 2015 om 15:38 heeft Richard Hipp d...@sqlite.org het volgende
geschreven:
On 6/27/15, David Mason dma...@ryerson.ca wrote:
A simple fix would seem to be to match *.fossil but not .fossil - in other
words, require a non-empty prefix to consider it a fossil.
That's what
On 6/27/15, Remco Schoen remco_sch...@me.com wrote:
Op 27 jun. 2015 om 15:38 heeft Richard Hipp d...@sqlite.org het volgende
geschreven:
On 6/27/15, David Mason dma...@ryerson.ca wrote:
A simple fix would seem to be to match *.fossil but not .fossil - in
other
words, require a non-empty
On Sat, Jun 27, 2015 at 2:53 PM, David Mason dma...@ryerson.ca wrote:
A simple fix would seem to be to match *.fossil but not .fossil - in other
words, require a non-empty prefix to consider it a fossil.
That's what Richard's patch does. The checkin comment: In the fossil
server --repolist
On 6/27/15, Remco Schoen remco_sch...@me.com wrote:
Op 27 jun. 2015, om 17:01 heeft Richard Hipp d...@sqlite.org het volgende
geschreven:
Op 27 jun. 2015 om 15:38 heeft Richard Hipp d...@sqlite.org het
volgende
geschreven:
On 6/27/15, David Mason dma...@ryerson.ca wrote:
A simple fix
Op 27 jun. 2015, om 17:01 heeft Richard Hipp d...@sqlite.org het volgende
geschreven:
Op 27 jun. 2015 om 15:38 heeft Richard Hipp d...@sqlite.org het volgende
geschreven:
On 6/27/15, David Mason dma...@ryerson.ca wrote:
A simple fix would seem to be to match *.fossil but not .fossil -
Op 26 jun. 2015 om 15:23 heeft Remco Schoen remco_sch...@me.com het
volgende geschreven:
Do you have a file under . that is named *.fossil that is not really
a Fossil repository?
I had a file called .fossil there. If I remove it, it now lists my
repositories.
I found out that the
On 6/26/15, Remco Schoen remco_sch...@me.com wrote:
I have found out where the .fossil comes from. It is the one that fossil
creates in the home folder of the current user. In the case of the docker
image this is the folder /opt/fossil for the user fossil.
Does
Op 26 jun 2015 om 19:49 uur uur schreef Richard Hipp d...@sqlite.org:
I have found out where the .fossil comes from. It is the one that fossil
creates in the home folder of the current user. In the case of the docker
image this is the folder /opt/fossil for the user fossil.
Does
On 6/26/2015 5:59 AM, Remco Schoen wrote:
I'm trying to host a directory with multiple fossils, but when I want to
list the available repositories, I get this error:
SQLITE_ERROR: no such table: config
Database Error
no such table: config SELECT value FROM config WHERE name='allow-symlinks'
On 6/26/15, Remco Schoen remco_sch...@me.com wrote:
Hi,
I'm trying to host a directory with multiple fossils, but when I want to
list the available repositories, I get this error:
SQLITE_ERROR: no such table: config
Database Error
no such table: config SELECT value FROM config WHERE
Hi,
I'm trying to host a directory with multiple fossils, but when I want to list
the available repositories, I get this error:
SQLITE_ERROR: no such table: config
Database Error
no such table: config SELECT value FROM config WHERE name='allow-symlinks'
The command that I'm using:
fossil
Op 26 jun 2015 om 14:12 uur uur schreef Richard Hipp d...@sqlite.org:
On 6/26/15, Remco Schoen remco_sch...@me.com wrote:
Hi,
I'm trying to host a directory with multiple fossils, but when I want to
list the available repositories, I get this error:
SQLITE_ERROR: no such table: config
19 matches
Mail list logo
