Navigation Menu

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

Uploading a relation that has itself as a member causes SystemStackError #2023

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

Uploading a relation that has itself as a member causes SystemStackError #2023

openstreetmap-trac opened this issue Jul 23, 2021 · 1 comment
Assignees
@openstreetmap-trac
Labels
Component: api Priority: major Resolution: fixed Type: defect

Comments

@openstreetmap-trac
Copy link

Reporter: Ldp
[Submitted to the original trac issue database at 8.56pm, Thursday, 2nd July 2009]

I inadvertently added a relation as a member of itself (in JOSM), and tried to upload the change.

[unneccesary other members removed]

This comes back as a 500 from the API:

org.openstreetmap.josm.io.OsmTransferException: org.openstreetmap.josm.io.OsmApi
Exception: ResponseCode=500, Error Header=<SystemStackError: stack level too deep>,Error Body=<SystemStackError: stack level too deep
@openstreetmap-trac openstreetmap-trac self-assigned this Jul 23, 2021
@openstreetmap-trac
Copy link
Author

Author: iandees
[Added to the original trac issue at 7.00pm, Monday, 9th September 2013]

There are self-referential relations in the database now.

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

@openstreetmap-trac openstreetmap-trac

Labels
Component: api Priority: major Resolution: fixed Type: defect
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@openstreetmap-trac