Skip to content
This repository has been archived by the owner on Jul 24, 2021. It is now read-only.

Railsport will successfully upload a GPX trace even if it can't write it to disk #1926

Closed
openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Closed

Railsport will successfully upload a GPX trace even if it can't write it to disk #1926

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Assignees
@openstreetmap-trac
Labels
Component: website Priority: critical Resolution: wontfix Type: defect

Comments

@openstreetmap-trac
Copy link

Reporter: avarab[at]gmail.com
[Submitted to the original trac issue database at 7.18pm, Saturday, 6th June 2009]

Start railsport

Don't create /home/osm

Upload GPX trace

Rails will throw an exception saying /home/osm doesn't exist, but it'll still create an entry for the trace in the database (and it'll show up on /traces).

Another exception is generated when trying to download the trace data, which of course doesn't exist in /home/osm/traces/NUM.gpx since /home/osm doesn't exist.
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: tom[at]compton.nu
[Added to the original trac issue at 11.05pm, Saturday, 6th June 2009]

This is hard to avoid because we need to add the record to the database to get the ID number before we can move the file to it's final home because the ID is used in the filename.

The record will be deleted when the import daemon comes along and finds the file doesn't exist.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@openstreetmap-trac openstreetmap-trac

Labels
Component: website Priority: critical Resolution: wontfix Type: defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openstreetmap-trac