-
Notifications
You must be signed in to change notification settings - Fork 4
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Link Data to Bundle fails with invalid accept header #139
Comments
I will look into milestone 2.5.0, starting next week... ETA |
This was a common issue with ':' based endpoints, i.e |
I had looked at this issue. I don't think we can do much about the situation here from SDK/Client side. Server enforce versioning check at endpoint through HTTP header which is ambiguous and contradict the endpoint use case condition. I can only feedback that ICAv2 backend adoption of "API versioning through media type / content type header" technique is a bit bleeding edge. This technique still have few standing caveats and ambiguity for endpoint versioning. See OAI feature request at OAI/OpenAPI-Specification#2142 |
On the second thought over the weekend, we can add this Accept header at SDK level. This would mean every client call is set to One has to overwrite v4 (or any later version) if wanting to switch When server-side started to deprecate Let me explore whether I can put some facade, in front... |
I have discussed this with Alexis. At the mo, we will keep this on hold and low prior as Alexis can work around with header switches. Non ideal, ACK. We shall revisit with milestone 3.0; whereas we may able to sort out neatly by rooting to newer / more modern generator version. |
Hello! I'm also encountering this error with from libica.openapi.v2.api.project_pipeline_api import ProjectPipelineApi
client_v3 = get_icav2_client(version=3)
project_pipeline_api = ProjectPipelineApi(api_client=client_v3)
project_pipeline_api.link_pipeline_to_project(project_id=project_id, pipeline_id=pipeline_id) fails with HTTP response body: {
"id": "cdd1e0a0-94ff-4e3c-9ff0-a54391c2f671",
"type": "about:blank",
"title": "ICA_API_004",
"status": 400,
"detail": "Invalid Accept Header",
"instance": "http://ica.illumina.com/ica/rest/api/projects/<project-id>/pipelines/<pipeline-id>",
"parameters": {},
"timestamp": "2024-08-21T02:33:40Z",
"method": "POST"
} for a variety of different target pipelines. Are there any updates for this bug? Or a projected release date for the patch? |
Hi @averyschiff, You might want to try the solution above
So in your case it's a matter of running the following methods on
You may wish to look at our other projects wrapica and icav2-cli-plugins if you'd rather not need to interact with the API and use just higher-level-functions instead |
We can make the SDK set default to |
I have added examples/issue_139.py script with comments to explain the situation and work around. |
The work-around is working great, thank you very much! |
Try
Fails with
Solution was to add the accept header in
The text was updated successfully, but these errors were encountered: