sagex-api / sagex-services v9.1.7.0

[stuckless]

I released a new version of the sagex apis, updated to reflect the current apis in SageTV V9.1.7

This release fixes a memory leak in the RMI remote apis, and fixes that leak, but no long caching anything on the server. So from here on the remote apis are completely stateless.

I also removed a bunch of RPC connectivity options that have been deprecated since v7, and they are now removed. This likely doesn't affect anyone, since most people use either the RMI apis or the /sagex/api REST endpoint.

sagex-service deploys an Open API browser (Swagger UI) for viewing and interacting with the /sagex/api REST apis. This is a work in progress, but it's fairly functional.

You can access it from the jetty server using the following path /apidocs/

Related to the /sagex/api REST apis, I'm also working on a set JavaScript wrappers for the REST apis.

https://github.com/stuckless/sagetv-js-api

This js-api is a work in progress and I don't recommend people use it, yet, but just letting people know that this is coming, and it aims to make it easier to develop web applications that integrate with SageTV. I'm currently building it out while prototyping a web ui using React + Bootstrap.

[waynedunham]

The "apis in SageTV V9.1.7" may be why I can't get them to install on my SageTV machines. They say "Compatible= NO".

The Plugin details says that it has been brought up to SageTV V9 and I have V9.1.6.747 on both of my machines. I'm guessing that because I'm not on 9.1.7 is why they are showing as incompatible?

Actually that is why I came to the forums today, to see if there was a newer version of SageTV for Windows than what I am running.

[stuckless]

Originally Posted by waynedunham

The "apis in SageTV V9.1.7" may be why I can't get them to install on my SageTV machines. They say "Compatible= NO".

The Plugin details says that it has been brought up to SageTV V9 and I have V9.1.6.747 on both of my machines. I'm guessing that because I'm not on 9.1.7 is why they are showing as incompatible?

Actually that is why I came to the forums today, to see if there was a newer version of SageTV for Windows than what I am running.

Because the sagex apis is an api wrapper, and they wrap the 9.1.7 sage tv apis, then the min version is also set to 9.1.7. So yeah, you'd need to be at 9.1.7 of sagetv to install the new sagex apis.

[EnterNoEscape]

Originally Posted by stuckless

You can access it from the jetty server using the following path /apidocs/

Very cool.

[awhenry]

Note if you still use the (incomparably useful) SJQ, this update breaks it. You'll need to copy the sagex-api.jar file from your SageTV JARs folder to your sjqagent lib folder to restore operation. Unfortunately I did not discover this until after my SJQ filecleaner process ran, irrevocably deleting each and every one of my EDL and closed caption files for thousands of recordings (since it thought the media file was gone)...

[stuckless]

Originally Posted by awhenry

Note if you still use the (incomparably useful) SJQ, this update breaks it. You'll need to copy the sagex-api.jar file from your SageTV JARs folder to your sjqagent lib folder to restore operation. Unfortunately I did not discover this until after my SJQ filecleaner process ran, irrevocably deleting each and every one of my EDL and closed caption files for thousands of recordings (since it thought the media file was gone)...

Well, that certainly sucks. Unfortunately, I can't foresee how people are using this outside of sagetv, and, since I don't use sjq, I don't foresee this at all

[EnterNoEscape]

Originally Posted by awhenry

Note if you still use the (incomparably useful) SJQ, this update breaks it. You'll need to copy the sagex-api.jar file from your SageTV JARs folder to your sjqagent lib folder to restore operation. Unfortunately I did not discover this until after my SJQ filecleaner process ran, irrevocably deleting each and every one of my EDL and closed caption files for thousands of recordings (since it thought the media file was gone)...

Interesting. I updated and my SJQ tasks are still running ok.

[awhenry]

Originally Posted by EnterNoEscape

Interesting. I updated and my SJQ tasks are still running ok.

In my case the tasks were still running, just whenever they queried any media info from Sage they got back nulls, which in some cases just caused a task to do nothing, but in others caused the task to do something undesirable.

Maybe there are other variables which impact what behavior the update causes, I wouldn't be surprised. I just know what I was seeing, and that updating the sagex-api jar in the SJQ client lib folder restored normal functionality. Probably would be a good idea to update this jar even if you *aren't* having problems right now, as there is no mechanism to automatically update this library and over time it will grow further out of sync with Sage.

