Closed dudekw closed 8 years ago
The asio error: End of file
implies that the server hang up the connection abruptly.
I don't know why the server responds with no image file received.
I've checked the code and commited/pushed again, so make sure you pull first.
Can you pull
then make clean
and make
from start?
The following lines which I've added in includes/cloud/asio/asio_http/asio_http.cpp
27 std::cout << asio_handler::make_header(info, head_preamble_, content_length)
28 << post_;
should print out both header and post data to check if something is malformed.
TBH the platform errors are too generic, e.g., if a POST is malformed it should say so instead of the cryptic "no map image received".
EDIT
Just noticed that I've been sending a json
content disposition with a JSON, I've renamed it to map_name
and removed the JSON sending only a string, according to the platform spec - is this what you expect @klpanagi ?
Thank you!
Hi @alexge233, @klpanagi ! I tied to run the path_planner example and it failed. We've tested it with our cloud also. Python API call works well.
The map files are not being saved in the cloud.
Client log:
Cloud log: