[ws-daemon] Unexpected cannot find workspace during DisposeWorkspace

[aledbf]

Bug description

Steps to reproduce

Workspace affected

No response

Expected behavior

If it's not really an error condition, then change this to be a warning. The warning would essentially be an indicator that we're calling dispose 2 or more times, and the 1st time would have done disposal.

Example repository

No response

Anything else?

When does this error happen? Is it really an error? Is there anything else we can log with it, to determine the state of the workspace on the node (/workspace still exist?)

[kylos101]

👋 @jenting , may I ask you to focus on #11713, move this back to scheduled, and unassign yourself for now? This way you can focus on #11713. If you think there's a need to do both at the same time, can you share why? I'm not seeing the relationship, and am trying to limit work in progress.

[kylos101]

👋 @jenting alternatively, if you already started #11710, please move #11713 back to scheduled, etc.

[jenting]

From the Jaeger tracing, the observation is that we call the finalizeWorkspaceContent almost within the same time.

case 1.

case 2.