Regarding my personal loss of files, I was able to restore about 80% of what I lost using my parity-based file recovery system (snapraid). For the remaining 1500 or so lost files...oh well, guess I'm stuck watching the commercials and missing the CC, at least for the ones I already compressed (which was most of them). Need to get in and tweak the task to abort and issue an alert if it would delete more than 100 files or something (once I remember how to do that, haven't messed with my tasks in years).

[wayner]

Originally Posted by awhenry

Note if you still use the (incomparably useful) SJQ, this update breaks it. You'll need to copy the sagex-api.jar file from your SageTV JARs folder to your sjqagent lib folder to restore operation. Unfortunately I did not discover this until after my SJQ filecleaner process ran, irrevocably deleting each and every one of my EDL and closed caption files for thousands of recordings (since it thought the media file was gone)...

Can you be a bit more specific on this?

In my instance the sjq-agent folder on my server is \\server\appdata\sagetv\server\plugins\sjq-agent (I am on unRAID) - assuming that I have the correct folder. This folder currently only contains two directories - conf and logs. So I copy the sagex-api.jar file do this folder so that it is the only file (other than the dirs) in this folder?

I also run a sjq client remotely on a separate Win10 PC. On that PC I have a c:\sjqagent folder that contains a bunch of directories - bin, conf, engines, lib and logs. In the lib directory there is an existing sagex-api.jar file. In my instance this file is dated 6/11/2011.

Do I need to update anything on the server or just on the remote client Win PC? And if it is the later then do I have to restart anything after doing this copy?

[EnterNoEscape]

Originally Posted by awhenry

In my case the tasks were still running, just whenever they queried any media info from Sage they got back nulls, which in some cases just caused a task to do nothing, but in others caused the task to do something undesirable.

Maybe there are other variables which impact what behavior the update causes, I wouldn't be surprised. I just know what I was seeing, and that updating the sagex-api jar in the SJQ client lib folder restored normal functionality. Probably would be a good idea to update this jar even if you *aren't* having problems right now, as there is no mechanism to automatically update this library and over time it will grow further out of sync with Sage.

Regarding my personal loss of files, I was able to restore about 80% of what I lost using my parity-based file recovery system (snapraid). For the remaining 1500 or so lost files...oh well, guess I'm stuck watching the commercials and missing the CC, at least for the ones I already compressed (which was most of them). Need to get in and tweak the task to abort and issue an alert if it would delete more than 100 files or something (once I remember how to do that, haven't messed with my tasks in years).

That makes sense now. The reason I'm not having any issues is because I'm running the agent in the SageTV JVM since I'm using Linux and it keeps things less complicated. I misread what you posted thinking it broke the SJQ server piece, not the agent.

[awhenry]

Originally Posted by wayner

Can you be a bit more specific on this?

In my instance the sjq-agent folder on my server is \\server\appdata\sagetv\server\plugins\sjq-agent (I am on unRAID) - assuming that I have the correct folder. This folder currently only contains two directories - conf and logs. So I copy the sagex-api.jar file do this folder so that it is the only file (other than the dirs) in this folder?

I also run a sjq client remotely on a separate Win10 PC. On that PC I have a c:\sjqagent folder that contains a bunch of directories - bin, conf, engines, lib and logs. In the lib directory there is an existing sagex-api.jar file. In my instance this file is dated 6/11/2011.

Do I need to update anything on the server or just on the remote client Win PC? And if it is the later then do I have to restart anything after doing this copy?

For sure you will need to update the jar in the lib folder on your Win 10 client (one of my clients is that exact setup). You will then need to restart the client, whether you are running it in the service mode or the application mode.

I have a linux client as well, but it is not unraid (and not my Sage server), so it does have a lib folder under the sjqagent folder where the jar needed updated. It sounds like your setup there might be similar to EnterNoEscape's, in which case you probably don't need to do anything beyond updating the Sage plug-in.

[phelme]

Originally Posted by awhenry

Note if you still use the (incomparably useful) SJQ, this update breaks it. You'll need to copy the sagex-api.jar file from your SageTV JARs folder to your sjqagent lib folder to restore operation. Unfortunately I did not discover this until after my SJQ filecleaner process ran, irrevocably deleting each and every one of my EDL and closed caption files for thousands of recordings (since it thought the media file was gone)...

Thanks for posting about this BTW. I was wondering why my SJQ suddenly died (though the script failure logs I saw were pointing in this general direction ).