Shashwat Vangani

Updated from [pr3010.01](https://github.com/shaavan/rust-lightning/commits/pr3010.01) to [pr3010.02](https://github.com/shaavan/rust-lightning/commits/pr3010.02) ([diff](https://github.com/shaavan/rust-lightning/compare/pr3010.01..pr3010.02)): Changes: 1. Introduce `Readable impl for InvoiceRequest` 2. Restructure commits.

Updated from [pr3010.02](https://github.com/shaavan/rust-lightning/commits/pr3010.02) to [pr3010.03](https://github.com/shaavan/rust-lightning/commits/pr3010.03) ([diff](https://github.com/shaavan/rust-lightning/compare/pr3010.02..pr3010.03)): Updates: 1. Rebase on main, to resolve merge conflicts. 2. Fix ci

Updated from [pr3010.03](https://github.com/shaavan/rust-lightning/commits/pr3010.03) to [pr3010.04](https://github.com/shaavan/rust-lightning/commits/pr3010.04) ([diff](https://github.com/shaavan/rust-lightning/compare/pr3010.03..pr3010.04)): Changes: 1. Introduce retry_tick_occurred test.

Updated from [pr3010.04](https://github.com/shaavan/rust-lightning/commits/pr3010.04) to [pr3010.05](https://github.com/shaavan/rust-lightning/commits/pr3010.05) ([diff](https://github.com/shaavan/rust-lightning/compare/pr3010.04..pr3010.05)): Addressed @TheBlueMatt comments Updates: 1. Removed the secondary timer in ln_background_processor. 2. Moved the `retry_tick_occurred` to a private function, and renamed it to `retry_invoice_request_messages`....

Updated from [pr3010.05](https://github.com/shaavan/rust-lightning/commits/pr3010.05) to [pr3010.06](https://github.com/shaavan/rust-lightning/commits/pr3010.06) ([diff](https://github.com/shaavan/rust-lightning/compare/pr3010.05..pr3010.06)): Update: 1. Rebase on main. 2. To keep the code consistent with the main, now the `create_invoice_reqeust_message`, and `retry_invoice_request_messages` functions return `Result`

Updated from [pr3010.06](https://github.com/shaavan/rust-lightning/commits/pr3010.06) to [pr3010.07](https://github.com/shaavan/rust-lightning/commits/pr3010.07) ([diff](https://github.com/shaavan/rust-lightning/compare/pr3010.06..pr3010.07)): Update: 1. Replaced using `unsafe` with using internal `Mutex` variable for tracking call counts.

Updated from [pr3010.07](https://github.com/shaavan/rust-lightning/commits/pr3010.07) to [pr3010.08](https://github.com/shaavan/rust-lightning/commits/pr3010.08) ([diff](https://github.com/shaavan/rust-lightning/compare/pr3010.07..pr3010.08)): Changes: 1. Rebase on main, to solve merge conflicts.

Hi Matt! Thanks a lot for the suggestion! I think this will definitely be a more maintainable way to handle this change than introducing a counter! Worked out your suggestion...

Updated from [pr3010.08](https://github.com/shaavan/rust-lightning/commits/pr3010.08) to [pr3010.09](https://github.com/shaavan/rust-lightning/commits/pr3010.09) ([diff](https://github.com/shaavan/rust-lightning/compare/pr3010.08..pr3010.09)): Addressed @TheBlueMatt's comment **Update:** 1. Rebase on main 2. Introduced a new approach for retrying invoice request messages. **Details:** 1. This approach triggers `InvoiceRequest`...

Updated from [pr3010.09](https://github.com/shaavan/rust-lightning/commits/pr3010.09) to [pr3010.10](https://github.com/shaavan/rust-lightning/commits/pr3010.10) ([diff](https://github.com/shaavan/rust-lightning/compare/pr3010.09..pr3010.10)): Addressed @TheBlueMatt comments Changes: 1. Update function name from `retry_invoice_requests` -> `handle_message_received`, so that it's more explicit about its calling behavior than specific functionality....