by Luc Saffre · in Developers · assigned to Sharif Mehedi

Summary

Children

Comments

• 3 years, 11 months ago by Sharif Mehedi about #4692 (public demo site loops with update_found=1 after upgrade) : update_found works fine now.
• 3 years, 11 months ago by Sharif Mehedi about #4692 (public demo site loops with update_found=1 after upgrade) : yes. it's a problem of caching the static files. I will try to fix it.
• 3 years, 11 months ago by Sharif Mehedi about #4692 (public demo site loops with update_found=1 after upgrade) : nope, it still recurses, the only other thing that looks suspicious is the main.js, it looks as if it doesn't make a request to the server to get the main.js ('cos there's no status code and the network tab doesn't give anything on the /static/main.js)
• 3 years, 11 months ago by Sharif Mehedi about #4692 (public demo site loops with update_found=1 after upgrade) : update_found=1, still recurses probably because of nginx cache. I am investigating the scenario.
• 3 years, 11 months ago by Luc Saffre in reply to Sharif Mehedi about #4692 (public demo site loops with update_found=1 after upgrade) : Ta-daa! Bravo!
• 3 years, 11 months ago by Sharif Mehedi about #4692 (public demo site loops with update_found=1 after upgrade) (1 reply) : the nginx voga1r.conf had: location /media Set to: .../lino_local/voga1r/media/
  But as master_site it should point to: .../lino_local/voga1e/media/
• 3 years, 11 months ago by Sharif Mehedi about #4692 (public demo site loops with update_found=1 after upgrade) : Unknown value "cache" probably comes due to the fact that we don't use cache feature at all, we only use storage and cookies. Let's try upgrading the sites and see what happens.
• 3 years, 11 months ago by Sharif Mehedi about #4692 (public demo site loops with update_found=1 after upgrade) : Firefox console says: Clear-Site-Data header found. Unknown value “"cache"”. but the other key works: Clear-Site-Data header forced the clean up of “storage” data. I am not sure yet why firefox says Unknown value "cache"
• 3 years, 11 months ago by Luc Saffre about #4692 (public demo site loops with update_found=1 after upgrade) : The js code around 'update_found' and 'version_mismatch' looks suspicious. But I don't understand enough of it.
• 3 years, 11 months ago by Luc Saffre about #4692 (public demo site loops with update_found=1 after upgrade) : I did a series of code cleanup and optimizations regarding the site cache. TODO: write better docs. The test suite passes, and I would like to release it to jane, froinde and the demos.
• 3 years, 11 months ago by Luc Saffre about #4692 (public demo site loops with update_found=1 after upgrade) : Ha! There is another attribute "site_cache_root", which is probably nonsense.
• 3 years, 11 months ago by Luc Saffre about #4692 (public demo site loops with update_found=1 after upgrade) : The renderer.build_site_cache() is called from Plugin.get_patterns(), i.e. after startup() and before any incoming request. But renderer.build_js_cache() is being called only when the first request comes in. That's because of the build_js_cache_on_startup attribute.
• 3 years, 11 months ago by Luc Saffre about #4692 (public demo site loops with update_found=1 after upgrade) : We tested together that the settings.SITE.kernel.code_mtime does reflect the modification time of the settings.py file after "touch settings.py". And the json files are being re-generated when a next request comes in.
  In DataProvider.js we have: query[constants.URL_PARAM_LINO_VERSION] = window.App.s...
• 4 years ago by Luc Saffre about #4692 (public demo site loops with update_found=1 after upgrade) : Maybe it's because voga1r is a slave site of voga1e.
• 4 years ago by Luc Saffre about #4692 (public demo site loops with update_found=1 after upgrade) : More precisely, on noi1r the loops stopped after manually removing site data. But on voga1r it doesn't even go away after removing site data.
• 4 years ago by Luc Saffre about #4692 (public demo site loops with update_found=1 after upgrade) : Created a new Ticket.