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

Similar exceptions not considered similar #9

Open
trivoallan opened this issue Jul 30, 2010 · 2 comments
Open

Similar exceptions not considered similar #9

trivoallan opened this issue Jul 30, 2010 · 2 comments

Comments

@trivoallan
Copy link

Hi,

Just sent two similar exceptions to my ErrorNot server instance. Both share the same exact message and backtrace :

  • Empty module and/or action after parsing the URL "/images/rollover-menu.png" (/).
  • 0classsfFrontWebControllerline170type->functiondispatchfile/mnt/home/tristan/color-party/sources/recette/lib/vendor/symfony/lib/util/sfContext.class.php
    1classsfContextline13type->functiondispatchfile/mnt/home/tristan/color-party/sources/recette/web/index.php

Unfortunately, it generates two separate error reports in ErrorNot.

Looking at the code, it seems that similarity is calculated by looking at error's message and backtrace equivalence.

Or did i misunderstood the code ?

@shingara
Copy link
Member

Yes you right.

Can you paste the request POST on your errornot instance in your log file.

@trivoallan
Copy link
Author

Here's a production.log showing two similar exceptions generating two distinct error reports : http://gist.github.com/500658

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

No branches or pull requests

2 participants