-
Notifications
You must be signed in to change notification settings - Fork 2
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.
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
Non-intuitive error message when token is invalid #23
Comments
Error above is from STABLE / device-code flow. SUMO VERSIONS: IN THE CONSOLE where ert gui was run: ert gui drogon_design.ert NOTE! Please login to Equinor Azure to enable Sumo access: we opened a login web-page for you in your browser. Failed Equinor Azure login for Sumo access, one possible reason is timeout NOTE! Please login to Equinor Azure to enable Sumo access: we opened a login web-page for you in your browser. Failed Equinor Azure login for Sumo access, one possible reason is timeout THEN IN THE SUMO_UPLOAD JOB IS LOOKS LIKE THIS: INFO:fmu.sumo.uploader._sumocase:Filepath: /scratch/fmu/rowh/drogon-kmdotst-2--devdec-01/realization-0/iter-0/share/results/polygons/topvolon--gl_faultlines_extract_postprocess.csv INFO:fmu.sumo.uploader._sumocase:Filepath: /scratch/fmu/rowh/drogon-kmdotst-2--devdec-01/realization-0/iter-0/share/results/polygons/basevolantis--gl_faultlines_extract_postprocess.csv INFO:fmu.sumo.uploader._sumocase:Filepath: /scratch/fmu/rowh/drogon-kmdotst-2--devdec-01/realization-0/iter-0/share/results/polygons/topvolantis--gl_faultlines_extract_postprocess.csv INFO:fmu.sumo.uploader._sumocase:Filepath: /scratch/fmu/rowh/drogon-kmdotst-2--devdec-01/realization-0/iter-0/share/results/polygons/toptherys--gl_faultlines_extract_postprocess.csv |
A user got the error printed below in
stderr
. When runningsumo_login
afterwards, she is taken through the device code flow process. So looks like her token was not valid. However, it is not possible to read from the error message that this is the issue.Related to proxy...?
Any way we can/should detect this and provide clearer message?
The text was updated successfully, but these errors were encountered: