• Status Unconfirmed
  • Percent Complete
  • Task Type Bug Report
  • Category Backend/Core
  • Assigned To No-one
  • Operating System Linux
  • Severity Low
  • Priority Very Low
  • Reported Version 1.0 devel (github master)
  • Due in Version Undecided
  • Due Date Undecided
  • Votes
  • Private
Attached to Project: Flyspray
Opened by Thanatermesis - 26.10.2017

FS#2448 - error message in eventlog reports

The last version of Flyspray is simply amazing! it works like a charm :)

This is a small bug report in the eventlog page, that shows this message:

Notice: unserialize(): Error at offset 237 of 808 bytes in /home/elivebugs/ on line 88 Notice: unserialize(): Error at offset 229 of 796 bytes in /home/elivebugs/ on line 88

There’s a small screenshot:

Thank you!

Project Manager

I know similiar bugs can be seen on only on very old entries in the eventlog, see my screenshot.
I ignored them in favor of stuff with higher priorities as I thought they were just corrupt entries from a very ancient flyspray version.

But if that bad entries can be reproduced with 'not so old' versions of Flyspray, that would sure increase priority to detect (and maybe give a hint how to fix them in the database table).

Can you please filter by eventtype and timerange to identify the bad eventlogs?
Ideally look at provoking entries in your database, e.g. by mysql commandline or phpmyadmin

Thanks peterdd,

As you said, if this only affects to old database entries we should not care much (who cares about old/closed tasks? since they still works correctly should be enough)

In any case, I just did some filters and it happens in "user creation" for exactly this day:

Where one of the reporters in the logs seems to be empty?



Available keyboard shortcuts


Task Details

Task Editing