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
The changes in #46 makes the plugin fail when Flow doesn't run. That is clearly an improvement. But the error message is not always accurate: it complains about 32 bit even when the cause is something else — for example, the glibc version being too low (Flow issue #49), or the FLOW_BIN variable pointing to a binary that doesn't exist.
As a solution I would propose changing the error message to say simply that the plugin was unable to run Flow. If the 32-bit error is very common it might still be mentioned as a possible cause.
If you agree I could try to prepare a PR for this change.
The text was updated successfully, but these errors were encountered:
The changes in #46 makes the plugin fail when Flow doesn't run. That is clearly an improvement. But the error message is not always accurate: it complains about 32 bit even when the cause is something else — for example, the glibc version being too low (Flow issue #49), or the
FLOW_BIN
variable pointing to a binary that doesn't exist.As a solution I would propose changing the error message to say simply that the plugin was unable to run Flow. If the 32-bit error is very common it might still be mentioned as a possible cause.
If you agree I could try to prepare a PR for this change.
The text was updated successfully, but these errors were encountered: