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
This is a bug report for the wlinknet upgrade branch of the main repo. It occurs on that branch.
This is an issue which was on the old node as well, currently the master branch. The issue has not been fixed in the upgrade yet.
The Wlinknet upgrade solves the major issue with the CLI wallet involving remote sends, which is great :) This means that people can send using ./bin/cli without running a local server. However, users are still likely to complain about the random segfaults.
No specific input triggers the segfault during ./bin/cli
To replicate the issue, just try running './bin/cli --local' a few times for extended periods of time
The issue does not prevent sends if you enter your information fast enough.
I think this is worth fixing, as other users have complained about this in the past.
The text was updated successfully, but these errors were encountered:
This is a bug report for the wlinknet upgrade branch of the main repo. It occurs on that branch.
This is an issue which was on the old node as well, currently the master branch. The issue has not been fixed in the upgrade yet.
The Wlinknet upgrade solves the major issue with the CLI wallet involving remote sends, which is great :) This means that people can send using ./bin/cli without running a local server. However, users are still likely to complain about the random segfaults.
No specific input triggers the segfault during ./bin/cli
To replicate the issue, just try running './bin/cli --local' a few times for extended periods of time
The issue does not prevent sends if you enter your information fast enough.
I think this is worth fixing, as other users have complained about this in the past.
The text was updated successfully, but these errors were encountered: