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
When the Context.work setter fails to find a factory function for an operation, it tries to issue a log message on only the master rank. But in the current implementation, an MPI communicator is not acquired (if at all) until the work width is known and the Session is launching. This prevents useful handling of the error condition and instead creates a confusing Type error.
We should remove the check from Context.work. It should be implemented in the logging infrastructure instead, anyway.
The text was updated successfully, but these errors were encountered:
When the Context.work setter fails to find a factory function for an operation, it tries to issue a log message on only the master rank. But in the current implementation, an MPI communicator is not acquired (if at all) until the work width is known and the Session is launching. This prevents useful handling of the error condition and instead creates a confusing Type error.
We should remove the check from Context.work. It should be implemented in the logging infrastructure instead, anyway.
The text was updated successfully, but these errors were encountered: