openclaw - 💡(How to fix) Fix ClawHub install for @openguardrails/moltguard fails with missing zip in /tmp [1 participants]

The package should download/extract/install successfully, or fail with a clearer package fetch error if the artifact is missing upstream.

Fix Plan

To resolve the issue with installing the @openguardrails/moltguard plugin, we will attempt to fix the temporary path handling for source-linked community code-plugins.

1. Verify the package metadata: Check the package metadata to ensure the artifact location is correct.
2. Update the OpenClaw configuration: Update the OpenClaw configuration to use a custom temporary directory.
3. Implement a custom download handler: Implement a custom download handler to handle the package download and extraction.

Example Code: Custom Download Handler

// custom-download-handler.js
const fs = require('fs');
const path = require('path');
const https = require('https');

const downloadPackage = (packageName, packageVersion) => {
  const url = `https://clawhub.com/packages/${packageName}/${packageVersion}.zip`;
  const tempDir = path.join(process.cwd(), 'tmp');
  const packagePath = path.join(tempDir, `${packageName}.zip`);

  return new Promise((resolve, reject) => {
    https.get(url, (res) => {
      const file = fs.createWriteStream(packagePath);
      res.pipe(file);

      file.on('finish', () => {
        file.close();
        resolve(packagePath);
      });
    }).on('error', (err) => {
      reject(err);
    });
  });
};

module.exports = downloadPackage;

Usage:

node custom-download-handler.js @openguardrails/moltguard 6.9.4

Then, use the downloaded package path to install the plugin:

openclaw plugins install --package-path /path/to/downloaded/package.zip

Verification

To verify the fix, attempt to install the plugin using the custom download handler and check the installation logs for any errors.

Extra Tips

• Ensure the custom temporary directory has the necessary permissions for the OpenClaw process.
• Consider implementing error handling and logging for the custom download handler.
• If the issue persists, investigate the package metadata and artifact location for any discrepancies.