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

Saving import template sometimes causes an error popup to show, and the app dies #117

Open
tonnydourado opened this issue Dec 28, 2023 · 3 comments

Comments

@tonnydourado
Copy link

Describe your Environment
OS: Windows 10
Paisa Version: 0.6.2
App Variant: Desktop

Describe the bug
Sometimes, when saving an import template, I get this error:

Paisa Error Screenshot 2023-12-28 233057

And then the app closes, usually loosing any edits in the template.

To Reproduce
Steps to reproduce the behavior: Not quite sure. Sometimes, I re-open the app and paste the exact same template, and click save, and it works.

Expected behavior
I would expect that syntax errors on an import template would not kill the app

Screenshots
Screenshot is in the description

Journal
I don't have any data in the journal.

@ananthakumaran
Copy link
Owner

@tonnydourado to give some context, the error is about a newly introduced config field called strict. Since the templates are stored in the config file, any update to the config file will trigger the validation and for some reason, strict field validation is failing. Could you look into paisa.yaml and check what's the current value of strict. I am still not sure what sequence of actions could lead to this error. Let me also know if you switched back to an older version of Paisa after the upgrade by any chance.

@tonnydourado
Copy link
Author

@ananthakumaran I have had strict: "no", pretty much from the start, and it still happens, sometimes. I also only ever used the latest version.

@ananthakumaran
Copy link
Owner

Though the error is very obvious (it tries to save strict with some value other than yes/no/""), I am not sure how it will go to that state. I had a quick look at the code, but I can't find any obvious mistake so far. If you could find a way to reproduce the error reliably, that would be very useful.

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