Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

AutoStart fails if AuthenticateFn has wrong valence, but does not show the info about the error. #33

Open
mbaas2 opened this issue Sep 22, 2022 · 0 comments
Open

AutoStart fails if AuthenticateFn has wrong valence, but does not show the info about the error. #33

mbaas2 opened this issue Sep 22, 2022 · 0 comments
Assignees
@bpbecker

Comments

@mbaas2
Copy link
Contributor

mbaas2 commented Sep 22, 2022

I happened to define an ambivalent AuthenticateFn where a monadic one was expected.
The session output (after starting APL with jarvis.dws and a configfile-argument) was:

⍎Unable to start server - "#.CITA_Server. 0
      Server←AutoStart
      ∧
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@bpbecker bpbecker

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@bpbecker @mbaas2