Improve docs on passing args to node process
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 25/100
- Issue type
- Documentation
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- node.js, typescript
- Domain
- documentation
Research direction
Start with the func start argument behavior and the local.settings.json NODE_OPTIONS example described in the issue. Clarify how Node.js profiling arguments are passed, where the resulting .log file is written, and whether the documentation should explain the NODE_OPTIONS restriction; done means the documented workflow works or its limitation is explicit.
Written by the indexing model from the issue text.
Description
func start with -- "--prof" seems to do nothing. I, at least, can't find the resulting *.log file anywhere on my system.
Adding --prof to NODE_OPTIONS in local.settings.json results in an error message.
Relevant output snippet:
Azure Functions Core Tools
Core Tools Version: 4.0.4865 Commit hash: N/A (64-bit)
Function Runtime Version: 4.12.2.19454
[2022-12-01T13:39:27.380Z] Language Worker Process exited. Pid=14562.
[2022-12-01T13:39:27.380Z] node exited with code 9 (0x9). .
[2022-12-01T13:39:27.390Z] node: --prof is not allowed in NODE_OPTIONS
Easy profiling of Node.js apps (https://nodejs.org/en/docs/guides/simple-profiling/) seems impossible, unless I'm missing something.
Please allow us to profile Node.js apps run with func start.
- Dominant language
- TypeScript
- Stars
- 110
- Forks
- 52
- Avg merge
- 7h 33m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from Azure/azure-functions-nodejs-worker
-
Handle valid prerelease Node.js versions without failing worker initializationPossibly taken @TsuyoshiUshio claimed this 52 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
-
area:nodejs-functions dependencies engineering tests
Difficulty 5/5 Over a week Newbie friendliness 35/100
-
Specialization race: double startApp() with stale require cache leaves worker on default v3 model with all functions unloadablePossibly taken @swapnil-nagar claimed this 58 days ago. Open
Difficulty 5/5 Over a week Newbie friendliness 30/100
Azure/azure-functions-nodejs-worker#838 · 1 comment ·
-
c-ares DNS misconfiguration on Windows Consumption causes mongodb+srv:// and dns.resolve*() failuresOpen
Difficulty 4/5 3-5 days Newbie friendliness 64/100
Azure/azure-functions-nodejs-worker#830 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
All issues in Azure/azure-functions-nodejs-worker
Similar issues
-
Unsampled pageload span is profiled when profileLifecycle is 'trace' (browser UI profiling)Possibly taken @Jxxunnn claimed this today. OpenBrowser Waiting for: Product Owner
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
getsentry/sentry-javascript#25497 · 1 comment ·
Maintainers usually reply within 1 day
-
e2e-failure ready-to-code
Difficulty 2/5 1-3 hours Newbie friendliness 77/100
redhat-developer/rhdh-plugin-export-overlays#4438 · 1 comment ·
Maintainers usually reply within 1 day
-
resource: destroying a resource calls AbortController.abort() without a reason, creating an AbortError with a stack trace each timePossibly taken A pull request linked to this issue is open or already merged. Openarea: core
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
angular/angular#71422 · 1 comment ·
Maintainers usually reply within 1 day
-
bug status: needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
facebook/docusaurus#12739 · 1 comment ·
Maintainers usually reply within 1 day
-
factory-active task-identify-harness-labels-done task-identify-issue-type-done
Difficulty 1/5 1-3 hours Newbie friendliness 68/100
Maintainers usually reply within 1 day