-
Notifications
You must be signed in to change notification settings - Fork 11
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
Upload FIDIL JSON to FIDIL endpoint #576
Comments
We could add this to the upload file menu in the project settings, see #479 |
The FIDIL upload is POST "hmi-server:8080:/fidil/structured/datasets/upload" with json body. To make this more general, how about defining an environment variable HMI_SEVER_HOST_PORT.
If |
Do you mean adding an |
@kyao I've added this in the backend, but how do we test it? |
@g1eb Please add the upload load menu item. Then I will test it over there at CausX by starting up an instance. |
I was just about to add the same comment hah, adding that button right now |
@kyao for some reason this was not tagged with a milestone, I just added M2 because it seems related to the other tickets generating and downloading the FIDIL files. |
I've added a button to upload the FIDIL files but the endpoint is still missing, i'm getting a 404 for the GET request to |
We got the button and the connection all set up, just need to figure out the ENV variable part and test with Ke-Thia being able to rebuild docker images over on the causx cluster |
@kyao have you had a chance to to rebuild the latest t2wml-web version on causx gitlab with that environment variable set? |
@devowit @g1eb When I select
Am I using the wrong |
And, for |
When I try uploading the FIDIL file on a causx instance, I am getting invalid json error. I think t2wml is trying upload the HTML 404 error message, instead of the actual JSON file. |
Looks like the endpoint is expecting a filename in the path? |
the endpoint you're looking at is for downloading the fidil json, not uploading it. You want it looks like you don't have the most up to date version, which is on causx branch of t2wml. @g1eb ? |
That's because Ke-Thia is using an older version of t2wml and t2wml-api as far as I can see from the git commit hashes he posted above. @kyao could you update the hash to be the latest in both repos? It would be the |
@g1eb Those hashes should be the latest, t2wml-api in |
@kyao if they want the whole endpoint to be configurable, that means we don't need HMI_SERVER_HOST_PORT anymore, right? just FIDIL_UPLOAD_ENDPOINT? |
hmm the hash specified in the Dockerfile-backend (why do we have 2 of those by the way?) is set to this:
|
@g1eb once we're fixing the hashes may as well update to the version with abhinav's copy annotation changes and my change to the environment variable that I just pushed. no clue why we have two docker files. where are you seeing that? I only see one... |
There is a Dockerfile in the Edit to add the links to those Dockerfiles: |
We discussed this issue with Ke-Thia today and here is the summary of that meeting:
|
re problem 1: |
@devowit After the meeting with @g1eb I tried again, and this time FIDIL json had content. Not sure what happened previously. Here is what is happening when I try running an instance at CX. The first error is when I tried to download the FIDIL JSON. The download was block because it was not served over HTTPS. Not sure why this particular request to the backend endpoint was blocked, but not other accesses to the endpoints were not blocked. The second error is when I tried to upload the FIDIL JSON. I am guessing our code is expecting a JSON and got back HTML instead? This could a problem on the CX side. But, we need better error check on our side. I have asked them on how get access to the logs. |
Looks like we need to add |
Issue with downloading the FIDIL file has been fixed, it was a trailing slash at the end of that url 3a6c05e Upload FIDIL file connection with |
The Fidil upload endpoint should be an environmental variable:
FIDIL_UPLOAD_ENDPOINT="hmi-server:8080:/fidil/structured/datasets/upload"
The text was updated successfully, but these errors were encountered: