Results 16 comments of Stuart Frost

@AnubisSec yeah it looks to be an easy fix, I'll make a PR for @roovo to review.

I wasn't able to recreate this using Granite version 0.23.2. @confact is this still an issue? Here's the full script I used to try to recreate: ```crystal require "sqlite3" Granite::Connections...

I haven't been able to recreate this issue using version 0.23.2 of Granite and both sqlite or pg adapters - @confact is this still an issue for you? I've added...

I've resolved issues like this before by setting `export PKG_CONFIG_PATH=$PKG_CONFIG_PATH:$(brew --prefix openssl)/lib/pkgconfig/`

This is an interesting one to implement because the command line arguments can be a single file or a glob. In [glob_utils.cr#expand](https://github.com/crystal-ameba/ameba/blob/master/src/ameba/glob_utils.cr#L22-L27) the list of arguments are expanded and only...

Thanks - #394. I've tried all the edge cases I can think of and it work as I would expect.

I've tried a lot of options with [`String.new`](https://devdocs.io/crystal/string#new(bytes:Bytes,encoding:String,invalid:Symbol|Nil=nil):String-class-method) and couldn't fix this issue. I also tried manually getting the bytes out of the pointer and then initialise a string.

The Dockerfile was generated by [fly.io](https://fly.io) (my hosting provider) therefore I haven't ever built and run the image myself, I'd be happy to try to help you get it up...