You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@felipecampanini is working on a case in which there are Shareaza Library1.dat and Library2.dat files.
Processing with IPED 4.1.0, 4.0.x and 3.18.x these files weren't parsed.
Investigating the issue, I found out that using the Python parser written by @fmpfeifer, both files were parsed successfully.
Comparing IPED Java parser code and the Python one, I found out that last fixes applied in the original project weren't reflected in IPED: fmpfeifer/ShareazaParser@f220278
As the changes were very simple, I applied them to our project and confirmed the issue was fixed.
Other sample Shareaza files that I have were also processed successfully.
The text was updated successfully, but these errors were encountered:
Thanks @tc-wleite, it was in my backlog of things to do in iped. Unfortunately I'm busy in other projects and could not spare some time to work on this. I still have a few other items in my iped to do list that I hope I can put forward soon.
Sorry for the the long delay and thanks again
@fmpfeifer feel free to use this issue tracker to document your TODO list. If they are bug fixes, it's important to document here. Please remember to open them here before start working to avoid duplicate efforts.
If both of you need time to work on something important, let me know and I can try to negotiate with my chief and yours to borrow some time from you, thanks.
@felipecampanini is working on a case in which there are Shareaza Library1.dat and Library2.dat files.
Processing with IPED 4.1.0, 4.0.x and 3.18.x these files weren't parsed.
Investigating the issue, I found out that using the Python parser written by @fmpfeifer, both files were parsed successfully.
Comparing IPED Java parser code and the Python one, I found out that last fixes applied in the original project weren't reflected in IPED:
fmpfeifer/ShareazaParser@f220278
As the changes were very simple, I applied them to our project and confirmed the issue was fixed.
Other sample Shareaza files that I have were also processed successfully.
The text was updated successfully, but these errors were encountered: