mirror of
https://github.com/lightningnetwork/lnd.git
synced 2024-11-19 18:10:34 +01:00
7cf28773bf
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. |
||
|---|---|---|
| .. | ||
| migration | ||
| migration12 | ||
| migration13 | ||
| migration16 | ||
| migration20 | ||
| migration21 | ||
| migration23 | ||
| migration24 | ||
| migration25 | ||
| migration26 | ||
| migration27 | ||
| migration_01_to_11 | ||
| migtest | ||
| addr_test.go | ||
| addr.go | ||
| channel_cache_test.go | ||
| channel_cache.go | ||
| channel_test.go | ||
| channel.go | ||
| codec.go | ||
| db_test.go | ||
| db.go | ||
| duplicate_payments.go | ||
| error.go | ||
| forwarding_log_test.go | ||
| forwarding_log.go | ||
| forwarding_package_test.go | ||
| forwarding_package.go | ||
| graph_cache_test.go | ||
| graph_cache.go | ||
| graph_test.go | ||
| graph.go | ||
| invoice_test.go | ||
| invoices.go | ||
| legacy_serialization.go | ||
| log.go | ||
| meta_test.go | ||
| meta.go | ||
| mp_payment_test.go | ||
| mp_payment.go | ||
| nodes_test.go | ||
| nodes.go | ||
| options_test.go | ||
| options.go | ||
| paginate.go | ||
| payment_control_test.go | ||
| payment_control.go | ||
| payments_test.go | ||
| payments.go | ||
| peers_test.go | ||
| peers.go | ||
| README.md | ||
| reject_cache_test.go | ||
| reject_cache.go | ||
| reports_test.go | ||
| reports.go | ||
| revocation_log_test.go | ||
| revocation_log.go | ||
| setup_test.go | ||
| waitingproof_test.go | ||
| waitingproof.go | ||
| witness_cache_test.go | ||
| witness_cache.go | ||
channeldb
The channeldb implements the persistent storage engine for lnd and
generically a data storage layer for the required state within the Lightning
Network. The backing storage engine is
boltdb, an embedded pure-go key-value store
based off of LMDB.
The package implements an object-oriented storage model with queries and mutations flowing through a particular object instance rather than the database itself. The storage implemented by the objects includes: open channels, past commitment revocation states, the channel graph which includes authenticated node and channel announcements, outgoing payments, and invoices
Installation and Updating
⛰ go get -u github.com/lightningnetwork/lnd/channeldb