Server to report configuration via meta#3
Conversation
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| policy_metadata["config"] = args.policy.config | ||
| policy_metadata["directory"] = args.policy.dir |
There was a problem hiding this comment.
Guard metadata enrichment for default policy
When the server is started without an explicit checkpoint (the default CLI path where args.policy is Default()), the new metadata assignments access args.policy.config and .dir, but the Default dataclass has no such attributes. This now raises an AttributeError before the websocket server is created, breaking the default-serving flow; only checkpoint-based invocations work. Consider populating these fields only when the policy is a Checkpoint.
Useful? React with 👍 / 👎.
No description provided.