-
Notifications
You must be signed in to change notification settings - Fork 33
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
Loading assets with the API #3
Comments
Hi! I tested the local SVL cloud with the existing quick start examples provided in LGSVL Python API repository and did not see errors like this. Can you share your complete script so I can take a closer look? When I was collecting data from WISE, I noticed some plugins seemed to have existed before but cannot be downloaded anymore. I remember seeing a plugin used for some competition but could not download it anywhere. |
Hi,
which I believe is the expected output, therefore I am not sure what happened on your end. I do think this is a setup issue and please do the following to debug this.
Regarding the WebSocket issue, it is caused by client container running React project in dev mode. I have pushed some updates to compile React project before serving it, you should no longer be seeing this error. This error also does not affect anything. |
Sorry for the delay. I tried it in another PC just in case and the error is the same. Also i can't access to the step 2 link. A white screen with 'Not found' appears. |
Thanks for the response! You need to be able to access the link for 2, because the downloading process requests resource from that url. I am very sure this issue is same as the later one. I need some help from you:
|
Is this what you need from 1. ?
Thank you! |
Hi! Thanks for the response! The screenshots are helpful! This file structure looks correct, but why do all files under maps have ".zip" ending? Maybe Google Drive added that when you are downloading. Can you remove all ".zip" from assets/maps filenames and see if it helps? |
In my last comment I misread your answer and I ran it with the -d flag.
So now I unzipped the maps and still don't work for me. Then I followed the steps in #4 (with and without maps because he did it without the maps folder) and I am stucked in the step docker-compose up --build again.
And goes on... I can't see the error but it seems in #4 after that he could download the map from http://localhost/api/v1/assets/download/bundle/0a4026cb-39eb-42ce-8065-26da778d2f74 When I use the -d flag i got the same in npm run start
I followed his steps so I don't know why it is different |
Hi, You don't need to use "-d" flag now that I (think I) know where the problem is. "-d" makes you see the output from each of the containers and normally just the last few outputs tell if any of the containers go wrong. You were not supposed to unzip the files, you just need to remove the ".zip" ending from the filename. Google for some reason added ".zip" to the end, and I never uploaded zip files. The server code will look for file /assets/maps/{id} when requesting a download, but now you have /assets/maps/{id}.zip, which is why the server cannot find the file for you. |
It works! Thanks a lot and congratulations for your work! |
Thank you for pointing out the issue as well! I added this note to the readme to hopefully help future users as well. |
Hello again. I am testing with the python API and I have some questions.
I downloaded the google drive maps, vehicles, puglins, hdmaps and previews. Why the identifiers numbers are not the same as the ones of the same maps, etc in the preview? Just curious
Also when loading some vehicles, errors like this appear
Like some sensor plugins couldn't be found. Could it be that the sensor plugins they are linked to, also have different identifiers? Do you know why could this be? For example, with Spectator Ego vehicle this error doesn't appear beacuse it doesn't have any sensor plugins.
The text was updated successfully, but these errors were encountered: