nachzugler's recent timeline updates nachzugler's recent timeline updates |
nachzuglerV2EX member #52227, joined on 2013-12-19 16:45:41 +08:00 |
| GPT-5.6 疑似灰度流出 OpenAI • nachzugler • May 14 • Lastly replied by HaydenYe | 36 |
nachzugler's recent replies
May 12 Replied to a topic by nachzugler › OpenAI › GPT-5.6 疑似灰度流出 |
那确实，我就纳闷了。。
May 12 Replied to a topic by nachzugler › OpenAI › GPT-5.6 疑似灰度流出 |
@hang333 跑了，我其实不知道这是啥
May 12 Replied to a topic by nachzugler › OpenAI › GPT-5.6 疑似灰度流出 |
好奇怪啊搞得我怀疑人生
May 12 Replied to a topic by nachzugler › OpenAI › GPT-5.6 疑似灰度流出 |
@yokisama 你下方的 opencode context window 显示的 9%预示着就是 1md 模型 因为我写死的 1050000
May 12 Replied to a topic by nachzugler › OpenAI › GPT-5.6 疑似灰度流出 |
May 12 Replied to a topic by nachzugler › OpenAI › GPT-5.6 疑似灰度流出 |
@BlueSkyXN 不是，我自己的 是透传 可控
May 12 Replied to a topic by nachzugler › OpenAI › GPT-5.6 疑似灰度流出 |
The 12M isolated run came back fast with HTTP 200, which means the earlier bigger failures were mostly a concurrency/tooling artifact; I’m rechecking 15M the same way before pushing the total higher.
May 12 Replied to a topic by nachzugler › OpenAI › GPT-5.6 疑似灰度流出 |
@neteroster
I’ve now proven the 8M and 12M one-message failures are request-string guards, not token-limit rejections, so I’m probing aggregate size with multiple sub-cap messages next.
我有点不可置信，目前探测的上限到了 10M
I’ve now proven the 8M and 12M one-message failures are request-string guards, not token-limit rejections, so I’m probing aggregate size with multiple sub-cap messages next.
我有点不可置信，目前探测的上限到了 10M
May 12 Replied to a topic by nachzugler › OpenAI › GPT-5.6 疑似灰度流出 |
@Removable 同步出来的，只是之前通道关着
May 12 Replied to a topic by nachzugler › OpenAI › GPT-5.6 疑似灰度流出 |
Select Language