Skip to content

Frequently asked questions

First steps

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

  1. Check the installed zstd version: ls /opt/homebrew/Cellar/zstd/

  2. Install trilogy with the matching version in the path (1.5.0 below):

    gem install trilogy -- --with-opt-dir=$(brew --prefix openssl) --with-ldflags=-L/opt/homebrew/Cellar/zstd/1.5.0/lib

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

caching_sha2_password is the default authentication plugin of MySQL 8.0+ and Percona Server 8.x. Trilogy requires TLS or a Unix socket with it.

Connect through 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';

Do not switch the user to mysql_native_password: it is disabled by default since MySQL 8.4 and removed in MySQL 9.0.

Development

My frontend changes do not show up. What should I check?

  1. The browser serves cached assets: do a hard reload.
  2. The Vite dev server is not running: start it with bundle exec vite dev.
  3. The build failed: fix the error shown in the Vite output.
  4. Vite does not see file changes: restart it.

How to prepare merge request?

See Contributing for titles, descriptions and task references. Before you submit:

  1. Link the related task.
  2. Describe in the description why the change is made.
  3. Target the correct branch, see Branch naming conventions.
  4. Assign the merge request to the correct group or person.
  5. Make sure the pipeline is green and the branch is up to date with the target branch.

When is the right time for release?

A RYS under heavy development (many merge requests for a feature in preparation) does not need a release after every merge. Release it once after a larger code review.

A stable RYS with no ongoing development (a language file fix or another small change) is released right after the merge.

How to properly release?

See the release guidelines