The working directory of nodes with git fields is only decided on `dora
build` because that's where we translate the branch/tag name into the
commit hash.
Before, we fell back to using the base working directory if no build was
done. However, this is confusing since the reason for the different
working directory is not communicated in any.
This commit throws an error if no build happened before starting a
dataflow with git nodes.
The working directory of nodes with git fields is only decided on `dora build` because that's where we translate the branch/tag name into the commit hash.
Before, we fell back to using the base working directory if no build was done. However, this is confusing since the reason for the different working directory is not communicated in any.
This commit throws an error if no build happened before starting a dataflow with git nodes.
Most important change is https://github.com/GREsau/schemars/pull/310,
which keeps newlines unchanged during schema generation. This is
important to preserve the lists, markdown code blocks, and markdown
headings in our docs.
Note: This PR deliberately does not update the schema file yet in order
to test #1083. So it should be merged after #1083.
Most important change is https://github.com/GREsau/schemars/pull/310, which keeps newlines unchanged during schema generation. This is important to preserve the lists, markdown code blocks, and markdown headings in our docs.
- Buffer log messages that are sent before subscribers are connected
- Include working directory in 'running build command' message
- Lower log level of 'building' message to `Debug`
We forgot to create the working directory in a few cases in #901. This
PR fixes this by adding the proper `create_dir_all` calls.
Alternative to https://github.com/dora-rs/dora/pull/1064