Unexplained errors, explained!
When writing any sort of software, it's inevitable to run into errors that Googling, scrolling through myriad Stack Overflow answers, and random fixes ultimately cannot resolve. Here at BaseTen, we’ve made an effort to rid you of some of that misery by adding more descriptive error messages to worklet and node outputs.
Here are a few of the errors we’ve made more clear:
New requirements still being applied to your python environment: If you’re trying to use new requirements right away, you’ll see a message letting you know they’re still being applied.
(ModuleNotFoundError): No module named 'cv2'; this might be due to the new requirements that are still being applied.
Timing out in a worklet or node: When you run a worklet or node with some code that times out because it runs for longer than 5 minutes, you’ll see a message encouraging you to optimize your code or run it as a background task.
(ReadTimeout): The node timed out. Nodes must be executed in 300s or less; you can make this error go away by optimizing your code, or running it as a background task.
Server errors: When you run a worklet or node with some code that causes a server error, you’ll see a message letting you know that you should try again or contact us.
(HTTPError): An error has occurred. Please try running your code again. If the error persists, reach out to BaseTen for more information.
Here’s to hoping you never run into unexplained errors in Baseten 🤞 But if you do, we’re here to help. Happy coding!
