This topic was automatically generated from Slack. You can find the original thread here.
How are folks debugging code (node.js) that just hangs? When I cancel, no errors are logged, even though I have error handling included. Is there something I am missing?
— I noticed this suggestion in another thread with a similar issue. Is there something like this for node.js?
Hard to debug when the process just hangs and no errors are logged when a test is cancelled.
Just found the CLI tool and the docs surrounding it. Working to implement them now.
— In the context of Pipedream CLI, what is a component?
In the context of Pipedream CLI, a component is a Node.js module that runs on Pipedream’s serverless infrastructure. Components can be used as building blocks for Pipedream workflows or as typical serverless functions. They can be triggered by HTTP requests, timers, cron schedules, or manually, and can use Pipedream managed auth for various apps and most npm packages without the need for npm install or package.json. You can find more information about components in the Pipedream documentation.
— What does the following error in CLI mean?
Non-200 status from …
The “Non-200 status” error in the CLI means that the HTTP request made within your code received a response with a status code other than 200. A 200 status code indicates a successful HTTP request. When you encounter this error, it’s important to check the API documentation or the specific endpoint you’re calling to understand the possible error codes and their meanings. You may also want to add error handling in your code to handle non-200 status codes and log the response for easier debugging.
Hi , one tip from me is that you can copy the code on Pipedream code step action to your local machine and develop on your local machine. You can mock the handler function params.
I really think that you need a sufficient coding knowledge to implement. If you’re still unsure that you can implement your usecase, you can: