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

Unpredictable behavior when change the set of "Additional info" columns #107

Closed
asivura opened this issue Feb 26, 2021 · 5 comments
Closed
Labels

Comments

@asivura
Copy link

asivura commented Feb 26, 2021

Steps to reproduce:

  1. Import file to Usagi and choose only one additional column with text values.
  2. Do some mappings and export them
  3. Import file to Usagi step 1 and choose few additional columns (in our case we had additional columns with numeric values) including the column from step 1.
  4. Apply mapping from step 2
  5. Start randomly approve and unapprove records. After some period of time records start to disappear and the app freezes.

We use Usagi version 1.3.0 on MacOS 10.15.7
Java version: openjdk 15.0.1 2020-10-20

@MaximMoinat
Copy link
Collaborator

Hi @asivura. I haven't seen this behaviour before.
For my understanding, why are you importing the same file twice? To continue working in the same file you can save the raw data and open it again later (which will automatically include all the additional columns).

@asivura
Copy link
Author

asivura commented Mar 1, 2021

Hi @MaximMoinat . We have to add additional records into the initial file from time to time. There is the reason why we are importing the new file and applying existing mappings. We decided to add additional columns when we imported the file and had the issue I described before. As a workaround, I added additional columns into our existing file with mappings manually with prefix "ADD_INFO:", but I think it would be great to fix it to avoid others having the same issue. It took us a few hours to understand why it is happening, and we lost some of the mapping results.

@MaximMoinat
Copy link
Collaborator

That helps. So you are using the File –> Apply previous mapping functionality?

That is indeed something that might not be tested in all scenarios. Thanks for reporting!

@MaximMoinat MaximMoinat added the bug label Mar 3, 2021
@asivura
Copy link
Author

asivura commented Mar 3, 2021

Yes we use "File –> Apply previous mapping".

@MaximMoinat
Copy link
Collaborator

@asivura Was able to replicate. The bug occurs with the applied mapping contains new codes and has fewer additional columns. The issue is that additional columns are not read from the applied mapping file.

Working on a fix for the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants