-
Notifications
You must be signed in to change notification settings - Fork 51
Issues: flux-framework/flux-core
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
kvs/content: checkpoint should not overwrite current checkpointed reference
#6629
opened Feb 12, 2025 by
chu11
1000 elcap nodes are shown as "lost connection" on rank 0 but compute node thinks it is still connected
#6626
opened Feb 11, 2025 by
garlick
Issue: flux resource status is incorrectly merging drain messages with specific field formatting options
#6625
opened Feb 11, 2025 by
kkier
can we run prolog/epilog/housekeeping in the flux systemd instance?
#6619
opened Feb 10, 2025 by
garlick
flux-config-exec(5) does not contain much detail about the kill timer
#6606
opened Feb 5, 2025 by
garlick
Suggestion: add the ability to enter an "undrain" message when undraining nodes
#6599
opened Feb 3, 2025 by
kkier
after an emergency restart, flux doesn't know about user processes that are still running
#6590
opened Jan 30, 2025 by
garlick
design: consider partitions as a separate abstraction from queues
#6567
opened Jan 21, 2025 by
garlick
Previous Next
ProTip!
Add no:assignee to see everything that’s not assigned.