Repository navigation
Fix lock TTL mismatch between test and implementation #517
Description
Activity
@Fatima0105 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
pls I would like to work on this issue
ℹ️ Repo Maintainers: To accept this application, review their application or assign @Fatima0105 to this issue.
@somotochukwu-dev has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
Hi
Please assign this issue to me
Thanksℹ️ Repo Maintainers: To accept this application, review their application or assign @somotochukwu-dev to this issue.
@PrimeFactor-Dev has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
I would love to work on this issue.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @PrimeFactor-Dev to this issue.
Congratulations, @PrimeFactor-Dev! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @PrimeFactor-Dev: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.
Warning
When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.
🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.
🌊 Happy Wave 🌊
- added a commit that references this issue
on Oct 2, 2026 🎉 This issue has been marked as completed on GrantFox!
@PrimeFactor-Dev's PR #550 was approved and merged by @DeFiVC.
🏆 @PrimeFactor-Dev: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (551 total points). Track your full progress on GrantFox.
👏 Great work, @PrimeFactor-Dev! Keep contributing to ChainLearnOfficial.
Bug Description
The
withLockutility insrc/utils/lock.tsuses a lock TTL of 60000ms (60 seconds) instead of the expected 30000ms (30 seconds) based on the test expectations.Location
tests/unit/utils/lock.test.tsline 39The Problem
The test was written expecting a 30-second lock TTL, but the implementation uses 60 seconds. This could indicate:
Impact
Acceptance Criteria
Severity
low - Test assertion mismatch. The 60-second TTL may be intentional for preventing race conditions in Stellar transactions.