Enhancement #967
Error message for missing transports is uninformative
Status: | Resolved | Start date: | 03/20/2012 | |
---|---|---|---|---|
Priority: | Normal | Due date: | ||
Assignee: | J. Wienke | % Done: | 100% | |
Category: | Python | |||
Target version: | rsb-0.7 |
Description
Without a .config/rsb.conf, I get the following message when calling createInformer:
ValueError: No transports specified (config is ParticipantConfig[[] {}])
I'd say that is not particularly helpful for someone who doesn't know that RSB has different transports, and needs them configured. I would recommend pointing them to a page of documentation with configuration tips or the like.
Related issues
History
#1 Updated by J. Wienke about 12 years ago
- Category set to Python
Which version are you using? Do you have a short test case for this? Usually there is a default configuration with spread (no need for a config file) so it might be related to the remaining things you are doing.
#3 Updated by J. Wienke almost 12 years ago
- Status changed from Feedback to Resolved
- Assignee set to J. Wienke
- Target version set to rsb-0.7
- % Done changed from 0 to 100
It seems there really was no default transport so far. We have now decided to make the socket process the default and this is coded. So users should only see this warning now if they explicitly disable everything using the configuration mechanism (and in that case they probably have found documentation for the configuration). Reopen if still an issue for you.