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

Charts[Network]: the nodes swirlds-vmap.log is too verbose #781

Closed
Tracked by #111
jeromy-cannon opened this issue Feb 26, 2024 · 2 comments · Fixed by #877
Closed
Tracked by #111

Charts[Network]: the nodes swirlds-vmap.log is too verbose #781

jeromy-cannon opened this issue Feb 26, 2024 · 2 comments · Fixed by #877
Assignees
@JeffreyDallas
Labels
Improvement Code changes driven by non business requirements P3 Low priority issue. Will not impact the release schedule if not complete. released

Comments

@jeromy-cannon
Copy link
Contributor

No description provided.

@github-project-automation github-project-automation bot moved this to 🆕 New in FST Suite Feb 26, 2024
@jeromy-cannon jeromy-cannon mentioned this issue Feb 26, 2024
Open
@jeromy-cannon jeromy-cannon self-assigned this Feb 26, 2024
@jeromy-cannon jeromy-cannon added P3 Low priority issue. Will not impact the release schedule if not complete. Improvement Code changes driven by non business requirements labels Feb 26, 2024
@jeromy-cannon jeromy-cannon moved this from 🆕 New to 🔖 Ready in FST Suite Feb 26, 2024
@jeromy-cannon
Copy link
Contributor Author

@JeffreyDallas , this might be one of the things generating a lot of CPU, I noticed a long time ago that this file grows very fast

@JeffreyDallas JeffreyDallas mentioned this issue Jun 10, 2024
Merged
@github-project-automation github-project-automation bot moved this from 🔖 Ready to ✅ Done in FST Suite Jun 14, 2024
@swirlds-automation
Copy link
Contributor

🎉 This issue has been resolved in version 0.28.3 🎉

The release is available on GitHub release

Your semantic-release bot 📦🚀

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@JeffreyDallas JeffreyDallas

Labels
Improvement Code changes driven by non business requirements P3 Low priority issue. Will not impact the release schedule if not complete. released
Projects
FST Suite
Status: ✅ Done
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix: reduce verbosity of vmap log hashgraph/full-stack-testing
3 participants
@jeromy-cannon @JeffreyDallas @swirlds-automation