You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
after the init() I get errors, as this deletes the config and it will report missing argv parameters and such.
I'm trying to sniff everything at once (that's why I'm using the parallel option). I'd like to avoid the previous way where I ran the sniffer every time on a single file (which takes a long time to process and is memory expensive).
Also I'm not sure Config::setConfigData parts in my code are being picked up in the runner.
I'm not sure what part am I missing here.
The text was updated successfully, but these errors were encountered:
Sorry, I haven't had time to look into this. Work is really crazy so I'm not sure when I will.
But I can say that you understood what I meant by doing your own runner. And yes, if you do this, you can't use the parallel feature of the main runner - you'd have to implement that yourself.
This issue connects to the #2035 issue. I made some progress in the meantime, but I'm still not getting any results.
I'm rewriting the WordPress theme sniffer plugin and in my
run_sniffer()
ajax callback method I haveWhat I get back from the ajax is
{"success":true,"data":true}
.I logged the config and runner class, and the config is picked up
log output when adding error_log( print_r( $this->config, true ) ); in init() method of Runner.php
It looks like no report is being generated.
If I add
after the
init()
I get errors, as this deletes the config and it will report missingargv
parameters and such.I'm trying to sniff everything at once (that's why I'm using the parallel option). I'd like to avoid the previous way where I ran the sniffer every time on a single file (which takes a long time to process and is memory expensive).
Also I'm not sure
Config::setConfigData
parts in my code are being picked up in the runner.I'm not sure what part am I missing here.
The text was updated successfully, but these errors were encountered: