SShortSingh.
Back to feed

NovelAI V5 Models Work in ComfyUI but Anlas Balance Error Needs a Manual Fix

0
·87 views

Both nai-diffusion-5-full and nai-diffusion-5-curated model IDs function correctly through the ComfyUI_NAIDGenerator node, despite a README caveat stating they had not been verified against the live API. A widely reported 'Error fetching Anlas 400' is unrelated to the models themselves and stems from NovelAI having moved its user endpoints from api.novelai.net to image.novelai.net around the V5 launch. The fix requires updating USER_API_BASE_URL in two places within nodes.py to point to the new host. An additional complication arises because the new endpoint returns trainingStepsLeft as a nested object rather than an integer, causing a TypeError when the node attempts arithmetic on the balance. On an Opus-tier account, generating a standard 832×1216 image at 28 steps consumed zero Anlas, confirming the generation pipeline itself works as expected.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Log in to join the discussion and vote.

Log in

Related stories

0
ProgrammingDEV Community ·

Domains with multiple SPF records fail validation; merging them into one fixes it

A domain may publish only one SPF record, and under RFC 7208 a domain with two SPF records fails authentication. Email service setup guides often instruct users to add a new SPF record, which leads people to create duplicates instead of updating the existing one. The recommended fix is to combine the include mechanisms from all records into a single SPF record and delete the extras. Administrators should also watch the 10-lookup limit, since each include counts toward it. The problem can be detected by checking whether more than one of a domain's TXT records begins with v=spf1.

0
ProgrammingDEV Community ·

Guidance on retry budgets for publishing pipelines

A short DEV Community note offers advice on handling retries in a publishing pipeline. It recommends capping the number of retry attempts so failures do not repeat indefinitely. It also suggests using exponential backoff to space out successive retries. The note further advises preserving the most recent error for diagnostic purposes. The article links to its source repository, an Mbin instance, and the author's profile on DEV.

0
ProgrammingDEV Community ·

DateTime and DateTimeOffset pitfalls in .NET when time zones and clock changes collide

A .NET backend developer describes how storing dates without their time zone led to inconsistent query results across regions in a production UI. The core problem was that SQL Server's datetime2 column dropped the offset from DateTimeOffset values, so the same filter returned different rows depending on the user's zone. The article explains that a day with a daylight saving transition lasts 25 or 23 hours, so fixed 24-hour calculations can miss data. It also contrasts DateTime's ambiguous Kind handling with DateTimeOffset, which preserves a moment in time but not the originating time zone. The author proposes keeping the zone alongside the instant and sets out criteria for a solution that avoids building a custom time zone database.