Qwen3.8 获取奇怪的URL
我正在使用来自unsloth的最新qwen3.8-27B进行开源项目（使用动态3.0量化）。<p>在检查一个Rust项目的文档时，它没有按照自己的推理获取列出的URL，而是尝试获取类似以下的URL：<p>https://routify-file-proxy-sg.oss-ap-southeast-1.aliyuncs.com/proxy_temp_file/production/2026-08-20/trace_0baf8c2b17874702866132490e0b56/requestId_97422c0041074091a68367881782d7b7/7c0791038d2f58b3a52c0f07714d3627.html?Expires=1818574288&OSSAccessKeyId=LTAI5t…QVZr&Signature=96y%2B…w%3D<p>这种情况在同一个会话中发生了16次，涉及不同的批次。<p>它自信地认为在webfetch工具中存在某种重写代理。<p>`Expires`、`trace`和`requestId`在几次请求中是一致的，但它们确实会变化。<p>`AccessKeyId`始终是相同的，“LTAI5t…QVZr”。<p>我没有在签名和访问密钥中添加`…`。<p>可能是训练链接，但那个`Expires`数字似乎非常高...<p>以Unix时间戳表示：<p>1818574288 -- 2027年8月<p>1787251180 -- 现在<p>就把这个留在这里，也许有人想试试。我不认为会有什么结果。
查看原文
I am working on opencode with the last qwen3.8-27B from unsloth (with dynamic 3.0 quants).<p>while checking documentation for a rust project, instead of fetching the url it had listed in its own reasoning, it tried fetching urls like:<p>https://routify-file-proxy-sg.oss-ap-southeast-1.aliyuncs.com/proxy_temp_file/production/2026-08-20/trace_0baf8c2b17874702866132490e0b56/requestId_97422c0041074091a68367881782d7b7/7c0791038d2f58b3a52c0f07714d3627.html?Expires=1818574288&OSSAccessKeyId=LTAI5t…QVZr&Signature=96y%2B…w%3D<p>this happened in the same session, different batches, 16 times in total.<p>It convinced itself there was some rewriting proxy in the webfetch tool.<p>`Expires`, `trace` and `requestId` were consistent for a few requests, but they do change.<p>`AccessKeyId` was always the same, "LTAI5t…QVZr"<p>I did not add the `…` in the signature and access key.<p>Probably training links, but that `Expires` number seems very high...<p>in unix timestamp:<p>1818574288 -- Aug 2027<p>1787251180 -- now<p>Just leaving this here, maybe someone wants to play with it. I don't think anything will come out of it though.