Queue error logging
Jamroom Developers
DannyA:Forget about the queue. Again, after the conversion function has failed 3 consecutive times, we have not idea why.
We don't know why it failed, what users, what media.
So the a queue log entry telling me something has failed is useless. It does not help us identify and fix the probelem. So a user can potentially be re-submitting a failing job countless times and we can't identify it or fix it.
There are many thing that can cause the function to fail: unable to read/write, corrupt files, invalid formats, etc....
That's right - the core is
not supposed to tell you what went wrong - that is what I keep saying. Only the worker function can tell you want went wrong. By the time you see the "3rd time failing" error message from the core, that can only tell you something went wrong, and to start investigating - it is a "last gasp" "oops something has gone really wrong and you should check it out".
Again - the CORE queue functions have no idea what you are doing, what a queue worker is doing, etc. It does NOT know that the worker could not "download a file", or whatever. In theory queue workers could be doing thousands of different things. It only provides the framework for handling queue entries.
So again - nothing is needed at the core queue level, nor will we be making any changes since no changes are needed. It is functioning 100% as it should.
So with that said, I think what you are getting at is that the conversion process is failing and you don't know WHY. Debugging it is just like debugging anything else:
- go into the conversion function
- add print lines - i.e. fdebug('made it to here'); all over the place
- run the function and see where it gets to.
There's no magical way to figure it out - you just have to debug it.