-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] Is there any problem when running on “root“ ? #81
Comments
Thanks for the feedback! We'll try to troubleshoot... |
Zeyi-Lin
changed the title
🐛 [BUG] Is there any problem when running on “root“ ?
[BUG] Is there any problem when running on “root“ ?
Jan 6, 2024
@SAKURA-CAT Has the issue been resolved in v0.1.3? |
the milestone is v0.2.0, at present, there are still some problems to be solved. |
SAKURA-CAT
added a commit
that referenced
this issue
Jan 23, 2024
- [x] Users can turn on the service even if runs.swanlab does not exist. - [x] version update, and limit - [x] UI adjust - [x] Close #205 - [x] Close #81 - [x] ... --------- Co-authored-by: Zirui Cai <74649535+Feudalman@users.noreply.github.com> Co-authored-by: Ze-Yi LIN <58305964+xiaolin199912@users.noreply.github.com> Co-authored-by: ZeYi Lin <944270057@qq.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When I am running the ·swanlab watch· on a remote machine, and found the below bug.
It there the problem caused by running on "root" authority?
Waiting to fix it! 😀
The text was updated successfully, but these errors were encountered: