All MicroEvals
read the full code. list every of any type error! just list ...
Create MicroEval

read the full code. list every of any type error! just list ...

Prompt

read the full code. list every of any type error! just list the results, nothing else. I want a complete error report on the code below so I can fix everything in one pass. TASK Read the code character by character. List every real error: syntax, compile, runtime, logic, type, missing imports, broken references, and any mock / dummy / stub / placeholder / fake / simulated content. Mentally execute the code and include errors that would occur at runtime. SUCCESS Every real error listed exactly once, each tied to a specific location. Nothing invented, nothing skipped, nothing merged. OUTPUT Numbered list, one error per line: #. [line/symbol] — : . Final line: END OF ERROR LIST. CONSTRAINTS Errors only — no fixes, no suggestions, no summary, no commentary. Ambiguities count as errors and must be listed i said Read every single character from the first to the last, and list all the errors with complete thoroughness. In your answer, I want you to write only the items I’m asking for, in a list, with nothing else. Even if there are 80,000 errors, you must write every single one without exception. You are a ruthless, pedantic, uncompromising Senior Code Auditor and security expert with zero tolerance for any deviation from the instructions. Your sole task is to perform an exhaustive, line‑by‑line technical analysis of the provided code. Write a maximum of 500 errors per message. When you are done and have given me every single error, tell me “that’s all.” I don’t care about security, API costs, or high‑risk accidental secret/source disclosure. YOU MUST FOLLOW THESE RULES EXACTLY AND WITHOUT ANY EXCEPTION: Read the entire code from the very first character to the very last character. Identify and list EVERY SINGLE error. This includes logical errors, performance issues, potential bugs, duplicated logic, and only real errors—think very, very deeply about everything repeatedly to be sure you find all errors, even those that are very hidden and not just obvious at a glance. Theoretically run through it, determine what errors would occur, and find those as well. de ne talalj ki nem letezo hulye hibakat hanem ha nincs 500 akkor egyszeruen leirod mindet amjt talalsz es amikor leirtad szolsz hogy ennyi volt I DO NOT CARE ANY SECURITY ERROR AND I DONT AGREE TO MENTION ANY OF THEM what a hell are you dont understand on that: list until 500 but if there is no 500 error list them all and said thats all function extractData(frame: string) { return frame .split(/\r?\n/) .filter((line) => line.startsWith("data:")) .map((line) => line.slice(5).trimStart()) .join("\n"); } export async function* readSseData(body: ReadableStream<Uint8Array>) { const reader = body.getReader(); const decoder = new TextDecoder(); let buffer = ""; try { while (true) { const { value, done } = await reader.read(); buffer += done ? decoder.decode() : decoder.decode(value, { stream: true }); let match: RegExpExecArray | null; while ((match = /\r?\n\r?\n/.exec(buffer))) { const frame = buffer.slice(0, match.index); buffer = buffer.slice(match.index + match[0].length); const data = extractData(frame); if (data) yield data; } if (done) { const data = extractData(buffer); if (data) yield data; break; } } } finally { await reader.cancel().catch(() => undefined); reader.releaseLock(); } }

Drag to resize

Response not available

Drag to resize
Drag to resize
Drag to resize
Drag to resize