spaasis

Yeah this behavior is not the best. I could try having a go at this... Am I correct in inferring that the ultimately the parameter types (for postgres) come from...

@ErikEJ apologies, misunderstood the opening

In Swagger UI I've gotten used to being able to copy the request as cURL - do you think that would be reasonable to include here too?

@antlio I think it could be something like taking this:  And showing it, with the actual sent values, here: 

@antlio Oh sorry, I missed this tiny tool in the bottom left of the send dialog. The stuff I need is already implemented 🎉 

I'm still hitting this with 0.59.1: ``` aider --model ollama/llama3.1:latest --no-verify-ssl ────────────────────────────────── Aider v0.59.1 Model: ollama/llama3.1:latest with whole edit format ────────────────────────────────── > Hello [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: unable to...

I worked around this by creating an nginx proxy: ``` events {} http { server { listen 80; server_name ollama.local; location / { proxy_pass https://org-internal-ollama; proxy_set_header Authorization "Bearer eyJh...."; proxy_ssl_verify...

Just confirming that this fix works - making these modifications allows me to connect to an ollama instance that would otherwise fail from the self signed certificate Upd: there's still...

Got a note for this in a security audit. Quite surprised there isn't an option for turning off stack traces already

@mikepizzo that makes sense. The stack trace says as much too - sorry I didn't read into it enough: [16:27:24 ERR] An unhandled exception has occurred while executing the request....