question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[Export] BUG: Inconsistent balances in Daily Balance CSV

See original GitHub issue

Issue Description

I am experiencing two issues with the daily balance CSV export:

  1. The daily balances exported from v1.4.0 do not match a previous export I made from v1.3.x. For example, the v1.3.x export may report 102.321 DCR on 12/31/2018 but a subsequent export from v1.4.0 reports 100.876 DCR on 12/31/2018. I know the second balance is wrong because of the second point below.

  2. The sum of the spendable, immature, and locked columns in the export do not equal the total column. For certain dates the discrepancy can be > 100 DCR.

Expected result

For days that have closed, the daily balance in the CSV should not change between exports. The sum of the spendable, immature, and locked columns should equal the total column.

Versions Affected

Experiencing this issue with Version 1.4.0. I was able to export a correct CSV from Version 1.3.2

Steps to reproduce

  1. Be running decrediton with staking turned on
  2. Export the Daily Balances CSV file from v1.4.0
    • This is sufficient to surface issue 2
  3. Export the Daily Balances CSV from v1.3.x and compare to v1.4.0 export
    • Necessary to surface issue 1

Issue Analytics

  • State:closed
  • Created 4 years ago
  • Comments:14 (14 by maintainers)

github_iconTop GitHub Comments

1reaction
matheusdcommented, Apr 24, 2019

Do you have any thoughts on what might be causing this? Is it possible the last operation of the day is completely excluded from all columns?

Seems something like that, yeah. We can reproduce the problem now, seems like some transactions get offset into the next day, which ends up throwing the calculations off. We’ll keep you posted once we have a fix for it.

0reactions
matheusdcommented, May 17, 2019

It won’t work anymore, given it’s been hardforked out of the network (due to the latest voting).

Read more comments on GitHub >

github_iconTop Results From Across the Web

6 Common CSV Import Errors and How to Fix Them - Flatfile
One of the most common CSV import errors is that the file is simply too large. That can be caused by too many...
Read more >
Trial Balance unable to export to csv file. - Microsoft Dynamics ...
A couple of our GP users are unable to save their Trial Balances. Reports > Financial > Trial Balance. On the TB window...
Read more >
Date formats are inconsistent when exporting Impromptu ... - IBM
When the report is exported to a CSV, the date is in the following format: YYYY-MM-DD HH:MM (for example: 2004-10-01 12:00). Why is...
Read more >
Troubleshoot CSV Export - AppSheet Help - Google Support
If the CSV Export data action fails, the following tips may help you resolve the problem. Export fails after about two minutes.
Read more >
Add a Baseline to a Playbook - LogicHub Documentation
In Advanced Mode, a baseline allows you to compare current (most recent) behavior with past behavior to determine whether the current behavior is...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found