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
The problem is only with files attached via file indexes. Would it be possible to amend the repository's REST API replies so that the client will work again? Alternatively, we could adapt the client to the new APIs and make a new release, but it would be better to keep the old APIs alive, if possible, so that even older versions of clients (that people might have around) continue working.
We should try to enrich the test suite to cover these early. The cernopendata-client has its own test suite, so this error is caught there; but we do not run it periodically, and since there are no test cases in the cernopendata-portal repository for this functionality, the problem was not caught before deployment.
The text was updated successfully, but these errors were encountered:
P.S. Note also the --no-expand client option that should list index files themselves, e.g. for record 1 the output should contain CMS_Run2010B_BTau_AOD_Apr21ReReco-v1_0001_file_index.json. Something to beware of when fixing this issue.
Current behaviour
After latest deployment, the
cernopendata-client
cannot get file locations for records that have file indexes:There is no output and there is no error code passed onto the user.
Expected behaviour
The output should look like:
Notes
The problem is only with files attached via file indexes. Would it be possible to amend the repository's REST API replies so that the client will work again? Alternatively, we could adapt the client to the new APIs and make a new release, but it would be better to keep the old APIs alive, if possible, so that even older versions of clients (that people might have around) continue working.
We should try to enrich the test suite to cover these early. The
cernopendata-client
has its own test suite, so this error is caught there; but we do not run it periodically, and since there are no test cases in thecernopendata-portal
repository for this functionality, the problem was not caught before deployment.The text was updated successfully, but these errors were encountered: