I have ”Always expand posts marked with content warnings” on in my settings, but CW-marked posts in the Android app still show as unexpanded.
I’m fairly sure this used to work until recently, and #87 being closed as ”completed” back in October would imply I wasn’t just imagining it.
I’m using a crypt-on-sftp remote, which was working just fine up until v1.65.2. With v1.66, attempts to sync to it now fail with ”optional feature not implemented”. I’ve not narrowed down whether it’s the crypt or the sftp layer, so I’m just reporting my (failing) test case below.
I did a bisect, and apparently this issue came in at f5f8678 (which was a fix for #6685).
rclone version)1.66.0
Ubuntu 22.04 (64-bit)
sftp
rclone copy /tmp remote:tmp)rclone sync a/ C:
rclone --config test.conf configmkdir -p ftp a/b # on the sftp remote; here I'm using localhosttouch a/test1 # on the sftp remoterclone --config test.conf sync a/ C: -vv # no problemstouch a/b/test2 # on the sftp remoterclone --config test.conf sync a/ C: -vv-vv flag (e.g. output from rclone -vv copy /tmp remote:tmp)2024/03/12 14:33:36 DEBUG : rclone: Version "v1.66.0" starting with parameters ["rclone" "--config" "test.conf" "sync" "a/" "C:" "-vv"]
2024/03/12 14:33:36 DEBUG : Creating backend with remote "a/"
2024/03/12 14:33:36 DEBUG : Using config file from "/home/jani/test.conf"
2024/03/12 14:33:36 DEBUG : fs cache: renaming cache item "a/" to be canonical "/home/jani/a"
2024/03/12 14:33:36 DEBUG : Creating backend with remote "C:"
2024/03/12 14:33:37 DEBUG : Creating backend with remote "S:ftp"
2024/03/12 14:33:37 DEBUG : sftp://jani@localhost:22/ftp: New connection 127.0.0.1:48814->127.0.0.1:22 to "SSH-2.0-OpenSSH_8.9p1 Ubuntu-3ubuntu0.6"
2024/03/12 14:33:37 DEBUG : sftp://jani@localhost:22/ftp: Shell type "unix" from config
2024/03/12 14:33:37 DEBUG : sftp://jani@localhost:22/ftp: Relative path resolved to "/home/jani/ftp"
2024/03/12 14:33:37 DEBUG : sftp://jani@localhost:22/ftp: Using root directory "/home/jani/ftp"
2024/03/12 14:33:37 DEBUG : test1: Size and modification time the same (differ by -995.288851ms, within tolerance 1s)
2024/03/12 14:33:37 DEBUG : test1: Unchanged skipping
2024/03/12 14:33:37 DEBUG : b/test2: Need to transfer - File not found at Destination
2024/03/12 14:33:37 DEBUG : Encrypted drive 'C:': Waiting for checks to finish
2024/03/12 14:33:37 DEBUG : Encrypted drive 'C:': Waiting for transfers to finish
2024/03/12 14:33:37 DEBUG : sftp://jani@localhost:22/ftp: Shell path "/home/jani/ftp/98.g/149.zkyz4.EACoEuq1.vgxzogr"
2024/03/12 14:33:37 DEBUG : sftp://jani@localhost:22/ftp: Running remote command: md5sum /home/jani/ftp/98.g/149.zkyz4.EACoEuq1.vgxzogr
2024/03/12 14:33:37 DEBUG : sftp://jani@localhost:22/ftp: Remote command result: ac83867dee807f03ee4f8f307cda1257 /home/jani/ftp/98.g/149.zkyz4.EACoEuq1.vgxzogr
2024/03/12 14:33:37 DEBUG : 98.g/149.zkyz4.EACoEuq1.vgxzogr: Parsed hash: ac83867dee807f03ee4f8f307cda1257
2024/03/12 14:33:37 DEBUG : b/test2.yuwiyok9.partial: md5 = ac83867dee807f03ee4f8f307cda1257 OK
2024/03/12 14:33:37 DEBUG : b/test2.yuwiyok9.partial: renamed to: b/test2
2024/03/12 14:33:37 INFO : b/test2: Copied (new)
2024/03/12 14:33:37 ERROR : Encrypted drive 'C:': not deleting files as there were IO errors
2024/03/12 14:33:37 ERROR : Encrypted drive 'C:': not deleting directories as there were IO errors
2024/03/12 14:33:37 ERROR : Attempt 1/3 failed with 1 errors and: optional feature not implemented
2024/03/12 14:33:37 DEBUG : test1: Size and modification time the same (differ by -995.288851ms, within tolerance 1s)
2024/03/12 14:33:37 DEBUG : test1: Unchanged skipping
2024/03/12 14:33:37 DEBUG : b/test2: Size and modification time the same (differ by -116.891668ms, within tolerance 1s)
2024/03/12 14:33:37 DEBUG : b/test2: Unchanged skipping
2024/03/12 14:33:37 DEBUG : Encrypted drive 'C:': Waiting for checks to finish
2024/03/12 14:33:37 DEBUG : Encrypted drive 'C:': Waiting for transfers to finish
2024/03/12 14:33:37 ERROR : Encrypted drive 'C:': not deleting files as there were IO errors
2024/03/12 14:33:37 ERROR : Encrypted drive 'C:': not deleting directories as there were IO errors
2024/03/12 14:33:37 ERROR : Attempt 2/3 failed with 1 errors and: optional feature not implemented
2024/03/12 14:33:37 DEBUG : test1: Size and modification time the same (differ by -995.288851ms, within tolerance 1s)
2024/03/12 14:33:37 DEBUG : test1: Unchanged skipping
2024/03/12 14:33:37 DEBUG : b/test2: Size and modification time the same (differ by -116.891668ms, within tolerance 1s)
2024/03/12 14:33:37 DEBUG : b/test2: Unchanged skipping
2024/03/12 14:33:37 DEBUG : Encrypted drive 'C:': Waiting for checks to finish
2024/03/12 14:33:37 DEBUG : Encrypted drive 'C:': Waiting for transfers to finish
2024/03/12 14:33:37 ERROR : Encrypted drive 'C:': not deleting files as there were IO errors
2024/03/12 14:33:37 ERROR : Encrypted drive 'C:': not deleting directories as there were IO errors
2024/03/12 14:33:37 ERROR : Attempt 3/3 failed with 1 errors and: optional feature not implemented
2024/03/12 14:33:37 INFO :
Transferred: 32 B / 32 B, 100%, 0 B/s, ETA -
Errors: 1 (retrying may help)
Checks: 5 / 5, 100%
Transferred: 1 / 1, 100%
Elapsed time: 0.3s
2024/03/12 14:33:37 DEBUG : 15 go routines active
2024/03/12 14:33:37 DEBUG : sftp://jani@localhost:22/ftp: Closing 1 unused connections
2024/03/12 14:33:37 Failed to sync: optional feature not implemented
Raudoitusrauta törröttää pyörätien laidalla.
Leveä lumipalle liikennevalonappipurnukoiden edessä tässä risteyksessä.
Tästä heräsi kysymys, että mitenkähän tarkasti lähiavaruutta nykyisin valvotaan. Jos sukkulaa käytettäisiin toisen valtion satelliitin nappaamiseen (luvatta), onnistuisiko se mahdollisesti todistusjälkiä jättämättä, vai seurataanko tällaisia avaruusaluksia maan pinnalta jo niin tarkasti, että syyllinen olisi ilmiselvä jo alusta asti?
@amyblais Alright, I finally managed to get through the signup. Here’s my suggestion, although it’s in moderation for now, so the link probably won’t work until it’s approved.
A ”Mark read” choice in push notifications about new messages, as seen in many IM apps, would be handy in Mattermost Mobile too. Currently the message can only be marked read by tapping the message to open the app (which is slow).
Vastaa viestiin sen kontekstissa (Mattermost Feature Idea Forum)
Hi @amyblais,
I could post this on the feature idea forum, but I can’t figure out how the signup on the site works. When I click on ”Create an account”, I get a prompt to verify my email address, and having done that, a page saying ”Go back to Production to finish logging in”. I don’t know what ”Production” is, and at no point was there any actual way to set up a password, so I can’t log in.
A ”Mark read” choice in push notifications about new messages, as seen in many IM apps, would be handy in Mattermost Mobile too. Currently the message can only be marked read by tapping the message to open the app (which is slow).
Have a ”Mark read” option underneath the expanded notification.
No ”Mark read” option, only ”Reply”.
I was on my Android device, saving URLs pointing to individual comments in threads at Ubiquiti’s Unifi forums, but later returning to them on my desktop realized that the hash (fragment) portion had been dropped, so that the URLs only pointed to the opening post. Hence, just one link (pointing to the first post) had been saved. This is pretty useless for threads spanning multiple pages, where finding an individual comment is tough without the exact link.
Here’s a (random) example of a URL pointing to the second comment on the third page of one thread. Sharing it from any of Android, iPhone or desktop results in a link pointing to the first post instead.