etn version 2.3.0 login error

[PieterjanVerhelst]

I just ran the new etn beta version on my local drive and as explained by @PietrH I had to provide my credentials after running a function. However, I still get an error when running a function, for example get_animal_projects():

> get_animal_projects()
Error: ODBC failed with error 00000 from \
             .

In call:
opencpu:::rapachehandler()

Backtrace:
    ▆
 1. └─output_handler$error(e)

When filling in my password, I did not include the " showing its a factor. Could that be the issue or would the password prompt appear again when filling in the incorrect password?

[PietrH]

Hi Pieterjan, You need to enter your username and password without the "", if you included them that would explain the error. You can check, and also set them manually with Sys.getenv("userid") and Sys.setenv(userid= "username") -> with the "". For the password you could still set it manually using Sys.setenv(pwd="*****"). Just like the etn of old. Hope that helps! If not, let me know. Pieter

…

On Fri, 4 Oct 2024, 17:31 Pieterjan Verhelst, ***@***.***> wrote: I just ran the new etn beta version and as explained by @PietrH <https://github.com/PietrH> I had to provide my credentials after running a function. However, I still get an error when running a function, for example get_animal_projects(): > get_animal_projects() Error: ODBC failed with error 00000 from \ . In call: opencpu:::rapachehandler() Backtrace: ▆ 1. └─output_handler$error(e) When filling in my password, I did not include the " showing its a factor. Could that be the issue or would the password prompt appear again when filling in the incorrect password? — Reply to this email directly, view it on GitHub <#324>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ALOW2OYASTQJSUQBSJ6NQ43ZZ2YEJAVCNFSM6AAAAABPMDWXH2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3DMNRUGY4DQNA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[PieterjanVerhelst]

I tried again and added password without the "", but still got the error. When I tried Sys.setenv(pwd="*****"), it worked 👍 .

[PietrH]

There needs to be better error handling for issues with the credentials:

• When storing credentials, check if they work (small api call?), if they don't: report and ask for credentials again
• don't allow empty usernames "" (hitting enter too quickly)
• offer a way to reset the credentials, currently if you store them, the only way to reset is to restart your R session