The Assette VS Code Extension provides interactive development and content management capabilities for Assette blocks. As part of its robust feature set, the extension logs messages to guide users through authentication, file operations, upload/download processes, and workspace interactions. This article outlines the error and status messages users may encounter, categorized by function and context, to help diagnose issues and improve the user experience.
All users should familiarize themselves with these messages before using the extension to streamline debugging and support communication.
Authentication Messages #
These errors appear when signing in to the extension or validating client credentials.
- “The client code you entered is invalid.”
Triggered when the provided client code is not recognized. - “The username or password you entered is incorrect.”
Occurs when sign-in fails due to incorrect credentials. - “User Client ID is not defined.”
Sign-in attempt made without a client ID being configured. - “Policy data is not defined for the given client ID.”
The client ID provided does not map to a valid policy configuration. - “No API key entered.”
The API key required for communication is missing in configuration.
Workspace Related Messages #
These messages relate to the user’s file environment and VS Code workspace configuration.
- “No workspace folder is open.”
The extension requires an open folder to function. This appears if VS Code has no active workspace selected.
File Download Operation Messages #
These are shown when downloading blocks or collections of content from Assette.
Common to All Download Functions #
- “Error writing file: [err]”
Indicates a problem writing files to the local filesystem. - “Error occurred while deleting ZIP file: [unlinkErr]”
Local ZIP cleanup failed after download extraction. - “Error extracting files: [extractErr]”
Extraction of the downloaded archive failed. - “File(s) download failed. Information: [message]”
The download did not complete successfully; message contains additional context. - “Warning: [errorMessage] – Retrying ([retryCount]/[maxRetries])…”
Retry logic is engaged after transient errors. - “Error: [errorMessage]”
Final error after retry attempts have been exhausted.
Specific Download Functions #
downloadBlock,downloadAllTypesBlock,downloadAll, anddownloadBlockByNameeach use the same error handling pattern as listed above.
File Upload Operation Messages #
Errors encountered during upload operations, including bulk and single file upload scenarios.
General Upload Errors #
- “File name label is missing.”
Required label for the block is not defined in the file’s metadata. - “File path is missing in selected folder.”
A referenced file or folder cannot be found on disk. - “Could not determine the root folder.”
The folder structure is not compatible with expected upload format. - “Metadata file not found: [metadataFilePath]”
Metadata file required for upload context is missing. - “No files found in this group with satisfied data. Skipping upload for this group.”
The extension attempted to process a group, but no valid files were found. - “Error uploading file: [error]”
Upload failure due to connection or server-side issues.
Specific Functions #
uploadPythonBlock, uploadBlocksByFolder, uploadBlocks, uploadSingleFile, uploadTemplateFileData #
- Also include:
- “Avoid uploading [folder] folder.”
- “You are going to upload all blocks in [folderName] folder.”
- “Template upload failed: [data.message]”
Block Operation Messages #
Messages tied to specific block processing routines.
- “Failed to fetch block data after multiple attempts.”
Shown duringfetchBlocksDataByTypeFromApi. - “Upload completed for Block: [blockName] Issued block Id: [blockId]”
Confirmation that a block was successfully uploaded. - “Failed Block: [blockName] Error: [message]”
Block upload failed with a provided message. - “[summaryMessage]”
Summary error status from bulk upload.
Retry Logic Messages #
These messages indicate automatic retry attempts for transient errors across download and upload tasks.
- “[errorMessage] – Retrying ([retryCount]/[maxRetries])…”
Shows retry count and total allowed attempts. - “[errorMessage]”
Final message after all retry attempts have failed.
File System Operation Messages #
Relates to file reading and folder scanning issues.
- “Error reading [root_folder] folder: [error]”
Directory read failed due to permission or disk error. - “Error reading folder: [error]”
Generalized version of the above for any folder.
Log and Status Messages #
These messages are typically written to logs and status displays to track upload workflows.
- “Could not get modified date for file: [file.name]”
- “File [file.name] marked as modified…”
- “Found [N] modified files” / “No modified files found”
- “Error processing folder [folder.name]: [error]”
- “Error in filterModifiedBlocks: [error]”
- “Start Processing Group: [GroupCount]”
- “Uploading group [X] out of [Y]”
- “End Group: [GroupCount]”
- “Root folder not found” / “Folder label is undefined”
Additional Guidance #
If you’re encountering an error not listed here, or repeated issues even after retries, check the following:
- Ensure your extension configuration matches your environment (development, production).
- Confirm your workspace is properly structured with all required metadata files.
- Use the latest version of the extension to benefit from updated validations and improved error reporting.