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

flux-topo:46: attempt to index field 'conf' (a nil value) #763

Closed
garlick opened this issue Aug 12, 2016 · 4 comments
Closed

flux-topo:46: attempt to index field 'conf' (a nil value) #763

garlick opened this issue Aug 12, 2016 · 4 comments
Assignees
Milestone

Comments

@garlick
Copy link
Member

garlick commented Aug 12, 2016

When the live module is not loaded (as is now the default), the flux-topo utility doesn't work, because it obtains the topology from the KVS, the result of a reduction that occurs each time the topology changes.

Since the topology is static when that KVS value is unavailable, the topology should probably be calculated on rank 0 and written to the KVS or elsewhere so flux-topo can work. Alternatively, it could simply handle the error more gracefully.

@garlick
Copy link
Member Author

garlick commented Dec 30, 2016

Let's just remove flux-topo as a subcommand for now (and update flux-up(1) and flux-topo(1)). Easy one if somebody wants to grab it.

@garlick garlick added this to the release 0.7.0 milestone Jan 4, 2017
@chu11 chu11 self-assigned this Jan 17, 2017
@chu11
Copy link
Member

chu11 commented Jan 18, 2017

@garlick Did you mean "remove flux-topo as a listed subcommand" or did you mean "remove remove" flux-topo? A bit confused by "update flux-up(1) and flux-topo(1)"??

@chu11
Copy link
Member

chu11 commented Jan 18, 2017

Oh, I should say a simple error check would output a nicer error message in flux-topo, so no need to "remove remove" it if that's what you were initially thinking.

@garlick
Copy link
Member Author

garlick commented Jan 18, 2017

Sorry I'm not sure what I meant there! Both flux-topo and flux-up are essentially no-ops with the live module not loaded. We should probably just remove them and their man pages, and any other refs in the docs. They can come back when we do something interesting with resiliency.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants