-
Notifications
You must be signed in to change notification settings - Fork 63
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
Is the project still maintained? #109
Comments
cc @marler8997 |
Looks dead. I wonder if there is another fork that is actively maintained |
I'm still using zigup everyday. There's still things to improve on. Possibly PRs that I've forgotten about and issues that should get addressed. Feel free to comment on the issues you'd like to see fixed and I'll see it and take that into account as we go. |
I can't use the tool because of this #93 |
I was unable to reproduce #93 on my own hardware. @OlshaMB could you reply on that thread with how you reproduced it, what hardware you're using, what version of zigup you're using (downloaded or built yourself). Also if you could build a debug version of zigup youreself and reproduce it then we could get a stack trace and maybe I can fix it without having the same hardware. |
I tried to trace the error but i don't now from where the error NotLink is coming from. I am using a MacBook Pro 16 M1 Max. |
I can't build zigup, which version of zig should I use? |
0.11.0 should work. Since it doesn't it seems like we now have a couple problems on your system. I'd like to see if we can get these fixed, if you like you can ping me on discord and we can start a chat or hop on a call and see if we can get these things fixed. I think #93 is a simple fix but I'd like to verify the fix works before we push a change. For discord just ping me ("marler8997") in the zig discord in whatever channel makes sense. |
zigup is maintained, so i am closing the issue |
There was no activity for a 4 months and issues are not fixed. So I am asking the question is the project still maintained?
The text was updated successfully, but these errors were encountered: