faustinoaq changed the topic of #amber to: Welcome to Amber Framework community! | https://amberframework.org | Developer happiness, productivity and bare metal performance | GH: https://github.com/amberframework | Docs: https://docs.amberframework.org | Gitter: https://gitter.im/amberframework/amber | IRC Logger: https://irclog.whitequark.org/amber | Amber::Server.start
<FromGitter> <drujensen> @nsuchy Sorry about this. We are trying to get micrate fixed which also has a dependency on crystal-db
<FromGitter> <drujensen> you can update the pg to 0.19.0 and that should fix the discrepancy for your project
<FromGitter> <nsuchy> @drujensen I understand this a volunteer as you have free time project, I'm sorry if I came off a bit too assertively earlier. Thanks for the suggestion concerning PG. ⏎ ⏎ @Blacksmoke16 Considering the separate Granite bug that came up I posted a larger error trace https://github.com/amberframework/granite/issues/365#issuecomment-535733198
<FromGitter> <nsuchy> also I checked my shards file and I'm using pg 0.19.0 already.
<FromGitter> <Blacksmoke16> `VirtualMachine.all("WHERE ? = ANY(allowed_clients)", client.id_value)`
<FromGitter> <Blacksmoke16> try making that
<FromGitter> <Blacksmoke16> `VirtualMachine.all("WHERE ? = ANY(allowed_clients)", [client.id_value])`
<FromGitter> <Blacksmoke16> but thats prob the issue
<FromGitter> <nsuchy> @Blacksmoke16 that fixes the build issue
<FromGitter> <nsuchy> and my app starts
<FromGitter> <Blacksmoke16> 👍
<FromGitter> <Blacksmoke16> should really add some type restrictions to stuff tho
<FromGitter> <Blacksmoke16> would have made that prob a bit easier
<FromGitter> <nsuchy> the question is why didn't it work before?
<FromGitter> <Blacksmoke16> the value was being passed to `db#query` like `db.query statement, params`
<FromGitter> <Blacksmoke16> where that method is like `statement : String, *params`
<FromGitter> <Blacksmoke16> but now we're doing like `db.query statement, args: params` which requires it to be an array
<FromGitter> <nsuchy> ah I see
<FromGitter> <nsuchy> any other methods requiring an array?
<FromGitter> <nsuchy> or just the .all method
<FromGitter> <Blacksmoke16> they all do afaik
<FromGitter> <nsuchy> i need to re-read my app's codebase
<FromGitter> <nsuchy> figure out which methods need an array
<FromGitter> <nsuchy> everything seems to compile fine
<FromGitter> <Blacksmoke16> then you're prob good
<FromGitter> <nsuchy> awesome, thanks for that
<FromGitter> <Blacksmoke16> np
<FromGitter> <nsuchy> @Blacksmoke16 will you be leaving the new functionlaity as is or do you plan on converting the args into an array later on?
<FromGitter> <Blacksmoke16> dunno yet
<FromGitter> <Blacksmoke16> prob two methods, one with splat overload that calls the array one
_whitelogger has joined #amber
feepbot has quit [Ping timeout: 265 seconds]
feepbot has joined #amber
<FromGitter> <bendangelo> I found this issue `43 | (bcrypt_pass = self.password) ? bcrypt_pass == password : false ⏎ ⏎ ``` ^``` ⏎ ⏎ Warning: Deprecated Crypto::Bcrypt::Password#==. Use `Crypto::Bcrypt::Password#verify` [https://gitter.im/amberframework/amber?at=5d8df7ba0e829f6047367ca5]
<FromGitter> <bendangelo> I think the auth generated code needs to be updated. Just letting you know
<FromGitter> <nsuchy> If anyone wants to review/merge this
<FromGitter> <nsuchy> Does Docker work on Windows for Amber?
<FromGitter> <nsuchy> I get this error when I try to start docker compose, ERROR: for ulayerpanel_migrate_1 Cannot create container for service migrate: b'Drive has not been shared'
<FromGitter> <nsuchy> Also
<FromGitter> <nsuchy> I see a commit that fixes the database issues, but no new release
<FromGitter> <nsuchy> is something blocking the release of a new amber version?
<FromGitter> <nsuchy> nvm I got it working
<FromGitter> <nsuchy> had to pull amber master though
<FromGitter> <sam0x17> just an FYI guys, I'm working on duktape-based crystal shards that bring in uglify-js, html-minifier, and clean-css from the npm world so we can run them directly in crystal -- might be a good way to replace the `node` dependency in amber (and other frameworks)
<FromGitter> <charleystran> Hey all. I am getting the following error when my app compiles and I cant for the life of me find where in the source its being triggered. anyone have any debugging tips ```In /usr/local/Cellar/crystal/0.30.1/src/enumerable.cr:37:16 ⏎ ⏎ 37 | abstract def each(&block : T -> _) ⏎ ⏎ ``` ^---``` ... [https://gitter.im/amberframework/amber?at=5d8e69c4deb6da63d7bc72c1]
<FromGitter> <Blacksmoke16> make sure you're declaring your block types
<FromGitter> <Blacksmoke16> if you're reopening/extending that type
<FromGitter> <charleystran> I am not doing anything like that. I actually tried to comment out all of my calls to each to pinpoint it but no luck
<FromGitter> <Blacksmoke16> hmm
<FromGitter> <sam0x17> this is gonna be one of those like missing space before a `:` errors
<FromGitter> <sam0x17> or something totally innocuous and seemingly unrelated
<FromGitter> <charleystran> is there anyway to get more out of the stack trace
<FromGitter> <sam0x17> `--error-trace` I think
<FromGitter> <charleystran> I tried that, no difference
<FromGitter> <sam0x17> is there a point where you remove a line / series of lines / file where the error stops?
<FromGitter> <charleystran> I am trying that now, but I am onto areas of the code I havent touched in a very long lime
<FromGitter> <sam0x17> did this start happening with the 0.31.0 upgrade?
<FromGitter> <charleystran> I think so. I havent worked on this project much.
<FromGitter> <sam0x17> you probably have to update amber
<FromGitter> <sam0x17> someone will probably chime in a bit and say "oh, that's one of the errors a non-upgraded amber would get" I would guess
<FromGitter> <charleystran> ill give it a shot
<FromGitter> <sam0x17> 👍
<FromGitter> <sam0x17> do `shards update` on the project AND update your local installation of amber
<FromGitter> <charleystran> I am going to have to come back to this one. the update is throwing other errors
<FromGitter> <charleystran> ```Fetching https://github.com/will/crystal-pg.git ⏎ Error resolving db (~> 0.7.0, ~> 0.6.0)``` [https://gitter.im/amberframework/amber?at=5d8e71ba66c8b451222b1cf5]
<FromGitter> <elorest> This issue was actually only and issue with micrate. It is solved now. ⏎ ⏎ https://github.com/amberframework/micrate/issues/44