Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Major outages across ChatGPT and API

status.openai.com

Post reply on HN
Print view View original

351–360 of 617 posts

Re: Major outages across ChatGPT and API

#354

Post by wokwokwok »

benterix wrote: post #71
Philpax wrote: post #12

Earlier quoted context omitted.

You can do that today depending on what you need from the models.

Let's say I'm writing Flask code all day, and I need help with various parts of my code. Can I do it today or not? With questions like, "How to add 'Log in with Google' to the login screen" etc.

If you have sufficiently good hardware, the 34B code llama model [1] (hint: pick the quantised model you can use based on “Max RAM required”, eg. q5/q6) running on llama.cpp [2], can answer many generic python and flask related questions, but it’s not quite good enough to generate entire code blocks for you like gpt4.

It’s probably as good as you can get at the moment though; and hey, trying it out costs you nothing but the time it takes to download llama.cpp and run “make” and then point it at the q6 model file.

So if it’s no good, you’ve probably wasted nothing more than like 30 min giving it a try.

[1] - https://huggingface.co/TheBloke/CodeLlama-34B-Instruct-GGUF [2] - https://github.com/ggerganov/llama.cpp

Re: Major outages across ChatGPT and API

#357

Post by bomewish »

lannisterstark wrote: post #282
m3kw9 wrote: post #149

Earlier quoted context omitted.

The first coding question I tested it on, it gave me something completely wrong and it was pretty easy stuff, I’m sure it gets a lot right but this just shows unreliability

Phind for me has worked pretty bleh compared to just back and forth conversation with a python GPT4 bot I made lol.

To use the api and stop them logging your chat? Have you compared to aider? Also got it on a repo?

Re: Major outages across ChatGPT and API

#358

Post by TechRemarker »

Yes, shortly have it said it was resolved I still was unable to access so assumed the fix was still slowing rolling out, or was infact still ongoing contrary to the status update which seems to be the case. Wouldn't call this "Another" outage rather they they just errenously that the existing issue was resolved.
Post reply on HN