Ive tried this module and its seems that a lot of commands (GNATS daemon) not supported by daemon.
For example : QFMT full, QUER <number>
I replaced it with relevant analogs ( FULL and QURY)
and get output from daemon.
But anyway a lot of staff seems are not working.
- Could not parse gnatsd response
and so on
And all protocol looks slightly different.
Gary Z
There is a list of commands from daemon help
Escape character is '^]'.
200 korora GNATS server 3.113 ready.
help
230-The GNATS daemon accepts the following commands:
230- HELO and QUIT say hello and goodbye
230- NOCL skip closed PRs
230- LCAT list the available categories
230- LRES list the available responsible names
230- LSUB list the available submitters
230- LSTA list the available states
230- LCLA list the available classes
230- LCFG list the GNATS config file
230- CATG <category> search for PRs in <category>
230- SYNP <synopsis> search for PRs have the synopsis <synopsis>
230- RESP <person> search for PRs that <person> is responsible for
230- SUBM <submitter> search for PRs with a submitter <submitter>
230- ORIG <originator> search for PRs with an originator <originator>
230- RLSE <release> search for PRs from the release <release>
230- FXRL <fixed_in_release> search for PRs fixed in the release <fixed_in_release>
230- CLSS <class> search for PRs of class <class>
230- QRTR <quarter> search for PRs with Quarter <quarter>
230- KYWD <keywords> search for PRs with Keywords <keywords>
230- BFOR <date> find PRs with Date-Required: before <date>
230- AFTR <date> find PRs with Date-Required: after <date>
230- PRIO <priority> search for PRs which are of the priority <priority>
230- ABFR <date> find all PRs that arrived before <date>
230- ARAF <date> find all PRs that arrived before <date>
230- MBFR <date> find all PRs that were modified before <date>
230- MAFT <date> find all PRs that were modified before <date>
230- CBFR <date> find all PRs that were closed before <date>
230- CAFT <date> find all PRs that were closed before <date>
230- VDAT <date> validate the format of <date>
230- SVTY <severity> search for PRs which are of the severity <severity>
230- STAT <state> search for PRs in the state <state>
230- CONF <yes|no> set whether or not to include confidential PRs
230- TEXT <text> search for PRs with single-line <text>
230- MTXT <text> search for PRs with multiple-line <text>
230- MLPR <PR> list who should get mail about <PR>
230- MLCT <category> list who should get mail about <category>
230- MLSU <submitter> list who should get mail about <submitter>
230- MLRS <full> <strict> <person> give the email address for <person>
230- TYPE <submitter> give the type of a given submitter
230- RSET reset internal settings to initial startup
230- LKDB lock the main GNATS database
230- UNDB unlock the main GNATS database
230- LOCK <PR> <user> <pid> lock <PR> for <user> and optional <pid> and return PR text
230- UNLK <PR> unlock <PR>
230- CHEK check PR text for errors
230- EDIT <PR> check in edited <PR>
230- CHDB <database> change GNATS ROOT to <database>
230- DBLS list databases known to server
230- DBLA list database aliases known to server
230- USER <userid> <passwd> UserId and password for database access.
230-The search itself is taken by either QURY, SUMM, or FULL. Each
230- may be invoked with no arguments, which will search the entire
230- database given the constraints above, or with one or more PRs
230- in its command, which will display those PRs specifically.
230-The QURY command will show a given PR in a multi-line summary
230- format, SUMM will show that PR in a single-line summary, and the
230- FULL command will show the entire header and body of the PR.
230-You may also use the option SQLF or SQL2, which will give you an SQL
230- format line for each PR, which you can bring into your own database.
230 End of HELP info for GNATS daemon.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
There were big changes with interacting with the gnatsd in verison 4.0, it's much clearer now... So backwards compatibility would be difficult.
I've just added code to Gnats.pm to verify that gnatsd version is correct. Someone could probably make it compatible with 3.x, we would just need a developer with some time and desire.
later,
jim
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hello,
Does this API works with GNATS 3.11
Ive tried this module and its seems that a lot of commands (GNATS daemon) not supported by daemon.
For example : QFMT full, QUER <number>
I replaced it with relevant analogs ( FULL and QURY)
and get output from daemon.
But anyway a lot of staff seems are not working.
- Could not parse gnatsd response
and so on
And all protocol looks slightly different.
Gary Z
There is a list of commands from daemon help
Escape character is '^]'.
200 korora GNATS server 3.113 ready.
help
230-The GNATS daemon accepts the following commands:
230- HELO and QUIT say hello and goodbye
230- NOCL skip closed PRs
230- LCAT list the available categories
230- LRES list the available responsible names
230- LSUB list the available submitters
230- LSTA list the available states
230- LCLA list the available classes
230- LCFG list the GNATS config file
230- CATG <category> search for PRs in <category>
230- SYNP <synopsis> search for PRs have the synopsis <synopsis>
230- RESP <person> search for PRs that <person> is responsible for
230- SUBM <submitter> search for PRs with a submitter <submitter>
230- ORIG <originator> search for PRs with an originator <originator>
230- RLSE <release> search for PRs from the release <release>
230- FXRL <fixed_in_release> search for PRs fixed in the release <fixed_in_release>
230- CLSS <class> search for PRs of class <class>
230- QRTR <quarter> search for PRs with Quarter <quarter>
230- KYWD <keywords> search for PRs with Keywords <keywords>
230- BFOR <date> find PRs with Date-Required: before <date>
230- AFTR <date> find PRs with Date-Required: after <date>
230- PRIO <priority> search for PRs which are of the priority <priority>
230- ABFR <date> find all PRs that arrived before <date>
230- ARAF <date> find all PRs that arrived before <date>
230- MBFR <date> find all PRs that were modified before <date>
230- MAFT <date> find all PRs that were modified before <date>
230- CBFR <date> find all PRs that were closed before <date>
230- CAFT <date> find all PRs that were closed before <date>
230- VDAT <date> validate the format of <date>
230- SVTY <severity> search for PRs which are of the severity <severity>
230- STAT <state> search for PRs in the state <state>
230- CONF <yes|no> set whether or not to include confidential PRs
230- TEXT <text> search for PRs with single-line <text>
230- MTXT <text> search for PRs with multiple-line <text>
230- MLPR <PR> list who should get mail about <PR>
230- MLCT <category> list who should get mail about <category>
230- MLSU <submitter> list who should get mail about <submitter>
230- MLRS <full> <strict> <person> give the email address for <person>
230- TYPE <submitter> give the type of a given submitter
230- RSET reset internal settings to initial startup
230- LKDB lock the main GNATS database
230- UNDB unlock the main GNATS database
230- LOCK <PR> <user> <pid> lock <PR> for <user> and optional <pid> and return PR text
230- UNLK <PR> unlock <PR>
230- CHEK check PR text for errors
230- EDIT <PR> check in edited <PR>
230- CHDB <database> change GNATS ROOT to <database>
230- DBLS list databases known to server
230- DBLA list database aliases known to server
230- USER <userid> <passwd> UserId and password for database access.
230-The search itself is taken by either QURY, SUMM, or FULL. Each
230- may be invoked with no arguments, which will search the entire
230- database given the constraints above, or with one or more PRs
230- in its command, which will display those PRs specifically.
230-The QURY command will show a given PR in a multi-line summary
230- format, SUMM will show that PR in a single-line summary, and the
230- FULL command will show the entire header and body of the PR.
230-You may also use the option SQLF or SQL2, which will give you an SQL
230- format line for each PR, which you can bring into your own database.
230 End of HELP info for GNATS daemon.
Gary,
There were big changes with interacting with the gnatsd in verison 4.0, it's much clearer now... So backwards compatibility would be difficult.
I've just added code to Gnats.pm to verify that gnatsd version is correct. Someone could probably make it compatible with 3.x, we would just need a developer with some time and desire.
later,
jim