trace: emit agent-core events from NOC graph#61
Conversation
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
PR Code Suggestions ✨Explore these optional code suggestions:
|
b030457 to
c1ff300
Compare
|
Addressed the PR-agent suggestions in c1ff300:
Validation after the fix: |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: b030457ef1
ℹ️ 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".
| "discord.py>=2.5.0", | ||
| "pyjwt[crypto]>=2.9", | ||
| "asyncpg>=0.30", | ||
| "agent-core", |
There was a problem hiding this comment.
Keep trace-only agent-core out of required installs
Because the tracing code imports agent_core lazily and returns before importing it unless HYRULE_NOC_AGENT_CORE_TRACE is enabled, this required dependency now makes normal installs and the CI uv sync --frozen --group dev path fetch https://github.com/AS215932/agent-core even when tracing is off. In environments without GitHub egress/credentials, the whole app/test install fails before the best-effort flag gate can apply; make this an optional extra or otherwise ensure it is available from the normal dependency source.
Useful? React with 👍 / 👎.
Summary
Validation