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.

Sign up for GitHub

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

Jump to bottom

Map - improve UX for long-running requests that fail with a 502 proxy error #1242

Open

bobular opened this issue Oct 22, 2024 · 1 comment

Labels

bug

Member

bobular commented Oct 22, 2024

hat tip: @aurreco-uga

Megastudy, default marker variable (species) then do a "timeline histogram" of collection start date

Overlaying with species breaks it for me (though it works on a second attempt)

bobular added the bug label

Member

aurreco-uga commented Oct 23, 2024

what i observed in this case is that rserve takes longer than a minute.. the service ends with 200 (logs do not show awareness of the problem)..

the rserve developer should check why this takes longer than a minute....
and if we are okay with this happening, or in general i wonder if the client should grab teh proxy error and tell the user something generic about the request is too big? or too slow? and that they should try with less data.

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