Beta [webif] Web Interface 1.3.4 / Sweeper 2.1.4

Status
Not open for further replies.
af123

af123

Administrator
Staff member
I have just uploaded this pair of packages to the beta repository. There are a couple of new features in here that could do with some wider testing before being rolled out.

The first is the addition of a new background processing queue - an idea inspired by recent discussion and by MymsMan's detectads package. Things can be placed into the queue through sweeper rules (for which there are new actions) or by selecting files in the web interface browse window and then selecting the queue.

Screenshot%202016-12-17%2023.52.53.png


Screenshot%202016-12-17%2023.54.32.png

Any item which is queued for something will have a new icon against it -
Screenshot%202016-12-17%2023.57.41.png
and the queue itself can be viewed through diagnostics or via the 'View Queue' button at the bottom of the browse pages.

The second new feature is a set of options to control when background automatic processing occurs:

Screenshot%202016-12-17%2023.59.19.png

These may be refined downstream...

If you would like to try them out then install the opkg-beta package and then refresh the list of available packages. If you already have this package installed then these new updates will appear automatically when you next update.
 
"...how many minutes is soon?" doesn't have any bounds on the lower/upper values.
The "Suspend automatic processing" selection is missing 23:00-23:59. How do you deselect all times?
 
Last edited:
I deselected all the times but one would not 'go'. I used ctrl-click and it went. I pressed set next to the times and a 'loading settings' screen appeared and the circle kept going.
I did a page refresh and all okay.
 
On the Settings page, opening
"Settings for chaseget package" or "Settings for detectads package" just shows the text "ERROR: can't read "settings": no such variable"
"Settings for redring package" says "ERROR: can't read "rrflags": no such variable"
All the other settings appear to be OK

I have tried a page referesh and I get the same on both my recorders.
 
The template detectAds sweeper rule has a condition "not queued for detectads", do we need a similar one for "not queued for decryption"; maybe it is the same thing (or could be made as simply "not queued")
 
hairy_mutley said:
"Settings for redring package" says "ERROR: can't read "rrflags": no such variable"
Click to expand...
I have this error message, plus another in "Settings for tempmon package" which says "ERROR: can't read "settings": no such variable".
 
I am going to have to download and find time to play but there are obviously overlaps, similarities and differences with the existing DetectAds queueing mechanism and sweeper actions.

It could be confusing to have both - however I don't see Ad Detection in the 'Queue for' list of actions on my system . Do I need to add another .hook file to the DetectAds package to allow use of the new queuing mechanism?

One option available with DeteactAds that I don't see in the new support is a start time for processing. I felt it would be useful when queueing to be processed later to be able to say when later should be.
This is less important with Sweeper since you can use current time rules to control when items are added to the queue, but from Browse it would be nice to select a group of files and say process them after 01:00AM without having to go to settings to alter the Auto process time ranges first. DetectAds offers a choice of ASAP or a start time.
What do others think?
 
Does the Queued task list need both a Refresh page button and automatic page refresh, I find it quite disconcerting to have the Refresh page box keep popping up.

I like the keeping of completed items with their status but we will probably need a 'Select all completed' button to allow clean up of the list, or will they automatically expire after some period.
 
Thanks for all the feedback so far!
prpr said:
It would be nice if clicking on a single item that was already selected deselected it.
Click to expand...
Yes, I think I need to come up with a new GUI for this bit.

hairy_mutley said:
On the Settings page, opening
"Settings for chaseget package" or "Settings for detectads package" just shows the text "ERROR: can't read "settings": no such variable"
"Settings for redring package" says "ERROR: can't read "rrflags": no such variable"
Click to expand...
Brian said:
I have this error message, plus another in "Settings for tempmon package" which says "ERROR: can't read "settings": no such variable".
Click to expand...

Thanks - I'll investigate and fix.

hairy_mutley said:
The template detectAds sweeper rule has a condition "not queued for detectads", do we need a similar one for "not queued for decryption"; maybe it is the same thing (or could be made as simply "not queued")
Click to expand...

The same thing can't be added to the queue more than once so it isn't strictly necessary to have a condition like that, but I should add one for consistency. It's straightforward enough.

MymsMan said:
Does the Queued task list need both a Refresh page button and automatic page refresh, I find it quite disconcerting to have the Refresh page box keep popping up.
Click to expand...

I'm going to convert that screen to load the data via AJAX which will stop the refresh being noticeable (and avoid a whole page refresh each time).

MymsMan said:
I like the keeping of completed items with their status but we will probably need a 'Select all completed' button to allow clean up of the list, or will they automatically expire after some period.
Click to expand...

That's easy enough - I'll do that. At the moment the completed jobs are automatically cleaned up during boot after a few days. I will need to do something for boxes that don't reboot often too.

MymsMan said:
I am going to have to download and find time to play but there are obviously overlaps, similarities and differences with the existing DetectAds queueing mechanism and sweeper actions.
Click to expand...

Yes, it's something I was going to message you about so we can work out what the best solution is that suits us both and is least confusing. The extra detectads options in my screenshots are there because I've slightly modified my installed copy of detectads; I'll send you the diffs as a starter for ten.
Having the ability to directly select recordings in a folder and queue them up for ad-detection is something I will use a lot. At the moment I go into sweeper, set up a rule to do this and then run it before removing the rule again. I suspect a few people have a similar work flow.
 
The queued tasks list shows processing start time, which on completion is replaced by end time, but it would be useful to know how long processing took; this would help understand what time to set for the "soon" parameter.
 
I think I've addressed almost everything in the package updates now available:
  • Fixed the settings screen;
  • Added min/max constraints to the "soon minutes" field;
  • Improved the GUI for choosing which hours are active/inactive;
  • 23:00-23:59 now shown;
  • Handle stuck and expired queue entries better (no reboots required now);
  • Queue screen refreshes using AJAX so barely noticeable now and much faster;
  • Queue screen has more quick select buttons;
  • Queue screen shows how long it took to process each item;
  • Completed items now removed after 7 days (was 3 - could be a settings).
 
af123 said:
Completed items now removed after 7 days (was 3 - could be a settings)
Click to expand...
Probably better as a setting.

One weird thing I've noticed is that if you use the up and down keys on the time list, it doesn't behave as you might expect. Granted this is not a hugely likely thing for most people to do, but I'm a 'keyboard type' a lot of the time.

There's a box with the word 'dummy' in as well, which I guess is not meant to be there!
 
The keyboard stuff is supposed to work according to the plugin documentation:

Screenshot%202016-12-19%2011.40.11.png

I'll have a look!
 
My crontabs/root has been changed. I had auto running at 10,30,50 but it is now 5,25,45. Also my auto.log is filling up as it is now running every 3 minutes doing all the auto checks, presumably because of the new line in crontabs/root (*/3 * * * * /mod/webif/lib/bin/auto -queue >/dev/null 2>&1).
Also I recorded 'More new for you' which started at 8 minutes past midnight. The first couple of minutes had very bad pixelling but all okay after that. Any connection ?
For info I have just updated sweeper and webif - might they have an impact on the above ?
 
Because the kick off times for auto had been changed it looked like the full auto check was being done. However having another look the output is like this:
2469

19/12/2016 17:00:02 - Media scan completed in 0.18 seconds.
2468 19/12/2016 17:00:02 - Media scan starting, DLNA server status: 1
2467 19/12/2016 17:00:02 - -------------------------------------------------------
2466 19/12/2016 17:00:02 - Registered ::sweeper::scansingledir for postdecryptsingledir hook with priority 50.
2465 19/12/2016 17:00:02 - Registered ::sweeper::scan for postdecryptscan hook with priority 50.
2464 19/12/2016 17:00:02 - Registered ::newk::scan for postexpirescan hook with priority 50.
2463 19/12/2016 17:00:02 - Registered do_arbookmarks for postdecrypt hook with priority 50.
2462 19/12/2016 16:57:01 - Media scan completed in 0.123 seconds.
2461 19/12/2016 16:57:01 - Media scan starting, DLNA server status: 1
2460 19/12/2016 16:57:01 - -------------------------------------------------------
2459 19/12/2016 16:57:01 - Registered ::sweeper::scansingledir for postdecryptsingledir hook with priority 50.
2458 19/12/2016 16:57:01 - Registered ::sweeper::scan for postdecryptscan hook with priority 50.
2457 19/12/2016 16:57:01 - Registered ::newk::scan for postexpirescan hook with priority 50.
2456 19/12/2016 16:57:01 - Registered do_arbookmarks for postdecrypt hook with priority 50.
 
peterworks said:
My crontabs/root has been changed. I had auto running at 10,30,50 but it is now 5,25,45
Click to expand...
That will happen whenever you upgrade the web interface package (not just this beta one). It resets the cron entries.
There's no harm in those messages appearing in your auto log, it will just be automatically rotated as necessary. If you don't want them, decrease the logging level to "Actions and errors only".
 
Not a major problem but there seem to be some oddities in the package numbering as shown during update.
The From level doesn't always match the To level of the previous update and the latest Sweeper update appears to have gone to a lower level number
I haven't been doing manual updates
Code: 
1027    20/12/2016 08:13:20 - Automatically upgraded package webif from 1.3.4-2 to 1.3.4-5
1026    20/12/2016 08:13:19 - Automatically upgraded package sweeper from 2.1.4 to 2.1.3-1 (See forum for details)
1001    19/12/2016 06:48:24 - Automatically upgraded package webif from 1.3.4 to 1.3.4-2
1000    19/12/2016 06:47:39 - Automatically upgraded package recmon from 2.2.1 to 2.2.1-1 (Disable debugging)
982    18/12/2016 06:48:20 - Automatically upgraded package webif from 1.3.3-3 to 1.3.3-3
981    18/12/2016 06:48:19 - Automatically upgraded package nugget from 0.97 to 0.97-1
980    18/12/2016 06:48:18 - Automatically upgraded package sweeper from 2.1.3-1 to 2.1.3-1 (See forum for details)
897    14/12/2016 06:47:35 - Automatically upgraded package gtar from 1.26-1 to 1.26-2
896    14/12/2016 06:47:34 - Automatically upgraded package pkgtools from 1.0.0 to 1.0.1
874    13/12/2016 06:47:35 - Automatically upgraded package tunefix-update from 1.0.15 to 1.0.16
688    02/12/2016 06:47:34 - Automatically upgraded package dropbear-ssh from 2016.72-1 to 2016.74
687    02/12/2016 06:47:33 - Automatically upgraded package opkg-beta from 1.0 to 1.1
521    23/11/2016 06:48:19 - Automatically upgraded package webif from 1.3.3-2 to 1.3.3-3
307    12/11/2016 06:48:22 - Automatically upgraded package webif from 1.3.2-13 to 1.3.2-14
259    10/11/2016 02:14:48 - Automatically upgraded package webif from 1.3.2-10 to 1.3.2-12
 
Status
Not open for further replies.
Back
Top