Skip to content

FAQs

In this article we try to explain the most frequently asked questions.

First steps

bundle install throws the error library not found for -lzstd when installing trilogy gem on my MacOS. What should I do?

  1. Check your zstd version that you have installed - ls /opt/homebrew/Cellar/zstd/
  2. Install trilogy by running gem install trilogy -- --with-opt-dir=$(brew --prefix openssl) --with-ldflags=-L/opt/homebrew/Cellar/zstd/1.5.0/lib using the correct version in the path at the end.

I get an authentication error with caching_sha2_password when using Trilogy. What should I do?

This is a known issue with caching_sha2_password (default auth plugin in MySQL 8.0+).

Trilogy requires either TLS or a Unix socket when using caching_sha2_password.

The quickest workaround is to switch the user to mysql_native_password: - not preferred

ALTER USER 'your_user'@'localhost' IDENTIFIED WITH mysql_native_password BY 'your_password';
FLUSH PRIVILEGES;

Or, when connecting locally via TCP, prefer forcing a Unix socket in config/database.yml:

development:
  adapter: trilogy
  socket: /tmp/mysql.sock # or /var/run/mysqld/mysqld.sock

Check your socket path:

SHOW VARIABLES LIKE 'socket';

Why this happens:

  • MySQL 8.0 switched default auth to caching_sha2_password, which requires an encrypted channel.
  • mysql2 handled this differently, while Trilogy is stricter.

Note: mysql_native_password is deprecated in MySQL 8.4+ and removed in MySQL 9.0, so the Unix socket approach is the better long-term fix.

Development

What to do when EASY VUE is not propagating changes I've made?

Probable causes:

  1. The browser is caching old assets (using hard reload in the browser)
  2. Webpack failed to build a new version (for example, on failure of linter, fix it)
  3. You haven't linked the easy_vue plugin before starting the rails server (restart rails server).
  4. Webpack doesn't recognize changes in the filesystem (restart webpack)
  5. Problem between the chair and the keyboard.

How to prepare Merge Request?

  1. Make sure you added link to task which is related to your merge request.
  2. In description of your merge request add everything which may be helpful for others to understand why is your changes about.
  3. Make sure you assigned your merge request to correct branch. See which branch to select here
  4. Assign merge request to correct group/person
  5. Make sure your pipeline is green and branch is up to date with the branch you want to merge your changes

When is the right time for release?

It depends.

If RYS is under heavy development - like a currently prepared feature which means lots of merge-requests there is no need to release RYS immediately after merge. But only once per "some period" after a big code-review.

On the other hand when you just fix langfile or do some small change (or maybe not so small) in RYS which is "stable" and there is no development - make sense to release it right after merge.

How to properly release?

See our release guidelines