Re: [fossil-users] Fossil local repository no more able to push checkin (error 141)

[Richard Hipp]

On 4/7/16, Étienne Deparis  wrote:
>
> Since yesterday, one of my machine stopped pushing to upstream. On all
> other machines (I had some stuff to do, so several commit helped me to
> test) I encounter no problem commiting (and thus, pushing) upstream, but
> for one of them pulling is ok, commiting is ok but the « push phase » of
> syncing fails with a return code of 141 (as you can see on screen [3])

That 141 seems to be something your shell is generating.  I don't know
what it means.  I grepped the Fossil sources for 141 and didn't find
anything.  I don't think Fossil ever generates any kind of "141"
error.


-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Fossil local repository no more able to push checkin (error 141)

[Étienne Deparis]

Hello,

First of all, I'm very sorry if this problem has yet been
discussed. I've search on the wiki/doc and quickly on the net, but in
fact I'm not very sure of the cause of my problem, so find an answer was
impossible. I need some help to better understand what is going on my
repository. How to extract log file or debug information from fossil for
instance.

My case :

I've an upstream repository available at [1]

I've cloned this repository on various machines of mine and usually
update it without problem (I use fossil sync by default, thus any commit
made is directly pushed upstream).

This upstream repository is served by a cgi script, as described here
[2] with simple cgi :

#!/usr/bin/fossil
repository: /home/fossil/repo.fossil

I use hiawatha webserver to expose this cgi script inside a chroot on a
custom (non ssl) port, and a second hiawatha webserver elsewhere as
reverse proxy, which expose the https port.

Since yesterday, one of my machine stopped pushing to upstream. On all
other machines (I had some stuff to do, so several commit helped me to
test) I encounter no problem commiting (and thus, pushing) upstream, but
for one of them pulling is ok, commiting is ok but the « push phase » of
syncing fails with a return code of 141 (as you can see on screen [3])

Any other attempt to simply push this repository fails with the same
error code.

Question :

 - what is the signification of this error code ?
 - can I do something to get some more informations on what is
   happening ?
 - could the problem be related to ssl or reverse-proxy configuration
   (even if, for simpler commit (one file modified) it seems to works) ?

Thank you very much for any advice or help on this subject.

Cheers,

Étienne


[1] https://projects.depar.is/divers
[2] http://fossil-scm.org/index.html/doc/trunk/www/server.wiki
[3] http://ovh.to/81uGgtF

--
Étienne Deparis

0x8C9CEE3D
https://etienne.depar.is/
xmpp: etie...@depar.is
twitter: @milouse
06 01 64 22 55
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

[fossil-users] Fossil and SQLite on Slant

[David Mason]

I just added
http://www.slant.co/topics/1274/viewpoints/5/~acid-compliant-scalable-databases~sqlite
and
http://www.slant.co/topics/2727/viewpoints/8/~self-hosted-bug-trackers~fossil
on Slant.co

Others might be better placed to add pros and cons.

../Dave
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] fossil update --latest not working

[Matt Welland]

On Thu, Apr 7, 2016 at 5:04 AM, John Regehr  wrote:

> Argh, thanks, sorry for the noise!
>
> John
>
>
> On 4/7/16 2:02 PM, Richard Hipp wrote:
>
>> On 4/7/16, John Regehr  wrote:
>>
>>> What is the branch tag reported by fossil status? Perhaps the branch you
 were on got renamed?

