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

[13.0][FIX] partner_statement: minor fixes (partial backport) #991

Open
wants to merge 2 commits into
base: 13.0
Choose a base branch
from

Conversation

MiquelRForgeFlow
Copy link
Contributor

Backport of some minor fixes done in #967 and #988.

@MiquelRForgeFlow MiquelRForgeFlow force-pushed the 13.0-fix-partner_statement-minor-fixes branch 10 times, most recently from 659c691 to 531740d Compare January 16, 2023 17:40
Copy link
Contributor

@gdgellatly gdgellatly left a comment

Choose a reason for hiding this comment

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

The PR that this is backporting seems to now produce wrong opening balances. Suggest we hold until those are resolved.

@MiquelRForgeFlow MiquelRForgeFlow force-pushed the 13.0-fix-partner_statement-minor-fixes branch from 531740d to cddb2f2 Compare February 9, 2023 12:05
@MiquelRForgeFlow
Copy link
Contributor Author

Thanks, fixed.

@MiquelRForgeFlow MiquelRForgeFlow force-pushed the 13.0-fix-partner_statement-minor-fixes branch from cddb2f2 to 15b72a1 Compare February 10, 2023 10:46
@MiquelRForgeFlow MiquelRForgeFlow force-pushed the 13.0-fix-partner_statement-minor-fixes branch from e8d5b7d to ee6366c Compare October 3, 2023 08:59
@MiquelRForgeFlow
Copy link
Contributor Author

@gdgellatly I would like to merge these backport fixes. Is it fine?

@gdgellatly
Copy link
Contributor

@MiquelRForgeFlow I don't know, we are still stuck on a December 2022 release of partner statement because a whole load of changes landed between then and Feb and they produce wrong numbers and in some cases complete nonsense. I haven't checked since about July whether these things have been fixed, but I know the first round of fixes didn't resolve.

Copy link

There hasn't been any activity on this pull request in the past 4 months, so it has been marked as stale and it will be closed automatically if no further activity occurs in the next 30 days.
If you want this PR to never become stale, please ask a PSC member to apply the "no stale" label.

@github-actions github-actions bot added the stale PR/Issue without recent activity, it'll be soon closed automatically. label Feb 11, 2024
@github-actions github-actions bot closed this Mar 17, 2024
@AaronHForgeFlow AaronHForgeFlow added no stale Use this label to prevent the automated stale action from closing this PR/Issue. and removed stale PR/Issue without recent activity, it'll be soon closed automatically. labels Mar 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
no stale Use this label to prevent the automated stale action from closing this PR/Issue.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants