AssertFailedException: false

[spencerrecneps]

Expected behavior and actual behavior

Expected: returns results from a basic pgr_drivingdistance query

Actual: returns AssertFailedException error

Error message

ERROR:  AssertFailedException: false at /build/pgrouting-z9Xs4y/pgrouting-2.6.1/include/dijkstra/pgr_dijkstra.hpp:591
*** Execution path***
[bt]/usr/lib/postgresql/9.5/lib/libpgrouting-2.6.so(_Z13get_backtraceB5cxx11v+0x3c) [0x7f19a80b5a5c]
[bt]/usr/lib/postgresql/9.5/lib/libpgrouting-2.6.so(_ZN12Pgr_dijkstraIN9pgrouting5graph14Pgr_base_graphIN5boost14adjacency_listINS3_4vecSES5_NS3_14bidirectionalSENS0_12Basic_vertexENS0_10Basic_edgeENS3_11no_propertyENS3_5listSEEES7_S8_EEE39get_drivingDistance_with_equicost_pathsERSC_RKSt6vectorIlSaIlEERSt5dequeISF_ImSaImEESaISM_EEd+0x672) [0x7f19a810a9b2]
[bt]/usr/lib/postgresql/9.5/lib/libpgrouting-2.6.so(_ZN12Pgr_dijkstraIN9pgrouting5graph14Pgr_base_graphIN5boost14adjacency_listINS3_4vecSES5_NS3_14bidirectionalSENS0_12Basic_vertexENS0_10Basic_edgeENS3_11no_propertyENS3_5listSEEES7_S8_EEE29drivingDistance_with_equicostERSC_St6vectorIlSaIlEEd+0x515) [0x7f19a810d665]
[bt]/usr/lib/postgresql/9.5/lib/libpgrouting-2.6.so(_Z19pgr_drivingDistanceIN9pgrouting5graph14Pgr_base_graphIN5boost14adjacency_listINS3_4vecSES5_NS3_14bidirectionalSENS0_12Basic_vertexENS0_10Basic_edgeENS3_11no_propertyENS3_5listSEEES7_S8_EEESt5dequeI4PathSaISE_EERT_St6vectorIlSaIlEEdbRNSt7__cxx1119basic_ostringstreamIcSt11char_traitsIcESaIcEEE+0x162) [0x7f19a8110bc2]
[bt]/usr/lib/postgresql/9.5/lib/libpgrouting-2.6.so(do_pgr_driving_many_to_dist+0x2c0) [0x7f19a81079c0]
[bt]/usr/lib/postgresql/9.5/lib/libpgrouting-2.6.so(driving_many_to_dist+0x342) [0x7f19a8106da2]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(ExecMakeTableFunctionResult+0x414) [0x560254af1bc4]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(+0x218b17) [0x560254b06b17]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(ExecScan+0xd4) [0x560254af3894]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(ExecProcNode+0x1c0) [0x560254aec4e0]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(standard_ExecutorRun+0x10e) [0x560254ae951e]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(+0x306e9f) [0x560254bf4e9f]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(PortalRun+0x300) [0x560254bf6450]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(PostgresMain+0x1b1d) [0x560254bf3aed]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(+0xa15cb) [0x56025498f5cb]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(PostmasterMain+0x107b) [0x560254b9765b]

HINT:  
********** Error **********

ERROR: AssertFailedException: false at /build/pgrouting-z9Xs4y/pgrouting-2.6.1/include/dijkstra/pgr_dijkstra.hpp:591
*** Execution path***
[bt]/usr/lib/postgresql/9.5/lib/libpgrouting-2.6.so(_Z13get_backtraceB5cxx11v+0x3c) [0x7f19a80b5a5c]
[bt]/usr/lib/postgresql/9.5/lib/libpgrouting-2.6.so(_ZN12Pgr_dijkstraIN9pgrouting5graph14Pgr_base_graphIN5boost14adjacency_listINS3_4vecSES5_NS3_14bidirectionalSENS0_12Basic_vertexENS0_10Basic_edgeENS3_11no_propertyENS3_5listSEEES7_S8_EEE39get_drivingDistance_with_equicost_pathsERSC_RKSt6vectorIlSaIlEERSt5dequeISF_ImSaImEESaISM_EEd+0x672) [0x7f19a810a9b2]
[bt]/usr/lib/postgresql/9.5/lib/libpgrouting-2.6.so(_ZN12Pgr_dijkstraIN9pgrouting5graph14Pgr_base_graphIN5boost14adjacency_listINS3_4vecSES5_NS3_14bidirectionalSENS0_12Basic_vertexENS0_10Basic_edgeENS3_11no_propertyENS3_5listSEEES7_S8_EEE29drivingDistance_with_equicostERSC_St6vectorIlSaIlEEd+0x515) [0x7f19a810d665]
[bt]/usr/lib/postgresql/9.5/lib/libpgrouting-2.6.so(_Z19pgr_drivingDistanceIN9pgrouting5graph14Pgr_base_graphIN5boost14adjacency_listINS3_4vecSES5_NS3_14bidirectionalSENS0_12Basic_vertexENS0_10Basic_edgeENS3_11no_propertyENS3_5listSEEES7_S8_EEESt5dequeI4PathSaISE_EERT_St6vectorIlSaIlEEdbRNSt7__cxx1119basic_ostringstreamIcSt11char_traitsIcESaIcEEE+0x162) [0x7f19a8110bc2]
[bt]/usr/lib/postgresql/9.5/lib/libpgrouting-2.6.so(do_pgr_driving_many_to_dist+0x2c0) [0x7f19a81079c0]
[bt]/usr/lib/postgresql/9.5/lib/libpgrouting-2.6.so(driving_many_to_dist+0x342) [0x7f19a8106da2]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(ExecMakeTableFunctionResult+0x414) [0x560254af1bc4]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(+0x218b17) [0x560254b06b17]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(ExecScan+0xd4) [0x560254af3894]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(ExecProcNode+0x1c0) [0x560254aec4e0]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(standard_ExecutorRun+0x10e) [0x560254ae951e]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(+0x306e9f) [0x560254bf4e9f]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(PortalRun+0x300) [0x560254bf6450]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(PostgresMain+0x1b1d) [0x560254bf3aed]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(+0xa15cb) [0x56025498f5cb]
[bt]postgres: 9.5/main: gis san_jose 192.168.30.224(62435) SELECT(PostmasterMain+0x107b) [0x560254b9765b]
SQL state: XX000

Steps to reproduce the problem

Network table here.

Run the following query:

SELECT
    route.node AS node_id,
    route.agg_cost
FROM pgr_drivingdistance(
        'SELECT * FROM "tmp_net"',
ARRAY[28143,37447,43401,50409,91800,98234,108908,1888,1897,85914,1898,85930,112714,11851,31406,37961,43534,50994,57875,71749,77860,4424,4641,35309,53002,57762,75549,79856,80019,88626,89435,116859,37736,51812,97808]::INTEGER[],
        2680,
        equicost:=TRUE,
        directed:=TRUE
    ) route

Specifications like the version of pgRouting/PostGIS and PostgreSQL as well as Operating System

PostgreSQL version:
PostgreSQL 9.5.14 on x86_64-pc-linux-gnu (Ubuntu 9.5.14-1.pgdg18.04+1), compiled by gcc (Ubuntu 7.3.0-16ubuntu3) 7.3.0, 64-bit

PostGIS version:
POSTGIS="2.4.4 r16526" PGSQL="95" GEOS="3.6.2-CAPI-1.10.2 4d2925d6" PROJ="Rel. 4.9.3, 15 August 2016" GDAL="GDAL 2.2.3, released 2017/11/20" LIBXML="2.9.4" LIBJSON="0.12.1" LIBPROTOBUF="1.2.1" RASTER

pgr version:
(2.6.1,v2.6.1,1360698,release/2.6,1.65.1)

[cvvergara]

Will test as soon as possible

[cvvergara]

Found the problem: one of the vertices of the array is not in the edges table:

select * from tmp_net where source = 85930;
 id | source | target | cost 
----+--------+--------+------
(0 rows)

issue1152=# select * from tmp_net where target = 85930;
 id | source | target | cost 
----+--------+--------+------
(0 rows)

So, how I will fix it is: when the vertex is not in the edges table, it will return one row that contains

 seq |   node   | edge | cost | agg_cost
-----+----------+------+------+----------
   X |    85930 |   -1 |    0 |        0

[spencerrecneps]

Makes sense to me.