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 a Mojo newbie and have just started working on it recently.
My project is located in an iCloud path, but the iCloud path contains white spaces, so Mojo can’t find the file.
Is there any method to resolve this issue without moving the project out of iCloud?
The root cause seems to be the folder named 'Mobile Documents'.
Even though I created a symbolic link for that path, the problem still persists.
❯ mojo main.mojo
sh: /Users/Giromi/Library/Mobile: No such file or directory
dlopen failed: dlopen(, 0x000A): tried: '' (no such file), '/System/Volumes/Preboot/Cryptexes/OS' (not a file), '/Users/Giromi/Library/Mobile
Documents/com~apple~CloudDocs/Repos/Giromi-archive/mojo/py_custom/.magic/envs/default/bin/../lib/' (not a file), '/usr/lib/' (not a file, not in
dyld cache), '' (no such file)
Please submit a bug report to https://github.com/modularml/mojo/issues and include the crash backtrace along with all the relevant source codes.
Stack dump:
0. Program arguments: mojo main.mojo
mojo crashed!
Please file a bug report.
[34387:51109714:20241231,101923.887722:WARNING in_range_cast.h:38] value -634136515 out of range
[34387:51109714:20241231,101923.892827:WARNING crash_report_exception_handler.cc:257] UniversalExceptionRaise: (os/kern) failure (5)
[1] 34385 trace trap mojo main.mojo
Bug description
I’m a Mojo newbie and have just started working on it recently.
My project is located in an iCloud path, but the iCloud path contains white spaces, so Mojo can’t find the file.
Is there any method to resolve this issue without moving the project out of iCloud?
The root cause seems to be the folder named 'Mobile Documents'.
Even though I created a symbolic link for that path, the problem still persists.
Steps to reproduce
System information
mojo -v
magic -V
ormagic --version
magic info
.The text was updated successfully, but these errors were encountered: