Query: All Stories

	Include stories about projects I am a member of.

conn instead of provider

ideally we also wouldn't even watch the log files for external runs unless we had an active subscription on them

we could land this after a bit of cleanup - but i think im tempted to just have this feed in to a more systemic refactor of all this PipelineRun stuff.

Add mock to dagster-graphql dev requirements

(venv) root@ip-172-31-1-11:/# dagit
Traceback (most recent call last):
  File "/venv/lib/python3.5/site-packages/pkg_resources/__init__.py", line 635, in _build_master
    ws.require(__requires__)
  File "/venv/lib/python3.5/site-packages/pkg_resources/__init__.py", line 943, in require
    needed = self.resolve(parse_requirements(requirements))
  File "/venv/lib/python3.5/site-packages/pkg_resources/__init__.py", line 834, in resolve
    raise VersionConflict(dist, req).with_context(dependent_req)
pkg_resources.ContextualVersionConflict: (Flask 1.1.1 (/venv/lib/python3.5/site-packages), Requirement.parse('Flask<1.1.0,>=0.12.4'), {'dagit'})

Update releasing docs

Do we know what is actually breaking?

open and close connections every time

Remove use of kwargs in start and end schedule mutations

should put this somewhere other than bin?

looks pretty solid to me

Add bash script deletion check in test_start_and_end_schedule()

Mock $DAGSTER_HOME for test

Fix end_schedule, and remove hardcoded DAGSTER_HOME

[dagster-graphql] use obj for required resource

might be worth moving from init to a couple smaller files

Write to log file with filename {schedule name}_{schedule id}.log in the same directory as the bash script and metadata file

Mutations for start and end schedule, create TestSystemCronScheduler, and write tests for all new queries and mutations

It's a good question - I'm not sure if there's any good way to solve this, maybe @max has some thoughts since he was looking at the airflow <> flask stuff originally?

So will limit what versions of airflow we can integrate with? I’m a little hazy on how this all coheres to a flexible sane strategy around deps

This looks great to me. I'll let @max approve to resolve your question re: the use/non-use of raise_from.

fix airline demo snippet

adjust the dagstermill code snippets for the airline demo docs

yeah its definitely brittle. An alternative we've considered in the past is to just inline the code, but then the code samples are not tested. Definitely open to ideas if you've seen this done any other/better way

All Stories
Use Results
Edit Query
Hide Query

Today

Yesterday

Sat, Aug 17

Fri, Aug 16

Thu, Aug 15