Skip to content

🧪 [testing improvement description]#1223

Closed
Hardonian wants to merge 2 commits into
mainfrom
add-queue-tests-3369590038567870017
Closed

🧪 [testing improvement description]#1223
Hardonian wants to merge 2 commits into
mainfrom
add-queue-tests-3369590038567870017

Conversation

@Hardonian

Copy link
Copy Markdown
Owner

🎯 What: Added tests for PrioritizedQueue class to cover missing queue and priority logic.
📊 Coverage: Covered constructor, job addition, startWorker, getStats, and lifecycle methods, checking priority calculation based on TenantTier.
Result: Improved reliability in queue system and priority calculation logic.


PR created automatically by Jules for task 3369590038567870017 started by @Hardonian

@google-labs-jules

Copy link
Copy Markdown

👋 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.

@vercel

vercel Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
settler Error Error Jul 17, 2026 1:00pm

@github-actions

Copy link
Copy Markdown

🔒 Release Safety Check Results

Safety Checks Passed

{"code":"NOT_FOUND","message":"Requested function was not found"}

@github-actions

Copy link
Copy Markdown

🔍 Classification Check Results

  • Total Files: 5292
  • OSS_PUBLIC: 52 ✅
  • PLATFORM_PROPRIETARY: 104
  • INTERNAL_BUSINESS: 1644
  • SECRET_RISK: 0 ✅
  • Violations: 0 ✅

No violations detected. Safe to merge!


📊 View full classification report

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a979be3600

ℹ️ 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".

expect(mockQueueInstance.add).toHaveBeenCalledWith(
"job",
data,
expect.objectContaining({ priority: 50 })

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Correct BullMQ priority ordering in the test

For non-enterprise jobs, this expectation locks in priority: 50 for a PRO/HIGH job, but BullMQ v5 processes lower numeric priority values first (official docs: https://docs.bullmq.io/guide/jobs/prioritized). In the inspected implementation, FREE/LOW gets 1 while PRO/HIGH gets 50, so this new test codifies the inversion and will keep higher-tier urgent jobs behind lower-tier jobs once real BullMQ ordering is exercised.

Useful? React with 👍 / 👎.

@github-actions

Copy link
Copy Markdown

🔒 Release Safety Check Results

Safety Checks Passed

{"code":"NOT_FOUND","message":"Requested function was not found"}

@github-actions

Copy link
Copy Markdown

🔍 Classification Check Results

  • Total Files: 5292
  • OSS_PUBLIC: 52 ✅
  • PLATFORM_PROPRIETARY: 104
  • INTERNAL_BUSINESS: 1644
  • SECRET_RISK: 0 ✅
  • Violations: 0 ✅

No violations detected. Safe to merge!


📊 View full classification report

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fbae2c65c3

ℹ️ 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".

"outDir": "dist",
"rootDir": "src"
},
"references": [{ "path": "../logger" }],

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Build logger before referencing it in agents

With this project reference in place, the package-local script pnpm --filter @settler/agents run typecheck now fails on a clean checkout when packages/logger/dist has not already been emitted: TypeScript reports TS6305 for packages/logger/dist/index.d.ts from src/security-agent.ts. The package still runs plain tsc --noEmit, so it does not build referenced projects itself; either the agents script needs to use build mode / a prebuild step, or this reference should not require prebuilt logger outputs.

Useful? React with 👍 / 👎.

@Hardonian

Copy link
Copy Markdown
Owner Author

Closed during PR cleanup: mergeable=UNKNOWN base=main. Reopen only with a current verified change.

@Hardonian Hardonian closed this Jul 20, 2026
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