404 Error When Triggering KA JS Miner Pipeline on Main Branch of Edge Node API #30
Description
Description
When attempting to trigger the KA JS Miner pipeline on the main branch of the Edge Node API, the request results in a 404 Not Found error. This suggests that the endpoint responsible for handling the KA JS Miner process is either missing, incorrect, or not properly registered in the main branch.
Steps to Reproduce
1. Run the Edge Node API on the main branch.
2. Attempt to trigger the KA JS Miner pipeline using the the node dataset/import endpoint.
3. Observe that the response returns a 404 Not Found error.
Expected Behavior
The KA JS Miner pipeline should be successfully triggered, and the expected response should be returned.
Actual Behavior
The request results in a 404 error, indicating that the endpoint is not found.
Possible Causes
• The KA JS Miner route might not be included or registered in the main branch.
• There may have been a recent refactor or change that affected the availability of this endpoint.
• The route definition or API path might differ from what the request expects.
Suggested Fixes
• Verify whether the KA JS Miner endpoint is defined in the main branch.
• If missing, ensure the feature is correctly merged.
• Check the API routes and confirm the correct path.
• Ensure the request aligns with the defined route.
• Compare with the feature/ka-mining-js branch to see if the necessary logic exists there but is absent from main.
I was not able to spend much more time hunting the issue. I just know it exists.