Assets incorrectly has supply=0 meaning that assets available in DB cannot be found via API about digital-asset-rpc-infrastructure HOT 6 CLOSED

OK, I think I see what's going on here:

let asset = scopes::asset::get_by_id(db, id, false).await?;

since include_no_supply: bool, is set to false then the asset gets filtered by the das api frontend:

    if !include_no_supply {
        asset_data = asset_data.filter(Condition::all().add(asset::Column::Supply.gt(0)));
    }
    ```

from digital-asset-rpc-infrastructure.

For some reason these assets have supply set to 0 after ingestion into the DB.

from digital-asset-rpc-infrastructure.

Look for flawed error handling where errors are silently swallowed, and a default value is set to zero.

from digital-asset-rpc-infrastructure.

It seems like there might be an issue with the API not being able to find the assets in the database. One possible reason could be that the assets were not properly indexed in the API's database.

To troubleshoot this issue, you can try the following steps:

1. Check if the assets are present in the API's database by querying the database directly. You can use a database client like pgAdmin to connect to the database and run a query to check if the assets are present.

2. If the assets are present in the database, then there might be an issue with the API's indexing. You can try re-indexing the assets by running a script that updates the API's database with the latest data from the blockchain.

3. If the assets are not present in the database, then there might be an issue with the data pipeline that feeds data into the API's database. You can check the logs of the data pipeline to see if there are any errors or issues that might be causing the assets to not be properly indexed.

I hope this helps! Let me know if you have any further questions.

from digital-asset-rpc-infrastructure.

Yeah we added this filter to eliminate burned nfts.
This could be where the metadata shows up and they mint in a instruction or transaction later and somehow that's missed by the token account query to update the supply of the nft

from digital-asset-rpc-infrastructure.

This looks like it was fixed already by patch submitted.

from digital-asset-rpc-infrastructure.