You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When trying to open a new brat without first creating a config.py, the following messages are shown:
Protocol error: ActiongetCollectionInformation returned the results of action undefined
Missing file config.py in the installation dir. If this is a new installation, copy the template file config_template.py to config.py in your installation directory ("cp config_template.py config.py") and edit it to suit your environment.
Protocol error: Actionwhoami returned the results of action undefined
Missing file config.py in the installation dir. If this is a new installation, copy the template file config_template.py to config.py in your installation directory ("cp config_template.py config.py") and edit it to suit your environment.
Protocol error: ActionloadConf returned the results of action undefined
Missing file config.py in the installation dir. If this is a new installation, copy the template file config_template.py to config.py in your installation directory ("cp config_template.py config.py") and edit it to suit your environment.
As the correct message ("Missing file config.py") is included, this isn't a big deal, but as this issue is likely to be frequently encountered on fresh installations, it would be nice if the output were a bit cleaner.
The text was updated successfully, but these errors were encountered:
Perhaps we could create a new client-server protocol exception specific to missing configuration and have the client deal with the best way of presenting the info to the user?
62754d4 fixes a few protocol errors, but messages seem to go missing at the moment. Also, opened #719 for the client-side issue of avoiding message duplication.
When trying to open a new brat without first creating a config.py, the following messages are shown:
As the correct message ("Missing file config.py") is included, this isn't a big deal, but as this issue is likely to be frequently encountered on fresh installations, it would be nice if the output were a bit cleaner.
The text was updated successfully, but these errors were encountered: