Gaetan de Menten | 7 Oct 17:32

Cache not invalidated/emptied automatically on 0.8 to trunk upgrade

I'm regularly switching from the 0.8 release to trunk (I have both
versions on my disk), hence my earlier complaint about the path being
specified at several places.

There is another issue to it I forgot to mention: when upgrading from
0.8, to trunk, I have the following error:

Traceback (most recent call last):
  File "/home/ged/devel/qooxdoo/trunk/tool/bin/generator.py", line
133, in <module>
    main()
  File "/home/ged/devel/qooxdoo/trunk/tool/bin/generator.py", line 128, in main
    Generator(config, job, console).run()
  File "/home/ged/devel/qooxdoo/trunk/tool/pylib/generator/Generator.py",
line 413, in run
    classList = self._depLoader.getClassList(smartInclude,
smartExclude, explicitInclude, explicitExclude, variants)
  File "/home/ged/devel/qooxdoo/trunk/tool/pylib/generator/code/DependencyLoader.py",
line 64, in getClassList
    result = self.resolveDependencies(include, block, variants)
  File "/home/ged/devel/qooxdoo/trunk/tool/pylib/generator/code/DependencyLoader.py",
line 103, in resolveDependencies
    self._resolveDependenciesRecurser(item, block, variants, result)
  File "/home/ged/devel/qooxdoo/trunk/tool/pylib/generator/code/DependencyLoader.py",
line 127, in _resolveDependenciesRecurser
    deps = self.getCombinedDeps(item, variants)
  File "/home/ged/devel/qooxdoo/trunk/tool/pylib/generator/code/DependencyLoader.py",
line 175, in getCombinedDeps
    'undef' : static['undef']
KeyError: 'undef'
(Continue reading)

thron7 | 7 Oct 18:49

Re: Cache not invalidated/emptied automatically on 0.8 to trunk upgrade

Gaetan,

you would have had to clear the cache anyway, even if you would be using 
just the trunk all the time, since I made a change to some cache object 
format that made existing trunk caches invalid. (We previously had an 
automatic cache invalidation after changes in the tool chain; we might 
re-establish that at some point).

If you maintain 0.8 and trunk side-by-side, I'd recommend having a 
separate cache for each of them. That would insulate the two 
environments nicely from each other.

Thomas

Gaetan de Menten wrote:
> I'm regularly switching from the 0.8 release to trunk (I have both
> versions on my disk), hence my earlier complaint about the path being
> specified at several places.
>
> There is another issue to it I forgot to mention: when upgrading from
> 0.8, to trunk, I have the following error:
>
> Traceback (most recent call last):
>   File "/home/ged/devel/qooxdoo/trunk/tool/bin/generator.py", line
> 133, in <module>
>     main()
>   File "/home/ged/devel/qooxdoo/trunk/tool/bin/generator.py", line 128, in main
>     Generator(config, job, console).run()
>   File "/home/ged/devel/qooxdoo/trunk/tool/pylib/generator/Generator.py",
> line 413, in run
(Continue reading)

Gaetan de Menten | 8 Oct 09:52

Re: Cache not invalidated/emptied automatically on 0.8 to trunk upgrade

On Tue, Oct 7, 2008 at 6:49 PM, thron7 <thron7 <at> users.sourceforge.net> wrote:

> you would have had to clear the cache anyway, even if you would be using
> just the trunk all the time, since I made a change to some cache object
> format that made existing trunk caches invalid. (We previously had an
> automatic cache invalidation after changes in the tool chain; we might
> re-establish that at some point).

Once you realize the problem comes from the cache, clearing it is not
really a problem... It just can be very confusing, and depending on
your "wakeness"  at the time can take a while to figure out what's
wrong.

> If you maintain 0.8 and trunk side-by-side, I'd recommend having a
> separate cache for each of them. That would insulate the two
> environments nicely from each other.

Thanks for the suggestion. Though, that'll be one more path to
maintain and modify when I switch versions, or is the "cache" key (or
whatever it is called, haven't checked yet) accepting macros?

--

-- 
Gaƫtan de Menten
http://openhex.org

-------------------------------------------------------------------------
This SF.Net email is sponsored by the Moblin Your Move Developer's challenge
Build the coolest Linux based applications with Moblin SDK & win great prizes
Grand prize is a trip for two to an Open Source event anywhere in the world
http://moblin-contest.org/redirect.php?banner_id=100&url=/
(Continue reading)


Gmane