Bug 795246 - Cannot pull revision of spec
Summary: Cannot pull revision of spec
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: PressGang CCMS
Classification: Community
Component: CSProcessor
Version: 1.x
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Lee Newson
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-02-20 04:41 UTC by Joshua Wulf
Modified: 2014-10-19 23:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2013-06-07 01:30:37 UTC

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Joshua Wulf 2012-02-20 04:41:53 UTC 
$ csprocessor revisions -c 6192

....
-> ID: 39397 on Mon, Feb 20, 2012 at 01:23:11 PM


$ csprocessor pull -r 39397 -c 6192

INFO:  The data requested for the specified ID is empty!
Comment 1 Lee Newson 2012-02-20 05:38:23 UTC 
Technically this isn't a bug as no post content specification does exist for that revision and topic id.

However perhaps a better fix would be to display more info on the revisions list.
Comment 2 Joshua Wulf 2012-02-20 07:00:47 UTC 
Should this return something?


csprocessor pull -r 39397 -c 6192 --pre
CSProcessor client version: 0.16.3
Loading configuration from /home/jwulf/.config/csprocessor.ini
Web Service at http://csprocessor.cloud.lab.eng.bne.redhat.com:8080/ version: 0.21.1

INFO:  The data requested for the specified ID is empty!
Comment 3 Lee Newson 2012-02-20 07:09:52 UTC 
Yes it should. Sorry I forgot to mention that the pre was broken. I've now fixed it and released it as version 0.21.2. the problem was from using a less than (<) where a less than or equal to (<=) should have been used to compare revisions.
Comment 4 Lee Newson 2013-06-07 01:30:37 UTC 
Closing and setting as current release as no QA was performed by the original reporter. If there is still an issue with this bug still than please re-open it.
Note You need to log in before you can comment on or make changes to this bug.