>>>
>>> It says this:
>>>
>>> tags: pager-get-noinit
>>>
>>> whereas I had previously been on the trunk.  Is that expected that I
>>> will be silently moved between branches?
>>>
>>>
>> Normally Fossil does not move between branches.  Except, if you use
>> the --latest option, it will move to the most latest descendent of the
>> current check-out, regardless of the branch.  So probably what
>> happened is that you did "fossil up --latest" at a time when the
>> pager-get-noinit branch was the latest descendent of the trunk
>> check-in that you were previously on.  But pager-get-noinit is
>> currently a dead-end.  (Maybe we'll merge it to trunk later, or maybe
>> not - still undecided on that.)  And so subsequent "fossil up
>> --latest" commands do not move you off of that check-in because that
>> check-in currently has no descendants.
>>
>
>From a design-for-humans perspective I think fossil should stick to the
branch *name*. The least surprising thing is to end up on the tip of the
branch where you were working previously, not on the tip of some new
branch. If I'm working on "trunk" and do a fossil update and end up on
"some-debug-branch" I will be confused. The symbolic name is the critical
data here IMHO.


>
>> If you want to move to the latest trunk check-in, then the command to
>> use is "fossil update trunk".
>>
>> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] fossil update --latest not working

[Ross Berteig]

On 4/7/2016 5:02 AM, Richard Hipp wrote:

On 4/7/16, John Regehr  wrote:


Is that expected that I will be silently moved between branches?


Normally Fossil does not move between branches.  Except, if you use
the --latest option, it will move to the most latest descendent of the
current check-out, regardless of the branch
If you want to move to the latest trunk check-in, then the command to
use is "fossil update trunk".


That answers a nagging question I'd had: What is the difference between 
"fossil update --latest" and "fossil update tip"?


Answer: "tip" is the very last checkin to any branch, while "--latest" 
is the very last checkin descending from "current".



So now my question is what can we do to the wording of the help for 
update that makes the actual meaning of --latest clearer?


It currently says:

Usage: %fossil update ?OPTIONS? ?VERSION? ?FILES...?

The VERSION argument can be a specific version or tag or branch
name.  If the VERSION argument is omitted, then the leaf of the
subtree that begins at the current version is used, if there is
only a single leaf.  VERSION can also be "current" to select the
leaf of the current version or "latest" to select the most recent
check-in.

Options:
   
   --latest acceptable in place of VERSION, update to
latest version
   


One thing that should be at least hinted at here is that using anything 
other than "fossil update" or "fossil update current" (which are exact 
synonyms) *can* move you to a different branch, and unless you are 
deliberately attempting to change to a different branch that move is 
likely to be surprising.


It should probably also say that "--latest" and "latest" are the same 
thing. As it is worded now, the two ways of describing it seem to hint 
at a difference that isn't there.


I'll take a crack at rewriting that "soon", but if anyone else has ideas 
I'm all ears...


--
Ross Berteig   r...@cheshireeng.com
Cheshire Engineering Corp.   http://www.CheshireEng.com/

___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] fossil update --latest not working

[John Regehr]

Argh, thanks, sorry for the noise!

John


On 4/7/16 2:02 PM, Richard Hipp wrote:

On 4/7/16, John Regehr  wrote:

What is the branch tag reported by fossil status? Perhaps the branch you
were on got renamed?


It says this:

tags: pager-get-noinit

whereas I had previously been on the trunk.  Is that expected that I
will be silently moved between branches?



Normally Fossil does not move between branches.  Except, if you use
the --latest option, it will move to the most latest descendent of the
current check-out, regardless of the branch.  So probably what
happened is that you did "fossil up --latest" at a time when the
pager-get-noinit branch was the latest descendent of the trunk
check-in that you were previously on.  But pager-get-noinit is
currently a dead-end.  (Maybe we'll merge it to trunk later, or maybe
not - still undecided on that.)  And so subsequent "fossil up
--latest" commands do not move you off of that check-in because that
check-in currently has no descendants.

If you want to move to the latest trunk check-in, then the command to
use is "fossil update trunk".


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] fossil update --latest not working

[Richard Hipp]

On 4/7/16, John Regehr  wrote:
>> What is the branch tag reported by fossil status? Perhaps the branch you
>> were on got renamed?
>
> It says this:
>
> tags: pager-get-noinit
>
> whereas I had previously been on the trunk.  Is that expected that I
> will be silently moved between branches?
>

Normally Fossil does not move between branches.  Except, if you use
the --latest option, it will move to the most latest descendent of the
current check-out, regardless of the branch.  So probably what
happened is that you did "fossil up --latest" at a time when the
pager-get-noinit branch was the latest descendent of the trunk
check-in that you were previously on.  But pager-get-noinit is
currently a dead-end.  (Maybe we'll merge it to trunk later, or maybe
not - still undecided on that.)  And so subsequent "fossil up
--latest" commands do not move you off of that check-in because that
check-in currently has no descendants.

If you want to move to the latest trunk check-in, then the command to
use is "fossil update trunk".

-- 
D. Richard Hipp
d...@sqlite.org
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] fossil update --latest not working

[John Regehr]

What is the branch tag reported by fossil status? Perhaps the branch you
were on got renamed?


It says this:

tags: pager-get-noinit

whereas I had previously been on the trunk.  Is that expected that I 
will be silently moved between branches?


Sorry if I'm asking dumb questions-- I'm really just trying to keep my 
interactions with fossil to a minimum while staying up to date with the 
latest sqlite sources.


Thanks,

John
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] fossil update --latest not working

[Scott Robison]

On Thu, Apr 7, 2016 at 4:45 AM, Scott Robison 
wrote:

> What is the branch tag reported by fossil status? Perhaps the branch you
> were on got renamed?
>
> On Thu, Apr 7, 2016 at 2:43 AM, John Regehr  wrote:
>
>> Hi Andy,
>>
>> I'm returning to this topic because I again have a repo that got "stuck".
>>
>> Please see the interaction with fossil below.  I ran "fossil update
>> --latest" and it received 53 artifacts, but didn't end up updating and of
>> my local files.  And in fact, a diff between a fresh checkout of sqlite and
>> the repo below shows that I don't have the latest changes. My experience is
>> that a repo that gets stuck in this fashion will continue to receive
>> artifacts from the server but will never again update my local files with
>> fresh content.
>>
>
Sorry for the premature / top posted reply previously.

Anyway, if you are not on trunk, fossil update --latest will only take you
to the latest commit on whatever branch you are on. If a branch was
renamed, you'll be some place other than where you expected.
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] fossil update --latest not working

[Scott Robison]

What is the branch tag reported by fossil status? Perhaps the branch you
were on got renamed?

On Thu, Apr 7, 2016 at 2:43 AM, John Regehr  wrote:

> Hi Andy,
>
> I'm returning to this topic because I again have a repo that got "stuck".
>
> Please see the interaction with fossil below.  I ran "fossil update
> --latest" and it received 53 artifacts, but didn't end up updating and of
> my local files.  And in fact, a diff between a fresh checkout of sqlite and
> the repo below shows that I don't have the latest changes. My experience is
> that a repo that gets stuck in this fashion will continue to receive
> artifacts from the server but will never again update my local files with
> fresh content.
>
> Thanks,
>
> John
>
>
>
> john@TrustInSoft-Box-V:~$ cd sqlite/
> john@TrustInSoft-Box-V:~/sqlite$ fossil update --latest
> Autosync:  http://www.sqlite.org/cgi/src
> Round-trips: 3   Artifacts sent: 0  received: 53
> Pull done, sent: 2148  received: 33277  ip: 67.18.92.124
>
> ---
> checkout: 0c97b80240b38d60236cd8e1e51954b20f147eed 2016-04-05 00:44:01
> UTC
> tags: pager-get-noinit
> comment:  Avoid unnecessary memset() operations in sqlite3PagerGet().
> (user: drh)
> changes:  None. Already up-to-date
> john@TrustInSoft-Box-V:~/sqlite$
> john@TrustInSoft-Box-V:~/sqlite$
> john@TrustInSoft-Box-V:~/sqlite$ fossil update --latest
> Autosync:  http://www.sqlite.org/cgi/src
> Round-trips: 1   Artifacts sent: 0  received: 0
> Pull done, sent: 289  received: 658  ip: 67.18.92.124
>
> ---
> checkout: 0c97b80240b38d60236cd8e1e51954b20f147eed 2016-04-05 00:44:01
> UTC
> tags: pager-get-noinit
> comment:  Avoid unnecessary memset() operations in sqlite3PagerGet().
> (user: drh)
> changes:  None. Already up-to-date
> john@TrustInSoft-Box-V:~/sqlite$
>
>
>
>
>
> On 3/8/16 3:47 PM, Andy Bradford wrote:
>
>> Thus said John Regehr on Tue, 08 Mar 2016 10:18:15 +0100:
>>
>> This usually works, but every couple of weeks my local repository gets
>>> somehow stuck in a state where  the remote changes appear to be pulled
>>> from the  server, but then they  are not applied to  my local sources.
>>> This has happened about 4 times.
>>>
>>
>> Can you be a little more specific about what this means? For example, do
>> you see the remote changes in  the timeline in your local repository and
>> Fossil simply  does not update your  open checkout to those  versions of
>> the file? Or do you not see the changes at all?
>>
>> Can you provide  some output from the commands you're  running when this
>> problem happens?
>>
>> Thanks,
>>
>> Andy
>>
>> ___
> fossil-users mailing list
> fossil-users@lists.fossil-scm.org
> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>



