17 May 2021 Release Notes¶

Version 1.1.216. Note that version 1.1.215 was deployed to DataKitchen testing environments only.

Feature Highlights¶

Merge Editor Offers More Space for Review¶

Users who review code conflicts in very long files during a kitchen merge asked for ways to reduce the scrolling required and for better visibility of lines of code. This release introduces functions in the Merge Editor that hide the left-hand file list and toggle the view from 3 panes to 2 panes. See Merge Kitchens for more information. [DEV-7424]

The new Hide File List button collapses the left pane, allowing the file diff panes to expand in width. The existing :material-: filter button was moved to accommodate the new function.

The new 2-pane and 3-pane buttons change the file diff panes as follows. Importantly, note how the order of the panes change.

The 3-pane view is the default, showing source kitchen > merge preview > target kitchen as usual.
The 2-pane view shows the target kitchen > source kitchen when there are no merge conflicts.
The 2-pane view shows the merge preview > source kitchen when there are code conflicts.

Page Previews

The Kitchen Merge pages have new functions to aid in code review.

The 2-pane view and hidden file list enable easier code reviews.

Graph Processing Defaults to Fast-Throughput Method¶

This release turns on fast-throughput graph execution as the default processing method for all customers.

While the DataKitchen platform traditionally processed graphs by executing one node level at a time, the platform introduced an optional, faster method last year. With fast-throughput execution, the platform can process a node as soon as its predecessor completes. Any one "path" of a graph does not have to wait until another path catches up before it can complete its execution.

Now, this more efficient method is the default for all graphs. See Processing Graphs and, specifically, the Order of Execution section for more information. [DEV-8262]

A node begins processing when the previous node in the same path completes.

With the sequential method, node_e and node_g can be processed while node_d is still in progress.

Note

Planned Switch for Existing Accounts: To prevent recipe failures resulting from a wholesale change in how DK processes graphs, existing customer accounts will be switched over to the new default method only after their recipes have been thoroughly reviewed.

New README File and Display Offer Increased Collaboration¶

DataKitchen has revamped the conventional readme.txt to provide a way for teams to communicate details about their recipes and instructions for their teammates!

A new Wiki tab on the Recipes page will display any README.md file that users place in the root of a recipe's file structure. The file can be added and edited via the File Editor using GitHub Flavored Markdown syntax. See Use the Recipe README for more information.

In future releases, the platform will add a README.md file containing templated content when any new recipe is created. Also coming soon, the existing readme.txt file automatically created in the resources folder will be deprecated for all new recipes. [DEV-5644]

The README.md displays in the new Wiki tab on the Recipes page.

CLI Supports Run Once Orders¶

While the webapp has offered users the ability to select Run Once as a schedule option when running a variation, the Automation command line interface (CLI) has supported this option only via a predefined variable override. This enhancement adds a --now parameter to the existing order-run command for an easy way to submit an order for an immediate, on-demand run. See order-run for more information. [DEV-4829]

Example command and output

~Kitchens/Dev_Sprint/Recipe1 $ dk order-run -y --now Variation1

Current context is: default
YYYY-MM-DD HH:MM:SS - Create an Order:
        Kitchen: Dev_Sprint
        Recipe: Recipe1
        Variation: Variation1

CREATE ORDER
Order ID is: c9dc1bd2-4ef6-11e8-a762-080027aceabc
The following variables will be overridden:
schedule: now

Other Fixes & Enhancements¶

Limit Removed from MySQL Field: The Hostname field for configuring MySQL data source and data sink connections was limiting entries to 80 characters in the Node Editor. Because database hostnames are routinely longer than that limit, users were working around the problem by using kitchen override variables. This issue has been resolved, and the character limit on the field has been removed completely. [DEV-8018]

Schedule Shows Correct Next Run: The Schedule tab on the Variation page and the Add/Edit Schedule dialog on the Recipes page were displaying the date and time incorrectly for daylight saving time (DST) in the Next Run field. The First Run field in the Run Variation dialog was similarly affected. The cron expression showed the proper setting, but the next or first run time was one hour off. This issue has been resolved, and the run times display correctly. DEV-8025]

Response Improved on Order Run Failure: Users found that when an order run failed before starting to process its graph, the platform displayed a generic error and prevented access to the Order Run Details page. This problem occurred most often with out-of-memory scenarios where the system could not even create an order run. This release updates the platform so that users can access the page and receive a more detailed error message in this situation. [DEV-8081, DEV-8082]

The platform generates a new error when order runs fail before processing.

No Logs Message Hidden on Load: The Order Run Logs dialog was displaying a "No logs found" message when reloading log entries after users quickly selected different Log Levels filters. This issue has been resolved, and the dialog displays only the loading bar. [DEV-8016]

Filters Updated to Save Settings: The filters in the Order Run Logs dialog and on the Variation Metrics page have been updated to behave like all other platform pages—to save users' filter selections in their local browser storage. This means that if a user changes the log levels displayed or toggles the RAM and Disk data in the logs, those filters will persist for that user, across the current kitchen, when using the same browser and without clearing the cache. Similarly, the node, status, and sort order filters persist on the Variation Metrics page but solely for the single variation context. If a user accesses a platform page using a pre-filtered link, however, the settings stored in that link take precedence. [DEV-8106]

Graphs Do Not Duplicate Test Results: Under specific circumstances for pass/fail tests, the graphs on the Variation Metrics page were plotting duplicate values on the Y axis. This issue has been resolved, and the graphs plot two values for pass/fail test results as expected. [DEV-8160]

Ingredient Variables Process Correctly: The platform was processing outflowing, dictionary-type variables from an ingredient incorrectly. This problem resulted a difference in the actual value of the variable and the value that was read by any node or test consuming it. This issue has been resolved, and outflowing variables from an ingredient now process properly and consistently. [DEV-8155]

Resume Function Shows Compile Errors: The resume order run feature was not reporting compilation errors, as are displayed in error messages in the Run Variation dialog. This issue has been resolved, and the Resume Order Run dialog now shows compilation error messages as well. [DEV-8143]

Custom Icons Upload Properly: A user reported receiving an error while uploading a custom icon for a new container node. The icon upload worked correctly, however, from the Node Details sidebar after the node was created. This issue has been resolved, and the icon function in the Add Node sidebar accepts uploads without error. [DEV-8097]