CAR Inline Example currently not working about atproto HOT 5 CLOSED

Thanks for your quick reaction, especially since the release 1.0.0 is still further up on the road...

It looks like it might be:

client.me.did possibly returns a DID that's no longer valid for get_repo

Will you be able to fix this on the python side to get back to the previous behavior, or will the coding just get more complicated for users of your python wrapper?

(I assume the issue won't simply disappear when they have fiished the roll-out, or will it?)

Cheers
Harald

from atproto.

You receive the server side error. Python SDK works properly and show this error as expected. To be honest I don't know why server returns this error for you. Perhaps your account has not been migrated yet or something. Try to login to the official bsky app. Also, maybe you are using the deprecated server method. Double-check if there is another way to get a repo

I'll try to run this example with my account later

from atproto.

Hello, maybe this is related bluesky-social/atproto#1832

from atproto.

True, the SDK's get_repo just gives the server side error. Using indigo you'll get the same error, as indeed @ericvolp12 with his Bluesky Walker can't do but write this error message into the CAR file for download.

Getting a repo essentially works without login. I can look for the DID elsewhere, say my_did, and just use
repo = client.com.atproto.sync.get_repo({'did': my_did}) without using client.login('my-handle', 'my-password') at all.

So I already tested with a handful of DIDs, and it's been the same error. It seems to be related with what @strideynet describes here.

Most probably it concerns all accounts that have been migrated already.

The official app doesn't have the option to DL (archive) the repo, and all programmatical ways I know of - indigo, dart api, Python SDK - seem to have the same problems.

I fear it can only be fixed by bluesky-social, and they probably have different priorities... :(

from atproto.

Repos have been moved to new PDSs and don't all live on bsky.social anymore. You should be checking a user's DID doc to figure out which PDS is hosting their repo and then downloading it from there using the getRepo endpoint or you can download it from the Relay service at bsky.network which stores a mirror of all repos. Since migrating users to new PDSs, some users have repos with bad signatures that will be fixed the next time they create a record, so the Relay service may not provide the repo for those users while their PDS will still work for getRepo. See https://atproto.com/blog/repo-export#on-another-instance

from atproto.