I just tested uploading from the Nextcloud app, and it is similarly affected: no conflict dialog is shown and the existing file gets overwritten.

Steps to reproduce

1. Have a PDF file with the name ”ä.pdf” (sic) in your Nextcloud.
2. Have a different PDF file with the same name on your IOS device (Files app).
3. Choose to share the file from your IOS device to Nextcloud.
4. Select the folder where ”ä.pdf” already exists.
5. Upload.

Expected behaviour

Get a dialog to choose how to deal with the filename conflict.

Actual behaviour

No dialog. The the existing file is silently overwritten by the newly shared file.

Logs

Nothing in server logs, but here’s the app log (at the default level).

Reasoning or why should it be changed/implemented?

The issue leads to data loss. I discovered this when I realized that saving bills from my banking app by sharing them to my Nextcloud had been doing this for who knows how long. (My electricity bills have the service provider name, ”Oulun Energia Sähköverkko Oy” in their filename.)

Environment data

iOS version: 17.0.3

Nextcloud iOS app version: ”Nextcloud Liquid for iOS 4.9.1.0”

Server operating system:

Web server: Apache 2.4.41

Database: MySQL/MariaDB 10.3.38

PHP version: 8.2

Nextcloud version: 27.1.3.2

Miscellaneous

• This is not reproducible on Android (with my server), which is why I’m pretty sure the fault lies with the IOS app.
• Also not reproducible on IOS with filenames with ASCII-only names (FWICT); this general case was apparently fixed when first reported as Upload via Share Menu Silently Overwrites Existing Files #1737.

Summary

As of this writing, push proxy v5.25.0 was released 5 days ago, but the published assets on Github only include the source code.

Steps to reproduce

As per documentation,

wget https://github.com/mattermost/mattermost-push-proxy/releases/download/v5.25.0/mattermost-push-proxy.tar.gz

Expected behavior

Receive mattermost-push-proxy.tar.gz

Observed behavior (that appears unintentional)

404 Not Found

I have the same issue. I’m doing this in a Linux container (Ubuntu 20.04 inside Ubuntu 20.04), but like matthaios-easy-bi, I’m using npm run build:android to build (as per documentation). This has worked up until 2.0, but with 2.1 it always fails due to non-existent org.webrtc. Manually running npm install prior to npm run build:android makes no difference, nor does node node_modules/react-native-webrtc/tools/downloadWebRTC.js (although it does seemingly download the package successfully).

Here’s excerpts from the build output.

25.0.3 (as indicated by output from `occ –version` above).

The exit code issue is still there:

# sudo -u www-data /usr/bin/php /var/www/nextcloud/occ --version
Nextcloud 25.0.3
# sudo -u www-data /usr/bin/php /var/www/nextcloud/occ files:scan -- nonexistantuser
Unknown user 1 nonexistantuser
+---------+-------+--------------+
| Folders | Files | Elapsed time |
+---------+-------+--------------+
| 0       | 0     | 00:00:00     |
+---------+-------+--------------+
# echo $?
0

In fact the man page seems to be completely out of sync with reality. None of minage, maxage, minsize and maxsize appear to work at all despite being documented there. Minage is read at least (according to debug output), but then still ignored. Specifying minsize or maxsize has no effect, logs are rotated when they hit 1 M regardless. At least the plain `size` directive does appear to work as documented.

The man page for logrotate says ”Each configuration file can set global options (local definitions override global ones, and later definitions override earlier ones)”. This is inconsistent with how it actually behaves.

== Steps to reproduce ==
$ logrotate –version
logrotate 3.14.0

Default mail command: /usr/bin/mail
Default compress command: /bin/gzip
Default uncompress command: /bin/gunzip
Default compress extension: .gz
Default state file path: /var/lib/logrotate/status
ACL support: yes
SELinux support: yes
$ mkdir /tmp/logrotest
$ cd /tmp/logrotest
$ touch test.log
$ touch other.log
$ cat >logrotate.conf
/tmp/logrotest/*.log {
minsize 5M
}

/tmp/logrotest/test.log {
minsize 1M
}
$ logrotate –state /tmp/logrostate logrotate.conf

== What happens ==
error: logrotate.conf:5 duplicate log entry for /tmp/logrotest/test.log

== What I expect to happen instead ==
No error, test.log being processed with its specific, later-defined directives.

Hi @hmhealey,

Yes, it’s mainly about expectation. For an actual use case, I noticed this when mentioning an IRC channel name, which became a long, distracting and useless hashtag link, exacerbated by agglutination and multi-word hyphenation typical in Finnish, (e.g. #channelname-irc-kanavalla). I tried to make it less distracting by editing in a preceding backslash, only to discover that it didn’t work here.

Summary

There is no way to escape a word-starting hash character (#) in plaintext.

Steps to reproduce

In MM 7.3.0, post this, verbatim: \#anything

Expected behavior

#anything

Observed behavior (that appears unintentional)

#anything

Possible fixes

Workaround: instead of ”\#anything”, post this: &#​35;anything

Using backticks (`\#anything`) also works, but obviously the word then gets formatted as code and not plaintext.

Other notes

This is mainly an issue of inconsistency and surprise: backslash works to escape most other special formatting, so I’d expect it to work here too.