You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
-------- Forwarded Message --------
Subject: Re: out of quota !
Date: Thu, 2 May 2024 10:29:30 +0200
From: Konstantin Androsov [email protected]
To: Stefano Belforte [email protected]
About the JSON API. Yes, I'm currently using "crab status --json" to parse the statuses of individual jobs. However, JSON doesn't contain the same amount of information as the full output: there is no status on scheduler, status on server, various warnings (that sometimes can be actionable), url to dashboard etc. For that reason, I am still parsing txt output... If all commands had a complete json interface it would be a big improvement.
The text was updated successfully, but these errors were encountered:
As Konstantin Androsov @kandrosov reported
-------- Forwarded Message --------
Subject: Re: out of quota !
Date: Thu, 2 May 2024 10:29:30 +0200
From: Konstantin Androsov [email protected]
To: Stefano Belforte [email protected]
About the JSON API. Yes, I'm currently using "crab status --json" to parse the statuses of individual jobs. However, JSON doesn't contain the same amount of information as the full output: there is no status on scheduler, status on server, various warnings (that sometimes can be actionable), url to dashboard etc. For that reason, I am still parsing txt output... If all commands had a complete json interface it would be a big improvement.
The text was updated successfully, but these errors were encountered: