Daniel Reeves

Remote filesystem stuff keeps coming up in multiple contexts. And we already have support for this in, of all places, `cosmos/plugin/__init__.py` with the `open_file()` function. I think this function should...

This is small but a simple starting point would be to move to the LoggingMixin instead of a global logger. This would still be backwards compatible I believe, wouldn't change...

Big post incoming # Issue Users have been seeing duplicate logs and other logging related issues (see #639, #747. #906) for a while. In my experience, logging issues have gotten...

@gbatiz #1047 puts a bandaid on the issue. In addition to setting `cosmos.propagate_logs = False` in the config, you should be all set when the next alpha release of `1.5.0`...

If the feature here is to make it so when a user renders the DAG/Task Group they _only_ get test nodes (this is my understanding of the issue), I think...

@tatiana Oh my god I figured it out and it's kind of funny and unfortunate. Basically, the partial parse saves the location of the seed file. So if you use...

Actually let me think for a second about what the solution should be for the API. Setting the cwd as the AIRFLOW_HOME would be bad for users who run "cd...

In more positive news... this does confirm that I am successfully using the `partial_parse.msgpack` in Cosmos 1.4.0a 😉 Although it's a distressing way to figure out that it worked.

> @dwreeves would it make more sense for us to solve the problem when we generate the partial_parse.msgpack? How did you generate it? Sigh, it's harder than I was hoping...

1. An implementation note-- This would require running multiple dbt nodes in a single operator. This is feasible, but not a typical pattern in the Cosmos context. This makes the...