Erik A. Brandstadmoen

Hi, @kimjamia . I understand this can be a bit confusing. I intended to hide the logs for the internal migrations/bootstrapping. As part of #482 , I've started using grate...

Thanks for chiming in, @DonalLOConnor ! To help me understand better, could you please give me some details about how you run grate? Is it the normal command-line version? Or...

Thanks a lot for this output, @DonalLOConnor ! ## Explanation This output is, although a bit confusing, actually just as expected. For grate 1.7+, I run some internal grate migrations...

@kimjamia, thank you. This makes perfect sense, and this is as expected (even though you shouldn't be exposed to it, as I planned to turn the logging off, which will...

Aha, @DonalLOConnor - that explains it. Great to hear you were able to solve your particular issue too! Shell escaping in Azure Devops tasks are a pain. I've experienced just...

@kimjamia - thanks a lot for you simple repro. That helped me a lot being able to understand what happened. Given my explanation, do you still think we have a...

Closing this, as I think we solved it, and I'm getting no more feedback.

Hi, @thallesnoce! Thanks for your input. I haven't used the `--isuptodate` option with RoundhousE, but just to double-check, the request is for grate to output text similar to the following,...

Yes it is, @Tsingis . I created a new, related issue: #582

The issue is that the base tables migration is always run in baseline mode (i.e. always registered as run), if the scriptsrun, scriptsrunerrors and version tables already exist (which they...