Closed asmunds closed 5 months ago
This a bug. Today we have a planning session for the upcoming 2-week sprint. I'll let you know about the outcome and possible timeline.
Great, thanks
Because of other urgent planned activities we didn't include this this issue into the new sprint. I'll inform you about the next planning session outcome in 2 weeks. Meanwhile please let me know about the urgency of this issue, so we can prioritize it better.
@asmunds, information from our planning session: the issue is included in our current sprint - starting today.
The issue was entirely on the Mesh server side. Now it is fixed and will be available in Mesh 2.14 which is planned to be released in June.
Okay, thanks!
Closing as not planned as there was nothing to be done on Mesh Python SDK side.
I am doing the following:
which returns an object with path
Model/Agder/Ulla-Førre
As you can see, the returned object does not correspond to the requested target. This seems to me to be erroneous behavior.
Note that the requested object does not exist. But still, I would expect an error message, not a wrong object.