-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enabling profiling via env variable in Serverless Framework not working #64
Comments
Potential duplicate of #45 --it's the same error. Is this just on Node 10, or with Node 8 as well? |
@mrickard Not seeing this error in the issue referenced? May be related, @austinhuminski reports this error is being seen in |
|
@kolanos True--that issue's a silent error, while I was seeing local invocations logging an error to stdout. Part of the problem there appears to be that the import of util from -core is undefined. In jest tests of -profile, util is imported correctly, but on inclusion in a project, -profile isn't able to import the separately-included -core. This can happen when there's a circular dependency, and while this isn't circular, as far as I can tell, the problem does seem to be the import. Locally, it seems that the profile import of core does not throw this error if the function is using iopipe-js 1.15, but I've seen the error under 1.14. |
Tried this without the serverless-iopipe-layers plugin and got the same error. Used the @iopipe/iopipe method on both Node 10 and Node 8 with the same results. |
@austinhuminski Interesting--I'm building a couple layers functions and I'll test them against non-layer as well. |
@kolanos Unfortunately no! I did check that, but the error's still being thrown to the console. It's related to dependencies, I think, so I'm trying to configure a circular dependency check in ESLint. |
When settings
IOPIPE_ENABLE_PROFILER: true
in serverless.yml file profiling is not getting enabled and I get an error in my CW logs with debug onNode10
serverless-iopipe-layers: 0.3.3
arn:aws:lambda:us-east-1:146318645305:layer:IOpipeNodeJS10:1
The text was updated successfully, but these errors were encountered: