Xen Orchestra has stopped updating commits
-
@JamfoFL No problem, this is an interesting feedback and something we have to improve
No we did not remove Turbo, but it will rebuild everything if you reinstall the dependencies (as the cache is located in
node_modules/
). -
Hi,
Sorry for necroposting here. But just wanted to bump and let y'all know that this is still an issue.
Where right now, the About section will say that I'm on commit 7e66a. With 8 commits behind master 51f95But doing a (several) full update according to installation instructions in the docs. git show -s, tells me that I'm on
commit 51f95b3c8590492164be38a77ad2c7bf5dc42451
-
@jr-m4 said in Xen Orchestra has stopped updating commits:
Hi,
Sorry for necroposting here. But just wanted to bump and let y'all know that this is still an issue.
Where right now, the About section will say that I'm on commit 7e66a. With 8 commits behind master 51f95But doing a (several) full update according to installation instructions in the docs. git show -s, tells me that I'm on
commit 51f95b3c8590492164be38a77ad2c7bf5dc42451
Quick update:
After clearing/deleting the folder node_modules completely along with another upgrade, solved the symptom for me. However, it is quite obvious that the underlying issue isn't fixed.
It might be superfical at first glace. But as @olivierlambert said, it is quite beneficial to know which is the actual commit being used/applied.Also for completeness sake:
I do my updates through a short script that goes through the commands listed in the official installation docs. Along with me using it as a systemd service#!/bin/bash git checkout . &&\ git pull --ff-only &&\ yarn &&\ yarn build &&\ systemctl restart xo-server
-
ping @julien-f
-
@jr-m4 You're saying that
git
no longer updates the repo`?What's the
git pull --ff-only
error message? -
@julien-f
Hi,No. I'm saying that sometimes the "About"-section in XO (source version). Doesn't show the actual commit being used. And is instead lagging behind. Even though the acctual code being compile is on the newest commit.
Removing the node_modules folder, cleared this issue. So there is some cache that doesn't always get updated with new commit versions. -
Are you rebuilding and then refreshing xo-web?
-
@olivierlambert
I amUpdate:
Correction.. I run this script I pasted above. That builds the entire code AFAIK. As to what specific portions of the code that acctually get recompile. I do not know. -
It seems like the commit info is being embedded in to xo-web package. With the new turborepo addition, xo-web isn't rebuilt each time you rebuild XO, which causes the old commit info to be displayed on the About page. AFAICS, this is benign but still misleading.
Pretty sure this is still the reason for the discrepancy.
-
@Danp This is exactly that