cspclient-0.24.7-1.noarch OS: Fedora release 15 (Lovelock) JAVA: java version "1.7.0" Java(TM) SE Runtime Environment (build 1.7.0-b147) Java HotSpot(TM) Client VM (build 21.0-b17, mixed mode, sharing) [jwulf@radhe Messaging_Programming_Reference]$ csprocessor push CSProcessor client version: 0.24.7 Loading configuration from /home/jwulf/.config/csprocessor.ini Loading project configuration from csprocessor.cfg Connecting to Skynet server: http://skynet.usersys.redhat.com:8080/TopicIndex/ INFO: The Content Specification is valid. ERROR: An error occurred during processing please try again. [jwulf@radhe Messaging_Programming_Reference]$ cat csprocessor.cfg # SPEC_TITLE=Messaging_Programming_Reference SPEC_ID=8025 SERVER_URL=http://skynet.usersys.redhat.com:8080/TopicIndex/
No error thrown in the server log. It does this consistently with two different specs that I've checked out locally: 8025 and 7069 (3-4 attempts each)
[jwulf@radhe Messaging_Programming_Reference]$ csprocessor info CSProcessor client version: 0.24.7 Loading configuration from /home/jwulf/.config/csprocessor.ini Loading project configuration from csprocessor.cfg Connecting to Skynet server: http://skynet.usersys.redhat.com:8080/TopicIndex/ Content Specification ID: 8025 Content Specification Revision: 140349 Content Specification Title: Messaging Programming Reference
This comment is just for reference, for when I get to look at this properly. There are no errors that exist in the Skynet server logs.
Fixed. As I told josh yesterday I'll have to move this back down the commits to be able to fix it properly, so I'll change this to ON_QA and put a version number up once that happens. Cause: The clone function was trying to clone a null object in the CommonUtilities class, as such a NPE was thrown. Consequence: Topics couldn't be cloned to be updated and as such the push would fail. Fix: Add a check to see if the category tags is null before cloning. This should be fixed for all REST entities.
Just to add, as a reference why everyone else I talked to didn't have any issues, appears to be because they weren't adding tags to existing topics through global tags like Josh's two examples.
Released in version 0.24.8.
Verified with 0.24.8