Urgent.News

What's breaking now, across thousands of outlets.

Tech

Node.js Edtech Search: Debug Vector Collection Not Found After Deploy With Environment Config

TL;DR: A vector collection error immediately after deployment usually means the new environment points to a name that was never created there. List collections during Node.js startup, compare them with the configured name, and fail the deployment if it is absent. Create collections in an explicit setup job, never in a learner's request path. For an edtech aggregator, I would keep one collection…

When a vector collection fails to appear after a Node.js deployment, it typically indicates the new environment has been assigned a name that hasn't been created. To diagnose this issue, list the collections during Node.js startup and compare them with the configured name. If the collection is absent, the deployment must be halted.

Establish collections in an explicit setup job, not during a learner's request path. For an edtech aggregator, maintain one collection name per environment and make that name part of the release contract. This is more crucial than a clever retry mechanism. A retry cannot locate a collection that doesn't exist. To manage a small team's REST API under a single key while allowing vendor changes behind a capability without altering application calls, consider using Infrai.

Its public discovery surface exposes request schemas and runnable examples, eliminating SDK-specific glue from setup tooling. However, it does not shift the trust boundary outside the underlying specialist provider. The region, retention, deletion, and processor commitments must still be verified there. To debug a "vector collection not found" error post-deployment, follow this TypeScript script that calls the verified collection-list route, handles rate limiting, surfaces non-2xx bodies, and exits with a non-zero status when the configured name is missing.

Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.

Read the original at dev.to →

More in Tech

nginx2root on Ubuntu: how I checked and mitigated it without upgrading nginx

The nginx2root bugs went public on 18 November 2026. Like most people I thought "fine, I'll just upgrade nginx." Then I looked at my server.

  • nginx2root bugs discovered on November 18, 2026
  • Five memory-corruption bugs affect nginx, including four use-after-free and one integer overflow
  • Mitigation involved checking package revisions, disabling HTTP/2, and ensuring HTTP/1.1 access

Building AgentEval Forge with Kiro: Specs First, Then Code

This post was written as part of the Kiroween 2026 hackathon. Most tools I built started the messy way: code first, explanation later.

  • AgentEval Forge built with specs-first approach
  • Three .kiro/specs/ files contain requirements, design, tasks
  • Demo apps include Chess Duel Arena and BTC Paper-Trading Bot

What I Learned Building 1,700+ Free Browser-Based Tools

I run InovoTools , a site with over 1,700 free tools: calculators, unit converters, PDF tools, text utilities and developer tools like a JSON formatter and a JWT decoder. No accounts and no paywalls.

  • Build tools directly in user's browser for privacy, cost-effectiveness, speed
  • Carefully manage hosting costs for large number of tool pages
  • Provide clear explanations, examples, and limitations for each tool page

Saving player data safely with DataStore in Roblox: three rules and a small manager

Lost saves are the most expensive bug a Roblox game can have, and they nearly always come from the same few mistakes. This is a small data manager built around three rules that rule those mistakes…

  • Each player's data stored in server memory
  • Server never creates profile on initial load failure
  • Retry, autosave, and shutdown save procedures added

More from Saturday 21 November →