We have a way of running the tests against
the actualy php-proxy script:
CYPRESS_INTEGRATION="php-proxy" make check
So let's remove the C++ implementation, so we don't
need to maintain a duplicated code.
Change-Id: Ie095a70a8175cc8cb4894905826d13762127b148
Signed-off-by: Tamás Zolnai <tamas.zolnai@collabora.com>
the final ruler offset
Unfortunately with the introduction of the Canvas layer,
the property of tiles (style. left) are no longer set
and it will cause an infinity value to calculate the rules
offset with the result of undefined behavior.
Instead, it is used the document bounds to get the top left
coordinate.
Change-Id: Icebb5409c5627cfd6437851b3985d442b5162757
This can happen on a 'savetostorage' which is after a failed load.
Change-Id: Iad26bf6415c772c8646a119b0454c202873d6860
Signed-off-by: Miklos Vajna <vmiklos@collabora.com>
As recommended by the GitHub Community Guidelines.
It is recognized by file name and featured to contributors
automatically in various ways.
Signed-off-by: Muhammet Kara <muhammet.kara@collabora.com>
Change-Id: Ic408627e39d565f006c6f8591e110bcc9e97c17e
As the comment describes, this is a temporary workaround.
The issue happens when nocaps is enabled, no doubt due
to the timing difference from the more common (and default)
caps-enabled case.
Change-Id: I742d7b9fd63f0babe8e1d45b968e09026d78debc
Signed-off-by: Ashod Nakashian <ashod.nakashian@collabora.co.uk>
std::ifstream's tellg() returns -1 on error.
This is handled very poorly and shows up as ULONG_MAX.
Luckily, we have Stat class that does the same
both more safely and more efficiently.
Without opening the file, we now get the necessary
information unambiguously.
Change-Id: I2448bc71e01b0f166a9dd66aa38a88ea97a50cdd
Signed-off-by: Ashod Nakashian <ashod.nakashian@collabora.co.uk>
And set the LOOL_LOGFILE envar only when
we have a path.
Change-Id: Ide5144c7e5aec5ddb9a5a6c32538e9e0a3a6ed0b
Signed-off-by: Ashod Nakashian <ashod.nakashian@collabora.co.uk>
The idea it to run an existing cypress test while
the same document is opened by a second user. The second
user does some activity (e.g. moving cursor, clicking, etc)
and we check whether it makes any interference with the first
user's view. The first user is doing the actual test's steps,
so we can see if interference breaks the assertions.
Now it's just a prototype for testing it in the CI setup.
Change-Id: I3e02c037754862d628c73bbb4b2d82ea84b8a719
This helps in case you deleted a remote branch using the GitHub web UI,
so the local view is outdated.
Change-Id: I98be33ea5712c66589f42b64e3462b76b84fbcc5
In some cases, the integration needs to paste the data directly to the
document, outside of our mechanism that detects whether we should use
the internal paste, or not.
Change-Id: I5e5de09a990ed68451af34dd208a81391a0e9cfa
It leads to the app being rejected when uploaded to App Store Connect.
The rejection email says:
ITMS-90176: Unrecognized Locale - The locale names used in
localization directories at ('Payload/Mobile.app/Settings.bundle/ca-VALENCIA.lproj')
are invalid. iTunes supports BCP47 but not the UN M.49
specification. Refer to the Language and Locale Designations guide
at https://developer.apple.com/library/content/documentation/MacOSX/Conceptual/BPInternational/LanguageandLocaleIDs/LanguageandLocaleIDs.html
for more information on naming your language-specific directories.
Change-Id: I0ede85c5cc65c203e93ff4b75e898a3faaef20e2
