[Sputnik-list] Bug in sputnik + xavante/wsapi

[Enrico Tassi]

Hi,
 I'm experiencing a nasty bug using sputnik on top of xavante. The bug is
really nasty since many factors contribute to it. I belive it has
something to do with the load_isolated_launcher in wsapi.common. 

It seems to try to reuse states to speedup the application loading
and if (app_state.mtime == mtime) no reload operation is performed.
Changing this test to fale (always call bootstra_app) solves the issue,
but I'm pretty sure It can not be that wrong thus I must be missing
something...

The bug is easy to reproduce on my setup, just edit a page (like the
configuration file) and change the main colour of sputnik... The
modification does not apply, repeatedly reloading the page gives
sometimes the expected result (the new color shows up) but not always,
while restarting xavante or touching sputnik.ws makes the modification
"stable". The bug is even nastries sometimes, since realoding may lead
the user to loose autentication (like if it was reusing a previous state 
in which the user had not log in yet...).

I've not tried sputnik on top of Apache, but I'll do soon to understand
if the problem is wsapi of wsapi+xavante/rings. Not sure it is
important, but I'm not using luarocks.require (but I'm using the very
same software that luarocks installed, I've just copied it in the right
path so that no luarocks.require is needed).

Any ideas?
-- 
Enrico Tassi