Bug or misuse? "JavaScript Inline Code" component throws 500 internal server error. Because of "node analysis worker" #1197
Unanswered
loelindstrom
asked this question in
Help Needed
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
What I'm doing
It seems like overnight, "Javascript Inline Code" components stopped working for me when I try to develop Logic App workflows locally in VS Code.
I've created a very simple workflow to demonstrate:
Click to see
workflow.json
What's happening
With this I get the stack trace seen below in the log excerpt.
But if I remove the "Javascript Inline Code" component the Logic App starts up and runs fine locally.
Click to see stack trace/log excerpt
These two seem like interesting log entries:
[2024-10-10T09:15:43.571Z] Workflow Info: operationName='NodeProcessHandler.StartNodeProcessIfNotStarted', message='Using node analysis worker on port '61614'. Startup time was '409' milliseconds.', exception='', extensionVersion='1.91.14.0', siteName='UNDEFINED_SITE_NAME', slotName='', activityId='53c799ce-7607-43c3-bb99-df7b2c54a4b8'.
[2024-10-10T09:15:47.671Z] Outgoing HTTP request ends with server failure: correlationId='53c799ce-7607-43c3-bb99-df7b2c54a4b8', operationName='POST/', httpMethod='POST', hostName='localhost', targetUri='http://localhost:61614', clientRequestId='30d70a06b2df4ba695a7d978f4ecd1d5', clientSessionId='', clientApplicationId='', apiVersion='', contentLength='-1', serviceRequestId='', durationInMilliseconds='4087', httpStatusCode='0', exceptionMessage='System.Net.Sockets.SocketException (10061): No connection could be made because the target machine actively refused it.
Please help!
Anyone got an idea what's going on?
From the logs it seems like some Node process ("node analysis worker") is starting locally and is not working as expected. Is it some configuration I am missing? Is it calling out to some Azure stuff and it's a firewall thing? The error message is not clear to me.
Perhaps someone has an idea on how I could investigate it even further?
It's also weird that it just appeared from one day to another..
It seems like the same problem as this, but their solutions are workarounds, suggesting it's a bug:
Specs
IDE: VS Code 1.94.0
Logic App edition: Standard (using latest VS Code extension)
OS: Windows 10
Core Tools Version: 4.0.5455 Commit hash: N/A (64-bit)
Function Runtime Version: 4.27.5.21554
Beta Was this translation helpful? Give feedback.
All reactions