-- 
Scott Robison
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Re: [fossil-users] fossil update --latest not working

[John Regehr]

Hi Andy,

I'm returning to this topic because I again have a repo that got "stuck".

Please see the interaction with fossil below.  I ran "fossil update 
--latest" and it received 53 artifacts, but didn't end up updating and 
of my local files.  And in fact, a diff between a fresh checkout of 
sqlite and the repo below shows that I don't have the latest changes. My 
experience is that a repo that gets stuck in this fashion will continue 
to receive artifacts from the server but will never again update my 
local files with fresh content.


Thanks,

John



john@TrustInSoft-Box-V:~$ cd sqlite/
john@TrustInSoft-Box-V:~/sqlite$ fossil update --latest
Autosync:  http://www.sqlite.org/cgi/src
Round-trips: 3   Artifacts sent: 0  received: 53
Pull done, sent: 2148  received: 33277  ip: 67.18.92.124
---
checkout: 0c97b80240b38d60236cd8e1e51954b20f147eed 2016-04-05 
00:44:01 UTC

tags: pager-get-noinit
comment:  Avoid unnecessary memset() operations in 
sqlite3PagerGet(). (user: drh)

changes:  None. Already up-to-date
john@TrustInSoft-Box-V:~/sqlite$
john@TrustInSoft-Box-V:~/sqlite$
john@TrustInSoft-Box-V:~/sqlite$ fossil update --latest
Autosync:  http://www.sqlite.org/cgi/src
Round-trips: 1   Artifacts sent: 0  received: 0
Pull done, sent: 289  received: 658  ip: 67.18.92.124
---
checkout: 0c97b80240b38d60236cd8e1e51954b20f147eed 2016-04-05 
00:44:01 UTC

tags: pager-get-noinit
comment:  Avoid unnecessary memset() operations in 
sqlite3PagerGet(). (user: drh)

changes:  None. Already up-to-date
john@TrustInSoft-Box-V:~/sqlite$





On 3/8/16 3:47 PM, Andy Bradford wrote:

Thus said John Regehr on Tue, 08 Mar 2016 10:18:15 +0100:


This usually works, but every couple of weeks my local repository gets
somehow stuck in a state where  the remote changes appear to be pulled
from the  server, but then they  are not applied to  my local sources.
This has happened about 4 times.


Can you be a little more specific about what this means? For example, do
you see the remote changes in  the timeline in your local repository and
Fossil simply  does not update your  open checkout to those  versions of
the file? Or do you not see the changes at all?

Can you provide  some output from the commands you're  running when this
problem happens?

Thanks,

Andy


___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users