bliss blocks when using invalid proposal name
reported by @meyer from id19:
using an invalid proposal same (such as 'ihsomething') blocks bliss due to blocking behaviour in the metadata tango server when trying to access the logbook (even during session startup).
there is a merge request from @demariaa for the metadatamanager (icat/tango-metadata!34 (merged)diffs) that circumvents the problem.
The real solution should include a check in bliss whether the current proposal name is a valid proposal name, if not the proposal name needs to be set to something valid (None
?) to unblock bliss.
Further we should consider to make logbook comm asynchronous to avoid this sort of problem.