Repository navigation
fix: use verified staging Control API endpoint in Control Center - #52
Conversation
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
Reviewer's GuideUses of the APIPoint the Control Center at the verified staging Control API Worker so its API requests reach the active deployment.
TestsUpdate the staging smoke check’s default API base URL to match the verified Worker endpoint used by the Control Center.
Tips and commandsInteracting with Sourcery
Customizing Your ExperienceAccess your dashboard to:
Getting Help
|
|
ⓘ Qodo reviews are paused because your trial has ended. Ask your workspace admin to add credits to resume reviews. Manage billing |
Codex Review Summary: ❌ FailedThis comment shows the latest Codex review activity on this pull request.
ℹ️ About Codex in GitHubYour team has set up Codex to review pull requests in this repo. Reviews are triggered when you
Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings. |
|
You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard. |
There was a problem hiding this comment.
Hey - I've found 2 issues
Prompt for AI Agents
Please address the comments from this code review:
## Individual Comments
### Comment 1
<location path="index.html" line_range="58" />
<code_context>
let dashboardRequestSequence=0;
let dashboardAbortController=null;
-const CONTROL_API_BASE='https://ocodejs-server-api-staging.ocodejs-df1.workers.dev/api/v1';
+const CONTROL_API_BASE='https://ocodejs-server-api-staging.huynhthuongg2505-f9b.workers.dev/api/v1';
const MCP_ENDPOINT='https://ocodejs-mcp-staging.huynhthuongg2505-f9b.workers.dev/mcp';
const services=[['AI Agent Runtime','Điều phối tác vụ agent','Chưa kết nối','off','—'],['API Gateway','Định tuyến API & rate limits','Chưa kết nối','off','—'],['Identity / Auth','OAuth · session · account','Chưa kết nối','off','—'],['MCP Registry','Quản lý MCP endpoints','Chưa kết nối','off','—'],['Developer Telemetry','Logs · metrics · traces','Chưa kết nối','off','—']];
</code_context>
<issue_to_address>
**CI passes for broken dashboard**
When the workers.dev endpoint used by the dashboard fails while the custom-domain endpoint remains healthy, `check-control-api-staging.mjs` uses its default `https://api-staging.ocodejs.co/api/v1` because the workflow supplies no override, so CI passes without checking the dashboard’s endpoint and users see it as UNVERIFIED.
Configure the smoke test or workflow to probe the same workers.dev endpoint that the dashboard uses.
</issue_to_address>
### Comment 2
<location path="index.html" line_range="58" />
<code_context>
let dashboardRequestSequence=0;
let dashboardAbortController=null;
-const CONTROL_API_BASE='https://ocodejs-server-api-staging.ocodejs-df1.workers.dev/api/v1';
+const CONTROL_API_BASE='https://ocodejs-server-api-staging.huynhthuongg2505-f9b.workers.dev/api/v1';
const MCP_ENDPOINT='https://ocodejs-mcp-staging.huynhthuongg2505-f9b.workers.dev/mcp';
const services=[['AI Agent Runtime','Điều phối tác vụ agent','Chưa kết nối','off','—'],['API Gateway','Định tuyến API & rate limits','Chưa kết nối','off','—'],['Identity / Auth','OAuth · session · account','Chưa kết nối','off','—'],['MCP Registry','Quản lý MCP endpoints','Chưa kết nối','off','—'],['Developer Telemetry','Logs · metrics · traces','Chưa kết nối','off','—']];
</code_context>
<issue_to_address>
**Operators verify the wrong endpoint**
When an operator follows the staging guide or Worker README to verify or troubleshoot the API, the guide and README still point to the old `ocodejs-df1.workers.dev` hostname, which returns DNS `ENOTFOUND`, so operators cannot verify the dashboard’s replacement endpoint and receive misleading diagnostics.
Update the staging guide and Worker README to direct operators to the replacement workers.dev endpoint.
</issue_to_address>Sourcery assessment
Approval pending. 2 findings to address first.
Blocking findings: index.html:58, index.html:58
Sourcery withdrew this approval because the latest commits introduced blocking findings.
|
Deployment failed for project pages.ocodejs.theme with the following error: Learn More: https://vercel.com/ocodejs-co?upgradeToPro=build-rate-limit |
|
Deployment failed for project ocodejs.github.io with the following error: Learn More: https://vercel.com/ocodejs-co?upgradeToPro=build-rate-limit |
Summary
ocodejs-df1.workers.devhostname returned DNSENOTFOUNDfrom GitHub-hosted runners.huynhthuongg2505-f9b.workers.devhostname now passes DNS, health/live, health/ready, service registry, andhttps://ocodejs.coCORS checks after syncing the CI-tested Worker source to staging.Safety
Summary by Sourcery
Use the verified staging Control API endpoint and expand CI smoke checks across public ecosystem sites.
Bug Fixes:
Enhancements:
CI: