You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the getBlock function, I will re-write the data even if the file already exists. We should make the data 'gold' (by checking it against the raw results from parity or geth) and then never write it again. To recast the data (i.e. changes its contents or format), one would have to delete the file explicitly
In a recent case, I had programmed getBlock incorrectly and was writing partial data to the file, thereby corrupting immutable data.
From In a recent case, I had programmed getBlock incorrectly and was writing partial data to the file, thereby corrupting immutable data.
In the getBlock function, I will re-write the data even if the file already exists. We should make the data 'gold' (by checking it against the raw results from parity or geth) and then never write it again. To recast the data (i.e. changes its contents or format), one would have to delete the file explicitly
In a recent case, I had programmed getBlock incorrectly and was writing partial data to the file, thereby corrupting immutable data.
From In a recent case, I had programmed getBlock incorrectly and was writing partial data to the file, thereby corrupting immutable data.
From https://github.com/Great-Hill-Corporation/ethslurp/issues/107
The text was updated successfully, but these errors were encountered: