You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
It seems, though, we will have to change the signature of SimpleJobManager.allocateJob, as that one will need to receive the logger URI explicitly. That means the call will fail with older jobmanagers. How much of an issue is that?
The text was updated successfully, but these errors were encountered:
This is now merged in both masters. THe URi is passed in Workflow metadata (Execution.Log_URI) but is sent as parameters when requesting job allocation from jobmanager — the respective local variable should be set before mupif is imported in the child process, to avoid (messy) log redirections later. More testing will be needed for sure, I am closing this now.
This needs some co-operation between mupifDB and mupif itself. There are currently branches https://github.com/mupif/mupif/tree/dev-log and https://github.com/mupif/mupifDB/tree/dev-log . Can @stanislavsulc have a look? They pass remote log URI parameter; it could be given to workflow as a part of metadata.
It seems, though, we will have to change the signature of SimpleJobManager.allocateJob, as that one will need to receive the logger URI explicitly. That means the call will fail with older jobmanagers. How much of an issue is that?
The text was updated successfully, but these errors were encountered: