You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Congratulations, @sheyman546! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @sheyman546: 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.
Moderator's reason: [Auto-assessed] The PR was merged by maintainer @Abd-Standard on 2026-10-05T14:32:51Z (as confirmed by the issue completion comment and mergedAt timestamp), and successfully addresses the rate-limit testing and load-testing workflow requirements requested in issue #852.
😎 @sheyman546: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.
Activity
sheyman546 commentedon Sep 28, 2026
@sheyman546 has applied to work on this issue as part of the Stellar Wave Program's 9th wave.
ℹ️ Repo Maintainers: To accept this application, review their application or assign @sheyman546 to this issue.
drips-wave commentedon Sep 29, 2026
Congratulations, @sheyman546! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on September 30, 2026.
🧑💻 @sheyman546: 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 🌊
test(listener): cover API rate limits under normal, burst and repeate…
grantfox-oss commentedon Oct 5, 2026
🎉 This issue has been marked as completed on GrantFox!
@sheyman546's PR #895 was approved and merged by @Abd-Standard.
🏆 @sheyman546: You earned 40 FoxPoints for this contribution! Your current tier: Builder (2,188 total points). Track your full progress on GrantFox.
👏 Great work, @sheyman546! Keep contributing to Core-Foundry.
drips-wave commentedon Oct 11, 2026
This issue has been marked as completed by a Drips Wave moderator for @sheyman546 as part of the Stellar Wave Program's 9th Wave 🥳
Moderator's reason: [Auto-assessed] The PR was merged by maintainer @Abd-Standard on 2026-10-05T14:32:51Z (as confirmed by the issue completion comment and mergedAt timestamp), and successfully addresses the rate-limit testing and load-testing workflow requirements requested in issue #852.
😎 @sheyman546: You earned 200 Points for completing this issue! Once the Wave's rewards are finalized, you'll be eligible for a percentage of the Wave's reward pool based on the percentage of total points you've earned. Learn more here.
🧑💻 Repo maintainers: How'd the contributor do? Leave a review to share your experience working with them.
ℹ️ Note: This issue was marked complete via moderation. Points were issued even though the GitHub issue remains open.