Quick view top panel displays no data for an experiment

[kinow]

Hi, I accessed t033 as I thought this was an experiment that @ainagaya had used for some tests (I was reviewing an issue from @mcastril & @TracyMcBean), but the top panel of the quick view has no data. There are no warnings, and no errors displayed.

I think we may have a bug somewhere, causing this data to not be displayed? Not sure if the experiment was moved, or if it's an issue between AS versions, etc.

[LuiggiTenorioK]

It is not returning anything since the config parser fails giving the same error as described in BSC-ES/autosubmit-api#173

The description should be returned even if it fails after this API patch: BSC-ES/autosubmit-api#165

Also, the error message of the upper bar is properly included in the new upper bar patch: #219

Both patches are already merged, it is a matter of waiting for the release and update 👍

[LuiggiTenorioK]

@kinow Ulf updated the API some time ago with the BSC-ES/autosubmit-api#165 patch. Now, if you visit https://climatedt-wf.csc.fi/experiment/t033/quick it shows the data it can get.

I think this issue can be closed now ✅

[kinow]

@kinow Ulf updated the API some time ago with the BSC-ES/autosubmit-api#165 patch. Now, if you visit https://climatedt-wf.csc.fi/experiment/t033/quick it shows the data it can get.

I think this issue can be closed now ✅

@LuiggiTenorioK do you know why the user is still not displayed?

If I enter the VM, I can see that the experiment belongs to Ivan:

$ stat . | grep "Uid"
Access: (0755/drwxr-xr-x)  Uid: ( 1083/ ivan'suser)   Gid: (10000/autosubmit_users)

And if I open the current metadata/experiment_data.yml I can see that the HPC is LUI,

$ grep "HPCARCH" experiment_data.yml -m 1
  HPCARCH: LUMI

I think the branch or other Git info displayed at the right hand side should be available too, by inspecting the proj folder, or conf, perhaps.

Why is it that that information cannot be displayed in the GUI? Is it because of a compatibility issue between API & parser now?

Thanks!

[LuiggiTenorioK]

do you know why the user is still not displayed?

This is because there is a class that retrieves the data from the yml files and the filesystem stats which I realized always tries to get the jobs data. It fails because the yml file doesn't have the JOBS section making it fail when trying to get the user data from the dir stats data.

What I did in the API was to avoid the DB data failing when the config parser fails but not the directory data.

Maybe the correct solution is to stop using that annoying class.

---

Nevertheless, about the error that causes it (that also is shown in the other pages of that experiment: 'JOBS'), I left a question in a config parser PR: BSC-ES/autosubmit-config-parser#68 (comment)

Should these methods raise an error or should they return a default value when they fail? 🤔

[kinow]

Maybe the correct solution is to stop using that annoying class.

😆 🤣 😄

Nevertheless, about the error that causes it (that also is shown in the other pages of that experiment: 'JOBS'), I left a question in a config parser PR

👍