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
I'm checking out this mxlint-cli because I also used linting at my previous job (another development environment) and I want to look what is possible here and what is not.
But I noticed a problem on large validation microflows, at a certain point the mx-lint process keeps hanging and produces no output anymore.
I then tried to find the reason why the process hangs by building the validation microflow piece by piece and run the mxlint-process in between changes.
The whole time it worked fine untill a certain point that I've added another validation-test and then I noticed that it took a whole while longer then before for the process to ended.
After then adding another validation-test the mxlint-process suddenly keeps hanging forever.
I aso noticed that, for this validation-microflow, a few msg like ' level=info msg="Loop detected; not traversing" are shown in cmd.
When does this type of msg gets produced? In this validation-microflow there are no loops? that is why I ask.
I don't know if I can easely check this myself or not or if I can provide the microflow with the problem so you can check?
regards
Didier
The text was updated successfully, but these errors were encountered:
We are aware of this "similar" issue. The logic to convert a microflow is buggy. It would be great if you can reproduce the issue with an example .mpk (project export).
Hi,
I'm checking out this mxlint-cli because I also used linting at my previous job (another development environment) and I want to look what is possible here and what is not.
But I noticed a problem on large validation microflows, at a certain point the mx-lint process keeps hanging and produces no output anymore.
I then tried to find the reason why the process hangs by building the validation microflow piece by piece and run the mxlint-process in between changes.
The whole time it worked fine untill a certain point that I've added another validation-test and then I noticed that it took a whole while longer then before for the process to ended.
After then adding another validation-test the mxlint-process suddenly keeps hanging forever.
I aso noticed that, for this validation-microflow, a few msg like ' level=info msg="Loop detected; not traversing" are shown in cmd.
When does this type of msg gets produced? In this validation-microflow there are no loops? that is why I ask.
I don't know if I can easely check this myself or not or if I can provide the microflow with the problem so you can check?
regards
Didier
The text was updated successfully, but these errors were encountered: