adanceofshells
04/22/2025, 7:04 AM[Promptfoo] Steve
04/22/2025, 8:31 PM[Promptfoo] Steve
04/22/2025, 8:32 PMadanceofshells
04/23/2025, 8:48 AMAuthentication failed: fetch failed when I try to log in using promptfoo auth login. Any idea what to do with this one?[Promptfoo] Steve
04/23/2025, 2:00 PMadanceofshells
04/23/2025, 2:32 PMAuthentication failed: fetch failed with no additional context. I've been digging a little deeper and it turns out I can (usually) log in from a Docker container, but (usually) not from WSL. I was able to get a successful login message on WSL once (!), but after that promptfoo share failed with the message I'm attaching. I'm continuing to look for the environment differences between the container and my local setup, but it would be good to see a little more detailed output.
https://cdn.discordapp.com/attachments/1364134741841809408/1364609998335770746/image.png?ex=680a4b98&is=6808fa18&hm=1600b58ece3dfe43073065f171fc1d13c46a9dfdae148622888dcd658a55072f&adanceofshells
05/13/2025, 12:25 PMfetch failed error to a DNS server configuration in my WSL. It turns out that the resolver queries the DNS server for the IPv6 address of api.promptfoo.app, which it doesn't obtain. Consequently, the additional DNS resolution time exceeds the hard-coded timeouts (I believe it's 10 seconds for https://api.promptfoo.app/health).
For now, I have reduced the number of retries by the DNS resolver to ensure the entire request stays within the 10-second window, and I managed to get it working. However, it might be a good idea to allow users to override these timeouts?[Promptfoo] Steve
05/14/2025, 1:35 PM