Matthew McGarvey

Validations: https://luckyframework.org/guides/database/callbacks-and-validations#validations I think the solution would be moving away from a table and to separate sections for each. I looked around for an existing pattern to follow in the...

🛑 This is a nuclear option I don't think we should recommend, see https://github.com/luckyframework/wordsmith/issues/17#issuecomment-834746709

https://github.com/luckyframework/lucky/issues/1255

@wontruefree It might be but we don't have anything in place to know whether or not they have that column and I'd be worried about that being unexpected behavior

The source of the problem is here https://github.com/luckyframework/website/blob/991937d21e572f56bfc10d95afbc410b786d69db/vendor/html2lucky/tags/tag.cr#L79-L81

So, I started going down this route, but it made me wonder, is a separate page for a specific query necessary? What if the list of queries that happened during...

@Liberatys of course! Let us know in discord if you need any help

My ideal workflow is that a github action would run a benchmark and comment on the PR "The benchmark ran in X, it's X% faster/slower than the master branch"

The error is pointing towards the more important issue of #21 but it still should not fail like this. If the process is dead, there's nothing to stop. Job done...

I think it might be connected to the fact that Overmind uses PTY (pseudo-terminals) which causes the command to think it's outputting to the terminal, while Nox does not so...