We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
There are several issues when running place connectivity builder for entire US data
place connectivity builder
Timeout in the middle
1000
500
While decoding float64 array in response, always met following issue
runtime error: invalid memory address or nil pointer dereference
Even when decoding at httpclient.Get still have such error
httpclient.Get
func (oc *osrmHTTPClient) send(req *request, c chan<- message) { resp, err := oc.httpclient.Get(req.url) glog.V(3).Infof("[osrmHTTPClient] send function succeed with request %s.\n" + req.url) m := message{req: req, resp: resp, err: err} c <-
After I changed the definition of table.response from
table.response
type Response struct { Code string `json:"code"` Durations [][]*float64 `json:"durations"` Distances [][]*float64 `json:"distances"` }
To
type Response struct { Code string `json:"code"` Durations [][]float64 `json:"durations"` Distances [][]float64 `json:"distances"` }
I don't met such issue any more. I think it might related with timeout and only part of data be loaded.
timeout
The text was updated successfully, but these errors were encountered:
fix: Adjust max destination count for table service and adjust table …
065c35f
…response's format issue: #267
CodeBear801
No branches or pull requests
There are several issues when running
place connectivity builder
for entire US dataTimeout in the middle
1000
to500
and such issue didn't happen any more.While decoding float64 array in response, always met following issue
Even when decoding at
httpclient.Get
still have such errorAfter I changed the definition of
table.response
fromTo
I don't met such issue any more. I think it might related with
timeout
and only part of data be loaded.The text was updated successfully, but these errors were encountered: