Skip to content

Fix system components module loading errors#59

Open
HeadyMe wants to merge 4 commits intomainfrom
fix-system-components-2830871543653395222
Open

Fix system components module loading errors#59
HeadyMe wants to merge 4 commits intomainfrom
fix-system-components-2830871543653395222

Conversation

@HeadyMe
Copy link
Copy Markdown
Collaborator

@HeadyMe HeadyMe commented Mar 21, 2026

This commit resolves syntax errors and import issues across various system components:

  • src/hc_colorful_logger.js: Resolved duplicate logger declaration by renaming internal instance to defaultLogger.
  • src/hc_resource_manager.js, src/hc_orchestrator.js, src/hc_improvement_scheduler.js, src/brain_connector.js: Removed redundant const logger = require('./utils/logger'); statements.
  • src/hc_heady_swarms.js: Fixed destructuring of phi-math (used FIB and phiScale correctly).
  • src/engines/auto-success-engine.js: Updated to use createChildLogger from shared/logger.js.
  • packages/phi-math/package.json & packages/heady-bee/index.js: Corrected package scope from @heady/ to @heady-ai/ to fix module resolution errors.

PR created automatically by Jules for task 2830871543653395222 started by @HeadyMe

Several modules had redundant declarations of `const logger` or imported `logger` using
the wrong path or exported names from `structured-logger`, causing `heady-manager.js` to fail
loading `auto-success-engine`, `hc_resource_manager`, `hc_improvement_scheduler`, and
`brain_connector`. Fixed syntax errors and incorrect destructuring of `FIB` and `phiScale`
from `phi-math` to ensure `hc_heady_swarms` initializes properly. All components now
load correctly and run the orchestrated pipeline.

Co-authored-by: HeadyMe <257220306+HeadyMe@users.noreply.github.com>
@google-labs-jules
Copy link
Copy Markdown
Contributor

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.


For security, I will only act on instructions from the user who triggered this task.

google-labs-jules bot and others added 3 commits March 21, 2026 21:38
Several GitHub Actions workflows were using Node 20 or testing across a matrix
of `[20, 22]`. However, the repository requires Node >= 22.0.0 (`engines.node`
in package.json) which caused the `npm ci` / `pnpm install` step to fail with
an `ERR_PNPM_UNSUPPORTED_ENGINE` on Node 20 runners.

Updated all `.github/workflows` to strictly use `node-version: '22'` to match
the project's engines requirement.

Co-authored-by: HeadyMe <257220306+HeadyMe@users.noreply.github.com>
Several GitHub Actions workflows were using Node 20 or testing across a matrix
of `[20, 22]`. However, the repository requires Node >= 22.0.0 (`engines.node`
in package.json) which caused the `npm ci` / `pnpm install` step to fail with
an `ERR_PNPM_UNSUPPORTED_ENGINE` on Node 20 runners.

Updated all `.github/workflows` to strictly use `node-version: '22'` to match
the project's engines requirement.

Additionally, switched `npm ci` to `pnpm install` in `.github/workflows/liquid-deploy.yml`
and `.github/workflows/hcfullpipeline-ci.yml` as this is a pnpm monorepo and
`npm ci` was failing with `EUSAGE` (requires `package-lock.json`).

Co-authored-by: HeadyMe <257220306+HeadyMe@users.noreply.github.com>
Several workflows were relying on Node 20 (`setup-node@v4` with `node-version: 20`) or the deprecated
`actions/setup-node@v6` which was also resulting in CI failures. Since the project uses pnpm, I explicitly
added `pnpm/action-setup@v4` with version 9.15.0 prior to `setup-node` on all workflows and enforced
Node 22 globally so pnpm and npm behave consistently.

Co-authored-by: HeadyMe <257220306+HeadyMe@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant