Skip to content
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

Yaml rule parse error #5

Closed
GBrachetta opened this issue Jan 1, 2022 · 5 comments
Closed

Yaml rule parse error #5

GBrachetta opened this issue Jan 1, 2022 · 5 comments

Comments

@GBrachetta
Copy link

GBrachetta commented Jan 1, 2022

Hi, I don't want to be a pain in the ass, but just want your app to work, so I'm trying all combinations of folder creation, etc, and sometimes I get the following error. It happened in Monterey and now it's happening in Catalina.

I'm not sure if this tells you anything.

Screenshot 2022-01-01 at 15 37 24

In order to get rid of the error I have to delete the .heptapod folder and recreate it, and copy the rules again.

@tg44
Copy link
Owner

tg44 commented Jan 2, 2022

You are far from pain, you are the first "real" user :D It sometimes happens that what is working on some machines is not working on others. I'm also sorry that its not working as is, and I question a lot.

First of all, the stacktrace points to this line and tells that there is a nil error. This is really strange bcs I handle all the errors in this function.

I will push a new version in the next hour, which will give us the file we had the error, so at least we can go deeper.

@tg44 tg44 changed the title Random occasional error Yaml rule parse error Jan 2, 2022
tg44 added a commit that referenced this issue Jan 2, 2022
@GBrachetta
Copy link
Author

I have really zero idea of go language!

I don't even know how to reproduce the error 😊

Once I delete the folder .heptapod and recreate it with the rules, the error is gone.

The only thing I saw was some Stack Overflow posts about the error, but I apologize because I really don't know the language!

@tg44
Copy link
Owner

tg44 commented Jan 2, 2022

I'm not a pro either. If you get this error again, it will tell you exactly which file it is, and we can try to go deeper.

@GBrachetta
Copy link
Author

I'll keep an eye on this one. I really I don't know what I had to do for it to happen, only that it happened on both machines! 😊

@tg44
Copy link
Owner

tg44 commented Apr 29, 2024

I close this due inactivity.

@tg44 tg44 closed this as completed Apr 29, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants