Xen Orchestra has stopped updating commits

Danp

@julien-f @olivierlambert Would NodeGit provide the needed functionality?

JamfoFL

@Danp @julien-f @olivierlambert Thanks everyone for looking into this. I'm sorry I kicked over such a hornet's nest.

Just to keep everyone up-to-date, I ran through the process to update the commits this morning and it looks like Turbopro was maybe removed or modified? The process to apply the commits went back to the old length of time it took to complete (maybe about two minutes) and my XO About screen is displaying the most recent commit once again.

Thank you!

julien-f

@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/).

jr-m4

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 51f95

But 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

@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 51f95

But 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

olivierlambert

ping @julien-f

julien-f

@jr-m4 You're saying that git no longer updates the repo`?

What's the git pull --ff-only error message?

jr-m4

@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.

olivierlambert

Are you rebuilding and then refreshing xo-web?

jr-m4

@olivierlambert
I am

Update:
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.

Danp

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.

julien-f

@Danp This is exactly that

janpan

Just a small thing from my side, I know this thread is old, but perhaps it might help someone.

I am also updating my xen-orchestra the same way as @jr-m4 with a script, as per documentation instructions.

I also noted that it kept on saying I was behind a commit in the xen orchestra web interface / about page, however the commit was the latest one.

Changing my script from this:

cd /path/to/xen-orchestra/
git checkout .
git pull --ff-only
yarn
yarn build
service orchestra restart

to this, note the yarn build --force:

cd /path/to/xen-orchestra/
git checkout .
git pull --ff-only
yarn
yarn build --force
service orchestra restart

fixed the issue, as it forces a complete rebuild, and it changes the yarn build command to run this (note the force part):

$ TURBO_TELEMETRY_DISABLED=1 turbo run build --filter xo-server --filter xo-server-'*' --filter xo-web --force

instead of this:

$ TURBO_TELEMETRY_DISABLED=1 turbo run build --filter xo-server --filter xo-server-'*' --filter xo-web

This makes the script run a bit longer, but it's not that big of a deal, and it fixes my xen orchestra web interface to always show the latest version.

archw

That happens to me about once every six weeks on one of the XO installs. For what its worth, if I just kill the XO vm and let it reboot, as long as its not out of disk space, it always works the second time.