chore: allow custom TEE log path

[batudo]

Relates to

#2415

Risks

Low: it only affects the TEE logs.

Background

What does this PR do?

Fixes an error when TEE logs are enabled that shows the message "Cannot open database because the directory does not exist".

What kind of change is this?

Bug fix.

Documentation changes needed?

My changes do not require a change to the project documentation.

Testing

Where should a reviewer start?

Starting an agent with tee-log enabled using TDX_DSSTACK

Detailed testing steps

Configure the agent with this env variables:

TEE_MODE=LOCAL
WALLET_SECRET_SALT=secret_salt
ENABLE_TEE_LOG=true

Start TEE simulator as on https://elizaos.github.io/eliza/docs/advanced/eliza-in-tee/#environment-setup

docker run --rm -p 8090:8090 phalanetwork/tappd-simulator:latest

And then start the agent with:

pnpm start

This should not display the message "Cannot open database because the directory does not exist" when in this branch, same config with the code in main will display it.

Discord username

fcatena

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

---

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

• Review comments: Directly reply to a review comment made by CodeRabbit. Example:
  • I pushed a fix in commit <commit_id>, please review it.
  • Generate unit testing code for this file.
  • Open a follow-up GitHub issue for this discussion.
• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit testing code for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
  • @coderabbitai read src/utils.ts and generate unit testing code.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
  • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai full review to do a full review from scratch and review all the files again.
• @coderabbitai summary to regenerate the summary of the PR.
• @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
• @coderabbitai help to get help.

Other keywords and placeholders

• Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
• Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
• Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• Please see the configuration documentation for more information.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

• Visit our Documentation for detailed information on how to use CodeRabbit.
• Join our Discord Community to get help, request features, and share feedback.
• Follow us on X/Twitter for updates and announcements.

[github-actions]

Hi @batudo! Welcome to the elizaOS community. Thanks for submitting your first pull request; your efforts are helping us accelerate towards AGI. We'll review it shortly. You are now an elizaOS contributor!

[HashWarlock]

@ShuochengWang do you know about the last 2 changes to TEE Log plugin?

[ShuochengWang]

@ShuochengWang do you know about the last 2 changes to TEE Log plugin?

This indeed appears to be an issue. It is likely caused by differing initial paths.

In the SGX environment, the initial path is /agent, and then it searches according to the database path ./data/tee_log.sqlite. Ultimately, it uses agent/data/tee_log.sqlite as the path. The agent/data/ path is written into https://github.com/elizaOS/eliza/blob/develop/eliza.manifest.template

However, in the dstack environment, the initial path seems to be the root directory? This discrepancy in paths leads to a mismatch?

[ShuochengWang]

Just confirmed:
In the SGX environment, the path data/tee_log.sqlite works. This is because the starting directory in the SGX environment is ./agent.
In the dstack Local environment, the path data/tee_log.sqlite also works.

This path is the same as the one I initially set, so why was this correct path modified earlier in #2415

The reason for the different starting directory in SGX is that I started the application in the agent directory using node --loader ts-node/esm src/index.ts --isRoot, rather than using pnpm. Using pnpm in the SGX environment introduces more complex dependencies.

Additionally, recent testing revealed that the latest version of Eliza has more WASM-related dependencies, and the SGX environment is very unfriendly to the default WASM configuration. The default WASM configuration consumes an enormous amount of memory during initialization in SGX. The current develop version of Eliza requires the SGX EPC to be set to 128GB of memory to start (enabling EDMM significantly speeds up the startup process, as it prevents the actual consumption of this much memory, which is entirely caused by WASM initialization).

@HashWarlock

[batudo]

If you initialize the agent from the repo root, which is the intention on all README notes and tutorials, then the previous path was wrong.

[HashWarlock]

If you initialize the agent from the repo root, which is the intention on all README notes and tutorials, then the previous path was wrong.

Launching in TEE Cloud using dstack requires building docker image and creating a docker-compose file to launch. So the path would be <root-dir>/data/tee-log.sqlite. Maybe this path can be an env variable? Haven't thought too much on this.

[ShuochengWang]

If you initialize the agent from the repo root, which is the intention on all README notes and tutorials, then the previous path was wrong.

Launching in TEE Cloud using dstack requires building docker image and creating a docker-compose file to launch. So the path would be <root-dir>/data/tee-log.sqlite. Maybe this path can be an env variable? Haven't thought too much on this.

Well, then I think the best choice here is to use an env variable instead of a constant path @batudo

[batudo]

Done, you can now configure the path via ENV.