-
Notifications
You must be signed in to change notification settings - Fork 6
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
Unhandled characters in build info args #17
Comments
even if i try avoid getting panicked, another error comes up |
Hey there, I've implemented a fix for |
Hello, first of all thanks for the fast response, you are right after fixing the first error now i get a different one |
No problem, if you don't mind reporting on any missing build info arg support in here, then I'll do what I can to get them implemented. I have added support for the |
sure, gotta catch them all i guess? |
OK that should be fixed in commit 01ac679. |
ok, next one |
OK that one should be fixed with commit 86a5d79. |
next |
That's a strange one because it doesn't seem to follow the documentation of the I've made a change that includes the build info args when an unexpected character is encountered in commit 2ff0ba3. Could you include the entire new error message so that I can verify the context and ensure it's not a parsing error? |
the full error is like the others
edit: i think you meant for me to parse the error after the latest commit? unfortunately doing so prints a huge list of sensitive strings i would avoid sending, is there an alternative? sorry about this |
I think your local copy might be out of date. Could you verify that your |
do you have telegram? i found the GR-3 issue i think |
Yes I do, my account is |
Hello, im getting a weird error, something about MultipleProcessSupport flag?
here is the log
Im running the script on ubuntu 22.04 and rustc 1.74.0
The text was updated successfully, but these errors were encountered: