ICRAR / ngas

69%

master: 69%

LAST BUILD ON BRANCH issue-38

branch: issue-38

CHANGE BRANCH

x

Reset

• issue-38
• 98-query-ignore
• NGAS-163
• aiosmtpd
• avoid-installing-bsddb3-in-py27
• bbcp_fixes
• c_client_warning_fixes
• centos7-compatibility-changes
• clone-fix
• clone-order-fixes
• correct-janitor-init
• correct-logging-c
• coverage-stability
• direct_sql
• doc-updates
• docs-fix
• document-future-removal-of-27
• fits_optional_arcfile
• fix-requests-dependency-specs
• fs-monitor
• fs-monitor-fixes
• github-actions
• improve-register-error-message
• issue-103
• issue-13
• issue-44
• issue-50
• issue-51
• janitor-thread-startup
• macos-hostnames
• macos-travis-fix
• macos-travis-update
• master
• netifaces-fix
• next
• no-create-venv
• none-reg-parameters
• partner_sites
• plugins-importing
• py311
• py39
• python-client-improvements
• relaxed-netifaces
• release-12.0
• remove-2.7-builds
• remove-test-generic-registration-plugin
• requests-pinning
• richer-archiving-event
• separate-test-servers
• servers-flag
• small-improvements
• smtp-testing
• stream-proxy-request
• subscription-def
• subscription_thread_ng
• travis-errors
• travis-fixes
• travis-focal
• update-travis-matrix
• uwe-fixes
• v11
• v12
• v12.0
• various_improvements
• volumes

Fix --servers flag for ngamsArchiveClient

The ClientWrapper class in the fs_monitor module was always creating an
ngamsPClient object with host, port and servers, although they are
mutually exclusive arguments (host/port and servers). This was only
triggered when users specified the --servers flag on the
ngamsArchiveClient utility.

This commit fixes this situation, and adds a new unit test to ensure the
--servers flag continues working as expected.

This addresses #38.

Signed-off-by: Rodrigo Tobar <rtobar@icrar.org>