Skip to main content

Online Development Related

After deleting a cloud function on the cloud development platform, it still exists in the online editor​

  • Cause Analysis

    In the cloud development platform, cloud functions are deployment services, while the online editor is used to store the code of cloud functions. These two are independent of each other; deleting a cloud function deployment does not automatically delete the corresponding code.

    For example, we write a service's code locally and deploy it to the online environment. When the service is no longer needed, we can take it offline, meaning delete the deployment. However, the local service code will still be retained and will not automatically disappear due to the deletion of the online service.

    The online editor in the cloud development platform is essentially a remote version of a local editor. It simply means writing code in a different location, and its code storage mechanism follows the same principle as the local writing and deployment model.

  • Solution

    If you no longer need a certain cloud function's code, simply delete it directly in the online editor.

After deleting and recreating a cloud function with the same name on the cloud development platform, the online editor still displays the previous version​

  • Cause Analysis

    This is related to the online editor's automatic download strategy. When a cloud function with the same name already exists in the workspace, the online editor automatically skips the download process to prevent code overwriting, and prompts the user to manually download updates.

  • Solution

    Synchronize the cloud function code via manual download.

    For specific steps, refer to the download section in the Cloud Function Online Development manual.

Download Failure When Entering Online Development After Creating Function-based Cloud Run​

  • Cause Analysis

    Function-based Cloud Run is based on Cloud Run. In the absence of deployment history, online development cannot download the corresponding code package, thus the following prompt will appear.

  • Solution

    Please wait patiently for the cloud function deployment to complete before entering online development to perform operations.

Where is the functional operations menu for Online Development?​

Please refer to Cloud Function Online Development

pnpm Error When Installing Dependencies​

  • Cause Analysis

    The pnpm version declared in the project's package.json does not match the pnpm version installed in the current environment.

  • Solution

    Open the terminal and execute the command corepack enable.

The online editor warns that disk usage is too high​

When the disk space usage of the online editor exceeds 85%, you will see the following prompt:

You can click the "Auto Clean Cache" button to clean dependency caches such as npm / yarn / pnpm / pip. Meanwhile, please check if there are large files (e.g., compressed files, binary installation files) in the workspace. It is recommended to retain only necessary code files.

If the disk space usage exceeds 90%, the system will automatically clean the cache to ensure the normal operation of the online editor.

You can execute the command "df -h" to check the disk usage of the workspace.

Timeout When Obtaining Temporary Credentials: Some Features of the Online Editor Will Not Function Properly​

  • Cause Analysis

    When encountering the above prompt, first check whether the "Tencent CloudBase Toolkit V2" extension is installed in the online editor. If not installed, search for the keyword "Tencent CloudBase Toolkit V2" in the Extensions Marketplace to find and install this extension, then refresh the page and retry.

    If the issue is not among the above, it is likely due to insufficient disk space in the online editor, causing extension execution to malfunction. Please follow the solutions below to resolve it.

  • Solution

    Usually, when entering the online editor, a relevant prompt will appear. Refer to Online Editor Warns That Disk Usage Is Too High

    If there is no prompt, you can first open the terminal and execute the command df -h to check the remaining disk space.

    If you find that disk space is nearly exhausted, try running the following commands to clear the cache and clean up unnecessary large files in the workspace.

    npm cache clean --force
    pnpm store prune
    yarn cache clean
    pip cache purge

    Finally, check again with the df -h command to see if the disk space usage has decreased. If the usage has decreased, you can re-enter the online editor to perform operations.

  • Cause Analysis

    Debugging links are only valid within the online editor. To prevent external access, debugging links can only be accessed within the [Test Panel] and are inaccessible from any other location.

  • Solution

    Please use the [Test Panel] that automatically opens during debugging in the online editor to perform debugging operations, as shown in the figure below: