> We were aware of this mismatch before launch. We expected the engine to return an error for any prompt it could not process, and our long-context tests returned successful responses, so we did not believe this to be an issue.
This is insane? They thought it would return errors for long context, which didn’t happen, and they proceeded assuming it was fine? Didn’t even investigate the known misconfiguration and issue before going to production?
This is insane? They thought it would return errors for long context, which didn’t happen, and they proceeded assuming it was fine? Didn’t even investigate the known misconfiguration and issue before going to production?