Request Scan Granularity and Risk

Ignition
1

Hello,

We have a 8.3.8 gateway with ~10 production critical (manufacturing) projects, each project has its own tag changes and gateway scripts.

We migrate code to this production server via git and use system.project.requestScan from the gateway UI, eventually from a hook to call it from the api.

For simplicity sake, lets say today I need to change the color of a button in one of the projects - does that mean I have to shut down the entire factory while request scan is running to prevent missed gateway messages?

What we had happen today was we did a very small update to one project (scripts and ui, not messages) and request scan triggered "Restarting Gateway Scripts" on every project (plus a billion client session errors?). The top line in the screen shot shows that caused us to miss a gateway message, ultimately resulting in equipment downtime.

Looking for some advice - am I misunderstanding or doing something wrong? Its a tough ask (impossible) for me to tell the plant to shut down every time we update these apps.

image
image3407×2523 1 MB

Thanks,

Jake

2

This is a surprise. I would have expected only the changed projects to restart. Unless, you had resource.json timestamps/hashcodes changed in the git repo. After you did the project scan, did git show any new changes scattered across the projects?

(Presuming you aren't using .gitignore to omit resource.json.)

3

The changed project got two new commits spanning 2 views (resource.json, thumbnail.png, view.json) and 2 scripts (code.py, resource.json). The other projects wouldn't have had any files changed, although its not impossible something touched their timestamps?

4

Git should tell you (via git status) about uncommitted changes in the gateway. Note that if a resource had to be re-hashed, and the project was inheritable, any child projects of it would also restart.

5

No one develops using the designer on this gateway so the working directories are always clean.The other projects all got a new commit ~12 days ago for the necessary conversion from binary to .json messages after the 8.3 upgrade, but aside from that they are very static. We scanned after doing that, and have scanned almost every day since then (maintaining this one project) and always, it shows every project getting restarted.

This project in particular inherits "global" but global remains static aside from the aforementioned 8.3 commit.

image
image1723×1843 482 KB

6

Sequence to verify:

  1. gateway does git pull or git checkout to grab changes to one project.

  2. Use git show to look at the diff to ensure only the expected files are included.

  3. Run project rescan.

  4. Use git status to see if rescan caused any other files to change (signatures or timestamps) and be in an uncommitted state.

7

I wonder if this has something to do with that dang last modification entry we still haven't gotten rid of...