Submitted job is missing a username

[grallewellyn]

But @bsatoriu says it is showing up in figaro
And once it fails it shows up

Maybe this is related to this:
Private Zenhub Image
? but queued isn't an option for me and the queued job doesn't show up even when I unselect this

[bsatoriu]

@grallewellyn I'm seeing queued jobs in OPS after subsequent testing. The initial problem of the missing queued job appears to have been caused by a missing username associated to my original job. Somehow, after submitting my initial job, no username was assigned to the job metadata and, therefore, went missing in HySDS as a user-less job. It appears the username was not included in the payload from ADE to the MAAP API.

[bsatoriu]

The username property that the Jupyter DPS extension is sending originates from this function: https://github.com/MAAP-Project/dps-jupyter-extension/blob/861ff55c8842c8b5334f5db0fdc6b7cf5109c543/src/utils/utils.ts#L50

In my case, it may be that my username was missing briefly while being reset from Keycloak? It seems like an edge case that we can just monitor and investigate later if it recurs.

[grallewellyn]

Figaro looks like this:

and test33 isn't showing up on my jobs list
Although the console has

and never indicates there was a problem getting the username

Next steps are I am going to add some print statements in dps to see if the frontend is submitting the username with the request

We believe this issue is different than the issue where a job might not show up when it is in the queued state, but then shows up when it is in the failed state

[grallewellyn]

This is happening fairly consistently for me. Here are some console logs

You can see in the highlighted line that dps-jupyter-extension successfully got my username when we launched the submit jobs window, however the job was still submitted with the username being null
Expanded version of same console logs, just showing what happens when submitJob

It seems pretty consistent that the username is being sent as null when you stop and restart a workspace, then open the submit jobs tab and submit a job. If you stop and restart a workspace then open the view jobs tab first or ay any point, then the username is correctly set and sent when you submit a job. I believe this is because this function

export const userInfoSlice = createSlice({
  name: 'UserInfo',
  initialState,
  reducers: {
    resetUsername: () => initialState,
    setUsername: (state, action) => {
      state.username = action.payload
    },
  },
})

Is not being called when you just open the submit jobs tab. This function is only called when you open the view jobs tab

So I think this shouldn't be too difficult of a fix @marjo-luc @bsatoriu