globus_gra..._job_state(3)

πŸ’– globus_gram_protocol_job_state β€” GRAM Job States πŸ’–

okay bestie, welcome to the Library Functions Manual ✨ this is the page for globus_gram_protocol_job_state, aka the GRAM Job States and it's literally just the whole vibe dictionary for "what is my job doing rn" πŸ’…


πŸŽ€ NAME πŸŽ€

globus_gram_protocol_job_state β€” GRAM Job States

  • GRAM Job States.

(yeah they said it twice, iconic of them, no notes 🫢)


✨ SYNOPSIS ✨

Enumerations

enum globus_gram_protocol_job_state_t {
    GLOBUS_GRAM_PROTOCOL_JOB_STATE_PENDING =1,
    GLOBUS_GRAM_PROTOCOL_JOB_STATE_ACTIVE =2,
    GLOBUS_GRAM_PROTOCOL_JOB_STATE_FAILED =4,
    GLOBUS_GRAM_PROTOCOL_JOB_STATE_DONE =8,
    GLOBUS_GRAM_PROTOCOL_JOB_STATE_SUSPENDED =16,
    GLOBUS_GRAM_PROTOCOL_JOB_STATE_UNSUBMITTED =32,
    GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_IN =64,
    GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_OUT =128,
    GLOBUS_GRAM_PROTOCOL_JOB_STATE_ALL =0xFFFFF }

🌸 DETAILED DESCRIPTION 🌸

GRAM Job States. periodt πŸ’…

so globus_gram_protocol_job_state_t is holding all the tea about the current state of the job as known by the job manager. every time the state changes, the Job Manager sends that update out to all registered clients β€” like a group chat notification but for your job's whole life πŸ¦‹

and a client can also just. ask. πŸ‘€ via the status request, if it wants the info on demand.


πŸ”₯ ENUMERATION TYPE DOCUMENTATION πŸ”₯

enum globus_gram_protocol_job_state_t

GRAM Job States

Enumerator

  • GLOBUS_GRAM_PROTOCOL_JOB_STATE_PENDING β€” the job is just sitting there waiting for resources to become available so it can actually run. it's giving "on read" energy 😭
  • GLOBUS_GRAM_PROTOCOL_JOB_STATE_ACTIVE β€” yay!! the job got its resources and the application is executing. main character moment, fr fr ✨
  • GLOBUS_GRAM_PROTOCOL_JOB_STATE_FAILED β€” the job terminated before completion because of an error, a user-triggered cancel, or a system-triggered cancel. rip πŸ’€
  • GLOBUS_GRAM_PROTOCOL_JOB_STATE_DONE β€” the job completed successfully. ate and left no crumbs πŸ‘‘
  • GLOBUS_GRAM_PROTOCOL_JOB_STATE_SUSPENDED β€” the job has been suspended. and heads up: resources that were allocated for this job may have been released due to some scheduler-specific reason. so like, don't assume they're still yours 🫢
  • GLOBUS_GRAM_PROTOCOL_JOB_STATE_UNSUBMITTED β€” the job has not been submitted to the scheduler yet, because it's waiting on the reception of the GLOBUS_GRAM_PROTOCOL_JOB_SIGNAL_COMMIT_REQUEST signal from a client. it's pending approval bestie, we don't move till we get the signal πŸ™ˆ
  • GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_IN β€” the job manager is staging in files to run the job. bringing the supplies in πŸ“¦βœ¨
  • GLOBUS_GRAM_PROTOCOL_JOB_STATE_STAGE_OUT β€” the job manager is staging out files generated by the job. cleaning up and carrying the results out πŸ§ΊπŸ’–
  • GLOBUS_GRAM_PROTOCOL_JOB_STATE_ALL β€” a mask of all job states. literally all of them, the whole squad 🌈

πŸ’œ AUTHOR πŸ’œ

Generated automatically by Doxygen for globus_gram_protocol from the source code. (not a human writing this, just doxygen doing its lil thing, and honestly? respect 🫑)


aaaand that's the page!! πŸŽ€ this was globus_gram_protocol Version 13.6 β€” tysm for reading, go check your job states, mwah πŸ’‹πŸ’–πŸ¦‹

πŸ“¦ where this page comes from