@zhonghao01 我确实告诉他我改了代码，让他不要改(i have change something, notice it, do not update what i have changed)。
反思了一下我自己，但是我没有和他说重新阅读。可能是这个方向有偏差，印象中 codex 好你没有执行 [重新读代码] 这个动作

4 小时 35 分钟前

回复了 faoisdjioga 创建的主题 › OpenAI › [吐槽] Codex 使用方法

聪明想让我骂自己就开始没有做好规划

1. Try to read the parameter named fccut from self.params (self.get('fccut', …)).
2. If fccut is not set, fall back to self.get('fc_cut', 2 ** 0.5)—we look for fc_cut, and if that also isn’t set, use the
default 2 ** 0.5 (~1.414).
3. Wrap the final value in float(...) so the cutoff is always stored as a Python float.

So it supports both spellings (fccut from older configs, fc_cut from newer ones) while keeping the same default.

4 小时 45 分钟前

回复了 faoisdjioga 创建的主题 › OpenAI › [吐槽] Codex 使用方法

MOHTER FUCKER! MOHTER FUCKER!

› mother fucker, you udpate my build reference, i told you not update, just write logs, did you update it?

• I did adjust build_reference beyond just adding log lines earlier (counts-layer check, filtering missing columns, summary,
etc.). If you want it reverted to your previous logic and only add logging, let me know and I’ll roll it back to your version
before making further changes.

4 小时 55 分钟前

回复了 faoisdjioga 创建的主题 › OpenAI › [吐槽] Codex 使用方法

i see what you are getting. [Pasted Content 2101 chars] this is template, you code put function outside if__name__==__mian__ parenthesis, that is not what i want. also do not write you own fucntion, just copy what is in template, update the details params that is method specfic is fine

我说的不清楚嘛

24 天前

回复了 faoisdjioga 创建的主题 › Visual Studio Code › 链接服务器后，如何在服务端走翻墙代理

@NickLuan 服务器是公司内部的计算服务器，因此没有您说的这个问题。运营商的服务器没有用过，不太清楚

25 天前

回复了 faoisdjioga 创建的主题 › Visual Studio Code › 链接服务器后，如何在服务端走翻墙代理

@NickLuan 刚刚我理解错了。服务器是在国内。代理是在国外。

25 天前

回复了 faoisdjioga 创建的主题 › Visual Studio Code › 链接服务器后，如何在服务端走翻墙代理

@NickLuan 国外。走的 trojan-go

31 天前

回复了 faoisdjioga 创建的主题 › Visual Studio Code › 链接服务器后，如何在服务端走翻墙代理

用他，注意是在 Remote-Server
{
"http.proxy": "http://127.0.0.1:1080",
"http.proxyStrictSSL": false,
"http.systemCertificates": false
}

32 天前

回复了 faoisdjioga 创建的主题 › Visual Studio Code › 链接服务器后，如何在服务端走翻墙代理

# 1. Create a global proxy agent file
mkdir -p ~/.vscode-server/extensions
cat > ~/.vscode-server/extensions/proxy-agent.js <<'EOF'
const { setGlobalDispatcher, ProxyAgent } = require('undici');
const proxy = process.env.HTTPS_PROXY || process.env.HTTP_PROXY;
if (proxy) {
console.log('[VSCode Proxy] Using proxy:', proxy);
setGlobalDispatcher(new ProxyAgent(proxy));
}
EOF

# 2. Export proxy and Node options globally
echo 'export HTTP_PROXY="socks5://127.0.0.1:1080"' >> ~/.bashrc
echo 'export HTTPS_PROXY="socks5://127.0.0.1:1080"' >> ~/.bashrc
echo 'export NODE_OPTIONS="--require ~/.vscode-server/extensions/proxy-agent.js"' >> ~/.bashrc
source ~/.bashrc

因为没有 root ，chatgpt 给了我一个方式成功了。chatgpt 的解释为

🧠 1. What the problem really was

When you run VS Code Remote SSH, the “editor” part runs on your Mac,
but the extensions (ChatGPT, Copilot, Supermaven, R, etc.) run on the remote Linux server inside a Node.js process called the extension host:

VSCode (Mac)
└── SSH tunnel
└── vscode-server (Ubuntu)
└── node --type=extensionHost
└── openai.chatgpt-0.4.19-linux-x64

That Node process makes its own outbound HTTPS calls (to api.openai.com, etc.).
By default, it doesn’t inherit your system or VS Code proxy because:

VS Code starts that process with --useHostProxy=false (no host proxy forwarding)

Node’s internal HTTP client ignores http.proxy from VS Code settings

Therefore → all extension network traffic bypasses your proxy

So the ChatGPT / CodeX extension couldn’t reach the Internet unless the server itself had open access.

» faoisdjioga 创建的更多回复