StanBright
Repos
29
Followers
41
Following
50

Events

Created at 1 week ago
Created at 1 week ago
Created at 2 weeks ago

Rename paperclip-vips to paperclip_vips

Created at 3 weeks ago

WIP: migrating to kt-paperclip compatibility

Rename gem to kt-paperclip-vips

Fix Vips::Image.thumbnail arguments

Replace byebug with debug gem + add .tool-version file

Created at 3 weeks ago
issue comment
Make period on metrics page configurable via select

OK, thanks... I went through the docs again: The graphs only show data for the last hour and the data is only retained in Redis for 8 hours.

Apparently I had a misunderstanding between shown data and retained data.

Created at 1 month ago
issue comment
Make period on metrics page configurable via select

Thanks for your answer @mperham. I know it's odd. I double checked, and the data being kept is only 1h actually ¯_(ツ)_/¯

Created at 1 month ago
started
Created at 1 month ago
issue comment
Make period on metrics page configurable via select

SHORT_TERM = 8 * 60 * 60

Thanks @mperham, I'm using Sidekiq v7.0.2 (OSS) in three different projects, and it seems that metrics data is kept for 2h only. I couldn't find a relevant config or something related. Do you know what could be the reason?

Created at 1 month ago
issue comment
age() function in postgres not working as expected

Amazing response. Thanks!

Created at 1 month ago
Created at 1 month ago
opened issue
age() function in postgres not working as expected

Hi,

First, thanks for the amazing gem/engine you've built. It's an indispensable part of all my projects. Kudos!

I'm using the latest version of blazer (2.6.5 as of now), and I'm trying to incorporate the age() function from Postgres https://www.postgresql.org/docs/current/functions-datetime.html in some of my reports.

For example, showing the latest users and when they were created:

SELECT username, age(now() at time zone 'utc', max(created_at))
FROM users
ORDER BY created_at DESC

However, instead of date-time-in-words (e.g. "4 days 5 hours"), Blazer's UI returns/renders a float representing the age in seconds - an interval in Postgres. At the same, if I execute the same query in the DB console directly, I'm getting the expected string.

I'm wondering, is that behaviour expected is a kind of bug/known-issue?

Thanks, Stan

Created at 1 month ago
Created at 1 month ago
Created at 2 months ago
issue comment
Add opted_out? methods to upgrade guide

Out of curiosity, what's stopping this of being merged?

Created at 2 months ago
Created at 2 months ago
Created at 2 months ago
started
Created at 2 months ago