- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Yesterday
Thu, Feb 25
Wed, Feb 24
Also wanted to second daniel's concern about running the migration while dagit is in use.
Another option is to ask users to connect to their cluster and manually run kubectl apply -f dagster-instance-migrate.yaml to create the migration job so that users aren't caught off guard? for example, some users may want to be extra safe and backup their database before migration in case something unexpected happens
Mon, Feb 22
Fri, Feb 19
Wed, Feb 17
a few comments; afterwards, good to go
Tue, Feb 16
Mon, Feb 15
Sat, Feb 13
Thu, Feb 11
the changes after the "accept" review were only to add the tests in helm.py that check that the label is correctly applied to the deployment
up
up
up
up
up
up
up
up
up
up
sent a snippet of user's code over Slack. yes, the flower env is different from the celery env in their case (also I think being maximally flexible for stuff like flower is preferable, so that we don't get in users' way)
up
added tests
up
up
up
up
rebase
sweet ✨
Tue, Feb 9
Looks good so far! Sending it back to your queue for "Add video thumbnails and move the resources center to dagster.io."
Sat, Feb 6
Fri, Feb 5
Wed, Feb 3
Fri, Jan 29
Jan 29 2021
will defer to ben or sashank on the code review. the demo for this looks amazing and can't wait till users get to benefit from it 💃
Jan 26 2021
feel free to merge after making one last formatting change
Awesome, looks great. one last change (and a missing .) and then it's good to ship
Jan 25 2021
Jan 24 2021
Jan 23 2021
requesting a few changes. next time, might be better to do this in a quip doc for faster iteration?
Jan 21 2021
Jan 20 2021
Jan 19 2021
Jan 17 2021
Jan 15 2021
Jan 14 2021
update license
rebase