You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
click "ungeoreference" on this layer to completely start over
now the entire map overview page gets a 502 error.
after a minute or so, the 502s go away and everything is back to normal.
Expected behavior
No 502 errors.
Additional Context
I'm guessing that this is caused by an "orphan" session not being properly deleted during the "ungeoreference" process, specifically the session that had been created in step 1 above but then was abandoned. At this point, the session would stick around until the cleanup process deletes it, but accessing the session.lyr2 attribute, for example, would fail because the layer no longer exists.
A better way to handle this would be to introduce a "void" status for sessions, such that they don't need to be deleted when the "ungeoreference" or "unprepare" actions are taken. This would be ideal, but will have other implications that need to be thought out.
The text was updated successfully, but these errors were encountered:
mradamcox
changed the title
[Bug] 502 errors on map overview after ungeoreference "sometimes"
[Bug] 502 errors on map overview after ungeoreference sometimes
Dec 28, 2024
Describe the problem
@oxguy3 reported this series of actions:
Expected behavior
No 502 errors.
Additional Context
I'm guessing that this is caused by an "orphan" session not being properly deleted during the "ungeoreference" process, specifically the session that had been created in step 1 above but then was abandoned. At this point, the session would stick around until the cleanup process deletes it, but accessing the
session.lyr2
attribute, for example, would fail because the layer no longer exists.A better way to handle this would be to introduce a "void" status for sessions, such that they don't need to be deleted when the "ungeoreference" or "unprepare" actions are taken. This would be ideal, but will have other implications that need to be thought out.
The text was updated successfully, but these errors were encountered: