Results 118 comments of Will Winder

I'm still seeing this issue from time to time. https://github.com/algorand/go-algorand/pull/1687

Thanks for the report, this appears to be a bug. For the `v2/accounts` endpoint we must only check whether or not the account has been deleted, but if an asset-id...

Sounds like this is no longer an issue with the current releases. Please reopen if it happens again.

@jeapostrophe as @brianolson mentioned it's best to consider indexer as "near-past". What are you trying to do, and what are your applications requirements for "near-past"? Is there an error in...

It looks like we can update to a slightly newer version, and the warning is removed: https://github.com/vektra/mockery/pull/456#issuecomment-1143766606

I think this is still an issue.

I believe the creator was removed from the holding object in algod when we uncapped the asset/application limit.

goal doesn't use the REST API yet, not until the release which is going out soon.

This suggestion makes sense to me. In the meantime, you can also use the closed_at field to identify whether the asset has been deleted.

This could be added to go-algorand as an PR integration te st. Start sandbox pointing at the PR branch and see if it's compatible with the sandbox dev branch.