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

Exception in LogMessagesUC's LogGrid_CustomSummaryCalculate during/after Time Difference calculation #1839

Closed
Benedicht opened this issue Sep 3, 2023 · 6 comments
Labels
bug Something isn't working

Comments

@Benedicht
Copy link

Describe the bug

I have an >50 Mb json file that i load with Json Log Parser. Right clicking and selecting Calculate time difference from this point throws a System.ArgumentNullException in LogMessagesUC.LogGrid_CustomSummaryCalculate at line 1138:

else if (e.SummaryProcess == CustomSummaryProcess.Calculate)
{
counts[(string)e.FieldValue] = counts[(string)e.FieldValue] + 1;
}

Tried out both the pre-built v4.14.1 version and latest bits pulled down from the git repo. Both of them gave the very same result.

ℹ Computer information

  • OS: Windows 10 Pro 19042.450 64 bit
  • Analogy Version: Both latest pre-built release and source built using .NET Core 7
  • JSon Data Provider

📝 Provide detailed reproduction steps (if any)

  1. Load the attached top500_Timered.json
  2. Right-click on the first row.
  3. Select Calculate time difference from this point menu item
  4. Exception thrown in the above mentioned line

✔️ Expected result

Calculate time difference.

❌ Actual result

Exception thrown.

📷 Screenshots

image

top500_Timered.zip

@LiorBanai LiorBanai added the bug Something isn't working label Sep 3, 2023
@LiorBanai
Copy link
Member

@Benedicht thanks for reporting. I'll check this

@Benedicht
Copy link
Author

Thanks! Let me know if i can add any more details.

@LiorBanai
Copy link
Member

I see you are using the json parser. Can you please add the mapped fields you are using so I can reproduce it faster

@Benedicht
Copy link
Author

All json objects in the file should have both the date and level fields, no mapping should be needed.

@LiorBanai
Copy link
Member

ok thanks. I'll update :)

LiorBanai added a commit that referenced this issue Sep 5, 2023
@Benedicht
Copy link
Author

I have tested your commit and it's working correctly, thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants