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

Fix app hanging when schedule moved before weekend #4196

Merged
merged 3 commits into from
Jan 19, 2025

Conversation

matt-fidd
Copy link
Contributor

Keeps the loop moving if it gets "stuck" with the same nextDate twice in a row

@actual-github-bot actual-github-bot bot changed the title Fix app hanging when schedule moved before weekend [WIP] Fix app hanging when schedule moved before weekend Jan 19, 2025
@matt-fidd matt-fidd changed the title [WIP] Fix app hanging when schedule moved before weekend Fix app hanging when schedule moved before weekend Jan 19, 2025
Copy link

netlify bot commented Jan 19, 2025

Deploy Preview for actualbudget ready!

Name Link
🔨 Latest commit d99f4d1
🔍 Latest deploy log https://app.netlify.com/sites/actualbudget/deploys/678d1cfafd2d43000852fc7e
😎 Deploy Preview https://deploy-preview-4196.demo.actualbudget.org
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site configuration.

Copy link
Contributor

github-actions bot commented Jan 19, 2025

Bundle Stats — desktop-client

Hey 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

Files count Total bundle size % Changed
15 6.67 MB → 6.67 MB (+3.83 kB) +0.06%
Changeset
File Δ Size
locale/nl.json 📈 +2.55 kB (+5.04%) 50.6 kB → 53.15 kB
home/runner/work/actual/actual/packages/loot-core/src/client/data-hooks/transactions.ts 📈 +124 B (+2.05%) 5.9 kB → 6.02 kB
locale/pt-BR.json 📈 +1.15 kB (+1.08%) 106.65 kB → 107.8 kB
View detailed bundle breakdown

Added

No assets were added

Removed

No assets were removed

Bigger

Asset File Size % Changed
static/js/nl.js 50.6 kB → 53.15 kB (+2.55 kB) +5.04%
static/js/pt-BR.js 106.65 kB → 107.8 kB (+1.15 kB) +1.08%
static/js/index.js 4.27 MB → 4.27 MB (+124 B) +0.00%

Smaller

No assets were smaller

Unchanged

Asset File Size % Changed
static/js/en-GB.js 96.03 kB 0%
static/js/en.js 97.98 kB 0%
static/js/workbox-window.prod.es5.js 5.69 kB 0%
static/js/resize-observer.js 18.37 kB 0%
static/js/indexeddb-main-thread-worker-e59fee74.js 13.5 kB 0%
static/js/uk.js 118.39 kB 0%
static/js/AppliedFilters.js 10.21 kB 0%
static/js/useAccountPreviewTransactions.js 1.63 kB 0%
static/js/narrow.js 84.83 kB 0%
static/js/BackgroundImage.js 122.29 kB 0%
static/js/wide.js 101.22 kB 0%
static/js/ReportRouter.js 1.59 MB 0%

Copy link
Contributor

github-actions bot commented Jan 19, 2025

Bundle Stats — loot-core

Hey 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

Files count Total bundle size % Changed
1 1.33 MB 0%

Changeset

No files were changed

View detailed bundle breakdown

Added

No assets were added

Removed

No assets were removed

Bigger

No assets were bigger

Smaller

No assets were smaller

Unchanged

Asset File Size % Changed
kcab.worker.js 1.33 MB 0%

Copy link
Contributor

coderabbitai bot commented Jan 19, 2025

Warning

Rate limit exceeded

@matt-fidd has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 15 minutes and 16 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between aa94d8d and d99f4d1.

📒 Files selected for processing (1)
  • packages/loot-core/src/client/data-hooks/transactions.ts (1 hunks)

Walkthrough

The pull request modifies the transaction date generation logic in the packages/loot-core/src/client/data-hooks/transactions.ts file. The changes introduce a loop iteration limit of 400 to prevent infinite looping when generating upcoming transaction dates for recurring schedules. A new variable i is added to track iterations, and a condition is implemented to stop the loop if it reaches 400 iterations. Additionally, a new check is added to prevent adding duplicate dates to the dates array by skipping dates that are already present. This modification ensures more controlled and predictable date generation for recurring transactions.

Possibly related PRs

Suggested labels

sparkles: Merged

Suggested reviewers

  • youngcw

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR. (Beta)
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 0

🧹 Nitpick comments (1)
packages/loot-core/src/client/data-hooks/transactions.ts (1)

187-191: LGTM! Effective solution to prevent hanging.

The duplicate date check effectively prevents the loop from getting stuck when getNextDate returns the same date repeatedly. The implementation ensures forward progress by skipping to the next day when a duplicate is found.

A small optimization could be to use a Set for O(1) lookups:

-const dates: string[] = [];
+const dates = new Set<string>();
-if (dates.includes(nextDate)) {
+if (dates.has(nextDate)) {
   day = parseDate(addDays(day, 1));
   continue;
 }
-dates.push(nextDate);
+dates.add(nextDate);

Note: You'll need to convert the Set back to an array before using it in the schedules array below.

📜 Review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 9d63b23 and aa94d8d.

⛔ Files ignored due to path filters (1)
  • upcoming-release-notes/4196.md is excluded by !**/*.md
📒 Files selected for processing (1)
  • packages/loot-core/src/client/data-hooks/transactions.ts (1 hunks)
🧰 Additional context used
📓 Learnings (1)
packages/loot-core/src/client/data-hooks/transactions.ts (1)
Learnt from: matt-fidd
PR: actualbudget/actual#4166
File: packages/loot-core/src/client/data-hooks/transactions.ts:200-200
Timestamp: 2025-01-16T14:29:13.188Z
Learning: In the scheduled transactions implementation within `packages/loot-core/src/client/data-hooks/transactions.ts`, the `upcoming` flag is set based on `schedules.length > 0` to act as an override, where the first occurrence gets `false` and subsequent occurrences get `true`. This is intentional and should not be changed to date-based comparison.
⏰ Context from checks skipped due to timeout of 90000ms (4)
  • GitHub Check: build (macos-latest)
  • GitHub Check: Analyze
  • GitHub Check: build (windows-latest)
  • GitHub Check: build (ubuntu-latest)
🔇 Additional comments (1)
packages/loot-core/src/client/data-hooks/transactions.ts (1)

179-179: LGTM! Good safety measure to prevent infinite loops.

The addition of a loop counter with a maximum of 400 iterations is a reasonable safeguard against infinite loops while allowing enough iterations to cover more than a year of daily transactions.

Also applies to: 181-182

@matt-fidd matt-fidd merged commit f35c5a0 into actualbudget:master Jan 19, 2025
20 checks passed
@matt-fidd matt-fidd deleted the schedule-loop branch January 19, 2025 16:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants