Releases: textileio/powergate
v2.2.0
Changes
- Make lotus-devnet speed configurable for tests (#785)
- A new flag to indicate if the miner's index wants to be refreshed on Powergate start (default: false). (#784)
- Remove "Online" discovery for miners. This wasn't used and can add too much load. (#784)
- Re-enable location resolving for miners in the miner's metadata subindex. (#784)
- Include (Active/Live/Faulty) sector counts in miner's index, as to have a metric of sector counts of miners which is helpful to imagine their size and involvement in the network. (#784)
- Include the new index data in the indices API. (#784)
- For storage-deal records information, the deal information is always refreshed, not only when the deal becomes active. This can leave more useful data even if the deal fails. (#784)
- Bug fix regarding adding awareness of pending storage-deal records becoming final in the updated-at internal index. (#784)
- Removed CI workflows and dependabot referencing removed
developbranch. (#784) - Update Lotus client to v1.5.0. (#784)
- Update localnet to newly created v1.5.0. (#784)
- Reference newly created Lotus v1.5.0 docker-image. (#784)
- Update dependencies. (#784)
🙏 A big thank you to all the contributors to this release:
v2.1.0
NOTE: This release includes a migration. Please, make a backup of Powergate's database before the update.
Changes
- README: clarify that docker-compose should be installed to run localnet.
- Lotus: update localnet, docker image, and the client to Lotus v1.4.2
- README: clarify that by localnet run with BIGSECTOR enabled by default.
- API: Add Message CID to SendFilResponse.
- StorageConfig: Add
verifiedDealattribute to allow creating verified-deals. - Indices API: New APIs to fetch indices information about miners.
- Ask Index: Verified ask price is also registered, and added to the gateway.
- Improve deal records registration:
- Failed deals are now recorded, and not deleted in storage-deal records.
- Storage-deal records now register transfer and sealing start and ending timestamps.
- Retrieval records now register transfer start en ending timestamps.
- Records API: New APIs to fetch created/modified storage/retrieval records.
- Multiple internal improvements/fixes.
🙏 A big thank you to all the contributors to this release:
v2.1.0-rc2
fix bingo for go1.16 Signed-off-by: Ignacio Hagopian <[email protected]>
v2.0.0
This release includes lots of new features, and has breaking APIs. Please read the release notes carefully to prepare for the update. As always, it's recommended that you backup your Powergate datastore before the update since migrations will run; be safe.
Deal imports
Users can now call the existing API for applying a StorageConfig to a cid, with a new option to provide an array of deal ids. Powergate will import all the deal information and store it internally as if those deals were created by Powergate. After that moment, the user can continue to use Powergate as usual and do whatever they like with the newly stored deal information. If the user specifies that hot storage should be enabled with AllowUnfreeze = true, Powergate will run retrieval deals, if necessary, to get the underlying deal data from a miner and store it in IPFS hot storage.
New default miner selector
The new default miner-selector is reputation. Execute your own due diligence in setting --ffsminerselector to sr2 if you were using a remote-list intentionally.
New pow config apply options
A new --no-exec flag lets you apply a new StorageConfig without triggering a new job execution.
The flag --import-deals allows the importing of existing deal information as described in the section above.
These options are available to the Go client method Client.StorageConfig.Apply() using the new options WithNoExec and WithImportDealIDs.
StorageConfig.Hot.Ipfs.AddTimeout change
StorageConfig.Hot.Ipfs.AddTimeout is always considered as a timeout now. Before we used a fixed big timeout as a quick help in SpaceRace2 competition, since we didn't have the powcfg tool to make a massive change in all StorageConfigs easily. If that's your case, consider using powcfg.
Client API changes
Method name updates
A few client method names were renamed to avoid stuttering, for example Client.StorageInfo.StorageInfo(cid string) is now Client.StorageInfo.Get(cid string).
Simplified CidInfo
The Client.Data.CidInfo() method, accessed in the pow CLI as pow data info, now returns detailed information for only one cid (vs many cids previously) that is specified as an argument.
The data returned from CidInfo no longer contains LatestFinalJob and LatestSuccessfulJob fields.
StorageJobs API changes
The API for querying StorageJob data has been updated. Individual methods for getting queued, executing, and final storage jobs (Client.StorageJobs.Queued() and pow storage-jobs queued, for example) have been replaced with a single "list" method Client.StorageJobs.List()/pow storage-jobs list. This method takes query options that can be configured to change the query behavior and filter the results to jobs in the queued, executing or final states.
StorageJob.List() and pow storage-jobs list now support paging of results. By default, all data is retuned, but if a limit argument is provided, that number of results will be returned as a page of data along with a more field specifying if more pages of data exist and a nextPageToken that should be passed in the request for the next page of data.
We may consider enforcing a default limit on client calls in the future which will mean code using the client should be written to handle pages of data.
We may also add support for data paging to other API methods that have the potential to return lots of data.
Client API additions
Cid summary
There is a new method Client.Data.CidSummary(), pow data summary in the CLI, that provides a high level summary about the state of many or all cids in Powergate.
StorageInfo API
We Added a Client.StorageInfo, pow storage-info in the CLI, API for querying the current storage state of a cid in Powergate. This is strictly for data that is already stored and does not represent any information about storage operations that are pending or currently processing.
New dev tooling
powcfg
A new dev-tool powcfg provides all needed boilerplate to make massive StorageConfig transformations in an existing Powergate. It supports both Badger and MongoDB backing go-datastore usages.
migrtest
There is another new dev-tool, migrtest, that lets you test Powergate migrations safely before running them during the update process. Currently, it only supports targeting MongoDB go-datastores, but if you use badger and interested in having support, please file an issue.
Other updates
- Updated dependencies.
- Bugfixes and improvements.
v2.0.0-rc3
improving some api func names in the client (#756) Signed-off-by: Aaron Sutula <[email protected]>
v2.0.0-rc1
new labels for release drafter ++ (#752) * new tags for release drafter Signed-off-by: Aaron Sutula <[email protected]> * develop for release drafter Signed-off-by: Aaron Sutula <[email protected]> * v2 module Signed-off-by: Aaron Sutula <[email protected]>