Problems on the payload processing

[mereghost]

One of my monitored apps sent an ArgumentError that exploded on the Rack Middleware and somehow, Squash didn't process the issue correctly.

Now we are presented with an error without an error count or latest occurrences.

Any ideas on what may cause that?

[RISCfuture]

Possibly a validation error when saving the Occurrence but not the Bug. You can check the log for the API request; any error raised in the course of processing an error is logged.

[mereghost]

I'll check the logs then. Thanks in advance. =)

[mereghost]

The weird issue is that no errors are reported on log.

After some investigation on the PG logs, it seems that the very reason the exception occurs on the app, breaks the triggers: an invalid UTF-8 byte sequence.

    2013-02-08 11:58:56 BRST ERROR:  invalid byte sequence for encoding "UTF8": 0xe16769

[RISCfuture]

Oh, tricksy. Would it be possible for me to get the payload (minus sensitive data) so I can repro on my machine?

[mereghost]

I'll get it and send it your way.

[evanwalsh]

@mereghost any progress on this? I'm running into this and I'm not sure if I should start working on a PR.