Skip to content
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

error when no 201 response received from the server and we retry a job with deleted reply #833

Closed
sssoleileraaa opened this issue Feb 28, 2020 · 0 comments · Fixed by #837
Closed

error when no 201 response received from the server and we retry a job with deleted reply #833

sssoleileraaa opened this issue Feb 28, 2020 · 0 comments · Fixed by #837
Labels
bug Something isn't working
Milestone
Initial beta release

Comments

@sssoleileraaa
Copy link
Contributor

sssoleileraaa commented Feb 28, 2020 •
edited
Loading

Description

See part 2 of this comment; #820 (comment)

STR

  1. Set reply timeout to 0.01
  2. Run the client
  3. Send a reply and see it fail in the GUI
  4. Check the server to see that the reply exists in the replies table

Expected

If the reply exists in the replies table, it should show up as successful in the GUI

Actual

The reply shows up as failed
@sssoleileraaa sssoleileraaa changed the title error when no response received from the server and we retry a reply error when no 201 response received from the server and we retry a job with deleted reply Feb 28, 2020
@sssoleileraaa sssoleileraaa added the bug Something isn't working label Feb 28, 2020
@redshiftzero redshiftzero added this to the 0.2.0beta milestone Feb 28, 2020
@redshiftzero redshiftzero mentioned this issue Feb 28, 2020
Closed
@sssoleileraaa sssoleileraaa mentioned this issue Feb 28, 2020
Merged
3 tasks
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
bug Something isn't working
Projects
None yet
Milestone
Initial beta release
Development

Successfully merging a pull request may close this issue.

fix reply succeeds but still shows up as failed freedomofpress/securedrop-client
2 participants
@sssoleileraaa @redshiftzero