You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The worker environment isn't running with NODE_ENV set to production.
This isn't neccessarily a problem, but it does mean that Lightning is printing deprecation notices on the old common.http helpers. It shouldn't really be doing that - the deprecation notice is designed only to come out in the CLI because the message is targeted at adaptor writers. Job writers can't do anything about it.
Probably the main worker server is running in prod mode, but the nested child process worker environment isn't inheriting it.
Maybe its even the sandbox - the sandbox, very deliberately, doesn't inherit the parent env. But maybe we should pipe NODE_ENV through.
The text was updated successfully, but these errors were encountered:
The worker environment isn't running with NODE_ENV set to production.
This isn't neccessarily a problem, but it does mean that Lightning is printing deprecation notices on the old common.http helpers. It shouldn't really be doing that - the deprecation notice is designed only to come out in the CLI because the message is targeted at adaptor writers. Job writers can't do anything about it.
Probably the main worker server is running in prod mode, but the nested child process worker environment isn't inheriting it.
Maybe its even the sandbox - the sandbox, very deliberately, doesn't inherit the parent env. But maybe we should pipe NODE_ENV through.
The text was updated successfully, but these errors were encountered: