Changelog

You can now see your BaseTen-provided Postgres tables and external connections in one place. Click into the Data overview page to manage all your tables and connections.

Coming very soon, you'll also be able to manage all your queries from the Data page.

‍

The Applications and Models overview pages are now table-based instead of card-based. With these tables, we’ve streamlined the information on each page and removed the reliance on icons to designate metadata. The tables are also better suited for larger numbers of models and applications and set us up to support filtering and sorting in the future.

✕

Tables replace cards screenshot

We've released the first of many small navigation changes, all intended to make it easier for you to get around the product and differentiate between exploration mode (when you need to understand how all your models, apps, and data relate to each other) and focus mode (when you’re actively building in BaseTen).

Your main navigation now includes words, because the icons in the old icon-only navigation didn’t speak for themselves. The main navigation also minimizes when you’re editing worklets and views now, to give you more space to build.

We're always trying to make it easier for you to work on BaseTen, both on your own and with others. Here’s a little improvement that should help your editing experience when you have multiple windows of BaseTen open or are collaborating on BaseTen with someone else.

If you accidentally end up editing a worklet, view, or query in multiple windows, we kindly prevent you from saving changes that’ll overwrite your work. We do the same thing when you and a colleague are collaborating on an application together, so no more accidentally editing over each other's work.

‍

ML tasks can be fairly time-consuming. Processing audio, video, and images can take minutes, sometimes even hours. While BaseTen already supported processing of up to 5 minutes per python node invocation, even that can be limiting.

We're happy to announce that long-running tasks are now a first-class citizen in BaseTen. Each python node invocation can take up to 4 hours, as long as you invoke the worklet in async mode.

✕

Worklet run as background task

If your worklet has long-running tasks, i.e. tasks that take more than a few minutes, we highly recommend marking the worklet for background execution. Then, the worklet will always execute in async mode.

Alternatively, you can pass the async flag in the API request to execute any worklet in async mode:

curl -X POST https://app.baseten.co/applications/{YOUR_APP_ID}/worklets/{YOUR_WORKLET_ID}/invoke -H 'Authorization: Api-Key YOUR_API_KEY' -d '{ "worklet_input": WORKLET_INPUT , "async": true}'

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!

‍

The new select component replaces our old dropdown component, with improved functionality. Use this new select component to allow operators to select from a list of options in your app, for example, when labeling data.

Add all your options at once

In the old dropdown component, you had to configure your options one-by-one as individual input fields. With the new Select component, you can add all your options through a single display function.

Add dynamic options

You can display dynamic options in the select component. For example, the option the operator chooses in one select component could determine the options available to them in a second select component.

Search for options in the UI

When using your app, operators can type to search and more quickly find the option they’re looking for.

Create new options from the UI

If an operator searches for something and doesn’t find it in the list of existing options, you can give them the ability to easily create a new option from the UI. You can choose whether to enable or disable this functionality in the select component.

Dynamically disable the Select component

You can dynamically disable the select component. For example, you can require operators to submit text through a text input component before being able to select an option in the select component.

We’d love to see what you build with this new component.

When building our own application views, a few of us at BaseTen got frustrated when we couldn’t use the delete key to quickly remove components.

✕

You can now remove components by hitting the delete key

Mike to the rescue. You (and we!) can now remove components by hitting the delete key. Happy view building!

‍

You can now search model logs using regular expressions, logging level, and time span.

‍

If you’ve been eagerly waiting to be able to give coworkers, friends, family, pets (anyone with an email address!) access to collaborate on your amazing BaseTen creations, look no further than this new addition to Baseten! As an Owner or Admin in your BaseTen organization, you can now invite others to see and edit your applications, models, and data sources. Better yet, if you need to restrict editing permissions, the access is role-based. You can choose between: Admin, Creator, and Operator roles. Head over to the “Manage access” popup in your settings tab to start inviting members!

‍