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.
Since GetModelAsync is asynchronous, if it takes too long, RESTier routing won't get registered in time and all requests before the registration done will fail.
Also, in test runs sometimes 2 or more test methods run simultaneously, which leads to GetModelAsync called simultaneously for a same Api, the model pipeline will throw for lacking synchronization mechanism. I think this could be triggered in production when 2 services expose a same Api.
The text was updated successfully, but these errors were encountered: