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.

Sign up for GitHub

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

Jump to bottom

[Bug]: Actual import error message claims errors are automatically reported #1069

Closed
1 task done
shall0pass opened this issue May 29, 2023 · 1 comment · Fixed by #1155
Closed
1 task done

[Bug]: Actual import error message claims errors are automatically reported #1069

shall0pass opened this issue May 29, 2023 · 1 comment · Fixed by #1155
Labels
bug Something isn't working

Comments

@shall0pass
Copy link
Contributor

Verified issue does not already exist?

  • I have searched and found no existing issue

What happened?

Found an error message that needs to be updated to point to GitHub rather than informing the user that the error is automatically reported.

FYI. This was an attempt to import a 'new' test file since the hidden category feature was added into an older PR. There should also be a note in the next release notes about a breaking change.

image

What error did you receive?

No response

Where are you hosting Actual?

Other

What browsers are you seeing the problem on?

Chrome

Operating System

Windows 11
@shall0pass shall0pass added bug Something isn't working needs triage labels May 29, 2023
@j-f1 j-f1 removed the needs triage label May 29, 2023
@j-f1
Copy link
Contributor

j-f1 commented May 29, 2023

FYI. This was an attempt to import a 'new' test file since the hidden category feature was added into an older PR. There should also be a note in the next release notes about a breaking change.

Currently, we do not support reverting migrations that have been applied to a file. That means that if you run a budget file with a newly added migration, it can no longer be loaded in a previous Actual version. I’m not sure how we can best message this, since whether or not a release includes new migration(s) is generally independent of what new features it has (e.g. Nordigen integration requires no migration)

@j-f1 j-f1 changed the title [Bug]: Update text on error [Bug]: Actual import error message claims errors are automatically reported May 29, 2023
MatissJanis added a commit that referenced this issue Jun 20, 2023
@MatissJanis
🐛 remove 'we have been notified' copy
290d624 
Closes #1069
@MatissJanis MatissJanis mentioned this issue Jun 20, 2023
Merged
MatissJanis added a commit that referenced this issue Jun 20, 2023
@MatissJanis
🐛 remove 'we have been notified' copy (#1155)
c286f1c 
Closes #1069

I've not actually tested this change. Which is why I'm not changing it
to direct links (as they might not work).

Instead I'm just applying a very quick patch so the message would not be
misleading anymore.
FlorianLang06 pushed a commit to FlorianLang06/actual that referenced this issue Mar 7, 2024
@MatissJanis
🐛 remove 'we have been notified' copy (actualbudget#1155)
f21f017 
Closes actualbudget#1069

I've not actually tested this change. Which is why I'm not changing it
to direct links (as they might not work).

Instead I'm just applying a very quick patch so the message would not be
misleading anymore.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

🐛 remove 'we have been notified' copy actualbudget/actual
2 participants
@shall0pass @j-f1