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
We have a check in place for (custom) matrix size consistency. For example using "matrices": {"car": {"durations": [[0]]}} result in an adequate error if some location_index values are not zero. But the problem is that we somehow assume that a custom matrix is not empty. If it is, then based on its size in this check we behave as if no matrix was provided in input and try grabbing a non-existing routing wrapper.
This is really an edge case as there is no point in defining an empty custom matrix in input (probably why no-one reported this yet), but still we should handle this properly.
The text was updated successfully, but these errors were encountered:
We have a check in place for (custom) matrix size consistency. For example using
"matrices": {"car": {"durations": [[0]]}}
result in an adequate error if somelocation_index
values are not zero. But the problem is that we somehow assume that a custom matrix is not empty. If it is, then based on its size in this check we behave as if no matrix was provided in input and try grabbing a non-existing routing wrapper.With
"matrices": {"car": {"durations": []}}
:This is really an edge case as there is no point in defining an empty custom matrix in input (probably why no-one reported this yet), but still we should handle this properly.
The text was updated successfully, but these errors were encountered: