Skip to content
#

workflow

Here are 2,339 public repositories matching this topic...

turbaszek
turbaszek commented Sep 1, 2020

Description

BigQueryToGCSOperator uses currently cursor from BigQueryHook and its method run_extract. Both are deprecated.

This operator should use insert_job method of BigQueryHook. This method requires job configuration as specified in
https://cloud.google.com/bigquery/docs/reference/rest/v2/Job#JobConfiguration. This operator should build extract configuration as a di

foobarbecue
foobarbecue commented Sep 1, 2020

Summary

UI always flashes "Pod did not output any logs." before showing logs.

This should actually say something like "Attempting to load logs." unless there is a way to determine definitively that there are actually no logs.

Diagnostics

2.10.0

shaunc
shaunc commented Aug 21, 2020

Hello!

I've found an issue here:In order to deploy your flow to Kubernetes the flow is required to have a Docker Storage with the image pushed to a registry that your Kubernetes cluster has access to.

Page reference: https://docs.prefect.io/orchestration/tutorial/k8s.html

Is it in fact true that a flow deployed to Kubernetes EKS can't use s3 storage? If so, an explicit affirmation of th

SuiteCRM
martinjaime
martinjaime commented Sep 14, 2017

Had the branch ancestry:

branch-1
  branch-2-bug-fix
    branch-3

All three branches had an open PR. branch-2-bug-fix‘s PR was a duplicate of a fix that someone else had already put in and merged at the same time. I closed the PR on branch-2-bug-fix and ran git town kill on that branch.

I was expecting it to change the base branch of branch-3‘s PR but instead it closed it

Improve this page

Add a description, image, and links to the workflow topic page so that developers can more easily learn about it.

Curate this topic

Add this topic to your repo

To associate your repository with the workflow topic, visit your repo's landing page and select "manage topics."

Learn more

You can’t perform that action at this time.