Skip to content
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

Fix fallback_speed vector access #5291

Merged
merged 4 commits into from
Dec 5, 2018
Merged

Fix fallback_speed vector access #5291

merged 4 commits into from
Dec 5, 2018

Conversation

ghoshkaj
Copy link
Member

@ghoshkaj ghoshkaj commented Dec 5, 2018

Issue

If there is an assymetric (more sources than destinations) matrix request and fallback_speed is used, garbage is returned, or it segfaults. This PR fixes this issue.

Tasklist

Requirements / Relations

Link any requirements here. Other pull requests this PR is based on?

@ghoshkaj ghoshkaj mentioned this pull request Dec 5, 2018
6 tasks
@ghoshkaj ghoshkaj merged commit 3d781e6 into master Dec 5, 2018
@ghoshkaj ghoshkaj deleted the fix-fallback_speed branch December 5, 2018 05:41
ghoshkaj added a commit that referenced this pull request Dec 5, 2018
* add failing cuke test

* correctly access durations vector

* changelog

* one more cuke test
ghoshkaj added a commit that referenced this pull request Dec 10, 2018
* Prepare RC.1

* Bump version.

* remove destination/sources length <= coordinates length check (#5289)

* Add node 10 builds to travis (#5246)

* Add node 10 builds to travis

* Add changelog

* bump version to rc5

* Fix fallback_speed vector access (#5291)

* add failing cuke test

* correctly access durations vector

* changelog

* one more cuke test

* bump rc version

* 5.20.0

* remove line from changelog about commit that isn't actually in here

* update CHANGELOG and osrm version in package.json for v5.20.0

* bump to restart appveyor
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants