Fueling Curiosity, One Insight at a Time

CLS i.e Cumulative Layout Shift a metric used to quantify the stability of the content on a website when it loads. Normally a layout Shift occurs whenever any element on the web page changes it position unexpectedly.

Major Reason that constitutes to CLS are :-
1. Images without dimensions
2. Dynamically Injected Content
3. Web Fonts (Fall back font getting replaced with the new font)
Steps to prevent CLS:-
1. Always include size attributes on your images and video elements, or otherwise reserve the required space with something like CSS aspect ratio boxes
2. Never insert content above existing content, except in response to a user interaction.
Resource I used to learn about this:-
• https://web.dev/cls/

In order to take a database dump or restore it on fly.io, use flyctl proxy 5499:5432 -a . Then one can do psql postgres://:@localhost:5499/ to connect to the remote db

Postgres index names are limited to maximum length of 63 characters.
If index name is longer than 63 characters while running rails migration it throws error

Index name 'index_external_reservation_airport_transfers_on_external_reservation_id' on table 'external_reservation_airport_transfers' is too long; the limit is 63 characters

Fix is to explicitly specify the index name

t.references :external_reservation, null: false, foreign_key: true, index: {:name => 'idx_external_reservation_airport_transfers_external_reservation'}

If we want to query data for specific pages we can use PageQuery, however we cannot directly access the data. We will need to first destructure it first and then it can be passed as props.

const IndexPage = (data) => {

Styled components : const Content = styled.div margin: 30px 10px; display: grid; grid-template-columns: repeat(auto-fill, minmax(200px, 1fr)); grid-gap: 2rem; ;
lorem ipsum

lorem ipsum will inherit all the styles passed in Content component

cc: @iffyuva

is this getting recorded now. Take 5

found in very hardway that typeorm has timestamp & timestamptz as types. and this works differently.

even if you have configured a gitlab-runner for gitlab-ci and the runner’s ssh keys or api keys are used to clone the repo into the runners environment, if the build is triggered by a person who is not the member of the project you will get below error.

fatal: remote origin already exists.
 Clean repository
 remote: You are not allowed to download code from this project.
 fatal: unable to access 'https://gitlab-ci-token:[MASKED]@example.gitlab.com/project.git/': The requested URL returned error: 403
 ERROR: Job failed: exit code 1

The error is slightly miss leading as it says gitlab-ci-token in it, but it is occurred due to the triggering entity not being member of the project. Even if the person who triggered the project has owner access in Gitlab and is not a member of the project, you will still see this error.

We can access iex console on compiled elixir app using remote_console utility command. https://alchemist.camp/episodes/remote-console-iex