Patch Note 2022-08-03

Oh boy, have we got a doozy for you! While most of the Valohai crew was enjoying a well-earned Finnish summer over July, a couple of us held down the fort and cranked out a bunch of features and bugfixes for all y'all.

New features

• You can now view the queue and scaling status for your execution's or task's environment in a nifty pop-over card.
• Let us know if there are more details that you'd like to see in the card and we'll look into it!
• Spot/pre-emptible executions can now be automatically restarted if they get pre-empted.
• A future iteration will also automagically carry over any output state from the pre-empted execution, but for now you'll have to start from scratch.
• You'll now get a notification when you're added to a team or to collaborate on a project.

Task UI improvements

• The Task detail table got a face lift. It's now more concise and readable.
• You can now see the price estimate for an entire task in the Task detail table. There's naturally also an API endpoint for that.
• Tasks can now be tagged.

Other UI improvements

• We yeeted the secondary "project navigation bar" out and tucked its content into the top navigation bar. UX SCIENCE!!!
• Nearly all disabled UI elements now have a nifty tooltip telling you why they're disabled.
• You can now create deployment nodes in the create pipeline view (if that feature is enabled for your account, anyway).
• You can now save local drafts of pipelines in the create pipeline view, if you're lucky enough to be allowed to do so.
• You can now view the API call for creating a deployment version. Automation!
• The "Create Project" Ownership dropdown is now a lot clearer. Optgroups are a thing!
• Links in the execution event log are now clickable. Wow!

API enhancements

• You can now filter executions by their creation time range.
• You can now set the status_detail field of a running execution via the API.
• In the near future, we'll also surface this to the execution itself, so it's one valohai-utils call away!

Performance improvements

• The datum browser got a bit faster.
• When changing filters or sorting in various tables, we now sneakily cancel any outstanding requests to the server. Less requests = less lag, or that's the theory anyway.
• The execution property keys endpoint learned a thing or two about caching.
• Retrieving metadata for multiple executions at once is now much faster.
• Purging an execution's outputs is now somewhat faster. Would that cloud storage providers had an API for all-or-nothing deletion of multiple files...

Bugfixes

• The Usage view got some love:
• Date filtering was fixed. Turns out end dates aren't the same thing as start dates.
• Aggregations were occasionally mishandled. We replaced the "mis" with "correct", so now they're correcthandled, which isn't a word, but it's a good thing.
• Relative time popovers now show the date too, not just the time. Although, of course we all know that executions run in the witching hour tend to have the best accuracy metrics.
• The datum browser no longer loads data twice to start with. That was silly to do, wasn't it?
• Copying tasks or executions with inputs that referred to datums could occasionally break the UI. This should no longer happen.
• The quite defunct forms in the Browsable API were obliterated.
• Legacy execution realtime stats are now properly formatted. No more 300,000 CPUs for you, sorry!
• Deployments will no longer crash and burn due to environment variables that Kubernetes just can't deal with.
• Scaling status is no longer shown for environments that can't scale.
• Non-billed environments are no longer considered for execution credit check.