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/domain order #114

Merged
merged 13 commits into from
Sep 18, 2021
Merged

Fix/domain order #114

merged 13 commits into from
Sep 18, 2021

Conversation

PierreRust
Copy link
Collaborator

@PierreRust PierreRust commented May 17, 2021

This should fix #108 and ensure that all detected domains are displayed. Let me know what you think.

Before merging, I'm wondering why the 'package' domain is not handled as the other domains ? Is there any reason I'm missing ? I could try to change that but it would probably have an impact on all other exporters.

Besides, I have yet to check the Json exporter to check if the same fix is needed.

bpetit and others added 10 commits April 9, 2021 14:11
…rter' into feature/hubblo-org#75-shortcomings-of-current-json-exporter
…-shortcomings-of-current-json-exporter

Feature/hubblo-org#75 shortcomings of current json exporter
For all sockets in a topology.
Use a field, populated when adding a new socket.
This avoid rebuilding the list everytime we query it.
using the precomputed sorted domains list
@PierreRust PierreRust self-assigned this May 17, 2021
No need to rely on a array of names, the Domain object already has a
name field.
@PierreRust
Copy link
Collaborator Author

I've just added a fix for the json exporter, it was actually much simpler, we just needed to use the name field from the domain.

@wanecek
Copy link

wanecek commented May 17, 2021

I can confirm that this works on my computer, both for stdout and json exporters 👍

@PierreRust
Copy link
Collaborator Author

Great news, thanks for the feedback @wanecek !

@PierreRust PierreRust requested a review from bpetit May 18, 2021 06:44
@PierreRust PierreRust changed the title WIP: Fix/domain order Fix/domain order May 18, 2021
@bpetit bpetit added this to the Release v0.4.0 milestone Sep 11, 2021
Copy link
Contributor

@bpetit bpetit left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Seems good to me. Thanks a lot for that PR !

Before merging, I'm wondering why the 'package' domain is not handled as the other domains ? Is there any reason I'm missing ? I could try to change that but it would probably have an impact on all other exporters.

Do you mean why it was not contained in the static list you got rid of ?

For bad reasons I think, pkg is a domain that is seen on pretty new hardware afaik. I didn't get an occasion to get it in my tests yet.

I also think PR #97 is not needed anymore thanks to this one. Am I right or did I forget something ?

@bpetit bpetit linked an issue Sep 11, 2021 that may be closed by this pull request
@bpetit bpetit merged commit 8cbf410 into hubblo-org:main Sep 18, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Previous releases
Development

Successfully merging this pull request may close these issues.

Consistently reports 0 W for DRAM consumption Shortcomings of current json exporter
3 participants