Closed dlr-tangosierra closed 3 years ago
Fixed:
prosEO (PTM)> orbit show PTS
S/C Orb-# Sensing Start Sensing Stop
PTS 03000 2019-11-04T09:00:00.200000 2019-11-04T10:41:10.300000
PTS 03001 2019-11-04T10:41:10.300000 2019-11-04T12:22:20.400000
PTS 03002 2019-11-04T12:22:20.400000 2019-11-04T14:03:30.500000
PTS 03003 2019-11-04T14:03:30.500000 2019-11-04T15:44:40.600000
PTS 03004 2019-11-04T15:44:40.600000 2019-11-04T17:25:50.700000
PTS 03005 2019-11-04T17:25:50.700000 2019-11-04T19:07:00.800000
prosEO (PTM)> orbit show --from=3004 PTS
S/C Orb-# Sensing Start Sensing Stop
PTS 03004 2019-11-04T15:44:40.600000 2019-11-04T17:25:50.700000
PTS 03005 2019-11-04T17:25:50.700000 2019-11-04T19:07:00.800000
prosEO (PTM)> orbit show --to=3001 PTS
S/C Orb-# Sensing Start Sensing Stop
PTS 03000 2019-11-04T09:00:00.200000 2019-11-04T10:41:10.300000
PTS 03001 2019-11-04T10:41:10.300000 2019-11-04T12:22:20.400000
prosEO (PTM)> orbit show --from=3001 --to=3001 PTS
S/C Orb-# Sensing Start Sensing Stop
PTS 03001 2019-11-04T10:41:10.300000 2019-11-04T12:22:20.400000
prosEO version 0.5.2 Windows 10
Context: When the user is trying to show a range or orbits and uses only [from] or [to], the system retrieves all the orbits. This is a bug.
Proposition: Return an error message requiring both from and to.
Problematic example 1
problematic example 2