Set up Mailgun/Talon on GCP. Using the sample triggered an error due to a missing decision function in the classifier. See example below:
from talon.sig_handler import extract_sig
msg_content = "Thanks Sasha, I've hit my limit.\n\nJane Doe\nvia mobile"
result, sig_fragment = extract_sig(msg_content, user='[email protected]')
I encountered a similar issue while working with Mailgun/Talon on GCP. The error was triggered because the classifier did not have an initialized decision function which led to the failure during signature extraction. What eventually worked for me was ensuring that I was using a version of Talon that properly supported customized decision functions. I ended up manually supplying a simple function during initialization which rectified the issue. It also helped to verify that all dependencies were correctly in place and no configuration steps were missed in the setup process.
I faced a similar obstacle with Mailgun/Talon when the decision function was unaccounted for in the classifier setup. In my case, the resolution came by defining a minimal custom decision function that met the requirements during the initialization phase. This modification ensured that the signature extraction process had the necessary criteria to operate effectively. I recommend checking the version compatibility of Talon and device-specific instructions in the documentation. It might also help to debug starting from the classifier initialization to ensure that no essential function is inadvertently omitted.
hey all, i solved it by adding a dummy decision fn during init. updated my talon version and deps, so check docs for gcp setup quirks. maybe helps if your classifier misses a decision function
I encountered a similar issue when working with Mailgun/Talon on GCP. In my experience, the problem wasn’t solely about a missing decision function; it turned out that an outdated dependency and an improperly configured initialization routine were also at play. I resolved the issue by upgrading my Talon package and ensuring that the initialization code incorporated a fallback decision function. This approach helped in bypassing the failure that occurred during signature extraction. It is crucial to double-check the dependency versions and configuration settings since minor version mismatches can result in unexpected errors during runtime.