-
Notifications
You must be signed in to change notification settings - Fork 419
Permalink
Choose a base ref
{{ refName }}
default
Choose a head ref
{{ refName }}
default
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
base repository: lightningdevkit/rust-lightning
Failed to load repositories. Confirm that selected base ref is valid, then try again.
Loading
base: d5bd25c
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
...
head repository: lightningdevkit/rust-lightning
Failed to load repositories. Confirm that selected head ref is valid, then try again.
Loading
compare: dc2b11f
Could not load branches
Nothing to show
Loading
Could not load tags
Nothing to show
{{ refName }}
default
Loading
- 11 commits
- 8 files changed
- 3 contributors
Commits on Mar 20, 2023
-
Drop
serde
dependency fromlightning-block-sync
`serde` doesn't bother with MSRVs, so its expected to break frequently. Yesterday, the `derive` feature had its MSRV broken in a patch version without care. Luckily its trivial for us to remove the `serde` dependency in `lightning-block-sync`, using only `serde_json` for the JSON deserialization part. It even ends up net-negative on LoC.
Configuration menu - View commit details
-
Copy full SHA for b701a6c - Browse repository at this point
Copy the full SHA b701a6cView commit details -
Merge pull request #2116 from TheBlueMatt/2023-03-serde-sucks
Drop `serde` dependency from `lightning-block-sync`
Configuration menu - View commit details
-
Copy full SHA for 86e94c4 - Browse repository at this point
Copy the full SHA 86e94c4View commit details -
Since we don't store `pending_claim_events` within `OnchainTxHandler` as they'll be regenerated on restarts, we opt to implement `PartialEq` manually such that the field is not longer considered.
Configuration menu - View commit details
-
Copy full SHA for cfa8941 - Browse repository at this point
Copy the full SHA cfa8941View commit details -
Configuration menu - View commit details
-
Copy full SHA for e7fb47b - Browse repository at this point
Copy the full SHA e7fb47bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 1958626 - Browse repository at this point
Copy the full SHA 1958626View commit details -
Configuration menu - View commit details
-
Copy full SHA for 7c446b4 - Browse repository at this point
Copy the full SHA 7c446b4View commit details -
Clarify OnchainEvent::Claim behavior
The previous documentation was slightly incorrect, a `Claim` can also be from the counterparty if they happened to claim the same exact set of outputs as a claiming transaction we generated.
Configuration menu - View commit details
-
Copy full SHA for 1638c8b - Browse repository at this point
Copy the full SHA 1638c8bView commit details -
Configuration menu - View commit details
-
Copy full SHA for 7b9c28a - Browse repository at this point
Copy the full SHA 7b9c28aView commit details -
Maintain order of yielded claim events
Since the claim events are stored internally within a HashMap, they will be yielded in a random order once dispatched. Claim events may be invalidated if a conflicting claim has confirmed on-chain and we need to generate a new claim event; the randomized order could result in the new claim event being handled prior to the previous. To maintain the order in which the claim events are generated, we track them in a Vec instead and ensure only one instance of a PackageId only ever exists within it. This would have certain performance implications, but since we're bounded by the total number of HTLCs in a commitment anyway, we're comfortable with taking the cost.
Configuration menu - View commit details
-
Copy full SHA for 4be56b9 - Browse repository at this point
Copy the full SHA 4be56b9View commit details -
Configuration menu - View commit details
-
Copy full SHA for 2cc48c5 - Browse repository at this point
Copy the full SHA 2cc48c5View commit details -
Configuration menu - View commit details
-
Copy full SHA for dc2b11f - Browse repository at this point
Copy the full SHA dc2b11fView commit details
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff d5bd25c...dc2b11f