Actions not showing on local env

Help me!
21

I think since the changes you made kinda broke your project, the forestadmin-schema was wrong and so your cache was updated with no smart actions (since it couldn’t process the schema).
Then when you rolled back, FA updated your cache and thought the added smart actions where new, so by default it disabled their visibility.

22

Thanks for the insight at least I could fix it on my own if it ever happens again.

Cheers

1 Like
23

Hey @anon94532230 ,

I’m still getting these on my last version when I run the server locally:

-    "engine_version": "14.14.0",
-    "framework": "express",
-    "framework_version": "~4.17.1",
+    "engine_version": "12.16.1",
+    "framework": "other",
+    "framework_version": null,

Any idea where that comes from? I’m scared it breaks my local env again.

Everything is fine on production.

24

Hi @mathieuh

I’m still getting these

You mean smart action that disappear and/or break your smart action UI ?
If that’s the case, could you tell me if:
1 - You are using nodemon ?
2 - If your server crashed and reload when this happened ?

If not, could you precise the behavior you are experiencing ?

25

Hi @jeffladiray,

No I’m just talking about the changes in the schema.json when I run the server. The changes that @anon94532230 noticed look wrong.

I’m using nodemon, when running npm start it does only this:

     "liana": "forest-express-sequelize",
     "liana_version": "6.3.13",
     "engine": "nodejs",
-    "engine_version": "14.14.0",
+    "engine_version": "12.16.1",
     "framework": "express",
     "framework_version": "~4.17.1",
     "orm_version": "5.21.7"

I shouldn’t use nodemon then?
Any idea why it decreases the engine_version?

Cheers,

26

No, no that’s perfectly fine to use nodemon, I guess I mixed your response with another potential issue here.

This engine version correspond to the version of nodejs you are using, so my guess would be that you updated your nodejs environment and .forestadmin_schema.json is updated to reflect this change.

The other changes seems weird to me though. I’ll try on my end to update my env to node14 to check if this is what’s leads you to this behavior.

27

Ok, I didn’t upgrade to node14 so I don’t know how it got there…
The v12.16.1 is the right one.

So nodemon@1.14.11 makes these weird changes while I’m on node 12.16.1.
I’ll play with versions to see if it fix this.

28

On my end, upgrading to node 14.14.0 seems to trigger the same issue as yours. This might need further investigation on our end, so I’ll open a ticket for this purpose.

In the meantime, I would suggest to check with node --version to make sure your are still using 12.16.1 and that these changes does not appear anymore.

Let me know if that helps.

1 Like
29

Ok, actually one of the devs switch to the 14 and I didn’t notice.

Yes I’m on the 12.16.1. But even with the 12.16.1 using nodemon I get:

-    "engine_version": "14.14.0",
-    "framework": "express",
-    "framework_version": "~4.17.1",
+    "engine_version": "12.16.1",
+    "framework": "other",
+    "framework_version": null,

With npm start:

-    "engine_version": "14.14.0",
+    "engine_version": "12.16.1",
     "framework": "express",
     "framework_version": "~4.17.1",

Could you link me the ticket so I know when it is fixed?

30

No problem, here it is. The ticket is related to the fact that all informations should be correct, even on nodejs 14.

But in order to fully fix this issue (Whatever the nodejs version you are using), all your development environment should be running the same nodejs version (This would avoid conflicts on this file, but would also diminish risks of having inconsistent behavior between all you environments)