You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Files generated/modified by update_vocabs.py are tracked by git, which is necessary when running the pipelines but gets confusing when working locally.
The text was updated successfully, but these errors were encountered:
@rob-metalinkage, I have added an output directory argument to the script. We can now run it locally like this:
python -m ogc.na update_vocabs.py -o build <rest of args>
and all new files (validation outputs, entailed files) will be put under that build subdirectory, recreating the path structure from the working directory (e.g., definitions/x/y.ttl is entailed into build/definitions/x/entailed/y.ttl). We could also use an external directory (like /tmp/build).
When running from the pipe, we just leave the output directory option out, and it works like it always has.
We could also create a simple cleanup.py script that finds all entailed and
validation results files and undoes the changes (using git checkout / git
clean / rm)...
--
Enviado desde mi teléfono.
El 20 de octubre de 2022 16:10:01 Rob Atkinson ***@***.***>
escribió:
Good idea.. we can revisit if we need to test redirection to these
locally... but that is a bigger issue to consider.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you were assigned.Message ID:
***@***.***>
Files generated/modified by
update_vocabs.py
are tracked by git, which is necessary when running the pipelines but gets confusing when working locally.The text was updated successfully, but these errors were encountered: