Segfault when trying to run GQOL query against empty set

clarisma / geodesk-py

Fast and storage-efficient spatial database engine for OpenStreetMap data

https://docs.geodesk.com/python

GNU Lesser General Public License v3.0

36 stars 0 forks source link

Segfault when trying to run GQOL query against empty set #50

Closed osmuser63783 closed 6 months ago

osmuser63783 commented 6 months ago

Trying to check if a traffic sign is part of a way with a highway tag or not:

traffic_signs = planet_240219("n[traffic_sign]")
traffic_signs[0].parents.ways("*[highway]")
Segmentation fault (core dumped)

(When reading this I thought challenge accepted, that's easy with Geodesk!)

clarisma commented 6 months ago

Thanks! I haven't been able to reproduce this, can you check if you have the latest releases?

This looks similar to #46 (Affected empty sets in general; fixed in v0.1.7)
Alternatively, it may be caused by #clarisma/gol-tool#105, which in some cases produced faulty encodings, which in turn caused access to nodes to fail (Fixed in GOL Tool 0.1.9)

osmuser63783 commented 6 months ago

OK this is odd. I was on Geodesk 0.1.7 and gol-tool 0.1.9. Now I've updated to 0.1.8 and 0.1.10 and re-built my GOL and I can no longer reproduce the issue. Nevermind, sorry about the false positive

clarisma commented 6 months ago

Thanks for checking this again. This may still be the sign of a latent bug. Does #51 still fail? (The weird part is that the crash occurred when accessing a relation, clarisma/gol-tool#105 only affected ways, but not relations)