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
On the current master branch, the expected output from valhalla_export_edges appears to be combined with logs. As far as I can tell, the standard logging facility must be going to stdout, which causes the output to be mixed. It seems the workaround for now is probably to create a new config specifically for exporting edges with mjolnir.logging configured to output to a file.
Long-term fix ideas:
I would expect these to go to stderr, but I may be missing some reason why it's useful for these to go to stdout.
Alternately, we could have valhalla_export_edges require a file argument to which the contents will be written. I don't know all the history, but the major use case for this command (Pelias) consumes a file on disk.
Thoughts?
The text was updated successfully, but these errors were encountered:
it's a regression. we did a couple overhauls of all the executables and probably accidentally turned on logging for it when it wasn't on before. just need to patch it up to how it used to be
On the current master branch, the expected output from valhalla_export_edges appears to be combined with logs. As far as I can tell, the standard logging facility must be going to stdout, which causes the output to be mixed. It seems the workaround for now is probably to create a new config specifically for exporting edges with
mjolnir.logging
configured to output to a file.Long-term fix ideas:
Thoughts?
The text was updated successfully, but these errors were encountered: