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

Uploading directory to site frequently fails - AuthdClientError("Failed to read response: connection closed: timed out") #1125

Open
S-Coyle opened this issue Dec 19, 2019 · 1 comment
Labels

Comments

@S-Coyle
Copy link
Member

S-Coyle commented Dec 19, 2019

macOS 10.5.1
SAFE Browser v0.15.4 Beta.2
SNAPP 0.0.5 Beta.1

Reproduction steps:

  • log in to SNAPP and launch the Browser via SNAPP.
  • create a new site and upload a directory, in my tests I used a folder containing a jpeg & an index.html which displayed that image,
  • edit the index.html, e.g. point it to another jpeg in the folder,
  • upload the folder again to create a new version of the site (v=2)
  • repeat the edit & upload of your site & after 1 or 2 uploads it consistently fails for me either by the upload button seemingly being unresponsive, or by the the upload not actually having any effect, i.e. the image I pointed the latest index.html to is not displayed, the previous version is still displayed.

Logs:
Only the background.log file has any information relating to this issue. The error below appears every minute in the log:

  • [error] Failed to authorise application: AuthdClientError("Failed to read response: connection closed: timed out")

SNAPP:
In SNAPP I'm also seeing multiple snapp windows appear (I'm undocked). This seems to match with the number of times I've clicked upload and it fails. E.g. if I click upload and it fails then I'll soon see another SNAPP window appear behind the previous window.

Not clear yet whether this issue is with Browser or SNAPP. Adding my notes here & I'll follow up tomorrow & try with the browser authenticated via the CLI to see if I can narrow it down.

@S-Coyle
Copy link
Member Author

S-Coyle commented Dec 20, 2019

Tested again today using the CLI to logon & authenticate the browser and I'm able to replicate the issue, so this indicates that the Browser is where the issue is.
I'm not seeing the same background.log entry that I added in my comment yesterday, doesn't appear to be any logs generated at all when the issue occurs

@S-Coyle S-Coyle added the bug label Dec 20, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant