Looks like this was some transitory bad interaction between a specific back-end and a particular state of the front-end code. At any rate, it's gone away now – most likely never to return.
Mike Taylor April 14, 2017 at 4:26 PM
I tried using setTimeout in requestLogin so that it waits a second before fetching the user, and two seconds before fetching the perms. It doesn't help – they still error out with an uninformative 500.
Mike Taylor April 14, 2017 at 4:21 PM
Got some way into investigating this, before my VM got into a state where I couldn't log in properly any more: although the login request itself succeeded, the subsequent fetch of the user object and the perms both failed with that BLOODY 500 ERROR – see FOLIO-516.
Mike Taylor April 14, 2017 at 3:13 PM
confirms that he sees the same thing (also against backend v0.8.3)
See attached screencap. This is with ui-users and stripes-components from git head, running against folio-blackbox-auth v0.8.3.