When a project is started/restarted launcher details not populated

[hardillb]

Current Behavior

When a project is starting for the first time or is being restarted after being suspended the version details are empty.

Once it enters started state this does not get updated.

Expected Behavior

The launcher, nodejs, and node-red version are populated when the project enters started state.

Steps To Reproduce

Start a new project

Or suspend a project, navigate to the team overview, back to the project and start it.

Environment

• FlowForge version: 0.9
• Node.js version: 16.x
• npm version: 8.x
• Platform/OS: K8s/Linux
• Browser: Chrome

[Steve-Mcl]

@hardillb looking at this for last 45 mins - tried about 20 different combinations with 2 FF installs and 3 different projects - I cannot get this to happen.
I only spend as long as I did as I remember seeing this myself about 2 weeks ago.

My gut feeling is it was fixed when recent PR to wait for project running status change was merged with all other changes in 0.10.0

Could you please re-test this at your side on latest/git version?

[sammachin]

@Steve-Mcl I'm still seeing this on staging when creating a new project, If you're testing with localfs it may be hard to reproduce as the project starts much quicker than a k8s install

[Steve-Mcl]

Thanks for that @sammachin - definitely something to look at

[Steve-Mcl]

@hardillb I've noticed when running localfs the update comes through relatively quickly however on cloud there is no update at all (have to browse away then come back).
I suppose I would start looking at the differences between localfs and k8s?

[hardillb]

yep, and given the install demo this moring I think the delay going from starting to runnning is in a similar spot.

[Steve-Mcl]

associated PRs...

• Improve project status & detail reporting to frontend #58
• Npm install starting #75

[hardillb]

I'm going to say this is done, staging is behaving