yyforyongyu 7cf28773bf multi: export channel status field in migration25 ... Previously, in `migration25.OpenChannel`, there was a private field `chanStatus` used to keep track of the channel status. The following migrations, `migration26` and `migration27` also have their own `OpenChannel` defined, with `migration26` inherited from `migration25`, and `migration27` inherited from `migration26`. The private field `chanStatus`, however, is NOT inherited and each of the migrations uses its own. This is fine for reading and writing as, under the hood, the `chanStatus` is just a `uint8` value. Because each migration has its own fetcher and putter, it can safely access its private field to read and write it correctly. The issue pops up when we use the method `migration25.FundingTxPresent()`. Because it's evaluating its channel status using its own private field `chanStatus`, this field would always be the default value(`ChanStatusDefault`), leading the statement `!c.hasChanStatus(ChanStatusRestored)` to always be true. Thus a restored channel will be mistakenly considered to have funding tx present, causing failures in reading the channel info in the following migrations. We fix this by exporting the `ChanStatus` field so its value can be set by following migrations.		2022-05-23 03:55:00 +08:00
..
channel.go	multi: export channel status field in migration25	2022-05-23 03:55:00 +08:00
log.go	channeldb+migration: add migration to save the initial balances	2022-04-20 01:18:12 +08:00
migration_test.go	migration25: export methods to be used for following migrations	2022-05-19 03:34:13 +08:00
migration.go	migration25: export methods to be used for following migrations	2022-05-19 03:34:13 +08:00