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.

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

Fix the issue of not refreshing the token expiration time when reconnecting #394

Merged
merged 1 commit into from
Oct 30, 2024

Conversation

mstmdev
Copy link
Member

@mstmdev mstmdev commented Oct 30, 2024

Fixes #393

@mstmdev mstmdev added this to the v0.9.0 milestone Oct 30, 2024
@mstmdev mstmdev added the bug Something isn't working label Oct 30, 2024
Copy link

codecov bot commented Oct 30, 2024

Codecov Report

Attention: Patch coverage is 38.88889% with 11 lines in your changes missing coverage. Please review.

Project coverage is 31.45%. Comparing base (f3aff20) to head (aabd481).
Report is 1 commits behind head on main.

Files with missing lines Patch % Lines
monitor/remote_client_monitor.go 0.00% 8 Missing ⚠️
api/apiclient/grpc_client.go 70.00% 3 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main     #394      +/-   ##
==========================================
- Coverage   31.48%   31.45%   -0.04%     
==========================================
  Files         134      134              
  Lines        7266     7274       +8     
==========================================
  Hits         2288     2288              
- Misses       4884     4892       +8     
  Partials       94       94              

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

@mstmdev mstmdev merged commit 4ad495e into no-src:main Oct 30, 2024
13 checks passed
@mstmdev mstmdev deleted the fix-393 branch October 30, 2024 02:50
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

Successfully merging this pull request may close these issues.

The logs grow very quickly, causing the hard drive to fill up
1 participant