Mulitiple spice plugins are being triggered about zeroclickinfo-spice HOT 8 CLOSED

@jagtalon the reason for multiple spice calls is because zipcode (and possibly octopart) are in the non-exclusive block which lets them race against other spices (because the query space for anything in non-exclusive is supposed to be large) hence zipcode is triggering because the ne5555 matches the regex looking for a possible postal code which is essentially a comobo of numbers and letters, however it fails over to octopart which then gives the result. As for the older version of occtopart triggering that seems like its a bigger issue so we should ask @yegg why that is happening. Any ideas Gabe?

from zeroclickinfo-spice.

I'm looking at Firebug on those queries and not seeing the old version. Was this the deep trigger you were testing on your machine or something?

As for multiple triggers, @moollaza is right about that. Generally, it isn't bad and they fire in parallel. However, if there are large cases where it is triggering when it shouldn't be then we can reign in the trigger with a qualifying regex. In this case zip code seems to be triggering on

https://www.duckduckgo.com/js/spice/zipcode/NE555/datasheet

And maybe it shouldn't be (given datasheet) but I haven't looked too closely.

We can generally check for false positives by seeing what queries it is triggering on in the back end. I can show you how to do that if (either of) you want to look into it.

from zeroclickinfo-spice.

@yegg @moollaza Thanks! It's much clearer now. I thought non-exclusive plugins only trigger if plugins in other categories (spice, exclusive, etc.) didn't. I'll see if the same thing happens with other plugins.

I'm using the latest version of deep (in the master branch), and it's not modified in any way. I tried Firebug and it's still there (try searching 121):

https://saucelabs.com/tests/18e867aa78014eb79626cbb212559945

https://saucelabs.com/tests/c4001e5b039f44ab807485c931a1f197#

from zeroclickinfo-spice.

Are you seeing this on the main site? I'm looking at

https://duckduckgo.com/?q=ne555+datasheet

and not seeing it.

from zeroclickinfo-spice.

@yegg sorry you are correct, I didn't realize @jagtalon 's links were to his dev instance. I believe the reason you are seeing the duplicate spice then Jag is because the newest version, 128, was deployed on your instance by yourself, however older versions of the octopart spice stay on your instance (we don't remove the perl modules) and I'm guessing that the newer octopart spice triggers differently, because I see two spice calls to octopart: "ne555" and "ne555%20datasheet" so I think both versions, because they are different are each triggering. I might be mistaken though. This might be a question for @Getty.

from zeroclickinfo-spice.

@moollaza @yegg Whoops. I'm sorry, I forgot to mention that it only happens to my dev machine. I don't get that either because I just updated triggers any => "datasheet", "specs" to triggers any => "datasheet", "specs", "octopart";

from zeroclickinfo-spice.

Look in source to see who is calling it.

from zeroclickinfo-spice.

Is this resolved? I do not see it on your dev node.

from zeroclickinfo-spice.