-
-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
Goals: speed up and a bugfix #1718
Conversation
✅ Deploy Preview for actualbudget ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
Bundle Stats — desktop-clientHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset No files were changed View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller No assets were smaller Unchanged
|
Bundle Stats — loot-coreHey there, this message comes from a GitHub action that helps you and reviewers to understand how these changes affect the size of this project's bundle. As this PR is updated, I'll keep you updated on how the bundle size is impacted. Total
Changeset
View detailed bundle breakdownAdded No assets were added Removed No assets were removed Bigger No assets were bigger Smaller
Unchanged
|
Was this a bug? If you have two templates in a category, #template 30 The standard rollover budget would fill 90 for this. With this change, the report budget will only fill 30. |
It works as expected in all my tests. Remember that the current budgeted value gets passed into applyCategoryTemplates (ln248). That prev_budgeted value is the starting value for the template return so it won't get missed. So the standard processing already returns a value that includes the previous pass(es) budgeted value. So what was happening, assuming 3 priority passes. The db was getting written and overwritten a whole bunch. Even if the priority pass didn't have any new actions on a category, that category would be written to the db again because the action was still in the list from before. |
I just tried my example again, and it works correctly. Weird! It didn't do that earlier for me, so maybe I had something strange on my system. |
* speed up and a bug fix * cleanup * note * lint
Fixed a bug where report budget income templates would compound instead of replacing previous values.
Fixed an issue where the list of budgeted values to apply to the db would persist between priority runs. This caused every processed template to be applied again in all future priority runs. That wasn't very noticeable when accessing locally, but on slower networks it would bog down the process a lot as each db change would be sent to the server.