Robo

/fixedWith https://github.com/microsoft/vscode/commit/8422282f04e8401240d4bd2d1a1184d97080812e

Thanks @bpasero , the issue only affects non standard custom schemes and data urls. The ones we use `vscode-file`, `vscode-webview` for `loadURL` are standard schemes, will continue to work as...

Unless we need to revert for major regressions, this change will be available in our `1.98` release in the beginning of March.

Sorry missed this thread, if you are still seeing this issue with electron fetcher can you restart the application with `--log-net-log=/netlog.json`, once the failure happens quit the application and send...

Thanks for narrowing down the issue, however I see a [comment](https://github.com/microsoft/vscode-copilot-release/issues/10262#issuecomment-2968041399) mentioning that disabling Electron fetcher resolved the issue. Do others facing the issue also see it addressed when running...

> I don’t know what the implementation details look like, but if these fetchers are running in different sub processes, it’s possible that they’re getting different DNS results when running...

> The troubleshooting done here already is very thorough, so thank you for that! As a next step, could someone experiencing this issue capture: >Which nameservers are being used when...

@MarshallOfSound this might be a bug in our `net.fetch` implementation. The [spec](https://fetch.spec.whatwg.org/#http-fetch) mentions if `mode` is not `navigate` then an `opaqueResponse` should be provided. We are missing the handling of...

Okay Node.js implementation was initially following the spec but it was later changed per https://github.com/nodejs/undici/issues/1193. What should be the behavior we match in our `net.Fetch` API for this case ?

For browsers opaque responses are needed for preventing xss attacks https://fetch.spec.whatwg.org/#atomic-http-redirect-handling. In Electron, users already can use Node.js fetch in these process to get those responses, so if we were...