Errors while setting up on MacOS #6
Comments
|
Thank you for the bug report! Error 1 should be resolved in the new release. Binary naming issue; on Mac and Linux it is Regarding error 2, could you try running |
|
Sure |
TroubleshootingTerminal command Hypothesis
FixExplicitly define PATH environment. ce9bf04 Was unable to verify whether Mac OS stores binaries in $PATH/bin. @maxxar92 Does release 0.9.7 fix the problem? Alternative Hypothesis
Alternative Fixes
|
|
The new release does not fix it, same output as before. I tried a short rust program from my terminal (run with cargo run) that prints out |
|
Found this thread about a known bug + fix in the frontend framework on MacOS & Linux. The tricky part of the bug is that it even works in dev, but not after build. tauri-apps/tauri#4788 63dcb0e Also reverted the earlier attempted fix because the PATH env should already be available. "If program is not an absolute path, the PATH will be searched in an OS-defined way." & (https://doc.rust-lang.org/std/process/struct.Command.html#implementations) 8875e59 "I'm only able to run the executable with explicitly choosing to trust unidentified developer". I think this is related to code signing (similar to Microsoft Smartscreen warning): #7. It might have an impact on permissions too. |
|
Thank you, that seems to have solved it. Now the next issue appears at the start node command: |
|
We're getting closer to solving the problem! @maxxar92 Can you paste the permissions within the folder? I think these commands should work: Pre AnalysisThe problem seems to be that the Rust backend has no permission to execute a command using the edge binary. First off, based on the snippet above we can eliminate potential problems:
Furthermore, seeing It is possible to include binaries as part of a Tauri installation via a sidecar. Several users report Mac OS permission problems: Relative paths can be problematic on MacOS. rust-lang/rust#80537 is no problem either because the path is absolute. rust-lang/rust#80819 However, the Edge Staking GUI works different because it always wants to download the latest appropriate HypothesisOn MacOS, the downloaded Edge CLI has no executable permissions set for the file owner. FixAfter file is fully downloaded, explicitly set the file permissions. edge_staking_gui/src-tauri/src/utility.rs Line 124 in db0080f https://doc.rust-lang.org/std/fs/struct.Permissions.html#implementations Alternative Hypothesis
|
|
Sure: Seems no x bit is set, yup. After doing a chmod +x I can execute the ./edge binary in the folder |
|
That seems likely to be the problem. After chmod +x, can you also double check if the GUI can run the |
|
Yes, now it works 👍 |
|
Okay awesome, that seems to be the issue. Will prepare a fix. Let me know if you get to the next screen in the GUI. It should show status messages similar to: The screen looks like this: I would also be interested to hear if notifications work properly + the buttons |
|
The log and GUI look like that, yes 👍 I got a prompt about notifications from the program, that seems to have worked, I also got a notifications about that my node autostarted. One remaining issue I noticed is a second application icon (the black dot) appearing the top left corner (a weird position for mac), even when the program is minimized and another is focused such as: |
|
Seems like a transient issue though, it vanishes as soon as I switch desktop views |
|
Regarding the log & GUI, that's great. Attempted to create a permission fix as part of release 0.9.9. Don't have access to a Mac laptop so it feels like flying blind. You can test the fix by clicking the button |
|
In the log there should also be a new entry upon downloading the CLI: OR |
|
Also to clarify for a complete reset you don't need to create a new host stake. You can reassign an existing one. |
|
Technically it's possible to keep the data by setting |
|
@maxxar92 Hope the permission fix works upon a fresh setup. "One remaining issue I noticed is a second application icon (the black dot) appearing the top left corner (a weird position for mac), even when the program is minimized and another is focused such as". Hmmm that's an interesting bug. Opened up a separate issue for it. #8 |
|
Yes, the fresh setup works also, thank you |
|
Thanks for your help! |
There are two errors when trying to install on MacOS (14.1, running on Silicon M1 pro macbook).
Log messages say:
Log messages:
The text was updated successfully, but these errors were encountered: