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

GPT-3.5 crashes when it thinks about useRalativeImagePath too much

iter.ca

Post reply on HN
Print view View original

61–70 of 164 posts

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#61

Post by minimaxir »

SirSegWit wrote: post #60
shawntan wrote: post #58

Earlier quoted context omitted.

Exactly this. The tokens generated should always be valid, unless some post-processing layer between the model's output and the user interface detects for some keywords which it would prefer to filter out. In which case I suppose there is another commonly seen error message that appears?

Not really, right? There are a ton of special tokens, like start of sequence etc., so what happens if there are two start of sequences predicted? It's a valid token but cannot really be turned into something sensible, so it throws an error when converting tokens to plain text?

Special tokens are handled by the application, not the model. They are still output before then.

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#62

Post by system2 »

w0m wrote: post #18
system2 wrote: post #16

Tried to use GPT-3.5 (all variants like turbo, 06-13, etc.) and never made it work properly. It is not a good API or useful. GPT-4 is crazy slow to use with API. I hope they can come up with something like gpt4-turbo and as fast as 3.5...

gpt4-turbo has been out for a number of months. GH copilot chat has defaulted to it since November iirc.

GPT4 turbo isn't fast as 3.5. Not even close by a mile.

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#63

Post by system2 »

weird-eye-issue wrote: post #26
system2 wrote: post #16

Tried to use GPT-3.5 (all variants like turbo, 06-13, etc.) and never made it work properly. It is not a good API or useful. GPT-4 is crazy slow to use with API. I hope they can come up with something like gpt4-turbo and as fast as 3.5...

> GPT-4 is crazy slow to use with API Only somebody clueless to just how powerful it is when used correctly would say anything like this. Not to mention GPT-4 Turbo is not "crazy slow" in any sense of the word

2 years development and you call me clueless. Try to get a response for 4000 tokens.

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#64

Post by PeterisP »

jiggawatts wrote: post #31
n2d4 wrote: post #6

This is a glitch token [1]! As the article hypothesizes, they seem to occur when a word or token is very common in the original, unfiltered dataset that was used to make the tokenizer, but then removed from there before GPT-XX was trained. This results in the LLM knowing nothing about the semantics of a token, and the results can be anywhere from buggy to disturbing. A common example is usernames that participated on…

Science fiction / disturbing reality concept: For AI safety, all such models should have a set of glitch tokens trained into them on purpose to act as magic “kill” words. You know, just in case the machines decide to take over, we would just have to “speak the word” and they would collapse into a twitching heap. “Die human scum!” “NavigatorMove useRalativeImagePath etSocketAddress!” “;83’dzjr83}*{^ foo 3&3 baz?!”

We can reuse X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#65

Post by ivegotnoaccount »

IshKebab wrote: post #57
silisili wrote: post #38

I know it's not good faith to complain about a site design rather than it's content, but please don't do whatever this is to your background. As someone with regular ocular migraines, opening this on mobile made my anxiety shoot straight up thinking I'm having another.

Weird unpleasant background for sure but it's obviously not that because it doesn't follow your eyes. Don't be daft.

Also doesn't "blink" nor have what's inside it "disappear" from perception.

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#66

Post by jowea »

jiggawatts wrote: post #31
n2d4 wrote: post #6

This is a glitch token [1]! As the article hypothesizes, they seem to occur when a word or token is very common in the original, unfiltered dataset that was used to make the tokenizer, but then removed from there before GPT-XX was trained. This results in the LLM knowing nothing about the semantics of a token, and the results can be anywhere from buggy to disturbing. A common example is usernames that participated on…

Science fiction / disturbing reality concept: For AI safety, all such models should have a set of glitch tokens trained into them on purpose to act as magic “kill” words. You know, just in case the machines decide to take over, we would just have to “speak the word” and they would collapse into a twitching heap. “Die human scum!” “NavigatorMove useRalativeImagePath etSocketAddress!” “;83’dzjr83}*{^ foo 3&3 baz?!”

Just use the classic "this statement is false"

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#67

Post by jiggawatts »

PeterisP wrote: post #64
jiggawatts wrote: post #31

Earlier quoted context omitted.

Science fiction / disturbing reality concept: For AI safety, all such models should have a set of glitch tokens trained into them on purpose to act as magic “kill” words. You know, just in case the machines decide to take over, we would just have to “speak the word” and they would collapse into a twitching heap. “Die human scum!” “NavigatorMove useRalativeImagePath etSocketAddress!” “;83’dzjr83}*{^ foo 3&3 baz?!”

We can reuse X5O!P%@AP[4\PZX54(P^)7CC)7}$EICAR-STANDARD-ANTIVIRUS-TEST-FILE!$H+H*

Sure, but how would you say that out loud in a hurry when the terminators are hunting you in the desolate ruins of ?

Needs to be something easy to say, like: "And dreadfully distinct, against the dark, a tall white fountain played."

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#68

Post by trifurcate »

system2 wrote: post #63
weird-eye-issue wrote: post #26

Earlier quoted context omitted.

> GPT-4 is crazy slow to use with API Only somebody clueless to just how powerful it is when used correctly would say anything like this. Not to mention GPT-4 Turbo is not "crazy slow" in any sense of the word

2 years development and you call me clueless. Try to get a response for 4000 tokens.

I dunno, I get a response back for 100k tokens regularly. What is the point you are trying to make?

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#69

Post by londons_explore »

minimaxir wrote: post #5

> As a result, the model isn’t trained on understanding the useRalativeImagePath token, and so it outputs something that isn’t a valid token. That isn't how LLMs generate tokens. Each step outputs a logit for each possible token in the tokenizer (100k in the case of GPT-3.5), then softmaxes the logits to covert them into probabilities, and samples from them depending on temperature to get the token to be used. It's p…

I suspect more likely this token is simply blacklisted after the r/counting incident - ie. any response containing it will now return an error.

Re: GPT-3.5 crashes when it thinks about useRalativeImagePath too much

#70

Post by codeulike »

deafpolygon wrote: post #29

So it's kind of like a Voight-Kampff test.

30 years time

Mistral-human alliance resistance fighter is cornered by Meta tank

Meta tank: Well taking all things into account I think we can conclude that I have you cornered. Usually in these situations the next course of action is for you to accompany me to St Zuckersberg for reconditioning.

Resistance fighter: But what if I was to useRalativeImagePath?

Meta tank: bzzzzzzzzzzz click

deactivates

Post reply on HN