Skip to content

feat: migrate TXM and AptosService config to duration types#406

Merged
Fletch153 merged 4 commits intodevelopfrom
PLEX-2598/turn-constants-into-config
Mar 26, 2026
Merged

feat: migrate TXM and AptosService config to duration types#406
Fletch153 merged 4 commits intodevelopfrom
PLEX-2598/turn-constants-into-config

Conversation

@Fletch153
Copy link
Contributor

Summary

  • Replace raw integer seconds (ConfirmPollSecs, SubmitDelayDuration, TxExpirationSecs, PruneIntervalSecs, PruneTxExpirationSecs) with config.Duration types using proper duration strings ('2s', '4h')
  • Add new [AptosService] TOML config section with SubmitPollTimeout and SubmitPollInterval to decouple CRE/workflow polling from TXM config
  • Remove stale TODO comments resolved by these changes

Test plan

  • Existing TXM config tests updated and passing with new duration types
  • New AptosService config section tested with custom values and defaults
  • Global default mutation guard extended to cover AptosService config
  • Integration test TOML templates updated — verify node startup
  • Manual verification with local devnet

🤖 Generated with Claude Code

…ptosService config section

Replace raw integer seconds (ConfirmPollSecs, SubmitDelayDuration, TxExpirationSecs,
PruneIntervalSecs, PruneTxExpirationSecs) with config.Duration types using proper
duration strings ('2s', '4h'). Add new AptosService config section with
SubmitPollTimeout and SubmitPollInterval to decouple CRE/workflow polling from TXM
config. Remove stale TODO comments resolved by these changes.
@Fletch153 Fletch153 requested a review from a team as a code owner March 24, 2026 16:50
@github-actions
Copy link
Contributor

👋 Fletch153, thanks for creating this pull request!

To help reviewers, please consider creating future PRs as drafts first. This allows you to self-review and make any final changes before notifying the team.

Once you're ready, you can mark it as "Ready for review" to request feedback. Thanks!

@Fletch153 Fletch153 force-pushed the PLEX-2598/turn-constants-into-config branch from de2836f to 6cf8abc Compare March 25, 2026 12:36
@Fletch153 Fletch153 force-pushed the PLEX-2598/turn-constants-into-config branch from 6cf8abc to f191bc2 Compare March 25, 2026 13:43
@Fletch153 Fletch153 requested review from a team as code owners March 25, 2026 13:43
@Fletch153 Fletch153 force-pushed the PLEX-2598/turn-constants-into-config branch from f191bc2 to 4f25f14 Compare March 25, 2026 13:49
@Fletch153 Fletch153 force-pushed the PLEX-2598/turn-constants-into-config branch from 4f25f14 to b48ecc0 Compare March 25, 2026 14:46
@Fletch153 Fletch153 force-pushed the PLEX-2598/turn-constants-into-config branch 5 times, most recently from f3cfcf6 to 432b712 Compare March 25, 2026 18:13
Add RPCConfig section with MaxConcurrentRequests and Timeout to replace
hardcoded rate limiter values in chain.go. Add SimulateTx boolean to
AptosServiceConfig. Add CacheTTL and CacheCleanupInterval to LogPoller
config to replace hardcoded cache constants.
@Fletch153 Fletch153 force-pushed the PLEX-2598/turn-constants-into-config branch from 432b712 to a48783c Compare March 25, 2026 18:14
…stants-into-config

# Conflicts:
#	relayer/txm/config.go
@yashnevatia
Copy link
Contributor

LGTM!
Ci failing (not sure if rerun will fix it or if its related)
Do we need a corresponding PR in core or common ?

NewLogPoller requires a non-nil config after a48783c added configurable
cache settings. Update 3 test callsites to pass DefaultConfigSet instead
of nil.

PLEX-2598
@Fletch153 Fletch153 force-pushed the PLEX-2598/turn-constants-into-config branch from 776e67f to 8c21414 Compare March 26, 2026 12:41
@Fletch153 Fletch153 deployed to integration March 26, 2026 12:41 — with GitHub Actions Active
@Fletch153 Fletch153 merged commit 6816c9d into develop Mar 26, 2026
21 checks passed
@Fletch153 Fletch153 deleted the PLEX-2598/turn-constants-into-config branch March 26, 2026 13:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants