Great, thanks.
The timeout was set at 300. I can't remember ever having touched it -- maybe this was the default at some time?
While I'm at it, here's another issue that I have.
As mentioned, I have a setup where I work against a svnsync'ed mirror repo with writethrough to the master. In this environment, a branch/tag operation often fails if either of the options 'switch working copy to new branch/tag' or 'set explicit version for externals' is enabled. The branch/tag creation itself completes successfully, but the followup switch/property operation depends on the new branch/tag being present on the mirror, which may not be the case if svnsync is not quick enough.
Is it possible to have tsvn make sure that the committed revision is visible before performing additional operations?
Cheers,
Oddvar
> -----Original Message-----
> From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
> Sent: 4. mars 2015 19:20
> To: dev_at_tortoisesvn.tigris.org
> Subject: Re: Tsvn update does not always fetch HEAD after commit
>
> On 04.03.2015 16:56, Oddvar Kloster wrote:
> > Hi,
> >
> > I sometimes see the following:
> > * Working copy is at HEAD of trunk, e.g. r100, with changes
> > * Commit r101
> > * Run SVN Update from the explorer context menu
> > -> Working copy is updated to r100
> > * Open log dialog. Shows all revisions, including r101, with r100 in
> > bold
> > * Run Update item to revision r101 in log dialog context menu
> > -> Working copy is updated to r101
> > * Again, run SVN Update from the explorer context menu
> > -> Working copy is updated to r100
> >
> > This situation can persist for perhaps a minute after the commit was made.
> After that, SVN Update correctly updates to r101.
> >
> > Platform: Windows 7, TortoiseSVN 1.8.10, Build 26129 - 64 Bit The
> > repository is a local mirror updated with svnsync, with writethrough to the
> master on commit. I'm assuming that the problem might be related to
> caching in the Apache server.
> > However, running svn update using the command line client correctly
> updates to r101 in this situation. I can switch back and forth between r100
> and r101 many times by updating alternately using the command line and
> tsvn.
>
> The TSVN update command first fetches the HEAD revision before running
> the actual update to ensure that if there are multiple update targets, all
> targets are updated to the same revision (just in case that during the update,
> someone else makes a commit).
>
> And since the log cache also caches the HEAD revision, that's what you're
> seeing here: the HEAD revision of the log cache is used.
>
> You can configure the cache time of the HEAD revision in the settings
> dialog->log caching->timeout in seconds before updating the HEAD
> dialog->revision
>
> by default, that value is set to zero.
>
> I guess you have a different value there.
>
> I'll change it so that for the update command, the log cache HEAD isn't used
> but the actual HEAD.
>
> Stefan
>
> --
> ___
> oo // \\ "De Chelonian Mobile"
> (_,\/ \_/ \ TortoiseSVN
> \ \_/_\_/> The coolest interface to (Sub)version control
> /_/ \_\ http://tortoisesvn.net
>
> ------------------------------------------------------
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessa
> geId=3102873
>
> To unsubscribe from this discussion, e-mail: [dev-
> unsubscribe_at_tortoisesvn.tigris.org].
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=757&dsMessageId=3103054
To unsubscribe from this discussion, e-mail: [dev-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2015-03-05 18:57:23 CET