Dylan Bienstock

06/09/2021, 6:01 PM
Hi everyone, I was using the following example to get the run status of a pipeline run using the graphQL and ran into a couple issues. For one, when i wrote the following pipeline to get the status from a run ID it failed the dagster type check (returning a string instead of a PipelineRunStatus) I dug a little deeper and found that printing up the PipelineRunStatus.Success also just echoed it, instead of returning the string result. It seems to me there is inconsistency between the clients return and the PipelineRunStatus object unless this is intentional I was able to get the matching string by using PipelineRunStatus.SUCCESS.value, but this doesn't line up with the docs. Also I am using dagster v0.11.12


06/09/2021, 6:11 PM
cc @sid ya looks like a bug we don’t parse the string in to the enum like the mypy typehint says we were going to


06/09/2021, 6:32 PM
You’re totally right, oops! Will put up a patch for this & it should be included in 0.11.13. Apologize for any inconvenience Dylan, and thanks for bringing this up!
❤️ 1
What were the other issues you ran into with the GraphQL client? Would love to help troubleshoot / fix them!

Dylan Bienstock

06/09/2021, 6:37 PM
Awesome. No inconvenience at all! When I mentioned "a couple issues" I was only referencing my confusion with the run status. On that note, do you have an plans to expand the graphQL resource? I am mostly interested if there might be added capability to get a pipeline run object from a run id using the graphQL. (I was able to do so using the context.instance.get_runs() and filter to the id but this seemed a little clunky) 🙂


06/09/2021, 9:16 PM
hey @Dylan Bienstock - feel free to file an issue for feature requests you’re looking for in the graphql client
👍 1