Subversion Repositories SmartDukaan

Last modification

• Rev 37402 2026-08-25 20:57:24
• Author: amit

• Log message:

  Vivo IMEI activation: report Vivo's captcha verdict back to the solver
  
  Only this cron ever learns whether Vivo accepted a captcha (status 0 means it
  was wrong), so it is the only place that can label the solver's training data.
  After each checkCode response it now posts the image, the code and the outcome
  to the solver's /verdict endpoint, which files the sample as accepted (the
  prediction was right - a free label) or rejected (needs a human to label it).
  
  The solver has been running at a measured 22.3% accept rate and no training
  data was ever collected, so the model could not be improved at all.
  
  Strictly best-effort: 2s connect / 3s read timeouts and every exception
  swallowed. Data collection must never slow down or break IMEI activation.
  
  The shared secret is read from CAPTCHA_VERDICT_TOKEN in the environment,
  falling back to a captcha.verdict.token property, so it need not be committed.
  Without a token the call is skipped entirely.
  
  Also drops /tmp/captcha.jpg: the captcha bytes are needed in memory for the
  verdict report anyway, so the two concurrently-scheduled Vivo jobs no longer
  share one file and overwrite each other's image.