Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
feat: fix tari pulse running as fast as possible (#6704)
Description --- ~- Solve openssl build issue for non-base nodes by moving the Tari pulse service to the base node application~ - Fixed Tari pulse not adhering to the tick intervals Motivation and Context --- ~- Openssl cause build issues for other platforms~ - Tari puls were running _as fast as possible_, instead of adhering to the tick intervals ``` 2024-11-27 10:31:41.834109900 [c::bn::tari_pulse] INFO Initializing Tari Pulse Service 2024-11-27 10:31:41.834119800 [c::bn::tari_pulse] INFO Tari Pulse Service initialized 2024-11-27 10:31:41.994249400 [c::bn::tari_pulse] INFO Tari Pulse Service initialized with DNS name: checkpoints-nextnet.tari.com 2024-11-27 10:31:41.995570900 [c::bn::tari_pulse] TRACE Interval tick: 1 2024-11-27 10:31:42.093937500 [c::bn::tari_pulse] TRACE Passed checkpoints: true, DNS: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa), Local: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa) 2024-11-27 10:31:42.099942200 [c::bn::tari_pulse] TRACE Interval tick: 2 2024-11-27 10:31:42.151937500 [c::bn::tari_pulse] TRACE Passed checkpoints: true, DNS: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa), Local: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa) 2024-11-27 10:31:42.162359500 [c::bn::tari_pulse] TRACE Interval tick: 3 2024-11-27 10:31:42.553671300 [c::bn::tari_pulse] TRACE Passed checkpoints: true, DNS: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa), Local: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa) 2024-11-27 10:31:42.568889200 [c::bn::tari_pulse] TRACE Interval tick: 4 2024-11-27 10:31:42.622576100 [c::bn::tari_pulse] TRACE Passed checkpoints: true, DNS: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa), Local: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa) 2024-11-27 10:31:42.627371600 [c::bn::tari_pulse] TRACE Interval tick: 5 2024-11-27 10:31:42.870493900 [c::bn::tari_pulse] TRACE Passed checkpoints: true, DNS: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa), Local: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa) ``` - This PR: ``` 2024-11-27 11:51:08.123837900 [c::bn::tari_pulse] INFO Initializing Tari Pulse Service 2024-11-27 11:51:08.123852600 [c::bn::tari_pulse] INFO Tari Pulse Service initialized 2024-11-27 11:51:08.278346300 [c::bn::tari_pulse] INFO Tari Pulse Service initialized with DNS name: checkpoints-nextnet.tari.com 2024-11-27 11:51:08.279742100 [c::bn::tari_pulse] TRACE Interval tick: 1 2024-11-27 11:51:08.353759600 [c::bn::tari_pulse] TRACE Passed checkpoints: true, DNS: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa), Local: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa) 2024-11-27 11:53:08.297138300 [c::bn::tari_pulse] TRACE Interval tick: 2 2024-11-27 11:53:08.700206500 [c::bn::tari_pulse] TRACE Passed checkpoints: true, DNS: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa), Local: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa) 2024-11-27 11:55:08.303411400 [c::bn::tari_pulse] TRACE Interval tick: 3 2024-11-27 11:55:08.358827400 [c::bn::tari_pulse] TRACE Passed checkpoints: true, DNS: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa), Local: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa) 2024-11-27 11:57:08.311930500 [c::bn::tari_pulse] TRACE Interval tick: 4 2024-11-27 11:57:08.416916200 [c::bn::tari_pulse] TRACE Passed checkpoints: true, DNS: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa), Local: (45168, 1e3c56468f464072d9879e29a70891e9916f2206116c8819637c266a8b1d2efa) ``` How Has This Been Tested? --- System-level testing. ~**Note:** Build tests for other platforms must still be performed.~ What process can a PR reviewer use to test or verify this change? --- Code review. System-level testing. <!-- Checklist --> <!-- 1. Is the title of your PR in the form that would make nice release notes? The title, excluding the conventional commit tag, will be included exactly as is in the CHANGELOG, so please think about it carefully. --> Breaking Changes --- - [x] None - [ ] Requires data directory on base node to be deleted - [ ] Requires hard fork - [ ] Other - Please specify <!-- Does this include a breaking change? If so, include this line as a footer --> <!-- BREAKING CHANGE: Description what the user should do, e.g. delete a database, resync the chain -->
- Loading branch information