Conversation
vindard
changed the title
Contributor
Author
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
DO NOT MERGE, this is to explore the problem and see if it's an actual bug. So far, it's just a misuse of account sets.
I've been able to isolate the issue to this DAG
The problem shows up when we create an interest account under this setup of account sets. Can be done via:
make reset-deps run-serverbats -t bats/add-interest-account.batsThe problem goes away if any of the solid lines in the DAG is broken since it breaks double-adding interest account to chart of accounts account-set.
Should this problem show up before we get to the
Interest Accountcreation though?