Exception: EOF while parsing a value at line 1 column 0 about anthropic-sdk-python

[moelllerniklas]

I'm experiencing the same right now.

[Kolufs]

Same.

[sergeyf]

A temporary work-around is to set disable_checks=True in the completion call:

import anthropic

anthropic_client = anthropic.Client(api_key=...)

prompt = '\n\nHuman: This is a chat between me and you\n\nAssistant:'

resp = anthropic_client.completion(
    prompt=prompt,
    stop_sequences=[anthropic.HUMAN_PROMPT],
    model="claude-instant-v1",
    max_tokens_to_sample=200,
    disable_checks=True,
)

[mikelambert]

It appears like you are having a problem parsing the AWS bucket file. Are you able to share the results of the following when run on the same box as the failing code above?

curl https://public-json-tokenization-0d8763e8-0d7e-441b-a1e2-1c73b8e79dc3.storage.googleapis.com/claude-v1-tokenization.json | cut -b1-100

[sergeyf]

Sure:

{"version":"1.0","truncation":null,"padding":null,"added_tokens":[{"id":0,"special":true,"content":"

[sergeyf]

OK I think the issue is fixed, but many others might have issues still.

Here's what happened. The tokenizer JSON file you linked to was just a file with an AWS error when I looked at it last week. Today, it's a valid JSON. However, I was still getting errors this morning because the previous JSON was cached locally. I found it via https://github.com/anthropics/anthropic-sdk-python/blob/main/anthropic/tokenizer.py#L12 and it was an empty file.

To fix, I deleted it and everything started working again, but anyone who cached the broken JSON will need to delete it...

For others who find this, here is a set of instructions:

Open a python console and type in:

import tempfile
import os

print(os.path.join(tempfile.gettempdir(), "anthropic"))

Then go to that directory delete the tokenizer JSON.

I'll leave this ticket open.

[mikelambert]

Thanks for the diagnosis, didn't realize you were getting an AWS error earlier last week (thought it just broke yesterday!). Yes, agreed the cache file might be busted, and your solution will work. I'm going to bump the tempfile name in the next release, so upgrading will just fix it.

[mikelambert]

#16 should hopefully fix this issue from a few different angles (fail-open, change cache filename, blow away cache if it's busted)

[sergeyf]

Thanks! Feel free to close as you see fit.