Proceed regularly to exports in case of host failure #49
Reference in New Issue
Block a user
No description provided.
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
As currently face:
Note that I censored the document body, as well as:
Is last known (and history) of document state kept locally anyway in case of full host failure?
I confirm that can't write in document in such case.
Note that the second screenshot shows that it is not a problem with the first screenshot document which is the issue it seems, related to #43.
https://uptime.cryptpad.org/status/cryptpad does not denote issue since last 10 minutes.
Could use own instance otherwise. E2EE is maybe still preferable in such case.
Refreshing the webpage does not help.
Same issue on Chromium.
On another document have:
Note that can scroll the message it seems.
No button shown to create a new document it seems.
https://cryptpad.fr/contact.html
https://matrix.to/#/#cryptpad:matrix.xwiki.com
https://social.xwiki.com/@CryptPad
https://github.com/cryptpad/cryptpad/issues/ (even closed ones)
https://forum.cryptpad.org
do not seem to mention anything going on.
So let us wait a bit and ask on Element if necessary.
Maybe the servers are just slow, but respond after a time out.
I am trying to create an account to reproduce the issue, but face #50 for tens of seconds at least on my Linux Mint 22.1 Cinnamon Framework 13 Firefox.
https://cryptpad.fr/support/
for minutes at least.
https://matrix.to/#/!50jN0sbkQM2Vv0Zp2nMk7uMJF1jusDIn26Sae1o_ZBQ/$wyUhIJpwR-GCulYIPXUAS4Gp9GLjHnumAMrZ1r9V6hU mentions the issue.
for minutes such that my laptop overheated.
Is log out only local? If so, then I could have kept a copy of local state to possibly keep my read-only access. Well I am logged in on Chromium too, can list drive files and access my main one, so I am quite fine with that.
Would help the issue:
Now that the issue is solved hashing takes less than 3 seconds.