Thread Tagging Improvements 1.0.8 Patch Level 1

[Recep Baltaş]

I believe it's dead :/

 

[Digital Doctor]

We use 021's AI Chatbot add-on

have him fix the issue ?

 

[Enes3078]

have him fix the issue ?

Both are lazy programmers, 021 and mazzly

 

[Digital Doctor]

lazy

$$ just pay for it if you want it.

 

[Enes3078]

$$ just pay for it if you want it.

021 doesn't care about bugs and mazzly, you know he doesn't care about anything about add-ons. So, it shouldn't cost money to fix bugs, am I right?

 

[Digital Doctor]

Mazzly provided free coding for this addon but you think "he doesn't care".

That's a weird take, bro.

Q: Should you expect him to keep donating his time to this addon ?
A: Probably not !

 

[Recep Baltaş]

I am encountering a blocking error in the server error logs that is causing the job queue to get stuck. It appears that the collectWordsCron task is attempting to save an excessive amount of data into the xf_job table, exceeding the column limit.

The Error:

XF\Db\Exception: MySQL query error [1406]: Data too long for column 'execute_data' at row 1 src/XF/Db/AbstractStatement.php:230

Stack Trace:

UPDATE  `xf_job` SET `execute_data` = ?, `trigger_date` = ?, `last_run_date` = ? WHERE job_id = ?<br>------------<br>#0 src/XF/Db/Mysqli/Statement.php(207): XF\Db\AbstractStatement-&gt;getException('MySQL query err...', 1406, '22001')<br>#1 src/XF/Db/Mysqli/Statement.php(83): XF\Db\Mysqli\Statement-&gt;getException('MySQL query err...', 1406, '22001')<br>#2 src/XF/Db/AbstractAdapter.php(96): XF\Db\Mysqli\Statement-&gt;execute()<br>#3 src/XF/Db/AbstractAdapter.php(323): XF\Db\AbstractAdapter-&gt;query('UPDATE  `xf_job...', Array)<br>#4 src/XF/Job/Manager.php(226): XF\Db\AbstractAdapter-&gt;update('xf_job', Array, 'job_id = ?', 18133810)<br>

Analysis:

I inspected the problematic row in the xf_job table. The job class is MaZ\PotentialTagHelper:RebuildPotentialTagWords.

The execute_data column for this specific job has grown to 13.9 MiB, which is too large for the standard MEDIUMBLOB column type in XenForo (and generally too large for a job state payload).

• Job ID: 18133810
• Unique Key: collectWordsCron
• Execute Class: MaZ\PotentialTagHelper:RebuildPotentialTagWords
• Execute Data Size: ~13.9 MiB (BLOB)

It seems the add-on is trying to carry over too much data between job steps. I had to manually delete the job and disable the add-on to clear the queue.