* adding a hello world end point in analytics service for customerio
* adding updateCustomerIoUser handler function
* setting up the function recordUserAnalyticsEvent
* removing hello function and adding end points for update and track function
* installing the node js source for customer io
* adding the the functions for identify and track events
* adding a properties property
* adding new API key
* cleaning some code and making some changes to make it work
* renaming function to include identify keyword
* adding some detailed succes messages and try catch blocks
* adding a temporary key for testing
* adding the env variable for key
* adding a fallback value for acceptance test, this will need more investigation later on
* deleting the controller, as the handler functions will directly be linked to the customerio queue, so we do not want this path anynmore
GitOrigin-RevId: 38e0cb713e5d6a14c70cdbfb2a7463c633746bbe
* Use opInflightSince to measure unsaved doc time
* Use performance.now() for lastAcked timestamp
* Use inflightOpCreatedAt
* Increase MAX_UNSAVED_ALERT_SECONDS to 15
* Increase MAX_UNSAVED_SECONDS to 30
* Increase FATAL_OP_TIMEOUT to 45000
* Convert "Connection lost" modal to a notification
GitOrigin-RevId: 2d4233723620fd03ce6d6c5795c48c33c0b2f92c
* Create script: remove_unconfirmed_emails.mjs
* Update script remove_unconfirmed_emails.mjs after pairing
Co-authored-by: Rebeka <rebeka.dekany@overleaf.com>
* Add user counts. Add timing
* Revert previous changes: just remove the fully unconfirmed emails
* Add tests on scripts/remove_unconfirmed_emails.mjs
* Update audit log so `removedEmail` is a string and doesn't break the admin-panel audit logs list
* Update remove_unconfirmed_emails to have a `--generate` and a `--consume` mode
* Update tests on remove_unconfirmed_emails
* Add tests checking that `--consume` doesn't delete any email
* Update script so `--consume` checks that emails shouldn't be deleted again!
* Update CSV path to `/tmp/...`
* Add test cases: deleted users, deleted email, comma in email
---------
Co-authored-by: Rebeka <rebeka.dekany@overleaf.com>
GitOrigin-RevId: 8c60b56bcdfa33bc6143d66c32a5f430fb76f6d7
* [server-ce] upgrade mongo to 6.0 in e2e tests
* [server-ce] upgrade mongo to 6.0 for CE dev-env
GitOrigin-RevId: 6a76297d32177a8b5a067d325e74bdb01971af30
* Use 2 columns for socket diagnostics
* Fixup time so it's never negative
* Add "Copy to clipboard" feature
GitOrigin-RevId: ba7bcc672287c2697afadd904ade315b4a39f954
* adding the right translations to match figma
* adding 2 more translations
* adding the correct styling for the translation
* adding the last translation
* removing unused button and extra line
* adding the p tags and necessary styling to remover margin bottom
GitOrigin-RevId: 97c47e53ee4ae13e95027c602521258f056a6bed
The default logger is "json-file", which writes json blobs and splits
stdout and stderr. We do not need to split and also can save on extra
serialization overhead in the docker daemon by switching the driver.
- use the cheaper "local" driver for containers that we need logs from
(test containers), the local driver streams stdout+stderr into a file
- use the no-op "none" driver for support containers that we do need any
logs from.
GitOrigin-RevId: 55c7cb7c91860e192b6d54354f4550a0ee9a672c
* [web] tests: rename User.upgradeFeatures to User.upgradeSomeFeatures
The upgrades features do not match with any plan.
* [web] make user feature changes in tests more reliable
* [web] fix schema for featuresOverride in tests
* [web] log in after upgrading features
GitOrigin-RevId: ac5b19c798712926c118b221c553540b413802cd
