Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

[HBAR Rate Limit Redesign] Improive logging logic for hbarLimit related classes #3025

Open
Tracked by #2739
quiet-node opened this issue Sep 21, 2024 · 0 comments · May be fixed by #3058
Open
Tracked by #2739

[HBAR Rate Limit Redesign] Improive logging logic for hbarLimit related classes #3025

quiet-node opened this issue Sep 21, 2024 · 0 comments · May be fixed by #3058
Assignees
@victor-yanev
Labels
enhancement New feature or request
Milestone
0.57.0

Comments

@quiet-node
Copy link
Member

Problem

Logging in the classes within the hbarLimiter repositories (e.g., EthAddressHbarSpendingPlanRepository, HbarSpendingPlanRepository, IPAddressHbarSpendingPlanRepository) appears to be duplicated and does not include a requestId. This makes it difficult to track logs during debugging.

Solution

Improve logging for HbarLimitter related classes

Alternatives

No response
@quiet-node quiet-node added the enhancement New feature or request label Sep 21, 2024
@quiet-node quiet-node added this to the 0.57.0 milestone Sep 21, 2024
@quiet-node quiet-node self-assigned this Sep 21, 2024
@quiet-node quiet-node mentioned this issue Sep 21, 2024
Open
@victor-yanev victor-yanev mentioned this issue Sep 21, 2024
Merged
2 tasks
@victor-yanev victor-yanev linked a pull request Oct 4, 2024 that will close this issue
Open
2 tasks
@victor-yanev victor-yanev linked a pull request Oct 4, 2024 that will close this issue
feat: implement configuration to pre-populate the cache with spending plans #3058
Open
2 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@victor-yanev victor-yanev

Labels
enhancement New feature or request
Projects
Smart Contract Sprint Board
Status: In Review
Milestone
0.57.0
2 participants
@quiet-node @victor-yanev