search

microbiomedata / nmdc-runtime

Runtime system for NMDC data management and orchestration
https://microbiomedata.github.io/nmdc-runtime/
Other
7 stars 3 forks source link

Swagger UI shows "😱 Could not render response" when sending request to newly-updated Runtime instance #775

Closed aclum closed 1 week ago

aclum commented 1 week ago

Describe the bug Different behavior in swagger with list_from_collection_nmdcschema__collection_name__get end point between dev and prod. Note using curl produces the same results. Response is '😱 Could not render responses_Responses, see the console.'

To Reproduce Steps to reproduce the behavior: search by collection name of workflow_execution_set and a filter of {"id":"nmdc:wfmb-13-1v78b457.1"} on https://api-dev.microbiomedata.org/docs#/metadata/list_from_collection_nmdcschema__collection_name__get

Expected behavior 200 with a response json which can be downloaded, see runtime prod behavior on this same endpoint.

Example user story template: AS A {user|persona|system}, [INSTEAD OF {current condition}] I EXPECTED {result} [SO THAT {value or justification}] [NO LATER THAN {best by date}]

Screenshots

Screenshot 2024-11-14 at 2 54 36 PM

Acceptance Criteria Above query results in a 200 response code when executed in dev using the swagger UI.

eecavanna commented 1 week ago

It's working OK for me (i.e. I haven't been able to reproduce this).

image

Will you refresh the page in your web browser and try again?

eecavanna commented 1 week ago

I am wondering whether you have had the web page open for a few days, in which case, it might have been served up by the old version of the Runtime; but now is trying to interact with the new version of the Runtime.

eecavanna commented 1 week ago

Note using curl produces the same results.

hmm... if curl is also showing the error (I take it that's what you meant by "same results"), then a stale web page is not the issue (at least is not the only issue).

eecavanna commented 1 week ago

That error message looks to me like a Swagger UI error message; in which case, the "console" it's referring to is the web browser's JavaScript console.

eecavanna commented 1 week ago

I think I may have misinterpreted what you meant by "same results." Does curl produce the error for you also, or does curl fetch the results normally (i.e. with no error)? I'm talking about the development Runtime API, not the production one.

eecavanna commented 1 week ago

This is resolved. I think @aclum was using a Swagger UI web page that had been served up by the previous version of the (dev) Runtime. Since we updated the (dev) Runtime yesterday, that may have created some incompatibility between the "stale" Swagger UI page and the server. I don't know for sure because who knows what Swagger UI is doing under the hood.