-
Notifications
You must be signed in to change notification settings - Fork 8
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
Exception in all/tracks.geojson - suspected MySQL 8 incompatibility with SQLAlchemy #295
Exception in all/tracks.geojson - suspected MySQL 8 incompatibility with SQLAlchemy #295
Comments
@obscurerichard does anything actually use the geo data? It appeared completely unused to me. |
There's 2 endpoints that use the geojson data:
See the code in freezing.web.views.api freezing-web/freezing/web/views/api.py Lines 184 to 256 in 8b773a2
freezing-web pulls on this library.
So from that standpoint we could remove the geojson library and the 2 API calls and have I'm actually far more worried about the code paths in |
The other projects all got updated to help with the fallout of freezingsaddles/freezing-web#295 and freezingsaddles/freezing-sync#56 This makes it possible to test tags for freezing-nq as well.
While doing some exploratory testing on freezingsaddles.org for Bump geojson from 2.5.0 to 3.1.0 #272 I got an exception
pymysql.err.OperationalError: (1305, 'FUNCTION freezing.AsBinary does not exist')
- this came from deep in the guts ofpmysql
andsqlalchemy
and . We need to triage this more and figure out what upgrades we need to do to get around this, preferably before the start of the 2025 season. This might extend intofreezing-sync
as well, since that uses some geometry related stuff too.This is an unintended consequence of #281 .
@obscurerichard has limited knowledge of the MySQL geospatial facilities and the supporting libraries so debugging this may be a challenge... also the tests for this area of freezing-web, freezing-model, and freezing-sync are almost non-existent.
Leads
BaseGeometry
to override `as_binary = 'ST_asText'Solution options
Security considerations
We might consider restricting who can call
all/tracks.geojson
and the related teams .geojson. We definitely should verify that there's no personally identifying information about the athletes in it. It looks like those geojson files could be used to build an awesome heatmap, but there's nothing in the code today that uses these.Error logs
The text was updated successfully, but these errors were encountered: