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.

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

Submitted files not showing in client + "Failed" messages didn't? #909

Closed
ninavizz opened this issue Mar 11, 2020 · 3 comments
Closed

Submitted files not showing in client + "Failed" messages didn't? #909

ninavizz opened this issue Mar 11, 2020 · 3 comments
Labels
bug Something isn't working needs/reproducing

Comments

@ninavizz
Copy link
Member

Problem n°1

I submitted a message and a file as a new source, to the Jenntastic instance. On the workstation client, both came in quickly and clearly.

image

..
After the first journalist reply, I sent more files and messages. None appeared in the client. However, I was still able to send messages back to the source from the client, and those messages appeared to me in the Source UI.

When I went to check the Journalist web UI to see if the server had received things, indeed it had:
image

...
Conor theorized it could be a loss of the connection to the SD server, however I was still able to send replies to the source, from the client.

image

image

Note: I had deleted one reply in the Source UI, it is below—and I will follow a separate issue in the sd repo, for the dialog jankery:
image

Problem n°2

See in the above screenshots, that the Source UI shows moo to you and once more both as received, however the Client shows them as failed. That feels like a biggy problem to me.

@ninavizz ninavizz added the bug Something isn't working label Mar 11, 2020
@eloquence
Copy link
Member

eloquence commented Mar 11, 2020

Thanks for the detailed report, Nina! I'm unable to reproduce this with the latest client (master, not the nightly) in Qubes running against my own prod instance. Note for other testers: Nina's workstation is configured with v2 onion services, mine with v3.

(Nina clarified that this behavior occurred after a full system reboot.)

@redshiftzero
Copy link
Contributor

Problem 1 here should be resolved by #937, problem 2 is still outstanding

@zenmonkeykstop
Copy link
Contributor

no.2 is a known issue with replies (also related to #653). Closing this ticket.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs/reproducing
Projects
None yet
Development

No branches or pull requests

4 participants