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
As you mentioned, the feature is not implemented.
I understand the need but still wondering how to implement it.
The point is that danger-periphery blocks IO while it is running because it uses Open3.capture3 internally.
However, I think that console log should be implemented in smarter way, like non-blocking IO that is constantly written while running Periphery.
Using other methods like Kernel#spawn may solve this problem. I'll try it later (and I'm welcome PRs as well).
Is there a way to make the utility output everything it prints to the console?
is it possible to run Periphery separately and feed its JSON output to danger-periphery instead?
Although both ways sound good to me, 2 would be simpler considering the above blocking problem 🤔
I'm running Periphery using the following Dangerfile script:
In the CI console, I only see:
It seems that no logs from Periphery itself are being shown. Is there a way to make the utility output everything it prints to the console?
Alternatively, is it possible to run Periphery separately and feed its JSON output to danger-periphery instead?
The text was updated successfully, but these errors were encountered: