Skip to content

Unknown Error in Command Runs

A message similar to the following appears in the command line to alert you:

c:\Users\your_home\Kitchens\your_context\your_kitchen\your_recipe>dk recipe-status
Current context is: your_context
2020-12-02 13:58:21 - Getting the status of Recipe 'your_recipe' in Kitchen 'your_kitchen'
        versus directory 'c:\Users\your_home\Kitchens\your_context\your_kitchen\your_recipe'
Error: not enough values to unpack (expected 2, got 1)

c:\Users\your_home\Kitchens\your_context\your_kitchen\your_recipe>

Details

There are hidden system files for each context, local kitchen copy, and local recipe copy. These files contain metadata that DKCloudCommand relies on to function properly.

Potential causes

If some of the metadata files are deleted or become corrupted, the CLI may produce atypical errors.

Note

While merge and diff files can be deleted and replaced at the next run of either operation, other files can create problems if missing or corrupt.

Files with the following information can cause this type of atypical error:

  • Configurations and connection information.
  • Credentials (token) for user login.
  • Metadata stored from merge and diff operations.
  • Metadata that tracks the current state of recipe files.

Solution

Begin at the recipe level of your working directories. Perform these steps to refresh your local versions.

Step 1: Recipe level

  1. In a file manager application, locate the recipe folder of the recipe you were working on when the error occurred.
  2. Move the recipe folder to a temporary location outside of your working path (i.e. outside kitchen and context directories).
  3. In the CLI, run the recipe-get command to pull a fresh copy of the recipe from remote.
  4. Use a comparison tool to compare the new recipe folder contents with the original folder.
  5. Take note of any differences.
  6. Recreate your local changes in the recipe copy that you pulled from remote.
  7. Run the recipe-update command to update your local changes.
  8. Attempt the action where you performing when you received the error message.

Step 2: Kitchen level

If the problem has not been resolved by making changes at the recipe level, repeat the procedure at the kitchen level.

  1. Locate the relevant kitchen folder and move it to a temporary location.
  2. In the CLI, run the kitchen-get command to pull a fresh copy of the kitchen.
  3. Run the recipe-get command as many times as needed to pull down recipes you need.
  4. Repeat Step 1 (4) to (8) above for each recipe.

DKCloudCommand

Note

Still not working? Contact DataKitchen Support. We can work through this together.